Ephemeral threads

[Dmitry Zaslavsky]

Please don’t kill me…..
My current experiment on a large code base and I am using JDK 25 and opening up some internals.
I try to stick to what available in loom branch…. Hoping to reap out my kludge with what you’ll presumably provide.
For example I provided myself 
Thread.ofVirtual().factory().scheduler() 

I will have a question / report email in a few weeks.

I see that doc there (loom repro) changes as well. 
It’s not clear to me if all you want to expose is what’s in current doc or what is still in the code.
For example I need that variable on VirtualTask that disappeared in the current doc.

I can start the thread now :) 



> On Jan 9, 2026, at 10:08 AM, Alan Bateman <alan.bateman at oracle.com> wrote:
> 
> On 09/01/2026 14:39, Dmitry Zaslavsky wrote:
>> I wanted to add another ’user’ vote for Ephemeral threads.
>> 
>> We are experimenting with custom schedulers (thread pools) for VT
> 
> Are these experiments using one of the prototypes in the loom repo? Are you able to send a summary to the mailing list about your experiments?
> 
> -Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20260109/fe5a3d01/attachment.htm>