clojure-dev

2026-06-25T02:18:18.461409Z

To me, the value of a Clojure data-structure lies in its ability to be data, so without proper EDN support and literal syntax it's kind of a big bummer.

2026-06-25T02:20:09.115379Z

I'd rather there just wasn't a queue at all, because... Ya there's no queue, use interrop, I go ok. But, there is a queue, it's not data and doesn't have proper Clojure APIs, that's just like giving me a half eaten box of chocolate 😝

➕ 1
phronmophobic 2026-06-25T02:20:52.122439Z

If only there was a data notation that was extensible.

☝️ 1
🤣 1
2026-06-25T02:28:21.130519Z

I know, I mean it's strange to me to package a data structure that's not properly data inside Clojure. If it came from another Java library, I'd expect to have to make it data on my own, but having it part of this beautiful buffet of truly data data-structures from the project that taught me the benefit of representing data-structures as data, it makes me sad lol. Not a huge deal cause I think I only had to wrangle my own data reader for queue once in 10 years, but still I can relate with OP

👍 2
2026-06-25T02:31:39.442009Z

If I had to choose though, I'd likely prefer having sorted-set and sorted-map have data representations, I think I've wanted to preserve those semantics in EDN more often than queue. Though I guess the sorting fn is the challenge.