Handling source locations in HsSyn via TTG

[Simon Peyton Jones]

Vlad

Are you arguing for Solution D?  Or are you proposing some new solution E?  I can't tell.


| As to merge request !1970, it isn’t good to special-case GhcPass in a
| closed type family, making other tools second-class citizens. Let’s say I
| have `MyToolPass`, how would I write an instance of `WrapL` for it?

Easy

	type instance WrapL ToolPass t = ...

What am I missing?

Simon

| -----Original Message-----
| From: Vladislav Zavialov <vladislav at serokell.io>
| Sent: 28 October 2019 10:07
| To: Simon Peyton Jones <simonpj at microsoft.com>
| Cc: ghc-devs at haskell.org
| Subject: Re: Handling source locations in HsSyn via TTG
| 
| I care about this, and I maintain my viewpoint described in
| https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.has
| kell.org%2Fpipermail%2Fghc-devs%2F2019-
| February%2F017080.html&data=02%7C01%7Csimonpj%40microsoft.com%7C06c859
| d8bc0f48c73cb208d75b8e895c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63
| 7078540055975603&sdata=FhkqfWGXaNX%2Fz4IiCcvoVCyzVsSAlyz6Y1dxEGUjX9I%3
| D&reserved=0
| 
| I’m willing to implement this.
| 
| As to merge request !1970, it isn’t good to special-case GhcPass in a
| closed type family, making other tools second-class citizens. Let’s say I
| have `MyToolPass`, how would I write an instance of `WrapL` for it?
| 
| - Vlad
| 
| > On 28 Oct 2019, at 12:31, Simon Peyton Jones via ghc-devs <ghc-
| devs at haskell.org> wrote:
| >
| > Friends
| >
| > As you know
| >
| > 	• We are trying to use “Trees That Grow” (TTG) to move HsSyn towards
| a situation in which GHC is merely a client of a generic HsSyn data type
| that can be used by clients other than GHC.
| > 	• One sticking point has been the question of attaching source
| locations.  We used to have a “ping-pong” style, in which very node is
| decorated with a source location, but that’s a bit more awkward in TTG.
| > 	• This wiki page outlines some choices, while ticket #15495 has a
| lot of discussion.
| > 	• HEAD embodies Solution A.  But it has the disadvantage that the
| type system doesn’t enforce locations to be present at all.   That has
| undesirable consequences (eg ticket #17330)
| > 	• The proposal is to move to Solution D on that page; you can see
| how it plays out in MR !1970.
| > 	• (I think Solutions B and C are non-starters by comparison.)
| > If you care, please check out the design and the MR.   We can change
| later, of course, but doing so changes a lot of code, including client
| code, so we’d prefer not to.
| >
| > Let’s try to converge by the end of the week.
| >
| > Thanks
| >
| > Simon
| >
| >
| >
| >
| >
| > _______________________________________________
| > ghc-devs mailing list
| > ghc-devs at haskell.org
| >
| https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask
| ell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-
| devs&data=02%7C01%7Csimonpj%40microsoft.com%7C06c859d8bc0f48c73cb208d7
| 5b8e895c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637078540055975603&a
| mp;sdata=CRYEYmjuAYYIhoAeTPbi%2FctCiWmkIjL6pKUTBgVBwo8%3D&reserved=0