snippetrustMajor
How to iterate over Unicode grapheme clusters in Rust?
Viewed 0 times
graphemehowclustersoveriterateunicoderust
Problem
I am learning Rust and I just have been surprised by the fact that Rust only is able to distinguish UTF-8 byte sequences, but not actual grapheme clusters (i.e. a diacritic is considered as a distinct "char").
So for example, Rust can turn input text to a vector like this (with the help of
But how do I get a vector like this?
So for example, Rust can turn input text to a vector like this (with the help of
"नमस्ते".chars()):['न', 'म', 'स', '्', 'त', 'े'] // 4 and 6 are diacritics and shouldn't be distinct itemsBut how do I get a vector like this?
["न", "म", "स्", "ते"]Solution
You may want to use the
(Playground, note: the playground editor can't properly handle the string, so the cursor position is wrong in this one line)
This prints:
The
Segmentation into Unicode grapheme clusters was supported by the standard library at some point, but unfortunately it was deprecated and then removed due to the size of the required Unicode tables. Instead, the de-facto solution is to use the crate. But yes, I think it's really unfortunate that the "default standard library segmentation" uses codepoints which semantically do not make a lot of sense (i.e. counting them or splitting them up generally doesn't make sense).
unicode-segmentation crate:use unicode_segmentation::UnicodeSegmentation; // 1.5.0
fn main() {
for g in "नमस्ते".graphemes(true) {
println!("- {}", g);
}
}
(Playground, note: the playground editor can't properly handle the string, so the cursor position is wrong in this one line)
This prints:
- न
- म
- स्
- तेThe
true as argument means that we want to iterate over the extended grapheme clusters. See graphemes documentation for more information.Segmentation into Unicode grapheme clusters was supported by the standard library at some point, but unfortunately it was deprecated and then removed due to the size of the required Unicode tables. Instead, the de-facto solution is to use the crate. But yes, I think it's really unfortunate that the "default standard library segmentation" uses codepoints which semantically do not make a lot of sense (i.e. counting them or splitting them up generally doesn't make sense).
Code Snippets
- न
- म
- स्
- तेContext
Stack Overflow Q#58770462, score: 63
Revisions (0)
No revisions yet.