This is a reopening of #24407 issue. So I took back what was already there and updated it:
This is a metabug for rustc --explain error 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:
$ ./x.py test src/test/ui -- stage1
$ export PATH=x86_64-unknown-linux-gnu/stage1/bin:$PATH
$ export LD_LIBRARY_PATH=x86_64-unknown-linux-gnu/stage1/lib:$LD_LIBRARY_PATH
$ rustc --explain EXXXX
You can add --jobs 4 to use 4 parallel make processes:
$ ./x.py build --stage 1 --jobs4
Once you're happy with the result, submit a pull request and we'll review it.
Progress
cc @steveklabnik
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