メニュー
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 ページを確認してインストールできます。
SOC 職業分類に基づく
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
Mastering C++ Smart Pointers: unique_ptr, shared_ptr, weak_ptr. Triggers: memory management, cycles, enable_shared_from_this, make_unique, make_shared, custom deleters.
Mastering C++ Const Correctness and Mutability. Triggers: const, mutable, logically const, bitwise const, data race, mutex, shared_mutex, thread safety.
Mastering C++ Polymorphism: Templates, Concepts, and Virtual Functions. Triggers: templates, concepts, vtable, CRTP, static polymorphism, dynamic polymorphism, SFINAE.
Mastering C++ Type-Driven Design. Triggers: strong types, phantom types, type state pattern, builder pattern, invalid state unrepresentable.
Mastering C++ Error Handling. Triggers: exceptions, try-catch, noexcept, std::expected, std::optional, error codes, assert, terminate.
| 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. |
Who owns this resource, and does it need to move?
In C++, ownership is a discipline, not just a compiler check. You must decide:
std::unique_ptr.std::shared_ptr.T* or T& (non-owning).| 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? |
Does it need a heap allocation?
std::unique_ptr (Rule of Zero).Is it a Transfer or a Copy?
std::move.clone() pattern if polymorphic).Is this a View?
std::string_view, std::span, or const T&.std::shared_ptr unless transferring shared ownership.Trace Up (Diagnosing):
T*) managing a resource?unique_ptr or vector.Trace Down (Implementing):
void consume(BigThing t); called with consume(std::move(thing));| 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. |