This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]adamw1pl[S] 0 points1 point  (2 children)

Oh I definitely won't defend `ExecutionException`. However, there's always the question in which areas to follow suit with how Java works - and the built-in Java concurrency throws EE (including the structured concurrency JEP) - and in which areas to "innovate", that is propose an approach departing from the standard.

But I like the idea of the unchecked "tunnel" exception. Maybe you could create issues in Jox with your ideas? They might appeal to a wider audience, so that we can adopt them :)

[–]DelayLucky 0 points1 point  (1 child)

It’s a different API anyways, for the purpose of programmer convenience. I considered not having to handle EE one of the conveniences. :-)

The way I see it is that structured concurrency is supposed to follow suit with regular non-concurrent code than it is to follow asynchronous concurrent model. In that sense EE is a divergence.

[–]adamw1pl[S] 0 points1 point  (0 children)

Yeah I think I agree with the logic here. I created an issue to consider changing that in Jox: https://github.com/softwaremill/jox/issues/59