-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
feat(ast): derive Clone
for TemplateElement
and TemplateElementValue
#8658
feat(ast): derive Clone
for TemplateElement
and TemplateElementValue
#8658
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Clone
and Copy
for TemplateElement
and TemplateElementValue
CodSpeed Performance ReportMerging #8658 will not alter performanceComparing Summary
|
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.
Would just Clone
be sufficient? TemplateElement
is 48 bytes. That's a bit big to be Copy
.
2d79a31
to
e2bb198
Compare
a2a6454
to
a730f99
Compare
e2bb198
to
b73f8a8
Compare
b73f8a8
to
f0ed208
Compare
Clone
and Copy
for TemplateElement
and TemplateElementValue
Clone
for TemplateElement
and TemplateElementValue
Yes, it is enough. |
f0ed208
to
d287a61
Compare
Merge activity
|
d287a61
to
e2412c8
Compare
e2412c8
to
233dc07
Compare
In #8614, we need to duplicate the same template literal, and derive
Copy
andClone
to avoid usingCloneIn
.