1.
Why not to add this methods to mutex itself.

local m = effil.mutex()
m:unique_lock(function()
  -- 
end)

2. Idiom for this is synchronized.
https://docs.oracle.com/javase/tutorial/essential/concurrency/syncmeth.html

3. Can we add regular C'like mutex?

1.
Why not to add this methods to mutex itself.

Yes, it's a good idea

2. Idiom for this is synchronized.
https://docs.oracle.com/javase/tutorial/essential/concurrency/syncmeth.html

I don't get what you mean

3. Can we add regular C'like mutex?

Instead of this implementation or in addition to?

Rename this stuff from unique_lock to synchronized or something like it.
And add regular mutex, shared mutex and conditional variable.

We don't really need regular mutex if we have shared mutex (just use unique lock). If we have two types of locks 'shared' and 'unique' then 'synchronized' is not really good option.

Condition variable is a good idea too, but it can be implemented separately.

Is there still a desire to merge this? defined mutex would be nice as opposed to just using channel

closes #171