Added mutex unlockAll

[XeniaSiskaki]

Add possibility for user to release all locks for #14

[ronkorving]

Thanks @XeniaSiskaki !

Sorry for being so nitpicky about naming, I hope it doesn't hurt your motivation in your contribution. Changing it later would constitute a breaking change however, so I wanna make sure we get it right on the first try.

I think unlockAll is not technically correct. The mutex can only be locked zero or one time. Its state is very boolean. Your implementation of unlockAll does what we agreed upon in #14, which implies it doesn't actually unlock the mutex. You still need to call unlock to do that. This is good, but that does mean that unlockAll to me is a bit confusing a name.

What it does is, it forgets all waiting callbacks, so that after a call to unlock they will not be invoked. That's why in #14 I suggested calling it reset, which arguably is also not a great name. Suggestions very welcome, but IMHO unlockAll is a little bit confusing. Thoughts?

[XeniaSiskaki]

Hey, sorry for the late response, I was on vacation! I think I'll get to it this weekend, as I don't have much time on work days.

I agree that unlockAll doesn't describe what the function actually does. However, I still think reset is a bit vague as it doesn't explain what it resets. It's too general in my opinion. Maybe something like resetQueue would be more fitting?

[ronkorving]

Sure, that works for me 👍

[XeniaSiskaki]

Sorry, took me longer to get back to it!

[ronkorving]

No worries, thanks for your contribution!

[XeniaSiskaki]

@ronkorving when do you think this will make it into npm?