I'm excited about the upcoming improvements to Structured Concurrency in Java 25 and would love to hear about the latest developments. I've read there's a significant upgrade coming, particularly with the StructuredTaskScope API, as mentioned in the JEP 505 documentation. Can anyone provide insights on what's changing and how it might solve current problems, particularly concerning handling declared exceptions?
3 Answers
One of the big changes is how exceptions thrown by subtasks are handled. They’re now wrapped in a FailedException, making it easier to deal with them through a switch or instanceof check. This new method might seem less fluid than before, but it definitely aligns better with the overall goal of simplifying concurrent programming. Plus, you have the flexibility to create your own Joiner to manage exceptions however you like!
Thanks for the explanation! I wanted to know more about the implications of that change.
It feels like Structured Concurrency has been in preview forever! It’s almost a joke at this point, given the various other major events happening in the world right now. It suggests to me that quality matters, and maybe they’re just taking their time to get it right. We need to provide feedback on these previews for them to move forward, so let’s keep at it!
Totally agree. If people aren't using it and providing feedback, it'll just drag on longer. We need to see enough engagement to justify making it permanent.
I also think the complexity of the API design plays a huge role in how long it stays in preview.
I was really counting on seeing this feature in Java 25, but it looks like we might have to wait for the next LTS release. The changes and scope values are expected to significantly affect frameworks, and it’s a bit disappointing to hear we might not get it just yet.
Just a heads up, OpenJDK doesn’t adhere to the LTS concept like some might expect.
Exactly! Remember, some features, like FFM, were rolled out without waiting for an LTS. So there’s still hope it could come sooner!
That's interesting! Would you say there’s a good way to manage this with generics for exceptions? I haven’t heard about that around.