Fwd: GHC Module change database

AF ---------- Forwarded message --------- From: Ari Fordsham Date: Sun, 8 Aug 2021 at 16:43 Subject: Re: GHC Module change database To: Vaibhav Sagar 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 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 wrote:

Hi Ari,

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

Thanks, Vaibhav

On Mon, Aug 9, 2021 at 1:34 AM Ari Fordsham wrote:

...

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

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 http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs