-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Spans for view items are fairly inaccurate #650
Comments
I fixed this one, but I'm not sure how to add a regression test when the right error message involves having a certain span. If anyone has suggestions, let me know. |
Maybe you could formulate a test where the span is minimally likely to change. Or you could put comments in the test indicated that you're specifically testing for the correct span, so whoever messes with it feels more inclined to update the test. Or you could just skip the test; sometimes that's easiest. |
Yeah, I'm skipping it for now. But the code example is right here in case anyone wants to add it as a test ;-) |
We can't test s390x because qemu segfaults but we can at least verify that it compiles. Closes rust-lang#650
Clean up CI configuration and add s390x We can't test s390x because qemu segfaults but we can at least verify that it compiles. Closes rust-lang#650
our closure syntax comes from Ruby
…en fixed (rust-lang#650) * Enabled CBMC unknown language mode test now that rust-lang#533 has been fixed and migrated it to a cargo-rmc test
In this test case:
I get this error:
The spans for the two imports, while in the general ballpark, are not very exact. I suspect that all types of view items have similar problems with their spans.
The text was updated successfully, but these errors were encountered: