concurrency
Jason House
jason.james.house at gmail.com
Mon Feb 4 07:51:37 PST 2008
Sean Kelly Wrote:
> Bedros Hanounik wrote:
> > I think the best way to tackle concurrency is to have two types of functions
> >
> > blocking functions (like in the old sequential code execution)
> >
> > and non-blocking functions (the new parallel code execution)
> >
> > for non-blocking functions, the function returns additional type which is true when function execution is completed
>
> This is basically how futures work. It's a pretty useful approach.
>
>
> Sean
I've never heard of that. Does anyone have a good link for extra detail on futures?
More information about the Digitalmars-d
mailing list