he/him 
Even the most basic functionality (return type annotations) have this problem: foo = a ? (b) : c => (d) : e => f If `a` is `false`, does `foo(1)` return a function or f?
Parsing JavaScript is easy compared to Flow or TypeScript. Type arguments on call/new should have never existed: foo<Foo>(bar); Or is it... foo < Foo > (bar);
-
-
-
I'm actually working on that test right now
pic.twitter.com/DsI58y6TlC
- 1 more reply
New conversation -
-
-
After arrows and destructuring, how bad could it be
-
Have you heard about conditional expressions and arrow functions with return types...
- 1 more reply
New conversation -
-
-
what's the alternative in this case?
-
Less than/greater than
- 2 more replies
New conversation -
-
-
Not sure if Flow or TypeScript allow this, but it'd be useful for things like: JSON.parse<MyObject>(bar) Definitely much more useful in languages with reified generics, though! Type erasure limits the usefulness.
- 4 more replies
New conversation -
-
-
Ha don't be crazy it's foo <Foo>(bar);</Foo>
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But do you do a ton of Boolean inequality checks?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.