This causes implementations that don't over-ride that method to lose the benefits of sparsity when iterating through rows.
I deduce from the existence of your email that important sparse matrix implementations suffer from this defect. On Wed, Mar 21, 2012 at 10:32 PM, Jake Mannix <[email protected]> wrote: > Can anyone tell me what the following implementation choice will cause: > > public class MatrixVectorView extends AbstractVector { > > //... > > public Iterator<Element> iterateNonZero() { > return iterator(); > } > > // ... > > } > > Note that MatrixVectorView is returned from every call to viewRow(), and > getRow() was removed in the last release. > > -- > > -jake >
