BAPCtools
BAPCtools copied to clipboard
Tools for developing ICPC-style programming contest problems.
This issue is for tracking commits related to windows support.
Warn if inline testcases are ignored.
Warn/error whenever non-icpc-spec features are used. Add a `--icpc` command line arg and/or `icpc: true` to `contest.yaml` to validate that the problem adheres to the ICPC subset
See https://clics.ecs.baylor.edu/index.php?title=Problem_format#limits
We could find gaps in testdata by mutation testing the accepted `c++` submissions. Any (most?) mutated solutions should fail.
We could improve the stability of our output validators by fuzz testing them.
Teams should be able to run this is contest mode: - start a contest and write config to a file: #problems, duration of contest - run code on samples, print...
When an AC solution gives WA/TLE, y/n prompt to move it to that directory. Also allow --copy to copy AC solutions to the right directory. This allows fixing them in...
To speed up evals, we could cache `(hash of submission, hash of testcase)` pairs and do a lookup there instead of rerunning the code.
java and kotlin can use more cpu time than user time because they seem to do JIT in separate threads. Pinning them to a single core would prevent that, probably...