Jon Shier

Looks like this is a known Swift runtime issue, unfortunately: https://github.com/swiftlang/swift/issues/75952 I haven't been able to find a workaround yet, even using the older, deprecated version of `withTaskCancellationHandler` is crashing...

I've pushed a `bug/xcode16-cancellation-handler-crash` branch which remove the cancellation handler in that call altogether, so that, in combination with passing `automaticallyCancelling: false` to any async `serializing*` methods, should avoid the...

One other thing to check: make sure you're compiling in Release mode (or a configuration with Release in the name, Xcode uses name matching to turn on release optimizations in...

Looks like this is a known issue and is already [fixed](https://github.com/swiftlang/swift/pull/76218) for what will hopefully be the upcoming Swift 6.0.1 release. They haven't announced anything but hopefully the release won't...

This has been resolved in newer versions of Xcode (and by dropping support for beta OS versions).

One complication for such a rule would be distinguishing between Swift 6 in Swift 6 mode and Swift 6 in Swift 5 mode, as there's no `--swiftversion` which refers to...

It allows you to detect enumerated versions directly, otherwise you need to have other checks. ```swift #if swift(>=6) // Swift 6+ compiler in Swift 6 mode. #elseif compiler(>=6) // Swift...

If you did want to that, it should probably be a separate setting or a configuration option separate from the collection values.

> `String(decoding: data, as: UTF8.self)` may panic at runtime if `data` cannot be represented as UTF-8. This just isn't true, `String(decoding:as:)` will insert the replacement character (repair the string) as...

Thanks for the PR! Thinking about this I think we need to keep the same logic given existing users of the library. In the future we may reevaluate that choice,...