@wycats sorry to bother - can you confirm I'm reading your proposal correctly - computed names disallowed?
@ foo [x] = () => true
invalid?
-
-
Disappointed, but I'll easily live :)
-
it's changable over time, but the ambiguities were really bad.
-
destructuring I assume? Ie having to deal with / disambiguate nonsense like class x { @ foo [a, b] = junk
End of conversation
New conversation -
-
-
To clarify, decorating computed names for class properties disallowed, or using `[]` lookup in decorator expr is
? -
"using `[]` lookup in decorator expr" meaning computed member expression, to help remove ambiguity from this tweet :)
-
Right - @ foo({ x: [] }) ofc still valid I assume.
@wycats -
Yeah, not referring to literals in call expr, though. Looks like spec introduces new Call/Member expr type to 1/
-
disallow computed property lookups, but still allow decorating computed props
-
right this is the key -- gotta allow decorating computed props without confusion/ambiguity.
-
Wait - sorry. How in the world can you decorate computed props? I thought the whole point here was that's disallowed?
@drewml -
class {
@foo [Symbol.iter]*() { } } - 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.