fix(codegen): clear print_next_indent_as_space after newlines

[s7tya]

print_comments() can set print_next_indent_as_space after inline comments to request a single space before the next token. If a newline is emitted before the flag is consumed, the flag may leak across line boundaries and get consumed at the start of the next statement, producing stray leading spaces.

This PR clears print_next_indent_as_space whenever a newline is emitted (print_soft_newline / print_hard_newline) and routes print_semicolon_after_statement() through print_hard_newline() so newline handling consistently resets the flag.

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will not alter performance

_{Comparing s7tya:clear-indent-space-flag-on-newline (da113bb) with main (9e89389)¹}

Summary

✅ 42 untouched benchmarks
⏩ 3 skipped benchmarks²

Footnotes

1. No successful run was found on main (62b7a01) during the generation of this report, so 9e89389 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

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

[Dunqing]

Thank you

[graphite-app]

Merge activity

• Jan 12, 2:27 AM UTC: @s7tya we removed the merge queue label because we could not find a Graphite account associated with your GitHub profile.

You must have a Graphite account in order to use the merge queue. Create an account and try again using this link

[Boshen]

The fix doesn't look right, let me double check.