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

Assertions in the runtime library for obvious preconditions and proof obligations #118

Closed
bandurvp opened this issue Sep 28, 2017 · 2 comments
Assignees
Milestone

Comments

@bandurvp
Copy link
Contributor

The Continental model revealed that

  • proof obligations are not discharged in a standard modelling activity such as theirs
  • simple assertions for the obvious cases of non-existent keys, heads of empty lists etc. in the runtime library would be extremely useful

In this issue we should add support for obvious proof obligations and preconditions in the runtime library. The preferred assert statement is assert(condition && message_text). @peterwvj this is my responsibility, but any thoughts otherwise?

@bandurvp bandurvp added this to the v0.1.18 milestone Sep 28, 2017
@bandurvp bandurvp self-assigned this Sep 28, 2017
@peterwvj
Copy link
Member

peterwvj commented Oct 2, 2017

I'm OK with adding those checks. It's similar to the assertions we've already added to ensure that the TVPs passed to certain functions carry the right types (e.g. the runtime version of + expects numbers).

@bandurvp
Copy link
Contributor Author

bandurvp commented Oct 2, 2017

Yeah, that's the kind of check that's missing in some parts of the runtime. I'll add those now.

bandurvp added a commit that referenced this issue Oct 2, 2017
@bandurvp bandurvp closed this as completed Oct 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants