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
Only instantiate binder during dyn's built-in trait candidate probe once #117610
Conversation
compiler/rustc_trait_selection/src/traits/select/candidate_assembly.rs
Outdated
Show resolved
Hide resolved
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.
r=me with the nit
compiler/rustc_trait_selection/src/traits/select/candidate_assembly.rs
Outdated
Show resolved
Hide resolved
d63c039
to
171d558
Compare
Fixed this the right way by not instantiating the binder twice, but only once during the probe. |
r? aliemjay |
☀️ Test successful - checks-actions |
Finished benchmarking commit (114f1f6): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 662.279s -> 663.784s (0.23%) |
See UI test for demonstration of the issue.
This was "caused" by #117131, but only because we're using the
normalize_param_env
(which has been augmented with a projection clause used to normalize GATs) which features non-lifetime bound vars in it.Fixes #117602 technically, though that's also fixed by #117542.
r? types