How uynilo9/cpcpp works
Cpcpp is an archive of independent C++ competitive-programming solutions, not a single application. A user or judge supplies a problem-specific input (or invokes a LeetCode method); each solution computes and returns or prints its answer independently. The sampled files show this standalone pattern, while the README and tree establish the platform collections. No shared runtime orchestration or common data store is evident.
Main entry points: atcoder_abc096_c.cpp Grid check · atcoder_abc247_d.cpp Queue queries · atcoder_abc283_d.cpp Scope check · kattis_averageshard.cpp Average split
Components 10
AtCoder
- Grid check
atcoder/atcoder_abc096_c.cpp - Queue queries
atcoder/atcoder_abc247_d.cpp - Scope check
atcoder/atcoder_abc283_d.cpp
Kattis
- Average split
kattis/kattis_averageshard.cpp - Keyboard editor
kattis/kattis_lyklagangriti.cpp
LeetCode
- Roman conversion
leetcode/leetcode_13.cpp - Substring length
leetcode/leetcode_3.cpp
NTOJ
- Grid attack
ntoj/ntoj_1077.cpp - Range damage
ntoj/ntoj_1089.cpp
Other components
- User / judge
Connections 18
- User / judge → Grid check: provides input
- Grid check → User / judge: prints answer
- User / judge → Queue queries: provides input
- Queue queries → User / judge: prints answers
- User / judge → Scope check: provides input
- Scope check → User / judge: prints answer
- User / judge → Average split: provides input
- Average split → User / judge: prints answer
- User / judge → Keyboard editor: provides input
- Keyboard editor → User / judge: prints result
- User / judge → Roman conversion: invokes method
- Roman conversion → User / judge: returns integer
- User / judge → Substring length: invokes method
- Substring length → User / judge: returns length
- User / judge → Grid attack: provides input
- Grid attack → User / judge: prints result
- User / judge → Range damage: provides input
- Range damage → User / judge: prints result