Bryan Wilkinson

> unexpected result: everything is completed normally, but some children are cancelled for some reason The Java analogue: when you shutdown() an executor, new tasks are rejected despite no failure...

This restricts [modular testing](https://github.com/Kotlin/kotlinx-lincheck#modular-testing) to using only a single submodule.

Can you clarify whether support in only the runner would resolve #121 ?

With a time limit, changes to the system under test can result in gradually degraded test quality. What about configuring a limit on number of context switches explored, since lincheck...

It seems important to me to at least keep the door open to some form of "fixed quality" test. When it comes to correctness of my system, I can't take...

I don't have a formal measure of quality but I do know that my tests catch bugs/races/deadlocks that I introduce manually, which gives me some confidence that similar issues will...

I generally follow the same rules of thumb: "have at least three threads with three operations in each, reasonable (50-200) scenarios". I don't have a good way of tuning invocations...

Unfortunately I can't... If I find time I'll try to make a minimal example. But fyi, I use several low-level data structures like Semaphore and ConcurrentLinkedDeque/LinkedBlockingDeque. I was able to...

Here are efficient read-write lock and semaphore implementations that I would like to contribute. https://github.com/btwilk/kotlinx.coroutines/tree/new-sync/core/kotlinx-coroutines-core/src/main/kotlin/kotlinx/coroutines/experimental/sync I've been using them for a while without any problems but I would appreciate review...

I think tracking multiple owners is too much overhead for a low-level primitive, which is the main reason I didn't consider it. Also, the Mutex interface is pretty heavy. I...