For collection types List, Set, Map use equals() rather than isAssign… #406
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.
…able() - To support Guava ImmutableList etc
When using isAssignable(), the specialised collection types like Guava ImmutableList get treated like java.util.List and this means that we don't end up using any Custom JsonAdapter that we define for those special types.
Changing to use equals() means that we really expect the java.util List|Set|Map collection types to be used and no ArrayList, LinkedList etc (which would have kind of worked before but not really in that they all would have ended up as ArrayList, LinkedHashSet, LinkedHashMap. So using equals() here should be ok.