Add null checks to methods of Block.Builder and Body.Builder.

[mabbay]

Add null checks to methods of Block.Builder and Body.Builder. The null checks take precedence over finished building checks.

---

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

Progress

• Change must not contain extraneous whitespace

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/babylon.git pull/1104/head:pull/1104
$ git checkout pull/1104

Update a local copy of the PR:
$ git checkout pull/1104
$ git pull https://git.openjdk.org/babylon.git pull/1104/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1104

View PR using the GUI difftool:
$ git pr show -t 1104

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/babylon/pull/1104.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back mabbay! A progress list of the required criteria for merging this PR into code-reflection will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@mabbay This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

Add null checks to methods of Block.Builder and Body.Builder.

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 15 new commits pushed to the code-reflection branch:

• 522ed32: 8388391: BytecodeGenerator fails to generate bytecode for models containing AssertOp
• 1bc3213: [hat] PROFILE_CUDA_KERNEL option merged with PROFILE
• 98a6bbe: [hat] Add warning to remove the I/O annotations for non annotated kernel annotated methods
• ... and 12 more: https://git.openjdk.org/babylon/compare/de54b5465092142cdb2858d692be9d470477aef4...code-reflection

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the code-reflection branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 01: Full - Incremental (7a32550e)
• 00: Full (116f67ea)

[mabbay]

I found a similar case in method public CodeBuilder jdk.internal.classfile.impl.BufferedCodeBuilder#with(CodeElement element), there the order of the checks is status first then null.