Analyzers/AnalyzerScope loops endlessly when analysing public inner c… #3164
Conversation
This file contains 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
siegfriedpammer
force-pushed
the
feature/AnalyzerScope
branch
from
808cef9 to
97ddd62
Compare
|
Thank you for your contribution! |
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.
…lass
Link to issue(s) this covers
Problem
Link to, or brief information about the issue
Solution
Any comments on the approach taken, its consistency with surrounding code, etc.
Small one line code change, to use iterative object instead of the beginning one
Which part of this PR is most in need of attention/improvement?
At least one test covering the code changed
There is one test for the problem.