Thanks for that, I've attached a possible fix to the ticket.
> On 5 Jan 2016, at 15:40, 'wparke...@yahoo.com' via Clojure
> wrote:
>
> I have logged an issue at http://dev.clojure.org/jira/browse/CLJ-1874
>
> Thank you all for the responses.
>
> On Wednesday, December 30, 2015 at 12:02:35 P
I have logged an issue at http://dev.clojure.org/jira/browse/CLJ-1874
Thank you all for the responses.
On Wednesday, December 30, 2015 at 12:02:35 PM UTC-6, Nicola Mometto wrote:
>
> While it's true that AOT has many issues, it's getting better release
> after release and this is definitely a
This issue is a subtle one. I do find it interesting that all vars are
created and mapped to their namespace in the initN() (where N is 0 though
whatever) methods.
However, other top-level function calls happen in the load() method. All
of this runs in the clinit of the class though.
I'd re
While it's true that AOT has many issues, it's getting better release after
release and this is definitely a bug.
I don't understand why you wouldn't expect this to work, you *should*.
OP: can you open a ticket for this bug? I'd love to have a look at this and try
to fix it.
> On 29 Dec 2015,
AOT-compilation breaks almost any code that tries to redefine Vars. I
wouldn't expect this to work.
—S
On Monday, December 28, 2015, wparker30 wrote:
>
> I have found what appears to be a bug in AOT-compiled Clojure when
> ns-unmap is used. I have the following reduced case:
>
> (ns unmap-test
I have found what appears to be a bug in AOT-compiled Clojure when ns-unmap
is used. I have the following reduced case:
(ns unmap-test.core)
(def a :test-1)
(ns-unmap 'unmap-test.core 'a)
(def a :test-2)
It turns out that a is not resolvable when this namespace is loaded. When
I looked at
