You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.
Wrap() and Wrapf() are good example of annotating error with stack trace and given error message. Wrap() and Wrapf() are best option if errors comes in different labels(different function). If errors are in same label(same function) then we can have an option to merge those errors in a single error annotating with extra message.
The text was updated successfully, but these errors were encountered:
shovanmaity
changed the title
Proposal: add support for merging more than one error using merge() and mergef() like wrap() and wrapf()
Proposal: add support for merging more than one errors using merge() and mergef() like wrap() and wrapf()
Apr 24, 2019
What's the use case for recording an error, continuing execution within the same function and subsequently merging that original error with other error(s)?
Typically you'd want check for an error and either handle it or return it up the call stack. Wrapf solves annotation and type preservation at the site of the original error.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Wrap()
andWrapf()
are good example of annotating error with stack trace and given error message.Wrap()
andWrapf()
are best option if errors comes in different labels(different function). If errors are in same label(same function) then we can have an option to merge those errors in a single error annotating with extra message.The text was updated successfully, but these errors were encountered: