|
SRFI 214: Flexvectors
Arthur A. Gleckler
(07 Oct 2020 17:10 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 09:41 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 09:59 UTC)
|
|
Re: SRFI 214: Flexvectors Adam Nelson (08 Oct 2020 12:10 UTC)
|
|
Nomenclature
Lassi Kortela
(08 Oct 2020 12:19 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 12:19 UTC)
|
|
Nomenclature
Lassi Kortela
(08 Oct 2020 12:26 UTC)
|
|
Re: Nomenclature
Marc Nieper-Wißkirchen
(08 Oct 2020 12:31 UTC)
|
|
Re: Nomenclature
Lassi Kortela
(08 Oct 2020 12:50 UTC)
|
|
Re: Nomenclature
Marc Nieper-Wißkirchen
(08 Oct 2020 13:01 UTC)
|
|
Flexvectors vs subtyping
Per Bothner
(08 Oct 2020 17:23 UTC)
|
|
Re: Flexvectors vs subtyping
Arthur A. Gleckler
(08 Oct 2020 17:29 UTC)
|
|
Re: Flexvectors vs subtyping
Adam Nelson
(08 Oct 2020 17:32 UTC)
|
|
Re: Flexvectors vs subtyping
Marc Nieper-Wißkirchen
(08 Oct 2020 17:46 UTC)
|
|
Re: Flexvectors vs subtyping
Adam Nelson
(08 Oct 2020 17:56 UTC)
|
|
Re: Flexvectors vs subtyping
Marc Nieper-Wißkirchen
(08 Oct 2020 19:21 UTC)
|
|
Re: Flexvectors vs subtyping
Lassi Kortela
(08 Oct 2020 20:09 UTC)
|
|
Re: Flexvectors vs subtyping
Marc Nieper-Wißkirchen
(08 Oct 2020 20:51 UTC)
|
|
Re: Flexvectors vs subtyping
Lassi Kortela
(08 Oct 2020 21:23 UTC)
|
|
Re: Flexvectors vs subtyping
Arvydas Silanskas
(12 Oct 2020 09:58 UTC)
|
|
Re: Flexvectors vs subtyping
Marc Nieper-Wißkirchen
(08 Oct 2020 20:35 UTC)
|
|
Re: Flexvectors vs subtyping
Per Bothner
(08 Oct 2020 17:54 UTC)
|
|
Re: Flexvectors vs subtyping
Lassi Kortela
(08 Oct 2020 20:39 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 17:32 UTC)
|
|
Re: SRFI 214: Flexvectors
Adam Nelson
(08 Oct 2020 17:35 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 18:05 UTC)
|
|
Re: SRFI 214: Flexvectors
Adam Nelson
(08 Oct 2020 18:34 UTC)
|
|
Re: SRFI 214: Flexvectors
Marc Nieper-Wißkirchen
(08 Oct 2020 18:57 UTC)
|
|
Flexvector computational complexity
Adam Nelson
(08 Oct 2020 17:47 UTC)
|
|
Re: Flexvector computational complexity
Marc Nieper-Wißkirchen
(08 Oct 2020 19:04 UTC)
|
|
Re: Flexvector computational complexity
John Cowan
(08 Oct 2020 19:18 UTC)
|
|
Re: Flexvector computational complexity
Adam Nelson
(08 Oct 2020 19:40 UTC)
|
I like "buffer", although it's not a name that makes it immediately obvious that the type has a relationship to vectors/lists. Another possibility is to just accept overloading of existing terms, and to use "arraylist", which anyone familiar with Java will immediately recognize. I'm not a fan of "field", it's too overloaded of a term and it usually refers to a binding or a text input GUI widget. On 10/8/20 5:59 AM, Marc Nieper-Wißkirchen wrote: > Am Do., 8. Okt. 2020 um 11:40 Uhr schrieb Marc Nieper-Wißkirchen > <xxxxxx@nieper-wisskirchen.de>: > > [...] > >> It would be nice if we could find a new term as sexy as "list", >> "array", and "vector". What about "(dynamic) field", for example? > PS While I still like the term "field", "buffer" could be an > alternative. A "char-buffer" (type-specialized "flexvector" that > stores characters) could then be the basis of an editor like Emacs.
