<div dir="ltr">Thanks Alan! It looks like this is the commit that removed the prototype? <a href="https://github.com/openjdk/loom/commit/cad26ce74c98e28854f02106117fe03741f69ba0" target="_blank">https://github.com/openjdk/loom/commit/cad26ce74c98e28854f02106117fe03741f69ba0</a><div><br></div><div>I'll see if that's enough to experiment with, and will report back if I have any feedback in case that's useful if this is revisited in the future.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 6, 2024 at 9:37 PM Alan Bateman <<a href="mailto:Alan.Bateman@oracle.com" target="_blank">Alan.Bateman@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 07/06/2024 01:51, Liam Miller-Cushon wrote:<br>
> Hi,<br>
><br>
> There were some mentions of 'pluggable schedulers' in the early Loom <br>
> docs [1][2] that would have allowed users to replace ForkJoinPool with <br>
> a custom scheduler, but it wasn't included in the later proposals. I <br>
> found a mention on loom-dev@ in 2022 that they were 'being worked on <br>
> but were not delivered in JEP 425' [3].<br>
><br>
> I'm curious what became of that idea--is it still possible future <br>
> work, or was a decision made not to support that at some point?<br>
<br>
It's a feature that we have to be very cautious about. The EA builds <br>
exposed a prototype API for a long time but there wasn't much feedback. <br>
Definitely not enough usage to help decide what hooks to expose. The API <br>
(not the implementation support) was pulled when preparing the proposal <br>
for the main line (JEP 425). There is interest in some areas to explore <br>
the topic again, just nothing definite (no JEP) at this time.<br>
<br>
-Alan<br>
<br>
<br>
</blockquote></div>