Lua translation!

C Translation (author inactive).

wow!! that's nice

Removed the performance requirements from PHP as the reference solution was not working anymore in current PHP versions without increasing available memory of the PHP process.

Ruby: Missing sample and random tests.

perfect

JavaScript fork (author inactive)

• enabling Node v18.0+
• using chai assertions
• better markdown in the description
• using modern JS features such as class and const, including in the initial code

Another great kata challenge! This is very helpful for learning about accessing subarray indexes. Thanks!

Lua translation!

In R the naive solution may timeout, depending on the random test rolled. And since mine failed on the first try, I introduced memoisation. Sumbitted, passed (not sure now if coz of luck or not) and found the naive solution to be the "best" one.
Meh. :(

If imported properly as you shown, no prob.
If imported with from solution import *, you can import other symbols: seems obvious but it is often done, even in production code.
Always better to avoid trivial names in test suite - that might collide with other imports/libraries.

I still would like to understand. only f and m are imported:

from solution import f, m

symbols used in f() and m() will still refer to their value in solution.py, not to the ones in test.py, even if those happen to have the same name, wont they ? what am i mising ?

Can still collide with user-defined functions though - as they are imported into test suites.
Nevertheless referee solutions have now a non-trivial suffix, so this issue is no longer relevant.