Fix: issue #4047 Symbol Solver mixes name with type #4206
Merged
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.
Fixes #4047 .
When the scope of the method invocation is a NameExpr there was a specific type resolution that appears to take static methods into account. However, static methods are already taken into consideration. This code snippet that was removed has been there since the start of the project but may no longer be useful now. Still, this snippet raises a problem in certain cases where the scope is a variable declared in the method block and if the name of the variable also corresponds to a type. In this case it is the type of the variable which should make it possible to determine the declaration of the method.