I created a video editorial talking about how to use Atcoder Library's Segment Tree to optimize CF2019D: Speedbreaker
# | User | Rating |
---|---|---|
1 | jiangly | 4039 |
2 | tourist | 3841 |
3 | jqdai0815 | 3682 |
4 | ksun48 | 3590 |
5 | ecnerwala | 3542 |
6 | Benq | 3535 |
7 | orzdevinwang | 3526 |
8 | gamegame | 3477 |
9 | heuristica | 3357 |
10 | Radewoosh | 3355 |
# | User | Contrib. |
---|---|---|
1 | cry | 168 |
2 | -is-this-fft- | 165 |
3 | atcoder_official | 160 |
3 | Um_nik | 160 |
5 | djm03178 | 157 |
6 | Dominater069 | 156 |
7 | adamant | 153 |
8 | luogu_official | 152 |
9 | awoo | 151 |
10 | TheScrasse | 147 |
I created a video editorial talking about how to use Atcoder Library's Segment Tree to optimize CF2019D: Speedbreaker
Name |
---|
Very hard problems
I dont get it, D was extremely simple. You just have to track the first and last occursnce of each character, and then keep intersecting the segments.
A 20 line implementation would reach $$$O(n)$$$ without segment trees on this problem.
Yes, I agree Segment Tree might be an overkill for this problem. However, I arrived at the segtree solution without a lot of efforts, hence wanted to share an alternate solution from the editorial.
Also, looking at submission count of Problem C (6529) vs Problem D (1373), a lot of people did not submit the overkill segtree solution, possibly because they were not aware of such data structures or thought process of reducing the problem to a standard domain, hence the video.
Yes it's always useful to learn different ways to solve a problem.
Can you please explain your code and thought process of this problem ?