ML-style patterns are held as a future direction
This commit is contained in:
parent
25911d7c9d
commit
db7f703c0e
6
TODO.org
6
TODO.org
@ -296,9 +296,9 @@ keyword resolves against the expected type and against nothing else, so two enum
|
||||
could always share a member spelling. What the prefix buys is the call site read
|
||||
on its own.
|
||||
|
||||
** TODO ML-style patterns
|
||||
Wanted: nested destructuring (data cases, structs, arrays, slices), guards, or-patterns,
|
||||
literals at any depth, and exhaustiveness checked over the nesting. Needs a design pass.
|
||||
** WAIT ML-style patterns
|
||||
Held 2026-09-25 as a future direction, like the JS backend: nested destructuring,
|
||||
guards, or-patterns, literals at any depth, exhaustiveness over the nesting.
|
||||
|
||||
** NEXT match over numbers and strings
|
||||
Decided 2026-09-25: a match arm's pattern can be an integer, a float, a char or a
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user