example of typical async/await usage: async.zig const std = @import("std"); const Allocator = std.mem.Allocator; pub fn main() void { _ = async amainWrap(); // Typically we would use an event std.process.exit(1); }; } fn amain() !void { const allocator = std.heap.page_allocator; var download_frame = async fetchUrl(allocator, "https://example.com/data.html"); var awaited_download_frame (!awaited_download_frame) { if (await download_frame) |r| allocator.free(r) else |_| {} }; var file_frame = async readFile(allocator, "something.txt"); var awaited_file_frame = false; errdefer

the Zig Standard Library's testing allocator, std.testing.allocator, the default test runner will report any leaks that are found from using the testing allocator: test.zig const std = @import("std"); @import("std"); test "detect leak" { var list = std.ArrayList(u21).init(std.testing.allocator); // missing `defer list.deinit();` try list.append('+'); try std.testing.expect(list /home/ci/release-0.10.1/out/zig-x86_64-linux-musl-baseline/lib/zig/std/array_list. const new_memory = try self.allocator.reallocAtLeast(self.allocate); /home/ci/release-0.10.1/out/zig-x86_64-linux-musl-baseline/lib/zig/std/array_list

parametrized with a user-provided allocator but they never actually use it directly ## Memory pools and C++ ## There is good news though ## Even when the user-provided allocator is not used, a related (“rebound”) they allocate for template class allocator { // ... template struct rebind { using other = allocator; }; // ... using pointer = T*; which adopts standard C++ allocator model without modifications but allocate from a memory pool under the hood ## I mplementation Components: 1. A memory pool 2. An allocator which allocates from a memory