Arthur Stolyar

@RReverser so say then so to Facebook React and ask them to stop doing optimizations here facebook/react#3228 @sebmck I know. Why then we are talking about problems with object literals?

@sebmck it wasn't proposed to React, I believe. JSX-IR has its own use cases which might not be good for React or some other framework. Using string templates also has...

> In fact, it's you who mentions React repeatedly in this thread, while we're trying to convince you that JSX implementation in Babel is not React-specific. It's and people are...

I am not saying there is dependency of React, I am saying that React's JSX output became de-facto standard. There is many React's artifacts in current Babel's JSX output, but...

And nobody spotted it. At least, it could be marked deprecated or something and TS will just ignore then. On Mar 8, 2016 1:10 PM, "Ingvar Stepanyan" [email protected] wrote: >...

@JamesHenry > It looks like it's just a regression bug. > And nobody spotted it. If you have any evidence that Babel users spotted it or had problems with it,...

@JamesHenry I know, but I may write here as many as I want, until owners came here and say my comments are inappropriate, which **were** not because I just left...

Btw, JSX does not limits Component's variable to be of particular type. It's rather React and react-jsx transpilation behavior, so this issue should be discussed in ReactJS repo.

@npryce > `````` > > ... > ``` > `````` This does not looks better than this: ``` javascript jsx` ... ` ``` This is why JSX captures variables. What...

@s-belous yeah, I can do that. Thanks for reporting this :-)