Fixing the escape check to provide better errors #3105
Merged
Conversation
This file contains 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
Helps with debugging.
Otherwise, the call to try_teq is wrong as one of the terms cannot be typed in this environment. Also, wrap the whole thing in a try/catch, and if something fails we can just report that the variable escapes. Fixes FStarLang#3102.
|
Got an everest green locally, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes #3102, which I should have realized was a variable escaping in the type of the letbinding. But, the error message was bad since it was raising an internal failure instead of properly reporting the escape. A patch in this PR fixes it (ae3e0cd), and there's some other misc stuff too.