I'm still really bothered by: class extends Node { textValue = "hi" } Way too subtle.
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.
-
would be nice if it were an option in vanilla JS... would align nicely with import
@BrendanEich -
yessir. And it's well motivated (adds expressiveness). Wanna propose it in November together?
-
I also want: constructor(options) { this.{ x, y } = options; }
- 3 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.