feat(traverse): add TraverseCtx::change_parent_scope_for_expression

[Dunqing]

It is used for moving an expression to another block, then we need to change the parent for it.

[Dunqing]

• feat(traverse): add TraverseCtx::change_parent_scope_for_expression #8510 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

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-hq]

CodSpeed Performance Report

Merging #8510 will not alter performance

_{Comparing 01-15-feat_traverse_add_traversectx_change_parent_scope_for_expression (f60110a) with main (a368726)}

Summary

✅ 32 untouched benchmarks

[overlookmotel]

Probably I'm missing something, but how is this different from TraverseScoping::insert_scope_below_expression?

[Dunqing]

Probably I'm missing something, but how is this different from TraverseScoping::insert_scope_below_expression?

Oh, it is no different, and it is better than change_parent_scope_for_expression!