pub fn family_rows() -> Vec<(&'static ParamSpec, &'static FamilyParam)>Expand description
Every family-dependent parameter declaration in the engine, paired with the
FamilyParam row that describes it — the lookup markdown_for needs,
which the document does not, because push_roster already has the roster’s
label in hand and this walk does not.
Keyed by declaration, because the editor schema’s definitions are. A
family-dependent declaration shared by two systems would key one hover on the
other’s families; every_family_row_declaration_belongs_to_one_roster in
core/tests/suite/preset.rs is what forbids that, and it fails rather than
letting a wrong hover be printed.