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

Merge pull request #27872 from franciscolopezsancho/avoid-migrating-to-typed-wording

Browse source 
changing wording in docs. From 'migrating' to 'upgrade'
This commit is contained in:
Patrik Nordwall 2019-10-03 15:52:43 +02:00 • committed by GitHub
commit 2566912fca
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
akka-docs/src/main/paradox/typed/style-guide.md
View file

@ -91,7 +91,7 @@ Some reasons why you may want to use the object-oriented style:
* You are more familiar with an object-oriented style of structuring the code with methods
in a class rather than functions.
* Some state is not immutable.
* It could be more familiar and easier to migrate existing classic actors to this style.
* It could be more familiar and easier to upgrade existing classic actors to this style.
* Mutable state can sometimes have better performance, e.g. mutable collections and
avoiding allocating new instance for next behavior (be sure to benchmark if this is your
motivation).
@ -111,7 +111,7 @@ Some reasons why you may want to use the object-oriented style:
* Some state is not immutable, e.g. immutable collections are not widely used in Java.
It is OK to use mutable state also with the functional style but you must make sure
that it's not shared between different actor instances.
* It could be more familiar and easier to migrate existing classic actors to this style.
* It could be more familiar and easier to upgrade existing classic actors to this style.
* Mutable state can sometimes have better performance, e.g. mutable collections and
avoiding allocating new instance for next behavior (be sure to benchmark if this is your
motivation).