... | @@ -32,6 +32,8 @@ Since every `RdrName` of interest is `Located`, it would be enough to add a list |
... | @@ -32,6 +32,8 @@ Since every `RdrName` of interest is `Located`, it would be enough to add a list |
|
|
|
|
|
This is the approach currently used in `HaRe`, and is presented for inclusion in the GHC API as [ https://phabricator.haskell.org/D5330](https://phabricator.haskell.org/D5330)
|
|
This is the approach currently used in `HaRe`, and is presented for inclusion in the GHC API as [ https://phabricator.haskell.org/D5330](https://phabricator.haskell.org/D5330)
|
|
|
|
|
|
|
|
#### D. Modify the `RenamedSource` AST so that it also fully represents the parsed source file, when used with the API Annotations.
|
|
|
|
|
|
### Discussion
|
|
### Discussion
|
|
|
|
|
|
|
|
|
... | @@ -40,4 +42,7 @@ AZ opinions: |
... | @@ -40,4 +42,7 @@ AZ opinions: |
|
|
|
|
|
Option A is not viable. Option B could work, but would have to be subject to a `DynFlag` otherwise the space penalty would be prohibitive for normal usage.
|
|
Option A is not viable. Option B could work, but would have to be subject to a `DynFlag` otherwise the space penalty would be prohibitive for normal usage.
|
|
Option C is a "bolt-on", but is known to do the job.
|
|
Option C is a "bolt-on", but is known to do the job.
|
|
|
|
|
|
|
|
|
|
|
|
Option D would be the best from a tooling perspective, but would be a massive engineering effort, and hard to justify given the use case.
|
|
|
|
|