7903321: Use a set instead of a map to record methods in class 'MethodGroup'

[lgxbslgx]

Hi all,

This patch changes the type of the field MethodGroup#methods from a map to a set so that it is more suitable for its meaning.

Thanks for the taking the time to review.

Best Regards,
-- Guoxiong

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• CODETOOLS-7903321: Use a set instead of a map to record methods in class 'MethodGroup'

Reviewers

• Aleksey Shipilev (@shipilev - Committer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 79

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmh/pull/79.diff

[bridgekeeper]

👋 Welcome back gli! 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.

[mlbridge]

Webrevs

• 02: Full - Incremental (52960cc8)
• 01: Full - Incremental (e585e859)
• 00: Full (8662ead8)

[shipilev]

This looks fine, but we can make it simpler. Let's see that all GHA tests are also green.

[shipilev]

All right then!

[openjdk]

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

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

7903321: Use a set instead of a map to record methods in class 'MethodGroup'

Reviewed-by: shade

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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 (@shipilev) 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).

[lgxbslgx]

@shipilev Thanks for the review.

/integrate

[openjdk]

@lgxbslgx
Your change (at version 52960cc) is now ready to be sponsored by a Committer.

[shipilev]

I'll sponsor after GHAs go green.

[shipilev]

/sponsor

[openjdk]

Going to push as commit 622ed6e.

[openjdk]

@shipilev @lgxbslgx Pushed as commit 622ed6e.

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