I hacked my solution after contest. But now the same code got Accepted!!
Problem: 1722A - Spell Check
Hacked Submission: 170196701
Accepted Submission : 170591464
Both Are Same Code..!
# | User | Rating |
---|---|---|
1 | tourist | 3993 |
2 | jiangly | 3743 |
3 | orzdevinwang | 3707 |
4 | Radewoosh | 3627 |
5 | jqdai0815 | 3620 |
6 | Benq | 3564 |
7 | Kevin114514 | 3443 |
8 | ksun48 | 3434 |
9 | Rewinding | 3397 |
10 | Um_nik | 3396 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 155 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
10 | nor | 152 |
I hacked my solution after contest. But now the same code got Accepted!!
Problem: 1722A - Spell Check
Hacked Submission: 170196701
Accepted Submission : 170591464
Both Are Same Code..!
Name |
---|
It seems there was a problem on systest.
Because of the huge number of hacks to A, many successful hack cases are excluded from the systest, and
10 hudairoTLE
x1000 (or similar cases) are not included in the systest. This case will killnext_permutation
codes. There should be at least one such case in the systest but actually no.I guess some codes which passed the systest should be killed by this case on the systest, and this cause something unfair.
UPD: uphacked the same code. 170657084
The hack case will be automatically added to the future test, but still the problem of systest wasn't resolved.