v1 #4
Merged
v1 #4
Conversation
This file contains 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
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.
After a bunch of experimentation with the sub-packages in this repo (errctx, and friends) I've figured out all the pain points and requirements for a fully fledged error library with all the bells and whistles.
Wrapcurrently just calls all the wrappers in-series on the error value. But the plan is to provide a bunch of basic functionality that one would expect from an error library, most notably: stack traces. Which will likely take a lot of inspiration from eris but in a compact and less opinionated way.It's going to look a lot like the original fault library, but with the added bonus of composable wrappers to decorate the error with additional information in various ways!