-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Make Const::val()
return a ref, to avoid copies.
#94202
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
I got small wins locally with this, let's see what happens on CI. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5a858f4b82990b735ecd36f1d6540d00335b45af with merge cd5bb4597008c7ac6ea4149005523abc0955b5e2... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The idea comes from the last commit of rust-lang#90951.
5a858f4
to
a9d3cd1
Compare
@bors try |
⌛ Trying commit a9d3cd1 with merge e93437f564dcb9cd868f5ec5177b53a0a0b7b4e5... |
☀️ Try build successful - checks-actions |
Queued e93437f564dcb9cd868f5ec5177b53a0a0b7b4e5 with parent 026d8ce, future comparison URL. |
Finished benchmarking commit (e93437f564dcb9cd868f5ec5177b53a0a0b7b4e5): comparison url. Summary: This benchmark run did not return any relevant results. 13 results were found to be statistically significant but too small to be relevant. 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 led to changes in compiler perf. @bors rollup=never |
Nothing interesting going on here. |
The idea comes from the last commit of #90951.
r? @ghost