Lesson 7: C++ toolchain and basics: Performance perspective

Concept Explanation

This lesson introduces performance from a beginner-friendly C++ angle: not micro-optimization, but choosing simple structures that avoid waste and stay safe. You will work with a small example that uses automatic resource management, then look at why that style is usually faster and more reliable than manual allocation patterns. The goal is to notice how ownership, object lifetime, and clean interfaces affect both speed and maintainability. By the end, you should be able to explain why modern C++ prefers RAII-based code and how that choice helps in everyday programs.

Where to Put the Code

1. Start with variables and inputs. Keep includes, main function, and data types explicit.
2. Add processing logic in the middle section.
3. Finish with output and quick validation.

Command Reference

• Compile and run the example, then explain what owns the integer and when it is released.
• Replace the stored value with a second number and confirm that the output changes as expected.
• Compare this RAII-based version with a raw pointer version and note which one is easier to reason about.
• Write down one concrete reason modern C++ code often prefers automatic cleanup over manual delete.

Step-by-step Guide

1. Build the program once and confirm that it prints the stored value correctly.
2. Identify which line creates the resource and which part of the program is responsible for cleanup.
3. Change the value or output text, then run again to verify the edit.
4. Describe in one sentence why std::make_unique is safer than allocating manually for this case.
5. Finish with a short checklist: correct output, clear ownership, and no unnecessary code.

Practice Exercises

• Create a similar example that stores a player's level or a product count instead of a score.
• Write a second version with a helper function that returns a smart pointer and print the result in main.
• Refactor the example so the variable names describe the data more clearly.

Coding Challenges

• Implement both a raw pointer version and a std::unique_ptr version, then compare readability and risk.
• Extend the program so it manages two values and still keeps ownership clear and automatic.

Mini Practice Tasks

• Rename one variable to make its purpose obvious.
• Add one extra print line that confirms the program ran correctly.
• Write a one-line note about how RAII helps performance and safety together.