Peter Jaszkowiak
Peter Jaszkowiak
The main advantage of `do` expressions is implicit returns. Pretty much everything inside a do block is an expression.
This is related to #9 and #11, if common statements like `if`, `try`, etc are converted to expressions, which I can't think of any way that would be breaking, then...
If it is absolutely breaking, that is, there's no way around it like what @Kovensky suggested, then why are those issues being left open?
Seems like that could be fixed by making it so statements as expressions are only evaluated as such where there would currently be a syntax error: in the right hand...
A new JS context? You might need to expand on that. In my opinion, every sub-expression and sub-block should inherit the expression-oriented syntax, with the exception, maybe, of functions, since...
If it's only top level, this common example wouldn't work: ```js if (thing) { 5; } else { 3; } ```
Unless your definition of top-level is different. You should provide examples.
I think this also kind of relates to the two issues about treating if, else, switch, etc as expressions instead of statements. If that's possible then this discussion is irrelevant....
Breaking `eval` happens all of the time. Every addition to the language results in a breaking change in `eval` behavior.
The completion values of loops have been discussed elsewhere. The completion value of behavior of every other statement with the exception of function or class declarations are, in my opinion,...