A new build and a new structured concurrency API

Ron Pressler ron.pressler at oracle.com
Tue Nov 16 23:05:57 UTC 2021

> On 16 Nov 2021, at 17:20, Mike Rettig <mike.rettig at gmail.com> wrote:
> The full interface I would like to see would look more like this:
> interface TaskExecutor<T>{
>     Task newVoidTask(T t);
>     //TODO add tasks that return values...
> }
> This allows developers to define their own domain specific tasks and decide how the tasks execute asynchronously. The runtime can coordinate the tasks and provide visibility to the tooling. Type safety can be enforced and domain specific methods can be added for complex task coordination.
> Providing a type safe, pluggable api would open up a whole new world of possibilities. An api based on Runnable, Callback, and the thread api is a great default implementation, but is too limiting for complex scenarios. 
> Mike

I fail to understand what this has to do with the structured concurrency JEP on the one hand, and why is it not exactly what the ExecutorService interface is. What problem are you trying to solve? What is the complex scenario that you’d like help with?

— Ron

More information about the loom-dev mailing list