# | User | Rating |
---|---|---|
1 | tourist | 3856 |
2 | jiangly | 3747 |
3 | orzdevinwang | 3706 |
4 | jqdai0815 | 3682 |
5 | ksun48 | 3591 |
6 | gamegame | 3477 |
7 | Benq | 3468 |
8 | Radewoosh | 3462 |
9 | ecnerwala | 3451 |
10 | heuristica | 3431 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | -is-this-fft- | 162 |
3 | Dominater069 | 160 |
4 | Um_nik | 158 |
5 | atcoder_official | 156 |
6 | Qingyu | 153 |
7 | djm03178 | 152 |
7 | adamant | 152 |
9 | luogu_official | 150 |
10 | awoo | 147 |
Name |
---|
This rather seems like an RTE. Your pw array is sized 26 and bs = 25, hence j + 2 can be max 26 which is out of bounds for pw, hence RTE.
When an RTE happens, it is actually an Undefined behavior, which can result in any type of judgment -> TLE in this case.
But this submission is my AC submission!
The difference isn't much the solution passed in 2979 ms. Maybe it took approx 20 ms to access the element in the array (j*a) times as it was in nested for which was then resolved by providing a constant value to hi. I am not very sure though.But still the code is too close to TLE.
Wait, did I catch a totally different bug lol.