Sebastian

That was the one I talked at, I recall the homepage being reverted to the November meetup for some time too so that's what I assume.

This is likely a deliberate decision. Semicolon terminators imply a statement list and the execution of decorators is different in that it's more analogous to function calls.

I don't think @RReverser was talking about the syntactic ambiguity rather that in JavaScript a `.` is used to represent property access and the use of it as a key...

FWIW, Babel actually implements [do expressions](http://wiki.ecmascript.org/doku.php?id=strawman:do_expressions). With this it means that the original example of: ``` {if (x) } ``` can be represented as: ``` { do { if (x)...

Also, I **really** like @syranide's proposal of allowing an abitrary list of statements inside JSX expression containers, I particularly like the completion record example of: ``` {Value} {if (x) else...

@mathieumg Yeah, `switch`es aren't possible. Easiest way to test out completion records (rather than digging through the spec) is to use the return value of `eval`: ``` javascript eval("switch (1)...

@matthewrobb There isn't. It's a deliberate choice because there's no current proposal document or spec text.

I can implement this in Babel with literally a few lines so :+1: from me. Also see reactjs/react-future#35 which is the exact issue that prompted that tweet and discussion :smile:

Let's figure out a way to prioritize this.

Draft PR now open from @MichaReiser in #3702 🤯🥳