The legacy C string APIs create BINARY strings, but the new APIs have an encoding parameter.
-
-
The Swift devs strongly disagree; they just use the "empty" locale. I'm still feelin' this decision out.
-
afaict because such a comp requires allocation (in general), systems code needs a different ==...
-
I think it's a mistake. Consider sorting: if you normalize, lose stability for cases that aren't identical
-
why would you lose stability? Is there a non-total ordering 3 strings can make?
-
imagine a Set of three different but unicode-equivalent strings. copy them into another set. sort/compare
-
Swift literally says those aren't different strings; it is a set of one string.
-
right, so what about non-normalized strings as keys in a map?
-
there isn't normal and non-normal. All queries behave normalized, even hashing: http://swiftlang.ng.bluemix.net/#/repl/5817ea0b35979e5bb9778721 …
End of conversation
New conversation -
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.