Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate JEP 334: JVM Constants API #22294

Open
tgodzik opened this issue Jan 2, 2025 · 0 comments
Open

Investigate JEP 334: JVM Constants API #22294

tgodzik opened this issue Jan 2, 2025 · 0 comments
Labels
area:jdk Issues tied to artifacts published under a particular jdk compat:java:jep:stable Issues corresponding to a JEP which got already delivered as a stable feature in a JDK release compat:java:jep Issues corresponding to a JEP (JDK Enhancement Proposal) itype:enhancement

Comments

@tgodzik
Copy link
Contributor

tgodzik commented Jan 2, 2025

JEP 334 introduced JVM Constants API, which at a glance seems useful to Scala. Especially since in the description it's mentioned:

Compilers and offline transformers (such as jlink plugins) need to describe classes and members for classes that cannot be loaded into the running VM. Compiler plugins (such as annotation processors) similarly need to describe program elements in symbolic terms.

Since we are planning to update to a newer JDK at an unspecified future I hope we can figure out if this is in any way useful for us.

And if we can actually use them or whether it will be impossible for us.

Introduced in JDK 12

@tgodzik tgodzik added area:jdk Issues tied to artifacts published under a particular jdk compat:java:jep Issues corresponding to a JEP (JDK Enhancement Proposal) compat:java:jep:stable Issues corresponding to a JEP which got already delivered as a stable feature in a JDK release labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:jdk Issues tied to artifacts published under a particular jdk compat:java:jep:stable Issues corresponding to a JEP which got already delivered as a stable feature in a JDK release compat:java:jep Issues corresponding to a JEP (JDK Enhancement Proposal) itype:enhancement
Projects
None yet
Development

No branches or pull requests

2 participants