I was working with files containing a Byte Order Mark today, and in the process 
of writing a test case, I discovered that 

(string->symbol “\uFEFF”)

produces a symbol whose printed representation is 


… which seems unfortunate; I guess I would have expected something like


(… although I see now that this kind of escaping is not currently enabled 
inside vertical bars).

This leads to situations where two symbols with the same printed representation 
may not be equal?, which seems unfortunate.

Am I overlooking a good reason why this is the desired behavior?


You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to