We ended up sticking with AOT (for now, anyway), because it seems easier to
manage in the codebase. The alternative is to use data structures that can
be eval'd, like you would use in the body of a macro. I like how that
clearly separates the code that runs on the local machine from that which
Thanks for your replies.
I've looked at clj-headlights a bunch, and datasplash, too. I was mistaken
to think that AOT was necessary. Earlier in the project, AOT simplified a
few things, like affording the use of anonymous functions (in ParDo
implementations), and I don't think I realized until
Interesting! I had not seen clj-headlights but my org is using Beam +
Clojure and we've made some similar decisions as clj-headlights.
Specifically we are avoiding AOT and its headaches,.
On Thursday, September 12, 2019 at 12:37:24 AM UTC-5, Kimmo Koskinen wrote:
>
> Hi!
>
> Not a direct answer,
