
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Thanks for linking to the SO question. Honestly, all of those look ugly to me. I can’t believe a pretty standard use case requires that much code - it really hides the flow - which I feel is against the primary purpose of structured concurrency - to make this more obvious and reliable - not less.<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Aug 24, 2025, at 8:11 AM, Atakan Serin <serinatakan@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div>Hi,<div dir="auto"><br></div><div dir="auto">One experience using Structured Concurrency:</div><div dir="auto"><br></div><div dir="auto">When there is a timeout, even the succeded subtasks throws illegal state exception, I guess due to the fact that owner is not joined. This was not so convenient for me and had to find work arounds:</div><div dir="auto"><div><a href="https://stackoverflow.com/questions/79744109/how-to-get-partial-results-with-java-structured-concurrency-in-a-timeout-scenari">https://stackoverflow.com/questions/79744109/how-to-get-partial-results-with-java-structured-concurrency-in-a-timeout-scenari</a></div><br></div><div dir="auto">Best regards,</div><div dir="auto">Atakan</div>

</div></blockquote></div><br></body></html>