generate-proxy produces unpredictable method order in generated classes
Using core/proxy to generate proxies for Java classes produces unpredictable method ordering in the generated class files.
This is a problem for repeatable builds (when doing AOT).
Specifically, I'm running Clojure inside Docker, and I'd like my application image layer to be as small as those produced by Java developers (using Meta-inf classpaths and a lib directory). Anyway, to get this working properly so that all dependencies (including those compiled as part of AOT) are on a separate layer, I need the output of compiling my applications' dependencies' proxies to be the same each time I run the build. This reduces build time, image push time, image pull time and container scheduling time.
Example code that exhibits the problem (you'll need to run it a few times to see the issue).
Cause: I've tracked it down to the use of an unsorted map here:
Approach: Use a sorted map, sorted by hash of the key (which is a vector of method name, seq of param types, and return type).
Screened by: Alex Miller
OSX, OpenJDK 8
Note that this ordering may still change across Clojure or JVM versions as there is no guarantee of hashing across those. Pre-screening for now.
As requested, using Clojure 'hash' instead.
Thanks Alex - learned about boolean comparators too!
While this is probably fine, it might be better to use the hash (Clojure) function rather than .hashCode (Java) function. The map itself is hashed based on the hash so that seems more appropriate.
Now with more consistent formatting of 'let'
Copy paste between branches error. Tested this time.