-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
nll: remove "warning: not reporting region error due to nll" #52768
Comments
(in fact, taking care of this would bring a number of the |
But on the other hand, my diagnostic review (#52663) is revealing a couple of cases where a diagnostic is missing useful info that we used to report, and I think they correspond to these region errors that we are not reporting. |
I'm bumping the priority on this and nominating it for discussion. |
So the only issue that I'm aware of that we need to fix eventually in NLL is the diagnostic regression which I have now filed as #53771 |
but I also do not think that #53771 needs to be resolved for RC (see the end of the description for that issue for why). Anyway, the question still remains: Are we ready to kill that "region error" warning? |
If that's okay, I can prepare a PR with the warning removed and wait for the question to be resolved before merging it? If the modification is just removing a warning, I think it should be fairly resilient to merge conflicts. Or is it more complicated than that? |
I think we are |
I agree and am going to r+ PR #53865 |
Remove 'not reporting regions error due to nll' warning Fix #52768
As I understand it, our plan has always been to remove this warning eventually.
Certainly it cannot stay as it currently stands.
And from what I've seen, the diagnostics that we now report from MIR-borrowck tend to be good enough that the warning is just noise.
The text was updated successfully, but these errors were encountered: