> means that you can just use :keyword instead of #(get % :keyword) in
> cases where you provide a function as an argument (for example: (map
> :type objects)).
>
> On 16 September 2015 at 14:20, Michael O'Keefe > wrote:
>
>> Hello All:
>>
>> Noticed the foll
d something (feel free to point me in the right
direction).
Is it just a "quirk" or is it useful in some way? Intended behavior or bug?
Cheers,
Michael O'Keefe
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to t
Awesome! Very much appreciated!
Michael
On Monday, August 25, 2014 12:15:51 AM UTC-6, Mikera wrote:
>
> Hi All,
>
> Prasant and Aleksandr have been working all summer making Clojure even
> better for data science / numerical computing. On behalf of myself and my
> co-mentor Alex Ott I want to o
Awesome job, everyone! You guys rock!
Michael
On Saturday, July 26, 2014 3:09:56 PM UTC-6, miner wrote:
>
> I tried the latest patch from Ambrose for CLJ-1475. Looks good to me.
> Well done.
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To
Nice work everyone on the patches -- I'm very impressed!
There's been a couple of questions about how to interpret this. My thought
is we should try and mimic an explicit recursion:
In other words:
(defn g
[xs acc]
{:pre [(or (nil? xs) (sequential? xs)) (number? acc)]
:post [(number? %)]
on the termination of the
>> loop, or when the recur form is not conditionally present in the
>> expression, then you are essentially asking the impossible for the
>> compiler: it cannot know your intentions better than you do.
>>
>>
>> On Friday, July 25, 201
Thanks Bob, Steve, and Andy. I was trying to get logged into JIRA to file
the bug report but I seem to be having a heck of a time -- I have a CA and
am signed up at dev.clojure.org but when I try to log into JIRA, it gives
me a nice "System Error" saying " user should not be null!". I've run out
Ambrose, thanks -- I was NOT aware of that. Sorry I misunderstood your
original.
Andy, good advice and I agree. Thanks. I'll think on it then.
Cheers,
Michael
On Thursday, July 24, 2014 10:20:57 PM UTC-6, Ambrose Bonnaire-Sergeant
wrote:
>
> On Fri, Jul 25, 2014 at 12:13 PM, Mich
Ambrose
>
>
> On Fri, Jul 25, 2014 at 6:56 AM, Michael O'Keefe > wrote:
>
>> Hello All,
>>
>> I encountered the following behavior in Clojure 1.6 and wanted to check
>> if it should be considered a bug or not. I would say yes but wanted to
>>
s) acc)
Thanks,
Michael O'Keefe
--
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.
Thank you for all you do. This is wonderful!
-Michael O'Keefe
On Tuesday, June 10, 2014 6:49:52 AM UTC-6, Tim Visher wrote:
>
> (boom)
>
> On Mon, Jun 9, 2014 at 1:23 PM, Alex Miller > wrote:
> > Starting today, we have updated the Clojure Contributor Agreement
me to really think
about my design decisions.
Anyhow, just wanted to thank you for your inspirational words and I'm
excited to check out your video.
Sincerely,
Michael O'Keefe
On Wednesday, February 1, 2012 5:51:53 AM UTC-7, daly wrote:
>
> On Wed, 2012-02-01 at 10:43 +00
12 matches
Mail list logo
