+1
It definitely reads better with curried arguments.
best
Carsten
Am Dienstag, 28. April 2015 13:12:38 UTC+2 schrieb Konrad Malawski:
On a personal style-preference note I’m with Jakub here.
While not specifically required for inference or things like that, it does
read/write itself
Roland you are right with the arguments applying to foldLeft only, but this
is just a syntactic matter. MapAsync is one of the most frequently used
stream combinators and the streams would loose readability significantly
like this ...
On Tuesday, April 28, 2015 at 10:38:17 AM UTC+2, rkuhn
Hello,
Sorry, I don't see how this:
.mapAsync(parallelism = 7) { res =
...
}
is any better readable than this:
.mapAsync(parallelism = 7, { res =
...
})
The second makes it more obvious that the {...} block is part of a method
call.
Best, Oliver
On Tue, Apr
Oliver: personally I’m with you on this one, for me there is no big difference
between the two, but since the Scala style guide recommends one of them I
prepared a PR https://github.com/akka/akka/pull/17328.
Jakub: thanks for raising this point—even though personally I don’t see how the
RC1
On a personal style-preference note I’m with Jakub here.
While not specifically required for inference or things like that, it does
read/write itself nicer with 2 parameter lists.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 28 April 2015 at 12:53:30, Jakub Liska
I have to admit that I prefer the curried argument list in this case. It
reads more DSLly:
.mapAsync(parallelism = 7) (do stuff)
-Endre
On Tue, Apr 28, 2015 at 10:38 AM, Roland Kuhn goo...@rkuhn.info wrote:
More reasoning (but please correct me): for foldLeft the curried argument
list is
I too would prefer to see the curried style used for the reasons @Odd
mentioned.
--
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
+1
On 28.04.2015, at 12:10, Reid Spencer r...@reactific.com wrote:
I too would prefer to see the curried style used for the reasons @Odd
mentioned.
--
You received this message because you are subscribed to the Google Groups
Akka Developer List group.
To unsubscribe from this group
Another reason to prefer the curried argument list in this case is to allow
the following style:
.mapAsync(parallelism = 7) { res =
...
}
and:
.mapAsync(parallelism = 7) {
case ...
}
The Scala Style Guide mentions it here:
I'm on the phone right now and might be missing something but shouldn't the
following work?
.mapAsync(4, { case …})
Regards,
Roland
Sent from my iPhone
On 28 Apr 2015, at 07:37, Jakub Liska liska.ja...@gmail.com wrote:
I'm deconstructing the argument on like 20 places in my application
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
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
Thanks for pointing that one out!
I fixed the page: https://github.com/akka/akka.github.com/pull/196
Thanks again and happy hakking!
-- konrad
W dniu niedziela, 26 kwietnia 2015 14:13:32 UTC+2 użytkownik Anton Kulaga
napisał:
akka-http-testkit-experimental_2.11 changed to
akka-http-testkit-experimental_2.11 changed to
*akka-http-scala-experimental_2.11*.
Thanks for the clarification. Could you please update http://akka.io/docs/
as there are names without scala suffix there.
On Saturday, April 25, 2015 at 10:22:13 AM UTC+3, Patrik Nordwall wrote:
The artifact
What about Websockets, as I understood they are supported in RC-1 but is
there anything in documentation that explains how to use them in akka-http?
On Friday, April 24, 2015 at 10:19:13 PM UTC+3, Patrik Nordwall wrote:
Dear Hakkers,
we—the Akka committers—are exceptionally proud to present
@patrik That works better. Thank you for the clarification. /Magnus
2015-04-25 9:22 GMT+02:00 Patrik Nordwall patrik.nordw...@gmail.com:
The artifact name of akka-http-experimental_2.11 has been changed to
*akka-http-scala-experimental_2.11*.
akka-http-testkit-experimental_2.11 changed to
The artifact name of akka-http-experimental_2.11 has been changed to
*akka-http-scala-experimental_2.11*.
akka-http-testkit-experimental_2.11 changed to
*akka-http-testkit-scala-experimental_2.11*.
Same with the _2.10 artifacts. Sorry that we missed that in the
announcement.
/Patrik
On Fri, Apr
Is there any documentation about the new websocket api?
On Friday, 24 April 2015 23:04:37 UTC+2, Magnus Andersson wrote:
By the way
These packages seems to be missing:
com.typesafe.akka:akka-http-experimental_2.11:1.0-RC1
com.typesafe.akka:akka-http-testkit-experimental_2.11:1.0-RC1
Very nice work! Excited to get started.
I was asking about TLS for akka-http just a few hours ago in another
thread. Really hoping you manage to squeeze the high level APIs into 1.0.
In the mean time, are there some examples of SSL+HTTP (HTTPS) for client
connections? I don't mind using
By the way
These packages seems to be missing:
com.typesafe.akka:akka-http-experimental_2.11:1.0-RC1
com.typesafe.akka:akka-http-testkit-experimental_2.11:1.0-RC1
Looked at the Maven repo and RC-1 were not present:
https://repo1.maven.org/maven2/com/typesafe/akka/akka-http-experimental_2.11/
20 matches
Mail list logo
