CSR for Class-File API (Preview)

[-]

First, congratulations on the progress of Classfile API!
There are two outstanding issues that I see for now.
1. The design of Classfiles (context) object, where options are
shared; and some options might be localized to individual
codebuilder/classbuilder etc.
2. Many of the API endpoints are missing specifications, such as
missing @sealedGraph tag. I would be glad to provide or improve
documentation for the Classfile API.

In addition, what's the rationale for putting all these new contents
under java.lang instead of java, like java.classfile vs
java.lang.classfile?

Chen Liang

On Wed, May 24, 2023 at 7:18 AM Adam Sotona <adam.sotona at oracle.com> wrote:
>
> Hi,
>
> I’ve just kicked off CSR JDK-8308754 Class-File API (Preview) to have enough time for discussions and improvements.
>
> Javadoc at https://cr.openjdk.org/~asotona/8308754/classfile-api/javadoc/java.base/java/lang/classfile/package-summary.html is altered to show target java.lang.classfile package and will be updated according to our current main codebase.
>
> No branch nor fork is created for the transition and all API or javadoc changes are expected to go to the current codebase in the jdk main under jdk.internal.classfile package.
>
>
>
> Please let me know your comments.
>
>
>
> Thanks,
>
> Adam
>
>
>
>
>
>
>
>
>
>
>
>