# | User | Rating |
---|---|---|
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 |
# | User | Contrib. |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | adamant | 157 |
6 | awoo | 157 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | djm03178 | 153 |
Name |
---|
:(
I once kept getting ,for a Binary search on answer problem, Memory limit exceeded on TEST 7 for days. And it only needed to comment #define int long long XD!
My friend once encountered the same bug
I don't feel anything cuz I don't do these silly mistakes.
You won't understand because solving *800 difficulty problems never get you these kinds of bugs. They just make you stuck on newbie forever.
You can also avoid this bug by never hardcoding constraints. (Use std::vector).
True!
vector resizing is cozy as well :v
Agreed.
nice! But I needed an array of vectors in this problem
I hope i will never encounter this
I even commented all define of my code for find the problem XD
It happens! I remember spending a whole day on single bug, but it's worth!
Exactly! If you find such bugs once, you will not make this mistake again Everything is experience!
Is it UB?
And you can compile with Clang++17 Diagnostics.