"JEP 525 continues the evolution of the structured concurrency API that has been refined across multiple preview rounds since JDK 21, aiming to make concurrent task management clearer, safer, and easier to reason about than traditional ExecutorService/Future patterns. While this iteration makes minor but useful tweaks, the core model remains stable. Structured concurrency treats groups of related tasks as a single unit of work, improving cancellation, error propagation, and observability compared to ad-hoc thread management."
"Unlike Preview 5, which replaced constructors with static factory methods and introduced richer policies, Preview 6 focuses on a set of small, incremental refinements to the API. Structured concurrency scopes can be configured with a timeout. Prior to this preview, a timed-out would immediately throw aTimeoutException. Preview 6 introduces a new callback on , letting custom joiners react to timeouts and return partial or fallback results instead of always throwing."
JEP 525 (Structured Concurrency Sixth Preview) has been completed for JDK 26, continuing refinements begun in JDK 21 to simplify and make concurrent task management safer and more observable. The API centers on java.util.concurrent.StructuredTaskScope and an abstraction that controls how and when results from forked subtasks are combined. Preview 6 applies small incremental refinements rather than large redesigns. Scopes can be configured with timeouts and now support a timeout callback that lets custom joiners supply partial or fallback results. Common joiners were streamlined: allSuccessfulOrThrow() now returns a value directly and anySuccessfulResultOrThrow() was renamed to anySuccessfulOrThrow(). The basic usage pattern of opening a scope and forking subtasks remains unchanged.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]