Thanks for taking the initiative again. Before voting, may I ask one
more question?

What kind of algorithmic time guarantees will the next draft include?
I am asking because we have suggested that it may be a good idea to
say that the SRFI 214 entities are as fast as vectors on the platform.
But if the platform vectors are more or less O(1), this may rule out
more possible alternative implementations (see here:
https://en.wikipedia.org/wiki/Dynamic_array#Performance) than we want.
Depending on whether you actually want to fix an implementation model,
some of the above names may be better than others.

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