Streamline Binary
equality and comparison
#110
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.
Unlike
Integer
andText
,Binary
equality/comparison have been modified to be less convenient.Binary
instances behave "as expected" (element-wise equality).Binary
,byte[]
, andImmutableArray<byte>
. The rationale being, one generally does not expect two array/list to be equal because the sequence of elements are the same. Generic equality usually refers to having the same reference for two objects. This is pretty standard across many programming languages including even javascript and python. Such functionality is generally provided by a separate method.