[NREPL-4] Provide sane multiplexing of output in the face of multithreaded, asynchronous operation Created: 30/Sep/11 Updated: 12/Nov/14
|Reporter:||Chas Emerick||Assignee:||Chas Emerick|
Basically, (send-off some-agent println) & co. should get what's printed to out in that agent's thread back to the nREPL client — not silently let it dump out to System/out.
Portal ostensibly does this well. Examine their approach, see if it is compatible with nREPL's objectives.
Ill-formed brain dump:
|Comment by Federico Ragona [ 12/Nov/14 1:59 PM ]|
Seems to be fixed, I was unable to reproduce the issue using
REPL-y 0.3.5, nREPL 0.2.6
Should this issue be closed?