-
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
Using <Iter>::new instead of exposing internal fields #76787
Conversation
15eca49
to
95dd12f
Compare
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.
Thanks, LGTM. It might be better to create the NonNull
outside of the new
functions so that these functions don't have any additional safety requirements.
95dd12f
to
75ea5bc
Compare
slice.iter is quite hot, let's see if we somehow regress something here. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Awaiting bors try build completion |
⌛ Trying commit 75ea5bcb25469d100c5063fa3cf08ede866a2d32 with merge 949e85c6bc2e139a5e9b07b26df01c81c9ecd99e... |
☀️ Try build successful - checks-actions, checks-azure |
Queued 949e85c6bc2e139a5e9b07b26df01c81c9ecd99e with parent 95386b6, future comparison URL. |
Finished benchmarking try commit (949e85c6bc2e139a5e9b07b26df01c81c9ecd99e): 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 |
You might have to put |
8b1dde5
to
eafe1b3
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit eafe1b365e6784208d7df8462d22da5c2b207f37 with merge d2df5ef8b0f37065ba646a8a28bb6085e0d3b724... |
☀️ Try build successful - checks-actions, checks-azure |
Queued d2df5ef8b0f37065ba646a8a28bb6085e0d3b724 with parent 95386b6, future comparison URL. |
Finished benchmarking try commit (d2df5ef8b0f37065ba646a8a28bb6085e0d3b724): 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.
LGTM
perf also seems fine now 👍
Thanks 👍 @bors r+ rollup=never |
📌 Commit 39732ab8f6e6493079d5e9364521e44d133049fa has been approved by |
Did you mark all the file as viewed ? Because I intend to squash some commits together. |
Init false state in Split* constructors
now I did 😆 go ahead |
39732ab
to
b659370
Compare
Done. |
@bors r+ rollup=never |
📌 Commit b659370 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
As requested in #76311 (comment)