Abort early after type-checking malformed constraint guards#1695
Merged
RyanGlScott merged 2 commits intomasterfrom Jul 3, 2024
Merged
Abort early after type-checking malformed constraint guards#1695RyanGlScott merged 2 commits intomasterfrom
RyanGlScott merged 2 commits intomasterfrom
Conversation
RyanGlScott
force-pushed
the
issue1593-issue1693
branch
from
b46fffa to
6e417aa
Compare
yav
approved these changes
Jul 3, 2024
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.
Checking ill-typed constraint guards for exhaustivity can cause Cryptol to panic. If we detect any type errors after type-checking the guards, we now abort early and report any recorded errors instead of proceeding to check exhaustivity.
Fixes #1593. Fixes #1693.