Skip to content

api: Size Sets and Maps correctly in handling of Metadata values to be exchanged during a call #12229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2025

Conversation

kilink
Copy link
Contributor

@kilink kilink commented Jul 17, 2025

Fix instances where HashSet / HashMap were initialized with initial capacity of the number of keys to be inserted, which would always lead to a rehash / resize operation.

Fix instances where HashSet / HashMap were initialized with initial capacity of the number
of keys to be inserted, which would always lead to a rehash / resize operation.
Copy link

linux-foundation-easycla bot commented Jul 17, 2025

CLA Signed


The committers listed above are authorized under a signed CLA.

@ejona86 ejona86 added the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Jul 17, 2025
@ejona86 ejona86 requested a review from AgraVator July 17, 2025 21:34
@grpc-kokoro grpc-kokoro removed the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Jul 17, 2025
@kannanjgithub kannanjgithub changed the title Size Sets and Maps correctly in Metadata api: Size Sets and Maps correctly in handling of Metadata values to be exchanged during a call Jul 22, 2025
@kannanjgithub kannanjgithub merged commit 8021727 into grpc:master Jul 22, 2025
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants