Merged
Conversation
The inferred type of this projection does not even type check, in general.
The eta-expansion contains invalid projections, and the eta-rule is subsumed by proof irrelevance anyhow.
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 removes two more occurrences in the kernel where invalid projections where generated.
(_ : ∃ x, p).2type checked, and the resulting type contained.1.(_ : ∃ x, p).1.I ran into the these errors when running mathport with the latest nightly. To stay clear of these issues in the future, we might want to restrict primitive projections to structures in Type, and add an explicit flag for projection support to InductiveVal so that we're using the same condition everywhere.