Fix RDF::List#== comparisons to RDF::Values #305
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.
Ruby 2.3.0 changed the behavior of
Comparable#==to avoid hiding errors. This led toNoMethodErrors for comparisons that returnfalsefor previous Rubies.This introduces a custom
RDF::List#==implementation for explicitly supported comparisons betweenRDF::Valueclasses. We returnfalseimmediately forRDF::Values which are not#list?; falling back onComparablefor other types.Further,
RDF::Lists with three elements that happen to coincide with the terms of an RDF::Statement would previously returntrue. E.g.:RDF::List[:s, :p, :o] == RDF::Statement(:s, :p, :o). This unusual edge case is patched by way of the changes described above.A similar change is made to
RDF::Statement#==to preserve symmetry.Closes #304