# Zig 0.15.2 Released

**URL:** <https://ziggit.dev/t/zig-0-15-2-released/12466>\
**Category:** News\
**Tags:** zig-0-15-2\
**Created:** [October 12, 2025, 10:20am UTC](https://ziggit.dev/t/zig-0-15-2-released/12466 "2025-10-12T10:20:32Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![truly-not-taken](https://ziggit.dev/user_avatar/ziggit.dev/truly-not-taken/32/6205_2.png) [@truly-not-taken](https://ziggit.dev/u/truly-not-taken)\
**Post date:** [October 14, 2025, 12:59pm UTC](https://ziggit.dev/t/zig-0-15-2-released/12466/10 "2025-10-14T12:59:28Z")

</div>

> [@marler8997](#):
>
> - Fixed `takeDelimiter` to correctly handle delimiters and end-of-stream
> - Fixed `peekDelimiterInclusive` and `peekDelimiterExclusive` with proper boundary handling

This fix accidentally introduced a breaking change.

@mlugg [said](https://zsf.zulipchat.com/#narrow/channel/454371-std/topic/.E2.9C.94.20is.20takeDelimiterExclusive.20broken.3F/near/544413926):

> the function called `takeDelimiter` did not exist in 0.15.1; that behavior was in `takeDelimiterExclusive`, and iirc that was intentional at the time. i recall you discussing changes around these functions’ API contracts a few times at the start of this release cycle

@andrewrk [said](https://zsf.zulipchat.com/#narrow/channel/454371-std/topic/.E2.9C.94.20is.20takeDelimiterExclusive.20broken.3F/near/544414170):

> I agree it was a mistake, because I intended to only merge pure bug fixes with no behavior changes like this

Replace `takeDelimiterExclusive()` with `takeDelimiter()` when you upgrade to 0.15.2

---

_[View the full topic](https://ziggit.dev/t/zig-0-15-2-released/12466)._