Clarifying bitvector-pad Shiro Kawai (27 Aug 2023 23:30 UTC)
Re: Clarifying bitvector-pad John Cowan (28 Aug 2023 07:26 UTC)
Re: Clarifying bitvector-pad Wolfgang Corcoran-Mathe (28 Aug 2023 16:33 UTC)
Re: Clarifying bitvector-pad Wolfgang Corcoran-Mathe (28 Aug 2023 19:11 UTC)
Re: Clarifying bitvector-pad Shiro Kawai (28 Aug 2023 22:56 UTC)
Re: Clarifying bitvector-pad Wolfgang Corcoran-Mathe (29 Aug 2023 00:31 UTC)

Re: Clarifying bitvector-pad Wolfgang Corcoran-Mathe 29 Aug 2023 00:31 UTC

On 2023-08-28 12:56 -1000, Shiro Kawai wrote:
> If both of the authors like to make it an error when _length_ is shorter
> than the bitvector, it's ok as well, though inconsistencies between SRFIs
> may confuse newcomers.  The SRFI text should be clarified either way,
> though.

Whatever John thinks best is fine with me. There's sense in both
arguments. I also agree that we should minimize inconsistencies with
the string SRFIs.

> BTW, the current reference implementation returns _bvec_ as is when
> _length_ is the same as the length of _bvec_, but it contradicts the SRFI
> text "Returns a copy of _bvec_ ...".  As bitvectors are mutable, this makes
> a difference.

Thanks very much for finding this. I'll fix it and look through the
sample implementation for similar contradictions.

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