Fix allocator concept #23
Merged
Conversation
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
…roy-used Fix issue where allocator construct/destroy functions weren't being used with custom allocators on trivial types
…which were not default constructible
gharveymn
force-pushed
the
fix-allocator-concept
branch
from
a37af01 to
effa6a6
Compare
gharveymn
merged commit 4152925
into
ensure-allocator-construct-destroy-used
15 checks passed
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.
A few fixes for the Allocator concept, and other compilation errors which came up while writing an integration test using the PMR allocator combined with the Boost Interprocess shared memory manager.