This document is about Task, an alternative for Scalaz's Task or Scala's Future.
Note this is work in progress and this document suffered multiple modifications already:
UPDATE - May 30, 2016 - This document is now obsolete, replaced by the Monix Task documentation:
@puffnfresh: 👍
Hi all,
You might be interested to look at my matterhorn experiment: https://github.com/aloiscochard/matterhorn
It is basically a specialized interpreter for IO actions: https://github.com/aloiscochard/matterhorn/blob/master/core/src/main/scala/rts/Interpreter.scala
There is some tests and benchmarks showing how it work:
https://github.com/aloiscochard/matterhorn/blob/master/core/src/test/scala/CoreSpec.scala
https://github.com/aloiscochard/matterhorn/blob/master/bench/src/main/scala/pure.scala
The approach to concurrency is to use a STM, I just did plug a library for having rapid prototyping.
Good luck
@aloiscochard, @puffnfresh thanks, will take a look.
scalaz.concurrent.Task is not very good. Using just a reasonable IO type, it should be possible to subsume Task's use cases with some uses of MVar-like atomic-references. For example:
I agree, and that is the route we are going with FS2's Task type (which I suppose could be renamed to 'IO'), which implements MVar-like references and then uses that to implement async (and lots of other operations, like parallelTraverse, as well as all the concurrent stream operations of FS2 itself): https://github.com/functional-streams-for-scala/fs2/blob/topic/redesign/core/src/main/scala/fs2/Async.scala#L75
scalaz.concurrent.Task is not very good. Using just a reasonable IO type, it should be possible to subsume Task's use cases with some uses of MVar-like atomic-references. For example:
scalaz/scalaz@series/7.3.x...puffnfresh:feature/concurrent-io
I highly recommend focusing on doing a good job at I/O and then using that to talk about concurrency, rather than trying to do the opposite.