| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | jiangly | 3670 |
| 3 | Kevin114514 | 3657 |
| 4 | maroonrk | 3355 |
| 5 | Um_nik | 3353 |
| 6 | squareOf105 | 3346 |
| 7 | tourist | 3343 |
| 8 | strapple | 3324 |
| 9 | heuristica | 3322 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | AmShZ | 143 |
| 4 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | BledDest | 135 |
| 9 | maroonrk | 133 |
| 10 | qwexd | 130 |
| Name |
|---|



Auto comment: topic has been updated by mansigpt (previous revision, new revision, compare).
though map size is 1 still z.Second++ is unable to update it. I too don't don't get it.
auto creates copy so use this to update I think this may be the issue not completely sure though m[{(z.F.F),(z.F.S)}]++;
try passing by reference:
Right now z is just a copy of the pair in the map. In general, in the code
each x will be a copy of an element in v, and changes to x won't be reflected in v. Maybe read about references somewhere to learn more details.
In range-based loops
for (auto x : container)mean you doing with copy ofxand it is changable (but not the variable in the container)for (auto &x : container)mean you doing with reference ofxand it is changablefor (const auto x : container)mean you doing with copy ofxand it is unchangablefor (const auto &x : container)mean you doing with reference ofxand it is unchanableIf you use large container and not want to change it, you should use
for (const auto &x : container)since it wont have to waste time on creating copies then detroys themIf you want the variable to be changable, you should use
for (auto &x : container)