# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3839 |
3 | Radewoosh | 3646 |
4 | jqdai0815 | 3620 |
4 | Benq | 3620 |
6 | orzdevinwang | 3612 |
7 | Geothermal | 3569 |
7 | cnnfls_csy | 3569 |
9 | ecnerwala | 3494 |
10 | Um_nik | 3396 |
# | User | Contrib. |
---|---|---|
1 | Um_nik | 164 |
2 | maomao90 | 160 |
3 | -is-this-fft- | 159 |
4 | atcoder_official | 158 |
4 | cry | 158 |
4 | awoo | 158 |
7 | adamant | 155 |
8 | nor | 154 |
9 | TheScrasse | 153 |
10 | maroonrk | 152 |
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 ofx
and it is changable (but not the variable in the container)for (auto &x : container)
mean you doing with reference ofx
and it is changablefor (const auto x : container)
mean you doing with copy ofx
and it is unchangablefor (const auto &x : container)
mean you doing with reference ofx
and 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)