perf(codegen): restructure print_comments to avoid index comparisons in loop

[camc314]

The idea is that this is a hot-ish path, so if we can remove the index checks from within the hot loop, it should be faster

[camc314]

• perf(codegen): restructure print_comments to avoid index comparisons in loop #17402 👈 (View in Graphite)
• perf(codegen): use print_ascii_byte in more places #17401
• perf(codegen): avoid allocation in PrivateIdentifier gen when not mangling #17395
• 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 #17402 will not alter performance

_{Comparing c/12-27-perf_codegen_restructure_print_comments_to_avoid_index_comparisons_in_loop (55395f8) with c/12-27-perf_codegen_use_print_ascii_byte_in_more_places (d2e530b)}

Summary

✅ 42 untouched
⏩ 3 skipped¹

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. ↩

[Boshen]

Merge activity

• Dec 28, 5:00 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 28, 5:00 AM UTC: Boshen added this pull request to the Graphite merge queue.
• Dec 28, 5:07 AM UTC: Merged by the Graphite merge queue.