Replace key_free_values field with PrimaryStorage enum in builders
Using a struct with both `primary: FxIndexMap` and `key_free_values: Vec` left the mixed case (keyed + key-free in the same builder) as a legitimate state with ad-hoc handling. An enum makes the two modes mutually exclusive and self-documenting: either all entries are keyed (dedup by RequestKey) or none are (append-only). The mixed case — keyed self merging a key-free other and vice versa — is handled explicitly by promoting the key-free side before the merge.
Showing
This diff is collapsed.
Please
register
or
sign in
to comment