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.
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.
.
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:
[]
per Mauro's issue.Suggestions:
Thanks, kata description updated.
An issue was logged about this by users Invariance & lukaswelinder .
I'm running into this same issue.
I love card katas, and all the changes look extremely good and reasonable to me
This nuance is especially something this kata description had to have
Approved
fixed
Loading more items...