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