Custom types for commonly used structures

[cicr99]

There are some places in the code where structures such as map[felt.Felt]map[felt.Felt]*felt.Felt to refer to StorageDiff or map[felt.Felt]*felt.Felt to refer to others like DeployedContracts, are used.
We could define instead a custom type like:

type StorageDiff map[felt.Felt]map[felt.Felt]*felt.Felt

Or consider creating types such as Address or ClassHash for felts, so DeployedContracts map would look like map[Address]ClassHash.

This will allow the code to be more readable and easier to work with (when creating new structures or passing them as arguments in functions). It would also make it safer as you restrict the specific type that must be used (not just any felt for example), and it even allows to create methods on top of these structures.

Check out these two comments for reference:

• implement logic to build genesis state for the sequencer #2371 (comment)
• implement logic to build genesis state for the sequencer #2371 (comment)

[rodrodros]

Removing the label Good first issue because even if it is simple to code in the surface, I believe it is hard to get it right. It requires many design choices that will affect data types through out the code.

[TheRanomial]

Can I contribute to this one?

[github-actions]

This issue is stale because it has been open 35 days with no activity. Remove stale label or comment or this will be closed in 14 days.