This kata is a subject to deduplication process here: https://github.com/codewars/content-issues/issues/228.
Please join the discussion to help us identify duplicate kata and retire them.

Lua translation!

Either I'm seriously misunderstanding the kata, or there is something incredibly wrong with the random tests in Haskell.

Falsifiable (after 5 tests and 9 shrinks):
  0.0
  -2.0
  Positive {getPositive = 1.0}
Test Failed
expected: 1.0 within margin of 1.0e-6
 but got: 0.0

0 and -2 are at the same point on a circle with circumference 1, are they not?

the initial code in C should be a function definition, not a function declaration

Groovy translation

Potential duplicate of Regex for a decimal number divisible by 4

The kata there is a sentence:
"..It should find two different items in the array"

The point there is about finding different values in context of array (different indices of values, not values itself)

Description should be fixed to clarify it

JavaScript:

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

fork fixing all

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