Skip to content

Conversation

sandersn
Copy link
Member

Fixes #6783

When getting a default construct signature, if there is base with a generic construct signature, the signature needs to be instantiated with the type parameters from the derived class. When doing this however, the target should not refer back to the base class -- the default construct signature is considered separate from the base's signature.

Unset the instantiated signature's target to make this happen.

When getting a default construct signature, if there is base with a
generic construct signature, the signature needs to be instantiated with
the type parameters from the derived class. When doing this however, the
target should not refer back to the base class -- the default construct
signature is considered separate from the base's signature.

Unset the instantiated signature's target to make this happen.
@sandersn
Copy link
Member Author

The correct fix is in #8713. The fix is not to unset the target, but to remove the target-following code in getErasedSignature.

@sandersn sandersn closed this May 23, 2016
@sandersn sandersn deleted the fix-generic-default-construct-signature-inheritance branch May 23, 2016 20:11
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants