Codeforces и Polygon могут быть недоступны в период с 6 декабря, 22:00 (МСК) по 7 декабря, 00:00 (МСК) в связи с проведением технических работ.
→ Обратите внимание
→ Трансляции
→ Лидеры (рейтинг)
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 3985 |
| 2 | jiangly | 3741 |
| 3 | jqdai0815 | 3682 |
| 4 | Benq | 3529 |
| 5 | orzdevinwang | 3526 |
| 6 | ksun48 | 3489 |
| 7 | Radewoosh | 3483 |
| 8 | Kevin114514 | 3443 |
| 9 | ecnerwala | 3392 |
| 9 | Um_nik | 3392 |
| Страны | Города | Организации | Всё → |
→ Лидеры (вклад)
| № | Пользователь | Вклад |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 3 | maomao90 | 162 |
| 3 | atcoder_official | 162 |
| 5 | adamant | 158 |
| 5 | -is-this-fft- | 158 |
| 7 | awoo | 156 |
| 8 | djm03178 | 155 |
| 9 | TheScrasse | 154 |
| 10 | Dominater069 | 153 |
→ Найти пользователя
→ Прямой эфир
Codeforces (c) Copyright 2010-2024 Михаил Мирзаянов
Соревнования по программированию 2.0
Время на сервере: 05.12.2024 05:41:19 (h2).
Десктопная версия, переключиться на мобильную.
При поддержке
why not?
It took long time
I guess, this submission was the reason why they made it unrated.
Rumors say that rainboy is still refreshing that page to see whether the submission will pass
must be O(2^n) or soemthn
the 2.5 second time limit must have been wrong ig...
Wouldn't it be crazy if that were the case though? Like he submitted some O(2^n) stuff and the time limit glitched out for some reason and some computer has been running his code for the past 3 years?
fr, we can blame queue lags on his submission now :)
If so, I feel bad for the computer. Imagine running someone’s wrong code for 3 years straight
This is why you move to the next problem instead of refreshing the page.
but the work time is shown! So it's accepted but just with this.
This contest is even System testing.
LoL
rainboy, the man,the myth,the legend
It's probably a data base error, the memory and time are shown, meaning the solution was tested, there is this scenario:
the internet or something went a little bit slow, so the db updates got jammed, and one wasn't applied,
Or: the data center files went dumb and the db file didn't get saved correctly