-
Notifications
You must be signed in to change notification settings - Fork 632
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
Shrink Proofs/Obligations by default and deprecate option #218
Commits on Jun 27, 2016
-
Configuration menu - View commit details
-
Copy full SHA for acb40a0 - Browse repository at this point
Copy the full SHA acb40a0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6ffb187 - Browse repository at this point
Copy the full SHA 6ffb187View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0ce92e8 - Browse repository at this point
Copy the full SHA 0ce92e8View commit details -
Shrink Proofs/Obligations by default and deprecate
Fix bug in Shrink obligations with Program in the process.
Configuration menu - View commit details
-
Copy full SHA for 4952664 - Browse repository at this point
Copy the full SHA 4952664View commit details -
Fix implementation of shrink for abstract proofs
- Update doc in term.mli to reflect the fact that let-in's are part of what is returned by [decompose_lam_assum].
Configuration menu - View commit details
-
Copy full SHA for 6967e85 - Browse repository at this point
Copy the full SHA 6967e85View commit details -
Add Unset Shrink Abstract/Obligations in Coq85
For compatibility with 8.5.
Configuration menu - View commit details
-
Copy full SHA for 2056e54 - Browse repository at this point
Copy the full SHA 2056e54View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3b594da - Browse repository at this point
Copy the full SHA 3b594daView commit details -
Rework treatment of default transparency of obligations
By default obligations defined by tactics are defined transparently or opaque according to the Obligations Transparent flag, except proofs of subset obligations which are treated as opaque by default. When the user proves the obligation using Qed or Defined, this information takes precedence, and only when the obligation cannot be Qed'ed because it contains references to a recursive function an error is raised (this prevents the guardness checker error). Shrinked obligations were not doings this correctly.
Configuration menu - View commit details
-
Copy full SHA for 6140d62 - Browse repository at this point
Copy the full SHA 6140d62View commit details -
Fix semantics of obligation status.
Forcing transparency due to fixpoint prototypes takes precedence over the user preference.
Configuration menu - View commit details
-
Copy full SHA for e12e74b - Browse repository at this point
Copy the full SHA e12e74bView commit details -
Program: refine shrinking of obligations
Ensure correspondence between the term and type to shrink, so that Lets are preserved when they are used relevantly in either of them. This avoids e.g. "simpl" in the shrinked hypotheses to reduce shrinking, while maintaining unsimplified types in the type of the shrinked obligations (for compatibility).
Configuration menu - View commit details
-
Copy full SHA for 4109c88 - Browse repository at this point
Copy the full SHA 4109c88View commit details -
Program: do not force opacity of subset proofs
This maintains compatibility.
Configuration menu - View commit details
-
Copy full SHA for ea7336d - Browse repository at this point
Copy the full SHA ea7336dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4a0eecd - Browse repository at this point
Copy the full SHA 4a0eecdView commit details -
Simplify Lambda, Prod case of shrinking
By invariant (we start with a term and its type), the abstraction's types correspond.
Configuration menu - View commit details
-
Copy full SHA for 8f686e6 - Browse repository at this point
Copy the full SHA 8f686e6View commit details