http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/NREPL-17 tools.nrepl <p>We talked about this briefly on IRC/github: <a href="https://github.com/overtone/overtone/issues/85">https://github.com/overtone/overtone/issues/85</a>. I guess the nicest way to fix it would be to stop using agents in nREPL. There's only one spot where agents are created, and a few send-off calls (no sends), all internal, so any solution will be non-intrusive from an API perspective.</p> <p>One implementation idea is to use a simple blocking queue and thread pool in java-land.</p> <p>Another is to use nearly the same implementation as Agent, but remove the nesting restriction (call it NestableAgent?). Also get rid of the STM interaction and validator business since those aren't available outside the clojure.lang package <img class="emoticon" src="http://dev.clojure.org/jira/images/icons/emoticons/sad.gif" height="20" width="20" align="absmiddle" alt="" border="0"/> - and then provide a parallel version of send-off. I've spiked a bit on this one, but I'm starting to think a plain queue/thread pool is cleaner.</p> <p>Thoughts?</p> NREPL-17

Agent nesting causes issues

Defect Blocker Closed Completed Chas Emerick Colin Jones Fri, 13 Apr 2012 00:11:34 -0500 Mon, 16 Apr 2012 15:08:50 -0500 Mon, 16 Apr 2012 15:08:50 -0500 0.2.0 0 0 <p>Yes, I started working on this yesterday. Agents have definitely proven themselves unsuitable here, and a poor choice.</p> <p>I'm not going to be fancy; we don't need fancy here.</p> <p>Great news! Thanks for the quick response.</p> <p>Fixed in <tt>0.2.0-beta6</tt>.</p> Global Rank