-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Preintern some TyKind::Bound
values
#144434
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
base: master
Are you sure you want to change the base?
Conversation
- Cover `DebruijnIndex(2)`, for slightly better coverage. - Rename some things, to account for other region things that were renamed.
We already do the same thing for bound regions. This is a small perf win for the new trait solver.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Preintern some `TyKind::Bound` values
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (06fbedc): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.4%, secondary -2.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 469.891s -> 470.107s (0.05%) |
(note about results: I saw in other PRs that a handful of benchmarks are currently bimodal) |
|
r? @lcnr |
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.
Is this still a draft? I think that this is fine for now.
This seems pretty difficult and probably not worth blocking this on that. |
Correct, this no longer needs to be a draft.
Ok. Any time I do a shallow "make operation X faster" micro-optimization I always wonder if there is a deeper and better "avoid operation X altogether" change that could be done instead. |
The new trait solver produces a lot of these.
r? @compiler-errors