squint 2026-11-11

I was actually just thinking about this yesterday… I think I have a hack that might work, but maybe I should ask here. I’m trying to get as many clj* hosts working under eve as possible. Squint is close but it can’t round trip keywords. They come back as strings. I’m thinking I can just make a custom tagged reader for keywords so they round trip. That’ll solve the round tripping but IDK if it’ll look ugly in code. Any thoughts here? Any appetite to change squint in that regard in the future? Is there an easier way I’m missing?

I’ve experimented a lot to get proper keywords in squint but I haven’t found a way that doesn’t have serious performance downsides

Seemed like a fair tradeoff, as a language experiment

Not suggesting squint should necessarily change it

But it would be interesting if we could get an efficient reader for it at the literal level, without too much ugliness

do you mean #k :foo ?

that could work. can you explain what this would buy you and how anyone would be willing to use it like this?

Basically so other clj*s interacting with squint would be able to round trip keys through squint. Curious if cljs-bean would be an efficient keyword abstraction for squint. It just wraps js objects with the cljs api.

(that’s as an aside)

But, if squint supports tagged readers, I should be able to do #eve/key :foo out of the box now, for my purposes. Just wouldn’t be the smoothest for people trying to dev on eve on squint, maybe… Not sure yet.

Yeah I could add support for that at least

Mind posting an issue?

For adding tagged readers to support round tripping foreign value literals?

Or for cljs-bean-ish api?

My use case can resolve with tagged readers. Honestly I wasn’t sure if squint supported them yet.

I’ll check and if it doesn’t support them I’ll file an issue.

No for tagged literals

released support for tagged literals

🎉 3