ah, I've been mulling over this sort of thing to reduce cognitive load... lead to many frustrating runtime crashes?
-
-
or just bad practice?
1 reply 0 retweets 0 likes -
Replying to @Gankro @ManishEarth
if it were up to me, I'd make it more automatic in the low-level C APIs, but it works well enough in practice.
1 reply 0 retweets 1 like -
the pattern is like: body.force_encoding(req.content_type).encode! (in Rust you'd get a Result of course)
1 reply 0 retweets 0 likes -
Replying to @wycats @ManishEarth
does ruby bother to follow unicode tables (e.g. Ensuring various flavours of é are "equal")?
1 reply 0 retweets 0 likes -
-
I don’t think == should do normalization anyway, if only because there’s multiple variations of it to pick from
1 reply 0 retweets 0 likes -
indeed.
1 reply 0 retweets 0 likes -
The Swift devs strongly disagree; they just use the "empty" locale. I'm still feelin' this decision out.
1 reply 0 retweets 0 likes -
afaict because such a comp requires allocation (in general), systems code needs a different ==...
3 replies 0 retweets 0 likes
what use cases do they have in mind in particular?
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.