Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Correctly handle type promoted module symbols [#332, #375, #401] #414
We get the incorrect type when analysing type promoted module symbols, causing the incorrect symbol to be used when qualifying names explicitly.
Additionally, renamed imports are removed when they match an import that's added automatically.
When an unqualified name is used in VB, the converted C# did not qualify it if it would become ambiguous.
Use the containing type of the symbol to determine the correct LHS for a
If there are multiple imports of the same namespace, prefer the import with an alias, and use that for name resolution.
When converting a generic name, qualify it if possible to ensure we select the right reference.