semantic: assign ast node ids during semantic build Entire-Checkpoint: a4f3fdbfe5b0

[Boshen]

Entire-Checkpoint: a4f3fdbfe5b0

[Boshen]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• semantic: assign ast node ids during semantic build Entire-Checkpoint: a4f3fdbfe5b0 #19263 👈 (View in Graphite)
• feat(ast): add node_id field to all AST struct nodes #18138
• 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]

Merging this PR will degrade performance by 6.16%

❌ 5 regressed benchmarks
✅ 42 untouched benchmarks
⏩ 3 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	semantic[binder.ts]	3 ms	3.2 ms	-5.31%
❌	Simulation	semantic[RadixUIAdoptionSection.jsx]	60.7 µs	62.8 µs	-3.42%
❌	Simulation	semantic[cal.com.tsx]	21.3 ms	22.7 ms	-6.16%
❌	Simulation	semantic[react.development.js]	1.2 ms	1.3 ms	-5.21%
❌	Simulation	pipeline[binder.ts]	14.8 ms	15.5 ms	-4.3%

---

_{Comparing 02-11-semantic_assign_ast_node_ids_during_semantic_build_entire-checkpoint_a4f3fdbfe5b0 (f7faacd) with feat/ast-node-id (b7438d5)²}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on feat/ast-node-id (a8088c0) during the generation of this report, so 452c823 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩