After adding this, I still can't see an exception before the app dies.
maanantai 6. maaliskuuta 2017 12.04.16 UTC+2 JokkeB kirjoitti:
>
> Thanks for the reply.
>
> I haven't tried catching any or all errors. Is it a false assumption that
> an error should be logged if it comes from the main
Right, of course! It seems almost obvious now :P
Thanks Kevin
On Tuesday, March 7, 2017 at 12:42:08 AM UTC+1, red...@gmail.com wrote:
>
> On 03/06/2017 03:28 PM, juan.facorro wrote:
> > While I was debugging some code I found something related to the *loop
> > *macro that I found curious. I'm
On 03/06/2017 03:28 PM, juan.facorro wrote:
> While I was debugging some code I found something related to the *loop
> *macro that I found curious. I'm probably missing something but here it
> goes.
>
> The expression generated by the *loop* macro includes a wrapping *let
> *when there is any
While I was debugging some code I found something related to the *loop *macro
that I found curious. I'm probably missing something but here it goes.
The expression generated by the *loop* macro includes a wrapping *let *when
there is any de-structuring in the bindings.
(require '[clojure.walk
Moe: Good point. The specific use case I had was that I wanted to be able
to extract all the values that were on a path—in other words the ability to
use a wildcard in get-in. For example, this returns "X1". I would like to
use get-in to return ["X1" "X2"]. In other words use a wildcard for :b1.
On Monday, March 6, 2017 at 10:33:43 AM UTC-6, Mars0i wrote:
>
> On Monday, March 6, 2017 at 9:32:37 AM UTC-6, Alex Miller wrote:
>>
>> Ok, this looks like it's related to the macro gen, so I don't see any
>> issue to fix in the spec - valid inputs at the point are either strings or
>> symbols -
On Monday, March 6, 2017 at 9:32:37 AM UTC-6, Alex Miller wrote:
>
> Ok, this looks like it's related to the macro gen, so I don't see any
> issue to fix in the spec - valid inputs at the point are either strings or
> symbols - I think through eval you were ending up with a class instance.
>
Ok, this looks like it's related to the macro gen, so I don't see any issue
to fix in the spec - valid inputs at the point are either strings or
symbols - I think through eval you were ending up with a class instance.
On Monday, March 6, 2017 at 1:16:38 AM UTC-6, Mars0i wrote:
>
>
>
> On
On Monday, March 6, 2017 at 1:16:38 AM UTC-6, Mars0i wrote:
>
>
> On Sunday, March 5, 2017 at 6:51:57 PM UTC-6, Alex Miller wrote:
>>
>> I would really appreciate seeing the ns declaration that caused the
>> original error. I have not been able to exactly reproduce what you are
>> describing.
For a lecture I have implemented the write-skew example from Mark
Volkmann's article:
(defn write-skew []
(let [cats (ref 1)
dogs (ref 1)
john (future
(dosync
(when (< (+ @cats @dogs) 3)
(alter cats inc
mary
Thanks for the reply.
I haven't tried catching any or all errors. Is it a false assumption that
an error should be logged if it comes from the main thread? Can an
exception in another thread kill the app? Anyways, I now added this piece
of code in main, like instructed
in
We are pleased to announce that Google has selected Clojure as a mentoring
organisation for this year’s summer of code! This means that Google will
sponsor students from around the world to work on projects that are part of
the Clojure ecosystem. Now that we know that Clojure will be
On Friday, March 3, 2017 at 7:36:27 AM UTC-6, Maitreya Verma wrote:
>
> Hello,
> I am Maitreya Verma, second year undergrad student.
> I am very enthusiastic to work on the idea of adding cool features to
> KLIPSE for GSoC. There are many other ideas which I think can be
> implemented on
However, it does mean that libraries depending on 1.9 may be waiting to
release so as not to support a Clojure version that can make breaking
changes to the new features at any time.
On Mon, Mar 6, 2017 at 12:41 AM, Alexander Kiel
wrote:
> We also run Clojure 1.9-alpha
We also run Clojure 1.9-alpha with great success in production. Being alpha
doesn't mean that it's buggy. It just means that the new stuff can still
change.
Am Dienstag, 28. Februar 2017 21:10:59 UTC+1 schrieb Dan Burton:
>
> Obligatory: "our team uses clojure-future-spec with clojure-1.8" --
15 matches
Mail list logo