Re: seq? empty? and every?

2012-12-26 Thread Baishampayan Ghose
>>> user=> (seq? []) >>> false A vector is not a seq [though it's seq-able]. >>> user=> (empty? []) >>> true An empty vector is indeed empty. >>> user=> (every? seq? []) >>> true >>> >>> user=> (every? empty? []) >>> true every? with any predicate over an empty sequence/collection always retur

seq? empty? and every?

2012-12-26 Thread Peter West
> > user=> (seq? []) > > false > > user=> (empty? []) > > true > > user=> (every? seq? []) > > true > > user=> (every? empty? []) > > true > > user=> > > Can someone explain this to me? (1.4) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post

Re: Merry Christmas Everybody

2012-12-26 Thread Peter West
And me (belatedly). Well, there are twelve days of Christmas! On Wednesday, 26 December 2012 19:27:35 UTC+10, Matthew wrote: > > Merry Christmas from me too! > > (source ) > -- You received this message because you are subscribed to

Re: Writing a simple nrepl middleware and client

2012-12-26 Thread jaime
It looks like your connection is broken somehow, this might be caused by an OS level issue(firewall etc.) but not the application itself. To test if this is due to an OS level issue, I suggest you to try connect nREPL by telnet, here's how to start nREPL in a TTY mode, in any REPL session type

Re: list* not returning a list

2012-12-26 Thread Tom Jack
A small bug in ClojureScript was related to this: https://github.com/clojure/clojurescript/commit/88b36c177ebd1bb49dbd874a9d13652fd1de4027 It looks like the only thing missing to make Cons implement IPersistentList is IPersistentStack. Why not implement it? On Wednesday, December 26, 2012 4:13:

methods of a protocol

2012-12-26 Thread Sunil S Nandihalli
Hi Everybody, It looks like the following way of definition is not allowed.. what is a good alternative way of doing this (defprotocol symbolicExpr (evalx [this args])) (let [y #(+ 1 2)] (deftype x [a] symbolicExpr (evalx [this args] (y I know I can do a (def y #

Re: list* not returning a list

2012-12-26 Thread Ben Wolfson
On Wed, Dec 26, 2012 at 2:07 PM, Stephen Compall wrote: > On Wed, 2012-12-26 at 12:35 -0800, Marek Šrank wrote: >> ...however, its docstring says: "Creates a new list containing the items >> prepended to the rest, the last of which will be treated as a sequence." > > List is almost always colloqui

Re: list* not returning a list

2012-12-26 Thread Stephen Compall
On Wed, 2012-12-26 at 12:35 -0800, Marek Šrank wrote: > ...however, its docstring says: "Creates a new list containing the items > prepended to the rest, the last of which will be treated as a sequence." List is almost always colloquial, not literally IPersistentList. I would be in favor of elim

list* not returning a list

2012-12-26 Thread Marek Šrank
function list* doesn't return a list, because it uses 'cons' under the hood: (list? (list* 1 2 3 '())) ;=> false (class (list* 1 2 3 '())) ;=> clojure.lang.Cons ...however, its docstring says: "Creates a new list containing the items prepended to the rest, the last of which will be treated as a

Re: Misleading ArityException error string

2012-12-26 Thread Vladimir Tsichevski
Thanx! On Wednesday, December 26, 2012 6:49:36 PM UTC+4, Andy Fingerhut wrote: > > Timothy Baldridge wrote a patch to improve this issue and attached it to > CLJ-1083: > > http://dev.clojure.org/jira/browse/CLJ-1083 > > Andy > > On Dec 26, 2012, at 3:20 AM, Vladimir Tsichevski wrote: > > Hi,

[ANN] Slamhound 1.3.0

2012-12-26 Thread Phil Hagelberg
Hello folks. Last night I pushed a new release of Slamhound, the ns-rewriting tool. This version has a few notable new features courtesy of Alex Baranosky: 0) It no longer recommends :use for referring vars but uses the new :require/:refer notation for Clojure 1.4. 1) It no longer requires that

Re: New Clojurescript Project: browsing the web collectively.

2012-12-26 Thread eduardoejp
Looks awesome, man. Finally someone gets "social" right. Good luck. -- 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 y

Re: Misleading ArityException error string

2012-12-26 Thread Andy Fingerhut
Timothy Baldridge wrote a patch to improve this issue and attached it to CLJ-1083: http://dev.clojure.org/jira/browse/CLJ-1083 Andy On Dec 26, 2012, at 3:20 AM, Vladimir Tsichevski wrote: > Hi, > > if the function name has characters, which are mangled by Clojure compiler, > and we pass

Re: Clojure 1.5.0 RC 1

2012-12-26 Thread Toby Crawley
I just pushed a new lein-swank release (1.4.5)[1] that should work with 1.5.0-RC1. Let me know if you have any issues with it. [1]: https://groups.google.com/d/topic/swank-clojure/WIrLw2NxuEs/discussion Jeff Dik writes: > On Sun, Dec 23, 2012 at 10:21 PM, Toby Crawley wrote: >> >> Jeff Dik writ

Misleading ArityException error string

2012-12-26 Thread Vladimir Tsichevski
Hi, if the function name has characters, which are mangled by Clojure compiler, and we pass to such function wrong number of argument, we got wrong error message. For example: (defn a->b [x] x) (a->b 1 2) produces: clojure.lang.ArityException: Wrong number of args (2) passed to: user$*a* at

Re: Merry Christmas Everybody

2012-12-26 Thread Matthew
Merry Christmas from me too! (source ) -- 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 m