cleanups to do after JEP 483 push

[John Rose]

Now that our “JEP One” (483) is nearing the target stage,
it is time to talk about post-push work.  That would be small
stuff like bug fixes, refactorings (for tech debt payoff),
and API adjustments. The big stuff (JEPs Two and Three for
persistent profiles and AOT code) will follow in time.

Here’s my current list of possible post-483 cleanups.
We don’t need to do them all, nor necessarily in JDK 24.

- contract adjustments for stable, and usage corrections
- Mat C.’s hook for ending training runs (small API upgrade)
- fix for handling signed JARs (minor bug in PIT)
- fix for class loader table overflow (minor bug in PIT)
- cleanups for bootstrap orchestration (this is open-ended)
- clarify user model for integer box cache, when using AOT cache
- get rid of the “scratch object” lifecycle in AOT processing

Let’s track this “wish list” under [JDK-8343023], please.
And start proper RFEs or bugs as each item gets momentum.

And, do reply with more suggestions.  Bigger, longer range
items are welcome also, but let’s keep them distinct in our
minds.  I’m mainly talking here about stuff that will make
JEP One more robust and maintainable, and a better foundation
for JEPs Two, Three, and so on.

More to follow…

— John

[JDK-8343023]: https://bugs.openjdk.org/browse/JDK-8343023
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20241107/a9ff60ef/attachment.htm>