Skip to content
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

Add large example at the end of the manual #195

Closed
atomb opened this issue May 2, 2017 · 2 comments · Fixed by #816
Closed

Add large example at the end of the manual #195

atomb opened this issue May 2, 2017 · 2 comments · Fixed by #816
Labels
documentation Issues involving documentation
Milestone

Comments

@atomb
Copy link
Contributor

atomb commented May 2, 2017

The current version of the manual ends rather abruptly, and doesn't show examples of some of the more advanced features. It would be nice to conclude it with a large-ish example of compositional verification of some Java or C program to tie all of the previous sections together.

@atomb atomb added the documentation Issues involving documentation label May 2, 2017
@atomb atomb added this to the 1.0 milestone Jun 4, 2019
@atomb atomb modified the milestones: 0.5, 0.6 Apr 24, 2020
@ChrisEPhifer
Copy link
Member

@atomb Do you have any ideas on what you might like this larger example to be? I'd be happy to both work on the verification task & document my process to supplement the manual, but I can't say I have any super good ideas on what that verification task should actually be :)

@atomb
Copy link
Contributor Author

atomb commented Aug 11, 2020

I don't have any really good ideas. To take an example that already exists, it could be reasonable to use examples/salsa20. It's a case where, if you want to prove it for just one size, doing things monolithically is faster (at least last time I tried; this sort of thing changes all the time) but if you want to prove multiple sizes then proving all the fixed-size functions first and then just iterating over the top-level function for multiple sizes is faster. So it's a sort of interesting demonstration of where it can be useful (but it's not an example of the case where monolithic verification is infeasible, even though such examples exist).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issues involving documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants