-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[gmock] Rename struct Result to avoid shadowing #4221
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing just the case won't help much. We can think of some better name.
@ankit-gautam23 I agree, so maybe let's change that struct name to something to one of this: NonMoveableType, NonMoveableStruct, NonMoveableData, NonMoveableTestData or just NonMoveable. Or perhaps you have diffrent proposition? |
@TurboGawron Its truly okay. I will update this and raise the PR. Will add you as a reviewer. Thanks |
struct Result { | ||
explicit Result(int x_in) : x(x_in) {} | ||
Result(Result&&) = delete; | ||
struct result { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we name it NonMoveableStruct
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok
7638dba
to
d40fcb4
Compare
Struct Result shadows global definition of class Result in gmock-spec-builders_test.cc inside ExpectCallTest.NonMoveableType test