After some more analysis, we have decided to drop the initialization warning from the initial JEP 401 integration.
First, the definition of initialization warnings is a little ambiguous, as it can mean one of two things: * pretend super() was at the bottom of a constructor, and see what happens * pretend all fields were strict, and see what happens These two things are not identical, and lead to a different sets of warnings being generated. Secondly, there's a lot of noise with these warnings: * JDK code contains ~67 suppressions * if we tweak the code to also report the warning when `--enable-preview` is disabled, an additional 80+ warnings show up during an early phase of the build (but there's possibly many many more) For the time being, we'll revert the code that issues the new warnings, related tests and suppressions. --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - Address review comments - Drop support for initialization warnings Changes: https://git.openjdk.org/valhalla/pull/2512/files Webrev: https://webrevs.openjdk.org/?repo=valhalla&pr=2512&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8385955 Stats: 432 lines in 81 files changed: 2 ins; 339 del; 91 mod Patch: https://git.openjdk.org/valhalla/pull/2512.diff Fetch: git fetch https://git.openjdk.org/valhalla.git pull/2512/head:pull/2512 PR: https://git.openjdk.org/valhalla/pull/2512
