Luite Stegeman

I used my tachyon drive to go two days back in time and do a proof of concept to show how the GHC API should be set up for GHCJS...

Just to be clear, pretty much everything is still GHC, the `ghc` package is still needed, but the session is changed to use the GHCJS compilation settings, which means different...

`ghc-mod` would need to know whether to typecheck a project with ghc or with ghcjs. I think this would mean either adding the logic to detect the configured compiler for...

hmm, perhaps I can change it to use a single pipe for all watches. if many watches are created, having an thread for each of them would probably also be...

is that really something that should be done in the `.cabal` file? shouldn't GHC know what compiler to run (and the options that it accepts) when it encounters a `.m`...

I've been hesitant to patch this package, since the problem points to a GHC installation issue rather than a problem with the package itself. Instead of hardcoding a compiler program...

Ah the error messages there aren't yet as good as they should be. And the plugin loading mechanism is rather hacky right now. Right now what GHCJS does is the...

Does anyone still see this problem? I've never encountered it (I get my GHC installs from GHCup usually).

Which cabal version are you using? It doesn't appear to fail on my system (macOS 14.2.1): ``` cabal-install version 3.10.2.0 compiled using version 3.10.2.1 of the Cabal library ```

Maybe I can reproduce it with stack. What's the `stack9.8.yaml` file you're using?