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

Abduction: another way to detect bad applications of induction #194

Open
yutakang opened this issue May 8, 2023 · 1 comment
Open

Abduction: another way to detect bad applications of induction #194

yutakang opened this issue May 8, 2023 · 1 comment

Comments

@yutakang
Copy link
Collaborator

yutakang commented May 8, 2023

  1. We apply the induct tactic.
  2. We get a step case whose shape looks like induction_hypothesis ==> conclusion.
  3. Take conclusion from this step case.
  4. Apply clarsimp to the conclusion`.
  5. If there is a remaining goal, then call it conclusion1, else decide that the induction was not bad.
  6. Apply clarsimp to the entire step case induction_hypothesis ==> conclusion.
  7. If there is a remaining goal of the form of induction_hypothesis2 ==> conclusion2, then take conclusion2, else decide that the induction was not bad.
  8. Compare conclusion1 against conclusion2.
  9. If they are different, then decide that the induction was not bad, else the induction was not useful.

If at least one subgoal is "was not bad", then the induction was "useful".

@yutakang
Copy link
Collaborator Author

I need a concrete example for this.

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

No branches or pull requests

1 participant