owenRiddy

I investigated this issue and it seems to come down to the behaviour of `clojure.walk/macroexpand-all`. Eg, ``` (clojure.walk/macroexpand-all '(letfn [(dummy [] true)] (d))) ; => (letfn* [dummy (fn* dummy ([]...

Hey, just passing through; sorry if I'm about to be unhelpful. The torch version (`torch-2.0.1+rocm5.4.2`) looks suspicious. [Easy diffusion](https://github.com/easydiffusion/easydiffusion) has done great work supporting the unsupportable for me and I...

This issue is being caused by the use of `clojure.core/proxy-super`. That function is not thread safe and one of the symptoms is that occasionally a proxy object will forget the...

Yes. The [fine print says](https://clojure.org/reference/java_interop#primitives) > Functions have limited support for primitive arguments and return type: type hints for long and double (only these) generate primitive-typed overloads. Note that this...

I think that would be enough. Problems were only occurring at compile time and I didn't see anything complaining apart from the Clojure compiler.

Implementing `proxy-super` properly seems a bit hard. I couldn't figure out how to detect whether the code is in a context where it is usually legal to call the superclass...

> I think doing this properly would ultimately require support from the Clojure compiler. It'd be helpful. Although after spending 24 hours mulling I'm not sure even access to the...