Am Fr., 10. Apr. 2020 um 21:13 Uhr schrieb John Cowan <xxxxxx@ccil.org>:
Indeed, the existing post-finalization notes have been incorporated by the vote, though I mention the fact in each case for the avoidance of doubt.  Currently the R7RS-large set/bag, immutable list, flonum, comparator, and vector libraries all have post-finalization notes incorporated.  SRFIs 48 (format strings) and 149 (syntax-rules template extensions) will be balloted.  SRFI 97's note is purely editorial in nature.

I will possibly replace SRFI 149 by a version that is compatible with the R6RS so that implementations like Larceny that want to support both standards can do so without any problem.

Marc
 

On Fri, Apr 10, 2020 at 12:05 AM Vincent Manis <xxxxxx@gmail.com> wrote:

On 2020-04-09 8:55 a.m., John Cowan wrote:
> I think this is a case for a post-finalization note, which is a
> recommendation to implementers placed in the Status section of the
> SRFI.  You can look at SRFI 113 for what they look like if you want to
> draft one.  On this set of facts, I'm reasonably sure Alex and Arthur
> would accept it.

My thoughts on post-finalization notes are that when people vote on a
SRFI for inclusion in R7RS-Large, they are explicitly voting for or
against the SRFI as amended, unless the ballot question explicitly rules
out a note.

So while a post-finalization note is a recommendation in the SRFI, it
becomes normative if adopted into R7RS-Large.

-- v