<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 19/12/2025 08:33, David Alayachew
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAA9v-_PO9Rgg8mX=U30y0WUhkg_oDzdLZXf_MFAHgniJrDeN5g@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-family:monospace">And
maybe it'll help if I clarify what I was saying to <a class="gmail_plusreply" id="m_755086139635793918plusReplyChip-7" href="mailto:holo3146@gmail.com" target="_blank" moz-do-not-send="true">@Holo The Sage Wolf</a>.</div>
<div class="gmail_default" style="font-family:monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace">Holo
is saying that they like the default joiner, but adding a
timeout to it takes more code than necessary. They proposed
multiple different overloads, but I suggested the following
overload instead.</div>
<div class="gmail_default" style="font-family:monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace">StructuredTaskScope.open(UnaryOperator<StructuredTaskScope.Configuration>
configOperator)</div>
<br>
</div>
</div>
</blockquote>
<br>
There are two built-in joiners that implement the policy to cancel
the scope and cause join to throw if any subtask fails. One is
suited to subtasks that produce results of the same type. It can
collect the results and have join yield the list of results. The
other is suited to subtasks that produce results of very different
types and where it is more convenient to retain the Subtask returned
from fork. The feedback to date on which would be the better default
is inconclusive. The choice influences the return from the 1-arg
open method is being discussed here, and is why it is not included
in the current API.<br>
<br>
-Alan<br>
</body>
</html>