Consistently use make_shared, make_unique utilities to avoid potential memory leaks · envoyproxy/envoy#14044 | Good First Issue

(1 评论) (0 反应) (0 负责人)C++ (5,373 fork)batch import

help wantedtech debt

仓库指标

Star: (27,997 star)
PR 合并指标: (平均合并 8天) (30 天内合并 378 个 PR)

描述

Currently in code there is no consistent strategy for creating new objects wrapped into smart pointers. Is it recommended to use make_shared, make_unique utils to gracefully handle exceptions upon object construction: https://en.cppreference.com/w/cpp/memory/shared_ptr/make_shared https://en.cppreference.com/w/cpp/memory/unique_ptr/make_unique

Example of code to be fixed: https://github.com/envoyproxy/envoy/blob/master/test/integration/clusters/custom_static_cluster.cc#L25

贡献者指南

研究方向: 查找代码库中所有原始 'new' 的实例，特别是测试文件，并将其替换为适当的 std::make shared 或 std::make unique。
技术栈: cpp
领域: backend
议题类型: 重构
难度: 1
预计时间: 1 小时以内
活动状态: 活跃
清晰度: 清晰
前置要求: C++smart pointers
新手友好度: 80