Structured concurrency: Difference between revisions

Content deleted Content added
Lucenty (talk | contribs)
rewrite introduction with an intention to be more descriptive and concise
Lucenty (talk | contribs)
m orderly --> expedient
Line 6:
 
==Variations==
A major point of variation is how an error in one member of a concurrent thread tree is handled. Simple implementations will merely wait until the children and siblings of the failing thread run to completion before propagating the error to the parent scope. However, that could take an indefinite amount of time. The alternative is to employ a general cancellation mechanism (typically a cooperative scheme allowing program invariants to be honored) to terminate the children and sibling threads in an orderlyexpedient manner.
 
==See also==