I tend to agree.
However it is worth noting that there are some libraries in the Clojure
ecosystem e.g. Om and stuartsierra/component that do expect users to
interact directly with protocols as part of the public API. So this doesn't
seem to be yet adopted as a universal rule.
On Sunday, 28
Hi!
If I understand correctly... consider something like the following:
(let [log (d/log (db/conn))
my-tx 123456789123456]
(- (d/tx-range log my-tx (inc my-tx))
seq
pprint))
You get a bunch of datoms and transaction ID.
You can access a datom's fields with: :e :a :v :tx
This is cool. Kind of makes me wish my sparse matrices were larger than
300x300. I'll experiment with it anyway.
On Saturday, December 27, 2014 4:56:55 AM UTC-5, Mike Anderson wrote:
Here is a little belated Christmas present for Clojure data aficionados:
;; setup
(use
Thanks,
that helped a lot.
Regards
Roger
--
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
Hi,
it seems as if there is a test package for vertx and Clojure
(vertx.testools)
Since I would like to test my vertices I tried this simple approach:
(tt/as-embedded (fn []
(core/deploy-verticle project/vertices/time.clj)
(tt/test-complete*)))
But this gives me a timeout.
BTW: The
You're overlooking the fact that a service provider interface is simply
enterprise design pattern jargon for a subset of public APIs that expose
the underlying interfaces of the library to consumers. Saying that Rich is
saying protocols should never ever be part of the public API is both
On Sun, Dec 28, 2014 at 9:52 AM, rogergl ro...@gilliar.de wrote:
it seems as if there is a test package for vertx and Clojure
(vertx.testools)
Since I would like to test my vertices I tried this simple approach:
(tt/as-embedded (fn []
(core/deploy-verticle project/vertices/time.clj)
@Chris Thanks, hope it's useful for you. I might have a play with ggvis and
see how it works out.
@Mike Yeah, it would definitely be good to support core.matrix datasets.
One thing that would be nice would be to avoid the overhead of loading all
of core.matrix for those that don't use it. Do
I think I'm getting close. The eventbus_test.clj
https://github.com/vert-x/mod-lang-clojure/blob/master/api/src/test/clojure/vertx/eventbus_test.clj
runs
and I changed my test to:
(deftest eb-send
(core/deploy-verticle /project/vertices/time.clj)
(let [addr const/topic-time
id
I was not implying anything about what Rich have said. While the SPI term
may be used in the 'enterprise' field too much (and in an unnecessary
complicated manner), I think it has perfectly valid uses in Clojure. The
API tells you what a function or a macro does for you, but SPI tells you
what
Maybe it is a better solution to put the code I wan't to test outside the
vertices and just leave the basic eventbus setup insides the vertices ?
Regards
Rpger
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
Glad to see the addition of new-sparse-array to core.matrix. It looks like
it defaults to SparseRowMatrix for the Vectorz implementation? Should the
API provide a way to specify which sparse matrix representation (e.g., row-
vs column-based, indexed vs hashed) should be used? I'd suggest a
Apologies for resurrecting the thread but I wanted to add a link to a
minimalistic example that reproduces the issue, if anybody comes across it:
https://github.com/frankiesardo/annotation-processing
On Friday, December 12, 2014 7:46:07 PM UTC, Frankie Sardo wrote:
Hi all,
I'd like to use
Interesting idea. The challenge is that I'm not sure how to add
representation specification in an implementation independent way. It's a
quirk of vectorz that it has both indexed and hashed storage, I probably
wouldn't expect any other implementations to have that. Likewise row and
column
On Dec 28, 2014, at 7:28 PM, Mike Anderson mike.r.anderson...@gmail.com
wrote:
Interesting idea. The challenge is that I'm not sure how to add
representation specification in an implementation independent way. It's a
quirk of vectorz that it has both indexed and hashed storage, I
Looks like you have some good changes in your Vectorz branch - any chance
you could tidy up and make a PR?
I like the idea of specialised getSlices and getColumns in particular -
these should be much faster than getting the slices one-by-one if the data
is very sparse.
On Monday, 29 December
core.matrix isn't that big of a dependency itself - it only gets expensive
in/when you load the implementations (NDArray, vectorz-clj, Clatrix etc.).
Which should be a choice of the ultimate user.
It is possible to just depend on the protocols, but I think that risks
breakage since protocols
Cool, I'll give your fork a try. I've been using lein-shell to just run sassc
directly, but it's annoying because sassc bombs if the target folder doesn't
exist.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
18 matches
Mail list logo
