whichever 0.6.0

Implements a trait for an enum by forwarding to whichever variant it holds
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

# Releasing whichever

Releases are cut from a clean `main` with every CI job green. Two crates
ship together at one version, `whichever-macros` and `whichever`, and
`whichever` pins the macro crate to the exact version, since `__private`
and the generated code are one interface.

## 1. Prepare the release commit

- Choose the version. Before 1.0 a breaking change raises the minor
  version, and the changelog lists it without apology.
- Set `version` in `Cargo.toml` and in `macros/Cargo.toml` to the same
  number, and the `whichever-macros` dependency in `Cargo.toml` to
  `=<version>`.
- Rename `## Unreleased` in `CHANGELOG.md` to `## <version> - <date>` and add
  a fresh empty `## Unreleased` above it. Each entry's first sentence says
  what the release is for.
- When the generated code or the benchmarks changed and a number is quoted,
  rerun the suite on an otherwise idle machine with
  `benchmarks/scripts/run.sh`, which regenerates `benchmarks/RESULTS.md`,
  and update the numbers the README and `docs/when-to-use-enum-dispatch.md`
  quote from it. Never substitute a shared-runner timing.
- Commit as `Release <version>`; the commit touches the manifests and the
  changelog.

## 2. Reproduce the local gates

```sh
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo test --test expand -- --ignored
RUSTDOCFLAGS="-D warnings" cargo doc --no-deps -p whichever -p whichever-macros
cargo check -p whichever --no-default-features --tests
cargo check -p smoke-no-std --target thumbv7em-none-eabi
cargo bench -p whichever-benchmarks --no-run
python3 benchmarks/scripts/codegen.py
python3 benchmarks/scripts/check_numbers.py
```

The compile-fail snapshots are pinned to stable's wording; CI runs the other
toolchains with `-- --skip compile_fail`.

## 3. Inspect the packages

```sh
cargo package --list -p whichever-macros
cargo package --list -p whichever
```

The `whichever` archive carries the source, the README, the changelog, the
acknowledgements, this checklist and the licenses; `Cargo.toml` excludes the
smoke crates, the benchmarks, `docs/`, the workflows, the toolchain file,
the planning notes and `CLAUDE.md`.

## 4. Publish and tag

1. `cargo publish -p whichever-macros`, and wait until the new version
   resolves from the registry.
2. `cargo publish -p whichever`.
3. Tag the release commit `v<version>`, push the commit and the tag, and
   check that docs.rs builds both crates.
4. Leave the worktree clean. A post-release issue goes in the planning
   notes, not into a historical release entry.