memory-safety-patterns

Ожидаемый результат:

• C: use goto cleanup blocks or explicit create and destroy functions
• C++: use RAII with destructors and smart pointers
• Rust: rely on ownership, borrowing, and Drop semantics

Ожидаемый результат:

• Use unique_ptr when a single owner controls the lifetime
• Use shared_ptr when multiple owners must share the resource
• Prefer unique_ptr with move semantics over shared_ptr when possible

Ожидаемый результат:

• The compiler tracks ownership and enforces single owner by default
• References (borrows) have checked lifetimes
• Memory is freed automatically when the owner goes out of scope