pub enum Life {
Live,
ReadOnlyDead(&'static str),
WriteOnlyDead(&'static str),
Unexamined,
}Expand description
Whether the engine reads a label at a path, and if not, why saying so helps.
A schema answers “what may a legitimate file contain”, which is wider than “what does the engine read”: labels the engine ignores still appear in files the toolset wrote, so leaving them out would make an unrecognized-field check fire once per shipped resource. Keeping them without marking them is not much better, because then a diagnostic can only say a field is unrecognized when the useful message is that setting it does nothing and here is what the engine reads instead.
Variants§
Live
The engine reads this label at this path.
ReadOnlyDead(&'static str)
Legitimate file content the engine never reads, with why.
The payload finishes the sentence “setting it has no effect, because …”. A payload rather than an optional note, so no marking can exist without one.
WriteOnlyDead(&'static str)
The engine writes it and never reads it back.
Unexamined
Nobody has looked.
The default, and countable. This is the state the old axis lacked, and lacking it is what let a thousand entries claim the engine reads a field when all anyone knew was that the field existed.