| # | User | Rating |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | Kevin114514 | 3611 |
| 4 | jiangly | 3583 |
| 5 | strapple | 3515 |
| 6 | tourist | 3470 |
| 7 | dXqwq | 3436 |
| 8 | Radewoosh | 3415 |
| 9 | Otomachi_Una | 3413 |
| 10 | Um_nik | 3376 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 160 |
| 2 | adamant | 150 |
| 3 | Um_nik | 146 |
| 4 | Dominater069 | 144 |
| 5 | errorgorn | 141 |
| 6 | cry | 139 |
| 7 | Proof_by_QED | 136 |
| 8 | YuukiS | 135 |
| 9 | chromate00 | 134 |
| 9 | TheScrasse | 134 |
-[submission:195959656]: Passes
-195731060: TLE on 27
What happens when this happens in an actual contest though. Is the solution judged multiple times, before the final verdict, or you just say you had a bad day?
I remember the second code passing the system tests before the hacking phase. The complexity is same as the intended one
If the solution very hardly passes the TL, you are in the danger zone.
The solution is judged multiple times if it gets a TLE, iirc. In that case, you got TLE in multiple test cases.