This repository has been archived by the owner on May 4, 2024. It is now read-only.
[Prover] Fix an issue in the concretization in the mono analysis #725
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
Prover concretizes a type parameter `T` into `Primitive(Range)` which eventually causes the panic. So, this commit excludes the spec only primitive types during the mono analysis. Resolves move-language#700
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Prover concretizes a type parameter
TintoPrimitive(Range)which eventually causes the panic (at this line: https://github.com/move-language/move/blob/main/language/move-prover/boogie-backend/src/boogie_helpers.rs#L194).So, this commit excludes the spec only primitive types during the mono analysis.
Resolves #700
Motivation
To fix an issue in the mono analysis
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
cargo test