clojure-dev

seancorfield 2026-06-10T01:58:26.351689Z

Upvoting works: https://ask.clojure.org/index.php/3821/add-queue-and-queue-to-clojure-core

2026-06-10T01:59:42.667879Z

well sort of lol, the data reader one had 9 upvotes

2026-06-10T01:59:57.995899Z

they use votes to determine what to evaluate, certainly

seancorfield 2026-06-10T02:04:15.114589Z

#queue [:a :b :c]
(queue :a :b :c)
Hard to justify that first syntax when we'll have the second one 🙂 I suspect we'll continue to grumble about printing tho'...?

☝️ 1
seancorfield 2026-06-10T02:07:24.422939Z

This made me curious about our use of PersistentQueue. We have just three uses in 150k lines: • in a test, dealing with file descriptor stability over time(!) • in production code but only to assist with debugging (in a global atom) • in production code where we genuinely need a queue So, yeah, I agree with the reasoning here that a literal syntax is really not warranted.

Steven Lombardi 2026-06-10T02:24:44.689539Z

Makes sense. I've found it easy enough to implement my own literals. In general, I've yet to hit a situation where something lacking support in core has outright prevented me from accomplishing my goal. Which, pretty sure Clojure is the only language I've worked in where that's the case.

Steven Lombardi 2026-06-10T02:26:02.091329Z

But Noah, I'm sympathetic to your desire for dialect parity. It will likely need to be solved at the library level.

Alex Miller (Clojure team) 2026-06-10T02:46:33.289279Z

what parity are you missing? I think it's very uncommon to need to represent a literal queue across edn (vs a vector or list)

Alex Miller (Clojure team) 2026-06-10T02:47:56.885629Z

I have only ever used persistent queues to hold data being processed dynamically at runtime. queues are not even useful across threads unless you put them in some other stateful holder like an atom

👍🏽 1
Steven Lombardi 2026-06-10T19:08:46.298269Z

My parity comment wasn't necessarily related to the issue in this thread.

👍 1