Zig Allocator interface signature changes between 0.11.0 and nightly

The std.mem.Allocator interface has undergone significant evolution since Zig 0.11.0, particularly regarding how allocation failures are signaled and handled. While the philosophy of explicit allocator passing remains constant, the method signatures for heap allocation and the associated error handling patterns have shifted across pre-1.0 iterations.

Developers transitioning older projects face inconsistencies in the expected error return types and the requirements for the alloc.init call patterns. There is uncertainty regarding whether the current nightly signatures represent the final stabilized API for the release or if further refinements to the error-handling wrapping will be introduced to improve memory tracking.

What are the specific breaking changes in the std.mem.Allocator method signatures between 0.11.0 and the current nightly? What is the recommended pattern for handling allocation-related errors to ensure forward-compatibility with upcoming stable releases?