* One does not "simply"
* It's not obvious
* It's not really _that_ easily done
* Basically is basically a useless word
* Of course - if you already know how things work you wouldn't be reading the docs
* Clearly is maybe not so clear for everyone
* Just was just a bit harder as there are some uses that are just
* add java support in akka-actor module in the class Abstract.ActorContext by adding the setReceiveTimeout and CancelReceiveTimeout
* add akka.actor.AbstractActor#ActorContext cancelReceiveTimeout and setReceiveTimeout to mima-excludes file
* removed scala.concurrent.duration dependency in ActorDocTest and add new method expectTerminated with java.time.Duration support in TestKit
* used java.time.Duration as default import
* +str,typ introduce akka typed ask for akka stream
address feedback and add actor interop stages incl ask to docs
more compile tests and adjusted things
last docs
* document adding stages to docs in CONTRIBUTING
* address review comments
* rebase conflicts
`groupBy`'s default behavior is to filter elements, that would go to a substream
that is already closed. This allows `groupBy` to recreate those already closed streams,
if wanted, and run them as if they would've never run before in the first place.
Overload instead of default parameter
Make set of closed keys unmodifiable if not needed
Adjust documentation, adding a warning on memory consumption.
Add MiMa exclude.
* Documented wrapping PersistentBehavior in typed actors persistence documentation #24679
* Removed "Current Limitations" section
* Added description on wrapping PersistentBehavior
* Added Scala and Java example for the pattern
* updated persistence docs for the hinted changes
* added missing "the" as requested in the hint
* automatic throttle burst size, #24699
* throttleEven used maxBurst=Int.MaxValue, which in practise resulted
in no throttling at all at high rates
* The original problem that throttleEven tried to solve was that when
the throttle rate (cost / per) was high the cost of scheduling
dominated and became much lower than the given rate, if 0 or low
maxBurst was given. Difficult for user to know what maxBurst to use.
* In fact, that was already the case for rates > 30/s.
* This is fixed by automatically adjusting the maxBurst for higher
throttle rates in a new throttle overload that doesn't include
maxBurst parameter
* Also skipped the mode parameter for that variant since Shaping is
what almost always is what you want, and otherwise you can use
the full signature with a good maxBurst
* Deprecated throttleEven, since it is the same. Also fixed the
implementation of throttleEven to use the automatic burst size,
since Int.MaxValue is not useful at all.
