Having a 'single source of truth' database will help with this.

Don't hesitate to make a PR to https://gitlab.haskell.org/haskell/ghc-api-compat so that at least the DB and the .cabal files live in the same repo. I have created this package but I don't use it so anyone should really feel free to take it over. Sylvain On 08/08/2021 17:46, Ari Fordsham wrote:

AF

---------- Forwarded message --------- From: *Ari Fordsham* <arifordsham@gmail.com <mailto:arifordsham@gmail.com>> Date: Sun, 8 Aug 2021 at 16:43 Subject: Re: GHC Module change database To: Vaibhav Sagar <vaibhavsagar@gmail.com <mailto:vaibhavsagar@gmail.com>>

That's where I generated it from :-)

It would be nice to generate that from the new database.

My main motivation was as follows: There are two possible paradigms for GHC API compatibility:

- Export old names for new modules - as in ghc-api-compat <https://gitlab.haskell.org/haskell/ghc-api-compat>   This allows existing code to (kind of) 'just work' - but it doesn't help in managing that code as it gets extended to use new features

- Export new names to old modules   I am thinking of working on a tool that does this.   You need to rewrite code to use current modules (maybe https://github.com/facebookincubator/retrie/issues/33 <https://github.com/facebookincubator/retrie/issues/33> will help), but then you can just target the latest API, and have compatibility built in.   This seems to me better for active codebases.

  Having a 'single source of truth' database will help with this.

AF

On Sun, 8 Aug 2021 at 16:36, Vaibhav Sagar <vaibhavsagar@gmail.com <mailto:vaibhavsagar@gmail.com>> wrote:

Hi Ari,

Have you seen https://gitlab.haskell.org/haskell/ghc-api-compat <https://gitlab.haskell.org/haskell/ghc-api-compat>?

Thanks, Vaibhav

On Mon, Aug 9, 2021 at 1:34 AM Ari Fordsham <arifordsham@gmail.com <mailto:arifordsham@gmail.com>> wrote:

I've made a database of GHC API module changes.

https://github.com/AriFordsham/ghc-module-renames <https://github.com/AriFordsham/ghc-module-renames>

This might be useful for automatic tooling.

It would be nice if this would be moved into the GHC Gitlab, and kept up-to-date.

Ari Fordsham _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org <mailto:ghc-devs@haskell.org> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs <http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs>

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs