Timeline for Code that handles n% of test cases but not all
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2018 at 20:52 | comment | added | Stingy | @NicHartley I've provided some examples in comments to 200_success' answer here (which 200_success mysteriously never responded to). Maybe I'm a bit too focused on the specific question I defended in my answer here, but I seriously think the code from this question is not broken and the 50% correctness stem from a mere misunderstanding, so I think the question was closed inappropriately. Even according to 200_success' own answer here, the question might not be off-topic, but apparently, 200_success is not interested in his/her judgement being questioned. | |
| May 7, 2018 at 16:00 | comment | added | Nic | I don't follow your logic. If someone knows a thing, then tells me that thing, I now know it too. Likewise, if someone else knows my code is badly broken (passes just 50% of test cases), then tells me that, then... I know that, now. Yes, it's not particularly useful if the test cases aren't at least hinted with examples, but that's a problem with the website; in any case, the OP still knows their code is broken, and we can't guess how any more than they can. | |
| Apr 30, 2018 at 14:06 | history | answered | Stingy | CC BY-SA 3.0 |