New draft (#5) and last call for comments on SRFI 164: Enhanced multi-dimensional Arrays
Arthur A. Gleckler
(20 Jul 2019 20:01 UTC)
|
Re: New draft (#5) and last call for comments on SRFI 164: Enhanced multi-dimensional Arrays
John Cowan
(21 Jul 2019 07:29 UTC)
|
array-map [was: last call]
Per Bothner
(22 Jul 2019 05:13 UTC)
|
Re: array-map [was: last call]
Lassi Kortela
(24 Jul 2019 10:37 UTC)
|
Re: array-map [was: last call]
Per Bothner
(25 Jul 2019 15:43 UTC)
|
Re: array-map [was: last call]
Lassi Kortela
(28 Jul 2019 15:25 UTC)
|
Re: array-map [was: last call]
Per Bothner
(04 Aug 2019 23:28 UTC)
|
Re: array-map [was: last call]
Lassi Kortela
(07 Aug 2019 18:07 UTC)
|
Re: array-map [was: last call]
John Cowan
(24 Jul 2019 11:01 UTC)
|
Re: array-map [was: last call]
Per Bothner
(25 Jul 2019 15:35 UTC)
|
Re: array-map [was: last call]
John Cowan
(25 Jul 2019 18:49 UTC)
|
Re: New draft (#5) and last call for comments on SRFI 164: Enhanced multi-dimensional Arrays Per Bothner (07 Aug 2019 17:38 UTC)
|
Re: New draft (#5) and last call for comments on SRFI 164: Enhanced multi-dimensional Arrays
Lassi Kortela
(07 Aug 2019 18:15 UTC)
|
My druthers is to finalize srfi-164 as is, except for fixing the typos John reported. I agree there is functionality that could be reasonably added (such as array-map), but those can always be added in the future. It is harder to change or remove functionality, which argues for focusing on a small number of useful building blocks. I also think before expanding the API, we should standardize on an API and/or syntax for ranges. It may also be useful to gain more experience with the "generalized vector" concept. So barring last-minute objections, I'll ask Arthur to finalize this thing tomorrow. -- --Per Bothner xxxxxx@bothner.com http://per.bothner.com/