[concurrency-interest] RRWL with 'bad' Thread.getId() implementations

Martin Buchholz martinrb at google.com
Tue Jun 25 17:13:29 EDT 2013


On Tue, Jun 25, 2013 at 1:55 PM, Stanimir Simeonoff <stanimir at riflexo.com>wrote:

> WeakReference obviously,
> Like I've said: Thread.id is a cheap hack for == and weak reference.
> Alternative incl. eetop field.
>
>
We the maintainers of RRWL dislike the use of both ThreadLocals and
WeakReferences and wish that RRWL could be implemented without either.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20130625/4ff88a92/attachment.html>


More information about the Concurrency-interest mailing list