containers: rework handling of ProxyVector internal storage #193
Conversation
This file contains 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
andrea-iob
force-pushed
the
containers.rework.proxy.vector
branch
2 times, most recently
from
0f1fb93
to
7118713
Compare
andrea-iob
force-pushed
the
containers.rework.proxy.vector
branch
from
7118713
to
a3925ea
Compare
Open
roccoarpa
approved these changes
Jun 29, 2021
edoardolombardi
approved these changes
Jun 29, 2021
marcocisternino
approved these changes
Jul 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've added a very simple "pool allocator" to the ProxyVector container, in order to reduce memory allocations when ProxyVector needs an internal storage. I'm using quotes because what I'm doing is not really a pool allocator, I just save the last 10 internal storages and I re-used those storages when a new ProxyVector is created.