meetings/working-groups/expressions-statements/ES-2022-11-30.md
Our agenda was to review proposal issues and make an initial decision on whether or not we wanted to pursue the feature in the short term. We organized the discussion around feature areas and scenarios.
(var x = 1).ToString().
Resolution: We felt this is not a feature we will work on in the near term.
throw in expression contexts, where we currently allow throw ex.
We will work on this in the near term.
break, return, continue in an expression context
This would allow break, return, or continue where we allow throw ex expressions today.
We think
throwwas a special case. We thinkreturnmay be a similar special case. There are identified scenarios where??andnullchecks might immediately return from a method. We're less sure aboutbreakandcontinue. We need to see scenarios where those would be compelling. Those may not be added now.
These centered on the different structures of the switch statement and switch expression.
There are two alternative for bringing the switch expression and statement syntax closer together:
We're interested in pursuing this in the near term. We're not sure if these are mutually exclusive, or which would be more useful.
These are are very similar, each being a different syntax with potentially different things allowed inside the syntax, but they're all similar in concept.
Of these, the only one we're interested in pursuing in the near term is #3037
Overall, of this set, we are interested in these three items: