Léo NOEL

That makes sense. `get-value` is a blocking call therefore it's wrong to call it directly from `m/sp`, and the error message should explain that. The right fix is to turn...

Your implementation is compliant with the task protocol, some remarks though : * check `Throwable` instead of `Exception` (`some?` works too, as it's impossible to throw `null` on the JVM)...

I have reworked the page and also added more examples, including the core.async helper we discussed with @mjmeintjes.

The point is that you can write asynchronous logic the exact same way you would have written synchronous logic. A synchronous solution could use e.g `java.util.function.Supplier` to represent a job...

I'm not sure to understand which part was not clear to you. The difference between the missionary solution and the supplier solution is the former is non-blocking and the latter...

Thank you for this clarification. There's a lot of room for improvement for these topics in the current state of documentation, and I'm planning to write more of it before...

I think your mental model about tasks is the right one. Some remarks about your implementation of join : * it returns results in the order they're available, instead of...

There's a big difference between active polling (repeatedly checking some condition in a loop) and waiting for a value on a queue or a future. In the former case, the...

It may improve efficiency, but still considered a bad practice. The general recommendation is to leverage `java.util.concurrent` facilities, and refrain to use low-level thread machinery unless there's a good reason...

Another feature that is missing in your join implementation is the ability to react to thread interruption. When a join is interrupted, it must propagate the interruption signal to all...