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

Use variable order in {:inductive} attribute. #34

Open
richardlford opened this issue Sep 27, 2016 · 1 comment
Open

Use variable order in {:inductive} attribute. #34

richardlford opened this issue Sep 27, 2016 · 1 comment
Labels
difficulty: easy Issues that should take a few days at most to fix kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny part: verifier Translation from Dafny to Boogie (translator) priority: not yet Will reconsider working on this when we're looking for work status: designed Issues that have a complete story on how to implement this feature and why we want it

Comments

@richardlford
Copy link
Collaborator

Induction can be applied in two contexts:

  • A method, in which case the potential induction variables are all the in-parameters
  • A quantifier expression, in which case the potential induction variables are the bound variables
    of the quantifier expression.

The {:inductive} attribute is used to specify that only a subset of the potential
inductive variables be used. The current implementation requires that the given subset
be listed in the same order as they appear in the potential induction variables list.
But there does not seem to be a good reason for this restriction.

We propose that this restriction be removed and that induction be applied in the order
specified in the {:induction} attribute.

@seanmcl seanmcl added the kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny label Jul 1, 2019
@acioc
Copy link
Collaborator

acioc commented Jul 8, 2020

Investigation if this is still an issue is for 3.0

@acioc acioc added this to the Dafny 3.0 milestone Jul 8, 2020
@davidcok davidcok modified the milestones: Dafny 3.0, Dafny 3.1 Dec 23, 2020
camrein added a commit that referenced this issue Apr 8, 2021
…ion-tests

Added integration tests for the signature help.
@atomb atomb removed this from the Dafny 3.1 milestone Apr 21, 2022
@cpitclaudel cpitclaudel added part: verifier Translation from Dafny to Boogie (translator) status: designed Issues that have a complete story on how to implement this feature and why we want it difficulty: easy Issues that should take a few days at most to fix labels May 11, 2022
@MikaelMayer MikaelMayer added the priority: not yet Will reconsider working on this when we're looking for work label Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: easy Issues that should take a few days at most to fix kind: enhancement Enhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafny part: verifier Translation from Dafny to Boogie (translator) priority: not yet Will reconsider working on this when we're looking for work status: designed Issues that have a complete story on how to implement this feature and why we want it
Projects
None yet
Development

No branches or pull requests

7 participants