Skip to content
This repository was archived by the owner on Jun 30, 2025. It is now read-only.

Conversation

@sergiud
Copy link
Contributor

@sergiud sergiud commented Apr 8, 2021

This allows CHECK_NE(foo, nullptr) to compile and produces "nullptr" for the string representation of nullptr.

Finalizes #342

Closes #562 #341

@sergiud sergiud added this to the 0.5 milestone Apr 8, 2021
@google-cla
Copy link

google-cla bot commented Apr 8, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Apr 8, 2021
@sergiud sergiud linked an issue Apr 8, 2021 that may be closed by this pull request
@google-cla google-cla bot added cla: yes and removed cla: no labels Apr 8, 2021
@sergiud sergiud self-assigned this Apr 8, 2021
@sergiud sergiud force-pushed the nullptr branch 2 times, most recently from 9bce407 to 06e72c7 Compare April 8, 2021 22:04
@sergiud sergiud requested a review from drigz April 8, 2021 22:05
Copy link
Member

@drigz drigz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Could you also add -DHAVE_CXX11_NULLPTR_T to common_copts in bazel/glog.bzl?

@sergiud
Copy link
Contributor Author

sergiud commented Apr 9, 2021

@drigz In that case, ac_cv_cxx11_nullptr_t should also be set to 1 in common_config, correct?

@drigz
Copy link
Member

drigz commented Apr 9, 2021

@drigz In that case, ac_cv_cxx11_nullptr_t should also be set to 1 in common_config, correct?

Ah, I misread and thought that it was set to 1, sorry. Either approach is OK, in that case, but I have a slight preference for assuming a modern environment in the Bazel build: I think that people with weird environments use build systems with environment detection, and Bazel users are expecting the modern features.

This allows CHECK_NE(foo, nullptr) to compile and produces "nullptr" for the
string representation of nullptr.
Copy link
Member

@drigz drigz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

compile error: use of overloaded operator '<<' is ambiguous CHECK_XX variants do not compile if nullptr is an argument

2 participants