Why build a Clojure string using literal characters?

Question

I was reading some code just now, and I ran across this line:

(str cache \, \space lru \, \space tick \, \space limit)

This is odd to me. Consecutive literal characters are used, instead of a string containing those characters. I would expect something more like this:

(str cache ", " lru ", " tick ", " limit)

But this is in a core library written by some venerable Clojure veterans, which makes me think that maybe there's a reason. What's the reason? Performance? Or what?

I'd guess stylistic choice. More than once I've thought, "Man I hate these stupid quotes.". — deadghost
– deadghost, Commented Jul 13, 2014 at 1:05

amalloy · Accepted Answer · 2014-07-14 06:15:52Z

6

There is no good reason. It probably performs worse than the version with strings, in addition to being uglier. You could also write (join ", " [cache lru tick limit]), which would be my preference, but I can understand choosing to write it out longhand. Using characters instead of strings is inexplicable, though. I can't track down the commit that added this line, because the repo has been destroyed and rebuilt at least twice as it switched names, but I'd wager there was no good reason. Maybe some misguided performance ideas.

edited Jul 14, 2014 at 6:15

answered Jul 13, 2014 at 2:45

amalloy

93k8 gold badges149 silver badges216 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why build a Clojure string using literal characters?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related