From 6354aaf49420a2f9e21ee9fc23e3fe578e062ead Mon Sep 17 00:00:00 2001 From: Eric Loots Date: Wed, 11 Oct 2023 08:33:33 +0200 Subject: [PATCH] Integrate PR feedback - Point out that Union types are Scala 3 specific --- docs/src/main/paradox/typed/interaction-patterns.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/src/main/paradox/typed/interaction-patterns.md b/docs/src/main/paradox/typed/interaction-patterns.md index 75f9db36bc3..fac3197166a 100644 --- a/docs/src/main/paradox/typed/interaction-patterns.md +++ b/docs/src/main/paradox/typed/interaction-patterns.md @@ -117,8 +117,9 @@ Most often the sending actor does not, and should not, support receiving the res In such cases we need to provide an @apidoc[actor.typed.ActorRef] of the right type and adapt the response message to a type that the sending actor can handle. In the case of Scala, we need to make a distinction between Scala 2 -and Scala 3. In the latter case, we can actually get rid of the need to adapt the response message which vastly -simplifies the handling of responses. The details can be found in the section @ref:[Handling actor responses in Scala 3](handling-actor-responses-with-scala3.md). +and Scala 3. In the latter case, we can actually get rid of the need to adapt the response message by leveraging +Scala 3's Union types, which vastly simplifies the handling of responses. The details can be found in the +section @ref:[Handling actor responses in Scala 3](handling-actor-responses-with-scala3.md). **Example:**