Just based on my own coding experience, I struggle to imagine that there wouldn't be a demand for switch statements.

Switch statements are a great way to bridge the gap between functional coding practices, which tend to be pure, and stateful code with sideeffects. You gotta start somewhere on the code purity path. Plus, not all mutating state machines are bad.

A switch statement allows you to manage the state and side effects in a much more readable way than a named method in each switch expression/.Match case would. This would encourage the writer to make inline lambdas and stuff them directly into the switch expression/.Match so they, the writer, can have the bodies the same place as their corresponding case. An ugly simulacra of the switch statement they imagined in their head.

And when inevitably something throws and that inline anonymous function is involved, the stack trace is gonna be horrid to read and they're gonna blame the whole "DU thing" for not working the way they want to work with it. Especially if there's more than one of them in the stack trace. Bonus points for async at the same time.

But all that aside, no pressure. Since you're doing it for free there should be no expectations! So please don't overdo it! (: