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.
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
Introduce paged vector #66430
Introduce paged vector #66430
Changes from 10 commits
07da937
ba19f7d
81ab2c0
a6aa4f4
597e9b1
ce1ea6b
912f8f2
f8758f1
af92d90
3cf7542
f862ab3
bcc1dc6
7b4b29a
e728b08
2465ce5
7f0316e
4962ef4
a2f0d74
5c063a6
8241145
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we really want to support shrinking? I mean I understand the general usecase but if we "sell" this data structure as a performance optimization applicable in cases when we know the container size (but we do not know the memory access pattern and we only assume it will be sparse). I'd think that we want to complain if people try to use it outside of this use-case...
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, in the beginning I had
expand()
but there was the comment that it would have required changing the user code. In the end it was relatively easy to supportresize()
and indeed it simplifies integration. Given the work is already done, whatever simplifies approval of this PR is fine with me.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.
IIRC @dwblaikie raised this point. @dwblaikie, would you be okay if we assert on and make no-op the resize operation if the size was already set? I am fine keeping it as it is but I feel the current state is not very coherent from the perspective of what we intend to use this data structure for...