Because of how the replace operations were defined it acts on the whole Store at once. This is data inefficient and a it makes it so updates via changes clumsy. If the replace operation also included the index into the store being modified it should have the same properties of the current replace.
Because of how the replace operations were defined it acts on the whole
Store
at once. This is data inefficient and a it makes it so updates via changes clumsy. If the replace operation also included the index into the store being modified it should have the same properties of the current replace.