[WIP] Verify send guard in Run #249
Closed
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
|
@mlimbeck can you remind me what are the lemmas that need to be proven to complete the checks for the guard? Maybe, it would make sense to merge the IO spec branch here and to merge this PR in that branch soon to avoid a proliferation of merge conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contains the current progress of verifying the send guard in the run method.
Still missing:
absIO_val(dp, msgs[i].Buffers[i], ingressID, msgs[i].N) == absIO_val(dp, tmpBuf, ingressID, msgs[i].N)absIO_valDummy())SplitRange_Bytesin Run