You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an assert or some other error occurs, the erroring line is pointed out with no context as to how the program execution got to that point. This is particularly problematic if the error occurs within a library.
Happy Case
Instead of storing Option<Location> for an instruction, we should store Vec<Location> where each instruction originally holds only the absolute location, and it is eventually pushed to over time during each function inlining step adding a stack frame.
We would need to rework the way errors are displayed to enable them to show full stack traces.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered:
Problem
When an assert or some other error occurs, the erroring line is pointed out with no context as to how the program execution got to that point. This is particularly problematic if the error occurs within a library.
Happy Case
Instead of storing
Option<Location>
for an instruction, we should storeVec<Location>
where each instruction originally holds only the absolute location, and it is eventually pushed to over time during each function inlining step adding a stack frame.We would need to rework the way errors are displayed to enable them to show full stack traces.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: