Redefining existing prototype methods is a very, very dangerous game. It's hard to do correctly, and in this case, it can't be done correctly because you are changing functionality.
Why not just ask for a function bind(fn,context,...args) {}?
There is absolutely no reason for it to be a prototype method anyway, and it's much safer for existing programs that depend on existing functionality.
C translation (author gone)
JVM translations:
Java
Kotlin
Clojure
Scala
Groovy
Failed tests logs should also give
n, and not just the aray, otherwise they are useless.Needs random tests.
Redefining existing prototype methods is a very, very dangerous game. It's hard to do correctly, and in this case, it can't be done correctly because you are changing functionality.
Why not just ask for a
function bind(fn,context,...args) {}?There is absolutely no reason for it to be a prototype method anyway, and it's much safer for existing programs that depend on existing functionality.
Please write your kata in English.
Could do with a test with a line starting with 7 (or more)
#s, which would have to be left alone.