focusedId=14750017&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14750017
>
>
> Cheers,
> √
>
>
> *Viktor Klang*
> Software Architect, Java Platform Group
> Oracle
> --
> *From:* Viktor Klang
> *Sent:* Thursday, 6 February 2025 11:51
>
t; This change is likely going to need some extra verbiage in the spec for
> mapConcurrent, and thus a CSR. This behavior aligns mapConcurrent with how
> parallel streams work in conjunction with interrup...
> github.com
>
>
> Cheers,
> √
>
>
> *Viktor Klang*
> Softw
them.
>
> Cheers,
> √
>
>
> *Viktor Klang*
> Software Architect, Java Platform Group
> Oracle
> --
> *From:* Jige Yu
> *Sent:* Monday, 27 January 2025 17:00
> *To:* Viktor Klang
> *Cc:* core-libs-dev@openjdk.org
> *Subject
Hi!
>
> Please see: https://github.com/openjdk/jdk/pull/23100
>
> Cheers,
> √
>
>
> *Viktor Klang*
> Software Architect, Java Platform Group
> Oracle
> --
> *From:* Jige Yu
> *Sent:* Sunday, 26 January 2025 23:03
> *To:* Vik
for not preserving the encounter order, that would be a completely
> different thing, and I'd encourage you to experiment with that if that
> functionality would be interesting for your use-case(s).
>
> Again, thanks for your feedback!
>
> Cheers,
> √
>
>
> *Viktor Kl
Hi Java Experts,
I sent this email incorrectly to loom-dev@ and was told on Reddit that
core-libs-dev is the right list.
The question is about the behavior of mapConcurrent() when the thread is
interrupted.
Currently mapConcurrent()'s finisher phase will re-interrupt the thread,
then stop at wha
