Sam Halliday a écrit : > Dear all, > > The decompositions in the linear package have been given their own > package... I'm just flagging up a concern (prior to the release of the API > for 2.0) that this might make things tricky in the future. The current > implementations of the decompositions are nice and general, but we will have > implementations that are optimised for the storage types in the future. > > Since the decompositions are in a separate package, that means the default > implementations will never be able to access implementation details of the > matrices they are working on. Unless future implementations end up going > into the linear package. That will just get messy and users will be confused > why some decompositions are in "linear" and others are in "decompositions". > > I recommend that the decompositions package be simply merged into the linear > package. This is the way we do it in matrix-toolkits-java and to the best of > my knowledge, nobody has complained about that structure for any reason. >
The decision was taken on 15th February: http://markmail.org/thread/62peuye5psp6o433 I understand your concerns and agree with them. If everybody is OK, we can go back to a single (but very large) linear package. I won't start an official vote on this though ... Luc --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
