On 2020-08-18 15:10 -0400, John Cowan wrote:
> That said, we should either make bitvector= do what vector= does, or we
> should change it to bitvector=?

If bitvector= is to do what vector= does, it should take a comparison
procedure.  SRFI 160's @vector= doesn't.  Alex Shinn opines
that this is a Bad Thing:

https://github.com/ashinn/chibi-scheme/issues/674#issuecomment-666943410

I don't know whether it's useful to allow custom comparisons on
bitvectors.  It's obviously good that vector= allows them, but I
wonder if it makes any sense with homogeneous collections.

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"For good or ill, when I went off to grad school, I studied
linguistics, so the only computer language I used there was LISP.
It was my own personal McCarthy era." --Larry Wall