Ban non-exhaustive Zig switch else prongs - #10623
Merged
Merged
Conversation
rtfeldman
marked this pull request as ready for review
August 5, 2026 03:35
Contributor
|
Too many files changed for review (252 files, 100 file limit). Bypass the limit by tagging |
rtfeldman
force-pushed
the
exhaustive-switch-lint
branch
from
August 5, 2026 03:52
c0b0282 to
72c1a3f
Compare
rtfeldman
marked this pull request as draft
August 5, 2026 03:52
# Conflicts: # src/postcheck/monotype/solve.zig
# Conflicts: # ci/zig_lints.zig
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an AST-based Zig lint that rejects else switch prongs unless the switch contains numeric, string, or character literal cases, where a catch-all represents value-domain behavior rather than an omitted enum tag. Existing enum, error, and OS switches now enumerate their cases or use a discard prong where Zig permits it, so future enum additions fail to compile instead of silently taking an existing default.