Closed pbtoast closed 5 years ago
I've thought a bit about this, and this violates the Less Is More rule. Not every field has meaningful metadata, and forcing a practitioner to name components for intermediate fields not exposed to users is a burden I'd rather avoid.
Let's leave metadata to the I/O subsystem.
Now that we have fully-fledged field types, we can adorn them with some richer characteristics, such as names for their components. This in turn allows us to simplify the field I/O methods on silo_file, among other things.