A New Early Access Build

[Dávid Karnok]

I have no way of knowing if an executor is virtual or not at the moment
from the outside. It is up to Loom to make it work, make it detectable or
disallow it by throwing an exception.

Nawazish Khan <md.nawazish.khan at gmail.com> ezt írta (időpont: 2020. jan.
3., Pén 7:46):

> Why would, or what could be a good use case to schedule virtual threads on
> pool of virtual threads?
>
> On Thu, Jan 2, 2020 at 11:36 PM Alan Bateman <Alan.Bateman at oracle.com>
> wrote:
>
>> On 01/01/2020 12:24, Dávid Karnok wrote:
>> > Before the API change in Loom, I was using
>> > FiberScope.background().schedule(executor, work) where executor was
>> > any Executor without extra constraints as I understood it.
>> The prototypes to date haven't supported this. You may have got lucky
>> but you would probably have tripped over a number of asserts if running
>> with -esa.
>>
>> So yes, it's a hazard in the current prototype. If you are using a
>> custom scheduler, the threads (or "carrier threads" as we've been
>> calling them) must be kernel/heavyweight threads. There are several
>> issues that will need to be worked through before it will be possible to
>> multiplex virtual threads over a pool of virtual threads over a pool of
>> ...  Hopefully this won't prevent you from testing other things.
>>
>> -Alan
>>
>