Skip to content

Conversation

@sandersn
Copy link
Member

Yet again, the fix is to stop using checkExpressionCached. As before, I don't know how to fix checkExpressionCached to not cause these infinite recursions.

Fixes #25149

@sandersn sandersn requested a review from weswigham June 26, 2018 16:35
Copy link
Member

@weswigham weswigham left a comment

Choose a reason for hiding this comment

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

We could set a global checker bit on entry into getFlowTypeOfReference that causes checkExpressionCached to either throw or quietly not cache. I mean, flowLoopStart already exists, we're just using it to signal resetting flow control (which is what causes the problem), rather than proceeding without a cache - it seems like simply that the concept of caching results during flow control is inherently unstable?

In any case, this is OK.

@sandersn sandersn merged commit 9025bc7 into master Jun 26, 2018
@sandersn sandersn deleted the fix-control-flow-loop-in-yield-expr branch June 26, 2018 19:50
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
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.

Compiler error: Maximum call stack size exceeded

3 participants