LazyBuffers: LazyBufferHandle

[gatesn]

Summary

Closes: #000

Testing

[gatesn]

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

• LazyBuffers: more reduce rules #7093
• LazyBuffers: use LazyBufferHandle #7092
• LazyBuffers: LazyBufferHandle #7091 👈 (View in Graphite)
• LazyBuffers: filter buffer handles #7071
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

Merging this PR will degrade performance by 76.84%

❌ 2 regressed benchmarks
✅ 1007 untouched benchmarks
⏩ 1529 skipped benchmarks¹

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

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	like_substr_low_match	12.1 ms	38.1 ms	-68.14%
❌	Simulation	like_substr_high_match	9.1 ms	39.2 ms	-76.84%

---

_{Comparing ngates/lazy-buffers/lazy-buffer (9fd8a54) with ngates/lazy-buffers/slicing (d0d6558)}

Footnotes

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

[gatesn]

FIXME: I think we need to change SegmentSource to take a Vec so we don't end up heap-allocating hundreds of requests. This can flow all the way into the coalesced reader if we need to.