Karl

@CTMacUser Yes, good catch!

> `OverlayCollection.makeIndex(_:)` can't work if the source collections use the same `Index` type, because then the two overloads would have identical signatures. Possible fix: explicitly use the words "base" or...

@natecook1000 Thoughts?

Awesome! Is this syntax compatible with DocC? I still need to fix the documentation workflow on this repo. I think it broke due to GitHub updating the version of Node...

It seems that there has been recent work on supporting cross-module links in DocC: https://github.com/apple/swift-docc/pull/710 Of course I'd want to use something that is DocC-compatible, and it would be unfortunate...

Yeah, this is a bit of an arbitrary restriction, to be honest. My recollection is that this was inspired by servo/rust-url, which intentionally blocks them (https://github.com/servo/rust-url/issues/720). I asked why, but...

Ugh the reason for the failing "build-only macos" build (`error: cannot specialize protocol type 'Collection'`) is that it uses the default Xcode version, which on GHA runners is 14.0.1 [for...

The main issue is getting a good quality timestamp. IMO the spec is a little bit ambiguous, because the section on UUIDv7 says the timestamp should be: > the number...

I think conceptually the idea is that we don't want to couple the hostnames of special URLs _too tightly_ with DNS, although I don't think it is well defined (long-standing...

Sure. For creation, we have: `NSURL(absoluteURLWithDataRepresentation:relativeTo:)`, whose [implementation](https://github.com/apple/swift-corelibs-foundation/blob/04ddb8ebe4c6fd017abef1920116b038b72133bd/Sources/Foundation/NSURL.swift#L286) forwards to the same CFURL function that is currently used. ```swift NSURL(absoluteURLWithDataRepresentation: Data("https://example.com?q=1|2".utf8), relativeTo: nil) as URL $R34: Foundation.URL = "https://example.com?q=1|2" ^...