.
# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
# | User | Contrib. |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
5 | adamant | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | djm03178 | 153 |
Name |
---|
This is definitely not a good idea for some constructive problems, where knowing the jury answer could allow participants to reverse-engineer the solution from the outputs. This is a bit less of an issue for problems with fixed answers, but something like that can still happen to a lesser degree.
Ari It can be taken care of , if we enable this checking only a limited number of times per each question, for example a maximum of 4 checks per question , I guess this clears it .
You can easily know you've misunderstood the problem when you receive WA verdict.
Yeah but in contests won't it be a -50 after passing pretest-1 only to fail in the next one
Don't turn Codeforces into HackerEarth.