-
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
Deprecated suggestion message could be better #98631
Comments
This is because it's a suggestion, but being rendered inline. You could bump it up to a verbose suggestion so it renders more distinctly. |
Hm, thinking more about it, could it not be simplified to:
As then the help message would focus on what's actionable without repeating less essential information. |
The problem is that this is a suggestion, and when suggestions are rendered inline they always are presented like edit: whoops, i guess i missed the colon in your revised message. i guess it could be shortened like that. |
Yeah, sorry I edited once I started actually playing with this. |
I think it's meaningful for the suggestion's message to say what it's doing -- "try replacing with" seems a bit terse. I think I still prefer how this would render if we just bumped the suggestion to a verbose (not inclined) suggestion. |
Ah ok. My thought was just that it's essentially repeating warning message using slightly different language. |
#![feature(deprecated_suggestion)]
(#94785) produces warning messages that I think could be improved? The current suggestion message doesn't seem ideal to me:Specifically this part sounds to me more like
Once::new()
is the deprecated constant:I think something like this would be better, but I don't know how easy it would be to implement a more natural sentence:
The text was updated successfully, but these errors were encountered: