Deprecate all java.util.concurrent.*FieldUpdater
David M. Lloyd
david.lloyd at redhat.com
Wed Oct 5 14:45:59 UTC 2016
I'm sure I recall an email from the past few months which proposed that
*FieldUpdater are still going to be recommended in many cases over
VarHandle because the latter is probably too low-level for casual uses.
It was (IIRC) an argument in favor of more advanced fence methods or
something like that.
Am I imagining it?
On 10/04/2016 04:19 PM, Martin Buchholz wrote:
> VarHandle is a reasonable replacement for FieldUpdaters, but it's not yet
> complete (where is accumulateAndGet?), and when do you deprecate something
> when the replacement won't be ubiquitous for 10 years?
> On Tue, Oct 4, 2016 at 1:32 PM, Remi Forax <forax at univ-mlv.fr> wrote:
>> Given that Java 9 introduces a faster way to emit things like
>> compareAndSet by using the VarHandke API and that AtomiReference (and
>> likes) are now rewritten to use VarHandles directly,
>> i think it's time to deprecate all *FieldUpdater with something saying
>> that they have been superseded by the VarHandle API.
>> substitute dr deprecator
More information about the core-libs-dev