-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Enhanced Support for "Hack-Like Problems" with Non-WA Verdicts #38
Comments
My current thought is to add an option to run a judge-provided program as the last stage, and a "hack wrapper" option that does the following things:
|
This seems unnecessary, as output format validation can already be handled within the special judge program. Adding this feature may bring some potential issues, especially when validation is time-consuming. In such cases, the judge-provided program's time limit will become less. The other proposed design ideas sound excellent! |
Oh so in that case the special judge will need to validate the output after the first stage, and do a manual comparison to determine AC after the second stage? |
Yes, this is a more reasonable process in my opinion. |
For problems where the goal is to "provide the original problem and a fake solution, and try to construct a test case to make it fail," it's straightforward to include both the correct and fake solutions in the checker to achieve "Wrong Answer (WA) Hacking" behavior, as demonstrated in this example.
However, if the expected verdicts are TLE, RE, or other non-WA results, implementing this requires unconventional workarounds, such as using
clock()
(as in this example) ortry
statements. Currently, there seems to be no standardized way to handle this.Since there is a "Custom Summary" feature, adding an option to "run the judge's program only" and detect its verdict directly could simplify the process. A possible approach might be to use the "Number of Execution Stages" feature, one can place the judge’s program in the second stage since the input is the output from the first stage.
The text was updated successfully, but these errors were encountered: