Not-critical API changes wishlist

[thockin]

Let's make a list of API changes we would like to make that are non-critical RIGHT NOW but should be evaluated before we call it 1.0

Julian Gutierrez Oschmann (@juli4n) Eitan Yarmush (@EItanya)

[thockin]

"SnapshotsConfig" -> "SnapshotConfig" and "snapshots_config" -> "snapshot_config"

[thockin]

Don't allow UNSPECIFIED for enums (we don't have a back-compat requirement yet)

[thockin]

Should we reify default values of leave them as unspecified fields?

[thockin]

Remove all "reserved" use in proto files

[thockin]

Bundle page_size and page_token into ListOptions

[thockin]

Should we use quantity-strings ("1Gi", "0.001m", etc) or require quantized units ("cpu_millcores", "memory_megabytes"). Quantities are hard because a) floating point can be very imprecise (exactly what is "1.6Gi"); b) it can represent numbers that we don't want to quantize (e.g. "0.001m"); and c) can easily overflow standard ints. Handling them as native types is tricky. Also it's weird to encode "3 cores" as a string "3".

https://github.com/agent-substrate/substrate/pull/1283/changes#r3918227639

And if we DO use the string format, do we process those values as math/big.Float or something?

[thockin]

Decide and be consistent about capitalization of API nouns in comments ("this Actor will..." vs "this actor will...")

[BenTheElder]

Also "microVM" vs "micro-vm" and "gVisor" vs "gvisor".

[thockin]

All the methods in atepg and impl do different error transformations -- we should have one place where than is done the same for everyone?