This is to facilitate the HPPC/Colt maneuver, and also to allow a collections lib unmixed with math.
Upon closer examination, it looks like the rest of you remove the JET dependencies from the collections code when you imported it. So, a simpler proposal arises: 1) Move Sorting and a few other non-mathematical things to utils. 2) Move collections to 'collections'. 3) The remainder remains in 'math'. On Wed, Jan 27, 2010 at 5:33 PM, Sean Owen <sro...@gmail.com> wrote: > Chiming in late -- I'd ask, do you expect this split to be useful? > meaning, will there be a non-trivial number of cases where someone > imports 1 sub module and not the others? Because importing all that is > 'math' now isn't a big deal, IMHO. If it's looking painful, I say just > drop it? > > On Wed, Jan 27, 2010 at 10:20 PM, Benson Margulies > <bimargul...@gmail.com> wrote: >> I took a first look at this, and tied myself up in a pretzel. There >> are some rather complex loops here. >> >> One approach is to pull only the bare dependencies of collections into >> scalar math, and then put everything else that isn't collections into >> vector-math. >> >> Some might prefer to see more things go into the scalar library. >> >> I might argue that starting with this approach and then doing a few >> extra shuffles is the way to go in any case. >> >
