-
Notifications
You must be signed in to change notification settings - Fork 62
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
Make it easier to track down errors that occur in a thunk #57
Comments
This seems to work to do option 1.
Note that I think we should do this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider:
There was an error thrown within the thunk.
but the stacktrace tells me nothing about how to find the thunk.
It doesn't tell me wher the Thunk was, nor what it contained.
There are a few things we can investigate:
[5]
reflect where the@thunk
was rather than its contentssource.__line__
andsource.__file__
to actually include that in the functions namedisable_thunking()=@eval macro thunk(x) x end
and matchingenable_thunk()
to restore original definitionThe text was updated successfully, but these errors were encountered: