-
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
Remove unnecessay .report() on ExitCode #97170
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @joshtriplett (or someone else) soon. Please see the contribution instructions for more information. |
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.
Good point, thanks!
@bors r+ rollup |
📌 Commit 7013dc5 has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#96539 (Add release notes for 1.61.0) - rust-lang#97142 (move processing of `source_scope_data` into `MutVisitor`'s impl of `Integrator` when inline) - rust-lang#97155 (Fix doc typo) - rust-lang#97169 (Improve `u32 as char` cast diagnostic) - rust-lang#97170 (Remove unnecessay .report() on ExitCode) - rust-lang#97171 (Add regression test for rust-lang#88119) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Since #93442, the return type is
ExitCode
anyway so there's no need to do a conversion using.report()
(which is now just a no-op).