Bikeshedding Structured Concurrency

[David Alayachew]

Hello Chen.

I'd agree with you if we were describing a parameter. But when describing
what we are returning, I think it causes needless confusion.

Remember, STS will catch ALL THROWABLES and serve them via that method.
That includes things like OOME and StackOverflowError. I imagine that most
developers would appreciate having the method name be throwable() if stuff
like those can come down the pipe.

On Fri, Aug 1, 2025 at 1:23 AM Chen Liang <liangchenblue at gmail.com> wrote:

> Hi David, I think it is a convention to use the lowercased "exception" to
> refer to all throwable. This is for example seen in the title of JLS 11.
>
> On Fri, Aug 1, 2025, 00:06 David Alayachew <davidalayachew at gmail.com>
> wrote:
>
>> Hello @loom-dev <loom-dev at openjdk.org>,
>>
>> I have been enjoying the Structured Concurrency JEP's as they have come,
>> and I am excited to try the JDK 25 variant with all the new changes with
>> Joiner.
>>
>> I have a bikeshed request.
>>
>> For Subtask, can we change the method name from exception() to
>> throwable()? It more accurately describes what is happening.
>>
>> Thank you for your time and help.
>> David Alayachew
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20250801/844748e0/attachment-0001.htm>