| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | ecnerwala | 3648 |
| 2 | Benq | 3580 |
| 3 | orzdevinwang | 3570 |
| 4 | cnnfls_csy | 3569 |
| 5 | Geothermal | 3568 |
| 6 | tourist | 3565 |
| 7 | maroonrk | 3530 |
| 8 | Radewoosh | 3520 |
| 9 | Um_nik | 3481 |
| 10 | jiangly | 3467 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | maomao90 | 174 |
| 2 | awoo | 164 |
| 2 | adamant | 164 |
| 4 | TheScrasse | 159 |
| 4 | nor | 159 |
| 6 | maroonrk | 156 |
| 7 | -is-this-fft- | 150 |
| 8 | SecondThread | 147 |
| 9 | orz | 146 |
| 10 | pajenegod | 145 |
Привет, Codeforces!
Вы же помните мой пост Новое: Диагностика решений на C++? Если нет, пожалуйста, прочтите его.
Совсем недавно я реализовал улучшенное отображение диагностики. Теперь на страницах со списком попыток (статус) вы иногда можете заменить вот такое нововведение:
По нажатию на значок 
вы увидите код с выделенной проблемной строкой и описание возможной ошибки.
Как вам?
It's great!
а другим языкам будет добавлена такая фишка?
fantastic!
Thanks MikeMirzayanov for the efforts put into improving codeforces!
Cool thing. I just hope that people won't rely just on this. Remember that you can catch silly mistakes yourself with good compilation flags. You will find mistakes faster and you can use it during the contest too, while CF diagnostics are only for practice (right?).
Thanks!!!!!
But can we see this feature during contests?
/// upd: sorry for repeating comment.
Awesome
Maybe in future we will see smth like: "please stop doing this task, author's solution is not reliable"
XD this comment made my day :P
A great addition to the existing system. Kudos!
How to turn this off? It makes me feel so stupid when I see "potential out of bounds error on line X"............. qwq. I would rather find it myself.
What about coding in notepad and submitting without compiling first? Stupid compiler telling you there's a missing semicolon. :>
Yup, the testing system is clearly suitable for testing.
(bad translation from a local Russian meme)
If you don't click the icon, the tips wouldn't show. So, it actually is a switch.
Sir ,is this feature only works for GNU c++17 ?
Not only for it, I've tried.
круто, добавьте такое-же на python, пожалуйста
наныли!
It must be disabled on contests.
of course it will
otherwise it will create more problems
It's awesome!!!. Great work Sir
Cool! & Thanks!
I think contests would be more challenging if this feature is disabled for contestants!
Is this going to be enabled on pretests during contests?
If not, how do I setup these diagnostics on my own system? I see usually that the diagnostics reported on Codeforces are from VS 2017 — is it possible to setup this on Linux? If not, how do I do it on Windows?
that is great and fantastic efforts
I am curious about its implementation and its limitations
Great
It's really convenient to correct the error.
In fact,this is a good tool.But if people are depend on this without debug by themselves,that will be bad
awesome!!
Can we choose to turn this off for practice?
Can't you just not click to the
?
It gives a slight hint as to where your solution went wrong, even if you just see it and don't click on it. I would still like to find out that my solution has some sort of undefined behavior by myself instead of being told.
It can make easy for me to believe that my logic is correct and implementation has something wrong. But I don't want that when doing the practice. I want to figure out myself what exactly is wrong, the logic or the code.
While waiting for the feature to be implemented, it's possible to use some userscript or user stylesheet as a workaround.
There is a setting in a user profile to hide the feature.
please add an option to turn it off :(
Just use J A V A
I like it
Deleted. I 'm sorry for my unnecessary comment.
Or just leave Codeforces for good /s
Very helpful features.Nice work!!!!
Я так понял это и есть главный аргумент писать на c++
HAHAHAHAHAHAHAHAHAHHAHAHA. ROFL. LMAO
nice!
All we asked for a way to access large testcases for which our code fails! Just kidding, This UI will definitely help a lot! :)
Wow! Fantastic!
Great job!!
It's very great ,and it will be better to see this feature in contests it will help us find the mistake fast .
I think, this feature is going to be off during the contest
may be , but I hope not .
Nice！！！！
It’s so good
One of the reasons why codeforces is the best platform to practice and master competitive programming. Keep up the good work !
ok, I still think we need a way to turn this off, because when I submit some wrong solution to cf for practice it literally is stuck for like 2 minutes running the diagnostic and it is annoying to not know if it is just a judging system hold up or the diagnostic
I don't think this is the case. The diagnostic solution should also be executed in limited time. (otherwise it would be too easy to cause a DoS by doing
#ifdef _GLIBCXX_DEBUG while(1); #endif)Also the diagnostic is only run if the solution run quickly, so even if it's a few times slower it should not take a few minutes.
They give the diagnostic a lot more time to run, it is not infinite time, but it is still a lot more.
What about show participiant's place in result table after contest completed in every page.
So great!We can save a lot of time debugging!