On Wed, Oct 6, 2021 at 2:08 PM Brian Goetz <brian.go...@oracle.com> wrote:
> One more thing we could do is reach out to the most popular libraries that > do this and give them a heads up that they need to tolerate the field not > being there. > Good idea, I filed bugs against several libraries that are reflecting on fields named this$. I skipped examples that contain textual occurrences of this$ that were clearly safe, e.g. because they were filtering fields with that name out of the results of getDeclaredFields(). https://github.com/classgraph/classgraph/issues/570 https://github.com/robolectric/robolectric/issues/6757 https://github.com/micrometer-metrics/micrometer/issues/2806 https://github.com/awaitility/awaitility/issues/223 https://issues.apache.org/jira/browse/MAPREDUCE-7364 https://issues.apache.org/jira/browse/BEAM-13020 https://issues.apache.org/jira/browse/AVRO-3228
