Tamas Herman

Made a repro repo: https://github.com/onetom/babashka-fs-issue-111 Here is one symptom of not taking into account of the file system of a `Path`: ```clojure (-> s3-path (fs/path "test.txt")) ; Execution error (UnsupportedOperationException)...

Pushed some Jimfs examples too. Regarding the implementation, here are some observations: 1. The `path` & `as-path` functions are calling `io/file`, involves the legacy `java.io.File` concept, which doesn't support pluggable...

This `Thread.stop()` issue with recent JDKs has been discussed in the nREPL project and nREPL `1.2.0-beta1` has a way to address it: https://github.com/nrepl/nrepl/issues/296#issuecomment-2124840163 So I guess before Cursive would adopt...

btw, here is an example session of what would happen, if i eval some infinite sequences and try to interrupt the evaluation ```clojure Loading src/repl.clj... done (range) Evaluation interrupted. 123...

Here is an example: ``` lein change :dependencies conj '[org.clojars.benfb/gorilla-repl "0.6.0"]' ```

In case it's not clear from the main description, `(swap! test-clk t/>> (t/new-duration 5 :minutes))` would be the way to change the time within automated tests. I would rather write...

Another thing I haven't made clear probably is that my proposal would be the replacement of `tick.core/AtomicClock`. While it's a funny name, fusing the Clojure atom concept with the java.time.Clock;...

I also forgot to mention the `t/with-clock` facility, which is described here: https://www.juxt.land/tick/docs/index.html#_substitution While `t/with-clock` solves the problem for a single thread, using dynamic vars is trickier in multi-threaded situations....

is there any significance of using `mutable_clock.MutableClock`, instead of just `MutableClock` in the `proxy` call?

Very exciting! In our app we have a `:clk` component in our system map and everything relies on it explicitly. We inject it into our Datomic components too, so even...