authorgravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-03-11 15:19:52+00:00
committergravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-03-11 22:15:43+00:00
log24db007cde02f756c8825d0bab0ed46c104f5430
tree6e63969ba26b34d45a938e7aa0998941a0e964e2
parent77395457fe1eb1bd7b96df1e13d4348edb5f1727

std.mem.Allocator.remap: fix incorrect doc comment (part 2)

1 files changed, 2 insertions(+), 1 deletions(-)

lib/std/mem/Allocator.zig+2-1
...@@ -308,7 +308,8 @@ pub fn resize(self: Allocator, allocation: anytype, new_len: usize) bool {...@@ -308,7 +308,8 @@ pub fn resize(self: Allocator, allocation: anytype, new_len: usize) bool {
308/// In such case, it is more efficient for the caller to perform those308/// In such case, it is more efficient for the caller to perform those
309/// operations.309/// operations.
310///310///
311/// `allocation` may be an empty slice, in which case `null` is always returned.311/// `allocation` may be an empty slice, in which case `null` is returned,
312/// unless `new_len` is also 0, in which case `allocation` is returned.
312///313///
313/// `new_len` may be zero, in which case the allocation is freed.314/// `new_len` may be zero, in which case the allocation is freed.
314pub fn remap(self: Allocator, allocation: anytype, new_len: usize) t: {315pub fn remap(self: Allocator, allocation: anytype, new_len: usize) t: {