-
Notifications
You must be signed in to change notification settings - Fork 710
Optionally store hie files #8685
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
Comments
I have success using the following:
Now when I remove |
This is something about IDEs, right? @jneira: could you ping some cabal devs that use IDE and so would have an opinion? |
I think @fendor could have a good vision of the interaction between hie files and cabal |
I don't think this is necessarily about IDEs. HIE files can be consumed by many other tools (e.g. policeman, calligraphy). I would find it very useful if cabal could store them (e.g. for analysing the whole application depenency graph). |
I also wonder if this is something that should have a more "official" flag for producing the additional artifacts, much like we have |
Hi all, I would like to encourage these changes to be made sooner rather than later. I am working on gotoDefinition for hls as part of Summer of Haskell and I need the hie files to be generated for the changes I will be making. How can I help this process move forward? I have tried out the changes @aavogt proposed above with similar results. I would be happy to work on a pull request, but I don't want to step on your toes, @aavogt. |
@nlander make the pull request. I look forward to using "gotoDefinition for hls". |
I believe #9019 solves this issue. |
I added the following to my
~/.cabal/config
But I do not end up with .hie files in
~/.cabal/store/
. I think they should go beside thehi
files. Maybe-hiedir
needs to be set. I want this because the hoogle/haddock fileshare/doc/html/<packagename>.txt
is missing information about instances of associated types.The text was updated successfully, but these errors were encountered: