Continuations before Fibers

Alan Bateman Alan.Bateman at
Sat Mar 7 16:28:17 UTC 2020

On 07/03/2020 15:34, Alen Vrečko wrote:
> :
> I'd still like to be able to have control over scheduling. I think a 
> simple API addition such as:
> // able to do this while the VThread already did some work but is not 
> yet finished
> VirtualThread.setScheduler(vt, useThisSchedulerInstread);
> virtualThread.get/setScheduler.
> Would do the trick. You are probably rolling your eyes. But looking at 
> the code it doesn't look like a big deal to add API like this. If it 
> would make it easier, could allow for change of scheduler only from 
> within the executing VThread?
Maybe not easy to find either but Thread.Builder has a virtual(Executor) 
method so you can specify your own scheduler for the advanced cases that 
need it.

> Another note. I think it would make sense to make VirtualThread class 
> public. I find something like:
> vt = new VirtualThread(myRunnable);
> vt.start();
> more natural than Thread.builder().virtual().task(myRunnable).start();
We've trying to avoid exposing a sub-type in the API at this time. We do 
need to improve the factory methods, that work stalled a bit due to 
legacy ThreadGroup. For now you can do this:
    var thread = Thread.newThread(Thread.VIRTUAL, task);
but expect it to change once there is something better.


More information about the loom-dev mailing list