| # | User | Rating |
|---|---|---|
| 1 | tourist | 3803 |
| 2 | jiangly | 3707 |
| 3 | Benq | 3627 |
| 4 | ecnerwala | 3584 |
| 5 | orzdevinwang | 3573 |
| 6 | Geothermal | 3569 |
| 6 | cnnfls_csy | 3569 |
| 8 | Radewoosh | 3542 |
| 9 | jqdai0815 | 3532 |
| 10 | gyh20 | 3447 |
| # | User | Contrib. |
|---|---|---|
| 1 | maomao90 | 168 |
| 2 | awoo | 163 |
| 3 | adamant | 162 |
| 4 | maroonrk | 152 |
| 5 | nor | 151 |
| 5 | -is-this-fft- | 151 |
| 7 | atcoder_official | 147 |
| 7 | TheScrasse | 147 |
| 9 | Petr | 145 |
| 10 | pajenegod | 144 |
Execution time being equal to the time limit
in codeforces judge it is (or at least it was) pretty common to get 999ms time on a problem with 1000ms time limit.
but I saw some submission getting 2500ms time on 2500ms a problem with 2500 time limit.
has the rules of codeforces changed so it doesn't consider it time limit exit or the judgement system of codeforces has changed so it can get 2500ms time and it couldn't before?
| Rev. | Lang. | By | When | Δ | Comment | |
|---|---|---|---|---|---|---|
| en4 |
|
Random_Bulshit_Submit | 2024-06-25 20:56:29 | 2 | ||
| en3 |
|
Random_Bulshit_Submit | 2024-06-25 20:43:35 | 0 | (published) | |
| en2 |
|
Random_Bulshit_Submit | 2024-06-25 20:43:10 | 4 | ||
| en1 |
|
Random_Bulshit_Submit | 2024-06-25 20:42:23 | 545 | Initial revision (saved to drafts) |
