refactor(all)!: remove binding pattern wierdness#15925
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. |
b41648c to
497689d
Compare
CodSpeed Performance ReportMerging #15925 will not alter performanceComparing Summary
Footnotes
|
fb8fd1d to
a46b36c
Compare
3f8218e to
21ccffa
Compare
c7c26a3 to
cb33768
Compare
dbbda2a to
fbac3c5
Compare
|
@overlookmotel this should be ready for review 🙏 . I also tested this in rolldown, and although rolldown requires changes, no tests fail - it all looks OK 👌 |
fbac3c5 to
9807b77
Compare
|
🐐 |
7441ca1 to
45f242e
Compare
45f242e to
76a0c6d
Compare
Merge activity
|
fixes #11489 Note, in quite a few places i changed the span we report on to look something like this, the only reason for this is to reduce the diff in some of the snapshots ``` decl.type_annotation.as_ref().map_or_else( || decl.id.span(), |type_annotation| decl.id.span().merge(type_annotation.span()), ), ```

fixes #11489
Note, in quite a few places i changed the span we report on to look something like this, the only reason for this is to reduce the diff in some of the snapshots