Tasks and communication

[rust-highfive]

Issue by larsbergstrom
Wednesday Jul 16, 2014 at 13:30 GMT

For earlier discussion, see rust-lang/rust#15713

This issue was labelled with: A-concurrency, A-libs, A-servo in the Rust repository

---

Currently, any large program using tasks and channels will have a mixture of deadlocks and unpredictable task failures due to the interaction of task failure, channel communications, and asynchronous communication protocols.

Ideas in this space:

• Controlled tear-down behavior, ala either the old linked task failure or something else easier to implement for a group of tasks.
• Static protocol checking to ensure progress / avoid deadlock or livelock. Note that, unlike much of the existing literature, this needs to be robust in the face of both async. comm. and async. + multiple failures.

CC: @pcwalton

[larsbergstrom]

Please close - we're planning to do this on our side instead.