WaitableEvent incomplete docs, features

The WaitableEvent constructor documentation does not explain if the newly created event is in the signaled state or not.

There’s also no way to choose the signaled state at the time of construction.

Thanks, I’ll clarify that. It’s easy enough to call notify() immediately after construction if you want it to be initially signalled.

Not really. Lets say your ctor-initializer list that includes the WaitableEvent member is followed by a ctor-initializer for another class that constructs with the event object and waits on it immediately.

I’m adding bool initiallySignaled=false to the WaitableEvent ctor and then in PosixSharedCode and Win32Threads I will call signal() if its true.