-
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
Suggest appropriate place for type argument after associated type #57385
Labels
A-suggestion-diagnostics
Area: Suggestions generated by the compiler applied by `cargo fix`
Comments
estebank
added
A-diagnostics
Area: Messages for errors, warnings, and lints
A-suggestion-diagnostics
Area: Suggestions generated by the compiler applied by `cargo fix`
and removed
A-diagnostics
Area: Messages for errors, warnings, and lints
labels
Jan 6, 2019
Centril
added a commit
to Centril/rust
that referenced
this issue
Jan 25, 2019
Add suggestion for moving type declaration before associated type bindings in generic arguments. Fixes rust-lang#57385. r? @estebank
Why wasn't that regression caught by our tests? |
The test was also updated. Presumably it wasn't noticed and the test got |
The above code now generates a suggestion.
I assume this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like we do for lifetimes, suggest the appropriate place for type arguments written after associated an type.
Given
we currently emit
The text was updated successfully, but these errors were encountered: