We’ve been running 1.9 prerelease builds in production from the first alpha. We
did not notice any performance changes from 1.8.
We’ve run prerelease builds of Clojure in production since the 1.3 days. It’s
always been stable enough to do that.
Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
schema.utils.NamedError does not look like a loading error; is there any chance
that could be an error thrown by the library? Are you positive "some string" is
a valid argument to validate-statement-data?
A cursory look at the README of xapi-schema seems to indicate that function
will throw an
If you require a namespace that requires another namespace, this will all
be resolved and loaded automatically as long as all the namespace files can
be found on the classpath.
I suspect that what you showed here is not the full error output, it seems
to be missing the information we would need to
Hi all,
I am totally new to Clojure. From Java I am trying to call a Clojure
function which belongs to a wider project and has dependencies. I have
compiled the Clojure project to an uber jar running lein uberjar, the
imported the jar into my Java project, and then did
IFn require = Clojure.va
I’ve upgraded several apps to 1.9 in production. The transition has been super
smooth, although some libs, amongst them core.async, have needed upgrades.
I have not seen any performance degradation, but then I haven’t been checking
for that.
Erik.
--
i farta
> 24. des. 2017 kl. 15:58 skrev
Clojure 1.9 has been out for a while, are there any companies updating to
Clojure 1.9 ? How is the performance compared to 1.8 ? Is the migration
smooth?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@go
