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
The typical DOM object-detection case looks like this: `var foo = foo || myPolyfill()`. I think it would work correctly under either setup, if I understand the thing we're discussing correctly.
-
-
I’m thinking of variations such as discussed lower in message text at https://esdiscuss.org/topic/const-vs-features-detection#content-7 …
-
But given “use strict” it may be that browser engines could comply without web compat breakage. Only one way to find out for sure....
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.