# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3831 |
3 | Radewoosh | 3646 |
4 | jqdai0815 | 3620 |
4 | Benq | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | gamegame | 3386 |
10 | ksun48 | 3373 |
# | User | Contrib. |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | awoo | 157 |
7 | adamant | 156 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | Dominater069 | 153 |
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?