add Error() assertions on the final error value of multi-return value functions #480
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.
This PR follows up on #392, implementing a new
Error
method onAssertions
.Error
method toAssertion
, returning a newAssertion
configured for error-related assertions (see below for details).Error
-returnedAssertion
is configured to vet differently from non-error-related assertions in order to correctly handle the Go error idiom, where either (A) all return values must be zero values in case of a trailing non-nil error, or (B) there are no constraints on the return values when the trailing error value is nil.Error
.