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

Assume now accepts impure assertions #1

Open
viper-admin opened this issue Jun 20, 2019 · 1 comment
Open

Assume now accepts impure assertions #1

viper-admin opened this issue Jun 20, 2019 · 1 comment
Labels
bug Something isn't working major

Comments

@viper-admin
Copy link
Member

Created by @fabiopakk on 2019-06-20 12:44

https://github.com/viperproject/tutorial/issues/162 states that assume is being translated to inhale and is therefore inadvertently allowing impure assertions to be used with assume. As the discussion in https://github.com/viperproject/tutorial/issues/162 shows, this description is outdated and impure assertions are now supported in assume. However the Viper tutorial still states the opposite.

When fixing this part of the tutorial, please refer to https://github.com/viperproject/tutorial/issues/162 in Silver for further references to the work that implemented such extension.

@viper-admin viper-admin added bug Something isn't working major labels Apr 6, 2020
@Aurel300 Aurel300 mentioned this issue Jul 14, 2022
5 tasks
@Aurel300
Copy link
Member

@alexanderjsummers Can you comment on the resolution here? The linked discussion is a bit confusing. The tutorial currently states (wrongly):

  • assume E is equivalent to inhale E; note that it takes an expression rather than an assertion, which must not contain resource assertions such as accessibility predicates; this restriction may be lifted in future versions of Viper.

I think even saying "is equivalent to" is wrong, because assume acc(...) is different from inhale acc(...), right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major
Projects
None yet
Development

No branches or pull requests

2 participants