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