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
Describe the bug
Currently, if we use a keyword with an Unicode escape, it will just work, and interpret it as the keyword itself. This is a follow-up from #1117.
To Reproduce
The following JavaScript code reproduces the issue:
letx=f\u{61}lse;
Expected behavior
This should throw a syntax error. Instead, it just assigns the false boolean value to the x variable.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, if we use a keyword with an Unicode escape, it will just work, and interpret it as the keyword itself. This is a follow-up from #1117.
To Reproduce
The following JavaScript code reproduces the issue:
Expected behavior
This should throw a syntax error. Instead, it just assigns the
false
boolean value to thex
variable.The text was updated successfully, but these errors were encountered: