On Mon, Jul 3, 2017 at 11:10 AM, Takashi Kato <ktakashi19@gmail.com> wrote:

* bits->list is specified to accept only one argument but sample implementation accepts optional argument len

I think the implementation is correct, and I will change the spec.
 
* It might be useful and consistence if vector->bits also takes
optional argument
  start and end like other vector->* procedures (e.g. vector->string)

This SRFI doesn't do optional arguments, primarily so it can be fast on systems where optional arguments are slow due to consing.  So I reluctantly reject this one.  It would be fine to add it as an extension, of course.

-- 
John Cowan          http://vrici.lojban.org/~cowan        xxxxxx@ccil.org
"Why yes, I'm ten percent Jewish on my manager's side."
        --Connie Francis