How to solve this problem
# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | Dominater069 | 154 |
8 | awoo | 154 |
10 | luogu_official | 150 |
Name |
---|
Maybe you can use treap in segment tree?
Here's one (maybe not an optimal) solution:
Let's imagine first that we have no update queries. Then the problem can be easily solved using SQRT-decomposition of queries (I think that's how it's
done in the PewDiePie towncalled in English) and a map/unordered_map.The solution is practically the same as the one described in this blog and has time asymptotic.
Now we need to handle update queries. Assume . Let's store update queries in an auxillary array in the sorted (by position) order. Now the idea is practically the same as above. We handle question queries as if there were no update but after we've inserted current segment in our DS we have to perform all necessary updates (there'll be no more than of them) in a straightforward way.
Of course, there's no such strange constraint as . But we can create it: just split all Q queries into blocks of and after we've handled a block we perform all updates from this block with our original array.
I hope it's right.
is this correct, Did it work??