to be fair I did assign rather than define intentionally
-
-
we get plenty of reports on this in Flow too. We came up with an inline syntax but ppl would still make the mistake
@BrendanEich -
what's the flow inline syntax? The problem is it's impossible to lint :(
-
class X {} function foo({ x: X }} legitimately ambiguous :/ could try to guess.
-
havent built only POC'd: function f({x: (y: X)}) {} Consistent w casting syntax and gen'izes annot grmr forall bindings
-
argues against my { x as y } proposal, which might be nice
-
let { x: y as X } or let { x as X } would be the same strategy in TS. it's not bad
-
ya `:` syntax predates TS "as" - but want to be consistent w casting. Prob with "as": used in import for value binding
@BrendanEich -
yeah which is why I want it in regular destructuring.
- 6 more replies
New conversation -
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.