Conversation
…sitional information to not only the generatated PredicateAccessPredicate but also PredicateAccess as the latter is used as offending node in the resulting reason
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
2 participants
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.
If a predicate instance is used as a termination measure but there are insufficient permissions for this predicate instance, Viper creates a
PredicateInstanceNoAccesserror with that predicate instance as a reason.While the PredicateInstance plugin propagates positional information to the translated PredicateAccessPredicate, it did not do so for the PredicateAccess contained therein. However, it seems that Viper uses the PredicateAccess as offending node and this PR adapts the PredicateInstance plugin to use the same positional information for both, the generated PredicateAccessPredicate and PredicateAccess.