jypma commented on issue #1801:
URL: https://github.com/apache/pekko/issues/1801#issuecomment-2912199445
@pjfanning Thanks for the clarification. However, I'm not fully
understanding the concrete way forward you're suggesting. Should I close the
PR, and retain this only as a separate library on a separate repository? I
don't expect I can give that the needed visibility on my own.
It would also be a lot less comfortable to use, since `Flow`, `Source` and
friends would lack first-class `Task` operators. This is particular challenge
for Java code bases, which is precisely what I envisioned for this change:
there really isn't a "nice" Java-friendly effect system out there. (Scala is
less of an issue, implicits can make anything glue together).
For this to be nice to use, we need to be able to (in Java) write things like
```java
Source.from(someStuff)
.mapTask(elem -> constructTask(elem))
.mapTask(res -> Task.connect(someOtherSource(elem), someOtherSink))
```
which is impossible in the current pekko API (since, besides type
conversions, `Materializer` is needed to invoke nested graph creations).
I'd prefer to keep the work open as an actual fork/PR of the main repo, with
frequent rebases. We can certainly delay an actual release (or even plan of
that) until a later time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org
For additional commands, e-mail: notifications-h...@pekko.apache.org
