-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix: Correct span info for mir::Operand #19247
base: master
Are you sure you want to change the base?
Conversation
Right now the question is whether I should go the extra mile and make |
@@ -18,7 +18,22 @@ pub(crate) fn moved_out_of_ref(ctx: &DiagnosticsContext<'_>, d: &hir::MovedOutOf | |||
mod tests { | |||
use crate::tests::check_diagnostics; | |||
|
|||
// FIXME: spans are broken | |||
#[test] | |||
fn abc() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That... doesn't seem like the most descriptive name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry about that 😂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't worry, it happens to me too that I put a test before the changes and don't bother to make its name meaningful, I understand you can forget to do that after :)
I think it'd be better if we wouldn't make this optional when there is no reason. |
Fixes #19172