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

gcc warning in inspector protocol implementation #32357

Open
targos opened this issue Mar 19, 2020 · 8 comments
Open

gcc warning in inspector protocol implementation #32357

targos opened this issue Mar 19, 2020 · 8 comments
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. v8 engine Issues and PRs related to the V8 dependency.

Comments

@targos
Copy link
Member

targos commented Mar 19, 2020

[1934/2890] CXX obj/gen/src/node/inspector/protocol/libnode.Protocol.o
gen/src/node/inspector/protocol/Protocol.cpp: In member function ‘virtual std::unique_ptr<node::inspector::protocol::Value> node::inspector::protocol::DictionaryValue::clone() const’:
gen/src/node/inspector/protocol/Protocol.cpp:698:21: warning: redundant move in return statement [-Wredundant-move]
  698 |     return std::move(result);
      |            ~~~~~~~~~^~~~~~~~
gen/src/node/inspector/protocol/Protocol.cpp:698:21: note: remove ‘std::move’ call
gen/src/node/inspector/protocol/Protocol.cpp: In member function ‘virtual std::unique_ptr<node::inspector::protocol::Value> node::inspector::protocol::ListValue::clone() const’:
gen/src/node/inspector/protocol/Protocol.cpp:739:21: warning: redundant move in return statement [-Wredundant-move]
  739 |     return std::move(result);
      |            ~~~~~~~~~^~~~~~~~
gen/src/node/inspector/protocol/Protocol.cpp:739:21: note: remove ‘std::move’ call
@targos targos added the c++ Issues and PRs that require attention from people who are familiar with C++. label Mar 19, 2020
@himself65
Copy link
Member

@sam-github
Copy link
Contributor

https://chromium-review.googlesource.com/c/deps/inspector_protocol/+/2057545

@targos
Copy link
Member Author

targos commented Mar 19, 2020

@sam-github you should mark the patch as ready for review

@targos targos added the v8 engine Issues and PRs related to the V8 dependency. label Mar 19, 2020
@sam-github
Copy link
Contributor

OK, I figured out how to do that. Obviously if I want someone else to review something... I have to "start review". 🤕

@sam-github
Copy link
Contributor

@targos I'd have to find who in IBM has legal authority to sign a contributor agreement for me, but honestly, I'm not sure if its worth it. I might get to it next week, but maybe you want to PR the fix? I give the code to you if you want it.

@mmarchini
Copy link
Contributor

@sam-github since IBM already have folks contributing to V8, you probably already have a signed agreement. If that's the case, using your IBM email shot be enough.

@sam-github
Copy link
Contributor

sam-github commented Mar 20, 2020

I can't see any way to change the owner of a CL, and it looked like I needed a agreement that specifically mentioned me, and my company.EDIT: I abandoned the CL, its easier for the maintainers to just fix it than to go through the CL process with an external contributor. Sorry, @targos.

@mmarchini
Copy link
Contributor

They might not push the changes since you proposed it first to avoid any legal issues (I know, I know). Hopefully that's not the case.

I can't see any way to change the owner of a CL

Not possible AFAIK, you would need to resubmit it.

it looked like I needed a agreement that specifically mentioned me, and my company

Larger companies usually have a company-wide signed CLA with open source projects, and discourage (or disallow) individual signatures. Of course, maybe IBM handles this differently, but having a company-wide signature is also recommended by the "Legal Stuff" they referenced:

"All contributors must complete the contributor license agreement. For individual contributors, please complete the Individual Contributor License Agreement online. Corporate contributors must fill out the Corporate Contributor License Agreement and send it to us as described on that page."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

No branches or pull requests

4 participants