[SR-2252] Making `URL.resourceSpecifier` unavailable makes `mailto:` URLs unusable

[beccadax]

Previous ID	SR-2252
Radar	None
Original Reporter	@beccadax
Type	Bug

Environment

Xcode 8 beta 4 (swiftlang-800.0.41.2), OS X 10.11.5 (15F34)

Additional Detail from JIRA

Votes	1
Component/s	Foundation
Labels	Bug, SDKOverlay
Assignee	None
Priority	Medium

md5: 814ae571937761d91f55e39691ec4779

Issue Description:

The Foundation overlay included with Xcode 8 beta 4 (swiftlang-800.0.41.2) marks the `resourceSpecifier` as "Unavailable" with the message "Use `path`, `query`, and `fragment` instead". However, when initialized with a `mailto` URL, none of these properties contains the email address. In fact, if you paste the following code into a REPL, you'll notice that no property contains the email address without the "mailto:" prefix:

import Foundation
let url = URL(string: "mailto:test@example.com")!
dump(url.absoluteString)
dump(url.relativeString)
dump(url.baseURL)
dump(url.absoluteURL)
dump(url.scheme)
dump(url.host)
dump(url.port)
dump(url.user)
dump(url.password)
dump(url.path)
dump(url.relativePath)
dump(url.fragment)
dump(url.query)

The relevant commit seems to be <swiftlang/swift@05778cc9aba3eab2576786e4008a7bce0e0d43b9\>.

[swift-ci]

Comment by David Liu (JIRA)

please update and check again this issue seems resolved resourceSpecifier is part of the working API

Edit:
Nvm Brent you are correct this is still an issue with the Overlay

[swift-ci]

Comment by John Jacob Jingleheimer Schmidt (JIRA)

I believe that `path` should contain the mail address in this case, according to RFC 3986. But it seems like URL doesn't recognize any path that doesn't begin with / (forward slash), even though the RFC only requires a beginning slash for URIs that include an authority component.

[swift-ci]

Comment by Charlie Monroe (JIRA)

There seems to be a discrepency between URL and URLComponents:

let url = URL(string: "mailto:test@example.com")!
url.path // ""

let components = URLComponents(url: url, resolvingAgainstBaseURL: false)!
components.path // mailto:test@example.com

[futuretap]

Is there a particular reason why resourceSpecifier is unavailable? Seems like a strange regression.