Added error 'lift' operator that more ergonomically handles mixed error types via combined enum#1830
Merged
kperryua merged 1 commit intoswiftlang:experimental/new-codablefrom Mar 25, 2026
Conversation
…or types via combined enum
kperryua
force-pushed
the
mixed-typed-errors
branch
from
328d186 to
849f8bd
Compare
Contributor
Author
|
Merging this major infrastructural change to avoid further drifting. |
kperryua
merged commit 2c56c4d
into
swiftlang:experimental/new-codable
18 of 19 checks passed
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
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.
Per #1825, improve the ergonomics of
JSONErrorandCodingError.Decodingerrors being mixed in recursive JSON parsing. This also eliminates theas!cast that we currently are using to get by, but which isn't compatible with Embedded Swift.Wishing for better language support here. This pattern being implicitly sugared into the language would be great. But I'd settle for changes to the typed throws inference / overload disambiguation mechanisms that would allow this bespoke operator to be postfix-unary.