<div dir="ltr">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 ^^<div><br></div><div>Thanks a lot,</div><div>Eric</div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-10 10:52 GMT+02:00 Brent Royal-Gordon <span dir="ltr"><<a href="mailto:brent@architechies.com" target="_blank">brent@architechies.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On May 8, 2017, at 9:39 AM, Eric Blachère via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a>> wrote:<br>
><br>
> I was just wondering if there are plans to bring NSString functions manipulating paths into the native String class. (such as lastPathComponent, pathComponents etc...)<br>
> 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 have to do it ;)<br>
<br>
</span>Unfortunately, it seems like the decision not to include these methods on String was quite deliberate.<br>
<br>
Here's the revision where that happened: <<a href="https://github.com/apple/swift/commit/1f2390f1c75be65f57f189247bfe4f9b2fc11e3b#diff-d38f60064c3752f096c043e756d8f201R925" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift/commit/<wbr>1f2390f1c75be65f57f189247bfe4f<wbr>9b2fc11e3b#diff-<wbr>d38f60064c3752f096c043e756d8f2<wbr>01R925</a>> As you can see, they had that working and chose to disable it, presumably because they want you to manipulate paths through `URL`. (I wish the radar referenced in the commit message were public, but alas, it's not.)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
<br>
</font></span></blockquote></div><br></div>