Vector optimize for reallocations #3
Labels
enhancement
New feature or request
Comments
adam-fonseca
pushed a commit
to adam-fonseca/radiant-cpp
that referenced
this issue
Jul 22, 2024
Merge in SEN/radiant-cpp from upstream-sync-2 to sensor-main * commit '2db8d56da1d01fdfc18586755261b6a4d77e775e': Revert "Provide strong guarantee for rad::Vector" allocator concept requirements Forgot to set the size to 0 fix formatting errors Move clear out of class and use DtorRange refactor to remove uncovered line Fix build for mac and windows Provide strong guarantee for rad::Vector rename Handle to UniqueResource
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the feature, modification, idea, or suggestion.
The allocator contract was originally in-flux when
Vectorwas originally being developed. As such the reallocation capability on the allocator contract did not exist yet.Vectorcan take advantage of the ability to reallocate a block of memory through the allocator in paths where a new allocation must occur.Proposed implementation details (optional)
Vectorshould take advantage of the reallocation capability of the allocator contract to optimize resizing of the underlying block of memory whenever possible.The text was updated successfully, but these errors were encountered: