Loosening requirements for super() invocation

[Archie Cobbs]

On Tue, Nov 1, 2022 at 5:58 PM Brian Goetz <brian.goetz at oracle.com> wrote:

> Right, more of the same trick.  The key is not crossing source files,
> since that is over the analysis horizon.
>

OK so let's assume we can come up with a reasonable definition for "this
escape" that is rich enough to be practically useful but not too complex to
calculate in the compiler.

What next?

This new "this escape" warning would really just be a new compiler feature
rather than a language change, right? It's not changing the language, it's
just expanding the set of possible warnings that can be generated.
Obviously it would be very helpful in getting people to think more about
"constructor hygiene".

So then would its inclusion in a JEP be more about precisely defining the
concept and describing the goodness that comes from it?

Thanks,
-Archie

-- 
Archie L. Cobbs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/amber-dev/attachments/20221102/37d4d76b/attachment.htm>