# stage2: explicitly tagged enums no longer have one possible value · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/7453f56e678c80928ababa2868c69cfe41647fed)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 7453f56e678c80928ababa2868c69cfe41647fed

Requested commit: 7453f56e678c80928ababa2868c69cfe41647fed

Commit: 7453f56e678c80928ababa2868c69cfe41647fed

Tree: 689bfb73cab6314cb91898b174fcf12d50196009

Author: Andrew Kelley

Committer: Andrew Kelley

## Message

```
stage2: explicitly tagged enums no longer have one possible value

Previously, Zig had inconsistent semantics for an enum like this:

`enum(u8){zero = 0}`

Although in theory this can only hold one possible value, the tag
`zero`, Zig no longer will treat the type this way. It will do loads and
stores, as if the type has runtime bits.

Closes #12619

Tests passed locally:
 * test-behavior
 * test-cases

```

## Parents

- [af19909b9cde3d009f0306ac825f39912644bca6](https://git.cafe/gitcafe/zig/commit/af19909b9cde3d009f0306ac825f39912644bca6?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/7453f56e678c80928ababa2868c69cfe41647fed?format=markdown)