Add instance Ord for Field, FieldLine, SectionArg and Name #9387
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geekosaur
approved these changes
Nov 1, 2023
alt-romes
approved these changes
Nov 2, 2023
mergify
bot
added
the
merge delay passed
Mikolaj
force-pushed
the
ord-for-fields
branch
from
67a9438 to
af0126c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While not terribly interesting semantically, having
instance Ordallows to put things intoSetandMapand also allows to deriveinstance Ordfor types, containingFieldas a record field (my motivational example wasConfig).{-# LANGUAGE StandaloneDeriving #-}is there just to attach@sinceannotations without requiring GHC >= 8.2 or so.