Oct. 14, 2019
10:21 p.m.
Noury - I happened to notice in a recent article about the Rust scheduler (it caught my eye) it had a section on concurrent testing and a tool they write called Loom to test all possible permutations and catch errors. This might be an avenue of investigation for your work ? An idea any way. https://tokio.rs/blog/2019-10-scheduler/ Sent from my iPhone
On 4 Sep 2019, at 14:31, Noury Bouraqadi <bouraqadi@gmail.com> wrote:
Hi everyone,
Can I get your input on the following questions :
- What are your best practices and recommendations for developing and testing concurrent software?
- How to discover need for synchronization/critical sections/ when doing TDD?
- How to write code to avoid dead-locks?
Noury