q after the first two hard-coded values, and it worked.
What happens when you put it after just the first hard-coded value? Can you
explain why?
(def fibs (cons 0 (lazy-seq (cons 1 (map +' fibs (rest fibs))
-- Dan Burton
On Mon, Sep 4, 2017 at 5:33 PM, mrwizard82d1 wrote:
> I
This design is surprising to me. If this is the case, then I don't
understand the point of `:opt` for s/keys.
-- Dan Burton
On Wed, Jun 28, 2017 at 2:17 AM, Max Penet wrote:
> Hi,
>
> It's by design, as the doc of s/keys states:
>
> In addition, the values of *all*
Obligatory: "our team uses clojure-future-spec with clojure-1.8" -- no
problems so far.
-- Dan Burton
On Tue, Feb 28, 2017 at 11:59 AM, Sean Corfield wrote:
> On 2/28/17, 10:26 AM, "Erik Assum" e...@assum.net> wrote:
> > And, yes, I'm aware of the fact th
Note that when Haskell.org didn't make it into gsoc last year, they
successfully organized a similar program through private donations. While
one hopes that Clojure will be accepted into gsoc, consider having a
similar course of action as Plan B.
-- Dan Burton
On Thu, Feb 2, 2017 at 10:
ng pushed for Clojure 1.9! Nice work.
-- Dan Burton
On Tue, Aug 9, 2016 at 1:49 PM, Alex Miller wrote:
> There are really two aspects to this - one is actually including the
> metadata in core.async, which can definitely be done.
>
> The second is adding functionality to Clojure c
gt;
>>
>>
>>
>>
>> --
> 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 pat
cljs,
and gotten-obj is js/Object. Thus, you can write cljc macros that
symbolically refer to obj/obj and turn out as the correct thing. This is
because the macro doesn't refer to the *value* of obj, just to the symbol,
which isn't evaluated until runtime.
-- Dan Burton
On Fri, May 20,
true
...) and it still behaves this way. It might seem unexpected or undesirable
that it runs the "catch" branch, but it does seem like a good idea to let a
future-try/catch block clean up after itself. /shrug
-- Dan Burton
On Fri, Apr 29, 2016 at 6:26 PM, Dan Burton
wrote:
>
re-cancel thread#))
(throw e#)
Try running (def f2 (test-f2 11)) with that future-try, and it goes crazy.
After waiting 5 seconds, it spews out numbers up to around 2031, then stops
because (second f2) wasn't able to allocate any more threads. I have no
explanation for this.
same technique
probably works.
A simpler technique in this case would be to only catch the kinds of
exceptions that you expect the inner block to throw, rather than "catching
all exceptions" with (catch Exception e ...).
-- Dan Burton
On Fri, Apr 29, 2016 at 6:35 AM, Ashish Negi
wrote:
lojure+unsubscr...@googlegroups.com
>
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and st
11 matches
Mail list logo
