... | ... | @@ -2,7 +2,7 @@ |
|
|
|
|
|
## Status as of July 2017
|
|
|
|
|
|
- There is some work afoot moving GHC to `prettyprinter`. See [\#14005](https://gitlab.haskell.org/ghc/ghc/issues/14005).
|
|
|
- There is some work afoot moving GHC to `prettyprinter`. See #14005.
|
|
|
|
|
|
## Status as of June 2017
|
|
|
|
... | ... | @@ -13,7 +13,7 @@ The following was extracted from Ben's response to Siddharth Bhat on [ghc-devs]( |
|
|
|
|
|
>
|
|
|
>
|
|
|
> I saw this ticket on trac: [\#8809](https://gitlab.haskell.org/ghc/ghc/issues/8809).
|
|
|
> I saw this ticket on trac: #8809.
|
|
|
> I would like to take this up, but I'd like help / pointers and stuff. I
|
|
|
> have GHC setup, I know how to use phabricator, but.. where do I start? :)
|
|
|
>
|
... | ... | @@ -25,7 +25,7 @@ meaning to write down some thoughts on it. Here it goes: |
|
|
|
|
|
|
|
|
Currently Alfredo Di Napoli is [working](https://github.com/haskell/pretty/pull/43) on the `pretty` library to
|
|
|
both improve performance and allow us to drop GHC's fork (see [\#10735](https://gitlab.haskell.org/ghc/ghc/issues/10735)),
|
|
|
both improve performance and allow us to drop GHC's fork (see #10735),
|
|
|
perhaps to use annotated pretty-printer documents. Meanwhile, David
|
|
|
Luposchainsky, has recently [released](https://www.reddit.com/r/haskell/comments/6e62i5/ann_prettyprinter_10_ending_the_wadlerleijen_zoo/) his `prettyprinter` library
|
|
|
which may serve as a drop-in replacement to `pretty` and handles all of
|
... | ... | @@ -93,7 +93,7 @@ fork. |
|
|
In my opinion we should avoid baking more stylistic decisions (e.g. printing
|
|
|
types in red, terms in blue) into the modules like TcErrors which produce
|
|
|
error messages. This is why I propose that we use annotated
|
|
|
pretty-printer documents in [\#8809](https://gitlab.haskell.org/ghc/ghc/issues/8809) (see comment 3). This would allow us
|
|
|
pretty-printer documents in #8809 (see comment 3). This would allow us
|
|
|
to represent the typical things seen in GHC error messages (e.g. types,
|
|
|
terms, spans, binders, etc.) in structured form, allowing the error
|
|
|
message consumer (e.g. GHC itself, a GHC API user, or some JSON error
|
... | ... | |