Include support for the definition of implicit invariants#3
Open
esebastian wants to merge 1 commit intonoflopsquad:masterfrom
Open
Include support for the definition of implicit invariants#3esebastian wants to merge 1 commit intonoflopsquad:masterfrom
esebastian wants to merge 1 commit intonoflopsquad:masterfrom
Conversation
Member
|
I like it |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It occurred to me that in some cases it would be nice if the invariants could also be declared inline, as a block (the return value of the block will determine if the invariant holds or not).
I'm calling the existing mechanism 'explicit' (a method is declared) and I'm calling the new one 'implicit' (the invariants are written in a block, no method declaration needed).
I've kept both alternatives mutually exclusive to avoid precedence problems.