-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add support for aliased references #40
Labels
enhancement
New feature or request
Comments
kzu
added a commit
that referenced
this issue
Nov 18, 2022
We need to update the way we emit full names, and also add extern aliases to the generated source file. Closes #40
kzu
added a commit
to devlooped/Dynamically
that referenced
this issue
Nov 18, 2022
kzu
added a commit
to devlooped/Dynamically
that referenced
this issue
Nov 18, 2022
kzu
added a commit
that referenced
this issue
Nov 18, 2022
We need to update the way we emit full names, and also add extern aliases to the generated source file. Closes #40
kzu
added a commit
to devlooped/Dynamically
that referenced
this issue
Nov 18, 2022
kzu
added a commit
that referenced
this issue
Nov 18, 2022
We need to update the way we emit full names, and also add extern aliases to the generated source file. Closes #40
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever type name collisions exist, .NET offers aliases to disambiguate.
For example, you can add the
Aliases
metadata to a project reference as follows:Then code must use:
To reference types in one or the other, even if the types have the exact same full name,
the compiler will be able to disambiguate.
Currently, we do not even process references that have aliases, meaning no services
will be registered at all. We should do so, and emit code that can compile by also
including the
extern alias
declarations as needed.The text was updated successfully, but these errors were encountered: