Lassi Kortela <xxxxxx@lassi.io> writes:

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

How about a ranking? Implementations can be tested and assigned
conformance scores and then sorted into a list.

I started a project a few days ago to measure and display this, and
uploaded it to Github now:
https://github.com/a2379/r7rs-compliance

I also want to include performance benchmarks and rankings.

> 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.

I would be hesistant because most implementations could be put into a
"base conformance" profile, but then the "more conformant" profiles
would have to be awkward and arbitrary to fit the different
implementations' quirks.

The only profile that comes to mind is TCO and continuations. I intend
to include them in the compliance tests.