-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Necromancing (putting back some removed error codes explanations) #66836
Conversation
Some changes occurred in diagnostic error codes |
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 |
Do you plan to do this for all the removed errors? |
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
69718f9
Compare
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
65061c1
Compare
Fixed tidy. |
@bors r+ rollup |
📌 Commit 65061c1 has been approved by |
@bors r- |
Ah okay. No issues 👍 |
☔ The latest upstream changes (presumably #67104) made this pull request unmergeable. Please resolve the merge conflicts. |
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