Re: We probably shouldn't allow user-defined storage classes
Bradley Lucier 22 Feb 2025 17:10 UTC
On 2/17/25 17:22, John Cowan wrote:
> This argument proves too much.
OK, I'll remove this item from my list of proposed changes.
Arthur just committed some changes I made to eliminate (I hope) all
unnecessary mutations in the library code and to copy modifiable
procedure arguments (lists and vectors) before calling user-defined
storage class procedures. These changes remove some types of possible
internal library crashes.
Brad
Things to change in a future library:
1. (srfi 231) is "safe", with an "unsafe" library (srfi 231 unsafe);
mixing safe and unsafe arrays and operations could be accomplished by
renaming routines.
2. Get rid of array-freeze!
3. Do not fix the order of evaluation of array elements in arguments to
the "bang" (!) procedures.
4. Add (array-rebase array [lower-bounds]) to translate an array to
given lower bounds.
5. Add broadcasting of arrays and adding new axes to arrays.
6. Add a notation for quickly specifying Bawden-style array
transformations similar to that of NumPy or Racket's math/array.