News for hackers. Stuff that matters.
Re:Grokking Python 3’s str by perlgeek on Saturday January 14, 2017 @11:57AM (#13399266)
> For example ISO 10646 ("Unicode") has multi-code point sequences denoting still a single character

I only know two programming languages that deal correctly with that: Swift and Perl 6. If you know more, please tell me.

Re:Grokking Python 3’s str by steveklabnik on Saturday January 14, 2017 @02:05PM (#13399952)
Rust separates this out; the standard library gives you bytes and Unicode Scalar Values. Grapheme cluster stuff is in a package on Cargo, maintained by the Servo team.
Re:Grokking Python 3’s str by bquinlan on Saturday January 14, 2017 @05:58PM (#13401110)
You can iterate over Grapheme clusters using the standard library: https://doc.rust-lang.org/1.3.0/std/str/struct.Graphemes.htm...
Re:Grokking Python 3’s str by steveklabnik on Saturday January 14, 2017 @06:28PM (#13401260)
Those are unstable docs for 1.3; they don't exist in today's Rust.
Re:Grokking Python 3’s str by perlgeek on Sunday January 15, 2017 @09:00AM (#13403968)
If you rely on libraries, there are ICU libraries for C and Java too, see for example http://userguide.icu-project.org/boundaryanalysis
Re:Grokking Python 3’s str by jacobush on Saturday January 14, 2017 @06:42PM (#13401328)
Sounds like Rust follows in the tradition of C. Like you now always hear about hos C has no string type, just a bunch of char, will we hear in the future that, alas, Rust has no native support for grapheme clustering?
Re:Grokking Python 3’s str by steveklabnik on Saturday January 14, 2017 @07:30PM (#13401530)
The issue is, there's multiple ways to do the clustering, in my understanding. We picked the most core thing to be our most core thing. Text is hard.
Re:Grokking Python 3’s str by jacobush on Saturday January 14, 2017 @08:42PM (#13401843)
Oh I get it didn't want to come across as flippant. Indeed text is hard.