Fix name collision between generic and non-generic forward declarations #24
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.
SonarDelphi currently crashes when parsing multiple forward declarations with the same name. This usually occurs when a non-generic type and a generic type share a name and are both forward declared, such as the below:
This PR modifies the code that identifies forward declarations to take into account the number of generic parameters of a declaration. This resolves the crash and correctly matches a full declaration to its forward declaration.