Skip to content

doc: add C++20 migration assessment for libModSecurity#40

Open
Easton97-Jens wants to merge 3 commits intov3/masterfrom
codex/evaluate-migration-from-c++17-to-c++20
Open

doc: add C++20 migration assessment for libModSecurity#40
Easton97-Jens wants to merge 3 commits intov3/masterfrom
codex/evaluate-migration-from-c++17-to-c++20

Conversation

@Easton97-Jens
Copy link
Copy Markdown
Owner

Motivation

  • Provide maintainers a rigorous, security-first decision basis for a possible migration from C++17 to C++20 for libModSecurity.
  • Capture repository facts, toolchain/CI realities, ABI/API implications and platform/packaging constraints that make this migration high-risk if done naively.
  • Offer concrete, phased migration strategy with Stop/Go criteria and prioritized next steps so maintainers can proceed incrementally and safely.

Description

  • Add a new German-language assessment file doc/cpp20-migration-assessment.md containing a 14-section analysis covering Executive Summary, repository/toolchain facts, feature-by-feature C++20 evaluation, detailed risk analysis, CI/tooling readiness, performance/security considerations, effort estimates and a phased migration plan.
  • The document includes a C++20 feature matrix (recommend/hold/avoid), concrete refactoring patterns (std::span, std::string_view, std::source_location, targeted constexpr), and 15 prioritized next steps for maintainers.
  • This is a documentation-only change and does not modify source, build scripts or CI configuration; it intentionally separates facts from assumptions and prescribes a conservative, toolchain-driven rollout.

Testing

  • No code-unit/regression/benchmark tests were run because this is a documentation-only change.
  • Presence and contents of the new file were inspected via repository file listing and file-content checks (e.g., nl/sed output) to ensure the assessment was written and placed at doc/cpp20-migration-assessment.md.
  • Further validation (CI builds, sanitizer runs, ABI checks and benchmarks) is recommended before any code changes or C++20 flag switch are merged.

Codex Task

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant