Consider adding derived Ord instances #139
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.
Hi!
We have a scenario in which we are using
Data.Avro.Schema
inside a Set to avoid duplicated entries, and had to manually provideOrd
instances for everything (here: https://github.com/higherkindness/avro-parser-haskell/blob/master/src/Language/Avro/Types.hs#L36-L52).Maybe you can consider adding this if it is not too invasive? 馃槃
Also, we'd like to know (@serras and me) if there's any ETA on the next release which contains the logical types, since we'd love to publish the newest version of our library using those changes! 馃槈