Re: [swift-corelibs-dev] Bring NSString functions to String

> On May 11, 2017, at 5:17 PM, Andrey Fidrya wrote: > >> >> On 12 May 2017, at 00:05, Tony Parker > > wrote: >> >>> On May 10, 2017, at 4:19 AM, Andrey Fidrya via swift-corelibs-dev >>>

Re: [swift-corelibs-dev] Bring NSString functions to String

> On May 10, 2017, at 4:19 AM, Andrey Fidrya via swift-corelibs-dev > wrote: > > Hi All, > > Btw, when migrating from NSString's methods to URL I've noticed > that they work a bit differently: URL's methods convert strings > from NFC to NFD (decomposed) unicode

Re: [swift-corelibs-dev] Bring NSString functions to String

Hi All, Btw, when migrating from NSString's methods to URL I've noticed that they work a bit differently: URL's methods convert strings from NFC to NFD (decomposed) unicode form which is demonstrated by the example below. I had to additionally call .precomposedStringWithCanonicalMapping on

Re: [swift-corelibs-dev] Bring NSString functions to String

Thanks for the answer ! It seems a bit weird from them to advocate using NSString methods in the unavailability comment. I would rather use URL when I can even if the conversions are a bit tedious ^^ Thanks a lot, Eric 2017-05-10 10:52 GMT+02:00 Brent Royal-Gordon : > >

Re: [swift-corelibs-dev] Bring NSString functions to String

> On May 8, 2017, at 9:39 AM, Eric Blachère via swift-corelibs-dev > wrote: > > I was just wondering if there are plans to bring NSString functions > manipulating paths into the native String class. (such as lastPathComponent, > pathComponents etc...) > Because

[swift-corelibs-dev] Bring NSString functions to String

Hello, I was just wondering if there are plans to bring NSString functions manipulating paths into the native String class. (such as lastPathComponent, pathComponents etc...) Because even if we can always make an extension of String to easily cast it into NSString, it's still a bit of a shame to