Move statements before super(..) in Java constructor #733

[rkampani]

What's changed?

• Relates to #5397
  Jep 513 calls for allowing statements before the call to super() in Java constructors, allowing for simple assignments and validations before doing expensive construction.

Java version >= 25
(Also double check Jep 513 lands in Java 25)

Before Applying Recipe

class A {
    public A(String bar) {
        super();
        if(bar.equals("test"))
            throw new RuntimeException();
    }
}

After Applying Recipe

class A {
    public A(String bar) {
        if(bar.equals("test"))
            throw new RuntimeException();
        super();
    }
}

What's your motivation?

Anything in particular you'd like reviewers to focus on?

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 997-1007
  • lines 1036-1042

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 997-1007
  • lines 1036-1042
  • lines 7108-7107

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 997-1007
  • lines 1036-1042
  • lines 7108-7107

[timtebeek]

We're seeing some unrelated test failures; no need for alarm or debugging; we'll try to get those sorted soon. :)

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 701-700
  • lines 997-1007
  • lines 1036-1042

[MBoegers]

ATM you move the super() call to the very end of a constructor call. If i recall correctly there are limitations regarding the reference to instance fields. Could you please revisit JEP 513s section about Early-construction-contexts and verify that we are producing JLS compliant code?

[MBoegers]

Thanks for your contribution, I love seeing new Language features been picked up :) I think 1 or 2 tests should be enough to make sure we are JLS compliant in the context of the Early construction contexts.