<!DOCTYPE html><html><head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  </head>

  <body>

    <font size="4" face="monospace">Slight correction; the JEP is

      attempting to get to Preview in 22.  There will be still time to

      make API adjustments.</font><br>

    <br>

    <div class="moz-cite-prefix">On 11/17/2023 6:24 PM, - wrote:<br>

    </div>

    <blockquote type="cite" cite="mid:CABe8uE2byvx7DZ_0Xbaq8aKm5ng0DYjJoK7ryZe0oitN1+ZQcQ@mail.gmail.com">

      <div dir="ltr">Hello,<br>

        <div>I believe that there are some issues with the current API

          of Class-File API, where the class signature should require

          its superclass and superinterfaces to be class types (<a href="https://github.com/openjdk/jdk/pull/16514" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/openjdk/jdk/pull/16514</a>)

          and the type argument model adjustment (<a href="https://github.com/openjdk/jdk/pull/16517" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/openjdk/jdk/pull/16517</a>).

          Yet, the current Class-File API JEP is finalized and targeting

          JDK 22.</div>

        <div><br>

        </div>

        <div>Should these 2 improvements make their way into the JEP, or

          should they become separate patches integrated after the JEP's

          integration? Making them part of the JEP may increase effort

          to integration, and making them separate will require CSR

          filling and probably will cause these fixes to fail to catch

          up with JDK 22.</div>

        <div><br>

        </div>

        <div>Best,</div>

        <div>Chen Liang</div>

      </div>

    </blockquote>

    <br>

  </body>

</html>