StaticArray(T, N)#map returns an Array(T)

[Nephos]

Hello,

I wonder why a StaticArray.map returns an Array and not a StaticArray.

If you think it is better to returns a StaticArray, tell me I'll make a PR.

Regards,

[asterite]

We could do this, yes. Right now map returns Array in all types except Tuple. There's a bit of tension because Array is the recommended container type to use, but I guess optimizing that for StaticArray and Slice would be a good idea (one can invoke to_a at the end if you need an array in the end).

[Nephos]

I changed my mind, regarding how map should behave.
As it is still possible to use .map!, we can also do .dup.map! (optimizing way).

I don't think there is a need to change the behaviour of StaticArray(T, N).map (it means map cannot return something else than StaticArray(T, N))

I just added .map_with_index! which was missing.

• no optimization problem as it is possible to use .dup.map!
• no non-standard behavior as .map can returns something else than elements of type T (StaticArray(T, N))

Is it acceptable ?