Add a note about spread operator limitations

[lpinca]

This improves the existing note about the spread operator specifying that it only works with array literals and function calls on Node 5.x.

Closes #653.

[MylesBorins]

Should the language be explicit about node 6.x having greater support for the spear operator?

[MylesBorins]

Actually... in thinking about it more the only way this change makes sense will be if we update the information regarding the spread operator at the end of the month when we bump to 6, as 5 will no longer be receiving support

[lpinca]

Yeah, was thinking the same. I mean we can update it when node 6 will be released with something like:
"spread operator works on array literals, function calls and destructuring".

[lpinca]

Or just wait for node 6 and use a sentence similar to the above one directly.

[MylesBorins]

You could send this PR directly to 5.x and send the other to master.

[lpinca]

Whoever reads site contents, reads master afaik.

[MylesBorins]

the generated docs for v5 will be made from that branch's doc folder though

[lpinca]

@thealphanerd Are you suggesting to move this pr to node repo? Otherwise I don't get it.

[MylesBorins]

@lpinca OH darn... this is what I get for responding via email when I am not fully awake yet.

I thought this was against the node repo. Sorry for the confusion

[lpinca]

No problem :)

[lpinca]

I've updated the pr, but it's probably better to close it.
The issue it tries to solve (#653) is probably invalid because the author used the spread operator on a non-iterable object tried to use object spread.
I don't see a real value in adding this note. This info should be (and actually is) in the operator documentation, not here.

[fhemberger]

Ok, closing this now. Feel free to reopen this PR if required.