Only Hermes compiler gives a correct warning for the unresolved LHS. Other engines still seem deviate from the PutValue in the spec: 'use strict'; undeclared = ( this.undeclared = 10, print(undeclared), 10 ); Should be a Ref.Error for LHS, while normally eval'ing RHS
-
-
Replying to @DmitrySoshnikov
Since all non-Hermes engines implement it the same way, this is arguably a spec bug. Please file it here:https://github.com/tc39/ecma262/issues …
3 replies 0 retweets 2 likes -
Replying to @DmitrySoshnikov @mathias
This devergence of browsers from the spec. has been discussed many times within TC39 and TC39 has always chosen to stand firm on the specification for this issues. (or at least, been unable to reach consensus to change the spec) cc/
@BrendanEich2 replies 0 retweets 0 likes -
-
I wasn’t making any general assertion about web-reality conforming changes. I was specifically talking about this specific issue and its long standing history.
1 reply 0 retweets 2 likes
Ack
10:21 AM - 14 Oct 2019
0 replies
0 retweets
0 likes
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.