How princek0/learning-cpp works
Project type and purpose
• This is not a service or full‑stack app but a code‑sample repository (“Learning-CPP”) containing:
• A simple “Hello World” program
• Solutions to competitive/programming‑challenge problems from CSES, LeetCode, Project Euler
• Its goal is to organize and version these C++ examples, not to run as a unified system.
File structure
• Top‑level:
• Other/ — misc or demo code (HelloWorld.cpp)
• Problems/ — all challenge solutions, further grouped
• README.md — repo description
• Under Problems/:
• .vscode/ — IDE launch and build configs
• CSES/ — subfolder “Introductory Problems” with .cpp and compiled .exe
• Leetcode/ — individual .cpp files
• Project Euler/ — .cpp, .exe and .vscode config
• Each .cpp is compiled (e.g., via g++ or VS) into a .exe.
README for additional insights
• Confirms: “Random C++ projects/solutions to problems/implementations.”
• No runtime or server components—just source → compile → binary.
a. Main components
1. Developer Environment
• Editor/IDE (.vscode)
• C++ Compiler Toolchain (g++, clang++, MSVC)
2. Source Tree
• Other Module (HelloWorld)
• Problems Module
• CSES
• LeetCode
• Project Euler
3. Build Artifacts
• Executable binaries (.exe)
b. Relationships and data flow
• Dev edits .cpp in VS Code → invokes compiler → outputs .exe
• Organizing folders group by source domain (CSES, etc.)
c. Architectural patterns / principles
• Separation of concerns by problem category
• Convention over configuration: each problem’s naming is self‑descriptive
• Minimal “build pipeline” per folder (via .vscode tasks)
d. Relevant technologies
• C++17/20 standard
• VS Code tasks and launch configurations
• g++ / MSVC command‑line arguments