YR Chen

For main docsets and cheat sheets, maybe you can maintain an XML feed especially for the sizes of each docset and cheatsheet? For 3rd-party ones, maybe sizes can be integrated...

Is the newly released [swift-collections-benchmark](https://github.com/apple/swift-collections-benchmark) suitable for such case? I thought that’s exactly the one we need.

In a real-world case, we could have a couple of offices referenced by `city+number`, and a number of employees each tied to one office. Of course this could be resolved...

> can you give me some examples of environment variables that affect swift build and swift package manager operations? Most of them control lookup path(s) for tools and libraries, and...

It feels like the VS Code pattern (current) is more precise🤔 SwiftPM is resolving packages using their identifier instead of package name now. This means there could be packages with...

> For example, when you reference a product in a target dependency you use the package name. If they weren't unique that would be problematic. I believe identifier is used...

@adam-fowler I believe `package:` should take package identifier instead of its "name" here. The `name:` field in `Package.swift` is not intended to be used any more. It’s clearly marked as...

> @stevapple well that isn't what the swift-realm is doing https://github.com/realm/realm-swift/blob/master/Package.swift It is using a deprecated API with ```swift dependencies: [ .package(name: "RealmDatabase", url: "https://github.com/realm/realm-core", .exact(Version(coreVersionStr)!)) ], ``` which explicitly...

> @stevapple > RealmDatabase is the package name > the url last component is the identifier if im correct, the name could mean more to me > (my question was...

> it seems the identifier/product name/target should be unique somehow that are handled by SwiftPM and engineers As you can see, manifest name does nothing here. SwiftPM only cares about...