Re: "concurrency" branch updated

[John Wiegley]

>>>>> David Kastrup <address@hidden> writes:

> For example, Lua offers "coroutines" which are basically not more than
> independent stacks but not parallel execution: the corresponding functions,
> "yield" and "resume" both _take_ and _return_ values. Essentially, this is
> used as a control flow mechanism similar to function calls and returns, with
> the difference that such "functions" do not lose their place and local
> variables when "returning" but continue upon resuming.

What you describe sounds similar to several libraries used often in Haskell,
where continuations are used to shuttle control up and down a connected
pipeline of coordinated functions (see 'pipes' if interested). Parallel
execution cannot be automatically enabled there either, though it can be
injected between stages (see 'pipes-async').

John