| # | 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 | 3442 |
| 9 | ecnerwala | 3392 |
| 9 | Um_nik | 3392 |
| # | User | Contrib. |
|---|---|---|
| 1 | cry | 169 |
| 2 | atcoder_official | 162 |
| 2 | maomao90 | 162 |
| 2 | Um_nik | 162 |
| 5 | djm03178 | 158 |
| 6 | -is-this-fft- | 157 |
| 7 | adamant | 155 |
| 8 | awoo | 154 |
| 8 | Dominater069 | 154 |
| 10 | nor | 150 |
What happened with __int128_t?
I was solving problem F of ABC just now. And I got passed with long long, but when I change the type into __int128_t, it got wrong answer in most of the cases. Why is that?
Upd: It is said that __int128_t can not be the index of array. It may cause wrong answer. So it is always not a good idea to use things like #define int __int128_t.
| Rev. | Lang. | By | When | Δ | Comment | |
|---|---|---|---|---|---|---|
| en6 |
|
0x0002 | 2024-06-10 13:36:14 | 18 | ||
| en5 |
|
0x0002 | 2024-06-10 09:01:19 | 226 | ||
| en4 |
|
0x0002 | 2024-06-09 17:32:32 | 77 | ||
| en3 |
|
0x0002 | 2024-06-09 14:50:40 | 4 | Tiny change: 'aid that `int128` can not ' -> 'aid that `__int128_t` can not ' | |
| en2 |
|
0x0002 | 2024-06-09 06:49:47 | 91 | ||
| en1 |
|
0x0002 | 2024-06-08 17:08:35 | 379 | Initial revision (published) |
