<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Right but then you can’t reclaim ‘a’ especially with a finalizer but even then it will break all sorts of things even when it doesn’t. </div><div dir="ltr"><br><blockquote type="cite">On Jul 31, 2024, at 12:25 PM, Pedro Lamarão <pedro.lamarao@prodist.com.br> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">In the situation being considered, the finally block will never, ever, run.<div>What is the meaning of requiring that this effect be ordered before or after some point in time?</div><div>Effects that will never, ever, happen, have no place in time to be ordered here or there.</div><div>The machine cannot fail to properly order an effect that will never, ever, happen.</div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua., 31 de jul. de 2024 às 14:16, robert engels <<a href="mailto:robaho@icloud.com">robaho@icloud.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="ltr"></div><div dir="ltr">More specifically, it is that ‘a’ cannot be reclaimed and the finally not run. This breaks the program ordering guarantees as related to retainability. </div><div dir="ltr"><br><blockquote type="cite">On Jul 31, 2024, at 11:59 AM, Pedro Lamarão <<a href="mailto:pedro.lamarao@prodist.com.br" target="_blank">pedro.lamarao@prodist.com.br</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">This seems to me a simple contradiction of requirements.<div>One cannot require that this program behaves as stated, that this thread cannot proceed, and then require that the finally block runs.</div><div>Either the thread can proceed, or it cannot.</div><div>If it cannot, requiring that this thread runs code is nonsensical to me.</div><div>Perhaps one should just revise one's queue design and/or implementation to avoid becoming "impossible" instead.</div><div>The fact the queue in question allows for "zombie platform thread" does not seem a feature to me.</div><div>"zombie platform threads" is just a resource leak in a system with no automatic resource reclamation.</div></div>
</div>
</div></blockquote></div></blockquote></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Pedro Lamarão</div></div></div></div>
</div></blockquote></body></html>