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

Dafny should issue a warning when an annotation is not supported #395

Open
mschlaipfer opened this issue Oct 18, 2019 · 1 comment
Open
Labels
kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny

Comments

@mschlaipfer
Copy link
Member

mschlaipfer commented Oct 18, 2019

In https://stackoverflow.com/questions/58310238/assertion-violation-in-mvs-with-dafny-but-it-is-verified-in-rise4fun a user tries to use {:arith 2} in assert {:arith 2} forall b,e,x,t,p :: (0 <= t <= e && p * power(x,t) == power(b,e) && t > 0 ) ==> (0 <= t-1 <= e && p * x * power(x,t-1) == power(b,e)); instead of the flag -arith:2. {:arith 2} has no effect. Dafny should probably issue a warning in such cases.

@acioc acioc added kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny and removed should be warning labels Jun 22, 2020
@acioc acioc modified the milestones: Dafny 3.0, Post 3.0 Aug 12, 2020
@davidcok
Copy link
Collaborator

The implementation issue here is that checks for attributes simply ask whether a given attribute relevant at some program point is in the list of attributes for the entity in question. And those checks are very distributed. There is no central list (in the implementation) of the strings used as attributes.

@robin-aws robin-aws removed this from the Post 3.1 milestone Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny
Projects
None yet
Development

No branches or pull requests

4 participants