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
As #16568 suggests, the platform should not depend on the implementation of the state. And the fact that State is a Merkle tree is that implementation detail. It should removed from the class name. However, the name StateLifecycle would be confusing as well, as the state lifecycle denotes a different thing. Specifically, it can be represented by this diagram:
In this case we're dealing with SwirldsState lifecycle. That's, a platform perspective of the state. So, the better name for the interface should be SwirldsStateLifecycle
The text was updated successfully, but these errors were encountered:
As #16568 suggests, the platform should not depend on the implementation of the state. And the fact that
State
is a Merkle tree is that implementation detail. It should removed from the class name. However, the nameStateLifecycle
would be confusing as well, as the state lifecycle denotes a different thing. Specifically, it can be represented by this diagram:In this case we're dealing with
SwirldsState
lifecycle. That's, a platform perspective of the state. So, the better name for the interface should beSwirldsStateLifecycle
The text was updated successfully, but these errors were encountered: