envoyproxy/envoy

Support some extensions from C++20 in Windows CI

Open

#18,489 opened on Oct 6, 2021

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/buildarea/windowsenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Google style permits designated initializers from C++20. MSVC is strict about C++17. The request is to allow Google style code in Windows CI even if it's not fully compliant with C++17. An option is to use C++20 in MSVC.

Contributor guide

Research direction
Evaluate switching MSVC to C++20 in Windows CI to allow designated initializers. Check current C++ standard used and any other C++20 features that might cause issues.
Tech stack
ccpp
Domain
backendci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++ build configurationWindows CI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80