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 @awbjs
I meant it’s a spec bug in the sense that it doesn’t match implementation reality.
10:02 AM - 14 Oct 2019
0 replies
0 retweets
1 like
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.