Kata

those rules are unambiguous, unlike your user name

It's literally my initials and last name, what does your user name stand for?

here's the ambiguity with your name

Great logic and attitude, keep that up! :)

Bye, take care

Hate speech or imagery: Any form of expression (e.g. speech, text, or images) that can increase the risk of violence against members of another group. This includes using coded language, hate symbols, the denial of historical events, support for hate groups and people promoting hateful activities, prejudice and conspiracy theories.

Your name contains a hate symbol "SS". I will report you.

Just to note, I accidentally left the It title for the random tests as empty_string rather than random_test_cases. I just used the editor to patch this up. Hope that's fine

Don't use the editor, use rather the fork button, if you see it (just on the left of the edit button). The edit panel has side effects on contributors, when it comes to progress elligibility (as in: losing it), if they want to complete the kata in multiple languages and/or translate it also with the idea of gaining the progress in that language.

Oh that's strange - noted. Sorry if this affected anyone I just assumed this was too minor of a change to warrant forking again

no, the only potentially affected person is you, that's all.

this has already been fixed

The fact that the example solution pukes on chunky strings of length 0 only strengthens me in this opinion.

I just noticed fixed tests only use, and random tests always generate, strings of exactly 1 chunk. The specs leave open the possibility of a string containing any number of chunks.

What is the intention here?

If a chunky string is supposed to be exactly one chunk, length 0 actually does not make sense. ( The specs should also just say so. ) If a chunky string can contain multiple chunks, there should of course be tests with that.

With make_chunk(depth), there is no real reason to specify an upper bound to the string length anymore.

The description now states that "A 'chunky string' is a string consisting of exactly one chunk.". So yes, the empty string case should be done away with; the only other alternative is to consider an empty string a valid chunk, which would lead to absurd conclusions

The intention was that a chunky string consists of exactly one chunk. I think I'll keep it like that for this kata.

I have kept an upper bound on the string length to limit the amount of output in case of an error

Empty string test case is now gone

No need for an upper bound if you set the recursive limit to 8 (in which case the maximum will be 255) or 7 (~115 or something iirc).

yes, it is possible for random tests to result in a recursion limit error if the recursion depth exceeds the default limit set by python

fixed by author