Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mrousavy
force-pushed
the
mrousavy/v1-async-callback-call-operator
branch
from
October 20, 2026 19:10
6c99f22 to
7ec7337
Compare
mrousavy
force-pushed
the
mrousavy/v1-async-callback-call-operator
branch
from
October 20, 2026 19:18
7ec7337 to
326c296
Compare
mrousavy
force-pushed
the
mrousavy/v1-async-callback-call-operator
branch
from
October 20, 2026 19:20
326c296 to
781939e
Compare
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add an
async throwscall operator for Swift callbacks solet value = try await callback()awaits the result and propagates errors. It uses the same implementation andSendableresult constraint as the existing asynccallAsync()overload.Includes a
Voidspecialization so typedVoidexpressions also await the callback and propagate errors. Swift prefers the async overload inside async functions; usecallAndForget()explicitly for fire-and-forget calls there. Synchronous call-operator behavior is unchanged.Update existing standalone callers and the callback docs. Nitrogen regeneration produces no changes.
Validation: compiler probes cover 24 cases each in Swift 5 and Swift 6. Runtime checks in both modes cover successful results, thrown errors,
Void, typedVoid,async let, and multiple arguments. The standalone iOS suite and all 13 React Native harness tests pass with the updated callers.