YR Chen

It's super unfortunate that stack trace on Windows doesn’t contain symbol names. Any suggestions for further debugging?

> Note that the assertion could be a side effect of manually adding the clang headers to the module path; it isn't necessarily relevant to the original build failure. I...

I'm going to close the issue with the following conclusions: - `Atomics` is not compatible with Visual Studio 2019 and older. Use VS 2022 instead. - A problem within toolchain...

When trying to adopt `Atomics` in Swift NIO, we see CI failure because of missing `Sendable` conformance in Swift 5.5, where `@preconcurrency` is not supported. Since we cannot drop 5.5...

apple/swift#40340

This is a generally high-level layout that can be used beyond simple system programming. eg, `[email protected]:/bin/sh` can be parsed into root `[email protected]:/` and components `["bin", "sh"]` (and the latter may...

> It's my understanding that this library should wrap the C std lib APIs, like Foundation is a wrapper for CoreFoundation, ICU, cURL and libXML. Nope. `SwiftSystem` is a wrapper...

> How about this case: > > ```swift > myFunc(x: 1, > closure: { > return true > }) > ``` > > ? I think this is okay (give...

The code could be prettier if we didn’t force a closure to be multi-lined, so the following is allowed: ```swift myFunc({ return true }) ``` which eliminates the need for...

This should be properly solved by buffering (and implementing `ReadAt`), which can allow the MinIO client to re-read some part of the LFS object when recovering from a network problem....