You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, V8 exhibits different behavior from JSC and SpiderMonkey for this construction.
When I first wrote this, I reported that JSC exhibited a third behavior (early SyntaxError). However this appears to be fixed in JSC as of 14.1 TP, making V8 the outlier.
In V8, a runtime ReferenceError is thrown when the expression is evaluated (chromium issue).
In JSC and SpiderMonkey, no error is thrown and behavior is, as far as I’m aware, correct.
I cloned Test262 and started poking around to see if maybe I could author a coherent test, but I figured I should open an issue first to confirm that the SpiderMonkey/JSC behavior is the correct one.
The text was updated successfully, but these errors were encountered:
It seems like a valid case. I'd need to run through the tests to find something but I believe the search will be challenging for the object methods.
One way to potentially find equivalent tests would be searching for failures in V8 runs for the class and objects tests. Although, I'm not finding anything like it so far.
Currently, V8 exhibits different behavior from JSC and SpiderMonkey for this construction.
In V8, a runtime ReferenceError is thrown when the expression is evaluated (chromium issue).
In JSC and SpiderMonkey, no error is thrown and behavior is, as far as I’m aware, correct.
Examples:
I cloned Test262 and started poking around to see if maybe I could author a coherent test, but I figured I should open an issue first to confirm that the SpiderMonkey/JSC behavior is the correct one.
The text was updated successfully, but these errors were encountered: