On Thu, Apr 24, 2014 at 5:13 PM, √iktor Ҡlang <viktor.kl...@gmail.com>wrote:
> Because there are many potential implementations, we explicitly opted out > of flatMap. For now. > > Probably a good decision. Otherwise people will complain when you remove it again. You can always implicit your own. Maybe have a canonical flatMap available that has to be implicitly imported. I just wanted to confirm that there is no fundamental limitation. > A minor correction: Akka Streams (Flow etc) will never become a standard > for the JVM. > The standardization effort is Reactive Streams and that is for interop > between implementations. As such it does not prescribe any DSL as that will > vary between JVM langs and libraries. > > Of course. I think the underlying interfaces are nice and simple and should work well from other JVM languages. What does the spec say about when you throw an (unchecked) exception in e.g. onNext? I did not see anything in https://github.com/reactive-streams/reactive-streams/blob/master/tck/src/main/resources/spec.md. You are allowed to call onNext synchronously from requestMore. Will the caller of requestMore get the exception, or will onError be called? cheers, Rüdiger -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
