Feature: Option to enable auto-throwing of Result failures #7
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.
The way it works now, (or when using this in disabled mode once this gets merged), this is handled on a case-by-case basis within a given operation by unwrapping
Results using the built-inget()function, which either returns the value or throws on failure.This PR makes it so that you don't have to do this case-by-case, and instead can have the built-in error propagation just handle it automatically without the boilerplate check.
Here, the
Anchorchecks if it's value is aResult<_, Error>and then looks for a .failure. If one is found, it will automatically reroute it down the error path so that anyerrorHandlers and/oronErrortriggers can catch them as expected.This config will be enabled by default, but can be disabled using the
QLCommon.Config.Anchor.autoThrowResultFailuresglobal setting.