3 ms·
I'm curious -- what have you needed from Unicode 13 that wasn't in the previous version of Go? (Presumably new codepoints still work fine, as long as you're jus
by benhoyt 6y ago
I'm curious -- what have you needed from Unicode 13 that wasn't in the previous version of Go? (Presumably new codepoints still work fine, as long as you're just passing characters through, and not relying on the categorization functions in the unicode package.)
- smasher164 6y agoI do care about categorization though. Here’s an identifier parsing library of mine (https://github.com/smasher164/xid https://github.com/smasher164/xid) where I can’t test that codepoints are in some category without knowing the version. If unicode was an external library, it would be my responsibility to update this identifier parsing library.
- benhoyt 6y agoNice! I suspect you're in a minority of developers who need this level of control, though. I don't think I've ever used "unicode" directory, though I reach for "unicode/utf8" often enough.