[GHC] #8796: -ddump-splices prints to error stream

GHC ghc-devs at haskell.org
Mon Feb 17 11:44:51 UTC 2014


#8796: -ddump-splices prints to error stream
-------------------------------+-------------------------------------------
        Reporter:  jstolarek   |            Owner:
            Type:  bug         |           Status:  new
        Priority:  normal      |        Milestone:
       Component:  Compiler    |          Version:  7.9
      Resolution:              |         Keywords:
Operating System:              |     Architecture:  Unknown/Multiple
  Unknown/Multiple             |       Difficulty:  Easy (less than 1 hour)
 Type of failure:              |       Blocked By:
  None/Unknown                 |  Related Tickets:
       Test Case:              |
        Blocking:              |
-------------------------------+-------------------------------------------

Comment (by jstolarek):

 I looked at the code responsible for this and it seems that this was a
 concious decision (not sure if correct one). Code is in
 [[GhcFile(typecheck/TcRnMonad.lhs)]]. There's `dumpTcRn` function which
 uses `printInfoForUser` to print to `stderr` (`printOutputForUser` would
 print to `stdout`). `dumpTcRn` is used as a backend for dumping renamer
 and typechecker traces as well as TH splices. Now I'm not sure if all of
 this should be printed on stdout or just the TH splices? It seems strange
 to me that stderr is used as an output for more detailed debugging
 information. I feel this is not the intent for stderr.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8796#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list