You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the each variable relating to a token is in its own mapping. It could be more efficient to make a single collectable 'struct' to store all these variables. (for a single map lookup in functions that use/modify multiple variables).
Just a thought about a potential downside, if we use ZeppelinOS for upgradability, then we won't be able to modify the shape of that struct. But we could keep on adding new mappings.
The text was updated successfully, but these errors were encountered:
Currently the each variable relating to a token is in its own mapping. It could be more efficient to make a single collectable 'struct' to store all these variables. (for a single map lookup in functions that use/modify multiple variables).
Just a thought about a potential downside, if we use ZeppelinOS for upgradability, then we won't be able to modify the shape of that struct. But we could keep on adding new mappings.
The text was updated successfully, but these errors were encountered: