Rust translation has an incorrect reference solution. For example, if r = 6 and c = 11 then the correct expected value rounded down is -3. But Rust expects -2.

Also, Sample Tests do not compile.

Lua translation!

Both n and k can start at 0 instead of 1.

python new test frameworks

Random tests coverage is pretty bad in all languages presumably... Solutions that check on count of sub-words appearing in either word type can pass the tests after few attempts.

Tests should be restructured to generate all combinations of below evenly and shuffle them accordingly.

• NOUN + NOUN
• NOUN + ADJECTIVE
• ADJECTIVE + NOUN
• ADJECTIVE + ADJECTIVE
• Combination of one or more NOUN and one or more ADJECTIVE, resulting in at least 3 types of words (2X NOUN + 1X ADJECTIVE / 1X NOUN + 2X ADJECTIVE etc...)
• NOUN
• ADJECTIVE
• Random words that is not in both lists

The input arrays are unreasonably huge in JavaScript, and for some reason they are also logged on failure. If you somehow make a mistake in your code, debugging it with such monstrosity is impossible.

Edit: turns out the input arrays are hige in all languages, but JS is the only one which additionally dumps the inputs. The latter can be left as is, but the former should definitely be changed.

The kata would benefit from 2-3 examples in the description. Currently, it's really hard to understand the task.

Description image is broken.

Why Test.assert_equals(solve([[1]]), 1)?

I can select {{1}, {}}, right?

Issue because of not conforming to the description of selecting 1* rectangles.

This beta attempt has been published for some hours now, and because multiple concerns have been immediately raised with no response at all, I have to wonder... dear author, where are you? Do you care about this? Did you just drop your 'kata' off at the daycare center to go play tennis? Please unpublish this and read some available documentation on the kata creation process.

Sample Tests are broken.

File "main.py", line 4
    
                                                                          ^
SyntaxError: unexpected EOF while parsing

Author's (would-be reference) solution is invalid.

No random tests.

Maybe what is inside reversed(q) should be given as function argument? Now it's too similar to other reverse list katas.

Note that converting it to decimal and then to octal isn't practical due to some very large test cases.

This is false. At least in Python because integers have arbitrary precision.