docs/memory_management.md

# Memory Management

- Avoid using bare pointers for dynamically allocated objects. Prefer `std::unique_ptr`,
  `std::shared_ptr`, or another RAII class such as `BSONObj`.
- If you assign the output of `new/malloc()` directly to a bare pointer you should document where
  it gets deleted/freed, who owns it along the way, and how exception safety is ensured.
SERVER-37414 Move branch-specific docs from GitHub Wiki into repo 2020-02-12 12:21:17 -05:00			`# Memory Management`

SERVER-88970 Added yaml formatting to server repo GitOrigin-RevId: 35db3811d8f749edd5b79ba910adcbc1ceb54cc4 2024-04-03 16:12:53 -07:00			- Avoid using bare pointers for dynamically allocated objects. Prefer `std::unique_ptr`,
			`std::shared_ptr`, or another RAII class such as `BSONObj`.
			- If you assign the output of `new/malloc()` directly to a bare pointer you should document where
			`it gets deleted/freed, who owns it along the way, and how exception safety is ensured.`