-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Improve get_by_key_enumerated
more
#86429
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking try commit (172d0d098473f7e9b4ee053d7ed424405c064d3a): 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 still requires finding the upper bound/amount of items before returning the iterator. That's needed because the key (of type &Q) doesn't live long enough to return it. But since |
So, you mean making |
No, I'm suggesting just taking the |
Ah, that makes sense! Applied the suggestion via d731d61. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking try commit (a683ef3cff6fb2682ca8fbed8aa293340539643d): 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 |
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.
Nice.
(You still need to update the tests.)
Since I'm not on the compiler team or compiler-contributors, assigning it to someone on the compiler team for final approval:
d731d61
to
55974fa
Compare
55974fa
to
edc012a
Compare
This comment has been minimized.
This comment has been minimized.
edc012a
to
702ca32
Compare
☔ The latest upstream changes (presumably #87287) made this pull request unmergeable. Please resolve the merge conflicts. |
702ca32
to
7cc7e27
Compare
7cc7e27
to
6761826
Compare
r? @oli-obk for re-assigning (according to the GitHub reviewer suggestions) |
@bors r+ |
📌 Commit 6761826 has been approved by |
☀️ Test successful - checks-actions |
Follow-up of #86392, this applies the suggestions by @m-ou-se.
r? @m-ou-se