Yeah, I found out we needed to provide more arguments to the functions. I thought this would be an exact copy of the first kata, that also got retired.

you did get that while having a mistake in your code, right?
'Cause, well... your code will interact with/affect the code running the tests, in this kata

What on earth does this mean? TypeError: suite.total is not a function

Hi,

Duplicate, as pointed below. @evanrh: do not close the issue, it's aslo a general flag and has meaning outside of the scope of your kata itself.

also, for further use (on different kind of tasks ;) ):

• try to not test some requirements only in the full test suite. Here: no example test with the index
• if you try to mimic the original, why no tests on the array parameter?
• note that mimicking builtins generally results in kata of very low interest.
• the random tests are rather bad, for several reasons:
  • reduce is not tested
  • the callbacks are fixed
  • only 1 single random test
  • the size of the input arrays is fixed
• the mutation tests:
  • they are in the random test section => have nothing to do here
  • they are not testing that the input has not been mutated, but that the output is different from the input

Cheers

Thanks for the feedback!
I didn't find this series when I was researching the topic initially.

I'll put my effort towards those problems instead.

Added a check in the preloaded code to disable requiring of the vm module

Sure!
I'll start with the map and filter functions.

Both map and filter's callback functions can take up to three parameters in the following order:

1. The current element
2. The current element's index
3. The array being iterated over

This means you can pass a callback that looks like this:

const arr = ["a", "b", "c"];
const res = arr.map((elem, index) => index);
console.log(res) // [0, 1, 2]

Reduce's callback follows a similar pattern:

1. An accumulator
2. The current element
3. The current element's index
4. The array being iterated over

Here's links to docs in MDN that explain it in further detail

1. map parameters
2. filter parameters
3. reduce parameters

https://www.codewars.com/kata/reviews/64d545985fd4000001e8b990/groups/64d57c875fd4000001e8c15e

should provide the index to the callback function

Could you elaborate further on this point? I don't understand what the kata is asking me to do (should I pass the index to the function as a parameter or...?)

Python fork with random tests and standard failure messages: https://www.codewars.com/kumite/64b321a2206744001d337b9e?sel=64b321a2206744001d337b9e

Submitted a Javascript translation for this kata.

I have never seen someone write a for loop that way. That is an interesting way to do so.

This code makes me happy.