Analyze: Handle Case Where Name is None and New Intersection Option#898
Merged
Analyze: Handle Case Where Name is None and New Intersection Option#898
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #898 +/- ##
===========================================
+ Coverage 40.30% 41.40% +1.09%
===========================================
Files 15 22 +7
Lines 1119 1512 +393
Branches 152 214 +62
===========================================
+ Hits 451 626 +175
- Misses 632 841 +209
- Partials 36 45 +9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Collaborator
Author
|
|
pearce8
approved these changes
Jul 21, 2025
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
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.
Description
benchpark analyzewill fail with error:because of the check in the Thicket Query. Modifiying the check to not check against
Nonefixes this issueintersectionof the calltree instead of theunionwhich is an alternative way to address this issue, but also a feature.Adding/modifying core functionality, CI, or documentation: