-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] performance optimizations in Array.replaceSubrange
#66160
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
fa50e89
[stdlib] remove most branches from `Array.replaceSubrange`
oxy 869bbe9
[stdlib] fix `Array.replaceSubrange` for incorrect with: count
oxy bedda7e
[stdlib] only move/erase/add if required in Array.replaceSubrange
oxy c096203
[stdlib] add contiguous fast path in Array.replaceSubrange
oxy 0590552
[stdlib] remove unneeded replaceSubrange branch
oxy f2abb35
[stdlib] remove deinitialize branch (does this do anything?)
oxy 08586c5
[stdlib] `Array.replaceSubrange` code cleanup
oxy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It's so annoying that withContiguousStorageIfAvailable is allowed to pass a buffer with a nil baseAddress rather than just returning nil without executing the closure in that case. Otherwise we could use .unsafelyUnwrappedUnchecked here.
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.
(Actually what IS supposed to happen in that case? Should it just be the same as if newValues was empty?)
Uh oh!
There was an error while loading. Please reload this page.
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.
well, it says that if there is no contiguous representation, it should ignore body and just return nil?
and in this case,
newValues.count
/newCount
should be the same (and from above,> 0
) for a well-implemented collection?I'm not sure if its worth throwing in an extra assert for $0.count == newCount, or removing
!
for.unsafelyUnwrappedUnchecked
either.