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

fix: drop vavr (#2248)

Browse source
This commit is contained in:
Ronan Takizawa 2025-09-20 11:33:46 -06:00 • committed by GitHub
parent 343491bcdb
commit 57812486e1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/src/main/paradox/actors.md
View file

@ -827,8 +827,7 @@ That has benefits such as:
The @javadoc[Receive](pekko.actor.AbstractActor.Receive) can be implemented in other ways than using the `ReceiveBuilder` since in the
end, it is just a wrapper around a Scala `PartialFunction`. In Java, you can implement `PartialFunction` by
extending `AbstractPartialFunction`. For example, one could implement an adapter
to Vavr Pattern Matching DSL. See the [Akka Vavr sample project](https://github.com/akka/akka-samples/tree/2.5/akka-sample-vavr) for more details.
extending `AbstractPartialFunction`.
If the validation of the `ReceiveBuilder` match logic turns out to be a bottleneck for some of your
actors you can consider implementing it at a lower level by extending @javadoc[UntypedAbstractActor](pekko.actor.UntypedAbstractActor) instead

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

@ -467,8 +467,7 @@ be good to know that it's optional in case you would prefer a different approach
* direct processing because there is only one message type
* if or switch statements
* annotation processor
* Vavr Pattern Matching DSL
* pattern matching since JDK 14 ([JEP 305](https://openjdk.java.net/jeps/305))
* pattern matching since JDK 21 ([JEP 441](https://openjdk.org/jeps/441))
In `Behaviors` there are `receive`, `receiveMessage` and `receiveSignal` factory methods that takes functions
instead of using the `ReceiveBuilder`, which is the `receive` with the class parameter.