원클릭으로 Manus에서 모든 스킬 실행

m01-ownership

스타14

포크3

업데이트2026년 1월 25일 07:37

Mastering C++ Ownership: Move Semantics, RAII, and Reference Safety. Triggers: std::move, use-after-free, double-free, dangling pointer, copy elision, RVO, reference qualifiers.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

13eholder

13eholder/Modern-Cpp-Skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

C++ Ownership (Move Semantics & RAII)

Core Question

Who owns this resource, and does it need to move?

In C++, ownership is a discipline, not just a compiler check. You must decide:

Scope-bound? Use Stack (RAII).
Exclusive? Use std::unique_ptr.
Shared? Use std::shared_ptr.
View? Use T* or T& (non-owning).

Error → Design Question

Compiler/Sanitizer Error	Design Question
Double Free	Who owns this? Did you copy a raw pointer?
Use After Free	Did a reference outlive its owner?
Memory Leak	Where is the destructor called? (Did you use `new`?)
Object slicing	Why are you passing by value instead of pointer/reference?
Moved-from usage	Why are you touching a variable after `std::move`?

Thinking Prompt

Does it need a heap allocation?
- No? → Stack value (Rule of Zero).
- Yes? → std::unique_ptr (Rule of Zero).
- DO NOT write a destructor unless managing a non-RAII C handle.
Is it a Transfer or a Copy?
- Transfer? → std::move.
- Copy? → Copy Constructor (or clone() pattern if polymorphic).
Is this a View?
- Yes? → std::string_view, std::span, or const T&.
- Never pass std::shared_ptr unless transferring shared ownership.

Trace Up / Down

Trace Up (Diagnosing):
- Error: "Segfault / Heap Corruption"
- Ask: Is there a raw pointer (T*) managing a resource?
- Fix: Wrap in unique_ptr or vector.
Trace Down (Implementing):
- Intent: "I want to pass this big object to a function and never see it again."
- Code: void consume(BigThing t); called with consume(std::move(thing));

Quick Reference

Pattern	Cost	Use When
Value (Stack)	Zero	Default choice. Small/Medium objects.
`unique_ptr`	Zero	Heap needed. Exclusive ownership.
`shared_ptr`	Atomic Inc/Dec	Cyclic graph or true shared ownership.
`T&` (Ref)	Zero	Parameter passing (non-null).
*`T` (Ptr)**	Zero	Parameter passing (nullable).
`std::move`	Zero	Transferring ownership.

이 저장소의 다른 Skills

같은 저장소

cpp20-skill-creator

13eholder/Modern-Cpp-Skills

Use when creating skills for C++20 standard library features, language constructs, remote third-party libraries, or local C++ projects. Keywords: create C++20 skill, create std skill C++, create concept skill, create local C++ skill, 创建 C++20 skill, 创建标准库技能, 创建 concept 技能, 本地库生成 skill, 动态 C++ skill, skill for ranges, skill for coroutines, skill for concepts, generate C++ skill from local path, C++20 技能, 从文档创建 skill, from docs create C++ skill

2026-02-1414

m02-resource

13eholder/Modern-Cpp-Skills

Mastering C++ Smart Pointers: unique_ptr, shared_ptr, weak_ptr. Triggers: memory management, cycles, enable_shared_from_this, make_unique, make_shared, custom deleters.

2026-01-2514

m03-mutability

13eholder/Modern-Cpp-Skills

Mastering C++ Const Correctness and Mutability. Triggers: const, mutable, logically const, bitwise const, data race, mutex, shared_mutex, thread safety.

2026-01-2514

m04-zero-cost

13eholder/Modern-Cpp-Skills

Mastering C++ Polymorphism: Templates, Concepts, and Virtual Functions. Triggers: templates, concepts, vtable, CRTP, static polymorphism, dynamic polymorphism, SFINAE.

2026-01-2514

m05-type-driven

13eholder/Modern-Cpp-Skills

Mastering C++ Type-Driven Design. Triggers: strong types, phantom types, type state pattern, builder pattern, invalid state unrepresentable.

2026-01-2514

m06-error-handling

13eholder/Modern-Cpp-Skills

Mastering C++ Error Handling. Triggers: exceptions, try-catch, noexcept, std::expected, std::optional, error codes, assert, terminate.

2026-01-2514

name	m01-ownership
description	Mastering C++ Ownership: Move Semantics, RAII, and Reference Safety. Triggers: std::move, use-after-free, double-free, dangling pointer, copy elision, RVO, reference qualifiers.

C++ Ownership (Move Semantics & RAII)

Core Question

Who owns this resource, and does it need to move?

In C++, ownership is a discipline, not just a compiler check. You must decide:

Scope-bound? Use Stack (RAII).
Exclusive? Use std::unique_ptr.
Shared? Use std::shared_ptr.
View? Use T* or T& (non-owning).

Error → Design Question

Compiler/Sanitizer Error	Design Question
Double Free	Who owns this? Did you copy a raw pointer?
Use After Free	Did a reference outlive its owner?
Memory Leak	Where is the destructor called? (Did you use `new`?)
Object slicing	Why are you passing by value instead of pointer/reference?
Moved-from usage	Why are you touching a variable after `std::move`?

Thinking Prompt

Does it need a heap allocation?
- No? → Stack value (Rule of Zero).
- Yes? → std::unique_ptr (Rule of Zero).
- DO NOT write a destructor unless managing a non-RAII C handle.
Is it a Transfer or a Copy?
- Transfer? → std::move.
- Copy? → Copy Constructor (or clone() pattern if polymorphic).
Is this a View?
- Yes? → std::string_view, std::span, or const T&.
- Never pass std::shared_ptr unless transferring shared ownership.

Trace Up / Down

Trace Up (Diagnosing):
- Error: "Segfault / Heap Corruption"
- Ask: Is there a raw pointer (T*) managing a resource?
- Fix: Wrap in unique_ptr or vector.
Trace Down (Implementing):
- Intent: "I want to pass this big object to a function and never see it again."
- Code: void consume(BigThing t); called with consume(std::move(thing));

Quick Reference

Pattern	Cost	Use When
Value (Stack)	Zero	Default choice. Small/Medium objects.
`unique_ptr`	Zero	Heap needed. Exclusive ownership.
`shared_ptr`	Atomic Inc/Dec	Cyclic graph or true shared ownership.
`T&` (Ref)	Zero	Parameter passing (non-null).
*`T` (Ptr)**	Zero	Parameter passing (nullable).
`std::move`	Zero	Transferring ownership.