How to solve this problem
# | User | Rating |
---|---|---|
1 | tourist | 3856 |
2 | jiangly | 3747 |
3 | orzdevinwang | 3706 |
4 | jqdai0815 | 3682 |
5 | ksun48 | 3591 |
6 | gamegame | 3477 |
7 | Benq | 3468 |
8 | Radewoosh | 3462 |
9 | ecnerwala | 3451 |
10 | heuristica | 3431 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | -is-this-fft- | 162 |
3 | Dominater069 | 160 |
4 | Um_nik | 158 |
5 | atcoder_official | 157 |
6 | Qingyu | 155 |
7 | djm03178 | 152 |
7 | adamant | 152 |
9 | luogu_official | 150 |
10 | awoo | 147 |
Name |
---|
Maybe you can use treap in segment tree?
Here's one (maybe not an optimal) solution:
time asymptotic.
. 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.
. 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.
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
Now we need to handle update queries. Assume
Of course, there's no such strange constraint as
I hope it's right.
is this correct, Did it work??