Hi, good day everyone! I’m trying to get my feet wet with Clojure internals. Currently I’m reading iterate implementation in src/jvm/clojure/lang/Iterate.java and it caught my attention that _seed and _next are volatile variables. I’ve also seen that in first implementation seed was just final and got changed to volatile. Could someone explain a bit, or show me a path to understand why is that? Why it’s important for _seed and _next to have always the same value visible in all threads? What would happen if that wasn’t the case? Is that anyhow connected with laziness?

any vscode / calva users? How do I stop a command in the repl? lol.. it's just looping

next.jdbc question - where can i specify the builder-fn in here? Want to get lowercase qualified keys

(with-open [conn (jdbc/get-connection config/h2-spec)]
    (sql/query conn ["select * from connections"]))

Hi, is there some kind of "in memory" file / buffer that can act as a file? Basically want to test reading files, but I don't want to actually create any on the filesystem.

Oh looks like this works (let [a (.ByteArrayOutputStream.)] (spit a "foo") (slurp (.toByteArray a)))

If there's a cleaner way then I'm all open for suggestions

Hi, I have a set of tests (using clojure.test), all in one namespace that have an each fixture declared. Now I want to run the same set of tests unchanged (same input / output and assertions) twice, where the only difference is that in the each function, a different file is loaded for the second run. I guess there is a way to do that, but cannot come up with one right now that is simple, so, I'd be interested in ideas in how to solve that. It would also be great to see, if a test fails, with which precondition it failed.

@sveri About the only place where I use dynamic vars is with clojure.test-related code. Might also work in this case.

Would it bea idiomatic to run the test function twice? Something like:

(defn database-setup [f]
  (create-test-specs)
  (f)
  (create-test-specs-without-paths)
  (f))

where database-setup is the each fixture.

@sveri are you aware of test-ns-hook ?

@jason358 No, thank you, I will have a look

-.- I am using kaocha, which has an open issue for support of test-ns-hook https://github.com/lambdaisland/kaocha/issues/29 So unless I change my test runner I will have to look for a different solution.

Hi everyone. As an experienced Clojurist, how often do you use https://twitter.com/hashtag/Clojure?src=hashtag_click's (comment ) form in your day to day development? Do you have any other use case for it other than trying out something during development? Do you later delete it or do you push it along to production?

I use it every day as a place to evaluate code into my repl. I often leave the blocks in committed code for the next time I'm working there

Anyone with experience with depstar?

@hadilsabbagh18 We use it at work to build all our deployment artifacts. And I maintain it.

Hi @seancorfield! I figured out the problem I was having. Sorry to bother you...

@kraulain I use (comment ..) every day. I leave a lot of the comment blocks in the code when it is committed. I use it both to explore the problem space and the solution space, as well as to provide "set up" code for use with the REPL. You'll see that sort of thing in several of my open source projects too, for example https://github.com/seancorfield/usermanager-example/blob/master/src/usermanager/main.clj#L212-L219

Another, longer example is in next.jdbc: https://github.com/seancorfield/next-jdbc/blob/develop/src/next/jdbc/connection.clj#L283

I also generally have a (comment ...) block at the bottom of my files. It's often my scratchpad for building up functions and implementations. Sometimes I migrate them into tests. https://gitlab.com/jamesleonis/dht-cljc/-/blob/master/src/dht_cljc/infohash.cljc#L58