The title says its all!
→ Обратите внимание
→ Трансляции
→ Лидеры (рейтинг)
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 3880 |
| 2 | jiangly | 3669 |
| 3 | ecnerwala | 3654 |
| 4 | Benq | 3627 |
| 5 | orzdevinwang | 3612 |
| 6 | Geothermal | 3569 |
| 6 | cnnfls_csy | 3569 |
| 8 | jqdai0815 | 3532 |
| 9 | Radewoosh | 3522 |
| 10 | gyh20 | 3447 |
| Страны | Города | Организации | Всё → |
→ Лидеры (вклад)
| № | Пользователь | Вклад |
|---|---|---|
| 1 | awoo | 161 |
| 2 | maomao90 | 160 |
| 3 | adamant | 156 |
| 4 | maroonrk | 153 |
| 5 | atcoder_official | 148 |
| 5 | -is-this-fft- | 148 |
| 5 | SecondThread | 148 |
| 8 | Petr | 147 |
| 9 | nor | 144 |
| 10 | TheScrasse | 142 |
→ Найти пользователя
→ Прямой эфир
Codeforces (c) Copyright 2010-2024 Михаил Мирзаянов
Соревнования по программированию 2.0
Время на сервере: 27.07.2024 15:10:04 (h2).
Десктопная версия, переключиться на мобильную.
При поддержке
No annoying Cloudflare checks + smaller queues :)
The judge should have extremely powerful hardware to handle that
Agreed!
Sadly they're largely incompatible — the Cloudfare checks prevent bot swarming, if not for the checks, the queues would be larger (especially during contests)
Stress testing
Feature to see failing rest cases in practice as on atcoder or cses
You could take cue from Errichto's video on stress testing, given that you can find AC codes without hassle, you'd just need to write a generator to find failing cases
Thanks for help
Is there a way to find failing test cases during contents
Watch the video — if you can cook up a brute-force solution that works, it should be possible. Do note that it would be a time-taking endeavour and may not be worth it in a contest setting
But if we consider the 5 hours contest, then it is already worth it. Moreover, if you had written it normally, you could use it for all problems.
I mean with small changes
Agreed. There's always a trade-off though, and I didn't want to just hand it over as candy to someone starting off as it can be counterproductive as well.
stress testing is definitely a good skill. But it would still be nice to have the failing test, sometimes I'm to lazy to stress test. Even though the failing test often is big, you can still run your code on it with tons of asserts, or in debug. Basically i just want to find the bug with minimal effort and move on
Something that tell you don't be sad after getting WA.
Displaying some waifu pic would be helpful I guess -.- Someone might even try to get WA on purpose, lol.
This can be helpful ^-^
Duuu nato givu appu senpaii!!~~~ yyuuu can stiru duu zisu!!