Skip to content

Conversation

@cjihrig
Copy link
Contributor

This fixes the following warning (and subsequent warnings that occurred from fixing the original warning):

../src/inspector/runtime_agent.h:26:16: warning: private field 'env_' is not used [-Wunused-private-field] Environment* env_; ^ 1 warning generated. 
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot
Copy link
Collaborator

@ZYSzysZYSzys added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. c++ Issues and PRs that require attention from people who are familiar with C++. inspector Issues and PRs related to the V8 inspector protocol labels Jun 3, 2019
@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Jun 3, 2019

CI: https://ci.nodejs.org/job/node-test-pull-request/23589/

EDIT(cjihrig): CI was yellow.

@cjihrigcjihrig changed the title src: fix unused private field errorsrc: fix unused private field warningJun 3, 2019
Copy link
Contributor

@sam-githubsam-github left a comment

Choose a reason for hiding this comment

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

LGTM. Is the explicit related to the _env fix?

@cjihrig
Copy link
ContributorAuthor

Is the explicit related to the _env fix?

Yes. After removing the unused constructor argument, you get the following warning: Zero-parameter constructors should not be marked explicit.

@danbev
Copy link
Contributor

Could we fast track this?

If you agree please give a 👍 and if you disagree please remove the fast-track label.

@danbevdanbev added the fast-track PRs that do not need to wait for 48 hours to land. label Jun 4, 2019
@danbev
Copy link
Contributor

Landed in 2c76874.

@danbevdanbev closed this Jun 5, 2019
danbev pushed a commit that referenced this pull request Jun 5, 2019
PR-URL: #28036 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@cjihrigcjihrig deleted the unused branch June 5, 2019 21:01
BridgeAR pushed a commit that referenced this pull request Jun 17, 2019
PR-URL: #28036 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@BridgeARBridgeAR mentioned this pull request Jun 17, 2019
codebytere added a commit to electron/node that referenced this pull request Jul 3, 2019
Removed in nodejs/node#28036; this patch can be removed when we update to v12.5.0
codebytere added a commit to electron/node that referenced this pull request Jul 3, 2019
Removed in nodejs/node#28036; this patch can be removed when we update to v12.5.0
MarshallOfSound pushed a commit to electron/node that referenced this pull request Jul 4, 2019
Removed in nodejs/node#28036; this patch can be removed when we update to v12.5.0
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.c++Issues and PRs that require attention from people who are familiar with C++.fast-trackPRs that do not need to wait for 48 hours to land.inspectorIssues and PRs related to the V8 inspector protocol

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@cjihrig@nodejs-github-bot@danbev@sam-github@targos@BridgeAR@ZYSzys