@Mike Thinking out loud here ... one option would be to put the core.matrix 
dependent stuff in gg4clj in a separate ns, like gg4clj.datasets or 
similar. This would then avoid the loading time for users just wanting to 
use gg4clj.core. I'm not sure I think this as good a solution, ultimately, 
as trying to make core.matrix load in a more incremental fashion -  but I 
do appreciate that it's not so easy to change core.matrix, and that there 
are good reasons not to. What do you think - does this sound like a 
reasonable way forward to you? 


Jony

-- 
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.

Reply via email to