Co-authored-by: Ralf Jung <post@ralfj.de>
///
/// Note that you may not rely on this method actually getting called, even if there are calls
/// to it in the source. The optimizer may detect unused allocations that it can either
- /// eliminate entirely or move to the stack and thus never invoke the allocator here. The
+ /// eliminate entirely or move to the stack and thus never invoke the allocator. The
/// optimizer may further assume that allocation is infallible, so code that used to fail due
/// to allocator failures may now suddenly work because the optimizer worked around the
/// need for an allocation.