@Mads if your only concern with making `break` optional in `case` is breaking the automatic fall-through between empty cases when there is a semi-colon (empty statement), just make that empty statement a warning. People can easily remove it if they want fall-through.
Great move with the non-nullable default syntax. Thank you very much for this!
Why exactly is tuple deconstruction not unified with pattern matching decomposition? It's mentioned in the video that it's a shame it's not but I couldn't find any reason why anywhere.
I mean, I can see that these two usecases aren't 100 % overlapping but they're (IMHO) overlapping enough so that having them not-unified could produce a lot of confusion, code duplication, ...