And you also have nuanced critique of the exact encoding system used or how it fits in with everything else.
-
-
Replying to @ManishEarth @aymericaugustin
right, but the original tweet tarred both with one brush. For context: http://yehudakatz.com/2010/05/17/encodings-unabridged/ …
4 replies 0 retweets 0 likes -
Replying to @wycats @aymericaugustin
Right, because (a) it's a tweet :p and (b) the former kind of critique is waaay too common.
3 replies 0 retweets 0 likes -
TLDR I'm tired of explaining the concept of a grapheme cluster to idiots.
3 replies 0 retweets 1 like -
Replying to @ManishEarth @aymericaugustin
idiot is a state of mind. it can change. ;p
2 replies 0 retweets 0 likes -
Replying to @wycats @aymericaugustin
I call them idiots precisely for their obstinate refusal to change. Im more than happy to explain unicode otherwise
2 replies 0 retweets 0 likes -
Replying to @ManishEarth @aymericaugustin
yeah, belief that "dynamic typing" is a great virtue for strings is kind of idiotic ;)
1 reply 0 retweets 2 likes -
Replying to @wycats @aymericaugustin
In my case I get annoyed when people want to break languages to make O(1) indexing work.
1 reply 0 retweets 0 likes -
Replying to @ManishEarth @aymericaugustin
I think it should usually be possible to do a single-pass index of strings (once) and get O(1) after
1 reply 0 retweets 0 likes -
Replying to @wycats @aymericaugustin
I mean, yeah, tricks like that exist. It's not free though.
2 replies 0 retweets 0 likes
right. I think you'd have to do it explicitly in Rust: String<T: Encoding>.index -> IndexedString<T: Encoding>
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.