Skip to content
CP4CPP/cpp.root:cpp #cpp_contest_c_reference#role
Theme

cpp - Contest C++ Reference

Role

cp4cpp.com/cpp is the Contest C++ Reference.

It exists for quick, correct, readable lookup of C++ syntax, STL, idioms, and contest-relevant language behavior.

cppreference previewcppreference preview

Purpose

  • Look up syntax, idioms, and STL use cases quickly and reliably.
  • Notice typical features and common mistakes in C++11, C++14, C++17, and C++20.
  • Keep contest-useful C++ knowledge filtered, version-aware, and easier to digest.

Lineage

ProjectMeaningTimeForm
CCCC++ Coding ConventionDec 2023HackMD
CC4CCC++ Completionist For Competitive CodingJan 2020Discord
SIMPStandard Implementation Module PracticesMar 2024Discord

References

ShortProjectUse
C++REFcppreferenceAuthoritative C++ language and library reference.
C++COMcplusplusBeginner-friendly tutorials, reference, articles, and forum hub.
C++ISOStandard C++ FoundationModern C++ standard community and guidance.
GODBOLTCompiler ExplorerCompiler behavior, flags, generated code, and quick experiments.
DEVDOCSDevDocs C++Fast documentation browser with offline support.
LEARNCPPLearn C++Structured modern C++ fundamentals and good practices.
HACKCPPHacking C++Concise visual C++ guides and cheat sheets.
CODEFUNBí Kíp Luyện RồngVietnamese C++ learning hub.

Learning Style

Root-like learning: users learn foundational prerequisite material in any order, as shared primitives used by other navigations.

Strengths To Preserve

  • C++ lookups help learners who are unfamiliar with syntax, structure, idioms, and standard library features.
  • Contest learners need fast STL, syntax, and idiom reminders.
  • Advanced learners still need completeness checks and version-specific reminders.

Weaknesses To Fix

  • Common STL traps stay scattered across blogs, notes, and editorials.
  • Version changes matter, but explanations are often split across unrelated sources.

CP4CPP Rules

  • Keep cpp filtered, version-aware, and focused on contest use.
  • Group duplicated pages by use case and characteristic when that improves lookup.
  • Only separate contest-relevant options for C++11, C++14, C++17, and C++20.
  • Prefer verified standard documentation and clearly cited first-hand references.