taming resource scopes

Chris Vest mr.chrisvest at gmail.com
Sat May 29 14:35:28 UTC 2021

It's not clear to me why the Handle acquire/release API is inferior to this
new proposal, or why it can't solve the use cases discussed.
Looks fine, otherwise.


On Fri, 28 May 2021 at 18:34, Maurizio Cimadamore <
maurizio.cimadamore at oracle.com> wrote:

> Hi,
> we've been looking beyond 17 at things we can do to improve support for
> resource scopes, especially in the context of native calls. I tried to
> capture the various things we explored in the writeup below:
> https://inside.java/2021/05/28/taming-resource-scopes/
> I think overall the takeaway points are pretty good:
> * we can simplify the acquire/release scope mechanism with a better,
> higher-level API
> * we can enhance safety when calling native functions using _any kind_
> of resource scopes (with relatively little overhead)
> * we can make it easier to tailor the safety characteristics of CLinker
> to suit application needs
> Cheers
> Maurizio

More information about the panama-dev mailing list