-
Notifications
You must be signed in to change notification settings - Fork 13.3k
partially move type outlives handling into trait solving #97641
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
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit e79af26 with merge b53ad5f2483f02c39bfe14104e375f804cbd1a14... |
💔 Test failed - checks-actions |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit dd0275a14a5639efe5513b4052b5747f534abe33 with merge d9bc44bb8c0843cdc8098318762cf7e779d43e5f... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued d9bc44bb8c0843cdc8098318762cf7e779d43e5f with parent fb19760, future comparison URL. |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (d9bc44bb8c0843cdc8098318762cf7e779d43e5f): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
cachegrind for regression-31157-Check-Full
|
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 2b0b3119d9e574a3c7d296561e571c806a7b3d1b with merge 24d477a06bd06c22ae5041e196ebb2eceabca339... |
Queued 48512925c982ea116a15d1c632e429f39d32129d with parent 64a7aa7, future comparison URL. |
Finished benchmarking commit (48512925c982ea116a15d1c632e429f39d32129d): comparison url. Instruction count
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
it's still slightly worse, though at a point where it's close to meaningless. One more improvement: @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 1b4014705e47bdb61f275bfc1ff44f2842b37d7c with merge 3819c8a3730afd08cf40b3709a67b3f0e799b483... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued 3819c8a3730afd08cf40b3709a67b3f0e799b483 with parent 1a97162, future comparison URL. |
Finished benchmarking commit (3819c8a3730afd08cf40b3709a67b3f0e799b483): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 Footnotes |
alright, good enough for me not to bother, time to improve the diagnostics |
= note: but lifetime parameter must outlive the static lifetime | ||
|
||
error: aborting due to previous error | ||
|
||
For more information about this error, try `rustc --explain E0477`. | ||
For more information about this error, try `rustc --explain E0478`. |
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.
I think this PR could also fix E0478
to not show must outlive the static lifetime
error message. See #41816.
@lcnr any updates on this? |
not really, can close this for now |
r? @nikomatsakis cc @oli-obk