My favorite among the four alternatives is:

*buffer*

The reason is that the entities of SRFI 214 have the same algorithmic
complexity guarantees and support the same operations as a *gap
buffer* (see [1]) whose gap is fixed to the right end, so a SRFI 214
entity is essentially a gap buffer without a gap. Moreover, it is
rather trivial to upgrade the data structure of SRFI 214 to a full gap
buffer at virtually no additional charge. Another reason why I would
choose this name among the four is that it easily composes with
data-type prefixes like u8buffer or charbuffer. The procedure names in
SRFI 214 will also become shorter as in buffer-length vs
flexvector-length, etc.

*vectorlist* would also be okay for me, but is by far not as good.

--

[1] https://en.wikipedia.org/wiki/Gap_buffer

Am Mo., 12. Okt. 2020 um 18:51 Uhr schrieb Adam Nelson <xxxxxx@nels.onl>:
>
> Since there's been a lot of discussion on alternatives to the name "flexvector", but no real conclusion reached, and I don't have a clear favorite alternative name, I'm going to put it to a vote. There are four names suggested so far that that I'd be okay with. I'm going to decide using approval voting (https://en.wikipedia.org/wiki/Approval_voting), and use the winning name in the next draft a few days from now.
>
> Reply to this email (and CC the list) with a list of which names, out of these four, you would accept as the name for the SRFI 214 data structure:
>
> flexvector
> arraylist
> vectorlist
> buffer