I understood what he was suggesting. I still disagree. Dynamic dispatch and non-lattice typing structure is still required to make this all work. Java doesn't really do that. Pretending that what Java does is sufficient is hammer-looking-for-a-nail, not solving the problems at hand.
On Mon, Aug 15, 2011 at 6:52 PM, Greg Sterijevski <gsterijev...@gmail.com>wrote: > Forgive me for pushing my nose under the tent... I couldn't resist. > > I think Gilles is saying that each specialization of the matrix/vector > objects would need to support pre (and post) multiplication with a dense. > So > the type issue would not be problematic. > > On Mon, Aug 15, 2011 at 6:34 PM, Ted Dunning <ted.dunn...@gmail.com> > wrote: > > > No. > > > > You can't. This is because the type is lost as you enter the generic > > library. > > > > On Mon, Aug 15, 2011 at 4:28 PM, Gilles Sadowski < > > gil...@harfang.homelinux.org> wrote: > > > > > > They know that their own object is dense, but they don't know what > kind > > > of > > > > input they were given. They should still run fast if the input is > > > sparse. > > > > > > Couldn't we still rely on polymorphism by implementing "preTimes": > > > unknown.preTimes(dense) > > >
