Wrap user stash to avoid confusion between PersistentActor.UnstashAll… #1757
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.
… and PersistentActor.Stash.UnstashAll
I do find it fascinating (for lack of a better word) that
Unstash()
andUnstashAll(predicate)
do not get the same treatment asUnstashAll()
, i.e. prepending the user stash messages to the_internalStash
. It may come up in the future.