abstract object/array type out so that arbitrary types can be used #209
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.
This pull request fixes some conflicts from #169, but is basically the work of @erichkeane (thanks for that!). I only fixed a conflict and added documentation.
Changes: The container types
object_t
andarray_t
can now be set to any container provided that it is aliased to a type with 2 template arguments (object_t
- defaulting tostd::map<Key,T>
) and 1 argument (array_t
- defaulting tostd::vector<T>
).As the public API changes in a subtle way, the feature can be added in 2.0.0 at the earliest.