tools: enable no-self-assign ESLint rule
authorRich Trott <rtrott@gmail.com>
Thu, 3 Mar 2016 21:45:08 +0000 (13:45 -0800)
committerMyles Borins <mborins@us.ibm.com>
Mon, 21 Mar 2016 20:07:01 +0000 (13:07 -0700)
commit64d5752711db79cee3744989af0a7e46d537ea5e
tree7b32f75b081b80595947d54a4ee648dad22fb57c
parent04d3f8a7416916fc0f56b68d6c9c4798bcb60fb7
tools: enable no-self-assign ESLint rule

Enabled no-self-assign rule in ESLint.

This required one change in a benchmark file. Changed a loop (that is
outside of the benchmark itself, so performance is not critical) from a
for loop that repeats a string to use String.prototype.repeat() instead.

While at it, took the opportunity to const-ify the benchmark file.

Also moved the "Strict" section in the .eslintrc to match where it is in
the ESLint documentation. Updated the link for Strict rules to point to
the ESLint website rather than the GitHub-hosted code.

PR-URL: https://github.com/nodejs/node/pull/5552
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
.eslintrc
benchmark/buffers/buffer-base64-decode.js