You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First i was going to vote for (C) but now i think option (A) is the best use for Array. A trait for something that is like an array could be called ArrayLike.
Thanks for the input. I'm somehow hoping that using ArrayBase in client code can be avoided (and they stick to OwnedArray, ArrayView). But as usual I don't know enough yet 😄
So we would need a trait (Array) to work with generic arrays (OwnedArray or ArrayView) without ArrayBase in client code?
Maybe Array could combine multiple specialized traits to allow implementing generic algorithms (similar to the approach of ImgLib2).
Activity
jdroenner commentedon Mar 13, 2016
First i was going to vote for (C) but now i think option (A) is the best use for
Array. A trait for something that is like an array could be calledArrayLike.bluss commentedon Mar 13, 2016
Thanks for the input. I'm somehow hoping that using ArrayBase in client code can be avoided (and they stick to OwnedArray, ArrayView). But as usual I don't know enough yet 😄
jdroenner commentedon Mar 13, 2016
So we would need a trait (
Array) to work with generic arrays (OwnedArrayorArrayView) withoutArrayBasein client code?Maybe
Arraycould combine multiple specialized traits to allow implementing generic algorithms (similar to the approach of ImgLib2).bluss commentedon Mar 13, 2016
or to be generic over something that does not exist yet, for example proposed masked arrays or arrays with various statically known properties