undefined | Better HN

0 pointsNullabillity4y ago0 comments

True, but Loom won't really help you there since that already CompletableFuture.runAsync already uses a pooling scheduler. Same for cats-effect and zio, for that matter.

(And that's aside from CompletableFuture having its own separate problems, like the obtrude methods)

0 comments

derefr4y ago

> already uses a pooling scheduler

A bounded pooling scheduler. (The ForkJoinPool.commonPool.)

Loom, I believe, "dummies out" the ForkJoinPool.commonPool — ForkJoinTasks/CompletableFutures/etc. by default just execute on Loom's unbounded virtual-thread executor.

(Which happens to be built on top of a ForkJoinPool, because it's a good scheduler. Don't fix what ain't broke.)

j / k navigate · click thread line to collapse

0 comments

derefr4y ago

> already uses a pooling scheduler

A bounded pooling scheduler. (The ForkJoinPool.commonPool.)

Loom, I believe, "dummies out" the ForkJoinPool.commonPool — ForkJoinTasks/CompletableFutures/etc. by default just execute on Loom's unbounded virtual-thread executor.

(Which happens to be built on top of a ForkJoinPool, because it's a good scheduler. Don't fix what ain't broke.)

j / k navigate · click thread line to collapse