Ad
  • Custom User Avatar

    both are valid solutions

  • Default User Avatar

    So just to clarify. Can I return asci art to return five or do I need to return another value that equals five?

  • Custom User Avatar

    Someone needs to make a Haskell translation for it to be solvable in Haskell (it isn't impossible in that language at all).

  • Custom User Avatar
  • Custom User Avatar
  • Custom User Avatar

    It's a good kata, But an additional notes that # is also not allowed would be nice.. i tried to solve it using acii and make it as a notes. already using the len methods but never returns tru. To all that is crawling on the discourse sections... "DONT USE #### AT ALLL"

  • Custom User Avatar

    Overthinking most of the time hahaha good kata !

  • Default User Avatar

    funny kata love it (:

  • Custom User Avatar

    Duplicate posting issue again

  • Custom User Avatar

    Or was it two issues in 24h?

    I think it's 2 existing issues within 7 days of last kata re-publish date, which is updated whenever a kata is published from draft to beta, approved from beta, or have a translation approved. (I don't think adding/deleting language versions through kata editor bumps the kata.) So bumping a kata will make the kata eligible to be sent to draft again. Notably, said issues don't need to be all recent.

  • Custom User Avatar

    I admit I am surprised a bit, because I was pretty sure that a beta gets auto-unpublished by issues only during a short period (24h?) after publication. I was certain that new issues cannot unpublish an old kata. Apparently, I was wrong and need to check. Or was it two issues in 24h? Dang, can't remember.
    But still, an old kata with low satisfaction can get auto-retired as "hopeless", and there are kata which were lost this way, true.

  • Custom User Avatar

    I do not know if direct edits with kata editor bump kata up or not

    Definitely not (or else beta katas would be bumped up all the time).

    But yes, there should be some way to stop katas all getting sent to draft so easily, or at least make them recoverable. There are lots of katas just get sent to draft and become basically lost.

  • Custom User Avatar

    Author solution is incorrect: ultimaProb(["BEWD","BEWD","BEWD"],1,0,1) expects None. It can't handle the situation when initial hand has more than strictly enough of 1 ingredient but not the other.

    Basically, it's never going to work (this can be verified by manually counting all the combinations) and needs to be rewritten if random tests are going to be added.

  • Custom User Avatar

    Bumping a myriad of old beta katas up the list when it's just updating the test block is pretty disruptive to the kata list (I sort kata by newest to look for newest beta katas). They're also often of dubious quality, and this also refreshes the kata freshness, so it's pretty much guaranteed to get all of them sent to draft via the issues raised soon after.

    Updating the test block alone shouldn't bump a kata, only a new translation or a unpublish/republish will. Why is it suddenly bumping katas?

  • Custom User Avatar

    It's unclear whether each parameter includes the other parameters, e.g:

    • Does d, b and p include the current hand?
    • Does d include b and p?
  • Loading more items...