I'd rather note as fact that cycles are burnt by this in multiple places
#12851: Regression: GHC doesn't show filepaths by default anymore -------------------------------------+------------------------------------- Reporter: hvr | Owner: Type: bug | Status: patch Priority: low | Milestone: 8.2.1 Component: Compiler | Version: 8.1 Resolution: | Keywords: regression Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D2728 Wiki Page: | -------------------------------------+------------------------------------- Comment (by bgamari): like emacs/vim/atom/vscode and hie/ghc-mod/intero, those could be burnt in one place. This is a fair point.
Third, I think ghc is just breaking expectations here. Just try to load Ruby, Python or C with the following code and see how much you expect:
...
I'm not entirely sure this is an apples-to-apples comparison though. Python and Ruby are both interpreted languages with no real compile-/run- time phase distinction and certainly no "batch" compilation. In the case of C++ you rarely invoke the compiler itself; instead you typically invoke it via some build system, most of which do provide per- module feedback on progress. The same holds for most Scala and Java build systems, as far as I know. Of course, none of this is to say we shouldn't reconsider our output. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12851#comment:11 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler