It works for the development branch of Incanter 2.0 - which is a pretty significant project with a lot of matrix code. You can switch between Clatrix (native BLAS via JBlas), persistent vectors (regular Clojure vectors) and vectorz-clj (pure JVM code) transparently.
I think it would be the same for Neanderthal - I don't see anything that would be inconsistent with core.matrix from an API perspective. On Wednesday, 14 January 2015 05:38:22 UTC+8, Dragan Djuric wrote: > > It would be nice if that would be that easy. However, I am sceptical... > > On Tuesday, January 13, 2015 at 8:13:36 PM UTC+1, Christopher Small wrote: >> >> Awesome project! >> >> I'll echo the encouragement towards having Neanderthal implement the >> core.matrix protocols. You'll have much higher adoption if folks know they >> can just plug your tool in by changing a single line setting the underlying >> implementation to Neanderthal. And as Mikera points out, it would be nice >> if we kept the Clojure matrix API space cohesive. >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
