I wonder if we could use the lambda operator in the solution to convvey the "arrow"-ness? .filter(x -> x % 2 == 0)

Why did you need the parseFloat there?

The scope of those variables is inside the function, so the way you manipulate them has no effect on the variables outside this function. A simple example to better understand this:

function incrementX(x){
  x++;
  console.log(x); 
}
var x = 1;
console.log(x); // logs 1
incrementX(x); // logs 2
console.log(x); // logs 1

Can you provide more info on the issue you are having?

Thank you!
Translation has been added.

The sorting was a left over of the initial thought.

A damaged arrow is no longer good, no.

Here's a link:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const

Hope you mean guys :)

Marking issue as fixed.

Note taken. Will update description.

LE: description has been updated. Please let me know if this makes it clearer now.

Don't know... maybe the request changed and it was supposed to leave the input array unaltered... doesn't make much sense now :)

They are called arrow functions: https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Functions/Arrow_functions