* Should interval= be named interval=? instead, by analogy with
string=?, char=?, etc.?
* Since interval-intersect? returns a usable 'true' value, should it
be named interval-intersect, by analogy with member, etc
* Arrays and intervals are specified as being Scheme types different
from all others. However, storage classes do not seem to have
this requirement. I am guessing this design is intentional,
perhaps to make some optimized implementations easier, but am not
sure.
* In the description of specialized-array-default-safe?, is the #t
intentionally specific, or is any true value (i.e., anything other
than #f and #false) permissible there?
Similarly, there are a few places
where an argument is restricted to being a boolean. I assume this
would be interpreted as limiting valid values to those for which
boolean? yields true.
* Would it be desirable for array->list to guarantee lexicographic
traversal of the array (similar to the guarantee provided by
array->specialized-array)? If such a guarantee is added, then it
would also propagate to array-fold and array-fold-right given
their definitions in terms of array->list.]]
* SRFI 25's array-ref and array-set! permit array indices to be
provided either as separate arguments or as a vector or as a
1-dimensional array. Would a similar strategy be useful for the
relevant procedures of this SRFI?