Until JS supports switch expressions, nested ternaries will continue to be the most effective way to write multi-state conditionals.
Also, stop using linting tools that prioritize consistency over human readability, and then complaining that the code they generate is not easily-readable by humans.
they also said switch expressions, which indicates they want the switch statement to be settable directly to a variable with whatever the return type of the switch is.
Until JS supports switch expressions, nested ternaries will continue to be the most effective way to write multi-state conditionals.
Also, stop using linting tools that prioritize consistency over human readability, and then complaining that the code they generate is not easily-readable by humans.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch - hasnt it had this forever? Or are you refering to something else?
Pretty sure they meant
match
as in pattern matching, notswitch
as in switch/case/break.You can see the proposal here: https://github.com/tc39/proposal-pattern-matching
Your probably right, that looks quite desirable.
they also said switch
expressions
, which indicates they want the switch statement to be settable directly to a variable with whatever the return type of the switch is.Match already returns the value which can be thrown into a variable.
Nah, I meant switch, as that's what it's called in C#-land. See above.
That proposal for matching looks interesting, but not quite the same, no.
Are you sure?
Your C# example:
JS proposal for match:
Aha, yeah, I see it now. Looking forward to it.
Yeah, a switch expression is different than a switch statement. I'm not actually sure how many languages actually have them, but in C# its...