-
Notifications
You must be signed in to change notification settings - Fork 12.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
proposal for deprecation of error code E0313 #103742
Comments
If |
Sure, that sounds good. |
@akabinds Sorry just for clarification, do you want me to do the PR or you? |
…errors remove unreachable error code `E0313` Fixes rust-lang#103742 Makes rust-lang#103433 redundant Implements removal of `E0313`. I agree with the linked issue that this error code is unreachable but if someone could confirm that would be great, are crater runs done for this sort of thing? Also removed a redundant `// ignore-tidy-filelength` that I found while reading code. cc `@GuillaumeGomez` rust-lang#61137
This issue is a proposal for the deprecation of error code
E0313
.Background
I opened a PR (#103433) as part of an effort to add long error explanations for error codes that didn't have one (#61137). I chose
E0313
and for my erroneous code example, I used the example from #42574. I quickly realized, through running the example and other code that would also raiseE0313
and through the CI failure message, thatE0313
was not being raised. I went back to consult the issue I received the original code example from and noticed comments aboutE0313
not occurring anymore withNLL
. The issue was eventually labeled withNLL-fixed-by-NLL
. But, looking at the current contents of thenote.rs
file,E0313
can still be emitted even while it isn't:E0313
also doesn't have any UI tests as it is part of the error codes inEXEMPTED_FROM_TEST
.Reasoning
Since
E0313
, is no longer actually emitted (although it is in code that it could) thanks toNLL
, I believe it should be deprecated.I would be happy to help deprecate the error code, if it is decided that it should happen. I would just need to know the proper steps to take to deprecate an error code. If there are reasons for why it is still an error code, I would love to be enlightened.
@rustbot claim
The text was updated successfully, but these errors were encountered: