-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Highlight when errors have automatically applicable suggestions #59103
Comments
I believe some iteration of the following would be appropriate:
With proper coloring, this should be easy to follow. Does CC @killercup |
rustfix only applies MachineApplicable suggestions, because… it's a
machine. Yeah, that's why, totally not to masquerade its AI superpowers or
anything.
…On Mon, 11 Mar 2019, 17:59 Esteban Kuber, ***@***.***> wrote:
I believe some iteration of the following would be appropriate:
error[E0252]*: the name `X` is defined multiple times
--> $DIR/double-type-import.rs:3:9
|
LL | pub use self::bar::X;
| ------------ previous import of the type `X` here
LL | use self::bar::X;
| ^^^^^^^^^^^^ `X` reimported here
|
= note: `X` must be defined only once in the type namespace of this module
error: aborting due to previous error
For more information about this error, try `rustc --explain E0252`.
* `rustfix` applicable suggestion is available for this error
With proper coloring, this should be easy to follow.
Does rustfix apply MaybeIncorrect suggestions? If not, this should be
only included for MachineApplicable suggestions.
CC @killercup <https://github.com/killercup>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOX35DahZBIZOanQ65ILnYVd1Xa36eks5vVouOgaJpZM4bo0p8>
.
|
In that case, we should only provide the asterisk (or whatever we land on) for The position of the asterisk and the last line text is bikeshedable to death:
|
I'll kick off the bikeshed by saying that I prefer the fourth option. |
+1 this comment if you think 1st option is best option |
I personally feel that all the presented options are suboptimal, but I don't care enough to fight too much. I think overall that either 1 or 4 lead the pack. Vote on the individual comments below for your preference. |
|
|
|
|
|
|
bikeshed-signal to @rust-lang/wg-diagnostics |
Won't that asterisk (or any other symbol) just be very confusing if you don't already know what to look for? I'd prefer a nonsigil solution, so something like
|
or
|
or
|
Perhaps if |
s/autofixable/rustfix/ |
With
tool_only_span_diagnostics
having landed, some suggestions that can be automatically applied aren't shown to the user as labels withhelp: ...
messages, so users who look for that to know they can automatically apply the fix won't know about those suggestions.We should add some indicator that tells the user that an error can be automatically fixed.
See this conversation.
The text was updated successfully, but these errors were encountered: