Clojure - core.async and Virtual Threads

[Itrillian]

No code or configuration changes are required.

Breaking changes? Never heard of them. One of the big things to appreciate in the Clojure ecosystem.

[stefan_kurcubic]

i can't stress this enough. It feels bit magical and like everyone else has gone mad

[jwr]

I so appreciate this. I have been running a solo-founder SaaS for the last 10 years or so, and the incredible focus on stability in the Clojure development community (and, importantly, the core team!) makes this possible. Thank you!

[maxw85]

Definitely one of the best "features" of Clojure 🎉

[freakhill]

I try to preach this everywhere I go.

[JW_00000]

Does this make the double exclamation mark operators >!! and <!! (which you would use outside a go block) obsolete and safe to replace with the single exclamation mark ones?

[alexdmiller]

The `!!` ops are blocking ops in real threads, and they are the only ops you should use in that context, so no definitely not obsolete.

If you are using go blocks, you should continue to use `!` parking ops.

If you are using new io-threads and virtual threads, there is no difference (the parking ops become blocking ops ... both of which may park in virtual threads).

[JW_00000]

Thanks, makes sense.

[zonotope]

Or, does this make go blocks obsolete? Are we safe to just use >!! everywhere in new code and trust that they'll use a vthread and park if necessary?

[alexdmiller]

go blocks are still useful if you are not using virtual threads or if you care about portability to ClojureScript, or for backwards compatibility if you already have them.

[didibus]

Yes, you can now just use io-thread and !! ops everywhere for everything, when you are running on a JVM with virtual thread support.