[concurrency-interest] Deprecate all java.util.concurrent.*FieldUpdater
vladimir.x.ivanov at oracle.com
Wed Oct 5 16:55:00 UTC 2016
>> My interpretation of Martin's comment is that using deprecation for
>> things that aren't actually broken just means that people will live
>> with lots of deprecation warnings in their code for years to
>> come. This could be a perfect case for introducing a weaker
>> alternative to deprecation, saying "here's something better that you
>> should really be using for new code" -- e.g. ArrayList vs. Vector. I
>> remember the Guava team talking about that a lot. Don't know if they
>> ever implemented it.
> OK. But we really do need a way to do that.
Doesn't enhanced deprecation  in 9 cover that?
More information about the core-libs-dev