id summary reporter owner description type status priority milestone component version resolution keywords cc difficulty 1576 Keywords get encoded with leading NUL byte, breaking read-write invariance of symbols starting with a NUL byte sjamaan "Similar to #1077, the string belonging to keywords still get interned by prefixing it with a NUL byte. This means {{{(string->symbol ""\000foo"")}}} gets read as a keyword and printed back as `#:foo`. This is of course not really correct. Fixing it means we'll need to get rid of the in-bound signaling of the keyword information. A potential fix could involve storing keywords in a different symbol table than regular symbols." defect closed minor 5.1 core libraries 5.0.0 fixed keywords, symbols, read-write invariance medium