New: space-after-function-name (fixes #1340)

Adds a new rule, `space-after-function-name`, that enforces
consistent spacing between a function name and its parameters.
Fix: detect for...in in no-loop-func (fixes #1573)
Merge pull request #1574 from gcochard/fix-1573

Fix: detect for...in in no-loop-func (fixes #1573)
0.10.2
Merge pull request #1554 from jrvidal/master

Rule: space-after-function-name (fixes #1340)
Update: add yoda exception for range tests (fixes #1561)
Merge pull request #1570 from btmills/issue1561

Update: add yoda exception for range tests (fixes #1561)
Fix: check if next statement is on newline when warning against extra semicolons. (fixes #1580)
Merge pull request #1581 from yyx990803/fix-extra-semicolon

Fix: check if next statement is on newline when warning against extra semicolons. (fixes #1580)
Fix: function arguments now count towards no-shadow check (fixes #1584)
Fix: yoda treats negative numbers as literals (fixes #1571)

Negative numbers like `-1` are represented in the AST as a
numeric `Literal` node with positive one as the value, wrapped in
a `UnaryExpression` node with `-` as the prefix operator to negate
the literal. This PR treats both positive and negative numbers as
normal literals.

Because the range test exception validates ranges to ensure that
the left end of the range <= the right end of the range, it was
necessary to combine the negating wrapper and literal into a
single negative literal node rather than simply checking for the
presence of the negating wrapper so that the actual negative value
is available.

This brings test coverage of `lib/rules/yoda.js` back up to 100%.

It also fixes a spelling error in the docs pointed out by @ljharb.
Merge pull request #1588 from glenjamin/shadow-func-args

Function arguments now count towards no-shadow check (fixes #1584)
Merge pull request #1579 from eslint/issue1571

Fix: yoda treats negative numbers as literals (fixes #1571)