Make post-Returns callback delegate validation more strict
#876
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
stakx
force-pushed
the
callback-after-returns-delegate-validation
branch
from
7d08f7c
to
cde585c
Compare
stakx
force-pushed
the
callback-after-returns-delegate-validation
branch
from
cde585c
to
814685b
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 in response to, and closes, #872.
There's currently an inconsistency regarding how
Callbackdelegates are validated: In the post-Returnsposition, validation is very relaxed, while it's more strict in a pre-Returnsor no-Returnsscenario.This makes
Callbackdelegate validation strict regardless ofCallback's position in the setup.