Fork me on GitHub
Ben Sless07:12:02

The primitive wrapper classes getting designated as value based in Java 16 How should this affect Clojure?


without really doing an audit, I can't say for certain, but I would be surprised if Clojure itself is using or emitting code that called primitive wrapper constructors, or synchronized on primitive wrappers, or relied on equal but not identicalness. If so, those should all be easily fixable.


the differences between primitives and primitive wrapper objects are one of the most pervasively painful things across the implementation of Clojure. probably nothing but upside for us in the greater direction they're heading as value-based stuff is where Clojure has always lived

👍 2
🙏 1
Ben Sless08:12:48

I see the value classes as an absolute win, just hoping there isn't any cat in the bag there. Wondering how Clojure will leverage it in the future. Theoretically Java8 is in EOL but Clojure still supports even older versions, no?


Since Clojure 1.10, it supports >= Java 8


right now, as of survey last year, Java 8 is still the most common java used with Clojure. until that changes, I don't see moving to greater min Java

Ben Sless08:12:10

Alright, thanks


we removed all Clojure usages of primitive wrapper constructors in 1.10 those have been deprecated since JDK9

👍 1