dokar3
dokar3
You can't have multithreaded JavaScript here, that's how it's designed. Running them simultaneously will break the runtime (stack overflows, async jobs, and results would make it a nightmare). If concurrency...
This is weird, if all calls happen on the same thread, you shouldn't have a chance to start another `evaluate` call when the jobs from the previous `evaluate` are still...
I kind of understand, do you mean using "evaluate" to create a promise but not using "await" on it and then doing the same thing? This is not currently possible...
Okay, I still didn't get it, Any sample code to elaborate on the `block`?
> But the first one blocks the second one, so the second one prints only after the first one prints. Okay, this is the expected behavior, right?
Sorry for the delay, do you mean managing multiple `evaluate` (and their event loop) in the same coroutine dispatcher?
I got your points, suspending is not blocking and we can 'await' multiple `evaluate` in a single thread dispatcher. However, managing multiple `evaluate` and their loop separately is not quite...
Great, would be glad to see that!
This is quite right, it does not cancel jobs if the parent job of `evaluate` cancels. Using "NonCancellable" is a bit of overkill in my opinion. Also, this may break...
I didn't see how canceling `evaluate` but it does not stop the JS execution making the cancellation cooperative, on the contrary, it makes "evaluate()" harder to cancel. IMO, canceling `evaluate`...