Adapt to new hax naming. #774
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
26 tasks
maximebuyse
force-pushed
the
adapt-to-new-hax-naming
branch
from
4932e37 to
3ce9b09
Compare
…patible with new hax naming.
maximebuyse
force-pushed
the
adapt-to-new-hax-naming
branch
from
3ce9b09 to
4602719
Compare
franziskuskiefer
approved these changes
Jan 30, 2025
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 removes some hardcoded names in raw fstar strings. We use the $ feature of hax-lib to make this more robust. With this changes, the extracted code lax-checks with both hax main and cryspen/hax#1199.
In some places, we need to use a workaround documented in cryspen/hax#1276 (comment)