Closed altaic closed 8 years ago
At first glance this looks like ghc-mod problem. @DanielG, thoughts?
Hmm you probably need to run stack test
or something first so it does the equivalent of --enable-test
. Not sure how stack handles this to be honest.
I've been rigorously using my test-suite, so I can verify that running stack test
does not fix the problem.
ghc-mod 5.5.0.0 seems to pick those up just fine, so I think this was fixed upstream. Closing.
Any dependencies unique to the test-suite aren't detected by
haskell-ghc-mod
while using stack, thus producing erroneousimport
errors. The workaround is to additionally use a cabal sandbox.