| # | 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 | adamant | 159 |
| 6 | -is-this-fft- | 158 |
| 7 | awoo | 157 |
| 8 | TheScrasse | 154 |
| 8 | Dominater069 | 154 |
| 8 | nor | 154 |
Crazy time difference between submissions with minimal changes
Hi, if you compare this submission (296ms) with this one (3025ms), this is the difference:
I think this is crazy because g is a vector<vector<int>> with size 3 * 10^5 with at most 3 * 10^5 entries, and the function build that returns g is called once in the program. This huge time difference is the same on both 64-bit C++ compilers, but it is not present in the 32-bit C++ compiler.
UDP: Calling the function build twice solves the problem
| Rev. | Lang. | By | When | Δ | Comment | |
|---|---|---|---|---|---|---|
| en7 |
|
wnmrmr | 2024-02-21 20:21:26 | 2 | Tiny change: 'iler.\n\nUDP: Calling ' -> 'iler.\n\nUPD: Calling ' | |
| en6 |
|
wnmrmr | 2024-02-21 20:19:37 | 8 | Tiny change: '7645857)\n\n\n | |
| en5 |
|
wnmrmr | 2024-02-21 20:17:42 | 317 | (saved to drafts) | |
| en4 |
|
wnmrmr | 2024-02-21 16:29:50 | 0 | (published) | |
| en3 |
|
wnmrmr | 2024-02-21 16:28:48 | 28 | Tiny change: 'ers, but is not p' -> 'ers, but it is not p' | |
| en2 |
|
wnmrmr | 2024-02-21 16:25:38 | 317 | Tiny change: 'ze `3 * 10 ^ 5` with at' -> 'ze `3 * 10^5` with at' | |
| en1 |
|
wnmrmr | 2024-02-21 16:18:40 | 322 | Initial revision (saved to drafts) |
