GHC API: Call for requirements

#1

Dear all,

I am pleased to announce that the Haskell Foundation and Tweag are resuming efforts to define a stable API for GHC, and that I will continue the work of Alexis King as coordinator of the initiative.

In the first phase, we will collect and share a list of requirements for the GHC API that its users can propose, and select with the stakeholders the key features for an initial proposal of the API. For the sake of progress, the first proposal may be conservative, but it should serve as a foundation for further growth. In a second phase, a specification of the API will be elaborated.

To kick off the conversation, I invite all developers with a concern for the GHC API to reach out to me at facundo.dominguez@tweag.io. I’m keen to learn about the use cases and requirements that matter most to you.

Cheers!

35 Likes
Charting a course toward a stable API for GHC
[GHC API stability] Update #1
#2

Perfect, I’ll get in touch!

2 Likes
#3

I hope it’s okay that I write here instead of via email.

I’d like to point to Ben Gamari’s dump-decls script (link) which I think is a good example of something that should be possible to implement via the future GHC API.

1 Like
#4

I’m already on it :wink: Maintain a golden test of your package's API with `diff-package-api` and `print-api`

4 Likes
#5

It makes no difference to me :slight_smile:

Thanks for the pointer.

#6

:wave: Here’s a first update on the initiative.

3 Likes