Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Library for Escalable Locks, Slimmest API? Date: Fri, 12 Aug 2016 22:18:16 +0200 Lines: 20 Message-ID: References: <26c75c11-5955-45a6-919d-3de1255c9c15@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 5kykpyCGgmuYPoCLnYdGgQPG8oDFRYOsnz+th1Xb2N8hgYLXQ= Cancel-Lock: sha1:SVdMCmETy8G0nSWvtlhGSeKkXJA= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:35275 On 11.08.2016 12:43, Jan Burse wrote: > I am planning to open source my new implementation > of ReadWrite locks, that do escalate.(*) But please do it with a big, red warning sign "There may be deadlocks!" > Possibly go with the first variant first, until > it is hardened. How do you harden something that inherently comes with the potential for deadlock? Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/