<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="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 4 Jan 2023, at 16:57, <a href="mailto:forax@univ-mlv.fr" class="">
forax@univ-mlv.fr</a> wrote:</div>
<div class="">
<div style="caret-color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<br class="">
</div>
</div>
</blockquote>
<blockquote type="cite" class="">
<div data-marker="__QUOTED_TEXT__" style="caret-color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<div class="">Those suppressed exceptions are interesting, independently of the success of the computation.<br data-mce-bogus="1" class="">
</div>
<div class="">If each fork logs itself, you make the monitoring work harder because you are loosing the information that the errors are part of the same computation.<br data-mce-bogus="1" class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Logging a fork’s failure in its scope is not an effective mechanism for observing context because it’s only one level deep — the parent scope’s own context is lost, not to mention that it doesn’t provide context for any logging events that aren’t task
failures. Rather, the solution we have in mind for logging is to provide an API that allows observing the full context hierarchy for logging and monitoring purposes (i.e. you’ll be able to observe a stack of the hierarchy up to the root).</div>
<div><br class="">
</div>
<br class="">
<blockquote type="cite" class="">
<div data-marker="__QUOTED_TEXT__" style="caret-color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<div class=""><br class="">
</div>
<div class="">I do not see how the indirection can work given that the Future object returned by fork() is specific to a StructuredTaskScope ?<br data-mce-bogus="1" class="">
</div>
<div class=""><br class="">
</div>
</div>
</blockquote>
</div>
<div><br class="">
</div>
<div>Since we only care about completed futures anyway, what I had in mind is something like:</div>
<div><br class="">
</div>
<div><font face="Courier New" class=""> Supplier<Future<T>> sf = sts.fork(asCompletedFuture(() -> foo()));</font></div>
<div><br class="">
</div>
<div>where,</div>
<div><font face="Courier New" class=""><br class="">
</font></div>
<div><font face="Courier New" class=""> static <T> Callable<Future<T>> toCompletedFuture(Callable<T> task) {</font></div>
<div><font face="Courier New" class=""> return () -> {</font></div>
<div><font face="Courier New" class=""> try {</font></div>
<div><font face="Courier New" class=""> return CompletableFuture.completedFuture(task.call());</font></div>
<div><font face="Courier New" class=""> } catch (Exception ex) {</font></div>
<div><font face="Courier New" class=""> return CompletableFuture.failedFuture(ex);</font></div>
<div><font face="Courier New" class=""> }</font></div>
<div><font face="Courier New" class=""> });</font></div>
<div><font face="Courier New" class=""> }</font></div>
<br class="">
<div class="">This could be used when an association between exceptions and particular tasks is needed for uses other than logging. What I’m trying to ascertain is how frequently this is needed, where my hypothesis is not very frequently at all.</div>
<div class=""><br class="">
</div>
<div class="">Now, in addition to making the right thing more obvious, the Supplier approach directs the user into the right frame of mind when working with STS, i.e. to think of the forks as a unit rather than individual tasks, and anything that belongs to
the individual task should be done in the fork.</div>
<div class=""><br class="">
</div>
<div class="">— Ron</div>
</div>
</body>
</html>