On Fri, 13 Jan 2023 16:20:41 GMT, Archie L. Cobbs <[email protected]> wrote:
>> I'm OK either way we can revisit this later either as part of this PR or in
>> a future one. I let it to your consideration
>
> Sounds good - thanks.
Ah. I just realized that we need to do it your way because of the following bug:
Suppose you have a constructor and a field with initializer that both leak, but
you have `@SuppressWarnings("this-escape")` on the constructor.
Then the leak for the field will never be reported because we never get to it.
I'll fix.
-------------
PR: https://git.openjdk.org/jdk/pull/11874
