-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Clone questionMark and dotdotdot token #58263
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
Conversation
@typescript-bot perf test this |
Starting jobs; this comment will be updated as builds start and complete.
|
4d63a61
to
26b6afc
Compare
@typescript-bot perf test this |
@armanio123 Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
startupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
This makes sense; But, this does need a test; the linked issue should come with one that can be minimized. |
@typescript-bot perf test this |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
startupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
Tested, and the test does actually test the crash, nice. |
Fixes #57924 (comment)
CompletionInfo
is failing due to a syntheticpropertySignature
using an incorrectquestionToken
position which cause the Assert to fail.The positions are incorrect due to the checker reusing the synthetic node for the
questionToken
. When assigning positions the value gets overwritten by the latest position update this generating a node that is "not contained" on the parent.The PR fixes this by always cloning a synthetic
questionToken
instead of reusing it.