The smart_pointers section is too big

Open
  • Is something wrong?
#1,701 2 comments 5 reactions 0 assignees View on GitHub

@theayush07 is already working on this.

Since Oct 7, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
content, documentation

Research direction

Review the smart_pointers exercise references, especially the Smart Pointers and Fearless Concurrency chapters and the Cow documentation linked in the issue. Check how the arc1 exercise is grouped with the threads topics. Done means the reading is less repetitive and appropriately scoped, with arc1 moved if that change is accepted.

Written by the indexing model from the issue text.

Description

A-exercises

When following the exercises, it is nice to check the suggested reading.
For the smart_pointers exercises, it includes a lot of reading:

  • Smart Pointers
    -> the full chapter about Smart Pointers in The Book. It is a big chapter.
  • Using Box to Point to Data on the Heap
    -> Repetition. This is included in the Smart Pointers chapter
  • Rc<T>, the Reference Counted Smart Pointer
    -> Repetition. This is included in the Smart Pointers chapter
  • Shared-State Concurrency
    -> This is included in the chapter Fearless Concurrency in The Book.
    To understand it, it is better to read the full chapter, and it is a Big chapter.
  • Cow Documentation
    -> Advanced topic about Copy-On-Write (actually, Clone-On-Write in Rust), a performance optimization technique, which requires to check other sources (example) to understand well. (This is not actually covered in The Book).

The exercises and reading to do before the Smart Pointers section are quite fast to get through. However, reading the references for 2 full chapters in The Book + researching about the Cow type is more time consuming. So, less engaging.

I would suggest to move the arc1 exercise under the threads topics to not have to read about concurrency yet.

Rustlings v5.6.1

Dominant language
Rust
Stars
64.6k
Forks
11.3k
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/rustlings

All issues in rust-lang/rustlings

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.