Can you answer my questions?
# | 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 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
Can you answer my questions?
Name |
---|
Pretty much the answer
Or in short, no.
As far as I know, I don't see many problems that can only be solved by using interval trees (or I am dumb, I do not know much of its properties anyway), so for now the latter one is enough. We need to learn things that are more useful first.
Not entirely. There are two different concepts called "segment tree".
The first one is what the top answer in StackOverflow is talking about, and also what the Segment tree article in Wikipedia talks about. It's something to do with counting the number of intervals that cover a given point.
The second one is more or less a term only used within competitive programming: a perfectly balanced binary tree where each node maintains the sum (or any other monoid) of its descendant leaves.
Oh, I see, that's why a lot of people (including me) see both of them as one sometimes. I was really surprised back then when saw that the interval tree was a different data structure.
Thanks a lot!
thanks