RFR 8010182: Thread safety of Thread get/setName()

Florian Weimer fweimer at redhat.com
Tue May 21 06:32:42 UTC 2013

On 05/21/2013 07:07 AM, Mike Duigou wrote:
> Since the char array is never modified it could use the String(char[], boolean) constructor. This has advantages for cases such as logging which may read the thread name very many times.

Couldn't we store the original string instead?

Florian Weimer / Red Hat Product Security Team

More information about the core-libs-dev mailing list