-
-
Notifications
You must be signed in to change notification settings - Fork 794
refactor(ast)!: remove JSXOpeningElement::self_closing field
#10275
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
refactor(ast)!: remove JSXOpeningElement::self_closing field
#10275
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. |
CodSpeed Instrumentation Performance ReportMerging #10275 will not alter performanceComparing Summary
|
|
+1% improvement on |
Merge activity
|
Remove `self_closing` field from `JSXOpeningElement`. Whether the tag is self-closing can be determined by whether the `JSXElement` has a `closing_element` or not. This is advantageous for 2 reasons: 1. Reduce size of `JSXOpeningElement` by 8 bytes. 2. Make it impossible for `self_closing` and `closing_element` fields to get out of sync. Only one source of truth.
ce89055 to
a26fd34
Compare

Remove
self_closingfield fromJSXOpeningElement. Whether the tag is self-closing can be determined by whether theJSXElementhas aclosing_elementor not.This is advantageous for 2 reasons:
JSXOpeningElementby 8 bytes.self_closingandclosing_elementfields to get out of sync. Only one source of truth.