Scala translation

Since the answers can be very large, return only the last 8 digits of the answer in case it exceeds 8 digits. The answers to the test cases will all be shorter than 8 digits.

These two sentences are directly contradictory and one of them needs to be removed, as well as the tests being adjusted to match.

In general there's a lot of room to increase the size of the test inputs such that the modulus requirement is enforced, so I think we should do that.

Fixed

Possibilities to get happ using the first 6 letters:

1. [h]h[a]a[pp]...
2. [h]ha[a][pp]...
3. h[h][a]a[pp]...
4. h[h]a[a][pp]...

The amount of possibilities on the right side is 512.

So, total is 512 * 4 = 2048.

Javascript update fork

• Enabled Node v18
• Used chai for assertion
• Changed the random tests generator to use the same algorithm as the Python version

Auto-approved after elapsed grace-period.

Rust translation for your consideration

yeah, that was required at some point in the past, to get access to the edit panel of the kata (an issue had to be raised for more than 7 days). Nowadays, the fork thing allow to modify the kata "directly" (considering time)

Ok, sure. I just see power users raise framework updates as an issue all the time, thought it was appropriate.

(note for further use: if it's only about the framework update, you a suggestion is enough)

.

Random tests in Javascript have the same issues as random tests in Python, and are A LOT less intensive.

.

In Python, the initial solution should have more descriptive parameter names: a and b are completely useless. Without looking at the tests and doing some "common sense" analysis, I have no way of knowing which is which.
The parameters should be called needle and haystack, just like the description uses.