Reflection is supported by GraalVM native compilation, but you need to declare what classes you need reflection support for at compilation.
What you must understand though, is that you're asking for something contradictory. You cannot get runtime eval and code linking and also deliver a statically linked compiled machine code binary.
That's why statically linked to machine code binary languages don't offer dynamic code generation, linking and reflection that can't be declared or performed at compile time.
This is true for GraalVM. It means when you develop Clojure for GraalVM native compilation you can't leverage such dynamic behavior as well.
Though you can embed the SCI Clojure interpreter inside your application and do dynamic code evaluation with it at runtime.
What you must understand though, is that you're asking for something contradictory. You cannot get runtime eval and code linking and also deliver a statically linked compiled machine code binary.
That's why statically linked to machine code binary languages don't offer dynamic code generation, linking and reflection that can't be declared or performed at compile time.
This is true for GraalVM. It means when you develop Clojure for GraalVM native compilation you can't leverage such dynamic behavior as well.
Though you can embed the SCI Clojure interpreter inside your application and do dynamic code evaluation with it at runtime.