-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Old school errors not showing labels as notes #35330
Comments
Maybe it would make sense to have a separate |
@nagisa - yeah, though we should chat with @nikomatsakis. He's been leaning towards more tests being UI tests that check for these things, so you can check layout at the same time. |
@jonathandturner I am reminded that I had planned to start a thread on internals to talk it over. I am not sure what I think would be best, but I feel pretty sure that I do not like the fact that |
…jonathandturner Turn on new errors and json mode This PR is a big-switch, but on a well-worn path: * Turns on new errors by default (and removes old skool) * Moves json output from behind a flag The RFC for new errors [landed](rust-lang/rfcs#1644) and as part of that we wanted some bake time. It's now had a few weeks + all the time leading up to the RFC of people banging on it. We've also had [editors updating to the new format](https://github.com/saviorisdead/RustyCode/pull/159) and expect more to follow. We also have an [issue on old skool](#35330) that needs to be fixed as more errors are switched to the new style, but it seems silly to fix old skool errors when we fully intend to throw the switch in the near future. This makes it lean towards "why not just throw the switch now, rather than waiting a couple more weeks?" I only know of vim that wanted to try to parse the new format but were not sure how, and I think we can reach out to them and work out something in the 8 weeks before this would appear in a stable release. We've [hashed out](#35330) stabilizing JSON output, and it seems like people are relatively happy making what we have v1 and then likely adding to it in the future. The idea is that we'd maintain backward compatibility and just add new fields as needed. We'll also work on a separate output format that'd be better suited for interactive tools like IDES (since JSON message can get a little long depending on the error). This PR stabilizes JSON mode, allowing its use without `-Z unstable-options` Combined, this gives editors two ways to support errors going forward: parsing the new error format or using the JSON mode. By moving JSON to stable, we can also add support to Cargo, which plugin authors tell us does help simplify their support story. r? @nikomatsakis cc @rust-lang/tools Closes #34826
Should this be closed now, since old school errors no longer exist (#35401)? |
@lfairy - good catch |
Originally, we had intended that old school errors would treat most labels as notes just so we would have similar information between the two formats. With the latest refactor, this seems to have been removed.
This may or may not be related: https://gist.github.com/trixnz/ad11e68687529e164427df8f8eb63116
Same error after
unset RUST_NEW_ERROR_FORMAT
The text was updated successfully, but these errors were encountered: