RFR: 8194743: Compiler implementation for Statements before super() [v14]

[Chen Liang]

On Fri, 22 Sep 2023 22:02:04 GMT, Archie Cobbs <acobbs at openjdk.org> wrote:

>> This is a first draft of a patch for JEP 447.
>> 
>> Summary of changes:
>> 
>> 1. Track when we're within a constructor "prologue" via new flag `AttrContext.ctorPrologue`
>> 1. Add checks for illegal early access to `this` in constructor prologues, and update existing checks to distinguish between static context vs. constructor prologue context
>> 1. Verify allowed placement of `super()`/`this()` calls via new method `Check.checkSuperInitCalls()`
>> 1. Remove/refactor assumptions in several places that `super()`/`this()` was always the first statement
>> 
>> The changes in `Flow.java` are an example of <span>#</span>4. `Flow.FlowAnalyzer` checks for uncaught checked exceptions. For initializer blocks, this was previously done by requiring that any checked exceptions thrown be declared as thrown by all constructors containing `super()`. This list of checked exceptions was being pre-calculated before recursing into the initial constructors. This worked because initializer blocks were executed at the beginning of each initial constructor right after `super()` is called.
>> 
>> Now initializer blocks are traversed as each `super()` invocation is encountered, reflecting what actually happens at runtime. Similarly, final fields are marked as DA after encountering `this()`, not automatically at the beginning of those  constructors. These changes produce equivalent checks, but are compatible with the new flexibility of placement of `super()`/`this()` as well as possible future changes that could occur along these same lines.
>
> Archie Cobbs has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Remove obsolete flag "constructorArgs".

In the latest update to [JEP 401](https://openjdk.org/jeps/401) [Value Objects](https://bugs.openjdk.org/browse/JDK-8251554), it proposes to reuse the pre-initialization context from here for its "regulated Constructors". However, the regulated context anticipates local classes to be static while our pre-initialization context currently declares local classes non-static (except interfaces, records, and enums, which are implicitly static) and thus cannot be used before super call. Should we make pre-initialization local classes static to ease the compiler implementation for "regulated Constructors" in the future?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/13656#issuecomment-1732179148