test: Add fixture for defineProperty call with recursive property access#76
Draft
RandomByte wants to merge 1 commit intomainfrom
Draft
test: Add fixture for defineProperty call with recursive property access#76RandomByte wants to merge 1 commit intomainfrom
RandomByte wants to merge 1 commit intomainfrom
Conversation
RandomByte
force-pushed
the
recursive-prop-define
branch
from
878bb51 to
8473db4
Compare
|
|
This currently causes a Maximum call stack size exceeded exception within TypeScript's checker#typeToString method.
matz3
force-pushed
the
recursive-prop-define
branch
from
8473db4 to
ae478f2
Compare
Member
|
Still reproducible with the current state (TypeScript 5.9) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This currently causes a Maximum call stack size exceeded exception
within TypeScript's checker#typeToString method.
This illustrates the issue reported in #75