Return Never from requireFail #1194
Open
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.
I want to use
requireFail
in some test cases whererequire
doesn't feel right. The problem is that while it's guaranteed to throw, the code doesn't know that, so it can't be used in a guard statement.For example, the following code has a compiler error "'guard' body must not fall through, consider using a 'return' or 'throw' to exit the scope"
I've been getting around this locally with a simple wrapper:
We can improve
requireFail
by simply adding theNever
return type. When compiling Nimble, Swift validates thatrequireFail
does indeed always throw and when compiling tests, it knows no code will ever execute afterrequireFail
.This is an API change but should be source compatible. Any code below a
requireFail
call will receive a "Will never be executed" warning but still compile.Checklist - While not every PR needs it, new features should consider this list: