Scotty Jamison

This is a syntax shorthand for IIFEs, correct? This kind of idea has been proposed a handful of times, and while it solves many of the same problems that the...

Sorry - I didn't look close enough, you're right that you were using the `return` keyword and not doing implicit return, so yes, you don't have any issues there. >...

Alternatively, if you don't make it an iife shorthand, then you could have async/return/yield/etc within your shorthand syntax. You'll end up something very similar to this discussion #1. That, together...

I'm not sure I understand your pipe syntax. ``` const c = value -> value+1 -> value+1 -> value+2 console.log(c) //5 ``` This is pretty odd. From what it looks...

So, would this not be allowed? ``` const c = obj.value -> ???? + 1 // What goes in the ???? ```

I think there are really only two use cases for do expressions without braces: if and try. Maybe "throw" too if [this](https://github.com/tc39/proposal-throw-expressions) proposal to make "throw" become an expression doesn't...

There seems to be a lot of talk about how if we had a "do " semantics, then we would also be required to place an extra semicolon at the...

I don't see why it would or should. The trick seems to be to make the "do" not so greedy so it doesn't try and consume as much as possible....

Some more thoughts on how the do shorthand could work: ~~Firstly, what if we just made it so the do shorthand only operates on statements, not expressions? There's no reason...

Some related discussion towards this idea has been happening on the TC39 forms [here](https://es.discourse.group/t/the-role-of-inheritance-in-javascripts-future/919).