Refl should ignore entries when caller is either clojure.lang.Compiler$ObjExpr or clojure.lang.Compiler$NewInstanceExpr, clojure.lang.Compiler$StaticFieldExpr etc. about refl HOT 6 OPEN

@FieryCod I think a better option is to AOT (Clojure compile) your code first and not run Clojure's compilation process through the native image agent.

from refl.

@borkdude Traces comes from one of the holy-lambda examples (native-configuration here). HL automatically compiles user code with depstar.

As you can see here. I'm running native-agent on jar. For simple projects where aws-api is not used, both traces and reflection configurations do not contain any of the entries specified in this issue.

from refl.

Please make a smaller repro.

from refl.

To be clear, I am interested in improvements, but I'd like to learn what causes these reflections. An already compiled Clojure program should probably not hit any clojure.lang.Compiler reflections anymore. Hence I am interested in a repro, e.g. an addition to src/refl/main.clj which triggers this.

from refl.

@borkdude here is the repro. FieryCod@4752c4b

from refl.

@FieryCod Thanks, that helps. I'll take a closer look this weekend hopefully.

What is interesting is that it also stumbles upon:

Could not resolve clojure.core$eval12 for reflection configuration. Reason: java.lang.ClassNotFoundException: clojure.core$eval12

It seems that eval is being called somewhere in this program, which doesn't work with GraalVM anyway. So some deeper digging would be worth to find out why this is the case. Perhaps it hits this spot?

https://github.com/clojure/clojure/blob/b1b88dd25373a86e41310a525a21b497799dbbf2/src/clj/clojure/core.clj#L5481

from refl.