ze-fix-alloc

To remove a single allocation in a Go encoding path, you refactor the target function to eliminate the heap allocation, read the containing function and its callers to propagate changes safely, and verify the result with lint and unit tests.

The best way to refactor a buffer-writing pattern in Go is to identify the specific allocation, apply the smallest safe change to remove it, and validate the encoding path with lint and unit tests to guard against regressions.

Analyzing the call graph helps optimize hot-path encoding code by reading all callers of the target function, ensuring that removing an allocation and updating the buffer-writing pattern propagates safely without breaking behavior.

Yes, you need to run unit tests after removing an allocation from a Go encoding function to verify correctness across callers and guard against regressions caused by the buffer-writing pattern changes.

This approach applies specifically when optimizing hot-path encoding code in the Ze repository, requiring changes to align with the repo's buffer-writing pattern and validation through Ze lint and unit tests.

Removing an allocation requires reading all callers because the refactor must propagate changes safely across the call graph, ensuring the updated buffer-writing pattern maintains correct behavior throughout the encoding path.