Add one prelude axiom to be identified in axiom-usage-info
#1397
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
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.
The proof of concrete sequence sorted by mergesort requires a prelude axiom, which is not reflected by
verus -V broadcast-usage-infobefore, as the verus will only take the named axioms in unsat-core. We named one axiom in air prelude (which seems to be the only one not about unboxing/boxing conversions orhas_type).We also changed
broadcast-usage-infotoaxiom-usage-infoto match the vargo build option (vargo build --features axiom-usage-info)By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.