added more details to the description and bumped up the kyu

updated

it's just for convenience

I think probably I'll just make the random tests fail-fast so that only one big error is displayed instead of 100. I'll also make the early random tests smaller so that you don't have to parse through a 20-variable example to figure out what went wrong

I would have given this 5.5 kyu and just rounded down to 6, rationale being that it's 6 kyu implementation difficulty and 5 kyu domain knowledge

maybe limit and suppress shouldn't be tested for negative values, or at least the fact that the input can be negative should be documented in the description. it's really not related to the task at hand at all and it's perfectly reasonable for implementors to assume that the input should be nonnegative as a precondition.

(marked as a spoiler because apparently the fact that limit and suppress can take negative counts is considered a spoiler :I)

my solution keeps timing out on the real tests, and i'm not really sure where the bottleneck is in my code. help?

(also, a bunch of existing solutions just got trashed by the null yields test... rip)

thanks, i've added your new tests. i've also added a note to the description warning that yielded values may be null

this kata isn't really meant to test for multiple threads of execution, but i suspect using static variables to store generator-specific data will likely fail in cases with multiple generators anyways

a good implementation probably should allow for unrelated generators to run in parallel threads, but this kata doesn't require or test for that

figuring out how to do that is part of the challenge of this kata.

no. you can assume that any calls to a generator object will be sequential

weird

you should not use imports, since they take semicolons