Karl Glazebrook wrote: > Dan Sugalski wrote: > > > On the other hand, just extending out arrays to be multidimensional may > > well be good enough. > > > > This is my view. > Ditto. As I said yesterday, my current preferred option is that a list ref of list refs will also support a multidimensional indexing syntax. Furthermore, if it has a single basic data type and is declared ':compact' it should be stored in a contiguous block of memory. Finally, I believe that we need to adjust RFCs for reduce(), list generation, and zip/unzip/partition/reshape to work with n-dim matrices. Oh, and we also would need to look at how we can hide as much of the dereferencing as possible.
- Re: New variable type: matrix Jim Edwards
- Re: New variable type: matrix Nathan Wiger
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Baris
- Re: New variable type: matrix Christian Soeller
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Christian Soeller
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Buddha Buck
- Re: New variable type: matrix Jeremy Howard