James Lucas

You're not the first person to suggest this which means we should give it some serious thought! If I'm understanding correctly, your suggestion is to: - Change current `rows()` to...

Personally I'm with @Andlon . I prefer the current naming (though don't have an issue with having `rows()` return an iterator). I am also against adding alias functions, for the...

I agree with @Andlon . Currently we accept the row and column index in all functions and produce the flat data index ourself. I'm not sure of a situation when...

I'm afraid that I'm still not convinced (or maybe I just don't get it). Is it possible for you to give a (preferably) small example? There is actually an [example...

I'm afraid I'm not following this discussion very well... It seems this issue is at least somewhat resolved? Personally I think that even if this addition would add some utility...

@prismatica this makes sense to me though my opinion weighs less heavily than @Andlon and your own on this.

I'm labeling this as easy to highlight that there is room for some really valuable and lightweight contributions here. Most of the functionality is not bench-marked right now which leaves...

Thanks for writing this up and sharing. I'm very busy for the next couple of weeks but after I'll have some time to properly review and put some ideas forward....

Thanks for writing this up -I think it's a great idea! It certainly makes the decompositions easier to use in some cases and makes the signatures of some functions nicer....

I actually _really_ like this lazy evaluation approach. It feels very rust-like and has the advantage that it lets us compute things in the most efficient manor. The code is...