-
-
Notifications
You must be signed in to change notification settings - Fork 780
refactor(ast)!: change TSInterfaceDeclaration::extends from Option<Vec> to Vec
#10472
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)!: change TSInterfaceDeclaration::extends from Option<Vec> to Vec
#10472
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 #10472 will not alter performanceComparing Summary
|
|
The only remaining oxc/crates/oxc_ast/src/ast/js.rs Lines 2366 to 2380 in 1952e30
That one should stay as is, because |
Merge activity
|
…<Vec>` to `Vec` (#10472) It wasn't possible for `extends` field to be `Some` containing an empty `Vec` because this is not legal code: ```ts interface Foo extends {} ``` So use `Vec` for `extends` field, instead of `Option<Vec>`. This prevents creating an invalid AST, and simplifies code in various places.
f809e9e to
eda2c5f
Compare
…<Vec>` to `Vec` (#10472) It wasn't possible for `extends` field to be `Some` containing an empty `Vec` because this is not legal code: ```ts interface Foo extends {} ``` So use `Vec` for `extends` field, instead of `Option<Vec>`. This prevents creating an invalid AST, and simplifies code in various places.
eda2c5f to
6eb7faa
Compare
…<Vec>` to `Vec` (#10472) It wasn't possible for `extends` field to be `Some` containing an empty `Vec` because this is not legal code: ```ts interface Foo extends {} ``` So use `Vec` for `extends` field, instead of `Option<Vec>`. This prevents creating an invalid AST, and simplifies code in various places.
882b517 to
1dbe1c1
Compare
…<Vec>` to `Vec` (#10472) It wasn't possible for `extends` field to be `Some` containing an empty `Vec` because this is not legal code: ```ts interface Foo extends {} ``` So use `Vec` for `extends` field, instead of `Option<Vec>`. This prevents creating an invalid AST, and simplifies code in various places.
1dbe1c1 to
7212803
Compare

It wasn't possible for
extendsfield to beSomecontaining an emptyVecbecause this is not legal code:So use
Vecforextendsfield, instead ofOption<Vec>. This prevents creating an invalid AST, and simplifies code in various places.