-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Remove redundant session field #106813
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove redundant session field #106813
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @GuillaumeGomez (or someone else) soon. Please see the contribution instructions for more information. |
Good catch, thanks! Do you think it's worth a perf run? If not just r=me. |
I don't believe this will affect perf @bors r=GuillaumeGomez rollup |
📌 Commit 67f8afd1064c753cd6ea14e2a4b7c53637832309 has been approved by It is now in the queue for this repository. |
@bors r- |
@rustbot ready |
@bors r=GuillaumeGomez,petrochenkov |
…omez,petrochenkov Remove redundant session field There was already a session available in the resolver, so we access that session.
…iaskrgr Rollup of 10 pull requests Successful merges: - rust-lang#104645 (Add log-backtrace option to show backtraces along with logging) - rust-lang#106465 (Bump `IMPLIED_BOUNDS_ENTAILMENT` to Deny + ReportNow) - rust-lang#106489 (Fix linker detection for linker (drivers) with a version postfix (e.g. clang-12 instead of clang)) - rust-lang#106585 (When suggesting writing a fully qualified path probe for appropriate types) - rust-lang#106641 (Provide help on closures capturing self causing borrow checker errors) - rust-lang#106678 (Warn when using panic-strategy abort for proc-macro crates) - rust-lang#106701 (Fix `mpsc::SyncSender` spinning behavior) - rust-lang#106793 (Normalize test output more thoroughly) - rust-lang#106797 (riscv: Fix ELF header flags) - rust-lang#106813 (Remove redundant session field) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
There was already a session available in the resolver, so we access that session.