Adapt according to nilness-checking changes in Gobra - #431
Draft
jcp19 wants to merge 3 commits into
Draft
Conversation
jcp19
commented
Aug 9, 2026
This file contains hidden or 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
1 participant
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.
viperproject/gobra#531 and viperproject/gobra#1077 will change the way we check nilness of deref'd points. This PR adapts SCION accordingly by adding non-nilness conditions on various function inputs to make Gobra happy. All conditions added are semantically redundant, but the non-nilness info could only be obtained after unfolding predicates