Re: [ANN] tawny-owl 0.11

Thank you for adding this. I've added some text to my README, so that the next release will have more information. As I have said, in another reply, Clojure developers are not my primary audience; this seems like a reasonable excuse for early versions, but is much less plausible now I approach a 1

Re: Defining the ground truth

On every project I've ever worked on, specs were ephemera, falling out of date almost immediately despite occasional herculean efforts to keep them up-to-date. Personally, the best answer I've found to the spec/code dilemma to be automated tests, as they evolve along with the code and fail if they

Real-world Clojure application

Hello, can anyone give a hint on real-world Clojure application? I would like to compare applications written in different dynamic JVM languages with respect to different JVM characteristics. Usually this kind of things are done by means of benchmarking, however, no benchmarking suite exists

Re: Real-world Clojure application

One of the applications that might be comparable are web apps / frameworks. They can be configured relatively easily to give deterministic results (html /json) on arguably comparable input (http request). There's already an existing benchmark site

Re: How to: reduce boolean operations?

Whether (false 1) or (false true) is truthy is irrelevant. What matters is that false returns truthy values when called with any members of [], which is of course the case, as [] has no members. (For it not to be the case, there would have to exist an x in [] for which (false x) were not truthy --

Re: How to: reduce boolean operations?

when you say the word "false" I'm assuming you're referring to "false?" the function (not "false" the boolean value), otherwise I don't understand so like: "What matters is that *false?* returns truthy values when called with any members of []" makes sense to me. So all I was saying above is that

Re: How to: reduce boolean operations?

On Thu, May 23, 2013 at 11:30 AM, atkaaz wrote: > So all I was saying above is that it should throw when [] is empty just as > it does when [] is not empty, but it doesn't throw when empty because it's > never called (by "it" i mean "false" not "false?") > This sort of behavior is handy for user

Re: How to: reduce boolean operations?

A while back I saw some java slides that elude me now, they mentioned approaches to safety like defensive copying, immutability, etc.. their conclusion at the end, that I seem to remember, was it only really made sense to validate user input, a sort of wall, where anything past the wall is assumed

Re: How to: reduce boolean operations?

On 23 May 2013 18:30, atkaaz wrote: > when you say the word "false" I'm assuming you're referring to "false?" the > function (not "false" the boolean value), otherwise I don't understand I mean false-the-Boolean-value. To rephrase the point I was making previously, "(false x) is a truthy value f

Re: How to: reduce boolean operations?

At this moment after reading again this thread, I lost my sense of what false and true mean :) I'll now stick with maybe, it's much clearer... Luc P. > On 23 May 2013 18:30, atkaaz wrote: > > when you say the word "false" I'm assuming you're referring to "false?" the > > function (not "false"

Re: Time complexity of operations on collections

http://www.innoq.com/blog/st/2010/04/clojure_performance_guarantees.html -- -- 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 patie

Re: Real-world Clojure application

The trouble is, so much depends on the problem space. For example, my team is building a "real world" clojure application - mostly data transformation and routing - but in the "real world" the actual speed of clojure execution is fairly insignificant compared to I/O. You could extract just the dat

Re: Time complexity of operations on collections

Exactly what I was looking for, thanks!!! John On Thursday, May 23, 2013 7:06:39 PM UTC-5, Matthew wrote: > > http://www.innoq.com/blog/st/2010/04/clojure_performance_guarantees.html > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to t

Re: How to: reduce boolean operations?

Firstly let me just say that I really enjoy this conversation, ergo I thank you! On Thu, May 23, 2013 at 9:00 PM, Michał Marczyk wrote: > On 23 May 2013 18:30, atkaaz wrote: > > when you say the word "false" I'm assuming you're referring to "false?" > the > > function (not "false" the boolean v