don't shift goalposts to "bad", admit it, your "invisible" was inaccurate.
-
-
Replying to @BrendanEich @lbljeffmo and
of course I didn't mean to imply it wasn't speccable.
1 reply 0 retweets 0 likes -
Replying to @wycats @BrendanEich and
strict: function x() { new.target } function x(y=z) {} function x(...y) {} 1/
2 replies 0 retweets 0 likes -
-
I agreed 100% with
@domenic that we shouldn't base semantics on version of JS feature 1st appeared in1 reply 0 retweets 0 likes -
Replying to @wycats @lbljeffmo and
We agreed to impute strictness on Andreas Rossberg for V8, you were there. https://esdiscuss.org/notes/2015-07-29 …
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @lbljeffmo and
we didn't impute strictness, we disallowed ambiguity
2 replies 0 retweets 0 likes -
Replying to @wycats @BrendanEich and
no imputed strictpic.twitter.com/ngI9HLtj0F
1 reply 0 retweets 0 likes -
Replying to @wycats @lbljeffmo and
Not for default parameters. See the notes! The case in question is documented there.
2 replies 0 retweets 0 likes -
Replying to @BrendanEich @wycats and
Make it an error to have a "use strict" directive in a function with a non-simple parameter list.
1 reply 0 retweets 0 likes
which doesn't impute strict -- it makes the ambiguous case an error.
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.