Uh oh!
There was an error while loading. Please reload this page.
Necromancing (putting back some removed error codes explanations) - #66836
Necromancing (putting back some removed error codes explanations)#66836GuillaumeGomez wants to merge 8 commits into
Conversation
rust-highfive
commented
Nov 28, 2019
Some changes occurred in diagnostic error codes |
rust-highfive
commented
Nov 28, 2019
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
petrochenkov
commented
Nov 28, 2019
Do you plan to do this for all the removed errors? |
GuillaumeGomez
commented
Nov 28, 2019
Not all of them. Some didn't even have an explanation so there is no point into adding those back... Like I said, this is mainly for users using old versions of the compiler. And I also marked all of them as not being used by the compiler anymore (as a title, so no confusion). |
c34faf9 to
69718f9Comparerust-highfive
commented
Nov 28, 2019
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
69718f9 to
65061c1CompareGuillaumeGomez
commented
Nov 29, 2019
Fixed tidy. |
Dylan-DPC-zz
commented
Nov 29, 2019
@bors r+ rollup |
bors
commented
Nov 29, 2019
📌 Commit 65061c1 has been approved by |
petrochenkov
commented
Nov 29, 2019
@bors r- |
Dylan-DPC-zz
commented
Nov 29, 2019
Ah okay. No issues 👍 |
bors
commented
Dec 7, 2019
☔ The latest upstream changes (presumably #67104) made this pull request unmergeable. Please resolve the merge conflicts. |
pnkfelix
commented
Dec 12, 2019
We discussed this in the T-compiler meeting last week. The general consensus was that we are not totally sure what our plan is with respect to preservation of error codes and error explanations, but we are pretty sure that whatever the plan is, it does not involve having to build explanations for old+unused error codes into the current compiler. ((We would like to figure out what our actual long term plan is for error codes (and internationalization, etc. But that is probably a topic at least for a design meeting; not something where one would jump straight to writing code.)) |
Even if the error code isn't used by the compiler anymore, we should keep the explanations in case people using old versions of the compiler want to read them.
r? @Dylan-DPC