Nice Feature.
It will be helpful for beginners to understand their mistake.
Cool feature, but I doubt if it works for some problems. Anyways, People will now stop spamming discussion forums when they get \text{WA} verdicts.
Edit: I tried to find a test case for which a solution fails a long time ago. Here’s the link: BURGER - Editorial - #22 by suman_18733097
I couldn’t find it even after a stress test for about 5 minutes. Your feature got it in 10 seconds
. Awesome work
.
This should always be free. Codeforces provide quality materials completely for free. Such platforms are a community where everyone helps each other, not some money-making machine. They have sponsors and even if they fall short then they can open a donation box where everyone can contribute.
That is one cool feature ![]()
![]()
Nice Feature,
It will save a lot of time,
but there is a bad or negative thing also such as participants may not think deeply about that problem if they get the expected output of that problem.
Cool Feature !!
But we need it for free
Yes
Much awaited feature ![]()
Thanks Chef
Good for newbies while struggling for finding testcase.
Running something for free is not always a feasible option. In the end, there are a lot of people working to run the platform who should be paid for their work.
Not working for recent contest problem.
UPD: CodeChef: Practical coding for everyone
Please help me with this. Feature can’t find a testcase where the solution fails , neither can I. If that’s not the case I think solution should be correct.
Consider this test case:
STDIN
1
9 2
8 6
8 2
Expected Output
7
4
Your Output
7
2
Nice Feature, this would be very much helpful.
There was an issue with the test case finder. It is fixed now. You can try again.
Actually thats a really good feature
… because till now we never knew where we are failing and giving a test case to check our corner cases would be great … and the best part we won’t be given a full testcase that requires a lot of time , but the case where it gave WA… nice ![]()
Bestest update till now, appreciable feature. ![]()
Hey guys, wouldnt this make competitive programming a pay to win?![]()
I feel they should limit the number of times one can use this feature in a month. Say, around 20 free debugs and then charge based on the usage
.