Hi Remi,
Thanks, that was what I assumed as well. It was only because
Lookup.unreflectVarHandle() was very particular about every possible
modifier type. That I had a second of doubt.
Best,
Kasper
On Sun, 16 Jun 2019 at 12:03, Remi Forax wrote:
>
> Hi Kasper,
> as usual, a getter on a volatil
Hi Kasper,
as usual, a getter on a volatile field will return a method handle that does a
volatile read.
The idea of the basic methodhandles, the one for field access, method calls,
etc is to have exactly the same semantics as the bytecode equivalent, so
unreflectGetter works like getfield and u
