-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proof of SetHopField #361
Proof of SetHopField #361
Conversation
pkg/slayers/path/scion/raw.go
Outdated
// @ ensures acc(s.Mem(ubuf), R20) | ||
// @ ensures sl.Bytes(ubuf, 0, len(ubuf)) | ||
// @ ensures r != nil ==> r.ErrorMem() | ||
// posts for IO: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm starting to feel like these "posts for IO" annotations are a bit misleading, mostly because they are not about the IO behaviour, but instead about functional properties of the function. It just so happens that the correctness of the IO behaviour is predicated on the functional correctness of the packet processing. @Dspil would you be ok with us dropping these annotations, or do you think that it will still be useful for you to have the comments here?
@mlimbeck can you disable moreJoins for |
To avoid this bit-rotting, I will now merge it. We can debug the perf. issues later |
No description provided.