Book Code for Competitive Programming
Translation pending
EducationC++ · PythonGitHub @ecnerwalaSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗This is my library of reference code for competitive programming. The goal is to write generic, fast, and clean algorithm implementations for use in contests like CodeForces or ICPC.
The library lives in src/ as standalone headers organized by area
(#include "fft/series.hpp", #include "ds/seg_tree.hpp", compiled with
-I src), all inside namespace wala. The library requires C++23 (the whole toolchain
builds with -std=c++23, e.g. g++ >= 13). Browsable source, verification
results, and coverage are hosted at https://ecnerwala.github.io/cp-book/.
cmake -B build && cmake --build build
ctest --test-dir build # or ./build/tests
Unfortunately, some files (e.g. full power series with all fft engines) are too long to fit in CF's submission limit, so we need to bundle/minify them for submission.
scripts/bundle.py verify/fft/convolution_mod.test.cpp > submission.cpp
scripts/bundle.py fft/series.hpp ds/seg_tree.hpp # bundle headers together
scripts/bundle.py --minify fft/series.hpp # compiler-directed minification
scripts/bundle.py --all # pregenerate all headers
The script runs in the repo's uv project
(pyproject.toml / uv.lock, which pin competitive-verifier). To run it
offline, first populate the environment with
uv sync
Then, you can run
UV_OFFLINE=1 scripts/bundle.py ...
uv run --offline scripts/bundle.py ...
Bump the pinned competitive-verifier by editing rev in pyproject.toml
and running
uv lock --upgrade-package competitive-verifier
verify/ holds Library Checker solutions,
verified in CI with
competitive-verifier.
# Run verification locally
uv run competitive-verifier oj-resolve --include src verify --exclude third_party \
--config .competitive-verifier/config.toml > verify_files.json
uv run competitive-verifier verify --verify-json verify_files.json
contest/ holds standalone tooling for contests: a problem-directory
template (Makefile with sanitizers and precompiled headers), a layered
.template instantiator (make_prob.py), and a
Competitive Companion
listener (download_prob.py). See contest/README.md.
Contest programs are standalone; vendor book code in as needed (e.g. with
scripts/bundle.py).
All code is written by me and CC0 licensed unless otherwise noted in the file. Inspiration is largely drawn from KACTL and other references.