Scalaz has some nice (usefully typed) concurrency tools:
https://github.com/scalaz/scalaz/tree/scalaz-seven/concurren...
https://github.com/scalaz/scalaz-stream
Like everything with Scalaz, the tools are great but almost completely undocumented.
> Like everything with Scalaz, the tools are great but almost completely undocumented.
Exactly. I will start considering scalaz once its authors grow up and realize that the lack of documentation is not a sign of quality.
Really now? As if these guys get paid to do create and fix scalaz all day right? Like Oracle yeah? This is the story about every single open source project. You can choose something else, wait it out for documentation, or contribute it. Lucky you even have the source!
Re:On Scala
by eli_gottlieb on Wednesday June 19, 2013 @07:48AM
(#5904953)
The maintainer and contributors have full-time jobs. On the one hand, part of that job is keeping up Scalaz for their own professional usage. On the other hand, no part of that job is documenting it for everyone else.
They could just have kept the code proprietary.
My understanding is that the new typed channels feature in the upcoming Akka 2.2 release will address this.
The macro feature introduced in Scala 2.10 makes this possible.
http://doc.akka.io/docs/akka/2.2.0-RC1/scala/typed-channels....
It's possible to make them typed with the stdlib[1]. Link also gives some reasons as to why they're untyped. Short answer is it started as a way to replicate Erlang in Scala[2].
[1] http://stackoverflow.com/questions/5547947/why-are-messages-...
What's the point of having a powerful type system like Scala's and then throw it out of the window just so I can use a distributed framework?