[
https://issues.apache.org/jira/browse/MATH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082299#comment-13082299
]
Gilles commented on MATH-626:
-----------------------------
Wouldn't it be an incompatible change? I'm referring to the title of this
issue, not the various other suggestions that should have been in their own
JIRA requests.
> Move RealVector.sparseIterator() to SparseRealVector
> ------------------------------------------------------
>
> Key: MATH-626
> URL: https://issues.apache.org/jira/browse/MATH-626
> Project: Commons Math
> Issue Type: Improvement
> Reporter: Arne Plöse
> Priority: Minor
> Fix For: 3.1
>
>
> Having this method available for all is not very efficient, because if I want
> use this feature I must check for interface SparseRealVector.
> otherwise different implementations could be faster.
> I.e. no array clone and the assigning all values again.
> Maybe one could add a menthod fillstate() to SparseRealVector to guide which
> is faster - use array clone and then sparseIterator or just create the array
> and then fill it up.
> To reduce confusion a second Interface ArrayRealVector with the method
> getDataRef() and removing getData() from RealVector would be nice - there is
> a toArray() this should be sufficient.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
