NotificationsYou must be signed in to change notification settings
Fork548
Star2.8k

[generator] Reference bound *Appearance types using global:: syntax. Fixes #6834.#6859

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

rolfbjarne merged 1 commit intodotnet:xcode11fromrolfbjarne:issue-6834

Aug 28, 2019

Merged

[generator] Reference bound *Appearance types using global:: syntax. Fixes #6834.#6859

rolfbjarne merged 1 commit intodotnet:xcode11fromrolfbjarne:issue-6834

Aug 28, 2019

Conversation

Copy link

Member

rolfbjarne commentedAug 27, 2019

The generator will create special *Appearance types (these are nested
classes). If we've bound a type with the same *Appearance name, we can end up
in a situation where the csc compiler uses the the type we don't want due to
C#'s resolution rules - this happens if the bound *Appearance type is
referenced from the containing type of the special *Appearance type. So always
reference the bound *Appearance types using global:: syntax.

Fixes#6834.

[generator] Reference bound *Appearance types using global:: syntax.F…

497f761

…ixesdotnet#6834.The generator will create special *Appearance types (these are nestedclasses). If we've bound a type with the same *Appearance name, we can end upin a situation where the csc compiler uses the the type we don't want due toC#'s resolution rules - this happens if the bound *Appearance type isreferenced from the containing type of the special *Appearance type. So alwaysreference the bound *Appearance types using global:: syntax.Fixesdotnet#6834.