Vojin Jovanovic
Vojin Jovanovic
To be efficient, this flag should only instrument instantiation of classes that are marked for initialization at build time.
The problem was reported here: https://github.com/graalvm/native-build-tools/issues/550#issuecomment-1983920449 The agent collects metadata into intermediary folders and all the metadata is then merged. Since `SIGINT` interrupts the agent, then all the metadata merging...
End users with third-party dependencies without provided reflection metadata must currently devise the required metadata themselves. Producing metadata is time-consuming and it can discourage users from compiling natively. We need...
Currently, the only thing we get is: ``` [native-image-plugin] Instrumenting task with the native-image-agent: run ``` which is not very useful.
### TL;DR When building a native image, the user has no information about the elements that were included via the reachability metadata. This makes debugging and testing of reachability metadata...
### TL;DR Expressing reflection over lambda-proxy and Java-proxy types in JSON-based reachability metadata is currently impossible. To compile programs that require those features, users currently have to rewrite the code...
### TL;DR The reachability metadata JSON files must evolve to completely cover the Java semantics. The most important upcoming features are: `type` for proxy and lambda classes [#7476](https://github.com/oracle/graal/issues/7476), new conditions...
# TL;DR Libraries often rely on catching exceptions from the reflection API and they have a mechanism to recover from them. Native Image does not distinguish between missing [reachability metadata](https://www.graalvm.org/22.2/reference-manual/native-image/metadata/)...