perf(formatter): Allocation free interned

[MichaReiser]

Summary

This PR removes the need for an Rc to implement interned by using the Buffer as an interner

• Create an ID for the interned content
• Wrap the content in StartInterned and EndInterned tag with the corresponding ID and write the content directly to the target Buffer.
• Write a Reference(id) node to reference to the interned content.

The Printer skips interned content but writes it to an internal Index. The Printer uses the internal Index to resolve the Interned content when it sees a Reference. The fact that ids tend to be monotonic allows the use of a Vec as an Index similar to Group ids

The downside of this approach is that it is more complicated to reason about and it is no longer possible to inspect the content of Reference without tracking all interned content. Another downside is that the IR is slightly misleading because you see Interned content and would assume it gets printed in that place, which is not true. For example, the interned content appears before the best_fitting, but the content only gets printed inside the best-fitting variants. Moving the Interned content into the first best fitting variant doesn't work because that content only gets printed conditionally, meaning the Printer would then not always see the Interned content, failing to resolve the Reference.

Alternatives

One alternative that I explored is to use bumpallo instead and use it to allocate BestFitting vectors, dynamic strings, and Rcs. This could improve performance even more because it eliminates the 3-4% drop-time too. However, it comes at the downside that Buffer requires a new 'elements lifetime that needs to be added everywhere (Format, Formatter, Buffer, FormatNode, FormatNodeRule....). I gave up at some point because it made the API significantly more complicated.

Test Plan

cargo test

[MichaReiser]

Current dependencies on/for this PR:

• main
  • PR perf: Reduce best fitting allocations #7411
    • PR perf(formatter): Allocation free interned #7443 👈

This comment was auto-generated by Graphite.

[codspeed-hq]

CodSpeed Performance Report

Merging #7443 will degrade performances by 2.45%

_{Comparing allocation-free-interned (e112b02) with best-fitting-reduce-allocations (2843fc0)}

Summary

⚡ 2 improvements
❌ 1 regressions
✅ 22 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	best-fitting-reduce-allocations	allocation-free-interned	Change
⚡	formatter[unicode/pypinyin.py]	3.7 ms	3.6 ms	+2.26%
⚡	formatter[large/dataset.py]	57.3 ms	56.2 ms	+2.01%
❌	linter/all-rules[numpy/ctypeslib.py]	34.2 ms	35 ms	-2.45%

[MichaReiser]

We may want to bring this back when working on other best fitting layouts but closing for now