Rating changes for last rounds are temporarily rolled back. They will be returned soon. ×

MikeMirzayanov's blog

New: Diagnostics of Solutions in C++ (Better UI)
By MikeMirzayanov, history, 5 years ago, In English

Hello,

Do you remember my post New: Diagnostics of Solutions in C++? If not, please read it.

Recently, I've implemented better UI to show you diagnostics. Now in on the status pages sometimes you can notice something like this:

Click to the and you'll see the code with the highlighted problematic line and description with the possible reason of the mistake.

Do you like it?

  • Vote: I like it
  • +1754
  • Vote: I do not like it

Comments Comments (52)
| Write comment?
»
5 years ago, # |
  Vote: I like it +70 Vote: I do not like it

It's great!

→ Reply
»
5 years ago, # |
  Vote: I like it +33 Vote: I do not like it

fantastic!

→ Reply
»
5 years ago, # |
← Rev. 2   Vote: I like it +15 Vote: I do not like it

Thanks MikeMirzayanov for the efforts put into improving codeforces!

→ Reply
»
5 years ago, # |
  Vote: I like it +225 Vote: I do not like it

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?).

→ Reply
»
5 years ago, # |
← Rev. 2   Vote: I like it 0 Vote: I do not like it

Thanks!!!!!

But can we see this feature during contests?

/// upd: sorry for repeating comment.

→ Reply
»
5 years ago, # |
  Vote: I like it +10 Vote: I do not like it

Awesome

→ Reply
»
5 years ago, # |
← Rev. 2   Vote: I like it -81 Vote: I do not like it

Maybe in future we will see smth like: "please stop doing this task, author's solution is not reliable"

→ Reply
»
5 years ago, # |
  Vote: I like it +19 Vote: I do not like it

A great addition to the existing system. Kudos!

→ Reply
»
5 years ago, # |
  Vote: I like it +31 Vote: I do not like it

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.

→ Reply
  • »
    »
    5 years ago, # ^ |
      Vote: I like it +162 Vote: I do not like it

    What about coding in notepad and submitting without compiling first? Stupid compiler telling you there's a missing semicolon. :>

    → Reply
    • »
      »
      »
      5 years ago, # ^ |
      ← Rev. 2   Vote: I like it +28 Vote: I do not like it

      Yup, the testing system is clearly suitable for testing.

      (bad translation from a local Russian meme)

      → Reply
  • »
    »
    5 years ago, # ^ |
      Vote: I like it +7 Vote: I do not like it

    If you don't click the icon, the tips wouldn't show. So, it actually is a switch.

    → Reply
»
5 years ago, # |
← Rev. 2   Vote: I like it 0 Vote: I do not like it

Sir ,is this feature only works for GNU c++17 ?

→ Reply
»
5 years ago, # |
  Vote: I like it +36 Vote: I do not like it

It must be disabled on contests.

→ Reply
»
5 years ago, # |
  Vote: I like it +1 Vote: I do not like it

It's awesome!!!. Great work Sir

→ Reply
»
5 years ago, # |
  Vote: I like it +3 Vote: I do not like it

Cool! & Thanks!

I think contests would be more challenging if this feature is disabled for contestants!

→ Reply
»
5 years ago, # |
← Rev. 2   Vote: I like it +2 Vote: I do not like it

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?

→ Reply
»
5 years ago, # |
  Vote: I like it +1 Vote: I do not like it

that is great and fantastic efforts

I am curious about its implementation and its limitations

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Great

→ Reply
»
5 years ago, # |
  Vote: I like it +1 Vote: I do not like it

It's really convenient to correct the error.

→ Reply
»
5 years ago, # |
  Vote: I like it +12 Vote: I do not like it

In fact,this is a good tool.But if people are depend on this without debug by themselves,that will be bad

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

awesome!!

→ Reply
»
5 years ago, # |
  Vote: I like it +43 Vote: I do not like it

Can we choose to turn this off for practice?

→ Reply
  • »
    »
    5 years ago, # ^ |
      Vote: I like it +1 Vote: I do not like it

    Can't you just not click to the ?

    → Reply
    • »
      »
      »
      5 years ago, # ^ |
        Vote: I like it +22 Vote: I do not like it

      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.

      → Reply
    • »
      »
      »
      5 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      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.

      → Reply
  • »
    »
    5 years ago, # ^ |
      Vote: I like it +10 Vote: I do not like it

    While waiting for the feature to be implemented, it's possible to use some userscript or user stylesheet as a workaround.

    .diagnostics-icon {
	display: none !important;
}
    → Reply
»
5 years ago, # |
  Vote: I like it +20 Vote: I do not like it

please add an option to turn it off :(

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

I like it

→ Reply
»
5 years ago, # |
← Rev. 3   Vote: I like it +5 Vote: I do not like it

Deleted. I 'm sorry for my unnecessary comment.

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Very helpful features.Nice work!!!!

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

nice!

→ Reply
»
5 years ago, # |
  Vote: I like it +3 Vote: I do not like it

All we asked for a way to access large testcases for which our code fails! Just kidding, This UI will definitely help a lot! :)

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Wow! Fantastic!

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Great job!!

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

It's very great ,and it will be better to see this feature in contests it will help us find the mistake fast .

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Nice！！！！

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

It’s so good

→ Reply
»
5 years ago, # |
  Vote: I like it +10 Vote: I do not like it

One of the reasons why codeforces is the best platform to practice and master competitive programming. Keep up the good work !

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

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

→ Reply
  • »
    »
    5 years ago, # ^ |
    ← Rev. 3   Vote: I like it 0 Vote: I do not like it

    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.

    → Reply
    • »
      »
      »
      5 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      They give the diagnostic a lot more time to run, it is not infinite time, but it is still a lot more.

      → Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

What about show participiant's place in result table after contest completed in every page.

→ Reply
»
5 years ago, # |
  Vote: I like it 0 Vote: I do not like it

So great!We can save a lot of time debugging!

→ Reply