[swift6][client] make api calls concurrent #22790
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 40 files
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="modules/openapi-generator/src/main/resources/swift6/APIs.mustache">
<violation number="1" location="modules/openapi-generator/src/main/resources/swift6/APIs.mustache:122">
P2: Guard the new `@concurrent` attribute with a Swift version check so generated code still compiles on Swift 6.0/6.1 toolchains.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
There was a problem hiding this comment.
2 issues found across 107 files (changes from recent commits).
Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="modules/openapi-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache">
<violation number="1" location="modules/openapi-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache:72">
P1: The new `T: Sendable` constraint on `URLSessionRequestBuilder` requires the factory method to also constrain `T` (and likely the `RequestBuilderFactory` protocol). Without that, returning `URLSessionRequestBuilder<T>.self` is ill-typed and fails to compile for non-Sendable types.</violation>
<violation number="2" location="modules/openapi-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache:322">
P1: The new `T: Decodable & Sendable` constraint on `URLSessionDecodableRequestBuilder` requires the factory method signature (and protocol) to include `Sendable`. Otherwise the return type no longer matches and compilation fails.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
...-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache
Show resolved
Hide resolved
...-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache
Show resolved
Hide resolved
# Conflicts: # modules/openapi-generator/src/main/resources/swift6/libraries/urlsession/URLSessionImplementations.mustache # samples/client/petstore/swift6/asyncAwaitLibrary/Sources/PetstoreClient/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/combineDeferredLibrary/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/combineLibrary/Sources/CombineLibrary/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/default/Sources/PetstoreClient/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/oneOf/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/promisekitLibrary/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/resultLibrary/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/rxswiftLibrary/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/urlsessionLibrary/Sources/PetstoreClient/Infrastructure/URLSessionImplementations.swift # samples/client/petstore/swift6/validation/PetstoreClient/Classes/OpenAPIs/Infrastructure/URLSessionImplementations.swift
There was a problem hiding this comment.
13 issues found across 36 files (changes from recent commits).
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Tag.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Tag.swift:10">
P2: Avoid `@unchecked Sendable` on this mutable class; it is not thread-safe. Either remove the unchecked conformance or make the type immutable/thread-safe before claiming Sendable.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/User.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/User.swift:10">
P2: `@unchecked Sendable` on a mutable class bypasses compiler safety checks and can introduce data races. Either make the model immutable or remove the unchecked conformance unless thread-safety is guaranteed.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/MapTest.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/MapTest.swift:10">
P2: `@unchecked Sendable` on a mutable reference type is unsafe because the class has `var` properties and no synchronization. This can introduce data races when instances are shared across tasks. Consider removing `@unchecked Sendable` or making the type immutable/actor-isolated.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/FileSchemaTestClass.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/FileSchemaTestClass.swift:10">
P2: `@unchecked Sendable` is unsafe here because the class has mutable properties and no thread-safety guarantees. Either make the model immutable and truly `Sendable` or remove the unchecked conformance to avoid implying safe cross-task sharing.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfArrayOfNumberOnly.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfArrayOfNumberOnly.swift:10">
P2: `@unchecked Sendable` is unsafe here because this class has mutable stored state with no synchronization. This can introduce data races when instances are passed across concurrency domains. Consider removing the unchecked conformance or making the type immutable/thread-safe.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Name.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Name.swift:11">
P2: Avoid marking this mutable reference type as `@unchecked Sendable` without guaranteeing thread safety. With public mutable vars, this can introduce data races when instances cross actor boundaries.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/OuterComposite.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/OuterComposite.swift:10">
P2: Avoid @unchecked Sendable on a mutable reference type without synchronization; it promises thread-safety that the class does not provide and can lead to data races when used concurrently.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Return.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Return.swift:11">
P2: `@unchecked Sendable` on a mutable reference type suppresses concurrency safety checks without enforcing thread safety, risking data races when instances are shared across tasks. Consider removing `@unchecked Sendable` or making the type immutable/actorsafe before declaring it sendable.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Animal.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Animal.swift:10">
P2: Avoid marking a mutable reference type as `@unchecked Sendable` unless it is actually thread-safe. This class has mutable `var` properties with no synchronization, so `@unchecked Sendable` can introduce data races when used across concurrency boundaries.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ReadOnlyFirst.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ReadOnlyFirst.swift:10">
P2: `@unchecked Sendable` on a mutable reference type with `var` properties can introduce data races when used across concurrency domains. Either make the type immutable or avoid declaring it `Sendable` without synchronization.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Cat.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Cat.swift:10">
P2: `@unchecked Sendable` is unsafe here because `Cat` is a mutable class with unsynchronized `var` properties. This advertises thread-safety that the type does not provide and can lead to data races when passed across concurrency domains.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfNumberOnly.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfNumberOnly.swift:10">
P2: Avoid marking a mutable reference type as `@unchecked Sendable` without enforcing thread safety. Either make the type immutable (e.g., `let` properties) or remove `@unchecked Sendable` to prevent unsafe cross-actor usage.</violation>
</file>
<file name="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Client.swift">
<violation number="1" location="samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Client.swift:10">
P2: `@unchecked Sendable` on this mutable reference type is unsafe without synchronization. Either make the model immutable (and use `Sendable`) or add synchronization around mutations instead of bypassing compiler checks.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| import Foundation | ||
|
|
||
| @objcMembers public class Tag: NSObject, Codable { | ||
| @objcMembers public final class Tag: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: Avoid @unchecked Sendable on this mutable class; it is not thread-safe. Either remove the unchecked conformance or make the type immutable/thread-safe before claiming Sendable.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Tag.swift, line 10:
<comment>Avoid `@unchecked Sendable` on this mutable class; it is not thread-safe. Either remove the unchecked conformance or make the type immutable/thread-safe before claiming Sendable.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class Tag: NSObject, Codable {
+@objcMembers public final class Tag: NSObject, Codable, @unchecked Sendable {
public var _id: Int64?
</file context>
Suggested change
| @objcMembers public final class Tag: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class Tag: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class User: NSObject, Codable { | ||
| @objcMembers public final class User: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable on a mutable class bypasses compiler safety checks and can introduce data races. Either make the model immutable or remove the unchecked conformance unless thread-safety is guaranteed.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/User.swift, line 10:
<comment>`@unchecked Sendable` on a mutable class bypasses compiler safety checks and can introduce data races. Either make the model immutable or remove the unchecked conformance unless thread-safety is guaranteed.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class User: NSObject, Codable {
+@objcMembers public final class User: NSObject, Codable, @unchecked Sendable {
public var _id: Int64?
</file context>
| import Foundation | ||
|
|
||
| @objcMembers public class MapTest: NSObject, Codable { | ||
| @objcMembers public final class MapTest: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable on a mutable reference type is unsafe because the class has var properties and no synchronization. This can introduce data races when instances are shared across tasks. Consider removing @unchecked Sendable or making the type immutable/actor-isolated.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/MapTest.swift, line 10:
<comment>`@unchecked Sendable` on a mutable reference type is unsafe because the class has `var` properties and no synchronization. This can introduce data races when instances are shared across tasks. Consider removing `@unchecked Sendable` or making the type immutable/actor-isolated.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class MapTest: NSObject, Codable {
+@objcMembers public final class MapTest: NSObject, Codable, @unchecked Sendable {
public enum MapOfEnumString: String, Sendable, Codable, CaseIterable {
</file context>
Suggested change
| @objcMembers public final class MapTest: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class MapTest: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class FileSchemaTestClass: NSObject, Codable { | ||
| @objcMembers public final class FileSchemaTestClass: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable is unsafe here because the class has mutable properties and no thread-safety guarantees. Either make the model immutable and truly Sendable or remove the unchecked conformance to avoid implying safe cross-task sharing.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/FileSchemaTestClass.swift, line 10:
<comment>`@unchecked Sendable` is unsafe here because the class has mutable properties and no thread-safety guarantees. Either make the model immutable and truly `Sendable` or remove the unchecked conformance to avoid implying safe cross-task sharing.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class FileSchemaTestClass: NSObject, Codable {
+@objcMembers public final class FileSchemaTestClass: NSObject, Codable, @unchecked Sendable {
public var file: File?
</file context>
Suggested change
| @objcMembers public final class FileSchemaTestClass: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class FileSchemaTestClass: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class ArrayOfArrayOfNumberOnly: NSObject, Codable { | ||
| @objcMembers public final class ArrayOfArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable is unsafe here because this class has mutable stored state with no synchronization. This can introduce data races when instances are passed across concurrency domains. Consider removing the unchecked conformance or making the type immutable/thread-safe.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfArrayOfNumberOnly.swift, line 10:
<comment>`@unchecked Sendable` is unsafe here because this class has mutable stored state with no synchronization. This can introduce data races when instances are passed across concurrency domains. Consider removing the unchecked conformance or making the type immutable/thread-safe.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class ArrayOfArrayOfNumberOnly: NSObject, Codable {
+@objcMembers public final class ArrayOfArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable {
public var arrayArrayNumber: [[Double]]?
</file context>
Suggested change
| @objcMembers public final class ArrayOfArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class ArrayOfArrayOfNumberOnly: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class Animal: NSObject, Codable { | ||
| @objcMembers public final class Animal: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: Avoid marking a mutable reference type as @unchecked Sendable unless it is actually thread-safe. This class has mutable var properties with no synchronization, so @unchecked Sendable can introduce data races when used across concurrency boundaries.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Animal.swift, line 10:
<comment>Avoid marking a mutable reference type as `@unchecked Sendable` unless it is actually thread-safe. This class has mutable `var` properties with no synchronization, so `@unchecked Sendable` can introduce data races when used across concurrency boundaries.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class Animal: NSObject, Codable {
+@objcMembers public final class Animal: NSObject, Codable, @unchecked Sendable {
public var _className: String
</file context>
Suggested change
| @objcMembers public final class Animal: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class Animal: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class ReadOnlyFirst: NSObject, Codable { | ||
| @objcMembers public final class ReadOnlyFirst: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable on a mutable reference type with var properties can introduce data races when used across concurrency domains. Either make the type immutable or avoid declaring it Sendable without synchronization.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ReadOnlyFirst.swift, line 10:
<comment>`@unchecked Sendable` on a mutable reference type with `var` properties can introduce data races when used across concurrency domains. Either make the type immutable or avoid declaring it `Sendable` without synchronization.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class ReadOnlyFirst: NSObject, Codable {
+@objcMembers public final class ReadOnlyFirst: NSObject, Codable, @unchecked Sendable {
public var bar: String?
</file context>
Suggested change
| @objcMembers public final class ReadOnlyFirst: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class ReadOnlyFirst: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class Cat: NSObject, Codable { | ||
| @objcMembers public final class Cat: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable is unsafe here because Cat is a mutable class with unsynchronized var properties. This advertises thread-safety that the type does not provide and can lead to data races when passed across concurrency domains.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Cat.swift, line 10:
<comment>`@unchecked Sendable` is unsafe here because `Cat` is a mutable class with unsynchronized `var` properties. This advertises thread-safety that the type does not provide and can lead to data races when passed across concurrency domains.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class Cat: NSObject, Codable {
+@objcMembers public final class Cat: NSObject, Codable, @unchecked Sendable {
public var _className: String
</file context>
Suggested change
| @objcMembers public final class Cat: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class Cat: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class ArrayOfNumberOnly: NSObject, Codable { | ||
| @objcMembers public final class ArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: Avoid marking a mutable reference type as @unchecked Sendable without enforcing thread safety. Either make the type immutable (e.g., let properties) or remove @unchecked Sendable to prevent unsafe cross-actor usage.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/ArrayOfNumberOnly.swift, line 10:
<comment>Avoid marking a mutable reference type as `@unchecked Sendable` without enforcing thread safety. Either make the type immutable (e.g., `let` properties) or remove `@unchecked Sendable` to prevent unsafe cross-actor usage.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class ArrayOfNumberOnly: NSObject, Codable {
+@objcMembers public final class ArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable {
public var arrayNumber: [Double]?
</file context>
Suggested change
| @objcMembers public final class ArrayOfNumberOnly: NSObject, Codable, @unchecked Sendable { | |
| @objcMembers public final class ArrayOfNumberOnly: NSObject, Codable { |
| import Foundation | ||
|
|
||
| @objcMembers public class Client: NSObject, Codable { | ||
| @objcMembers public final class Client: NSObject, Codable, @unchecked Sendable { |
There was a problem hiding this comment.
P2: @unchecked Sendable on this mutable reference type is unsafe without synchronization. Either make the model immutable (and use Sendable) or add synchronization around mutations instead of bypassing compiler checks.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At samples/client/petstore/swift6/objcCompatible/Sources/PetstoreClient/Models/Client.swift, line 10:
<comment>`@unchecked Sendable` on this mutable reference type is unsafe without synchronization. Either make the model immutable (and use `Sendable`) or add synchronization around mutations instead of bypassing compiler checks.</comment>
<file context>
@@ -7,7 +7,7 @@
import Foundation
-@objcMembers public class Client: NSObject, Codable {
+@objcMembers public final class Client: NSObject, Codable, @unchecked Sendable {
public var client: String?
</file context>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[swift6][client] make api calls concurrent
In preparation to Swift 6.2 NonisolatedNonsendingByDefault, we are making the api calls concurrent, to make sure we are doing the work in a background thread.
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)"fixes #123"present in the PR description)@jgavris (2017/07) @ehyche (2017/08) @Edubits (2017/09) @jaz-ah (2017/09) @4brunu (2019/11) @dydus0x14 (2023/06)
Summary by cubic
Make Swift 6 client API calls concurrent and strengthen thread safety for Swift 6.2’s NonisolatedNonsendingByDefault. Adds @Concurrent to async RequestBuilder.execute and marks core infrastructure as Sendable; bumps swift-tools-version to 6.2.
Refactors
Migration
Written for commit 0100044. Summary will update on new commits.