Haskell fork

The random input generation has been limited to printable ASCII characters to avoid confusion (this is a white kata, after all!), addressing these issues.

Lua translation!

Lua translation!

Having two diffrent return types isn't good practice. Returning None is fine.

More test cases should be added. Only three of the fixed test cases need you to return False, and the random ones usually never do.

Description should not specify sorting to determine the minimum. Don't encourage bad coding.

Specifying the transformation on the first value before telling solvers to return said first value is better description authoring.

Hey PG1, please rephrase the description and parameters. GJ.

Why are half the exercise's instructions in the comments of the editor? Seems more ideal for this information to be in the instructions section

No fixed tests in Swift, also random tests should be increased and follow DRY principle

Groovy: random tests seem to generate a bunch of '/' for s and same amount of spaces for x (no other characters), and the expected result for all of them is false. This seems incorrect according to description, as every hole is matched with a tile (although I'm not 100% what was intended, it was different in JS version at least).

Groovy, possibly others: description states that "Words in your solution should be left-aligned". It's not obvious whether this means initial text or mirrored text (I'm assuming the latter), but random tests expect them to be right-aligned (compared to JS expecting left-aligned result). Please clarify what is meant by that sentence, or fix the reference solution.

js/didn't check others:

missing fixed test where a subarray has a matching character multiple times such as
[['OOO', 79], 3] with the duplicates required to reach the target - instructions state that a sub array may only be counted once. random tests are not sufficiently well crafted to consistently fail such solutions

additionally, the test output should quote strings in the "testing for ..." it name, that's really annoying when looking to call it myself

preloaded section emits warnings:

/workspace/spec/support/preloaded.rb:11:
Passing `mean` with the 1st argument of `normal` is deprecated.
Use keyword argument like `normal(mean: ...)` instead.

preloaded section emits warnings:

/workspace/spec/support/preloaded.rb:11:
Passing `digits` with the 1st argument of `number` is deprecated.
Use keyword argument like `number(digits: ...)` instead.

the preloaded section emits warnings:

/workspace/spec/support/preloaded.rb:17:
Passing `from` with the 1st argument of `between` is deprecated.
Use keyword argument like `between(from: ...)` instead.