Fix constructors for custom container #40
Merged
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.
Previously I (wrongly) used containers for the construction of maps when a custom container was specified. That's not really how it is intended, the parameter should still be an allocator.
This fixes that issues, so now its possible to copy/move etc. maps when a custom container is used. That container needs the constructors that accept an allocator.
I had to bump version by a major number to 2.0.0 because this is an incompatible API change.