-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pattern Catching Gone Wrong #1485
Comments
Oh, I see what's happening. Adding parens and changing whitespace for clarity, though I'm not sure if this version still parses:
|
It's like this: (try
foo()
catch e) <? RangeError
bar(e) It's not that crazy, given what patterns are currently supported... But obviously not what you wanted. I think mainly we need to implement this form of pattern. Maybe we also want to forbid content on the same line as a try/catch block, but I could also imagine that it might be useful sometimes... |
If nothing else, content before the
|
Thanks to #1668, the original example now works: try
foo()
catch e <? RangeError
bar(e) |
What on earth is this miscompile
The text was updated successfully, but these errors were encountered: