Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(dotnet): use fully-qualified type names #651

Merged
merged 4 commits into from
Jul 30, 2019
Merged

Conversation

RomainMuller
Copy link
Contributor

Stop generating using statements for types referenced in a particular
file, so as to avoid running into cases where a given type (leaf) name
corresponds to a locally defined type as well as a dependent type, which
breaks compilation as dotnet will resolve to the local type with
higher priority than the using type.

Fixes #650


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Stop generating `using` statements for types referenced in a particular
file, so as to avoid running into cases where a given type (leaf) name
corresponds to a locally defined type as well as a dependent type, which
breaks compilation as `dotnet` will resolve to the local type with
higher priority than the  `using` type.

Fixes #650
@RomainMuller RomainMuller merged commit d32e2cd into master Jul 30, 2019
@RomainMuller RomainMuller deleted the rmuller/fix/650 branch July 30, 2019 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

.NET code ambiguous, does not build
2 participants