<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 02/05/2025 16:17, Pavel Rappo wrote:<br>
<blockquote type="cite" cite="mid:CAChcVu=h6rHaT2Reyp3yEmCQe4OX4ME2fKWZ=i7t-cqXGECg5w@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">I've recently re-read documentation for ScheduledExecutorService. I
noticed that the documentation uses the term "enabled", but does not
define it. The semantics of the term feels almost intuitive, but not
quite.
To check my intuitions, I searched through the package documentation
and source comments. I found usages of "enabled" in similar context of
the time-scheduled task execution. Some of those usages are
descriptions that are close to a proper definition. However, those
descriptions are scattered through implementations of
SchedulledExecutorService.
I wonder if it makes sense to properly define "enable"/"enabled" in
SchedulledExecutorService.
</pre>
</blockquote>
As it happens, this came up recently when updating ForkJoinPool to
implement ScheduledExecutorService . FJP class description make it
clear what "enabled" means. It could potentially copied into SES.<br>
<br>
-Alan<br>
</body>
</html>