Clojurians Log v2

show & tell: I've been playing around with extracting the state from stateful transducers https://gist.github.com/jamesmacaulay/9ae8e35a1c2e50f79c3f

this might be useful for various reasons, but one reason would be to hold the state somewhere in a global app state atom so that you could e.g. rewind it along with other app state

Hiiii friends

The acid just kicked in.

hi, I have a circular dependency between two defrecords. Is there another way to resolve this than move them into separate namespaces?

@nicholasf: https://clojuredocs.org/clojure.core/declare could be useful

nha: thanks, I tried declare

defrecord creates a Java class under the hood, declare only creates a var stub

nha: I ended up working around it

https://gist.github.com/nicholasf/0a94122da382a1fc16da

see the agency comment

ah I see.. well I was thinking about it : is it Clojure trying to nudge us into not having circular dependencies in records ?

I dont really want to guess what clojure means

@nicholasf: search the Clojure mailing list for this, I seem to remember something about circular defrecords

will do

must async channels be closed or are they eventually garbage collected. i.e. in

(<!! (go 1))

@ordnungswidrig: I believe they are GC'd whether or not they are closed, as long as there are no pending puts or takes (or any other references to it, of course)

Doesn't closing a channel drop all pending puts on the floor (resolves the >! to false)?