Andreas Svensson

> However this value would be wrapped in an array. We could potentially unwrap it for single items. Unfortunately that can have consequences for React key semantics, since this would...

@ogwh Over-abstraction is also a serious readability problem, simple problems should be simple to understand at a glance. The current situation is that even a lot of should-be-simple cases become...

@bmeck I was writing a reply to this in the other issue but apparently I was no longer allowed to. Anyway, there's a fundamental problem with having all children be...

Just a note about a variation of your example: ```jsx render() { if (this.state.invalid) { {this.state.invalid.text} } } ``` Will have one of two behaviors when "this.state.invalid" is false. 1....

> This is an investigation! Lets go over those problems. This also reminds me of #84 (comment) @bmeck ```jsx if (cond) { } else { } ``` Will not reuse...

Ok, wait. I assumed this was mostly a continuation of the previous issue and just glossed over your text. My bad. If it's just about adjacent JSX elements then these...

> The ASI is an issue that is solved the same way as other ASI issues are solved, by adding a semicolon. Right now it fails to parse which is...

@bmeck Maybe it's just me or I don't fully understand the purpose of "phrasing it that way". If we take the original example as a starting-point: ```jsx render() { if...

I should just clarify exactly instead: ```jsx render() { let out = []; if (this.state.invalid) { out.push({this.state.invalid.text}) } out.push() out.push() return out } ``` **EDIT:** Are we on the same...

@bmeck Here's where I'm confused, we're talking about functions, no normal statements inside a function has a completion value. So the above examples don't make sense? It seems like you're...