On Fri, 13 Jan 2023 21:33:02 GMT, Archie L. Cobbs <[email protected]> wrote:
>> 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.
yep, right in that case that leak wouldn't be reported
-------------
PR: https://git.openjdk.org/jdk/pull/11874