Proposal: Result Codable conformance and async init #2741
+83
−0
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
j-f1
reviewed
Mar 17, 2025
YOCKOW
reviewed
Mar 17, 2025
YOCKOW
reviewed
Mar 17, 2025
YOCKOW
reviewed
Mar 17, 2025
Co-authored-by: YOCKOW <YOCKOW@users.noreply.github.com>
Co-authored-by: YOCKOW <YOCKOW@users.noreply.github.com>
|
Thanks for the fixups :) |
rjmccall
added
the
LSG
grynspan
reviewed
Mar 20, 2025
| /// | ||
| /// - Parameter body: A potentially throwing asynchronous closure to evaluate. | ||
| @_alwaysEmitIntoClient | ||
| public init(catching body: () async throws(Failure) -> Success) async { |
m1guelpf
reviewed
Aug 12, 2025
|
|
||
| ## Motivation | ||
|
|
||
| The Result type is often used to bridge between async and not async contexts, and it may be useful to initialize a `Result` from the result of an async computation, to then pass it along to other non-async code without unwrapping it first. This is currently inconvenitnt because the `init(catching:)` initializer is missing an `async` overload. |
There was a problem hiding this comment.
Suggested change
| The Result type is often used to bridge between async and not async contexts, and it may be useful to initialize a `Result` from the result of an async computation, to then pass it along to other non-async code without unwrapping it first. This is currently inconvenitnt because the `init(catching:)` initializer is missing an `async` overload. | |
| The Result type is often used to bridge between async and not async contexts, and it may be useful to initialize a `Result` from the result of an async computation, to then pass it along to other non-async code without unwrapping it first. This is currently inconvenient because the `init(catching:)` initializer is missing an `async` overload. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This is a proposal to add:
catching:initThe combination of those allows "catching" an async computation and have the result be Codable if the error also was.