This is a good clarification.
I found that when I tried to exclude some AOT stuff from the jar you can
get into a situation where Clojure will dynamically produce a class that is
already statically-produced at the root classloader and then you'll hit
ClassPathExceptions when you try to pass the
Don't get me wrong, I'm as much against types as the next R̶i̶c̶h̶
̶H̶i̶c̶k̶e̶y̶ guy.
However -- there are many popular Java frameworks that love to reflect on
their annotations and their generic type signatures.
To name a heavyweight: Spring. But also, of late: big data frameworks, many
writ
acade, the Clojure code
can make new objects just fine, so you're staying in Clojure for the rest
of it.
Very helpful, thanks!
On Monday, June 10, 2019 at 8:20:44 AM UTC-5, Alex Miller wrote:
>
>
> On Mon, Jun 10, 2019 at 12:04 AM eglue >
> wrote:
>
>> This is great,
puredanger/clojure-from-java/blob/master/src/cfj/core.clj>.
>
> Just `lein uberjar` and you're done. Use the Support API from Java as any
> other Java class. No AOT required.
>
>
>
> On Sunday, June 9, 2019 at 9:53:56 PM UTC-5, eglue wrote:
>>
>> I'
Regarding calling Clojure **from** Java...
I saw a Stuart Halloway tweet responding to someone who'd found this a
"soul-crushing, miserable experience."
I had a similar miserable experience and figured it was just me, but am now
suspecting that's not the case. (Happy to be shown the light howev
Oops, this should have be titled "Calling Clojure from Java" ... the
interop with Clojure calling Java is obviously well-worn and solid.
On Sunday, June 9, 2019 at 9:53:56 PM UTC-5, eglue wrote:
>
> I've been stalking Clojure for a while but now doing it professionally
I've been stalking Clojure for a while but now doing it professionally
full-time (woo hoo!).
I saw a Stuart Halloway tweet responding to someone who'd found it a
"soul-crushing, miserable experience."
I had a similar miserable experience and figured it was just me, but am now
suspecting that's
