-
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
Update E0057 error message to new format #35395
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. |
Looks good! @bors r+ rollup |
📌 Commit edca8ec has been approved by |
☔ The latest upstream changes (presumably #35365) made this pull request unmergeable. Please resolve the merge conflicts. |
🔒 Merge conflict |
@paulfanelli - can you update this to fix the merge conflict? With that, I think we're good to go. |
Will do...I'll take a look at. |
edca8ec
to
f6cc95a
Compare
Looks like the reason there was a conflict, is that someone else had also fixed it. To fix the conflict, I updated my fork with the latest rust code and rebased my branch where i did the work (update-e0057-error-msg) onto the lastest rust code. I re-complied and tested it. I then pushed the updated code back to the update-e0057-error-msg branch of my fork. I think this pull request now is good to go. (?) |
@paulfanelli - if I'm reading this right, did someone fix this issue already? If so, I can close this and you can pick another one from the list (if you like): #35233 |
Yep, someone fixed it, just a bit differently. Ok, go ahead and close this and I'll take #35233 , if still available. |
Oops, didn't realize that #35233 is the catch-all issue; can't take them all, lol. I'll pick something from the list. |
Hey, just a heads up, I never did any bonus work on this one. Not sure if whoever fixed it, did either. |
☔ The latest upstream changes (presumably #36274) made this pull request unmergeable. Please resolve the merge conflicts. |
I believe this is now being addressed by #36222 , so I'll close this (feel free to reopen if I'm wrong). Thanks for the effort in any case! :) |
@bstrie - neither PR has landed, yet. Though given that both haven't moved in over two weeks, perhaps we should close both? |
Fixes #35214 as part of #35233.
r? @jonathandturner