core-async

Pavel Filipenco 2025-12-05T06:22:45.678689Z

If I use >!! in a virtual thread, do I understand correctly that the virtual thread will be "parked", i.e. roughly the same behavior as if I used >! in a go block?

2025-12-08T15:05:09.157699Z

the way to think about it is that !! ops will be treated like any other JVM blocking operations under vthreads - this has nothing to do with core.async. That’s important since the actual mechanism for vthread parking might be different than async/go

❤️ 2
fogus (Clojure Team) 2025-12-05T14:58:14.335569Z

yes

👍 1
Pavel Filipenco 2025-12-05T13:33:04.559889Z

Another question. You probably have many functions which run a loop taking from one channel/non-channel source and putting into a channel. What is the naming convention for such functions? I want to use ->, but I have doubts since it already has an established meaning of functions that take Something and return SomethingElse, converting the Something into a SomethingElse. Should I use -> or make some other notation that avoids long words and expresses the meaning precisely?

ghadi 2025-12-05T15:00:49.821609Z

in general, that's a type of process, so I usually say "proc"

Pavel Filipenco 2025-12-06T04:36:41.340209Z

proc what?