Re: Why does interruptible-eval from tools.nrepl queue evaluations?

By channel you mean sessions right? That's a simple way to circumvent the serialized nature of evaluations - you can just spin a new session for each evaluation. Never benchmarked what's the overhead of this, though. On 4 May 2018 at 00:36, Gary Fredericks wrote: > I

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

I used the hacky tactic of just sending messages through the nrepl channels (while the eval is blocked) to implement this: https://github.com/gfredericks/debug-repl Gary Fredericks (803)-295-0195 fredericksg...@gmail.com gfredericks.com On Thu, May 3, 2018 at 4:31 PM, Carlo Zancanaro

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

On Thu, May 03 2018, Gary Fredericks wrote: Separately, I use this macro for running background things in the repl. It probably targets different concerns, but seems related at least. My use case is quite different. Requiring someone to decide

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

Separately, I use this macro for running background things in the repl. It probably targets different concerns, but seems related at least. Gary Fredericks (803)-295-0195 fredericksg...@gmail.com gfredericks.com On Thu, May 3, 2018 at 8:01 AM, Carlo

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

Apologies, I forgot to cc the list. On Thu, May 03 2018, Gary Fredericks wrote: You would also have race conditions on the meaning of *1, *2, *3, and *e. On Thu, May 3, 2018 at 5:43 AM, Carlo Zancanaro wrote: >But what happens when a user set!s a var? is it

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

But what happens when a user set!s a var? is it effective for all future evals but not the concurrent ones? On Wed, May 2, 2018 at 8:35 PM, Carlo Zancanaro wrote: > > > >I think dynamic vars in particular would be problematic. The repl is > built around being able to

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

>I think dynamic vars in particular would be problematic. The repl is built >around being able to set! certain vars, and you can't do that to the same >binding from multiple threads. The dynamic thread bindings are established within the function passed to queue-eval, though, so it seems

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

I think dynamic vars in particular would be problematic. The repl is built around being able to set! certain vars, and you can't do that to the same binding from multiple threads. On Wednesday, May 2, 2018 at 5:48:46 AM UTC-5, Carlo Zancanaro wrote: > > Hey there! > > With tools.nrepl, if you

Re: Why does interruptible-eval from tools.nrepl queue evaluations?

I suspect it's because queuing up operations is a relatively safe increment in convenience over the most naive implementation: having to wait for each evaluation to complete before submitting the next. Attempting to increasing the convenience further by evaluating expressions in parallel