Matrix-type-friendly syntax and more

[bearophile]

Gor Gyolchanyan:

> I don't think strides are necessary. You can always opApply your image
> in a certain way. Define a private struct, which has an opApply, which
> iterates over every third channel of each pixel.

See:
http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=146466


> lazy ranges are generally better, then arrays, because with them, you
> can avoid copying anything altogether.

Strides is just a syntax. The user defined type is later allowed to perform a lazy striding.

Bye,
bearophile