-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Update error format for E0130 #35331
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jonathandturner (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@bors r+ rollup |
📌 Commit 625fc29 has been approved by |
…dturner Update error format for E0130 Fixes rust-lang#35256 as part of rust-lang#35233 r? @jonathandturner
From Travis:
|
@bors r+ rollup |
📌 Commit 4c672e0 has been approved by |
…dturner Update error format for E0130 Fixes rust-lang#35256 as part of rust-lang#35233 r? @jonathandturner
@bors r- doesn't merge cleanly |
4c672e0
to
e2cc157
Compare
@bors r+ rollup |
📌 Commit e2cc157 has been approved by |
…dturner Update error format for E0130 Fixes rust-lang#35256 as part of rust-lang#35233 r? @jonathandturner
…dturner Update error format for E0130 Fixes rust-lang#35256 as part of rust-lang#35233 r? @jonathandturner
Fixes #35256 as part of #35233
r? @jonathandturner