-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
const_err spans not rendered when rust-src not installed #97699
Comments
Cc @rust-lang/wg-diagnostics : IMO it is a bug in the rustc diagnostic printing that it entirely omits information attached to spans where the source is missing. Is there anything we can do about that? |
We could emit the information as a |
Has this been resolved by #103970 ? |
The error message is
without
with the |
So it does not seem entirely resolved -- the 'unable to copy parts of a pointer from memory at alloc6+0x1' is still missing completely when rust-src is not installed. |
ugh... I'm slowly wondering if we should enable |
Yeah if that is possible that would probably be good. |
Well... either way, I found a way to fix this specific diagnostic, so once that is landed I'll experiment with unconditionally setting that flag on all ui tests. |
…bank,RalfJung Start emitting labels even if their pointed to file is not available locally r? `@estebank` cc `@RalfJung` fixes rust-lang#97699
This code causes a const_err somewhere in the standard library:
When the
rust-src
package is not installed, the error is pretty unreadable:This is missing the key information of what goes wrong! With
rust-src
, the following is added, making it much clearer:If the sources are missing, we should probably still show the error, even if we cannot attach it to any code.
Cc @rust-lang/wg-const-eval
The text was updated successfully, but these errors were encountered: