<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">But why not? Future is pervasive - and then the user can easily switch between synchronous executors and async executors with no user code change - and 0 changes to the JDK.<div class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 7, 2023, at 3:32 PM, Attila Kelemen <<a href="mailto:attila.kelemen85@gmail.com" class="">attila.kelemen85@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Robert Engels <<a href="mailto:rengels@ix.netcom.com" class="">rengels@ix.netcom.com</a>> ezt írta (időpont: 2023. aug. 7., H, 20:58):<br class=""></div><div class="gmail_quote"><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" class=""><div dir="ltr" class=""></div><div dir="ltr" class="">I think by the time you cover all of the cases in the api - (eg interrupted/other exception) you are going to end up with the Future/Executor interface anyway. </div></div></blockquote><div class=""><br class=""></div><div class="">Sadly, I kinda agree with the part that the exceptions are a considerable issue for the interface, especially the most awkward `InterruptedException` (though ending up with Future is a bit of an exaggeration).</div></div></div>
</div></blockquote></div><br class=""></div></div></body></html>