I'm deconstructing the argument on like 20 places in my application :
flow.mapAsync { case res :: errors :: result :: HNil => ... }
and now pattern matching will have to be used everywhere for the argument
to be deconstruced ... this interface is really unfortunate
On Tuesday, April 28, 2015 at 7:24:34 AM UTC+2, Jakub Liska wrote:
>
> Hey,
>
> shouldn't the :
>
> Flow#mapAsync(parallelism: Int, f: Out ⇒ Future[T]): Repr[T, Mat]
>
> method have this signature :
>
> Flow#mapAsync(parallelism: Int)(f: Out ⇒ Future[T]): Repr[T, Mat]
>
> as scala collection foldLeft, so it could be called like :
>
> Flow[Resource].mapAsync(4) { res => asyncCode }
>
> It is always a drag to call methods with function argument if multiple
> arguments are present...
>
--
>>>>>>>>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
