Virtual threads and executor ?
Ron Pressler
ron.pressler at oracle.com
Thu Nov 18 20:53:31 UTC 2021
The rationale is simple: that mechanism is much less mature than others because we’ve focused on higher-priority items that are relevant to more people, and so, while we’re working on it, we don’t want to hold up the rest of the features in the project, so we took it out until we feel comfortable enough with its design and operation.
— Ron
> On 18 Nov 2021, at 19:22, Remi Forax <forax at univ-mlv.fr> wrote:
>
> In the latest refresh of loom, a user can not set the executor anymore.
> That's an issue because existing codes tend to use an executor so the refactoring to introduce virtual threads is now harder.
> The other issue I have is that i can not create a virtual thread on a non-daemon thread anymore, so i have a code of a proxy that terminates too early when using virtual threads.
>
> What is the rational behind not letting a user to specify an Executor when creating a virtual thread ?
>
> regards,
> Rémi
More information about the loom-dev
mailing list