Ad
  • Custom User Avatar

    The input (included in fixed tests) includes double spaces between each set of symbols (I don't know how to display it correctly in markdown), and the correct output is "9 8 7 6 5 4 3 2 1 0" in this case.

  • Custom User Avatar

    I think there's an issue with tests in Julia:

    decodemorse("----. ---.. --... -.... ..... ....- ...-- ..--- .---- -----") --> "9 8 7 6 5 4 3 2 1 0"

    These characters don't have 4 spaces between them, so the output should be one word per the instructions. Am I missing something?

  • Custom User Avatar

    Thanks for the edits! I've done all but packing all testing code within the call to test_that. It seems cleaner to have test setup separate from the actual tests so that what test_that is testing is clear. Happy to try everything in test_that if that's accepted practice here.

  • Custom User Avatar
    • No sample tests
    • Comments should be removed
    • Random test cases should be ordered in a way that imports are above, followed by random input generation and assertions, all packed within test_that (context should be removed)
  • Custom User Avatar

    Might as well add some multiple dispatch. Julia people, is this the right way to handle these inputs or are conditionals more "julian"?

  • Custom User Avatar

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

  • Custom User Avatar

    When there is a flaw you get for example:

    Test Failed
    	`actual` not equal to `expected`.
    	2/3 mismatches (average diff: 144)
    	[1]  0 -   1 ==   -1
    	[2] 32 - 320 == -288
    

    Here a 0 and 32 are returned instead of (a fake) 1 and 320.

  • Custom User Avatar

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

  • Custom User Avatar

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

  • Custom User Avatar

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