Other than spotting an issue with yada which involved upgrading aleph
(https://github.com/juxt/yada/issues/199) and an issue with ClojureScript
with was fixed on master I haven't encountered any problems. All our
integration tests pass. Good luck with bringing Clojure 1.9.0 out the door!
On Thu
boot-bundle now comes with unit tests and supports first class version
values:
https://github.com/borkdude/boot-bundle/blob/master/README.md#version-values
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email
Only a few lines of code, but it does the job:
https://github.com/borkdude/boot-bundle
This library lets you define a set of dependencies by a keyword. Details in
the README.
I found it especially useful in a multi-project repo where we use a lot of
the same dependencies in each project
I posted this call for contributors to Reddit. Maybe there are many people
like me there, who don't read this group regularly.
Anyway, it seems a fun idea. Count me in.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send em
I posted this call for contributors to Reddit. Maybe there are many people
like me there, who don't read this group regularly.
Anyway, it seems a fun idea. Count me in.
On Saturday, October 15, 2016 at 10:59:07 AM UTC+2, James Laver wrote:
>
> (bump)
>
> At the minute, including myself there ar
+1 for the feature to connect to an external nREPL session!
--
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
fir
I was playing around with 1.5-RC1 and stumbled unto this behavior:
https://www.refheap.com/paste/7817
Clojure lets me define a var which name contains a dot, but I can't
dereference it by name (because it is seen as a classname with a method or
field). Clojure shouldn't let me let define it in
I guess it wouldn't hurt having them available in the else, even if people
won't use them often.
On Monday, May 21, 2012 7:11:05 PM UTC+2, Aaron Cohen wrote:
>
> On Wed, May 16, 2012 at 9:53 AM, Walter Tetzner <
> robot.ninja.saus...@gmail.com> wrote:
>
>> On Wednesday, May 16, 2012 9:16:29 AM UT
Wow, the discussion continued!
I agree on what most people have said: AND-combined and none of the
bindings available in the else.
On Friday, May 18, 2012 7:20:06 AM UTC+2, FrankS wrote:
>
> Christophe Grand was "experimenting" with some extensions to if-let and
> when-let that had implicit AN
The docstring of if-let is as follows:
bindings => binding-form test
If test is true, evaluates then with binding-form bound to the value of
test, if not, yields else
I think it should be mentioned in the docs that if-let and when-let support
only *one binding*, not multiple bindings (like for
10 matches
Mail list logo
