You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a project with cabal new-style builds, flycheck always prints and error about not being able to find dependencies, since they are not in the global ghc store.
The text was updated successfully, but these errors were encountered:
Cabal new-style builds are not very well supported at the moment. As a good alternative I can suggest using dante. It may require a bit more setup but also provides a bit more features (e.g. get type of identifier at point). Ultimately it boils down to using vanilla ghci and calling cabal repl (stack repl, nix-style thing, etc) which works pretty robustly (similar to how this projects attempts to address the "getting warnings out of the compiler" problem). It also has flycheck integration.
Given the existence of strictly more featureful alternatives (e.g. dante, haskell-language-server), with dante being about as complicated to set up as this project, it's probably safe to state that this project is unlikely to get support for new-style builds. It's potentinally possible given enough time but not at all clear whether benefit/cost ratio makes it a good idea.
When using a project with cabal new-style builds, flycheck always prints and error about not being able to find dependencies, since they are not in the global ghc store.
The text was updated successfully, but these errors were encountered: