# | 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 |
Name |
---|
This type of diagnostic error (the one in your submission) usually happens in my case whenever I try to access a non-allocated memory space (like trying to access an element not in an array), I can see a lower_bound in your code, have you checked for it's edge cases, like when it throws last?
PS — I am only a noob so take this with a grain of salt
Seems fine to me....have used the same thing many times.....but am not much of an expert myself.....
You do binary search on a not sorted array.
Thanks......I just assumed that input was ordered.....
Still getting WA for this, would really appreciate if someone could point out what is wrong?