8231602: Deprecate Thread.suspend/resume for removal
Chris Hegarty
chris.hegarty at oracle.com
Wed Oct 23 09:15:51 UTC 2019
> On 22 Oct 2019, at 19:25, Alan Bateman <Alan.Bateman at oracle.com> wrote:
>
> ...
> Here's the webrev with the changes to deprecate-for-removal Thread.suspend/resume, ThreadGroup.suspend/resume, and ThreadGroup.allowThreadSuspsion:
> http://cr.openjdk.java.net/~alanb/8231602/webrev/index.html
This look ok.
The CSR makes reference to Project Loom. I assume that this advancement
effort of ordinarily deprecated methods to terminally deprecated
methods, is in part, related to the recent discussion on loom-dev [1]:
"The Thread API does come with baggage (ThreadGroup, TCCL, ...) but it
may not be too bad when you consider that most developers don't use
the Thread API directly. In addition, we can degrade and/or eliminate
at least some of this baggage over time, starting with the deprecated
features."
While orthogonal to this JIRA issue, 8231602 says: "It's time to dial
this up to forRemoval=true so these methods can be removed in a future
release." - Is there a planned release where these methods will be
removed? If so, what is that release?
-Chris.
[1] https://mail.openjdk.java.net/pipermail/loom-dev/2019-October/000796.html
More information about the core-libs-dev
mailing list