Ad
  • Custom User Avatar

    Switching versions did allow me to pass the kata, but like Unnamed said, the incorrect version needs to be disabled.

  • Custom User Avatar

    Haskell translation is broken.

    The name of the test module must end with 'Spec'

  • Custom User Avatar

    It appears to be working now

  • Custom User Avatar

    I'm seeing an error from the test module when I try to submit with Haskell. Same error for both versions of GHC.

    test/JumpingSpec.hs:41:11: error:
        • Variable not in scope: digs :: a -> [a]
        • Perhaps you meant ‘digs'’ (line 40)
       |
    41 | digs' x = digs (x `div` 10) ++ [x `mod` 10]      
       |           ^^^^
    
  • Custom User Avatar

    Ah, yes. That worked. Thanks!

  • Custom User Avatar

    When I run the sample tests in C# my code compiles and runs fine, but when I try to run the full test suite it fails to compile with an error about missing assembly references. Seems to be something with setting up and tearing down the code runtime. Here's the text of the error I get.

    fixture.cs(12,3): error CS0246: The type or namespace name `OneTimeSetUp' could not be found. Are you missing an assembly reference?
    fixture.cs(170,3): error CS0246: The type or namespace name `OneTimeTearDown' could not be found. Are you missing an assembly reference?
    
  • Custom User Avatar

    The problem description clearly states that c is the largest value

  • Custom User Avatar

    Agreed. The type should either be Int or Integer, depending on how big the tests get. It uses int in C, C++, C#, and Java.

  • Custom User Avatar

    I'm fairly certain that my code works, but I keep seeing Error in '/home/codewarrior/solution': malloc(): memory corruption for the 24th test case. When I printed the input and output of my code for that test case it produced the expected result, but still fails the test case with the error. When I run the same code on my machine with that test case it works just fine.

  • Custom User Avatar

    The Haskell Hello World test case shows shows the actual output as the expected and vice versa.