It will be available for garbage collection:

> (future
    (reify
      Object
      (finalize [_]
        (println "goodbye"))))
#<Future@18bd51a8: 
  #object[$eva...66"]>
> (System/gc)
goodbye

Thankyou. Great little bit of example code.

does this actually garbage collect though?

user=> (def fut
  #_=> (future
  #_=>     (reify
  #_=>       Object
  #_=>       (finalize [_]
  #_=>         (println "goodbye")))))
#'user/fut
user=> fut
#object[clojure.core$future_call$reify__8439 0x68d96261 {:status :ready, :val #object[user$fn$reify__2006 0x35c59975 "user$fn$reify__2006@35c59975"]}]
user=> (System/gc)
goodbye
nil
user=> fut
#object[clojure.core$future_call$reify__8439 0x68d96261 {:status :ready, :val #object[user$fn$reify__2006 0x35c59975 "user$fn$reify__2006@35c59975"]}]
user=> @fut
#object[user$fn$reify__2006 0x35c59975 "user$fn$reify__2006@35c59975"]

or will it gc when fut is gced?

will fut be gced when finished?

It will be available for garbage collection when there aren't any references pointing towards it

yep great thanks

but printing “goodbye” means something have been gc’d right when fut was live? i see an other “goodbye” after

(def fut nil)
(System/gc)

(def fut
  (future
    (reify
      Object
      (finalize [this]
        (println (.hashCode this))))))
=> #'finaliz/fut
(System/gc)
1723828443
=> nil
(.hashCode @fut)
=> 822250702
(def fut nil)
=> #'finaliz/fut
(System/gc)
822250702
=> nil

interesting

I don’t really see any benefit in turning this into a record. You already have it properly structured with nice names and all that and Clojure’s APIs work best with this kind of data 🙂 If you need Java interop then maybe, but as is, nah.

That is what I thought. Thanks! 🙏

are you testing your main function in REPL?

No, I’m calling it from the shell via clojure -M -m exception-test.core

ok, that isn’t working because of https://github.com/clojure/clojure/blob/master/src/clj/clojure/main.clj#L650-L672 exception thrown by your code will be catched by clojure’s main function

Thanks a lot. I just figured out the same thing.

Here is my dep.edn for application.

{:paths ["src" "resources"]
 :deps {org.clojure/clojure {:mvn/version "1.10.3"}
        com.amazonaws/aws-lambda-java-core   {:mvn/version "1.0.0"}
        com.amazonaws/aws-lambda-java-events {:mvn/version "1.0.0"}}
 :aliases
 {:dev  {:extra-deps {clojure.java-time/clojure.java-time {:mvn/version "0.3.2"}}}
  :uberjar {:replace-deps {com.github.seancorfield/depstar {:mvn/version "2.0.211"}}
            :exec-fn hf.depstar/uberjar
            :exec-args {:aot true
                        :jar "lambda-demo.jar"
                        :main-class "yhnam.lambda-demo"
                        :sync-pom true}}}}

Test for separate java-time dependency

I'd say that scope provided is something for libs to use, not applications If you need to make a dependency optional, you can simply isolate it via the :aliases mechanism e.g. it can be present under the :dev alias but otherwise absent by default. Anyway I'd recommend taking a step back and describing your problem more precisely, before considering any specific solution

So basically you want to compile your AOT code with some dependency on the classpath and then make an uberjar with that dependency not on the classpath

or otherwise not included in the uberjar

depstar supports different sets of aliases for compilation and for JAR-building, which was added specifically for this use case.

:aliases and :compile-aliases are the exec arguments you need but you'll need to ensure that what you need for compilation is added via an alias, so that you can tell depstar "compile it with these dependencies" and then "build it with these different dependencies".

https://github.com/kwladyka/consistency-clj/blob/master/deps.edn here is example of real code for compile to uberjar and publish to clojars consider just use https://clojure.org/guides/tools_build#_parameterized_build . I didn’t have a chance to try, but looks like it can be new standard.

@U0WL6FA77 That is not a useful example: it does not involve :aliases or :compile-aliases for depstar which is what the OP needs.

ok sorry, I didn’t quite understand the question.

Thanks a lot! it’s really helpful.

confirmed, it was the issue

it is worth to look on number of threads in the process. if it is growing in time it can means something not close properly.

This seems to work:

(ns-unmap *ns* 'Enum)
(defrecord Enum [])

not sure if there's a cleaner way

Seems like the best idea I can think of

Thanks!