Skip to content

Feature Request: Enhanced Support for "Hack-Like Problems" with Non-WA Verdicts #38

@baluteshih

Description

@baluteshih

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) or try 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions