-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
#[inline(always)] on forwarding slice/vec methods #85202
Conversation
r? @scottmcm (rust-highfive has picked a reviewer for you, use r? to override) |
Insufficient permissions to issue commands to rust-timer. |
@kornelski: 🔑 Insufficient privileges: not in try users |
Insufficient permissions to issue commands to rust-timer. |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit f4cf82d with merge b29ffaa953e639231b99078ce39e67382e0a909b... |
☀️ Try build successful - checks-actions |
Queued b29ffaa953e639231b99078ce39e67382e0a909b with parent e1ff91f, future comparison URL. |
Finished benchmarking try commit (b29ffaa953e639231b99078ce39e67382e0a909b): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
It has up to 3.7% impact on compile time, ugh. |
Similar to #85218