xid VS uniseg

I do care about categorization though. Here’s an identifier parsing library of mine (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.

So far, I've found this package for Unicode text segmentation: https://github.com/rivo/uniseg

Ah this is an intreresting one. I’ve recently had to deal with graphemes and after learning a bit more about them with a coworker, was surprised to find there doesn’t seem to be native support for them in Golang. Does anyone know if support for dealing with graphemes will be added eventually? For the moment I’ve used https://github.com/rivo/uniseg

Yes, what you want is called a grapheme cluster. It faithfully represents one "visible" character in your terminal. Use something like https://github.com/rivo/uniseg to turn a string into graphemes and iterate over them.

There is an open source library github.com/rivo/uniseg that provides a function to do just this. It provides a function GraphemeClusterCount that returns the number of characters that is present in this string. Check out the source code on Github for details about the author and the implementation.