Improved support of mutually (recursive) nominal datatypes #1421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #1418 (@mn200's own work).
In case multiple mutually recursive nominal types are being defined, the newly added "witnesses" argument of the API function
new_type_step1
provides a list ofgenind_exists
theorems generated from previous calls to the same function, otherwise the proof ofterm_exists
may not succeed.As a sample application of the improve
nomdatatype
package, I added the initial theory of my ongoing pi-calculus work, inexamples/formal-languages/pi-calculus
. There are totally 3 nominal types (mutual but not recursive), expressed in future APINominal_datatype
:Below are the basic tpm and induction theorems for the
:pi
type and theFV
function for getting free variables:The following theorems show the (correct) built-in alpha conversion of the
Input
andRes
constructors: