Earn extra honor and gain new allies!
Honor is earned for each new codewarrior who joins.
Learn more
  • The description is vague not sure why you ware using different words in description like CamelCase camelCase camel_case
    If I didn't have the tests wouldn't be sure whether to make a method name in python which is snake_case.

    1. camelCase != UpperCamelCase or camelCase != PascalCase
    2. Too easy for 6 kyu IMO.
  • Updated the description

  • You will get the list with keywords

    It's not mentioned what to do when no arguments are passed. Apart from that, the expected result makes no sense: as words are surrounded by '' it's perfectly logical to assume that "''" represents a word of length 0 which is impossible.

  • I just checked and both Clang 3.6 and Clang 8 seem to work well - my solution works as expected, tests for Clang 8 print some compilation warnings but other than that, consistently pass. I did not check the code of tests, but since my expected-to-pass solution passes, I am rather inclined to think that your solution has some problems with memory management - do you return a free-able buffer every time?
    If you still think that your solution is correct and should not be rejected, post it here (remember abour "spoiler" flag!) and someone will have a look at it.

  • In C the test is crazy, it is throwing a free exception randomly. I run the same source code many times and I got different Test results. The program was tested directly in the computer and it works and the memory check seems also fine.

  • The task doesn't ask for camel casing, it asks for pascal case.
    The task should be renamed to ease confusion.

  • Hi,

    I have the same problem and i don't know if we are missing something or if it is broken.

    No, it was my mistake, its not broken.

  • Thank you for the tip Chrono, I figured it out. On to the next challenge!

  • It's a problem with your code, check the error message: begin 0, end 1, length 0 find those numbers in your code, and add a control test to avoid it.

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

  • I think I've found the cause of the weird behavior. Declaring your own capizalied method in a solution can mess up the tests.

    // extension String {
    // var capitalized: String { return "hey" }
    // }

  • Returning the input shows the expected result has all the initial letters of each word capitalized. Are you sure?

    Random Tests
    XCTAssertEqual failed: ("qixjchzvavcrjf  kpqkrymdjazny  zvwmhbic  mnerfq  eafzqa") is not equal to ("QixjchzvavcrjfKpqkrymdjaznyZvwmhbicMnerfqEafzqa") - Failed for input 'qixjchzvavcrjf  kpqkrymdjazny  zvwmhbic  mnerfq  eafzqa'
    
  • For swift this kata seems to be broken - basic tests are ok, but all random tests just capitalize the first word and ignore all the rest

  • Loading more items...