[#9] Add support for atomic updates with Mutekt models #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes: How do you do atomic update with this ? #9
As discussed: Adding support for atomic updates for two or more state field updates #12
For example: If the following is a model
Then, atomic update will be possible with
update{}
method:Here, on mutating
loading
andnotes
field of a state, only a a single value will be emitted as a state without affecting the current coroutine dispatcher.MutektState
andMutektMutableState
. Mutable model implements it.