Oops, I realized (scheme bytevector) already adopted that argument
order.   Please disregard my message.

On Tue, Sep 15, 2026 at 12:22 AM Shiro Kawai <xxxxxx@gmail.com> wrote:
>
> Except single-octet and native endianness ones, the setters take the
> argument in this order: bytevector, index, value-to-set, endianness,
> and size (if necessary).
> If they take the value-to-set as the last argument, we can just use
> them as a setter procedure corresponding to the getter, e.g.
>
> (getter-with-setter bytevector-uint-ref bytevector-uint-set!)
>
> Is there a reason for the current argument order?