-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Don't store a redundant span in user-type projections #137123
Conversation
@bors try @rust-timer queue r? @oli-obk |
This comment has been minimized.
This comment has been minimized.
Don't store a redundant span in user-type projections While experimenting with some larger changes, I noticed that storing this span here is unnecessary, because it is also present in the corresponding `CanonicalUserTypeAnnotation` and can be retrieved via the annotation's ID.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (aa2aeba): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 4.9%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 790.759s -> 787.867s (-0.37%) |
Don't store a redundant span in user-type projections While experimenting with some larger changes, I noticed that storing this span here is unnecessary, because it is also present in the corresponding `CanonicalUserTypeAnnotation` and can be retrieved via the annotation's ID.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors retry temp for failure on windows |
☔ The latest upstream changes (presumably #137295) made this pull request unmergeable. Please resolve the merge conflicts. |
9f3fdb1
to
ffaf825
Compare
This span is already present in the corresponding `CanonicalUserTypeAnnotation`, and can be retrieved via the annotation's ID.
Actually, I'm going to back out the visitor changes, as I'm no longer confident in them, and they aren't strictly necessary for the other changes. @bors r- |
ffaf825
to
8bb574f
Compare
PR CI is green; I'm going to unilaterally re-approve this because it's a subset of the changes that were originally approved. @bors r=oli-obk |
☀️ Test successful - checks-actions |
Finished benchmarking commit (28b83ee): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 2.0%)This 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 sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 773.474s -> 774.026s (0.07%) |
While experimenting with some larger changes, I noticed that storing this span here is unnecessary, because it is also present in the corresponding
CanonicalUserTypeAnnotation
and can be retrieved via the annotation's ID.