There's a misunderstanding about stagnating proposals in TC39, that it's because TC39 dislikes a proposal. It's often not the proposal itself but the work of the champion. E.g. not enough research, poor presentation, lack of arguments or it's a topic which requires extra effort.
-
Show this thread
-
Replying to @sebmarkbage
Can you provide any inside into TC39’s stance on types in JS? With the popularity TS and Flow are getting, is the issue here the same as you just mentioned? The champion? Or a lack of interest to bring types to JS
2 replies 0 retweets 0 likes -
Replying to @mattapperson
The stance is basically to let the space play itself out, outside of standards. That space is huge and very much still in motion. It's not that types can never be added. However, there are arguments for some smaller type hints which could possibly be made by a strong champion.
3 replies 0 retweets 9 likes -
Replying to @sebmarkbage @mattapperson
I second this. Hints would have to be added with cooperation from an implementation that would agree that the hints would help.
1 reply 0 retweets 1 like -
Replying to @wycats @sebmarkbage
Are there any proposals yet for hints just yet that need a champion?
1 reply 0 retweets 0 likes -
Replying to @mattapperson @sebmarkbage
I have some myself, but don't have time to champion them. I've talked about them somewhat with
@sebmarkbage too.1 reply 0 retweets 0 likes -
Ones that we already have: * |0 and the rest of the asm.js suite * Integer's cast
1 reply 0 retweets 0 likes -
I would love: * Guaranteed string interning * Explicit opt out of inlining * Explicit opt out in to lazy parsing Now that I think about it, these are JIT hints not type hints
1 reply 0 retweets 0 likes
Stuff like String(foo) might already count as string annotations but I'm not sure if they're fast.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.