cleaned up yet, thought of a possibly better solution to
protecting mutices & associated data from premature deletion.
It wound up being a more involved permission system than a
simple attach & detach, at the start of the new system I had
thought to refuse threads not part of the group but then realised
there are legitiment cases where public permissions are needed,
such as a mutex for blocking io on standard file descriptors
meant for piped communication between processes, when an
opengl debug callback triggers there's no garuntee the thread it
triggers in is of the group so public permissions are needed
there, I stuck to the octal permissions linux usually uses so it
would be easy for devs to understand the source code, currently
the permission system is internal since it may need further
adaption before it is suitable for exposure, for now though I just
want to see if anyone sees any issues