Only compile Agda instances to a Haskell instance if they target a Haskell class #284
Conversation
This file contains 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
|
The second commit implements the same logic but for instance arguments: if the type of an argument is not compiled to a class in Haskell, then we compile it to a regular argument instead. |
This was
linked to
issues
Feb 22, 2024
jespercockx
force-pushed
the
NonClassInstance
branch
from
80c4998 to
ebbabd1
Compare
Co-authored-by: Lucas Escot <[email protected]>
jespercockx
force-pushed
the
NonClassInstance
branch
from
ebbabd1 to
4dacb56
Compare
This was referenced Oct 1, 2024
Closed
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.
This is a little gift for @jakobn-ai , who asked in #270 (comment) if we could have instances on the Agda side that compile to regular functions in Haskell. I thought this should be easy since we can just check whether a given instance actually targets a type that is compiled to a Haskell class, and it turns out I was right :)