Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
My previous comment got flaged as a spoiler. Since I can't remove the suggestion tag from it (even though I think that might be what got it flaged) here's an official suggestion.
I suggest adding something to the effect of "the order of the stings in strarr should not be rearranged" to the description.
I believe that's what most people's biggest miscommunication with this kata is.
It makes me sad that my original post is flaged as a spoiler. I don't understand why and, I can't remove it. Now, because of that, it won't be able to help anybody else.
I'm very glad that my coment helped so many people before it got flaged as spoiler though!
Edit: Yay it's un-flaged for now!
Keep the words in "strarr" in the same order as they're given to you. Then find the (first) longest string using "k" number of consecutive strings.
Kata ranking can't be changed anymore (or for the time being).
This comment is hidden because it contains spoiler information about the solution
https://www.codewars.com/kata/reviews/59530d2f01d6039f86000021/groups/5dc0afd11318910001b936cf#5dc0b536c4c331002de1d9d7
Well, that is very stranged. I just looked at my C++ test cases again and that value cannot be generated...
I know, I do return lowercases the upper was in the tests not my return, Just happened once (a "P"), I realoaded the tests serveral times and didn't occured, I hadded
"if(i>='A'&&i<='Z') i+= -'A'+'a';" in case
public static long HowManyMeasurements(long n)
The lastest function signature maybe right.Check your code again~
Can you kindly check above, as a problem might still be persisting?
Sample test works fine. My code shouldn't have impact on test failures (exception thrown)?
Looks good to me.
nope, same exception: tests/Fixture.cs(24,78): error CS1503: Argument 1: cannot convert from 'long' to 'int'
Fixed.
Fixed, I guess?
Loading more items...