<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 02/12/2024 21:42, Chen Liang wrote:<br>
</div>
<blockquote type="cite" cite="mid:SJ2PR10MB7669FFF868EF3EF63979728DA2352@SJ2PR10MB7669.namprd10.prod.outlook.com">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Masoud,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As you can see in JEP 499 (<a href="https://openjdk.org/jeps/499" moz-do-not-send="true" class="moz-txt-link-freetext">https://openjdk.org/jeps/499</a>),
there is no change in the 4<sup>th</sup> preview.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Originally, it was planned to make STS an interface (see <a href="https://github.com/openjdk/loom/commit/3996f6c9e930e941076a33a1b58ebc7e475285c8" moz-do-not-send="true" class="moz-txt-link-freetext">
https://github.com/openjdk/loom/commit/3996f6c9e930e941076a33a1b58ebc7e475285c8</a>)
in the 4<sup>th</sup> preview; Alan seems to have deferred these
changes to a 5<sup>th</sup> preview per
<a href="https://github.com/openjdk/jdk/pull/21934" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/openjdk/jdk/pull/21934</a>,
most likely due to various cleanup after the integration of JEP
486, the removal of Security Manager.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
</blockquote>
<br>
The JEP with the API refresh is submitted with a view to getting it
onto the technical roadmap. Too many other JEPs were also trying to
get onto the technical roadmap around the same time and several
(including this one) didn't get onto the roadmap in time. Hopefully
next release. It's nothing to do JEP 486.<br>
<br>
As regards the naming it came from Future.State when this API
changed from returning a Future to Subtask for the first preview.<br>
<br>
-Alan<br>
</body>
</html>