epic: jidoka types

[ClementWalter]

Why

While we were confident that the fuzz diff testing were allowing us to dev fast and accuratly, we faced a significant number of bugs while finalizing the state transition functions. Amongst them:

• careless casting = go from one internal XXXStruct to another type NewType(prev.valu/e) caused a lot of issues related especially to endianess
• verbose type creation and update = hard to understand the core logic of a function when 50% of the code is boilerplate

What

Remove this two issues

• no more cast (either with the actual keyword, or with the pattern above mentioned) outside of a well scope util
• modifier for types so that what can just trie_get in one line (example)

How

• Do not share internal struct if they are not the same underlying data (e.g. Uint256 used by Hash32, U256, etc.)
• List all such cases and create ad-hoc uils, e.g.
  • U256_to_be_bytes
  • U256_into_Hash32
• wherever there is a cast, think about a dedicated util/"method" to encapsulate it so that it's well delimited

Tasks

Preview Give feedback

1. encapsulate required cast into dedicated functions #801
   kaizen +1
2. dev: create dict utils for each type #776
   kaizen +1
   
3. dev: remove output tuple typle when possible #775
   kaizen +1