[fix] Only map nodes of the exact same type #71 #73
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.
Fix #71
This PR fixes the problem of array type references and "normal" type references being matched, which in turn can result in crashes when the merge tree is being built. The reason for this behavior is that 3DM merge has absolutely no notion of correct relationships between parent and child nodes. Thus, if nodes of mismatched type are mapped, then their children may be merged such that whichever type comes out triumphant from the merge suddenly has children of types (or with roles) that it can't actually have. Thus, building the merged spoon tree crashes.
This is a very conservative fix, and forces matches to only be between exactly the same type of node. This may cause issues elsewhere. I'm not sure. Only benchmarks can tell. I do think it is necessary, however, due to 3DM's ignorance of valid and invalid parent-child relationships.