Michel Hermier

I think we should enforce the block after the ':' for multiline to follow the logic of the rest of the grammar. Single line statement is a bit confusing, but...

In that case I suggest that the keyword `fallthrough` is added, and must be the last expression in the block. Having `switch` nested in loops is pretty frequent and reusing...

Well it can be augmented in a second revision. This is a bare minimum so it is working.

I don't understand the point of the `|` as a separator, parsing wise at best it serve as a separator for blocks but it fells out off place for some...

In all the case `_` as default is not an option since it is a valid member variable name.

Don't use acronym, autocompletion is a thing since more than 10 years... Also, I really don't like that each case is specific, it implies special handling in the compiler for...

My solution is a little bit more elegant, you only have to trick the compiler to dupe the value on each case, and start evaluating from there. While it seems...

There is some precedence somewhere also with the operator `~=` at least on lua and probably other. But considering the wanted usage, it looks odd... I still have some reservations,...

`~=` does not really make any sense as an assignment operator, because `~` as no meaning as a binary operator (as for `!`), and because of the nature of it...

Both `~~` and `~=` are fine for me, I only prefer the second one because of the symmetry with the other equality operators. The biggest reservations I have is about...