I think its so obscure and changing core code that might burn others - we've
had fascinating lock/unlock bugs in 2.0.14-18 for example that unless you
can cite a POSIX.1/POSIX.4 reference on this it shouldnt be fixed in 2.0.x
To start with there may be other people relying on the existing behaviour
to wait for all threads of a task to exit...