C++ 26 is released.
So why codeforces till now doesn't have this cpp version ?
C++ 26 is released.
So why codeforces till now doesn't have this cpp version ?
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3408 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | AmShZ | 145 |
| 5 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | BledDest | 136 |
| 8 | adamant | 135 |
| 9 | maroonrk | 132 |
| 10 | cry | 130 |
As usual, nothing useful in this standard. Which of these features would you like to use? Maybe
std::debugging::breakpoint_if_debuggingstd::linalgandstd::simdseem pretty cool, although I just instinctively find it hard to trust the codegen for the lattermaybe its the amount of compile-time stuff u can do
LOL, 23 was added in the middle of 2024
cppreference hasn't even documented the functions yet properly (or at least for linalg), and I refuse to read any other c++ reference.
I would like to wait for the compiler implementing most features and getting stabilized, rather than having a half-baked compiler in a rush.
If Codeforces updates compilers more frequently, I wouldn't oppose the idea. But based on the pace of compiler updates in the past, having an incomplete compiler has a risk that it will stick way too long, leaving us unable to use some features for a long time.