GC Issue 108: All Clojure interfaces should specify CharSequence instead of String when possible

Question

 Reported by redchin, Apr 20, 2009

rhickey: unlink: then just use a map {:escaped true :val "foo"}

unlink: What I meant is, everything in between would want to see something
String-y, not caring whether it's a String or MyString.

hiredman: unlink: if you use something that implements CharSequence and
IMeta (I think it's IMeta) you get something that is basically a String,
but with metadata

rhickey: what hiredman said

hiredman: ideally most things would not specify String but CharSequence in
their interface

hiredman: but somehow I doubt that is case

unlink: ok.

unlink: Good to know.

rhickey: hiredman: unfortunately that's not true of some of Clojure - could
you enter an issue for it please - use CharSequence when possible?

Answer 1

Comment made by: importer

richhickey said: Updating tickets (#8, #19, #30, #31, #126, #17, #42, #47, #50, #61, #64, #69, #71, #77, #79, #84, #87, #89, #96, #99, #103, #107, #112, #113, #114, #115, #118, #119, #121, #122, #124)

Answer 2

Comment made by: importer

Converted from http://www.assembla.com/spaces/clojure/tickets/112

Answer 3

Reference: https://clojure.atlassian.net/browse/CLJ-112 (reported by alex+import)