Introduce MappingCollection
interfaces as modifiable views of a tree's internal mapping store
#133
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.
Contains some Generics fuckery, mostly due to the inability to represent
V extends ElementMappingView super E
. This is required since the collection holds elements of typeE
, but allows elements of typeV
to be added or queried via the*Compatible
methods. Thankfully the API doesn't need to expose any of these internal shenanigans.A byproduct of the PR's changes is that mapping trees'
add
methods now also accept read-only mapping element views, the code for converting such arguments to the tree's internal representation was already in place; this doesn't change the API semantics.I also moved the
getKind
methods fromMemoryMappingTree
's internal mapping entry implementations directly toElementMappingView
and added default implementations for them, used for some minor optimizations in the mapping collections.Supersedes #129.