Using Class/forName in the .importClass call in proxy+ is not necessary, as the class is already loaded by its definition (define-class). The Class/forName usage causes problems when proxy+ is AOT'd as the root classloader attempts to load the proxy class, which is only available/defined in a child DynamicClassLoader.
Using
Class/forNamein the.importClasscall inproxy+is not necessary, as the class is already loaded by its definition (define-class). TheClass/forNameusage causes problems whenproxy+is AOT'd as the root classloader attempts to load the proxy class, which is only available/defined in a childDynamicClassLoader.