stack ghci attempts to load a removed module

[UnkindPartition]

If you remove a module from a project and erase all mentions of it from the cabal file and other source files, stack ghci may still attempt to load it (and fail).

This happens because Stack.Package.getDependencies will resurrect the dead module name from a stale interface file.

I don't really know what to do about this, but it sure was annoying and took me quite some time to figure out.

% stack --version
Version 1.0.3, Git revision 3f7b50fe598ec83eda5d393fe5b08a99ce5ac1e9 (dirty) (3212 commits) x86_64

[borsboom]

That definitely sounds like a bug. I think at one point it was the other way around (where modules left out of the .cabal file but referenced by source files wouldn't get loaded), but this is going a bit too far :)

Does running stack build and then stack ghci again help? In theory, the stack build should refresh the interface files and remove mentions of the removed module. Although stack ghci should be running the build first anyway, unless you're passing in --no-build.

[mgsloan]

I cannot reproduce the issue: https://gist.github.com/mgsloan/1b30acd0de8b57f1d014 . Does the thing I tried work for you? What's different about your setup?

Like @borsboom mentioned, are you passing in --no-build? Issues like this are why building is done by default. It'll be necessary until #1364

[UnkindPartition]

In my case, the code wasn't buildable. It contained some errors that I was going to fix with the help of ghci. So, I guess stack did try to build it but failed.

[borsboom]

Yup, that explains it! Perhaps for the GHCI case we could have it skip any unlisted module which can't be found on the file system. In any case, we could make the warning in case of failed pre-GHCi build more clear that there can be inconsistent results.

[mgsloan]

Fixed!