Implement compare operations for view types #5900
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.
Which issue does this PR close?
Closes #5897 .
Rationale for this change
Now we can compare two view type arrays.
Unfortunately, this PR becomes larger than I thought, partly because the test cases are rather comprehensive and the comparison is non-trivial.
The view type comparison code might be slightly more esoteric than one might expected, I hope the comments could help understanding/justify the complexity.
What changes are included in this PR?
Are there any user-facing changes?