Consider a ClassValue for this, if there is not an obvious bit to be repurposed somewhere.

On 6/23/2020 12:30 PM, Chris Hegarty wrote:
I think it is worth considering caching the record-ness state of a j.l.Class, 
as I’m sure it will be widely used in third-party serialization libraries, as 
well as by Java Serialization.

Reply via email to