Nice and enjoyable kata, well done, congratulations.

It would be nice if the C translation would print the received array, even if the number of entries is not as expected, to help the user.

In ruby you just have to replace the solution in class to a function and replace the random test top level describe block to it block

I enabled node 12, not proficient in Ruby tho

added sample tests in Ruby

• Node 12 should be enabled (Refer this and this for more info)

• Ruby 3.0 should be enabled (Refer this & this for more detail)

Done, thanks.

[C] Sample test module generates a lot of compiler warnings, which clutter the output and interfer with spotting compiler errors. These should be cleaned up.

There is something what could be helpful then: kata-authoring-help gitter chat. You can go and talk there about your new idea, or even when you author new kata you can give us a link to it before publishing, while it's still in draft. Drafts are not publicly visible, but are still accessiblia with direct links. This way, you won't risk it will collect downvotes or be immediately retired, and it can be eventually easily deleted.

Ok, thanks for explaining that. It does make sense - though I would suggest a grace period (7 days?) before a kata is retired. As someone who doesn't visit CodeWars all that often, and just woke up one day with an idea for a kata in my head, the experience of submitting a kata so far hasn't made me want to come back or recommend CodeWars to others.

Also @anter69, please pardon my sarcasm. What I like about this kata is that it takes a problem that everyone is deeply familiar with but flips it in order to introduce a language-fundamentals concept (infinite sequences) that a lot of junior developers won't be familiar with. So the fact that FizzBuzz is a cliche is almost the point.

Anyway, I'll resubmit it with the suggested improvements when I have time! Thanks all.

sort of, yes. But there is a "problem" with the beta process: everything that is in beta is already part of the database and of cw itself.

Some time ago here is the kind of problem that led to: if the author didn't update his kata accordingly to what users were asking from him, not much could be done to prune the database from "low quality content". Hence, the "auto"-retirement process was introduced, so that low quality content could be retired without action of the author. But on the other hand, that transformed the beta process into some sort of hammer. The "philosphy" of it is now "retire everything that is too low quality as quick as possible, even if it might have potential, to have more chances we don't end up again with a new bad kata stuck in beta forever"...

So the quality at publication time is critical for a beta to survive, now. You should read those, so that you get a clearer idea about what's expected:

• https://github.com/codewars/codewars.com/wiki/Tutorial%3A-Create-Your-First-Kata
• https://github.com/codewars/codewars.com/wiki/Kata-Creator

cheers

"and the point is also to sort out the katas that are up to a certain standard "

.. isn't this the function of beta testing? i.e you don't let a kata advance beyond beta until it's up to a certain standard. Retiring a kata after only 1 day in beta seems a bit Spartan.

Oh you don't say? There was me thinking that FizzBuzz would be new to CW... how stupid of me.

Yes, and the point is also to sort out the katas that are up to a certain standard - this one didn't hit that standard :-) But worry not, you can create another kata (or even the same thing), hopefully with better result next time.

A word of advice: fizzbuzz is not exactly a new thing on CW... see: https://www.codewars.com/kata/search/?q=fizzbuzz