8169425: Values computed by a ClassValue should not strongly reference the ClassValue

Jochen Theodorou blackdrag at gmx.org
Thu Nov 10 08:54:52 UTC 2016



On 09.11.2016 19:18, Doug Lea wrote:
[...]
> And: Similar cases can indeed occur with ThreadLocal, but users seem
> to mostly avoid them, sometimes after painful experience.

ThreadLocal is already a bad choice once you subclass it.

bye Jochen


More information about the core-libs-dev mailing list