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 is the first step in a possible solution to #621.
Currently there's this very loose contract between subjects, verifiers and matchers. At the moment it's possible to pair any kind of subject with any kind of verifier. One problem with this is that a plain old subject can be added to an async verifier, even though it's not possible for the subject to be re-evaluated multiple times.
This is the first simplification of the set of types conforming to
KWVerifying
.Also, because this is a breaking change, I've created a new
3.0-development
branch, which this PR targets. It's going to be helpful to have a place that's safe to put these changes!