Skip to content

Fix runaway recursion in object type member resolution #25336

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

Merged
merged 5 commits into from
Jul 3, 2018

Conversation

ahejlsberg
Copy link
Member

Fixes #25291.

@ahejlsberg ahejlsberg requested a review from mhegazy June 30, 2018 03:18
@@ -5514,7 +5517,7 @@ namespace ts {
// (otherwise there'd be an error from hasBaseType) - this is fine, but `.members` should be reset
// as `getIndexedAccessType` via `instantiateType` via `getTypeFromClassOrInterfaceReference` forces a
// partial instantiation of the members without the base types fully resolved
(type as Type as ResolvedType).members = undefined!; // TODO: GH#18217
type.members = undefined; // TODO: GH#18217
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need for the comment now.

@ahejlsberg ahejlsberg merged commit e8d64a9 into master Jul 3, 2018
@ahejlsberg ahejlsberg deleted the fixResolveTypeMembers branch July 3, 2018 17:53
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.

2 participants