Skip to content

Conversation

Helcaraxan
Copy link
Contributor

The ILRepack has introduced type conflict issues that are not easily
solved. This boils down to the fact that the public API surface of the
Platform SDK exposes types provided by dependencies. ILRepack creates an
artificial assembly to export those types.

However any user will need to import the original dependency assembly in
order to construct function arguments with the types in question. This
will result in duplicate type errors as they will exist in both the
user-imported dependency and the new artificial assembly created by the
ILRepack.

The ILRepack has introduced type conflict issues that are not easily
solved. This boils down to the fact that the public API surface of the
Platform SDK exposes types provided by dependencies. ILRepack creates an
artificial assembly to export those types.

However any user will need to import the original dependency assembly in
order to construct function arguments with the types in question. This
will result in duplicate type errors as they will exist in both the
user-imported dependency and the new artificial assembly created by the
ILRepack.
@Helcaraxan Helcaraxan self-assigned this Aug 8, 2019
@improbable-prow-robot improbable-prow-robot added jira/no-ticket Indicates a PR has no corresponding JIRA ticket size/M Denotes a PR that changes 40-149 lines, ignoring generated files. labels Aug 8, 2019
@Helcaraxan Helcaraxan merged commit c42703e into master Aug 8, 2019
@Helcaraxan Helcaraxan deleted the undo-ilrepack branch August 8, 2019 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/no-ticket Indicates a PR has no corresponding JIRA ticket size/M Denotes a PR that changes 40-149 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants