Hello everyone!
I often find it very frustrating when there is one testcase that gets a wrong answer and you have no idea why. Is there a strategy among coders as to how to deal with edge cases?
Thanks in advance
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
Hello everyone!
I often find it very frustrating when there is one testcase that gets a wrong answer and you have no idea why. Is there a strategy among coders as to how to deal with edge cases?
Thanks in advance
Название |
---|
trying to make small test cases and solving them manually works for me most of the time.
Actually there isn't. Firstly if your solution has a lot of edge cases, then you should probably look for some better solution, because the correct ones mostly don't have many edge cases.
Secondly, you should emphasize on thinking the solution thoroughly, before implementing. This is a good practise and will save you a lot of time later.
Thirdly, once you solve a lot of problems, the bugs and edge cases are mostly similar. You'll eventually become good at identifying them.
You can also use these two links https://mirror.codeforces.com/blog/entry/18087 https://mirror.codeforces.com/blog/entry/44493#comment-290139