-
Notifications
You must be signed in to change notification settings - Fork 12.8k
createNodeArray
always makes a new nodeArray
when given a nodeArray
#59135
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
base: main
Are you sure you want to change the base?
Conversation
@typescript-bot perf test this |
I suspect this will be bad for other cases where reuse is actually intended, and I’m not sure whether that will show up on the perf suite, but we can see. I think it would probably be better to have just the one call we identified in checker.ts do something different to ensure it always creates a new NodeArray. |
@iisaduan 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: |
Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
@typescript-bot perf test this |
@DanielRosenwasser 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: |
Debug.attachNodeArrayDebugInfo(elements); | ||
return elements; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels bit scary to me; I do think we need to think about how we should be defining what this function is actually supposed to do, i.e. come up with create
and update
separately or something (what you mention in #59137).
fixes #59115
this is the more extensive version of #59137, as it stands, this PR might be changing too much, and was set up for perf testing curiosity