Update GHCJS conditions to also support the GHC JavaScript backend #75
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
|
My opinion is same as in #73 Add a CI job to The #73 is not merged, because we apparently need some GHC specifc WASI toolchain, and I'm not gonna bother with something like that. I cannot easily debug if there is a problem, I don't care about accepting the patch (and taking maintenance burden). |
|
This patch doesn't appear to be in head.hackage? |
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 MR is to update CPP and cabal file conditions to support the GHC JavaScript backend.
Because the JavaScript backend uses a different FFI syntax than GHCJS, the
initialSeedJSfunction now has two versions of the import string.The main motivation for this change is the use of this function in
ghcjs-base's testsuite.