Unmaintained implementations Antero Mejr (13 May 2024 14:25 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 14:39 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 15:17 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 17:46 UTC)
Re: Unmaintained implementations Antero Mejr (13 May 2024 18:05 UTC)
Categorizing and describing implementations Lassi Kortela (13 May 2024 18:24 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (13 May 2024 20:16 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 20:23 UTC)
Re: Categorizing and describing implementations Lassi Kortela (13 May 2024 20:37 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 20:39 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (13 May 2024 21:19 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (13 May 2024 21:26 UTC)
Containers Lassi Kortela (13 May 2024 21:37 UTC)
Re: Containers Arthur A. Gleckler (13 May 2024 21:41 UTC)
Re: Categorizing and describing implementations John Cowan (13 May 2024 21:51 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 08:23 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 11:55 UTC)
Snap and Lisp Lassi Kortela (14 May 2024 12:15 UTC)
Re: Snap and Lisp Stephen De Gabrielle (14 May 2024 12:45 UTC)
Re: Snap and Lisp Lassi Kortela (14 May 2024 13:33 UTC)
Re: Categorizing and describing implementations Marc Feeley (14 May 2024 12:48 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 13:09 UTC)
Re: Categorizing and describing implementations Marc Feeley (14 May 2024 13:29 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 14:03 UTC)
Re: Categorizing and describing implementations Stephen De Gabrielle (14 May 2024 17:45 UTC)
Re: Categorizing and describing implementations Lassi Kortela (19 May 2024 13:47 UTC)
Re: Categorizing and describing implementations Antero Mejr (20 May 2024 14:03 UTC)
Re: Categorizing and describing implementations Arthur A. Gleckler (20 May 2024 14:24 UTC)
Definition of "Scheme" Lassi Kortela (14 May 2024 13:21 UTC)
Re: Categorizing and describing implementations Jakub T. Jankiewicz (14 May 2024 13:53 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 19:12 UTC)
Re: Unmaintained implementations Jakub T. Jankiewicz (13 May 2024 20:40 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 20:43 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 20:49 UTC)
Re: Unmaintained implementations Arthur A. Gleckler (13 May 2024 20:55 UTC)
Re: Unmaintained implementations Lassi Kortela (13 May 2024 21:07 UTC)
Re: Unmaintained implementations Antero Mejr (13 May 2024 21:18 UTC)
Metadata files Lassi Kortela (13 May 2024 21:34 UTC)
Re: Metadata files Antero Mejr (13 May 2024 21:41 UTC)

Re: Categorizing and describing implementations Lassi Kortela 19 May 2024 13:47 UTC

> I think we can include table like this one:
>
> https://web.scheme.org/
>
> But larger with more essential Scheme features, and those that implement
> more of them will be on top. More mature Scheme implementation will most
> likely implement all the features.
>
> For some people the features will not matter. Only the language of
> implementation and where it runs. For some they will pick the one that
> implement most of the features.
>
> We can do something like Wikipedia does for parser generators:
>
> https://en.wikipedia.org/wiki/Comparison_of_parser_generators
>
> we can indicate the supported feature with green and not supported with red
> and partial with yellow.

This is all reasonable.

But I think we should present some kind of summary by default so that
newcomers are not overwhelmed by too much detail.

It would be good to define some "profiles" of RnRS conformance. A
profile would be a group of features, and criterion for how fully each
feature is supported.

This will probably take a lot of experimentation to get right.