Post Weights Checklist

[shawntabrizi]

Here are some things that we should do once initial weights are "completed" (see #5596)

• Write down all changed APIs to pallets (additional parameters, additional traits, etc)

• Write down all changed functionality to pallets (new functions? functions do different things?)

• Write down all assumptions about maximums taken in weight calculations.

• Double check all weights one last time (sanity check)

• Ensure Polkadot JS API is updated for changed APIs and Functionality

• Check operational dispatches if they should be operational, and check if any new dispatches can be operational.

• Make sure we can save a blockchain with full blocks using only operational transactions. (Allow operational recovery path if on_initialize use fullblock. #6089)

[joepetrowski]

• Fee calculation from block data: Account for post-dispatch weight correction #6022

[kianenigma]

• move all weights to saturating_xxx.

[apopiak]

• collect open questions regarding future weight work (e.g. "how to do transitive weights well?", "how to help others building with substrate to do weights well?")

[gui1117]

move all weights to saturating_xxx.

an option could also be to use a type which saturate by itself, std provides, https://doc.rust-lang.org/core/num/struct.Wrapping.html
Somebody implemented https://crates.io/crates/saturating
Though I think manual saturation is fine.