Re: [swift-corelibs-dev] NSString.isAbsolutePath inconsistency

2017-01-20 Thread Nethra Ravindran via swift-corelibs-dev
Hi Tony and Philippe, I can now see that it is available in swift-3.1 branch. Sorry for the confusion. - Nethra Ravindran On Fri, Jan 20, 2017 at 3:53 AM, Tony Parker wrote: > Hi Nethra, > > If this was in master sometime before this past Tuesday, it should be > included in the swift-3.1 bra

Re: [swift-corelibs-dev] NSString.isAbsolutePath inconsistency

2017-01-19 Thread Tony Parker via swift-corelibs-dev
Hi Nethra, If this was in master sometime before this past Tuesday, it should be included in the swift-3.1 branch by default (that branch received merges from master). Did you check out the latest version of the swift-3.1 branch to verify that this change was missing? - Tony > On Jan 19, 2017

[swift-corelibs-dev] NSString.isAbsolutePath inconsistency

2017-01-19 Thread Nethra Ravindran via swift-corelibs-dev
Hi Philippe, A naming inconsistency with NSString.isAbsolutePath (file - NSPathUtilities.swift) was fixed in your PR named “ Import CoreFoundation changes from Sierra “: https://github.com/apple/swift-corelibs-foundation/commit/a455cde38e06052385560d0a7c5aeb5a4991f844 However it appears that t