+4
-5
nixos/doc/manual/development/option-types.section.md
+4
-5
nixos/doc/manual/development/option-types.section.md
···-A sum type can be thought of, conceptually, as a *`types.enum`* where each valid item is paired with a type, through some value syntax.Nix does not have a built-in syntax for this pairing of a label and a type or value, so sum types may be represented in multiple ways.-If the built-in Nix value types provide enough distinction, you simplify your syntax with a [union type](#sec-option-types-unions) instead.
···+A sum type can be thought of, conceptually, as a *`types.enum`* where each valid item is paired with at least a type, through some value syntax.Nix does not have a built-in syntax for this pairing of a label and a type or value, so sum types may be represented in multiple ways.+If the you're interested in can be distinguished without a label, you may simplify your value syntax with a [union type](#sec-option-types-unions) instead.+the attribute set (`attr1`, etc) and whose value consists of definitions that are valid for the corresponding option (`option1`, etc).