optimized range insertion for boost::container::hub - #339
Merged
igaztanaga merged 1 commit intoAug 5, 2026
Merged
Conversation
boost::container::hub
igaztanaga
added a commit
that referenced
this pull request
Aug 6, 2026
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
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.
Optimizes range insertion taking advantage of the fact that insertion goes through all non-empty and non-full blocks first and then uses empty blocks exclusively. Current hub tests cover all the new code, including
catchblocks.Performance increase (
perf.cpp, release mode):GCC 13
Before
After
Clang 13 for Visual Studio (clang-cl)
Before
After
VS 2022
Before
After