Go Concurrency Patterns: Pipelines and cancellation

Re:Go Concurrency Patterns: Pipelines and cancellation by dack on Friday March 14, 2014 @12:34AM (#7397004)

I think one huge difference is that a channel in Go is a stream of data, in which each element can cause the consuming code to wait for new responses. In your example, the future can only return one bit of data.

Afaik, what Go does is just an implementation of http://en.wikipedia.org/wiki/Communicating_sequential_proces... which is also available in some other languages (Clojure is the one that comes to mind for me). In Java, I think a closer analogy is a http://docs.oracle.com/javase/7/docs/api/java/util/concurren... which lets the producer and consumer threads automatically work in lock step as well.

[ Parent | on HN ]

Re:Go Concurrency Patterns: Pipelines and cancellation by crypto5 on Friday March 14, 2014 @02:12AM (#7397231)

> I think one huge difference is that a channel in Go is a stream of data, in which each element can cause the consuming code to wait for new responses. In your example, the future can only return one bit of data.

In java you also can do something like:

List<Future<Long>> futures = new ArrayList<>();

for(int i = 0; i < n; i ++) futures.add(some parallel execution logic);

long count = 0;

for(Future<Long> f: futures) count += f.get();

[ Parent | on HN ]