On Dec 18, 2013, at 7:55 PM, Nathan Myers <[email protected]> wrote: > On 12/18/2013 07:07 PM, Patrick Walton wrote: >> (dropping messages, or exploding in memory consumption, or >> introducing subtle deadlocks) are all pretty bad. It may well > > be that dropping the messages is the last bad option, because >> the last two options usually result in a crashed app... > > As I understand it, getting into a state where the channel would > drop messages is a programming error. In that sense, terminating > the task in such a case amounts to an assertion failure. > > In the case of Servo, somebody needs drop excess events > because it makes no sense to queue more user-interface actions > than the user can remember.
By that logic, you'd want to drop the oldest unprocessed events, not the newest. -Kevin _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
