Results 433 comments of Max Desiatov

https://github.com/swiftlang/swift-package-manager/pull/7722 @swift-ci build toolchain

https://github.com/apple/swift-package-manager/pull/7450 https://github.com/apple/swift-driver/pull/1578 https://github.com/apple/swift/pull/72949 @swift-ci smoke test

https://github.com/apple/swift-package-manager/pull/7450 https://github.com/apple/swift-driver/pull/1578 https://github.com/apple/swift/pull/72949 @swift-ci test

https://github.com/apple/swift-package-manager/pull/7450 https://github.com/apple/swift-driver/pull/1578 https://github.com/apple/swift/pull/72949 @swift-ci test

https://github.com/apple/swift-package-manager/pull/7450 https://github.com/apple/swift-driver/pull/1578 https://github.com/apple/swift/pull/72949 @swift-ci test

> The underlying issue is SPM. It does not have the concept of libraries, and the code is built incorrect. The result of that is that we try to export...

This could also be platform-dependent, Apple documentation doesn't cover swift-corelibs-libdispatch, which largely lacks `Sendable` annotations for vast majority of its types.

Same here, metrics not updated for https://cocoapods.org/pods/XMLCoder and https://cocoapods.org/pods/CoreXLSX

Having an explicit `LICENSE` file would make this more obvious. The link to the license file if one is present (and even the name of the license if detected correctly)...

I can confirm that running `wasm-strip` from [wabt](https://github.com/WebAssembly/wabt) and `wasm-opt -Os` from [binaryen](https://github.com/WebAssembly/binaryen) (in this order, `wasm-opt` seems to choke on raw binaries produced by `swift build` without having `wasm-strip`...