Repository navigation
Fix JVM analysis aborts after rejected symbolic assumptions - #550
Merged
Merged
Conversation
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.
Engine.assumeSymboliccould hide a rejectedscope.assertbehindUnit, then complete the call on a dead scope and abort the analysis. Build the guarded assumption as a pure expression and assert once, so rejection prunes its state while other states continue. Concrete and null references keep their existing behavior.Validation: the public-path reproducer fails on
mainwith the originalStepScopeexception; all four focused regression tests pass after the fix, including a guarded concrete alternative. Changed Kotlin files pass strict Detekt against a temporary baseline generated from the original main source; the three pre-existing findings and the repository baseline remain unchanged.