| # | User | Rating |
|---|---|---|
| 1 | tourist | 3985 |
| 2 | jiangly | 3741 |
| 3 | jqdai0815 | 3682 |
| 4 | Benq | 3529 |
| 5 | orzdevinwang | 3526 |
| 6 | ksun48 | 3489 |
| 7 | Radewoosh | 3483 |
| 8 | Kevin114514 | 3443 |
| 9 | ecnerwala | 3392 |
| 9 | Um_nik | 3392 |
| # | User | Contrib. |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 3 | atcoder_official | 162 |
| 3 | maomao90 | 162 |
| 5 | adamant | 158 |
| 5 | -is-this-fft- | 158 |
| 7 | awoo | 156 |
| 8 | TheScrasse | 154 |
| 8 | djm03178 | 154 |
| 10 | Dominater069 | 153 |
It happened during last Div.4
In this submission in compilation log you can see only warnings, no errors, but verdict is CE
So experimentally I figured out that an error in line 1285, ofc locally it works good with C++17:
constexpr auto darr = array<pair<int, int>, 4>{{{1, 0}, {0, 1}, {-1, 0}, {0, -1}}};
Will be nice if codeforces show full compilation log or somehow print errors first
Like cf-tool, but in python and single file, so you dont need to install anything
