Another day, another concurrency bug that could have been avoided with linear types. Any timely users noticing a surprising deadlock with distributed mode, or process-local zero copy, grab the back-ported 0.7.2 timely_communication crate. https://github.com/frankmcsherry/timely-dataflow/pull/197/files …
By "linear types" you mean "force you to use the value"? How would that have prevented your bug?
-
-
The thing I probably should do / have done is make sure messages (things stashed in the queue) can't be dropped except in a controlled manner. In the context of timely, dropping a message w/o processing is guaranteed deadlock.
-
I see. It's not a perfect fix, but there are two options that can be useful: tagging the type(s) with `#[must_use]` and having a `Drop` impl that panics (and then invoking `mem::forget` once successfully processed).
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.