refactor(StateVariables): Use SharedImmutableState
more consistently
#4756
Labels
aztec.nr
Aztec smart contract library
SharedImmutableState
more consistently
#4756
We are currently not using the
SharedImmutable
when we should, for example the contracts using the slow updates tree seldom store the address inSharedImmutable
but instead have a public and a separate private variable for it.Also, the macro is currently not supporting
SharedImmutable
ofsize != 1
. This essentially mean that the automatic storage slot allocation will cause overlapping storage if usingSharedImmutable
with values with a serialized size larger than 1. See #5078 for this part.The text was updated successfully, but these errors were encountered: