Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should Fox have an Empty-preserving variant of ?~>? #7141

Closed
fm3 opened this issue Jun 14, 2023 · 0 comments · Fixed by #7137
Closed

Should Fox have an Empty-preserving variant of ?~>? #7141

fm3 opened this issue Jun 14, 2023 · 0 comments · Fixed by #7137
Labels
backend discussion refactoring

Comments

@fm3
Copy link
Member

fm3 commented Jun 14, 2023

?~> wraps Failures and Emptys in a new Failure with the argument error message prepended in the chain.

Some use cases have come up when we only want to add the message in failure case, but leave Empty as is.

Should this become the default behavior? Or should there be two variants of this? We should have a look
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend discussion refactoring
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Async IO for HttpsDataVault, Fox Error Handling scalableminds/webknossos
1 participant
@fm3