-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
syntax: Follow-up to the incorrect qpath recovery PR #46827
Conversation
--> $DIR/bad-assoc-ty.rs:37:10 | ||
| | ||
37 | type G = 'static + (Send)::AssocTy; | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `< 'static + Send>::AssocTy` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stray space?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pre-existing, all object types are actually pretty-printed like this.
Since it came up again, I'll fix this tomorrow, probably in a separate PR.
@bors r+ rollup |
📌 Commit 48699b0 has been approved by |
Fix whitespacing issues in pretty-printing of bounds cc rust-lang#46827 (comment)
48699b0
to
d333752
Compare
@bors r=estebank |
📌 Commit d333752 has been approved by |
syntax: Follow-up to the incorrect qpath recovery PR cc rust-lang#46788 Add tests checking that "priority" of qpath recovery is higher than priority of unary and binary operators Fix regressed parsing of paths with fn-like generic arguments r? @estebank
cc #46788
Add tests checking that "priority" of qpath recovery is higher than priority of unary and binary operators
Fix regressed parsing of paths with fn-like generic arguments
r? @estebank