refactor(ast)!: remove PrivateInExpression::operator field#9041
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 Performance ReportMerging #9041 will not alter performanceComparing Summary
|
|
@leaysgur I'm going to go ahead and merge this, as we've had lots of problems with merge conflicts while we're rapidly progressing ESTree compatibility, and I'd like to avoid that. I think the change I've made to If this PR causes you a problem, please let me know and we can revert it. |
Merge activity
|
Remove `PrivateInExpression::operator` field. This field had no purpose beyond getting correct serialization to ESTree - it was always `BinaryOperator::In`, and no other value for `operator` makes sense in this position. So remove the field from the Rust type, and produce the desired output in ESTree AST using `#[estree(add_fields)]` instead. This follows on after changes made to serialization of `PrivateInExpression` in #9033.
c9a7999 to
d9189f1
Compare

Remove
PrivateInExpression::operatorfield.This field had no purpose beyond getting correct serialization to ESTree - it was always
BinaryOperator::In, and no other value foroperatormakes sense in this position. So remove the field from the Rust type, and produce the desired output in ESTree AST using#[estree(add_fields)]instead.This follows on after changes made to serialization of
PrivateInExpressionin #9033.