Expand description
ActiveModes: the major + ordered minors set per buffer.
M.3 lands ActiveModes as a field on Document; M.1 keeps
it as a standalone type that tests can construct directly.
The registry’s activation / deactivation methods take
&mut ActiveModes as a parameter so they can mutate the set
without owning per-buffer state – letting lattice-mode be
buffer-storage-agnostic for the foundation slice.
Minor mode order matters (it’s the activation order; later
activations override earlier ones at the option-resolution
layer per mode-architecture.md §6.2). The registry keeps
this ordering stable: activate appends to the end,
deactivate removes by id without disturbing relative order
of the survivors.
Structs§
- Active
Modes - The set of modes active on a buffer. Exactly one major (or none, prior to first major activation), plus any number of minors in activation order.