-
Notifications
You must be signed in to change notification settings - Fork 842
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
For ghc >= 8.2, default to -fhide-source-paths #3784
Comments
On second thought, we already doing munging on build output, perhaps the munging should be updated to default to removing paths from the build output? This way it can work for ghc < 8.2 and the build logs get stored with full paths. |
I'd much rather see this made the default in GHC than see Stack do some special stuff and basically reimplement it (edit: with munging, that is). Plus, if it were default in GHC, Stack could drop its existing munging, in favor of just telling the user that if they want the verbosity of paths at all, it might as well be absolute ones. |
We're already doing the munging. I agree with disabling it where possible and instead using the flag for GHC >= 8.2 . Here are the gory details of what it currently does: https://github.com/commercialhaskell/stack/blob/fix-category-ghc-options-in-config-yaml-3753/src/Stack/Build/Execute.hs#L1804 Actually, looking closely, I don't think this munging affects the filepaths of |
Hello. I would like to work on this, if that's ok. |
Sounds great @mauriciofierrom! I think you'll basically be looking at two parts to this modification:
Does that give enough direction to get started? |
Yes, thank you very much! |
Implemented in #4736, thanks @mauriciofierrom! |
Thanks for the great pointers @snoyberg 🙂 |
See http://hsyl20.fr/home/posts/2018-01-15-ghc-hiding-source-and-object-paths.html . Makes ghc build output look much nicer.
I see no strong downside, can probably be re-enabled with
-fno-hide-source-paths
. So, it should come before user-provided ghc-options.The text was updated successfully, but these errors were encountered: