GNU bug report logs - #53765
[PATCH 00/17] Remove limitations on clojure-tools

Previous Next

Full log

Message #296 received at 53765 <at> debbugs.gnu.org (full text, mbox):

From: Reily Siegel <mail <at> reilysiegel.com>
To: Maxime Devos <maximedevos <at> telenet.be>, 53765 <at> debbugs.gnu.org
Subject: Re: [PATCH v2 05/18] gnu: Add clojure-core-memoize.
Date: Sat, 19 Mar 2022 20:07:27 +0100

Maxime Devos <maximedevos <at> telenet.be> writes:

> Also, if a Clojure library misbehaves when being AOT-compiled, without
> additional context, that seems like a bug in the Clojure library to me
> (or the AOT-compilation code).

When I first started running into these issues, I reached out to Clojure
maintainers on the Clojurians Slack, and the response was that AOT
compilation is only meant for complete applications to reduce startup
latency, not individual libraries. Here are some of the specific
responses I got.

Alex Miller:

> Well, guix’s system is wrong to [AOT library code]. Lots of Clojure
> libs have clj files that are not part of the lib.


Sean Corfield:

> Packaging a library as AOT'd code is likely to cause horrible problems
> for consumers of that library. You're aware that lots of Clojure
> libraries are packaged as JAR files with no compilation of source
> code? "Packaging" Clojure libraries seems kinda wrong on several
> levels. The normal way to get Clojure libraries is as dependencies in
> a project -- fetched by the Clojure tooling itself, when it is run.

-- 
Reily Siegel

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.