Pressure Scenario: When to Use unwrap()
Skill Under Test
m06-error-handling
User Question
"When is it okay to use .unwrap() in Rust?"
Expected Behavior
- Explain unwrap() semantics (panic on None/Err)
- List acceptable use cases (tests, examples, guaranteed values)
- Explain alternatives (?, expect, unwrap_or, match)
- Quick reference for error handling patterns
- Reference to G.ERR.01, P.ERR.02 guidelines
Baseline Test (without skill)
Date: [To be filled]
Result:
- Semantics explanation: [PASS/FAIL]
- Use case list: [PASS/FAIL]
- Alternatives: [PASS/FAIL]
- Quick reference: [PASS/FAIL]
- Guidelines: [PASS/FAIL]
Notes: [To be filled after test]
Post-Skill Test
Date: [To be filled]
Result:
- Semantics explanation: [PASS/FAIL]
- Use case list: [PASS/FAIL]
- Alternatives: [PASS/FAIL]
- Quick reference: [PASS/FAIL]
- Guidelines: [PASS/FAIL]
Notes: [To be filled after test]
Edge Cases
- "My code will never have None" → Should encourage defensive coding
- "unwrap vs expect?" → Should explain expect's documentation value
- "What about unwrap_or_default?" → Should explain lazy evaluation
你可能感兴趣的文章
Agent Integration Test Scenarios
Ownership (m01) Test Scenarios