You've already forked rust-tutor
2.3 KiB
2.3 KiB
Learning Progress Log
Setup Phase
Date: 2026-01-12 Activity: Created learning scaffolding and multi-chat system Key Insight: Need structured approach to maintain context across multiple Claude chats
Book Progress
- ✅ Chapters 1-3: Basics, Variables, Functions, Control Flow
- ✅ Chapter 4: Ownership, Borrowing, Slices
- ✅ Chapters 5-6: Structs, Enums, Pattern Matching
- ✅ Chapter 7: Modules
- ✅ Chapter 8: Collections
- ⏳ Chapter 9: Error Handling
Exercise Completion Log
Will be updated as exercises are completed
Milestone 1: Chapters 1-3 (Basics)
- Temperature Converter CLI
- FizzBuzz with Customization
- Base58 Encoder/Decoder (crypto)
Milestone 2: Chapter 4 (Ownership)
- String Manipulator
- Array Analyzer
- Simple Hash Visualizer (crypto)
Milestone 3: Chapters 5-6 (Structs/Enums)
- Library Book System
- Calculator with Result
- Transaction Type Parser (crypto)
Milestone 4: Chapter 7 (Modules) - CURRENT
- Multi-Module Note-Taking CLI
- Calculator Plugin System
- Wallet Module Structure (crypto)
Milestone 5: Chapters 8-9 (Collections, Error Handling)
- Vec Statistics Calculator (Vec, HashMap, basic math) - 2026-01-15
- Contact Manager (HashMap, Option, Result)
- Log Parser (Vec, filtering, file handling)
- Transaction Pool/Mempool (crypto)
Milestone 6: Chapter 10 (Generics, Traits, Lifetimes)
- Generic Cache
- Comparable Trait
- Generic Transaction Validator (crypto)
Post-Book Projects
Simple Wallet Key Generator
- Generate keypair
- Save/load from file
- Sign messages
RPC Client
- Query blockchain state
- Display balances
- Async HTTP, JSON parsing
Reflections
2026-01-15 - Vec Statistics Exercise
Key Learning: Type conversion and ownership struggles are normal! Spent 45min wrestling with usize vs i32 vs f64 for vector length, and dealing with moved values when iterating multiple times. The compiler suggestions led to complex generics at first, but simpler as f64 casting solved the type issues. HashMap frequency counting clicked once the ownership issues were resolved. Insight: "Terrible but working" code is a valid first step - iterate to clean it up.
This file tracks overall learning journey and milestone completion