-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check that all used definitions are actually defined in the Haskell code #119
Comments
Alternatively we could use the following criterion for which functions are allowed to appear in compiled Haskell code:
If we have the full set of allowed functions, we could also make a call to |
jespercockx
added a commit
to jespercockx/agda2hs
that referenced
this issue
Jun 9, 2024
…rated Haskell code
jespercockx
added a commit
to jespercockx/agda2hs
that referenced
this issue
Jun 9, 2024
…rated Haskell code
jespercockx
added a commit
to jespercockx/agda2hs
that referenced
this issue
Sep 19, 2024
…rated Haskell code
jespercockx
added a commit
to jespercockx/agda2hs
that referenced
this issue
Sep 24, 2024
…ated Haskell code
jespercockx
added a commit
to jespercockx/agda2hs
that referenced
this issue
Sep 25, 2024
…ated Haskell code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@flupe mentioned to me that it would be a good idea to check that all defined symbols that are used in the generated Haskell code are also actually defined in the Haskell code. This would require some kind of "foreign" pragma for annotating a function that is already defined in the Haskell code.
The text was updated successfully, but these errors were encountered: