-
Notifications
You must be signed in to change notification settings - Fork 35
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
check if symbol is defined before trying to access it #440
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why aren't these symbols wrapped into QuoteNode
s ... ?
Codecov Report
@@ Coverage Diff @@
## master #440 +/- ##
==========================================
- Coverage 89.37% 85.46% -3.91%
==========================================
Files 12 12
Lines 2268 2250 -18
==========================================
- Hits 2027 1923 -104
- Misses 241 327 +86
Continue to review full report at Codecov.
|
Actually, this is more subtle than I initially thought. This essentially kicks the can down the road; suppose there is an object named I almost wonder if we should delete those Symbol lookup methods (that breaks a lot of tests, but maybe they can all be addressed individually). They might essentially correspond to cases where we fail to |
`evaluate_call_recurse!` calls `maybe_evaluate_builtin`, and if that doesn't return a `Some{Any}`, it uses the output as the new `call_expr`. The next thing it does is look up the args. Consequently, to avoid double-lookup, our expansion of `invoke` should return the non-looked-up arguments. Fixes #441 Closes #440
`evaluate_call_recurse!` calls `maybe_evaluate_builtin`, and if that doesn't return a `Some{Any}`, it uses the output as the new `call_expr`. The next thing it does is look up the args. Consequently, to avoid double-lookup, our expansion of `invoke` should return the non-looked-up arguments. Fixes #441 Closes #440
Fixes https://discourse.julialang.org/t/debugger-stops-without-hitting-a-breakpoint/50378.