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

benchmark: refactor to eliminate redeclared vars #5468

Closed
wants to merge 1 commit into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Feb 28, 2016

In order to comply with linting rules used in the rest of the code base,
eliminate redeclared variables. A conservative approach is used so as to
avoid unintentional performance issues (for example, as might be seen in
some situations when using let instead of var).

In order to comply with linting rules used in the rest of the code base,
eliminate redeclared variables. A conservative approach is used so as to
avoid unintentional performance issues (for example, as might be seen in
some situations when using `let` instead of `var`).
@Trott Trott added benchmark Issues and PRs related to the benchmark subsystem. lts-watch-v4.x labels Feb 28, 2016
@Trott
Copy link
Member Author

Trott commented Feb 29, 2016

/cc @nodejs/benchmarking @mscdex

@mscdex
Copy link
Contributor

mscdex commented Feb 29, 2016

LGTM

Trott added a commit to Trott/io.js that referenced this pull request Mar 1, 2016
In order to comply with linting rules used in the rest of the code base,
eliminate redeclared variables. A conservative approach is used so as to
avoid unintentional performance issues (for example, as might be seen in
some situations when using `let` instead of `var`).

PR-URL: nodejs#5468
Reviewed-By: Brian White <mscdex@mscdex.net>
@Trott
Copy link
Member Author

Trott commented Mar 1, 2016

Landed in 76e4a74

@Trott Trott closed this Mar 1, 2016
Fishrock123 pushed a commit that referenced this pull request Mar 2, 2016
In order to comply with linting rules used in the rest of the code base,
eliminate redeclared variables. A conservative approach is used so as to
avoid unintentional performance issues (for example, as might be seen in
some situations when using `let` instead of `var`).

PR-URL: #5468
Reviewed-By: Brian White <mscdex@mscdex.net>
@MylesBorins
Copy link
Contributor

@Trott to be grouped in with other benchmarking backports

@Trott
Copy link
Member Author

Trott commented Mar 17, 2016

@thealphanerd If you're OK doing them one at a time, this one maps to #5771

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Issues and PRs related to the benchmark subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants