Daniel Gröber (dxld)

If you are affected by this bug feel free to say so in the GHC ticket. Knowing how many users are actually affected by a given issue is hard and...

Yeah I can totally see how `-Werror` would mess things up in this case. The easy solution is to just add the module the warning mentions to `other-modules:` or you...

Ok I've tracked down the problem. We only ever pass the module names given on the command line to `loadTargets`, that used to not be a problem but with `warn-missing-home-modules`...

1ea7e85b31c5f2c6a7aae46c116f40680f0c05fc + 6bf0ac7de82a28f20e4144ff2ca66ed97b8fee03 is a quick hack to fix this issue, can you confirm it works for you?

You need to delete cabal-helper's binary cache since you used a pre-release version, assuming you're on unix that should be at `~/.cache/cabal-helper`. I really have to add some sort of...

@mdibaiee Probably, see: https://github.com/DanielG/ghc-mod/wiki#readpackagedb-inappropriate-type.

I think you're using a stackage nightly in your project which has Cabal-2.x already, actually I can see that from the output above. That isn't supported by cabal-helper-0.7.x. The release...

You did change the `resolver: __` setting in `stack.yaml`, right?

Very strange. If `$ stack path` also mentions that path: `"/Users/tehnix/Dropbox/__Synced/Testing/Haskell/Haskell-LLVM/.stack-work/dist/x86_64-osx/Cabal-2.0.0.2"` (note the `Cabal-2.0.0.2` bit) this sounds like a stack bug I guess. According to https://www.stackage.org/lts-9.1/package/Cabal the Cabal version should...

Sounds like a plan, I really have no idea why Stack would have the Cabal version used to build projects deviate from the one in the stackage snapshot..