fix(semantic): use correct scope flags for using declarations#9751
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. |
c117e01 to
354b424
Compare
CodSpeed Performance ReportMerging #9751 will not alter performanceComparing Summary
|
354b424 to
8516bd5
Compare
cd3f2fb to
3f73d01
Compare
8516bd5 to
f0ec0bb
Compare
f0ec0bb to
6707621
Compare
3f73d01 to
9a6702a
Compare
9a6702a to
12e19b9
Compare
208ff32 to
27fb1ae
Compare
27fb1ae to
bb26d9a
Compare
bb26d9a to
06aabfd
Compare
06aabfd to
1d3ed9b
Compare
There was a problem hiding this comment.
Nice job. A few small comments below.
Also, judging by the names of the conformance tests (transform-sync), it looks like this change only causes semantic errors in tests relating to using, but not await using. Seems odd.
Maybe the tests don't contain any cases where await using is in a nested block, and that explains it. But I think worth checking, if you didn't already.
2e0280e to
15f3481
Compare
12e19b9 to
f707d1f
Compare
51c14f5 to
b7def02
Compare
b7def02 to
388f955
Compare
Dunqing's feedback was addressed.
Merge activity
|
388f955 to
bc8bc08
Compare

fixes #9666