JavaScript:

• initial code should use a Class
• no random tests
• chai assertions should be used

fork fixing all

No random tests in Java.

Duplicate of at least 2 other kata's about ranges. And those kata's are published, without any issues, and with added performance constraints.

Random tests are floating point numbers, but description says all numbers are integers. Btw floating point numbers are a horrible idea. How will you assess ranges that "meet" with truncation and rounding errors in floating points?

Haskell tests appear to be broken. My solution failed on the randomized tests:
Falsifiable (after 7 tests and 4 shrinks):
"aa\71319a"
expected: "a2a"
but got: "aa\71319a"
Is \71319 supposed to be a character?

[At least python, maybe other languages]

• Random tests don't check that the function returns two DIFFERENT items.

[Python]

• Only one random test.
• Tests raise exceptions if indexes are out of range.
• The return type should be a tuple, the pythonic way to return a pair of values (and there are many valid solutions with tuples invalidated by the last fork)

(Working on python version.)

• Description should be langugae-agnostic

• Numbers might be passed in replacement of booleans, so false may be passed in as 0 and true may be passed in as 1. (This requirement should be removed since this is bad coding practices and not every language shares this property)

• Only 1 "random" test in JS is not acceptable prior to current standards

• Node 18. should be enabled

This kata is 8 years old and yet the first sample test for JavaScript returns the wrong solution. I finally ignored this, pressed submit, and passed. Author is inactive. Who will fix?

Ruby should be updated to 3.0

What is the expected order of instances in the pool? FIFO, LIFO, priority, or what?

CoffeeScript translation

Kata details states that "if you pass it a value, it will return true if a value is a valid primitive number or Number object, and false if not."

On the contrary, JavaScript tests assert that strings representing numbers, like "1" or "2", should return true. Strings are either number primitives or Number objects, so one or the other is wrong.