Adapting FiniteType to support constructors with multiple arguments #10
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.
It took me a while, but I figured out the problems of my first approach (see #2).
I turned out that
finite_surjective
was used as part of computations which get stuck once they encounter an opaque term/lemma. So the solution was basically to redefine all lemma dependencies using nothing than transparent terms.Now, we can finally derive
FiniteType
type classes for more complex (possibly even all finite) Inductive types.