On Thu, Mar 7, 2019 at 3:17 PM Lassi Kortela <xxxxxx@lassi.io> wrote:

I sympathize with your concern in that storing the type definitions
right in each SRFI's own Git repository would make them more likely to
stay in sync. At the same time, this might necessitate quite a lot of
edits to the definitions as the type checker is figured out over the
years. The SRFI repos were originally made to track the documents; they
would now track both the documents and the exploratory type checking
work based on them.

What does Arthur as the editor think about this?

I'm happy to have the SRFI repositories be the home of these files if they don't change, collectively, more than every few months — or more often when they're new.

For a while, the eggs for some of Chicken Scheme's SRFI implementations were stored in the SRFI repositories. However, that became a problem because they were changing so often, for reasons that were to do with Chicken and not with the SRFIs. Because of that, I asked the Chicken folks to host their own repos for those SRFIs, giving them complete control and relieving me of responding to countless pull requests.

So I do have a limit. Still, it would be great to have all this information, which applies to all Scheme implementations, gathered together with the corresponding SRFIs. So let's start with that assumption.

My personal motivation would be just to transcribe the simple things
written in the SRFIs into a machine-readable form, preferably quite soon
:) All the other work proposed here is awesome too, but I'm ambivalent
about how its the timeline and scope fit with the simpler and more
immediate goals originally proposed.

If I recall, Ciprian's format is extensible, so we could start by extracting, one way or another, simple type signatures, then add more information as Ciprian and others produce it.