3 ms·
Well, I did specify "modern", which arguably includes sane Unicode handling. I think a reasonable compromise is to have "char" be a 32 bit type, whereas a "st
by jabl 6y ago
Well, I did specify "modern", which arguably includes sane Unicode handling.
I think a reasonable compromise is to have "char" be a 32 bit type, whereas a "string" would be UTF8.
- pjmlp 6y agoNot sure if I would call string handling in Swift sane, but to each its own.