-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Inline DebruijnIndex
methods
#80057
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Inline DebruijnIndex
methods
#80057
Conversation
@bors try @rust-timer queue |
Insufficient permissions to issue commands to rust-timer. |
⌛ Trying commit 2208f5e with merge d556efc2d01383e316fdb5a9cad3ba9df3f9b0fb... |
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 2208f5e with merge c49e4b740ec507a6d372a03481e2990c33c1dade... |
☀️ Try build successful - checks-actions |
Queued c49e4b740ec507a6d372a03481e2990c33c1dade with parent 99baddb, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (c49e4b740ec507a6d372a03481e2990c33c1dade): 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 |
This doesn't seem to fix the performance 😕 |
I wonder if it's the functions on |
IIUC those already have |
What should I do with this? Should I close it? Should we merge it? |
If this isn't improving performance, I don't see why we should merge it. Thoughts? |
Yeah, I'll just close this. |
With regards to #79169, the only other function that got moved out was the |
Attempts to fix the perf regression from #79169. Could someone queue a perf run for this?
r? @nikomatsakis cc @rylev