# What Should We \_Remove\_ from Zig?

**URL:** <https://ziggit.dev/t/what-should-we-remove-from-zig/17518>\
**Category:** Brainstorming\
**Tags:** language\
**Created:** [September 7, 2026, 8:36am UTC](https://ziggit.dev/t/what-should-we-remove-from-zig/17518 "2026-09-07T08:36:02Z")\
**Posts on this page:** 1\
**Showing post:** 134

<div class="post-metadata">

**Author:** ![WarumSoZickZack](https://ziggit.dev/letter_avatar_proxy/v4/letter/w/898d66/32.png) [@WarumSoZickZack](https://ziggit.dev/u/WarumSoZickZack)\
**Post date:** [October 7, 2026, 11:14am UTC](https://ziggit.dev/t/what-should-we-remove-from-zig/17518/134 "2026-10-07T11:14:27Z")

</div>

> [@Proposal: remove continue-expression of while loops from the language](https://ziggit.dev/t/proposal-remove-continue-expression-of-while-loops-from-the-language/17856):
>
> what about adding a new keyword ‘continuedefer’ (or maybe ‘loopdefer’, …) that defers a statement in a loop IFF the loop continues (explicitly with ‘continue’ or implicitly by reaching end of loop body). I think this would solve an issue initially stated by @matklad (and the edge case stated by @andrewrk in the comment), since it would allow to replace the while () : ([continue expression]) syntax with a keyboard based explicit control-flow. Also this concept of a conditional defer already exi…

---

_[View the full topic](https://ziggit.dev/t/what-should-we-remove-from-zig/17518)._