Re: pthread_setname_np API is bad

[Martin Husemann <martin%duskware.de@localhost>]

On Fri, Aug 09, 2019 at 07:09:01PM +0200, Kamil Rytarowski wrote:
> Delayed adoption of a standardized version of pthread_setname()
> pthread_getname() will result in no API & ABI breakage with any existing
> code as we will keep our own _np() invention, at least until we will
> bump major number for libpthread. and drop redundant _np() variation

This is a good argument. And we may even opt to not drop the _np variant at
all.

However, if we go for this - why change anything at all right now?

Keeping everything unchanged, pushing for a posix version, and then adopt
that as soon as the signature is fixed sounds like a good plan to me.

If we touch it, we should do it cleanly.

Martin