raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

=doc Fixed typos in actor documentation

Browse source
This commit is contained in:
Oleg Anashkin 2014-02-27 22:51:38 -08:00
parent d7283abfcb
commit e2b0bb8d65
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
akka-docs/rst/scala/actors.rst
View file

@ -891,8 +891,8 @@ Extending Actors using PartialFunction chaining
=============================================== ===============================================
Sometimes it can be useful to share common behavior among a few actors, or compose one actor's behavior from multiple smaller functions. Sometimes it can be useful to share common behavior among a few actors, or compose one actor's behavior from multiple smaller functions.
This is is possible because an actor's :meth:`receive` method returns an ``Actor.Receive``, which is a type alias for ``PartialFunction[Any,Unit]``, This is possible because an actor's :meth:`receive` method returns an ``Actor.Receive``, which is a type alias for ``PartialFunction[Any,Unit]``,
and partial functions can be chained together using the ``PartialFunction#orElse`` method. You can chain as many functions you need, and partial functions can be chained together using the ``PartialFunction#orElse`` method. You can chain as many functions as you need,
however you should keep in mind that "first match" wins - which may be important when combining functions that both can handle the same type of message. however you should keep in mind that "first match" wins - which may be important when combining functions that both can handle the same type of message.
For example, imagine you have a set of actors which are either ``Producers`` or ``Consumers``, yet sometimes it makes sense to For example, imagine you have a set of actors which are either ``Producers`` or ``Consumers``, yet sometimes it makes sense to