John: Given the increasing number of issues hanging on it, perhaps we should vote on the formerly-Amber docket (whose central issue is syntax-case vs explicit renaming) next?
After the latest Great Rearrangement at <
https://github.com/johnwcowan/r7rs-work/blob/master/ColorDockets.md>, Orange is now Orange again and the rest are named after minor Greek gods and Titans: Kronos, Eos, Hypnos, Leto, Morpheus, Selene, Pan, Iris. That way there is no question of "natural ordering", and we can vote on them in whatever order makes sense. (I considered renaming Indigo to Chaos, but desisted.)
The one with syntax-case/ER is Kronos. Everything in Kronos has a SRFI too, but they are all non-portable. (Note that as things get voted in, non-portable code may become portable.)
[Kronos] is also nearly completely SRFI’d — we don’t have formal specifications for explicit renaming macros (cough, SRFI 211?),
I've fixed the link to the MIT Scheme description, which will serve as the Specifications section. Marc mentioned that to make it interoperate properly it needs free-identifier?, which will just be eq? on existing systems.
nor of the Racket/Gerbil syntax-case extensions I proposed (but they can be kicked down into a subsequent ballot if necessary),
Moved to the new Iris Docket (non-portable, non-SRFI).
nor of Guile’s with-ellipsis which is necessary to support R7RS's extended form of syntax-rules in a syntax-case-based implementation (again, SRFI 211). I think it would be helpful to have an answer to these questions sooner rather than later.
My only objection is political. Nobody has voted on any R7RS dockets for many years (mea maxima culpa), and I am afraid what will happen if we throw them into controversial waters right away. I expect Orange to be relatively calm by comparison, and if we can get through it alive, we can move on to Kronos.