gavin/developer-roadmap
1
0
Fork 0
mirror of https://github.com/kamranahmedse/developer-roadmap.git synced 2026-03-12 17:51:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fixed formatting for references comparison table (#9540)

Browse Source 
The formatting is unclear and messy initially, modified as a table instead for clarity.
This commit is contained in:
Kyle Nguyen
2026-01-14 07:28:17 -07:00
committed by GitHub
parent d27425175c
commit 38670635ce
1 changed files with 7 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
src/data/roadmaps/cpp/content/references@uUzRKa9wGzdUwwmAg3FWr.md
View File

@@ -69,57 +69,13 @@ When iterating over containers such as `std::vector<std::string>`, the choice of
### Comparison
Loop style
| Loop style | Copies made? | Can modify element? | Efficiency | Typical use case |
|---------------------|--------------|---------------------|------------------------------------|------------------------------------------|
| `auto str` | ✅ Yes | ✅ Only the copy | Less efficient for large objects | When you need a local, mutable copy |
| `auto const &str` | ❌ No | ❌ Read-only | Most efficient for read-only use | Safely read elements without copying |
| `auto &str` | ❌ No | ✅ Modifies original | Efficient, mutates container | Modify elements in place |
| `const auto str` | ✅ Yes | ❌ Read-only | Less efficient for large objects | Explicit read-only copy |
Copies made?
Can modify element?
Efficiency
Typical Use Case
`auto str`
✅ Yes
✅ Only the copy
Less efficient for large objects
When you need a local, mutable copy
`auto const &str`
❌ No
❌ Read-only
Most efficient for read-only use
Safely read elements without copying
`auto &str`
❌ No
✅ Modifies original
Efficient, mutates container
Modify elements in place
`const auto str`
✅ Yes
❌ Read-only
Less efficient for large objects
Explicit read-only copy
* * *
Example: Why `const auto str` Can Be Useful
-------------------------------------------
@@ -156,4 +112,4 @@ Performance Notes
* For **large objects** like `std::string`, `std::vector`, or custom classes, prefer **`auto const &`** to avoid unnecessary copies.
* For **small, cheap-to-copy types** like `int`, `char`, or `bool`, using `auto` or `const auto` is fine and often simpler.
* `auto &` should only be used when you _intend_ to modify the elements in place, since it directly mutates the container.
* `auto &` should only be used when you _intend_ to modify the elements in place, since it directly mutates the container.