I use vector::assign_range, and CE. Also happens on append_range (using C++23). Is the compiler outdated? If so, plz update.
I use vector::assign_range, and CE. Also happens on append_range (using C++23). Is the compiler outdated? If so, plz update.
| # | User | Rating |
|---|---|---|
| 1 | jiangly | 3810 |
| 2 | Benq | 3676 |
| 3 | Kevin114514 | 3655 |
| 4 | maroonrk | 3463 |
| 5 | strapple | 3447 |
| 6 | Um_nik | 3387 |
| 7 | heuristica | 3322 |
| 8 | turmax | 3317 |
| 9 | tourist | 3307 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 157 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | Um_nik | 142 |
| 5 | Errichto | 139 |
| 6 | adamant | 136 |
| 7 | AmShZ | 135 |
| 8 | maroonrk | 133 |
| 9 | BledDest | 132 |
| 10 | qwexd | 129 |
Auto comment: topic has been updated by ForgottenCat (previous revision, new revision, compare).
So C++ has something called feature testing. Basically, when GCC say implements C++23, there is no clear guarantee that they implement the whole of the standard. So, when something is implemented (at least as of C++20 I believe), there will be a corresponding flag enabled.
In this case, assign_range has the
__cpp_lib_containers_rangesfeature test macro, and as per the example they provide there, you can check whether or not that macro is actually present or not (I tested and it's not present on codeforces as you might expect).So as you said, most likely G++ 14.2 with C++23 [msys2, 64bit] just hasn't implemented that feature yet...