Skip to content

Conversation

@RyanGlScott
Copy link
Contributor

It is possible for a MIR JSON file to parse even if the schema version doesn't match what is expected, as noticed in GaloisInc/saw-script#2852 (comment). This ensures that the schema version is checked regardless of whether parsing succeeds or not.

Refactoring only, no change in behavior.
It is possible for a MIR JSON file to parse even if the schema version doesn't
match what is expected, as noticed in
GaloisInc/saw-script#2852 (comment). This
ensures that the schema version is checked regardless of whether parsing
succeeds or not.
@RyanGlScott RyanGlScott merged commit 4d88a65 into master Dec 3, 2025
31 checks passed
@RyanGlScott RyanGlScott deleted the rgs/crucible-mir-fix-schema-version-check-yet-again-ugh-i-hate-this-function branch December 3, 2025 00:33
RyanGlScott added a commit to GaloisInc/saw-script that referenced this pull request Dec 4, 2025
This bumps the `mir-json` and `crucible` submodules to bring in the changes
from:

* GaloisInc/mir-json#202
  (Print `rustc` version information before `mir-json` version)

* GaloisInc/crucible#1661
  (`crucible-mir`: Check schema version even when parsing succeeds)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

crucible MIR Issues relating to Rust/MIR support

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants