Update charon #357
Merged
Update charon #357
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
sonmarcho
reviewed
Nov 14, 2024
sonmarcho
reviewed
Nov 14, 2024
sonmarcho
reviewed
Nov 14, 2024
sonmarcho
approved these changes
Nov 14, 2024
Nadrieril
force-pushed
the
update-charon
branch
from
209a8a2
to
4a53ba6
Compare
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.
Companion PR to AeneasVerif/charon#457.
There's a tiny bit of trickiness around how
FailBottomremembers how deep in the place we are so that later we can recover the subplace. It might make sense to store the whole subplace instead of the depth.