Skip to content
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

container: fix introduction for node_hash_set.h #861

Closed
wants to merge 1 commit into from
Closed

container: fix introduction for node_hash_set.h #861

wants to merge 1 commit into from

Conversation

daohu527
Copy link

@daohu527 daohu527 commented Dec 12, 2020

container: fix introduction for node_hash_set.h

Fixed the wrong comment description "node_hash_map" to "node_hash_set"

@google-cla
Copy link

google-cla bot commented Dec 12, 2020

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Dec 12, 2020
@google-cla google-cla bot added cla: yes and removed cla: no labels Dec 12, 2020
@mbxx
Copy link
Member

mbxx commented Dec 14, 2020

Thank you! Looks good to me, merging.

absl-federation-github pushed a commit that referenced this pull request Dec 15, 2020
--
f0456157cdc6cef6dbb5d2f99f9dc3ca0e213fab by Abseil Team <absl-team@google.com>:

Improve flag_benchmark reproducibility, test multiple threads

This adds multiple threads to the flags benchmark, and also uses some
linker magic to ensure that the defined flags are mapped to a consistent
alignment regardless of other code changes in the benchmark binary.

The benchmark performance in multiple threads is somewhat sensitive to
the alignment of the FlagImpl class, depending on whether the flag value
and the absl::Mutex are on the same cacheline or different ones. Making
all flags be cacheline-aligned would probably waste too much memory,
so this CL instead just makes the memory alignment consistent within the
tests.

PiperOrigin-RevId: 347536882

--
a019646d306b9497a1eba7efa5e2c4c651d9979d by Derek Mauro <dmauro@google.com>:

Fix other comments in node_hash_set.h

PiperOrigin-RevId: 347462975

--
66a4b39fe84a3e81935ad08ee76291df13d1d5e6 by Abseil Team <absl-team@google.com>:

Internal change

PiperOrigin-RevId: 347436244

--
52f4d18c2c4439d26428f64ac4de41e6183919ee by Mark Barolak <mbar@google.com>:

container: fix introduction for node_hash_set.h

Import of #861

PiperOrigin-RevId: 347432772
GitOrigin-RevId: f0456157cdc6cef6dbb5d2f99f9dc3ca0e213fab
Change-Id: I629f27e5b9584d92b0a42284c1acf708779bad3f
@mbxx
Copy link
Member

mbxx commented Dec 15, 2020

It turns out there were a number of other copy-and-paste mistakes in the file; we've gone ahead and fixed those, too. Thank you so much for catching this!

@mbxx mbxx closed this Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants