I could use some help getting "nrepl-ritz" working

Basically, I get a error when I try to follow the directions at http://ianeslick.com/2013/05/17/clojure-debugging-13-emacs-nrepl-and-ritz/ . In my init.el, I get a error when evaluating: *(require 'nrepl-ritz) ;;after (require 'nrepl)* the error is: *Debugger entered--Lisp error: (void-variable

API management in Clojure

Hi all, I'm curious about the options for managing APIs in Clojure code in a relatively idiomatic / consistent / functional way. The features I'm roughly interested in are: - ability to "wrap" a remote API in a regular Clojure function - abstraction away from the details of how the API is implem

Re: Type hints for clojure.set functions

If it's a case of prioritization, that makes sense. I was going to suggest raising a bug, and then triaging it as low priority, but I notice that there is already a declined JIRA issue. I apologize for not checking there before adding this thread. I'

Re: type checking clojure.set with core.typed

Heh, based on that my guess is that no one has used lein-typed in CI builds. :) I've submitted a PR to Ambrose to exit with a non-zero code when type checking fails: https://github.com/frenchy64/lein-typed/pull/1 Since lein-typed is brand new I imagine people have been writing there own tasks

Re: type checking clojure.set with core.typed

Any experience reports? My experience so far: Type Checker: Found 1 error $ echo $? 0 On Mon, Sep 30, 2013 at 7:20 PM, Ben Mabey wrote: > On 9/30/13 5:16 PM, Stuart Halloway wrote: > >> I tried the following experiment with type checking clojure.set: >> >> (ns exploring.core-typed >> (:us

Re: type checking clojure.set with core.typed

On 9/30/13 5:16 PM, Stuart Halloway wrote: I tried the following experiment with type checking clojure.set: (ns exploring.core-typed (:use clojure.core.typed clojure.repl) (:require [clojure.set :as set])) (ann ^:no-check clojure.set/difference [(Set Any) (Set Any) -> (Set Any)]) (set/diff

type checking clojure.set with core.typed

I tried the following experiment with type checking clojure.set: (ns exploring.core-typed (:use clojure.core.typed clojure.repl) (:require [clojure.set :as set])) (ann ^:no-check clojure.set/difference [(Set Any) (Set Any) -> (Set Any)]) (set/difference #{1 2} [1 2]) (comment (check-ns)

Re: Type hints for clojure.set functions

Hi splondike, I disagree with your arguments about what is sensible -- *any* behavior is sensible when you violate the contract of an API. Of course everybody could get behind the "throwing the error" plan if the cost of throwing that error was zero: zero assessment cost, zero development cost,

Re: 1.6 alpha?

You can also get regular SNAPSHOT builds of Clojure from the Sonatype OSS repository. Instructions here: http://dev.clojure.org/display/community/Maven+Settings+and+Repositories -S On Monday, September 30, 2013 5:00:17 PM UTC-4, Andy Fingerhut wrote: > > I am not aware of any 1.6 alpha/beta rel

Re: 1.6 alpha?

I am not aware of any 1.6 alpha/beta releases yet. There might have been one that I missed, but I watch fairly closely for such things. If you want to locally install the latest 1.6.0-master-SNAPSHOT version in your local Maven repository, you can do this: git clone git://github.com/clojure/cloj

1.6 alpha?

Hi, I'm pretty new to Clojure, but having a great time with it so far. I wanted to check out the 1.6 alphas, but the link on the Clojure downloads page doesn't return any results: http://clojure.org/downloads Can someone please point me to where I can find the 1.6 alpha releases? Ideally I'd l

[ANN] jvm.tools.analyzer 0.5.2

Hi, jvm.tools.analyzer 0.5.2 includes a small bug fix. Readme Changelog Thanks, Ambrose -- -- You received this message because you are subscribed to the Google Groups "Cloj

Re: Stretch Goal 1: CinC development

This is fantastic news. If anything, CinC is almost a more important project since its applications are so broad. I'm delighted to see the community getting behind both of these projects - congratulations Ambrose and Nicola! On 1 October 2013 07:02, Rich Morin wrote: > I am delighted that the c

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

Hi Dima! No it will not :) I can put an additional :stacktrace key in the issue if that suits you. On 30/09/2013, at 23:38, Dima Sabanin wrote: > Hi Chris, > > Thanks for your work on this! I've a new question though. Will the exceptions > raised with raise-on and raise-on-all preserve the

Re: Type hints for clojure.set functions

Thanks for the comment. The current behaviour is sensible for the code branch where the second argument is the same length or shorter than the first (see my first post). It is the other branch that does not do what you would expect. My real issue though is how the behaviour changes dramatically

Re: Crowdfunding for full-time core.typed development

Adam Bard has written an interesting blog post, comparing core.typed to Haskell: http://adambard.com/blog/core-typed-vs-haskell/ Both the post and the comments are worthwhile... -r -- http://www.cfcl.com/rdmRich Morin http://www.cfcl.com/rdm/resume r...@cfcl.com http://www.c

Re: Stretch Goal 1: CinC development

I am delighted that the campaign has been going so well. The fact that the Clojure community is willing to contribute to a project of this nature speaks very well for both its foresight and its pragmatic generosity. I'm also delighted at your adding a stretch goal that helps out another valuable

Re: Curious behaviour of 'frequencies'

In general, do not rely on the order of maps that are not explicitly sorted, and you will have fewer bugs in your code. In this particular case, the order that seq returns the pairs of the hash map is in an order dependent upon the hash values of the keys. For integers in the range [0, Integer/MA

Re: Stretch Goal 1: CinC development

When I think Clojure 2.0, I think of CinC. We need to support this project. If you've ever been jealous of the amazing compiler optimisations in Chez Scheme, or the metaprogramming facilities in Racket, CinC is a crucial step in that direction for Clojure. I'm very glad to have the opportunity to

Stretch Goal 1: CinC development

Given the amazing support shown by the clojure community, Ambrose's campaign has already raised its goal. As some of you might have noticed, yesterday Ambrose revealed the first stretch goal of his campaign and that is helping me continue develop CinC and I want to spend some time explaining wha

Re: Curious behaviour of 'frequencies'

Thanks BG. I recently obtained this knowledge of map implementations myself, either on this list or in a book. However, it's the *first* map that has sorted keys! That's the opposite of what we'd expect from your explanation, because the large map appears sorted while the small map is unsort

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

Hi Chris, Thanks for your work on this! I've a new question though. Will the exceptions raised with raise-on and raise-on-all preserve the cause exception? It'd be great if original cause was visible in the stack trace. Thanks, Dima On Mon, Sep 30, 2013 at 7:24 AM, Chris Zheng wrote: > No wor

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

No worries! I'll have a think about how to best go about it. My last attempt at a meet up was a bit of a failure =) On 30/09/2013, at 8:49 PM, Baishampayan Ghose wrote: > Hi Chris, > If you get the time, could you also write about the architecture of > ribol, its implementation details, etc. t

Re: Curious behaviour of 'frequencies'

Thanks for the correction, Shantanu. It's indeed 8, I was not sure of 32 anyway. ~BG On Mon, Sep 30, 2013 at 4:26 PM, Shantanu Kumar wrote: > Hi Gavin and BG, > > > On Monday, 30 September 2013 16:06:45 UTC+5:30, Baishampayan Ghose wrote: >> >> The second one is actually a PersistentArrayMap and

Re: Curious behaviour of 'frequencies'

Hi Gavin and BG, On Monday, 30 September 2013 16:06:45 UTC+5:30, Baishampayan Ghose wrote: > > The second one is actually a PersistentArrayMap and hence properties > that might indicate (falsely) that it's a sorted-map (aka > PersistentTreeMap). Clojure uses PersistentArrayMap for small maps as

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

Hi Chris, If you get the time, could you also write about the architecture of ribol, its implementation details, etc. too? That'd be immensely useful. ~BG On Mon, Sep 30, 2013 at 4:16 PM, zcaudate wrote: > > Thanks everybody for your feedback and suggestions on the last post. > > Version 0.3.1 h

[ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

Thanks everybody for your feedback and suggestions on the last post. Version 0.3.1 has the following updates: The `finally` clause is supported on `manage` - http://z.caudate.me/ribol/#finally as well as all the hook forms - http://z.caudate.me/ribol/#hooks `raise-on` and `raise-on-all` have

Re: Curious behaviour of 'frequencies'

The second one is actually a PersistentArrayMap and hence properties that might indicate (falsely) that it's a sorted-map (aka PersistentTreeMap). Clojure uses PersistentArrayMap for small maps as an optimisation and automatically promotes to PersistentHashMap when the number of items crosses a cer

Re: random name generator using adjective-animal combinations

Hey great to hear! Thanks for the feedback! Gruß Waldemar > Am 30.09.2013 um 11:52 schrieb Gavin Sinclair : > > Believe it or not, I just had a use for this (generating test strings). > Thanks! > > Gavin -- -- You received this message because you are subscribed to the Google Groups "Clo

Curious behaviour of 'frequencies'

I have a value 'y' in my REPL that is a sequence containing two sequences of numbers: (def y '( (15 18 17 17 16 19 16 10 21 16 21 23 19 16 18 15 21 14 21 12 26 17 13 22 26 16 14 17 11 15 16 18 13 10 18 18 19 13 14 17 19 18 15 20 20 17 20 19 12 20 14 21 13 17 15 22 17 21 13 15 16 17 14

Re: [ANN] 美味しいClojure

Fantastic! Congratulations on the great work. On Monday, September 30, 2013 4:43:59 PM UTC+10, Nicolas Modrzyk wrote: > > Hi Everyone, > > Myself and a friend have just finished a book related to the Clojure > ecosystem: > > http://www.amazon.co.jp/dp/4774159913 > > We are focusing not on the cor

Re: Parallelising over a lazy sequence - request for help

Sorry to jump in, but I thought it worthwhile to add a couple points; (sorry for being brief) 1. Reducers work fine with data much larger than memory, you just need to mmap() the data you're working with so Clojure thinks everything is in memory when it isn't. Reducer access is fairly sequential,

Re: random name generator using adjective-animal combinations

Believe it or not, I just had a use for this (generating test strings). Thanks! Gavin -- -- 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

[ANN] 美味しいClojure

Hi Everyone, Myself and a friend have just finished a book related to the Clojure ecosystem: http://www.amazon.co.jp/dp/4774159913 We are focusing not on the core language itself, although we do at times, but we focus on all the tools and the different frameworks that can help make a project