Closed kfernandez31 closed 1 year ago
v2 - resolved @piodul 's comments apart from this one:
Another thing is the "Peering" part. Due to the problems highlighted above, I don't think map_mut and friends should provide access to the container because it would allow creating more references to the same shard-local instances.
I'd like to know whether the security checks I added have addressed your concerns or should I go ahead and rescind the access to the container of mut-maps.
v3: further comment resolution @piodul review ping
This branch introduces:
_mut
counterparts, which allow for regular mutability, instead of interior mutability. Note, however, thatstop
still requires interior mutability, should you want to alter the service's state.peering_sharded_service
, through which instances can communicate and delegate work.