[Swift-devel] Re: fixed_array_mapper versus array_mapper on output

[Mihael Hategan]

On Sat, 2011-02-12 at 22:40 +0000, Ben Clifford wrote:
> > Somebody remind me why we have those both since they seem to be intended
> > to do the same thing.
> 
> Array mapper is bug 27, r750 and r764.
> 
> I think maybe at the time there were no array literals in arbitrary 
> locations? (I think there didn't used to be early on...?)
> 
> Which would make it not quite a superset of the fixed_array_mapper at the 
> time it was introduced, though it looks like it is now (except apparently 
> its broken, so it isn't...)
> 

Ben, your emails are usually epitomes of clarity. This one, not so much.

I know that we used the fixed array mapper to allow returning arrays
from an app. It's isStatic() returns true, whereas array_mapper's
isStatic() returns false. So perhaps it's a matter of making
array_mapper "static".