I was using Python. I passed it already. Thanks for your help though.

I'm so satisfied with this kata! I was up all night trying to figure it out. I learned a lot from this and I appreciate the creator and contributors for this kata.

I cannot reproduce this problem with your current Python solution either.

Yes, it seems to me that negative numbers are tested.

Python, but I've gotten it to work already. I'm having trouble with passing the last attempted test because of timeouts. It also shows at the top Passed: 30 and Failed: ?

In what language? Negative numbers should be tested, but without knowing the language, I do not know where to check.

Your solution passes some thests and then either crashes, or times out. It is difficult to tell without knowiing your code, or the language you are attempting. I cannot reproduce this problem with your current C# solution.

I don't know if it's my CPU or something but everytime it hits the last one it shows execution error and says Passed: 30 Failed: ?. Does anyone know what this means?

Are negative numbers actually being passed to the fib function? When testing for negative (if n < 0) the condition is never met.

I appreciate your explanation and I'll do my part in making sure that I fully understand any kata as much as possible. I truly understand the concerns stated above and I honestly should have asked the question rather than raising an issue. I have done some research on this topic to fully understand it and I'm practicing as we speak. It is a challenging kata and appriciate you and the contributors for providing it.

I did not claim that understanding the task was common sense, everyone can make mistakes. I misunderstand or miss things in descriptions often, too, and only realize it when I submit my code and see that it does not pass the tests.

What I meant by common sense, as I wrote, and as explainedhere, was that when you think you have found a really big mistake, especially in a kata with so many completions (and 38,500 completions is massive), you should stop and think:
Did I understand the task correctly ? Am I solving the right problem ? Did I miss something in the description ?

Only after double checking everything, scrolling down the discourse page to see if there have been similar remarks / reports in the past, you should open an issue. Issues should not be opened lightly, as:

• they create more work for the volunteers who curate Codewars content, who will check the issue report, try to reproduce / analyze it, and possibly submit a patch
• accumulating bogus issues discourage people from trying a kata, and encourage newbies to blame the tests for their own mistakes, thereby opening yet more bogus issues.

I did try to explain the mistake in your logic, too, but you kept focused on your own interpretation of the task instead of on what the description explains.

@trashy_incel bro watch how you talk to people. There are plenty of ways to express yourself particularly when it comes to someone trying to figure things out. If you knew I didn't understand something, rather than telling me about common sense, then you should have at minimun replied with a link to some help. It obviously wasn't "common" to me. Sometimes it's how you express things and not about the assumptions you're making about the programmer. Yes, I raised an issue because I thought there was one but you could have replied with:

"you must be unfamiliar with this kind of problem here's a link to something that'll help you understand it more".

I'm actually doing my due diligence and learning more about this and practicing a whole lot more. I thought I knew what was going on but I completely misunderstood the entirety of the kata (conceptually). I was so focused on the procedural aspect rather than trying to truly understand it.

I'm actually doing my due diligence and learning more about this and practicing a whole lot more. I thought I knew what was going on but I completely misunderstood the entirety of the kata (conceptually). I was so focused on the procedural aspect rather than trying to truly understand it.

and stop raising issues when you do not understand something in a kata; it is rude. an issue implies there is a serious problem with a kata, that other regular users (volunteers) will have to analyze, debug and fix. when you are confused, ask a question.