-
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
Track source locations of preconditions #415
Comments
This is especially important for points-to assertions. I might have tens of these in my preconditions, many with the same types involved. It's quite difficult to tell which one should be fixed when something goes wrong, especially if they're all symbolic. |
It looks like the problem is that |
The case of |
PR #1679 implements most of this, to the point I think it's time to close this ticket. |
While implementing #414, I noticed that
matchArg
can only report source locations on the level of overrides. It would be nice if we could provide the user with line numbers for each precondition.This would probably involve changing
to something like
where
The text was updated successfully, but these errors were encountered: