TTG hsSyn for Batch and Interactive Parsing
Simon Peyton Jones
simonpj at microsoft.com
Fri May 18 14:13:02 UTC 2018
This sounds fine. But I still don’t understand
There would still be a single parser definition in Parser.y, which would make use of functions to add the additional info to the generated source tree, which would be NOPs if the information was not being kept. This is similar to what happens at present with the Api Annotations.
What is the type of the parser? Does it produce
parser :: String -> HsSyn (GhcPass (Parsed WithApiAnnotation)
parser :: String -> HsSyn (GhcPass (Parsed WithoutApiAnnotation)
We can’t make the result type depend on DynFlags! (Yet)(
parser :: DynFlags -> String
-> HsSyn (GhcPass (Parsed (if …
So I’m puzzled.
Nomenclature. I’d say “NoApiAnnotations” rather than “WithoutApiAnnotations”.
Also: do we have data to show that it’s not OK to always keep API annotations. That would be simpler, wouldn’t it.
Incidentally the Haddock stuff, decorations of type (Maybe LHsDocString) somehow belong in this world too, don’t they?
From: Alan & Kim Zimmerman <alan.zimm at gmail.com>
Sent: 10 May 2018 22:35
To: Simon Peyton Jones <simonpj at microsoft.com>
Cc: ghc-devs <ghc-devs at haskell.org>
Subject: Re: TTG hsSyn for Batch and Interactive Parsing
I have updated the Wiki with the clearer names, and noted that a single parser definition would still be used, as at present, but would only keep the extra info if it was requested to.
The naming around interactive and batch is to anticipate a further step I would like to take, to make the parser fully incremental, in the sense that it would process as input the prior parse tree and a list of changes to the source, and then generate a fresh parse tree, with the changed nodes marked. This mode would be tightly coupled to an external too like haskell-ide-engine, to manage the bookkeeping around this.
My thinking for this is to use the approach presented in the paper "Efficient and Flexible Incremental Parsing" by Wagner and Graham.
The plan is to modify `happy`, so that we can reuse the existing GHC Parser.y with minor modifications. This is the same approach as used in the library tree-sitter, which is a very active project on github.
WIP is at , but it is very early stage.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs