Inherited instance prop should override the parent: https://gist.github.com/DmitrySoshnikov/9387231f04d6e75bec2cf8da5a7e3e21 … @sebmck, seems Babel bug (cc @BrendanEich @awbjs)
I'm still really bothered by: class extends Node { textValue = "hi" } Way too subtle.
-
-
yea I'm torn on that also. IIRC I swayed toward dP last mtg frm other args made abt const fields
@sebmck@thejameskyle@BrendanEich -
const field arguments are persuasive to me. I regret reserving `:`
-
const and type arguments are twins, but integrity defense against getter attack prevails first.
-
Anyway, :T future-proofing secondary to : def beating = set here. Now, to 2ndary arg: u want :: ?!
-
I don't want `::`. But https://twitter.com/wycats/status/779331017865703424 … is a massive fail. Almost fatal.
-
to explain that, you mean function declaration w/ destructuring param needs {x}:{x:string} in TS.
-
yes. As a TS user, this has bitten me many many times.
-
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 - 13 more replies
New conversation -
-
-
I understand why JS semanticists prefer define. Just think we're suffering Curse of Knowledge.
-
also don't have a great solution here. Just more worried than most about define.
-
I do think that both dP and assign have their equal trade offs, so will need to tread carefully
-
but have some more recent concerns about dropping = that might be a little difficult to Twitter
End of conversation
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.