Well, we could just back out of it and stick with only setAccessible(). IIRC this Unsafe trick was only meant as a bypass for those warnings anyway (and it didn't really work in JDK 12+).