Re: Running test.check and cljs.test tests under Clojurescript

Hi Nathan, I've been developing a small library to do exactly that: https://github.com/bensu/doo It's still alpha and doesn't support all Js targets but it will get there :) I haven't tried test.check for clojurescript yet, but if you run into trouble please post an issue since it should work

[ANN] `comidi`: a committee approach to defining HTTP routes

Hiya. We really like the syntax of compojure for defining HTTP routes, but have had some trouble with use cases where we'd really like to be able to introspect the route tree, and aren't able to do so because the nested functions are pretty opaque. After spending some time trying to workaround t

[ANN] trapperkeeper-metrics, trapperkeeper-status, et al

Howdy. Just wanted to send out some info about a few new services we've open-sourced for use with our Trapperkeeper service framework recently. trapperkeeper-metrics: https://github.com/puppetlabs/trapperkeeper-metrics This service manages configuration and life cycle of a MetricRegistry (from h

(flatten non-sequential) has a surprising result

Hello Clojurists, Today I was surprised by the result of (flatten 1) which is '(). I was expecting '(1) or an error. Talking in some other people in #clojure @ clojurians.net, not everybody agrees that '(1) is a good result but that '() is somewhat surprising. Would it be better if it raised an

Re: [ANN] `comidi`: a committee approach to defining HTTP routes

Regarding the "Whats next" in the README: *looking into swagger integration. I could swear I found some bidi-swagger bindings somewhere a while back, but am not finding them at the moment* Could you perhaps be thinking of the Yada swagger integration? http://yada.juxt.pro/user-guide.html#Swagger

Re: [ANN] Clojure 1.7.0 is now available

> > Congratulations to everyone involved and thank you for this great piece of > work! Regards, Andrea. -- 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

Re: How to exclude compile-time dependencies from uberjar?

All suggestions made the dependencies unavailable when running `lein uberjar` which means the project won't build :/ -- 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 ne

Re: (flatten non-sequential) has a surprising result

On Wednesday, 1 July 2015 12:55:28 UTC+1, J. Pablo Fernández wrote: > > Hello Clojurists, > > Today I was surprised by the result of (flatten 1) which is '(). I was > expecting '(1) or an error. Talking in some other people in #clojure @ > clojurians.net, not everybody agrees that '(1) is a good

Re: [ANN] `comidi`: a committee approach to defining HTTP routes

Chris, this is definitely interesting. Quickly pluggable metrics & swagger & trapperkeeper componentization sure are useful integrations. Doing a quick review, it surprised me a bit how many dependencies you brought into comidi [de

Re: (flatten non-sequential) has a surprising result

I agree with you Mikera, it also maintains the homogeneity of always returning a sequence but some people disagreed with it, so an error might be better. -- J. Pablo Fernández http://pupeno.com On Jul 1, 2015 4:22 PM, "Mikera" wrote: > On Wednesday, 1 July 2015 12:55:28 UTC+1, J. Pablo Fernánde

Re: Clojars Private/Commercial Repos

I like the idea of projars, both as private hosting and as a marketplace for commercial libs... again, my Datomic headaches influence my opinion, but if commercial/internal libs could just be lein deps, it'd remove an annoyance from my workflow. As for clojars, I get wanting to keep it simple. FWI

clojure.core.match: AssertionError: Pattern row reuses wildcards

Hi - I am trying to write some unit tests for Datomic using core.match to keep things succinct. I was hoping to use a match pattern like this: [ {:e tx-eid :a :db/txInstant:v _ :tx tx-eid :added true} {:e _ :a :community/category :v "free stuff" :tx tx-eid

Re: clojure.core.match: AssertionError: Pattern row reuses wildcards

Just isn't supported. Patch welcome :) David On Wed, Jul 1, 2015 at 3:46 PM, Alan Thompson wrote: > Hi - I am trying to write some unit tests for Datomic using core.match to > keep things succinct. I was hoping to use a match pattern like this: > > [ {:e tx-eid :a :db/txInstant:v

zipmap different ordering in 1.7

Hey, I when i tried to run my program with the shiny new 1.7, it broke. I have traced it down to the fact that zipmap ( https://github.com/clojure/clojure/blame/master/src/clj/clojure/core.clj#L2940) does returns the keys in a different order than i'm used to. e.g clojure 1.6: nREPL server sta

Re: zipmap different ordering in 1.7

Unsorted hash maps changed their seq order from Clojure 1.5.1 to Clojure 1.6.0, and some unsorted maps changed their seq order from Clojure 1.6.0 to Clojure 1.7.0. If you are relying on the seq order of unsorted maps, your program is at risk of breaking across Clojure versions. Andy On Wed, Jul

No matching field found: length for class byte array

If I do this: json-for-nlp (cheshire/generate-string map-for-nlp) byte-array-json (.getBytes json-for-nlp) I assume I now have an array of bytes. But if I do: (.length byte-array-json) I get: No matching field found: length for class Why is that? More info below.

No matching field found: length for class byte array

Length is kind of a fake field. Use the Clojure alength function. -- 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 you

Re: zipmap different ordering in 1.7

On Wednesday, July 1, 2015 at 3:54:03 PM UTC-4, Jo Geraerts wrote: > > Hey, > > I when i tried to run my program with the shiny new 1.7, it broke. I have > traced it down to the fact that zipmap ( > https://github.com/clojure/clojure/blame/master/src/clj/clojure/core.clj#L2940) > > does returns

No matching field found: length for class byte array

Yep you're in a cast of confused hundreds? thousands? here. It's quickly googlable but I'd still prefer to see my (rejected) humane suggestion in the error. While I don't advocate coding lessons in error messages, this really is an anomalous Java detail leaking through. user=> (.length (int-arr

Re: [ANN] Introducing Yagni, a Leiningen plugin for finding unused code

Hey Stuart - Could you clarify what you meant your comment? I'm not sure I understand what you mean by a pure function in this context. - David On Tue, Jun 30, 2015 at 8:10 AM, Stuart Halloway wrote: > Nice. > > It would be really cool if run-yagni was a pure function of source-paths > and ma

Re: [ANN] Introducing Yagni, a Leiningen plugin for finding unused code

I may be putting words in Stuart's mouth here, but what I believe he meant is that it would be great if Yagni were just a Clojure library with a function you could call passing it everything it needs (probably source paths and entry point details), and ideally returning the results as data. Then th

Re: How to exclude compile-time dependencies from uberjar?

Hi "provided" dependencies should work for you, this is from my project.clj : :profiles {:provided {:dependencies [[org.apache.storm/storm-core "0.9.4"]]}} On Wed, Jul 1, 2015 at 5:14 PM, Robin Heggelund Hansen wrote: > All suggestions made the dependencies unavailable when running `lein >

Re: zipmap different ordering in 1.7

That was exactly what i'm doing to fix it. I didnt care about the actual order but assumed the order was going to stay the same. Bad assumption. Thank you all for the feedback. Op donderdag 2 juli 2015 03:06:00 UTC+2 schreef Fluid Dynamics: > > On Wednesday, July 1, 2015 at 3:54:03 PM UTC-4, J

Re: (flatten non-sequential) has a surprising result

Hi Pablo, I think you're right. Have a look at flatten source (defn flatten "Takes any nested combination of sequential things (lists, vectors, etc.) and returns their contents as a single, flat sequence. (flatten nil) returns an empty sequence." {:added "1.2" :static true} [x] (fil