# | 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 |
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?