Next: srfi ralists rationale, Previous: srfi ralists abstract, Up: srfi ralists [Index]
Procedure names have been chosen to be consistent with R6RS, even
though in some cases such as list-ref
and list-tail
the
choice seems poor since they include the prefix list-
even though
they do not operate on lists, but chains of pairs, i.e. lists and
improper lists, and arbitrary objects, respectively. Although the names
have remained the same, the descriptions have been corrected (e.g. using
pair or obj instead of list for parameter names).
Should the names be changed as well?
To what extent should standard Scheme procedures and syntax that consume
or construct lists be included in this proposal? For example, should
all of the (rnrs base)
library that deals with lists be
included? By my count this would mean adding: lambda
,
apply
, vector->list
, list->vector
,
string->list
, and list->string
. I am inclined to add
these. Should all of the (rnrs lists)
library be included?
These procedures are easily defined in terms of what’s given here, and
no performance advantage is gained by implementing them “under the hood”
using the data structures in the reference implementation. I am
inclined not to include them.
Should a car+cdr
procedure be added?
Should the current syntax and procedures sub–libraries be included?