ary 2025 17:04
To: Viktor Klang
Cc: core-libs-dev@openjdk.org
Subject: Re: [External] : Re: mapConcurrent() with InterruptedException
Sorry, did the PR stop using Semaphore?
I had naively thought that mapConcurrent() will keep a buffer of Future of all
currently-running concurrent tasks (it
*To:* Jige Yu
> *Cc:* core-libs-dev@openjdk.org
> *Subject:* Re: [External] : Re: mapConcurrent() with InterruptedException
>
> I think alignment in behavior between parallel Stream and mapConcurrent in
> terms of how interruptions are handled is a possible path forward.
>
> I d
: Re: [External] : Re: mapConcurrent() with InterruptedException
I think alignment in behavior between parallel Stream and mapConcurrent in
terms of how interruptions are handled is a possible path forward.
I decided to close the PR for now as I realized my parallel Stream example had
misle
ore-libs-dev@openjdk.org<mailto:core-libs-dev@openjdk.org>
mailto:core-libs-dev@openjdk.org>>
Subject: Re: [External] : Re: mapConcurrent() with InterruptedException
Thanks Viktor!
I understand the problem.
The main reason I asked is because I want to understand how the core Java team
think
are Architect, Java Platform Group
> Oracle
> --
> *From:* Jige Yu
> *Sent:* Wednesday, 5 February 2025 16:24
> *To:* Viktor Klang
> *Cc:* core-libs-dev@openjdk.org
> *Subject:* Re: [External] : Re: mapConcurrent() with InterruptedException
>
>
jdk.org<mailto:core-libs-dev@openjdk.org>
mailto:core-libs-dev@openjdk.org>>
Subject: Re: [External] : Re: mapConcurrent() with InterruptedException
Thanks Viktor!
It looks like the current fix ignores interruption.
I want to make sure my concern of it defeating cancellation is heard an
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
: Monday, 27 January 2025 17:00
To: Viktor Klang
Cc: core-libs-dev@openjdk.org
Subject: Re: [External] : Re: mapConcurrent() with InterruptedException
Thanks Viktor!
It looks like the current fix ignores interruption.
I want to make sure my concern of it defeating cancellation is heard and
tor Klang
> *Cc:* core-libs-dev@openjdk.org
> *Subject:* [External] : Re: mapConcurrent() with InterruptedException
>
> Checking in on what you've found out, Viktor.
>
> From where we left off, I understand that you were looking at alternatives
> instead of silent truncatio
: mapConcurrent() with InterruptedException
Checking in on what you've found out, Viktor.
From where we left off, I understand that you were looking at alternatives
instead of silent truncation?
Have you reached any conclusion?
We touched on disallowing interruption during mapConcurrent(). I still
Checking in on what you've found out, Viktor.
>From where we left off, I understand that you were looking at alternatives
instead of silent truncation?
Have you reached any conclusion?
We touched on disallowing interruption during mapConcurrent(). I still have
concerns with disabling cancellatio
Hi Ben,
Thanks for raising these questions—getting feedback is crucial in the Preview
stage of features.
I wrote a reply to the Reddit thread so I'll just summarize here:
It is important to note that mapConcurrent() is not a part of the Structured
Concurrency JEPs, so it is not designed to joi
12 matches
Mail list logo
