For editor's use only. Please do not edit this section.
??? the draft/final/withdrawn status of the SRFI, information on how to subscribe to its mailing list, and important dates in its history. The editor will add this section.
??? abstract, preferably shorter than 200 words. Please outline the need for, and design of, the proposal.
??? Optional section that may point out things to be resolved. This will not appear in the final SRFI.
??? detailed rationale. This should be 200-500 words long. Please explain why the proposal should be incorporated as a standard feature in Scheme implementations. List related standards and SRFIs, including dependencies, conflicts, and replacements. If there are other standards which this proposal will replace or with which it will compete, please explain why the present proposal is a substantial improvement.
??? detailed specification. This should be detailed enough that a conforming implementation could be completely created from this description.
Please include examples. They make it much easier for readers to understand your proposal.
Please follow the linguistic conventions described in the FAQ. In particular, please follow the conventions about the use of the terms must, must not, required, shall, shall not, should, should not, recommended, may, and optional defined by RFC 2119. This convention has been adopted by R7RS Small, too, in section 1.3.2 (PDF).
Also by convention, the phrase it is an error to X is used in Scheme documents to mean that X is not allowed, but to leave it up to the implementer to decide what to do in response. Implementations may signal an error, assign some new meaning to X, or fail catastrophically.
??? explanation of how it meets the sample implementation requirement (see process), and the code, if possible, or a link to it
We use the phrase sample implementation instead of reference implementation because the latter implies that the implementation itself is the source of truth, whereas for SRFIs, the document is normative.Source for the sample implementation.
??? credit where it is due
© 202? ???author(s)???.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.