Karl

> Thats fair, I guess its a personal preference but I do see the logic of what you are saying. My logic was that since its the preferred way to...

I think it would be better if these went the other way - i.e. in Foundation. The reason is that the natural layering of these 2 libraries would have swift-system...

So a couple of things: - We can define our own IP address storage types. There's nothing system-specific about them. - Similarly, constants like loopback addresses are not system-specific; they...

It sounds like a good idea to decode them, IMO. The [latest HTTP semantics draft spec](https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#rfc.section.4.2.3) says: > Scheme-based normalization (Section 6.2.3 of [RFC3986]) of "http" and "https" URIs involves...

We already define that `%2E` and `%2e` are equivalent to `.` in path components (even a mixed component like `.%2E` is treated equivalently to `..`). We also _add_ percent-encoding for...

I'm currently exploring implementing this in Swift, as over-encoding/removing over-encoding is an important feature for interop with our existing RFC-2396 URL type, as well as a generally useful feature. Having...

@alwinb As for why this is the way it is, my guess is that, since it only affects Windows users, and both Chrome and Edge support `file://localhost/SomeShare`, it just hasn't...

I think the `missing-credentials` error is incorrect. That error occurs if there is an `@` but no host. `https://@test.com` should not cause the parser to fail, but `https://username:password@` should (and...

CC @MattMenke2 who created the original issue

I apologise for the bump, and I'd be happy to open a new issue if that would be better. But I've also encountered an issue with the UTS46 tests. Is...