Does anyone know why cider-read-symbol-name and cider-try-symbol-at-point coerce keywords to symbols?

I was trying to write an extension to cider-doc which would dispatch to cider-browse-spec when called on a keyword, which is what I mean to do most of the time

And I can't think of a use-case where reading :foo/bar as foo/bar would be useful

@qythium Likely it’s just how thing-at-point works, which seems reasonable to me. Keep in mind that symbols and keywords are different syntactic entities.

I’m pretty certain I never made special efforts to coerce keywords to symbols. I just assumed that the users will run symbol specific commands on symbols. 🙂