-
Notifications
You must be signed in to change notification settings - Fork 32
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
Better backtraces #14
Comments
Probably use https://bramtayl.github.io/NumberedLines.jl/stable/ |
I started trying to work on this but I think the code surgery got a little out of hand. One reasonable first step would be to use MacroTools exclusively for expression decomposition. Then I could write a wrappers for macrotools such that any numbered line inputs will yield numbered line outputs. Then comes the question of how to put these pieces together, that is, which part of the generated code you want to point back to which original line. |
Hi @bramtayl, thanks for looking into this! I'm not 100% sure that MacroTools will work for 100%, but using more MacroTools is definitely good. I think starting non-fancy and just referencing the first line of the type def would be fine. But I'm off on holidays now and then crazy conference prep. So, don't expect much from me until the end of April. |
I realized today I had been thinking about this wrong. It seems like you would want backtraces to point to lines in the Parameters.jl file in |
Thanks for spending your brain cycles on this! There is probably a bit of both, but I think more the user-code (I assume that the Parameters.jl code is bug free ;-). Example:
Here it would be better to point to the user-code. |
Use the trick Tim used in mauro3/SimpleTraits.jl#6 to get better backtraces.
The text was updated successfully, but these errors were encountered: