Thread-local successor for object pooling

[Kasper Nielsen]

As far as I could understand from the original email. The main use
case is reuse of expensive-to-create objects. So (as noted in the JEP)
a scoped value is probably not the right way to solve the problem.


/Kasper

On Mon, 31 Oct 2022 at 10:46, Andrew Haley <aph-open at littlepinkcloud.com> wrote:
>
> On 10/31/22 10:20, Volkan Yazıcı wrote:
> > JEP 429 (Scoped values) might be the answer to our questions,
> > yet I have the impression that there will be a time gap between the GA
> > releases of vthreads and SVs. Hence I would like to know what is the best
> > angle to address this problem using the tooling that will be provided by
> > JEP 425.
>
> Unless something bad happens, we intend Scoped Values to be an incubator
> in the next JDK release.
>
> --
> Andrew Haley  (he/him)
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> https://keybase.io/andrewhaley
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
>