While working on moving the ARM types into a subpackage called arm, I noticed that referencing ARM types as v20240531a.Account instead of Account_ARM was considerably less clear.
This PR changes the way subpackages are imported to use the name of the subpackage (e.g. arm) if that works without causing conflicts. This will allow ARM types to be referenced as arm.Account which is nice and clear, and has the welcome side effect of changing many of our current references to storage, adding clarity to the existing code.
What this PR does / why we need it:
While working on moving the ARM types into a subpackage called
arm
, I noticed that referencing ARM types asv20240531a.Account
instead ofAccount_ARM
was considerably less clear.This PR changes the way subpackages are imported to use the name of the subpackage (e.g.
arm
) if that works without causing conflicts. This will allow ARM types to be referenced asarm.Account
which is nice and clear, and has the welcome side effect of changing many of our current references tostorage
, adding clarity to the existing code.How does this PR make you feel:
If applicable: