<p dir="ltr">I'm with mpickering on this one. Each stage has a debug format that makes sense for the stage. For parsing it is the exact ast</p>
<p dir="ltr">Alan</p>
<p dir="ltr"> </p>
<div class="gmail_quote">On 18 May 2016 12:43 PM, "GHC" <<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">#11140: add command-line option to GHC to dump raw parse trees of Haskell programs<br>
-------------------------------------+-------------------------------------<br>
Reporter: bollu | Owner:<br>
Type: feature request | Status: new<br>
Priority: low | Milestone:<br>
Component: Compiler | Version: 7.10.2<br>
Resolution: | Keywords:<br>
Operating System: Unknown/Multiple | Architecture:<br>
| Unknown/Multiple<br>
Type of failure: None/Unknown | Test Case:<br>
Blocked By: | Blocking:<br>
Related Tickets: | Differential Rev(s):<br>
Wiki Page: |<br>
-------------------------------------+-------------------------------------<br>
<br>
Comment (by mpickering):<br>
<br>
That is true but by them stages in the compilation pipeline you don't care<br>
about what the raw format looks like. When modifying the parser you need<br>
to know the precise structure of the AST rather than some pretty printed<br>
version produced by `Outputtable`.<br>
<br>
--<br>
Ticket URL: <<a href="http://ghc.haskell.org/trac/ghc/ticket/11140#comment:6" rel="noreferrer" target="_blank">http://ghc.haskell.org/trac/ghc/ticket/11140#comment:6</a>><br>
GHC <<a href="http://www.haskell.org/ghc/" rel="noreferrer" target="_blank">http://www.haskell.org/ghc/</a>><br>
The Glasgow Haskell Compiler<br>
</blockquote></div>