-
Notifications
You must be signed in to change notification settings - Fork 105
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
Possible Rust error format updates and IDE support #84
Comments
Just to follow-up here, we're discussing making the switch to new errors soon: rust-lang/rust#35401. Once the switch is made, there are still some weeks before it shows up in a stable release, which hopefully gives us time to make the transition as smooth as possible. If this impacts you, please let us know. |
#85 fixes the plugin to work with the new error messages. @brson or @steveklabnik, are you the ones we should bug to get this merged? |
Posted #87 as an attempt of supportting |
Great to see some progress here! Friendly reminder - I'm going to each plugin just to let people know that we're 17 days away from the Rust 1.12 release, where the new error format will be the main format (and the old error format will be removed). |
@jonathandturner #87 is now merged and we use it by default. So I'm guessing we're finished up here? |
Sounds good. Thanks all! |
The error format from Cargo changed rust-lang/rust-enhanced#84 so updating this package to match the current extended plugin's file_regex https://github.com/rust-lang/sublime-rust/blob/master/Cargo.sublime-build
The error format from Cargo changed rust-lang/rust-enhanced#84 so updating this package to match the current extended plugin's file_regex https://github.com/rust-lang/sublime-rust/blob/master/Cargo.sublime-build
Hi all,
Sorry to use the issue tracker as a message box, but I wanted to mention that we're working on a possible update to the compiler error output: rust-lang/rfcs#1644 This might have an impact on the sublime plugin if you all happen to be parsing the compiler output.
That said, we're also thinking about standardizing a JSON format, so IDEs can get more information from the compiler (and not have to parse the error).
Would love to chat and hear your thoughts.
The text was updated successfully, but these errors were encountered: