alloc_phase.ObservingPhaseAllocator

1/// Audits phase compliance across an application lifecycle by recording2/// unauthorized raw operations in local counters and call site slots while3/// forwarding those requests to the backing allocator. When a caller attempts4/// an operation outside the permitted phase, the guard increments the5/// corresponding violation counter, attempts to record the return address in6/// one of 16 call site slots, and forwards the invocation to the backing7/// allocator. If the backing allocator fails the request, the violation counter8/// remains incremented because the attempt itself violated lifecycle rules.9///10/// The guard stores its state in a separately allocated control block, allowing11/// wrapper copies and issued `std.mem.Allocator` handles to share the same12/// lifecycle phase, counters, and backing allocator. This control block13/// includes atomic return address slots, giving it a larger memory footprint14/// than `SealedPhaseAllocator`. The guard enforces the same lifecycle rules as15/// `SealedPhaseAllocator`, so invalid phase transitions, duplicate transitions,16/// handle requests in the wrong phase, and premature deinitialization trigger17/// an explicit panic in all build modes. This mechanism operates entirely18/// through its own allocator handles and functions independently from19/// `alloc_observe` event sessions.20pub const ObservingPhaseAllocator = PhaseAllocator(.observe);

1/// Audits phase compliance across an application lifecycle by recording2/// unauthorized raw operations in local counters and call site slots while3/// forwarding those requests to the backing allocator. When a caller attempts4/// an operation outside the permitted phase, the guard increments the5/// corresponding violation counter, attempts to record the return address in6/// one of 16 call site slots, and forwards the invocation to the backing7/// allocator. If the backing allocator fails the request, the violation counter8/// remains incremented because the attempt itself violated lifecycle rules.9///10/// The guard stores its state in a separately allocated control block, allowing11/// wrapper copies and issued `std.mem.Allocator` handles to share the same12/// lifecycle phase, counters, and backing allocator. This control block13/// includes atomic return address slots, giving it a larger memory footprint14/// than `SealedPhaseAllocator`. The guard enforces the same lifecycle rules as15/// `SealedPhaseAllocator`, so invalid phase transitions, duplicate transitions,16/// handle requests in the wrong phase, and premature deinitialization trigger17/// an explicit panic in all build modes. This mechanism operates entirely18/// through its own allocator handles and functions independently from19/// `alloc_observe` event sessions.20pub const ObservingPhaseAllocator = allocator.ObservingPhaseAllocator;