-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Change in isa
parsing in catch
#19987
Comments
Note that it works as expected if you do :(try catch ex; isa(ex, Exception) end) or :(try
catch ex
isa(ex, Exception)
end) But I agree that it seems weird to allow arbitrary binary operators after |
Just a reference to the last time this is broken for fun =) edit: Actually I think it was a different line... But also one liner try catch used in PyCall... |
JeffBezanson
added a commit
that referenced
this issue
Aug 28, 2017
JeffBezanson
added a commit
that referenced
this issue
Aug 28, 2017
JeffBezanson
added a commit
that referenced
this issue
Aug 29, 2017
Fixed by #23487. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this is at least the second time this particular line in the PyCall.jl tests being broken by base parser change....
It doesn't seem valid to allow arbitrary binary operator after catch so maybe this can be unbroken?
The text was updated successfully, but these errors were encountered: