-
Notifications
You must be signed in to change notification settings - Fork 353
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
give some context in error messages #1250
Conversation
PR lgtm, just a general question, if we are explaining things to users, should we link them to appropriate issues or so where they can get more info? |
I mean long-term it would be really cool for every "this is UB" message to link to the part of the Reference that says why this, specifically, is UB -- but that will need some more work I think. Right now, I am not sure what things we could specifically link to? |
Maybe the ucg repo? |
For most UB, that doesn't really have a lot to say, I feel. But we could link to the general reference UB page:
And for Stacked Borrows:
|
@bors r+ |
📌 Commit 6e302b8 has been approved by |
☀️ Test successful - checks-travis, status-appveyor |
…nkov Miri error type: remove UbExperimental variant In rust-lang/miri#1250, I will move Miri away from that variant, and use a custom `MachineStop` exception instead.
Those messages are great! |
It took almost 2 years but finally we are there. ;) |
Some examples for how different errors look now
Unsupported operation:
Unsupported operation that works without isolation:
Program abort:
UB:
Experimental UB:
Fixes #417