JMC-7154: [JFR Writer] Improve lazy evaluation of the type defining block

[jbachorik]

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7154: [JFR Writer] Improve lazy evaluation of the type defining block

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jmc pull/221/head:pull/221
$ git checkout pull/221

[bridgekeeper]

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

[openjdk]

@jbachorik this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout jb/lazy_type_registration
git fetch https://git.openjdk.java.net/jmc master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

[mlbridge]

Webrevs

• 02: Full - Incremental (eaef3b0)
• 01: Full - Incremental (946214f)
• 00: Full (ce67a64)

[openjdk]

@jbachorik 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:

7154: [JFR Writer] Improve lazy evaluation of the type defining block

Reviewed-by: hirt

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 2 new commits pushed to the master branch:

• c1937f1: 7139: Prepare new and noteworthy for JMC 8.0.0
• 0c7ae2a: 6936: Parser should track statistics during parsing

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@thegreystone) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[jbachorik]

/integrate

[openjdk]

@jbachorik
Your change (at version eaef3b0) is now ready to be sponsored by a Committer.

[thegreystone]

/sponsor

[openjdk]

@thegreystone @jbachorik Since your change was applied there have been 2 commits pushed to the master branch:

• c1937f1: 7139: Prepare new and noteworthy for JMC 8.0.0
• 0c7ae2a: 6936: Parser should track statistics during parsing

Your commit was automatically rebased without conflicts.

Pushed as commit e97d985.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.