make experimental pattern typing features mutually exclusive
This aims to reduce the complexity needed in the boolean logic for telling which rules we're using to type patterns. If we still want the functionality this removes, we can re-add it later, after some cleanup to pattern typing.
This commit is contained in:
parent
1f81f90689
commit
550b0ad036
5 changed files with 16 additions and 184 deletions
|
@ -718,7 +718,8 @@ impl Features {
|
|||
|
||||
/// Some features are not allowed to be used together at the same time, if
|
||||
/// the two are present, produce an error.
|
||||
///
|
||||
/// Currently empty, but we will probably need this again in the future,
|
||||
/// so let's keep it in for now.
|
||||
pub const INCOMPATIBLE_FEATURES: &[(Symbol, Symbol)] = &[];
|
||||
pub const INCOMPATIBLE_FEATURES: &[(Symbol, Symbol)] = &[
|
||||
// Experimental match ergonomics rulesets are incompatible with each other, to simplify the
|
||||
// boolean logic required to tell which typing rules to use.
|
||||
(sym::ref_pat_eat_one_layer_2024, sym::ref_pat_eat_one_layer_2024_structural),
|
||||
];
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue