Re: Using gen-class to generate methods with same names and arities but different type signatures

Hi, The problem may be come from the name of the class. Do you try to change the name of your class? For example, replace Class by Foo or another word. I'm not sure it's the correct answer :$ 2012/8/2 David Greenberg : > Hi Clojurians, > I'm finding myself far down the rabbit hole of gen-class.

Re: What concurrency models to document?

I think that you have to talk about concurrency! It is on everyone's mind. I would like to see the discussion go further than what I have seen in most other Clojure books. If you are REALLY interested in concurrency, you are probably interested in looking at using more than one node in a clu

Using gen-class to generate methods with same names and arities but different type signatures

Don't have an answer but I would sure enjoy hearing the group's wisdom on this. -- 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 p

Using gen-class to generate methods with same names and arities but different type signatures

Hi Clojurians, I'm finding myself far down the rabbit hole of gen-class. I am trying to generate a class that has a bunch of static methods, and each of those methods has many overloads of arities and types. Unfortunately, there is no interface--this class gets called through reflection in a legacy

Re: What concurrency models to document?

Adding my two cents: I'd say immutablity, transactions/refs, futures, and actors. I'd also talk a lot about what I call the "four horsemen of the parallel apocalypse"- race conditions, deadlocks, live locks, and priority inversions. These are all bugs that, while they *can* show up in senquentia

Re: What concurrency models to document?

Brian Marick writes: > Which raises the question: *is* concurrency actually a strong selling > point for functional languages? It definitely was/is for me. I'd avoided threads for most of my career-to-date because in imperative languages any thread could mutate any value to be anything at any p

Re: What concurrency models to document?

> > > You have to put quite a bit of thought in to get things right. > > Which raises the question: *is* concurrency actually a strong selling > point for functional languages? > > Yes, but I would question the concept of "free". I would sell the concurrency features thusly: 1) Assert that functio

Re: What concurrency models to document?

On 8/2/12 10:04 AM, Brian Marick wrote: On Aug 2, 2012, at 8:50 AM, Meikel Brandmeyer (kotarak) wrote: You have to put quite a bit of thought in to get things right. Which raises the question: *is* concurrency actually a strong selling point for functional languages? Sane defaults are a sel

Re: What concurrency models to document?

I don't find it to be one of the reasons I use Clojure... Nor do I find it significantly easier than other options I've used in the past (e.g. Java + Jetlang) I feel like concurrency is the half-truth we tell to encourage borderline adopters or spark interest. I don't believe it's a motivating fac

Re: What concurrency models to document?

On Aug 2, 2012, at 8:50 AM, Meikel Brandmeyer (kotarak) wrote: > You have to put quite a bit of thought in to get things right. Which raises the question: *is* concurrency actually a strong selling point for functional languages? In last year's state of clojure survey [*], concurrency ranked

Re: What concurrency models to document?

Hi, I agree with the previous posters. Concurrency in Clojure is neither free nor automatic. You have to put quite a bit of thought in to get things right. I'm always reminded of the classic memoize discussion. Things like futures or promis

Re: What concurrency models to document?

I find auto-concurrency in clojure to be misleadingly thrown around as free. I think a good description of what is free would be helpful, and examples of concurrency patterns that are still necessary above clojure data structures. A common example from my work is a screen that will need to display

core.logic 0.8-alpha1 is out

The list of changes is simply too long :) Please give it a shot. I'd like to make sure that it doesn't create problems for existing core.logic usage. Documentation on the new functionality forthcoming! David -- You received this message because you are subscribed to the Google Groups "Clojure"

clojurescript this reference inside functions

Hi All, I'm trying to use the google autocomplete widget in cljs and having problems converting the google basic example into cljs. This is the original: goog.ui.AutoComplete.Basic = function(data, input, opt_multi, opt_useSimilar) { var matcher = new goog.ui.AutoComplete.ArrayMatcher(data,