of the JAR file and confirmed that it is not in there.
All the documentation that I read seems to indicate that duck-streams
is not deprecated.
Thanks for any help,
Neal
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this gro
Stu,
Good book!
It was pretty clear to me that it was a snapshot. It was really a
user error on my part. Now that I have made that error, I won't make
it again.
Thanks,
Neal
On Apr 21, 9:31 am, Stuart Halloway wrote:
> The second level header tells you the branch (e.g. master)
Alex,
Yes. I was using the snapshot. My bad.
Neal
On Apr 21, 8:11 am, Alex Osborne wrote:
> Hi Neal,
>
> Neal writes:
> > I'm trying to use duck-streams, but it is missing from the clojure-
> > contrib JAR file (at least in build #81). I have listed the conten
OK. Thanks everyone for your help.
Neal
On Apr 21, 8:11 am, Alex Osborne wrote:
> Hi Neal,
>
> Neal writes:
> > I'm trying to use duck-streams, but it is missing from the clojure-
> > contrib JAR file (at least in build #81). I have listed the contents
> > of
> Is there a way to do something similar with a more general definition of
a path?
The lens library Fresnel (https://github.com/ckirkendall/fresnel) might be
worth a look - it abstracts
get-in/assoc-in into lenses which can store/retrieve state from complex
structures (and can be composed).
Nice!
This looks really useful - and beautiful too!
Figuring out what is going on in (and optimising performance of) a complex
UI
can get really difficult so it's great to see things like this that can
help.
Thanks for your work :)
On Thursday, October 26, 2017 at 4:31:53 PM UTC+1, Saskia L
This library looks great!
I've always liked ClojureQL much more than the other Clojure SQL libraries,
exactly for its emphasis on composability
and relational algebra.
At first looks - your library looks like it will be easier to extend for
different database servers...
I'd be interested in k
Sounds good!
I've been having a go with it today in a data-migration thing and I like
it. It feels very like clojureql but as you said, it fails earlier with
ambiguous queries, which definitely makes debugging easier.
One other difference I did notice with clojureql is that in clojureql the
d
https://plus.google.com/u/0/102817588588027389796/
--
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.
Hello,
I'm reading /Clojure in Action/, and I'm confused by one of the
examples. I'm hoping someone can clarify it for me. :-)
The author gives an example of an assertion macro:
(defmacro assert-true [test-expr]
(let [[operator lhs rhs] test-expr]
`(let [lhsv# ~lhs rhsv# ~rhs ret# ~test-e
Macro expansion time is not run time, is it? Thanks. :-)
On Jan 8, 2:59 pm, Michael Fogus wrote:
> The names in the first let only exist at compile time and do not exist when
> the expanded form eventually runs.
--
You received this message because you are subscribed to the Google
Groups "Clo
11 matches
Mail list logo
