-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weeder doesn't work with stack 2.* #53
Comments
I don't think hi-file-parser exposes nearly enough details. I also don't think HIE files helps massively - the info I need is already in the .hi, but there's a chance Weeder could be improved with the info. I think the short term solution is to read the .hi files and send them through GHC --show-interface and then read the result. |
Uh oh, turns out the |
I have edited the README to require adding |
Can weeder add an argument |
Could you do a release with the README update? It took me a fair bit of head-scratching before I found this issue. |
Yep this one got my head scratching also because it broke my Travis |
Related to this, it would be useful if weeder popped up a message saying something like "NO COMPILATIONS FOUND - please recheck instructions about ghc-options in stack.yaml" when no compilation at all was found, rather than simply telling me that every single module in my cabal file wasn't compiled. |
I don't know whether all observed behavior is caused by stack 2.* but I will add it here to avoid duplication. On windows, See e.g. this log
|
@pjljvandelaar it seems to be a different issue. There is no |
It doesn't work with Stack 2: ndmitchell/weeder#53
Weeder 2.0 is being developed at https://github.com/ocharles/weeder so I suggest you go see if that fixes your issues. |
The new version of Stack doesn't generate
.dump-hi
files anymore (commercialhaskell/stack#4804).The workaround is to tell stack to generate them:
--ghc-options "-ddump-to-file -ddump-hi"
.Are
dump-hi
files mandatory for weeder? Is possible to use.hi
files only?UPD. I guess the solution is to use http://hackage.haskell.org/package/hi-file-parser which is used by stack, but that's a lot of things to do.
UPD2. https://www.haskell.org/ghc/blog/20190626-HIEFiles.html
The text was updated successfully, but these errors were encountered: