Add error explanations for all error codes #32777
Comments
GuillaumeGomez
added
A-docs
E-easy
GuillaumeGomez
added
E-easy
|
I would like to take this =D How to I can start? |
|
@marti1125: I guess the first step is to find one of the listed error codes into the rust source code (github search makes it easy) and then try to get the error with rust code. From there, just follow the description of this issue and if you need help, you can always ask (here or on IRC on #rust-docs chan). |
Add E0393 error explanation Part of #32777. r? @Manishearth cc @steveklabnik
Add E0393 error explanation Part of #32777. r? @Manishearth cc @steveklabnik
|
I'm working on E0501. |
|
I'll open a PR for E0502 tomorrow. |
|
I'll open a PR for E0509 today or tomorrow. |
|
@timothy-mcroy, @cramertj: Thanks to both of you! :D |
|
Hey guys. I'll take the E0507. Tomorrow I'm going to work on it (Now is almost 1 am here in Brazil :P) |
…r=estebank E0090: Add explanation for error message See rust-lang#32777 $ rustc --explain E0090 The wrong number of lifetimes were supplied. For example: ``` fn foo<'a: 'b, 'b: 'a>() {} fn main() { foo::<'static>(); // error, expected 2 lifetime parameters } ```
…r=estebank E0090: Add explanation for error message See rust-lang#32777 $ rustc --explain E0090 The wrong number of lifetimes were supplied. For example: ``` fn foo<'a: 'b, 'b: 'a>() {} fn main() { foo::<'static>(); // error, expected 2 lifetime parameters } ```
|
In the instructions, it says:
and that link to the RFC above leads to rust-lang/rfcs#1567. Perhaps the link should point to the document explaining the RFC instead of the pull request? It took me a bit of digging to figure out where that document was. Edit: A link to the spreadsheet in this thread would be nice for newcomers as well. |
|
@GuillaumeGomez This issue are closed to contribution yet? |
|
@marioidival: If you find any error code not having a long error explanation; then it's not. Either add it yourself or open a new issue please. |
|
@GuillaumeGomez The progress show us that much is still missing. |
|
I think it's really outdated. |
|
I updated the list. I also checked the removed ones. |
|
Comments after each link are those extracted from either The following are commented out
I couldn't find any reference in git for these (using github search) Listed in These are the remaining items from the list
|
XAMPPRocky
added
the
C-tracking-issue
|
The following are not listed at all, but are missing:
|
|
There is a 907???????? |
|
I'm fixing those codes... EDIT: Done in #51475. |
|
Add extended information for E0594 in #60193. |
|
@GuillaumeGomez there are new error codes that do not have boxes yet |
|
I think this issue is completely out of date since a moment... Should we open a new one instead? |
|
Yeah, go for it
-Manish Goregaokar
…On Fri, May 24, 2019 at 11:38 AM Guillaume Gomez ***@***.***> wrote:
I think this issue is completely out of date since a moment... Should we
open a new one instead?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#32777?email_source=notifications&email_token=AAMK6SGW7NKBMJ35UP6LTRLPXAY4DA5CNFSM4CAFTAD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGIFXQ#issuecomment-495747806>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMK6SDJIZHGY7NYBW4MBJLPXAY4DANCNFSM4CAFTADQ>
.
|
|
Ok! |
|
Closing in favor of #61137. |
and others
This is a reopening of #24407 issue. So I took back what was already there and updated it:
This is a metabug for
rustc --explainerror descriptions.All the errors in need of descriptions are listed in this spreadsheet. If you'd like to help out, comment with the bunch of errors you'd like to tackle, and list yourself as assigned on the spreadsheet!
Choosing a few errors in the same file is probably a good way to start.
How to add an error explanation
Error explanations live in:
To add a new explanation you have to delete the error from the register_diagnostics! invocation and add it to the register_long_diagnostics! invocation, along with the explanation. The format for the explanation is 80 characters per line, with a newline at the very start and end of the string.
Please refer to this RFC when you'll write your error explanation (it can also helps you to start if don't know how to write it).
Once you've added an explanation you can test it out by compiling and running stage1 as follows:
You can add
--jobs 4to use 4 parallel make processes:Once you're happy with the result, submit a pull request and we'll review it.
Progress
cc @steveklabnik
The text was updated successfully, but these errors were encountered: