errbase: prevent a call cycle for Formatter/SafeFormatter errors #90
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.
Fixes #88.
We've found a need somewhere to implement an
Error()
method on aleaf by delegating the behavior to the
Formatter
orSafeFormatter
interfaces. In that case, the
errors.IsAny
call inside thespecial handler causes a call cycle.
This commit breaks the cycle by handling the special cases after
the interfaces.
A possible regression would be that one of the stdlib errors
starts implementing
fmt.Formatter
, whereby we'd lose the specialhandling (which, as of this writing, extracts safe strings).
At the time of this writing, none of the stdlib errors of interest
implement
fmt.Formatter
, so we're punting dealing with thatwhen/if it arises in the future.
This change is