Array interface refactoring

[Cale Gibbard]

On 23/02/06, Bulat Ziganshin <bulat.ziganshin at gmail.com> wrote:
> Hello John,
>
> Thursday, February 23, 2006, 4:07:52 PM, you wrote:
>
> JM> That is the plan. none of the current Array implementations will
> JM> change, they will still be instances of both MArray and HasBounds. it is
> JM> just that HasBounds will no longer be a superclass of MArray, however
> JM> that doesn't affect performance in any appreciable way.
>
> our plans are equal :)
>
> JM> (and array
> JM> operations pretty much always end up specialized anyway so all class
> JM> overhead disapears.)
>
> this depends. IArray/MArray interfaces currently contains only a few
> operations and all other implemented in fixed manner, so you can't
> omit any overheads

Well, there's always RULES pragmas. I can see that freeze and thaw get
rewritten in some cases, there's also a bunch for listArray.

 - Cale