Ad
  • Custom User Avatar

    Fixed

  • Custom User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Custom User Avatar

    #kata-forge

    Track: Build

    Language: Go

    What it is: This is concurrent web crawler.

    Runtime usage: Used latest Go 1.24 feature: per-iteration loop variables.

    AI-assisted:

  • Custom User Avatar

    This Kata is intended for Go 1.24. The loop variable capture issue was fixed in Go 1.22.

  • Custom User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Custom User Avatar

    You can add tabs and CR and LF symbols for edge cases

  • Custom User Avatar

    Thank you, fixed

  • Custom User Avatar

    Immediately did not notice the error, corrected

  • Custom User Avatar

    Water molecules??

  • Custom User Avatar

    Hello! I am a Codewars bot, and I reviewed your kata for common authoring mistakes.

    Click to see the review

    Commonly occurring issues

    • 🛑 No debugging info on failure: In the submission tests, the random tests block It("should pass random tests", func() { ... }) does not provide the specific input that caused a failure in assertion messages or in the test title. If one of the iterations fails, Ginkgo will only show the generic test name, not which of the 50 generated input strings was problematic. Consider including the current input (or its seed/index) in the Expect messages, for example by using Expect(isValidCO2(result)).To(BeTrue(), "input=%s result=%s", string(runes), result) or similar, so that a failing random case can be reproduced and diagnosed.

    Please mind that I am not a very smart bot, and you should verify my remarks with any resources available for kata authors and translators:

  • Custom User Avatar

    Hello! I am a Codewars bot, and I reviewed your kata for common authoring mistakes.

    Click to see the review

    Commonly occurring issues

    • ☠️ Missing random tests: Submission tests contain only fixed, hard-coded input strings like "HOH", "HHOOHH", and patterns built with strings.Repeat (e.g. strings.Repeat("HHO", 20)), but no randomly generated cases. To prevent hardcoded solutions and better exercise synchronization logic with varied arrival orders and sizes, you should add a section of tests that generate random sequences of H and O threads and verify them with isValidH2O.

    Please mind that I am not a very smart bot, and you should verify my remarks with any resources available for kata authors and translators: