Merged.

Implement testing that would force solutions to run in sub-linear time

no. As you pointed out, this is white. There shouldn't be performances requirements here. Rather:

• at worst, the info should get removed from the description
• at best, the kata should be retired because it's just a duplicate of many other kata.

edit: ok, I got a coffee in the belly, and now I see the previous line in your message... x) ->
I'd stick to point 2, though

.

Depends how high you put the bar. If you don't use more memory than necessary, I say you qualify. Nothing is keeping a normal iterator from keeping, possibly huge, state either.

Approved

approved

Hello RileyHunter
Hello again HerrWert...
I agree with you both! --> I've upvoted you both to show my support of your comments.

Approved

Approved in fork by dfhwze

Changes needed:

• Remove test for [] per Mauro's issue.
• Add proper assertion messages, current ones are useless.

Suggestions:

• Label your random test case generators with their intent.
• Remove refsol, you don't need it. Only the 4th generator doesn't have a guaranteed expected value, and that can be checked much faster than running an entire refsol due to how you set it up.
• Don't roll your own shuffle, you already imported random, there's a perfectly good shuffle in there.

Thanks, kata description updated.

An issue was logged about this by users Invariance & lukaswelinder .

I'm running into this same issue.