as of a few days ago, ghcide always shows me this error message:
Bad interface file:
/nix/store/ph44jry464pgkb6fssdgjjmi553kxk5j-polysemy-1.3.0.0/lib/ghc-8.10.1/x86_64-linux-ghc-8.10.1/polysemy-1.3.0.0-HG7iVIxbcLzLoj08Qvtejl/Polysemy/Internal/Union.hi
Something is amiss; requested module polysemy-1.3.0.0:Polysemy.Internal.Union differs from name
found in the interface file profunctors-5.5.2:Polysemy.Internal.Union (if these names look the
same, try again with -dppr-debug)
It's always a different package instead of profunctors, but it's always Polysemy.Internal.Union. any idea what could be up here?
that's what I suspected as well, and I fiddled around but couldn't fix it. I'm just wondering why it happens in multiple projects with different packages for the interface file
as of a few days ago, ghcide always shows me this error message:
It's always a different package instead of
profunctors
, but it's alwaysPolysemy.Internal.Union
. any idea what could be up here?this isn't related to nix caching a bad build?
I've seen the "bad interface file" issues, but they usually go away once I do
rm .stack-work
(and have not been necessarily related to polysemy, at least in their error output)
that's what I suspected as well, and I fiddled around but couldn't fix it. I'm just wondering why it happens in multiple projects with different packages for the interface file
also ghcid and
nix-build
work fine, and they use the same package setdo you have a consistent reproducer?
yeah, the polysemy-test project should do it, with
ghc8101
inops/nix/default.nix
. but I really doubt it's not related to nixwhat
polysemy-plugin
are you using?master
though I tried switching to the latest releaeseā¦I think
maybe it's another ghc 8.10.1 issue. for now I'll just use 8.8.4 for development
it built successfully for me, from the uploaded release on hackage
with stack and this
stack.yaml
I'm guessing there are some new things that aren't uploaded, but I didn't manage to find the source repo
ok. guess I'll have to try and clean up the nix store
I'd just really like to know why the package name in the error keeps changing