diff --git a/po/zh-CN.po b/po/zh-CN.po index d0f700527a8..8f8710c03fa 100644 --- a/po/zh-CN.po +++ b/po/zh-CN.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: Comprehensive Rust 🦀\n" -"POT-Creation-Date: 2023-10-06T12:36:03-07:00\n" +"POT-Creation-Date: 2024-01-05T12:50:57-08:00\n" "PO-Revision-Date: 2023-10-21 15:02+0800\n" "Last-Translator: \n" "Language-Team: Language zh-Hans\n" @@ -12,7 +12,7 @@ msgstr "" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Poedit 3.4\n" -#: src/SUMMARY.md:4 src/index.md:1 +#: src/SUMMARY.md:3 src/index.md:1 msgid "Welcome to Comprehensive Rust 🦀" msgstr "欢迎来到 Comprehensive Rust 🦀" @@ -48,992 +48,1213 @@ msgstr "代码示例" msgid "Running Cargo Locally" msgstr "在本地运行 Cargo" -#: src/SUMMARY.md:15 +#: src/SUMMARY.md:16 msgid "Day 1: Morning" msgstr "第一天：早上" -#: src/SUMMARY.md:19 src/SUMMARY.md:80 src/SUMMARY.md:135 src/SUMMARY.md:193 -#: src/SUMMARY.md:219 src/SUMMARY.md:269 +#: src/SUMMARY.md:18 src/SUMMARY.md:44 src/SUMMARY.md:70 src/SUMMARY.md:93 +#: src/SUMMARY.md:119 src/SUMMARY.md:138 src/SUMMARY.md:158 src/SUMMARY.md:184 +#: src/SUMMARY.md:207 src/SUMMARY.md:244 src/SUMMARY.md:286 src/SUMMARY.md:337 msgid "Welcome" msgstr "欢迎" -#: src/SUMMARY.md:20 src/welcome-day-1/what-is-rust.md:1 +#: src/SUMMARY.md:19 src/SUMMARY.md:21 src/hello-world.md:1 +#: src/hello-world/hello-world.md:1 +#, fuzzy +msgid "Hello, World" +msgstr "Hello World!" + +#: src/SUMMARY.md:20 src/hello-world/what-is-rust.md:1 msgid "What is Rust?" msgstr "什么是 Rust？" -#: src/SUMMARY.md:21 src/hello-world.md:1 -msgid "Hello World!" -msgstr "Hello World!" +#: src/SUMMARY.md:22 src/hello-world/benefits.md:1 +msgid "Benefits of Rust" +msgstr "" -#: src/SUMMARY.md:22 src/hello-world/small-example.md:1 -msgid "Small Example" -msgstr "简短示例" +#: src/SUMMARY.md:23 src/hello-world/playground.md:1 +msgid "Playground" +msgstr "" -#: src/SUMMARY.md:23 src/why-rust.md:1 -msgid "Why Rust?" -msgstr "为什么选择 Rust？" +#: src/SUMMARY.md:24 src/types-and-values.md:1 +msgid "Types and Values" +msgstr "" -#: src/SUMMARY.md:24 src/why-rust/an-example-in-c.md:1 src/credits.md:32 -msgid "An Example in C" -msgstr "C语言示例" +#: src/SUMMARY.md:25 src/types-and-values/variables.md:1 +msgid "Variables" +msgstr "变量" -#: src/SUMMARY.md:25 src/why-rust/compile-time.md:1 -msgid "Compile Time Guarantees" -msgstr "编译期保障" +#: src/SUMMARY.md:26 src/types-and-values/values.md:1 +msgid "Values" +msgstr "" -#: src/SUMMARY.md:26 src/why-rust/runtime.md:1 -msgid "Runtime Guarantees" -msgstr "运行时保障" +#: src/SUMMARY.md:27 src/types-and-values/arithmetic.md:1 +msgid "Arithmetic" +msgstr "" -#: src/SUMMARY.md:27 src/why-rust/modern.md:1 -msgid "Modern Features" -msgstr "现代特性" +#: src/SUMMARY.md:28 src/types-and-values/strings.md:1 +msgid "Strings" +msgstr "字符串" -#: src/SUMMARY.md:28 src/basic-syntax.md:1 -msgid "Basic Syntax" -msgstr "基本语法" +#: src/SUMMARY.md:29 src/types-and-values/inference.md:1 +msgid "Type Inference" +msgstr "类型推导" -#: src/SUMMARY.md:29 src/basic-syntax/scalar-types.md:1 -msgid "Scalar Types" -msgstr "标量类型" +#: src/SUMMARY.md:30 src/types-and-values/exercise.md:1 +msgid "Exercise: Fibonacci" +msgstr "" + +#: src/SUMMARY.md:31 src/SUMMARY.md:40 src/SUMMARY.md:51 src/SUMMARY.md:56 +#: src/SUMMARY.md:64 src/SUMMARY.md:75 src/SUMMARY.md:82 src/SUMMARY.md:89 +#: src/SUMMARY.md:103 src/SUMMARY.md:113 src/SUMMARY.md:129 src/SUMMARY.md:134 +#: src/SUMMARY.md:144 src/SUMMARY.md:152 src/SUMMARY.md:164 src/SUMMARY.md:171 +#: src/SUMMARY.md:180 src/SUMMARY.md:192 src/SUMMARY.md:201 +#: src/types-and-values/solution.md:1 src/control-flow-basics/solution.md:1 +#: src/tuples-and-arrays/solution.md:1 src/references/solution.md:1 +#: src/user-defined-types/solution.md:1 src/pattern-matching/solution.md:1 +#: src/methods-and-traits/solution.md:1 src/generics/solution.md:1 +#: src/std-types/solution.md:1 src/std-traits/solution.md:1 +#: src/memory-management/solution.md:1 src/smart-pointers/solution.md:1 +#: src/borrowing/solution.md:1 src/slices-and-lifetimes/solution.md:1 +#: src/iterators/solution.md:1 src/modules/solution.md:1 +#: src/testing/solution.md:1 src/error-handling/solution.md:1 +#: src/unsafe-rust/solution.md:1 +#, fuzzy +msgid "Solution" +msgstr "解答" -#: src/SUMMARY.md:30 src/basic-syntax/compound-types.md:1 -msgid "Compound Types" -msgstr "复合类型" +#: src/SUMMARY.md:32 src/control-flow-basics.md:1 +#, fuzzy +msgid "Control Flow Basics" +msgstr "控制流" -#: src/SUMMARY.md:31 src/basic-syntax/references.md:1 -msgid "References" -msgstr "引用" +#: src/SUMMARY.md:33 src/control-flow-basics/conditionals.md:1 +msgid "Conditionals" +msgstr "" -#: src/SUMMARY.md:32 src/basic-syntax/references-dangling.md:1 -msgid "Dangling References" -msgstr "悬垂引用" +#: src/SUMMARY.md:34 src/control-flow-basics/loops.md:1 +#, fuzzy +msgid "Loops" +msgstr "“for”循环" -#: src/SUMMARY.md:33 src/basic-syntax/slices.md:1 -msgid "Slices" -msgstr "切片" +#: src/SUMMARY.md:35 src/control-flow-basics/break-continue.md:1 +msgid "`break` and `continue`" +msgstr "`break` 和 `continue`" -#: src/SUMMARY.md:34 -msgid "String vs str" -msgstr "String vs str" +#: src/SUMMARY.md:36 src/control-flow-basics/blocks-and-scopes.md:1 +msgid "Blocks and Scopes" +msgstr "" -#: src/SUMMARY.md:35 src/basic-syntax/functions.md:1 +#: src/SUMMARY.md:37 src/control-flow-basics/functions.md:1 msgid "Functions" msgstr "函数" -#: src/SUMMARY.md:36 src/basic-syntax/rustdoc.md:1 -msgid "Rustdoc" -msgstr "Rustdoc" - -#: src/SUMMARY.md:37 src/SUMMARY.md:103 src/basic-syntax/methods.md:1 -#: src/methods.md:1 -msgid "Methods" -msgstr "方法" - -#: src/SUMMARY.md:38 -msgid "Overloading" -msgstr "重载" - -#: src/SUMMARY.md:39 src/SUMMARY.md:72 src/SUMMARY.md:106 src/SUMMARY.md:126 -#: src/SUMMARY.md:155 src/SUMMARY.md:185 src/SUMMARY.md:212 src/SUMMARY.md:233 -#: src/SUMMARY.md:261 src/SUMMARY.md:283 src/SUMMARY.md:304 -#: src/exercises/android/morning.md:1 src/exercises/bare-metal/morning.md:1 -#: src/exercises/bare-metal/afternoon.md:1 -#: src/exercises/concurrency/morning.md:1 -#: src/exercises/concurrency/afternoon.md:1 -msgid "Exercises" -msgstr "习题" - -#: src/SUMMARY.md:40 src/exercises/day-1/implicit-conversions.md:1 -msgid "Implicit Conversions" -msgstr "隐式类型转换" +#: src/SUMMARY.md:38 src/control-flow-basics/macros.md:1 +msgid "Macros" +msgstr "" -#: src/SUMMARY.md:41 -msgid "Arrays and for Loops" -msgstr "数组与 for 循环" +#: src/SUMMARY.md:39 src/control-flow-basics/exercise.md:1 +msgid "Exercise: Collatz Sequence" +msgstr "" -#: src/SUMMARY.md:43 +#: src/SUMMARY.md:42 msgid "Day 1: Afternoon" msgstr "第一天：下午" -#: src/SUMMARY.md:45 src/SUMMARY.md:296 src/control-flow.md:1 -msgid "Control Flow" -msgstr "控制流" +#: src/SUMMARY.md:45 src/SUMMARY.md:46 src/tuples-and-arrays.md:1 +#: src/tuples-and-arrays/tuples-and-arrays.md:1 +msgid "Tuples and Arrays" +msgstr "" -#: src/SUMMARY.md:46 src/control-flow/blocks.md:1 -msgid "Blocks" -msgstr "块" +#: src/SUMMARY.md:47 src/tuples-and-arrays/iteration.md:1 +#, fuzzy +msgid "Array Iteration" +msgstr "迭代器" -#: src/SUMMARY.md:47 -msgid "if expressions" -msgstr "if 表达式" +#: src/SUMMARY.md:48 src/SUMMARY.md:71 src/tuples-and-arrays/match.md:1 +#: src/pattern-matching.md:1 +msgid "Pattern Matching" +msgstr "模式匹配" -#: src/SUMMARY.md:48 -msgid "for expressions" -msgstr "for 表达式" +#: src/SUMMARY.md:49 src/SUMMARY.md:72 src/tuples-and-arrays/destructuring.md:1 +#: src/pattern-matching/destructuring.md:1 +#, fuzzy +msgid "Destructuring" +msgstr "解构枚举" -#: src/SUMMARY.md:49 -msgid "while expressions" -msgstr "while 表达式" +#: src/SUMMARY.md:50 src/tuples-and-arrays/exercise.md:1 +msgid "Exercise: Nested Arrays" +msgstr "" -#: src/SUMMARY.md:50 -msgid "break & continue" -msgstr "break & continue" +#: src/SUMMARY.md:52 src/references.md:1 +msgid "References" +msgstr "引用" -#: src/SUMMARY.md:51 -msgid "loop expressions" -msgstr "loop 表达式" +#: src/SUMMARY.md:53 src/references/shared.md:1 +#, fuzzy +msgid "Shared References" +msgstr "引用" -#: src/SUMMARY.md:53 src/basic-syntax/variables.md:1 -msgid "Variables" -msgstr "变量" +#: src/SUMMARY.md:54 src/references/exclusive.md:1 +#, fuzzy +msgid "Exclusive References" +msgstr "悬垂引用" -#: src/SUMMARY.md:54 src/basic-syntax/type-inference.md:1 -msgid "Type Inference" -msgstr "类型推导" +#: src/SUMMARY.md:55 src/references/exercise.md:1 +msgid "Exercise: Geometry" +msgstr "" -#: src/SUMMARY.md:55 -msgid "static & const" -msgstr "静态变量与常量" +#: src/SUMMARY.md:57 src/user-defined-types.md:1 +msgid "User-Defined Types" +msgstr "" -#: src/SUMMARY.md:56 src/basic-syntax/scopes-shadowing.md:1 -msgid "Scopes and Shadowing" -msgstr "作用域和遮蔽（Shadowing）" +#: src/SUMMARY.md:58 src/user-defined-types/named-structs.md:1 +#, fuzzy +msgid "Named Structs" +msgstr "结构体" -#: src/SUMMARY.md:57 src/enums.md:1 +#: src/SUMMARY.md:59 src/user-defined-types/tuple-structs.md:5 +msgid "Tuple Structs" +msgstr "元组结构体" + +#: src/SUMMARY.md:60 src/user-defined-types/enums.md:1 +#: src/pattern-matching/destructuring.md:24 +#: src/pattern-matching/destructuring.md:66 msgid "Enums" msgstr "枚举" -#: src/SUMMARY.md:58 src/enums/variant-payloads.md:1 -msgid "Variant Payloads" -msgstr "变体载荷" - -#: src/SUMMARY.md:59 src/enums/sizes.md:1 -msgid "Enum Sizes" -msgstr "枚举大小" - -#: src/SUMMARY.md:61 src/control-flow/novel.md:1 -msgid "Novel Control Flow" -msgstr "新式控制流" - -#: src/SUMMARY.md:62 -msgid "if let expressions" -msgstr "if let 表达式" - -#: src/SUMMARY.md:63 -msgid "while let expressions" -msgstr "while let 表达式" +#: src/SUMMARY.md:61 src/user-defined-types/static-and-const.md:1 +#, fuzzy +msgid "Static and Const" +msgstr "静态变量与常量" -#: src/SUMMARY.md:64 -msgid "match expressions" -msgstr "match 表达式" +#: src/SUMMARY.md:62 src/user-defined-types/aliases.md:1 +msgid "Type Aliases" +msgstr "" -#: src/SUMMARY.md:66 src/SUMMARY.md:74 src/pattern-matching.md:1 -msgid "Pattern Matching" -msgstr "模式匹配" +#: src/SUMMARY.md:63 src/user-defined-types/exercise.md:1 +msgid "Exercise: Elevator Events" +msgstr "" -#: src/SUMMARY.md:67 src/pattern-matching/destructuring-enums.md:1 -msgid "Destructuring Enums" -msgstr "解构枚举" +#: src/SUMMARY.md:68 +msgid "Day 2: Morning" +msgstr "第二天：上午" -#: src/SUMMARY.md:68 src/pattern-matching/destructuring-structs.md:1 -msgid "Destructuring Structs" -msgstr "解构结构体" +#: src/SUMMARY.md:73 src/pattern-matching/let-control-flow.md:1 +#, fuzzy +msgid "Let Control Flow" +msgstr "控制流" -#: src/SUMMARY.md:69 src/pattern-matching/destructuring-arrays.md:1 -msgid "Destructuring Arrays" -msgstr "解构数组" +#: src/SUMMARY.md:74 src/pattern-matching/exercise.md:1 +msgid "Exercise: Expression Evaluation" +msgstr "" -#: src/SUMMARY.md:70 src/pattern-matching/match-guards.md:1 -msgid "Match Guards" -msgstr "匹配守卫" +#: src/SUMMARY.md:76 src/methods-and-traits.md:1 +#, fuzzy +msgid "Methods and Traits" +msgstr "读取和写入" -#: src/SUMMARY.md:73 src/exercises/day-1/luhn.md:1 -#: src/exercises/day-1/solutions-afternoon.md:3 -msgid "Luhn Algorithm" -msgstr "卢恩算法" +#: src/SUMMARY.md:77 src/methods-and-traits/methods.md:1 +msgid "Methods" +msgstr "方法" -#: src/SUMMARY.md:76 -msgid "Day 2: Morning" -msgstr "第二天：上午" +#: src/SUMMARY.md:78 src/methods-and-traits/traits.md:1 +msgid "Traits" +msgstr "特征（Trait）" -#: src/SUMMARY.md:82 src/memory-management.md:1 -msgid "Memory Management" -msgstr "内存管理" +#: src/SUMMARY.md:79 src/methods-and-traits/deriving.md:1 +#, fuzzy +msgid "Deriving" +msgstr "派生特征" -#: src/SUMMARY.md:83 -msgid "Stack vs Heap" -msgstr "栈 vs 堆" +#: src/SUMMARY.md:80 src/methods-and-traits/trait-objects.md:1 +msgid "Trait Objects" +msgstr "特征对象" -#: src/SUMMARY.md:84 -msgid "Stack Memory" -msgstr "栈内存" +#: src/SUMMARY.md:81 src/methods-and-traits/exercise.md:1 +#, fuzzy +msgid "Exercise: GUI Library" +msgstr "一个简单的 GUI 库" -#: src/SUMMARY.md:85 src/memory-management/manual.md:1 -msgid "Manual Memory Management" -msgstr "手动内存管理" +#: src/SUMMARY.md:83 src/generics.md:1 +msgid "Generics" +msgstr "泛型" -#: src/SUMMARY.md:86 src/memory-management/scope-based.md:1 -msgid "Scope-Based Memory Management" -msgstr "基于作用域的内存管理" +#: src/SUMMARY.md:84 src/generics/generic-functions.md:1 +#, fuzzy +msgid "Generic Functions" +msgstr "外部函数" -#: src/SUMMARY.md:87 -msgid "Garbage Collection" -msgstr "垃圾回收" +#: src/SUMMARY.md:85 src/generics/generic-data.md:1 +msgid "Generic Data Types" +msgstr "通用数据类型" -#: src/SUMMARY.md:88 -msgid "Rust Memory Management" -msgstr "Rust 内存管理" +#: src/SUMMARY.md:86 src/generics/trait-bounds.md:1 +msgid "Trait Bounds" +msgstr "特征边界" -#: src/SUMMARY.md:89 src/ownership.md:1 -msgid "Ownership" -msgstr "所有权" +#: src/SUMMARY.md:87 src/generics/impl-trait.md:1 +msgid "`impl Trait`" +msgstr "`impl Trait`" -#: src/SUMMARY.md:90 src/ownership/move-semantics.md:1 -msgid "Move Semantics" -msgstr "移动语义" +#: src/SUMMARY.md:88 src/generics/exercise.md:1 +msgid "Exercise: Generic `min`" +msgstr "" -#: src/SUMMARY.md:91 src/ownership/moved-strings-rust.md:1 -msgid "Moved Strings in Rust" -msgstr "Rust 中移动的字符串" +#: src/SUMMARY.md:91 +msgid "Day 2: Afternoon" +msgstr "第二天：下午" -#: src/SUMMARY.md:92 -msgid "Double Frees in Modern C++" -msgstr "现代 C++ 中的双重释放" +#: src/SUMMARY.md:94 src/std-types.md:1 +#, fuzzy +msgid "Standard Library Types" +msgstr "标准库" -#: src/SUMMARY.md:93 src/ownership/moves-function-calls.md:1 -msgid "Moves in Function Calls" -msgstr "函数调用中的移动" +#: src/SUMMARY.md:95 src/std-types/std.md:1 +msgid "Standard Library" +msgstr "标准库" -#: src/SUMMARY.md:94 src/ownership/copy-clone.md:1 -msgid "Copying and Cloning" -msgstr "复制和克隆" +#: src/SUMMARY.md:96 src/std-types/docs.md:1 +#, fuzzy +msgid "Documentation" +msgstr "文档测试" -#: src/SUMMARY.md:95 src/ownership/borrowing.md:1 -msgid "Borrowing" -msgstr "借用" +#: src/SUMMARY.md:97 +msgid "`Option`" +msgstr "" -#: src/SUMMARY.md:96 src/ownership/shared-unique-borrows.md:1 -msgid "Shared and Unique Borrows" -msgstr "共享和唯一的借用" +#: src/SUMMARY.md:98 +msgid "`Result`" +msgstr "" -#: src/SUMMARY.md:97 src/ownership/lifetimes.md:1 -msgid "Lifetimes" -msgstr "生命周期" +#: src/SUMMARY.md:99 src/android/interoperability/cpp/type-mapping.md:5 +#, fuzzy +msgid "`String`" +msgstr "String" -#: src/SUMMARY.md:98 src/ownership/lifetimes-function-calls.md:1 -msgid "Lifetimes in Function Calls" -msgstr "函数调用中的生命周期" +#: src/SUMMARY.md:100 src/std-types/vec.md:1 +msgid "`Vec`" +msgstr "`Vec`" -#: src/SUMMARY.md:99 src/ownership/lifetimes-data-structures.md:1 -msgid "Lifetimes in Data Structures" -msgstr "数据结构中的生命周期" +#: src/SUMMARY.md:101 src/std-types/hashmap.md:1 src/bare-metal/no_std.md:46 +msgid "`HashMap`" +msgstr "`HashMap`" -#: src/SUMMARY.md:100 src/structs.md:1 -msgid "Structs" -msgstr "结构体" +#: src/SUMMARY.md:102 src/std-types/exercise.md:1 +#, fuzzy +msgid "Exercise: Counter" +msgstr "习题" -#: src/SUMMARY.md:101 src/structs/tuple-structs.md:1 -msgid "Tuple Structs" -msgstr "元组结构体" +#: src/SUMMARY.md:104 src/std-traits.md:1 +#, fuzzy +msgid "Standard Library Traits" +msgstr "标准库" -#: src/SUMMARY.md:102 src/structs/field-shorthand.md:1 -msgid "Field Shorthand Syntax" -msgstr "字段简写语法" +#: src/SUMMARY.md:105 src/std-traits/comparisons.md:1 src/async.md:17 +msgid "Comparisons" +msgstr "" -#: src/SUMMARY.md:104 src/methods/receiver.md:1 -msgid "Method Receiver" -msgstr "方法接收者" +#: src/SUMMARY.md:106 src/std-traits/operators.md:1 +#, fuzzy +msgid "Operators" +msgstr "迭代器" -#: src/SUMMARY.md:105 src/SUMMARY.md:167 src/SUMMARY.md:282 -#: src/methods/example.md:1 src/concurrency/shared_state/example.md:1 -msgid "Example" -msgstr "示例" +#: src/SUMMARY.md:107 src/std-traits/from-and-into.md:1 +msgid "`From` and `Into`" +msgstr "`From` 和 `Into`" -#: src/SUMMARY.md:107 src/exercises/day-2/book-library.md:1 -msgid "Storing Books" -msgstr "书籍存储" +#: src/SUMMARY.md:108 src/std-traits/casting.md:1 +#, fuzzy +msgid "Casting" +msgstr "测试" -#: src/SUMMARY.md:108 src/exercises/day-2/health-statistics.md:1 -#: src/exercises/day-2/solutions-morning.md:151 -msgid "Health Statistics" -msgstr "健康统计" +#: src/SUMMARY.md:109 src/std-traits/read-and-write.md:1 +msgid "`Read` and `Write`" +msgstr "`Read` 和 `Write`" #: src/SUMMARY.md:110 -msgid "Day 2: Afternoon" -msgstr "第二天：下午" - -#: src/SUMMARY.md:112 src/std.md:1 -msgid "Standard Library" -msgstr "标准库" - -#: src/SUMMARY.md:113 -msgid "Option and Result" -msgstr "Option 和 Result" - -#: src/SUMMARY.md:114 src/std/string.md:1 -msgid "String" -msgstr "String" +msgid "`Default`, struct update syntax" +msgstr "" -#: src/SUMMARY.md:115 -msgid "Vec" -msgstr "Vec" +#: src/SUMMARY.md:111 src/std-traits/closures.md:1 +msgid "Closures" +msgstr "闭包" -#: src/SUMMARY.md:116 -msgid "HashMap" -msgstr "哈希表" +#: src/SUMMARY.md:112 src/std-traits/exercise.md:1 +#, fuzzy +msgid "Exercise: ROT13" +msgstr "习题" #: src/SUMMARY.md:117 -msgid "Box" -msgstr "Box" +msgid "Day 3: Morning" +msgstr "第三天：上午" -#: src/SUMMARY.md:118 -msgid "Recursive Data Types" -msgstr "递归数据类型" +#: src/SUMMARY.md:120 src/memory-management.md:1 +msgid "Memory Management" +msgstr "内存管理" -#: src/SUMMARY.md:119 src/std/box-niche.md:1 -msgid "Niche Optimization" -msgstr "小众优化" +#: src/SUMMARY.md:121 src/memory-management/review.md:1 +msgid "Review of Program Memory" +msgstr "" -#: src/SUMMARY.md:120 -msgid "Rc" -msgstr "Rc" +#: src/SUMMARY.md:122 src/memory-management/approaches.md:1 +#, fuzzy +msgid "Approaches to Memory Management" +msgstr "自动内存管理" -#: src/SUMMARY.md:121 -msgid "Cell/RefCell" -msgstr "Cell/RefCell" +#: src/SUMMARY.md:123 src/memory-management/ownership.md:1 +msgid "Ownership" +msgstr "所有权" -#: src/SUMMARY.md:122 src/modules.md:1 -msgid "Modules" -msgstr "模块" +#: src/SUMMARY.md:124 src/memory-management/move.md:1 +msgid "Move Semantics" +msgstr "移动语义" -#: src/SUMMARY.md:123 src/modules/visibility.md:1 -msgid "Visibility" -msgstr "可见性" +#: src/SUMMARY.md:125 +msgid "`Clone`" +msgstr "" -#: src/SUMMARY.md:124 src/modules/paths.md:1 -msgid "Paths" -msgstr "路径" +#: src/SUMMARY.md:126 src/memory-management/copy-types.md:5 +#, fuzzy +msgid "Copy Types" +msgstr "复合类型" -#: src/SUMMARY.md:125 src/modules/filesystem.md:1 -msgid "Filesystem Hierarchy" -msgstr "文件系统层级结构" +#: src/SUMMARY.md:127 +#, fuzzy +msgid "`Drop`" +msgstr "Drop" -#: src/SUMMARY.md:127 src/exercises/day-2/iterators-and-ownership.md:1 -msgid "Iterators and Ownership" -msgstr "迭代器和所有权" +#: src/SUMMARY.md:128 src/memory-management/exercise.md:1 +msgid "Exercise: Builder Type" +msgstr "" -#: src/SUMMARY.md:128 src/exercises/day-2/strings-iterators.md:1 -#: src/exercises/day-2/solutions-afternoon.md:3 -msgid "Strings and Iterators" -msgstr "字符串和迭代器" +#: src/SUMMARY.md:130 src/smart-pointers.md:1 +msgid "Smart Pointers" +msgstr "" -#: src/SUMMARY.md:131 -msgid "Day 3: Morning" -msgstr "第三天：上午" +#: src/SUMMARY.md:131 src/smart-pointers/box.md:1 +#: src/android/interoperability/cpp/type-mapping.md:9 +#, fuzzy +msgid "`Box`" +msgstr "`Box`" -#: src/SUMMARY.md:136 src/generics.md:1 -msgid "Generics" -msgstr "泛型" +#: src/SUMMARY.md:132 src/smart-pointers/rc.md:1 +msgid "`Rc`" +msgstr "`Rc`" -#: src/SUMMARY.md:137 src/generics/data-types.md:1 -msgid "Generic Data Types" -msgstr "通用数据类型" +#: src/SUMMARY.md:133 src/smart-pointers/exercise.md:1 +msgid "Exercise: Binary Tree" +msgstr "" -#: src/SUMMARY.md:138 src/generics/methods.md:1 -msgid "Generic Methods" -msgstr "泛型方法" +#: src/SUMMARY.md:136 +msgid "Day 3: Afternoon" +msgstr "第三天：下午" -#: src/SUMMARY.md:139 src/generics/monomorphization.md:1 -msgid "Monomorphization" -msgstr "单态化" +#: src/SUMMARY.md:139 src/borrowing.md:1 +msgid "Borrowing" +msgstr "借用" -#: src/SUMMARY.md:140 src/traits.md:1 -msgid "Traits" -msgstr "特征（Trait）" +#: src/SUMMARY.md:140 src/borrowing/shared.md:1 +#, fuzzy +msgid "Borrowing a Value" +msgstr "借用" -#: src/SUMMARY.md:141 src/traits/trait-objects.md:1 -msgid "Trait Objects" -msgstr "特征对象" +#: src/SUMMARY.md:141 src/borrowing/borrowck.md:1 +#, fuzzy +msgid "Borrow Checking" +msgstr "借用" -#: src/SUMMARY.md:142 src/traits/deriving-traits.md:1 -msgid "Deriving Traits" -msgstr "派生特征" +#: src/SUMMARY.md:142 src/borrowing/interior-mutability.md:5 +#, fuzzy +msgid "Interior Mutability" +msgstr "互操作性" -#: src/SUMMARY.md:143 src/traits/default-methods.md:1 -msgid "Default Methods" -msgstr "默认方法" +#: src/SUMMARY.md:143 src/borrowing/exercise.md:1 +#, fuzzy +msgid "Exercise: Health Statistics" +msgstr "健康统计" -#: src/SUMMARY.md:144 src/traits/trait-bounds.md:1 -msgid "Trait Bounds" -msgstr "特征边界" +#: src/SUMMARY.md:145 src/slices-and-lifetimes.md:1 +#, fuzzy +msgid "Slices and Lifetimes" +msgstr "生命周期" -#: src/SUMMARY.md:145 -msgid "impl Trait" -msgstr "impl Trait" +#: src/SUMMARY.md:146 +#, fuzzy +msgid "Slices: `&[T]`" +msgstr "切片" -#: src/SUMMARY.md:146 src/traits/important-traits.md:1 -msgid "Important Traits" -msgstr "重要特征" +#: src/SUMMARY.md:147 src/slices-and-lifetimes/str.md:5 +#, fuzzy +msgid "String References" +msgstr "悬垂引用" -#: src/SUMMARY.md:147 -msgid "Iterator" -msgstr "迭代器" - -#: src/SUMMARY.md:148 src/traits/from-iterator.md:1 -msgid "FromIterator" -msgstr "FromIterator" +#: src/SUMMARY.md:148 src/slices-and-lifetimes/lifetime-annotations.md:1 +#, fuzzy +msgid "Lifetime Annotations" +msgstr "函数调用中的生命周期" #: src/SUMMARY.md:149 -msgid "From and Into" -msgstr "From 和 Into" +#, fuzzy +msgid "Lifetime Elision" +msgstr "生命周期" #: src/SUMMARY.md:150 -msgid "Read and Write" -msgstr "读取和写入" - -#: src/SUMMARY.md:151 -msgid "Drop" -msgstr "Drop" - -#: src/SUMMARY.md:152 -msgid "Default" -msgstr "Default" - -#: src/SUMMARY.md:153 -msgid "Operators: Add, Mul, ..." -msgstr "运算符：Add、Mul..." +#, fuzzy +msgid "Struct Lifetimes" +msgstr "生命周期" -#: src/SUMMARY.md:154 -msgid "Closures: Fn, FnMut, FnOnce" -msgstr "闭包：Fn、FnMut、FnOnce" +#: src/SUMMARY.md:151 src/slices-and-lifetimes/exercise.md:1 +msgid "Exercise: Protobuf Parsing" +msgstr "" #: src/SUMMARY.md:156 -msgid "A Simple GUI Library" -msgstr "一个简单的 GUI 库" - -#: src/SUMMARY.md:157 src/exercises/day-3/solutions-morning.md:142 -msgid "Points and Polygons" -msgstr "点和多边形" +#, fuzzy +msgid "Day 4: Morning" +msgstr "第一天：早上" -#: src/SUMMARY.md:159 -msgid "Day 3: Afternoon" -msgstr "第三天：下午" +#: src/SUMMARY.md:159 src/iterators.md:1 +msgid "Iterators" +msgstr "迭代器" -#: src/SUMMARY.md:161 src/error-handling.md:1 -msgid "Error Handling" -msgstr "错误处理" +#: src/SUMMARY.md:160 src/iterators/iterator.md:5 src/bare-metal/no_std.md:28 +msgid "`Iterator`" +msgstr "“Iterator”" -#: src/SUMMARY.md:162 src/error-handling/panics.md:1 -msgid "Panics" -msgstr "Panics" +#: src/SUMMARY.md:161 src/iterators/intoiterator.md:1 +msgid "`IntoIterator`" +msgstr "“IntoIterator”" -#: src/SUMMARY.md:163 -msgid "Catching Stack Unwinding" -msgstr "捕获堆栈展开" +#: src/SUMMARY.md:162 +#, fuzzy +msgid "`FromIterator`" +msgstr "FromIterator" -#: src/SUMMARY.md:164 -msgid "Structured Error Handling" -msgstr "结构化错误处理" +#: src/SUMMARY.md:163 src/iterators/exercise.md:1 +msgid "Exercise: Iterator Method Chaining" +msgstr "" -#: src/SUMMARY.md:165 -msgid "Propagating Errors with ?" -msgstr "使用 ? 传播错误" +#: src/SUMMARY.md:165 src/SUMMARY.md:166 src/modules.md:1 +#: src/modules/modules.md:1 +msgid "Modules" +msgstr "模块" -#: src/SUMMARY.md:166 src/error-handling/converting-error-types.md:1 -#: src/error-handling/converting-error-types-example.md:1 -msgid "Converting Error Types" -msgstr "转换错误类型" +#: src/SUMMARY.md:167 src/modules/filesystem.md:1 +msgid "Filesystem Hierarchy" +msgstr "文件系统层级结构" -#: src/SUMMARY.md:168 src/error-handling/deriving-error-enums.md:1 -msgid "Deriving Error Enums" -msgstr "派生错误枚举" +#: src/SUMMARY.md:168 src/modules/visibility.md:1 +msgid "Visibility" +msgstr "可见性" -#: src/SUMMARY.md:169 src/error-handling/dynamic-errors.md:1 -msgid "Dynamic Error Types" -msgstr "动态错误类型" +#: src/SUMMARY.md:169 +msgid "`use`, `super`, `self`" +msgstr "" -#: src/SUMMARY.md:170 src/error-handling/error-contexts.md:1 -msgid "Adding Context to Errors" -msgstr "为错误添加背景信息" +#: src/SUMMARY.md:170 src/modules/exercise.md:1 +msgid "Exercise: Modules for the GUI Library" +msgstr "" -#: src/SUMMARY.md:171 src/testing.md:1 +#: src/SUMMARY.md:172 src/SUMMARY.md:253 src/testing.md:1 +#: src/chromium/testing.md:1 msgid "Testing" msgstr "测试" -#: src/SUMMARY.md:172 src/testing/unit-tests.md:1 -msgid "Unit Tests" -msgstr "单元测试" - -#: src/SUMMARY.md:173 src/testing/test-modules.md:1 +#: src/SUMMARY.md:173 msgid "Test Modules" msgstr "测试模块" -#: src/SUMMARY.md:174 src/testing/doc-tests.md:1 -msgid "Documentation Tests" -msgstr "文档测试" - -#: src/SUMMARY.md:175 src/testing/integration-tests.md:1 -msgid "Integration Tests" -msgstr "集成测试" +#: src/SUMMARY.md:174 src/testing/other.md:1 +#, fuzzy +msgid "Other Types of Tests" +msgstr "其他资源" -#: src/SUMMARY.md:176 src/bare-metal/useful-crates.md:1 -msgid "Useful crates" +#: src/SUMMARY.md:175 src/SUMMARY.md:321 src/testing/useful-crates.md:1 +msgid "Useful Crates" msgstr "实用 crate" -#: src/SUMMARY.md:177 src/unsafe.md:1 +#: src/SUMMARY.md:176 src/testing/googletest.md:1 +msgid "GoogleTest" +msgstr "" + +#: src/SUMMARY.md:177 src/testing/mocking.md:1 +msgid "Mocking" +msgstr "" + +#: src/SUMMARY.md:178 src/testing/lints.md:1 +msgid "Compiler Lints and Clippy" +msgstr "" + +#: src/SUMMARY.md:179 src/testing/exercise.md:1 +#, fuzzy +msgid "Exercise: Luhn Algorithm" +msgstr "卢恩算法" + +#: src/SUMMARY.md:182 +#, fuzzy +msgid "Day 4: Afternoon" +msgstr "第一天：下午" + +#: src/SUMMARY.md:185 src/error-handling.md:1 +msgid "Error Handling" +msgstr "错误处理" + +#: src/SUMMARY.md:186 src/error-handling/panics.md:1 +msgid "Panics" +msgstr "Panics" + +#: src/SUMMARY.md:187 src/error-handling/try.md:1 +#, fuzzy +msgid "Try Operator" +msgstr "迭代器" + +#: src/SUMMARY.md:188 src/error-handling/try-conversions.md:1 +#, fuzzy +msgid "Try Conversions" +msgstr "隐式类型转换" + +#: src/SUMMARY.md:189 +#, fuzzy +msgid "`Error` Trait" +msgstr "`Drop` 特征" + +#: src/SUMMARY.md:190 src/error-handling/thiserror-and-anyhow.md:1 +#, fuzzy +msgid "`thiserror` and `anyhow`" +msgstr "`From` 和 `Into`" + +#: src/SUMMARY.md:191 +#, fuzzy +msgid "Exercise: Rewriting with `Result`" +msgstr "使用 `Result` 进行结构化错误处理" + +#: src/SUMMARY.md:193 src/unsafe-rust.md:1 src/unsafe-rust/unsafe.md:1 msgid "Unsafe Rust" msgstr "不安全 Rust" -#: src/SUMMARY.md:178 src/unsafe/raw-pointers.md:1 +#: src/SUMMARY.md:194 +#, fuzzy +msgid "Unsafe" +msgstr "是（不安全）" + +#: src/SUMMARY.md:195 src/unsafe-rust/dereferencing.md:1 msgid "Dereferencing Raw Pointers" msgstr "解引用裸指针" -#: src/SUMMARY.md:179 src/unsafe/mutable-static-variables.md:1 +#: src/SUMMARY.md:196 src/unsafe-rust/mutable-static.md:1 msgid "Mutable Static Variables" msgstr "可变的静态变量" -#: src/SUMMARY.md:180 src/unsafe/unions.md:1 +#: src/SUMMARY.md:197 src/unsafe-rust/unions.md:1 msgid "Unions" msgstr "联合体" -#: src/SUMMARY.md:181 src/unsafe/calling-unsafe-functions.md:1 -msgid "Calling Unsafe Functions" +#: src/SUMMARY.md:198 src/unsafe-rust/unsafe-functions.md:1 +#, fuzzy +msgid "Unsafe Functions" msgstr "调用 Unsafe 函数" -#: src/SUMMARY.md:182 src/unsafe/writing-unsafe-functions.md:1 -msgid "Writing Unsafe Functions" -msgstr "编写 Unsafe 函数" - -#: src/SUMMARY.md:183 -msgid "Extern Functions" -msgstr "外部函数" - -#: src/SUMMARY.md:184 src/unsafe/unsafe-traits.md:1 -msgid "Implementing Unsafe Traits" +#: src/SUMMARY.md:199 +#, fuzzy +msgid "Unsafe Traits" msgstr "实现 Unsafe Trait" -#: src/SUMMARY.md:186 src/exercises/day-3/safe-ffi-wrapper.md:1 -#: src/exercises/day-3/solutions-afternoon.md:3 -msgid "Safe FFI Wrapper" +#: src/SUMMARY.md:200 +#, fuzzy +msgid "Exercise: FFI Wrapper" msgstr "安全 FFI 封装容器" -#: src/SUMMARY.md:189 src/SUMMARY.md:259 src/bare-metal/android.md:1 +#: src/SUMMARY.md:203 src/SUMMARY.md:327 src/bare-metal/android.md:1 msgid "Android" msgstr "Android" -#: src/SUMMARY.md:194 src/android/setup.md:1 +#: src/SUMMARY.md:208 src/SUMMARY.md:245 src/android/setup.md:1 +#: src/chromium/setup.md:1 msgid "Setup" msgstr "设置" -#: src/SUMMARY.md:195 src/android/build-rules.md:1 +#: src/SUMMARY.md:209 src/SUMMARY.md:248 src/android/build-rules.md:1 msgid "Build Rules" msgstr "构建规则" -#: src/SUMMARY.md:196 +#: src/SUMMARY.md:210 msgid "Binary" msgstr "可执行文件" -#: src/SUMMARY.md:197 +#: src/SUMMARY.md:211 msgid "Library" msgstr "库" -#: src/SUMMARY.md:198 src/android/aidl.md:1 +#: src/SUMMARY.md:212 src/android/aidl.md:1 msgid "AIDL" msgstr "AIDL" -#: src/SUMMARY.md:199 +#: src/SUMMARY.md:213 msgid "Interface" msgstr "接口" -#: src/SUMMARY.md:200 +#: src/SUMMARY.md:214 msgid "Implementation" msgstr "实现" -#: src/SUMMARY.md:201 +#: src/SUMMARY.md:215 msgid "Server" msgstr "服务器" -#: src/SUMMARY.md:202 src/android/aidl/deploy.md:1 +#: src/SUMMARY.md:216 src/android/aidl/deploy.md:1 msgid "Deploy" msgstr "部署" -#: src/SUMMARY.md:203 +#: src/SUMMARY.md:217 msgid "Client" msgstr "客户端" -#: src/SUMMARY.md:204 src/android/aidl/changing.md:1 +#: src/SUMMARY.md:218 src/android/aidl/changing.md:1 msgid "Changing API" msgstr "更改 API" -#: src/SUMMARY.md:205 src/SUMMARY.md:249 src/android/logging.md:1 +#: src/SUMMARY.md:219 src/SUMMARY.md:317 src/android/logging.md:1 #: src/bare-metal/aps/logging.md:1 msgid "Logging" msgstr "日志记录" -#: src/SUMMARY.md:206 src/android/interoperability.md:1 +#: src/SUMMARY.md:220 src/android/interoperability.md:1 msgid "Interoperability" msgstr "互操作性" -#: src/SUMMARY.md:207 +#: src/SUMMARY.md:221 msgid "With C" msgstr "与 C 语言交互" -#: src/SUMMARY.md:208 +#: src/SUMMARY.md:222 msgid "Calling C with Bindgen" msgstr "使用 Bindgen 调用 C 语言" -#: src/SUMMARY.md:209 +#: src/SUMMARY.md:223 msgid "Calling Rust from C" msgstr "从 C 语言调用 Rust 语言" -#: src/SUMMARY.md:210 src/android/interoperability/cpp.md:1 -msgid "With C++" +#: src/SUMMARY.md:224 +#, fuzzy +msgid "With C++)" msgstr "与 C++ 交互" -#: src/SUMMARY.md:211 +#: src/SUMMARY.md:225 src/android/interoperability/cpp/bridge.md:1 +#, fuzzy +msgid "The Bridge Module" +msgstr "测试模块" + +#: src/SUMMARY.md:226 +#, fuzzy +msgid "Rust Bridge" +msgstr "Rust 二进制文件" + +#: src/SUMMARY.md:227 src/android/interoperability/cpp/generated-cpp.md:1 +msgid "Generated C++" +msgstr "" + +#: src/SUMMARY.md:228 +msgid "C++ Bridge" +msgstr "" + +#: src/SUMMARY.md:229 src/android/interoperability/cpp/shared-types.md:1 +#, fuzzy +msgid "Shared Types" +msgstr "标量类型" + +#: src/SUMMARY.md:230 src/android/interoperability/cpp/shared-enums.md:1 +msgid "Shared Enums" +msgstr "" + +#: src/SUMMARY.md:231 src/android/interoperability/cpp/rust-result.md:1 +#, fuzzy +msgid "Rust Error Handling" +msgstr "错误处理" + +#: src/SUMMARY.md:232 src/android/interoperability/cpp/cpp-exception.md:1 +#, fuzzy +msgid "C++ Error Handling" +msgstr "错误处理" + +#: src/SUMMARY.md:233 src/android/interoperability/cpp/type-mapping.md:1 +msgid "Additional Types" +msgstr "" + +#: src/SUMMARY.md:234 +msgid "Building for Android: C++" +msgstr "" + +#: src/SUMMARY.md:235 +msgid "Building for Android: Genrules" +msgstr "" + +#: src/SUMMARY.md:236 +msgid "Building for Android: Rust" +msgstr "" + +#: src/SUMMARY.md:237 msgid "With Java" msgstr "与 Java 交互" -#: src/SUMMARY.md:215 +#: src/SUMMARY.md:238 src/SUMMARY.md:300 src/SUMMARY.md:329 src/SUMMARY.md:351 +#: src/SUMMARY.md:373 src/exercises/android/morning.md:1 +#: src/exercises/bare-metal/morning.md:1 +#: src/exercises/bare-metal/afternoon.md:1 +#: src/exercises/concurrency/morning.md:1 +#: src/exercises/concurrency/afternoon.md:1 +msgid "Exercises" +msgstr "习题" + +#: src/SUMMARY.md:240 +msgid "Chromium" +msgstr "" + +#: src/SUMMARY.md:246 src/chromium/cargo.md:1 +msgid "Comparing Chromium and Cargo Ecosystems" +msgstr "" + +#: src/SUMMARY.md:247 +msgid "Policy" +msgstr "" + +#: src/SUMMARY.md:249 +#, fuzzy +msgid "Unsafe Code" +msgstr "不安全 Rust" + +#: src/SUMMARY.md:250 src/chromium/build-rules/depending.md:1 +msgid "Depending on Rust Code from Chromium C++" +msgstr "" + +#: src/SUMMARY.md:251 src/chromium/build-rules/vscode.md:1 +msgid "Visual Studio Code" +msgstr "" + +#: src/SUMMARY.md:252 src/SUMMARY.md:257 src/SUMMARY.md:265 src/SUMMARY.md:278 +#: src/exercises/chromium/third-party.md:1 +#, fuzzy +msgid "Exercise" +msgstr "习题" + +#: src/SUMMARY.md:254 src/chromium/testing/rust-gtest-interop.md:1 +msgid "`rust_gtest_interop` Library" +msgstr "" + +#: src/SUMMARY.md:255 src/chromium/testing/build-gn.md:1 +msgid "GN Rules for Rust Tests" +msgstr "" + +#: src/SUMMARY.md:256 src/chromium/testing/chromium-import-macro.md:1 +msgid "`chromium::import!` Macro" +msgstr "" + +#: src/SUMMARY.md:258 src/chromium/interoperability-with-cpp.md:1 +#, fuzzy +msgid "Interoperability with C++" +msgstr "与 C 的互操作性" + +#: src/SUMMARY.md:259 +#: src/chromium/interoperability-with-cpp/example-bindings.md:1 +#, fuzzy +msgid "Example Bindings" +msgstr "示例" + +#: src/SUMMARY.md:260 +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:1 +msgid "Limitations of CXX" +msgstr "" + +#: src/SUMMARY.md:261 +#: src/chromium/interoperability-with-cpp/error-handling.md:1 +#, fuzzy +msgid "CXX Error Handling" +msgstr "错误处理" + +#: src/SUMMARY.md:262 +#, fuzzy +msgid "Error Handling: QR Example" +msgstr "错误处理" + +#: src/SUMMARY.md:263 +#, fuzzy +msgid "Error Handling: PNG Example" +msgstr "错误处理" + +#: src/SUMMARY.md:264 +msgid "Using CXX in Chromium" +msgstr "" + +#: src/SUMMARY.md:266 src/chromium/adding-third-party-crates.md:1 +msgid "Adding Third Party Crates" +msgstr "" + +#: src/SUMMARY.md:267 +msgid "Configuring Cargo.toml" +msgstr "" + +#: src/SUMMARY.md:268 +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:1 +msgid "Configuring `gnrt_config.toml`" +msgstr "" + +#: src/SUMMARY.md:269 +#: src/chromium/adding-third-party-crates/downloading-crates.md:1 +msgid "Downloading Crates" +msgstr "" + +#: src/SUMMARY.md:270 +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:1 +msgid "Generating `gn` Build Rules" +msgstr "" + +#: src/SUMMARY.md:271 +#: src/chromium/adding-third-party-crates/resolving-problems.md:1 +msgid "Resolving Problems" +msgstr "" + +#: src/SUMMARY.md:272 +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:1 +msgid "Build Scripts Which Generate Code" +msgstr "" + +#: src/SUMMARY.md:273 +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:1 +msgid "Build Scripts Which Build C++ or Take Arbitrary Actions" +msgstr "" + +#: src/SUMMARY.md:274 +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:1 +msgid "Depending on a Crate" +msgstr "" + +#: src/SUMMARY.md:275 +msgid "Reviews and Audits" +msgstr "" + +#: src/SUMMARY.md:276 +msgid "Checking into Chromium Source Code" +msgstr "" + +#: src/SUMMARY.md:277 +#: src/chromium/adding-third-party-crates/keeping-up-to-date.md:1 +msgid "Keeping Crates Up to Date" +msgstr "" + +#: src/SUMMARY.md:279 +msgid "Bringing It Together - Exercise" +msgstr "" + +#: src/SUMMARY.md:280 src/exercises/chromium/solutions.md:1 +#, fuzzy +msgid "Exercise Solutions" +msgstr "解答" + +#: src/SUMMARY.md:282 msgid "Bare Metal: Morning" msgstr "裸金属：上午" -#: src/SUMMARY.md:220 -msgid "no_std" -msgstr "no_std" +#: src/SUMMARY.md:287 src/bare-metal/no_std.md:1 +msgid "`no_std`" +msgstr "" -#: src/SUMMARY.md:221 +#: src/SUMMARY.md:288 msgid "A Minimal Example" msgstr "最小示例" -#: src/SUMMARY.md:222 -msgid "alloc" -msgstr "alloc" +#: src/SUMMARY.md:289 src/bare-metal/no_std.md:12 src/bare-metal/alloc.md:1 +msgid "`alloc`" +msgstr "" -#: src/SUMMARY.md:223 src/bare-metal/microcontrollers.md:1 +#: src/SUMMARY.md:290 src/bare-metal/microcontrollers.md:1 msgid "Microcontrollers" msgstr "微控制器" -#: src/SUMMARY.md:224 src/bare-metal/microcontrollers/mmio.md:1 +#: src/SUMMARY.md:291 src/bare-metal/microcontrollers/mmio.md:1 msgid "Raw MMIO" msgstr "原始 MMIO" -#: src/SUMMARY.md:225 +#: src/SUMMARY.md:292 msgid "PACs" msgstr "PAC" -#: src/SUMMARY.md:226 +#: src/SUMMARY.md:293 msgid "HAL Crates" msgstr "HAL crate" -#: src/SUMMARY.md:227 +#: src/SUMMARY.md:294 msgid "Board Support Crates" msgstr "板级支持 Crate" -#: src/SUMMARY.md:228 +#: src/SUMMARY.md:295 msgid "The Type State Pattern" msgstr "类型状态模式" -#: src/SUMMARY.md:229 -#, fuzzy -msgid "embedded-hal" -msgstr "embedded-hal" +#: src/SUMMARY.md:296 src/bare-metal/microcontrollers/embedded-hal.md:1 +msgid "`embedded-hal`" +msgstr "" -#: src/SUMMARY.md:230 -msgid "probe-rs, cargo-embed" +#: src/SUMMARY.md:297 src/bare-metal/microcontrollers/probe-rs.md:1 +#, fuzzy +msgid "`probe-rs` and `cargo-embed`" msgstr "probe-rs、cargo-embed" -#: src/SUMMARY.md:231 src/bare-metal/microcontrollers/debugging.md:1 +#: src/SUMMARY.md:298 src/bare-metal/microcontrollers/debugging.md:1 #, fuzzy msgid "Debugging" msgstr "调试" -#: src/SUMMARY.md:232 src/SUMMARY.md:252 +#: src/SUMMARY.md:299 src/SUMMARY.md:320 msgid "Other Projects" msgstr "其他项目" -#: src/SUMMARY.md:234 src/exercises/bare-metal/compass.md:1 +#: src/SUMMARY.md:301 src/exercises/bare-metal/compass.md:1 #: src/exercises/bare-metal/solutions-morning.md:3 msgid "Compass" msgstr "罗盘" -#: src/SUMMARY.md:236 +#: src/SUMMARY.md:302 src/SUMMARY.md:331 src/SUMMARY.md:354 src/SUMMARY.md:376 +msgid "Solutions" +msgstr "解答" + +#: src/SUMMARY.md:304 msgid "Bare Metal: Afternoon" msgstr "裸金属：下午" -#: src/SUMMARY.md:238 +#: src/SUMMARY.md:306 msgid "Application Processors" msgstr "应用处理器" -#: src/SUMMARY.md:239 src/bare-metal/aps/entry-point.md:1 +#: src/SUMMARY.md:307 src/bare-metal/aps/entry-point.md:1 msgid "Getting Ready to Rust" msgstr "准备使用 Rust" -#: src/SUMMARY.md:240 +#: src/SUMMARY.md:308 msgid "Inline Assembly" msgstr "内联汇编" -#: src/SUMMARY.md:241 +#: src/SUMMARY.md:309 msgid "MMIO" msgstr "MMIO" -#: src/SUMMARY.md:242 +#: src/SUMMARY.md:310 msgid "Let's Write a UART Driver" msgstr "编写 UART 驱动程序" -#: src/SUMMARY.md:243 +#: src/SUMMARY.md:311 msgid "More Traits" msgstr "更多 trait" -#: src/SUMMARY.md:244 +#: src/SUMMARY.md:312 msgid "A Better UART Driver" msgstr "一个更好的 UART 驱动程序" -#: src/SUMMARY.md:245 src/bare-metal/aps/better-uart/bitflags.md:1 +#: src/SUMMARY.md:313 src/bare-metal/aps/better-uart/bitflags.md:1 msgid "Bitflags" msgstr "Bitflags" -#: src/SUMMARY.md:246 +#: src/SUMMARY.md:314 msgid "Multiple Registers" msgstr "多个寄存器" -#: src/SUMMARY.md:247 src/bare-metal/aps/better-uart/driver.md:1 +#: src/SUMMARY.md:315 src/bare-metal/aps/better-uart/driver.md:1 msgid "Driver" msgstr "驱动程序" -#: src/SUMMARY.md:248 src/SUMMARY.md:250 +#: src/SUMMARY.md:316 src/SUMMARY.md:318 msgid "Using It" msgstr "开始使用" -#: src/SUMMARY.md:251 src/bare-metal/aps/exceptions.md:1 +#: src/SUMMARY.md:319 src/bare-metal/aps/exceptions.md:1 msgid "Exceptions" msgstr "异常" -#: src/SUMMARY.md:253 -msgid "Useful Crates" -msgstr "实用 crate" - -#: src/SUMMARY.md:254 -msgid "zerocopy" -msgstr "zerocopy" +#: src/SUMMARY.md:322 src/bare-metal/useful-crates/zerocopy.md:1 +msgid "`zerocopy`" +msgstr "" -#: src/SUMMARY.md:255 -msgid "aarch64-paging" -msgstr "aarch64-paging" +#: src/SUMMARY.md:323 src/bare-metal/useful-crates/aarch64-paging.md:1 +msgid "`aarch64-paging`" +msgstr "" -#: src/SUMMARY.md:256 -msgid "buddy_system_allocator" -msgstr "buddy_system_allocator" +#: src/SUMMARY.md:324 src/bare-metal/useful-crates/buddy_system_allocator.md:1 +msgid "`buddy_system_allocator`" +msgstr "" -#: src/SUMMARY.md:257 -msgid "tinyvec" -msgstr "tinyvec" +#: src/SUMMARY.md:325 src/bare-metal/useful-crates/tinyvec.md:1 +msgid "`tinyvec`" +msgstr "" -#: src/SUMMARY.md:258 -msgid "spin" -msgstr "转动" +#: src/SUMMARY.md:326 src/bare-metal/useful-crates/spin.md:1 +msgid "`spin`" +msgstr "" -#: src/SUMMARY.md:260 src/bare-metal/android/vmbase.md:1 -msgid "vmbase" +#: src/SUMMARY.md:328 +#, fuzzy +msgid "`vmbase`" msgstr "vmbase" -#: src/SUMMARY.md:262 +#: src/SUMMARY.md:330 msgid "RTC Driver" msgstr "RTC驱动" -#: src/SUMMARY.md:265 +#: src/SUMMARY.md:333 msgid "Concurrency: Morning" msgstr "并发编程：上午" -#: src/SUMMARY.md:270 src/concurrency/threads.md:1 +#: src/SUMMARY.md:338 src/concurrency/threads.md:1 msgid "Threads" msgstr "线程" -#: src/SUMMARY.md:271 src/concurrency/scoped-threads.md:1 +#: src/SUMMARY.md:339 src/concurrency/scoped-threads.md:1 msgid "Scoped Threads" msgstr "范围线程" -#: src/SUMMARY.md:272 src/concurrency/channels.md:1 +#: src/SUMMARY.md:340 src/concurrency/channels.md:1 msgid "Channels" msgstr "通道" -#: src/SUMMARY.md:273 src/concurrency/channels/unbounded.md:1 +#: src/SUMMARY.md:341 src/concurrency/channels/unbounded.md:1 msgid "Unbounded Channels" msgstr "无界通道" -#: src/SUMMARY.md:274 src/concurrency/channels/bounded.md:1 +#: src/SUMMARY.md:342 src/concurrency/channels/bounded.md:1 msgid "Bounded Channels" msgstr "有界通道" -#: src/SUMMARY.md:275 -msgid "Send and Sync" -msgstr "Send 和 Sync" +#: src/SUMMARY.md:343 src/concurrency/send-sync.md:1 +msgid "`Send` and `Sync`" +msgstr "`Send` 和 `Sync`" -#: src/SUMMARY.md:275 -msgid "Send" -msgstr "Send" +#: src/SUMMARY.md:344 src/concurrency/send-sync/send.md:1 +msgid "`Send`" +msgstr "`Send`" -#: src/SUMMARY.md:275 -msgid "Sync" -msgstr "Sync" +#: src/SUMMARY.md:345 src/concurrency/send-sync/sync.md:1 +msgid "`Sync`" +msgstr "`Sync`" -#: src/SUMMARY.md:278 src/concurrency/send-sync/examples.md:1 +#: src/SUMMARY.md:346 src/concurrency/send-sync/examples.md:1 msgid "Examples" msgstr "示例" -#: src/SUMMARY.md:279 src/concurrency/shared_state.md:1 +#: src/SUMMARY.md:347 src/concurrency/shared_state.md:1 msgid "Shared State" msgstr "共享状态" -#: src/SUMMARY.md:280 -msgid "Arc" -msgstr "Arc" +#: src/SUMMARY.md:348 src/concurrency/shared_state/arc.md:1 +msgid "`Arc`" +msgstr "`Arc`" + +#: src/SUMMARY.md:349 src/concurrency/shared_state/mutex.md:1 +msgid "`Mutex`" +msgstr "`互斥器 (Mutex)`" -#: src/SUMMARY.md:281 -msgid "Mutex" -msgstr "Mutex" +#: src/SUMMARY.md:350 src/memory-management/review.md:16 +#: src/error-handling/try-conversions.md:23 +#: src/concurrency/shared_state/example.md:1 +msgid "Example" +msgstr "示例" -#: src/SUMMARY.md:284 src/SUMMARY.md:305 +#: src/SUMMARY.md:352 src/SUMMARY.md:374 #: src/exercises/concurrency/dining-philosophers.md:1 #: src/exercises/concurrency/solutions-morning.md:3 msgid "Dining Philosophers" msgstr "哲学家就餐问题 (Dining philosophers problem)" -#: src/SUMMARY.md:285 src/exercises/concurrency/link-checker.md:1 +#: src/SUMMARY.md:353 src/exercises/concurrency/link-checker.md:1 msgid "Multi-threaded Link Checker" msgstr "多线程链接检查器" -#: src/SUMMARY.md:287 +#: src/SUMMARY.md:356 msgid "Concurrency: Afternoon" msgstr "并发：下午" -#: src/SUMMARY.md:289 +#: src/SUMMARY.md:358 msgid "Async Basics" msgstr "异步基础" -#: src/SUMMARY.md:290 -msgid "async/await" -msgstr "async/await" +#: src/SUMMARY.md:359 src/async/async-await.md:1 +msgid "`async`/`await`" +msgstr "" -#: src/SUMMARY.md:291 src/async/futures.md:1 +#: src/SUMMARY.md:360 src/async/futures.md:1 msgid "Futures" msgstr "Futures" -#: src/SUMMARY.md:292 src/async/runtimes.md:1 +#: src/SUMMARY.md:361 src/async/runtimes.md:1 msgid "Runtimes" msgstr "Runtimes" -#: src/SUMMARY.md:293 src/async/runtimes/tokio.md:1 +#: src/SUMMARY.md:362 src/async/runtimes/tokio.md:1 msgid "Tokio" msgstr "Tokio" -#: src/SUMMARY.md:294 src/exercises/concurrency/link-checker.md:126 +#: src/SUMMARY.md:363 src/exercises/concurrency/link-checker.md:127 #: src/async/tasks.md:1 src/exercises/concurrency/chat-app.md:143 msgid "Tasks" msgstr "任务" -#: src/SUMMARY.md:295 src/async/channels.md:1 +#: src/SUMMARY.md:364 src/async/channels.md:1 msgid "Async Channels" msgstr "异步通道" -#: src/SUMMARY.md:297 src/async/control-flow/join.md:1 +#: src/SUMMARY.md:365 +msgid "Control Flow" +msgstr "控制流" + +#: src/SUMMARY.md:366 src/async/control-flow/join.md:1 msgid "Join" msgstr "加入" -#: src/SUMMARY.md:298 src/async/control-flow/select.md:1 +#: src/SUMMARY.md:367 src/async/control-flow/select.md:1 msgid "Select" msgstr "选择" -#: src/SUMMARY.md:299 +#: src/SUMMARY.md:368 msgid "Pitfalls" msgstr "误区" -#: src/SUMMARY.md:300 +#: src/SUMMARY.md:369 msgid "Blocking the Executor" msgstr "屏蔽执行器" -#: src/SUMMARY.md:301 src/async/pitfalls/pin.md:1 -msgid "Pin" -msgstr "固定" +#: src/SUMMARY.md:370 src/async/pitfalls/pin.md:1 +msgid "`Pin`" +msgstr "" -#: src/SUMMARY.md:302 src/async/pitfalls/async-traits.md:1 +#: src/SUMMARY.md:371 src/async/pitfalls/async-traits.md:1 msgid "Async Traits" msgstr "异步特质" -#: src/SUMMARY.md:303 src/async/pitfalls/cancellation.md:1 +#: src/SUMMARY.md:372 src/async/pitfalls/cancellation.md:1 msgid "Cancellation" msgstr "消除" -#: src/SUMMARY.md:306 src/exercises/concurrency/chat-app.md:1 +#: src/SUMMARY.md:375 src/exercises/concurrency/chat-app.md:1 #: src/exercises/concurrency/solutions-afternoon.md:95 msgid "Broadcast Chat Application" msgstr "广播聊天应用程序" -#: src/SUMMARY.md:309 +#: src/SUMMARY.md:378 msgid "Final Words" msgstr "结束语" -#: src/SUMMARY.md:313 src/thanks.md:1 +#: src/SUMMARY.md:382 src/thanks.md:1 msgid "Thanks!" msgstr "谢谢！" -#: src/SUMMARY.md:314 src/glossary.md:1 +#: src/SUMMARY.md:383 src/glossary.md:1 msgid "Glossary" msgstr "词汇表" -#: src/SUMMARY.md:315 +#: src/SUMMARY.md:384 msgid "Other Resources" msgstr "其他资源" -#: src/SUMMARY.md:316 src/credits.md:1 +#: src/SUMMARY.md:385 src/credits.md:1 msgid "Credits" msgstr "鸣谢" -#: src/SUMMARY.md:319 src/exercises/solutions.md:1 -msgid "Solutions" -msgstr "解答" - -#: src/SUMMARY.md:324 -msgid "Day 1 Morning" -msgstr "第一天上午" - -#: src/SUMMARY.md:325 -msgid "Day 1 Afternoon" -msgstr "第一天下午" - -#: src/SUMMARY.md:326 -msgid "Day 2 Morning" -msgstr "第二天上午" - -#: src/SUMMARY.md:327 -msgid "Day 2 Afternoon" -msgstr "第二天下午" - -#: src/SUMMARY.md:328 -msgid "Day 3 Morning" -msgstr "第三天上午" - -#: src/SUMMARY.md:329 -msgid "Day 3 Afternoon" -msgstr "第三天下午" - -#: src/SUMMARY.md:330 -msgid "Bare Metal Rust Morning" -msgstr "嵌入式 Rust：入门篇" - -#: src/SUMMARY.md:331 src/exercises/bare-metal/solutions-afternoon.md:1 -msgid "Bare Metal Rust Afternoon" -msgstr "嵌入式 Rust：进阶篇" - -#: src/SUMMARY.md:332 -msgid "Concurrency Morning" -msgstr "并发编程：入门篇" - -#: src/SUMMARY.md:333 -msgid "Concurrency Afternoon" -msgstr "并发编程：进阶篇" - #: src/index.md:3 #, fuzzy msgid "" @@ -1090,7 +1311,8 @@ msgid "Show you common Rust idioms." msgstr "展示常见的 Rust 习语。" #: src/index.md:22 -msgid "We call the first three course days Rust Fundamentals." +#, fuzzy +msgid "We call the first four course days Rust Fundamentals." msgstr "我们将前三天的课程称为“Rust 基础知识”。" #: src/index.md:24 @@ -1107,6 +1329,16 @@ msgstr "" "（AOSP）。课程内容包括与 C、C++ 和 Java 的互操作性。" #: src/index.md:28 +#, fuzzy +msgid "" +"[Chromium](chromium.md): a half-day course on using Rust within Chromium " +"based browsers. This includes interoperability with C++ and how to include " +"third-party crates in Chromium." +msgstr "" +"[Android](android.md)：为期半天的课程，介绍如何在 Android 平台开发中使用 Rust" +"（AOSP）。课程内容包括与 C、C++ 和 Java 的互操作性。" + +#: src/index.md:31 msgid "" "[Bare-metal](bare-metal.md): a whole-day class on using Rust for bare-metal " "(embedded) development. Both microcontrollers and application processors are " @@ -1115,7 +1347,7 @@ msgstr "" "[Bare-metal](bare-metal.md)：为期一天的课程，介绍如何使用 Rust 进行裸机（嵌入" "式）开发。课程内容涵盖微控制器和应用处理器。" -#: src/index.md:31 +#: src/index.md:34 msgid "" "[Concurrency](concurrency.md): a whole-day class on concurrency in Rust. We " "cover both classical concurrency (preemptively scheduling using threads and " @@ -1126,18 +1358,18 @@ msgstr "" "并发（使用线程和互斥锁进行抢占式调度）和 async/await 并发（使用 futures 进行" "协作式多任务处理）。" -#: src/index.md:37 +#: src/index.md:38 msgid "Non-Goals" msgstr "非目标" -#: src/index.md:39 +#: src/index.md:40 msgid "" "Rust is a large language and we won't be able to cover all of it in a few " "days. Some non-goals of this course are:" msgstr "" "Rust 是一门庞大的语言，我们无法在几天内涵盖所有内容。本课程的一些非目标包括：" -#: src/index.md:42 +#: src/index.md:43 msgid "" "Learning how to develop macros: please see [Chapter 19.5 in the Rust Book]" "(https://doc.rust-lang.org/book/ch19-06-macros.html) and [Rust by Example]" @@ -1147,11 +1379,11 @@ msgstr "" "book/ch19-06-macros.html) 和 [Rust by Examples](https://doc.rust-lang.org/" "rust-by-example/macros.html)。" -#: src/index.md:46 +#: src/index.md:48 msgid "Assumptions" msgstr "前提假设" -#: src/index.md:48 +#: src/index.md:50 msgid "" "The course assumes that you already know how to program. Rust is a " "statically-typed language and we will sometimes make comparisons with C and " @@ -1160,7 +1392,7 @@ msgstr "" "本课程假设你已经具备编程知识。Rust 是一种静态类型语言，我们有时会与 C 和 C++ " "进行比较，以更好地解释或对比 Rust 的方法。" -#: src/index.md:52 +#: src/index.md:54 msgid "" "If you know how to program in a dynamically-typed language such as Python or " "JavaScript, then you will be able to follow along just fine too." @@ -1168,7 +1400,7 @@ msgstr "" "如果你已经了解如 Python 或 JavaScript 等动态类型语言的编程，那么你也能够很好" "地跟上本课程。" -#: src/index.md:57 +#: src/index.md:59 msgid "" "This is an example of a _speaker note_. We will use these to add additional " "information to the slides. This could be key points which the instructor " @@ -1188,24 +1420,23 @@ msgid "" msgstr "以下是有关 Google 内部授课方式的一些背景信息。" #: src/running-the-course.md:8 +#, fuzzy msgid "" -"We typically run classes from 10:00 am to 4:00 pm, with a 1 hour lunch break " -"in the middle. This leaves 2.5 hours for the morning class and 2.5 hours for " -"the afternoon class. Note that this is just a recommendation: you can also " -"spend 3 hour on the morning session to give people more time for exercises. " -"The downside of longer session is that people can become very tired after 6 " -"full hours of class in the afternoon." +"We typically run classes from 9:00 am to 4:00 pm, with a 1 hour lunch break " +"in the middle. This leaves 3 hours for the morning class and 3 hours for the " +"afternoon class. Both sessions contain multiple breaks and time for students " +"to work on exercises." msgstr "" "上课时间通常是从上午 10:00 到下午 4:00，中间有 1 小时的午餐休息时间。这样，上" "午和下午各留了 2.5 小时的上课时间。请注意，这仅是建议：您也可以上午上课 3 小" "时，让学员有更多的时间进行练习。上课时间较长的缺点是，学员上了整整 6 小时的" "课，到了下午可能会非常疲倦。" -#: src/running-the-course.md:16 +#: src/running-the-course.md:13 msgid "Before you run the course, you will want to:" msgstr "在授课之前，你需要完成以下事项：" -#: src/running-the-course.md:18 +#: src/running-the-course.md:15 msgid "" "Make yourself familiar with the course material. We've included speaker " "notes to help highlight the key points (please help us by contributing more " @@ -1218,18 +1449,19 @@ msgstr "" "在“演讲者备注”旁边有一个小箭头）。这样，你就可以确保屏幕整洁有序，更好地向全" "班学员展示课程内容。" -#: src/running-the-course.md:24 +#: src/running-the-course.md:21 +#, fuzzy msgid "" -"Decide on the dates. Since the course takes at least three full days, we " -"recommend that you schedule the days over two weeks. Course participants " -"have said that they find it helpful to have a gap in the course since it " -"helps them process all the information we give them." +"Decide on the dates. Since the course takes four days, we recommend that you " +"schedule the days over two weeks. Course participants have said that they " +"find it helpful to have a gap in the course since it helps them process all " +"the information we give them." msgstr "" "确定培训日期。由于本课程至少需要三天的时间，因此我们建议你安排两周以上的时" "间。课程学员曾表示，在每堂课之间留一段间隔会很有帮助，因为这有利于他们吸收我" "们所提供的所有信息。" -#: src/running-the-course.md:29 +#: src/running-the-course.md:26 msgid "" "Find a room large enough for your in-person participants. We recommend a " "class size of 15-25 people. That's small enough that people are comfortable " @@ -1244,7 +1476,7 @@ msgstr "" "教室备有供你和学生使用的“课桌”：你们都需要能够坐下来并操作各自的笔记本电脑。" "特别是身为教师，你现场要进行大量编码，所以讲台对你来说用处不大。" -#: src/running-the-course.md:37 +#: src/running-the-course.md:34 msgid "" "On the day of your course, show up to the room a little early to set things " "up. We recommend presenting directly using `mdbook serve` running on your " @@ -1258,7 +1490,7 @@ msgstr "" "comprehensive-rust#building)）。这样可以确保你在切换页面时没有延迟，演示效果" "更好。当你或课程学员发现拼写错误时，你也可以使用笔记本电脑及时更正。" -#: src/running-the-course.md:43 +#: src/running-the-course.md:40 msgid "" "Let people solve the exercises by themselves or in small groups. We " "typically spend 30-45 minutes on exercises in the morning and in the " @@ -1273,13 +1505,13 @@ msgstr "" "助。如果你看到多位学员遇到同样的问题，请在班级集体进行讲解，并提供相应的解决" "方案，例如告诉大家在标准库的什么位置可以找到相关信息。" -#: src/running-the-course.md:51 +#: src/running-the-course.md:48 msgid "" "That is all, good luck running the course! We hope it will be as much fun " "for you as it has been for us!" msgstr "今天的分享就是这些，祝你授课顺利！希望你和我们一样，乐在其中！" -#: src/running-the-course.md:54 +#: src/running-the-course.md:51 msgid "" "Please [provide feedback](https://github.com/google/comprehensive-rust/" "discussions/86) afterwards so that we can keep improving the course. We " @@ -1297,42 +1529,35 @@ msgid "Rust Fundamentals" msgstr "Rust 基础知识" #: src/running-the-course/course-structure.md:7 +#, fuzzy msgid "" -"The first three days make up [Rust Fundaments](../welcome-day-1.md). The " -"days are fast paced and we cover a lot of ground:" +"The first four days make up [Rust Fundamentals](../welcome-day-1.md). The " +"days are fast paced and we cover a lot of ground!" msgstr "" "我们会在头三天介绍 [Rust 基础知识](../welcome-day-1.md)。这几天的步调会稍快," "因为我们要探讨许多层面:" #: src/running-the-course/course-structure.md:10 -msgid "Day 1: Basic Rust, syntax, control flow, creating and consuming values." -msgstr "第 1 天：Rust 基础知识、语法、控制流、创建及使用值。" - -#: src/running-the-course/course-structure.md:11 -msgid "" -"Day 2: Memory management, ownership, compound data types, and the standard " -"library." -msgstr "第 2 天：内存管理、所有权、复合数据类类型及标准库。" +#, fuzzy +msgid "{{%course outline Fundamentals}}" +msgstr "Rust 基础知识" #: src/running-the-course/course-structure.md:12 -msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." -msgstr "第 3 天：泛型、trait、错误处理、测试和不安全 Rust。" - -#: src/running-the-course/course-structure.md:14 msgid "Deep Dives" msgstr "深入探究" -#: src/running-the-course/course-structure.md:16 +#: src/running-the-course/course-structure.md:14 +#, fuzzy msgid "" -"In addition to the 3-day class on Rust Fundamentals, we cover some more " +"In addition to the 4-day class on Rust Fundamentals, we cover some more " "specialized topics:" msgstr "除了为期 3 天的“Rust 基础知识”课程外，我们还推出了一些专题课程：" -#: src/running-the-course/course-structure.md:19 +#: src/running-the-course/course-structure.md:17 msgid "Rust in Android" msgstr "Android 中的 Rust" -#: src/running-the-course/course-structure.md:21 +#: src/running-the-course/course-structure.md:19 msgid "" "The [Rust in Android](../android.md) deep dive is a half-day course on using " "Rust for Android platform development. This includes interoperability with " @@ -1341,7 +1566,7 @@ msgstr "" "[深入探究 Android](../android.md)课程为期半天，旨在介绍如何使用 Rust 进行 " "Android 平台开发。其中包括与 C、C++ 和 Java 的互操作性。" -#: src/running-the-course/course-structure.md:25 +#: src/running-the-course/course-structure.md:23 msgid "" "You will need an [AOSP checkout](https://source.android.com/docs/setup/" "download/downloading). Make a checkout of the [course repository](https://" @@ -1354,7 +1579,7 @@ msgstr "" "comprehensive-rust)， 然后将 `src/android/` 目录移至所签出的 AOSP 的根目录。" "这将确保 Android 构建系统能检测到 `src/android/` 中的 `Android.bp` 文件。" -#: src/running-the-course/course-structure.md:30 +#: src/running-the-course/course-structure.md:28 msgid "" "Ensure that `adb sync` works with your emulator or real device and pre-build " "all Android examples using `src/android/build_all.sh`. Read the script to " @@ -1364,11 +1589,31 @@ msgstr "" "sh` 预构建所有 Android 示例。请阅读脚本， 查看它所运行的命令，并确保这些命令" "能在你手动运行时正确执行。" +#: src/running-the-course/course-structure.md:35 +#, fuzzy +msgid "Rust in Chromium" +msgstr "Android 中的 Rust" + #: src/running-the-course/course-structure.md:37 +msgid "" +"The [Rust in Chromium](../chromium.md) deep dive is a half-day course on " +"using Rust as part of the Chromium browser. It includes using Rust in " +"Chromium's `gn` build system, bringing in third-party libraries (\"crates\") " +"and C++ interoperability." +msgstr "" + +#: src/running-the-course/course-structure.md:42 +msgid "" +"You will need to be able to build Chromium --- a debug, component build is " +"[recommended](../chromium/setup.md) for speed but any build will work. " +"Ensure that you can run the Chromium browser that you've built." +msgstr "" + +#: src/running-the-course/course-structure.md:46 msgid "Bare-Metal Rust" msgstr "裸金属 Rust" -#: src/running-the-course/course-structure.md:39 +#: src/running-the-course/course-structure.md:48 msgid "" "The [Bare-Metal Rust](../bare-metal.md) deep dive is a full day class on " "using Rust for bare-metal (embedded) development. Both microcontrollers and " @@ -1377,7 +1622,7 @@ msgstr "" "[深入探究裸金属 Rust](../bare-metal.md)课程为期一天，旨在介绍如何使用 Rust 进" "行裸金属（嵌入式）开发。其中涵盖了微控制器和应用处理器。" -#: src/running-the-course/course-structure.md:43 +#: src/running-the-course/course-structure.md:52 msgid "" "For the microcontroller part, you will need to buy the [BBC micro:bit]" "(https://microbit.org/) v2 development board ahead of time. Everybody will " @@ -1388,11 +1633,11 @@ msgstr "" "版开发板。每个人都需要安装多个软件包， 具体如[欢迎页面](../bare-metal.md)中所" "述。" -#: src/running-the-course/course-structure.md:48 +#: src/running-the-course/course-structure.md:57 msgid "Concurrency in Rust" msgstr "Rust 中的并发" -#: src/running-the-course/course-structure.md:50 +#: src/running-the-course/course-structure.md:59 msgid "" "The [Concurrency in Rust](../concurrency.md) deep dive is a full day class " "on classical as well as `async`/`await` concurrency." @@ -1400,7 +1645,7 @@ msgstr "" "[深入探究并发](../concurrency.md)课程为期一天，旨在介绍传统并发和 `async`/" "`await` 并发。" -#: src/running-the-course/course-structure.md:53 +#: src/running-the-course/course-structure.md:62 msgid "" "You will need a fresh crate set up and the dependencies downloaded and ready " "to go. You can then copy/paste the examples into `src/main.rs` to experiment " @@ -1409,11 +1654,11 @@ msgstr "" "你需要设置一个新 crate，下载所需的依赖项， 做好课前准备。然后，你可以将示例复" "制/粘贴到 `src/main.rs` 中， 以便对以下代码进行实验：" -#: src/running-the-course/course-structure.md:64 +#: src/running-the-course/course-structure.md:73 msgid "Format" msgstr "课程形式" -#: src/running-the-course/course-structure.md:66 +#: src/running-the-course/course-structure.md:75 msgid "" "The course is meant to be very interactive and we recommend letting the " "questions drive the exploration of Rust!" @@ -1473,7 +1718,37 @@ msgstr "" "com/hugojacob)、[@joaovicmendes](https://github.com/joaovicmendes) 和 " "[@henrif75](https://github.com/henrif75)。" -#: src/running-the-course/translations.md:7 +#: src/running-the-course/translations.md:8 +#, fuzzy +msgid "" +"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " +"by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" +"wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/" +"kongy), [@noahdragon](https://github.com/noahdragon), [@superwhd](https://" +"github.com/superwhd), [@SketchK](https://github.com/SketchK), and [@nodmp]" +"(https://github.com/nodmp)." +msgstr "" +"[简体中文版本](https://google.github.io/comprehensive-rust/zh-CN/) 译者：" +"[@suetfei](https://github.com/suetfei)、[@wnghl](https://github.com/wnghl), " +"[@anlunx](https://github.com/anlunx)、[@kongy](https://github.com/kongy), " +"[@noahdragon](https://github.com/noahdragon) 和 [@superwhd](https://github." +"com/superwhd)。" + +#: src/running-the-course/translations.md:10 +#, fuzzy +msgid "" +"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " +"by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" +"victorhsieh), [@mingyc](https://github.com/mingyc), [@kuanhungchen](https://" +"github.com/kuanhungchen), and [@johnathan79717](https://github.com/" +"johnathan79717)." +msgstr "" +"[繁体中文版本](https://google.github.io/comprehensive-rust/zh-TW/) 译者：" +"[@hueich](https://github.com/hueich)、[@victorhsieh](https://github.com/" +"victorhsieh)、[@mingyc](https://github.com/mingyc) 和 [@johnathan79717]" +"(https://github.com/johnathan79717)。" + +#: src/running-the-course/translations.md:12 msgid "" "[Korean](https://google.github.io/comprehensive-rust/ko/) by [@keispace]" "(https://github.com/keispace), [@jiyongp](https://github.com/jiyongp), and " @@ -1483,7 +1758,7 @@ msgstr "" "(https://github.com/keispace)、[@jiyongp](https://github.com/jiyongp) 和 " "[@jooyunghan](https://github.com/jooyunghan)。" -#: src/running-the-course/translations.md:8 +#: src/running-the-course/translations.md:13 msgid "" "[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid]" "(https://github.com/deavid)." @@ -1491,22 +1766,22 @@ msgstr "" "[西班牙语版本](https://google.github.io/comprehensive-rust/es/) 译者：" "[@deavid](https://github.com/deavid)。" -#: src/running-the-course/translations.md:10 +#: src/running-the-course/translations.md:15 msgid "" "Use the language picker in the top-right corner to switch between languages." msgstr "使用右上角的语言选择器切换语言。" -#: src/running-the-course/translations.md:12 +#: src/running-the-course/translations.md:17 msgid "Incomplete Translations" msgstr "未完成的翻译" -#: src/running-the-course/translations.md:14 +#: src/running-the-course/translations.md:19 msgid "" "There is a large number of in-progress translations. We link to the most " "recently updated translations:" msgstr "多数语言版本仍在翻译中。我们会提供最近更新的翻译的链接：" -#: src/running-the-course/translations.md:17 +#: src/running-the-course/translations.md:22 msgid "" "[Bengali](https://google.github.io/comprehensive-rust/bn/) by [@raselmandol]" "(https://github.com/raselmandol)." @@ -1514,33 +1789,7 @@ msgstr "" "[孟加拉语版本](https://google.github.io/comprehensive-rust/bn/) 译者：" "[@raselmandol](https://github.com/raselmandol)。" -#: src/running-the-course/translations.md:18 -msgid "" -"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " -"by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" -"victorhsieh), [@mingyc](https://github.com/mingyc), and [@johnathan79717]" -"(https://github.com/johnathan79717)." -msgstr "" -"[繁体中文版本](https://google.github.io/comprehensive-rust/zh-TW/) 译者：" -"[@hueich](https://github.com/hueich)、[@victorhsieh](https://github.com/" -"victorhsieh)、[@mingyc](https://github.com/mingyc) 和 [@johnathan79717]" -"(https://github.com/johnathan79717)。" - -#: src/running-the-course/translations.md:19 -msgid "" -"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " -"by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" -"wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/" -"kongy), [@noahdragon](https://github.com/noahdragon), and [@superwhd]" -"(https://github.com/superwhd)." -msgstr "" -"[简体中文版本](https://google.github.io/comprehensive-rust/zh-CN/) 译者：" -"[@suetfei](https://github.com/suetfei)、[@wnghl](https://github.com/wnghl), " -"[@anlunx](https://github.com/anlunx)、[@kongy](https://github.com/kongy), " -"[@noahdragon](https://github.com/noahdragon) 和 [@superwhd](https://github." -"com/superwhd)。" - -#: src/running-the-course/translations.md:20 +#: src/running-the-course/translations.md:23 msgid "" "[French](https://google.github.io/comprehensive-rust/fr/) by [@KookaS]" "(https://github.com/KookaS) and [@vcaen](https://github.com/vcaen)." @@ -1548,7 +1797,7 @@ msgstr "" "[法语版本](https://google.github.io/comprehensive-rust/fr/) 译者：[@KookaS]" "(https://github.com/KookaS) 和 [@vcaen](https://github.com/vcaen)。" -#: src/running-the-course/translations.md:21 +#: src/running-the-course/translations.md:24 msgid "" "[German](https://google.github.io/comprehensive-rust/de/) by [@Throvn]" "(https://github.com/Throvn) and [@ronaldfw](https://github.com/ronaldfw)." @@ -1556,7 +1805,7 @@ msgstr "" "[德语版本](https://google.github.io/comprehensive-rust/de/) 译者：[@Throvn]" "(https://github.com/Throvn) 和 [@ronaldfw](https://github.com/ronaldfw)。" -#: src/running-the-course/translations.md:22 +#: src/running-the-course/translations.md:25 msgid "" "[Japanese](https://google.github.io/comprehensive-rust/ja/) by [@CoinEZ-JPN]" "(https://github.com/CoinEZ) and [@momotaro1105](https://github.com/" @@ -1566,7 +1815,7 @@ msgstr "" "JPN](https://github.com/CoinEZ) 和 [@momotaro1105](https://github.com/" "momotaro1105)。" -#: src/running-the-course/translations.md:24 +#: src/running-the-course/translations.md:27 msgid "" "If you want to help with this effort, please see [our instructions](https://" "github.com/google/comprehensive-rust/blob/main/TRANSLATIONS.md) for how to " @@ -1590,15 +1839,15 @@ msgstr "" "绍一下什么是 Cargo、它如何融入更广泛的生态系统， 以及我们如何在本培训中合理利" "用 Cargo。" -#: src/cargo.md:8 +#: src/cargo.md:9 msgid "Installation" msgstr "安装" -#: src/cargo.md:10 +#: src/cargo.md:11 msgid "**Please follow the instructions on .**" msgstr "**请按照 上的说明操作。**" -#: src/cargo.md:12 +#: src/cargo.md:13 msgid "" "This will give you the Cargo build tool (`cargo`) and the Rust compiler " "(`rustc`). You will also get `rustup`, a command line utility that you can " @@ -1607,7 +1856,7 @@ msgstr "" "这将为你提供 Cargo 构建工具 (`cargo`)和 Rust 编译器 (`rustc`)。你还将获得 " "`rustup`，这是一个命令行实用程序,你可以用它来安装不同的编译器版本。" -#: src/cargo.md:14 +#: src/cargo.md:17 msgid "" "After installing Rust, you should configure your editor or IDE to work with " "Rust. Most editors do this by talking to [rust-analyzer](https://rust-" @@ -1624,7 +1873,7 @@ msgstr "" "html#vimneovim)及其他许多编辑器提供了自动补全及定义跳转的功能。同样也可以用一" "个叫[RustRover](https://www.jetbrains.com/rust/)的IDE。" -#: src/cargo.md:18 +#: src/cargo.md:25 msgid "" "On Debian/Ubuntu, you can also install Cargo, the Rust source and the [Rust " "formatter](https://github.com/rust-lang/rustfmt) via `apt`. However, this " @@ -1662,9 +1911,10 @@ msgstr "" "置的测试运行程序，用于执行单元测试。" #: src/cargo/rust-ecosystem.md:13 +#, fuzzy msgid "" "`rustup`: the Rust toolchain installer and updater. This tool is used to " -"install and update `rustc` and `cargo` when new versions of Rust is " +"install and update `rustc` and `cargo` when new versions of Rust are " "released. In addition, `rustup` can also download documentation for the " "standard library. You can have multiple versions of Rust installed at once " "and `rustup` will let you switch between them as needed." @@ -1673,14 +1923,10 @@ msgstr "" "更新 `rustc` 和 `cargo`。 此外，`rustup` 还可以下载标准库的文档。你可以同时安" "装多个版本的 Rust，并且 `rustup` 可让你根据需要在这些版本之间切换。" -#: src/cargo/rust-ecosystem.md:21 src/hello-world.md:25 -#: src/hello-world/small-example.md:27 src/why-rust/runtime.md:10 -#: src/why-rust/modern.md:21 src/basic-syntax/compound-types.md:32 -#: src/basic-syntax/references.md:24 -#: src/pattern-matching/destructuring-enums.md:35 -#: src/ownership/double-free-modern-cpp.md:55 -#: src/error-handling/try-operator.md:48 -#: src/error-handling/converting-error-types-example.md:50 +#: src/cargo/rust-ecosystem.md:21 src/hello-world/hello-world.md:25 +#: src/tuples-and-arrays/tuples-and-arrays.md:38 src/references/exclusive.md:19 +#: src/pattern-matching/destructuring.md:68 src/memory-management/move.md:152 +#: src/error-handling/try.md:52 src/android/setup.md:18 #: src/concurrency/threads.md:30 src/async/async-await.md:25 msgid "Key points:" msgstr "关键点：" @@ -1713,7 +1959,7 @@ msgstr "" "您也可以通过备用的[注册数据库](https://doc.rust-lang.org/cargo/reference/" "registries.html)、git及文件夹等资源来解析依赖项。" -#: src/cargo/rust-ecosystem.md:34 +#: src/cargo/rust-ecosystem.md:35 msgid "" "Rust also has [editions](https://doc.rust-lang.org/edition-guide/): the " "current edition is Rust 2021. Previous editions were Rust 2015 and Rust 2018." @@ -1721,13 +1967,13 @@ msgstr "" "Rust 也有三个\\[版本\\]：当前版本是 Rust 2021。之前的版本是 Rust 2015 和 " "Rust 2018。" -#: src/cargo/rust-ecosystem.md:37 +#: src/cargo/rust-ecosystem.md:38 msgid "" "The editions are allowed to make backwards incompatible changes to the " "language." msgstr "这些版本支持对语言进行向后不兼容的更改。" -#: src/cargo/rust-ecosystem.md:40 +#: src/cargo/rust-ecosystem.md:41 msgid "" "To prevent breaking code, editions are opt-in: you select the edition for " "your crate via the `Cargo.toml` file." @@ -1735,53 +1981,54 @@ msgstr "" "为防止破坏代码，你可以自行选择版本： 通过 `Cargo.toml` 文件为 crate 选择合适" "的版本。" -#: src/cargo/rust-ecosystem.md:43 +#: src/cargo/rust-ecosystem.md:44 msgid "" "To avoid splitting the ecosystem, Rust compilers can mix code written for " "different editions." msgstr "为免分割生态系统，Rust 编译器可以混合使用为不同版本编写的代码。" -#: src/cargo/rust-ecosystem.md:46 +#: src/cargo/rust-ecosystem.md:47 msgid "" "Mention that it is quite rare to ever use the compiler directly not through " "`cargo` (most users never do)." msgstr "" "提及不通过 `cargo` 而直接使用编译器的情况相当少见（大多数用户从不这样做）。" -#: src/cargo/rust-ecosystem.md:48 +#: src/cargo/rust-ecosystem.md:50 +#, fuzzy msgid "" "It might be worth alluding that Cargo itself is an extremely powerful and " -"comprehensive tool. It is capable of many advanced features including but " -"not limited to: " +"comprehensive tool. It is capable of many advanced features including but " +"not limited to:" msgstr "" "值得注意的是，Cargo 本身就是一个功能强大且全面的工具。它能够实现许多高级功" "能，包括但不限于：" -#: src/cargo/rust-ecosystem.md:49 +#: src/cargo/rust-ecosystem.md:53 msgid "Project/package structure" msgstr "项目/软件包结构" -#: src/cargo/rust-ecosystem.md:50 +#: src/cargo/rust-ecosystem.md:54 msgid "[workspaces](https://doc.rust-lang.org/cargo/reference/workspaces.html)" msgstr "\\[工作区\\]" -#: src/cargo/rust-ecosystem.md:51 +#: src/cargo/rust-ecosystem.md:55 msgid "Dev Dependencies and Runtime Dependency management/caching" msgstr "开发依赖项和运行时依赖项管理/缓存" -#: src/cargo/rust-ecosystem.md:52 +#: src/cargo/rust-ecosystem.md:56 msgid "" "[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts." "html)" msgstr "\\[构建脚本\\]" -#: src/cargo/rust-ecosystem.md:53 +#: src/cargo/rust-ecosystem.md:57 msgid "" "[global installation](https://doc.rust-lang.org/cargo/commands/cargo-install." "html)" msgstr "\\[全局安装\\] \\]" -#: src/cargo/rust-ecosystem.md:54 +#: src/cargo/rust-ecosystem.md:58 msgid "" "It is also extensible with sub command plugins as well (such as [cargo " "clippy](https://github.com/rust-lang/rust-clippy))." @@ -1789,7 +2036,7 @@ msgstr "" "它还可以使用子命令插件（例如 [cargo clippy](https://github.com/rust-lang/" "rust-clippy)）进行扩展。" -#: src/cargo/rust-ecosystem.md:55 +#: src/cargo/rust-ecosystem.md:60 msgid "" "Read more from the [official Cargo Book](https://doc.rust-lang.org/cargo/)" msgstr "如需了解详情，请参阅\\[ Cargo 官方图书\\]" @@ -1820,19 +2067,9 @@ msgstr "" msgid "The code blocks in this course are fully interactive:" msgstr "本课程中的代码块是完全交互式的：" -#: src/cargo/code-samples.md:13 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" +#: src/cargo/code-samples.md:15 src/cargo/running-locally.md:46 +msgid "\"Edit me!\"" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" #: src/cargo/code-samples.md:19 msgid "You can use " @@ -1840,7 +2077,7 @@ msgstr "当文本框为焦点时，你可以使用" #: src/cargo/code-samples.md:19 #, fuzzy -msgid "to execute the code when focus is in the text box." +msgid " to execute the code when focus is in the text box." msgstr "来执行代码。" #: src/cargo/code-samples.md:24 @@ -1885,34 +2122,34 @@ msgstr "" "这应会为你提供一个有效的 `rustc` 和 `cargo`。在撰写本文时，最新的 Rust 稳定版" "具有以下版本号：" -#: src/cargo/running-locally.md:15 +#: src/cargo/running-locally.md:16 msgid "" "You can use any later version too since Rust maintains backwards " "compatibility." msgstr "您也可以使用任何更高版本，因为 Rust 保持向后兼容性。" -#: src/cargo/running-locally.md:17 +#: src/cargo/running-locally.md:18 msgid "" "With this in place, follow these steps to build a Rust binary from one of " "the examples in this training:" msgstr "" "了解这些信息后，请按照以下步骤从本培训中的 一个示例中构建 Rust 二进制文件：" -#: src/cargo/running-locally.md:20 +#: src/cargo/running-locally.md:21 msgid "Click the \"Copy to clipboard\" button on the example you want to copy." msgstr "在你要复制的示例上点击“复制到剪贴板”按钮。" -#: src/cargo/running-locally.md:22 +#: src/cargo/running-locally.md:23 msgid "" "Use `cargo new exercise` to create a new `exercise/` directory for your code:" msgstr "使用 `cargo new exercise` 为你的代码新建一个 `exercise/` 目录：" -#: src/cargo/running-locally.md:29 +#: src/cargo/running-locally.md:30 msgid "" "Navigate into `exercise/` and use `cargo run` to build and run your binary:" msgstr "导航至 `exercise/` 并使用 `cargo run` 构建并运行你的二进制文件：" -#: src/cargo/running-locally.md:40 +#: src/cargo/running-locally.md:41 msgid "" "Replace the boiler-plate code in `src/main.rs` with your own code. For " "example, using the example on the previous page, make `src/main.rs` look like" @@ -1920,25 +2157,11 @@ msgstr "" "将 `src/main.rs` 中的样板代码替换为你自己的代码。例如， 使用上一页中的示例，" "将 `src/main.rs` 改为：" -#: src/cargo/running-locally.md:43 -msgid "" -"```rust\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" -msgstr "" -"```rust\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" - -#: src/cargo/running-locally.md:49 +#: src/cargo/running-locally.md:50 msgid "Use `cargo run` to build and run your updated binary:" msgstr "使用 `cargo run` 构建并运行你更新后的二进制文件：" -#: src/cargo/running-locally.md:59 +#: src/cargo/running-locally.md:60 msgid "" "Use `cargo check` to quickly check your project for errors, use `cargo " "build` to compile it without running it. You will find the output in `target/" @@ -1949,7 +2172,7 @@ msgstr "" "而不运行。你可以在 `target/debug/` 中找到常规调试 build 的输出。使用 `cargo " "build --release` 在 `target/release/` 中生成经过优化的 发布 build。" -#: src/cargo/running-locally.md:64 +#: src/cargo/running-locally.md:65 msgid "" "You can add dependencies for your project by editing `Cargo.toml`. When you " "run `cargo` commands, it will automatically download and compile missing " @@ -1958,7 +2181,7 @@ msgstr "" "你可以通过修改 `Cargo.toml` 为项目添加依赖项。当你 运行 `cargo` 命令时，系统" "会自动为你下载和编译缺失 的依赖项。" -#: src/cargo/running-locally.md:72 +#: src/cargo/running-locally.md:73 msgid "" "Try to encourage the class participants to install Cargo and use a local " "editor. It will make their life easier since they will have a normal " @@ -1977,7 +2200,7 @@ msgid "" "today:" msgstr "今天是学习 Comprehensive Rust 的第一天。我们会涉及很多内容：" -#: src/welcome-day-1.md:6 +#: src/welcome-day-1.md:5 msgid "" "Basic Rust syntax: variables, scalar and compound types, enums, structs, " "references, functions, and methods." @@ -1985,51 +2208,68 @@ msgstr "" "Rust 基本语法：变量、标量（scalar）和复合（compound）类型、枚举（Enum）、结构" "体（struct）、引用、函数和方法。" +#: src/welcome-day-1.md:7 +#, fuzzy +msgid "Types and type inference." +msgstr "类型推导" + +#: src/welcome-day-1.md:8 +msgid "Control flow constructs: loops, conditionals, and so on." +msgstr "" + #: src/welcome-day-1.md:9 -msgid "" -"Control flow constructs: `if`, `if let`, `while`, `while let`, `break`, and " -"`continue`." +msgid "User-defined types: structs and enums." msgstr "" -"控制流的构造：`if`、`if let`、`while`、`while let`、`break` 和 `continue`。" -#: src/welcome-day-1.md:12 +#: src/welcome-day-1.md:10 msgid "Pattern matching: destructuring enums, structs, and arrays." msgstr "模式匹配：解构枚举、结构体和数组（array）。" -#: src/welcome-day-1.md:16 +#: src/welcome-day-1.md:12 src/welcome-day-2.md:12 src/welcome-day-3.md:9 +#: src/welcome-day-4.md:11 +msgid "Schedule" +msgstr "" + +#: src/welcome-day-1.md:14 src/welcome-day-1-afternoon.md:3 +#: src/welcome-day-2.md:14 src/welcome-day-2-afternoon.md:3 +#: src/welcome-day-3.md:11 src/welcome-day-3-afternoon.md:3 +#: src/welcome-day-4.md:13 src/welcome-day-4-afternoon.md:3 +msgid "{{%session outline}}" +msgstr "" + +#: src/welcome-day-1.md:18 msgid "Please remind the students that:" msgstr "请提醒学生：" -#: src/welcome-day-1.md:18 +#: src/welcome-day-1.md:20 msgid "" "They should ask questions when they get them, don't save them to the end." msgstr "他们可以随时提问，不需要留到最后。" -#: src/welcome-day-1.md:19 +#: src/welcome-day-1.md:21 msgid "" "The class is meant to be interactive and discussions are very much " "encouraged!" msgstr "这个课程本应该是互动的，我们鼓励大家积极讨论。" -#: src/welcome-day-1.md:20 +#: src/welcome-day-1.md:22 #, fuzzy msgid "" "As an instructor, you should try to keep the discussions relevant, i.e., " -"keep the discussions related to how Rust does things vs some other " -"language. It can be hard to find the right balance, but err on the side of " -"allowing discussions since they engage people much more than one-way " -"communication." +"keep the discussions related to how Rust does things vs some other language. " +"It can be hard to find the right balance, but err on the side of allowing " +"discussions since they engage people much more than one-way communication." msgstr "" "作为讲师，你应该尽量保证讨论话题的相关性，例如，讨论围绕Rust是如何做某些事" "情，而不是其他的语言如何如何。 这个平衡点不容易找到，但是尽量倾向于允许讨论，" "因为讨论比起单方面的灌输更有利于让大家投入。" -#: src/welcome-day-1.md:24 +#: src/welcome-day-1.md:26 msgid "" "The questions will likely mean that we talk about things ahead of the slides." msgstr "有些问题会导致我们提前谈到后面的内容。" -#: src/welcome-day-1.md:25 +#: src/welcome-day-1.md:27 msgid "" "This is perfectly okay! Repetition is an important part of learning. " "Remember that the slides are just a support and you are free to skip them as " @@ -2038,40 +2278,33 @@ msgstr "" "这完全没有问题！重复是学习的一个重要方法。请记住，这些幻灯片只是一种辅助，你" "可以选择性地跳过。" -#: src/welcome-day-1.md:29 +#: src/welcome-day-1.md:31 msgid "" -"The idea for the first day is to show _just enough_ of Rust to be able to " -"speak about the famous borrow checker. The way Rust handles memory is a " -"major feature and we should show students this right away." +"The idea for the first day is to show the \"basic\" things in Rust that " +"should have immediate parallels in other languages. The more advanced parts " +"of Rust come on the subsequent days." msgstr "" -"第一天的主要目标是要谈到著名的 borrow checker，其他方面点到为止。Rust 处理内" -"存的方式是其主要特点，这点我们应该尽早展示给学生。" -#: src/welcome-day-1.md:33 +#: src/welcome-day-1.md:35 msgid "" "If you're teaching this in a classroom, this is a good place to go over the " -"schedule. We suggest splitting the day into two parts (following the slides):" +"schedule. Note that there is an exercise at the end of each segment, " +"followed by a break. Plan to cover the exercise solution after the break. " +"The times listed here are a suggestion in order to keep the course on " +"schedule. Feel free to be flexible and adjust as necessary!" msgstr "" -"如果你是在教室里教授此课程，不妨在这里介绍一下时间安排。 这边建议是把每天分成" -"两部分（跟着幻灯片来）：" -#: src/welcome-day-1.md:36 -msgid "Morning: 9:00 to 12:00," -msgstr "早上：9:00 到 12:00，" - -#: src/welcome-day-1.md:37 -msgid "Afternoon: 13:00 to 16:00." -msgstr "下午：13:00 到 16:00。" - -#: src/welcome-day-1.md:39 -msgid "" -"You can of course adjust this as necessary. Please make sure to include " -"breaks, we recommend a break every hour!" +#: src/hello-world.md:3 src/types-and-values.md:3 src/control-flow-basics.md:3 +#: src/tuples-and-arrays.md:3 src/references.md:3 src/user-defined-types.md:3 +#: src/pattern-matching.md:3 src/methods-and-traits.md:3 src/generics.md:3 +#: src/std-types.md:3 src/std-traits.md:3 src/memory-management.md:3 +#: src/smart-pointers.md:3 src/borrowing.md:3 src/slices-and-lifetimes.md:3 +#: src/iterators.md:3 src/modules.md:3 src/testing.md:3 src/error-handling.md:3 +#: src/unsafe-rust.md:3 +msgid "{{%segment outline}}" msgstr "" -"当然你也可以看情况调整时间。但是请务必记得提供休息时间。我们建议每个小时休息" -"一次！" -#: src/welcome-day-1/what-is-rust.md:3 +#: src/hello-world/what-is-rust.md:3 msgid "" "Rust is a new programming language which had its [1.0 release in 2015]" "(https://blog.rust-lang.org/2015/05/15/Rust-1.0.html):" @@ -2079,15 +2312,15 @@ msgstr "" "Rust 是一门新的编程语言，它的[1.0 版本于 2015 年发布](https://blog.rust-lang." "org/2015/05/15/Rust-1.0.html)：" -#: src/welcome-day-1/what-is-rust.md:5 +#: src/hello-world/what-is-rust.md:5 msgid "Rust is a statically compiled language in a similar role as C++" msgstr "Rust 是一门静态编译语言，其功能定位与 C++ 相似" -#: src/welcome-day-1/what-is-rust.md:6 +#: src/hello-world/what-is-rust.md:6 msgid "`rustc` uses LLVM as its backend." msgstr "`rustc` 使用 LLVM 作为它的后端。" -#: src/welcome-day-1/what-is-rust.md:7 +#: src/hello-world/what-is-rust.md:7 msgid "" "Rust supports many [platforms and architectures](https://doc.rust-lang.org/" "nightly/rustc/platform-support.html):" @@ -2095,118 +2328,108 @@ msgstr "" "Rust 支持多种[平台和架构](https://doc.rust-lang.org/nightly/rustc/platform-" "support.html):" -#: src/welcome-day-1/what-is-rust.md:9 +#: src/hello-world/what-is-rust.md:9 msgid "x86, ARM, WebAssembly, ..." msgstr "x86、ARM、WebAssembly......" -#: src/welcome-day-1/what-is-rust.md:10 +#: src/hello-world/what-is-rust.md:10 msgid "Linux, Mac, Windows, ..." msgstr "Linux、Mac、Windows......" -#: src/welcome-day-1/what-is-rust.md:11 +#: src/hello-world/what-is-rust.md:11 msgid "Rust is used for a wide range of devices:" msgstr "Rust 被广泛用于各种设备中：" -#: src/welcome-day-1/what-is-rust.md:12 +#: src/hello-world/what-is-rust.md:12 msgid "firmware and boot loaders," msgstr "固件和引导程序，" -#: src/welcome-day-1/what-is-rust.md:13 +#: src/hello-world/what-is-rust.md:13 msgid "smart displays," msgstr "智能显示器，" -#: src/welcome-day-1/what-is-rust.md:14 +#: src/hello-world/what-is-rust.md:14 msgid "mobile phones," msgstr "手机，" -#: src/welcome-day-1/what-is-rust.md:15 +#: src/hello-world/what-is-rust.md:15 msgid "desktops," msgstr "桌面，" -#: src/welcome-day-1/what-is-rust.md:16 +#: src/hello-world/what-is-rust.md:16 msgid "servers." msgstr "服务器。" -#: src/welcome-day-1/what-is-rust.md:21 +#: src/hello-world/what-is-rust.md:20 msgid "Rust fits in the same area as C++:" msgstr "Rust 和 C++ 适用于类似的场景：" -#: src/welcome-day-1/what-is-rust.md:23 +#: src/hello-world/what-is-rust.md:22 msgid "High flexibility." msgstr "极高的灵活性。" -#: src/welcome-day-1/what-is-rust.md:24 +#: src/hello-world/what-is-rust.md:23 msgid "High level of control." msgstr "高度的控制能力。" -#: src/welcome-day-1/what-is-rust.md:25 +#: src/hello-world/what-is-rust.md:24 msgid "" "Can be scaled down to very constrained devices such as microcontrollers." msgstr "能够在资源匮乏的设备（如手机）上运行。" -#: src/welcome-day-1/what-is-rust.md:26 +#: src/hello-world/what-is-rust.md:25 msgid "Has no runtime or garbage collection." msgstr "没有运行时和垃圾收集。" -#: src/welcome-day-1/what-is-rust.md:27 +#: src/hello-world/what-is-rust.md:26 msgid "Focuses on reliability and safety without sacrificing performance." msgstr "关注程序可靠性和安全性，而不会牺牲任何性能。" -#: src/hello-world.md:3 +#: src/hello-world/hello-world.md:3 msgid "" "Let us jump into the simplest possible Rust program, a classic Hello World " "program:" msgstr "让我们进入最简单的 Rust 程序，一个经典的 Hello World 程序：" -#: src/hello-world.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Hello 🌍!\");\n" -"}\n" -"```" +#: src/hello-world/hello-world.md:8 +msgid "\"Hello 🌍!\"" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Hello 🌍!\");\n" -"}\n" -"```" -#: src/hello-world.md:12 +#: src/hello-world/hello-world.md:12 msgid "What you see:" msgstr "你看到的：" -#: src/hello-world.md:14 +#: src/hello-world/hello-world.md:14 msgid "Functions are introduced with `fn`." msgstr "函数以 `fn` 开头。" -#: src/hello-world.md:15 +#: src/hello-world/hello-world.md:15 msgid "Blocks are delimited by curly braces like in C and C++." msgstr "像 C 和 C++ 一样，块由花括号分隔。" -#: src/hello-world.md:16 +#: src/hello-world/hello-world.md:16 msgid "The `main` function is the entry point of the program." msgstr "`main` 函数是程序的入口点。" -#: src/hello-world.md:17 +#: src/hello-world/hello-world.md:17 msgid "Rust has hygienic macros, `println!` is an example of this." msgstr "Rust 有卫生宏 (hygienic macros)，`println!` 就是一个例子。" -#: src/hello-world.md:18 +#: src/hello-world/hello-world.md:18 msgid "Rust strings are UTF-8 encoded and can contain any Unicode character." msgstr "Rust 字符串是 UTF-8 编码的，可以包含任何 Unicode 字符。" -#: src/hello-world.md:22 +#: src/hello-world/hello-world.md:22 #, fuzzy msgid "" "This slide tries to make the students comfortable with Rust code. They will " -"see a ton of it over the next three days so we start small with something " +"see a ton of it over the next four days so we start small with something " "familiar." msgstr "" "这张幻灯片试图让学生们熟悉 Rust 代码。在接下来的四天里，他们会看到很多 Rust " "代码, 所以我们从一些熟悉的东西开始。" -#: src/hello-world.md:27 +#: src/hello-world/hello-world.md:27 #, fuzzy msgid "" "Rust is very much like other languages in the C/C++/Java tradition. It is " @@ -2215,19 +2438,20 @@ msgstr "" "Rust 非常像 C/C++/Java 等其他传统语言。它是指令式语言（而非函数式），而且除非" "绝对必要，它不会尝试重新发明新的概念。" -#: src/hello-world.md:31 +#: src/hello-world/hello-world.md:30 msgid "Rust is modern with full support for things like Unicode." msgstr "Rust 是一门现代编程语言，它完全支持 Unicode 等特性。" -#: src/hello-world.md:33 +#: src/hello-world/hello-world.md:32 +#, fuzzy msgid "" "Rust uses macros for situations where you want to have a variable number of " -"arguments (no function [overloading](basic-syntax/functions-interlude.md))." +"arguments (no function [overloading](../control-flow-basics/functions.md))." msgstr "" "在需要处理可变数量的参数的情况下，Rust 使用宏（没有函数[重载](basic-syntax/" "functions-interlude.md)）。" -#: src/hello-world.md:36 +#: src/hello-world/hello-world.md:35 msgid "" "Macros being 'hygienic' means they don't accidentally capture identifiers " "from the scope they are used in. Rust macros are actually only [partially " @@ -2238,7 +2462,7 @@ msgstr "" "Rust 的宏只是[部分卫生](https://veykril.github.io/tlborm/decl-macros/" "minutiae/hygiene.html)。" -#: src/hello-world.md:40 +#: src/hello-world/hello-world.md:39 msgid "" "Rust is multi-paradigm. For example, it has powerful [object-oriented " "programming features](https://doc.rust-lang.org/book/ch17-00-oop.html), and, " @@ -2249,117 +2473,109 @@ msgstr "" "rust-lang.org/book/ch17-00-oop.html)，虽然它不是函数式语言，但包括一系列的[函" "数概念](https://doc.rust-lang.org/book/ch13-00-functional-features.html)。" -#: src/hello-world/small-example.md:3 -msgid "Here is a small example program in Rust:" -msgstr "以下是一个简短的 Rust 示例程序：" - -#: src/hello-world/small-example.md:5 -msgid "" -"```rust,editable\n" -"fn main() { // Program entry point\n" -" let mut x: i32 = 6; // Mutable variable binding\n" -" print!(\"{x}\"); // Macro for printing, like printf\n" -" while x != 1 { // No parenthesis around expression\n" -" if x % 2 == 0 { // Math like in other languages\n" -" x = x / 2;\n" -" } else {\n" -" x = 3 * x + 1;\n" -" }\n" -" print!(\" -> {x}\");\n" -" }\n" -" println!();\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"fn main() { // 程序入口\n" -" let mut x: i32 = 6; // 可变变量绑定\n" -" print!(\"{x}\"); // 与 printf 类似的输出宏\n" -" while x != 1 { // 表达式周围没有括号\n" -" if x % 2 == 0 { // 与其他语言类似的数值计算\n" -" x = x / 2;\n" -" } else {\n" -" x = 3 * x + 1;\n" -" }\n" -" print!(\" -> {x}\");\n" -" }\n" -" println!();\n" -"}\n" -"```" +#: src/hello-world/benefits.md:3 +msgid "Some unique selling points of Rust:" +msgstr "Rust 有一些独特的卖点：" -#: src/hello-world/small-example.md:23 +#: src/hello-world/benefits.md:5 msgid "" -"The code implements the Collatz conjecture: it is believed that the loop " -"will always end, but this is not yet proved. Edit the code and play with " -"different inputs." +"_Compile time memory safety_ - whole classes of memory bugs are prevented at " +"compile time" msgstr "" -"这段代码实现了 Collatz 猜想：猜想认为该循环总是会结束，但该猜想还没有被证明。" -"可以编辑代码来尝试不同的输入。" -#: src/hello-world/small-example.md:29 -msgid "" -"Explain that all variables are statically typed. Try removing `i32` to " -"trigger type inference. Try with `i8` instead and trigger a runtime integer " -"overflow." -msgstr "" -"说明所有变量的类型都是静态的。尝试删除 `i32` 来触发类型推断。尝试使用 `i8` 来" -"触发运行时整数溢出。" +#: src/hello-world/benefits.md:7 +msgid "No uninitialized variables." +msgstr "不存在未初始化的变量。" -#: src/hello-world/small-example.md:32 -msgid "Change `let mut x` to `let x`, discuss the compiler error." -msgstr "将 `let mut x` 改为 `let x`，讨论出现的编译错误。" +#: src/hello-world/benefits.md:8 +msgid "No double-frees." +msgstr "不存在“双重释放”。" -#: src/hello-world/small-example.md:34 -msgid "" -"Show how `print!` gives a compilation error if the arguments don't match the " -"format string." -msgstr "展示 `print!` 在参数与格式字符串不匹配时产生的编译错误。" +#: src/hello-world/benefits.md:9 +msgid "No use-after-free." +msgstr "不存在“释放后使用”。" -#: src/hello-world/small-example.md:37 -msgid "" -"Show how you need to use `{}` as a placeholder if you want to print an " -"expression which is more complex than just a single variable." -msgstr "展示如何使用 `{}` 作为占位符，来输出比单个变量更复杂的表达式。" +#: src/hello-world/benefits.md:10 +msgid "No `NULL` pointers." +msgstr "不存在 `NULL` 指针。" + +#: src/hello-world/benefits.md:11 +msgid "No forgotten locked mutexes." +msgstr "不存在被遗忘的互斥锁。" + +#: src/hello-world/benefits.md:12 +msgid "No data races between threads." +msgstr "不存在线程之间的数据竞争。" + +#: src/hello-world/benefits.md:13 +msgid "No iterator invalidation." +msgstr "不存在迭代器失效。" -#: src/hello-world/small-example.md:40 +#: src/hello-world/benefits.md:15 msgid "" -"Show the students the standard library, show them how to search for `std::" -"fmt` which has the rules of the formatting mini-language. It's important " -"that the students become familiar with searching in the standard library." +"_No undefined runtime behavior_ - what a Rust statement does is never left " +"unspecified" msgstr "" -"向学生展示标准库，展示如何搜索 `std::fmt`，其中包含用于格式化字符串的微型语言" -"规则。要点是让学生熟悉在标准库中搜索的过程。" -#: src/hello-world/small-example.md:44 +#: src/hello-world/benefits.md:17 +msgid "Array access is bounds checked." +msgstr "数组访问有边界检查。" + +#: src/hello-world/benefits.md:18 +msgid "Integer overflow is defined (panic or wrap-around)." +msgstr "整数溢出有明确定义（panic 或回绕）。" + +#: src/hello-world/benefits.md:20 msgid "" -"In a shell `rustup doc std::fmt` will open a browser on the local std::fmt " -"documentation" +"_Modern language features_ - as expressive and ergonomic as higher-level " +"languages" msgstr "" -"在 shell 中，运行 `rustup doc std::fmt` 会在浏览器中打开本地 std::fmt 文档" -#: src/why-rust.md:3 -msgid "Some unique selling points of Rust:" -msgstr "Rust 有一些独特的卖点：" +#: src/hello-world/benefits.md:22 +msgid "Enums and pattern matching." +msgstr "枚举和模式匹配。" + +#: src/hello-world/benefits.md:23 +msgid "Generics." +msgstr "泛型。" + +#: src/hello-world/benefits.md:24 +msgid "No overhead FFI." +msgstr "无额外开销的外部函数接口（FFI）。" + +#: src/hello-world/benefits.md:25 +msgid "Zero-cost abstractions." +msgstr "零成本抽象。" -#: src/why-rust.md:5 -msgid "Compile time memory safety." -msgstr "编译期内存安全。" +#: src/hello-world/benefits.md:26 +msgid "Great compiler errors." +msgstr "强大的编译器错误提示。" + +#: src/hello-world/benefits.md:27 +msgid "Built-in dependency manager." +msgstr "内置依赖管理器。" + +#: src/hello-world/benefits.md:28 +msgid "Built-in support for testing." +msgstr "对测试的内置支持。" -#: src/why-rust.md:6 -msgid "Lack of undefined runtime behavior." -msgstr "没有运行时未定义行为。" +#: src/hello-world/benefits.md:29 +msgid "Excellent Language Server Protocol support." +msgstr "优秀的语言服务协议（Language Server Protocol）支持。" -#: src/why-rust.md:7 -msgid "Modern language features." -msgstr "现代的编程语言特性。" +#: src/hello-world/benefits.md:33 +msgid "" +"Do not spend much time here. All of these points will be covered in more " +"depth later." +msgstr "" -#: src/why-rust.md:11 +#: src/hello-world/benefits.md:36 msgid "" "Make sure to ask the class which languages they have experience with. " "Depending on the answer you can highlight different features of Rust:" msgstr "应该问问学生们都使用过哪些语言。根据答案侧重讲解 Rust 的不同特性：" -#: src/why-rust.md:14 +#: src/hello-world/benefits.md:39 msgid "" "Experience with C or C++: Rust eliminates a whole class of _runtime errors_ " "via the borrow checker. You get performance like in C and C++, but you don't " @@ -2370,7 +2586,7 @@ msgstr "" "和 C++ 的性能，而没有内存不安全的问题。并且你还可以得到些现代的语言构造，比如" "模式匹配和内置依赖管理。" -#: src/why-rust.md:19 +#: src/hello-world/benefits.md:44 msgid "" "Experience with Java, Go, Python, JavaScript...: You get the same memory " "safety as in those languages, plus a similar high-level language feeling. In " @@ -2381,605 +2597,175 @@ msgstr "" "特性，并拥有类似的使用高级语言的感受。同时你可以得到类似 C 和 C++ 的高速且可" "预测的执行性能（无垃圾回收机制），以及在需要时对底层硬件的访问。" -#: src/why-rust/an-example-in-c.md:4 -msgid "Let's consider the following \"minimum wrong example\" program in C:" -msgstr "让我们查看以下 C 语言的“最小错误示例”程序：" - -#: src/why-rust/an-example-in-c.md:6 +#: src/hello-world/playground.md:3 msgid "" -"```c,editable\n" -"#include \n" -"#include \n" -"#include \n" -"\n" -"int main(int argc, char* argv[]) {\n" -"\tchar *buf, *filename;\n" -"\tFILE *fp;\n" -"\tsize_t bytes, len;\n" -"\tstruct stat st;\n" -"\n" -"\tswitch (argc) {\n" -"\t\tcase 1:\n" -"\t\t\tprintf(\"Too few arguments!\\n\");\n" -"\t\t\treturn 1;\n" -"\n" -"\t\tcase 2:\n" -"\t\t\tfilename = argv[argc];\n" -"\t\t\tstat(filename, &st);\n" -"\t\t\tlen = st.st_size;\n" -"\t\t\t\n" -"\t\t\tbuf = (char*)malloc(len);\n" -"\t\t\tif (!buf)\n" -"\t\t\t\tprintf(\"malloc failed!\\n\", len);\n" -"\t\t\t\treturn 1;\n" -"\n" -"\t\t\tfp = fopen(filename, \"rb\");\n" -"\t\t\tbytes = fread(buf, 1, len, fp);\n" -"\t\t\tif (bytes = st.st_size)\n" -"\t\t\t\tprintf(\"%s\", buf);\n" -"\t\t\telse\n" -"\t\t\t\tprintf(\"fread failed!\\n\");\n" -"\n" -"\t\tcase 3:\n" -"\t\t\tprintf(\"Too many arguments!\\n\");\n" -"\t\t\treturn 1;\n" -"\t}\n" -"\n" -"\treturn 0;\n" -"}\n" -"```" +"The [Rust Playground](https://play.rust-lang.org/) provides an easy way to " +"run short Rust programs, and is the basis for the examples and exercises in " +"this course. Try running the \"hello-world\" program it starts with. It " +"comes with a few handy features:" msgstr "" -#: src/why-rust/an-example-in-c.md:48 -msgid "How many bugs do you spot?" -msgstr "你发现了多少 bug？" - -#: src/why-rust/an-example-in-c.md:52 +#: src/hello-world/playground.md:8 msgid "" -"Despite just 29 lines of code, this C example contains serious bugs in at " -"least 11:" -msgstr "尽管该 C 语言示例仅有29行代码，但它却包含了至少11个严重 bug：" +"Under \"Tools\", use the `rustfmt` option to format your code in the " +"\"standard\" way." +msgstr "" -#: src/why-rust/an-example-in-c.md:54 -msgid "Assignment `=` instead of equality comparison `==` (line 28)" -msgstr "使用赋值 `=` 而非判断相等 `==`（第28行）" - -#: src/why-rust/an-example-in-c.md:55 -msgid "Excess argument to `printf` (line 23)" -msgstr "`printf` 有多余参数（第23行）" - -#: src/why-rust/an-example-in-c.md:56 -msgid "File descriptor leak (after line 26)" -msgstr "文件描述符泄露（第26行之后）" - -#: src/why-rust/an-example-in-c.md:57 -msgid "Forgotten braces in multi-line `if` (line 22)" -msgstr "多行 `if` 语句缺少花括号（第22行）" - -#: src/why-rust/an-example-in-c.md:58 -msgid "Forgotten `break` in a `switch` statement (line 32)" -msgstr "`switch` 语句忘记添加 `break`（第32行）" - -#: src/why-rust/an-example-in-c.md:59 -msgid "" -"Forgotten NUL-termination of the `buf` string, leading to a buffer overflow " -"(line 29)" -msgstr "`buf` 字符串忘记NUL终止符，从而导致缓冲区溢出（第29行）" - -#: src/why-rust/an-example-in-c.md:60 -msgid "Memory leak by not freeing the `malloc`\\-allocated buffer (line 21)" -msgstr "未释放由 `malloc` 分配的缓冲区，从而导致内存泄漏（第21行）" - -#: src/why-rust/an-example-in-c.md:61 -msgid "Out-of-bounds access (line 17)" -msgstr "越界访问（第17行）" - -#: src/why-rust/an-example-in-c.md:62 -msgid "Unchecked cases in the `switch` statement (line 11)" -msgstr "`switch` 语句存在未检查的情况（第11行）" - -#: src/why-rust/an-example-in-c.md:63 -msgid "Unchecked return values of `stat` and `fopen` (lines 18 and 26)" -msgstr "`stat` 和 `fopen` 存在未检查的返回值（第18行及第26行）" - -#: src/why-rust/an-example-in-c.md:65 -msgid "" -"_Shouldn't these bugs be obvious even for a C compiler?_ \n" -"No, surprisingly this code compiles warning-free at the default warning " -"level, even in the latest GCC version (13.2 as of writing)." -msgstr "" -"_即使对于 C 语言编译器，这些bug难道不应该是显而易见的吗？_ \n" -"惊人的是，即便使用最新版本的GCC（截至撰文时为13.2），在默认警告等级下编译代码" -"时也不出现任何警告。" - -#: src/why-rust/an-example-in-c.md:68 -msgid "" -"_Isn't this a highly unrealistic example?_ \n" -"Absolutely not, these kind of bugs have lead to serious security " -"vulnerabilities in the past. Some examples:" -msgstr "" -"_这是非常极端的示例吗？_ \n" -"当然不是。这些类型的bug在过去曾引发一系列的安全漏洞，比如以下案例：" - -#: src/why-rust/an-example-in-c.md:71 -msgid "" -"Assignment `=` instead of equality comparison `==`: [The Linux Backdoor " -"Attempt of 2003](https://freedom-to-tinker.com/2013/10/09/the-linux-backdoor-" -"attempt-of-2003)" -msgstr "" -"使用赋值 `=` 而非判断相等 `==`：[2003年Linux后门尝试](https://freedom-to-" -"tinker.com/2013/10/09/the-linux-backdoor-attempt-of-2003)" - -#: src/why-rust/an-example-in-c.md:72 -msgid "" -"Forgotten braces in multi-line `if`: [The Apple goto fail vulnerability]" -"(https://dwheeler.com/essays/apple-goto-fail.html)" -msgstr "" -"多行 `if` 语句缺少花括号：[Apple goto失败漏洞](https://dwheeler.com/essays/" -"apple-goto-fail.html)" - -#: src/why-rust/an-example-in-c.md:73 -msgid "" -"Forgotten `break` in a `switch` statement: [The break that broke sudo]" -"(https://nakedsecurity.sophos.com/2012/05/21/anatomy-of-a-security-hole-the-" -"break-that-broke-sudo)" -msgstr "" -"`switch` 语句忘记添加 `break`：[破坏sudo的break](https://nakedsecurity." -"sophos.com/2012/05/21/anatomy-of-a-security-hole-the-break-that-broke-sudo)" - -#: src/why-rust/an-example-in-c.md:75 -msgid "" -"_How is Rust any better here?_ \n" -"Safe Rust makes all of these bugs impossible:" -msgstr "" -"_Rust在这些方面表现得怎么样？_ \n" -"安全Rust使这些bug的出现变得不可能：" - -#: src/why-rust/an-example-in-c.md:78 -msgid "Assignments inside an `if` clause are not supported." -msgstr "不支持 `if` 语句内赋值。" - -#: src/why-rust/an-example-in-c.md:79 -msgid "Format strings are checked at compile-time." -msgstr "编译时检查格式化字符串。" - -#: src/why-rust/an-example-in-c.md:80 -msgid "Resources are freed at the end of scope via the `Drop` trait." -msgstr "在作用域末尾，Rust通过 `Drop` trait 来释放资源。" - -#: src/why-rust/an-example-in-c.md:81 -msgid "All `if` clauses require braces." -msgstr "所有 `if` 语句必须有花括号。" - -#: src/why-rust/an-example-in-c.md:82 -msgid "" -"`match` (as the Rust equivalent to `switch`) does not fall-through, hence " -"you can't accidentally forget a `break`." -msgstr "" -"`match` 语句（在 Rust 中相当于 `switch`）并不会落空，因此你不会意外忘记一个 " -"`break`。" - -#: src/why-rust/an-example-in-c.md:83 -msgid "Buffer slices carry their size and don't rely on a NUL terminator." -msgstr "缓冲区切片自带它们的大小，且不依赖NUL终止符。" - -#: src/why-rust/an-example-in-c.md:84 -msgid "" -"Heap-allocated memory is freed via the `Drop` trait when the corresponding " -"`Box` leaves the scope." -msgstr "当相关 `Box` 离开作用域时，Rust 通过 `Drop` trait 释放堆分配内存。" - -#: src/why-rust/an-example-in-c.md:85 -msgid "" -"Out-of-bounds accesses cause a panic or can be checked via the `get` method " -"of a slice." -msgstr "" -"越界访问会导致程序发生 panic 而终止，也可以用 `get` 方法来检查一个序列是否越" -"界。" - -#: src/why-rust/an-example-in-c.md:86 -msgid "`match` mandates that all cases are handled." -msgstr "`match` 语句规定要处理所有情况。" - -#: src/why-rust/an-example-in-c.md:87 -msgid "" -"Fallible Rust functions return `Result` values that need to be unwrapped and " -"thereby checked for success. Additionally, the compiler emits a warning if " -"you miss to check the return value of a function marked with `#[must_use]`." -msgstr "" -"可出错的 Rust 函数返回的 `Result` 值需要拆箱并检查是否成功。此外，如果你忽略" -"检查标注为 `#[must_use]` 的函数的返回值，编译器会发出警告。" - -#: src/why-rust/compile-time.md:3 -msgid "Static memory management at compile time:" -msgstr "编译期静态内存管理：" - -#: src/why-rust/compile-time.md:5 -msgid "No uninitialized variables." -msgstr "不存在未初始化的变量。" - -#: src/why-rust/compile-time.md:6 -msgid "No memory leaks (_mostly_, see notes)." -msgstr "不存在内存泄漏（_通常情况下_，见注释）。" - -#: src/why-rust/compile-time.md:7 -msgid "No double-frees." -msgstr "不存在“双重释放”。" - -#: src/why-rust/compile-time.md:8 -msgid "No use-after-free." -msgstr "不存在“释放后使用”。" - -#: src/why-rust/compile-time.md:9 -msgid "No `NULL` pointers." -msgstr "不存在 `NULL` 指针。" - -#: src/why-rust/compile-time.md:10 -msgid "No forgotten locked mutexes." -msgstr "不存在被遗忘的互斥锁。" - -#: src/why-rust/compile-time.md:11 -msgid "No data races between threads." -msgstr "不存在线程之间的数据竞争。" - -#: src/why-rust/compile-time.md:12 -msgid "No iterator invalidation." -msgstr "不存在迭代器失效。" - -#: src/why-rust/compile-time.md:16 -msgid "" -"It is possible to produce memory leaks in (safe) Rust. Some examples are:" -msgstr "在（安全的）Rust 中也有可能产生内存泄漏。例如：" - -#: src/why-rust/compile-time.md:19 -msgid "" -"You can use [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." -"html#method.leak) to leak a pointer. A use of this could be to get runtime-" -"initialized and runtime-sized static variables" -msgstr "" -"可以使用 [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." -"html#method.leak) 来泄漏一个指针。该方法可以用于得到在运行时决定大小和初始化" -"的静态变量" - -#: src/why-rust/compile-time.md:21 -msgid "" -"You can use [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." -"html) to make the compiler \"forget\" about a value (meaning the destructor " -"is never run)." -msgstr "" -"可以使用 [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." -"html) 来让编译器“忘记”一个值（即其析构函数不会被执行）。" - -#: src/why-rust/compile-time.md:23 -msgid "" -"You can also accidentally create a [reference cycle](https://doc.rust-lang." -"org/book/ch15-06-reference-cycles.html) with `Rc` or `Arc`." -msgstr "" -"可以使用 `Rc` 或 `Arc` 意外创建一个循环引用（[reference cycle](https://doc." -"rust-lang.org/book/ch15-06-reference-cycles.html)）。" - -#: src/why-rust/compile-time.md:25 -msgid "" -"In fact, some will consider infinitely populating a collection a memory leak " -"and Rust does not protect from those." -msgstr "" -"实际上，有人认为无限填充一个集合也是一种内存泄漏，而 Rust 对此没有保护。" - -#: src/why-rust/compile-time.md:28 -msgid "" -"For the purpose of this course, \"No memory leaks\" should be understood as " -"\"Pretty much no _accidental_ memory leaks\"." -msgstr "就本课程而言，“不存在内存泄漏”应理解为“几乎没有 _意外_ 内存泄漏”。" - -#: src/why-rust/runtime.md:3 -msgid "No undefined behavior at runtime:" -msgstr "Rust 没有运行时未定义行为：" - -#: src/why-rust/runtime.md:5 -msgid "Array access is bounds checked." -msgstr "数组访问有边界检查。" - -#: src/why-rust/runtime.md:6 -msgid "Integer overflow is defined (panic or wrap-around)." -msgstr "整数溢出有明确定义（panic 或回绕）。" - -#: src/why-rust/runtime.md:12 -msgid "" -"Integer overflow is defined via the [`overflow-checks`](https://doc.rust-" -"lang.org/rustc/codegen-options/index.html#overflow-checks) compile-time " -"flag. If enabled, the program will panic (a controlled crash of the " -"program), otherwise you get wrap-around semantics. By default, you get " -"panics in debug mode (`cargo build`) and wrap-around in release mode (`cargo " -"build --release`)." -msgstr "" -"整数溢出的行为由编译时的标志指定。可以选择 panic（一种受控的程序崩溃）或使" -"用“回绕（wrap-around）”语义。默认情况下，使用调试模式编译（`cargo build`）的" -"行为为 panic，使用发布模式编译（`cargo build --release`）的行为为“回绕”。" - -#: src/why-rust/runtime.md:18 +#: src/hello-world/playground.md:11 msgid "" -"Bounds checking cannot be disabled with a compiler flag. It can also not be " -"disabled directly with the `unsafe` keyword. However, `unsafe` allows you to " -"call functions such as `slice::get_unchecked` which does not do bounds " -"checking." +"Rust has two main \"profiles\" for generating code: Debug (extra runtime " +"checks, less optimization) and Release (fewer runtime checks, lots of " +"optimization). These are accessible under \"Debug\" at the top." msgstr "" -"边界检查不能使用编译标志禁用，也不能直接通过 `unsafe` 关键字禁用。然而， " -"`unsafe` 允许你调用 `slice::get_unchecked` 等不做边界检查的函数。" -#: src/why-rust/modern.md:3 -msgid "Rust is built with all the experience gained in the last decades." -msgstr "Rust 建立于过去几十年来所获得的经验之上。" - -#: src/why-rust/modern.md:5 -msgid "Language Features" -msgstr "语言特性" - -#: src/why-rust/modern.md:7 -msgid "Enums and pattern matching." -msgstr "枚举和模式匹配。" - -#: src/why-rust/modern.md:8 -msgid "Generics." -msgstr "泛型。" - -#: src/why-rust/modern.md:9 -msgid "No overhead FFI." -msgstr "无额外开销的外部函数接口（FFI）。" - -#: src/why-rust/modern.md:10 -msgid "Zero-cost abstractions." -msgstr "零成本抽象。" - -#: src/why-rust/modern.md:12 -msgid "Tooling" -msgstr "工具" - -#: src/why-rust/modern.md:14 -msgid "Great compiler errors." -msgstr "强大的编译器错误提示。" - -#: src/why-rust/modern.md:15 -msgid "Built-in dependency manager." -msgstr "内置依赖管理器。" - -#: src/why-rust/modern.md:16 -msgid "Built-in support for testing." -msgstr "对测试的内置支持。" - -#: src/why-rust/modern.md:17 -msgid "Excellent Language Server Protocol support." -msgstr "优秀的语言服务协议（Language Server Protocol）支持。" - -#: src/why-rust/modern.md:23 +#: src/hello-world/playground.md:15 msgid "" -"Zero-cost abstractions, similar to C++, means that you don't have to 'pay' " -"for higher-level programming constructs with memory or CPU. For example, " -"writing a loop using `for` should result in roughly the same low level " -"instructions as using the `.iter().fold()` construct." +"If you're interested, use \"ASM\" under \"...\" to see the generated " +"assembly code." msgstr "" -"与 C++ 类似的零成本抽象，意味着你不需要为高级程序语言的结构“付出”更多的内存" -"和 CPU。例如使用 `for` 循环与使用 `.iter().fold()` 结构应该会生成大致相同的底" -"层指令。" -#: src/why-rust/modern.md:28 +#: src/hello-world/playground.md:20 msgid "" -"It may be worth mentioning that Rust enums are 'Algebraic Data Types', also " -"known as 'sum types', which allow the type system to express things like " -"`Option` and `Result`." +"As students head into the break, encourage them to open up the playground " +"and experiment a little. Encourage them to keep the tab open and try things " +"out during the rest of the course. This is particularly helpful for advanced " +"students who want to know more about Rust's optimizations or generated " +"assembly." msgstr "" -"值得一提的是，Rust 的枚举是“代数数据类型”（也叫“和类型”）。它使得类型系统可以" -"表示 `Option` 和 `Result` 等结构。" -#: src/why-rust/modern.md:32 +#: src/types-and-values/variables.md:3 +#, fuzzy msgid "" -"Remind people to read the errors --- many developers have gotten used to " -"ignore lengthy compiler output. The Rust compiler is significantly more " -"talkative than other compilers. It will often provide you with _actionable_ " -"feedback, ready to copy-paste into your code." -msgstr "" -"提醒学生去阅读编译错误 --- 许多开发者已经习惯去忽略冗长的编译器输出。Rust 编" -"译器会比其它编译器更健谈。它通常会提供 _可操作的_ 反馈，可以直接复制粘贴到代" -"码中。" +"Rust provides type safety via static typing. Variable bindings are made with " +"`let`:" +msgstr "Rust 通过静态类型实现了类型安全。变量绑定默认是不可变的：" -#: src/why-rust/modern.md:37 -msgid "" -"The Rust standard library is small compared to languages like Java, Python, " -"and Go. Rust does not come with several things you might consider standard " -"and essential:" +#: src/types-and-values/variables.md:9 src/control-flow-basics/loops.md:30 +#: src/control-flow-basics/break-continue.md:34 +#: src/control-flow-basics/blocks-and-scopes.md:16 +msgid "\"x: {x}\"" msgstr "" -"相比 Java、Python 和 Go 等语言，Rust 标准库较为精简。Rust 并没有内置一些你可" -"能认为标准和必要的功能：" - -#: src/why-rust/modern.md:41 -msgid "a random number generator, but see [rand](https://docs.rs/rand/)." -msgstr "随机数生成器，可以使用 [rand](https://docs.rs/rand/) 替代。" -#: src/why-rust/modern.md:42 -msgid "support for SSL or TLS, but see [rusttls](https://docs.rs/rustls/)." -msgstr "SSL 和 TLS 支持，可以使用 [rusttls](https://docs.rs/rustls/) 替代。" - -#: src/why-rust/modern.md:43 -msgid "support for JSON, but see [serde_json](https://docs.rs/serde_json/)." -msgstr "JSON 支持，可以使用 [serde_json](https://docs.rs/serde_json/) 替代。" - -#: src/why-rust/modern.md:45 +#: src/types-and-values/variables.md:10 msgid "" -"The reasoning behind this is that functionality in the standard library " -"cannot go away, so it has to be very stable. For the examples above, the " -"Rust community is still working on finding the best solution --- and perhaps " -"there isn't a single \"best solution\" for some of these things." +"// x = 20;\n" +" // println!(\"x: {x}\");\n" msgstr "" -"Rust 这么做的原因是标准库中的功能是无法去除的，因此该功能必须非常稳定。对于以" -"上例子，Rust 社区仍在寻找最佳解决方案 --- 甚至对一些情况可能没有单一的“最佳解" -"决方案”。" -#: src/why-rust/modern.md:50 +#: src/types-and-values/variables.md:17 msgid "" -"Rust comes with a built-in package manager in the form of Cargo and this " -"makes it trivial to download and compile third-party crates. A consequence " -"of this is that the standard library can be smaller." +"Uncomment the `x = 20` to demonstrate that variables are immutable by " +"default. Add the `mut` keyword to allow changes." msgstr "" -"Rust 内置了一个包管理器 Cargo，使得下载和编译第三方 crate 变得简单。这也导致" -"标准库可以更加精简。" -#: src/why-rust/modern.md:54 +#: src/types-and-values/variables.md:20 msgid "" -"Discovering good third-party crates can be a problem. Sites like help with this by letting you compare health metrics for crates to " -"find a good and trusted one." +"The `i32` here is the type of the variable. This must be known at compile " +"time, but type inference (covered later) allows the programmer to omit it in " +"many cases." msgstr "" -"发现高质量的第三方 crate 也许是一个问题。 等网站对此问题有" -"所帮助。它能帮你比较 crate 的健康指标，以找到一个高质量并受信任的 crate。" -#: src/why-rust/modern.md:58 +#: src/types-and-values/values.md:3 msgid "" -"[rust-analyzer](https://rust-analyzer.github.io/) is a well supported LSP " -"implementation used in major IDEs and text editors." +"Here are some basic built-in types, and the syntax for literal values of " +"each type." msgstr "" -"[rust-analyzer](https://rust-analyzer.github.io/) 是一个受到广泛支持的 LSP 实" -"现，被主流的 IDE 和文本编辑器所使用。" - -#: src/basic-syntax.md:3 -msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" -msgstr "Rust 的许多语法与 C、C++ 和 Java 的语法相似：" - -#: src/basic-syntax.md:5 -msgid "Blocks and scopes are delimited by curly braces." -msgstr "代码块和作用域都是由花括号来界定的。" - -#: src/basic-syntax.md:6 -msgid "" -"Line comments are started with `//`, block comments are delimited by `/* ... " -"*/`." -msgstr "行内注释以 `//` 起始，块注释使用 `/* ... */` 来界定。" - -#: src/basic-syntax.md:8 -msgid "Keywords like `if` and `while` work the same." -msgstr "`if` 和 `while` 等关键词作用与以上语言一致。" - -#: src/basic-syntax.md:9 -msgid "Variable assignment is done with `=`, comparison is done with `==`." -msgstr "变量赋值使用 `=`，值之间比较使用 `==`。" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 -#: src/exercises/day-3/safe-ffi-wrapper.md:16 +#: src/types-and-values/values.md:6 +#: src/tuples-and-arrays/tuples-and-arrays.md:7 src/unsafe-rust/exercise.md:16 msgid "Types" msgstr "类型" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 +#: src/types-and-values/values.md:6 +#: src/tuples-and-arrays/tuples-and-arrays.md:7 msgid "Literals" msgstr "字面量" -#: src/basic-syntax/scalar-types.md:5 +#: src/types-and-values/values.md:8 msgid "Signed integers" msgstr "有符号整数" -#: src/basic-syntax/scalar-types.md:5 +#: src/types-and-values/values.md:8 msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" msgstr "`i8`、`i16`、`i32`、`i64`、`i128`、`isize`" -#: src/basic-syntax/scalar-types.md:5 +#: src/types-and-values/values.md:8 msgid "`-10`, `0`, `1_000`, `123_i64`" msgstr "`-10`、`0`、`1_000`、`123_i64`" -#: src/basic-syntax/scalar-types.md:6 +#: src/types-and-values/values.md:9 msgid "Unsigned integers" msgstr "无符号整数" -#: src/basic-syntax/scalar-types.md:6 +#: src/types-and-values/values.md:9 msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" msgstr "`u8`、`u16`、`u32`、`u64`、`u128`、`usize`" -#: src/basic-syntax/scalar-types.md:6 +#: src/types-and-values/values.md:9 msgid "`0`, `123`, `10_u16`" msgstr "`0`、`123`、`10_u16`" -#: src/basic-syntax/scalar-types.md:7 +#: src/types-and-values/values.md:10 msgid "Floating point numbers" msgstr "浮点数" -#: src/basic-syntax/scalar-types.md:7 +#: src/types-and-values/values.md:10 msgid "`f32`, `f64`" msgstr "`f32`、`f64`" -#: src/basic-syntax/scalar-types.md:7 +#: src/types-and-values/values.md:10 msgid "`3.14`, `-10.0e20`, `2_f32`" msgstr "`3.14`、`-10.0e20`、`2_f32`" -#: src/basic-syntax/scalar-types.md:8 -msgid "Strings" -msgstr "字符串" - -#: src/basic-syntax/scalar-types.md:8 -msgid "`&str`" -msgstr "`&str`" - -#: src/basic-syntax/scalar-types.md:8 -msgid "`\"foo\"`, `\"two\\nlines\"`" -msgstr "`\"foo\"`、`“两\\n行”`" - -#: src/basic-syntax/scalar-types.md:9 +#: src/types-and-values/values.md:11 msgid "Unicode scalar values" msgstr "Unicode 标量类型" -#: src/basic-syntax/scalar-types.md:9 +#: src/types-and-values/values.md:11 msgid "`char`" msgstr "`char`" -#: src/basic-syntax/scalar-types.md:9 +#: src/types-and-values/values.md:11 msgid "`'a'`, `'α'`, `'∞'`" msgstr "`'a'`、`'α'`、`'∞'`" -#: src/basic-syntax/scalar-types.md:10 +#: src/types-and-values/values.md:12 msgid "Booleans" msgstr "布尔值" -#: src/basic-syntax/scalar-types.md:10 +#: src/types-and-values/values.md:12 msgid "`bool`" msgstr "`bool`" -#: src/basic-syntax/scalar-types.md:10 +#: src/types-and-values/values.md:12 msgid "`true`, `false`" msgstr "`true`、`false`" -#: src/basic-syntax/scalar-types.md:12 +#: src/types-and-values/values.md:14 msgid "The types have widths as follows:" msgstr "各类型占用的空间为：" -#: src/basic-syntax/scalar-types.md:14 +#: src/types-and-values/values.md:16 msgid "`iN`, `uN`, and `fN` are _N_ bits wide," msgstr "`iN`, `uN` 和 `fN` 占用 _N_ 位，" -#: src/basic-syntax/scalar-types.md:15 +#: src/types-and-values/values.md:17 msgid "`isize` and `usize` are the width of a pointer," msgstr "`isize` 和 `usize` 占用一个指针大小的空间，" -#: src/basic-syntax/scalar-types.md:16 +#: src/types-and-values/values.md:18 msgid "`char` is 32 bits wide," msgstr "`char` 占用 32 位空间，" -#: src/basic-syntax/scalar-types.md:17 +#: src/types-and-values/values.md:19 msgid "`bool` is 8 bits wide." msgstr "`bool` 占用 8 位空间。" -#: src/basic-syntax/scalar-types.md:21 +#: src/types-and-values/values.md:23 msgid "There are a few syntaxes which are not shown above:" msgstr "上表中还有一些未提及的语法：" -#: src/basic-syntax/scalar-types.md:23 -msgid "" -"Raw strings allow you to create a `&str` value with escapes disabled: " -"`r\"\\n\" == \"\\\\n\"`. You can embed double-quotes by using an equal " -"amount of `#` on either side of the quotes:" -msgstr "" -"原始字符串可在创建 `&str` 时禁用转义：`r\"\\n\" == \"\\\\n\"`。可以在外层引号" -"两侧添加相同数量的 `#`，以在字符串中嵌入双引号：" - -#: src/basic-syntax/scalar-types.md:35 -msgid "Byte strings allow you to create a `&[u8]` value directly:" -msgstr "字节串可以用于直接创建 `&[u8]` 类型的值：" - -#: src/basic-syntax/scalar-types.md:45 +#: src/types-and-values/values.md:25 msgid "" "All underscores in numbers can be left out, they are for legibility only. So " "`1_000` can be written as `1000` (or `10_00`), and `123_i64` can be written " @@ -2988,4489 +2774,3260 @@ msgstr "" "数字中的所有下划线均可忽略，它们只是为了方便辨识。因此，`1_000` 可以写为 " "`1000`（或 `10_00`），而 `123_i64` 可以写为 `123i64`。" -#: src/basic-syntax/compound-types.md:5 -msgid "Arrays" -msgstr "数组（Arrays）" - -#: src/basic-syntax/compound-types.md:5 -msgid "`[T; N]`" -msgstr "`[T; N]`" - -#: src/basic-syntax/compound-types.md:5 -msgid "`[20, 30, 40]`, `[0; 3]`" -msgstr "`[20, 30, 40]`, `[0; 3]`" - -#: src/basic-syntax/compound-types.md:6 -msgid "Tuples" -msgstr "元组（Tuples）" +#: src/types-and-values/arithmetic.md:9 +msgid "\"result: {}\"" +msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "`()`, `(T,)`, `(T1, T2)`, ..." -msgstr "`()`, `(T,)`, `(T1, T2)`, ..." +#: src/types-and-values/arithmetic.md:15 +msgid "" +"This is the first time we've seen a function other than `main`, but the " +"meaning should be clear: it takes three integers, and returns an integer. " +"Functions will be covered in more detail later." +msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "`()`, `('x',)`, `('x', 1.2)`, ..." -msgstr "`()`, `('x',)`, `('x', 1.2)`, ..." +#: src/types-and-values/arithmetic.md:19 +msgid "Arithmetic is very similar to other languages, with similar precedence." +msgstr "" -#: src/basic-syntax/compound-types.md:8 -msgid "Array assignment and access:" -msgstr "数组的赋值和访问操作：" +#: src/types-and-values/arithmetic.md:21 +msgid "" +"What about integer overflow? In C and C++ overflow of _signed_ integers is " +"actually undefined, and might do different things on different platforms or " +"compilers. In Rust, it's defined." +msgstr "" -#: src/basic-syntax/compound-types.md:19 -msgid "Tuple assignment and access:" -msgstr "元组的赋值和访问操作：" +#: src/types-and-values/arithmetic.md:25 +msgid "" +"Change the `i32`'s to `i16` to see an integer overflow, which panics " +"(checked) in a debug build and wraps in a release build. There are other " +"options, such as overflowing, saturating, and carrying. These are accessed " +"with method syntax, e.g., `(a * b).saturating_add(b * c).saturating_add(c * " +"a)`." +msgstr "" -#: src/basic-syntax/compound-types.md:34 -msgid "Arrays:" -msgstr "数组：" +#: src/types-and-values/arithmetic.md:30 +msgid "" +"In fact, the compiler will detect overflow of constant expressions, which is " +"why the example requires a separate function." +msgstr "" -#: src/basic-syntax/compound-types.md:36 -#, fuzzy +#: src/types-and-values/strings.md:3 msgid "" -"A value of the array type `[T; N]` holds `N` (a compile-time constant) " -"elements of the same type `T`. Note that the length of the array is _part of " -"its type_, which means that `[u8; 3]` and `[u8; 4]` are considered two " -"different types." +"Rust has two types to represent strings, both of which will be covered in " +"more depth later. Both _always_ store UTF-8 encoded strings." msgstr "" -"数组中的元素具有相同的类型 `T`，数组的长度为 `N`，`N` 是一个编译期常量。 需要" -"注意的是数组的长度是它_类型的一部分\\_, 这意味着 `[u8; 3]` 和 `[u8; 4]` 在 " -"Rust 中被认为是不同的类型。" -#: src/basic-syntax/compound-types.md:40 -msgid "We can use literals to assign values to arrays." -msgstr "我们可以使用字面量来为数组赋值。" +#: src/types-and-values/strings.md:6 +#, fuzzy +msgid "`String` - a modifiable, owned string." +msgstr "`String` 是一个可变字符串缓冲区。" -#: src/basic-syntax/compound-types.md:42 -msgid "" -"In the main function, the print statement asks for the debug implementation " -"with the `?` format parameter: `{}` gives the default output, `{:?}` gives " -"the debug output. We could also have used `{a}` and `{a:?}` without " -"specifying the value after the format string." +#: src/types-and-values/strings.md:7 +msgid "`&str` - a read-only string. String literals have this type." msgstr "" -"在主函数中，打印（print）语句使用 `?` 格式请求调试实现。 使用参数 `{}` 打印默" -"认输出，`{:?}` 表示以调试格式输出。 我们也可以不在格式化字符串后面指定变量" -"值，直接使用 `{a}` 和 `{a:?}` 进行输出。" -#: src/basic-syntax/compound-types.md:47 -msgid "" -"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " -"easier to read." +#: src/types-and-values/strings.md:11 +msgid "\"Greetings\"" msgstr "" -"添加 `#`，比如 `{a:#?}`，会输出“美观打印（pretty printing）” 格式，这种格式可" -"能会更加易读。" -#: src/basic-syntax/compound-types.md:49 -msgid "Tuples:" -msgstr "元组：" +#: src/types-and-values/strings.md:12 +msgid "\"🪐\"" +msgstr "" -#: src/basic-syntax/compound-types.md:51 -msgid "Like arrays, tuples have a fixed length." -msgstr "和数组一样，元组也具有固定的长度。" +#: src/types-and-values/strings.md:15 +msgid "\", \"" +msgstr "" -#: src/basic-syntax/compound-types.md:53 -msgid "Tuples group together values of different types into a compound type." -msgstr "元组将不同类型的值组成一个复合类型。" +#: src/types-and-values/strings.md:17 +msgid "\"final sentence: {}\"" +msgstr "" -#: src/basic-syntax/compound-types.md:55 -msgid "" -"Fields of a tuple can be accessed by the period and the index of the value, " -"e.g. `t.0`, `t.1`." -msgstr "元组中的字段可以通过英文句号加上值的下标进行访问比如：`t.0`, `t.1`。" +#: src/types-and-values/strings.md:18 src/async/control-flow/join.md:30 +msgid "\"{:?}\"" +msgstr "" -#: src/basic-syntax/compound-types.md:57 -msgid "" -"The empty tuple `()` is also known as the \"unit type\". It is both a type, " -"and the only valid value of that type - that is to say both the type and its " -"value are expressed as `()`. It is used to indicate, for example, that a " -"function or expression has no return value, as we'll see in a future slide. " +#: src/types-and-values/strings.md:19 +msgid "//println!(\"{:?}\", &sentence[12..13]);\n" msgstr "" -"空元组 `()` 也被称作 “单元（unit）类型”. 它既是一个类型， 也是这种类型的唯一" -"值——也就是说它的类型和它的值都被表示为 `()`。它通常用于表示，比如，一个函数或" -"表达式没有返回值，我们会在后续的幻灯片种见到这种用法。" -#: src/basic-syntax/compound-types.md:61 +#: src/types-and-values/strings.md:25 msgid "" -"You can think of it as `void` that can be familiar to you from other " -"programming languages." -msgstr "你可以将其理解为你可能在其他编程语言中比较熟悉的 `void` 类型。" - -#: src/basic-syntax/references.md:3 -msgid "Like C++, Rust has references:" -msgstr "如同 C++ 一样，Rust 也提供了引用类型。" +"This slide introduces strings. Everything here will be covered in more depth " +"later, but this is enough for subsequent slides and exercises to use strings." +msgstr "" -#: src/basic-syntax/references.md:15 -msgid "Some notes:" -msgstr "一些注意事项：" +#: src/types-and-values/strings.md:28 +msgid "Invalid UTF-8 in a string is UB, and this not allowed in safe Rust." +msgstr "" -#: src/basic-syntax/references.md:17 +#: src/types-and-values/strings.md:30 msgid "" -"We must dereference `ref_x` when assigning to it, similar to C and C++ " -"pointers." +"`String` is a user-defined type with a constructor (`::new()`) and methods " +"like `s.push_str(..)`." msgstr "" -"就像 C 与 C++ 中的指针一样，对引用 `ref_x` 进行赋值时，我们必须对其解引用。" -#: src/basic-syntax/references.md:18 +#: src/types-and-values/strings.md:33 msgid "" -"Rust will auto-dereference in some cases, in particular when invoking " -"methods (try `ref_x.count_ones()`)." +"The `&` in `&str` indicates that this is a reference. We will cover " +"references later, so for now just think of `&str` as a unit meaning \"a read-" +"only string\"." msgstr "" -"Rust 有时会进行自动解引用。比如调用方法 `ref_x.count_ones()` 时，ref_x 会被解" -"引用。" -#: src/basic-syntax/references.md:20 +#: src/types-and-values/strings.md:36 msgid "" -"References that are declared as `mut` can be bound to different values over " -"their lifetime." +"The commented-out line is indexing into the string by byte position. " +"`12..13` does not end on a character boundary, so the program panics. Adjust " +"it to a range that does, based on the error message." msgstr "" -"如果引用值被声明为 `mut`（可变引用），那么这个引用值可以在它的生命周期内被绑" -"定为不同的值。" -#: src/basic-syntax/references.md:26 +#: src/types-and-values/strings.md:40 msgid "" -"Be sure to note the difference between `let mut ref_x: &i32` and `let ref_x: " -"&mut i32`. The first one represents a mutable reference which can be bound " -"to different values, while the second represents a reference to a mutable " -"value." +"Raw strings allow you to create a `&str` value with escapes disabled: " +"`r\"\\n\" == \"\\\\n\"`. You can embed double-quotes by using an equal " +"amount of `#` on either side of the quotes:" msgstr "" -"注意 `let mut ref_x: &i32` 与 `let ref_x: &mut i32` 之间的区别。第一条语句声" -"明了一个可变引用，所以我们可以修改这个引用所绑定的值；第二条语句声明了一个指" -"向可变变量的引用。" +"原始字符串可在创建 `&str` 时禁用转义：`r\"\\n\" == \"\\\\n\"`。可以在外层引号" +"两侧添加相同数量的 `#`，以在字符串中嵌入双引号：" -#: src/basic-syntax/references-dangling.md:3 -msgid "Rust will statically forbid dangling references:" -msgstr "Rust 会静态禁止悬垂引用：" +#: src/types-and-values/inference.md:3 +msgid "Rust will look at how the variable is _used_ to determine the type:" +msgstr "Rust 会根据变量的使用来确定其类型：" -#: src/basic-syntax/references-dangling.md:17 -msgid "A reference is said to \"borrow\" the value it refers to." -msgstr "一个引用被认为是“借用（borrow）”了它指向的值。" - -#: src/basic-syntax/references-dangling.md:18 +#: src/types-and-values/inference.md:28 msgid "" -"Rust is tracking the lifetimes of all references to ensure they live long " -"enough." -msgstr "Rust 会跟踪所有引用的生命周期，以确保这些值的存活时间足够长。" - -#: src/basic-syntax/references-dangling.md:20 -msgid "We will talk more about borrowing when we get to ownership." -msgstr "我们会在讲到所有权（ownership）时详细讨论借用（borrow）。" - -#: src/basic-syntax/slices.md:3 -msgid "A slice gives you a view into a larger collection:" -msgstr "切片 (slice) 的作用是提供对集合 (collection) 的视图 (view):" - -#: src/basic-syntax/slices.md:17 -msgid "Slices borrow data from the sliced type." -msgstr "切片从被切片的类型中借用 (borrow) 数据。" - -#: src/basic-syntax/slices.md:18 -#, fuzzy -msgid "Question: What happens if you modify `a[3]` right before printing `s`?" -msgstr "请思考：如果我们改变 `a[3]`，将会产生怎样的后果？" +"This slide demonstrates how the Rust compiler infers types based on " +"constraints given by variable declarations and usages." +msgstr "这张幻灯片演示了 Rust 编译器是如何根据变量声明和用法来推导其类型的。" -#: src/basic-syntax/slices.md:22 -#, fuzzy +#: src/types-and-values/inference.md:31 msgid "" -"We create a slice by borrowing `a` and specifying the starting and ending " -"indexes in brackets." -msgstr "创建切片时，我们借用了 `a` ，并在方括号中标明了起始和结尾下标。" +"It is very important to emphasize that variables declared like this are not " +"of some sort of dynamic \"any type\" that can hold any data. The machine " +"code generated by such declaration is identical to the explicit declaration " +"of a type. The compiler does the job for us and helps us write more concise " +"code." +msgstr "" +"需要重点强调的是这样声明的变量并非像那种动态类型语言中可以持有任何数据的“任何" +"类型”。这种声明所生成的机器码与明确类型声明完全相同。编译器进行类型推导能够让" +"我们编写更简略的代码。" -#: src/basic-syntax/slices.md:24 -#, fuzzy +#: src/types-and-values/inference.md:36 msgid "" -"If the slice starts at index 0, Rust’s range syntax allows us to drop the " -"starting index, meaning that `&a[0..a.len()]` and `&a[..a.len()]` are " -"identical." +"When nothing constrains the type of an integer literal, Rust defaults to " +"`i32`. This sometimes appears as `{integer}` in error messages. Similarly, " +"floating-point literals default to `f64`." msgstr "" -"如果切片的起始下标为 0， Rust 语法允许我们省略起始下标。比如说 `&a[0..a." -"len()]` 与 `&a[..a.len()]` 是等价的。" -#: src/basic-syntax/slices.md:26 -#, fuzzy -msgid "" -"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " -"identical." +#: src/types-and-values/inference.md:45 +msgid "// ERROR: no implementation for `{float} == {integer}`\n" msgstr "" -"结尾下标也可以用相同方式省略。比如说 `&a[2..a.len()]` 和 `&a[2..]` 是等价的。" -#: src/basic-syntax/slices.md:28 -#, fuzzy +#: src/types-and-values/exercise.md:3 msgid "" -"To easily create a slice of the full array, we can therefore use `&a[..]`." -msgstr "因此，我们可以用 `&a[..]` 来创建包含整个数组的切片。" +"The first and second Fibonacci numbers are both `1`. For n>2, the n'th " +"Fibonacci number is calculated recursively as the sum of the n-1'th and " +"n-2'th Fibonacci numbers." +msgstr "" -#: src/basic-syntax/slices.md:30 -#, fuzzy +#: src/types-and-values/exercise.md:7 msgid "" -"`s` is a reference to a slice of `i32`s. Notice that the type of `s` " -"(`&[i32]`) no longer mentions the array length. This allows us to perform " -"computation on slices of different sizes." +"Write a function `fib(n)` that calculates the n'th Fibonacci number. When " +"will this function panic?" +msgstr "" + +#: src/types-and-values/exercise.md:13 +msgid "// The base case.\n" msgstr "" -"切片会从另外一个对象中借用数据。在这个例子中， `a` 必须在其切片存活时保持存活" -"（处于作用域中）。" -#: src/basic-syntax/slices.md:32 +#: src/types-and-values/exercise.md:14 src/types-and-values/exercise.md:17 +#: src/control-flow-basics/exercise.md:27 +#: src/control-flow-basics/exercise.md:31 #, fuzzy -msgid "" -"Slices always borrow from another object. In this example, `a` has to remain " -"'alive' (in scope) for at least as long as our slice. " +msgid "\"Implement this\"" +msgstr "实现" + +#: src/types-and-values/exercise.md:16 +msgid "// The recursive case.\n" msgstr "" -"关于修改 `a[3]` 的问题可能会引发精彩的讨论。正确答案是：为了保证内存安全，在" -"创建切片后，我们不能通过 `a` 来修改数据。不过我们可以通过 `a` 或者 `s` 来读取" -"数据。我们将会在“借用”章节着重介绍这个内容。" -#: src/basic-syntax/slices.md:34 -msgid "" -"The question about modifying `a[3]` can spark an interesting discussion, but " -"the answer is that for memory safety reasons you cannot do it through `a` at " -"this point in the execution, but you can read the data from both `a` and `s` " -"safely. It works before you created the slice, and again after the " -"`println`, when the slice is no longer used. More details will be explained " -"in the borrow checker section." +#: src/types-and-values/exercise.md:23 src/types-and-values/solution.md:14 +msgid "\"fib(n) = {}\"" msgstr "" -"关于修改“a\\[3\\]”的问题可能会引发一些有趣的讨论，但正解是，出于内存安全方面" -"的原因，您无法在执行作业的这个时间点通过“a”来进行此修改，但可以从“a”和“s”安全" -"地读取数据。它会在您创建 Slice 之前运作，在“println”之后（不再使用 Slice 时）" -"再次运作。更多详情会在“借用检查器”部分中加以说明。" -#: src/basic-syntax/string-slices.md:1 -msgid "`String` vs `str`" -msgstr "“String”与“str”的区别" +#: src/control-flow-basics/conditionals.md:3 +msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" +msgstr "Rust 的许多语法与 C、C++ 和 Java 的语法相似：" -#: src/basic-syntax/string-slices.md:3 -msgid "We can now understand the two string types in Rust:" -msgstr "现在我们就可以理解 Rust 中的两种字符串类型：" +#: src/control-flow-basics/conditionals.md:5 +#, fuzzy +msgid "Blocks are delimited by curly braces." +msgstr "代码块和作用域都是由花括号来界定的。" -#: src/basic-syntax/string-slices.md:5 +#: src/control-flow-basics/conditionals.md:6 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1: &str = \"World\";\n" -" println!(\"s1: {s1}\");\n" -"\n" -" let mut s2: String = String::from(\"Hello \");\n" -" println!(\"s2: {s2}\");\n" -" s2.push_str(s1);\n" -" println!(\"s2: {s2}\");\n" -" \n" -" let s3: &str = &s2[6..];\n" -" println!(\"s3: {s3}\");\n" -"}\n" -"```" -msgstr "" +"Line comments are started with `//`, block comments are delimited by `/* ... " +"*/`." +msgstr "行内注释以 `//` 起始，块注释使用 `/* ... */` 来界定。" -#: src/basic-syntax/string-slices.md:20 -msgid "Rust terminology:" -msgstr "Rust 术语：" +#: src/control-flow-basics/conditionals.md:8 +msgid "Keywords like `if` and `while` work the same." +msgstr "`if` 和 `while` 等关键词作用与以上语言一致。" -#: src/basic-syntax/string-slices.md:22 -msgid "`&str` an immutable reference to a string slice." -msgstr "`&str` 是一个指向字符串片段的不可变引用。" +#: src/control-flow-basics/conditionals.md:9 +msgid "Variable assignment is done with `=`, comparison is done with `==`." +msgstr "变量赋值使用 `=`，值之间比较使用 `==`。" -#: src/basic-syntax/string-slices.md:23 -msgid "`String` a mutable string buffer." -msgstr "`String` 是一个可变字符串缓冲区。" +#: src/control-flow-basics/conditionals.md:11 +msgid "`if` expressions" +msgstr "`if` 表达式" -#: src/basic-syntax/string-slices.md:27 +#: src/control-flow-basics/conditionals.md:13 msgid "" -"`&str` introduces a string slice, which is an immutable reference to UTF-8 " -"encoded string data stored in a block of memory. String literals " -"(`”Hello”`), are stored in the program’s binary." +"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" +"if-expr.html#if-expressions) exactly like `if` statements in other languages:" msgstr "" -"`&str` 引入了一个字符串切片，它是一个指向保存在内存块中的 UTF-8 编码字符串数" -"据的不可变引用。 字符串字面量（`”Hello”`）会保存在程序的二进制文件中。" +"[`if` 表达式](https://doc.rust-lang.org/reference/expressions/if-expr." +"html#if-expressions) 的用法与其他语言中的 `if` 语句完全一样。" -#: src/basic-syntax/string-slices.md:30 -msgid "" -"Rust’s `String` type is a wrapper around a vector of bytes. As with a " -"`Vec`, it is owned." +#: src/control-flow-basics/conditionals.md:21 +#: src/control-flow-basics/conditionals.md:36 +msgid "\"small\"" msgstr "" -"Rust 的 `String` 类型是一个字节 vector 的封装。和 `Vec` 一样，它是拥有所有" -"权的。" -#: src/basic-syntax/string-slices.md:32 -msgid "" -"As with many other types `String::from()` creates a string from a string " -"literal; `String::new()` creates a new empty string, to which string data " -"can be added using the `push()` and `push_str()` methods." +#: src/control-flow-basics/conditionals.md:23 +msgid "\"biggish\"" msgstr "" -"和其他类型一样，`String::from()` 会从字符串字面量创建一个字符串；`String::" -"new()` 会创建一个新的空字符串， 之后可以使用 `push()` 和 `push_str()` 方法" -"向其中添加字符串数据。" -#: src/basic-syntax/string-slices.md:35 -msgid "" -"The `format!()` macro is a convenient way to generate an owned string from " -"dynamic values. It accepts the same format specification as `println!()`." +#: src/control-flow-basics/conditionals.md:25 +msgid "\"huge\"" msgstr "" -"`format!()` 宏可以方便地动态生成拥有所有权的字符串。它接受和 `println!()` 相" -"同的格式规范。" -#: src/basic-syntax/string-slices.md:38 +#: src/control-flow-basics/conditionals.md:30 msgid "" -"You can borrow `&str` slices from `String` via `&` and optionally range " -"selection." -msgstr "你可以通过 `&` 和可选的范围选择从 `String` 中借用 `&str` 切片。" +"In addition, you can use `if` as an expression. The last expression of each " +"block becomes the value of the `if` expression:" +msgstr "" +"此外，你还可以将 `if` 用作一个表达式。每个块的最后一个表达式 将成为 `if` 表达" +"式的值：" -#: src/basic-syntax/string-slices.md:40 -msgid "" -"For C++ programmers: think of `&str` as `const char*` from C++, but the one " -"that always points to a valid string in memory. Rust `String` is a rough " -"equivalent of `std::string` from C++ (main difference: it can only contain " -"UTF-8 encoded bytes and will never use a small-string optimization)." +#: src/control-flow-basics/conditionals.md:36 +msgid "\"large\"" msgstr "" -"对于 C++ 程序员：可以把 `&str` 当作 C++ 中的 `const char*`，但是它总是指向内" -"存中的一个有效字符串。 Rust 的 `String` 大致相当于 C++ 中 `std::string` " -"（主要区别：它只能包含 UTF-8 编码的字节， 并且永远不会使用小字符串优化" -"（small-string optimization））。" -#: src/basic-syntax/functions.md:3 -msgid "" -"A Rust version of the famous [FizzBuzz](https://en.wikipedia.org/wiki/" -"Fizz_buzz) interview question:" +#: src/control-flow-basics/conditionals.md:37 +msgid "\"number size: {}\"" msgstr "" -"一个 Rust 版本的著名 [FizzBuzz](https://en.wikipedia.org/wiki/Fizz_buzz) 面试" -"题：" -#: src/basic-syntax/functions.md:36 +#: src/control-flow-basics/conditionals.md:43 +#, fuzzy msgid "" -"We refer in `main` to a function written below. Neither forward declarations " -"nor headers are necessary. " +"Because `if` is an expression and must have a particular type, both of its " +"branch blocks must have the same type. Show what happens if you add `;` " +"after `\"small\"` in the second example." msgstr "" -"我们在 `main` 中引用了下面编写的一个函数。不需要提前声明或添加头文件。 " +"由于 `if` 是一个表达式且必须有一个特定的类型，因此它的两个分支块必须有相同的" +"类型。考虑在第二个示例中将 `;` 添加到 `x / 2` 的后面，看看会出现什么情况。" -#: src/basic-syntax/functions.md:37 +#: src/control-flow-basics/conditionals.md:47 msgid "" -"Declaration parameters are followed by a type (the reverse of some " -"programming languages), then a return type." -msgstr "类型跟随在声明的参数后（与某些编程语言相反），然后是返回类型。" +"When `if` is used in an expression, the expression must have a `;` to " +"separate it from the next statement. Remove the `;` before `println!` to see " +"the compiler error." +msgstr "" -#: src/basic-syntax/functions.md:38 -msgid "" -"The last expression in a function body (or any block) becomes the return " -"value. Simply omit the `;` at the end of the expression." +#: src/control-flow-basics/loops.md:3 +msgid "There are three looping keywords in Rust: `while`, `loop`, and `for`:" msgstr "" -"函数体（或任何块）中的最后一个表达式将成为返回值。只需省略表达式末尾的 `;` 即" -"可。" -#: src/basic-syntax/functions.md:39 +#: src/control-flow-basics/loops.md:5 +#, fuzzy +msgid "`while`" +msgstr "`while` 循环" + +#: src/control-flow-basics/loops.md:7 +#, fuzzy msgid "" -"Some functions have no return value, and return the 'unit type', `()`. The " -"compiler will infer this if the `-> ()` return type is omitted." +"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" +"expr.html#predicate-loops) works much like in other languages, executing the " +"loop body as long as the condition is true." msgstr "" -"有些函数没有返回值，会返回“单元类型（unit type）”`()`。如果省略了`-> ()`的返" -"回类型，编译器将会自动推断。" +"[`while` 关键字](https://doc.rust-lang.org/reference/expressions/loop-expr." +"html#predicate-loops) 的工作方式与其他语言非常相似：" -#: src/basic-syntax/functions.md:40 -msgid "" -"The range expression in the `for` loop in `print_fizzbuzz_to()` contains " -"`=n`, which causes it to include the upper bound." +#: src/control-flow-basics/loops.md:18 +msgid "\"Final x: {x}\"" msgstr "" -"`print_fizzbuzz_to()`函数中`for`循环的范围表达式（range expression）包含" -"`=n`，这会导致它包括上限。" -#: src/basic-syntax/rustdoc.md:3 -msgid "" -"All language items in Rust can be documented using special `///` syntax." -msgstr "Rust 中的所有语言元素都可以通过特殊的 `///` 语法进行文档化。" +#: src/control-flow-basics/loops.md:22 +#, fuzzy +msgid "`for`" +msgstr "`for` 循环" -#: src/basic-syntax/rustdoc.md:5 +#: src/control-flow-basics/loops.md:24 #, fuzzy msgid "" -"```rust,editable\n" -"/// Determine whether the first argument is divisible by the second " -"argument.\n" -"///\n" -"/// If the second argument is zero, the result is false.\n" -"///\n" -"/// # Example\n" -"/// ```\n" -"/// assert!(is_divisible_by(42, 2));\n" -"/// ```\n" -"fn is_divisible_by(lhs: u32, rhs: u32) -> bool {\n" -" if rhs == 0 {\n" -" return false; // Corner case, early return\n" -" }\n" -" lhs % rhs == 0 // The last expression in a block is the return " -"value\n" -"}\n" -"```" +"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) iterates " +"over ranges of values:" +msgstr "" +"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) 用于定义析构函" +"数。" + +#: src/control-flow-basics/loops.md:35 +msgid "`loop`" msgstr "" -"```rust,editable\n" -"/// 判断第一个参数是否可以被第二个参数整除。\n" -"///\n" -"/// 如果第二个参数是 0，则返回结果为 false。\n" -"fn is_divisible_by(lhs: u32, rhs: u32) -> bool {\n" -" if rhs == 0 {\n" -" return false; // 边界条件，直接返回\n" -" }\n" -" lhs % rhs == 0 // 代码块中的最后一个表达式就是它的返回值\n" -"}\n" -"```" -#: src/basic-syntax/rustdoc.md:22 +#: src/control-flow-basics/loops.md:37 #, fuzzy msgid "" -"The contents are treated as Markdown. All published Rust library crates are " -"automatically documented at [`docs.rs`](https://docs.rs) using the [rustdoc]" -"(https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is " -"idiomatic to document all public items in an API using this pattern. Code " -"snippets can document usage and will be used as unit tests." +"The [`loop` statement](https://doc.rust-lang.org/std/keyword.loop.html) just " +"loops forever, until a `break`." msgstr "" -"文档的内容会被当做 Markdown 处理。所有已发布 Rust 库 crate 都会自动被" -"[rustdoc](https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) 工具在 " -"[`docs.rs`](https://docs.rs)存档。 按照这种方式来为 API 中的所有公开项编写文" -"档是 Rust 中惯用的做法。" +"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) 用于定义析构函" +"数。" -#: src/basic-syntax/rustdoc.md:30 -msgid "" -"Show students the generated docs for the `rand` crate at [`docs.rs/rand`]" -"(https://docs.rs/rand)." +#: src/control-flow-basics/loops.md:45 +msgid "\"{i}\"" msgstr "" -"向学生展示在 [`docs.rs/rand`](https://docs.rs/rand) 中为 `rand` crate 生成的" -"文档。" -#: src/basic-syntax/rustdoc.md:33 +#: src/control-flow-basics/loops.md:55 msgid "" -"This course does not include rustdoc on slides, just to save space, but in " -"real code they should be present." +"We will discuss iteration later; for now, just stick to range expressions." msgstr "" -"本课程的幻灯片中不包含 rustdoc，这是为了节省空间，但是在实际的代码中，应当编" -"写相关的程序文档。" -#: src/basic-syntax/rustdoc.md:36 +#: src/control-flow-basics/loops.md:56 msgid "" -"Inner doc comments are discussed later (in the page on modules) and need not " -"be addressed here." -msgstr "内部文档注释将在稍后（在讲解模块的页面）讨论，这里无需进行说明。" +"Note that the `for` loop only iterates to `4`. Show the `1..=5` syntax for " +"an inclusive range." +msgstr "" -#: src/basic-syntax/rustdoc.md:39 +#: src/control-flow-basics/break-continue.md:3 +#, fuzzy msgid "" -"Rustdoc comments can contain code snippets that we can run and test using " -"`cargo test`. We will discuss these tests in the [Testing section](../" -"testing/doc-tests.html)." +"If you want to exit any kind of loop early, use [`break`](https://doc.rust-" +"lang.org/reference/expressions/loop-expr.html#break-expressions). For " +"`loop`, this can take an optional expression that becomes the value of the " +"`loop` expression." msgstr "" -"Rustdoc 注释可以包含我们可使用“cargo test”运行和测试的代码段。我们将在[“测" -"试”部分](../testing/doc-tests.html)中讨论这些测试。" +"如果你想提前退出循环，请使用 [`break`](https://doc.rust-lang.org/reference/" +"expressions/loop-expr.html#break-expressions)，" -#: src/basic-syntax/methods.md:3 +#: src/control-flow-basics/break-continue.md:8 msgid "" -"Methods are functions associated with a type. The `self` argument of a " -"method is an instance of the type it is associated with:" +"If you want to immediately start the next iteration use [`continue`](https://" +"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." +msgstr "" +"如果需要立即启动 下一次迭代，请使用 [`continue`](https://doc.rust-lang.org/" +"reference/expressions/loop-expr.html#continue-expressions)。" + +#: src/control-flow-basics/break-continue.md:24 +msgid "\"{result}\"" msgstr "" -"方法是与某种类型关联的函数。方法的 `self` 参数是与其关联类型的一个实例：" -#: src/basic-syntax/methods.md:6 +#: src/control-flow-basics/break-continue.md:28 msgid "" -"```rust,editable\n" -"struct Rectangle {\n" -" width: u32,\n" -" height: u32,\n" -"}\n" -"\n" -"impl Rectangle {\n" -" fn area(&self) -> u32 {\n" -" self.width * self.height\n" -" }\n" -"\n" -" fn inc_width(&mut self, delta: u32) {\n" -" self.width += delta;\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut rect = Rectangle { width: 10, height: 5 };\n" -" println!(\"old area: {}\", rect.area());\n" -" rect.inc_width(5);\n" -" println!(\"new area: {}\", rect.area());\n" -"}\n" -"```" +"Both `continue` and `break` can optionally take a label argument which is " +"used to break out of nested loops:" +msgstr "`continue` 和 `break` 都可以选择接受一个标签参数，用来 终止嵌套循环：" + +#: src/control-flow-basics/break-continue.md:37 +msgid "\"x: {x}, i: {i}\"" msgstr "" -#: src/basic-syntax/methods.md:30 +#: src/control-flow-basics/break-continue.md:47 msgid "" -"We will look much more at methods in today's exercise and in tomorrow's " -"class." -msgstr "我们将在今天的练习和明天的课程中更深入地学习方法相关的概念。" - -#: src/basic-syntax/methods.md:34 -#, fuzzy -msgid "Add a static method called `Rectangle::new` and call this from `main`:" -msgstr "新增一个 `Rectangle::new` 构造函数并在 `main` 函数中调用它:" +"In this case we break the outer loop after 3 iterations of the inner loop." +msgstr "在本示例中，我们会在内循环 3 次迭代后终止外循环。" -#: src/basic-syntax/methods.md:42 +#: src/control-flow-basics/break-continue.md:51 msgid "" -"While _technically_, Rust does not have custom constructors, static methods " -"are commonly used to initialize structs (but don't have to). The actual " -"constructor, `Rectangle { width, height }`, could be called directly. See " -"the [Rustnomicon](https://doc.rust-lang.org/nomicon/constructors.html)." +"Note that `loop` is the only looping construct which returns a non-trivial " +"value. This is because it's guaranteed to be entered at least once (unlike " +"`while` and `for` loops)." msgstr "" -"虽然从技术层面来讲，Rust 没有自定义构造函数，但静态方法通常用于初始化结构体" -"（但并非必须这样做）。您可以直接调用实际构造函数“Rectangle { width, " -"height }”。请参阅 [Rust 秘典](https://doc.rust-lang.org/nomicon/constructors." -"html)。" +"请注意，`loop` 是唯一返回有意义的值的循环结构。 这是因为它保证至少被输入一次" +"（与 `while` 和 `for` 循环不同）。" + +#: src/control-flow-basics/blocks-and-scopes.md:3 +msgid "Blocks" +msgstr "块" -#: src/basic-syntax/methods.md:45 +#: src/control-flow-basics/blocks-and-scopes.md:5 #, fuzzy msgid "" -"Add a `Rectangle::square(width: u32)` constructor to illustrate that such " -"static methods can take arbitrary parameters." +"A block in Rust contains a sequence of expressions. Each block has a value " +"and a type, which are those of the last expression of the block:" +msgstr "Rust 中的块包含值和类型：值是 块的最后一个表达式：" + +#: src/control-flow-basics/blocks-and-scopes.md:13 +msgid "\"y: {y}\"" msgstr "" -"新增一个 `Rectangle::new_square(width: u32)` 构造函数来说明构造函数可以接受任" -"意参数。" -#: src/basic-syntax/functions-interlude.md:1 -msgid "Function Overloading" -msgstr "函数重载" +#: src/control-flow-basics/blocks-and-scopes.md:20 +#, fuzzy +msgid "" +"If the last expression ends with `;`, then the resulting value and type is " +"`()`." +msgstr "不过，如果最后一个表达式以 `;` 结尾，那么生成的值和类型为 `()`。" -#: src/basic-syntax/functions-interlude.md:3 -msgid "Overloading is not supported:" -msgstr "不支持重载：" +#: src/control-flow-basics/blocks-and-scopes.md:22 +msgid "Scopes and Shadowing" +msgstr "作用域和遮蔽（Shadowing）" -#: src/basic-syntax/functions-interlude.md:5 -msgid "Each function has a single implementation:" -msgstr "每一个函数都只有一种实现：" +#: src/control-flow-basics/blocks-and-scopes.md:24 +msgid "A variable's scope is limited to the enclosing block." +msgstr "" -#: src/basic-syntax/functions-interlude.md:6 -msgid "Always takes a fixed number of parameters." -msgstr "始终接受固定个数的形参。" +#: src/control-flow-basics/blocks-and-scopes.md:26 +msgid "" +"You can shadow variables, both those from outer scopes and variables from " +"the same scope:" +msgstr "你可以隐藏变量，位于外部作用域的变量和 相同作用域的变量都可以：" -#: src/basic-syntax/functions-interlude.md:7 -msgid "Always takes a single set of parameter types." -msgstr "始终接受一组形参类型。" +#: src/control-flow-basics/blocks-and-scopes.md:32 +msgid "\"before: {a}\"" +msgstr "" -#: src/basic-syntax/functions-interlude.md:8 -msgid "Default values are not supported:" -msgstr "不支持提供默认值：" +#: src/control-flow-basics/blocks-and-scopes.md:34 +#: src/std-traits/from-and-into.md:7 src/std-traits/from-and-into.md:19 +#: src/slices-and-lifetimes/solution.md:225 +msgid "\"hello\"" +msgstr "" -#: src/basic-syntax/functions-interlude.md:9 -msgid "All call sites have the same number of arguments." -msgstr "实参的数量在所有调用的地方都是一样的。" +#: src/control-flow-basics/blocks-and-scopes.md:35 +msgid "\"inner scope: {a}\"" +msgstr "" -#: src/basic-syntax/functions-interlude.md:10 -msgid "Macros are sometimes used as an alternative." -msgstr "有时可以用宏（Macro）作为替代。" +#: src/control-flow-basics/blocks-and-scopes.md:38 +msgid "\"shadowed in inner scope: {a}\"" +msgstr "" -#: src/basic-syntax/functions-interlude.md:12 -msgid "However, function parameters can be generic:" -msgstr "然而，函数形参可以是泛型（generics）：" +#: src/control-flow-basics/blocks-and-scopes.md:41 +msgid "\"after: {a}\"" +msgstr "" -#: src/basic-syntax/functions-interlude.md:14 +#: src/control-flow-basics/blocks-and-scopes.md:47 msgid "" -"```rust,editable\n" -"fn pick_one(a: T, b: T) -> T {\n" -" if std::process::id() % 2 == 0 { a } else { b }\n" -"}\n" -"\n" -"fn main() {\n" -" println!(\"coin toss: {}\", pick_one(\"heads\", \"tails\"));\n" -" println!(\"cash prize: {}\", pick_one(500, 1000));\n" -"}\n" -"```" +"You can show how the value of the block changes by changing the last line in " +"the block. For instance, adding/removing a semicolon or using a `return`." msgstr "" -"```rust,editable\n" -"fn pick_one(a: T, b: T) -> T {\n" -" if std::process::id() % 2 == 0 { a } else { b }\n" -"}\n" -"\n" -"fn main() {\n" -" println!(\"coin toss: {}\", pick_one(\"heads\", \"tails\"));\n" -" println!(\"cash prize: {}\", pick_one(500, 1000));\n" -"}\n" -"```" +"你可以通过更改块的最后一行，来展示块值的变化情况。例如，添加/移除分号或使用 " +"`return`。" -#: src/basic-syntax/functions-interlude.md:27 +#: src/control-flow-basics/blocks-and-scopes.md:49 msgid "" -"When using generics, the standard library's `Into` can provide a kind of " -"limited polymorphism on argument types. We will see more details in a later " -"section." +"Show that a variable's scope is limited by adding a `b` in the inner block " +"in the last example, and then trying to access it outside that block." msgstr "" -"标准库中的 `Into` 通过泛型参数提供了一种具有有限多态性的参数类型。详见之后" -"的章节。" - -#: src/exercises/day-1/morning.md:1 -msgid "Day 1: Morning Exercises" -msgstr "第一天上午习题" - -#: src/exercises/day-1/morning.md:3 -msgid "In these exercises, we will explore two parts of Rust:" -msgstr "在这些习题中，我们将探索 Rust 的两个部分：" - -#: src/exercises/day-1/morning.md:5 -msgid "Implicit conversions between types." -msgstr "类型之间的隐式转换。" -#: src/exercises/day-1/morning.md:7 -msgid "Arrays and `for` loops." -msgstr "数组和 `for` 循环。" - -#: src/exercises/day-1/morning.md:11 -msgid "A few things to consider while solving the exercises:" -msgstr "在解题时要考虑几件事：" - -#: src/exercises/day-1/morning.md:13 -msgid "" -"Use a local Rust installation, if possible. This way you can get auto-" -"completion in your editor. See the page about [Using Cargo](../../cargo.md) " -"for details on installing Rust." -msgstr "" -"最好使用本地安装的 Rust，以实现在编辑器中自动补全。关于安装 Rust 的细节，请参" -"见 \\[使用 Cargo\\] 页面。" - -#: src/exercises/day-1/morning.md:17 -msgid "Alternatively, use the Rust Playground." -msgstr "也可以使用 Rust Playground 作为替代。" - -#: src/exercises/day-1/morning.md:19 +#: src/control-flow-basics/blocks-and-scopes.md:51 +#, fuzzy msgid "" -"The code snippets are not editable on purpose: the inline code snippets lose " -"their state if you navigate away from the page." +"Shadowing is different from mutation, because after shadowing both " +"variable's memory locations exist at the same time. Both are available under " +"the same name, depending where you use it in the code." msgstr "" -"页面内嵌的代码片段是不可编辑的：因为离开页面后内嵌代码片段中的修改会丢失。" +"定义: 遮蔽和变更（mutation）不同，因为在遮蔽之后，两个变量都会同时存在于内存" +"的不同位置中。在同一个名字下的两个变量都是可以被使用的，但是你在代码的哪里使" +"用会最终决定你使用哪一个变量。" -#: src/exercises/day-1/morning.md:22 src/exercises/day-2/morning.md:11 -#: src/exercises/day-3/morning.md:9 src/exercises/bare-metal/morning.md:7 -#: src/exercises/concurrency/morning.md:12 +#: src/control-flow-basics/blocks-and-scopes.md:54 #, fuzzy -msgid "" -"After looking at the exercises, you can look at the [solutions](solutions-" -"morning.md) provided." -msgstr "读完习题后，可以阅读本书提供的 \\[题解\\]。" +msgid "A shadowing variable can have a different type." +msgstr "一个遮蔽变量可以具有不同的类型。" -#: src/exercises/day-1/implicit-conversions.md:3 +#: src/control-flow-basics/blocks-and-scopes.md:55 msgid "" -"Rust will not automatically apply _implicit conversions_ between types " -"([unlike C++](https://en.cppreference.com/w/cpp/language/" -"implicit_conversion)). You can see this in a program like this:" -msgstr "" -"[与 C++ 不同](https://en.cppreference.com/w/cpp/language/" -"implicit_conversion)，Rust 不会自动进行 _隐式类型转换_。例如，下面的程序中不" -"存在隐式类型转换：" +"Shadowing looks obscure at first, but is convenient for holding on to values " +"after `.unwrap()`." +msgstr "隐藏起初看起来会有些晦涩，但是它很便于存 `.unwrap()` 之后的得到的值。" -#: src/exercises/day-1/implicit-conversions.md:20 +#: src/control-flow-basics/functions.md:21 msgid "" -"The Rust integer types all implement the [`From`](https://doc.rust-lang." -"org/std/convert/trait.From.html) and [`Into`](https://doc.rust-lang.org/" -"std/convert/trait.Into.html) traits to let us convert between them. The " -"`From` trait has a single `from()` method and similarly, the `Into` " -"trait has a single `into()` method. Implementing these traits is how a type " -"expresses that it can be converted into another type." -msgstr "" -"Rust 的整数类型都实现了 [`From`](https://doc.rust-lang.org/std/convert/" -"trait.From.html) 和 [`Into`](https://doc.rust-lang.org/std/convert/trait." -"Into.html) trait，使得我们可以在它们之间进行转换。`From` trait 包含 " -"`from()` 方法，`Into` trait 包含 `into()` 方法。类型通过实现这些 trait 来" -"表达它将被如何转换为另一个类型。" +"Declaration parameters are followed by a type (the reverse of some " +"programming languages), then a return type." +msgstr "类型跟随在声明的参数后（与某些编程语言相反），然后是返回类型。" -#: src/exercises/day-1/implicit-conversions.md:26 +#: src/control-flow-basics/functions.md:23 +#, fuzzy msgid "" -"The standard library has an implementation of `From for i16`, which " -"means that we can convert a variable `x` of type `i8` to an `i16` by " -"calling `i16::from(x)`. Or, simpler, with `x.into()`, because `From for " -"i16` implementation automatically create an implementation of `Into for " -"i8`." +"The last expression in a function body (or any block) becomes the return " +"value. Simply omit the `;` at the end of the expression. The `return` " +"keyword can be used for early return, but the \"bare value\" form is " +"idiomatic at the end of a function (refactor `gcd` to use a `return`)." msgstr "" -"标准库中包含 `From for i16` 的实现，即我们可以通过调用 `i16::from(x)` 来" -"将 `i8` 类型的变量 `x` 转换为 `i16`。或者也可以简单地使用 `x.into()`，因为 " -"`From for i16` 的实现会自动创建 `Into for i8` 的实现。" +"函数体（或任何块）中的最后一个表达式将成为返回值。只需省略表达式末尾的 `;` 即" +"可。" -#: src/exercises/day-1/implicit-conversions.md:31 +#: src/control-flow-basics/functions.md:27 msgid "" -"The same applies for your own `From` implementations for your own types, so " -"it is sufficient to only implement `From` to get a respective `Into` " -"implementation automatically." +"Some functions have no return value, and return the 'unit type', `()`. The " +"compiler will infer this if the `-> ()` return type is omitted." msgstr "" -"这同样也适用于自定义类型的 `From` 实现，只需实现 `From` 就可以自动得到对应的 " -"`Into` 实现。" - -#: src/exercises/day-1/implicit-conversions.md:34 -msgid "Execute the above program and look at the compiler error." -msgstr "执行上述程序，并查看对应的编译错误。" +"有些函数没有返回值，会返回“单元类型（unit type）”`()`。如果省略了`-> ()`的返" +"回类型，编译器将会自动推断。" -#: src/exercises/day-1/implicit-conversions.md:36 -msgid "Update the code above to use `into()` to do the conversion." -msgstr "修改代码，使用 `into()` 进行类型转换。" +#: src/control-flow-basics/functions.md:29 +#, fuzzy +msgid "" +"Overloading is not supported -- each function has a single implementation." +msgstr "每一个函数都只有一种实现：" -#: src/exercises/day-1/implicit-conversions.md:38 +#: src/control-flow-basics/functions.md:30 msgid "" -"Change the types of `x` and `y` to other things (such as `f32`, `bool`, " -"`i128`) to see which types you can convert to which other types. Try " -"converting small types to big types and the other way around. Check the " -"[standard library documentation](https://doc.rust-lang.org/std/convert/trait." -"From.html) to see if `From` is implemented for the pairs you check." +"Always takes a fixed number of parameters. Default arguments are not " +"supported. Macros can be used to support variadic functions." msgstr "" -"修改 `x` 和 `y` 的类型（例如 `f32`, `bool`, `i128` 等）来了解哪些类型之间可以" -"相互转换。尝试将较小的类型转换为较大的类型和将较大的类型转换为较小的类型。阅" -"读 [标准库文档](https://doc.rust-lang.org/std/convert/trait.From.html) 来了解" -"对于你所尝试的两个类型 `From` 是否已被实现。" -#: src/exercises/day-1/for-loops.md:1 -#: src/exercises/day-1/solutions-morning.md:3 -msgid "Arrays and `for` Loops" -msgstr "数组与 `for` 循环" - -#: src/exercises/day-1/for-loops.md:3 -msgid "We saw that an array can be declared like this:" -msgstr "我们可以这样声明一个数组：" - -#: src/exercises/day-1/for-loops.md:9 +#: src/control-flow-basics/functions.md:32 +#, fuzzy msgid "" -"You can print such an array by asking for its debug representation with `{:?}" -"`:" -msgstr "你可以使用 `{:?}` 来打印这种数组的调试格式：" +"Always takes a single set of parameter types. These types can be generic, " +"which will be covered later." +msgstr "始终接受一组形参类型。" -#: src/exercises/day-1/for-loops.md:19 +#: src/control-flow-basics/macros.md:3 msgid "" -"Rust lets you iterate over things like arrays and ranges using the `for` " -"keyword:" -msgstr "在 Rust 中，可以使用 `for` 关键词遍历数组和区间等元素：" +"Macros are expanded into Rust code during compilation, and can take a " +"variable number of arguments. They are distinguished by a `!` at the end. " +"The Rust standard library includes an assortment of useful macros." +msgstr "" -#: src/exercises/day-1/for-loops.md:22 +#: src/control-flow-basics/macros.md:7 #, fuzzy msgid "" -"```rust,editable\n" -"fn main() {\n" -" let array = [10, 20, 30];\n" -" print!(\"Iterating over array:\");\n" -" for n in &array {\n" -" print!(\" {n}\");\n" -" }\n" -" println!();\n" -"\n" -" print!(\"Iterating over range:\");\n" -" for i in 0..3 {\n" -" print!(\" {}\", array[i]);\n" -" }\n" -" println!();\n" -"}\n" -"```" +"`println!(format, ..)` prints a line to standard output, applying formatting " +"described in [`std::fmt`](https://doc.rust-lang.org/std/fmt/index.html)." msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let array = [10, 20, 30];\n" -" print!(\"Iterating over array:\");\n" -" for n in array {\n" -" print!(\" {n}\");\n" -" }\n" -" println!();\n" -"\n" -" print!(\"Iterating over range:\");\n" -" for i in 0..3 {\n" -" print!(\" {}\", array[i]);\n" -" }\n" -" println!();\n" -"}\n" -"```" +"运算符重载是通过 [`std::ops`](https://doc.rust-lang.org/std/ops/index.html) " +"中的特征实现的：" -#: src/exercises/day-1/for-loops.md:39 +#: src/control-flow-basics/macros.md:9 msgid "" -"Use the above to write a function `pretty_print` which pretty-print a matrix " -"and a function `transpose` which will transpose a matrix (turn rows into " -"columns):" +"`format!(format, ..)` works just like `println!` but returns the result as a " +"string." msgstr "" -"使用以上知识，写一个用易读的格式输出矩阵的 `pretty_print` 函数，以及一个对矩" -"阵进行转置（将行和列互换）的 `transpose` 函数：" -#: src/exercises/day-1/for-loops.md:49 -msgid "Hard-code both functions to operate on 3 × 3 matrices." -msgstr "硬编码这两个函数，让它们处理 3 × 3 的矩阵。" +#: src/control-flow-basics/macros.md:11 +msgid "`dbg!(expression)` logs the value of the expression and returns it." +msgstr "" -#: src/exercises/day-1/for-loops.md:51 +#: src/control-flow-basics/macros.md:12 msgid "" -"Copy the code below to and implement the " -"functions:" -msgstr "将下面的代码复制到 并实现上述函数：" +"`todo!()` marks a bit of code as not-yet-implemented. If executed, it will " +"panic." +msgstr "" -#: src/exercises/day-1/for-loops.md:54 +#: src/control-flow-basics/macros.md:14 msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn main() {\n" -" let matrix = [\n" -" [101, 102, 103], // <-- the comment makes rustfmt add a newline\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -"\n" -" println!(\"matrix:\");\n" -" pretty_print(&matrix);\n" -"\n" -" let transposed = transpose(matrix);\n" -" println!(\"transposed:\");\n" -" pretty_print(&transposed);\n" -"}\n" -"```" +"`unreachable!()` marks a bit of code as unreachable. If executed, it will " +"panic." msgstr "" -"```rust,should_panic\n" -"// TODO: 完成你的实现后移除此行。\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn main() {\n" -" let matrix = [\n" -" [101, 102, 103], // <-- 这个注释会让 rustfmt 添加一个新行\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -"\n" -" println!(\"matrix:\");\n" -" pretty_print(&matrix);\n" -"\n" -" let transposed = transpose(matrix);\n" -" println!(\"transposed:\");\n" -" pretty_print(&transposed);\n" -"}\n" -"```" -#: src/exercises/day-1/for-loops.md:82 -msgid "Bonus Question" -msgstr "附加题" +#: src/control-flow-basics/macros.md:32 +msgid "\"{n}! = {}\"" +msgstr "" -#: src/exercises/day-1/for-loops.md:84 +#: src/control-flow-basics/macros.md:38 msgid "" -"Could you use `&[i32]` slices instead of hard-coded 3 × 3 matrices for your " -"argument and return types? Something like `&[&[i32]]` for a two-dimensional " -"slice-of-slices. Why or why not?" +"The takeaway from this section is that these common conveniences exist, and " +"how to use them. Why they are defined as macros, and what they expand to, is " +"not especially critical." msgstr "" -"是否可以使用 `&[i32]` 切片而不是硬编码的 3 × 3 矩阵作为函数的参数和返回类型？" -"例如使用 `&[&[i32]]` 表示一个二维的切片的切片。为什么这样做是可行或不可行的？" -#: src/exercises/day-1/for-loops.md:89 +#: src/control-flow-basics/macros.md:42 msgid "" -"See the [`ndarray` crate](https://docs.rs/ndarray/) for a production quality " -"implementation." +"The course does not cover defining macros, but a later section will describe " +"use of derive macros." msgstr "" -"参考 [`ndarray` crate](https://docs.rs/ndarray/) 以了解该功能满足生产环境质量" -"的实现。" -#: src/exercises/day-1/for-loops.md:94 +#: src/control-flow-basics/exercise.md:3 msgid "" -"The solution and the answer to the bonus section are available in the " -"[Solution](solutions-morning.md#arrays-and-for-loops) section." +"The [Collatz Sequence](https://en.wikipedia.org/wiki/Collatz_conjecture) is " +"defined as follows, for an arbitrary n" msgstr "" -"题目解答和附加题的答案在 [题解](solutions-morning.md#arrays-and-for-loops) 章" -"节中。" -#: src/exercises/day-1/for-loops.md:97 -msgid "" -"The use of the reference `&array` within `for n in &array` is a subtle " -"preview of issues of ownership that will come later in the afternoon." +#: src/control-flow-basics/exercise.md:4 src/control-flow-basics/exercise.md:10 +msgid "1" msgstr "" -"在“for n in &array”中使用引用“&array”这一做法巧妙地预先展示了下午将谈到的所有" -"权问题。" -#: src/exercises/day-1/for-loops.md:100 -msgid "Without the `&`..." -msgstr "如果不使用“&”…" +#: src/control-flow-basics/exercise.md:4 +msgid " greater than zero:" +msgstr "" -#: src/exercises/day-1/for-loops.md:101 -msgid "" -"The loop would have been one that consumes the array. This is a change " -"[introduced in the 2021 Edition](https://doc.rust-lang.org/edition-guide/" -"rust-2021/IntoIterator-for-arrays.html)." +#: src/control-flow-basics/exercise.md:6 src/control-flow-basics/exercise.md:7 +#: src/control-flow-basics/exercise.md:8 +msgid "If _n" msgstr "" -"循环将会是一个使用数组的循环。这是一项[在 2021 年版中引入](https://doc.rust-" -"lang.org/edition-guide/rust-2021/IntoIterator-for-arrays.html)的变更。" -#: src/exercises/day-1/for-loops.md:104 -msgid "" -"An implicit array copy would have occurred. Since `i32` is a copy type, " -"then `[i32; 3]` is also a copy type." +#: src/control-flow-basics/exercise.md:6 src/control-flow-basics/exercise.md:7 +#: src/control-flow-basics/exercise.md:8 +msgid "i" msgstr "" -"会发生隐式数组复制。由于“i32”是复制类型，因此“\\[i32; 3\\]”也是复制类型。" -#: src/control-flow.md:3 -msgid "" -"As we have seen, `if` is an expression in Rust. It is used to conditionally " -"evaluate one of two blocks, but the blocks can have a value which then " -"becomes the value of the `if` expression. Other control flow expressions " -"work similarly in Rust." +#: src/control-flow-basics/exercise.md:6 +msgid "_ is 1, then the sequence terminates at _n" msgstr "" -"正如我们所知，`if` 是 Rust 中的一个表达式。它用于有条件地 评估两个块中的一" -"个，但这些块可以有一个值， 然后成为 `if` 表达式的值。其他控制流表达式在 Rust " -"中也有类似 的运作方式。" -#: src/control-flow/blocks.md:3 -#, fuzzy -msgid "" -"A block in Rust contains a sequence of expressions. Each block has a value " -"and a type, which are those of the last expression of the block:" -msgstr "Rust 中的块包含值和类型：值是 块的最后一个表达式：" +#: src/control-flow-basics/exercise.md:6 +msgid "_." +msgstr "" -#: src/control-flow/blocks.md:27 -#, fuzzy -msgid "" -"If the last expression ends with `;`, then the resulting value and type is " -"`()`." -msgstr "不过，如果最后一个表达式以 `;` 结尾，那么生成的值和类型为 `()`。" +#: src/control-flow-basics/exercise.md:7 +msgid "_ is even, then _n" +msgstr "" -#: src/control-flow/blocks.md:29 -msgid "" -"The same rule is used for functions: the value of the function body is the " -"return value:" -msgstr "同样的规则也适用于函数：函数主体的值 是返回值：" +#: src/control-flow-basics/exercise.md:7 src/control-flow-basics/exercise.md:8 +msgid "i+1" +msgstr "" -#: src/control-flow/blocks.md:45 src/enums.md:34 src/enums/sizes.md:28 -#: src/pattern-matching.md:25 src/pattern-matching/match-guards.md:22 -#: src/structs.md:31 src/methods.md:30 src/methods/example.md:46 -msgid "Key Points:" -msgstr "关键点：" +#: src/control-flow-basics/exercise.md:7 +msgid " = n" +msgstr "" -#: src/control-flow/blocks.md:46 -msgid "" -"The point of this slide is to show that blocks have a type and value in " -"Rust. " -msgstr "这张幻灯片的重点是说明在 Rust 中，块有类型和值。" +#: src/control-flow-basics/exercise.md:7 +msgid " / 2_." +msgstr "" -#: src/control-flow/blocks.md:47 -msgid "" -"You can show how the value of the block changes by changing the last line in " -"the block. For instance, adding/removing a semicolon or using a `return`." +#: src/control-flow-basics/exercise.md:8 +msgid "_ is odd, then _n" msgstr "" -"你可以通过更改块的最后一行，来展示块值的变化情况。例如，添加/移除分号或使用 " -"`return`。" -#: src/control-flow/if-expressions.md:1 -msgid "`if` expressions" -msgstr "`if` 表达式" +#: src/control-flow-basics/exercise.md:8 +msgid " = 3 * n" +msgstr "" -#: src/control-flow/if-expressions.md:3 -msgid "" -"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" -"if-expr.html#if-expressions) exactly like `if` statements in other languages:" +#: src/control-flow-basics/exercise.md:8 +msgid " + 1_." msgstr "" -"[`if` 表达式](https://doc.rust-lang.org/reference/expressions/if-expr." -"html#if-expressions) 的用法与其他语言中的 `if` 语句完全一样。" -#: src/control-flow/if-expressions.md:18 -msgid "" -"In addition, you can use `if` as an expression. The last expression of each " -"block becomes the value of the `if` expression:" +#: src/control-flow-basics/exercise.md:10 +msgid "For example, beginning with _n" msgstr "" -"此外，你还可以将 `if` 用作一个表达式。每个块的最后一个表达式 将成为 `if` 表达" -"式的值：" -#: src/control-flow/if-expressions.md:35 -msgid "" -"Because `if` is an expression and must have a particular type, both of its " -"branch blocks must have the same type. Consider showing what happens if you " -"add `;` after `x / 2` in the second example." +#: src/control-flow-basics/exercise.md:10 +msgid "_ = 3:" msgstr "" -"由于 `if` 是一个表达式且必须有一个特定的类型，因此它的两个分支块必须有相同的" -"类型。考虑在第二个示例中将 `;` 添加到 `x / 2` 的后面，看看会出现什么情况。" -#: src/control-flow/for-expressions.md:1 -msgid "`for` loops" -msgstr "`for` 循环" +#: src/control-flow-basics/exercise.md:12 +msgid "3 is odd, so _n" +msgstr "" -#: src/control-flow/for-expressions.md:3 -#, fuzzy -msgid "" -"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) is closely " -"related to the [`while let` loop](while-let-expressions.md). It will " -"automatically call `into_iter()` on the expression and then iterate over it:" +#: src/control-flow-basics/exercise.md:12 +msgid "2" msgstr "" -"[`for` 循环](https://doc.rust-lang.org/std/keyword.for.html) 与 [`when let` " -"循环](when-let-expression.md)密切相关。它会 自动对表达式调用 `into_iter()`，" -"然后对其进行迭代：" -#: src/control-flow/for-expressions.md:22 -msgid "You can use `break` and `continue` here as usual." -msgstr "你可以在此照常使用 `break` 和 `continue`。" +#: src/control-flow-basics/exercise.md:12 +msgid "_ = 3 * 3 + 1 = 10;" +msgstr "" -#: src/control-flow/for-expressions.md:26 -msgid "Index iteration is not a special syntax in Rust for just that case." -msgstr "在这种情况下，索引迭代在 Rust 中并不是一个特殊的语法。" +#: src/control-flow-basics/exercise.md:13 +msgid "10 is even, so _n" +msgstr "" -#: src/control-flow/for-expressions.md:27 -msgid "`(0..10)` is a range that implements an `Iterator` trait. " -msgstr "`(0..10)` 是实现 `Iterator` trait 的区间。" +#: src/control-flow-basics/exercise.md:13 src/bare-metal/aps/better-uart.md:22 +msgid "3" +msgstr "" -#: src/control-flow/for-expressions.md:28 -msgid "" -"`step_by` is a method that returns another `Iterator` that skips every other " -"element. " -msgstr "`step_by` 是返回另一个 `Iterator` 的方法，用于逐一跳过所有其他元素。" +#: src/control-flow-basics/exercise.md:13 +msgid "_ = 10 / 2 = 5;" +msgstr "" -#: src/control-flow/for-expressions.md:29 -msgid "" -"Modify the elements in the vector and explain the compiler errors. Change " -"vector `v` to be mutable and the for loop to `for x in v.iter_mut()`." +#: src/control-flow-basics/exercise.md:14 +msgid "5 is odd, so _n" msgstr "" -"修改矢量中的元素并说明编译器错误。将矢量 `v` 改为可变，并将 for 循环改为 " -"`for x in v.iter_mut()`。" -#: src/control-flow/while-expressions.md:1 -msgid "`while` loops" -msgstr "`while` 循环" +#: src/control-flow-basics/exercise.md:14 src/bare-metal/aps/better-uart.md:10 +msgid "4" +msgstr "" -#: src/control-flow/while-expressions.md:3 -msgid "" -"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" -"expr.html#predicate-loops) works very similar to other languages:" +#: src/control-flow-basics/exercise.md:14 +msgid "_ = 3 * 15 + 1 = 16;" msgstr "" -"[`while` 关键字](https://doc.rust-lang.org/reference/expressions/loop-expr." -"html#predicate-loops) 的工作方式与其他语言非常相似：" -#: src/control-flow/break-continue.md:1 -msgid "`break` and `continue`" -msgstr "`break` 和 `continue`" +#: src/control-flow-basics/exercise.md:15 +msgid "16 is even, so _n" +msgstr "" -#: src/control-flow/break-continue.md:3 -msgid "" -"If you want to exit a loop early, use [`break`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#break-expressions)," +#: src/control-flow-basics/exercise.md:15 +msgid "5" msgstr "" -"如果你想提前退出循环，请使用 [`break`](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#break-expressions)，" -#: src/control-flow/break-continue.md:4 -msgid "" -"If you want to immediately start the next iteration use [`continue`](https://" -"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." +#: src/control-flow-basics/exercise.md:15 +msgid "_ = 16 / 2 = 8;" msgstr "" -"如果需要立即启动 下一次迭代，请使用 [`continue`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#continue-expressions)。" -#: src/control-flow/break-continue.md:7 -msgid "" -"Both `continue` and `break` can optionally take a label argument which is " -"used to break out of nested loops:" -msgstr "`continue` 和 `break` 都可以选择接受一个标签参数，用来 终止嵌套循环：" +#: src/control-flow-basics/exercise.md:16 +msgid "8 is even, so _n" +msgstr "" -#: src/control-flow/break-continue.md:29 -msgid "" -"In this case we break the outer loop after 3 iterations of the inner loop." -msgstr "在本示例中，我们会在内循环 3 次迭代后终止外循环。" +#: src/control-flow-basics/exercise.md:16 src/bare-metal/aps/better-uart.md:14 +#: src/bare-metal/aps/better-uart.md:17 +msgid "6" +msgstr "" -#: src/control-flow/loop-expressions.md:1 -msgid "`loop` expressions" -msgstr "`loop` 表达式" +#: src/control-flow-basics/exercise.md:16 +msgid "_ = 8 / 2 = 4;" +msgstr "" -#: src/control-flow/loop-expressions.md:3 -msgid "" -"Finally, there is a [`loop` keyword](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#infinite-loops) which creates an endless loop." +#: src/control-flow-basics/exercise.md:17 +msgid "4 is even, so _n" msgstr "" -"最后是用于创建无限循环的 [`loop` 关键字](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#infinite-loops) 。" -#: src/control-flow/loop-expressions.md:6 -msgid "Here you must either `break` or `return` to stop the loop:" -msgstr "在下例中，你必须 `break` 或 `return` 才能停止循环：" +#: src/control-flow-basics/exercise.md:17 +msgid "7" +msgstr "" -#: src/control-flow/loop-expressions.md:28 -msgid "Break the `loop` with a value (e.g. `break 8`) and print it out." -msgstr "用一个值（例如 `break 8`）来中断 `loop` 并将其输出。" +#: src/control-flow-basics/exercise.md:17 +msgid "_ = 4 / 2 = 2;" +msgstr "" -#: src/control-flow/loop-expressions.md:29 -msgid "" -"Note that `loop` is the only looping construct which returns a non-trivial " -"value. This is because it's guaranteed to be entered at least once (unlike " -"`while` and `for` loops)." +#: src/control-flow-basics/exercise.md:18 +msgid "2 is even, so _n" msgstr "" -"请注意，`loop` 是唯一返回有意义的值的循环结构。 这是因为它保证至少被输入一次" -"（与 `while` 和 `for` 循环不同）。" -#: src/basic-syntax/variables.md:3 -msgid "" -"Rust provides type safety via static typing. Variable bindings are immutable " -"by default:" -msgstr "Rust 通过静态类型实现了类型安全。变量绑定默认是不可变的：" +#: src/control-flow-basics/exercise.md:18 src/bare-metal/aps/better-uart.md:12 +#: src/bare-metal/aps/better-uart.md:15 +msgid "8" +msgstr "" -#: src/basic-syntax/variables.md:18 -msgid "" -"Due to type inference the `i32` is optional. We will gradually show the " -"types less and less as the course progresses." +#: src/control-flow-basics/exercise.md:18 +msgid "_ = 1; and" msgstr "" -"由于类型推导，`i32` 可以省略。随着课程推进，我们会越来越少地看到类型声明。" -#: src/basic-syntax/type-inference.md:3 -msgid "Rust will look at how the variable is _used_ to determine the type:" -msgstr "Rust 会根据变量的使用来确定其类型：" +#: src/control-flow-basics/exercise.md:19 +msgid "the sequence terminates." +msgstr "" -#: src/basic-syntax/type-inference.md:27 +#: src/control-flow-basics/exercise.md:21 msgid "" -"This slide demonstrates how the Rust compiler infers types based on " -"constraints given by variable declarations and usages." -msgstr "这张幻灯片演示了 Rust 编译器是如何根据变量声明和用法来推导其类型的。" +"Write a function to calculate the length of the collatz sequence for a given " +"initial `n`." +msgstr "" -#: src/basic-syntax/type-inference.md:29 -msgid "" -"It is very important to emphasize that variables declared like this are not " -"of some sort of dynamic \"any type\" that can hold any data. The machine " -"code generated by such declaration is identical to the explicit declaration " -"of a type. The compiler does the job for us and helps us write more concise " -"code." +#: src/control-flow-basics/exercise.md:25 src/control-flow-basics/solution.md:4 +msgid "/// Determine the length of the collatz sequence beginning at `n`.\n" msgstr "" -"需要重点强调的是这样声明的变量并非像那种动态类型语言中可以持有任何数据的“任何" -"类型”。这种声明所生成的机器码与明确类型声明完全相同。编译器进行类型推导能够让" -"我们编写更简略的代码。" -#: src/basic-syntax/type-inference.md:33 -#, fuzzy -msgid "" -"The following code tells the compiler to copy into a certain generic " -"container without the code ever explicitly specifying the contained type, " -"using `_` as a placeholder:" +#: src/control-flow-basics/solution.md:20 src/concurrency/scoped-threads.md:11 +#: src/concurrency/scoped-threads.md:30 +msgid "\"Length: {}\"" msgstr "" -"下面的代码通过使用 `_` 占位符来告诉编译器无需明确指定其类型就可以将对应数据拷" -"贝到该容器： " -#: src/basic-syntax/type-inference.md:48 +#: src/welcome-day-1-afternoon.md:1 src/welcome-day-2-afternoon.md:1 +#: src/welcome-day-3-afternoon.md:1 src/welcome-day-4-afternoon.md:1 #, fuzzy +msgid "Welcome Back" +msgstr "欢迎" + +#: src/tuples-and-arrays/tuples-and-arrays.md:3 msgid "" -"[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." -"html#method.collect) relies on [`FromIterator`](https://doc.rust-lang.org/" -"std/iter/trait.FromIterator.html), which [`HashSet`](https://doc.rust-lang." -"org/std/collections/struct.HashSet.html#impl-FromIterator%3CT%3E-for-" -"HashSet%3CT,+S%3E) implements." +"Tuples and arrays are the first \"compound\" types we have seen. All " +"elements of an array have the same type, while tuples can accommodate " +"different types. Both types have a size fixed at compile time." msgstr "" -"[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." -"html#method.collect) 依赖 [`HashSet`](https://doc.rust-lang.org/std/iter/" -"trait.FromIterator.html) 实现的 `FromIterator`。" -#: src/basic-syntax/static-and-const.md:1 -msgid "Static and Constant Variables" -msgstr "静态变量和常量" +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +#: src/tuples-and-arrays/destructuring.md:27 +msgid "Arrays" +msgstr "数组（Arrays）" -#: src/basic-syntax/static-and-const.md:3 -msgid "" -"Static and constant variables are two different ways to create globally-" -"scoped values that cannot be moved or reallocated during the execution of " -"the program. " -msgstr "" -"静态变量和常量是创建全局范围值的两种不同方法，这类值在程序执行期间无法移动或" -"重新分配。" +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +msgid "`[T; N]`" +msgstr "`[T; N]`" -#: src/basic-syntax/static-and-const.md:6 -msgid "`const`" -msgstr "`const`" +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +msgid "`[20, 30, 40]`, `[0; 3]`" +msgstr "`[20, 30, 40]`, `[0; 3]`" -#: src/basic-syntax/static-and-const.md:8 -msgid "" -"Constant variables are evaluated at compile time and their values are " -"inlined wherever they are used:" -msgstr "系统会在编译时对常量变量进行求值；无论在何处使用，其值都会被内嵌：" +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +#: src/tuples-and-arrays/destructuring.md:9 +msgid "Tuples" +msgstr "元组（Tuples）" + +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +msgid "`()`, `(T,)`, `(T1, T2)`, ..." +msgstr "`()`, `(T,)`, `(T1, T2)`, ..." + +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +msgid "`()`, `('x',)`, `('x', 1.2)`, ..." +msgstr "`()`, `('x',)`, `('x', 1.2)`, ..." + +#: src/tuples-and-arrays/tuples-and-arrays.md:12 +msgid "Array assignment and access:" +msgstr "数组的赋值和访问操作：" + +#: src/tuples-and-arrays/tuples-and-arrays.md:24 +msgid "Tuple assignment and access:" +msgstr "元组的赋值和访问操作：" -#: src/basic-syntax/static-and-const.md:30 +#: src/tuples-and-arrays/tuples-and-arrays.md:40 +msgid "Arrays:" +msgstr "数组：" + +#: src/tuples-and-arrays/tuples-and-arrays.md:42 +#, fuzzy msgid "" -"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html) these are inlined upon use." +"A value of the array type `[T; N]` holds `N` (a compile-time constant) " +"elements of the same type `T`. Note that the length of the array is _part of " +"its type_, which means that `[u8; 3]` and `[u8; 4]` are considered two " +"different types. Slices, which have a size determined at runtime, are " +"covered later." msgstr "" -"根据 [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-vs-static." -"html) 这些变量在使用时是内联 (inlined) 的。" +"数组中的元素具有相同的类型 `T`，数组的长度为 `N`，`N` 是一个编译期常量。 需要" +"注意的是数组的长度是它_类型的一部分\\_, 这意味着 `[u8; 3]` 和 `[u8; 4]` 在 " +"Rust 中被认为是不同的类型。" -#: src/basic-syntax/static-and-const.md:32 +#: src/tuples-and-arrays/tuples-and-arrays.md:48 msgid "" -"Only functions marked `const` can be called at compile time to generate " -"`const` values. `const` functions can however be called at runtime." +"Try accessing an out-of-bounds array element. Array accesses are checked at " +"runtime. Rust can usually optimize these checks away, and they can be " +"avoided using unsafe Rust." msgstr "" -"在编译时只能调用标记为“const”的函数以生成“const”值。不过，可在运行时调" -"用“const”函数。" -#: src/basic-syntax/static-and-const.md:34 -msgid "`static`" -msgstr "`static`" +#: src/tuples-and-arrays/tuples-and-arrays.md:52 +msgid "We can use literals to assign values to arrays." +msgstr "我们可以使用字面量来为数组赋值。" -#: src/basic-syntax/static-and-const.md:36 +#: src/tuples-and-arrays/tuples-and-arrays.md:54 +#, fuzzy msgid "" -"Static variables will live during the whole execution of the program, and " -"therefore will not move:" -msgstr "静态变量在程序的整个执行过程中始终有效，因此不会移动：" - -#: src/basic-syntax/static-and-const.md:38 -msgid "" -"```rust,editable\n" -"static BANNER: &str = \"Welcome to RustOS 3.14\";\n" -"\n" -"fn main() {\n" -" println!(\"{BANNER}\");\n" -"}\n" -"```" +"The `println!` macro asks for the debug implementation with the `?` format " +"parameter: `{}` gives the default output, `{:?}` gives the debug output. " +"Types such as integers and strings implement the default output, but arrays " +"only implement the debug output. This means that we must use debug output " +"here." msgstr "" -"```rust,editable\n" -"static BANNER: &str = \"Welcome to RustOS 3.14\";\n" -"\n" -"fn main() {\n" -" println!(\"{BANNER}\");\n" -"}\n" -"```" +"在主函数中，打印（print）语句使用 `?` 格式请求调试实现。 使用参数 `{}` 打印默" +"认输出，`{:?}` 表示以调试格式输出。 我们也可以不在格式化字符串后面指定变量" +"值，直接使用 `{a}` 和 `{a:?}` 进行输出。" -#: src/basic-syntax/static-and-const.md:46 -#, fuzzy +#: src/tuples-and-arrays/tuples-and-arrays.md:59 msgid "" -"As noted in the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html), these are not inlined upon use and have an actual " -"associated memory location. This is useful for unsafe and embedded code, " -"and the variable lives through the entirety of the program execution. When a " -"globally-scoped value does not have a reason to need object identity, " -"`const` is generally preferred." +"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " +"easier to read." msgstr "" -"正如 [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-vs-static." -"html) 中所述，这些变量在使用时并不是内联的，而且还具有实际相关联的内存位置。" -"这对于不安全的嵌入式代码是有用的，并且这些变量存在于整个程序的执行过程之中。" +"添加 `#`，比如 `{a:#?}`，会输出“美观打印（pretty printing）” 格式，这种格式可" +"能会更加易读。" -#: src/basic-syntax/static-and-const.md:50 -msgid "" -"Because `static` variables are accessible from any thread, they must be " -"`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" -"lang.org/std/sync/struct.Mutex.html), atomic or similar. It is also possible " -"to have mutable statics, but they require manual synchronisation so any " -"access to them requires `unsafe` code. We will look at [mutable statics](../" -"unsafe/mutable-static-variables.md) in the chapter on Unsafe Rust." -msgstr "" -"由于“static”变量可从任何线程访问，因此它们必须是“Sync”。内部可变性可通过[“互" -"斥量”](https://doc.rust-lang.org/std/sync/struct.Mutex.html)、原子性或类似对" -"象实现。也可能具有可变静态项，但它们需要手动同步，因此对它们的任何访问都需" -"要“unsafe”代码。我们将在“不安全 Rust”章节中探讨[可变静态项](../unsafe/" -"mutable-static-variables.md)。" +#: src/tuples-and-arrays/tuples-and-arrays.md:62 +msgid "Tuples:" +msgstr "元组：" -#: src/basic-syntax/static-and-const.md:58 -msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." -msgstr "值得一提的是，`const` 在语义上与C++的 `constexpr` 类似。" +#: src/tuples-and-arrays/tuples-and-arrays.md:64 +msgid "Like arrays, tuples have a fixed length." +msgstr "和数组一样，元组也具有固定的长度。" -#: src/basic-syntax/static-and-const.md:59 +#: src/tuples-and-arrays/tuples-and-arrays.md:66 +msgid "Tuples group together values of different types into a compound type." +msgstr "元组将不同类型的值组成一个复合类型。" + +#: src/tuples-and-arrays/tuples-and-arrays.md:68 msgid "" -"`static`, on the other hand, is much more similar to a `const` or mutable " -"global variable in C++." -msgstr "另一方面，`static` 远远更类似于C++中的 `const` 或可改变的全局变量。" +"Fields of a tuple can be accessed by the period and the index of the value, " +"e.g. `t.0`, `t.1`." +msgstr "元组中的字段可以通过英文句号加上值的下标进行访问比如：`t.0`, `t.1`。" -#: src/basic-syntax/static-and-const.md:60 +#: src/tuples-and-arrays/tuples-and-arrays.md:71 #, fuzzy msgid "" -"`static` provides object identity: an address in memory and state as " -"required by types with interior mutability such as `Mutex`." +"The empty tuple `()` is also known as the \"unit type\". It is both a type, " +"and the only valid value of that type --- that is to say both the type and " +"its value are expressed as `()`. It is used to indicate, for example, that a " +"function or expression has no return value, as we'll see in a future slide." msgstr "" -"“static”提供对象标识：内存中的一个地址及具有内部可变性的类型（如“Mutex\n" -"\n" -"”）所需的状态。" +"空元组 `()` 也被称作 “单元（unit）类型”. 它既是一个类型， 也是这种类型的唯一" +"值——也就是说它的类型和它的值都被表示为 `()`。它通常用于表示，比如，一个函数或" +"表达式没有返回值，我们会在后续的幻灯片种见到这种用法。" -#: src/basic-syntax/static-and-const.md:61 +#: src/tuples-and-arrays/tuples-and-arrays.md:75 +#, fuzzy msgid "" -"It isn't super common that one would need a runtime evaluated constant, but " -"it is helpful and safer than using a static." -msgstr "" -"虽然需要使用在运行中求值的常量的情况并不是很常见，但是它是有帮助的，而且比使" -"用静态变量更安全。" +"You can think of it as `void` that can be familiar to you from other " +"programming languages." +msgstr "你可以将其理解为你可能在其他编程语言中比较熟悉的 `void` 类型。" -#: src/basic-syntax/static-and-const.md:62 -msgid "`thread_local` data can be created with the macro `std::thread_local`." -msgstr "可以使用宏“std::thread_local”创建“thread_local”数据。" +#: src/tuples-and-arrays/iteration.md:3 +msgid "The `for` statement supports iterating over arrays (but not tuples)." +msgstr "" -#: src/basic-syntax/static-and-const.md:64 -msgid "Properties table:" -msgstr "属性表：" +#: src/tuples-and-arrays/iteration.md:18 +msgid "" +"This functionality uses the `IntoIterator` trait, but we haven't covered " +"that yet." +msgstr "" -#: src/basic-syntax/static-and-const.md:66 -msgid "Property" -msgstr "属性" +#: src/tuples-and-arrays/iteration.md:21 +msgid "" +"The `assert_ne!` macro is new here. There are also `assert_eq!` and `assert!" +"` macros. These are always checked while, debug-only variants like " +"`debug_assert!` compile to nothing in release builds." +msgstr "" -#: src/basic-syntax/static-and-const.md:66 +#: src/tuples-and-arrays/match.md:3 #, fuzzy -msgid "Static" -msgstr "`static`" - -#: src/basic-syntax/static-and-const.md:66 -msgid "Constant" -msgstr "常量" +msgid "" +"The `match` keyword lets you match a value against one or more _patterns_. " +"The comparisons are done from top to bottom and the first match wins." +msgstr "" +"使用关键词 `match` 对一个值进行模式匹配。进行匹配时，会从上至下依次进行比较，" +"并选定第一个匹配成功的结果。" -#: src/basic-syntax/static-and-const.md:68 -msgid "Has an address in memory" -msgstr "在内存中有地址" +#: src/tuples-and-arrays/match.md:6 +msgid "The patterns can be simple values, similarly to `switch` in C and C++:" +msgstr "模式（pattern）可以是简单的值，其用法类似于 C 与 C++ 中的 `switch` 。" -#: src/basic-syntax/static-and-const.md:68 -#: src/basic-syntax/static-and-const.md:69 -#: src/basic-syntax/static-and-const.md:71 -#: src/basic-syntax/static-and-const.md:72 -msgid "Yes" -msgstr "是" +#: src/tuples-and-arrays/match.md:11 +msgid "'x'" +msgstr "" -#: src/basic-syntax/static-and-const.md:68 -msgid "No (inlined)" -msgstr "否（内嵌）" +#: src/tuples-and-arrays/match.md:13 +msgid "'q'" +msgstr "" -#: src/basic-syntax/static-and-const.md:69 -#, fuzzy -msgid "Lives for the entire duration of the program" -msgstr "`main` 函数是程序的入口。" +#: src/tuples-and-arrays/match.md:13 +msgid "\"Quitting\"" +msgstr "" -#: src/basic-syntax/static-and-const.md:69 -#: src/basic-syntax/static-and-const.md:70 -#: src/basic-syntax/static-and-const.md:72 -msgid "No" -msgstr "否" +#: src/tuples-and-arrays/match.md:14 src/std-traits/solution.md:16 +#: src/error-handling/exercise.md:62 src/error-handling/exercise.md:64 +#: src/error-handling/solution.md:62 src/error-handling/solution.md:64 +msgid "'a'" +msgstr "" -#: src/basic-syntax/static-and-const.md:70 -msgid "Can be mutable" -msgstr "可变" +#: src/tuples-and-arrays/match.md:14 +msgid "'s'" +msgstr "" -#: src/basic-syntax/static-and-const.md:70 -msgid "Yes (unsafe)" -msgstr "是（不安全）" +#: src/tuples-and-arrays/match.md:14 +msgid "'w'" +msgstr "" -#: src/basic-syntax/static-and-const.md:71 -#, fuzzy -msgid "Evaluated at compile time" -msgstr "值在编译时具有已知的固定大小。" +#: src/tuples-and-arrays/match.md:14 +msgid "'d'" +msgstr "" -#: src/basic-syntax/static-and-const.md:71 -msgid "Yes (initialised at compile time)" -msgstr "是（在编译时被初始化）" +#: src/tuples-and-arrays/match.md:14 +msgid "\"Moving around\"" +msgstr "" -#: src/basic-syntax/static-and-const.md:72 -msgid "Inlined wherever it is used" -msgstr "内嵌在使用它的任何位置" +#: src/tuples-and-arrays/match.md:15 src/error-handling/exercise.md:54 +#: src/error-handling/exercise.md:56 src/error-handling/exercise.md:64 +#: src/error-handling/solution.md:54 src/error-handling/solution.md:56 +#: src/error-handling/solution.md:64 +msgid "'0'" +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:3 -msgid "" -"You can shadow variables, both those from outer scopes and variables from " -"the same scope:" -msgstr "你可以隐藏变量，位于外部作用域的变量和 相同作用域的变量都可以：" +#: src/tuples-and-arrays/match.md:15 src/error-handling/exercise.md:54 +#: src/error-handling/exercise.md:56 src/error-handling/exercise.md:64 +#: src/error-handling/solution.md:54 src/error-handling/solution.md:56 +#: src/error-handling/solution.md:64 +msgid "'9'" +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let a = 10;\n" -" println!(\"before: {a}\");\n" -"\n" -" {\n" -" let a = \"hello\";\n" -" println!(\"inner scope: {a}\");\n" -"\n" -" let a = true;\n" -" println!(\"shadowed in inner scope: {a}\");\n" -" }\n" -"\n" -" println!(\"after: {a}\");\n" -"}\n" -"```" +#: src/tuples-and-arrays/match.md:15 +msgid "\"Number input\"" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let a = 10;\n" -" println!(\"before: {a}\");\n" -"\n" -" {\n" -" let a = \"hello\";\n" -" println!(\"inner scope: {a}\");\n" -"\n" -" let a = true;\n" -" println!(\"shadowed in inner scope: {a}\");\n" -" }\n" -"\n" -" println!(\"after: {a}\");\n" -"}\n" -"```" -#: src/basic-syntax/scopes-shadowing.md:25 -msgid "" -"Definition: Shadowing is different from mutation, because after shadowing " -"both variable's memory locations exist at the same time. Both are available " -"under the same name, depending where you use it in the code. " +#: src/tuples-and-arrays/match.md:16 +msgid "\"Lowercase: {key}\"" msgstr "" -"定义: 遮蔽和变更（mutation）不同，因为在遮蔽之后，两个变量都会同时存在于内存" -"的不同位置中。在同一个名字下的两个变量都是可以被使用的，但是你在代码的哪里使" -"用会最终决定你使用哪一个变量。" -#: src/basic-syntax/scopes-shadowing.md:26 -msgid "A shadowing variable can have a different type. " -msgstr "一个遮蔽变量可以具有不同的类型。" +#: src/tuples-and-arrays/match.md:17 +msgid "\"Something else\"" +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:27 +#: src/tuples-and-arrays/match.md:22 msgid "" -"Shadowing looks obscure at first, but is convenient for holding on to values " -"after `.unwrap()`." -msgstr "隐藏起初看起来会有些晦涩，但是它很便于存 `.unwrap()` 之后的得到的值。" +"The `_` pattern is a wildcard pattern which matches any value. The " +"expressions _must_ be irrefutable, meaning that it covers every possibility, " +"so `_` is often used as the final catch-all case." +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:28 +#: src/tuples-and-arrays/match.md:26 +#, fuzzy msgid "" -"The following code demonstrates why the compiler can't simply reuse memory " -"locations when shadowing an immutable variable in a scope, even if the type " -"does not change." +"Match can be used as an expression. Just like `if`, each match arm must have " +"the same type. The type is the last expression of the block, if any. In the " +"example above, the type is `()`." msgstr "" -"以下代码说明了为什么在作用域内隐藏一个不可变的变量时，即使是在变量类型没有改" -"变的情况下，编译器也不能简单地重复利用之前的内存位置。" +"与 `if let` 类似，每个匹配分支必须有相同的类型。该类型是块的最后一个 表达式" +"（如有）。在上例中，类型是 `()`。" -#: src/enums.md:3 +#: src/tuples-and-arrays/match.md:30 msgid "" -"The `enum` keyword allows the creation of a type which has a few different " -"variants:" -msgstr "`enum` 关键字允许创建具有几个 不同变体的类型：" +"A variable in the pattern (`key` in this example) will create a binding that " +"can be used within the match arm." +msgstr "" -#: src/enums.md:6 -msgid "" -"```rust,editable\n" -"fn generate_random_number() -> i32 {\n" -" // Implementation based on https://xkcd.com/221/\n" -" 4 // Chosen by fair dice roll. Guaranteed to be random.\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"enum CoinFlip {\n" -" Heads,\n" -" Tails,\n" -"}\n" -"\n" -"fn flip_coin() -> CoinFlip {\n" -" let random_number = generate_random_number();\n" -" if random_number % 2 == 0 {\n" -" return CoinFlip::Heads;\n" -" } else {\n" -" return CoinFlip::Tails;\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" println!(\"You got: {:?}\", flip_coin());\n" -"}\n" -"```" +#: src/tuples-and-arrays/match.md:33 +msgid "A match guard causes the arm to match only if the condition is true." msgstr "" -#: src/enums.md:36 -msgid "Enumerations allow you to collect a set of values under one type" -msgstr "枚举允许你从一种类型下收集一组值" +#: src/tuples-and-arrays/match.md:37 src/user-defined-types/named-structs.md:34 +#: src/user-defined-types/enums.md:28 src/methods-and-traits/methods.md:68 +msgid "Key Points:" +msgstr "关键点：" -#: src/enums.md:37 +#: src/tuples-and-arrays/match.md:39 #, fuzzy msgid "" -"This page offers an enum type `CoinFlip` with two variants `Heads` and " -"`Tails`. You might note the namespace when using variants." +"You might point out how some specific characters are being used when in a " +"pattern" msgstr "" -"本页提供了一个枚举类型 `CoinFlip`，其中包含 `Heads` 和`Tail`两个变体。在使用" -"变体时，你可能会注意到命名空间。" +"你可以解释一些用于表达模式的特殊字符的用法 \\*`|` 表示或 (or) \\*`..` 可以展" +"开为任意一个或多个值 \\*`1..=5` 代表了一个闭区间范围" -#: src/enums.md:38 -msgid "This might be a good time to compare Structs and Enums:" -msgstr "这可能是比较结构体和枚举的好时机：" +#: src/tuples-and-arrays/match.md:41 +#, fuzzy +msgid "`|` as an `or`" +msgstr "" +"解释模式匹配中的绑定的原理可能会很有帮助。比如可以用一个变量替代外卡，或者去" +"除 `q` 外面的引号。" -#: src/enums.md:39 -msgid "" -"In both, you can have a simple version without fields (unit struct) or one " -"with different types of fields (variant payloads). " +#: src/tuples-and-arrays/match.md:42 +#, fuzzy +msgid "`..` can expand as much as it needs to be" +msgstr "你可以展示如何匹配一个引用。" + +#: src/tuples-and-arrays/match.md:43 +#, fuzzy +msgid "`1..=5` represents an inclusive range" msgstr "" -"在这两者中，你可以获得一个不含字段的简单版本（单位结构体），或一个包含不同类" -"型字段的版本（变体载荷）。" +"现在是一个讲解不可反驳 (irrefutable) 模式的好时机。因为这个术语可能会出现在错" +"误信息中。" -#: src/enums.md:40 -msgid "In both, associated functions are defined within an `impl` block." -msgstr "在这两者中，关联的函数都在 `impl` 块中定义。" +#: src/tuples-and-arrays/match.md:44 +msgid "`_` is a wild card" +msgstr "“\\_”是通配符" -#: src/enums.md:41 +#: src/tuples-and-arrays/match.md:46 msgid "" -"You could even implement the different variants of an enum with separate " -"structs but then they wouldn’t be the same type as they would if they were " -"all defined in an enum. " +"Match guards as a separate syntax feature are important and necessary when " +"we wish to concisely express more complex ideas than patterns alone would " +"allow." msgstr "" -"你甚至可以使用单独的结构体实现枚举的不同变体，但这样一来，如果它们都已在枚举" -"中定义，类型与之前也不一样。" +"有些想法比模式本身所允许的程度更加复杂，如果我们希望简要地表达这些想法，就必" +"须把匹配守卫视为独立的语法功能。" -#: src/enums/variant-payloads.md:3 +#: src/tuples-and-arrays/match.md:48 msgid "" -"You can define richer enums where the variants carry data. You can then use " -"the `match` statement to extract the data from each variant:" +"They are not the same as separate `if` expression inside of the match arm. " +"An `if` expression inside of the branch block (after `=>`) happens after the " +"match arm is selected. Failing the `if` condition inside of that block won't " +"result in other arms of the original `match` expression being considered." msgstr "" -"你可以定义更丰富的枚举，其中变体会携带数据。然后，你可以使用 `match` 语句从每" -"个变体中提取数据：" +"它们与匹配分支中的单独“if”表达式不同。选择匹配分支后，分支块内（在“=>”之后）" +"会出现“if”表达式。如果该分支块内的“if”条件失败，系统不会考虑原始“match”表达式" +"的其他分支。" -#: src/enums/variant-payloads.md:6 +#: src/tuples-and-arrays/match.md:52 msgid "" -"```rust,editable\n" -"enum WebEvent {\n" -" PageLoad, // Variant without payload\n" -" KeyPress(char), // Tuple struct variant\n" -" Click { x: i64, y: i64 }, // Full struct variant\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(event: WebEvent) {\n" -" match event {\n" -" WebEvent::PageLoad => println!(\"page loaded\"),\n" -" WebEvent::KeyPress(c) => println!(\"pressed '{c}'\"),\n" -" WebEvent::Click { x, y } => println!(\"clicked at x={x}, y={y}\"),\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let load = WebEvent::PageLoad;\n" -" let press = WebEvent::KeyPress('x');\n" -" let click = WebEvent::Click { x: 20, y: 80 };\n" -"\n" -" inspect(load);\n" -" inspect(press);\n" -" inspect(click);\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"enum WebEvent {\n" -" PageLoad, // Variant without payload\n" -" KeyPress(char), // Tuple struct variant\n" -" Click { x: i64, y: i64 }, // Full struct variant\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(event: WebEvent) {\n" -" match event {\n" -" WebEvent::PageLoad => println!(\"page loaded\"),\n" -" WebEvent::KeyPress(c) => println!(\"pressed '{c}'\"),\n" -" WebEvent::Click { x, y } => println!(\"clicked at x={x}, y={y}\"),\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let load = WebEvent::PageLoad;\n" -" let press = WebEvent::KeyPress('x');\n" -" let click = WebEvent::Click { x: 20, y: 80 };\n" -"\n" -" inspect(load);\n" -" inspect(press);\n" -" inspect(click);\n" -"}\n" -"```" +"The condition defined in the guard applies to every expression in a pattern " +"with an `|`." +msgstr "只要表达式在包含“|”的模式中，就会适用守卫定义的条件。" -#: src/enums/variant-payloads.md:35 +#: src/tuples-and-arrays/destructuring.md:3 msgid "" -"The values in the enum variants can only be accessed after being pattern " -"matched. The pattern binds references to the fields in the \"match arm\" " -"after the `=>`." +"Destructuring is a way of extracting data from a data structure by writing a " +"pattern that is matched up to the data structure, binding variables to " +"subcomponents of the data structure." msgstr "" -"枚举变体中的值只有在被模式匹配后，才可访问。模式将引用绑定到 `=>` 之后" -"的“match 分支”中的字段。" -#: src/enums/variant-payloads.md:36 -msgid "" -"The expression is matched against the patterns from top to bottom. There is " -"no fall-through like in C or C++." -msgstr "表达式会从上到下与模式匹配。没有像 C 或 C++ 中那样的跳转。" +#: src/tuples-and-arrays/destructuring.md:7 +#, fuzzy +msgid "You can destructure tuples and arrays by matching on their elements:" +msgstr "你可以通过元素匹配来解构数组、元组和切片：" -#: src/enums/variant-payloads.md:37 -msgid "" -"The match expression has a value. The value is the last expression in the " -"match arm which was executed." -msgstr "匹配表达式拥有一个值。值是 match 分支中被执行的最后一个表达式。" +#: src/tuples-and-arrays/destructuring.md:18 +msgid "\"on Y axis\"" +msgstr "" -#: src/enums/variant-payloads.md:38 -msgid "" -"Starting from the top we look for what pattern matches the value then run " -"the code following the arrow. Once we find a match, we stop. " +#: src/tuples-and-arrays/destructuring.md:19 +msgid "\"on X axis\"" msgstr "" -"从顶部开始，查找与该值匹配的模式，然后沿箭头运行代码。一旦找到匹配，我们便会" -"停止。" -#: src/enums/variant-payloads.md:39 -msgid "" -"Demonstrate what happens when the search is inexhaustive. Note the advantage " -"the Rust compiler provides by confirming when all cases are handled. " +#: src/tuples-and-arrays/destructuring.md:20 +msgid "\"left of Y axis\"" msgstr "" -"展示搜索不详尽时会发生的情况。请注意 Rust 编译器的优势，即确认所有情况何时都" -"得到了处理。" -#: src/enums/variant-payloads.md:40 -msgid "`match` inspects a hidden discriminant field in the `enum`." -msgstr "`match` 会检查 `enum` 中的隐藏的判别字段。" +#: src/tuples-and-arrays/destructuring.md:21 +msgid "\"below X axis\"" +msgstr "" -#: src/enums/variant-payloads.md:41 -msgid "" -"It is possible to retrieve the discriminant by calling `std::mem::" -"discriminant()`" -msgstr "可以通过调用 `std::mem::discriminant()` 来检索判别" +#: src/tuples-and-arrays/destructuring.md:22 +msgid "\"first quadrant\"" +msgstr "" -#: src/enums/variant-payloads.md:42 -msgid "" -"This is useful, for example, if implementing `PartialEq` for structs where " -"comparing field values doesn't affect equality." -msgstr "这很有用，例如如果为结构体实现 `PartialEq`，比较字段值不会影响等式。" +#: src/tuples-and-arrays/destructuring.md:33 +msgid "\"Tell me about {triple:?}\"" +msgstr "" -#: src/enums/variant-payloads.md:43 -msgid "" -"`WebEvent::Click { ... }` is not exactly the same as `WebEvent::" -"Click(Click)` with a top level `struct Click { ... }`. The inlined version " -"cannot implement traits, for example." +#: src/tuples-and-arrays/destructuring.md:35 +msgid "\"First is 0, y = {y}, and z = {z}\"" msgstr "" -"`WebEvent::Click { ... }` 与含顶层 `struct Click { ... }` 的 `WebEvent::" -"Click(Click)` 不完全相同。例如，内嵌版本无法实现 trait。" -#: src/enums/sizes.md:3 -msgid "" -"Rust enums are packed tightly, taking constraints due to alignment into " -"account:" -msgstr "Rust 枚举被紧密地打包，考虑到了对齐的影响，因此存在一些限制：" +#: src/tuples-and-arrays/destructuring.md:36 +msgid "\"First is 1 and the rest were ignored\"" +msgstr "" + +#: src/tuples-and-arrays/destructuring.md:37 +msgid "\"All elements were ignored\"" +msgstr "" -#: src/enums/sizes.md:5 +#: src/tuples-and-arrays/destructuring.md:44 #, fuzzy +msgid "Create a new array pattern using `_` to represent an element." +msgstr "使用 `_` 创建一个新的模式来代表一个元素。" + +#: src/tuples-and-arrays/destructuring.md:45 +msgid "Add more values to the array." +msgstr "向数组中添加更多的值。" + +#: src/tuples-and-arrays/destructuring.md:46 msgid "" -"```rust,editable\n" -"use std::any::type_name;\n" -"use std::mem::{align_of, size_of};\n" -"\n" -"fn dbg_size() {\n" -" println!(\"{}: size {} bytes, align: {} bytes\",\n" -" type_name::(), size_of::(), align_of::());\n" -"}\n" -"\n" -"enum Foo {\n" -" A,\n" -" B,\n" -"}\n" -"\n" -"fn main() {\n" -" dbg_size::();\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"use std::mem::{align_of, size_of};\n" -"\n" -"macro_rules! dbg_size {\n" -" ($t:ty) => {\n" -" println!(\"{}: size {} bytes, align: {} bytes\",\n" -" stringify!($t), size_of::<$t>(), align_of::<$t>());\n" -" };\n" -"}\n" -"\n" -"enum Foo {\n" -" A,\n" -" B,\n" -"}\n" -"\n" -"fn main() {\n" -" dbg_size!(Foo);\n" -"}\n" -"```" +"Point out that how `..` will expand to account for different number of " +"elements." +msgstr "指出 `..` 是如何扩展以适应不同数量的元素的。" -#: src/enums/sizes.md:24 -msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/type-layout." -"html)." +#: src/tuples-and-arrays/destructuring.md:48 +msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" +msgstr "展示使用模式 `[.., b]` 和 `[a@..,b]` 来匹配切片的尾部。" + +#: src/tuples-and-arrays/exercise.md:3 +msgid "Arrays can contain other arrays:" msgstr "" -"请参阅 [Rust 引用](https://doc.rust-lang.org/reference/type-layout.html)。" -#: src/enums/sizes.md:30 +#: src/tuples-and-arrays/exercise.md:9 #, fuzzy -msgid "" -"Internally Rust is using a field (discriminant) to keep track of the enum " -"variant." -msgstr "在内部，Rust 使用字段（判别）来跟踪枚举变体。" +msgid "What is the type of this variable?" +msgstr "每个循环中的“word”是什么类型？" -#: src/enums/sizes.md:32 +#: src/tuples-and-arrays/exercise.md:11 #, fuzzy msgid "" -"You can control the discriminant if needed (e.g., for compatibility with C):" -msgstr "你可以根据需要控制判别（例如，与 C 的兼容性）：" +"Use an array such as the above to write a function `transpose` which will " +"transpose a matrix (turn rows into columns):" +msgstr "" +"使用以上知识，写一个用易读的格式输出矩阵的 `pretty_print` 函数，以及一个对矩" +"阵进行转置（将行和列互换）的 `transpose` 函数：" -#: src/enums/sizes.md:50 -#, fuzzy +#: src/tuples-and-arrays/exercise.md:22 +msgid "Hard-code both functions to operate on 3 × 3 matrices." +msgstr "硬编码这两个函数，让它们处理 3 × 3 的矩阵。" + +#: src/tuples-and-arrays/exercise.md:24 msgid "" -"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " -"bytes." -msgstr "" -"如果不使用 `repr`，判别类型会占用 2 个字节，因为 10001 是一个 2 个字节的数" -"值。" +"Copy the code below to and implement the " +"functions:" +msgstr "将下面的代码复制到 并实现上述函数：" -#: src/enums/sizes.md:54 -#, fuzzy -msgid "Try out other types such as" -msgstr "试试其他类型，例如：" +#: src/tuples-and-arrays/exercise.md:28 src/methods-and-traits/exercise.md:20 +#: src/borrowing/exercise.md:14 src/unsafe-rust/exercise.md:51 +msgid "// TODO: remove this when you're done with your implementation.\n" +msgstr "" -#: src/enums/sizes.md:56 -#, fuzzy -msgid "`dbg_size!(bool)`: size 1 bytes, align: 1 bytes," -msgstr "`dbg_size!(bool)`：大小占用 1 个字节，对齐占用 1 个字节；" +#: src/tuples-and-arrays/exercise.md:37 src/tuples-and-arrays/solution.md:34 +msgid "// <-- the comment makes rustfmt add a newline\n" +msgstr "" -#: src/enums/sizes.md:57 -#, fuzzy -msgid "" -"`dbg_size!(Option)`: size 1 bytes, align: 1 bytes (niche optimization, " -"see below)," +#: src/tuples-and-arrays/exercise.md:42 src/tuples-and-arrays/solution.md:39 +msgid "\"matrix: {:#?}\"" msgstr "" -"`dbg_size!(Option)`：大小占用 1 个字节，对齐占用 1 个字节（小众优化，请" -"参阅下文）；" -#: src/enums/sizes.md:58 -#, fuzzy -msgid "`dbg_size!(&i32)`: size 8 bytes, align: 8 bytes (on a 64-bit machine)," +#: src/tuples-and-arrays/exercise.md:44 src/tuples-and-arrays/solution.md:41 +msgid "\"transposed: {:#?}\"" msgstr "" -"`dbg_size!(&i32)`：大小占用 8 个字节，对齐占用 8 个字节（在 64 位设备上）；" -#: src/enums/sizes.md:59 -#, fuzzy -msgid "" -"`dbg_size!(Option<&i32>)`: size 8 bytes, align: 8 bytes (null pointer " -"optimization, see below)." +#: src/tuples-and-arrays/solution.md:17 src/tuples-and-arrays/solution.md:25 +msgid "//\n" msgstr "" -"`dbg_size!(Option<&i32>)`：大小占用 8 个字节，对齐占用 8 个字节（Null 指针优" -"化，请参阅下文）。" -#: src/enums/sizes.md:61 -#, fuzzy +#: src/references/shared.md:3 msgid "" -"Niche optimization: Rust will merge unused bit patterns for the enum " -"discriminant." -msgstr "小众优化：Rust 将对枚举判别合并使用 未使用的位模式。" +"A reference provides a way to access another value without taking " +"responsibility for the value, and is also called \"borrowing\". Shared " +"references are read-only, and the referenced data cannot change." +msgstr "" -#: src/enums/sizes.md:64 -#, fuzzy +#: src/references/shared.md:20 msgid "" -"Null pointer optimization: For [some types](https://doc.rust-lang.org/std/" -"option/#representation), Rust guarantees that `size_of::()` equals " -"`size_of::>()`." +"A shared reference to a type `T` has type `&T`. A reference value is made " +"with the `&` operator. The `*` operator \"dereferences\" a reference, " +"yielding its value." msgstr "" -"Null 指针优化：对于[某些 类型](https://doc.rust-lang.org/std/option/" -"#representation)，Rust 保证 `size_of::()` 等效于 `size_of::" -">()`。" -#: src/enums/sizes.md:68 -#, fuzzy +#: src/references/shared.md:24 +msgid "Rust will statically forbid dangling references:" +msgstr "Rust 会静态禁止悬垂引用：" + +#: src/references/shared.md:37 msgid "" -"Example code if you want to show how the bitwise representation _may_ look " -"like in practice. It's important to note that the compiler provides no " -"guarantees regarding this representation, therefore this is totally unsafe." +"A reference is said to \"borrow\" the value it refers to, and this is a good " +"model for students not familiar with pointers: code can use the reference to " +"access the value, but is still \"owned\" by the original variable. The " +"course will get into more detail on ownership in day 3." msgstr "" -"如果你想展示位表示方式在实践中“可能”会是什么样子，请参考示例代码。 请务必注" -"意，编译器对此表示法不提供任何保证，因此这是完全不安全的。" -#: src/enums/sizes.md:105 +#: src/references/shared.md:42 msgid "" -"More complex example if you want to discuss what happens when we chain more " -"than 256 `Option`s together." +"References are implemented as pointers, and a key advantage is that they can " +"be much smaller than the thing they point to. Students familiar with C or C+" +"+ will recognize references as pointers. Later parts of the course will " +"cover how Rust prevents the memory-safety bugs that come from using raw " +"pointers." msgstr "" -"如果您想讨论将 256 多个“Option”链在一起时会发生什么情况，可以使用下方这个更复" -"杂的示例。" -#: src/control-flow/novel.md:3 +#: src/references/shared.md:47 msgid "" -"Rust has a few control flow constructs which differ from other languages. " -"They are used for pattern matching:" -msgstr "Rust 有几个与其他语言不同的控制流结构。它们用于模式匹配：" - -#: src/control-flow/novel.md:6 src/control-flow/if-let-expressions.md:1 -msgid "`if let` expressions" -msgstr "`if let` 表达式" +"Rust does not automatically create references for you - the `&` is always " +"required." +msgstr "" -#: src/control-flow/novel.md:7 +#: src/references/shared.md:50 #, fuzzy -msgid "`while let` expressions" -msgstr "while let 表达式" - -#: src/control-flow/novel.md:8 src/control-flow/match-expressions.md:1 -msgid "`match` expressions" -msgstr "`match` 表达式" - -#: src/control-flow/if-let-expressions.md:3 msgid "" -"The [`if let` expression](https://doc.rust-lang.org/reference/expressions/if-" -"expr.html#if-let-expressions) lets you execute different code depending on " -"whether a value matches a pattern:" +"Rust will auto-dereference in some cases, in particular when invoking " +"methods (try `r.count_ones()`). There is no need for an `->` operator like " +"in C++." msgstr "" -"[`if let` 表达式](https://doc.rust-lang.org/reference/expressions/if-expr." -"html#if-let-expressions) 能让你根据某个值是否与模式相匹配来执行不同的代码：" +"Rust 有时会进行自动解引用。比如调用方法 `ref_x.count_ones()` 时，ref_x 会被解" +"引用。" -#: src/control-flow/if-let-expressions.md:7 +#: src/references/shared.md:53 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let arg = std::env::args().next();\n" -" if let Some(value) = arg {\n" -" println!(\"Program name: {value}\");\n" -" } else {\n" -" println!(\"Missing name?\");\n" -" }\n" -"}\n" -"```" +"In this example, `r` is mutable so that it can be reassigned (`r = &b`). " +"Note that this re-binds `r`, so that it refers to something else. This is " +"different from C++, where assignment to a reference changes the referenced " +"value." msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let arg = std::env::args().next();\n" -" if let Some(value) = arg {\n" -" println!(\"Program name: {value}\");\n" -" } else {\n" -" println!(\"Missing name?\");\n" -" }\n" -"}\n" -"```" -#: src/control-flow/if-let-expressions.md:18 -#: src/control-flow/while-let-expressions.md:22 -#: src/control-flow/match-expressions.md:23 +#: src/references/shared.md:57 msgid "" -"See [pattern matching](../pattern-matching.md) for more details on patterns " -"in Rust." +"A shared reference does not allow modifying the value it refers to, even if " +"that value was mutable. Try `*r = 'X'`." msgstr "" -"如需详细了解 Rust 中 的模式，请参阅[模式匹配](../pattern-matching.md)。" -#: src/control-flow/if-let-expressions.md:23 -#, fuzzy +#: src/references/shared.md:60 msgid "" -"Unlike `match`, `if let` does not have to cover all branches. This can make " -"it more concise than `match`." -msgstr "与 `match` 不同的是，`if let` 不支持模式匹配的 guard 子句。" - -#: src/control-flow/if-let-expressions.md:24 -msgid "A common usage is handling `Some` values when working with `Option`." -msgstr "使用 `Option` 时，常见的做法是处理 `Some` 值。" +"Rust is tracking the lifetimes of all references to ensure they live long " +"enough. Dangling references cannot occur in safe Rust. `x_axis` would return " +"a reference to `point`, but `point` will be deallocated when the function " +"returns, so this will not compile." +msgstr "" -#: src/control-flow/if-let-expressions.md:25 -msgid "" -"Unlike `match`, `if let` does not support guard clauses for pattern matching." -msgstr "与 `match` 不同的是，`if let` 不支持模式匹配的 guard 子句。" +#: src/references/shared.md:65 +msgid "We will talk more about borrowing when we get to ownership." +msgstr "我们会在讲到所有权（ownership）时详细讨论借用（borrow）。" -#: src/control-flow/if-let-expressions.md:26 -#, fuzzy +#: src/references/exclusive.md:3 msgid "" -"Since 1.65, a similar [let-else](https://doc.rust-lang.org/rust-by-example/" -"flow_control/let_else.html) construct allows to do a destructuring " -"assignment, or if it fails, execute a block which is required to abort " -"normal control flow (with `panic`/`return`/`break`/`continue`):" +"Exclusive references, also known as mutable references, allow changing the " +"value they refer to. They have type `&mut T`." msgstr "" -"自 1.65 版以来，类似的 [let-else](https://doc.rust-lang.org/rust-by-example/" -"flow_control/let_else.html) 结构允许执行解构赋值，或者如果不满足条件，则有一" -"个非返回块分支 (panic/return/break/continue)：" -#: src/control-flow/while-let-expressions.md:1 -msgid "`while let` loops" -msgstr "`while let` 循环" - -#: src/control-flow/while-let-expressions.md:3 +#: src/references/exclusive.md:21 msgid "" -"Like with `if let`, there is a [`while let`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#predicate-pattern-loops) variant which " -"repeatedly tests a value against a pattern:" +"\"Exclusive\" means that only this reference can be used to access the " +"value. No other references (shared or exclusive) can exist at the same time, " +"and the referenced value cannot be accessed while the exclusive reference " +"exists. Try making an `&point.0` or changing `point.0` while `x_coord` is " +"alive." msgstr "" -"与 `if let` 一样，[`while let`](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#predicate-pattern-loops) 变体会针对一个模式重复测" -"试一个值：" -#: src/control-flow/while-let-expressions.md:18 +#: src/references/exclusive.md:26 #, fuzzy msgid "" -"Here the iterator returned by `v.into_iter()` will return a `Option` on " -"every call to `next()`. It returns `Some(x)` until it is done, after which " -"it will return `None`. The `while let` lets us keep iterating through all " -"items." +"Be sure to note the difference between `let mut x_coord: &i32` and `let " +"x_coord: &mut i32`. The first one represents a shared reference which can be " +"bound to different values, while the second represents an exclusive " +"reference to a mutable value." msgstr "" -"在这里，每次 调用 `next()` 时，`v.iter()` 返回的迭代器都会返回一个 " -"`Option`。它将一直返回 `Some(x)`，直到完成。 之后它将返回 `None`。" -"`while let`能让我们持续迭代所有项。" +"注意 `let mut ref_x: &i32` 与 `let ref_x: &mut i32` 之间的区别。第一条语句声" +"明了一个可变引用，所以我们可以修改这个引用所绑定的值；第二条语句声明了一个指" +"向可变变量的引用。" -#: src/control-flow/while-let-expressions.md:27 +#: src/references/exercise.md:3 msgid "" -"Point out that the `while let` loop will keep going as long as the value " -"matches the pattern." -msgstr "指出只要值与模式匹配，`while let` 循环就会一直进行下去。" +"We will create a few utility functions for 3-dimensional geometry, " +"representing a point as `[f64;3]`. It is up to you to determine the function " +"signatures." +msgstr "" -#: src/control-flow/while-let-expressions.md:28 +#: src/references/exercise.md:7 msgid "" -"You could rewrite the `while let` loop as an infinite loop with an if " -"statement that breaks when there is no value to unwrap for `iter.next()`. " -"The `while let` provides syntactic sugar for the above scenario." +"// Calculate the magnitude of a vector by summing the squares of its " +"coordinates\n" +"// and taking the square root. Use the `sqrt()` method to calculate the " +"square\n" +"// root, like `v.sqrt()`.\n" msgstr "" -"你可以使用 if 语句将 `while let` 循环重写为无限循环，当 `iter.next()` 没有值" -"可以解封时中断。`while let` 为上述情况提供了语法糖。" -#: src/control-flow/match-expressions.md:3 +#: src/references/exercise.md:15 msgid "" -"The [`match` keyword](https://doc.rust-lang.org/reference/expressions/match-" -"expr.html) is used to match a value against one or more patterns. In that " -"sense, it works like a series of `if let` expressions:" +"// Normalize a vector by calculating its magnitude and dividing all of its\n" +"// coordinates by that magnitude.\n" msgstr "" -"[`match` 关键字](https://doc.rust-lang.org/reference/expressions/match-expr." -"html) 用于将一个值与一个或多个模式进行匹配。从这个意义上讲，它的工作方式 类似" -"于一系列的 `if let` 表达式：" -#: src/control-flow/match-expressions.md:7 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" match std::env::args().next().as_deref() {\n" -" Some(\"cat\") => println!(\"Will do cat things\"),\n" -" Some(\"ls\") => println!(\"Will ls some files\"),\n" -" Some(\"mv\") => println!(\"Let's move some files\"),\n" -" Some(\"rm\") => println!(\"Uh, dangerous!\"),\n" -" None => println!(\"Hmm, no program name?\"),\n" -" _ => println!(\"Unknown program name!\"),\n" -" }\n" -"}\n" -"```" +#: src/references/exercise.md:23 +msgid "// Use the following `main` to test your work.\n" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" match std::env::args().next().as_deref() {\n" -" Some(\"cat\") => println!(\"Will do cat things\"),\n" -" Some(\"ls\") => println!(\"Will ls some files\"),\n" -" Some(\"mv\") => println!(\"Let's move some files\"),\n" -" Some(\"rm\") => println!(\"Uh, dangerous!\"),\n" -" None => println!(\"Hmm, no program name?\"),\n" -" _ => println!(\"Unknown program name!\"),\n" -" }\n" -"}\n" -"```" -#: src/control-flow/match-expressions.md:20 -msgid "" -"Like `if let`, each match arm must have the same type. The type is the last " -"expression of the block, if any. In the example above, the type is `()`." +#: src/references/exercise.md:27 src/references/solution.md:22 +msgid "\"Magnitude of a unit vector: {}\"" msgstr "" -"与 `if let` 类似，每个匹配分支必须有相同的类型。该类型是块的最后一个 表达式" -"（如有）。在上例中，类型是 `()`。" -#: src/control-flow/match-expressions.md:28 -msgid "Save the match expression to a variable and print it out." -msgstr "将 match 表达式保存到一个变量中并输出结果。" +#: src/references/exercise.md:30 src/references/solution.md:25 +msgid "\"Magnitude of {v:?}: {}\"" +msgstr "" -#: src/control-flow/match-expressions.md:29 -msgid "Remove `.as_deref()` and explain the error." -msgstr "移除 `.as_deref()` 并说明错误。" +#: src/references/exercise.md:32 src/references/solution.md:27 +msgid "\"Magnitude of {v:?} after normalization: {}\"" +msgstr "" -#: src/control-flow/match-expressions.md:30 -msgid "" -"`std::env::args().next()` returns an `Option`, but we cannot match " -"against `String`." +#: src/references/solution.md:4 +msgid "/// Calculate the magnitude of the given vector.\n" msgstr "" -"`std::env::args().next()` 会返回 `Option`，但无法与 `String` 进行匹" -"配。" -#: src/control-flow/match-expressions.md:31 +#: src/references/solution.md:12 msgid "" -"`as_deref()` transforms an `Option` to `Option<&T::Target>`. In our case, " -"this turns `Option` into `Option<&str>`." +"/// Change the magnitude of the vector to 1.0 without changing its " +"direction.\n" msgstr "" -"`as_deref()` 会将 `Option` 转换为 `Option<&T::Target>`。在我们的示例中，这" -"会将 `Option` 转换为 `Option<&str>`。" -#: src/control-flow/match-expressions.md:32 -msgid "" -"We can now use pattern matching to match against the `&str` inside `Option`." -msgstr "现在，我们可以使用模式匹配来匹配 `Option` 中的 `&str`。" +#: src/user-defined-types/named-structs.md:3 +msgid "Like C and C++, Rust has support for custom structs:" +msgstr "与 C 和 C++ 一样，Rust 支持自定义结构体：" -#: src/pattern-matching.md:3 -msgid "" -"The `match` keyword let you match a value against one or more _patterns_. " -"The comparisons are done from top to bottom and the first match wins." +#: src/user-defined-types/named-structs.md:12 +msgid "\"{} is {} years old\"" msgstr "" -"使用关键词 `match` 对一个值进行模式匹配。进行匹配时，会从上至下依次进行比较，" -"并选定第一个匹配成功的结果。" -#: src/pattern-matching.md:6 -msgid "The patterns can be simple values, similarly to `switch` in C and C++:" -msgstr "模式（pattern）可以是简单的值，其用法类似于 C 与 C++ 中的 `switch` 。" +#: src/user-defined-types/named-structs.md:16 +#: src/android/interoperability/with-c/bindgen.md:87 +msgid "\"Peter\"" +msgstr "" -#: src/pattern-matching.md:8 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let input = 'x';\n" -"\n" -" match input {\n" -" 'q' => println!(\"Quitting\"),\n" -" 'a' | 's' | 'w' | 'd' => println!(\"Moving around\"),\n" -" '0'..='9' => println!(\"Number input\"),\n" -" _ => println!(\"Something else\"),\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/named-structs.md:22 +msgid "\"Avery\"" +msgstr "" + +#: src/user-defined-types/named-structs.md:27 +msgid "\"Jackie\"" msgstr "" -#: src/pattern-matching.md:21 -msgid "The `_` pattern is a wildcard pattern which matches any value." -msgstr "模式 `_` 是外卡 (wildcard) 模式。它可以匹配任何值。" +#: src/user-defined-types/named-structs.md:36 +msgid "Structs work like in C or C++." +msgstr "结构体的运作方式与使用 C 或 C++ 时类似。" + +#: src/user-defined-types/named-structs.md:37 +msgid "Like in C++, and unlike in C, no typedef is needed to define a type." +msgstr "不需要 typedef 即可定义类型，这与使用 C++ 类似，但与使用 C 不同。" + +#: src/user-defined-types/named-structs.md:38 +msgid "Unlike in C++, there is no inheritance between structs." +msgstr "与使用 C++ 不同的是，结构体之间没有继承关系。" -#: src/pattern-matching.md:26 +#: src/user-defined-types/named-structs.md:39 #, fuzzy msgid "" -"You might point out how some specific characters are being used when in a " -"pattern" -msgstr "" -"你可以解释一些用于表达模式的特殊字符的用法 \\*`|` 表示或 (or) \\*`..` 可以展" -"开为任意一个或多个值 \\*`1..=5` 代表了一个闭区间范围" +"This may be a good time to let people know there are different types of " +"structs." +msgstr "这时可能很适合告诉学员存在不同类型的结构体。" -#: src/pattern-matching.md:27 +#: src/user-defined-types/named-structs.md:41 #, fuzzy -msgid "`|` as an `or`" +msgid "" +"Zero-sized structs (e.g. `struct Foo;`) might be used when implementing a " +"trait on some type but don’t have any data that you want to store in the " +"value itself." msgstr "" -"解释模式匹配中的绑定的原理可能会很有帮助。比如可以用一个变量替代外卡，或者去" -"除 `q` 外面的引号。" +"针对某类型实现 trait 时，可能会使用大小为零的结构体 `e.g., struct Foo;`，但其" +"中没有任何您要储存在值本身中的数据。" + +#: src/user-defined-types/named-structs.md:44 +msgid "" +"The next slide will introduce Tuple structs, used when the field names are " +"not important." +msgstr "下一张幻灯片将介绍元组结构体，当字段名称不重要时使用。" -#: src/pattern-matching.md:28 +#: src/user-defined-types/named-structs.md:46 #, fuzzy -msgid "`..` can expand as much as it needs to be" -msgstr "你可以展示如何匹配一个引用。" +msgid "" +"If you already have variables with the right names, then you can create the " +"struct using a shorthand." +msgstr "如果您已有名称正确的变量，则可以使用简写形式创建结构体：" -#: src/pattern-matching.md:29 +#: src/user-defined-types/named-structs.md:48 #, fuzzy -msgid "`1..=5` represents an inclusive range" +msgid "" +"The syntax `..avery` allows us to copy the majority of the fields from the " +"old struct without having to explicitly type it all out. It must always be " +"the last element." msgstr "" -"现在是一个讲解不可反驳 (irrefutable) 模式的好时机。因为这个术语可能会出现在错" -"误信息中。" +"通过语法“..peter”，我们可以从旧结构体复制大部分字段，而无需明确地输入所有字" +"段。它必须始终是最后一个元素。" -#: src/pattern-matching.md:30 -msgid "`_` is a wild card" -msgstr "“\\_”是通配符" +#: src/user-defined-types/tuple-structs.md:7 +msgid "If the field names are unimportant, you can use a tuple struct:" +msgstr "如果字段名称不重要，您可以使用元组结构体：" -#: src/pattern-matching.md:31 -msgid "" -"It can be useful to show how binding works, by for instance replacing a " -"wildcard character with a variable, or removing the quotes around `q`." +#: src/user-defined-types/tuple-structs.md:14 +msgid "\"({}, {})\"" msgstr "" -"展示绑定的运作方式可能会很有帮助，例如通过用变量替换通配符或移除“q”周围的引号" -"来展示。" -#: src/pattern-matching.md:32 -msgid "You can demonstrate matching on a reference." -msgstr "您可以在参照项上演示如何匹配。" +#: src/user-defined-types/tuple-structs.md:18 +msgid "This is often used for single-field wrappers (called newtypes):" +msgstr "这通常用于单字段封装容器（称为 newtype）：" -#: src/pattern-matching.md:33 -msgid "" -"This might be a good time to bring up the concept of irrefutable patterns, " -"as the term can show up in error messages." +#: src/user-defined-types/tuple-structs.md:25 +msgid "\"Ask a rocket scientist at NASA\"" msgstr "" -"这时可能很适合提到“不可反驳的模式”这个概念，因为这个术语可能会出现在错误消息" -"中。" -#: src/pattern-matching/destructuring-enums.md:3 -msgid "" -"Patterns can also be used to bind variables to parts of your values. This is " -"how you inspect the structure of your types. Let us start with a simple " -"`enum` type:" +#: src/user-defined-types/tuple-structs.md:29 +#: src/android/interoperability/cpp/cpp-bridge.md:50 +#: src/bare-metal/microcontrollers/type-state.md:14 +#: src/async/pitfalls/cancellation.md:98 src/async/pitfalls/cancellation.md:101 +msgid "// ...\n" msgstr "" -"模式还可用于将变量绑定到值的某些部分。这是您检查类型结构的方式。我们先从简单" -"的“enum”类型开始：" -#: src/pattern-matching/destructuring-enums.md:6 +#: src/user-defined-types/tuple-structs.md:40 msgid "" -"```rust,editable\n" -"enum Result {\n" -" Ok(i32),\n" -" Err(String),\n" -"}\n" -"\n" -"fn divide_in_two(n: i32) -> Result {\n" -" if n % 2 == 0 {\n" -" Result::Ok(n / 2)\n" -" } else {\n" -" Result::Err(format!(\"cannot divide {n} into two equal parts\"))\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let n = 100;\n" -" match divide_in_two(n) {\n" -" Result::Ok(half) => println!(\"{n} divided in two is {half}\"),\n" -" Result::Err(msg) => println!(\"sorry, an error happened: {msg}\"),\n" -" }\n" -"}\n" -"```" +"Newtypes are a great way to encode additional information about the value in " +"a primitive type, for example:" msgstr "" +"如需对基元类型中的值的额外信息进行编码，使用 newtype 是一种非常好的方式，例" +"如：" -#: src/pattern-matching/destructuring-enums.md:29 +#: src/user-defined-types/tuple-structs.md:42 +msgid "The number is measured in some units: `Newtons` in the example above." +msgstr "数字会以某些单位来衡量：上方示例中为 `Newtons`。" + +#: src/user-defined-types/tuple-structs.md:43 +#, fuzzy msgid "" -"Here we have used the arms to _destructure_ the `Result` value. In the first " -"arm, `half` is bound to the value inside the `Ok` variant. In the second " -"arm, `msg` is bound to the error message." +"The value passed some validation when it was created, so you no longer have " +"to validate it again at every use: `PhoneNumber(String)` or `OddNumber(u32)`." msgstr "" -"在这里，我们使用了分支来解构“Result”值。在第一个分支中，“half”被绑定到“Ok”变" -"体中的值。在第二个分支中，“msg”被绑定到错误消息。" +"值在创建时已通过一些验证，因此您不再需要在每次使用时都再次验证它：" +"`PhoneNumber(String)` 或 `OddNumber(u32)`。" -#: src/pattern-matching/destructuring-enums.md:36 +#: src/user-defined-types/tuple-structs.md:46 msgid "" -"The `if`/`else` expression is returning an enum that is later unpacked with " -"a `match`." -msgstr "“if”/“else”表达式将返回一个枚举，该枚举之后会使用“match”进行解封装。" +"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " +"single field in the newtype." +msgstr "" +"展示如何通过访问 newtype 中的单个字段，将 `f64` 值添加到 `Newtons` 类型。" -#: src/pattern-matching/destructuring-enums.md:37 +#: src/user-defined-types/tuple-structs.md:48 msgid "" -"You can try adding a third variant to the enum definition and displaying the " -"errors when running the code. Point out the places where your code is now " -"inexhaustive and how the compiler tries to give you hints." -msgstr "" -"您可以尝试在枚举定义中添加第三个变体，并在运行代码时显示错误。指出代码现在有" -"哪些地方还不详尽，并说明编译器会如何尝试给予提示。" +"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " +"for instance using booleans as integers." +msgstr "Rust 通常不喜欢不明确的内容，例如自动解封或将布尔值用作整数。" -#: src/pattern-matching/destructuring-structs.md:3 -msgid "You can also destructure `structs`:" -msgstr "您还可以解构“structs”：" +#: src/user-defined-types/tuple-structs.md:50 +msgid "Operator overloading is discussed on Day 3 (generics)." +msgstr "运算符过载在第 3 天（泛型）讨论。" -#: src/pattern-matching/destructuring-structs.md:5 +#: src/user-defined-types/tuple-structs.md:51 msgid "" -"```rust,editable\n" -"struct Foo {\n" -" x: (u32, u32),\n" -" y: u32,\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let foo = Foo { x: (1, 2), y: 3 };\n" -" match foo {\n" -" Foo { x: (1, b), y } => println!(\"x.0 = 1, b = {b}, y = {y}\"),\n" -" Foo { y: 2, x: i } => println!(\"y = 2, x = {i:?}\"),\n" -" Foo { y, .. } => println!(\"y = {y}, other fields were " -"ignored\"),\n" -" }\n" -"}\n" -"```" +"The example is a subtle reference to the [Mars Climate Orbiter](https://en." +"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." msgstr "" +"此示例巧妙地引用了[火星气候探测者号](https://zh.wikipedia.org/wiki/" +"%E7%81%AB%E6%98%9F%E6%B0%A3%E5%80%99%E6%8E%A2%E6%B8%AC%E8%80%85%E8%99%9F) 的" +"失败事故。" -#: src/pattern-matching/destructuring-structs.md:23 -msgid "Change the literal values in `foo` to match with the other patterns." -msgstr "更改“foo”中的字面量值以与其他模式相匹配。" +#: src/user-defined-types/enums.md:3 +msgid "" +"The `enum` keyword allows the creation of a type which has a few different " +"variants:" +msgstr "`enum` 关键字允许创建具有几个 不同变体的类型：" -#: src/pattern-matching/destructuring-structs.md:24 -msgid "Add a new field to `Foo` and make changes to the pattern as needed." -msgstr "向“Foo”添加一个新字段，并根据需要更改模式。" +#: src/user-defined-types/enums.md:15 +msgid "// Simple variant\n" +msgstr "" -#: src/pattern-matching/destructuring-structs.md:25 -msgid "" -"The distinction between a capture and a constant expression can be hard to " -"spot. Try changing the `2` in the second arm to a variable, and see that it " -"subtly doesn't work. Change it to a `const` and see it working again." +#: src/user-defined-types/enums.md:16 +msgid "// Tuple variant\n" msgstr "" -"捕获和常量表达式之间的区别可能很难发现。尝试将第二个分支中的“2”更改为一个变" -"量，可以看到它几乎无法运作了。将它更改为“const”，可以看到它又正常运作了。" -#: src/pattern-matching/destructuring-arrays.md:3 -msgid "" -"You can destructure arrays, tuples, and slices by matching on their elements:" -msgstr "你可以通过元素匹配来解构数组、元组和切片：" +#: src/user-defined-types/enums.md:17 +msgid "// Struct variant\n" +msgstr "" -#: src/pattern-matching/destructuring-arrays.md:5 -msgid "" -"```rust,editable\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let triple = [0, -2, 3];\n" -" println!(\"Tell me about {triple:?}\");\n" -" match triple {\n" -" [0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" -" [1, ..] => println!(\"First is 1 and the rest were ignored\"),\n" -" _ => println!(\"All elements were ignored\"),\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/enums.md:22 +msgid "\"On this turn: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:21 -msgid "" -"Destructuring of slices of unknown length also works with patterns of fixed " -"length." -msgstr "对未知长度的切片进行解构也可以使用固定长度的模式。" +#: src/user-defined-types/enums.md:30 +#, fuzzy +msgid "Enumerations allow you to collect a set of values under one type." +msgstr "枚举允许你从一种类型下收集一组值" -#: src/pattern-matching/destructuring-arrays.md:24 +#: src/user-defined-types/enums.md:31 msgid "" -"```rust,editable\n" -"fn main() {\n" -" inspect(&[0, -2, 3]);\n" -" inspect(&[0, -2, 3, 4]);\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(slice: &[i32]) {\n" -" println!(\"Tell me about {slice:?}\");\n" -" match slice {\n" -" &[0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" -" &[1, ..] => println!(\"First is 1 and the rest were ignored\"),\n" -" _ => println!(\"All elements were ignored\"),\n" -" }\n" -"}\n" -"```" +"`Direction` is a type with variants. There are two values of `Direction`: " +"`Direction::Left` and `Direction::Right`." msgstr "" -"```rust,editable\n" -"fn main() {\n" -" inspect(&[0, -2, 3]);\n" -" inspect(&[0, -2, 3, 4]);\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(slice: &[i32]) {\n" -" println!(\"Tell me about {slice:?}\");\n" -" match slice {\n" -" &[0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" -" &[1, ..] => println!(\"First is 1 and the rest were ignored\"),\n" -" _ => println!(\"All elements were ignored\"),\n" -" }\n" -"}\n" -"```" - -#: src/pattern-matching/destructuring-arrays.md:41 -msgid "Create a new pattern using `_` to represent an element. " -msgstr "使用 `_` 创建一个新的模式来代表一个元素。" -#: src/pattern-matching/destructuring-arrays.md:42 -msgid "Add more values to the array." -msgstr "向数组中添加更多的值。" - -#: src/pattern-matching/destructuring-arrays.md:43 +#: src/user-defined-types/enums.md:33 msgid "" -"Point out that how `..` will expand to account for different number of " -"elements." -msgstr "指出 `..` 是如何扩展以适应不同数量的元素的。" +"`PlayerMove` is a type with three variants. In addition to the payloads, " +"Rust will store a discriminant so that it knows at runtime which variant is " +"in a `PlayerMove` value." +msgstr "" -#: src/pattern-matching/destructuring-arrays.md:44 -msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" -msgstr "展示使用模式 `[.., b]` 和 `[a@..,b]` 来匹配切片的尾部。" +#: src/user-defined-types/enums.md:36 +#, fuzzy +msgid "This might be a good time to compare structs and enums:" +msgstr "这可能是比较结构体和枚举的好时机：" -#: src/pattern-matching/match-guards.md:3 +#: src/user-defined-types/enums.md:37 +#, fuzzy msgid "" -"When matching, you can add a _guard_ to a pattern. This is an arbitrary " -"Boolean expression which will be executed if the pattern matches:" +"In both, you can have a simple version without fields (unit struct) or one " +"with different types of fields (variant payloads)." msgstr "" -"匹配时，您可以向模式中添加“守卫”。这是一个任意布尔表达式，如果模式匹配，就会" -"执行该表达式：" +"在这两者中，你可以获得一个不含字段的简单版本（单位结构体），或一个包含不同类" +"型字段的版本（变体载荷）。" -#: src/pattern-matching/match-guards.md:6 +#: src/user-defined-types/enums.md:39 +#, fuzzy msgid "" -"```rust,editable\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let pair = (2, -2);\n" -" println!(\"Tell me about {pair:?}\");\n" -" match pair {\n" -" (x, y) if x == y => println!(\"These are twins\"),\n" -" (x, y) if x + y == 0 => println!(\"Antimatter, kaboom!\"),\n" -" (x, _) if x % 2 == 1 => println!(\"The first one is odd\"),\n" -" _ => println!(\"No correlation...\"),\n" -" }\n" -"}\n" -"```" +"You could even implement the different variants of an enum with separate " +"structs but then they wouldn’t be the same type as they would if they were " +"all defined in an enum." msgstr "" +"你甚至可以使用单独的结构体实现枚举的不同变体，但这样一来，如果它们都已在枚举" +"中定义，类型与之前也不一样。" -#: src/pattern-matching/match-guards.md:23 -msgid "" -"Match guards as a separate syntax feature are important and necessary when " -"we wish to concisely express more complex ideas than patterns alone would " -"allow." +#: src/user-defined-types/enums.md:42 +msgid "Rust uses minimal space to store the discriminant." msgstr "" -"有些想法比模式本身所允许的程度更加复杂，如果我们希望简要地表达这些想法，就必" -"须把匹配守卫视为独立的语法功能。" -#: src/pattern-matching/match-guards.md:24 -msgid "" -"They are not the same as separate `if` expression inside of the match arm. " -"An `if` expression inside of the branch block (after `=>`) happens after the " -"match arm is selected. Failing the `if` condition inside of that block won't " -"result in other arms of the original `match` expression being considered." +#: src/user-defined-types/enums.md:43 +msgid "If necessary, it stores an integer of the smallest required size" msgstr "" -"它们与匹配分支中的单独“if”表达式不同。选择匹配分支后，分支块内（在“=>”之后）" -"会出现“if”表达式。如果该分支块内的“if”条件失败，系统不会考虑原始“match”表达式" -"的其他分支。" -#: src/pattern-matching/match-guards.md:26 -msgid "You can use the variables defined in the pattern in your if expression." -msgstr "您可以在 if 表达式中使用模式中定义的变量。" - -#: src/pattern-matching/match-guards.md:27 +#: src/user-defined-types/enums.md:44 msgid "" -"The condition defined in the guard applies to every expression in a pattern " -"with an `|`." -msgstr "只要表达式在包含“|”的模式中，就会适用守卫定义的条件。" - -#: src/exercises/day-1/afternoon.md:1 -msgid "Day 1: Afternoon Exercises" -msgstr "第 1 天：下午练习" - -#: src/exercises/day-1/afternoon.md:3 -msgid "We will look at two things:" -msgstr "我们将关注以下两方面：" - -#: src/exercises/day-1/afternoon.md:5 -#, fuzzy -msgid "The Luhn algorithm," -msgstr "Luhn 算法" - -#: src/exercises/day-1/afternoon.md:7 -#, fuzzy -msgid "An exercise on pattern matching." -msgstr "枚举和模式匹配。" +"If the allowed variant values do not cover all bit patterns, it will use " +"invalid bit patterns to encode the discriminant (the \"niche " +"optimization\"). For example, `Option<&u8>` stores either a pointer to an " +"integer or `NULL` for the `None` variant." +msgstr "" -#: src/exercises/day-1/afternoon.md:11 src/exercises/day-2/afternoon.md:7 -#: src/exercises/bare-metal/afternoon.md:7 -#: src/exercises/concurrency/afternoon.md:13 +#: src/user-defined-types/enums.md:48 #, fuzzy msgid "" -"After looking at the exercises, you can look at the [solutions](solutions-" -"afternoon.md) provided." -msgstr "读完习题后，可以阅读本书提供的 \\[题解\\]。" +"You can control the discriminant if needed (e.g., for compatibility with C):" +msgstr "你可以根据需要控制判别（例如，与 C 的兼容性）：" -#: src/exercises/day-1/luhn.md:3 +#: src/user-defined-types/enums.md:66 +#, fuzzy msgid "" -"The [Luhn algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is used " -"to validate credit card numbers. The algorithm takes a string as input and " -"does the following to validate the credit card number:" +"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " +"bytes." msgstr "" -"[卢恩算法](https://zh.wikipedia.org/wiki/卢恩算法)用于验证信用卡号。该算法将" -"字符串作为输入内容，并执行以下操作来验证信用卡号：" - -#: src/exercises/day-1/luhn.md:7 -msgid "Ignore all spaces. Reject number with less than two digits." -msgstr "忽略所有空格。拒绝少于两位的号码。" +"如果不使用 `repr`，判别类型会占用 2 个字节，因为 10001 是一个 2 个字节的数" +"值。" -#: src/exercises/day-1/luhn.md:9 -msgid "" -"Moving from **right to left**, double every second digit: for the number " -"`1234`, we double `3` and `1`. For the number `98765`, we double `6` and `8`." +#: src/user-defined-types/enums.md:69 +#: src/user-defined-types/static-and-const.md:75 +#: src/memory-management/review.md:50 src/memory-management/move.md:99 +#: src/smart-pointers/box.md:83 src/borrowing/shared.md:32 +msgid "More to Explore" msgstr "" -"从**右到左**，将偶数位的数字乘二。对于数字“1234”，我们将“3”和“1”乘二；对于数" -"字“98765”，将“6”和“8”乘二。" -#: src/exercises/day-1/luhn.md:12 +#: src/user-defined-types/enums.md:71 msgid "" -"After doubling a digit, sum the digits if the result is greater than 9. So " -"doubling `7` becomes `14` which becomes `1 + 4 = 5`." +"Rust has several optimizations it can employ to make enums take up less " +"space." msgstr "" -"将一个数字乘二后，如果结果大于 9，则将每位数字相加。因此，将“7”乘二得“14”，然" -"后“1 + 4 = 5”。" - -#: src/exercises/day-1/luhn.md:15 -msgid "Sum all the undoubled and doubled digits." -msgstr "将所有未乘二和已乘二的数字相加。" -#: src/exercises/day-1/luhn.md:17 -msgid "The credit card number is valid if the sum ends with `0`." -msgstr "如果总和以“0”结尾，则信用卡号有效。" - -#: src/exercises/day-1/luhn.md:19 +#: src/user-defined-types/enums.md:73 #, fuzzy msgid "" -"Copy the code below to and implement the " -"function." -msgstr "将下面的代码复制到 并实现上述函数：" - -#: src/exercises/day-1/luhn.md:21 -msgid "" -"Try to solve the problem the \"simple\" way first, using `for` loops and " -"integers. Then, revisit the solution and try to implement it with iterators." +"Null pointer optimization: For [some types](https://doc.rust-lang.org/std/" +"option/#representation), Rust guarantees that `size_of::()` equals " +"`size_of::>()`." msgstr "" -"使用“for”循环和整数，先尝试以简单的方式解决问题。然后，再次查看该解决方案，并" -"尝试使用迭代器来实现它。" +"Null 指针优化：对于[某些 类型](https://doc.rust-lang.org/std/option/" +"#representation)，Rust 保证 `size_of::()` 等效于 `size_of::" +">()`。" -#: src/exercises/day-1/luhn.md:25 +#: src/user-defined-types/enums.md:77 +#, fuzzy msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub fn luhn(cc_number: &str) -> bool {\n" -" unimplemented!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_non_digit_cc_number() {\n" -" assert!(!luhn(\"foo\"));\n" -" assert!(!luhn(\"foo 0 0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty_cc_number() {\n" -" assert!(!luhn(\"\"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_digit_cc_number() {\n" -" assert!(!luhn(\"0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_two_digit_cc_number() {\n" -" assert!(luhn(\" 0 0 \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_valid_cc_number() {\n" -" assert!(luhn(\"4263 9826 4026 9299\"));\n" -" assert!(luhn(\"4539 3195 0343 6467\"));\n" -" assert!(luhn(\"7992 7398 713\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_invalid_cc_number() {\n" -" assert!(!luhn(\"4223 9826 4026 9299\"));\n" -" assert!(!luhn(\"4539 3195 0343 6476\"));\n" -" assert!(!luhn(\"8273 1232 7352 0569\"));\n" -"}\n" -"\n" -"#[allow(dead_code)]\n" -"fn main() {}\n" -"```" +"Example code if you want to show how the bitwise representation _may_ look " +"like in practice. It's important to note that the compiler provides no " +"guarantees regarding this representation, therefore this is totally unsafe." msgstr "" +"如果你想展示位表示方式在实践中“可能”会是什么样子，请参考示例代码。 请务必注" +"意，编译器对此表示法不提供任何保证，因此这是完全不安全的。" -#: src/exercises/day-1/pattern-matching.md:1 -msgid "Exercise: Expression Evaluation" +#: src/user-defined-types/static-and-const.md:3 +#, fuzzy +msgid "" +"Static and constant variables are two different ways to create globally-" +"scoped values that cannot be moved or reallocated during the execution of " +"the program." msgstr "" +"静态变量和常量是创建全局范围值的两种不同方法，这类值在程序执行期间无法移动或" +"重新分配。" -#: src/exercises/day-1/pattern-matching.md:3 -msgid "Let's write a simple recursive evaluator for arithmetic expressions. " -msgstr "" +#: src/user-defined-types/static-and-const.md:6 +msgid "`const`" +msgstr "`const`" -#: src/exercises/day-1/pattern-matching.md:5 +#: src/user-defined-types/static-and-const.md:8 msgid "" -"```rust\n" -"/// An operation to perform on two subexpressions.\n" -"#[derive(Debug)]\n" -"enum Operation {\n" -" Add,\n" -" Sub,\n" -" Mul,\n" -" Div,\n" -"}\n" -"\n" -"/// An expression, in tree form.\n" -"#[derive(Debug)]\n" -"enum Expression {\n" -" /// An operation on two subexpressions.\n" -" Op {\n" -" op: Operation,\n" -" left: Box,\n" -" right: Box,\n" -" },\n" -"\n" -" /// A literal value\n" -" Value(i64),\n" -"}\n" -"\n" -"/// The result of evaluating an expression.\n" -"#[derive(Debug, PartialEq, Eq)]\n" -"enum Res {\n" -" /// Evaluation was successful, with the given result.\n" -" Ok(i64),\n" -" /// Evaluation failed, with the given error message.\n" -" Err(String),\n" -"}\n" -"// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" -"use Res::{Err, Ok};\n" -"\n" -"fn eval(e: Expression) -> Res {\n" -" todo!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_value() {\n" -" assert_eq!(eval(Expression::Value(19)), Ok(19));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_sum() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(20)),\n" -" }),\n" -" Ok(30)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_recursion() {\n" -" let term1 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(9)),\n" -" };\n" -" let term2 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(3)),\n" -" right: Box::new(Expression::Value(4)),\n" -" }),\n" -" right: Box::new(Expression::Value(5)),\n" -" };\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(term1),\n" -" right: Box::new(term2),\n" -" }),\n" -" Ok(85)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_error() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Div,\n" -" left: Box::new(Expression::Value(99)),\n" -" right: Box::new(Expression::Value(0)),\n" -" }),\n" -" Err(String::from(\"division by zero\"))\n" -" );\n" -"}\n" -"```" -msgstr "" +"Constant variables are evaluated at compile time and their values are " +"inlined wherever they are used:" +msgstr "系统会在编译时对常量变量进行求值；无论在何处使用，其值都会被内嵌：" -#: src/exercises/day-1/pattern-matching.md:100 +#: src/user-defined-types/static-and-const.md:31 msgid "" -"The `Box` type here is a smart pointer, and will be covered in detail later " -"in the course. An expression can be \"boxed\" with `Box::new` as seen in the " -"tests. To evaluate a boxed expression, use the deref operator to \"unbox\" " -"it: `eval(*boxed_expr)`." +"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html) these are inlined upon use." msgstr "" +"根据 [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-vs-static." +"html) 这些变量在使用时是内联 (inlined) 的。" -#: src/exercises/day-1/pattern-matching.md:105 +#: src/user-defined-types/static-and-const.md:33 msgid "" -"Some expressions cannot be evaluated and will return an error. The `Res` " -"type represents either a successful value or an error with a message. This " -"is very similar to the standard-library `Result` which we will see later." +"Only functions marked `const` can be called at compile time to generate " +"`const` values. `const` functions can however be called at runtime." msgstr "" +"在编译时只能调用标记为“const”的函数以生成“const”值。不过，可在运行时调" +"用“const”函数。" -#: src/exercises/day-1/pattern-matching.md:109 +#: src/user-defined-types/static-and-const.md:36 +msgid "`static`" +msgstr "`static`" + +#: src/user-defined-types/static-and-const.md:38 msgid "" -"Copy and paste the code into the Rust playground, and begin implementing " -"`eval`. The final product should pass the tests. It may be helpful to use " -"`todo!()` and get the tests to pass one-by-one." +"Static variables will live during the whole execution of the program, and " +"therefore will not move:" +msgstr "静态变量在程序的整个执行过程中始终有效，因此不会移动：" + +#: src/user-defined-types/static-and-const.md:42 +#, fuzzy +msgid "\"Welcome to RustOS 3.14\"" +msgstr "欢迎来到第一天" + +#: src/user-defined-types/static-and-const.md:45 +msgid "\"{BANNER}\"" msgstr "" -#: src/exercises/day-1/pattern-matching.md:113 +#: src/user-defined-types/static-and-const.md:49 +#, fuzzy msgid "" -"If you finish early, try writing a test that results in an integer overflow. " -"How could you handle this with `Res::Err` instead of a panic?" +"As noted in the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html), these are not inlined upon use and have an actual " +"associated memory location. This is useful for unsafe and embedded code, and " +"the variable lives through the entirety of the program execution. When a " +"globally-scoped value does not have a reason to need object identity, " +"`const` is generally preferred." msgstr "" +"正如 [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-vs-static." +"html) 中所述，这些变量在使用时并不是内联的，而且还具有实际相关联的内存位置。" +"这对于不安全的嵌入式代码是有用的，并且这些变量存在于整个程序的执行过程之中。" -#: src/welcome-day-2.md:1 -msgid "Welcome to Day 2" -msgstr "欢迎来到第二天" - -#: src/welcome-day-2.md:3 -msgid "Now that we have seen a fair amount of Rust, we will continue with:" -msgstr "现在我们已经了解了相当多的Rust，接下来我们将学习：" +#: src/user-defined-types/static-and-const.md:57 +msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." +msgstr "值得一提的是，`const` 在语义上与C++的 `constexpr` 类似。" -#: src/welcome-day-2.md:5 +#: src/user-defined-types/static-and-const.md:58 msgid "" -"Memory management: stack vs heap, manual memory management, scope-based " -"memory management, and garbage collection." -msgstr "内存管理：栈与堆，手动内存管理，基于作用域的内存管理，以及垃圾回收。" +"`static`, on the other hand, is much more similar to a `const` or mutable " +"global variable in C++." +msgstr "另一方面，`static` 远远更类似于C++中的 `const` 或可改变的全局变量。" -#: src/welcome-day-2.md:8 +#: src/user-defined-types/static-and-const.md:60 +#, fuzzy msgid "" -"Ownership: move semantics, copying and cloning, borrowing, and lifetimes." +"`static` provides object identity: an address in memory and state as " +"required by types with interior mutability such as `Mutex`." msgstr "" -"所有权：移动（move）的语义，复制（copy）和克隆（clone），借用（borrow），以及" -"生命周期。" - -#: src/welcome-day-2.md:10 -#, fuzzy -msgid "Structs and methods." -msgstr "结构体（struct）, 枚举（enum）, 方法（method）。" +"“static”提供对象标识：内存中的一个地址及具有内部可变性的类型（如“Mutex\n" +"\n" +"”）所需的状态。" -#: src/welcome-day-2.md:12 +#: src/user-defined-types/static-and-const.md:62 msgid "" -"The Standard Library: `String`, `Option` and `Result`, `Vec`, `HashMap`, " -"`Rc` and `Arc`." +"It isn't super common that one would need a runtime evaluated constant, but " +"it is helpful and safer than using a static." msgstr "" -"标准库: `字符串（String）`, `选项（Option）` 和 `结果（Result）`, `动态数组" -"（Vec）`, `散列表（HashMap）`, `引用计数（Rc）` 和 `共享引用计数（Arc）`。" +"虽然需要使用在运行中求值的常量的情况并不是很常见，但是它是有帮助的，而且比使" +"用静态变量更安全。" -#: src/welcome-day-2.md:15 -msgid "Modules: visibility, paths, and filesystem hierarchy." -msgstr "模块: 可见性, 路径和文件系统的层次结构。" +#: src/user-defined-types/static-and-const.md:65 +msgid "Properties table:" +msgstr "属性表：" -#: src/memory-management.md:3 -msgid "Traditionally, languages have fallen into two broad categories:" -msgstr "传统上，语言分为两大类：" +#: src/user-defined-types/static-and-const.md:67 +#: src/chromium/adding-third-party-crates.md:6 +msgid "Property" +msgstr "属性" -#: src/memory-management.md:5 -msgid "Full control via manual memory management: C, C++, Pascal, ..." -msgstr "通过手动内存管理实现完全控制：C、C++、Pascal…" +#: src/user-defined-types/static-and-const.md:67 +#, fuzzy +msgid "Static" +msgstr "`static`" -#: src/memory-management.md:6 -msgid "" -"Full safety via automatic memory management at runtime: Java, Python, Go, " -"Haskell, ..." -msgstr "运行时通过自动内存管理实现完全安全：Java、Python、Go、Haskell…" +#: src/user-defined-types/static-and-const.md:67 +msgid "Constant" +msgstr "常量" -#: src/memory-management.md:8 -msgid "Rust offers a new mix:" -msgstr "Rust 提供了一个全新的组合：" - -#: src/memory-management.md:10 -msgid "" -"Full control _and_ safety via compile time enforcement of correct memory " -"management." -msgstr "通过编译时强制执行正确的内存>管理来实现完全控制与安全。" - -#: src/memory-management.md:13 -msgid "It does this with an explicit ownership concept." -msgstr "它通过一个明确的所有权（ownership）概念来实现此目的。" - -#: src/memory-management.md:15 -msgid "First, let's refresh how memory management works." -msgstr "首先，我们回顾一下内存管理的工作原理。" - -#: src/memory-management/stack-vs-heap.md:1 -msgid "The Stack vs The Heap" -msgstr "栈与堆" +#: src/user-defined-types/static-and-const.md:69 +msgid "Has an address in memory" +msgstr "在内存中有地址" -#: src/memory-management/stack-vs-heap.md:3 -msgid "Stack: Continuous area of memory for local variables." -msgstr "栈：局部变量的连续内存区域。" +#: src/user-defined-types/static-and-const.md:69 +#: src/user-defined-types/static-and-const.md:70 +#: src/user-defined-types/static-and-const.md:72 +#: src/user-defined-types/static-and-const.md:73 +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +msgid "Yes" +msgstr "是" -#: src/memory-management/stack-vs-heap.md:4 -msgid "Values have fixed sizes known at compile time." -msgstr "值在编译时具有已知的固定大小。" +#: src/user-defined-types/static-and-const.md:69 +msgid "No (inlined)" +msgstr "否（内嵌）" -#: src/memory-management/stack-vs-heap.md:5 -msgid "Extremely fast: just move a stack pointer." -msgstr "速度极快：只需移动一个栈指针。" +#: src/user-defined-types/static-and-const.md:70 +#, fuzzy +msgid "Lives for the entire duration of the program" +msgstr "`main` 函数是程序的入口。" -#: src/memory-management/stack-vs-heap.md:6 -msgid "Easy to manage: follows function calls." -msgstr "易于管理：遵循函数调用规则。" +#: src/user-defined-types/static-and-const.md:70 +#: src/user-defined-types/static-and-const.md:71 +#: src/user-defined-types/static-and-const.md:73 +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "No" +msgstr "否" -#: src/memory-management/stack-vs-heap.md:7 -msgid "Great memory locality." -msgstr "优秀的内存局部性。" +#: src/user-defined-types/static-and-const.md:71 +msgid "Can be mutable" +msgstr "可变" -#: src/memory-management/stack-vs-heap.md:9 -msgid "Heap: Storage of values outside of function calls." -msgstr "堆：函数调用之外的值的存储。" +#: src/user-defined-types/static-and-const.md:71 +msgid "Yes (unsafe)" +msgstr "是（不安全）" -#: src/memory-management/stack-vs-heap.md:10 -msgid "Values have dynamic sizes determined at runtime." -msgstr "值具有动态大小，具体大小需在运行时确定。" +#: src/user-defined-types/static-and-const.md:72 +#, fuzzy +msgid "Evaluated at compile time" +msgstr "值在编译时具有已知的固定大小。" -#: src/memory-management/stack-vs-heap.md:11 -msgid "Slightly slower than the stack: some book-keeping needed." -msgstr "比栈稍慢：需要向系统申请空间。" +#: src/user-defined-types/static-and-const.md:72 +msgid "Yes (initialised at compile time)" +msgstr "是（在编译时被初始化）" -#: src/memory-management/stack-vs-heap.md:12 -msgid "No guarantee of memory locality." -msgstr "不保证内存局部性。" +#: src/user-defined-types/static-and-const.md:73 +msgid "Inlined wherever it is used" +msgstr "内嵌在使用它的任何位置" -#: src/memory-management/stack.md:1 +#: src/user-defined-types/static-and-const.md:77 #, fuzzy -msgid "Stack and Heap Example" -msgstr "栈 vs 堆" +msgid "" +"Because `static` variables are accessible from any thread, they must be " +"`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" +"lang.org/std/sync/struct.Mutex.html), atomic or similar." +msgstr "" +"由于“static”变量可从任何线程访问，因此它们必须是“Sync”。内部可变性可通过[“互" +"斥量”](https://doc.rust-lang.org/std/sync/struct.Mutex.html)、原子性或类似对" +"象实现。也可能具有可变静态项，但它们需要手动同步，因此对它们的任何访问都需" +"要“unsafe”代码。我们将在“不安全 Rust”章节中探讨[可变静态项](../unsafe/" +"mutable-static-variables.md)。" -#: src/memory-management/stack.md:3 +#: src/user-defined-types/static-and-const.md:82 #, fuzzy +msgid "Thread-local data can be created with the macro `std::thread_local`." +msgstr "可以使用宏“std::thread_local”创建“thread_local”数据。" + +#: src/user-defined-types/aliases.md:3 msgid "" -"Creating a `String` puts fixed-sized metadata on the stack and dynamically " -"sized data, the actual string, on the heap:" +"A type alias creates a name for another type. The two types can be used " +"interchangeably." msgstr "" -"创建 `String` 时将固定大小的数据存储在栈上， 并将动态大小的数据存储在堆上：" -#: src/memory-management/stack.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1 = String::from(\"Hello\");\n" -"}\n" -"```" +#: src/user-defined-types/aliases.md:13 +msgid "// Aliases are more useful with long, complex types:\n" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let s1 = String::from(\"Hello\");\n" -"}\n" -"```" -#: src/memory-management/stack.md:28 -msgid "" -"Mention that a `String` is backed by a `Vec`, so it has a capacity and " -"length and can grow if mutable via reallocation on the heap." +#: src/user-defined-types/aliases.md:22 +msgid "C programmers will recognize this as similar to a `typedef`." msgstr "" -"指出 `String` 底层由 `Vec` 实现，因此它具有容量和长度，如果值可变，则可以通过" -"在堆上重新分配存储空间进行增长。" -#: src/memory-management/stack.md:30 +#: src/user-defined-types/exercise.md:3 msgid "" -"If students ask about it, you can mention that the underlying memory is heap " -"allocated using the [System Allocator](https://doc.rust-lang.org/std/alloc/" -"struct.System.html) and custom allocators can be implemented using the " -"[Allocator API](https://doc.rust-lang.org/std/alloc/index.html)" +"We will create a data structure to represent an event in an elevator control " +"system. It is up to you to define the types and functions to construct " +"various events. Use `#[derive(Debug)]` to allow the types to be formatted " +"with `{:?}`." msgstr "" -"如果学员提出相关问题，你可以提及我们不仅能使用\\[系统分配器\\]在堆上分配底层" -"内存，还能使用 [Allocator API](https://doc.rust-lang.org/std/alloc/index." -"html) 实现自定义分配器" -#: src/memory-management/stack.md:32 +#: src/user-defined-types/exercise.md:7 msgid "" -"We can inspect the memory layout with `unsafe` code. However, you should " -"point out that this is rightfully unsafe!" +"This exercise only requires creating and populating data structures so that " +"`main` runs without errors. The next part of the course will cover getting " +"data out of these structures." msgstr "" -"我们可以使用 `unsafe` 代码检查内存布局。不过，你应该指出，这种做法不安全！" -#: src/memory-management/stack.md:34 -#, fuzzy +#: src/user-defined-types/exercise.md:12 src/user-defined-types/solution.md:4 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut s1 = String::from(\"Hello\");\n" -" s1.push(' ');\n" -" s1.push_str(\"world\");\n" -" // DON'T DO THIS AT HOME! For educational purposes only.\n" -" // String provides no guarantees about its layout, so this could lead " -"to\n" -" // undefined behavior.\n" -" unsafe {\n" -" let (ptr, capacity, len): (usize, usize, usize) = std::mem::" -"transmute(s1);\n" -" println!(\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\");\n" -" }\n" -"}\n" -"```" +"/// An event in the elevator system that the controller must react to.\n" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let mut s1 = String::from(\"Hello\");\n" -" s1.push(' ');\n" -" s1.push_str(\"world\");\n" -" // DON'T DO THIS AT HOME! For educational purposes only.\n" -" // String provides no guarantees about its layout, so this could lead " -"to\n" -" // undefined behavior.\n" -" unsafe {\n" -" let (capacity, ptr, len): (usize, usize, usize) = std::mem::" -"transmute(s1);\n" -" println!(\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\");\n" -" }\n" -"}\n" -"```" -#: src/memory-management/manual.md:3 -msgid "You allocate and deallocate heap memory yourself." -msgstr "你自己实现堆内存分配和释放。" +#: src/user-defined-types/exercise.md:15 +msgid "// TODO: add required variants\n" +msgstr "" -#: src/memory-management/manual.md:5 -msgid "" -"If not done with care, this can lead to crashes, bugs, security " -"vulnerabilities, and memory leaks." -msgstr "稍有不慎，这可能会导致崩溃、bug、安全漏洞和内存泄漏。" +#: src/user-defined-types/exercise.md:17 src/user-defined-types/solution.md:22 +msgid "/// A direction of travel.\n" +msgstr "" -#: src/memory-management/manual.md:7 -msgid "C Example" -msgstr "C++ 示例" +#: src/user-defined-types/exercise.md:24 src/user-defined-types/solution.md:39 +msgid "/// The car has arrived on the given floor.\n" +msgstr "" -#: src/memory-management/manual.md:9 -msgid "You must call `free` on every pointer you allocate with `malloc`:" -msgstr "你必须对使用 `malloc` 分配的每个指针调用 `free`：" +#: src/user-defined-types/exercise.md:29 src/user-defined-types/solution.md:44 +msgid "/// The car doors have opened.\n" +msgstr "" -#: src/memory-management/manual.md:11 -#, fuzzy -msgid "" -"```c\n" -"void foo(size_t n) {\n" -" int* int_array = malloc(n * sizeof(int));\n" -" //\n" -" // ... lots of code\n" -" //\n" -" free(int_array);\n" -"}\n" -"```" +#: src/user-defined-types/exercise.md:34 src/user-defined-types/solution.md:49 +msgid "/// The car doors have closed.\n" msgstr "" -"```c\n" -"void foo(size_t n) {\n" -" int* int_array = (int*)malloc(n * sizeof(int));\n" -" //\n" -" // ... lots of code\n" -" //\n" -" free(int_array);\n" -"}\n" -"```" -#: src/memory-management/manual.md:21 -#, fuzzy +#: src/user-defined-types/exercise.md:39 src/user-defined-types/solution.md:54 msgid "" -"Memory is leaked if the function returns early between `malloc` and `free`: " -"the pointer is lost and we cannot deallocate the memory. Worse, freeing the " -"pointer twice, or accessing a freed pointer can lead to exploitable security " -"vulnerabilities." +"/// A directional button was pressed in an elevator lobby on the given " +"floor.\n" msgstr "" -"如果函数在 `malloc` 和 `free` 之间提前返回，则会导致内存泄漏： 指针丢失，而我" -"们无法释放对应的内存。" -#: src/memory-management/scope-based.md:3 -msgid "" -"Constructors and destructors let you hook into the lifetime of an object." -msgstr "构造函数和析构函数让你可以钩入对象的生命周期。" +#: src/user-defined-types/exercise.md:44 src/user-defined-types/solution.md:59 +msgid "/// A floor button was pressed in the elevator car.\n" +msgstr "" -#: src/memory-management/scope-based.md:5 -msgid "" -"By wrapping a pointer in an object, you can free memory when the object is " -"destroyed. The compiler guarantees that this happens, even if an exception " -"is raised." +#: src/user-defined-types/exercise.md:52 src/user-defined-types/solution.md:67 +msgid "\"A ground floor passenger has pressed the up button: {:?}\"" msgstr "" -"通过将指针封装在对象中，你可以在该对象 被销毁时释放内存。编译器可保证这一点的" -"实现，即使引发了异常也不例外。" -#: src/memory-management/scope-based.md:9 -msgid "" -"This is often called _resource acquisition is initialization_ (RAII) and " -"gives you smart pointers." +#: src/user-defined-types/exercise.md:55 src/user-defined-types/solution.md:70 +msgid "\"The car has arrived on the ground floor: {:?}\"" msgstr "" -"这通常称为“资源获取即初始化 (resource acquisition is initialization, " -"RAII)”， 并为你提供智能指针。" -#: src/memory-management/scope-based.md:12 -msgid "C++ Example" -msgstr "C++ 示例" +#: src/user-defined-types/exercise.md:56 src/user-defined-types/solution.md:71 +msgid "\"The car door opened: {:?}\"" +msgstr "" -#: src/memory-management/scope-based.md:14 -msgid "" -"```c++\n" -"void say_hello(std::unique_ptr person) {\n" -" std::cout << \"Hello \" << person->name << std::endl;\n" -"}\n" -"```" +#: src/user-defined-types/exercise.md:58 src/user-defined-types/solution.md:73 +msgid "\"A passenger has pressed the 3rd floor button: {:?}\"" msgstr "" -"```c++\n" -"void say_hello(std::unique_ptr person) {\n" -" std::cout << \"Hello \" << person->name << std::endl;\n" -"}\n" -"```" -#: src/memory-management/scope-based.md:20 -msgid "" -"The `std::unique_ptr` object is allocated on the stack, and points to memory " -"allocated on the heap." -msgstr "`std::unique_ptr` 对象在栈上分配内存，并指向在堆上分配的内存。" +#: src/user-defined-types/exercise.md:61 src/user-defined-types/solution.md:76 +msgid "\"The car door closed: {:?}\"" +msgstr "" -#: src/memory-management/scope-based.md:22 -msgid "At the end of `say_hello`, the `std::unique_ptr` destructor will run." -msgstr "在 `say_hello` 结束时，`std::unique_ptr` 析构函数将运行。" +#: src/user-defined-types/exercise.md:62 src/user-defined-types/solution.md:77 +msgid "\"The car has arrived on the 3rd floor: {:?}\"" +msgstr "" -#: src/memory-management/scope-based.md:23 -msgid "The destructor frees the `Person` object it points to." -msgstr "析构函数释放它所指向的 `Person` 对象。" +#: src/user-defined-types/solution.md:7 +msgid "/// A button was pressed.\n" +msgstr "" -#: src/memory-management/scope-based.md:25 -msgid "" -"Special move constructors are used when passing ownership to a function:" -msgstr "将所有权传递给函数时，使用特殊的 move 构造函数：" +#: src/user-defined-types/solution.md:10 +msgid "/// The car has arrived at the given floor.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:1 -msgid "Automatic Memory Management" -msgstr "自动内存管理" +#: src/user-defined-types/solution.md:13 +msgid "/// The car's doors have opened.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:3 -msgid "" -"An alternative to manual and scope-based memory management is automatic " -"memory management:" -msgstr "自动内存管理是手动和基于作用域的内存管理 的替代方案：" +#: src/user-defined-types/solution.md:16 +msgid "/// The car's doors have closed.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:6 -msgid "The programmer never allocates or deallocates memory explicitly." -msgstr "程序员从不显式分配或取消分配内存。" +#: src/user-defined-types/solution.md:19 +msgid "/// A floor is represented as an integer.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:7 -msgid "" -"A garbage collector finds unused memory and deallocates it for the " -"programmer." -msgstr "垃圾回收器找到未使用的内存，并为程序员将其取消分配。" +#: src/user-defined-types/solution.md:29 +msgid "/// A user-accessible button.\n" +msgstr "" + +#: src/user-defined-types/solution.md:33 +msgid "/// A button in the elevator lobby on the given floor.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:9 -msgid "Java Example" -msgstr "Java 示例" +#: src/user-defined-types/solution.md:36 +msgid "/// A floor button within the car.\n" +msgstr "" -#: src/memory-management/garbage-collection.md:11 -msgid "The `person` object is not deallocated after `sayHello` returns:" -msgstr "`sayHello` 返回后，`person` 对象未被取消分配：" +#: src/welcome-day-2.md:1 +msgid "Welcome to Day 2" +msgstr "欢迎来到第二天" -#: src/memory-management/garbage-collection.md:13 +#: src/welcome-day-2.md:3 +#, fuzzy msgid "" -"```java\n" -"void sayHello(Person person) {\n" -" System.out.println(\"Hello \" + person.getName());\n" -"}\n" -"```" -msgstr "" -"```java\n" -"void sayHello(Person person) {\n" -" System.out.println(\"Hello \" + person.getName());\n" -"}\n" -"```" +"Now that we have seen a fair amount of Rust, today will focus on Rust's type " +"system:" +msgstr "现在我们已经了解了相当多的Rust，接下来我们将学习：" -#: src/memory-management/rust.md:1 -msgid "Memory Management in Rust" -msgstr "Rust 中的内存管理" +#: src/welcome-day-2.md:6 +#, fuzzy +msgid "Pattern matching: extracting data from structures." +msgstr "模式匹配：解构枚举、结构体和数组（array）。" -#: src/memory-management/rust.md:3 -msgid "Memory management in Rust is a mix:" -msgstr "Rust 中的内存管理是一种混合模式：" +#: src/welcome-day-2.md:7 +msgid "Methods: associating functions with types." +msgstr "" -#: src/memory-management/rust.md:5 -msgid "Safe and correct like Java, but without a garbage collector." -msgstr "像 Java 一样安全又正确，但没有垃圾回收器。" +#: src/welcome-day-2.md:8 +msgid "Traits: behaviors shared by multiple types." +msgstr "" -#: src/memory-management/rust.md:6 -msgid "Scope-based like C++, but the compiler enforces full adherence." -msgstr "像 C++ 一样基于作用域，但编译器会强制完全遵循规则。" +#: src/welcome-day-2.md:9 +msgid "Generics: parameterizing types on other types." +msgstr "" -#: src/memory-management/rust.md:7 +#: src/welcome-day-2.md:10 msgid "" -"A Rust user can choose the right abstraction for the situation, some even " -"have no cost at runtime like C." +"Standard library types and traits: a tour of Rust's rich standard library." msgstr "" -"Rust 用户可以根据具体情况选择合适的抽象，有些甚至没有像 C 那样的运行时开销。" -#: src/memory-management/rust.md:9 -#, fuzzy -msgid "Rust achieves this by modeling _ownership_ explicitly." -msgstr "它通过对“所有权”进行显式建模来实现这一点。" +#: src/pattern-matching/destructuring.md:3 +msgid "Like tuples, structs and enums can also be destructured by matching:" +msgstr "" -#: src/memory-management/rust.md:13 -msgid "" -"If asked how at this point, you can mention that in Rust this is usually " -"handled by RAII wrapper types such as [Box](https://doc.rust-lang.org/std/" -"boxed/struct.Box.html), [Vec](https://doc.rust-lang.org/std/vec/struct.Vec." -"html), [Rc](https://doc.rust-lang.org/std/rc/struct.Rc.html), or [Arc]" -"(https://doc.rust-lang.org/std/sync/struct.Arc.html). These encapsulate " -"ownership and memory allocation via various means, and prevent the potential " -"errors in C." +#: src/pattern-matching/destructuring.md:5 +#: src/pattern-matching/destructuring.md:58 +msgid "Structs" +msgstr "结构体" + +#: src/pattern-matching/destructuring.md:17 +msgid "\"x.0 = 1, b = {b}, y = {y}\"" msgstr "" -"如果此时被问及如何操作，你可以提及在 Rust 中，这通常由 RAII 封装容器类型（例" -"如 [Box](https://doc.rust-lang.org/std/boxed/struct.Box.html)、[Vec](https://" -"doc.rust-lang.org/std/vec/struct.Vec.html)、[Rc](https://doc.rust-lang.org/" -"std/rc/struct.Rc.html) 或 [Arc](https://doc.rust-lang.org/std/sync/struct." -"Arc.html)）处理。这些类型通过各种方式封装了所有权和内存分配，并防止了 C 中潜" -"在错误的发生。" -#: src/memory-management/rust.md:15 -msgid "" -"You may be asked about destructors here, the [Drop](https://doc.rust-lang." -"org/std/ops/trait.Drop.html) trait is the Rust equivalent." +#: src/pattern-matching/destructuring.md:18 +msgid "\"y = 2, x = {i:?}\"" msgstr "" -"你可能会被问及析构函数，此处 [Drop](https://doc.rust-lang.org/std/ops/trait." -"Drop.html) trait 是 Rust 等效项。" -#: src/ownership.md:3 -msgid "" -"All variable bindings have a _scope_ where they are valid and it is an error " -"to use a variable outside its scope:" -msgstr "所有变量绑定都有一个有效的“作用域”，使用 超出其作用域的变量是错误的：" +#: src/pattern-matching/destructuring.md:19 +msgid "\"y = {y}, other fields were ignored\"" +msgstr "" -#: src/ownership.md:19 +#: src/pattern-matching/destructuring.md:26 msgid "" -"At the end of the scope, the variable is _dropped_ and the data is freed." -msgstr "作用域结束时，变量会“被丢弃”，数据会被释放。" +"Patterns can also be used to bind variables to parts of your values. This is " +"how you inspect the structure of your types. Let us start with a simple " +"`enum` type:" +msgstr "" +"模式还可用于将变量绑定到值的某些部分。这是您检查类型结构的方式。我们先从简单" +"的“enum”类型开始：" -#: src/ownership.md:20 -msgid "A destructor can run here to free up resources." -msgstr "析构函数可在此运行以释放资源。" +#: src/pattern-matching/destructuring.md:39 +msgid "\"cannot divide {n} into two equal parts\"" +msgstr "" -#: src/ownership.md:21 -msgid "We say that the variable _owns_ the value." -msgstr "指出变量“拥有”值。" +#: src/pattern-matching/destructuring.md:46 +msgid "\"{n} divided in two is {half}\"" +msgstr "" -#: src/ownership/move-semantics.md:3 -#, fuzzy -msgid "An assignment will transfer _ownership_ between variables:" -msgstr "赋值操作将在变量之间转移所有权：" +#: src/pattern-matching/destructuring.md:47 +msgid "\"sorry, an error happened: {msg}\"" +msgstr "" -#: src/ownership/move-semantics.md:5 +#: src/pattern-matching/destructuring.md:52 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1: String = String::from(\"Hello!\");\n" -" let s2: String = s1;\n" -" println!(\"s2: {s2}\");\n" -" // println!(\"s1: {s1}\");\n" -"}\n" -"```" +"Here we have used the arms to _destructure_ the `Result` value. In the first " +"arm, `half` is bound to the value inside the `Ok` variant. In the second " +"arm, `msg` is bound to the error message." msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let s1: String = String::from(\"Hello!\");\n" -" let s2: String = s1;\n" -" println!(\"s2: {s2}\");\n" -" // println!(\"s1: {s1}\");\n" -"}\n" -"```" +"在这里，我们使用了分支来解构“Result”值。在第一个分支中，“half”被绑定到“Ok”变" +"体中的值。在第二个分支中，“msg”被绑定到错误消息。" -#: src/ownership/move-semantics.md:14 -msgid "The assignment of `s1` to `s2` transfers ownership." -msgstr "将 `s1` 赋值给 `s2`，即转移了所有权。" +#: src/pattern-matching/destructuring.md:60 +msgid "Change the literal values in `foo` to match with the other patterns." +msgstr "更改“foo”中的字面量值以与其他模式相匹配。" -#: src/ownership/move-semantics.md:15 -#, fuzzy -msgid "When `s1` goes out of scope, nothing happens: it does not own anything." -msgstr "当 `s1` 离开作用域时，什么都不会发生：它没有所有权。" +#: src/pattern-matching/destructuring.md:61 +msgid "Add a new field to `Foo` and make changes to the pattern as needed." +msgstr "向“Foo”添加一个新字段，并根据需要更改模式。" -#: src/ownership/move-semantics.md:16 -msgid "When `s2` goes out of scope, the string data is freed." -msgstr "当 `s2` 离开作用域时，字符串数据被释放。" +#: src/pattern-matching/destructuring.md:62 +msgid "" +"The distinction between a capture and a constant expression can be hard to " +"spot. Try changing the `2` in the second arm to a variable, and see that it " +"subtly doesn't work. Change it to a `const` and see it working again." +msgstr "" +"捕获和常量表达式之间的区别可能很难发现。尝试将第二个分支中的“2”更改为一个变" +"量，可以看到它几乎无法运作了。将它更改为“const”，可以看到它又正常运作了。" -#: src/ownership/move-semantics.md:17 -msgid "There is always _exactly_ one variable binding which owns a value." -msgstr "变量绑定在任一时刻有且“只有”一个值。" +#: src/pattern-matching/destructuring.md:70 +msgid "" +"The `if`/`else` expression is returning an enum that is later unpacked with " +"a `match`." +msgstr "“if”/“else”表达式将返回一个枚举，该枚举之后会使用“match”进行解封装。" -#: src/ownership/move-semantics.md:21 +#: src/pattern-matching/destructuring.md:72 msgid "" -"Mention that this is the opposite of the defaults in C++, which copies by " -"value unless you use `std::move` (and the move constructor is defined!)." +"You can try adding a third variant to the enum definition and displaying the " +"errors when running the code. Point out the places where your code is now " +"inexhaustive and how the compiler tries to give you hints." msgstr "" -"指出这与 C++ 中的默认值相反。除非你使用 `std::move`（并已定义 move 构造函" -"数！），否则 C++ 中的默认值是按值复制的。" +"您可以尝试在枚举定义中添加第三个变体，并在运行代码时显示错误。指出代码现在有" +"哪些地方还不详尽，并说明编译器会如何尝试给予提示。" -#: src/ownership/move-semantics.md:23 +#: src/pattern-matching/destructuring.md:75 msgid "" -"It is only the ownership that moves. Whether any machine code is generated " -"to manipulate the data itself is a matter of optimization, and such copies " -"are aggressively optimized away." +"The values in the enum variants can only be accessed after being pattern " +"matched. The pattern binds references to the fields in the \"match arm\" " +"after the `=>`." msgstr "" -"只有所有权发生了转移。是否会生成任何机器码来操控数据本身是一个优化方面的问" -"题，系统会主动优化此类副本。" +"枚举变体中的值只有在被模式匹配后，才可访问。模式将引用绑定到 `=>` 之后" +"的“match 分支”中的字段。" -#: src/ownership/move-semantics.md:25 +#: src/pattern-matching/destructuring.md:78 +#, fuzzy msgid "" -"Simple values (such as integers) can be marked `Copy` (see later slides)." -msgstr "简单的值（例如整数）可以标记为“Copy”（请看后续幻灯片）。" - -#: src/ownership/move-semantics.md:27 -msgid "In Rust, clones are explicit (by using `clone`)." -msgstr "在 Rust 中，克隆是显式的（通过使用 `clone`）。" +"Demonstrate what happens when the search is inexhaustive. Note the advantage " +"the Rust compiler provides by confirming when all cases are handled." +msgstr "" +"展示搜索不详尽时会发生的情况。请注意 Rust 编译器的优势，即确认所有情况何时都" +"得到了处理。" -#: src/ownership/moved-strings-rust.md:11 -msgid "The heap data from `s1` is reused for `s2`." -msgstr "`s1` 中的堆数据会被 `s2` 重复使用。" +#: src/pattern-matching/let-control-flow.md:3 +msgid "" +"Rust has a few control flow constructs which differ from other languages. " +"They are used for pattern matching:" +msgstr "Rust 有几个与其他语言不同的控制流结构。它们用于模式匹配：" -#: src/ownership/moved-strings-rust.md:12 -msgid "When `s1` goes out of scope, nothing happens (it has been moved from)." -msgstr "当 `s1` 离开作用域时，什么都不会发生（它已被移出）。" +#: src/pattern-matching/let-control-flow.md:6 +#: src/pattern-matching/let-control-flow.md:10 +msgid "`if let` expressions" +msgstr "`if let` 表达式" -#: src/ownership/moved-strings-rust.md:14 -msgid "Before move to `s2`:" -msgstr "移动到 `s2` 中之前：" +#: src/pattern-matching/let-control-flow.md:7 +#, fuzzy +msgid "`while let` expressions" +msgstr "while let 表达式" -#: src/ownership/moved-strings-rust.md:31 -msgid "After move to `s2`:" -msgstr "移动到 `s2` 中之后：" +#: src/pattern-matching/let-control-flow.md:8 +msgid "`match` expressions" +msgstr "`match` 表达式" -#: src/ownership/moved-strings-rust.md:33 +#: src/pattern-matching/let-control-flow.md:12 msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" -": : : :\n" -": s1 \"(inaccessible)\" : : :\n" -": +-----------+-------+ : : +----+----+----+----+ :\n" -": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" -": | len | 4 | : | : +----+----+----+----+ :\n" -": | capacity | 4 | : | : :\n" -": +-----------+-------+ : | : :\n" -": : | `- - - - - - - - - - - - - -'\n" -": s2 : |\n" -": +-----------+-------+ : |\n" -": | ptr | o---+---+--'\n" -": | len | 4 | :\n" -": | capacity | 4 | :\n" -": +-----------+-------+ :\n" -": :\n" -"`- - - - - - - - - - - - - -'\n" -"```" +"The [`if let` expression](https://doc.rust-lang.org/reference/expressions/if-" +"expr.html#if-let-expressions) lets you execute different code depending on " +"whether a value matches a pattern:" msgstr "" -"```bob\n" -" 栈 堆\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" -": : : :\n" -": s1 \"（无法访问）\" : : :\n" -": +-----------+-------+ : : +----+----+----+----+ :\n" -": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" -": | len | 4 | : | : +----+----+----+----+ :\n" -": | capacity | 4 | : | : :\n" -": +-----------+-------+ : | : :\n" -": : | `- - - - - - - - - - - - - -'\n" -": s2 : |\n" -": +-----------+-------+ : |\n" -": | ptr | o---+---+--'\n" -": | len | 4 | :\n" -": | capacity | 4 | :\n" -": +-----------+-------+ :\n" -": :\n" -"`- - - - - - - - - - - - - -'\n" -"```" +"[`if let` 表达式](https://doc.rust-lang.org/reference/expressions/if-expr." +"html#if-let-expressions) 能让你根据某个值是否与模式相匹配来执行不同的代码：" -#: src/ownership/double-free-modern-cpp.md:1 -#, fuzzy -msgid "Defensive Copies in Modern C++" -msgstr "现代 C++ 中的双重释放" +#: src/pattern-matching/let-control-flow.md:24 +msgid "\"slept for {:?}\"" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:3 -msgid "Modern C++ solves this differently:" -msgstr "现代 C++ 以不同的方式解决此问题：" +#: src/pattern-matching/let-control-flow.md:33 +#, fuzzy +msgid "`let else` expressions" +msgstr "while let 表达式" -#: src/ownership/double-free-modern-cpp.md:5 +#: src/pattern-matching/let-control-flow.md:35 msgid "" -"```c++\n" -"std::string s1 = \"Cpp\";\n" -"std::string s2 = s1; // Duplicate the data in s1.\n" -"```" +"For the common case of matching a pattern and returning from the function, " +"use [`let else`](https://doc.rust-lang.org/rust-by-example/flow_control/" +"let_else.html). The \"else\" case must diverge (`return`, `break`, or panic " +"- anything but falling off the end of the block)." msgstr "" -"```c++\n" -"std::string s1 = \"Cpp\";\n" -"std::string s2 = s1; // 复制 s1 中的数据。\n" -"```" - -#: src/ownership/double-free-modern-cpp.md:10 -msgid "" -"The heap data from `s1` is duplicated and `s2` gets its own independent copy." -msgstr "`s1` 中的堆数据被复制，`s2` 获得自己的独立副本。" - -#: src/ownership/double-free-modern-cpp.md:11 -msgid "When `s1` and `s2` go out of scope, they each free their own memory." -msgstr "当 `s1` 和 `s2` 离开作用域时，它们会各自释放自己的内存。" -#: src/ownership/double-free-modern-cpp.md:13 -msgid "Before copy-assignment:" -msgstr "复制-赋值之前：" +#: src/pattern-matching/let-control-flow.md:45 +#: src/pattern-matching/let-control-flow.md:107 +msgid "\"got None\"" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:30 -msgid "After copy-assignment:" -msgstr "复制-赋值之后：" +#: src/pattern-matching/let-control-flow.md:51 +#: src/pattern-matching/let-control-flow.md:111 +msgid "\"got empty string\"" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:57 -msgid "" -"C++ has made a slightly different choice than Rust. Because `=` copies data, " -"the string data has to be cloned. Otherwise we would get a double-free when " -"either string goes out of scope." +#: src/pattern-matching/let-control-flow.md:57 +#: src/pattern-matching/let-control-flow.md:115 +msgid "\"not a hex digit\"" msgstr "" -"C++ 做出了与 Rust 略有不同的选择。由于“=”会复制数据，因此必须克隆字符串数据。" -"否则，当任一字符串超出范围时，便会出现二次释放。" -#: src/ownership/double-free-modern-cpp.md:61 -msgid "" -"C++ also has [`std::move`](https://en.cppreference.com/w/cpp/utility/move), " -"which is used to indicate when a value may be moved from. If the example had " -"been `s2 = std::move(s1)`, no heap allocation would take place. After the " -"move, `s1` would be in a valid but unspecified state. Unlike Rust, the " -"programmer is allowed to keep using `s1`." +#: src/pattern-matching/let-control-flow.md:62 +#: src/pattern-matching/solution.md:113 +msgid "\"result: {:?}\"" msgstr "" -"C++ 还包含[“std::move”](https://en.cppreference.com/w/cpp/utility/move)，它用" -"于指示何时可以移动某个值。如果示例为“s2 = std::move(s1)”，则不会发生堆分配。" -"移动后，“s1”将处于有效但未指定的状态。与 Rust 不同，程序员可以继续使用“s1”。" -#: src/ownership/double-free-modern-cpp.md:66 -msgid "" -"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " -"which is being copied or moved." +#: src/pattern-matching/let-control-flow.md:62 +#: src/methods-and-traits/exercise.md:114 +#: src/methods-and-traits/exercise.md:115 +#: src/methods-and-traits/exercise.md:116 src/generics/trait-bounds.md:16 +#: src/smart-pointers/solution.md:87 src/smart-pointers/solution.md:90 +#: src/testing/googletest.md:11 src/testing/googletest.md:12 +#: src/testing/solution.md:83 +msgid "\"foo\"" msgstr "" -"与 Rust 不同，使用 C++ 时，“=”可以运行任意代码，具体取决于要复制或移动的类" -"型。" -#: src/ownership/moves-function-calls.md:3 +#: src/pattern-matching/let-control-flow.md:66 msgid "" -"When you pass a value to a function, the value is assigned to the function " -"parameter. This transfers ownership:" -msgstr "你将值传递给函数时，该值会被赋给函数 参数。这就转移了所有权：" +"Like with `if let`, there is a [`while let`](https://doc.rust-lang.org/" +"reference/expressions/loop-expr.html#predicate-pattern-loops) variant which " +"repeatedly tests a value against a pattern:" +msgstr "" +"与 `if let` 一样，[`while let`](https://doc.rust-lang.org/reference/" +"expressions/loop-expr.html#predicate-pattern-loops) 变体会针对一个模式重复测" +"试一个值：" -#: src/ownership/moves-function-calls.md:6 +#: src/pattern-matching/let-control-flow.md:82 +#, fuzzy msgid "" -"```rust,editable\n" -"fn say_hello(name: String) {\n" -" println!(\"Hello {name}\")\n" -"}\n" -"\n" -"fn main() {\n" -" let name = String::from(\"Alice\");\n" -" say_hello(name);\n" -" // say_hello(name);\n" -"}\n" -"```" +"Here [`String::pop`](https://doc.rust-lang.org/stable/std/string/struct." +"String.html#method.pop) returns `Some(c)` until the string is empty, after " +"which it will return `None`. The `while let` lets us keep iterating through " +"all items." msgstr "" -"```rust,editable\n" -"fn say_hello(name: String) {\n" -" println!(\"Hello {name}\")\n" -"}\n" -"\n" -"fn main() {\n" -" let name = String::from(\"Alice\");\n" -" say_hello(name);\n" -" // say_hello(name);\n" -"}\n" -"```" +"在这里，每次 调用 `next()` 时，`v.iter()` 返回的迭代器都会返回一个 " +"`Option`。它将一直返回 `Some(x)`，直到完成。 之后它将返回 `None`。" +"`while let`能让我们持续迭代所有项。" -#: src/ownership/moves-function-calls.md:20 -msgid "" -"With the first call to `say_hello`, `main` gives up ownership of `name`. " -"Afterwards, `name` cannot be used anymore within `main`." +#: src/pattern-matching/let-control-flow.md:89 +msgid "if-let" msgstr "" -"首次调用 `say_hello` 时，`main` 便放弃了 `name` 的所有权。此后，`main` 中不能" -"再使用 `name`。" -#: src/ownership/moves-function-calls.md:21 +#: src/pattern-matching/let-control-flow.md:91 +#, fuzzy msgid "" -"The heap memory allocated for `name` will be freed at the end of the " -"`say_hello` function." -msgstr "在 `say_hello` 函数结束时，系统会释放为 `name` 分配的堆内存。" +"Unlike `match`, `if let` does not have to cover all branches. This can make " +"it more concise than `match`." +msgstr "与 `match` 不同的是，`if let` 不支持模式匹配的 guard 子句。" -#: src/ownership/moves-function-calls.md:22 -msgid "" -"`main` can retain ownership if it passes `name` as a reference (`&name`) and " -"if `say_hello` accepts a reference as a parameter." -msgstr "" -"如果 `main` 将 `name` 作为引用 (`&name`) 传递过去，且 `say_hello` 接受作为参" -"数的引用，则可保留所有权。" +#: src/pattern-matching/let-control-flow.md:93 +msgid "A common usage is handling `Some` values when working with `Option`." +msgstr "使用 `Option` 时，常见的做法是处理 `Some` 值。" -#: src/ownership/moves-function-calls.md:23 +#: src/pattern-matching/let-control-flow.md:94 msgid "" -"Alternatively, `main` can pass a clone of `name` in the first call (`name." -"clone()`)." -msgstr "此外，`main` 也可以在首次调用时传递 `name` 的克隆 (`name.clone()`)。" +"Unlike `match`, `if let` does not support guard clauses for pattern matching." +msgstr "与 `match` 不同的是，`if let` 不支持模式匹配的 guard 子句。" -#: src/ownership/moves-function-calls.md:24 -msgid "" -"Rust makes it harder than C++ to inadvertently create copies by making move " -"semantics the default, and by forcing programmers to make clones explicit." +#: src/pattern-matching/let-control-flow.md:96 +msgid "let-else" msgstr "" -"相较于 C++，Rust 通过将移动语义设为默认值，并强制程序员进行显式克隆，更难以无" -"意中创建副本。" -#: src/ownership/copy-clone.md:3 +#: src/pattern-matching/let-control-flow.md:98 msgid "" -"While move semantics are the default, certain types are copied by default:" -msgstr "虽然移动语义是默认的，但默认情况下会复制某些类型：" - -#: src/ownership/copy-clone.md:15 -msgid "These types implement the `Copy` trait." -msgstr "这些类型实现了 `Copy` trait。" - -#: src/ownership/copy-clone.md:17 -msgid "You can opt-in your own types to use copy semantics:" -msgstr "你可以选择自己的类型来使用复制语义：" - -#: src/ownership/copy-clone.md:32 -msgid "After the assignment, both `p1` and `p2` own their own data." -msgstr "赋值之后，`p1` 和 `p2` 都拥有自己的数据。" - -#: src/ownership/copy-clone.md:33 -msgid "We can also use `p1.clone()` to explicitly copy the data." -msgstr "我们还可以使用 `p1.clone()` 显式复制数据。" +"`if-let`s can pile up, as shown. The `let-else` construct supports " +"flattening this nested code. Rewrite the awkward version for students, so " +"they can see the transformation." +msgstr "" -#: src/ownership/copy-clone.md:37 -msgid "Copying and cloning are not the same thing:" -msgstr "复制和克隆是两码事：" +#: src/pattern-matching/let-control-flow.md:102 +msgid "The rewritten version is:" +msgstr "" -#: src/ownership/copy-clone.md:39 -msgid "" -"Copying refers to bitwise copies of memory regions and does not work on " -"arbitrary objects." -msgstr "复制是指内存区域的按位复制，不适用于任意对象。" +#: src/pattern-matching/let-control-flow.md:122 +#, fuzzy +msgid "while-let" +msgstr "`while let` 循环" -#: src/ownership/copy-clone.md:40 +#: src/pattern-matching/let-control-flow.md:124 msgid "" -"Copying does not allow for custom logic (unlike copy constructors in C++)." -msgstr "复制不允许自定义逻辑（不同于 C++ 中的复制构造函数）。" +"Point out that the `while let` loop will keep going as long as the value " +"matches the pattern." +msgstr "指出只要值与模式匹配，`while let` 循环就会一直进行下去。" -#: src/ownership/copy-clone.md:41 +#: src/pattern-matching/let-control-flow.md:126 +#, fuzzy msgid "" -"Cloning is a more general operation and also allows for custom behavior by " -"implementing the `Clone` trait." -msgstr "克隆是一种更通用的操作，也允许通过实现 `Clone` trait 来自定义行为。" - -#: src/ownership/copy-clone.md:42 -msgid "Copying does not work on types that implement the `Drop` trait." -msgstr "复制不适用于实现 `Drop` trait 的类型。" +"You could rewrite the `while let` loop as an infinite loop with an if " +"statement that breaks when there is no value to unwrap for `name.pop()`. The " +"`while let` provides syntactic sugar for the above scenario." +msgstr "" +"你可以使用 if 语句将 `while let` 循环重写为无限循环，当 `iter.next()` 没有值" +"可以解封时中断。`while let` 为上述情况提供了语法糖。" -#: src/ownership/copy-clone.md:44 src/ownership/lifetimes-function-calls.md:30 -msgid "In the above example, try the following:" -msgstr "在上述示例中，请尝试以下操作：" +#: src/pattern-matching/exercise.md:3 +msgid "Let's write a simple recursive evaluator for arithmetic expressions." +msgstr "" -#: src/ownership/copy-clone.md:46 +#: src/pattern-matching/exercise.md:5 msgid "" -"Add a `String` field to `struct Point`. It will not compile because `String` " -"is not a `Copy` type." +"The `Box` type here is a smart pointer, and will be covered in detail later " +"in the course. An expression can be \"boxed\" with `Box::new` as seen in the " +"tests. To evaluate a boxed expression, use the deref operator (`*`) to " +"\"unbox\" it: `eval(*boxed_expr)`." msgstr "" -"在 `struct Point` 中添加 `String` 字段。由于 `String` 不属于 `Copy` 类型，因" -"此无法编译。" -#: src/ownership/copy-clone.md:47 +#: src/pattern-matching/exercise.md:10 msgid "" -"Remove `Copy` from the `derive` attribute. The compiler error is now in the " -"`println!` for `p1`." +"Some expressions cannot be evaluated and will return an error. The standard " +"[`Result`](https://doc.rust-lang.org/std/result/enum.Result." +"html) type is an enum that represents either a successful value " +"(`Ok(Value)`) or an error (`Err(String)`). We will cover this type in detail " +"later." msgstr "" -"从 `derive` 属性中移除 `Copy`。现在，编译器错误位于 `p1`的 `println!` 中。" - -#: src/ownership/copy-clone.md:48 -msgid "Show that it works if you clone `p1` instead." -msgstr "指出如果你改为克隆 `p1`，则可按预期运行。" -#: src/ownership/copy-clone.md:50 +#: src/pattern-matching/exercise.md:15 msgid "" -"If students ask about `derive`, it is sufficient to say that this is a way " -"to generate code in Rust at compile time. In this case the default " -"implementations of `Copy` and `Clone` traits are generated." +"Copy and paste the code into the Rust playground, and begin implementing " +"`eval`. The final product should pass the tests. It may be helpful to use " +"`todo!()` and get the tests to pass one-by-one. You can also skip a test " +"temporarily with `#[ignore]`:" msgstr "" -"如果学员问起 `derive`，只需说这是一种 在编译时生成 Rust 代码的方法。在这种情" -"况下，系统会生成 `Copy` 和 `Clone` trait 的默认实现。" -#: src/ownership/borrowing.md:3 +#: src/pattern-matching/exercise.md:26 msgid "" -"Instead of transferring ownership when calling a function, you can let a " -"function _borrow_ the value:" -msgstr "调用函数时，你可以让 函数“借用”值，而不是转移所有权：" +"If you finish early, try writing a test that results in division by zero or " +"integer overflow. How could you handle this with `Result` instead of a panic?" +msgstr "" -#: src/ownership/borrowing.md:23 -msgid "The `add` function _borrows_ two points and returns a new point." -msgstr "`add` 函数“借用”两个点并返回一个新点。" +#: src/pattern-matching/exercise.md:30 src/pattern-matching/solution.md:4 +msgid "/// An operation to perform on two subexpressions.\n" +msgstr "" -#: src/ownership/borrowing.md:24 -msgid "The caller retains ownership of the inputs." -msgstr "调用方会保留输入的所有权。" +#: src/pattern-matching/exercise.md:38 src/pattern-matching/solution.md:12 +msgid "/// An expression, in tree form.\n" +msgstr "" -#: src/ownership/borrowing.md:28 -msgid "Notes on stack returns:" -msgstr "关于栈返回的说明：" +#: src/pattern-matching/exercise.md:42 src/pattern-matching/solution.md:16 +msgid "/// An operation on two subexpressions.\n" +msgstr "" -#: src/ownership/borrowing.md:29 -#, fuzzy -msgid "" -"Demonstrate that the return from `add` is cheap because the compiler can " -"eliminate the copy operation. Change the above code to print stack addresses " -"and run it on the [Playground](https://play.rust-lang.org/) or look at the " -"assembly in [Godbolt](https://rust.godbolt.org/). In the \"DEBUG\" " -"optimization level, the addresses should change, while they stay the same " -"when changing to the \"RELEASE\" setting:" +#: src/pattern-matching/exercise.md:45 src/pattern-matching/solution.md:19 +msgid "/// A literal value\n" msgstr "" -"证明从 `add` 返回的开销很低，因为编译器可以消除复制操作。更改上述代码以输出栈" -"地址，并在 [Playground](https://play.rust-lang.org/) 上运行它。在“调试”优化级" -"别中，地址应发生变化，而在改成“发布”设置时保持不变：" -#: src/ownership/borrowing.md:50 -msgid "The Rust compiler can do return value optimization (RVO)." -msgstr "Rust 编译器能够执行返回值优化 (RVO)。" +#: src/pattern-matching/exercise.md:104 src/pattern-matching/solution.md:40 +#: src/pattern-matching/solution.md:102 +msgid "\"division by zero\"" +msgstr "" -#: src/ownership/borrowing.md:51 -#, fuzzy -msgid "" -"In C++, copy elision has to be defined in the language specification because " -"constructors can have side effects. In Rust, this is not an issue at all. If " -"RVO did not happen, Rust will always perform a simple and efficient `memcpy` " -"copy." +#: src/pattern-matching/solution.md:112 +msgid "\"expr: {:?}\"" msgstr "" -"在 C++ 中，必须在语言规范中定义复制省略，因为构造函数可能会有附带效应。在 " -"Rust 中，这完全不是问题。如果 RVO 未发生，Rust 将始终执行简单且高效的 " -"`memcpy` 复制。" -#: src/ownership/shared-unique-borrows.md:3 -msgid "Rust puts constraints on the ways you can borrow values:" -msgstr "Rust 限制了借用值的方式：" +#: src/methods-and-traits/methods.md:3 +msgid "" +"Rust allows you to associate functions with your new types. You do this with " +"an `impl` block:" +msgstr "Rust 允许您将函数与新类型相关联。您可以使用“impl”块来执行此操作：" -#: src/ownership/shared-unique-borrows.md:5 -msgid "You can have one or more `&T` values at any given time, _or_" -msgstr "在任何给定时间，你都可以有一个或多个 `&T` 值，或者" +#: src/methods-and-traits/methods.md:14 +msgid "// No receiver, a static method\n" +msgstr "" -#: src/ownership/shared-unique-borrows.md:6 -msgid "You can have exactly one `&mut T` value." -msgstr "你可以有且只有一个 `&mut T` 值。" +#: src/methods-and-traits/methods.md:19 +msgid "// Exclusive borrowed read-write access to self\n" +msgstr "" -#: src/ownership/shared-unique-borrows.md:26 -msgid "" -"The above code does not compile because `a` is borrowed as mutable (through " -"`c`) and as immutable (through `b`) at the same time." +#: src/methods-and-traits/methods.md:24 +msgid "// Shared and read-only borrowed access to self\n" msgstr "" -"上述代码无法编译，因为 `a` 同时作为可变值（通过 `c`）和不可变值（通过 `b`）被" -"借用。" -#: src/ownership/shared-unique-borrows.md:27 -msgid "" -"Move the `println!` statement for `b` before the scope that introduces `c` " -"to make the code compile." +#: src/methods-and-traits/methods.md:26 +msgid "\"Recorded {} laps for {}:\"" msgstr "" -"将`b` 的 `println!` 语句移到引入 `c` 的作用域之前，这段代码就可以编译。" -#: src/ownership/shared-unique-borrows.md:28 -msgid "" -"After that change, the compiler realizes that `b` is only ever used before " -"the new mutable borrow of `a` through `c`. This is a feature of the borrow " -"checker called \"non-lexical lifetimes\"." +#: src/methods-and-traits/methods.md:28 +msgid "\"Lap {idx}: {lap} sec\"" msgstr "" -"这样更改后，编译器会发现 `b` 只在通过 `c` 对 `a` 进行新可变借用之前使用过。这" -"是借用检查器的一个功能，名为“非词法作用域生命周期”。" -#: src/ownership/lifetimes.md:3 -msgid "A borrowed value has a _lifetime_:" -msgstr "借用的值是有“生命周期”的：" +#: src/methods-and-traits/methods.md:32 +msgid "// Exclusive ownership of self\n" +msgstr "" -#: src/ownership/lifetimes.md:5 -msgid "The lifetime can be implicit: `add(p1: &Point, p2: &Point) -> Point`." -msgstr "生命周期可以是隐式的：add(p1: &Point, p2: &Point) -> Point\\`。" +#: src/methods-and-traits/methods.md:35 +msgid "\"Race {} is finished, total lap time: {}\"" +msgstr "" -#: src/ownership/lifetimes.md:6 -msgid "Lifetimes can also be explicit: `&'a Point`, `&'document str`." -msgstr "生命周期也可以是显式的：`&'a Point`、`&'document str`。" +#: src/methods-and-traits/methods.md:40 +msgid "\"Monaco Grand Prix\"" +msgstr "" -#: src/ownership/lifetimes.md:7 src/ownership/lifetimes-function-calls.md:24 -msgid "" -"Read `&'a Point` as \"a borrowed `Point` which is valid for at least the " -"lifetime `a`\"." -msgstr "将 `&'a Point` 读取为“借用的 `Point，至少 在 `a\\` 生命周期内有效。" +#: src/methods-and-traits/methods.md:47 +msgid "// race.add_lap(42);\n" +msgstr "" -#: src/ownership/lifetimes.md:9 +#: src/methods-and-traits/methods.md:51 +#, fuzzy msgid "" -"Lifetimes are always inferred by the compiler: you cannot assign a lifetime " -"yourself." -msgstr "生命周期始终由编译器推断出来：你不能自行 分配生命周期。" +"The `self` arguments specify the \"receiver\" - the object the method acts " +"on. There are several common receivers for a method:" +msgstr "" +"上面的“&self”表明该方法以不可变的方式借用了对象。还有其他可能的方法接收器：" -#: src/ownership/lifetimes.md:11 +#: src/methods-and-traits/methods.md:54 msgid "" -"Lifetime annotations create constraints; the compiler verifies that there is " -"a valid solution." -msgstr "生命周期注释会创建约束条件；编译器会验证 是否存在有效的解决方案。" +"`&self`: borrows the object from the caller using a shared and immutable " +"reference. The object can be used again afterwards." +msgstr "" +"“&self”：使用不可变的共享引用从调用方借用对象。之后可以再次使用该对象。" -#: src/ownership/lifetimes.md:13 -#, fuzzy +#: src/methods-and-traits/methods.md:56 msgid "" -"Lifetimes for function arguments and return values must be fully specified, " -"but Rust allows lifetimes to be elided in most cases with [a few simple " -"rules](https://doc.rust-lang.org/nomicon/lifetime-elision.html)." +"`&mut self`: borrows the object from the caller using a unique and mutable " +"reference. The object can be used again afterwards." msgstr "" -"必须完全指定函数参数和返回值的生命周期， 但 Rust 允许在大多数情况下通过\\[一" -"些简单的 规则\\](https://doc.rust-lang.org/nomicon/lifetime-elision.html）来" -"省略此操作。" +"“&mut self”：使用唯一的可变引用从调用方借用对象。之后可以再次使用该对象。" -#: src/ownership/lifetimes-function-calls.md:3 +#: src/methods-and-traits/methods.md:58 msgid "" -"In addition to borrowing its arguments, a function can return a borrowed " -"value:" -msgstr "除了借用其参数之外，函数还可以返回借用的值：" - -#: src/ownership/lifetimes-function-calls.md:22 -msgid "`'a` is a generic parameter, it is inferred by the compiler." -msgstr "`'a` 是一个泛型形参，由编译器推断出来。" +"`self`: takes ownership of the object and moves it away from the caller. The " +"method becomes the owner of the object. The object will be dropped " +"(deallocated) when the method returns, unless its ownership is explicitly " +"transmitted. Complete ownership does not automatically mean mutability." +msgstr "" +"“self”：获取对象的所有权并将其从调用方移出。该方法会成为对象的所有者。除非明" +"确转移对象的所有权，否则在该方法返回时，对象将被丢弃（取消分配）。具备完全所" +"有权，不自动等同于具备可变性。" -#: src/ownership/lifetimes-function-calls.md:23 -msgid "Lifetimes start with `'` and `'a` is a typical default name." -msgstr "以 `'` 和 `'a` 开头的生命周期是典型的默认名称。" +#: src/methods-and-traits/methods.md:62 +#, fuzzy +msgid "`mut self`: same as above, but the method can mutate the object." +msgstr "`mut self`：同上，但该方法可以改变对象。" -#: src/ownership/lifetimes-function-calls.md:26 +#: src/methods-and-traits/methods.md:63 msgid "" -"The _at least_ part is important when parameters are in different scopes." -msgstr "当参数在不同的作用域时，“至少”部分至关重要。" +"No receiver: this becomes a static method on the struct. Typically used to " +"create constructors which are called `new` by convention." +msgstr "" +"无接收器：这将变为结构体上的静态方法。通常用于创建构造函数，按惯例被称" +"为“new”。" -#: src/ownership/lifetimes-function-calls.md:32 -msgid "" -"Move the declaration of `p2` and `p3` into a new scope (`{ ... }`), " -"resulting in the following code:" -msgstr "将 `p2` 和 `p3` 的声明移至新作用域 (`{ ... }`)，以产生以下代码：" +#: src/methods-and-traits/methods.md:70 +msgid "It can be helpful to introduce methods by comparing them to functions." +msgstr "引入方法时，将方法与函数进行比较会很有帮助。" -#: src/ownership/lifetimes-function-calls.md:52 -msgid "Note how this does not compile since `p3` outlives `p2`." -msgstr "请注意：由于 `p3` 的生命周期比 `p2` 长，因此无法编译。" +#: src/methods-and-traits/methods.md:71 +msgid "" +"Methods are called on an instance of a type (such as a struct or enum), the " +"first parameter represents the instance as `self`." +msgstr "" +"在某种类型（例如结构体或枚举）的实例上调用方法，第一个参数将该实例表示" +"为“self”。" -#: src/ownership/lifetimes-function-calls.md:54 +#: src/methods-and-traits/methods.md:73 msgid "" -"Reset the workspace and change the function signature to `fn left_most<'a, " -"'b>(p1: &'a Point, p2: &'a Point) -> &'b Point`. This will not compile " -"because the relationship between the lifetimes `'a` and `'b` is unclear." +"Developers may choose to use methods to take advantage of method receiver " +"syntax and to help keep them more organized. By using methods we can keep " +"all the implementation code in one predictable place." msgstr "" -"重置工作区，然后将函数签名更改为 `fn left_most<'a, 'b>(p1: &'a Point, p2: " -"&'a Point) -> &'b Point`。这不会被编译，因为 `'a` 和 `'b` 生命周期之间的关系" -"不明确。" +"开发者可能会选择使用方法，以便利用方法接收器语法并让方法更有条理。通过使用方" +"法，我们可以将所有实现代码保存在一个可预测的位置。" -#: src/ownership/lifetimes-function-calls.md:55 -msgid "Another way to explain it:" -msgstr "另一种解释方式：" +#: src/methods-and-traits/methods.md:76 +msgid "Point out the use of the keyword `self`, a method receiver." +msgstr "指出关键字“self”的用法，它是一种方法接收器。" -#: src/ownership/lifetimes-function-calls.md:56 +#: src/methods-and-traits/methods.md:77 msgid "" -"Two references to two values are borrowed by a function and the function " -"returns another reference." -msgstr "对两个值的两个引用被一个函数借用，该函数返回 另一个引用。" +"Show that it is an abbreviated term for `self: Self` and perhaps show how " +"the struct name could also be used." +msgstr "显示它是“self: Self”的缩写术语，或许要显示结构体名称的可能用法。" -#: src/ownership/lifetimes-function-calls.md:58 +#: src/methods-and-traits/methods.md:79 msgid "" -"It must have come from one of those two inputs (or from a global variable)." -msgstr "它必须是来自这两个输入中的一个（或来自一个全局变量）。" +"Explain that `Self` is a type alias for the type the `impl` block is in and " +"can be used elsewhere in the block." +msgstr "说明“Self”是“impl”块所属类型的类型别名，可以在块中的其他位置使用。" -#: src/ownership/lifetimes-function-calls.md:59 +#: src/methods-and-traits/methods.md:81 msgid "" -"Which one is it? The compiler needs to know, so at the call site the " -"returned reference is not used for longer than a variable from where the " -"reference came from." +"Note how `self` is used like other structs and dot notation can be used to " +"refer to individual fields." msgstr "" -"是哪一个呢？编译器需要知道这一点，因此在调用点，返回的引用 的使用时间不会超过" -"引用的来源中的变量。" +"指出“self”的使用方式与其他结构体一样，并且可以使用点表示法来指代各个字段。" -#: src/ownership/lifetimes-data-structures.md:3 +#: src/methods-and-traits/methods.md:83 +#, fuzzy msgid "" -"If a data type stores borrowed data, it must be annotated with a lifetime:" -msgstr "如果数据类型存储了借用的数据，则必须对其添加生命周期注释：" +"This might be a good time to demonstrate how the `&self` differs from `self` " +"by trying to run `finish` twice." +msgstr "" +"这可能是演示“&self”和“self”差别的好时机，您只要修改代码并尝试执行 say_hello " +"两次即可。" -#: src/ownership/lifetimes-data-structures.md:5 +#: src/methods-and-traits/methods.md:85 +#, fuzzy msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Highlight<'doc>(&'doc str);\n" -"\n" -"fn erase(text: String) {\n" -" println!(\"Bye {text}!\");\n" -"}\n" -"\n" -"fn main() {\n" -" let text = String::from(\"The quick brown fox jumps over the lazy dog." -"\");\n" -" let fox = Highlight(&text[4..19]);\n" -" let dog = Highlight(&text[35..43]);\n" -" // erase(text);\n" -" println!(\"{fox:?}\");\n" -" println!(\"{dog:?}\");\n" -"}\n" -"```" +"Beyond variants on `self`, there are also [special wrapper types](https://" +"doc.rust-lang.org/reference/special-types-and-traits.html) allowed to be " +"receiver types, such as `Box`." msgstr "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Highlight<'doc>(&'doc str);\n" -"\n" -"fn erase(text: String) {\n" -" println!(\"Bye {text}!\");\n" -"}\n" +"除“self”的变体外，还可以将[特殊封装容器类型](https://doc.rust-lang.org/" +"reference/special-types-and-traits.html)作为接收器类型，例如“Box\n" "\n" -"fn main() {\n" -" let text = String::from(\"The quick brown fox jumps over the lazy dog." -"\");\n" -" let fox = Highlight(&text[4..19]);\n" -" let dog = Highlight(&text[35..43]);\n" -" // erase(text);\n" -" println!(\"{fox:?}\");\n" -" println!(\"{dog:?}\");\n" -"}\n" -"```" +"”。" -#: src/ownership/lifetimes-data-structures.md:25 +#: src/methods-and-traits/traits.md:3 msgid "" -"In the above example, the annotation on `Highlight` enforces that the data " -"underlying the contained `&str` lives at least as long as any instance of " -"`Highlight` that uses that data." +"Rust lets you abstract over types with traits. They're similar to interfaces:" +msgstr "Rust 让您可以依据特征对类型进行抽象化处理。特征与接口类似：" + +#: src/methods-and-traits/traits.md:18 +msgid "\"Oh you're a cutie! What's your name? {}\"" msgstr "" -"在上述示例中，`Highlight` 注释会强制包含 `&str` 的底层数据的生命周期至少与使" -"用该数据的任何 `Highlight` 实例一样长。" -#: src/ownership/lifetimes-data-structures.md:26 -msgid "" -"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " -"the borrow checker throws an error." +#: src/methods-and-traits/traits.md:24 +#: src/methods-and-traits/trait-objects.md:20 +msgid "\"Woof, my name is {}!\"" msgstr "" -"如果 `text` 在 `fox`（或 `dog`）的生命周期结束前被消耗，借用检查器将抛出一个" -"错误。" -#: src/ownership/lifetimes-data-structures.md:27 -msgid "" -"Types with borrowed data force users to hold on to the original data. This " -"can be useful for creating lightweight views, but it generally makes them " -"somewhat harder to use." +#: src/methods-and-traits/traits.md:30 +#: src/methods-and-traits/trait-objects.md:26 +msgid "\"Miau!\"" msgstr "" -"借用数据的类型会迫使用户保留原始数据。这对于创建轻量级视图很有用，但通常会使" -"它们更难使用。" -#: src/ownership/lifetimes-data-structures.md:28 -msgid "When possible, make data structures own their data directly." -msgstr "如有可能，让数据结构直接拥有自己的数据。" +#: src/methods-and-traits/traits.md:36 +#: src/methods-and-traits/trait-objects.md:33 +msgid "\"Fido\"" +msgstr "" -#: src/ownership/lifetimes-data-structures.md:29 +#: src/methods-and-traits/traits.md:45 msgid "" -"Some structs with multiple references inside can have more than one lifetime " -"annotation. This can be necessary if there is a need to describe lifetime " -"relationships between the references themselves, in addition to the lifetime " -"of the struct itself. Those are very advanced use cases." +"A trait defines a number of methods that types must have in order to " +"implement the trait." msgstr "" -"一些包含多个引用的结构可以有多个生命周期注释。除了结构体本身的生命周期之外，" -"如果需要描述引用之间的生命周期关系，则可能需要这样做。这些都是非常高级的用" -"例。" -#: src/structs.md:3 -msgid "Like C and C++, Rust has support for custom structs:" -msgstr "与 C 和 C++ 一样，Rust 支持自定义结构体：" +#: src/methods-and-traits/traits.md:48 +msgid "Traits are implemented in an `impl for { .. }` block." +msgstr "" -#: src/structs.md:5 +#: src/methods-and-traits/traits.md:50 +#, fuzzy msgid "" -"```rust,editable\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"fn main() {\n" -" let mut peter = Person {\n" -" name: String::from(\"Peter\"),\n" -" age: 27,\n" -" };\n" -" println!(\"{} is {} years old\", peter.name, peter.age);\n" -" \n" -" peter.age = 28;\n" -" println!(\"{} is {} years old\", peter.name, peter.age);\n" -" \n" -" let jackie = Person {\n" -" name: String::from(\"Jackie\"),\n" -" ..peter\n" -" };\n" -" println!(\"{} is {} years old\", jackie.name, jackie.age);\n" -"}\n" -"```" +"Traits may specify pre-implemented (provided) methods and methods that users " +"are required to implement themselves. Provided methods can rely on required " +"methods. In this case, `greet` is provided, and relies on `talk`." msgstr "" +"trait 或许可指定预实现（默认）方法，以及用户需要自行实现的方法。具有默认实现" +"的方法可以依赖于必需的方法。" -#: src/structs.md:33 -msgid "Structs work like in C or C++." -msgstr "结构体的运作方式与使用 C 或 C++ 时类似。" - -#: src/structs.md:34 -msgid "Like in C++, and unlike in C, no typedef is needed to define a type." -msgstr "不需要 typedef 即可定义类型，这与使用 C++ 类似，但与使用 C 不同。" +#: src/methods-and-traits/deriving.md:3 +msgid "" +"Supported traits can be automatically implemented for your custom types, as " +"follows:" +msgstr "" -#: src/structs.md:35 -msgid "Unlike in C++, there is no inheritance between structs." -msgstr "与使用 C++ 不同的是，结构体之间没有继承关系。" +#: src/methods-and-traits/deriving.md:15 +msgid "// Default trait adds `default` constructor.\n" +msgstr "" -#: src/structs.md:36 -msgid "" -"Methods are defined in an `impl` block, which we will see in following " -"slides." -msgstr "方法是在“impl”块中进行定义的，我们将在后面的幻灯片中看到。" +#: src/methods-and-traits/deriving.md:16 +msgid "// Clone trait adds `clone` method.\n" +msgstr "" -#: src/structs.md:37 -msgid "" -"This may be a good time to let people know there are different types of " -"structs. " -msgstr "这时可能很适合告诉学员存在不同类型的结构体。" +#: src/methods-and-traits/deriving.md:17 +msgid "\"EldurScrollz\"" +msgstr "" -#: src/structs.md:38 -msgid "" -"Zero-sized structs `e.g., struct Foo;` might be used when implementing a " -"trait on some type but don’t have any data that you want to store in the " -"value itself. " +#: src/methods-and-traits/deriving.md:18 +msgid "// Debug trait adds support for printing with `{:?}`.\n" msgstr "" -"针对某类型实现 trait 时，可能会使用大小为零的结构体 `e.g., struct Foo;`，但其" -"中没有任何您要储存在值本身中的数据。" -#: src/structs.md:39 -msgid "" -"The next slide will introduce Tuple structs, used when the field names are " -"not important." -msgstr "下一张幻灯片将介绍元组结构体，当字段名称不重要时使用。" +#: src/methods-and-traits/deriving.md:19 +msgid "\"{:?} vs. {:?}\"" +msgstr "" -#: src/structs.md:40 +#: src/methods-and-traits/deriving.md:25 msgid "" -"The syntax `..peter` allows us to copy the majority of the fields from the " -"old struct without having to explicitly type it all out. It must always be " -"the last element." +"Derivation is implemented with macros, and many crates provide useful derive " +"macros to add useful functionality. For example, `serde` can derive " +"serialization support for a struct using `#[derive(Serialize)]`." msgstr "" -"通过语法“..peter”，我们可以从旧结构体复制大部分字段，而无需明确地输入所有字" -"段。它必须始终是最后一个元素。" - -#: src/structs/tuple-structs.md:3 -msgid "If the field names are unimportant, you can use a tuple struct:" -msgstr "如果字段名称不重要，您可以使用元组结构体：" -#: src/structs/tuple-structs.md:5 +#: src/methods-and-traits/trait-objects.md:3 msgid "" -"```rust,editable\n" -"struct Point(i32, i32);\n" -"\n" -"fn main() {\n" -" let p = Point(17, 23);\n" -" println!(\"({}, {})\", p.0, p.1);\n" -"}\n" -"```" +"Trait objects allow for values of different types, for instance in a " +"collection:" +msgstr "特征（Trait）对象可接受不同类型的值，举例来说，在集合中会是这样：" + +#: src/methods-and-traits/trait-objects.md:36 +msgid "\"Hello, who are you? {}\"" msgstr "" -#: src/structs/tuple-structs.md:14 -msgid "This is often used for single-field wrappers (called newtypes):" -msgstr "这通常用于单字段封装容器（称为 newtype）：" +#: src/methods-and-traits/trait-objects.md:41 +msgid "Memory layout after allocating `pets`:" +msgstr "以下是分配 `pets` 后的内存布局：" -#: src/structs/tuple-structs.md:16 +#: src/methods-and-traits/trait-objects.md:43 msgid "" -"```rust,editable,compile_fail\n" -"struct PoundsOfForce(f64);\n" -"struct Newtons(f64);\n" -"\n" -"fn compute_thruster_force() -> PoundsOfForce {\n" -" todo!(\"Ask a rocket scientist at NASA\")\n" -"}\n" -"\n" -"fn set_thruster_force(force: Newtons) {\n" -" // ...\n" -"}\n" -"\n" -"fn main() {\n" -" let force = compute_thruster_force();\n" -" set_thruster_force(force);\n" -"}\n" -"\n" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": pets : : +----+----+----+----" +"+ :\n" +": +-----------+-------+ : : +-----+-----+ .->| F | i | d | o " +"| :\n" +": | ptr | o---+---+-----+-->| o o | o o | | +----+----+----+----" +"+ :\n" +": | len | 2 | : : +-|-|-+-|-|-+ " +"`---------. :\n" +": | capacity | 2 | : : | | | | data " +"| :\n" +": +-----------+-------+ : : | | | | +-------+--|-------" +"+ :\n" +": : : | | | '-->| name | o, 4, 4 " +"| :\n" +": : : | | | | age | 5 " +"| :\n" +"`- - - - - - - - - - - - - -' : | | | +-------+----------" +"+ :\n" +" : | | " +"| :\n" +" : | | | " +"vtable :\n" +" : | | | +----------------------" +"+ :\n" +" : | | '---->| \"::talk\" " +"| :\n" +" : | | +----------------------" +"+ :\n" +" : | " +"| :\n" +" : | | " +"data :\n" +" : | | +-------+-------" +"+ :\n" +" : | '-->| lives | 9 " +"| :\n" +" : | +-------+-------" +"+ :\n" +" : " +"| :\n" +" : | " +"vtable :\n" +" : | +----------------------" +"+ :\n" +" : '---->| \"::talk\" " +"| :\n" +" : +----------------------" +"+ :\n" +" : :\n" +" '- - - - - - - - - - - - - - - - - - - - - " +"- -'\n" "```" msgstr "" -#: src/structs/tuple-structs.md:37 +#: src/methods-and-traits/trait-objects.md:77 msgid "" -"Newtypes are a great way to encode additional information about the value in " -"a primitive type, for example:" +"Types that implement a given trait may be of different sizes. This makes it " +"impossible to have things like `Vec` in the example above." msgstr "" -"如需对基元类型中的值的额外信息进行编码，使用 newtype 是一种非常好的方式，例" -"如：" -#: src/structs/tuple-structs.md:38 -msgid "The number is measured in some units: `Newtons` in the example above." -msgstr "数字会以某些单位来衡量：上方示例中为 `Newtons`。" +#: src/methods-and-traits/trait-objects.md:79 +msgid "" +"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " +"implements `Pet`." +msgstr "可通过“dyn Pet”这个方法向编译器告知实现“Pet”的动态大小类型。" -#: src/structs/tuple-structs.md:39 +#: src/methods-and-traits/trait-objects.md:81 msgid "" -"The value passed some validation when it was created, so you no longer have " -"to validate it again at every use: 'PhoneNumber(String)`or`OddNumber(u32)\\`." +"In the example, `pets` is allocated on the stack and the vector data is on " +"the heap. The two vector elements are _fat pointers_:" msgstr "" -"值在创建时已通过一些验证，因此您不再需要在每次使用时都再次验证它：" -"`PhoneNumber(String)` 或 `OddNumber(u32)`。" -#: src/structs/tuple-structs.md:40 +#: src/methods-and-traits/trait-objects.md:83 msgid "" -"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " -"single field in the newtype." +"A fat pointer is a double-width pointer. It has two components: a pointer to " +"the actual object and a pointer to the [virtual method table](https://en." +"wikipedia.org/wiki/Virtual_method_table) (vtable) for the `Pet` " +"implementation of that particular object." msgstr "" -"展示如何通过访问 newtype 中的单个字段，将 `f64` 值添加到 `Newtons` 类型。" -#: src/structs/tuple-structs.md:41 +#: src/methods-and-traits/trait-objects.md:86 msgid "" -"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " -"for instance using booleans as integers." -msgstr "Rust 通常不喜欢不明确的内容，例如自动解封或将布尔值用作整数。" +"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " +"has a `lives` field." +msgstr "" -#: src/structs/tuple-structs.md:42 -msgid "Operator overloading is discussed on Day 3 (generics)." -msgstr "运算符过载在第 3 天（泛型）讨论。" +#: src/methods-and-traits/trait-objects.md:88 +msgid "Compare these outputs in the above example:" +msgstr "比较上述示例中的这些输出：" -#: src/structs/tuple-structs.md:43 -msgid "" -"The example is a subtle reference to the [Mars Climate Orbiter](https://en." -"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." +#: src/methods-and-traits/trait-objects.md:90 +#: src/methods-and-traits/trait-objects.md:91 src/std-traits/closures.md:62 +msgid "\"{} {}\"" msgstr "" -"此示例巧妙地引用了[火星气候探测者号](https://zh.wikipedia.org/wiki/" -"%E7%81%AB%E6%98%9F%E6%B0%A3%E5%80%99%E6%8E%A2%E6%B8%AC%E8%80%85%E8%99%9F) 的" -"失败事故。" - -#: src/structs/field-shorthand.md:3 -msgid "" -"If you already have variables with the right names, then you can create the " -"struct using a shorthand:" -msgstr "如果您已有名称正确的变量，则可以使用简写形式创建结构体：" -#: src/structs/field-shorthand.md:6 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"impl Person {\n" -" fn new(name: String, age: u8) -> Person {\n" -" Person { name, age }\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let peter = Person::new(String::from(\"Peter\"), 27);\n" -" println!(\"{peter:?}\");\n" -"}\n" -"```" +#: src/methods-and-traits/trait-objects.md:92 +#: src/methods-and-traits/trait-objects.md:93 +#: src/methods-and-traits/solution.md:112 src/std-traits/exercise.md:23 +#: src/std-traits/solution.md:29 src/modules/solution.md:78 +#: src/android/build-rules/library.md:44 +#: src/android/interoperability/cpp/rust-bridge.md:17 +#: src/async/pitfalls/cancellation.md:59 +msgid "\"{}\"" msgstr "" -#: src/structs/field-shorthand.md:27 +#: src/methods-and-traits/exercise.md:3 msgid "" -"The `new` function could be written using `Self` as a type, as it is " -"interchangeable with the struct type name" +"Let us design a classical GUI library using our new knowledge of traits and " +"trait objects. We'll only implement the drawing of it (as text) for " +"simplicity." msgstr "" -"在编写“new”函数时可以使用“Self”作为类型，因为它可以与结构体类型名称互换" -#: src/structs/field-shorthand.md:41 -msgid "" -"Implement the `Default` trait for the struct. Define some fields and use the " -"default values for the other fields." -msgstr "为结构体实现“Default”trait。定义一些字段并对其他字段使用默认值。" - -#: src/structs/field-shorthand.md:43 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"impl Default for Person {\n" -" fn default() -> Person {\n" -" Person {\n" -" name: \"Bot\".to_string(),\n" -" age: 0,\n" -" }\n" -" }\n" -"}\n" -"fn create_default() {\n" -" let tmp = Person {\n" -" ..Person::default()\n" -" };\n" -" let tmp = Person {\n" -" name: \"Sam\".to_string(),\n" -" ..Person::default()\n" -" };\n" -"}\n" -"```" -msgstr "" +#: src/methods-and-traits/exercise.md:6 +msgid "We will have a number of widgets in our library:" +msgstr "我们的库中有许多 widget：" -#: src/structs/field-shorthand.md:68 -msgid "Methods are defined in the `impl` block." -msgstr "方法是在“impl”块中进行定义的。" +#: src/methods-and-traits/exercise.md:8 +msgid "`Window`: has a `title` and contains other widgets." +msgstr "“Window”：具有“title”且包含其他 widget。" -#: src/structs/field-shorthand.md:69 +#: src/methods-and-traits/exercise.md:9 msgid "" -"Use struct update syntax to define a new structure using `peter`. Note that " -"the variable `peter` will no longer be accessible afterwards." +"`Button`: has a `label`. In reality, it would also take a callback function " +"to allow the program to do something when the button is clicked but we won't " +"include that since we're only drawing the GUI." msgstr "" -"使用结构体更新语法以利用“peter”定义一个新结构。请注意，之后将无法再访问变" -"量“peter”。" -#: src/structs/field-shorthand.md:70 -msgid "" -"Use `{:#?}` when printing structs to request the `Debug` representation." -msgstr "在输出结构体时，使用“{:#?}”来请求“Debug”表示法。" +#: src/methods-and-traits/exercise.md:12 +msgid "`Label`: has a `label`." +msgstr "“Label”：具有“label”。" -#: src/methods.md:3 -msgid "" -"Rust allows you to associate functions with your new types. You do this with " -"an `impl` block:" -msgstr "Rust 允许您将函数与新类型相关联。您可以使用“impl”块来执行此操作：" +#: src/methods-and-traits/exercise.md:14 +msgid "The widgets will implement a `Widget` trait, see below." +msgstr "这些 widget 将实现“Widget”trait，如下所示。" -#: src/methods.md:6 +#: src/methods-and-traits/exercise.md:16 msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"impl Person {\n" -" fn say_hello(&self) {\n" -" println!(\"Hello, my name is {}\", self.name);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let peter = Person {\n" -" name: String::from(\"Peter\"),\n" -" age: 27,\n" -" };\n" -" peter.say_hello();\n" -"}\n" -"```" +"Copy the code below to , fill in the missing " +"`draw_into` methods so that you implement the `Widget` trait:" msgstr "" +"将以下代码复制到 ，然后填入缺少的“draw_into”方" +"法，以便实现“Widget”trait：" -#: src/methods.md:31 -msgid "It can be helpful to introduce methods by comparing them to functions." -msgstr "引入方法时，将方法与函数进行比较会很有帮助。" - -#: src/methods.md:32 -msgid "" -"Methods are called on an instance of a type (such as a struct or enum), the " -"first parameter represents the instance as `self`." +#: src/methods-and-traits/exercise.md:24 src/methods-and-traits/solution.md:5 +#: src/modules/solution.md:36 +msgid "/// Natural width of `self`.\n" msgstr "" -"在某种类型（例如结构体或枚举）的实例上调用方法，第一个参数将该实例表示" -"为“self”。" -#: src/methods.md:33 -msgid "" -"Developers may choose to use methods to take advantage of method receiver " -"syntax and to help keep them more organized. By using methods we can keep " -"all the implementation code in one predictable place." +#: src/methods-and-traits/exercise.md:27 src/methods-and-traits/solution.md:8 +#: src/modules/solution.md:39 +msgid "/// Draw the widget into a buffer.\n" msgstr "" -"开发者可能会选择使用方法，以便利用方法接收器语法并让方法更有条理。通过使用方" -"法，我们可以将所有实现代码保存在一个可预测的位置。" -#: src/methods.md:34 -msgid "Point out the use of the keyword `self`, a method receiver." -msgstr "指出关键字“self”的用法，它是一种方法接收器。" - -#: src/methods.md:35 -msgid "" -"Show that it is an abbreviated term for `self: Self` and perhaps show how " -"the struct name could also be used." -msgstr "显示它是“self: Self”的缩写术语，或许要显示结构体名称的可能用法。" +#: src/methods-and-traits/exercise.md:30 src/methods-and-traits/solution.md:11 +#: src/modules/solution.md:42 +msgid "/// Draw the widget on standard output.\n" +msgstr "" -#: src/methods.md:36 -msgid "" -"Explain that `Self` is a type alias for the type the `impl` block is in and " -"can be used elsewhere in the block." -msgstr "说明“Self”是“impl”块所属类型的类型别名，可以在块中的其他位置使用。" +#: src/methods-and-traits/exercise.md:34 src/methods-and-traits/solution.md:15 +#: src/modules/solution.md:46 +msgid "\"{buffer}\"" +msgstr "" -#: src/methods.md:37 -msgid "" -"Note how `self` is used like other structs and dot notation can be used to " -"refer to individual fields." +#: src/methods-and-traits/exercise.md:79 +msgid "// TODO: Implement `Widget` for `Label`.\n" msgstr "" -"指出“self”的使用方式与其他结构体一样，并且可以使用点表示法来指代各个字段。" -#: src/methods.md:38 -msgid "" -"This might be a good time to demonstrate how the `&self` differs from `self` " -"by modifying the code and trying to run say_hello twice." +#: src/methods-and-traits/exercise.md:81 +msgid "// TODO: Implement `Widget` for `Button`.\n" msgstr "" -"这可能是演示“&self”和“self”差别的好时机，您只要修改代码并尝试执行 say_hello " -"两次即可。" -#: src/methods.md:39 -msgid "We describe the distinction between method receivers next." -msgstr "下面，我们将介绍方法接收器之间的区别。" +#: src/methods-and-traits/exercise.md:83 +msgid "// TODO: Implement `Widget` for `Window`.\n" +msgstr "" -#: src/methods/receiver.md:3 -msgid "" -"The `&self` above indicates that the method borrows the object immutably. " -"There are other possible receivers for a method:" +#: src/methods-and-traits/exercise.md:87 src/methods-and-traits/solution.md:117 +#: src/modules/solution.md:183 +msgid "\"Rust GUI Demo 1.23\"" msgstr "" -"上面的“&self”表明该方法以不可变的方式借用了对象。还有其他可能的方法接收器：" -#: src/methods/receiver.md:6 -msgid "" -"`&self`: borrows the object from the caller using a shared and immutable " -"reference. The object can be used again afterwards." +#: src/methods-and-traits/exercise.md:88 src/methods-and-traits/solution.md:118 +#: src/modules/solution.md:185 +msgid "\"This is a small text GUI demo.\"" msgstr "" -"“&self”：使用不可变的共享引用从调用方借用对象。之后可以再次使用该对象。" -#: src/methods/receiver.md:8 -msgid "" -"`&mut self`: borrows the object from the caller using a unique and mutable " -"reference. The object can be used again afterwards." +#: src/methods-and-traits/exercise.md:89 src/methods-and-traits/solution.md:119 +#: src/modules/solution.md:186 +msgid "\"Click me!\"" msgstr "" -"“&mut self”：使用唯一的可变引用从调用方借用对象。之后可以再次使用该对象。" -#: src/methods/receiver.md:10 +#: src/methods-and-traits/exercise.md:94 +msgid "The output of the above program can be something simple like this:" +msgstr "上述程序的输出可能非常简单，例如：" + +#: src/methods-and-traits/exercise.md:106 msgid "" -"`self`: takes ownership of the object and moves it away from the caller. The " -"method becomes the owner of the object. The object will be dropped " -"(deallocated) when the method returns, unless its ownership is explicitly " -"transmitted. Complete ownership does not automatically mean mutability." +"If you want to draw aligned text, you can use the [fill/alignment](https://" +"doc.rust-lang.org/std/fmt/index.html#fillalignment) formatting operators. In " +"particular, notice how you can pad with different characters (here a `'/'`) " +"and how you can control alignment:" msgstr "" -"“self”：获取对象的所有权并将其从调用方移出。该方法会成为对象的所有者。除非明" -"确转移对象的所有权，否则在该方法返回时，对象将被丢弃（取消分配）。具备完全所" -"有权，不自动等同于具备可变性。" +"如果要绘制对齐的文本，可以使用[填充/对齐](https://doc.rust-lang.org/std/fmt/" +"index.html#fillalignment)格式设置运算符。需要特别注意的是您填充不同字符（此处" +"是“/”）的方式以及控制对齐的方式：" -#: src/methods/receiver.md:14 -msgid "`mut self`: same as above, but the method can mutate the object. " -msgstr "`mut self`：同上，但该方法可以改变对象。" +#: src/methods-and-traits/exercise.md:114 +msgid "\"left aligned: |{:/`." +#: src/methods-and-traits/exercise.md:116 +msgid "\"right aligned: |{:/>width$}|\"" msgstr "" -"除“self”的变体外，还可以将[特殊封装容器类型](https://doc.rust-lang.org/" -"reference/special-types-and-traits.html)作为接收器类型，例如“Box\n" -"\n" -"”。" -#: src/methods/receiver.md:24 +#: src/methods-and-traits/exercise.md:120 msgid "" -"Consider emphasizing \"shared and immutable\" and \"unique and mutable\". " -"These constraints always come together in Rust due to borrow checker rules, " -"and `self` is no exception. It isn't possible to reference a struct from " -"multiple locations and call a mutating (`&mut self`) method on it." +"Using such alignment tricks, you can for example produce output like this:" +msgstr "使用这些对齐技巧，您可以生成如下的输出内容：" + +#: src/methods-and-traits/solution.md:63 +msgid "// Add 4 paddings for borders\n" msgstr "" -"建议强调“共享且不可变”和“唯一且可变”。由于借用检查器规则的原因，这些约束在 " -"Rust 中总是一起出现，而“self”也不例外。您无法从多个位置引用结构体并对其调用一" -"项改变（“&mut self”）方法。" -#: src/methods/example.md:3 +#: src/methods-and-traits/solution.md:75 src/modules/solution.md:162 msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Race {\n" -" name: String,\n" -" laps: Vec,\n" -"}\n" -"\n" -"impl Race {\n" -" fn new(name: &str) -> Race { // No receiver, a static method\n" -" Race { name: String::from(name), laps: Vec::new() }\n" -" }\n" -"\n" -" fn add_lap(&mut self, lap: i32) { // Exclusive borrowed read-write " -"access to self\n" -" self.laps.push(lap);\n" -" }\n" -"\n" -" fn print_laps(&self) { // Shared and read-only borrowed access to self\n" -" println!(\"Recorded {} laps for {}:\", self.laps.len(), self.name);\n" -" for (idx, lap) in self.laps.iter().enumerate() {\n" -" println!(\"Lap {idx}: {lap} sec\");\n" -" }\n" -" }\n" -"\n" -" fn finish(self) { // Exclusive ownership of self\n" -" let total = self.laps.iter().sum::();\n" -" println!(\"Race {} is finished, total lap time: {}\", self.name, " -"total);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut race = Race::new(\"Monaco Grand Prix\");\n" -" race.add_lap(70);\n" -" race.add_lap(68);\n" -" race.print_laps();\n" -" race.add_lap(71);\n" -" race.print_laps();\n" -" race.finish();\n" -" // race.add_lap(42);\n" -"}\n" -"```" +"// TODO: after learning about error handling, you can change\n" +" // draw_into to return Result<(), std::fmt::Error>. Then use\n" +" // the ?-operator here instead of .unwrap().\n" msgstr "" -#: src/methods/example.md:47 -msgid "All four methods here use a different method receiver." -msgstr "这里的所有四种方法都使用一个不同的方法接收器。" - -#: src/methods/example.md:48 -msgid "" -"You can point out how that changes what the function can do with the " -"variable values and if/how it can be used again in `main`." +#: src/methods-and-traits/solution.md:78 src/methods-and-traits/solution.md:84 +#: src/modules/solution.md:165 src/modules/solution.md:171 +msgid "\"+-{:-` type tomorrow. For " -"now, you just need to know part of its API:" +"Rust supports generics, which lets you abstract algorithms or data " +"structures (such as sorting or a binary tree) over the types used or stored." msgstr "" -"我们明天会更详细地介绍结构体和“Vec\n" -"\n" -"”类型。目前，您只需了解其 API 的一部分：" - -#: src/exercises/day-2/book-library.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut vec = vec![10, 20];\n" -" vec.push(30);\n" -" let midpoint = vec.len() / 2;\n" -" println!(\"middle value: {}\", vec[midpoint]);\n" -" for item in &vec {\n" -" println!(\"item: {item}\");\n" -" }\n" -"}\n" -"```" +"Rust 支持泛型，允许您根据算法（例如排序）中使用的类型对算法进行抽象化处理。" + +#: src/generics/generic-functions.md:7 +msgid "/// Pick `even` or `odd` depending on the value of `n`.\n" msgstr "" -#: src/exercises/day-2/book-library.md:18 -#, fuzzy -msgid "" -"Use this to model a library's book collection. Copy the code below to " -" and update the types to make it compile:" -msgstr "将下面的代码复制到 并实现上述函数：" +#: src/generics/generic-functions.md:17 +msgid "\"picked a number: {:?}\"" +msgstr "" -#: src/exercises/day-2/book-library.md:21 -msgid "" -"```rust,should_panic\n" -"struct Library {\n" -" books: Vec,\n" -"}\n" -"\n" -"struct Book {\n" -" title: String,\n" -" year: u16,\n" -"}\n" -"\n" -"impl Book {\n" -" // This is a constructor, used below.\n" -" fn new(title: &str, year: u16) -> Book {\n" -" Book {\n" -" title: String::from(title),\n" -" year,\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Implement the methods below. Notice how the `self` parameter\n" -"// changes type to indicate the method's required level of ownership\n" -"// over the object:\n" -"//\n" -"// - `&self` for shared read-only access,\n" -"// - `&mut self` for unique and mutable access,\n" -"// - `self` for unique access by value.\n" -"impl Library {\n" -" fn new() -> Library {\n" -" todo!(\"Initialize and return a `Library` value\")\n" -" }\n" -"\n" -" fn len(&self) -> usize {\n" -" todo!(\"Return the length of `self.books`\")\n" -" }\n" -"\n" -" fn is_empty(&self) -> bool {\n" -" todo!(\"Return `true` if `self.books` is empty\")\n" -" }\n" -"\n" -" fn add_book(&mut self, book: Book) {\n" -" todo!(\"Add a new book to `self.books`\")\n" -" }\n" -"\n" -" fn print_books(&self) {\n" -" todo!(\"Iterate over `self.books` and print each book's title and " -"year\")\n" -" }\n" -"\n" -" fn oldest_book(&self) -> Option<&Book> {\n" -" todo!(\"Return a reference to the oldest book (if any)\")\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut library = Library::new();\n" -"\n" -" println!(\n" -" \"The library is empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -"\n" -" println!(\n" -" \"The library is no longer empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.print_books();\n" -"\n" -" match library.oldest_book() {\n" -" Some(book) => println!(\"The oldest book is {}\", book.title),\n" -" None => println!(\"The library is empty!\"),\n" -" }\n" -"\n" -" println!(\"The library has {} books\", library.len());\n" -" library.print_books();\n" -"}\n" -"```" +#: src/generics/generic-functions.md:18 +msgid "\"picked a tuple: {:?}\"" msgstr "" -#: src/exercises/day-2/health-statistics.md:3 -msgid "" -"You're working on implementing a health-monitoring system. As part of that, " -"you need to keep track of users' health statistics." +#: src/generics/generic-functions.md:18 +msgid "\"dog\"" msgstr "" -"你正在实现一个健康监控系统。作为其中的一部分，你需要对用户的健康统计数据进行" -"追踪。" -#: src/exercises/day-2/health-statistics.md:6 -msgid "" -"You'll start with some stubbed functions in an `impl` block as well as a " -"`User` struct definition. Your goal is to implement the stubbed out methods " -"on the `User` `struct` defined in the `impl` block." +#: src/generics/generic-functions.md:18 +msgid "\"cat\"" msgstr "" -"`User` 结构体的定义和 `impl` 块中一些函数的框架已经给出。你的目标是实现在 " -"`impl` 块中定义的 `User` `struct` 的方法。" -#: src/exercises/day-2/health-statistics.md:10 +#: src/generics/generic-functions.md:24 msgid "" -"Copy the code below to and fill in the missing " -"methods:" -msgstr "将以下代码复制到 ，并填充缺失的方法：" +"Rust infers a type for T based on the types of the arguments and return " +"value." +msgstr "" -#: src/exercises/day-2/health-statistics.md:13 +#: src/generics/generic-functions.md:26 msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub struct User {\n" -" name: String,\n" -" age: u32,\n" -" height: f32,\n" -" visit_count: usize,\n" -" last_blood_pressure: Option<(u32, u32)>,\n" -"}\n" -"\n" -"pub struct Measurements {\n" -" height: f32,\n" -" blood_pressure: (u32, u32),\n" -"}\n" -"\n" -"pub struct HealthReport<'a> {\n" -" patient_name: &'a str,\n" -" visit_count: u32,\n" -" height_change: f32,\n" -" blood_pressure_change: Option<(i32, i32)>,\n" -"}\n" -"\n" -"impl User {\n" -" pub fn new(name: String, age: u32, height: f32) -> Self {\n" -" todo!(\"Create a new User instance\")\n" -" }\n" -"\n" -" pub fn name(&self) -> &str {\n" -" todo!(\"Return the user's name\")\n" -" }\n" -"\n" -" pub fn age(&self) -> u32 {\n" -" todo!(\"Return the user's age\")\n" -" }\n" -"\n" -" pub fn height(&self) -> f32 {\n" -" todo!(\"Return the user's height\")\n" -" }\n" -"\n" -" pub fn doctor_visits(&self) -> u32 {\n" -" todo!(\"Return the number of time the user has visited the " -"doctor\")\n" -" }\n" -"\n" -" pub fn set_age(&mut self, new_age: u32) {\n" -" todo!(\"Set the user's age\")\n" -" }\n" -"\n" -" pub fn set_height(&mut self, new_height: f32) {\n" -" todo!(\"Set the user's height\")\n" -" }\n" -"\n" -" pub fn visit_doctor(&mut self, measurements: Measurements) -> " -"HealthReport {\n" -" todo!(\"Update a user's statistics based on measurements from a " -"visit to the doctor\")\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" println!(\"I'm {} and my age is {}\", bob.name(), bob.age());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_height() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.height(), 155.2);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_set_age() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.age(), 32);\n" -" bob.set_age(33);\n" -" assert_eq!(bob.age(), 33);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_visit() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.doctor_visits(), 0);\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (120, 80),\n" -" });\n" -" assert_eq!(report.patient_name, \"Bob\");\n" -" assert_eq!(report.visit_count, 1);\n" -" assert_eq!(report.blood_pressure_change, None);\n" -"\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (115, 76),\n" -" });\n" -"\n" -" assert_eq!(report.visit_count, 2);\n" -" assert_eq!(report.blood_pressure_change, Some((-5, -4)));\n" -"}\n" -"```" +"This is similar to C++ templates, but Rust partially compiles the generic " +"function immediately, so that function must be valid for all types matching " +"the constraints. For example, try modifying `pick` to return `even + odd` if " +"`n == 0`. Even if only the `pick` instantiation with integers is used, Rust " +"still considers it invalid. C++ would let you do this." msgstr "" -#: src/std.md:3 +#: src/generics/generic-functions.md:32 +#, fuzzy msgid "" -"Rust comes with a standard library which helps establish a set of common " -"types used by Rust library and programs. This way, two libraries can work " -"together smoothly because they both use the same `String` type." +"Generic code is turned into non-generic code based on the call sites. This " +"is a zero-cost abstraction: you get exactly the same result as if you had " +"hand-coded the data structures without the abstraction." msgstr "" -"Rust 附带一个标准库，此库有助于建立一个供 Rust 库和程序 使用的常用类型集。这" -"样一来，两个库便可顺畅地搭配运作， 因为它们使用相同的 `String` 类型。" +"这是零成本的抽象化处理：您得到的结果不会受到影响，也就是说，与在没有进行抽象" +"化处理的情况下，对数据结构进行手动编码时的结果一样。" -#: src/std.md:7 -msgid "The common vocabulary types include:" -msgstr "常见的词汇类型包括：" +#: src/generics/generic-data.md:3 +msgid "You can use generics to abstract over the concrete field type:" +msgstr "您可以使用泛型对具体字段类型进行抽象化处理：" -#: src/std.md:9 -msgid "" -"[`Option` and `Result`](std/option-result.md) types: used for optional " -"values and [error handling](error-handling.md)." +#: src/generics/generic-data.md:17 +msgid "// fn set_x(&mut self, x: T)\n" msgstr "" -"[`Option` 和 `Result`](std/option-result.md) 类型：用于可选值和 [错误处理]" -"(error-handling.md)。" -#: src/std.md:12 -msgid "[`String`](std/string.md): the default string type used for owned data." -msgstr "[`String`](std/string.md)：用于自有数据的默认字符串类型。" +#: src/generics/generic-data.md:23 +msgid "\"{integer:?} and {float:?}\"" +msgstr "" -#: src/std.md:14 -msgid "[`Vec`](std/vec.md): a standard extensible vector." -msgstr "[`Vec`](std/vec.md)：标准的可扩展矢量。" +#: src/generics/generic-data.md:24 +msgid "\"coords: {:?}\"" +msgstr "" -#: src/std.md:16 +#: src/generics/generic-data.md:30 msgid "" -"[`HashMap`](std/hashmap.md): a hash map type with a configurable hashing " -"algorithm." -msgstr "[`HashMap`](std/hashmap.md)：采用可配置哈希算法的哈希映射 类型。" - -#: src/std.md:19 -msgid "[`Box`](std/box.md): an owned pointer for heap-allocated data." -msgstr "[`Box`](std/box.md)：适用于堆分配数据的自有指针。" +"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " +"redundant?" +msgstr "" +"\\*问：\\*为什么 `T` 在 `impl Point {}` 中指定了两次？这不是多余的吗？" -#: src/std.md:21 +#: src/generics/generic-data.md:32 msgid "" -"[`Rc`](std/rc.md): a shared reference-counted pointer for heap-allocated " -"data." -msgstr "[`Rc`](std/rc.md)：适用于堆分配数据的共享引用计数指针。" +"This is because it is a generic implementation section for generic type. " +"They are independently generic." +msgstr "这是因为它是泛型类型的泛型实现部分。它们是独立的泛型内容。" -#: src/std.md:25 -msgid "" -"In fact, Rust contains several layers of the Standard Library: `core`, " -"`alloc` and `std`. " -msgstr "Rust 实际上含有多个层级的标准库，分别是 `core`、`alloc` 和 `std`。" +#: src/generics/generic-data.md:34 +msgid "It means these methods are defined for any `T`." +msgstr "这意味着这些方法是针对所有 `T` 定义的。" -#: src/std.md:26 +#: src/generics/generic-data.md:35 +#, fuzzy +msgid "It is possible to write `impl Point { .. }`." +msgstr "可以编写 `impl Point { .. }`。" + +#: src/generics/generic-data.md:36 +msgid "" +"`Point` is still generic and you can use `Point`, but methods in this " +"block will only be available for `Point`." +msgstr "" +"`Point` 依然是一个泛型，并且您可以使用 `Point`，但此块中的方法将仅适用" +"于 `Point`。" + +#: src/generics/generic-data.md:39 +msgid "" +"Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`. Update the " +"code to allow points that have elements of different types, by using two " +"type variables, e.g., `T` and `U`." +msgstr "" + +#: src/generics/trait-bounds.md:3 +msgid "" +"When working with generics, you often want to require the types to implement " +"some trait, so that you can call this trait's methods." +msgstr "" +"使用泛型时，您通常会想要利用类型来实现某些特性， 这样才能调用此特征的方法。" + +#: src/generics/trait-bounds.md:6 +msgid "You can do this with `T: Trait` or `impl Trait`:" +msgstr "您可以使用 `T: Trait` 或 `impl Trait` 执行此操作：" + +#: src/generics/trait-bounds.md:12 +msgid "// struct NotClonable;\n" +msgstr "" + +#: src/generics/trait-bounds.md:18 +msgid "\"{pair:?}\"" +msgstr "" + +#: src/generics/trait-bounds.md:24 +msgid "Try making a `NonClonable` and passing it to `duplicate`." +msgstr "" + +#: src/generics/trait-bounds.md:26 +msgid "When multiple traits are necessary, use `+` to join them." +msgstr "" + +#: src/generics/trait-bounds.md:28 +msgid "Show a `where` clause, students will encounter it when reading code." +msgstr "显示 `where` 子句，学员在阅读代码时会看到它。" + +#: src/generics/trait-bounds.md:39 +msgid "It declutters the function signature if you have many parameters." +msgstr "它会在您有多个形参的情况下整理函数签名。" + +#: src/generics/trait-bounds.md:40 +msgid "It has additional features making it more powerful." +msgstr "它具有额外功能，因此也更强大。" + +#: src/generics/trait-bounds.md:41 +msgid "" +"If someone asks, the extra feature is that the type on the left of \":\" can " +"be arbitrary, like `Option`." +msgstr "" +"如果有人提问，便阐明额外功能是指“:”左侧的类别可为任意值，例如 `Option`。" + +#: src/generics/trait-bounds.md:44 +msgid "" +"Note that Rust does not (yet) support specialization. For example, given the " +"original `duplicate`, it is invalid to add a specialized `duplicate(a: u32)`." +msgstr "" + +#: src/generics/impl-trait.md:3 +msgid "" +"Similar to trait bounds, an `impl Trait` syntax can be used in function " +"arguments and return values:" +msgstr "与特征边界类似，`impl Trait` 语法可以在函数形参 和返回值中使用：" + +#: src/generics/impl-trait.md:7 +msgid "" +"// Syntactic sugar for:\n" +"// fn add_42_millions>(x: T) -> i32 {\n" +msgstr "" + +#: src/generics/impl-trait.md:19 +msgid "\"{many}\"" +msgstr "" + +#: src/generics/impl-trait.md:21 +msgid "\"{many_more}\"" +msgstr "" + +#: src/generics/impl-trait.md:23 +msgid "\"debuggable: {debuggable:?}\"" +msgstr "" + +#: src/generics/impl-trait.md:29 +#, fuzzy +msgid "" +"`impl Trait` allows you to work with types which you cannot name. The " +"meaning of `impl Trait` is a bit different in the different positions." +msgstr "`impl Trait` 的意义因使用位置而略有不同。" + +#: src/generics/impl-trait.md:32 +msgid "" +"For a parameter, `impl Trait` is like an anonymous generic parameter with a " +"trait bound." +msgstr "对形参来说，`impl Trait` 就像是具有特征边界的匿名泛型形参。" + +#: src/generics/impl-trait.md:35 +msgid "" +"For a return type, it means that the return type is some concrete type that " +"implements the trait, without naming the type. This can be useful when you " +"don't want to expose the concrete type in a public API." +msgstr "" +"对返回值类型来说，它则意味着返回值类型就是实现该特征的某具体类型， 无需为该类" +"型命名。如果您不想在公共 API 中公开该具体类型，便可 使用此方法。" + +#: src/generics/impl-trait.md:39 +msgid "" +"Inference is hard in return position. A function returning `impl Foo` picks " +"the concrete type it returns, without writing it out in the source. A " +"function returning a generic type like `collect() -> B` can return any " +"type satisfying `B`, and the caller may need to choose one, such as with " +"`let x: Vec<_> = foo.collect()` or with the turbofish, `foo.collect::" +">()`." +msgstr "" +"在返回位置处进行推断有一定难度。会返回 `impl Foo` 的函数会挑选 自身返回的具体" +"类型，而不必在来源中写出此信息。会返回 泛型类型（例如 `collect() -> B`）的" +"函数则可返回符合 `B` 的任何类型，而调用方可能需要选择一个类型，例如使用 `let " +"x: Vec<_> = foo.collect()` 或使用以下 Turbofish：`foo.collect::>()`。" + +#: src/generics/impl-trait.md:46 +msgid "" +"What is the type of `debuggable`? Try `let debuggable: () = ..` to see what " +"the error message shows." +msgstr "" + +#: src/generics/exercise.md:3 +msgid "" +"In this short exercise, you will implement a generic `min` function that " +"determines the minimum of two values, using a `LessThan` trait." +msgstr "" + +#: src/generics/exercise.md:8 src/generics/solution.md:5 +msgid "/// Return true if self is less than other.\n" +msgstr "" + +#: src/generics/exercise.md:29 +msgid "// TODO: implement the `min` function used in `main`.\n" +msgstr "" + +#: src/generics/exercise.md:33 src/generics/solution.md:36 +msgid "\"Shapiro\"" +msgstr "" + +#: src/generics/exercise.md:34 src/generics/exercise.md:35 +#: src/generics/solution.md:37 src/generics/solution.md:38 +msgid "\"Baumann\"" +msgstr "" + +#: src/std-types.md:7 +msgid "" +"For each of the slides in this section, spend some time reviewing the " +"documentation pages, highlighting some of the more common methods." +msgstr "" + +#: src/std-types/std.md:3 +#, fuzzy +msgid "" +"Rust comes with a standard library which helps establish a set of common " +"types used by Rust libraries and programs. This way, two libraries can work " +"together smoothly because they both use the same `String` type." +msgstr "" +"Rust 附带一个标准库，此库有助于建立一个供 Rust 库和程序 使用的常用类型集。这" +"样一来，两个库便可顺畅地搭配运作， 因为它们使用相同的 `String` 类型。" + +#: src/std-types/std.md:7 +#, fuzzy +msgid "" +"In fact, Rust contains several layers of the Standard Library: `core`, " +"`alloc` and `std`." +msgstr "Rust 实际上含有多个层级的标准库，分别是 `core`、`alloc` 和 `std`。" + +#: src/std-types/std.md:10 +#, fuzzy msgid "" "`core` includes the most basic types and functions that don't depend on " -"`libc`, allocator or even the presence of an operating system. " +"`libc`, allocator or even the presence of an operating system." msgstr "" "`core` 包括最基本的类型与函数，这些类型与函数不依赖于 `libc`、分配器 或是否存" "在操作系统。" -#: src/std.md:28 +#: src/std-types/std.md:12 msgid "" "`alloc` includes types which require a global heap allocator, such as `Vec`, " "`Box` and `Arc`." msgstr "`alloc` 包括需要全局堆分配器的类型，例如 `Vec`、`Box` 和 `Arc`。" -#: src/std.md:29 +#: src/std-types/std.md:14 msgid "" "Embedded Rust applications often only use `core`, and sometimes `alloc`." msgstr "嵌入式 Rust 应用通常只使用 `core`，偶尔会使用 `alloc`。" -#: src/std/option-result.md:1 -msgid "`Option` and `Result`" -msgstr "`Option` 和 `Result`" +#: src/std-types/docs.md:3 +msgid "Rust comes with extensive documentation. For example:" +msgstr "" + +#: src/std-types/docs.md:5 +#, fuzzy +msgid "" +"All of the details about [loops](https://doc.rust-lang.org/stable/reference/" +"expressions/loop-expr.html)." +msgstr "" +"如果你想提前退出循环，请使用 [`break`](https://doc.rust-lang.org/reference/" +"expressions/loop-expr.html#break-expressions)，" + +#: src/std-types/docs.md:7 +msgid "" +"Primitive types like [`u8`](https://doc.rust-lang.org/stable/std/primitive." +"u8.html)." +msgstr "" + +#: src/std-types/docs.md:9 +#, fuzzy +msgid "" +"Standard library types like [`Option`](https://doc.rust-lang.org/stable/std/" +"option/enum.Option.html) or [`BinaryHeap`](https://doc.rust-lang.org/stable/" +"std/collections/struct.BinaryHeap.html)." +msgstr "" +"[“str”](https://doc.rust-lang.org/std/primitive.str.html)和[“String”]" +"(https://doc.rust-lang.org/std/string/struct.String.html)" + +#: src/std-types/docs.md:13 +msgid "In fact, you can document your own code:" +msgstr "" -#: src/std/option-result.md:3 -msgid "The types represent optional data:" -msgstr "这些类型表示可选数据：" +#: src/std-types/docs.md:16 +msgid "" +"/// Determine whether the first argument is divisible by the second " +"argument.\n" +"///\n" +"/// If the second argument is zero, the result is false.\n" +msgstr "" -#: src/std/option-result.md:5 +#: src/std-types/docs.md:27 #, fuzzy msgid "" -"```rust,editable\n" -"fn main() {\n" -" let numbers = vec![10, 20, 30];\n" -" let first: Option<&i8> = numbers.first();\n" -" println!(\"first: {first:?}\");\n" -"\n" -" let arr: Result<[i8; 3], Vec> = numbers.try_into();\n" -" println!(\"arr: {arr:?}\");\n" -"}\n" -"```" +"The contents are treated as Markdown. All published Rust library crates are " +"automatically documented at [`docs.rs`](https://docs.rs) using the [rustdoc]" +"(https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is " +"idiomatic to document all public items in an API using this pattern." +msgstr "" +"文档的内容会被当做 Markdown 处理。所有已发布 Rust 库 crate 都会自动被" +"[rustdoc](https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) 工具在 " +"[`docs.rs`](https://docs.rs)存档。 按照这种方式来为 API 中的所有公开项编写文" +"档是 Rust 中惯用的做法。" + +#: src/std-types/docs.md:32 +msgid "" +"To document an item from inside the item (such as inside a module), use `//!" +"` or `/*! .. */`, called \"inner doc comments\":" +msgstr "" + +#: src/std-types/docs.md:36 +msgid "" +"//! This module contains functionality relating to divisibility of " +"integers.\n" +msgstr "" + +#: src/std-types/docs.md:41 +#, fuzzy +msgid "" +"Show students the generated docs for the `rand` crate at ." +msgstr "" +"向学生展示在 [`docs.rs/rand`](https://docs.rs/rand) 中为 `rand` crate 生成的" +"文档。" + +#: src/std-types/option.md:1 +#, fuzzy +msgid "Option" +msgstr "异常" + +#: src/std-types/option.md:3 +msgid "" +"We have already seen some use of `Option`. It stores either a value of " +"type `T` or nothing. For example, [`String::find`](https://doc.rust-lang.org/" +"stable/std/string/struct.String.html#method.find) returns an `Option`." +msgstr "" + +#: src/std-types/option.md:10 +msgid "\"Löwe 老虎 Léopard Gepardi\"" +msgstr "" + +#: src/std-types/option.md:11 +msgid "'é'" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" let mut iter = v.into_iter();\n" -"\n" -" while let Some(x) = iter.next() {\n" -" println!(\"x: {x}\");\n" -" }\n" -"}\n" -"```" -#: src/std/option-result.md:18 -msgid "`Option` and `Result` are widely used not just in the standard library." +#: src/std-types/option.md:12 src/std-types/option.md:15 +msgid "\"find returned {position:?}\"" +msgstr "" + +#: src/std-types/option.md:14 +msgid "'Z'" +msgstr "" + +#: src/std-types/option.md:16 +msgid "\"Character not found\"" +msgstr "" + +#: src/std-types/option.md:22 +#, fuzzy +msgid "`Option` is widely used, not just in the standard library." msgstr "`Option` 和 `Result` 的使用范围很广，不局限于标准库。" -#: src/std/option-result.md:19 -msgid "`Option<&T>` has zero space overhead compared to `&T`." -msgstr "相较于 `&T`，`Option<&T>` 的空间开销为零。" +#: src/std-types/option.md:23 +msgid "" +"`unwrap` will return the value in an `Option`, or panic. `expect` is similar " +"but takes an error message." +msgstr "" + +#: src/std-types/option.md:25 +msgid "" +"You can panic on None, but you can't \"accidentally\" forget to check for " +"None." +msgstr "" -#: src/std/option-result.md:20 +#: src/std-types/option.md:27 msgid "" -"`Result` is the standard type to implement error handling as we will see on " -"Day 3." -msgstr "`Result` 是用于实现错误处理的标准类型，我们将在第 3 天的课程中介绍。" +"It's common to `unwrap`/`expect` all over the place when hacking something " +"together, but production code typically handles `None` in a nicer fashion." +msgstr "" -#: src/std/option-result.md:21 +#: src/std-types/option.md:29 msgid "" -"`try_into` attempts to convert the vector into a fixed-sized array. This can " -"fail:" +"The niche optimization means that `Option` often has the same size in " +"memory as `T`." +msgstr "" + +#: src/std-types/result.md:1 +msgid "Result" +msgstr "" + +#: src/std-types/result.md:3 +msgid "" +"`Result` is similar to `Option`, but indicates the success or failure of an " +"operation, each with a different type. This is similar to the `Res` defined " +"in the expression exercise, but generic: `Result` where `T` is used in " +"the `Ok` variant and `E` appears in the `Err` variant." +msgstr "" + +#: src/std-types/result.md:13 +msgid "\"diary.txt\"" +msgstr "" + +#: src/std-types/result.md:18 +msgid "\"Dear diary: {contents} ({bytes} bytes)\"" +msgstr "" + +#: src/std-types/result.md:20 +msgid "\"Could not read file content\"" +msgstr "" + +#: src/std-types/result.md:24 +msgid "\"The diary could not be opened: {err}\"" msgstr "" -#: src/std/option-result.md:22 +#: src/std-types/result.md:32 msgid "" -"If the vector has the right size, `Result::Ok` is returned with the array." +"As with `Option`, the successful value sits inside of `Result`, forcing the " +"developer to explicitly extract it. This encourages error checking. In the " +"case where an error should never happen, `unwrap()` or `expect()` can be " +"called, and this is a signal of the developer intent too." msgstr "" +"与 `Option` 方法相同，成功值位于 `Result` 方法内部， 开发者必须显示提取成功" +"值。因此，建议进行错误检查。在绝不应出现错误的情况下， 可以调用 `unwrap()` " +"或 `expect()` 方法，这也是一种开发者意向信号。" -#: src/std/option-result.md:23 -msgid "Otherwise, `Result::Err` is returned with the original vector." +#: src/std-types/result.md:36 +#, fuzzy +msgid "" +"`Result` documentation is a recommended read. Not during the course, but it " +"is worth mentioning. It contains a lot of convenience methods and functions " +"that help functional-style programming." msgstr "" +"我们建议阅读 `Result` 文档。虽然课程中不会涉及该文档，但是有必要提到它。 该文" +"档中包含许多便捷的方法和函数，对于函数式编程很有帮助。" + +#: src/std-types/result.md:39 +msgid "" +"`Result` is the standard type to implement error handling as we will see on " +"Day 3." +msgstr "`Result` 是用于实现错误处理的标准类型，我们将在第 3 天的课程中介绍。" + +#: src/std-types/string.md:1 +msgid "String" +msgstr "String" -#: src/std/string.md:3 +#: src/std-types/string.md:3 msgid "" "[`String`](https://doc.rust-lang.org/std/string/struct.String.html) is the " "standard heap-allocated growable UTF-8 string buffer:" @@ -7478,27 +6035,34 @@ msgstr "" "[`String`](https://doc.rust-lang.org/std/string/struct.String.html) 是标准堆" "分配的可扩容 UTF-8 字符串缓冲区：" -#: src/std/string.md:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut s1 = String::new();\n" -" s1.push_str(\"Hello\");\n" -" println!(\"s1: len = {}, capacity = {}\", s1.len(), s1.capacity());\n" -"\n" -" let mut s2 = String::with_capacity(s1.len() + 1);\n" -" s2.push_str(&s1);\n" -" s2.push('!');\n" -" println!(\"s2: len = {}, capacity = {}\", s2.len(), s2.capacity());\n" -"\n" -" let s3 = String::from(\"🇨🇭\");\n" -" println!(\"s3: len = {}, number of chars = {}\", s3.len(),\n" -" s3.chars().count());\n" -"}\n" -"```" +#: src/std-types/string.md:8 src/std-traits/read-and-write.md:35 +#: src/memory-management/review.md:23 src/memory-management/review.md:57 +#: src/testing/unit-tests.md:32 src/testing/unit-tests.md:37 +#: src/concurrency/scoped-threads.md:9 src/concurrency/scoped-threads.md:26 +msgid "\"Hello\"" +msgstr "" + +#: src/std-types/string.md:9 +msgid "\"s1: len = {}, capacity = {}\"" msgstr "" -#: src/std/string.md:22 +#: src/std-types/string.md:13 +msgid "'!'" +msgstr "" + +#: src/std-types/string.md:14 +msgid "\"s2: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/string.md:16 +msgid "\"🇨🇭\"" +msgstr "" + +#: src/std-types/string.md:17 +msgid "\"s3: len = {}, number of chars = {}\"" +msgstr "" + +#: src/std-types/string.md:21 msgid "" "`String` implements [`Deref`](https://doc.rust-lang.org/std/" "string/struct.String.html#deref-methods-str), which means that you can call " @@ -7508,7 +6072,7 @@ msgstr "" "struct.String.html#deref-methods-str)，这意味着您可以 对 `String` 调用所有 " "`str` 方法。" -#: src/std/string.md:30 +#: src/std-types/string.md:29 msgid "" "`String::new` returns a new empty string, use `String::with_capacity` when " "you know how much data you want to push to the string." @@ -7516,7 +6080,7 @@ msgstr "" "“String::new”会返回一个新的空字符串，如果您知道自己想要推送到字符串的数据量，" "请使用“String::with_capacity”。" -#: src/std/string.md:31 +#: src/std-types/string.md:31 msgid "" "`String::len` returns the size of the `String` in bytes (which can be " "different from its length in characters)." @@ -7524,7 +6088,7 @@ msgstr "" "“String::len”会返回“String”的大小（以字节为单位，可能不同于以字符为单位的长" "度）。" -#: src/std/string.md:32 +#: src/std-types/string.md:33 msgid "" "`String::chars` returns an iterator over the actual characters. Note that a " "`char` can be different from what a human will consider a \"character\" due " @@ -7535,13 +6099,13 @@ msgstr "" "docs.rs/unicode-segmentation/latest/unicode_segmentation/struct.Graphemes." "html)，“char”可能与人们所认为的“字符”有所不同。" -#: src/std/string.md:33 +#: src/std-types/string.md:36 msgid "" "When people refer to strings they could either be talking about `&str` or " "`String`." msgstr "当人们提到字符串时，可能是指“&str”或“String”。" -#: src/std/string.md:34 +#: src/std-types/string.md:38 msgid "" "When a type implements `Deref`, the compiler will let you " "transparently call methods from `T`." @@ -7549,7 +6113,13 @@ msgstr "" "当某个类型实现“Deref\\”时，编译器会让您以公开透明方式从“T”调用方" "法。" -#: src/std/string.md:35 +#: src/std-types/string.md:40 +msgid "" +"We haven't discussed the `Deref` trait yet, so at this point this mostly " +"explains the structure of the sidebar in the documentation." +msgstr "" + +#: src/std-types/string.md:42 msgid "" "`String` implements `Deref` which transparently gives it " "access to `str`'s methods." @@ -7557,11 +6127,12 @@ msgstr "" "“String”会实现“Deref\\”，后者可公开透明地授予其访问“str”方法的" "权限。" -#: src/std/string.md:36 -msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1`;." +#: src/std-types/string.md:44 +#, fuzzy +msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1;`." msgstr "写下并比较“let s3 = s1.deref();”和“let s3 = &\\*s1;”。" -#: src/std/string.md:37 +#: src/std-types/string.md:45 msgid "" "`String` is implemented as a wrapper around a vector of bytes, many of the " "operations you see supported on vectors are also supported on `String`, but " @@ -7570,28 +6141,24 @@ msgstr "" "“String”是作为字节矢量的封装容器实现的，矢量上支持的许多操作在“String”上也受" "支持，但有一些额外保证。" -#: src/std/string.md:38 +#: src/std-types/string.md:48 msgid "Compare the different ways to index a `String`:" msgstr "比较将“String”编入索引的不同方式：" -#: src/std/string.md:39 +#: src/std-types/string.md:49 msgid "" "To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, " "out-of-bounds." msgstr "使用“s3.chars().nth(i).unwrap()”转换为字符，其中“i”代表是否出界。" -#: src/std/string.md:40 +#: src/std-types/string.md:51 msgid "" "To a substring by using `s3[0..4]`, where that slice is on character " "boundaries or not." msgstr "" "通过使用“s3\\[0..4\\]”转换为子字符串，其中该 Slice 在或不在字符边界上。" -#: src/std/vec.md:1 -msgid "`Vec`" -msgstr "`Vec`" - -#: src/std/vec.md:3 +#: src/std-types/vec.md:3 msgid "" "[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " "resizable heap-allocated buffer:" @@ -7599,34 +6166,31 @@ msgstr "" "[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) 是标准的可调整大小" "堆分配缓冲区：" -#: src/std/vec.md:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut v1 = Vec::new();\n" -" v1.push(42);\n" -" println!(\"v1: len = {}, capacity = {}\", v1.len(), v1.capacity());\n" -"\n" -" let mut v2 = Vec::with_capacity(v1.len() + 1);\n" -" v2.extend(v1.iter());\n" -" v2.push(9999);\n" -" println!(\"v2: len = {}, capacity = {}\", v2.len(), v2.capacity());\n" -"\n" -" // Canonical macro to initialize a vector with elements.\n" -" let mut v3 = vec![0, 0, 1, 2, 3, 4];\n" -"\n" -" // Retain only the even elements.\n" -" v3.retain(|x| x % 2 == 0);\n" -" println!(\"{v3:?}\");\n" -"\n" -" // Remove consecutive duplicates.\n" -" v3.dedup();\n" -" println!(\"{v3:?}\");\n" -"}\n" -"```" +#: src/std-types/vec.md:9 +msgid "\"v1: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/vec.md:14 +msgid "\"v2: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/vec.md:16 +msgid "// Canonical macro to initialize a vector with elements.\n" +msgstr "" + +#: src/std-types/vec.md:19 +msgid "// Retain only the even elements.\n" +msgstr "" + +#: src/std-types/vec.md:21 src/std-types/vec.md:25 +msgid "\"{v3:?}\"" +msgstr "" + +#: src/std-types/vec.md:23 +msgid "// Remove consecutive duplicates.\n" msgstr "" -#: src/std/vec.md:29 +#: src/std-types/vec.md:29 msgid "" "`Vec` implements [`Deref`](https://doc.rust-lang.org/std/vec/" "struct.Vec.html#deref-methods-%5BT%5D), which means that you can call slice " @@ -7636,16 +6200,17 @@ msgstr "" "struct.Vec.html#deref-methods-%5BT%5D)，这意味着您可以对 `Vec` 调用 slice 方" "法。" -#: src/std/vec.md:37 +#: src/std-types/vec.md:37 +#, fuzzy msgid "" "`Vec` is a type of collection, along with `String` and `HashMap`. The data " "it contains is stored on the heap. This means the amount of data doesn't " -"need to be known at compile time. It can grow or shrink at runtime." +"need to be known at compile time. It can grow or shrink at runtime." msgstr "" "“Vec”以及“String”和“HashMap”都是一种集合。它包含的数据会存储在堆上。这意味着" "在编译时不需要知道数据量。它可以在运行时增大或缩小。" -#: src/std/vec.md:40 +#: src/std-types/vec.md:40 #, fuzzy msgid "" "Notice how `Vec` is a generic type too, but you don't have to specify `T` " @@ -7657,14 +6222,14 @@ msgstr "" "”也是一种泛型，但您不必明确指定“T”。和往常的 Rust 类别推断一样，系统会在第一" "次“push”调用期间建立“T”。" -#: src/std/vec.md:42 +#: src/std-types/vec.md:43 msgid "" "`vec![...]` is a canonical macro to use instead of `Vec::new()` and it " "supports adding initial elements to the vector." msgstr "" "“vec![...\\]”是用来代替“Vec::new()”的规范化宏，它支持向矢量添加初始元素。" -#: src/std/vec.md:44 +#: src/std-types/vec.md:45 msgid "" "To index the vector you use `[` `]`, but they will panic if out of bounds. " "Alternatively, using `get` will return an `Option`. The `pop` function will " @@ -7673,64 +6238,63 @@ msgstr "" "如需将矢量编入索引，您可以使用“\\[’ ‘\\]”方法，但如果超出边界，矢量将会 " "panic。此外，使用“get”将返回“Option”。“pop”函数会移除最后一个元素。" -#: src/std/vec.md:46 +#: src/std-types/vec.md:48 msgid "" -"Show iterating over a vector and mutating the value: `for e in &mut v { *e " -"+= 50; }`" -msgstr "介绍如何迭代矢量并更改它的值：“for e in &mut v { \\*e += 50; }”" - -#: src/std/hashmap.md:1 src/bare-metal/no_std.md:46 -msgid "`HashMap`" -msgstr "`HashMap`" +"Slices are covered on day 3. For now, students only need to know that a " +"value of type `Vec` gives access to all of the documented slice methods, too." +msgstr "" -#: src/std/hashmap.md:3 +#: src/std-types/hashmap.md:3 msgid "Standard hash map with protection against HashDoS attacks:" msgstr "标准的哈希映射，内含针对 HashDoS 攻击的保护措施：" -#: src/std/hashmap.md:5 -msgid "" -"```rust,editable\n" -"use std::collections::HashMap;\n" -"\n" -"fn main() {\n" -" let mut page_counts = HashMap::new();\n" -" page_counts.insert(\"Adventures of Huckleberry Finn\".to_string(), " -"207);\n" -" page_counts.insert(\"Grimms' Fairy Tales\".to_string(), 751);\n" -" page_counts.insert(\"Pride and Prejudice\".to_string(), 303);\n" -"\n" -" if !page_counts.contains_key(\"Les Misérables\") {\n" -" println!(\"We know about {} books, but not Les Misérables.\",\n" -" page_counts.len());\n" -" }\n" -"\n" -" for book in [\"Pride and Prejudice\", \"Alice's Adventure in " -"Wonderland\"] {\n" -" match page_counts.get(book) {\n" -" Some(count) => println!(\"{book}: {count} pages\"),\n" -" None => println!(\"{book} is unknown.\")\n" -" }\n" -" }\n" -"\n" -" // Use the .entry() method to insert a value if nothing is found.\n" -" for book in [\"Pride and Prejudice\", \"Alice's Adventure in " -"Wonderland\"] {\n" -" let page_count: &mut i32 = page_counts.entry(book.to_string())." -"or_insert(0);\n" -" *page_count += 1;\n" -" }\n" -"\n" -" println!(\"{page_counts:#?}\");\n" -"}\n" -"```" +#: src/std-types/hashmap.md:10 +msgid "\"Adventures of Huckleberry Finn\"" +msgstr "" + +#: src/std-types/hashmap.md:11 +msgid "\"Grimms' Fairy Tales\"" +msgstr "" + +#: src/std-types/hashmap.md:12 src/std-types/hashmap.md:21 +#: src/std-types/hashmap.md:29 +msgid "\"Pride and Prejudice\"" +msgstr "" + +#: src/std-types/hashmap.md:14 +msgid "\"Les Misérables\"" +msgstr "" + +#: src/std-types/hashmap.md:16 +msgid "\"We know about {} books, but not Les Misérables.\"" +msgstr "" + +#: src/std-types/hashmap.md:21 src/std-types/hashmap.md:29 +msgid "\"Alice's Adventure in Wonderland\"" +msgstr "" + +#: src/std-types/hashmap.md:23 +msgid "\"{book}: {count} pages\"" +msgstr "" + +#: src/std-types/hashmap.md:24 +msgid "\"{book} is unknown.\"" +msgstr "" + +#: src/std-types/hashmap.md:28 +msgid "// Use the .entry() method to insert a value if nothing is found.\n" +msgstr "" + +#: src/std-types/hashmap.md:34 +msgid "\"{page_counts:#?}\"" msgstr "" -#: src/std/hashmap.md:38 +#: src/std-types/hashmap.md:40 msgid "" "`HashMap` is not defined in the prelude and needs to be brought into scope." msgstr "“HashMap”未在序言中定义，因此需要纳入范围中。" -#: src/std/hashmap.md:39 +#: src/std-types/hashmap.md:41 msgid "" "Try the following lines of code. The first line will see if a book is in the " "hashmap and if not return an alternative value. The second line will insert " @@ -7739,23 +6303,19 @@ msgstr "" "请尝试使用以下代码行。第一行将查看图书是否在 hashmap 中；如果不在，则返回替代" "值。如果未找到图书，第二行会在 hashmap 中插入替代值。" -#: src/std/hashmap.md:41 -msgid "" -"```rust,ignore\n" -" let pc1 = page_counts\n" -" .get(\"Harry Potter and the Sorcerer's Stone \")\n" -" .unwrap_or(&336);\n" -" let pc2 = page_counts\n" -" .entry(\"The Hunger Games\".to_string())\n" -" .or_insert(374);\n" -"```" +#: src/std-types/hashmap.md:47 src/std-types/hashmap.md:59 +msgid "\"Harry Potter and the Sorcerer's Stone\"" +msgstr "" + +#: src/std-types/hashmap.md:50 src/std-types/hashmap.md:60 +msgid "\"The Hunger Games\"" msgstr "" -#: src/std/hashmap.md:49 +#: src/std-types/hashmap.md:53 msgid "Unlike `vec!`, there is unfortunately no standard `hashmap!` macro." msgstr "遗憾的是，与“vec!”不同，不存在标准的“hashmap!”宏。" -#: src/std/hashmap.md:50 +#: src/std-types/hashmap.md:54 msgid "" "Although, since Rust 1.56, HashMap implements [`From<[(K, V); N]>`](https://" "doc.rust-lang.org/std/collections/hash_map/struct.HashMap.html#impl-" @@ -7767,23 +6327,13 @@ msgstr "" "From%3C%5B(K,+V);+N%5D%3E-for-HashMap%3CK,+V,+RandomState%3E)，让我们能够轻松" "地从字面量数组初始化哈希映射：" -#: src/std/hashmap.md:52 -msgid "" -"```rust,ignore\n" -" let page_counts = HashMap::from([\n" -" (\"Harry Potter and the Sorcerer's Stone\".to_string(), 336),\n" -" (\"The Hunger Games\".to_string(), 374),\n" -" ]);\n" -"```" -msgstr "" - -#: src/std/hashmap.md:59 +#: src/std-types/hashmap.md:64 msgid "" "Alternatively HashMap can be built from any `Iterator` which yields key-" "value tuples." msgstr "或者，HashMap 也可以基于任何可生成键-值元组的“Iterator”进行构建。" -#: src/std/hashmap.md:60 +#: src/std-types/hashmap.md:66 msgid "" "We are showing `HashMap`, and avoid using `&str` as key to make " "examples easier. Using references in collections can, of course, be done, " @@ -7792,7 +6342,7 @@ msgstr "" "我们要展示“HashMap\\”，避免将“&str”用作键，以便简化示例。当然，" "可以在集合中使用引用，但可能会导致借用检查器出现复杂问题。" -#: src/std/hashmap.md:62 +#: src/std-types/hashmap.md:69 msgid "" "Try removing `to_string()` from the example above and see if it still " "compiles. Where do you think we might run into issues?" @@ -7800,7 +6350,7 @@ msgstr "" "尝试从上述示例中移除“to_string()”，看看它是否仍可编译。您认为我们可能会在哪些" "方面遇到问题？" -#: src/std/hashmap.md:64 +#: src/std-types/hashmap.md:72 msgid "" "This type has several \"method-specific\" return types, such as `std::" "collections::hash_map::Keys`. These types often appear in searches of the " @@ -7811,1792 +6361,1151 @@ msgstr "" "Keys”。这些类型通常会出现在 Rust 文档的搜索结果中。向学员展示此类型的文档，以" "及指向“keys”方法的实用链接。" -#: src/std/box.md:1 -msgid "`Box`" -msgstr "`Box`" - -#: src/std/box.md:3 +#: src/std-types/exercise.md:3 msgid "" -"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " -"pointer to data on the heap:" +"In this exercise you will take a very simple data structure and make it " +"generic. It uses a [`std::collections::HashMap`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html) to keep track of which values " +"have been seen and how many times each one has appeared." msgstr "" -"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) 是指向堆上数据的" -"自有指针：" -#: src/std/box.md:5 +#: src/std-types/exercise.md:9 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let five = Box::new(5);\n" -" println!(\"five: {}\", *five);\n" -"}\n" -"```" +"The initial version of `Counter` is hard coded to only work for `u32` " +"values. Make the struct and its methods generic over the type of value being " +"tracked, that way `Counter` can track any type of value." msgstr "" -#: src/std/box.md:26 +#: src/std-types/exercise.md:13 msgid "" -"`Box` implements `Deref`, which means that you can [call " -"methods from `T` directly on a `Box`](https://doc.rust-lang.org/std/ops/" -"trait.Deref.html#more-on-deref-coercion)." +"If you finish early, try using the [`entry`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html#method.entry) method to halve the " +"number of hash lookups required to implement the `count` method." msgstr "" -"`Box` 会实现 `Deref`，这意味着您可以[直接在 `Box` 上通过 " -"`T` 调用相应方法](https://doc.rust-lang.org/std/ops/trait.Deref.html#more-on-" -"deref-coercion)。" -#: src/std/box.md:34 +#: src/std-types/exercise.md:20 src/std-types/solution.md:6 msgid "" -"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " -"not null. " +"/// Counter counts the number of times each value of type T has been seen.\n" msgstr "" -"在 C++ 中，`Box` 与 `std::unique_ptr` 类似，除了它一定会不为 null 以外。" -#: src/std/box.md:35 -msgid "" -"In the above example, you can even leave out the `*` in the `println!` " -"statement thanks to `Deref`. " +#: src/std-types/exercise.md:27 src/std-types/solution.md:13 +msgid "/// Create a new Counter.\n" msgstr "" -"在上面的示例中，因为有 `Deref`，您甚至可以在 `println!` 语句中省略 `*`。" -#: src/std/box.md:36 -msgid "A `Box` can be useful when you:" -msgstr "在以下情况下，`Box` 可能会很实用：" +#: src/std-types/exercise.md:34 src/std-types/solution.md:18 +msgid "/// Count an occurrence of the given value.\n" +msgstr "" -#: src/std/box.md:37 -msgid "" -"have a type whose size that can't be known at compile time, but the Rust " -"compiler wants to know an exact size." -msgstr "在编译时间遇到无法知晓大小的类型，但 Rust 编译器需要知道确切大小。" +#: src/std-types/exercise.md:43 src/std-types/solution.md:23 +msgid "/// Return the number of times the given value has been seen.\n" +msgstr "" -#: src/std/box.md:38 -msgid "" -"want to transfer ownership of a large amount of data. To avoid copying large " -"amounts of data on the stack, instead store the data on the heap in a `Box` " -"so only the pointer is moved." +#: src/std-types/exercise.md:59 src/std-types/solution.md:39 +msgid "\"saw {} values equal to {}\"" msgstr "" -"想要转让大量数据的所有权。为避免在堆栈上复制大量数据，请改为将数据存储在 " -"`Box` 中的堆上，以便仅移动指针。" -#: src/std/box-recursive.md:1 -msgid "Box with Recursive Data Structures" -msgstr "包含递归数据结构的 Box" +#: src/std-types/exercise.md:63 src/std-types/exercise.md:65 +#: src/std-types/exercise.md:66 src/std-types/solution.md:43 +#: src/std-types/solution.md:45 src/std-types/solution.md:46 +msgid "\"apple\"" +msgstr "" -#: src/std/box-recursive.md:3 -msgid "" -"Recursive data types or data types with dynamic sizes need to use a `Box`:" -msgstr "递归数据类型或具有动态大小的数据类型需要使用 `Box`：" +#: src/std-types/exercise.md:64 src/std-types/solution.md:44 +msgid "\"orange\"" +msgstr "" -#: src/std/box-recursive.md:5 src/std/box-niche.md:3 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"enum List {\n" -" Cons(T, Box>),\n" -" Nil,\n" -"}\n" -"\n" -"fn main() {\n" -" let list: List = List::Cons(1, Box::new(List::Cons(2, Box::" -"new(List::Nil))));\n" -" println!(\"{list:?}\");\n" -"}\n" -"```" +#: src/std-types/exercise.md:66 src/std-types/solution.md:46 +msgid "\"got {} apples\"" msgstr "" -#: src/std/box-recursive.md:18 +#: src/std-traits.md:7 msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"list : : :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " -"| :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": : : :\n" -": : : :\n" -"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"```" +"As with the standard-library types, spend time reviewing the documentation " +"for each trait." msgstr "" -#: src/std/box-recursive.md:33 -#, fuzzy -msgid "" -"If `Box` was not used and we attempted to embed a `List` directly into the " -"`List`, the compiler would not compute a fixed size of the struct in memory " -"(`List` would be of infinite size)." +#: src/std-traits.md:10 +msgid "This section is long. Take a break midway through." msgstr "" -"如果这里未使用 `Box`，且我们曾尝试将一个 `List` 直接嵌入 `List`， 编译器就不" -"会计算内存中结构体的固定大小，结构体看起来会像是无限大。" -#: src/std/box-recursive.md:36 +#: src/std-traits/comparisons.md:3 msgid "" -"`Box` solves this problem as it has the same size as a regular pointer and " -"just points at the next element of the `List` in the heap." +"These traits support comparisons between values. All traits can be derived " +"for types containing fields that implement these traits." msgstr "" -"`Box` 大小与一般指针相同，并且只会指向堆中的下一个 `List` 元素， 因此可以解决" -"这个问题。" -#: src/std/box-recursive.md:39 -msgid "" -"Remove the `Box` in the List definition and show the compiler error. " -"\"Recursive with indirection\" is a hint you might want to use a Box or " -"reference of some kind, instead of storing a value directly." +#: src/std-traits/comparisons.md:6 +msgid "`PartialEq` and `Eq`" msgstr "" -"将 `Box` 从 List 定义中移除后，画面上会显示编译器错误。如果您看到“Recursive " -"with indirection”错误消息，这是在提示您使用 Box 或其他类型的引用，而不是直接" -"储存值。" -#: src/std/box-niche.md:16 +#: src/std-traits/comparisons.md:8 msgid "" -"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This " -"allows the compiler to optimize the memory layout:" +"`PartialEq` is a partial equivalence relation, with required method `eq` and " +"provided method `ne`. The `==` and `!=` operators will call these methods." msgstr "" -"`Box` 不得为空，因此指针始终有效且非 `null`。这样， 编译器就可以优化内存布" -"局：" -#: src/std/box-niche.md:19 +#: src/std-traits/comparisons.md:23 msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"-.\n" -": : : :\n" -": " -"list : : :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " -"| :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": : : :\n" -": : : :\n" -"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"-'\n" -"```" +"`Eq` is a full equivalence relation (reflexive, symmetric, and transitive) " +"and implies `PartialEq`. Functions that require full equivalence will use " +"`Eq` as a trait bound." msgstr "" -#: src/std/rc.md:1 -msgid "`Rc`" -msgstr "`Rc`" +#: src/std-traits/comparisons.md:27 +#, fuzzy +msgid "`PartialOrd` and `Ord`" +msgstr "`Read` 和 `Write`" -#: src/std/rc.md:3 +#: src/std-traits/comparisons.md:29 msgid "" -"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) is a reference-" -"counted shared pointer. Use this when you need to refer to the same data " -"from multiple places:" +"`PartialOrd` defines a partial ordering, with a `partial_cmp` method. It is " +"used to implement the `<`, `<=`, `>=`, and `>` operators." msgstr "" -"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) 是引用计数的共享指" -"针。如果您需要从多个位置 引用相同的数据，请使用此指针：" -#: src/std/rc.md:6 -msgid "" -"```rust,editable\n" -"use std::rc::Rc;\n" -"\n" -"fn main() {\n" -" let mut a = Rc::new(10);\n" -" let mut b = Rc::clone(&a);\n" -"\n" -" println!(\"a: {a}\");\n" -" println!(\"b: {b}\");\n" -"}\n" -"```" +#: src/std-traits/comparisons.md:49 +msgid "`Ord` is a total ordering, with `cmp` returning `Ordering`." msgstr "" -#: src/std/rc.md:18 -#, fuzzy +#: src/std-traits/comparisons.md:53 msgid "" -"See [`Arc`](../concurrency/shared_state/arc.md) and [`Mutex`](https://doc." -"rust-lang.org/std/sync/struct.Mutex.html) if you are in a multi-threaded " -"context." +"`PartialEq` can be implemented between different types, but `Eq` cannot, " +"because it is reflexive:" msgstr "" -"如果您在多线程情境中，请参阅 [`Arc`](https://doc.rust-lang.org/std/sync/" -"struct.Mutex.html)。" -#: src/std/rc.md:19 +#: src/std-traits/comparisons.md:68 msgid "" -"You can _downgrade_ a shared pointer into a [`Weak`](https://doc.rust-lang." -"org/std/rc/struct.Weak.html) pointer to create cycles that will get dropped." +"In practice, it's common to derive these traits, but uncommon to implement " +"them." msgstr "" -"您可以将共享指针_降级_为 [`Weak`](https://doc.rust-lang.org/std/rc/struct." -"Weak.html) 指针， 以便创建之后会被舍弃的循环引用。" - -#: src/std/rc.md:29 -msgid "" -"`Rc`'s count ensures that its contained value is valid for as long as there " -"are references." -msgstr "`Rc` 的计数可确保只要有引用，内含的值就会保持有效。" - -#: src/std/rc.md:30 -msgid "`Rc` in Rust is like `std::shared_ptr` in C++." -msgstr "Rust 中的“Rc”与 C++ 中的“std::shared_ptr”类似。" -#: src/std/rc.md:31 +#: src/std-traits/operators.md:3 msgid "" -"`Rc::clone` is cheap: it creates a pointer to the same allocation and " -"increases the reference count. Does not make a deep clone and can generally " -"be ignored when looking for performance issues in code." +"Operator overloading is implemented via traits in [`std::ops`](https://doc." +"rust-lang.org/std/ops/index.html):" msgstr "" -"`Rc::clone` 的成本很低：这个做法会创建指向相同分配的指针，并增加引用计数，而" -"不会产生深层的克隆，排查代码性能问题时通常可以忽略。" +"运算符重载是通过 [`std::ops`](https://doc.rust-lang.org/std/ops/index.html) " +"中的特征实现的：" -#: src/std/rc.md:32 -msgid "" -"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " -"and returns a mutable reference." +#: src/std-traits/operators.md:23 +msgid "\"{:?} + {:?} = {:?}\"" msgstr "" -"`make_mut` 实际上会在必要时克隆内部值（“clone-on-write”），并返回可变的引用。" -#: src/std/rc.md:33 -msgid "Use `Rc::strong_count` to check the reference count." -msgstr "使用 `Rc::strong_count` 可查看引用计数。" +#: src/std-traits/operators.md:29 src/memory-management/drop.md:47 +msgid "Discussion points:" +msgstr "讨论点：" -#: src/std/rc.md:34 +#: src/std-traits/operators.md:31 #, fuzzy msgid "" -"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " -"cycles that will be dropped properly (likely in combination with `RefCell`, " -"on the next slide)." +"You could implement `Add` for `&Point`. In which situations is that useful?" +msgstr "您可以针对 `&Point` 实现 `Add`。此做法在哪些情况下可派上用场？" + +#: src/std-traits/operators.md:32 +msgid "" +"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " +"the operator is not `Copy`, you should consider overloading the operator for " +"`&T` as well. This avoids unnecessary cloning on the call site." msgstr "" -"`Rc::downgrade` 会向您提供 _弱引用计数_ 对象， 以便创建之后会被适当舍弃的周期" -"（可能会与 `RefCell` 组合）。" +"回答：`Add:add` 会耗用 `self`。如果您的运算符重载对象 （即类型 `T`）不是 " +"`Copy`，建议您也为 `&T` 重载运算符。这可避免调用点上存在不必要的 克隆任务。" -#: src/std/cell.md:1 -msgid "`Cell` and `RefCell`" -msgstr "“Cell”和“RefCell”" +#: src/std-traits/operators.md:35 +msgid "" +"Why is `Output` an associated type? Could it be made a type parameter of the " +"method?" +msgstr "为什么 `Output` 是关联类型？可将它用作该方法的类型形参吗？" -#: src/std/cell.md:3 +#: src/std-traits/operators.md:37 #, fuzzy msgid "" -"[`Cell`](https://doc.rust-lang.org/std/cell/struct.Cell.html) and [`RefCell`]" -"(https://doc.rust-lang.org/std/cell/struct.RefCell.html) implement what Rust " -"calls _interior mutability:_ mutation of values in an immutable context." +"Short answer: Function type parameters are controlled by the caller, but " +"associated types (like `Output`) are controlled by the implementer of a " +"trait." msgstr "" -"您可以使用 [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 " -"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html) 对 `u8` 来源" -"进行抽象化处理：" +"简答：函数类型形参是由调用方控管，但 `Output` 这类关联类型则由特征实现人员 控" +"管。" -#: src/std/cell.md:8 +#: src/std-traits/operators.md:40 msgid "" -"`Cell` is typically used for simple types, as it requires copying or moving " -"values. More complex interior types typically use `RefCell`, which tracks " -"shared and exclusive references at runtime and panics if they are misused." +"You could implement `Add` for two different types, e.g. `impl Add<(i32, " +"i32)> for Point` would add a tuple to a `Point`." msgstr "" -"“Cell”通常用于简单类型，因为它需要复制或移动值。更复杂的内部类型通常使" -"用“RefCell”，它会在运行时跟踪已共享和专有的引用，并在这些引用被滥用时 panic。" +"您可以针对两种不同类型实现 `Add`，例如， `impl Add<(i32, i32)> for Point` 会" +"向 `Point` 中添加元组。" -#: src/std/cell.md:12 +#: src/std-traits/from-and-into.md:3 msgid "" -"```rust,editable\n" -"use std::cell::RefCell;\n" -"use std::rc::Rc;\n" -"\n" -"#[derive(Debug, Default)]\n" -"struct Node {\n" -" value: i64,\n" -" children: Vec>>,\n" -"}\n" -"\n" -"impl Node {\n" -" fn new(value: i64) -> Rc> {\n" -" Rc::new(RefCell::new(Node { value, ..Node::default() }))\n" -" }\n" -"\n" -" fn sum(&self) -> i64 {\n" -" self.value + self.children.iter().map(|c| c.borrow().sum()).sum::" -"()\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let root = Node::new(1);\n" -" root.borrow_mut().children.push(Node::new(5));\n" -" let subtree = Node::new(10);\n" -" subtree.borrow_mut().children.push(Node::new(11));\n" -" subtree.borrow_mut().children.push(Node::new(12));\n" -" root.borrow_mut().children.push(subtree);\n" -"\n" -" println!(\"graph: {root:#?}\");\n" -" println!(\"graph sum: {}\", root.borrow().sum());\n" -"}\n" -"```" +"Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." +"html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " +"facilitate type conversions:" msgstr "" +"类型会实现 [`From`](https://doc.rust-lang.org/std/convert/trait.From.html) " +"和 [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) 以加快类型" +"转换：" -#: src/std/cell.md:47 -msgid "" -"If we were using `Cell` instead of `RefCell` in this example, we would have " -"to move the `Node` out of the `Rc` to push children, then move it back in. " -"This is safe because there's always one, un-referenced value in the cell, " -"but it's not ergonomic." +#: src/std-traits/from-and-into.md:11 src/std-traits/from-and-into.md:23 +msgid "\"{s}, {addr}, {one}, {bigger}\"" msgstr "" -"在此示例中，如果我们使用的是“Cell”而非“RefCell”，则必须将“Node”从“Rc”中移出以" -"推送子项，然后再将其移回原位。这是安全的做法，因为单元格中总是有一个未引用的" -"值，但这不符合人体工程学。" -#: src/std/cell.md:48 +#: src/std-traits/from-and-into.md:15 msgid "" -"To do anything with a Node, you must call a `RefCell` method, usually " -"`borrow` or `borrow_mut`." +"[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) is " +"automatically implemented when [`From`](https://doc.rust-lang.org/std/" +"convert/trait.From.html) is implemented:" msgstr "" -"如需使用 Node 执行任何操作，您必须调用“RefCell”方法，通常" -"为“borrow”或“borrow_mut”。" +"实现 [`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 后，系统" +"会自动实现 [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html)：" -#: src/std/cell.md:49 +#: src/std-traits/from-and-into.md:29 msgid "" -"Demonstrate that reference loops can be created by adding `root` to `subtree." -"children` (don't try to print it!)." -msgstr "" -"演示可以通过向“subtree.children”添加“root”来创建引用循环（不要尝试输出" -"它！）。" +"That's why it is common to only implement `From`, as your type will get " +"`Into` implementation too." +msgstr "这就是为什么通常只需实现 `From`，因为您的类型也会实现 `Into`。" -#: src/std/cell.md:50 +#: src/std-traits/from-and-into.md:31 msgid "" -"To demonstrate a runtime panic, add a `fn inc(&mut self)` that increments " -"`self.value` and calls the same method on its children. This will panic in " -"the presence of the reference loop, with `thread 'main' panicked at 'already " -"borrowed: BorrowMutError'`." +"When declaring a function argument input type like \"anything that can be " +"converted into a `String`\", the rule is opposite, you should use `Into`. " +"Your function will accept types that implement `From` and those that _only_ " +"implement `Into`." msgstr "" -"为了演示运行时 panic，请添加一个会递增“self.value”并以相同方法调用其子项" -"的“fn inc(&mut self)”。如果存在引用循环，就会 panic，并且“thread”“main”会" -"因“already borrowed: BorrowMutError”而 panic。" +"若要声明某个函数实参输入类型（例如“任何可转换成 `String` 的类型”），规则便会" +"相反，此时应使用 `Into`。 您的函数会接受可实现 `From` 的类型，以及那些仅实现 " +"`Into` 的类型。" -#: src/modules.md:3 -msgid "We have seen how `impl` blocks let us namespace functions to a type." -msgstr "我们已看了“impl”块如何让我们将函数的命名空间建为一种类型。" +#: src/std-traits/casting.md:3 +msgid "" +"Rust has no _implicit_ type conversions, but does support explicit casts " +"with `as`. These generally follow C semantics where those are defined." +msgstr "" -#: src/modules.md:5 -msgid "Similarly, `mod` lets us namespace types and functions:" -msgstr "同样，“mod”让我们可为类型和函数建立命名空间：" +#: src/std-traits/casting.md:9 +msgid "\"as u16: {}\"" +msgstr "" -#: src/modules.md:7 -msgid "" -"```rust,editable\n" -"mod foo {\n" -" pub fn do_something() {\n" -" println!(\"In the foo module\");\n" -" }\n" -"}\n" -"\n" -"mod bar {\n" -" pub fn do_something() {\n" -" println!(\"In the bar module\");\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" foo::do_something();\n" -" bar::do_something();\n" -"}\n" -"```" +#: src/std-traits/casting.md:10 +msgid "\"as i16: {}\"" +msgstr "" + +#: src/std-traits/casting.md:11 +msgid "\"as u8: {}\"" msgstr "" -#: src/modules.md:28 +#: src/std-traits/casting.md:15 msgid "" -"Packages provide functionality and include a `Cargo.toml` file that " -"describes how to build a bundle of 1+ crates." +"The results of `as` are _always_ defined in Rust and consistent across " +"platforms. This might not match your intuition for changing sign or casting " +"to a smaller type -- check the docs, and comment for clarity." msgstr "" -"包提供功能，并包含一个描述如何构建包含 1 个以上 crate 的捆绑包的“Cargo." -"toml”文件。" -#: src/modules.md:29 +#: src/std-traits/casting.md:19 msgid "" -"Crates are a tree of modules, where a binary crate creates an executable and " -"a library crate compiles to a library." +"Casting with `as` is a relatively sharp tool that is easy to use " +"incorrectly, and can be a source of subtle bugs as future maintenance work " +"changes the types that are used or the ranges of values in types. Casts are " +"best used only when the intent is to indicate unconditional truncation (e.g. " +"selecting the bottom 32 bits of a `u64` with `as u32`, regardless of what " +"was in the high bits)." msgstr "" -"crate 是一种模块树，其中的二进制 crate 会创建一个可执行文件，而库 crate 会编" -"译为库。" -#: src/modules.md:30 -msgid "Modules define organization, scope, and are the focus of this section." -msgstr "模块定义了组织和范围，并且是本部分的重点。" +#: src/std-traits/casting.md:25 +msgid "" +"For infallible casts (e.g. `u32` to `u64`), prefer using `From` or `Into` " +"over `as` to confirm that the cast is in fact infallible. For fallible " +"casts, `TryFrom` and `TryInto` are available when you want to handle casts " +"that fit differently from those that don't." +msgstr "" -#: src/modules/visibility.md:3 -msgid "Modules are a privacy boundary:" -msgstr "模块是一种隐私边界：" +#: src/std-traits/casting.md:32 +msgid "Consider taking a break after this slide." +msgstr "" -#: src/modules/visibility.md:5 -msgid "Module items are private by default (hides implementation details)." -msgstr "默认情况下，模块项是私有的（隐藏实现详情）。" +#: src/std-traits/casting.md:34 +msgid "" +"`as` is similar to a C++ static cast. Use of `as` in cases where data might " +"be lost is generally discouraged, or at least deserves an explanatory " +"comment." +msgstr "" -#: src/modules/visibility.md:6 -msgid "Parent and sibling items are always visible." -msgstr "父项和同级子项始终可见。" +#: src/std-traits/casting.md:37 +msgid "This is common in casting integers to `usize` for use as an index." +msgstr "" -#: src/modules/visibility.md:7 +#: src/std-traits/read-and-write.md:3 msgid "" -"In other words, if an item is visible in module `foo`, it's visible in all " -"the descendants of `foo`." +"Using [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and " +"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html), you can " +"abstract over `u8` sources:" msgstr "" -"换言之，如果某个项在模块“foo”中可见，那么该项在“foo”的所有后代中均可见。" +"您可以使用 [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 " +"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html) 对 `u8` 来源" +"进行抽象化处理：" -#: src/modules/visibility.md:10 -msgid "" -"```rust,editable\n" -"mod outer {\n" -" fn private() {\n" -" println!(\"outer::private\");\n" -" }\n" -"\n" -" pub fn public() {\n" -" println!(\"outer::public\");\n" -" }\n" -"\n" -" mod inner {\n" -" fn private() {\n" -" println!(\"outer::inner::private\");\n" -" }\n" -"\n" -" pub fn public() {\n" -" println!(\"outer::inner::public\");\n" -" super::private();\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" outer::public();\n" -"}\n" -"```" +#: src/std-traits/read-and-write.md:14 +msgid "b\"foo\\nbar\\nbaz\\n\"" msgstr "" -#: src/modules/visibility.md:39 -msgid "Use the `pub` keyword to make modules public." -msgstr "使用“pub”关键字将模块设为公开。" +#: src/std-traits/read-and-write.md:15 +msgid "\"lines in slice: {}\"" +msgstr "" -#: src/modules/visibility.md:41 -msgid "" -"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " -"of public visibility." -msgstr "此外，您还可以使用高级“pub(...)”说明符来限制公开可见的范围。" +#: src/std-traits/read-and-write.md:18 +msgid "\"lines in file: {}\"" +msgstr "" -#: src/modules/visibility.md:43 +#: src/std-traits/read-and-write.md:23 msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" -"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." +"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " +"you abstract over `u8` sinks:" msgstr "" -"请参阅 [Rust 参考](https://doc.rust-lang.org/reference/visibility-and-" -"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)。" +"您同样可使用 [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) 对 " +"`u8` 接收器进行抽象化处理：" -#: src/modules/visibility.md:44 -msgid "Configuring `pub(crate)` visibility is a common pattern." -msgstr "配置“pub(crate)”可见性是一种常见模式。" +#: src/std-traits/read-and-write.md:30 +msgid "\"\\n\"" +msgstr "" -#: src/modules/visibility.md:45 -msgid "Less commonly, you can give visibility to a specific path." -msgstr "您可以为特定路径授予可见性，这种情况不太常见。" +#: src/std-traits/read-and-write.md:36 src/slices-and-lifetimes/str.md:12 +msgid "\"World\"" +msgstr "" -#: src/modules/visibility.md:46 -msgid "" -"In any case, visibility must be granted to an ancestor module (and all of " -"its descendants)." -msgstr "在任何情况下，都必须向祖先模块（及其所有后代）授予可见性。" +#: src/std-traits/read-and-write.md:37 +msgid "\"Logged: {:?}\"" +msgstr "" -#: src/modules/paths.md:3 -msgid "Paths are resolved as follows:" -msgstr "路径解析如下：" +#: src/std-traits/default.md:1 +msgid "The `Default` Trait" +msgstr "`Default` 特征" -#: src/modules/paths.md:5 -msgid "As a relative path:" -msgstr "作为相对路径：" +#: src/std-traits/default.md:3 +msgid "" +"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " +"produces a default value for a type." +msgstr "" +"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) 特征会" +"为类型生成默认值。" -#: src/modules/paths.md:6 -msgid "`foo` or `self::foo` refers to `foo` in the current module," -msgstr "`foo` 或 `self::foo` 是指当前模块中的 `foo`，" +#: src/std-traits/default.md:18 +msgid "\"John Smith\"" +msgstr "" -#: src/modules/paths.md:7 -msgid "`super::foo` refers to `foo` in the parent module." -msgstr "“super::foo”是指父模块中的“foo”。" +#: src/std-traits/default.md:24 +msgid "\"{default_struct:#?}\"" +msgstr "" -#: src/modules/paths.md:9 -msgid "As an absolute path:" -msgstr "作为绝对路径：" +#: src/std-traits/default.md:27 +msgid "\"Y is set!\"" +msgstr "" -#: src/modules/paths.md:10 -msgid "`crate::foo` refers to `foo` in the root of the current crate," -msgstr "`crate::foo` 是指当前 crate 的根中的 `foo`，" +#: src/std-traits/default.md:28 +msgid "\"{almost_default_struct:#?}\"" +msgstr "" -#: src/modules/paths.md:11 -msgid "`bar::foo` refers to `foo` in the `bar` crate." -msgstr "“bar::foo”是指“bar”crate 中的“foo”。" +#: src/std-traits/default.md:31 src/slices-and-lifetimes/exercise.md:211 +#: src/slices-and-lifetimes/solution.md:214 +msgid "\"{:#?}\"" +msgstr "" -#: src/modules/paths.md:13 +#: src/std-traits/default.md:37 msgid "" -"A module can bring symbols from another module into scope with `use`. You " -"will typically see something like this at the top of each module:" -msgstr "" -"一个模块可以使用“use”将另一个模块的符号全部纳入。您通常在每个模块的顶部会看到" -"如下内容：" +"It can be implemented directly or it can be derived via `#[derive(Default)]`." +msgstr "系统可以直接实现它，也可以通过 `#[derive(Default)]` 派生出它。" -#: src/modules/filesystem.md:3 +#: src/std-traits/default.md:38 +#, fuzzy msgid "" -"Omitting the module content will tell Rust to look for it in another file:" -msgstr "如果省略模块内容，则会指示 Rust 在另一个文件中查找：" +"A derived implementation will produce a value where all fields are set to " +"their default values." +msgstr "派生的实现会生成一个实例，其中字段全都设为其默认值。" -#: src/modules/filesystem.md:9 +#: src/std-traits/default.md:40 +msgid "This means all types in the struct must implement `Default` too." +msgstr "这意味着，该结构体中的所有类型也都必须实现 `Default`。" + +#: src/std-traits/default.md:41 msgid "" -"This tells rust that the `garden` module content is found at `src/garden." -"rs`. Similarly, a `garden::vegetables` module can be found at `src/garden/" -"vegetables.rs`." +"Standard Rust types often implement `Default` with reasonable values (e.g. " +"`0`, `\"\"`, etc)." msgstr "" -"这会告知 Rust 可以在“src/garden.rs”中找到“garden”模块内容。同样，您可以" -"在“src/garden/vegetables.rs”中找到“garden::vegetables”模块。" - -#: src/modules/filesystem.md:12 -msgid "The `crate` root is in:" -msgstr "“crate”根目录位于：" +"标准的 Rust 类型通常会以合理的值（例如 ` 0`\"\" \\``等）实现`Default\\`。" -#: src/modules/filesystem.md:14 -msgid "`src/lib.rs` (for a library crate)" -msgstr "“src/lib.rs”（对于库 crate）" +#: src/std-traits/default.md:43 +#, fuzzy +msgid "The partial struct initialization works nicely with default." +msgstr "部分结构体副本可与默认值完美搭配运作。" -#: src/modules/filesystem.md:15 -msgid "`src/main.rs` (for a binary crate)" -msgstr "“src/main.rs”（对于二进制文件 crate）" +#: src/std-traits/default.md:44 +#, fuzzy +msgid "" +"The Rust standard library is aware that types can implement `Default` and " +"provides convenience methods that use it." +msgstr "Rust 标准库了解类型可能会实现 `Default`，因此提供了便利的使用方式。" -#: src/modules/filesystem.md:17 +#: src/std-traits/default.md:46 +#, fuzzy msgid "" -"Modules defined in files can be documented, too, using \"inner doc " -"comments\". These document the item that contains them -- in this case, a " -"module." +"The `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" +"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" +"with-struct-update-syntax)." msgstr "" -"也可以使用“内部文档注释”对文件中定义的模块进行记录。这些用于记录包含它们的项" -"（在本例中为模块）。" +"“..”语法被称为[结构体更新语法](https://doc.rust-lang.org/book/ch05-01-" +"defining-structs.html#creating-instances-from-other-instances-with-struct-" +"update-syntax)" -#: src/modules/filesystem.md:20 +#: src/std-traits/closures.md:3 msgid "" -"```rust,editable,compile_fail\n" -"//! This module implements the garden, including a highly performant " -"germination\n" -"//! implementation.\n" -"\n" -"// Re-export types from this module.\n" -"pub use seeds::SeedPacket;\n" -"pub use garden::Garden;\n" -"\n" -"/// Sow the given seed packets.\n" -"pub fn sow(seeds: Vec) { todo!() }\n" -"\n" -"/// Harvest the produce in the garden that is ready.\n" -"pub fn harvest(garden: &mut Garden) { todo!() }\n" -"```" +"Closures or lambda expressions have types which cannot be named. However, " +"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." +"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " +"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" msgstr "" +"闭包或 lambda 表达式具有无法命名的类型。不过，它们会 实现特殊的 [`Fn`]" +"(https://doc.rust-lang.org/std/ops/trait.Fn.html)， [`FnMut`](https://doc." +"rust-lang.org/std/ops/trait.FnMut.html) 和 [`FnOnce`](https://doc.rust-lang." +"org/std/ops/trait.FnOnce.html) 特征：" -#: src/modules/filesystem.md:37 -msgid "" -"Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " -"`module.rs`, and this is still a working alternative for editions after 2018." +#: src/std-traits/closures.md:10 +#, fuzzy +msgid "\"Calling function on {input}\"" +msgstr "调用 Unsafe 函数" + +#: src/std-traits/closures.md:16 src/std-traits/closures.md:17 +msgid "\"add_3: {}\"" msgstr "" -"在 Rust 2018 之前的版本中，模块需要位于“module/mod.rs”而非“module.rs”中，对" -"于 2018 年之后的版本而言，这仍是有效的替代方案。" -#: src/modules/filesystem.md:39 -msgid "" -"The main reason to introduce `filename.rs` as alternative to `filename/mod." -"rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." +#: src/std-traits/closures.md:24 src/std-traits/closures.md:25 +msgid "\"accumulate: {}\"" msgstr "" -"引入“filename.rs”来替代“filename/mod.rs”的主要原因是，许多名为“mod.rs”的文件" -"在 IDE 中可能难以区分。" -#: src/modules/filesystem.md:42 -msgid "Deeper nesting can use folders, even if the main module is a file:" -msgstr "即使主模块是文件，更深层的嵌套也可以使用文件夹：" +#: src/std-traits/closures.md:28 +msgid "\"multiply_sum: {}\"" +msgstr "" -#: src/modules/filesystem.md:52 +#: src/std-traits/closures.md:34 msgid "" -"The place rust will look for modules can be changed with a compiler " -"directive:" -msgstr "Rust 寻找模块的位置可通过编译器指令更改：" +"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " +"perhaps captures nothing at all. It can be called multiple times " +"concurrently." +msgstr "" +"`Fn`（例如 `add_3`）既不会耗用也不会修改捕获的值，或许 也不会捕获任何值。它可" +"被并发调用多次。" -#: src/modules/filesystem.md:54 +#: src/std-traits/closures.md:37 msgid "" -"```rust,ignore\n" -"#[path = \"some/path.rs\"]\n" -"mod some_module;\n" -"```" +"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " +"multiple times, but not concurrently." msgstr "" +"`FnMut`（例如 `accumulate`）可能会改变捕获的值。您可以多次调用它， 但不能并发" +"调用它。" -#: src/modules/filesystem.md:59 +#: src/std-traits/closures.md:40 msgid "" -"This is useful, for example, if you would like to place tests for a module " -"in a file named `some_module_test.rs`, similar to the convention in Go." +"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " +"might consume captured values." msgstr "" -"例如，如果您想将某个模块的测试放在名为“some_module_test.rs”的文件中（类似于 " -"Go 中的惯例），这样做很有用。" - -#: src/exercises/day-2/afternoon.md:1 -msgid "Day 2: Afternoon Exercises" -msgstr "第二天下午习题" - -#: src/exercises/day-2/afternoon.md:3 -msgid "The exercises for this afternoon will focus on strings and iterators." -msgstr "今天下午的习题将重点关注字符串（string）和迭代器（iterator）。" +"如果您使用 `FnOnce`（例如 `multiply_sum`），或许只能调用它一次。它可能会耗用 " +"所捕获的值。" -#: src/exercises/day-2/iterators-and-ownership.md:3 +#: src/std-traits/closures.md:43 msgid "" -"The ownership model of Rust affects many APIs. An example of this is the " -"[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " -"[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " -"traits." +"`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " +"I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " +"use an `Fn` wherever an `FnMut` or `FnOnce` is called for." msgstr "" -"Rust 的所有权模式会影响许多 API。例如，[“Iterator”](https://doc.rust-lang." -"org/std/iter/trait.Iterator.html)和[“IntoIterator”](https://doc.rust-lang." -"org/std/iter/trait.IntoIterator.html) trait。" - -#: src/exercises/day-2/iterators-and-ownership.md:8 src/bare-metal/no_std.md:28 -msgid "`Iterator`" -msgstr "“Iterator”" +"`FnMut` 是 `FnOnce` 的子类型。`Fn` 是 `FnMut` 和 `FnOnce` 的子类型。也就是" +"说，您可以在任何 需要调用 `FnOnce` 的地方使用 `FnMut`，还可在任何需要调用 " +"`FnMut` 或 `FnOnce` 的地方 使用 `Fn`。" -#: src/exercises/day-2/iterators-and-ownership.md:10 +#: src/std-traits/closures.md:47 msgid "" -"Traits are like interfaces: they describe behavior (methods) for a type. The " -"`Iterator` trait simply says that you can call `next` until you get `None` " -"back:" +"When you define a function that takes a closure, you should take `FnOnce` if " +"you can (i.e. you call it once), or `FnMut` else, and last `Fn`. This allows " +"the most flexibility for the caller." msgstr "" -"trait 类似于接口：它们描述某类型的行为（方法）。`Iterator` trait 只是告知您可" -"以调用 `next`，直到返回 `None`：" -#: src/exercises/day-2/iterators-and-ownership.md:20 -msgid "You use this trait like this:" -msgstr "您可以按如下方式使用此 trait：" - -#: src/exercises/day-2/iterators-and-ownership.md:22 +#: src/std-traits/closures.md:51 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let v: Vec = vec![10, 20, 30];\n" -" let mut iter = v.iter();\n" -"\n" -" println!(\"v[0]: {:?}\", iter.next());\n" -" println!(\"v[1]: {:?}\", iter.next());\n" -" println!(\"v[2]: {:?}\", iter.next());\n" -" println!(\"No more items: {:?}\", iter.next());\n" -"}\n" -"```" +"In contrast, when you have a closure, the most flexible you can have is `Fn` " +"(it can be passed everywhere), then `FnMut`, and lastly `FnOnce`." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:34 -msgid "What is the type returned by the iterator? Test your answer here:" -msgstr "迭代器返回的类型是什么？请在此测试您的答案：" +#: src/std-traits/closures.md:54 +msgid "" +"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " +"`multiply_sum`), depending on what the closure captures." +msgstr "" +"编译器也会推断 `Copy`（例如针对 `add_3`）和 `Clone`（例如 `multiply_sum`）， " +"具体取决于闭包捕获的数据。" -#: src/exercises/day-2/iterators-and-ownership.md:36 +#: src/std-traits/closures.md:57 msgid "" -"```rust,editable,compile_fail\n" -"fn main() {\n" -" let v: Vec = vec![10, 20, 30];\n" -" let mut iter = v.iter();\n" -"\n" -" let v0: Option<..> = iter.next();\n" -" println!(\"v0: {v0:?}\");\n" -"}\n" -"```" +"By default, closures will capture by reference if they can. The `move` " +"keyword makes them capture by value." msgstr "" +"默认情况下，闭包会依据引用来捕获数据（如果可以的话）。`move` 关键字则可让闭包" +"依据值 来捕获数据。" -#: src/exercises/day-2/iterators-and-ownership.md:46 -msgid "Why is this type used?" -msgstr "为什么要使用此类型？" +#: src/std-traits/closures.md:66 +msgid "\"Hi\"" +msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:48 -msgid "`IntoIterator`" -msgstr "“IntoIterator”" +#: src/std-traits/closures.md:67 +msgid "\"there\"" +msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:50 +#: src/std-traits/exercise.md:3 msgid "" -"The `Iterator` trait tells you how to _iterate_ once you have created an " -"iterator. The related trait `IntoIterator` tells you how to create the " -"iterator:" +"In this example, you will implement the classic [\"ROT13\" cipher](https://" +"en.wikipedia.org/wiki/ROT13). Copy this code to the playground, and " +"implement the missing bits. Only rotate ASCII alphabetic characters, to " +"ensure the result is still valid UTF-8." msgstr "" -"“Iterator”trait会告知您在创建迭代器后如何进行迭代。相关 trait“IntoIterator”会" -"告知您如何创建迭代器：" -#: src/exercises/day-2/iterators-and-ownership.md:62 -msgid "" -"The syntax here means that every implementation of `IntoIterator` must " -"declare two types:" -msgstr "这里的语法表示，“IntoIterator”的每个实现都必须声明两种类型：" +#: src/std-traits/exercise.md:15 +msgid "// Implement the `Read` trait for `RotDecoder`.\n" +msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:65 -msgid "`Item`: the type we iterate over, such as `i8`," -msgstr "`Item`：我们迭代的类型，例如 `i8`，" +#: src/std-traits/exercise.md:20 src/std-traits/exercise.md:33 +#: src/std-traits/solution.md:26 src/std-traits/solution.md:39 +msgid "\"Gb trg gb gur bgure fvqr!\"" +msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:66 -msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." -msgstr "“IntoIter”：“into_iter”方法返回的“Iterator”类型。" +#: src/std-traits/exercise.md:36 src/std-traits/solution.md:42 +msgid "\"To get to the other side!\"" +msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:68 -#, fuzzy +#: src/std-traits/exercise.md:55 msgid "" -"Note that `IntoIter` and `Item` are linked: the iterator must have the same " -"`Item` type, which means that it returns `Option`" +"What happens if you chain two `RotDecoder` instances together, each rotating " +"by 13 characters?" msgstr "" -"请注意，“IntoIter”和“Item”已关联：迭代器必须具有相同的“Item”类型，这意味着它" -"会返回“Option\n" -"\n" -"”" - -#: src/exercises/day-2/iterators-and-ownership.md:71 -msgid "Like before, what is the type returned by the iterator?" -msgstr "和之前一样，迭代器返回的类型是什么？" -#: src/exercises/day-2/iterators-and-ownership.md:73 -msgid "" -"```rust,editable,compile_fail\n" -"fn main() {\n" -" let v: Vec = vec![String::from(\"foo\"), String::" -"from(\"bar\")];\n" -" let mut iter = v.into_iter();\n" -"\n" -" let v0: Option<..> = iter.next();\n" -" println!(\"v0: {v0:?}\");\n" -"}\n" -"```" +#: src/std-traits/solution.md:16 +msgid "'A'" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:83 -msgid "`for` Loops" -msgstr "“for”循环" +#: src/welcome-day-3.md:1 +msgid "Welcome to Day 3" +msgstr "欢迎参加第 3 天的课程" -#: src/exercises/day-2/iterators-and-ownership.md:85 -msgid "" -"Now that we know both `Iterator` and `IntoIterator`, we can build `for` " -"loops. They call `into_iter()` on an expression and iterates over the " -"resulting iterator:" +#: src/welcome-day-3.md:3 +msgid "Today, we will cover:" msgstr "" -"现在，我们已了解了“Iterator”和“IntoIterator”，接下来可以构建“for”循环了。它们" -"会针对表达式调用“into_iter()”，并对生成的迭代器进行迭代：" -#: src/exercises/day-2/iterators-and-ownership.md:89 +#: src/welcome-day-3.md:5 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let v: Vec = vec![String::from(\"foo\"), String::" -"from(\"bar\")];\n" -"\n" -" for word in &v {\n" -" println!(\"word: {word}\");\n" -" }\n" -"\n" -" for word in v {\n" -" println!(\"word: {word}\");\n" -" }\n" -"}\n" -"```" +"Memory management, lifetimes, and the borrow checker: how Rust ensures " +"memory safety." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:103 -msgid "What is the type of `word` in each loop?" -msgstr "每个循环中的“word”是什么类型？" +#: src/welcome-day-3.md:7 +msgid "Smart pointers: standard library pointer types." +msgstr "" + +#: src/memory-management/review.md:3 +msgid "Programs allocate memory in two ways:" +msgstr "" + +#: src/memory-management/review.md:5 +msgid "Stack: Continuous area of memory for local variables." +msgstr "栈：局部变量的连续内存区域。" + +#: src/memory-management/review.md:6 +msgid "Values have fixed sizes known at compile time." +msgstr "值在编译时具有已知的固定大小。" + +#: src/memory-management/review.md:7 +msgid "Extremely fast: just move a stack pointer." +msgstr "速度极快：只需移动一个栈指针。" -#: src/exercises/day-2/iterators-and-ownership.md:105 +#: src/memory-management/review.md:8 +msgid "Easy to manage: follows function calls." +msgstr "易于管理：遵循函数调用规则。" + +#: src/memory-management/review.md:9 +msgid "Great memory locality." +msgstr "优秀的内存局部性。" + +#: src/memory-management/review.md:11 +msgid "Heap: Storage of values outside of function calls." +msgstr "堆：函数调用之外的值的存储。" + +#: src/memory-management/review.md:12 +msgid "Values have dynamic sizes determined at runtime." +msgstr "值具有动态大小，具体大小需在运行时确定。" + +#: src/memory-management/review.md:13 +msgid "Slightly slower than the stack: some book-keeping needed." +msgstr "比栈稍慢：需要向系统申请空间。" + +#: src/memory-management/review.md:14 +msgid "No guarantee of memory locality." +msgstr "不保证内存局部性。" + +#: src/memory-management/review.md:18 #, fuzzy msgid "" -"Experiment with the code above and then consult the documentation for [`impl " -"IntoIterator for &Vec`](https://doc.rust-lang.org/std/vec/struct.Vec." -"html#impl-IntoIterator-for-%26'a+Vec%3CT,+A%3E) and [`impl IntoIterator for " -"Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-" -"for-Vec%3CT,+A%3E) to check your answers." +"Creating a `String` puts fixed-sized metadata on the stack and dynamically " +"sized data, the actual string, on the heap:" msgstr "" -"使用上方代码进行实验，然后参阅[“impl IntoIterator for &Vec\n" -"\n" -"”](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-for-" -"%26'a+Vec%3CT,+A%3E)和[“impl IntoIterator for Vec\n" -"\n" -"”](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-for-" -"Vec%3CT,+A%3E)的相关文档来检查您的答案。" +"创建 `String` 时将固定大小的数据存储在栈上， 并将动态大小的数据存储在堆上：" -#: src/exercises/day-2/strings-iterators.md:3 +#: src/memory-management/review.md:43 msgid "" -"In this exercise, you are implementing a routing component of a web server. " -"The server is configured with a number of _path prefixes_ which are matched " -"against _request paths_. The path prefixes can contain a wildcard character " -"which matches a full segment. See the unit tests below." +"Mention that a `String` is backed by a `Vec`, so it has a capacity and " +"length and can grow if mutable via reallocation on the heap." msgstr "" -"在本练习中，您将实现 Web 服务器的路由组件。服务器配置有多个路径前缀，这些前缀" -"与请求路径匹配。路径前缀可以包含与完整段匹配的通配符。请参阅下面的单元测试。" +"指出 `String` 底层由 `Vec` 实现，因此它具有容量和长度，如果值可变，则可以通过" +"在堆上重新分配存储空间进行增长。" -#: src/exercises/day-2/strings-iterators.md:8 +#: src/memory-management/review.md:46 msgid "" -"Copy the following code to and make the tests " -"pass. Try avoiding allocating a `Vec` for your intermediate results:" +"If students ask about it, you can mention that the underlying memory is heap " +"allocated using the [System Allocator](https://doc.rust-lang.org/std/alloc/" +"struct.System.html) and custom allocators can be implemented using the " +"[Allocator API](https://doc.rust-lang.org/std/alloc/index.html)" msgstr "" -"将以下代码复制到 ，然后设法通过测试。请尽量避免" -"为中间结果分配“Vec”：" +"如果学员提出相关问题，你可以提及我们不仅能使用\\[系统分配器\\]在堆上分配底层" +"内存，还能使用 [Allocator API](https://doc.rust-lang.org/std/alloc/index." +"html) 实现自定义分配器" -#: src/exercises/day-2/strings-iterators.md:12 +#: src/memory-management/review.md:52 +#, fuzzy msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub fn prefix_matches(prefix: &str, request_path: &str) -> bool {\n" -" unimplemented!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_without_wildcard() {\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/" -"abc-123\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/abc/" -"books\"));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/publishersBooks\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/parent/" -"publishers\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_with_wildcard() {\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/bar/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books/book1\"\n" -" ));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers/*/books\", \"/v1/" -"publishers\"));\n" -" assert!(!prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/booksByAuthor\"\n" -" ));\n" -"}\n" -"```" +"We can inspect the memory layout with `unsafe` Rust. However, you should " +"point out that this is rightfully unsafe!" msgstr "" +"我们可以使用 `unsafe` 代码检查内存布局。不过，你应该指出，这种做法不安全！" -#: src/welcome-day-3.md:1 -msgid "Welcome to Day 3" -msgstr "欢迎参加第 3 天的课程" - -#: src/welcome-day-3.md:3 -msgid "Today, we will cover some more advanced topics of Rust:" -msgstr "今天，我们将介绍一些更高级的 Rust 主题：" +#: src/memory-management/review.md:58 src/testing/unit-tests.md:15 +msgid "' '" +msgstr "" -#: src/welcome-day-3.md:5 -msgid "" -"Traits: deriving traits, default methods, and important standard library " -"traits." -msgstr "trait：派生 trait、默认方法和重要的标准库 trait。" +#: src/memory-management/review.md:59 +msgid "\"world\"" +msgstr "" -#: src/welcome-day-3.md:8 +#: src/memory-management/review.md:60 msgid "" -"Generics: generic data types, generic methods, monomorphization, and trait " -"objects." -msgstr "泛型：泛型数据类型、泛型方法、单态化和 trait 对象。" +"// DON'T DO THIS AT HOME! For educational purposes only.\n" +" // String provides no guarantees about its layout, so this could lead " +"to\n" +" // undefined behavior.\n" +msgstr "" -#: src/welcome-day-3.md:11 -msgid "Error handling: panics, `Result`, and the try operator `?`." -msgstr "错误处理：panic、“Result”和 try 运算符“?”。" +#: src/memory-management/review.md:65 +msgid "\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\"" +msgstr "" -#: src/welcome-day-3.md:13 -msgid "Testing: unit tests, documentation tests, and integration tests." -msgstr "测试：单元测试、文档测试和集成测试。" +#: src/memory-management/approaches.md:3 +msgid "Traditionally, languages have fallen into two broad categories:" +msgstr "传统上，语言分为两大类：" -#: src/welcome-day-3.md:15 -msgid "" -"Unsafe Rust: raw pointers, static variables, unsafe functions, and extern " -"functions." -msgstr "不安全 Rust：原始指针、静态变量、不安全函数和外部函数。" +#: src/memory-management/approaches.md:5 +msgid "Full control via manual memory management: C, C++, Pascal, ..." +msgstr "通过手动内存管理实现完全控制：C、C++、Pascal…" -#: src/generics.md:3 -#, fuzzy -msgid "" -"Rust support generics, which lets you abstract algorithms or data structures " -"(such as sorting or a binary tree) over the types used or stored." +#: src/memory-management/approaches.md:6 +msgid "Programmer decides when to allocate or free heap memory." msgstr "" -"Rust 支持泛型，允许您根据算法（例如排序）中使用的类型对算法进行抽象化处理。" - -#: src/generics/data-types.md:3 -msgid "You can use generics to abstract over the concrete field type:" -msgstr "您可以使用泛型对具体字段类型进行抽象化处理：" -#: src/generics/data-types.md:5 +#: src/memory-management/approaches.md:7 msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Point {\n" -" x: T,\n" -" y: T,\n" -"}\n" -"\n" -"fn main() {\n" -" let integer = Point { x: 5, y: 10 };\n" -" let float = Point { x: 1.0, y: 4.0 };\n" -" println!(\"{integer:?} and {float:?}\");\n" -"}\n" -"```" +"Programmer must determine whether a pointer still points to valid memory." msgstr "" -#: src/generics/data-types.md:21 -msgid "Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`." -msgstr "尝试声明一个新变量“let p = Point { x: 5, y: 10.0 };”。" - -#: src/generics/data-types.md:23 -msgid "Fix the code to allow points that have elements of different types." -msgstr "修正代码，以允许点具有不同类型的元素。" +#: src/memory-management/approaches.md:8 +msgid "Studies show, programmers make mistakes." +msgstr "" -#: src/generics/methods.md:3 -msgid "You can declare a generic type on your `impl` block:" -msgstr "您可以在 `impl` 块中声明通用类型：" +#: src/memory-management/approaches.md:9 +msgid "" +"Full safety via automatic memory management at runtime: Java, Python, Go, " +"Haskell, ..." +msgstr "运行时通过自动内存管理实现完全安全：Java、Python、Go、Haskell…" -#: src/generics/methods.md:5 +#: src/memory-management/approaches.md:11 msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Point(T, T);\n" -"\n" -"impl Point {\n" -" fn x(&self) -> &T {\n" -" &self.0 // + 10\n" -" }\n" -"\n" -" // fn set_x(&mut self, x: T)\n" -"}\n" -"\n" -"fn main() {\n" -" let p = Point(5, 10);\n" -" println!(\"p.x = {}\", p.x());\n" -"}\n" -"```" +"A runtime system ensures that memory is not freed until it can no longer be " +"referenced." msgstr "" -#: src/generics/methods.md:25 +#: src/memory-management/approaches.md:13 msgid "" -"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " -"redundant?" +"Typically implemented with reference counting, garbage collection, or RAII." msgstr "" -"\\*问：\\*为什么 `T` 在 `impl Point {}` 中指定了两次？这不是多余的吗？" -#: src/generics/methods.md:26 +#: src/memory-management/approaches.md:15 +msgid "Rust offers a new mix:" +msgstr "Rust 提供了一个全新的组合：" + +#: src/memory-management/approaches.md:17 msgid "" -"This is because it is a generic implementation section for generic type. " -"They are independently generic." -msgstr "这是因为它是泛型类型的泛型实现部分。它们是独立的泛型内容。" +"Full control _and_ safety via compile time enforcement of correct memory " +"management." +msgstr "通过编译时强制执行正确的内存>管理来实现完全控制与安全。" -#: src/generics/methods.md:27 -msgid "It means these methods are defined for any `T`." -msgstr "这意味着这些方法是针对所有 `T` 定义的。" +#: src/memory-management/approaches.md:20 +msgid "It does this with an explicit ownership concept." +msgstr "它通过一个明确的所有权（ownership）概念来实现此目的。" -#: src/generics/methods.md:28 -msgid "It is possible to write `impl Point { .. }`. " -msgstr "可以编写 `impl Point { .. }`。" +#: src/memory-management/approaches.md:24 +msgid "" +"This slide is intended to help students coming from other languages to put " +"Rust in context." +msgstr "" -#: src/generics/methods.md:29 +#: src/memory-management/approaches.md:27 msgid "" -"`Point` is still generic and you can use `Point`, but methods in this " -"block will only be available for `Point`." +"C must manage heap manually with `malloc` and `free`. Common errors include " +"forgetting to call `free`, calling it multiple times for the same pointer, " +"or dereferencing a pointer after the memory it points to has been freed." msgstr "" -"`Point` 依然是一个泛型，并且您可以使用 `Point`，但此块中的方法将仅适用" -"于 `Point`。" -#: src/generics/monomorphization.md:3 -msgid "Generic code is turned into non-generic code based on the call sites:" -msgstr "泛型代码根据调用位置转换为非泛型代码：" +#: src/memory-management/approaches.md:31 +msgid "" +"C++ has tools like smart pointers (`unique_ptr`, `shared_ptr`) that take " +"advantage of language guarantees about calling destructors to ensure memory " +"is freed when a function returns. It is still quite easy to mis-use these " +"tools and create similar bugs to C." +msgstr "" -#: src/generics/monomorphization.md:12 -msgid "behaves as if you wrote" -msgstr "具体行为与您所编写的一样" +#: src/memory-management/approaches.md:36 +msgid "" +"Java, Go, and Python rely on the garbage collector to identify memory that " +"is no longer reachable and discard it. This guarantees that any pointer can " +"be dereferenced, eliminating use-after-free and other classes of bugs. But, " +"GC has a runtime cost and is difficult to tune properly." +msgstr "" -#: src/generics/monomorphization.md:31 +#: src/memory-management/approaches.md:41 msgid "" -"This is a zero-cost abstraction: you get exactly the same result as if you " -"had hand-coded the data structures without the abstraction." +"Rust's ownership and borrowing model can, in many cases, get the performance " +"of C, with alloc and free operations precisely where they are required -- " +"zero cost. It also provides tools similar to C++'s smart pointers. When " +"required, other options such as reference counting are available, and there " +"are even third-party crates available to support runtime garbage collection " +"(not covered in this class)." msgstr "" -"这是零成本的抽象化处理：您得到的结果不会受到影响，也就是说，与在没有进行抽象" -"化处理的情况下，对数据结构进行手动编码时的结果一样。" -#: src/traits.md:3 +#: src/memory-management/ownership.md:3 msgid "" -"Rust lets you abstract over types with traits. They're similar to interfaces:" -msgstr "Rust 让您可以依据特征对类型进行抽象化处理。特征与接口类似：" +"All variable bindings have a _scope_ where they are valid and it is an error " +"to use a variable outside its scope:" +msgstr "所有变量绑定都有一个有效的“作用域”，使用 超出其作用域的变量是错误的：" -#: src/traits.md:5 +#: src/memory-management/ownership.md:20 +#, fuzzy msgid "" -"```rust,editable\n" -"struct Dog { name: String, age: i8 }\n" -"struct Cat { lives: i8 } // No name needed, cats won't respond anyway.\n" -"\n" -"trait Pet {\n" -" fn talk(&self) -> String;\n" -"}\n" -"\n" -"impl Pet for Dog {\n" -" fn talk(&self) -> String { format!(\"Woof, my name is {}!\", self." -"name) }\n" -"}\n" -"\n" -"impl Pet for Cat {\n" -" fn talk(&self) -> String { String::from(\"Miau!\") }\n" -"}\n" -"\n" -"fn greet(pet: &P) {\n" -" println!(\"Oh you're a cutie! What's your name? {}\", pet.talk());\n" -"}\n" -"\n" -"fn main() {\n" -" let captain_floof = Cat { lives: 9 };\n" -" let fido = Dog { name: String::from(\"Fido\"), age: 5 };\n" -"\n" -" greet(&captain_floof);\n" -" greet(&fido);\n" -"}\n" -"```" -msgstr "" +"We say that the variable _owns_ the value. Every Rust value has precisely " +"one owner at all times." +msgstr "指出变量“拥有”值。" -#: src/traits/trait-objects.md:3 +#: src/memory-management/ownership.md:23 +#, fuzzy msgid "" -"Trait objects allow for values of different types, for instance in a " -"collection:" -msgstr "特征（Trait）对象可接受不同类型的值，举例来说，在集合中会是这样：" +"At the end of the scope, the variable is _dropped_ and the data is freed. A " +"destructor can run here to free up resources." +msgstr "作用域结束时，变量会“被丢弃”，数据会被释放。" -#: src/traits/trait-objects.md:5 +#: src/memory-management/ownership.md:28 msgid "" -"```rust,editable\n" -"struct Dog { name: String, age: i8 }\n" -"struct Cat { lives: i8 } // No name needed, cats won't respond anyway.\n" -"\n" -"trait Pet {\n" -" fn talk(&self) -> String;\n" -"}\n" -"\n" -"impl Pet for Dog {\n" -" fn talk(&self) -> String { format!(\"Woof, my name is {}!\", self." -"name) }\n" -"}\n" -"\n" -"impl Pet for Cat {\n" -" fn talk(&self) -> String { String::from(\"Miau!\") }\n" -"}\n" -"\n" -"fn main() {\n" -" let pets: Vec> = vec![\n" -" Box::new(Cat { lives: 9 }),\n" -" Box::new(Dog { name: String::from(\"Fido\"), age: 5 }),\n" -" ];\n" -" for pet in pets {\n" -" println!(\"Hello, who are you? {}\", pet.talk());\n" -" }\n" -"}\n" -"```" +"Students familiar with garbage-collection implementations will know that a " +"garbage collector starts with a set of \"roots\" to find all reachable " +"memory. Rust's \"single owner\" principle is a similar idea." msgstr "" -#: src/traits/trait-objects.md:32 -msgid "Memory layout after allocating `pets`:" -msgstr "以下是分配 `pets` 后的内存布局：" +#: src/memory-management/move.md:3 +#, fuzzy +msgid "An assignment will transfer _ownership_ between variables:" +msgstr "赋值操作将在变量之间转移所有权：" + +#: src/memory-management/move.md:7 +#, fuzzy +msgid "\"Hello!\"" +msgstr "Hello World!" + +#: src/memory-management/move.md:9 src/slices-and-lifetimes/str.md:16 +#: src/slices-and-lifetimes/str.md:18 +msgid "\"s2: {s2}\"" +msgstr "" + +#: src/memory-management/move.md:10 +msgid "// println!(\"s1: {s1}\");\n" +msgstr "" + +#: src/memory-management/move.md:14 +msgid "The assignment of `s1` to `s2` transfers ownership." +msgstr "将 `s1` 赋值给 `s2`，即转移了所有权。" + +#: src/memory-management/move.md:15 +#, fuzzy +msgid "When `s1` goes out of scope, nothing happens: it does not own anything." +msgstr "当 `s1` 离开作用域时，什么都不会发生：它没有所有权。" -#: src/traits/trait-objects.md:34 +#: src/memory-management/move.md:16 +msgid "When `s2` goes out of scope, the string data is freed." +msgstr "当 `s2` 离开作用域时，字符串数据被释放。" + +#: src/memory-management/move.md:18 +msgid "Before move to `s2`:" +msgstr "移动到 `s2` 中之前：" + +#: src/memory-management/move.md:35 +msgid "After move to `s2`:" +msgstr "移动到 `s2` 中之后：" + +#: src/memory-management/move.md:37 msgid "" "```bob\n" " Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": pets : : +----+----+----+----" -"+ :\n" -": +-----------+-------+ : : +-----+-----+ .->| F | i | d | o " -"| :\n" -": | ptr | o---+---+-----+-->| o o | o o | | +----+----+----+----" -"+ :\n" -": | len | 2 | : : +-|-|-+-|-|-+ " -"`---------. :\n" -": | capacity | 2 | : : | | | | data " -"| :\n" -": +-----------+-------+ : : | | | | +-------+--|-------" -"+ :\n" -": : : | | | '-->| name | o, 4, 4 " -"| :\n" -": : : | | | | age | 5 " -"| :\n" -"`- - - - - - - - - - - - - -' : | | | +-------+----------" -"+ :\n" -" : | | " -"| :\n" -" : | | | " -"vtable :\n" -" : | | | +----------------------" -"+ :\n" -" : | | '---->| \"::talk\" " -"| :\n" -" : | | +----------------------" -"+ :\n" -" : | " -"| :\n" -" : | | " -"data :\n" -" : | | +-------+-------" -"+ :\n" -" : | '-->| lives | 9 " -"| :\n" -" : | +-------+-------" -"+ :\n" -" : " -"| :\n" -" : | " -"vtable :\n" -" : | +----------------------" -"+ :\n" -" : '---->| \"::talk\" " -"| :\n" -" : +----------------------" -"+ :\n" -" : :\n" -" '- - - - - - - - - - - - - - - - - - - - - " -"- -'\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"(inaccessible)\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" "```" msgstr "" +"```bob\n" +" 栈 堆\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"（无法访问）\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" -#: src/traits/trait-objects.md:68 +#: src/memory-management/move.md:58 msgid "" -"Types that implement a given trait may be of different sizes. This makes it " -"impossible to have things like `Vec` in the example above." +"When you pass a value to a function, the value is assigned to the function " +"parameter. This transfers ownership:" +msgstr "你将值传递给函数时，该值会被赋给函数 参数。这就转移了所有权：" + +#: src/memory-management/move.md:63 +msgid "\"Hello {name}\"" msgstr "" -#: src/traits/trait-objects.md:70 -msgid "" -"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " -"implements `Pet`." -msgstr "可通过“dyn Pet”这个方法向编译器告知实现“Pet”的动态大小类型。" +#: src/memory-management/move.md:67 src/android/interoperability/java.md:57 +#, fuzzy +msgid "\"Alice\"" +msgstr "切片" -#: src/traits/trait-objects.md:72 -msgid "" -"In the example, `pets` is allocated on the stack and the vector data is on " -"the heap. The two vector elements are _fat pointers_:" +#: src/memory-management/move.md:69 +msgid "// say_hello(name);\n" msgstr "" -#: src/traits/trait-objects.md:74 +#: src/memory-management/move.md:75 msgid "" -"A fat pointer is a double-width pointer. It has two components: a pointer to " -"the actual object and a pointer to the [virtual method table](https://en." -"wikipedia.org/wiki/Virtual_method_table) (vtable) for the `Pet` " -"implementation of that particular object." +"Mention that this is the opposite of the defaults in C++, which copies by " +"value unless you use `std::move` (and the move constructor is defined!)." msgstr "" +"指出这与 C++ 中的默认值相反。除非你使用 `std::move`（并已定义 move 构造函" +"数！），否则 C++ 中的默认值是按值复制的。" -#: src/traits/trait-objects.md:77 +#: src/memory-management/move.md:78 msgid "" -"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " -"has a `lives` field." +"It is only the ownership that moves. Whether any machine code is generated " +"to manipulate the data itself is a matter of optimization, and such copies " +"are aggressively optimized away." msgstr "" +"只有所有权发生了转移。是否会生成任何机器码来操控数据本身是一个优化方面的问" +"题，系统会主动优化此类副本。" -#: src/traits/trait-objects.md:79 -msgid "Compare these outputs in the above example:" -msgstr "比较上述示例中的这些输出：" - -#: src/traits/trait-objects.md:80 +#: src/memory-management/move.md:82 msgid "" -"```rust,ignore\n" -" println!(\"{} {}\", std::mem::size_of::(), std::mem::size_of::" -"());\n" -" println!(\"{} {}\", std::mem::size_of::<&Dog>(), std::mem::size_of::" -"<&Cat>());\n" -" println!(\"{}\", std::mem::size_of::<&dyn Pet>());\n" -" println!(\"{}\", std::mem::size_of::>());\n" -"```" -msgstr "" +"Simple values (such as integers) can be marked `Copy` (see later slides)." +msgstr "简单的值（例如整数）可以标记为“Copy”（请看后续幻灯片）。" -#: src/traits/deriving-traits.md:3 -msgid "" -"Rust derive macros work by automatically generating code that implements the " -"specified traits for a data structure." -msgstr "Rust 派生宏的运作方式是自动生成代码，用于实现数据结构的指定 trait。" +#: src/memory-management/move.md:84 +msgid "In Rust, clones are explicit (by using `clone`)." +msgstr "在 Rust 中，克隆是显式的（通过使用 `clone`）。" -#: src/traits/deriving-traits.md:5 -#, fuzzy -msgid "You can let the compiler derive a number of traits as follows:" -msgstr "您可以让编译器派生多个特征：" +#: src/memory-management/move.md:86 +msgid "In the `say_hello` example:" +msgstr "" -#: src/traits/deriving-traits.md:7 +#: src/memory-management/move.md:88 msgid "" -"```rust,editable\n" -"#[derive(Debug, Clone, PartialEq, Eq, Default)]\n" -"struct Player {\n" -" name: String,\n" -" strength: u8,\n" -" hit_points: u8,\n" -"}\n" -"\n" -"fn main() {\n" -" let p1 = Player::default();\n" -" let p2 = p1.clone();\n" -" println!(\"Is {:?}\\nequal to {:?}?\\nThe answer is {}!\", &p1, &p2,\n" -" if p1 == p2 { \"yes\" } else { \"no\" });\n" -"}\n" -"```" +"With the first call to `say_hello`, `main` gives up ownership of `name`. " +"Afterwards, `name` cannot be used anymore within `main`." msgstr "" +"首次调用 `say_hello` 时，`main` 便放弃了 `name` 的所有权。此后，`main` 中不能" +"再使用 `name`。" -#: src/traits/default-methods.md:3 -msgid "Traits can implement behavior in terms of other trait methods:" -msgstr "特征可以依照其他特征方法来实现行为：" - -#: src/traits/default-methods.md:5 +#: src/memory-management/move.md:90 msgid "" -"```rust,editable\n" -"trait Equals {\n" -" fn equals(&self, other: &Self) -> bool;\n" -" fn not_equals(&self, other: &Self) -> bool {\n" -" !self.equals(other)\n" -" }\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct Centimeter(i16);\n" -"\n" -"impl Equals for Centimeter {\n" -" fn equals(&self, other: &Centimeter) -> bool {\n" -" self.0 == other.0\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let a = Centimeter(10);\n" -" let b = Centimeter(20);\n" -" println!(\"{a:?} equals {b:?}: {}\", a.equals(&b));\n" -" println!(\"{a:?} not_equals {b:?}: {}\", a.not_equals(&b));\n" -"}\n" -"```" -msgstr "" +"The heap memory allocated for `name` will be freed at the end of the " +"`say_hello` function." +msgstr "在 `say_hello` 函数结束时，系统会释放为 `name` 分配的堆内存。" -#: src/traits/default-methods.md:32 +#: src/memory-management/move.md:92 msgid "" -"Traits may specify pre-implemented (default) methods and methods that users " -"are required to implement themselves. Methods with default implementations " -"can rely on required methods." +"`main` can retain ownership if it passes `name` as a reference (`&name`) and " +"if `say_hello` accepts a reference as a parameter." msgstr "" -"trait 或许可指定预实现（默认）方法，以及用户需要自行实现的方法。具有默认实现" -"的方法可以依赖于必需的方法。" - -#: src/traits/default-methods.md:35 -msgid "Move method `not_equals` to a new trait `NotEquals`." -msgstr "将方法“not_equals”移至新的 trait“NotEquals”。" - -#: src/traits/default-methods.md:37 -msgid "Make `Equals` a super trait for `NotEquals`." -msgstr "将“Equals”设为“NotEquals”的超 trait。" - -#: src/traits/default-methods.md:46 -msgid "Provide a blanket implementation of `NotEquals` for `Equals`." -msgstr "为“Equals”提供“NotEquals”的通用实现。" +"如果 `main` 将 `name` 作为引用 (`&name`) 传递过去，且 `say_hello` 接受作为参" +"数的引用，则可保留所有权。" -#: src/traits/default-methods.md:58 +#: src/memory-management/move.md:94 msgid "" -"With the blanket implementation, you no longer need `Equals` as a super " -"trait for `NotEqual`." -msgstr "借助通用实现，您不再需要将“Equals”作为“NotEqual”的超 trait。" +"Alternatively, `main` can pass a clone of `name` in the first call (`name." +"clone()`)." +msgstr "此外，`main` 也可以在首次调用时传递 `name` 的克隆 (`name.clone()`)。" -#: src/traits/trait-bounds.md:3 +#: src/memory-management/move.md:96 msgid "" -"When working with generics, you often want to require the types to implement " -"some trait, so that you can call this trait's methods." +"Rust makes it harder than C++ to inadvertently create copies by making move " +"semantics the default, and by forcing programmers to make clones explicit." msgstr "" -"使用泛型时，您通常会想要利用类型来实现某些特性， 这样才能调用此特征的方法。" +"相较于 C++，Rust 通过将移动语义设为默认值，并强制程序员进行显式克隆，更难以无" +"意中创建副本。" -#: src/traits/trait-bounds.md:6 -msgid "You can do this with `T: Trait` or `impl Trait`:" -msgstr "您可以使用 `T: Trait` 或 `impl Trait` 执行此操作：" +#: src/memory-management/move.md:101 +#, fuzzy +msgid "Defensive Copies in Modern C++" +msgstr "现代 C++ 中的双重释放" -#: src/traits/trait-bounds.md:8 -msgid "" -"```rust,editable\n" -"fn duplicate(a: T) -> (T, T) {\n" -" (a.clone(), a.clone())\n" -"}\n" -"\n" -"// Syntactic sugar for:\n" -"// fn add_42_millions>(x: T) -> i32 {\n" -"fn add_42_millions(x: impl Into) -> i32 {\n" -" x.into() + 42_000_000\n" -"}\n" -"\n" -"// struct NotClonable;\n" -"\n" -"fn main() {\n" -" let foo = String::from(\"foo\");\n" -" let pair = duplicate(foo);\n" -" println!(\"{pair:?}\");\n" -"\n" -" let many = add_42_millions(42_i8);\n" -" println!(\"{many}\");\n" -" let many_more = add_42_millions(10_000_000);\n" -" println!(\"{many_more}\");\n" -"}\n" -"```" +#: src/memory-management/move.md:103 +msgid "Modern C++ solves this differently:" +msgstr "现代 C++ 以不同的方式解决此问题：" + +#: src/memory-management/move.md:106 +msgid "\"Cpp\"" msgstr "" -#: src/traits/trait-bounds.md:35 -msgid "Show a `where` clause, students will encounter it when reading code." -msgstr "显示 `where` 子句，学员在阅读代码时会看到它。" +#: src/memory-management/move.md:107 +msgid "// Duplicate the data in s1.\n" +msgstr "" -#: src/traits/trait-bounds.md:46 -msgid "It declutters the function signature if you have many parameters." -msgstr "它会在您有多个形参的情况下整理函数签名。" +#: src/memory-management/move.md:110 +msgid "" +"The heap data from `s1` is duplicated and `s2` gets its own independent copy." +msgstr "`s1` 中的堆数据被复制，`s2` 获得自己的独立副本。" -#: src/traits/trait-bounds.md:47 -msgid "It has additional features making it more powerful." -msgstr "它具有额外功能，因此也更强大。" +#: src/memory-management/move.md:111 +msgid "When `s1` and `s2` go out of scope, they each free their own memory." +msgstr "当 `s1` 和 `s2` 离开作用域时，它们会各自释放自己的内存。" -#: src/traits/trait-bounds.md:48 -msgid "" -"If someone asks, the extra feature is that the type on the left of \":\" can " -"be arbitrary, like `Option`." -msgstr "" -"如果有人提问，便阐明额外功能是指“:”左侧的类别可为任意值，例如 `Option`。" +#: src/memory-management/move.md:113 +msgid "Before copy-assignment:" +msgstr "复制-赋值之前：" -#: src/traits/impl-trait.md:1 -msgid "`impl Trait`" -msgstr "`impl Trait`" +#: src/memory-management/move.md:129 +msgid "After copy-assignment:" +msgstr "复制-赋值之后：" -#: src/traits/impl-trait.md:3 +#: src/memory-management/move.md:154 msgid "" -"Similar to trait bounds, an `impl Trait` syntax can be used in function " -"arguments and return values:" -msgstr "与特征边界类似，`impl Trait` 语法可以在函数形参 和返回值中使用：" +"C++ has made a slightly different choice than Rust. Because `=` copies data, " +"the string data has to be cloned. Otherwise we would get a double-free when " +"either string goes out of scope." +msgstr "" +"C++ 做出了与 Rust 略有不同的选择。由于“=”会复制数据，因此必须克隆字符串数据。" +"否则，当任一字符串超出范围时，便会出现二次释放。" -#: src/traits/impl-trait.md:6 +#: src/memory-management/move.md:158 msgid "" -"```rust,editable\n" -"use std::fmt::Display;\n" -"\n" -"fn get_x(name: impl Display) -> impl Display {\n" -" format!(\"Hello {name}\")\n" -"}\n" -"\n" -"fn main() {\n" -" let x = get_x(\"foo\");\n" -" println!(\"{x}\");\n" -"}\n" -"```" +"C++ also has [`std::move`](https://en.cppreference.com/w/cpp/utility/move), " +"which is used to indicate when a value may be moved from. If the example had " +"been `s2 = std::move(s1)`, no heap allocation would take place. After the " +"move, `s1` would be in a valid but unspecified state. Unlike Rust, the " +"programmer is allowed to keep using `s1`." msgstr "" +"C++ 还包含[“std::move”](https://en.cppreference.com/w/cpp/utility/move)，它用" +"于指示何时可以移动某个值。如果示例为“s2 = std::move(s1)”，则不会发生堆分配。" +"移动后，“s1”将处于有效但未指定的状态。与 Rust 不同，程序员可以继续使用“s1”。" -#: src/traits/impl-trait.md:19 -msgid "`impl Trait` allows you to work with types which you cannot name." -msgstr "`impl Trait` 让您可使用无法命名的类型。" - -#: src/traits/impl-trait.md:23 +#: src/memory-management/move.md:163 msgid "" -"The meaning of `impl Trait` is a bit different in the different positions." -msgstr "`impl Trait` 的意义因使用位置而略有不同。" +"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " +"which is being copied or moved." +msgstr "" +"与 Rust 不同，使用 C++ 时，“=”可以运行任意代码，具体取决于要复制或移动的类" +"型。" -#: src/traits/impl-trait.md:25 -msgid "" -"For a parameter, `impl Trait` is like an anonymous generic parameter with a " -"trait bound." -msgstr "对形参来说，`impl Trait` 就像是具有特征边界的匿名泛型形参。" +#: src/memory-management/clone.md:1 +msgid "Clone" +msgstr "" -#: src/traits/impl-trait.md:27 +#: src/memory-management/clone.md:3 msgid "" -"For a return type, it means that the return type is some concrete type that " -"implements the trait, without naming the type. This can be useful when you " -"don't want to expose the concrete type in a public API." +"Sometimes you _want_ to make a copy of a value. The `Clone` trait " +"accomplishes this." msgstr "" -"对返回值类型来说，它则意味着返回值类型就是实现该特征的某具体类型， 无需为该类" -"型命名。如果您不想在公共 API 中公开该具体类型，便可 使用此方法。" -#: src/traits/impl-trait.md:31 +#: src/memory-management/clone.md:23 msgid "" -"Inference is hard in return position. A function returning `impl Foo` picks " -"the concrete type it returns, without writing it out in the source. A " -"function returning a generic type like `collect() -> B` can return any " -"type satisfying `B`, and the caller may need to choose one, such as with " -"`let x: Vec<_> = foo.collect()` or with the turbofish, `foo.collect::" -">()`." +"The idea of `Clone` is to make it easy to spot where heap allocations are " +"occurring. Look for `.clone()` and a few others like `Vec::new` or `Box::" +"new`." msgstr "" -"在返回位置处进行推断有一定难度。会返回 `impl Foo` 的函数会挑选 自身返回的具体" -"类型，而不必在来源中写出此信息。会返回 泛型类型（例如 `collect() -> B`）的" -"函数则可返回符合 `B` 的任何类型，而调用方可能需要选择一个类型，例如使用 `let " -"x: Vec<_> = foo.collect()` 或使用以下 Turbofish：`foo.collect::>()`。" -#: src/traits/impl-trait.md:37 +#: src/memory-management/clone.md:26 msgid "" -"This example is great, because it uses `impl Display` twice. It helps to " -"explain that nothing here enforces that it is _the same_ `impl Display` " -"type. If we used a single `T: Display`, it would enforce the constraint " -"that input `T` and return `T` type are the same type. It would not work for " -"this particular function, as the type we expect as input is likely not what " -"`format!` returns. If we wanted to do the same via `: Display` syntax, we'd " -"need two independent generic parameters." +"It's common to \"clone your way out\" of problems with the borrow checker, " +"and return later to try to optimize those clones away." msgstr "" -"这是一个非常棒的示例，因为它使用了两次 `impl Display`。这有助于说明 此处没有" -"任何项目会强制使用相同的 `impl Display` 类型。如果我们使用单个 `T: Display`，" -"它会强制限制输入 `T` 和返回 `T` 均为同一类型。 这并不适用于这个特定函数，因为" -"我们预期作为输入的类型可能 不会是 `format!` 返回的值。如果我们希望通过 `: " -"Display` 语法执行相同的操作，则需要两个 独立的泛型形参。" -#: src/traits/important-traits.md:3 +#: src/memory-management/copy-types.md:7 msgid "" -"We will now look at some of the most common traits of the Rust standard " -"library:" -msgstr "现在，我们来看看 Rust 标准库的一些最常见的特征：" +"While move semantics are the default, certain types are copied by default:" +msgstr "虽然移动语义是默认的，但默认情况下会复制某些类型：" -#: src/traits/important-traits.md:5 -msgid "" -"[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " -"[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " -"used in `for` loops," -msgstr "" -"[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) 和 " -"[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " -"用于 `for` 循环中，" +#: src/memory-management/copy-types.md:20 +msgid "These types implement the `Copy` trait." +msgstr "这些类型实现了 `Copy` trait。" -#: src/traits/important-traits.md:6 -msgid "" -"[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) and [`Into`]" -"(https://doc.rust-lang.org/std/convert/trait.Into.html) used to convert " -"values," -msgstr "" -"[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 和 [`Into`]" -"(https://doc.rust-lang.org/std/convert/trait.Into.html) 用于转换值，" +#: src/memory-management/copy-types.md:22 +msgid "You can opt-in your own types to use copy semantics:" +msgstr "你可以选择自己的类型来使用复制语义：" -#: src/traits/important-traits.md:7 -msgid "" -"[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and [`Write`]" -"(https://doc.rust-lang.org/std/io/trait.Write.html) used for IO," -msgstr "" -"[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 [`Write`]" -"(https://doc.rust-lang.org/std/io/trait.Write.html) 用于实现 IO。" +#: src/memory-management/copy-types.md:38 +msgid "After the assignment, both `p1` and `p2` own their own data." +msgstr "赋值之后，`p1` 和 `p2` 都拥有自己的数据。" -#: src/traits/important-traits.md:8 -msgid "" -"[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html), [`Mul`](https://" -"doc.rust-lang.org/std/ops/trait.Mul.html), ... used for operator " -"overloading, and" -msgstr "" -"[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html)、[`Mul`](https://" -"doc.rust-lang.org/std/ops/trait.Mul.html) 等用于实现运算符重载，" +#: src/memory-management/copy-types.md:39 +msgid "We can also use `p1.clone()` to explicitly copy the data." +msgstr "我们还可以使用 `p1.clone()` 显式复制数据。" -#: src/traits/important-traits.md:9 -msgid "" -"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) used for " -"defining destructors." -msgstr "" -"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) 用于定义析构函" -"数。" +#: src/memory-management/copy-types.md:43 +msgid "Copying and cloning are not the same thing:" +msgstr "复制和克隆是两码事：" -#: src/traits/important-traits.md:10 +#: src/memory-management/copy-types.md:45 msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) used " -"to construct a default instance of a type." -msgstr "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) 用于构" -"建相应类型的默认实例。" - -#: src/traits/iterator.md:1 -msgid "Iterators" -msgstr "迭代器" +"Copying refers to bitwise copies of memory regions and does not work on " +"arbitrary objects." +msgstr "复制是指内存区域的按位复制，不适用于任意对象。" -#: src/traits/iterator.md:3 +#: src/memory-management/copy-types.md:47 msgid "" -"You can implement the [`Iterator`](https://doc.rust-lang.org/std/iter/trait." -"Iterator.html) trait on your own types:" -msgstr "" -"您可以自行实现 [`Iterator`](https://doc.rust-lang.org/std/iter/trait." -"Iterator.html) 特征：" +"Copying does not allow for custom logic (unlike copy constructors in C++)." +msgstr "复制不允许自定义逻辑（不同于 C++ 中的复制构造函数）。" -#: src/traits/iterator.md:5 +#: src/memory-management/copy-types.md:48 msgid "" -"```rust,editable\n" -"struct Fibonacci {\n" -" curr: u32,\n" -" next: u32,\n" -"}\n" -"\n" -"impl Iterator for Fibonacci {\n" -" type Item = u32;\n" -"\n" -" fn next(&mut self) -> Option {\n" -" let new_next = self.curr + self.next;\n" -" self.curr = self.next;\n" -" self.next = new_next;\n" -" Some(self.curr)\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let fib = Fibonacci { curr: 0, next: 1 };\n" -" for (i, n) in fib.enumerate().take(5) {\n" -" println!(\"fib({i}): {n}\");\n" -" }\n" -"}\n" -"```" -msgstr "" +"Cloning is a more general operation and also allows for custom behavior by " +"implementing the `Clone` trait." +msgstr "克隆是一种更通用的操作，也允许通过实现 `Clone` trait 来自定义行为。" -#: src/traits/iterator.md:32 -msgid "" -"The `Iterator` trait implements many common functional programming " -"operations over collections (e.g. `map`, `filter`, `reduce`, etc). This is " -"the trait where you can find all the documentation about them. In Rust these " -"functions should produce the code as efficient as equivalent imperative " -"implementations." -msgstr "" -"`Iterator` 特征会对集合实现许多常见的函数程序操作， 例如 ` map`filter \\``和" -"`reduce\\` 等。您可以通过此特征找到有关它们的所有 文档。在 Rust 中，这些函数" -"应生成代码，且生成的代码应与等效命令式实现一样 高效。" +#: src/memory-management/copy-types.md:50 +msgid "Copying does not work on types that implement the `Drop` trait." +msgstr "复制不适用于实现 `Drop` trait 的类型。" -#: src/traits/iterator.md:37 -msgid "" -"`IntoIterator` is the trait that makes for loops work. It is implemented by " -"collection types such as `Vec` and references to them such as `&Vec` " -"and `&[T]`. Ranges also implement it. This is why you can iterate over a " -"vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." -msgstr "" -"`IntoIterator` 是迫使 for 循环运作的特征。此特征由集合类型 （例如 `Vec`）" -"和相关引用（例如 `&Vec` 和 `&[T]`）而实现。此外，范围也会实现这项特征。因" -"此， 您可以使用 `for i in some_vec { .. }` 来遍历某矢量，但 `some_vec." -"next()` 不存在。" +#: src/memory-management/copy-types.md:52 +msgid "In the above example, try the following:" +msgstr "在上述示例中，请尝试以下操作：" -#: src/traits/from-iterator.md:3 +#: src/memory-management/copy-types.md:54 msgid "" -"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " -"lets you build a collection from an [`Iterator`](https://doc.rust-lang.org/" -"std/iter/trait.Iterator.html)." +"Add a `String` field to `struct Point`. It will not compile because `String` " +"is not a `Copy` type." msgstr "" -"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " -"让您可通过 [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator." -"html) 构建一个集合。" +"在 `struct Point` 中添加 `String` 字段。由于 `String` 不属于 `Copy` 类型，因" +"此无法编译。" -#: src/traits/from-iterator.md:5 +#: src/memory-management/copy-types.md:56 #, fuzzy msgid "" -"```rust,editable\n" -"fn main() {\n" -" let primes = vec![2, 3, 5, 7];\n" -" let prime_squares = primes\n" -" .into_iter()\n" -" .map(|prime| prime * prime)\n" -" .collect::>();\n" -" println!(\"prime_squares: {prime_squares:?}\");\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" let mut iter = v.into_iter();\n" -"\n" -" while let Some(x) = iter.next() {\n" -" println!(\"x: {x}\");\n" -" }\n" -"}\n" -"```" - -#: src/traits/from-iterator.md:18 -msgid "" -"`Iterator` implements `fn collect(self) -> B where B: FromIterator, Self: Sized`" -msgstr "" -"`Iterator` 会实现 `fn collect(self) -> B where B: FromIterator, Self: Sized`" - -#: src/traits/from-iterator.md:24 -msgid "" -"There are also implementations which let you do cool things like convert an " -"`Iterator>` into a `Result, E>`." +"Remove `Copy` from the `derive` attribute. The compiler error is now in the " +"`println!` for `p1`." msgstr "" -"还有一些实现，让您可执行一些很酷的操作，比如 将 `Iterator>` 转换成 `Result, E>`。" - -#: src/traits/from-into.md:1 -msgid "`From` and `Into`" -msgstr "`From` 和 `Into`" +"从 `derive` 属性中移除 `Copy`。现在，编译器错误位于 `p1`的 `println!` 中。" -#: src/traits/from-into.md:3 -msgid "" -"Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." -"html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " -"facilitate type conversions:" -msgstr "" -"类型会实现 [`From`](https://doc.rust-lang.org/std/convert/trait.From.html) " -"和 [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) 以加快类型" -"转换：" +#: src/memory-management/copy-types.md:58 +msgid "Show that it works if you clone `p1` instead." +msgstr "指出如果你改为克隆 `p1`，则可按预期运行。" -#: src/traits/from-into.md:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s = String::from(\"hello\");\n" -" let addr = std::net::Ipv4Addr::from([127, 0, 0, 1]);\n" -" let one = i16::from(true);\n" -" let bigger = i32::from(123i16);\n" -" println!(\"{s}, {addr}, {one}, {bigger}\");\n" -"}\n" -"```" -msgstr "" +#: src/memory-management/drop.md:1 +msgid "The `Drop` Trait" +msgstr "`Drop` 特征" -#: src/traits/from-into.md:15 +#: src/memory-management/drop.md:3 msgid "" -"[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) is " -"automatically implemented when [`From`](https://doc.rust-lang.org/std/" -"convert/trait.From.html) is implemented:" +"Values which implement [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop." +"html) can specify code to run when they go out of scope:" msgstr "" -"实现 [`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 后，系统" -"会自动实现 [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html)：" +"用于实现 [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) 的值可以" +"指定在超出范围时运行的代码：" -#: src/traits/from-into.md:17 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s: String = \"hello\".into();\n" -" let addr: std::net::Ipv4Addr = [127, 0, 0, 1].into();\n" -" let one: i16 = true.into();\n" -" let bigger: i32 = 123i16.into();\n" -" println!(\"{s}, {addr}, {one}, {bigger}\");\n" -"}\n" -"```" +#: src/memory-management/drop.md:13 +msgid "\"Dropping {}\"" msgstr "" -#: src/traits/from-into.md:29 -msgid "" -"That's why it is common to only implement `From`, as your type will get " -"`Into` implementation too." -msgstr "这就是为什么通常只需实现 `From`，因为您的类型也会实现 `Into`。" - -#: src/traits/from-into.md:30 -msgid "" -"When declaring a function argument input type like \"anything that can be " -"converted into a `String`\", the rule is opposite, you should use `Into`. " -"Your function will accept types that implement `From` and those that _only_ " -"implement `Into`." +#: src/memory-management/drop.md:18 +#: src/exercises/concurrency/link-checker.md:93 +#: src/exercises/concurrency/solutions-morning.md:125 +msgid "\"a\"" msgstr "" -"若要声明某个函数实参输入类型（例如“任何可转换成 `String` 的类型”），规则便会" -"相反，此时应使用 `Into`。 您的函数会接受可实现 `From` 的类型，以及那些仅实现 " -"`Into` 的类型。" - -#: src/traits/read-write.md:1 -msgid "`Read` and `Write`" -msgstr "`Read` 和 `Write`" -#: src/traits/read-write.md:3 -msgid "" -"Using [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and " -"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html), you can " -"abstract over `u8` sources:" +#: src/memory-management/drop.md:20 src/testing/googletest.md:12 +msgid "\"b\"" msgstr "" -"您可以使用 [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 " -"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html) 对 `u8` 来源" -"进行抽象化处理：" -#: src/traits/read-write.md:5 -msgid "" -"```rust,editable\n" -"use std::io::{BufRead, BufReader, Read, Result};\n" -"\n" -"fn count_lines(reader: R) -> usize {\n" -" let buf_reader = BufReader::new(reader);\n" -" buf_reader.lines().count()\n" -"}\n" -"\n" -"fn main() -> Result<()> {\n" -" let slice: &[u8] = b\"foo\\nbar\\nbaz\\n\";\n" -" println!(\"lines in slice: {}\", count_lines(slice));\n" -"\n" -" let file = std::fs::File::open(std::env::current_exe()?)?;\n" -" println!(\"lines in file: {}\", count_lines(file));\n" -" Ok(())\n" -"}\n" -"```" +#: src/memory-management/drop.md:22 +msgid "\"c\"" msgstr "" -#: src/traits/read-write.md:23 -msgid "" -"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " -"you abstract over `u8` sinks:" +#: src/memory-management/drop.md:23 +msgid "\"d\"" msgstr "" -"您同样可使用 [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) 对 " -"`u8` 接收器进行抽象化处理：" -#: src/traits/read-write.md:25 -msgid "" -"```rust,editable\n" -"use std::io::{Result, Write};\n" -"\n" -"fn log(writer: &mut W, msg: &str) -> Result<()> {\n" -" writer.write_all(msg.as_bytes())?;\n" -" writer.write_all(\"\\n\".as_bytes())\n" -"}\n" -"\n" -"fn main() -> Result<()> {\n" -" let mut buffer = Vec::new();\n" -" log(&mut buffer, \"Hello\")?;\n" -" log(&mut buffer, \"World\")?;\n" -" println!(\"Logged: {:?}\", buffer);\n" -" Ok(())\n" -"}\n" -"```" +#: src/memory-management/drop.md:24 +msgid "\"Exiting block B\"" msgstr "" -#: src/traits/drop.md:1 -msgid "The `Drop` Trait" -msgstr "`Drop` 特征" - -#: src/traits/drop.md:3 -msgid "" -"Values which implement [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop." -"html) can specify code to run when they go out of scope:" +#: src/memory-management/drop.md:26 +msgid "\"Exiting block A\"" msgstr "" -"用于实现 [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) 的值可以" -"指定在超出范围时运行的代码：" -#: src/traits/drop.md:5 -msgid "" -"```rust,editable\n" -"struct Droppable {\n" -" name: &'static str,\n" -"}\n" -"\n" -"impl Drop for Droppable {\n" -" fn drop(&mut self) {\n" -" println!(\"Dropping {}\", self.name);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let a = Droppable { name: \"a\" };\n" -" {\n" -" let b = Droppable { name: \"b\" };\n" -" {\n" -" let c = Droppable { name: \"c\" };\n" -" let d = Droppable { name: \"d\" };\n" -" println!(\"Exiting block B\");\n" -" }\n" -" println!(\"Exiting block A\");\n" -" }\n" -" drop(a);\n" -" println!(\"Exiting main\");\n" -"}\n" -"```" +#: src/memory-management/drop.md:29 +msgid "\"Exiting main\"" msgstr "" -#: src/traits/drop.md:34 +#: src/memory-management/drop.md:35 msgid "Note that `std::mem::drop` is not the same as `std::ops::Drop::drop`." msgstr "" -#: src/traits/drop.md:35 +#: src/memory-management/drop.md:36 msgid "Values are automatically dropped when they go out of scope." msgstr "" -#: src/traits/drop.md:36 +#: src/memory-management/drop.md:37 msgid "" "When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" "drop` implementation will be called." msgstr "" -#: src/traits/drop.md:38 +#: src/memory-management/drop.md:39 msgid "" "All its fields will then be dropped too, whether or not it implements `Drop`." msgstr "" -#: src/traits/drop.md:39 +#: src/memory-management/drop.md:40 msgid "" "`std::mem::drop` is just an empty function that takes any value. The " "significance is that it takes ownership of the value, so at the end of its " @@ -9604,21 +7513,17 @@ msgid "" "values earlier than they would otherwise go out of scope." msgstr "" -#: src/traits/drop.md:42 +#: src/memory-management/drop.md:44 msgid "" "This can be useful for objects that do some work on `drop`: releasing locks, " "closing files, etc." msgstr "" -#: src/traits/drop.md:45 src/traits/operators.md:26 -msgid "Discussion points:" -msgstr "讨论点：" - -#: src/traits/drop.md:47 +#: src/memory-management/drop.md:49 msgid "Why doesn't `Drop::drop` take `self`?" msgstr "为什么 `Drop::drop` 不使用 `self`？" -#: src/traits/drop.md:48 +#: src/memory-management/drop.md:50 msgid "" "Short-answer: If it did, `std::mem::drop` would be called at the end of the " "block, resulting in another call to `Drop::drop`, and a stack overflow!" @@ -9626,6552 +7531,9259 @@ msgstr "" "简答：如果这样的话，系统会在代码块结尾 调用 `std::mem::drop`，进而引发再一次" "调用 `Drop::drop`，并引发堆栈 溢出！" -#: src/traits/drop.md:51 +#: src/memory-management/drop.md:52 msgid "Try replacing `drop(a)` with `a.drop()`." msgstr "尝试用 `a.drop()` 替换 `drop(a)`。" -#: src/traits/default.md:1 -msgid "The `Default` Trait" -msgstr "`Default` 特征" - -#: src/traits/default.md:3 +#: src/memory-management/exercise.md:3 msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " -"produces a default value for a type." +"In this example, we will implement a complex data type that owns all of its " +"data. We will use the \"builder pattern\" to support building a new value " +"piece-by-piece, using convenience functions." msgstr "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) 特征会" -"为类型生成默认值。" -#: src/traits/default.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug, Default)]\n" -"struct Derived {\n" -" x: u32,\n" -" y: String,\n" -" z: Implemented,\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct Implemented(String);\n" -"\n" -"impl Default for Implemented {\n" -" fn default() -> Self {\n" -" Self(\"John Smith\".into())\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let default_struct = Derived::default();\n" -" println!(\"{default_struct:#?}\");\n" -"\n" -" let almost_default_struct = Derived {\n" -" y: \"Y is set!\".into(),\n" -" ..Derived::default()\n" -" };\n" -" println!(\"{almost_default_struct:#?}\");\n" -"\n" -" let nothing: Option = None;\n" -" println!(\"{:#?}\", nothing.unwrap_or_default());\n" -"}\n" -"\n" -"```" +#: src/memory-management/exercise.md:7 +msgid "Fill in the missing pieces." msgstr "" -#: src/traits/default.md:40 -msgid "" -"It can be implemented directly or it can be derived via `#[derive(Default)]`." -msgstr "系统可以直接实现它，也可以通过 `#[derive(Default)]` 派生出它。" +#: src/memory-management/exercise.md:22 src/memory-management/solution.md:16 +msgid "/// A representation of a software package.\n" +msgstr "" -#: src/traits/default.md:41 -#, fuzzy +#: src/memory-management/exercise.md:34 src/memory-management/solution.md:28 msgid "" -"A derived implementation will produce a value where all fields are set to " -"their default values." -msgstr "派生的实现会生成一个实例，其中字段全都设为其默认值。" +"/// Return a representation of this package as a dependency, for use in\n" +" /// building other packages.\n" +msgstr "" -#: src/traits/default.md:42 -msgid "This means all types in the struct must implement `Default` too." -msgstr "这意味着，该结构体中的所有类型也都必须实现 `Default`。" +#: src/memory-management/exercise.md:37 +msgid "\"1\"" +msgstr "" -#: src/traits/default.md:43 +#: src/memory-management/exercise.md:40 src/memory-management/solution.md:37 msgid "" -"Standard Rust types often implement `Default` with reasonable values (e.g. " -"`0`, `\"\"`, etc)." +"/// A builder for a Package. Use `build()` to create the `Package` itself.\n" msgstr "" -"标准的 Rust 类型通常会以合理的值（例如 ` 0`\"\" \\``等）实现`Default\\`。" -#: src/traits/default.md:44 -msgid "The partial struct copy works nicely with default." -msgstr "部分结构体副本可与默认值完美搭配运作。" +#: src/memory-management/exercise.md:46 +msgid "\"2\"" +msgstr "" -#: src/traits/default.md:45 -msgid "" -"Rust standard library is aware that types can implement `Default` and " -"provides convenience methods that use it." -msgstr "Rust 标准库了解类型可能会实现 `Default`，因此提供了便利的使用方式。" +#: src/memory-management/exercise.md:49 src/memory-management/solution.md:52 +msgid "/// Set the package version.\n" +msgstr "" -#: src/traits/default.md:46 -msgid "" -"the `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" -"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" -"with-struct-update-syntax)" +#: src/memory-management/exercise.md:55 src/memory-management/solution.md:58 +msgid "/// Set the package authors.\n" msgstr "" -"“..”语法被称为[结构体更新语法](https://doc.rust-lang.org/book/ch05-01-" -"defining-structs.html#creating-instances-from-other-instances-with-struct-" -"update-syntax)" -#: src/traits/operators.md:1 -msgid "`Add`, `Mul`, ..." -msgstr "` Add`Mul \\``…" +#: src/memory-management/exercise.md:57 +msgid "\"3\"" +msgstr "" -#: src/traits/operators.md:3 -msgid "" -"Operator overloading is implemented via traits in [`std::ops`](https://doc." -"rust-lang.org/std/ops/index.html):" +#: src/memory-management/exercise.md:60 src/memory-management/solution.md:64 +msgid "/// Add an additional dependency.\n" msgstr "" -"运算符重载是通过 [`std::ops`](https://doc.rust-lang.org/std/ops/index.html) " -"中的特征实现的：" -#: src/traits/operators.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug, Copy, Clone)]\n" -"struct Point { x: i32, y: i32 }\n" -"\n" -"impl std::ops::Add for Point {\n" -" type Output = Self;\n" -"\n" -" fn add(self, other: Self) -> Self {\n" -" Self {x: self.x + other.x, y: self.y + other.y}\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let p1 = Point { x: 10, y: 20 };\n" -" let p2 = Point { x: 100, y: 200 };\n" -" println!(\"{:?} + {:?} = {:?}\", p1, p2, p1 + p2);\n" -"}\n" -"```" +#: src/memory-management/exercise.md:62 +msgid "\"4\"" msgstr "" -#: src/traits/operators.md:28 -msgid "" -"You could implement `Add` for `&Point`. In which situations is that useful? " -msgstr "您可以针对 `&Point` 实现 `Add`。此做法在哪些情况下可派上用场？" +#: src/memory-management/exercise.md:65 src/memory-management/solution.md:70 +msgid "/// Set the language. If not set, language defaults to None.\n" +msgstr "" -#: src/traits/operators.md:29 -msgid "" -"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " -"the operator is not `Copy`, you should consider overloading the operator for " -"`&T` as well. This avoids unnecessary cloning on the call site." +#: src/memory-management/exercise.md:67 +msgid "\"5\"" msgstr "" -"回答：`Add:add` 会耗用 `self`。如果您的运算符重载对象 （即类型 `T`）不是 " -"`Copy`，建议您也为 `&T` 重载运算符。这可避免调用点上存在不必要的 克隆任务。" -#: src/traits/operators.md:33 -msgid "" -"Why is `Output` an associated type? Could it be made a type parameter of the " -"method?" -msgstr "为什么 `Output` 是关联类型？可将它用作该方法的类型形参吗？" +#: src/memory-management/exercise.md:76 src/memory-management/solution.md:82 +msgid "\"base64\"" +msgstr "" -#: src/traits/operators.md:34 -msgid "" -"Short answer: Function type parameters are controlled by the caller, but " -"associated types (like `Output`) are controlled by the implementor of a " -"trait." +#: src/memory-management/exercise.md:76 src/memory-management/solution.md:82 +msgid "\"0.13\"" msgstr "" -"简答：函数类型形参是由调用方控管，但 `Output` 这类关联类型则由特征实现人员 控" -"管。" -#: src/traits/operators.md:37 -msgid "" -"You could implement `Add` for two different types, e.g. `impl Add<(i32, " -"i32)> for Point` would add a tuple to a `Point`." +#: src/memory-management/exercise.md:77 src/memory-management/solution.md:83 +msgid "\"base64: {base64:?}\"" msgstr "" -"您可以针对两种不同类型实现 `Add`，例如， `impl Add<(i32, i32)> for Point` 会" -"向 `Point` 中添加元组。" -#: src/traits/closures.md:1 -msgid "Closures" -msgstr "闭包" +#: src/memory-management/exercise.md:79 src/memory-management/solution.md:85 +msgid "\"log\"" +msgstr "" -#: src/traits/closures.md:3 -msgid "" -"Closures or lambda expressions have types which cannot be named. However, " -"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." -"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " -"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" +#: src/memory-management/exercise.md:79 src/memory-management/solution.md:85 +msgid "\"0.4\"" msgstr "" -"闭包或 lambda 表达式具有无法命名的类型。不过，它们会 实现特殊的 [`Fn`]" -"(https://doc.rust-lang.org/std/ops/trait.Fn.html)， [`FnMut`](https://doc." -"rust-lang.org/std/ops/trait.FnMut.html) 和 [`FnOnce`](https://doc.rust-lang." -"org/std/ops/trait.FnOnce.html) 特征：" -#: src/traits/closures.md:8 -msgid "" -"```rust,editable\n" -"fn apply_with_log(func: impl FnOnce(i32) -> i32, input: i32) -> i32 {\n" -" println!(\"Calling function on {input}\");\n" -" func(input)\n" -"}\n" -"\n" -"fn main() {\n" -" let add_3 = |x| x + 3;\n" -" println!(\"add_3: {}\", apply_with_log(add_3, 10));\n" -" println!(\"add_3: {}\", apply_with_log(add_3, 20));\n" -"\n" -" let mut v = Vec::new();\n" -" let mut accumulate = |x: i32| {\n" -" v.push(x);\n" -" v.iter().sum::()\n" -" };\n" -" println!(\"accumulate: {}\", apply_with_log(&mut accumulate, 4));\n" -" println!(\"accumulate: {}\", apply_with_log(&mut accumulate, 5));\n" -"\n" -" let multiply_sum = |x| x * v.into_iter().sum::();\n" -" println!(\"multiply_sum: {}\", apply_with_log(multiply_sum, 3));\n" -"}\n" -"```" +#: src/memory-management/exercise.md:80 src/memory-management/solution.md:86 +msgid "\"log: {log:?}\"" msgstr "" -#: src/traits/closures.md:34 -msgid "" -"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " -"perhaps captures nothing at all. It can be called multiple times " -"concurrently." +#: src/memory-management/exercise.md:81 src/memory-management/solution.md:87 +msgid "\"serde\"" msgstr "" -"`Fn`（例如 `add_3`）既不会耗用也不会修改捕获的值，或许 也不会捕获任何值。它可" -"被并发调用多次。" -#: src/traits/closures.md:37 -msgid "" -"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " -"multiple times, but not concurrently." +#: src/memory-management/exercise.md:82 src/memory-management/solution.md:88 +msgid "\"djmitche\"" msgstr "" -"`FnMut`（例如 `accumulate`）可能会改变捕获的值。您可以多次调用它， 但不能并发" -"调用它。" -#: src/traits/closures.md:40 -msgid "" -"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " -"might consume captured values." +#: src/memory-management/exercise.md:83 src/memory-management/solution.md:89 +msgid "\"4.0\"" msgstr "" -"如果您使用 `FnOnce`（例如 `multiply_sum`），或许只能调用它一次。它可能会耗用 " -"所捕获的值。" -#: src/traits/closures.md:43 -msgid "" -"`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " -"I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " -"use an `Fn` wherever an `FnMut` or `FnOnce` is called for." +#: src/memory-management/exercise.md:87 src/memory-management/solution.md:93 +msgid "\"serde: {serde:?}\"" msgstr "" -"`FnMut` 是 `FnOnce` 的子类型。`Fn` 是 `FnMut` 和 `FnOnce` 的子类型。也就是" -"说，您可以在任何 需要调用 `FnOnce` 的地方使用 `FnMut`，还可在任何需要调用 " -"`FnMut` 或 `FnOnce` 的地方 使用 `Fn`。" -#: src/traits/closures.md:47 +#: src/memory-management/solution.md:45 +msgid "\"0.1\"" +msgstr "" + +#: src/smart-pointers/box.md:3 msgid "" -"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " -"`multiply_sum`), depending on what the closure captures." +"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " +"pointer to data on the heap:" +msgstr "" +"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) 是指向堆上数据的" +"自有指针：" + +#: src/smart-pointers/box.md:9 +msgid "\"five: {}\"" msgstr "" -"编译器也会推断 `Copy`（例如针对 `add_3`）和 `Clone`（例如 `multiply_sum`）， " -"具体取决于闭包捕获的数据。" -#: src/traits/closures.md:50 +#: src/smart-pointers/box.md:26 msgid "" -"By default, closures will capture by reference if they can. The `move` " -"keyword makes them capture by value." +"`Box` implements `Deref`, which means that you can [call " +"methods from `T` directly on a `Box`](https://doc.rust-lang.org/std/ops/" +"trait.Deref.html#more-on-deref-coercion)." msgstr "" -"默认情况下，闭包会依据引用来捕获数据（如果可以的话）。`move` 关键字则可让闭包" -"依据值 来捕获数据。" +"`Box` 会实现 `Deref`，这意味着您可以[直接在 `Box` 上通过 " +"`T` 调用相应方法](https://doc.rust-lang.org/std/ops/trait.Deref.html#more-on-" +"deref-coercion)。" -#: src/traits/closures.md:52 +#: src/smart-pointers/box.md:30 msgid "" -"```rust,editable\n" -"fn make_greeter(prefix: String) -> impl Fn(&str) {\n" -" return move |name| println!(\"{} {}\", prefix, name)\n" -"}\n" -"\n" -"fn main() {\n" -" let hi = make_greeter(\"Hi\".to_string());\n" -" hi(\"there\");\n" -"}\n" -"```" +"Recursive data types or data types with dynamic sizes need to use a `Box`:" +msgstr "递归数据类型或具有动态大小的数据类型需要使用 `Box`：" + +#: src/smart-pointers/box.md:35 +msgid "/// A non-empty list: first element and the rest of the list.\n" msgstr "" -#: src/exercises/day-3/morning.md:1 -msgid "Day 3: Morning Exercises" -msgstr "第 3 天：上午练习" +#: src/smart-pointers/box.md:37 +msgid "/// An empty list.\n" +msgstr "" -#: src/exercises/day-3/morning.md:3 -msgid "We will design a classical GUI library using traits and trait objects." -msgstr "我们将使用 trait 和 trait 对象设计一个经典的 GUI 库。" +#: src/smart-pointers/box.md:44 src/smart-pointers/box.md:97 +msgid "\"{list:?}\"" +msgstr "" -#: src/exercises/day-3/morning.md:5 +#: src/smart-pointers/box.md:48 +#, fuzzy msgid "" -"We will also look at enum dispatch with an exercise involving points and " -"polygons." -msgstr "我们还将通过点和多边形的相关练习，探讨枚举调度情况。" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - - - - - - - - " +"- - - - -.\n" +": : : :\n" +": " +"list : : :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" +": | Element | 1 | o--+----+-----+--->| Element | 2 | o--+--->| Nil | // " +"| // | :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - - - - - - - - " +"- - - - -'\n" +"```" +msgstr "" +"```bob\n" +" 栈 堆\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"（无法访问）\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" -#: src/exercises/day-3/simple-gui.md:1 -#: src/exercises/day-3/solutions-morning.md:3 +#: src/smart-pointers/box.md:63 #, fuzzy -msgid "Drawing A Simple GUI" -msgstr "一个简单的 GUI 库" - -#: src/exercises/day-3/simple-gui.md:3 msgid "" -"Let us design a classical GUI library using our new knowledge of traits and " -"trait objects. We'll only implement the drawing of it (as text) for " -"simplicity." +"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " +"not null." msgstr "" +"在 C++ 中，`Box` 与 `std::unique_ptr` 类似，除了它一定会不为 null 以外。" -#: src/exercises/day-3/simple-gui.md:6 -msgid "We will have a number of widgets in our library:" -msgstr "我们的库中有许多 widget：" +#: src/smart-pointers/box.md:65 +msgid "A `Box` can be useful when you:" +msgstr "在以下情况下，`Box` 可能会很实用：" -#: src/exercises/day-3/simple-gui.md:8 -msgid "`Window`: has a `title` and contains other widgets." -msgstr "“Window”：具有“title”且包含其他 widget。" +#: src/smart-pointers/box.md:66 +msgid "" +"have a type whose size that can't be known at compile time, but the Rust " +"compiler wants to know an exact size." +msgstr "在编译时间遇到无法知晓大小的类型，但 Rust 编译器需要知道确切大小。" -#: src/exercises/day-3/simple-gui.md:9 +#: src/smart-pointers/box.md:68 msgid "" -"`Button`: has a `label`. In reality, it would also take a callback function " -"to allow the program to do something when the button is clicked but we won't " -"include that since we're only drawing the GUI." +"want to transfer ownership of a large amount of data. To avoid copying large " +"amounts of data on the stack, instead store the data on the heap in a `Box` " +"so only the pointer is moved." msgstr "" +"想要转让大量数据的所有权。为避免在堆栈上复制大量数据，请改为将数据存储在 " +"`Box` 中的堆上，以便仅移动指针。" -#: src/exercises/day-3/simple-gui.md:12 -msgid "`Label`: has a `label`." -msgstr "“Label”：具有“label”。" - -#: src/exercises/day-3/simple-gui.md:14 -msgid "The widgets will implement a `Widget` trait, see below." -msgstr "这些 widget 将实现“Widget”trait，如下所示。" +#: src/smart-pointers/box.md:72 +#, fuzzy +msgid "" +"If `Box` was not used and we attempted to embed a `List` directly into the " +"`List`, the compiler would not compute a fixed size of the struct in memory " +"(`List` would be of infinite size)." +msgstr "" +"如果这里未使用 `Box`，且我们曾尝试将一个 `List` 直接嵌入 `List`， 编译器就不" +"会计算内存中结构体的固定大小，结构体看起来会像是无限大。" -#: src/exercises/day-3/simple-gui.md:16 +#: src/smart-pointers/box.md:76 msgid "" -"Copy the code below to , fill in the missing " -"`draw_into` methods so that you implement the `Widget` trait:" +"`Box` solves this problem as it has the same size as a regular pointer and " +"just points at the next element of the `List` in the heap." msgstr "" -"将以下代码复制到 ，然后填入缺少的“draw_into”方" -"法，以便实现“Widget”trait：" +"`Box` 大小与一般指针相同，并且只会指向堆中的下一个 `List` 元素， 因此可以解决" +"这个问题。" -#: src/exercises/day-3/simple-gui.md:19 +#: src/smart-pointers/box.md:79 msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_imports, unused_variables, dead_code)]\n" -"\n" -"pub trait Widget {\n" -" /// Natural width of `self`.\n" -" fn width(&self) -> usize;\n" -"\n" -" /// Draw the widget into a buffer.\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write);\n" -"\n" -" /// Draw the widget on standard output.\n" -" fn draw(&self) {\n" -" let mut buffer = String::new();\n" -" self.draw_into(&mut buffer);\n" -" println!(\"{buffer}\");\n" -" }\n" -"}\n" -"\n" -"pub struct Label {\n" -" label: String,\n" -"}\n" -"\n" -"impl Label {\n" -" fn new(label: &str) -> Label {\n" -" Label {\n" -" label: label.to_owned(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Button {\n" -" label: Label,\n" -"}\n" -"\n" -"impl Button {\n" -" fn new(label: &str) -> Button {\n" -" Button {\n" -" label: Label::new(label),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Window {\n" -" title: String,\n" -" widgets: Vec>,\n" -"}\n" -"\n" -"impl Window {\n" -" fn new(title: &str) -> Window {\n" -" Window {\n" -" title: title.to_owned(),\n" -" widgets: Vec::new(),\n" -" }\n" -" }\n" -"\n" -" fn add_widget(&mut self, widget: Box) {\n" -" self.widgets.push(widget);\n" -" }\n" -"\n" -" fn inner_width(&self) -> usize {\n" -" std::cmp::max(\n" -" self.title.chars().count(),\n" -" self.widgets.iter().map(|w| w.width()).max().unwrap_or(0),\n" -" )\n" -" }\n" -"}\n" -"\n" -"\n" -"impl Widget for Label {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Widget for Button {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Widget for Window {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut window = Window::new(\"Rust GUI Demo 1.23\");\n" -" window.add_widget(Box::new(Label::new(\"This is a small text GUI demo." -"\")));\n" -" window.add_widget(Box::new(Button::new(\n" -" \"Click me!\"\n" -" )));\n" -" window.draw();\n" -"}\n" -"```" +"Remove the `Box` in the List definition and show the compiler error. " +"\"Recursive with indirection\" is a hint you might want to use a Box or " +"reference of some kind, instead of storing a value directly." msgstr "" +"将 `Box` 从 List 定义中移除后，画面上会显示编译器错误。如果您看到“Recursive " +"with indirection”错误消息，这是在提示您使用 Box 或其他类型的引用，而不是直接" +"储存值。" -#: src/exercises/day-3/simple-gui.md:128 -msgid "The output of the above program can be something simple like this:" -msgstr "上述程序的输出可能非常简单，例如：" +#: src/smart-pointers/box.md:85 +msgid "Niche Optimization" +msgstr "小众优化" -#: src/exercises/day-3/simple-gui.md:140 +#: src/smart-pointers/box.md:101 msgid "" -"If you want to draw aligned text, you can use the [fill/alignment](https://" -"doc.rust-lang.org/std/fmt/index.html#fillalignment) formatting operators. In " -"particular, notice how you can pad with different characters (here a `'/'`) " -"and how you can control alignment:" +"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This " +"allows the compiler to optimize the memory layout:" msgstr "" -"如果要绘制对齐的文本，可以使用[填充/对齐](https://doc.rust-lang.org/std/fmt/" -"index.html#fillalignment)格式设置运算符。需要特别注意的是您填充不同字符（此处" -"是“/”）的方式以及控制对齐的方式：" +"`Box` 不得为空，因此指针始终有效且非 `null`。这样， 编译器就可以优化内存布" +"局：" -#: src/exercises/day-3/simple-gui.md:145 +#: src/smart-pointers/box.md:104 +#, fuzzy msgid "" -"```rust,editable\n" -"fn main() {\n" -" let width = 10;\n" -" println!(\"left aligned: |{:/width$}|\", \"foo\");\n" -"}\n" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - -.\n" +": : : :\n" +": list : : :\n" +": +---------+----+----+ : : +---------+----+----+ :\n" +": | Element | 1 | o--+----+-----+--->| Element | 2 | // | :\n" +": +---------+----+----+ : : +---------+----+----+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - -'\n" "```" msgstr "" +"```bob\n" +" 栈 堆\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"（无法访问）\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" -#: src/exercises/day-3/simple-gui.md:154 +#: src/smart-pointers/rc.md:3 msgid "" -"Using such alignment tricks, you can for example produce output like this:" -msgstr "使用这些对齐技巧，您可以生成如下的输出内容：" +"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) is a reference-" +"counted shared pointer. Use this when you need to refer to the same data " +"from multiple places:" +msgstr "" +"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) 是引用计数的共享指" +"针。如果您需要从多个位置 引用相同的数据，请使用此指针：" + +#: src/smart-pointers/rc.md:13 +msgid "\"a: {a}\"" +msgstr "" -#: src/exercises/day-3/points-polygons.md:1 -msgid "Polygon Struct" -msgstr "多边形结构体" +#: src/smart-pointers/rc.md:14 +msgid "\"b: {b}\"" +msgstr "" -#: src/exercises/day-3/points-polygons.md:3 +#: src/smart-pointers/rc.md:18 +#, fuzzy msgid "" -"We will create a `Polygon` struct which contain some points. Copy the code " -"below to and fill in the missing methods to " -"make the tests pass:" +"See [`Arc`](../concurrency/shared_state/arc.md) and [`Mutex`](https://doc." +"rust-lang.org/std/sync/struct.Mutex.html) if you are in a multi-threaded " +"context." msgstr "" -"我们将创建一个包含一些点的“Polygon”结构体。将以下代码复制到 ，然后填入缺少的方法，设法通过测试：" +"如果您在多线程情境中，请参阅 [`Arc`](https://doc.rust-lang.org/std/sync/" +"struct.Mutex.html)。" -#: src/exercises/day-3/points-polygons.md:7 +#: src/smart-pointers/rc.md:19 msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub struct Point {\n" -" // add fields\n" -"}\n" -"\n" -"impl Point {\n" -" // add methods\n" -"}\n" -"\n" -"pub struct Polygon {\n" -" // add fields\n" -"}\n" -"\n" -"impl Polygon {\n" -" // add methods\n" -"}\n" -"\n" -"pub struct Circle {\n" -" // add fields\n" -"}\n" -"\n" -"impl Circle {\n" -" // add methods\n" -"}\n" -"\n" -"pub enum Shape {\n" -" Polygon(Polygon),\n" -" Circle(Circle),\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" fn round_two_digits(x: f64) -> f64 {\n" -" (x * 100.0).round() / 100.0\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_magnitude() {\n" -" let p1 = Point::new(12, 13);\n" -" assert_eq!(round_two_digits(p1.magnitude()), 17.69);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_dist() {\n" -" let p1 = Point::new(10, 10);\n" -" let p2 = Point::new(14, 13);\n" -" assert_eq!(round_two_digits(p1.dist(p2)), 5.00);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_add() {\n" -" let p1 = Point::new(16, 16);\n" -" let p2 = p1 + Point::new(-4, 3);\n" -" assert_eq!(p2, Point::new(12, 19));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_left_most_point() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -" assert_eq!(poly.left_most_point(), Some(p1));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_iter() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -"\n" -" let points = poly.iter().cloned().collect::>();\n" -" assert_eq!(points, vec![Point::new(12, 13), Point::new(16, 16)]);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_shape_perimeters() {\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(Point::new(12, 13));\n" -" poly.add_point(Point::new(17, 11));\n" -" poly.add_point(Point::new(16, 16));\n" -" let shapes = vec![\n" -" Shape::from(poly),\n" -" Shape::from(Circle::new(Point::new(10, 20), 5)),\n" -" ];\n" -" let perimeters = shapes\n" -" .iter()\n" -" .map(Shape::perimeter)\n" -" .map(round_two_digits)\n" -" .collect::>();\n" -" assert_eq!(perimeters, vec![15.48, 31.42]);\n" -" }\n" -"}\n" -"\n" -"#[allow(dead_code)]\n" -"fn main() {}\n" -"```" +"You can _downgrade_ a shared pointer into a [`Weak`](https://doc.rust-lang." +"org/std/rc/struct.Weak.html) pointer to create cycles that will get dropped." msgstr "" +"您可以将共享指针_降级_为 [`Weak`](https://doc.rust-lang.org/std/rc/struct." +"Weak.html) 指针， 以便创建之后会被舍弃的循环引用。" -#: src/exercises/day-3/points-polygons.md:117 +#: src/smart-pointers/rc.md:29 msgid "" -"Since the method signatures are missing from the problem statements, the key " -"part of the exercise is to specify those correctly. You don't have to modify " -"the tests." -msgstr "" -"由于问题语句中缺少方法签名，因此练习的关键部分是正确指定这些内容。您无需修改" -"测试。" +"`Rc`'s count ensures that its contained value is valid for as long as there " +"are references." +msgstr "`Rc` 的计数可确保只要有引用，内含的值就会保持有效。" -#: src/exercises/day-3/points-polygons.md:120 -msgid "Other interesting parts of the exercise:" -msgstr "练习的其他有趣部分：" +#: src/smart-pointers/rc.md:31 +msgid "`Rc` in Rust is like `std::shared_ptr` in C++." +msgstr "Rust 中的“Rc”与 C++ 中的“std::shared_ptr”类似。" -#: src/exercises/day-3/points-polygons.md:122 +#: src/smart-pointers/rc.md:32 msgid "" -"Derive a `Copy` trait for some structs, as in tests the methods sometimes " -"don't borrow their arguments." -msgstr "为某些结构体派生“Copy”trait，因为在测试中，方法有时不借用它们的参数。" +"`Rc::clone` is cheap: it creates a pointer to the same allocation and " +"increases the reference count. Does not make a deep clone and can generally " +"be ignored when looking for performance issues in code." +msgstr "" +"`Rc::clone` 的成本很低：这个做法会创建指向相同分配的指针，并增加引用计数，而" +"不会产生深层的克隆，排查代码性能问题时通常可以忽略。" -#: src/exercises/day-3/points-polygons.md:123 +#: src/smart-pointers/rc.md:35 msgid "" -"Discover that `Add` trait must be implemented for two objects to be addable " -"via \"+\". Note that we do not discuss generics until Day 3." +"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " +"and returns a mutable reference." msgstr "" -"发现必须实现“Add”trait 才能通过“+”添加两个对象。请注意，我们在第 3 天之前不会" -"讨论泛型。" +"`make_mut` 实际上会在必要时克隆内部值（“clone-on-write”），并返回可变的引用。" -#: src/error-handling.md:3 -msgid "Error handling in Rust is done using explicit control flow:" -msgstr "Rust 中的错误处理是使用显式控制流来进行的：" +#: src/smart-pointers/rc.md:37 +msgid "Use `Rc::strong_count` to check the reference count." +msgstr "使用 `Rc::strong_count` 可查看引用计数。" -#: src/error-handling.md:5 -msgid "Functions that can have errors list this in their return type," -msgstr "包含错误的函数会在返回类型中列出相关信息。" +#: src/smart-pointers/rc.md:38 +#, fuzzy +msgid "" +"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " +"cycles that will be dropped properly (likely in combination with `RefCell`)." +msgstr "" +"`Rc::downgrade` 会向您提供 _弱引用计数_ 对象， 以便创建之后会被适当舍弃的周期" +"（可能会与 `RefCell` 组合）。" -#: src/error-handling.md:6 -msgid "There are no exceptions." -msgstr "此规则没有例外。" +#: src/smart-pointers/exercise.md:3 +msgid "" +"A binary tree is a tree-type data structure where every node has two " +"children (left and right). We will create a tree where each node stores a " +"value. For a given node N, all nodes in a N's left subtree contain smaller " +"values, and all nodes in N's right subtree will contain larger values." +msgstr "" -#: src/error-handling/panics.md:3 -msgid "Rust will trigger a panic if a fatal error happens at runtime:" -msgstr "如果运行时发生严重错误，Rust 会触发 panic：" +#: src/smart-pointers/exercise.md:8 +msgid "Implement the following types, so that the given tests pass." +msgstr "" -#: src/error-handling/panics.md:5 +#: src/smart-pointers/exercise.md:10 msgid "" -"```rust,editable,should_panic\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" println!(\"v[100]: {}\", v[100]);\n" -"}\n" -"```" +"Extra Credit: implement an iterator over a binary tree that returns the " +"values in order." msgstr "" -#: src/error-handling/panics.md:12 -msgid "Panics are for unrecoverable and unexpected errors." -msgstr "Panic 用于指示不可恢复的意外错误。" +#: src/smart-pointers/exercise.md:14 src/smart-pointers/solution.md:5 +msgid "/// A node in the binary tree.\n" +msgstr "" -#: src/error-handling/panics.md:13 -msgid "Panics are symptoms of bugs in the program." -msgstr "Panic反映了程序中的 bug 问题。" +#: src/smart-pointers/exercise.md:21 src/smart-pointers/solution.md:13 +msgid "/// A possibly-empty subtree.\n" +msgstr "" -#: src/error-handling/panics.md:14 +#: src/smart-pointers/exercise.md:25 src/smart-pointers/solution.md:17 msgid "" -"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." -msgstr "如果崩溃不可接受，请使用不会触发 panic 的 API（例如 `Vec::get`）。" +"/// A container storing a set of values, using a binary tree.\n" +"///\n" +"/// If the same value is added multiple times, it is only stored once.\n" +msgstr "" -#: src/error-handling/panic-unwind.md:1 -msgid "Catching the Stack Unwinding" -msgstr "捕获堆栈展开" +#: src/smart-pointers/exercise.md:33 +msgid "// Implement `new`, `insert`, `len`, and `has`.\n" +msgstr "" -#: src/error-handling/panic-unwind.md:3 -msgid "" -"By default, a panic will cause the stack to unwind. The unwinding can be " -"caught:" -msgstr "默认情况下，panic 会导致堆栈展开。您可以捕获展开信息：" +#: src/smart-pointers/exercise.md:48 src/smart-pointers/solution.md:105 +msgid "// not a unique item\n" +msgstr "" -#: src/error-handling/panic-unwind.md:5 -msgid "" -"```rust,editable\n" -"use std::panic;\n" -"\n" -"fn main() {\n" -" let result = panic::catch_unwind(|| {\n" -" println!(\"hello!\");\n" -" });\n" -" assert!(result.is_ok());\n" -" \n" -" let result = panic::catch_unwind(|| {\n" -" panic!(\"oh no!\");\n" -" });\n" -" assert!(result.is_err());\n" -"}\n" -"```" +#: src/smart-pointers/solution.md:89 src/testing/googletest.md:11 +msgid "\"bar\"" msgstr "" -#: src/error-handling/panic-unwind.md:21 +#: src/borrowing/shared.md:3 +#, fuzzy msgid "" -"This can be useful in servers which should keep running even if a single " -"request crashes." -msgstr "" -"如果服务器需要持续运行（即使是在请求发生崩溃的情况下）， 此方法十分有用。" +"As we saw before, instead of transferring ownership when calling a function, " +"you can let a function _borrow_ the value:" +msgstr "调用函数时，你可以让 函数“借用”值，而不是转移所有权：" -#: src/error-handling/panic-unwind.md:23 -msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." -msgstr "如果您在 `Cargo.toml` 中设置了 `panic = 'abort'`，此方法不会生效。" +#: src/borrowing/shared.md:24 +msgid "The `add` function _borrows_ two points and returns a new point." +msgstr "`add` 函数“借用”两个点并返回一个新点。" -#: src/error-handling/result.md:1 -msgid "Structured Error Handling with `Result`" -msgstr "使用 `Result` 进行结构化错误处理" +#: src/borrowing/shared.md:25 +msgid "The caller retains ownership of the inputs." +msgstr "调用方会保留输入的所有权。" -#: src/error-handling/result.md:3 +#: src/borrowing/shared.md:29 msgid "" -"We have already seen the `Result` enum. This is used pervasively when errors " -"are expected as part of normal operation:" +"This slide is a review of the material on references from day 1, expanding " +"slightly to include function arguments and return values." msgstr "" -"在前面，我们看到了 `Result` 枚举。在遇到正常操作产生的预期错误时， 我们常会用" -"到此方法：" -#: src/error-handling/result.md:6 -msgid "" -"```rust,editable\n" -"use std::fs;\n" -"use std::io::Read;\n" -"\n" -"fn main() {\n" -" let file = fs::File::open(\"diary.txt\");\n" -" match file {\n" -" Ok(mut file) => {\n" -" let mut contents = String::new();\n" -" file.read_to_string(&mut contents);\n" -" println!(\"Dear diary: {contents}\");\n" -" },\n" -" Err(err) => {\n" -" println!(\"The diary could not be opened: {err}\");\n" -" }\n" -" }\n" -"}\n" -"```" -msgstr "" +#: src/borrowing/shared.md:34 +msgid "Notes on stack returns:" +msgstr "关于栈返回的说明：" -#: src/error-handling/result.md:27 +#: src/borrowing/shared.md:36 +#, fuzzy msgid "" -"As with `Option`, the successful value sits inside of `Result`, forcing the " -"developer to explicitly extract it. This encourages error checking. In the " -"case where an error should never happen, `unwrap()` or `expect()` can be " -"called, and this is a signal of the developer intent too." +"Demonstrate that the return from `add` is cheap because the compiler can " +"eliminate the copy operation. Change the above code to print stack addresses " +"and run it on the [Playground](https://play.rust-lang.org/?" +"version=stable&mode=release&edition=2021&gist=0cb13be1c05d7e3446686ad9947c4671) " +"or look at the assembly in [Godbolt](https://rust.godbolt.org/). In the " +"\"DEBUG\" optimization level, the addresses should change, while they stay " +"the same when changing to the \"RELEASE\" setting:" msgstr "" -"与 `Option` 方法相同，成功值位于 `Result` 方法内部， 开发者必须显示提取成功" -"值。因此，建议进行错误检查。在绝不应出现错误的情况下， 可以调用 `unwrap()` " -"或 `expect()` 方法，这也是一种开发者意向信号。" +"证明从 `add` 返回的开销很低，因为编译器可以消除复制操作。更改上述代码以输出栈" +"地址，并在 [Playground](https://play.rust-lang.org/) 上运行它。在“调试”优化级" +"别中，地址应发生变化，而在改成“发布”设置时保持不变：" + +#: src/borrowing/shared.md:62 +msgid "The Rust compiler can do return value optimization (RVO)." +msgstr "Rust 编译器能够执行返回值优化 (RVO)。" -#: src/error-handling/result.md:30 +#: src/borrowing/shared.md:63 +#, fuzzy msgid "" -"`Result` documentation is a recommended read. Not during the course, but it " -"is worth mentioning. It contains a lot of convenience methods and functions " -"that help functional-style programming. " +"In C++, copy elision has to be defined in the language specification because " +"constructors can have side effects. In Rust, this is not an issue at all. If " +"RVO did not happen, Rust will always perform a simple and efficient `memcpy` " +"copy." msgstr "" -"我们建议阅读 `Result` 文档。虽然课程中不会涉及该文档，但是有必要提到它。 该文" -"档中包含许多便捷的方法和函数，对于函数式编程很有帮助。" - -#: src/error-handling/try-operator.md:1 -msgid "Propagating Errors with `?`" -msgstr "使用 `?` 传播错误" +"在 C++ 中，必须在语言规范中定义复制省略，因为构造函数可能会有附带效应。在 " +"Rust 中，这完全不是问题。如果 RVO 未发生，Rust 将始终执行简单且高效的 " +"`memcpy` 复制。" -#: src/error-handling/try-operator.md:3 +#: src/borrowing/borrowck.md:3 +#, fuzzy msgid "" -"The try-operator `?` is used to return errors to the caller. It lets you " -"turn the common" -msgstr "try 操作符 `?` 用于将错误返回给调用方。它能把常用命令" +"Rust's _borrow checker_ puts constraints on the ways you can borrow values. " +"For a given value, at any time:" +msgstr "Rust 限制了借用值的方式：" -#: src/error-handling/try-operator.md:13 -msgid "into the much simpler" -msgstr "转换成更简单的命令" +#: src/borrowing/borrowck.md:6 +#, fuzzy +msgid "You can have one or more shared references to the value, _or_" +msgstr "在任何给定时间，你都可以有一个或多个 `&T` 值，或者" -#: src/error-handling/try-operator.md:19 +#: src/borrowing/borrowck.md:7 #, fuzzy -msgid "We can use this to simplify our error handling code:" -msgstr "我们可以用它来简化错误处理代码：" +msgid "You can have exactly one exclusive reference to the value." +msgstr "你可以有且只有一个 `&mut T` 值。" -#: src/error-handling/try-operator.md:21 +#: src/borrowing/borrowck.md:28 msgid "" -"```rust,editable\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let username_file_result = fs::File::open(path);\n" -" let mut username_file = match username_file_result {\n" -" Ok(file) => file,\n" -" Err(err) => return Err(err),\n" -" };\n" -"\n" -" let mut username = String::new();\n" -" match username_file.read_to_string(&mut username) {\n" -" Ok(_) => Ok(username),\n" -" Err(err) => Err(err),\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"alice\").unwrap();\n" -" let username = read_username(\"config.dat\");\n" -" println!(\"username or error: {username:?}\");\n" -"}\n" -"```" +"Note that the requirement is that conflicting references not _exist_ at the " +"same point. It does not matter where the reference is dereferenced." msgstr "" -#: src/error-handling/try-operator.md:50 -#: src/error-handling/converting-error-types-example.md:52 -msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." -msgstr "`username` 变量可以是 `Ok(string)` 或 `Err(error)`。" - -#: src/error-handling/try-operator.md:51 -#: src/error-handling/converting-error-types-example.md:53 +#: src/borrowing/borrowck.md:30 msgid "" -"Use the `fs::write` call to test out the different scenarios: no file, empty " -"file, file with username." +"The above code does not compile because `a` is borrowed as mutable (through " +"`c`) and as immutable (through `b`) at the same time." msgstr "" -"可以使用 `fs::write` 调用来测试不同的场景：没有文件、空文件、包含用户名的文" -"件。" +"上述代码无法编译，因为 `a` 同时作为可变值（通过 `c`）和不可变值（通过 `b`）被" +"借用。" -#: src/error-handling/try-operator.md:52 -#, fuzzy +#: src/borrowing/borrowck.md:32 msgid "" -"The return type of the function has to be compatible with the nested " -"functions it calls. For instance, a function returning a `Result` " -"can only apply the `?` operator on a function returning a `Result`. It cannot apply the `?` operator on a function returning an " -"`Option` or `Result` unless `OtherErr` implements " -"`From`. Reciprocally, a function returning an `Option` can only " -"apply the `?` operator on a function returning an `Option`." +"Move the `println!` statement for `b` before the scope that introduces `c` " +"to make the code compile." msgstr "" -"函数的返回值类型必须与其调用的嵌套函数兼容。例如，一个返回“Result\\”的函数只能对返回“Result\\”的函数应用“?”运算符。它无法对返" -"回“Option\n" -"\n" -"”或“Result\\”的函数应用“?”运算符，除非“OtherErr”实现“From\n" -"\n" -"”。相反地，返回“Option\n" -"\n" -"”的函数只能对返回“Option\n" -"\n" -"”的函数应用“?”运算符。" +"将`b` 的 `println!` 语句移到引入 `c` 的作用域之前，这段代码就可以编译。" -#: src/error-handling/try-operator.md:57 +#: src/borrowing/borrowck.md:34 msgid "" -"You can convert incompatible types into one another with the different " -"`Option` and `Result` methods such as `Option::ok_or`, `Result::ok`, " -"`Result::err`." +"After that change, the compiler realizes that `b` is only ever used before " +"the new mutable borrow of `a` through `c`. This is a feature of the borrow " +"checker called \"non-lexical lifetimes\"." msgstr "" -"您可以使用其他“Option”和“Result”方法（例如“Option::ok_or”“Result::" -"ok”“Result::err”）将不兼容的类型转换为另一种类型。" - -#: src/error-handling/converting-error-types.md:3 -msgid "" -"The effective expansion of `?` is a little more complicated than previously " -"indicated:" -msgstr "`?` 的有效展开比前面介绍的内容略微复杂一些：" - -#: src/error-handling/converting-error-types.md:9 -msgid "works the same as" -msgstr "效果等同于" +"这样更改后，编译器会发现 `b` 只在通过 `c` 对 `a` 进行新可变借用之前使用过。这" +"是借用检查器的一个功能，名为“非词法作用域生命周期”。" -#: src/error-handling/converting-error-types.md:18 +#: src/borrowing/borrowck.md:37 msgid "" -"The `From::from` call here means we attempt to convert the error type to the " -"type returned by the function:" +"The exclusive reference constraint is quite strong. Rust uses it to ensure " +"that data races do not occur. Rust also _relies_ on this constraint to " +"optimize code. For example, a value behind a shared reference can be safely " +"cached in a register for the lifetime of that reference." msgstr "" -"此处的 `From::from` 调用表示，我们尝试将错误类型转换为 函数返回的类型：" -#: src/error-handling/converting-error-types-example.md:3 +#: src/borrowing/borrowck.md:41 msgid "" -"```rust,editable\n" -"use std::error::Error;\n" -"use std::fmt::{self, Display, Formatter};\n" -"use std::fs::{self, File};\n" -"use std::io::{self, Read};\n" -"\n" -"#[derive(Debug)]\n" -"enum ReadUsernameError {\n" -" IoError(io::Error),\n" -" EmptyUsername(String),\n" -"}\n" -"\n" -"impl Error for ReadUsernameError {}\n" -"\n" -"impl Display for ReadUsernameError {\n" -" fn fmt(&self, f: &mut Formatter) -> fmt::Result {\n" -" match self {\n" -" Self::IoError(e) => write!(f, \"IO error: {e}\"),\n" -" Self::EmptyUsername(filename) => write!(f, \"Found no username " -"in {filename}\"),\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl From for ReadUsernameError {\n" -" fn from(err: io::Error) -> ReadUsernameError {\n" -" ReadUsernameError::IoError(err)\n" -" }\n" -"}\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::with_capacity(100);\n" -" File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(ReadUsernameError::EmptyUsername(String::from(path)));\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" let username = read_username(\"config.dat\");\n" -" println!(\"username or error: {username:?}\");\n" -"}\n" -"```" +"The borrow checker is designed to accommodate many common patterns, such as " +"taking exclusive references to different fields in a struct at the same " +"time. But, there are some situations where it doesn't quite \"get it\" and " +"this often results in \"fighting with the borrow checker.\"" msgstr "" -#: src/error-handling/converting-error-types-example.md:55 +#: src/borrowing/interior-mutability.md:7 msgid "" -"It is good practice for all error types that don't need to be `no_std` to " -"implement `std::error::Error`, which requires `Debug` and `Display`. The " -"`Error` crate for `core` is only available in [nightly](https://github.com/" -"rust-lang/rust/issues/103765), so not fully `no_std` compatible yet." +"Rust provides a few safe means of modifying a value given only a shared " +"reference to that value. All of these replace compile-time checks with " +"runtime checks." msgstr "" -"对所有不需要是“no_std”的错误类型来说，实现“std::error::Error”是一种很好的做" -"法，而这需要“Debug”和“Display”。“core”的“Error”crate 仅在 [nightly](https://" -"github.com/rust-lang/rust/issues/103765) 提供，因此尚未与“no_std”完全兼容。" -#: src/error-handling/converting-error-types-example.md:57 +#: src/borrowing/interior-mutability.md:11 +msgid "`Cell` and `RefCell`" +msgstr "“Cell”和“RefCell”" + +#: src/borrowing/interior-mutability.md:13 #, fuzzy msgid "" -"It's generally helpful for them to implement `Clone` and `Eq` too where " -"possible, to make life easier for tests and consumers of your library. In " -"this case we can't easily do so, because `io::Error` doesn't implement them." +"[`Cell`](https://doc.rust-lang.org/std/cell/struct.Cell.html) and [`RefCell`]" +"(https://doc.rust-lang.org/std/cell/struct.RefCell.html) implement what Rust " +"calls _interior mutability:_ mutation of values in an immutable context." msgstr "" -"对所有错误类型实现 `std::error::Error` 是一种很好的做法，而这需要结合使用 " -"`Debug` 和 `Display` 方法。 通常，在可能的情况下实现 `Clone` 和 `Eq` 也十分有" -"益， 可以让库的测试和使用变得更加简单。在本例中，我们无法轻松做到这一点， 因" -"为 `io::Error` 不能实现这些方法。" +"您可以使用 [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 " +"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html) 对 `u8` 来源" +"进行抽象化处理：" -#: src/error-handling/deriving-error-enums.md:3 +#: src/borrowing/interior-mutability.md:18 msgid "" -"The [thiserror](https://docs.rs/thiserror/) crate is a popular way to create " -"an error enum like we did on the previous page:" +"`Cell` is typically used for simple types, as it requires copying or moving " +"values. More complex interior types typically use `RefCell`, which tracks " +"shared and exclusive references at runtime and panics if they are misused." msgstr "" -"[thiserror](https://docs.rs/thiserror/) crate 是创建错误枚举的常用方法， 就像" -"前一页中提供的示例一样：" +"“Cell”通常用于简单类型，因为它需要复制或移动值。更复杂的内部类型通常使" +"用“RefCell”，它会在运行时跟踪已共享和专有的引用，并在这些引用被滥用时 panic。" -#: src/error-handling/deriving-error-enums.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Debug, Error)]\n" -"enum ReadUsernameError {\n" -" #[error(\"Could not read: {0}\")]\n" -" IoError(#[from] io::Error),\n" -" #[error(\"Found no username in {0}\")]\n" -" EmptyUsername(String),\n" -"}\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::new();\n" -" fs::File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(ReadUsernameError::EmptyUsername(String::from(path)));\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err}\"),\n" -" }\n" -"}\n" -"```" +#: src/borrowing/interior-mutability.md:50 +msgid "\"graph: {root:#?}\"" msgstr "" -#: src/error-handling/deriving-error-enums.md:39 -msgid "" -"`thiserror`'s derive macro automatically implements `std::error::Error`, and " -"optionally `Display` (if the `#[error(...)]` attributes are provided) and " -"`From` (if the `#[from]` attribute is added). It also works for structs." +#: src/borrowing/interior-mutability.md:51 +msgid "\"graph sum: {}\"" msgstr "" -"`thiserror` 的派生宏会自动实现 `std::error::Error`，并且可以选择性地实现 " -"`Display` （如果提供了 `#[error(...)]` 属性）和 `From`（如果添加了 `#[from]` " -"属性）。 此规则也适用于结构体。" - -#: src/error-handling/deriving-error-enums.md:43 -msgid "It doesn't affect your public API, which makes it good for libraries." -msgstr "但是，此规则不会影响公共 API，对于库而言，这非常理想。" -#: src/error-handling/dynamic-errors.md:3 +#: src/borrowing/interior-mutability.md:57 msgid "" -"Sometimes we want to allow any type of error to be returned without writing " -"our own enum covering all the different possibilities. `std::error::Error` " -"makes this easy." +"If we were using `Cell` instead of `RefCell` in this example, we would have " +"to move the `Node` out of the `Rc` to push children, then move it back in. " +"This is safe because there's always one, un-referenced value in the cell, " +"but it's not ergonomic." msgstr "" -"有时，我们需要允许返回任意类型的错误，但又不想自己手动编写枚举来涵盖所有不同" -"的可能性。 `std::error::Error` 可以让我们轻松做到这一点。" +"在此示例中，如果我们使用的是“Cell”而非“RefCell”，则必须将“Node”从“Rc”中移出以" +"推送子项，然后再将其移回原位。这是安全的做法，因为单元格中总是有一个未引用的" +"值，但这不符合人体工程学。" -#: src/error-handling/dynamic-errors.md:6 +#: src/borrowing/interior-mutability.md:61 msgid "" -"```rust,editable,compile_fail\n" -"use std::fs;\n" -"use std::io::Read;\n" -"use thiserror::Error;\n" -"use std::error::Error;\n" -"\n" -"#[derive(Clone, Debug, Eq, Error, PartialEq)]\n" -"#[error(\"Found no username in {0}\")]\n" -"struct EmptyUsernameError(String);\n" -"\n" -"fn read_username(path: &str) -> Result> {\n" -" let mut username = String::new();\n" -" fs::File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(EmptyUsernameError(String::from(path)).into());\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err}\"),\n" -" }\n" -"}\n" -"```" +"To do anything with a Node, you must call a `RefCell` method, usually " +"`borrow` or `borrow_mut`." msgstr "" +"如需使用 Node 执行任何操作，您必须调用“RefCell”方法，通常" +"为“borrow”或“borrow_mut”。" -#: src/error-handling/dynamic-errors.md:36 +#: src/borrowing/interior-mutability.md:63 msgid "" -"This saves on code, but gives up the ability to cleanly handle different " -"error cases differently in the program. As such it's generally not a good " -"idea to use `Box` in the public API of a library, but it can be a " -"good option in a program where you just want to display the error message " -"somewhere." +"Demonstrate that reference loops can be created by adding `root` to `subtree." +"children` (don't try to print it!)." msgstr "" -"虽然这可以省却编写代码的麻烦，但也会导致我们无法在程序中以不同的方式正常处理" -"不同的 错误情况。因此，在库的公共 API 中使用 `Box` 通常不是一个好" -"主意。 但是对于您只需要在某处显示错误消息的程序来说，这不失为一个 很好的选" -"择。" +"演示可以通过向“subtree.children”添加“root”来创建引用循环（不要尝试输出" +"它！）。" -#: src/error-handling/error-contexts.md:3 +#: src/borrowing/interior-mutability.md:65 msgid "" -"The widely used [anyhow](https://docs.rs/anyhow/) crate can help you add " -"contextual information to your errors and allows you to have fewer custom " -"error types:" +"To demonstrate a runtime panic, add a `fn inc(&mut self)` that increments " +"`self.value` and calls the same method on its children. This will panic in " +"the presence of the reference loop, with `thread 'main' panicked at 'already " +"borrowed: BorrowMutError'`." msgstr "" -"广泛使用的 [anyhow](https://docs.rs/anyhow/) crate 可以帮助我们为错误添加 背" -"景信息，并减少自定义错误类型的 数量。" +"为了演示运行时 panic，请添加一个会递增“self.value”并以相同方法调用其子项" +"的“fn inc(&mut self)”。如果存在引用循环，就会 panic，并且“thread”“main”会" +"因“already borrowed: BorrowMutError”而 panic。" -#: src/error-handling/error-contexts.md:7 +#: src/borrowing/exercise.md:3 msgid "" -"```rust,editable,compile_fail\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"use anyhow::{Context, Result, bail};\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::with_capacity(100);\n" -" fs::File::open(path)\n" -" .with_context(|| format!(\"Failed to open {path}\"))?\n" -" .read_to_string(&mut username)\n" -" .context(\"Failed to read\")?;\n" -" if username.is_empty() {\n" -" bail!(\"Found no username in {path}\");\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err:?}\"),\n" -" }\n" -"}\n" -"```" +"You're working on implementing a health-monitoring system. As part of that, " +"you need to keep track of users' health statistics." msgstr "" +"你正在实现一个健康监控系统。作为其中的一部分，你需要对用户的健康统计数据进行" +"追踪。" -#: src/error-handling/error-contexts.md:35 -#, fuzzy -msgid "`anyhow::Result` is a type alias for `Result`." -msgstr "“anyhow::Result" - -#: src/error-handling/error-contexts.md:36 +#: src/borrowing/exercise.md:6 #, fuzzy msgid "" -"`anyhow::Error` is essentially a wrapper around `Box`. As such " -"it's again generally not a good choice for the public API of a library, but " -"is widely used in applications." -msgstr "”是“Result\\”的类型别名。" +"You'll start with a stubbed function in an `impl` block as well as a `User` " +"struct definition. Your goal is to implement the stubbed out method on the " +"`User` `struct` defined in the `impl` block." +msgstr "" +"`User` 结构体的定义和 `impl` 块中一些函数的框架已经给出。你的目标是实现在 " +"`impl` 块中定义的 `User` `struct` 的方法。" -#: src/error-handling/error-contexts.md:38 +#: src/borrowing/exercise.md:10 #, fuzzy msgid "" -"Actual error type inside of it can be extracted for examination if necessary." -msgstr "“anyhow::Error”本质上是“Box" +"Copy the code below to and fill in the missing " +"method:" +msgstr "将以下代码复制到 ，并填充缺失的方法：" -#: src/error-handling/error-contexts.md:39 -#, fuzzy +#: src/borrowing/exercise.md:51 msgid "" -"Functionality provided by `anyhow::Result` may be familiar to Go " -"developers, as it provides similar usage patterns and ergonomics to `(T, " -"error)` from Go." +"\"Update a user's statistics based on measurements from a visit to the " +"doctor\"" msgstr "" -"”的封装容器。因此，就像前面提到的那样，在库的公共 API 中 使用它通常不是一个好" -"主意。但是它广泛用于应用中。\n" -"\n" -"如果需要，可以提取其内部的实际错误类型进行检查。\n" -"\n" -"Go 开发者可能会十分熟悉 `anyhow::Result` 提供的功能， 因为它的使用模式和工" -"效学设计与 Go 的 `(T, error)` 方法十分相似。" -#: src/testing.md:3 -msgid "Rust and Cargo come with a simple unit test framework:" -msgstr "Rust 和 Cargo 随附了一个简单的单元测试框架：" +#: src/borrowing/exercise.md:56 src/borrowing/exercise.md:62 +#: src/borrowing/exercise.md:68 src/borrowing/solution.md:58 +#: src/borrowing/solution.md:64 src/borrowing/solution.md:70 +#: src/android/build-rules/library.md:44 src/android/aidl/client.md:22 +msgid "\"Bob\"" +msgstr "" -#: src/testing.md:5 -msgid "Unit tests are supported throughout your code." -msgstr "单元测试在您的整个代码中都受支持。" +#: src/borrowing/exercise.md:57 src/borrowing/solution.md:59 +msgid "\"I'm {} and my age is {}\"" +msgstr "" -#: src/testing.md:7 -msgid "Integration tests are supported via the `tests/` directory." -msgstr "您可以通过 `tests/` 目录来支持集成测试。" +#: src/slices-and-lifetimes/slices.md:1 +msgid "Slices" +msgstr "切片" -#: src/testing/unit-tests.md:3 -msgid "Mark unit tests with `#[test]`:" -msgstr "使用 `#[test]` 标记单元测试：" +#: src/slices-and-lifetimes/slices.md:3 +msgid "A slice gives you a view into a larger collection:" +msgstr "切片 (slice) 的作用是提供对集合 (collection) 的视图 (view):" -#: src/testing/unit-tests.md:5 -msgid "" -"```rust,editable,ignore\n" -"fn first_word(text: &str) -> &str {\n" -" match text.find(' ') {\n" -" Some(idx) => &text[..idx],\n" -" None => &text,\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty() {\n" -" assert_eq!(first_word(\"\"), \"\");\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_word() {\n" -" assert_eq!(first_word(\"Hello\"), \"Hello\");\n" -"}\n" -"\n" -"#[test]\n" -"fn test_multiple_words() {\n" -" assert_eq!(first_word(\"Hello World\"), \"Hello\");\n" -"}\n" -"```" -msgstr "" +#: src/slices-and-lifetimes/slices.md:18 +msgid "Slices borrow data from the sliced type." +msgstr "切片从被切片的类型中借用 (borrow) 数据。" -#: src/testing/unit-tests.md:29 -msgid "Use `cargo test` to find and run the unit tests." -msgstr "使用 `cargo test` 查找并运行单元测试。" +#: src/slices-and-lifetimes/slices.md:19 +#, fuzzy +msgid "Question: What happens if you modify `a[3]` right before printing `s`?" +msgstr "请思考：如果我们改变 `a[3]`，将会产生怎样的后果？" -#: src/testing/test-modules.md:3 +#: src/slices-and-lifetimes/slices.md:23 +#, fuzzy msgid "" -"Unit tests are often put in a nested module (run tests on the [Playground]" -"(https://play.rust-lang.org/)):" -msgstr "" -"单元测试通常会放在嵌套模块中（在 [Playground](https://play.rust-lang.org/) 上" -"运行测试）：" +"We create a slice by borrowing `a` and specifying the starting and ending " +"indexes in brackets." +msgstr "创建切片时，我们借用了 `a` ，并在方括号中标明了起始和结尾下标。" -#: src/testing/test-modules.md:6 +#: src/slices-and-lifetimes/slices.md:26 +#, fuzzy msgid "" -"```rust,editable\n" -"fn helper(a: &str, b: &str) -> String {\n" -" format!(\"{a} {b}\")\n" -"}\n" -"\n" -"pub fn main() {\n" -" println!(\"{}\", helper(\"Hello\", \"World\"));\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" #[test]\n" -" fn test_helper() {\n" -" assert_eq!(helper(\"foo\", \"bar\"), \"foo bar\");\n" -" }\n" -"}\n" -"```" +"If the slice starts at index 0, Rust’s range syntax allows us to drop the " +"starting index, meaning that `&a[0..a.len()]` and `&a[..a.len()]` are " +"identical." msgstr "" +"如果切片的起始下标为 0， Rust 语法允许我们省略起始下标。比如说 `&a[0..a." +"len()]` 与 `&a[..a.len()]` 是等价的。" -#: src/testing/test-modules.md:26 -msgid "This lets you unit test private helpers." -msgstr "这样一来，您可以对专用帮助程序进行单元测试。" - -#: src/testing/test-modules.md:27 -msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." -msgstr "仅当您运行 `cargo test` 时，`#[cfg(test)]` 属性才有效。" +#: src/slices-and-lifetimes/slices.md:30 +#, fuzzy +msgid "" +"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " +"identical." +msgstr "" +"结尾下标也可以用相同方式省略。比如说 `&a[2..a.len()]` 和 `&a[2..]` 是等价的。" -#: src/testing/doc-tests.md:3 -msgid "Rust has built-in support for documentation tests:" -msgstr "Rust 本身就支持文档测试：" +#: src/slices-and-lifetimes/slices.md:33 +#, fuzzy +msgid "" +"To easily create a slice of the full array, we can therefore use `&a[..]`." +msgstr "因此，我们可以用 `&a[..]` 来创建包含整个数组的切片。" -#: src/testing/doc-tests.md:5 +#: src/slices-and-lifetimes/slices.md:35 +#, fuzzy msgid "" -"```rust\n" -"/// Shortens a string to the given length.\n" -"///\n" -"/// ```\n" -"/// # use playground::shorten_string;\n" -"/// assert_eq!(shorten_string(\"Hello World\", 5), \"Hello\");\n" -"/// assert_eq!(shorten_string(\"Hello World\", 20), \"Hello World\");\n" -"/// ```\n" -"pub fn shorten_string(s: &str, length: usize) -> &str {\n" -" &s[..std::cmp::min(length, s.len())]\n" -"}\n" -"```" +"`s` is a reference to a slice of `i32`s. Notice that the type of `s` " +"(`&[i32]`) no longer mentions the array length. This allows us to perform " +"computation on slices of different sizes." msgstr "" +"切片会从另外一个对象中借用数据。在这个例子中， `a` 必须在其切片存活时保持存活" +"（处于作用域中）。" -#: src/testing/doc-tests.md:18 -msgid "Code blocks in `///` comments are automatically seen as Rust code." -msgstr "`///` 注释中的代码块会自动被视为 Rust 代码。" - -#: src/testing/doc-tests.md:19 -msgid "The code will be compiled and executed as part of `cargo test`." -msgstr "代码会作为 `cargo test` 的一部分进行编译和执行。" +#: src/slices-and-lifetimes/slices.md:39 +#, fuzzy +msgid "" +"Slices always borrow from another object. In this example, `a` has to remain " +"'alive' (in scope) for at least as long as our slice." +msgstr "" +"关于修改 `a[3]` 的问题可能会引发精彩的讨论。正确答案是：为了保证内存安全，在" +"创建切片后，我们不能通过 `a` 来修改数据。不过我们可以通过 `a` 或者 `s` 来读取" +"数据。我们将会在“借用”章节着重介绍这个内容。" -#: src/testing/doc-tests.md:20 +#: src/slices-and-lifetimes/slices.md:42 +#, fuzzy msgid "" -"Adding `# ` in the code will hide it from the docs, but will still compile/" -"run it." +"The question about modifying `a[3]` can spark an interesting discussion, but " +"the answer is that for memory safety reasons you cannot do it through `a` at " +"this point in the execution, but you can read the data from both `a` and `s` " +"safely. It works before you created the slice, and again after the " +"`println`, when the slice is no longer used." msgstr "" +"关于修改“a\\[3\\]”的问题可能会引发一些有趣的讨论，但正解是，出于内存安全方面" +"的原因，您无法在执行作业的这个时间点通过“a”来进行此修改，但可以从“a”和“s”安全" +"地读取数据。它会在您创建 Slice 之前运作，在“println”之后（不再使用 Slice 时）" +"再次运作。更多详情会在“借用检查器”部分中加以说明。" -#: src/testing/doc-tests.md:21 +#: src/slices-and-lifetimes/str.md:7 msgid "" -"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" -"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." +"We can now understand the two string types in Rust: `&str` is almost like " +"`&[char]`, but with its data stored in a variable-length encoding (UTF-8)." msgstr "" -"在 [Rust Playground](https://play.rust-lang.org/?" -"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0) " -"上测试上述代码。" -#: src/testing/integration-tests.md:3 -msgid "If you want to test your library as a client, use an integration test." -msgstr "如果您想要以客户的身份测试您的库，请使用集成测试。" +#: src/slices-and-lifetimes/str.md:13 +msgid "\"s1: {s1}\"" +msgstr "" -#: src/testing/integration-tests.md:5 -msgid "Create a `.rs` file under `tests/`:" -msgstr "在 `tests/` 下方创建一个 `.rs` 文件：" +#: src/slices-and-lifetimes/str.md:15 +#, fuzzy +msgid "\"Hello \"" +msgstr "Hello World!" -#: src/testing/integration-tests.md:16 -msgid "These tests only have access to the public API of your crate." -msgstr "这些测试只能使用您的 crate 的公共 API。" +#: src/slices-and-lifetimes/str.md:21 +msgid "\"s3: {s3}\"" +msgstr "" -#: src/testing/useful-crates.md:1 -msgid "Useful crates for writing tests" -msgstr "用于编写测试的实用 crate" +#: src/slices-and-lifetimes/str.md:25 +msgid "Rust terminology:" +msgstr "Rust 术语：" -#: src/testing/useful-crates.md:3 -msgid "Rust comes with only basic support for writing tests." -msgstr "Rust 仅为编写测试提供基本支持。" +#: src/slices-and-lifetimes/str.md:27 +msgid "`&str` an immutable reference to a string slice." +msgstr "`&str` 是一个指向字符串片段的不可变引用。" -#: src/testing/useful-crates.md:5 -msgid "Here are some additional crates which we recommend for writing tests:" -msgstr "下面列出了我们建议在编写测试时使用的一些其他 crate：" +#: src/slices-and-lifetimes/str.md:28 +msgid "`String` a mutable string buffer." +msgstr "`String` 是一个可变字符串缓冲区。" -#: src/testing/useful-crates.md:7 +#: src/slices-and-lifetimes/str.md:32 +#, fuzzy msgid "" -"[googletest](https://docs.rs/googletest): Comprehensive test assertion " -"library in the tradition of GoogleTest for C++." +"`&str` introduces a string slice, which is an immutable reference to UTF-8 " +"encoded string data stored in a block of memory. String literals " +"(`”Hello”`), are stored in the program’s binary." msgstr "" -"[googletest](https://docs.rs/googletest)：遵从 GoogleTest for C++ 传统的综合" -"测试断言库。" +"`&str` 引入了一个字符串切片，它是一个指向保存在内存块中的 UTF-8 编码字符串数" +"据的不可变引用。 字符串字面量（`”Hello”`）会保存在程序的二进制文件中。" -#: src/testing/useful-crates.md:8 -msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." -msgstr "[proptest](https://docs.rs/proptest)：基于属性的测试，适用于 Rust。" +#: src/slices-and-lifetimes/str.md:36 +msgid "" +"Rust’s `String` type is a wrapper around a vector of bytes. As with a " +"`Vec`, it is owned." +msgstr "" +"Rust 的 `String` 类型是一个字节 vector 的封装。和 `Vec` 一样，它是拥有所有" +"权的。" -#: src/testing/useful-crates.md:9 +#: src/slices-and-lifetimes/str.md:39 +#, fuzzy msgid "" -"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " -"tests." -msgstr "[rstest](https://docs.rs/rstest)：支持固件和参数化测试。" +"As with many other types `String::from()` creates a string from a string " +"literal; `String::new()` creates a new empty string, to which string data " +"can be added using the `push()` and `push_str()` methods." +msgstr "" +"和其他类型一样，`String::from()` 会从字符串字面量创建一个字符串；`String::" +"new()` 会创建一个新的空字符串， 之后可以使用 `push()` 和 `push_str()` 方法" +"向其中添加字符串数据。" -#: src/unsafe.md:3 -msgid "The Rust language has two parts:" -msgstr "Rust 语言包含两个部分：" +#: src/slices-and-lifetimes/str.md:43 +#, fuzzy +msgid "" +"The `format!()` macro is a convenient way to generate an owned string from " +"dynamic values. It accepts the same format specification as `println!()`." +msgstr "" +"`format!()` 宏可以方便地动态生成拥有所有权的字符串。它接受和 `println!()` 相" +"同的格式规范。" -#: src/unsafe.md:5 -msgid "**Safe Rust:** memory safe, no undefined behavior possible." -msgstr "\\*\\*安全 Rust：\\*\\*内存安全，没有潜在的未定义行为。" +#: src/slices-and-lifetimes/str.md:46 +msgid "" +"You can borrow `&str` slices from `String` via `&` and optionally range " +"selection. If you select a byte range that is not aligned to character " +"boundaries, the expression will panic. The `chars` iterator iterates over " +"characters and is preferred over trying to get character boundaries right." +msgstr "" -#: src/unsafe.md:6 +#: src/slices-and-lifetimes/str.md:51 +#, fuzzy msgid "" -"**Unsafe Rust:** can trigger undefined behavior if preconditions are " -"violated." -msgstr "\\*\\*不安全 Rust：\\*\\*如果违反了前提条件，可能会触发未定义的行为。" +"For C++ programmers: think of `&str` as `std::string_view` from C++, but the " +"one that always points to a valid string in memory. Rust `String` is a rough " +"equivalent of `std::string` from C++ (main difference: it can only contain " +"UTF-8 encoded bytes and will never use a small-string optimization)." +msgstr "" +"对于 C++ 程序员：可以把 `&str` 当作 C++ 中的 `const char*`，但是它总是指向内" +"存中的一个有效字符串。 Rust 的 `String` 大致相当于 C++ 中 `std::string` " +"（主要区别：它只能包含 UTF-8 编码的字节， 并且永远不会使用小字符串优化" +"（small-string optimization））。" + +#: src/slices-and-lifetimes/str.md:56 +#, fuzzy +msgid "Byte strings literals allow you to create a `&[u8]` value directly:" +msgstr "字节串可以用于直接创建 `&[u8]` 类型的值：" -#: src/unsafe.md:8 +#: src/slices-and-lifetimes/lifetime-annotations.md:3 msgid "" -"We will be seeing mostly safe Rust in this course, but it's important to " -"know what Unsafe Rust is." +"A reference has a _lifetime_, which must not \"outlive\" the value it refers " +"to. This is verified by the borrow checker." msgstr "" -"本课程中出现的大多为“安全 Rust”，但是了解“不安全 Rust”的定义 非常重要。" -#: src/unsafe.md:11 +#: src/slices-and-lifetimes/lifetime-annotations.md:6 msgid "" -"Unsafe code is usually small and isolated, and its correctness should be " -"carefully documented. It is usually wrapped in a safe abstraction layer." +"The lifetime can be implicit - this is what we have seen so far. Lifetimes " +"can also be explicit: `&'a Point`, `&'document str`. Lifetimes start with " +"`'` and `'a` is a typical default name. Read `&'a Point` as \"a borrowed " +"`Point` which is valid for at least the lifetime `a`\"." msgstr "" -"不安全的代码通常内容很少而且与其他代码隔离， 其正确性也应得到仔细记录。这类代" -"码通常封装在安全的抽象层中。" -#: src/unsafe.md:14 -msgid "Unsafe Rust gives you access to five new capabilities:" -msgstr "不安全 Rust 提供了五种新功能：" +#: src/slices-and-lifetimes/lifetime-annotations.md:11 +#, fuzzy +msgid "" +"Lifetimes are always inferred by the compiler: you cannot assign a lifetime " +"yourself. Explicit lifetime annotations create constraints where there is " +"ambiguity; the compiler verifies that there is a valid solution." +msgstr "生命周期注释会创建约束条件；编译器会验证 是否存在有效的解决方案。" -#: src/unsafe.md:16 -msgid "Dereference raw pointers." -msgstr "解引用原始指针。" +#: src/slices-and-lifetimes/lifetime-annotations.md:15 +msgid "" +"Lifetimes become more complicated when considering passing values to and " +"returning values from functions." +msgstr "" -#: src/unsafe.md:17 -msgid "Access or modify mutable static variables." -msgstr "访问或修改可变的静态变量。" +#: src/slices-and-lifetimes/lifetime-annotations.md:36 +msgid "// What is the lifetime of p3?\n" +msgstr "" -#: src/unsafe.md:18 -msgid "Access `union` fields." -msgstr "访问 `union` 字段。" +#: src/slices-and-lifetimes/lifetime-annotations.md:37 +msgid "\"p3: {p3:?}\"" +msgstr "" -#: src/unsafe.md:19 -msgid "Call `unsafe` functions, including `extern` functions." -msgstr "调用 `unsafe` 函数，包括 `extern` 函数。" +#: src/slices-and-lifetimes/lifetime-annotations.md:43 +msgid "" +"In this example, the the compiler does not know what lifetime to infer for " +"`p3`. Looking inside the function body shows that it can only safely assume " +"that `p3`'s lifetime is the shorter of `p1` and `p2`. But just like types, " +"Rust requires explicit annotations of lifetimes on function arguments and " +"return values." +msgstr "" -#: src/unsafe.md:20 -msgid "Implement `unsafe` traits." -msgstr "实现 `unsafe` trait。" +#: src/slices-and-lifetimes/lifetime-annotations.md:49 +msgid "Add `'a` appropriately to `left_most`:" +msgstr "" -#: src/unsafe.md:22 +#: src/slices-and-lifetimes/lifetime-annotations.md:55 msgid "" -"We will briefly cover unsafe capabilities next. For full details, please see " -"[Chapter 19.1 in the Rust Book](https://doc.rust-lang.org/book/ch19-01-" -"unsafe-rust.html) and the [Rustonomicon](https://doc.rust-lang.org/nomicon/)." +"This says, \"given p1 and p2 which both outlive `'a`, the return value lives " +"for at least `'a`." msgstr "" -"下面，我们将简要介绍这些不安全功能。如需了解完整详情，请参阅 [《Rust 手册》" -"第 19.1 章](https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html) 和 " -"[Rustonomicon](https://doc.rust-lang.org/nomicon/)。" -#: src/unsafe.md:28 +#: src/slices-and-lifetimes/lifetime-annotations.md:58 msgid "" -"Unsafe Rust does not mean the code is incorrect. It means that developers " -"have turned off the compiler safety features and have to write correct code " -"by themselves. It means the compiler no longer enforces Rust's memory-safety " -"rules." +"In common cases, lifetimes can be elided, as described on the next slide." msgstr "" -"不安全 Rust 并不意味着代码不正确，而是这意味着开发者已停用 编译器的安全功能，" -"必须自行编写正确的 代码。也就是说，编译器不再强制执行 Rust 的内存安全规则。" -#: src/unsafe/raw-pointers.md:3 -msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" -msgstr "创建指针是安全的操作，但解引用指针需要使用 `unsafe` 方法：" +#: src/slices-and-lifetimes/lifetime-elision.md:1 +msgid "Lifetimes in Function Calls" +msgstr "函数调用中的生命周期" -#: src/unsafe/raw-pointers.md:5 +#: src/slices-and-lifetimes/lifetime-elision.md:3 +#, fuzzy msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut num = 5;\n" -"\n" -" let r1 = &mut num as *mut i32;\n" -" let r2 = r1 as *const i32;\n" -"\n" -" // Safe because r1 and r2 were obtained from references and so are\n" -" // guaranteed to be non-null and properly aligned, the objects " -"underlying\n" -" // the references from which they were obtained are live throughout the\n" -" // whole unsafe block, and they are not accessed either through the\n" -" // references or concurrently through any other pointers.\n" -" unsafe {\n" -" println!(\"r1 is: {}\", *r1);\n" -" *r1 = 10;\n" -" println!(\"r2 is: {}\", *r2);\n" -" }\n" -"}\n" -"```" +"Lifetimes for function arguments and return values must be fully specified, " +"but Rust allows lifetimes to be elided in most cases with [a few simple " +"rules](https://doc.rust-lang.org/nomicon/lifetime-elision.html). This is not " +"inference -- it is just a syntactic shorthand." +msgstr "" +"必须完全指定函数参数和返回值的生命周期， 但 Rust 允许在大多数情况下通过\\[一" +"些简单的 规则\\](https://doc.rust-lang.org/nomicon/lifetime-elision.html）来" +"省略此操作。" + +#: src/slices-and-lifetimes/lifetime-elision.md:8 +msgid "Each argument which does not have a lifetime annotation is given one." msgstr "" -#: src/unsafe/raw-pointers.md:27 +#: src/slices-and-lifetimes/lifetime-elision.md:9 msgid "" -"It is good practice (and required by the Android Rust style guide) to write " -"a comment for each `unsafe` block explaining how the code inside it " -"satisfies the safety requirements of the unsafe operations it is doing." +"If there is only one argument lifetime, it is given to all un-annotated " +"return values." msgstr "" -"我们建议（而且 Android Rust 样式指南要求）为每个 `unsafe` 代码块编写一条注" -"释， 说明该代码块中的代码如何满足其所执行的不安全操作的 安全要求。" -#: src/unsafe/raw-pointers.md:31 +#: src/slices-and-lifetimes/lifetime-elision.md:11 msgid "" -"In the case of pointer dereferences, this means that the pointers must be " -"[_valid_](https://doc.rust-lang.org/std/ptr/index.html#safety), i.e.:" +"If there are multiple argument lifetimes, but the first one is for `self`, " +"that lifetime is given to all un-annotated return values." msgstr "" -"对于指针解除引用，这意味着指针必须为 [_valid_](https://doc.rust-lang.org/std/" -"ptr/index.html#safety)，即：" -#: src/unsafe/raw-pointers.md:34 -msgid "The pointer must be non-null." -msgstr "指针必须为非 null。" +#: src/slices-and-lifetimes/lifetime-elision.md:52 +msgid "In this example, `cab_distance` is trivially elided." +msgstr "" -#: src/unsafe/raw-pointers.md:35 +#: src/slices-and-lifetimes/lifetime-elision.md:54 msgid "" -"The pointer must be _dereferenceable_ (within the bounds of a single " -"allocated object)." -msgstr "指针必须是 _dereferenceable_（在单个已分配对象的边界内）。" - -#: src/unsafe/raw-pointers.md:36 -msgid "The object must not have been deallocated." -msgstr "对象不得已取消分配。" +"The `nearest` function provides another example of a function with multiple " +"references in its arguments that requires explicit annotation." +msgstr "" -#: src/unsafe/raw-pointers.md:37 -msgid "There must not be concurrent accesses to the same location." -msgstr "不得并发访问相同位置。" +#: src/slices-and-lifetimes/lifetime-elision.md:57 +msgid "Try adjusting the signature to \"lie\" about the lifetimes returned:" +msgstr "" -#: src/unsafe/raw-pointers.md:38 +#: src/slices-and-lifetimes/lifetime-elision.md:63 msgid "" -"If the pointer was obtained by casting a reference, the underlying object " -"must be live and no reference may be used to access the memory." +"This won't compile, demonstrating that the annotations are checked for " +"validity by the compiler. Note that this is not the case for raw pointers " +"(unsafe), and this is a common source of errors with unsafe Rust." msgstr "" -"如果通过转换引用类型来获取指针，则底层对象必须处于活跃状态， 而且不得使用任何" -"引用来访问内存。" -#: src/unsafe/raw-pointers.md:41 -msgid "In most cases the pointer must also be properly aligned." -msgstr "在大多数情况下，指针还必须正确对齐。" +#: src/slices-and-lifetimes/lifetime-elision.md:67 +msgid "" +"Students may ask when to use lifetimes. Rust borrows _always_ have " +"lifetimes. Most of the time, elision and type inference mean these don't " +"need to be written out. In more complicated cases, lifetime annotations can " +"help resolve ambiguity. Often, especially when prototyping, it's easier to " +"just work with owned data by cloning values where necessary." +msgstr "" -#: src/unsafe/mutable-static-variables.md:3 -msgid "It is safe to read an immutable static variable:" -msgstr "读取不可变的静态变量是安全的操作：" +#: src/slices-and-lifetimes/struct-lifetimes.md:1 +msgid "Lifetimes in Data Structures" +msgstr "数据结构中的生命周期" -#: src/unsafe/mutable-static-variables.md:5 +#: src/slices-and-lifetimes/struct-lifetimes.md:3 msgid "" -"```rust,editable\n" -"static HELLO_WORLD: &str = \"Hello, world!\";\n" -"\n" -"fn main() {\n" -" println!(\"HELLO_WORLD: {HELLO_WORLD}\");\n" -"}\n" -"```" +"If a data type stores borrowed data, it must be annotated with a lifetime:" +msgstr "如果数据类型存储了借用的数据，则必须对其添加生命周期注释：" + +#: src/slices-and-lifetimes/struct-lifetimes.md:10 +msgid "\"Bye {text}!\"" msgstr "" -#: src/unsafe/mutable-static-variables.md:13 -msgid "" -"However, since data races can occur, it is unsafe to read and write mutable " -"static variables:" -msgstr "但是，读取和写入可变的静态变量是不安全的，因为这可能会 造成数据争用：" +#: src/slices-and-lifetimes/struct-lifetimes.md:14 +msgid "\"The quick brown fox jumps over the lazy dog.\"" +msgstr "" -#: src/unsafe/mutable-static-variables.md:16 -msgid "" -"```rust,editable\n" -"static mut COUNTER: u32 = 0;\n" -"\n" -"fn add_to_counter(inc: u32) {\n" -" unsafe { COUNTER += inc; } // Potential data race!\n" -"}\n" -"\n" -"fn main() {\n" -" add_to_counter(42);\n" -"\n" -" unsafe { println!(\"COUNTER: {COUNTER}\"); } // Potential data race!\n" -"}\n" -"```" +#: src/slices-and-lifetimes/struct-lifetimes.md:17 +msgid "// erase(text);\n" msgstr "" -#: src/unsafe/mutable-static-variables.md:32 -msgid "" -"Using a mutable static is generally a bad idea, but there are some cases " -"where it might make sense in low-level `no_std` code, such as implementing a " -"heap allocator or working with some C APIs." +#: src/slices-and-lifetimes/struct-lifetimes.md:18 +msgid "\"{fox:?}\"" msgstr "" -"通常，我们不建议使用可变的静态变量，但在某些情况下，在低层级 `no_std` 代码中" -"可能需要这样做， 例如实现堆分配器或使用某些 C API。" -#: src/unsafe/unions.md:3 -msgid "Unions are like enums, but you need to track the active field yourself:" -msgstr "联合体与枚举类似，但您需要自行跟踪活跃字段：" +#: src/slices-and-lifetimes/struct-lifetimes.md:19 +msgid "\"{dog:?}\"" +msgstr "" -#: src/unsafe/unions.md:5 +#: src/slices-and-lifetimes/struct-lifetimes.md:25 msgid "" -"```rust,editable\n" -"#[repr(C)]\n" -"union MyUnion {\n" -" i: u8,\n" -" b: bool,\n" -"}\n" -"\n" -"fn main() {\n" -" let u = MyUnion { i: 42 };\n" -" println!(\"int: {}\", unsafe { u.i });\n" -" println!(\"bool: {}\", unsafe { u.b }); // Undefined behavior!\n" -"}\n" -"```" +"In the above example, the annotation on `Highlight` enforces that the data " +"underlying the contained `&str` lives at least as long as any instance of " +"`Highlight` that uses that data." msgstr "" +"在上述示例中，`Highlight` 注释会强制包含 `&str` 的底层数据的生命周期至少与使" +"用该数据的任何 `Highlight` 实例一样长。" -#: src/unsafe/unions.md:21 +#: src/slices-and-lifetimes/struct-lifetimes.md:28 msgid "" -"Unions are very rarely needed in Rust as you can usually use an enum. They " -"are occasionally needed for interacting with C library APIs." +"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " +"the borrow checker throws an error." msgstr "" -"在 Rust 中很少需要用到联合体，因为您通常可以使用枚举。联合体只是偶尔用于 与 " -"C 库 API 进行交互。" +"如果 `text` 在 `fox`（或 `dog`）的生命周期结束前被消耗，借用检查器将抛出一个" +"错误。" -#: src/unsafe/unions.md:24 +#: src/slices-and-lifetimes/struct-lifetimes.md:30 msgid "" -"If you just want to reinterpret bytes as a different type, you probably want " -"[`std::mem::transmute`](https://doc.rust-lang.org/stable/std/mem/fn." -"transmute.html) or a safe wrapper such as the [`zerocopy`](https://crates.io/" -"crates/zerocopy) crate." +"Types with borrowed data force users to hold on to the original data. This " +"can be useful for creating lightweight views, but it generally makes them " +"somewhat harder to use." msgstr "" -"如果您只是想将字节重新解释为其他类型，则可能需要使用 [`std::mem::transmute`]" -"(https://doc.rust-lang.org/stable/std/mem/fn.transmute.html) 或 安全的封装容" -"器，例如 [`zerocopy`](https://crates.io/crates/zerocopy) crate。" +"借用数据的类型会迫使用户保留原始数据。这对于创建轻量级视图很有用，但通常会使" +"它们更难使用。" + +#: src/slices-and-lifetimes/struct-lifetimes.md:33 +msgid "When possible, make data structures own their data directly." +msgstr "如有可能，让数据结构直接拥有自己的数据。" -#: src/unsafe/calling-unsafe-functions.md:3 +#: src/slices-and-lifetimes/struct-lifetimes.md:34 msgid "" -"A function or method can be marked `unsafe` if it has extra preconditions " -"you must uphold to avoid undefined behaviour:" +"Some structs with multiple references inside can have more than one lifetime " +"annotation. This can be necessary if there is a need to describe lifetime " +"relationships between the references themselves, in addition to the lifetime " +"of the struct itself. Those are very advanced use cases." msgstr "" -"如果函数或方法具有额外的前提条件，您必须遵守这些前提条件来避免未定义的行为， " -"则可以将该函数或方法标记为 `unsafe`：" +"一些包含多个引用的结构可以有多个生命周期注释。除了结构体本身的生命周期之外，" +"如果需要描述引用之间的生命周期关系，则可能需要这样做。这些都是非常高级的用" +"例。" -#: src/unsafe/calling-unsafe-functions.md:6 +#: src/slices-and-lifetimes/exercise.md:3 msgid "" -"```rust,editable\n" -"fn main() {\n" -" let emojis = \"🗻∈🌏\";\n" -"\n" -" // Safe because the indices are in the correct order, within the bounds " -"of\n" -" // the string slice, and lie on UTF-8 sequence boundaries.\n" -" unsafe {\n" -" println!(\"emoji: {}\", emojis.get_unchecked(0..4));\n" -" println!(\"emoji: {}\", emojis.get_unchecked(4..7));\n" -" println!(\"emoji: {}\", emojis.get_unchecked(7..11));\n" -" }\n" -"\n" -" println!(\"char count: {}\", count_chars(unsafe { emojis." -"get_unchecked(0..7) }));\n" -"\n" -" // Not upholding the UTF-8 encoding requirement breaks memory safety!\n" -" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" -" // println!(\"char count: {}\", count_chars(unsafe { emojis." -"get_unchecked(0..3) }));\n" -"}\n" -"\n" -"fn count_chars(s: &str) -> usize {\n" -" s.chars().map(|_| 1).sum()\n" -"}\n" -"```" +"In this exercise, you will build a parser for the [protobuf binary encoding]" +"(https://protobuf.dev/programming-guides/encoding/). Don't worry, it's " +"simpler than it seems! This illustrates a common parsing pattern, passing " +"slices of data. The underlying data itself is never copied." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:3 +#: src/slices-and-lifetimes/exercise.md:8 msgid "" -"You can mark your own functions as `unsafe` if they require particular " -"conditions to avoid undefined behaviour." +"Fully parsing a protobuf message requires knowing the types of the fields, " +"indexed by their field numbers. That is typically provided in a `proto` " +"file. In this exercise, we'll encode that information into `match` " +"statements in functions that get called for each field." +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:13 +msgid "We'll use the following proto:" msgstr "" -"如果您自己编写的函数需要满足特定条件以避免未定义的行为， 您可以将这些函数标记" -"为 `unsafe`。" -#: src/unsafe/writing-unsafe-functions.md:6 +#: src/slices-and-lifetimes/exercise.md:28 msgid "" -"```rust,editable\n" -"/// Swaps the values pointed to by the given pointers.\n" -"///\n" -"/// # Safety\n" -"///\n" -"/// The pointers must be valid and properly aligned.\n" -"unsafe fn swap(a: *mut u8, b: *mut u8) {\n" -" let temp = *a;\n" -" *a = *b;\n" -" *b = temp;\n" -"}\n" -"\n" -"fn main() {\n" -" let mut a = 42;\n" -" let mut b = 66;\n" -"\n" -" // Safe because ...\n" -" unsafe {\n" -" swap(&mut a, &mut b);\n" -" }\n" -"\n" -" println!(\"a = {}, b = {}\", a, b);\n" -"}\n" -"```" +"A proto message is encoded as a series of fields, one after the next. Each " +"is implemented as a \"tag\" followed by the value. The tag contains a field " +"number (e.g., `2` for the `id` field of a `Person` message) and a wire type " +"defining how the payload should be determined from the byte stream." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:33 +#: src/slices-and-lifetimes/exercise.md:33 msgid "" -"We wouldn't actually use pointers for this because it can be done safely " -"with references." -msgstr "实际上，我们不会这样使用指针，因为使用引用可以安全地达到相同的目的。" +"Integers, including the tag, are represented with a variable-length encoding " +"called VARINT. Luckily, `parse_varint` is defined for you below. The given " +"code also defines callbacks to handle `Person` and `PhoneNumber` fields, and " +"to parse a message into a series of calls to those callbacks." +msgstr "" -#: src/unsafe/writing-unsafe-functions.md:35 +#: src/slices-and-lifetimes/exercise.md:38 msgid "" -"Note that unsafe code is allowed within an unsafe function without an " -"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " -"Try adding it and see what happens." +"What remains for you is to implement the `parse_field` function and the " +"`ProtoMessage` trait for `Person` and `PhoneNumber`." msgstr "" -"请注意，在不安全函数中，可以在没有 `unsafe` 代码块的情况下使用不安全代码。我" -"们可以 使用 `#[deny(unsafe_op_in_unsafe_fn)]` 来禁止此行为。请尝试添加该命" -"令，看看会出现什么情况。" -#: src/unsafe/extern-functions.md:1 -msgid "Calling External Code" -msgstr "调用外部代码" +#: src/slices-and-lifetimes/exercise.md:49 +#: src/slices-and-lifetimes/solution.md:11 +msgid "\"Invalid varint\"" +msgstr "" -#: src/unsafe/extern-functions.md:3 -msgid "" -"Functions from other languages might violate the guarantees of Rust. Calling " -"them is thus unsafe:" +#: src/slices-and-lifetimes/exercise.md:51 +#: src/slices-and-lifetimes/solution.md:13 +msgid "\"Invalid wire-type\"" msgstr "" -"基于其他语言的函数可能会违反 Rust 的保证。因此， 调用这类函数是不安全的：" -#: src/unsafe/extern-functions.md:6 -msgid "" -"```rust,editable\n" -"extern \"C\" {\n" -" fn abs(input: i32) -> i32;\n" -"}\n" -"\n" -"fn main() {\n" -" unsafe {\n" -" // Undefined behavior if abs misbehaves.\n" -" println!(\"Absolute value of -3 according to C: {}\", abs(-3));\n" -" }\n" -"}\n" -"```" +#: src/slices-and-lifetimes/exercise.md:53 +#: src/slices-and-lifetimes/solution.md:15 +msgid "\"Unexpected EOF\"" msgstr "" -#: src/unsafe/extern-functions.md:21 -msgid "" -"This is usually only a problem for extern functions which do things with " -"pointers which might violate Rust's memory model, but in general any C " -"function might have undefined behaviour under any arbitrary circumstances." +#: src/slices-and-lifetimes/exercise.md:55 +#: src/slices-and-lifetimes/solution.md:17 +msgid "\"Invalid length\"" msgstr "" -"这个问题通常仅存在于使用指针执行违反 Rust 内存模型的操作的外部函数中。 但一般" -"而言，任何 C 函数都有可能在任意情况下出现未定义行为。" -#: src/unsafe/extern-functions.md:25 -msgid "" -"The `\"C\"` in this example is the ABI; [other ABIs are available too]" -"(https://doc.rust-lang.org/reference/items/external-blocks.html)." +#: src/slices-and-lifetimes/exercise.md:57 +#: src/slices-and-lifetimes/solution.md:19 +msgid "\"Unexpected wire-type)\"" msgstr "" -"本例中的“C”是 ABI；[也可以使用其他 ABI](https://doc.rust-lang.org/reference/" -"items/external-blocks.html)。" -#: src/unsafe/unsafe-traits.md:3 -msgid "" -"Like with functions, you can mark a trait as `unsafe` if the implementation " -"must guarantee particular conditions to avoid undefined behaviour." +#: src/slices-and-lifetimes/exercise.md:59 +#: src/slices-and-lifetimes/solution.md:21 +msgid "\"Invalid string (not UTF-8)\"" msgstr "" -"与函数一样，如果您在实现某个 trait 时必须保证特定条件来避免未定义的行为， 您" -"也可以将该 trait 标记为 `unsafe`。" -#: src/unsafe/unsafe-traits.md:6 -msgid "" -"For example, the `zerocopy` crate has an unsafe trait that looks [something " -"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" +#: src/slices-and-lifetimes/exercise.md:62 +#: src/slices-and-lifetimes/solution.md:24 +msgid "/// A wire type as seen on the wire.\n" msgstr "" -"例如，`zerocopy` crate 包含一个不安全的 trait， [大致内容是这样的](https://" -"docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html)：" -#: src/unsafe/unsafe-traits.md:9 -msgid "" -"```rust,editable\n" -"use std::mem::size_of_val;\n" -"use std::slice;\n" -"\n" -"/// ...\n" -"/// # Safety\n" -"/// The type must have a defined representation and no padding.\n" -"pub unsafe trait AsBytes {\n" -" fn as_bytes(&self) -> &[u8] {\n" -" unsafe {\n" -" slice::from_raw_parts(self as *const Self as *const u8, " -"size_of_val(self))\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Safe because u32 has a defined representation and no padding.\n" -"unsafe impl AsBytes for u32 {}\n" -"```" +#: src/slices-and-lifetimes/exercise.md:65 +#: src/slices-and-lifetimes/solution.md:27 +msgid "/// The Varint WireType indicates the value is a single VARINT.\n" msgstr "" -#: src/unsafe/unsafe-traits.md:30 +#: src/slices-and-lifetimes/exercise.md:67 +#: src/slices-and-lifetimes/solution.md:29 msgid "" -"There should be a `# Safety` section on the Rustdoc for the trait explaining " -"the requirements for the trait to be safely implemented." +"//I64, -- not needed for this exercise\n" +" /// The Len WireType indicates that the value is a length represented as " +"a\n" +" /// VARINT followed by exactly that number of bytes.\n" msgstr "" -"在 Rustdoc 中有关 trait 的章节下，有一个标题为 `# 安全` 的部分介绍了 安全实" -"现 trait 的要求。" -#: src/unsafe/unsafe-traits.md:33 +#: src/slices-and-lifetimes/exercise.md:71 +#: src/slices-and-lifetimes/solution.md:33 msgid "" -"The actual safety section for `AsBytes` is rather longer and more " -"complicated." -msgstr "实际上，与 `AsBytes` 相关的安全说明远比这里展示的更详尽、更复杂。" +"/// The I32 WireType indicates that the value is precisely 4 bytes in\n" +" /// little-endian order containing a 32-bit signed integer.\n" +msgstr "" -#: src/unsafe/unsafe-traits.md:35 -msgid "The built-in `Send` and `Sync` traits are unsafe." -msgstr "内置的 `Send` 和 `Sync` trait 都是不安全的。" +#: src/slices-and-lifetimes/exercise.md:76 +#: src/slices-and-lifetimes/solution.md:38 +msgid "/// A field's value, typed based on the wire type.\n" +msgstr "" -#: src/exercises/day-3/afternoon.md:1 -msgid "Day 3: Afternoon Exercises" -msgstr "第 3 天：下午练习" +#: src/slices-and-lifetimes/exercise.md:80 +#: src/slices-and-lifetimes/solution.md:42 +msgid "//I64(i64), -- not needed for this exercise\n" +msgstr "" -#: src/exercises/day-3/afternoon.md:3 -msgid "Let us build a safe wrapper for reading directory content!" -msgstr "让我们构建一个用于读取目录内容的安全封装容器！" +#: src/slices-and-lifetimes/exercise.md:85 +#: src/slices-and-lifetimes/solution.md:47 +msgid "/// A field, containing the field number and its value.\n" +msgstr "" -#: src/exercises/day-3/afternoon.md:5 -msgid "" -"For this exercise, we suggest using a local dev environment instead of the " -"Playground. This will allow you to run your binary on your own machine." +#: src/slices-and-lifetimes/exercise.md:102 +#: src/slices-and-lifetimes/solution.md:64 +msgid "//1 => WireType::I64, -- not needed for this exercise\n" msgstr "" -"在本练习中，我们建议您使用本地开发环境，而不是 Playground。这样，您就可以在自" -"己的机器上运行二进制文件。" -#: src/exercises/day-3/afternoon.md:8 +#: src/slices-and-lifetimes/exercise.md:132 +#: src/slices-and-lifetimes/solution.md:94 msgid "" -"To get started, follow the [running locally](../../cargo/running-locally.md) " -"instructions." -msgstr "首先，请按照[在本地运行](../../cargo/running-locally.md)中的说明操作。" +"/// Parse a VARINT, returning the parsed value and the remaining bytes.\n" +msgstr "" -#: src/exercises/day-3/afternoon.md:14 +#: src/slices-and-lifetimes/exercise.md:140 +#: src/slices-and-lifetimes/solution.md:102 msgid "" -"After looking at the exercise, you can look at the [solution](solutions-" -"afternoon.md) provided." -msgstr "看过练习后，您可以查看所提供的[解题方法](solutions-afternoon.md)。" +"// This is the last byte of the VARINT, so convert it to\n" +" // a u64 and return it.\n" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:3 -msgid "" -"Rust has great support for calling functions through a _foreign function " -"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " -"functions you would use from C to read the names of files in a directory." +#: src/slices-and-lifetimes/exercise.md:150 +#: src/slices-and-lifetimes/solution.md:112 +msgid "// More than 7 bytes is invalid.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:7 -msgid "You will want to consult the manual pages:" -msgstr "建议您参考以下手册页面：" +#: src/slices-and-lifetimes/exercise.md:153 +#: src/slices-and-lifetimes/solution.md:115 +msgid "/// Convert a tag into a field number and a WireType.\n" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:9 -msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" -msgstr "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" +#: src/slices-and-lifetimes/exercise.md:161 +#: src/slices-and-lifetimes/solution.md:122 +msgid "/// Parse a field, returning the remaining bytes\n" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:10 -msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" -msgstr "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" +#: src/slices-and-lifetimes/exercise.md:167 +msgid "" +"\"Based on the wire type, build a Field, consuming as many bytes as " +"necessary.\"" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:11 -msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" -msgstr "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" +#: src/slices-and-lifetimes/exercise.md:169 +msgid "\"Return the field, and any un-consumed bytes.\"" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:13 +#: src/slices-and-lifetimes/exercise.md:171 +#: src/slices-and-lifetimes/solution.md:153 msgid "" -"You will also want to browse the [`std::ffi`](https://doc.rust-lang.org/std/" -"ffi/) module. There you find a number of string types which you need for the " -"exercise:" +"/// Parse a message in the given data, calling `T::add_field` for each field " +"in\n" +"/// the message.\n" +"///\n" +"/// The entire input is consumed.\n" msgstr "" -"您还需要浏览[“std::ffi”](https://doc.rust-lang.org/std/ffi/)模块。在下方，您" -"会发现完成这个练习所需的多种字符串类型：" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Encoding" -msgstr "编码" +#: src/slices-and-lifetimes/exercise.md:198 +msgid "// TODO: Implement ProtoMessage for Person and PhoneNumber.\n" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Use" -msgstr "使用" +#: src/slices-and-lifetimes/solution.md:146 +msgid "// Unwrap error because `value` is definitely 4 bytes long.\n" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "" -"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" -"(https://doc.rust-lang.org/std/string/struct.String.html)" +#: src/slices-and-lifetimes/solution.md:187 +#: src/slices-and-lifetimes/solution.md:198 +msgid "// skip everything else\n" msgstr "" -"[“str”](https://doc.rust-lang.org/std/primitive.str.html)和[“String”]" -"(https://doc.rust-lang.org/std/string/struct.String.html)" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "UTF-8" -msgstr "UTF-8" +#: src/slices-and-lifetimes/solution.md:225 +#: src/slices-and-lifetimes/solution.md:232 +#: src/slices-and-lifetimes/solution.md:239 +msgid "b\"hello\"" +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "Text processing in Rust" -msgstr "用 Rust 进行文本处理" +#: src/welcome-day-4.md:1 +#, fuzzy +msgid "Welcome to Day 4" +msgstr "欢迎来到第一天" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 +#: src/welcome-day-4.md:3 +#, fuzzy msgid "" -"[`CStr`](https://doc.rust-lang.org/std/ffi/struct.CStr.html) and [`CString`]" -"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" +"Today we will cover topics relating to building large-scale software in Rust:" +msgstr "今天，我们将介绍一些更高级的 Rust 主题：" + +#: src/welcome-day-4.md:5 +msgid "Iterators: a deep dive on the `Iterator` trait." msgstr "" -"[“CStr”](https://doc.rust-lang.org/std/ffi/struct.CStr.html)和[“CString”]" -"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "NUL-terminated" -msgstr "以空字符结尾" +#: src/welcome-day-4.md:6 +msgid "Modules and visibility." +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "Communicating with C functions" -msgstr "与 C 函数通信" +#: src/welcome-day-4.md:7 +#, fuzzy +msgid "Testing." +msgstr "测试" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "" -"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " -"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" -msgstr "" -"[“OsStr”](https://doc.rust-lang.org/std/ffi/struct.OsStr.html)和[“OsString”]" -"(https://doc.rust-lang.org/std/ffi/struct.OsString.html)" - -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "OS-specific" -msgstr "特定于操作系统" - -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "Communicating with the OS" -msgstr "与操作系统通信" - -#: src/exercises/day-3/safe-ffi-wrapper.md:22 -msgid "You will convert between all these types:" -msgstr "您将在以下所有类型之间进行转换：" +#: src/welcome-day-4.md:8 +msgid "Error handling: panics, `Result`, and the try operator `?`." +msgstr "错误处理：panic、“Result”和 try 运算符“?”。" -#: src/exercises/day-3/safe-ffi-wrapper.md:24 +#: src/welcome-day-4.md:9 msgid "" -"`&str` to `CString`: you need to allocate space for a trailing `\\0` " -"character," -msgstr "将 `&str` 转换为 `CString`：您需要为尾随 `\\0` 字符分配空格，" - -#: src/exercises/day-3/safe-ffi-wrapper.md:25 -msgid "`CString` to `*const i8`: you need a pointer to call C functions," -msgstr "将 `CString` 转换为 `\\*const i8` ：您需要一个指针来调用 C 函数，" +"Unsafe Rust: the escape hatch when you can't express yourself in safe Rust." +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:26 +#: src/iterators/iterator.md:7 msgid "" -"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " -"character," +"The [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait supports iterating over values in a collection. It requires a `next` " +"method and provides lots of methods. Many standard library types implement " +"`Iterator`, and you can implement it yourself, too:" msgstr "" -"将 `\\*const i8` 转换为 `&CStr` ：您需要一些能够找到尾随 `\\0` 字符的内容，" -#: src/exercises/day-3/safe-ffi-wrapper.md:27 -msgid "" -"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " -"unknow data\"," +#: src/iterators/iterator.md:31 +msgid "\"fib({i}): {n}\"" msgstr "" -"将 `&CStr` 转换为 `&\\[u8\\]` ：一个字节 Slice 是“一些未知数据”的通用接口，" -#: src/exercises/day-3/safe-ffi-wrapper.md:28 +#: src/iterators/iterator.md:38 +#, fuzzy msgid "" -"`&[u8]` to `&OsStr`: `&OsStr` is a step towards `OsString`, use [`OsStrExt`]" -"(https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html) to create it," +"The `Iterator` trait implements many common functional programming " +"operations over collections (e.g. `map`, `filter`, `reduce`, etc). This is " +"the trait where you can find all the documentation about them. In Rust these " +"functions should produce the code as efficient as equivalent imperative " +"implementations." msgstr "" -"将 `&\\[u8\\]` 转换为 `&OsStr` ：`&OsStr` 是向 `OsString` 迈进的一步，请使用" -"[`OsStrExt`](https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html)来" -"创建它，" +"`Iterator` 特征会对集合实现许多常见的函数程序操作， 例如 ` map`filter \\``和" +"`reduce\\` 等。您可以通过此特征找到有关它们的所有 文档。在 Rust 中，这些函数" +"应生成代码，且生成的代码应与等效命令式实现一样 高效。" -#: src/exercises/day-3/safe-ffi-wrapper.md:31 +#: src/iterators/iterator.md:43 msgid "" -"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " -"return it and call `readdir` again." +"`IntoIterator` is the trait that makes for loops work. It is implemented by " +"collection types such as `Vec` and references to them such as `&Vec` " +"and `&[T]`. Ranges also implement it. This is why you can iterate over a " +"vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." msgstr "" -"将“&OsStr”转换为“OsString”：您需要克隆“&OsStr”中的数据，以便能够返回它并再次" -"调用“readdir”。" +"`IntoIterator` 是迫使 for 循环运作的特征。此特征由集合类型 （例如 `Vec`）" +"和相关引用（例如 `&Vec` 和 `&[T]`）而实现。此外，范围也会实现这项特征。因" +"此， 您可以使用 `for i in some_vec { .. }` 来遍历某矢量，但 `some_vec." +"next()` 不存在。" -#: src/exercises/day-3/safe-ffi-wrapper.md:34 +#: src/iterators/intoiterator.md:3 +#, fuzzy msgid "" -"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " -"useful chapter about FFI." +"The `Iterator` trait tells you how to _iterate_ once you have created an " +"iterator. The related trait [`IntoIterator`](https://doc.rust-lang.org/std/" +"iter/trait.IntoIterator.html) defines how to create an iterator for a type. " +"It is used automatically by the `for` loop." msgstr "" -"[秘典](https://doc.rust-lang.org/nomicon/ffi.html) 中也有一个关于 FFI 的非常" -"实用的章节。" +"“Iterator”trait会告知您在创建迭代器后如何进行迭代。相关 trait“IntoIterator”会" +"告知您如何创建迭代器：" -#: src/exercises/day-3/safe-ffi-wrapper.md:45 -msgid "" -"Copy the code below to and fill in the missing " -"functions and methods:" +#: src/iterators/intoiterator.md:49 +msgid "\"point = {x}, {y}\"" msgstr "" -"将以下代码复制到 ，并填入缺少的函数和方法：" -#: src/exercises/day-3/safe-ffi-wrapper.md:48 +#: src/iterators/intoiterator.md:56 +#, fuzzy msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_imports, unused_variables, dead_code)]\n" -"\n" -"mod ffi {\n" -" use std::os::raw::{c_char, c_int};\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" use std::os::raw::{c_long, c_ulong, c_ushort, c_uchar};\n" -"\n" -" // Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" -" #[repr(C)]\n" -" pub struct DIR {\n" -" _data: [u8; 0],\n" -" _marker: core::marker::PhantomData<(*mut u8, core::marker::" -"PhantomPinned)>,\n" -" }\n" -"\n" -" // Layout according to the Linux man page for readdir(3), where ino_t " -"and\n" -" // off_t are resolved according to the definitions in\n" -" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_ino: c_ulong,\n" -" pub d_off: c_long,\n" -" pub d_reclen: c_ushort,\n" -" pub d_type: c_uchar,\n" -" pub d_name: [c_char; 256],\n" -" }\n" -"\n" -" // Layout according to the macOS man page for dir(5).\n" -" #[cfg(all(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_fileno: u64,\n" -" pub d_seekoff: u64,\n" -" pub d_reclen: u16,\n" -" pub d_namlen: u16,\n" -" pub d_type: u8,\n" -" pub d_name: [c_char; 1024],\n" -" }\n" -"\n" -" extern \"C\" {\n" -" pub fn opendir(s: *const c_char) -> *mut DIR;\n" -"\n" -" #[cfg(not(all(target_os = \"macos\", target_arch = \"x86_64\")))]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" // See https://github.com/rust-lang/libc/issues/414 and the section " -"on\n" -" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" -" //\n" -" // \"Platforms that existed before these updates were available\" " -"refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " -"PowerPC.\n" -" #[cfg(all(target_os = \"macos\", target_arch = \"x86_64\"))]\n" -" #[link_name = \"readdir$INODE64\"]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" pub fn closedir(s: *mut DIR) -> c_int;\n" -" }\n" -"}\n" -"\n" -"use std::ffi::{CStr, CString, OsStr, OsString};\n" -"use std::os::unix::ffi::OsStrExt;\n" -"\n" -"#[derive(Debug)]\n" -"struct DirectoryIterator {\n" -" path: CString,\n" -" dir: *mut ffi::DIR,\n" -"}\n" -"\n" -"impl DirectoryIterator {\n" -" fn new(path: &str) -> Result {\n" -" // Call opendir and return a Ok value if that worked,\n" -" // otherwise return Err with a message.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Iterator for DirectoryIterator {\n" -" type Item = OsString;\n" -" fn next(&mut self) -> Option {\n" -" // Keep calling readdir until we get a NULL pointer back.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Drop for DirectoryIterator {\n" -" fn drop(&mut self) {\n" -" // Call closedir as needed.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"fn main() -> Result<(), String> {\n" -" let iter = DirectoryIterator::new(\".\")?;\n" -" println!(\"files: {:#?}\", iter.collect::>());\n" -" Ok(())\n" -"}\n" -"```" -msgstr "" +"Click through to the docs for `IntoIterator`. Every implementation of " +"`IntoIterator` must declare two types:" +msgstr "这里的语法表示，“IntoIterator”的每个实现都必须声明两种类型：" -#: src/android.md:1 -msgid "Welcome to Rust in Android" -msgstr "欢迎来到Android 中的Rust" +#: src/iterators/intoiterator.md:59 +#, fuzzy +msgid "`Item`: the type to iterate over, such as `i8`," +msgstr "`Item`：我们迭代的类型，例如 `i8`，" -#: src/android.md:3 +#: src/iterators/intoiterator.md:60 +msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." +msgstr "“IntoIter”：“into_iter”方法返回的“Iterator”类型。" + +#: src/iterators/intoiterator.md:62 +#, fuzzy msgid "" -"Rust is supported for native platform development on Android. This means " -"that you can write new operating system services in Rust, as well as " -"extending existing services." +"Note that `IntoIter` and `Item` are linked: the iterator must have the same " +"`Item` type, which means that it returns `Option`" msgstr "" -"Rust 支持Android 的原生平台开发。这意味着您可以在Rust 中编写新的操作系统服" -"务，以及扩展现有服务。" +"请注意，“IntoIter”和“Item”已关联：迭代器必须具有相同的“Item”类型，这意味着它" +"会返回“Option\n" +"\n" +"”" -#: src/android.md:7 +#: src/iterators/intoiterator.md:65 +msgid "The example iterates over all combinations of x and y coordinates." +msgstr "" + +#: src/iterators/intoiterator.md:67 msgid "" -"We will attempt to call Rust from one of your own projects today. So try to " -"find a little corner of your code base where we can move some lines of code " -"to Rust. The fewer dependencies and \"exotic\" types the better. Something " -"that parses some raw bytes would be ideal." +"Try iterating over the grid twice in `main`. Why does this fail? Note that " +"`IntoIterator::into_iter` takes ownership of `self`." msgstr "" -"今天我们会尝试在你自己的项目中调用Rust。 所以试着在你的代码中找一小段来改成" -"Rust。 代码中越少依赖(dependencies)，越少“独特”的类型，越好。比如 一段解析原" -"始字符的代码就很理想。" -#: src/android/setup.md:3 +#: src/iterators/intoiterator.md:70 msgid "" -"We will be using an Android Virtual Device to test our code. Make sure you " -"have access to one or create a new one with:" +"Fix this issue by implementing `IntoIterator` for `&Grid` and storing a " +"reference to the `Grid` in `GridIter`." msgstr "" -"我们将会使用Android 虚拟设备（Android Virtual Device）来测试我们的代码。 确保" -"你有权限访问一个，或者用以下命令创建一个新的：" -#: src/android/setup.md:12 +#: src/iterators/intoiterator.md:73 msgid "" -"Please see the [Android Developer Codelab](https://source.android.com/docs/" -"setup/start) for details." +"The same problem can occur for standard library types: `for e in " +"some_vector` will take ownership of `some_vector` and iterate over owned " +"elements from that vector. Use `for e in &some_vector` instead, to iterate " +"over references to elements of `some_vector`." msgstr "" -"更多细节请参考 [Android Developer Codelab](https://source.android.com/docs/" -"setup/start)." -#: src/android/build-rules.md:3 -msgid "The Android build system (Soong) supports Rust via a number of modules:" -msgstr "Android 构建系统（Soong）通过一系列模块来支持Rust：" +#: src/iterators/fromiterator.md:1 +msgid "FromIterator" +msgstr "FromIterator" -#: src/android/build-rules.md:5 -#, fuzzy -msgid "Module Type" +#: src/iterators/fromiterator.md:3 +msgid "" +"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " +"lets you build a collection from an [`Iterator`](https://doc.rust-lang.org/" +"std/iter/trait.Iterator.html)." msgstr "" -"\\| 模块类型 | 描" -"述 " -"| \\|—————————|——————————————————————————————————————————————————| \\| " -"`rust_binary` | Rust 二进制文" -"件。 " -"| \\| `rust_library` | 生成Rust 库，并且提供 `rlib` 和 `dylib` 变" -"体。 | \\| `rust_ffi` | 生成可由 cc 模块使用的 " -"Rust C 库，并提供静态和共享变体。 | \\| `rust_proc_macro` | 生成 proc-" -"macro Rust 库。 这些宏与编译器插件类似。 | \\| " -"`rust_test` | 生成使用标准 Rust 自动化测试框架的 Rust 测试二进制文" -"件。 | \\| `rust_fuzz` | 生成使用 " -"libfuzzer 的 Rust 模糊测试二进制文" -"件。 | \\| `rust_protobuf` | 生成源" -"代码，并生成为特定 protobuf 提供接口的 Rust 库。| \\| `rust_bindgen` | 生" -"成源代码，并生成包含与 C 库的 Rust 绑定的 Rust 库。｜" - -#: src/android/build-rules.md:5 -msgid "Description" -msgstr "描述" +"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " +"让您可通过 [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator." +"html) 构建一个集合。" -#: src/android/build-rules.md:7 -msgid "`rust_binary`" -msgstr "`rust_binary`" +#: src/iterators/fromiterator.md:9 +msgid "\"prime_squares: {prime_squares:?}\"" +msgstr "" -#: src/android/build-rules.md:7 -msgid "Produces a Rust binary." -msgstr "生成一个Rust二进制文件。" +#: src/iterators/fromiterator.md:15 +#, fuzzy +msgid "`Iterator` implements" +msgstr "“Iterator”" -#: src/android/build-rules.md:8 -msgid "`rust_library`" -msgstr "`rust_library`" +#: src/iterators/fromiterator.md:24 +msgid "There are two ways to specify `B` for this method:" +msgstr "" -#: src/android/build-rules.md:8 -msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." -msgstr "生成一个 Rust 库，并提供 `rlib` 和 `dylib` 两种变体。" +#: src/iterators/fromiterator.md:26 +msgid "" +"With the \"turbofish\": `some_iterator.collect::()`, as " +"shown. The `_` shorthand used here lets Rust infer the type of the `Vec` " +"elements." +msgstr "" -#: src/android/build-rules.md:9 -msgid "`rust_ffi`" -msgstr "`rust_ffi`" +#: src/iterators/fromiterator.md:28 +msgid "" +"With type inference: `let prime_squares: Vec<_> = some_iterator.collect()`. " +"Rewrite the example to use this form." +msgstr "" -#: src/android/build-rules.md:9 +#: src/iterators/fromiterator.md:31 +#, fuzzy msgid "" -"Produces a Rust C library usable by `cc` modules, and provides both static " -"and shared variants." -msgstr "生成一个可由 `cc` 模块使用的 Rust C 库，并提供静态和共享两种变体。" +"There are basic implementations of `FromIterator` for `Vec`, `HashMap`, etc. " +"There are also more specialized implementations which let you do cool things " +"like convert an `Iterator>` into a `Result, E>`." +msgstr "" +"还有一些实现，让您可执行一些很酷的操作，比如 将 `Iterator>` 转换成 `Result, E>`。" -#: src/android/build-rules.md:10 -msgid "`rust_proc_macro`" -msgstr "`rust_proc_macro`" +#: src/iterators/exercise.md:3 +#, fuzzy +msgid "" +"In this exercise, you will need to find and use some of the provided methods " +"in the [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait to implement a complex calculation." +msgstr "" +"您可以自行实现 [`Iterator`](https://doc.rust-lang.org/std/iter/trait." +"Iterator.html) 特征：" -#: src/android/build-rules.md:10 +#: src/iterators/exercise.md:6 +#, fuzzy msgid "" -"Produces a `proc-macro` Rust library. These are analogous to compiler " -"plugins." +"Copy the following code to and make the tests " +"pass. Use an iterator expression and `collect` the result to construct the " +"return value." msgstr "" +"将以下代码复制到 ，然后设法通过测试。请尽量避免" +"为中间结果分配“Vec”：" -#: src/android/build-rules.md:11 -msgid "`rust_test`" -msgstr "`rust_test`" +#: src/iterators/exercise.md:11 src/iterators/solution.md:4 +msgid "" +"/// Calculate the differences between elements of `values` offset by " +"`offset`,\n" +"/// wrapping around from the end of `values` to the beginning.\n" +"///\n" +"/// Element `n` of the result is `values[(n+offset)%len] - values[n]`.\n" +msgstr "" -#: src/android/build-rules.md:11 -msgid "Produces a Rust test binary that uses the standard Rust test harness." -msgstr "生成使用标准 Rust 测试框架的 Rust 测试二进制文件。" +#: src/modules/modules.md:3 +msgid "We have seen how `impl` blocks let us namespace functions to a type." +msgstr "我们已看了“impl”块如何让我们将函数的命名空间建为一种类型。" -#: src/android/build-rules.md:12 -msgid "`rust_fuzz`" -msgstr "`rust_fuzz`" +#: src/modules/modules.md:5 +msgid "Similarly, `mod` lets us namespace types and functions:" +msgstr "同样，“mod”让我们可为类型和函数建立命名空间：" -#: src/android/build-rules.md:12 -msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." +#: src/modules/modules.md:10 +msgid "\"In the foo module\"" msgstr "" -#: src/android/build-rules.md:13 -msgid "`rust_protobuf`" -msgstr "`rust_protobuf`" +#: src/modules/modules.md:16 +msgid "\"In the bar module\"" +msgstr "" -#: src/android/build-rules.md:13 +#: src/modules/modules.md:28 msgid "" -"Generates source and produces a Rust library that provides an interface for " -"a particular protobuf." -msgstr "生成源代码并生成为特定 protobuf 提供接口的 Rust 库。" - -#: src/android/build-rules.md:14 -msgid "`rust_bindgen`" +"Packages provide functionality and include a `Cargo.toml` file that " +"describes how to build a bundle of 1+ crates." msgstr "" +"包提供功能，并包含一个描述如何构建包含 1 个以上 crate 的捆绑包的“Cargo." +"toml”文件。" -#: src/android/build-rules.md:14 +#: src/modules/modules.md:30 msgid "" -"Generates source and produces a Rust library containing Rust bindings to C " -"libraries." -msgstr "生成源代码并生成包含 Rust 绑定到 C 库的 Rust 库。" - -#: src/android/build-rules.md:16 -msgid "We will look at `rust_binary` and `rust_library` next." -msgstr "下面我们来看看 `rust_binary` 和 `rust_library`。" +"Crates are a tree of modules, where a binary crate creates an executable and " +"a library crate compiles to a library." +msgstr "" +"crate 是一种模块树，其中的二进制 crate 会创建一个可执行文件，而库 crate 会编" +"译为库。" -#: src/android/build-rules/binary.md:1 -msgid "Rust Binaries" -msgstr "Rust 二进制文件" +#: src/modules/modules.md:32 +msgid "Modules define organization, scope, and are the focus of this section." +msgstr "模块定义了组织和范围，并且是本部分的重点。" -#: src/android/build-rules/binary.md:3 +#: src/modules/filesystem.md:3 msgid "" -"Let us start with a simple application. At the root of an AOSP checkout, " -"create the following files:" -msgstr "让我们从一个简单的应用程序开始。在 AOSP 签出的根目录下，创建以下文件：" - -#: src/android/build-rules/binary.md:6 src/android/build-rules/library.md:13 -msgid "_hello_rust/Android.bp_:" -msgstr "_hello_rust/Android.bp_:" +"Omitting the module content will tell Rust to look for it in another file:" +msgstr "如果省略模块内容，则会指示 Rust 在另一个文件中查找：" -#: src/android/build-rules/binary.md:8 +#: src/modules/filesystem.md:9 msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust\",\n" -" crate_name: \"hello_rust\",\n" -" srcs: [\"src/main.rs\"],\n" -"}\n" -"```" +"This tells rust that the `garden` module content is found at `src/garden." +"rs`. Similarly, a `garden::vegetables` module can be found at `src/garden/" +"vegetables.rs`." msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust\",\n" -" crate_name: \"hello_rust\",\n" -" srcs: [\"src/main.rs\"],\n" -"}\n" -"```" +"这会告知 Rust 可以在“src/garden.rs”中找到“garden”模块内容。同样，您可以" +"在“src/garden/vegetables.rs”中找到“garden::vegetables”模块。" -#: src/android/build-rules/binary.md:16 src/android/build-rules/library.md:34 -msgid "_hello_rust/src/main.rs_:" -msgstr "_hello_rust/src/main.rs_:" +#: src/modules/filesystem.md:13 +msgid "The `crate` root is in:" +msgstr "“crate”根目录位于：" -#: src/android/build-rules/binary.md:18 -msgid "" -"```rust\n" -"//! Rust demo.\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"Hello from Rust!\");\n" -"}\n" -"```" -msgstr "" -"```rust\n" -"//! Rust demo.\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"Hello from Rust!\");\n" -"}\n" -"```" +#: src/modules/filesystem.md:15 +msgid "`src/lib.rs` (for a library crate)" +msgstr "“src/lib.rs”（对于库 crate）" -#: src/android/build-rules/binary.md:27 -msgid "You can now build, push, and run the binary:" -msgstr "你现在可以构建、推送和运行二进制文件：" +#: src/modules/filesystem.md:16 +msgid "`src/main.rs` (for a binary crate)" +msgstr "“src/main.rs”（对于二进制文件 crate）" -#: src/android/build-rules/binary.md:29 +#: src/modules/filesystem.md:18 msgid "" -"```shell\n" -"m hello_rust\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust /data/local/tmp\"\n" -"adb shell /data/local/tmp/hello_rust\n" -"```" +"Modules defined in files can be documented, too, using \"inner doc " +"comments\". These document the item that contains them -- in this case, a " +"module." msgstr "" +"也可以使用“内部文档注释”对文件中定义的模块进行记录。这些用于记录包含它们的项" +"（在本例中为模块）。" -#: src/android/build-rules/library.md:1 -msgid "Rust Libraries" -msgstr "Rust 库" - -#: src/android/build-rules/library.md:3 -msgid "You use `rust_library` to create a new Rust library for Android." -msgstr "您可以使用 `rust_library` 为 Android 创建一个新的 Rust 库。" - -#: src/android/build-rules/library.md:5 -msgid "Here we declare a dependency on two libraries:" -msgstr "在这里，我们声明了对两个库的依赖：" +#: src/modules/filesystem.md:22 +msgid "" +"//! This module implements the garden, including a highly performant " +"germination\n" +"//! implementation.\n" +msgstr "" -#: src/android/build-rules/library.md:7 -msgid "`libgreeting`, which we define below," -msgstr "`libgreeting`, 我们在下面进行了定义，" +#: src/modules/filesystem.md:24 +msgid "// Re-export types from this module.\n" +msgstr "" -#: src/android/build-rules/library.md:8 -msgid "" -"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" -"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" -"crates/)." +#: src/modules/filesystem.md:28 +msgid "/// Sow the given seed packets.\n" msgstr "" -"`libtextwrap`, 一个已经在 [`external/rust/crates/`](https://cs.android.com/" -"android/platform/superproject/+/master:external/rust/crates/) 中提供的 " -"crate。" -#: src/android/build-rules/library.md:15 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_with_dep\",\n" -" crate_name: \"hello_rust_with_dep\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"libgreetings\",\n" -" \"libtextwrap\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"\n" -"rust_library {\n" -" name: \"libgreetings\",\n" -" crate_name: \"greetings\",\n" -" srcs: [\"src/lib.rs\"],\n" -"}\n" -"```" +#: src/modules/filesystem.md:33 +msgid "/// Harvest the produce in the garden that is ready.\n" msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_with_dep\",\n" -" crate_name: \"hello_rust_with_dep\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"libgreetings\",\n" -" \"libtextwrap\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"\n" -"rust_library {\n" -" name: \"libgreetings\",\n" -" crate_name: \"greetings\",\n" -" srcs: [\"src/lib.rs\"],\n" -"}\n" -"```" -#: src/android/build-rules/library.md:36 +#: src/modules/filesystem.md:42 msgid "" -"```rust,ignore\n" -"//! Rust demo.\n" -"\n" -"use greetings::greeting;\n" -"use textwrap::fill;\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"{}\", fill(&greeting(\"Bob\"), 24));\n" -"}\n" -"```" +"Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " +"`module.rs`, and this is still a working alternative for editions after 2018." msgstr "" -"```rust,ignore\n" -"//! Rust demo.\n" -"\n" -"use greetings::greeting;\n" -"use textwrap::fill;\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"{}\", fill(&greeting(\"Bob\"), 24));\n" -"}\n" -"```" - -#: src/android/build-rules/library.md:48 -msgid "_hello_rust/src/lib.rs_:" -msgstr "_hello_rust/src/lib.rs_:" +"在 Rust 2018 之前的版本中，模块需要位于“module/mod.rs”而非“module.rs”中，对" +"于 2018 年之后的版本而言，这仍是有效的替代方案。" -#: src/android/build-rules/library.md:50 +#: src/modules/filesystem.md:45 msgid "" -"```rust,ignore\n" -"//! Greeting library.\n" -"\n" -"/// Greet `name`.\n" -"pub fn greeting(name: &str) -> String {\n" -" format!(\"Hello {name}, it is very nice to meet you!\")\n" -"}\n" -"```" +"The main reason to introduce `filename.rs` as alternative to `filename/mod." +"rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." msgstr "" -"```rust,ignore\n" -"//! Greeting library.\n" -"\n" -"/// Greet `name`.\n" -"pub fn greeting(name: &str) -> String {\n" -" format!(\"Hello {name}, it is very nice to meet you!\")\n" -"}\n" -"```" +"引入“filename.rs”来替代“filename/mod.rs”的主要原因是，许多名为“mod.rs”的文件" +"在 IDE 中可能难以区分。" -#: src/android/build-rules/library.md:59 -msgid "You build, push, and run the binary like before:" -msgstr "您可以像之前一样构建、推送和运行二进制文件：" +#: src/modules/filesystem.md:48 +msgid "Deeper nesting can use folders, even if the main module is a file:" +msgstr "即使主模块是文件，更深层的嵌套也可以使用文件夹：" -#: src/android/build-rules/library.md:61 +#: src/modules/filesystem.md:58 msgid "" -"```shell\n" -"m hello_rust_with_dep\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_with_dep\n" -"```" +"The place rust will look for modules can be changed with a compiler " +"directive:" +msgstr "Rust 寻找模块的位置可通过编译器指令更改：" + +#: src/modules/filesystem.md:61 +msgid "\"some/path.rs\"" msgstr "" -#: src/android/aidl.md:3 +#: src/modules/filesystem.md:65 msgid "" -"The [Android Interface Definition Language (AIDL)](https://developer.android." -"com/guide/components/aidl) is supported in Rust:" +"This is useful, for example, if you would like to place tests for a module " +"in a file named `some_module_test.rs`, similar to the convention in Go." msgstr "" -"Rust 支持 [Android 接口定义语言 (AIDL)](https://developer.android.com/guide/" -"components/aidl)：" - -#: src/android/aidl.md:6 -msgid "Rust code can call existing AIDL servers," -msgstr "Rust 代码可以调用现有的 AIDL 服务器，" +"例如，如果您想将某个模块的测试放在名为“some_module_test.rs”的文件中（类似于 " +"Go 中的惯例），这样做很有用。" -#: src/android/aidl.md:7 -msgid "You can create new AIDL servers in Rust." -msgstr "您可以在 Rust 中创建新的 AIDL 服务器。" +#: src/modules/visibility.md:3 +msgid "Modules are a privacy boundary:" +msgstr "模块是一种隐私边界：" -#: src/android/aidl/interface.md:1 -msgid "AIDL Interfaces" -msgstr "AIDL 接口" +#: src/modules/visibility.md:5 +msgid "Module items are private by default (hides implementation details)." +msgstr "默认情况下，模块项是私有的（隐藏实现详情）。" -#: src/android/aidl/interface.md:3 -msgid "You declare the API of your service using an AIDL interface:" -msgstr "您可以使用 AIDL 接口声明您的服务的 API：" +#: src/modules/visibility.md:6 +msgid "Parent and sibling items are always visible." +msgstr "父项和同级子项始终可见。" -#: src/android/aidl/interface.md:5 +#: src/modules/visibility.md:7 msgid "" -"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +"In other words, if an item is visible in module `foo`, it's visible in all " +"the descendants of `foo`." msgstr "" -"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +"换言之，如果某个项在模块“foo”中可见，那么该项在“foo”的所有后代中均可见。" -#: src/android/aidl/interface.md:17 -msgid "_birthday_service/aidl/Android.bp_:" -msgstr "_birthday_service/aidl/Android.bp_:" +#: src/modules/visibility.md:13 +msgid "\"outer::private\"" +msgstr "" -#: src/android/aidl/interface.md:19 -msgid "" -"```javascript\n" -"aidl_interface {\n" -" name: \"com.example.birthdayservice\",\n" -" srcs: [\"com/example/birthdayservice/*.aidl\"],\n" -" unstable: true,\n" -" backend: {\n" -" rust: { // Rust is not enabled by default\n" -" enabled: true,\n" -" },\n" -" },\n" -"}\n" -"```" +#: src/modules/visibility.md:17 +msgid "\"outer::public\"" msgstr "" -"```javascript\n" -"aidl_interface {\n" -" name: \"com.example.birthdayservice\",\n" -" srcs: [\"com/example/birthdayservice/*.aidl\"],\n" -" unstable: true,\n" -" backend: {\n" -" rust: { // 默认情况下不启用 Rust \n" -" enabled: true,\n" -" },\n" -" },\n" -"}\n" -"```" -#: src/android/aidl/interface.md:32 -msgid "" -"Add `vendor_available: true` if your AIDL file is used by a binary in the " -"vendor partition." +#: src/modules/visibility.md:22 +msgid "\"outer::inner::private\"" msgstr "" -"如果供应商分区中的二进制文件使用了您的 AIDL 文件，请添加 `vendor_available: " -"true`。" -#: src/android/aidl/implementation.md:1 -msgid "Service Implementation" -msgstr "服务实现" +#: src/modules/visibility.md:26 +msgid "\"outer::inner::public\"" +msgstr "" -#: src/android/aidl/implementation.md:3 -msgid "We can now implement the AIDL service:" -msgstr "我们现在可以实现AIDL服务：" +#: src/modules/visibility.md:39 +msgid "Use the `pub` keyword to make modules public." +msgstr "使用“pub”关键字将模块设为公开。" -#: src/android/aidl/implementation.md:5 -msgid "_birthday_service/src/lib.rs_:" -msgstr "_birthday_service/src/lib.rs_:" +#: src/modules/visibility.md:41 +msgid "" +"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " +"of public visibility." +msgstr "此外，您还可以使用高级“pub(...)”说明符来限制公开可见的范围。" -#: src/android/aidl/implementation.md:7 +#: src/modules/visibility.md:44 msgid "" -"```rust,ignore\n" -"//! Implementation of the `IBirthdayService` AIDL interface.\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"/// The `IBirthdayService` implementation.\n" -"pub struct BirthdayService;\n" -"\n" -"impl binder::Interface for BirthdayService {}\n" -"\n" -"impl IBirthdayService for BirthdayService {\n" -" fn wishHappyBirthday(&self, name: &str, years: i32) -> binder::" -"Result {\n" -" Ok(format!(\n" -" \"Happy Birthday {name}, congratulations with the {years} years!" -"\"\n" -" ))\n" -" }\n" -"}\n" -"```" +"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" +"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." msgstr "" -"```rust,ignore\n" -"//! 实现了 `IBirthdayService` AIDL 接口。\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"/// `IBirthdayService` 接口的具体实现。\n" -"pub struct BirthdayService;\n" -"\n" -"impl binder::Interface for BirthdayService {}\n" -"\n" -"impl IBirthdayService for BirthdayService {\n" -" fn wishHappyBirthday(&self, name: &str, years: i32) -> binder::" -"Result {\n" -" Ok(format!(\n" -" \"Happy Birthday {name}, congratulations with the {years} years!" -"\"\n" -" ))\n" -" }\n" -"}\n" -"```" - -#: src/android/aidl/implementation.md:26 src/android/aidl/server.md:28 -#: src/android/aidl/client.md:37 -msgid "_birthday_service/Android.bp_:" -msgstr "_birthday_service/Android.bp_:" +"请参阅 [Rust 参考](https://doc.rust-lang.org/reference/visibility-and-" +"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)。" -#: src/android/aidl/implementation.md:28 -msgid "" -"```javascript\n" -"rust_library {\n" -" name: \"libbirthdayservice\",\n" -" srcs: [\"src/lib.rs\"],\n" -" crate_name: \"birthdayservice\",\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -"}\n" -"```" -msgstr "" -"```javascript\n" -"rust_library {\n" -" name: \"libbirthdayservice\",\n" -" srcs: [\"src/lib.rs\"],\n" -" crate_name: \"birthdayservice\",\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -"}\n" -"```" +#: src/modules/visibility.md:46 +msgid "Configuring `pub(crate)` visibility is a common pattern." +msgstr "配置“pub(crate)”可见性是一种常见模式。" -#: src/android/aidl/server.md:1 -msgid "AIDL Server" -msgstr "AIDL 服务器" +#: src/modules/visibility.md:47 +msgid "Less commonly, you can give visibility to a specific path." +msgstr "您可以为特定路径授予可见性，这种情况不太常见。" -#: src/android/aidl/server.md:3 -msgid "Finally, we can create a server which exposes the service:" -msgstr "最后，我们可以创建一个暴露服务的服务器：" +#: src/modules/visibility.md:48 +msgid "" +"In any case, visibility must be granted to an ancestor module (and all of " +"its descendants)." +msgstr "在任何情况下，都必须向祖先模块（及其所有后代）授予可见性。" -#: src/android/aidl/server.md:5 -msgid "_birthday_service/src/server.rs_:" -msgstr "_birthday_service/src/server.rs_:" +#: src/modules/paths.md:1 +msgid "use, super, self" +msgstr "" -#: src/android/aidl/server.md:7 +#: src/modules/paths.md:3 msgid "" -"```rust,ignore\n" -"//! Birthday service.\n" -"use birthdayservice::BirthdayService;\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::BnBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// Entry point for birthday service.\n" -"fn main() {\n" -" let birthday_service = BirthdayService;\n" -" let birthday_service_binder = BnBirthdayService::new_binder(\n" -" birthday_service,\n" -" binder::BinderFeatures::default(),\n" -" );\n" -" binder::add_service(SERVICE_IDENTIFIER, birthday_service_binder." -"as_binder())\n" -" .expect(\"Failed to register service\");\n" -" binder::ProcessState::join_thread_pool()\n" -"}\n" -"```" +"A module can bring symbols from another module into scope with `use`. You " +"will typically see something like this at the top of each module:" msgstr "" -"```rust,ignore\n" -"//! 生日服务。\n" -"use birthdayservice::BirthdayService;\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::BnBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// 生日服务的入口。\n" -"fn main() {\n" -" let birthday_service = BirthdayService;\n" -" let birthday_service_binder = BnBirthdayService::new_binder(\n" -" birthday_service,\n" -" binder::BinderFeatures::default(),\n" -" );\n" -" binder::add_service(SERVICE_IDENTIFIER, birthday_service_binder." -"as_binder())\n" -" .expect(\"Failed to register service\");\n" -" binder::ProcessState::join_thread_pool()\n" -"}\n" -"```" +"一个模块可以使用“use”将另一个模块的符号全部纳入。您通常在每个模块的顶部会看到" +"如下内容：" -#: src/android/aidl/server.md:30 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_server\",\n" -" crate_name: \"birthday_server\",\n" -" srcs: [\"src/server.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" \"libbirthdayservice\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" -msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_server\",\n" -" crate_name: \"birthday_server\",\n" -" srcs: [\"src/server.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" \"libbirthdayservice\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" +#: src/modules/paths.md:11 +msgid "Paths" +msgstr "路径" -#: src/android/aidl/deploy.md:3 -msgid "We can now build, push, and start the service:" -msgstr "我们现在可以构建、推送和启动服务：" +#: src/modules/paths.md:13 +msgid "Paths are resolved as follows:" +msgstr "路径解析如下：" -#: src/android/aidl/deploy.md:5 -msgid "" -"```shell\n" -"m birthday_server\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_server\n" -"```" -msgstr "" +#: src/modules/paths.md:15 +msgid "As a relative path:" +msgstr "作为相对路径：" -#: src/android/aidl/deploy.md:11 -msgid "In another terminal, check that the service runs:" -msgstr "在另一个终端中，检查该服务是否正在运行：" +#: src/modules/paths.md:16 +msgid "`foo` or `self::foo` refers to `foo` in the current module," +msgstr "`foo` 或 `self::foo` 是指当前模块中的 `foo`，" -#: src/android/aidl/deploy.md:21 -msgid "You can also call the service with `service call`:" -msgstr "您还可以使用 `service call` 命令调用该服务：" +#: src/modules/paths.md:17 +msgid "`super::foo` refers to `foo` in the parent module." +msgstr "“super::foo”是指父模块中的“foo”。" -#: src/android/aidl/client.md:1 -msgid "AIDL Client" -msgstr "AIDL 客户端" +#: src/modules/paths.md:19 +msgid "As an absolute path:" +msgstr "作为绝对路径：" -#: src/android/aidl/client.md:3 -msgid "Finally, we can create a Rust client for our new service." -msgstr "最后，我们可以为我们的新服务创建一个 Rust 客户端。" +#: src/modules/paths.md:20 +msgid "`crate::foo` refers to `foo` in the root of the current crate," +msgstr "`crate::foo` 是指当前 crate 的根中的 `foo`，" -#: src/android/aidl/client.md:5 -msgid "_birthday_service/src/client.rs_:" -msgstr "_birthday_service/src/client.rs_:" +#: src/modules/paths.md:21 +msgid "`bar::foo` refers to `foo` in the `bar` crate." +msgstr "“bar::foo”是指“bar”crate 中的“foo”。" -#: src/android/aidl/client.md:7 +#: src/modules/paths.md:25 msgid "" -"```rust,ignore\n" -"//! Birthday service.\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// Connect to the BirthdayService.\n" -"pub fn connect() -> Result, binder::" -"StatusCode> {\n" -" binder::get_interface(SERVICE_IDENTIFIER)\n" -"}\n" -"\n" -"/// Call the birthday service.\n" -"fn main() -> Result<(), binder::Status> {\n" -" let name = std::env::args()\n" -" .nth(1)\n" -" .unwrap_or_else(|| String::from(\"Bob\"));\n" -" let years = std::env::args()\n" -" .nth(2)\n" -" .and_then(|arg| arg.parse::().ok())\n" -" .unwrap_or(42);\n" -"\n" -" binder::ProcessState::start_thread_pool();\n" -" let service = connect().expect(\"Failed to connect to " -"BirthdayService\");\n" -" let msg = service.wishHappyBirthday(&name, years)?;\n" -" println!(\"{msg}\");\n" -" Ok(())\n" -"}\n" -"```" +"It is common to \"re-export\" symbols at a shorter path. For example, the " +"top-level `lib.rs` in a crate might have" msgstr "" -"```rust,ignore\n" -"//! 生日服务。\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// 连接到 BirthdayService。\n" -"pub fn connect() -> Result, binder::" -"StatusCode> {\n" -" binder::get_interface(SERVICE_IDENTIFIER)\n" -"}\n" -"\n" -"/// 调用生日服务。\n" -"fn main() -> Result<(), binder::Status> {\n" -" let name = std::env::args()\n" -" .nth(1)\n" -" .unwrap_or_else(|| String::from(\"Bob\"));\n" -" let years = std::env::args()\n" -" .nth(2)\n" -" .and_then(|arg| arg.parse::().ok())\n" -" .unwrap_or(42);\n" -"\n" -" binder::ProcessState::start_thread_pool();\n" -" let service = connect().expect(\"Failed to connect to " -"BirthdayService\");\n" -" let msg = service.wishHappyBirthday(&name, years)?;\n" -" println!(\"{msg}\");\n" -" Ok(())\n" -"}\n" -"```" -#: src/android/aidl/client.md:39 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_client\",\n" -" crate_name: \"birthday_client\",\n" -" srcs: [\"src/client.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" +#: src/modules/paths.md:35 +msgid "" +"making `DiskStorage` and `NetworkStorage` available to other crates with a " +"convenient, short path." msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_client\",\n" -" crate_name: \"birthday_client\",\n" -" srcs: [\"src/client.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" - -#: src/android/aidl/client.md:52 -msgid "Notice that the client does not depend on `libbirthdayservice`." -msgstr "请注意，客户端不依赖于 `libbirthdayservice`。" - -#: src/android/aidl/client.md:54 -msgid "Build, push, and run the client on your device:" -msgstr "在您的设备上构建、推送并运行客户端：" -#: src/android/aidl/client.md:56 +#: src/modules/paths.md:38 msgid "" -"```shell\n" -"m birthday_client\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_client Charlie 60\n" -"```" +"For the most part, only items that appear in a module need to be `use`'d. " +"However, a trait must be in scope to call any methods on that trait, even if " +"a type implementing that trait is already in scope. For example, to use the " +"`read_to_string` method on a type implementing the `Read` trait, you need to " +"`use std::io::Read`." msgstr "" -#: src/android/aidl/changing.md:3 +#: src/modules/paths.md:44 msgid "" -"Let us extend the API with more functionality: we want to let clients " -"specify a list of lines for the birthday card:" -msgstr "让我们扩展API以提供更多功能：我们希望允许客户端指定生日贺卡的行列表：" +"The `use` statement can have a wildcard: `use std::io::*`. This is " +"discouraged because it is not clear which items are imported, and those " +"might change over time." +msgstr "" -#: src/android/logging.md:3 +#: src/modules/exercise.md:3 msgid "" -"You should use the `log` crate to automatically log to `logcat` (on-device) " -"or `stdout` (on-host):" +"In this exercise, you will reorganize the GUI Library exercise from the " +"\"Methods and Traits\" segment of the course into a collection of modules. " +"It is typical to put each type or set of closely-related types into its own " +"module, so each widget type should get its own module." msgstr "" -"你应该使用 `log` crate 来自动记录日志到 `logcat` （设备上）或 `stdout`（主机" -"上）：" -#: src/android/logging.md:6 -msgid "_hello_rust_logs/Android.bp_:" -msgstr "_hello_rust_logs/Android.bp_:" - -#: src/android/logging.md:8 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_logs\",\n" -" crate_name: \"hello_rust_logs\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"liblog_rust\",\n" -" \"liblogger\",\n" -" ],\n" -" prefer_rlib: true,\n" -" host_supported: true,\n" -"}\n" -"```" +#: src/modules/exercise.md:8 +msgid "" +"If you no longer have your version, that's fine - refer back to the " +"[provided solution](../methods-and-traits/solution.html)." msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_logs\",\n" -" crate_name: \"hello_rust_logs\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"liblog_rust\",\n" -" \"liblogger\",\n" -" ],\n" -" prefer_rlib: true,\n" -" host_supported: true,\n" -"}\n" -"```" -#: src/android/logging.md:22 -msgid "_hello_rust_logs/src/main.rs_:" -msgstr "_hello_rust_logs/src/main.rs_:" +#: src/modules/exercise.md:11 +#, fuzzy +msgid "Cargo Setup" +msgstr "设置" -#: src/android/logging.md:24 +#: src/modules/exercise.md:13 msgid "" -"```rust,ignore\n" -"//! Rust logging demo.\n" -"\n" -"use log::{debug, error, info};\n" -"\n" -"/// Logs a greeting.\n" -"fn main() {\n" -" logger::init(\n" -" logger::Config::default()\n" -" .with_tag_on_device(\"rust\")\n" -" .with_min_level(log::Level::Trace),\n" -" );\n" -" debug!(\"Starting program.\");\n" -" info!(\"Things are going fine.\");\n" -" error!(\"Something went wrong!\");\n" -"}\n" -"```" +"The Rust playground only supports one file, so you will need to make a Cargo " +"project on your local filesystem:" msgstr "" -"```rust,ignore\n" -"//! Rust logging demo.\n" -"\n" -"use log::{debug, error, info};\n" -"\n" -"/// Logs a greeting.\n" -"fn main() {\n" -" logger::init(\n" -" logger::Config::default()\n" -" .with_tag_on_device(\"rust\")\n" -" .with_min_level(log::Level::Trace),\n" -" );\n" -" debug!(\"Starting program.\");\n" -" info!(\"Things are going fine.\");\n" -" error!(\"Something went wrong!\");\n" -"}\n" -"```" -#: src/android/logging.md:42 src/android/interoperability/with-c/bindgen.md:98 -#: src/android/interoperability/with-c/rust.md:73 -msgid "Build, push, and run the binary on your device:" -msgstr "在你的设备上构建，推送，并运行二进制文件 ：" +#: src/modules/exercise.md:22 +msgid "" +"Edit `src/main.rs` to add `mod` statements, and add additional files in the " +"`src` directory." +msgstr "" -#: src/android/logging.md:44 +#: src/modules/exercise.md:27 msgid "" -"```shell\n" -"m hello_rust_logs\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_logs\n" -"```" +"Encourage students to divide the code in a way that feels natural for them, " +"and get accustomed to the required `mod`, `use`, and `pub` declarations. " +"Afterward, discuss what organizations are most idiomatic." msgstr "" -#: src/android/logging.md:50 -msgid "The logs show up in `adb logcat`:" -msgstr "日志将会在 `adb logcat` 中显示：" +#: src/modules/solution.md:30 +msgid "// ---- src/widgets.rs ----\n" +msgstr "" -#: src/android/interoperability.md:3 -msgid "" -"Rust has excellent support for interoperability with other languages. This " -"means that you can:" -msgstr "Rust 对于与其他编程语言的互操作性有着出色的支持。这意味着您可以：" +#: src/modules/solution.md:56 +msgid "// ---- src/widgets/label.rs ----\n" +msgstr "" -#: src/android/interoperability.md:6 -msgid "Call Rust functions from other languages." -msgstr "从其他语言调用 Rust 函数。" +#: src/modules/solution.md:71 +msgid "// ANCHOR_END: Label-width\n" +msgstr "" -#: src/android/interoperability.md:7 -msgid "Call functions written in other languages from Rust." -msgstr "从 Rust 调用用其他语言编写的函数。" +#: src/modules/solution.md:75 +msgid "// ANCHOR: Label-draw_into\n" +msgstr "" -#: src/android/interoperability.md:9 -msgid "" -"When you call functions in a foreign language we say that you're using a " -"_foreign function interface_, also known as FFI." +#: src/modules/solution.md:77 +msgid "// ANCHOR_END: Label-draw_into\n" msgstr "" -"当您从外部语言调用函数时，我们称之为使用 **外部函数接口**（*Foreign Function " -"Interface*， FFI）。" -#: src/android/interoperability/with-c.md:1 -msgid "Interoperability with C" -msgstr "与 C 的互操作性" +#: src/modules/solution.md:84 +msgid "// ---- src/widgets/button.rs ----\n" +msgstr "" -#: src/android/interoperability/with-c.md:3 -msgid "" -"Rust has full support for linking object files with a C calling convention. " -"Similarly, you can export Rust functions and call them from C." +#: src/modules/solution.md:99 +msgid "// ANCHOR_END: Button-width\n" msgstr "" -"Rust 对使用 C 调用约定链接目标文件提供了完整的支持。同样地，你可以导出 Rust " -"函数并从 C 中调用它们。" -#: src/android/interoperability/with-c.md:6 -msgid "You can do it by hand if you want:" -msgstr "如果你愿意的话，你可以手工完成它：" +#: src/modules/solution.md:103 +msgid "// ANCHOR: Button-draw_into\n" +msgstr "" -#: src/android/interoperability/with-c.md:8 -msgid "" -"```rust\n" -"extern \"C\" {\n" -" fn abs(x: i32) -> i32;\n" -"}\n" -"\n" -"fn main() {\n" -" let x = -42;\n" -" let abs_x = unsafe { abs(x) };\n" -" println!(\"{x}, {abs_x}\");\n" -"}\n" -"```" +#: src/modules/solution.md:105 +msgid "// ANCHOR_END: Button-draw_into\n" msgstr "" -"```rust\n" -"extern \"C\" {\n" -" fn abs(x: i32) -> i32;\n" -"}\n" -"\n" -"fn main() {\n" -" let x = -42;\n" -" let abs_x = unsafe { abs(x) };\n" -" println!(\"{x}, {abs_x}\");\n" -"}\n" -"```" -#: src/android/interoperability/with-c.md:20 -msgid "" -"We already saw this in the [Safe FFI Wrapper exercise](../../exercises/day-3/" -"safe-ffi-wrapper.md)." +#: src/modules/solution.md:120 +msgid "// ---- src/widgets/window.rs ----\n" msgstr "" -"我们已经在[安全 FFI 封装容器](../../exercises/day-3/safe-ffi-wrapper.md)练习" -"中看到了这个例子。" -#: src/android/interoperability/with-c.md:23 +#: src/modules/solution.md:147 msgid "" -"This assumes full knowledge of the target platform. Not recommended for " -"production." -msgstr "这假设对目标平台拥有充分的了解，不建议用于生产环境。" +"// ANCHOR_END: Window-width\n" +" // Add 4 paddings for borders\n" +msgstr "" -#: src/android/interoperability/with-c.md:26 -msgid "We will look at better options next." -msgstr "接下来我们将探讨更好的选择。" +#: src/modules/solution.md:152 +msgid "// ANCHOR: Window-draw_into\n" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:1 -msgid "Using Bindgen" -msgstr "使用 Bindgen" +#: src/modules/solution.md:154 +msgid "// ANCHOR_END: Window-draw_into\n" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:3 -msgid "" -"The [bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) " -"tool can auto-generate bindings from a C header file." +#: src/modules/solution.md:177 +msgid "// ---- src/main.rs ----\n" msgstr "" -"[bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) 工具可" -"以自动生成 C 头文件的绑定代码。" -#: src/android/interoperability/with-c/bindgen.md:6 -msgid "First create a small C library:" -msgstr "首先创建一个小型的 C 语言库：" +#: src/testing/unit-tests.md:1 +msgid "Unit Tests" +msgstr "单元测试" -#: src/android/interoperability/with-c/bindgen.md:8 -msgid "_interoperability/bindgen/libbirthday.h_:" -msgstr "interoperability/bindgen/libbirthday.h:" +#: src/testing/unit-tests.md:3 +msgid "Rust and Cargo come with a simple unit test framework:" +msgstr "Rust 和 Cargo 随附了一个简单的单元测试框架：" -#: src/android/interoperability/with-c/bindgen.md:19 -msgid "_interoperability/bindgen/libbirthday.c_:" -msgstr "_interoperability/bindgen/libbirthday.c_:" +#: src/testing/unit-tests.md:5 +msgid "Unit tests are supported throughout your code." +msgstr "单元测试在您的整个代码中都受支持。" -#: src/android/interoperability/with-c/bindgen.md:21 +#: src/testing/unit-tests.md:7 +msgid "Integration tests are supported via the `tests/` directory." +msgstr "您可以通过 `tests/` 目录来支持集成测试。" + +#: src/testing/unit-tests.md:9 msgid "" -"```c\n" -"#include \n" -"#include \"libbirthday.h\"\n" -"\n" -"void print_card(const card* card) {\n" -" printf(\"+--------------\\n\");\n" -" printf(\"| Happy Birthday %s!\\n\", card->name);\n" -" printf(\"| Congratulations with the %i years!\\n\", card->years);\n" -" printf(\"+--------------\\n\");\n" -"}\n" -"```" +"Tests are marked with `#[test]`. Unit tests are often put in a nested " +"`tests` module, using `#[cfg(test)]` to conditionally compile them only when " +"building tests." msgstr "" -"```c\n" -"#include \n" -"#include \"libbirthday.h\"\n" -"\n" -"void print_card(const card* card) {\n" -" printf(\"+--------------\\n\");\n" -" printf(\"| Happy Birthday %s!\\n\", card->name);\n" -" printf(\"| Congratulations with the %i years!\\n\", card->years);\n" -" printf(\"+--------------\\n\");\n" -"}\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:33 -msgid "Add this to your `Android.bp` file:" -msgstr "将该库添加到你的 `Android.bp` 文件中：" +#: src/testing/unit-tests.md:37 +#, fuzzy +msgid "\"Hello World\"" +msgstr "Hello World!" -#: src/android/interoperability/with-c/bindgen.md:35 -#: src/android/interoperability/with-c/bindgen.md:55 -#: src/android/interoperability/with-c/bindgen.md:69 -#: src/android/interoperability/with-c/bindgen.md:108 -msgid "_interoperability/bindgen/Android.bp_:" -msgstr "_interoperability/bindgen/Android.bp_:" +#: src/testing/unit-tests.md:42 +msgid "This lets you unit test private helpers." +msgstr "这样一来，您可以对专用帮助程序进行单元测试。" -#: src/android/interoperability/with-c/bindgen.md:37 -msgid "" -"```javascript\n" -"cc_library {\n" -" name: \"libbirthday\",\n" -" srcs: [\"libbirthday.c\"],\n" -"}\n" -"```" +#: src/testing/unit-tests.md:43 +msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." +msgstr "仅当您运行 `cargo test` 时，`#[cfg(test)]` 属性才有效。" + +#: src/testing/unit-tests.md:47 +msgid "Run the tests in the playground in order to show their results." msgstr "" -"```javascript\n" -"cc_library {\n" -" name: \"libbirthday\",\n" -" srcs: [\"libbirthday.c\"],\n" -"}\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:44 -msgid "" -"Create a wrapper header file for the library (not strictly needed in this " -"example):" -msgstr "为该库创建一个包装头文件（在此示例中不是必需的）：" +#: src/testing/other.md:3 +msgid "Integration Tests" +msgstr "集成测试" -#: src/android/interoperability/with-c/bindgen.md:47 -msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" -msgstr "_interoperability/bindgen/libbirthday_wrapper.h_:" +#: src/testing/other.md:5 +msgid "If you want to test your library as a client, use an integration test." +msgstr "如果您想要以客户的身份测试您的库，请使用集成测试。" -#: src/android/interoperability/with-c/bindgen.md:49 -msgid "" -"```c\n" -"#include \"libbirthday.h\"\n" -"```" +#: src/testing/other.md:7 +msgid "Create a `.rs` file under `tests/`:" +msgstr "在 `tests/` 下方创建一个 `.rs` 文件：" + +#: src/testing/other.md:10 +msgid "// tests/my_library.rs\n" msgstr "" -"```c\n" -"#include \"libbirthday.h\"\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:53 -msgid "You can now auto-generate the bindings:" -msgstr "您现在可以自动生成绑定代码：" +#: src/testing/other.md:19 +msgid "These tests only have access to the public API of your crate." +msgstr "这些测试只能使用您的 crate 的公共 API。" -#: src/android/interoperability/with-c/bindgen.md:57 -msgid "" -"```javascript\n" -"rust_bindgen {\n" -" name: \"libbirthday_bindgen\",\n" -" crate_name: \"birthday_bindgen\",\n" -" wrapper_src: \"libbirthday_wrapper.h\",\n" -" source_stem: \"bindings\",\n" -" static_libs: [\"libbirthday\"],\n" -"}\n" -"```" -msgstr "" -"```javascript\n" -"rust_bindgen {\n" -" name: \"libbirthday_bindgen\",\n" -" crate_name: \"birthday_bindgen\",\n" -" wrapper_src: \"libbirthday_wrapper.h\",\n" -" source_stem: \"bindings\",\n" -" static_libs: [\"libbirthday\"],\n" -"}\n" -"```" +#: src/testing/other.md:21 +msgid "Documentation Tests" +msgstr "文档测试" -#: src/android/interoperability/with-c/bindgen.md:67 -msgid "Finally, we can use the bindings in our Rust program:" -msgstr "最后，我们可以在 Rust 程序中使用这些绑定：" +#: src/testing/other.md:23 +msgid "Rust has built-in support for documentation tests:" +msgstr "Rust 本身就支持文档测试：" -#: src/android/interoperability/with-c/bindgen.md:71 +#: src/testing/other.md:26 msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"print_birthday_card\",\n" -" srcs: [\"main.rs\"],\n" -" rustlibs: [\"libbirthday_bindgen\"],\n" -"}\n" -"```" +"/// Shortens a string to the given length.\n" +"///\n" +"/// ```\n" +"/// # use playground::shorten_string;\n" +"/// assert_eq!(shorten_string(\"Hello World\", 5), \"Hello\");\n" +"/// assert_eq!(shorten_string(\"Hello World\", 20), \"Hello World\");\n" +"/// ```\n" msgstr "" -"```javascript\n" -"rust_binary {\n" -" name: \"print_birthday_card\",\n" -" srcs: [\"main.rs\"],\n" -" rustlibs: [\"libbirthday_bindgen\"],\n" -"}\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:79 -msgid "_interoperability/bindgen/main.rs_:" -msgstr "_interoperability/bindgen/main.rs_:" +#: src/testing/other.md:38 +msgid "Code blocks in `///` comments are automatically seen as Rust code." +msgstr "`///` 注释中的代码块会自动被视为 Rust 代码。" + +#: src/testing/other.md:39 +msgid "The code will be compiled and executed as part of `cargo test`." +msgstr "代码会作为 `cargo test` 的一部分进行编译和执行。" -#: src/android/interoperability/with-c/bindgen.md:81 +#: src/testing/other.md:40 msgid "" -"```rust,compile_fail\n" -"//! Bindgen demo.\n" -"\n" -"use birthday_bindgen::{card, print_card};\n" -"\n" -"fn main() {\n" -" let name = std::ffi::CString::new(\"Peter\").unwrap();\n" -" let card = card {\n" -" name: name.as_ptr(),\n" -" years: 42,\n" -" };\n" -" unsafe {\n" -" print_card(&card as *const card);\n" -" }\n" -"}\n" -"```" +"Adding `#` in the code will hide it from the docs, but will still compile/" +"run it." msgstr "" -"```rust,compile_fail\n" -"//! Bindgen demo.\n" -"\n" -"use birthday_bindgen::{card, print_card};\n" -"\n" -"fn main() {\n" -" let name = std::ffi::CString::new(\"Peter\").unwrap();\n" -" let card = card {\n" -" name: name.as_ptr(),\n" -" years: 42,\n" -" };\n" -" unsafe {\n" -" print_card(&card as *const card);\n" -" }\n" -"}\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:100 +#: src/testing/other.md:42 msgid "" -"```shell\n" -"m print_birthday_card\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/print_birthday_card\n" -"```" +"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" +"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." msgstr "" -"```shell\n" -"m print_birthday_card\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/print_birthday_card\n" -"```" +"在 [Rust Playground](https://play.rust-lang.org/?" +"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0) " +"上测试上述代码。" -#: src/android/interoperability/with-c/bindgen.md:106 -msgid "Finally, we can run auto-generated tests to ensure the bindings work:" -msgstr "最后，我们可以运行自动生成的测试来确保绑定代码正常工作：" +#: src/testing/useful-crates.md:3 +msgid "Rust comes with only basic support for writing tests." +msgstr "Rust 仅为编写测试提供基本支持。" -#: src/android/interoperability/with-c/bindgen.md:110 +#: src/testing/useful-crates.md:5 +msgid "Here are some additional crates which we recommend for writing tests:" +msgstr "下面列出了我们建议在编写测试时使用的一些其他 crate：" + +#: src/testing/useful-crates.md:7 msgid "" -"```javascript\n" -"rust_test {\n" -" name: \"libbirthday_bindgen_test\",\n" -" srcs: [\":libbirthday_bindgen\"],\n" -" crate_name: \"libbirthday_bindgen_test\",\n" -" test_suites: [\"general-tests\"],\n" -" auto_gen_config: true,\n" -" clippy_lints: \"none\", // Generated file, skip linting\n" -" lints: \"none\",\n" -"}\n" -"```" +"[googletest](https://docs.rs/googletest): Comprehensive test assertion " +"library in the tradition of GoogleTest for C++." msgstr "" -"```javascript\n" -"rust_test {\n" -" name: \"libbirthday_bindgen_test\",\n" -" srcs: [\":libbirthday_bindgen\"],\n" -" crate_name: \"libbirthday_bindgen_test\",\n" -" test_suites: [\"general-tests\"],\n" -" auto_gen_config: true,\n" -" clippy_lints: \"none\", // Generated file, skip linting\n" -" lints: \"none\",\n" -"}\n" -"```" - -#: src/android/interoperability/with-c/rust.md:1 -msgid "Calling Rust" -msgstr "调用 Rust" +"[googletest](https://docs.rs/googletest)：遵从 GoogleTest for C++ 传统的综合" +"测试断言库。" -#: src/android/interoperability/with-c/rust.md:3 -msgid "Exporting Rust functions and types to C is easy:" -msgstr "将 Rust 函数和类型导出到 C 很简单：" +#: src/testing/useful-crates.md:9 +msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." +msgstr "[proptest](https://docs.rs/proptest)：基于属性的测试，适用于 Rust。" -#: src/android/interoperability/with-c/rust.md:5 -msgid "_interoperability/rust/libanalyze/analyze.rs_" -msgstr "_interoperability/rust/libanalyze/analyze.rs_" +#: src/testing/useful-crates.md:10 +msgid "" +"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " +"tests." +msgstr "[rstest](https://docs.rs/rstest)：支持固件和参数化测试。" -#: src/android/interoperability/with-c/rust.md:7 +#: src/testing/googletest.md:3 +#, fuzzy msgid "" -"```rust,editable\n" -"//! Rust FFI demo.\n" -"#![deny(improper_ctypes_definitions)]\n" -"\n" -"use std::os::raw::c_int;\n" -"\n" -"/// Analyze the numbers.\n" -"#[no_mangle]\n" -"pub extern \"C\" fn analyze_numbers(x: c_int, y: c_int) {\n" -" if x < y {\n" -" println!(\"x ({x}) is smallest!\");\n" -" } else {\n" -" println!(\"y ({y}) is probably larger than x ({x})\");\n" -" }\n" -"}\n" -"```" +"The [GoogleTest](https://docs.rs/googletest/) crate allows for flexible test " +"assertions using _matchers_:" msgstr "" -"```rust,editable\n" -"//! Rust FFI demo.\n" -"#![deny(improper_ctypes_definitions)]\n" -"\n" -"use std::os::raw::c_int;\n" -"\n" -"/// Analyze the numbers.\n" -"#[no_mangle]\n" -"pub extern \"C\" fn analyze_numbers(x: c_int, y: c_int) {\n" -" if x < y {\n" -" println!(\"x ({x}) is smallest!\");\n" -" } else {\n" -" println!(\"y ({y}) is probably larger than x ({x})\");\n" -" }\n" -"}\n" -"```" - -#: src/android/interoperability/with-c/rust.md:24 -msgid "_interoperability/rust/libanalyze/analyze.h_" -msgstr "_interoperability/rust/libanalyze/analyze.h_" +"[googletest](https://docs.rs/googletest)：遵从 GoogleTest for C++ 传统的综合" +"测试断言库。" -#: src/android/interoperability/with-c/rust.md:26 -msgid "" -"```c\n" -"#ifndef ANALYSE_H\n" -"#define ANALYSE_H\n" -"\n" -"extern \"C\" {\n" -"void analyze_numbers(int x, int y);\n" -"}\n" -"\n" -"#endif\n" -"```" +#: src/testing/googletest.md:11 +msgid "\"baz\"" msgstr "" -"```c\n" -"#ifndef ANALYSE_H\n" -"#define ANALYSE_H\n" -"\n" -"extern \"C\" {\n" -"void analyze_numbers(int x, int y);\n" -"}\n" -"\n" -"#endif\n" -"```" -#: src/android/interoperability/with-c/rust.md:37 -msgid "_interoperability/rust/libanalyze/Android.bp_" -msgstr "_interoperability/rust/libanalyze/Android.bp_" +#: src/testing/googletest.md:12 +msgid "\"xyz\"" +msgstr "" -#: src/android/interoperability/with-c/rust.md:39 +#: src/testing/googletest.md:16 msgid "" -"```javascript\n" -"rust_ffi {\n" -" name: \"libanalyze_ffi\",\n" -" crate_name: \"analyze_ffi\",\n" -" srcs: [\"analyze.rs\"],\n" -" include_dirs: [\".\"],\n" -"}\n" -"```" +"If we change the last element to `\"!\"`, the test fails with a structured " +"error message pin-pointing the error:" msgstr "" -"```javascript\n" -"rust_ffi {\n" -" name: \"libanalyze_ffi\",\n" -" crate_name: \"analyze_ffi\",\n" -" srcs: [\"analyze.rs\"],\n" -" include_dirs: [\".\"],\n" -"}\n" -"```" - -#: src/android/interoperability/with-c/rust.md:48 -msgid "We can now call this from a C binary:" -msgstr "我们现在可以从一个 C 二进制文件中调用它：" -#: src/android/interoperability/with-c/rust.md:50 -msgid "_interoperability/rust/analyze/main.c_" -msgstr "_interoperability/rust/analyze/main.c_" +#: src/testing/googletest.md:36 +msgid "" +"GoogleTest is not part of the Rust Playground, so you need to run this " +"example in a local environment. Use `cargo add googletest` to quickly add it " +"to an existing Cargo project." +msgstr "" -#: src/android/interoperability/with-c/rust.md:52 +#: src/testing/googletest.md:40 msgid "" -"```c\n" -"#include \"analyze.h\"\n" -"\n" -"int main() {\n" -" analyze_numbers(10, 20);\n" -" analyze_numbers(123, 123);\n" -" return 0;\n" -"}\n" -"```" +"The `use googletest::prelude::*;` line imports a number of [commonly used " +"macros and types](https://docs.rs/googletest/latest/googletest/prelude/index." +"html)." msgstr "" -"```c\n" -"#include \"analyze.h\"\n" -"\n" -"int main() {\n" -" analyze_numbers(10, 20);\n" -" analyze_numbers(123, 123);\n" -" return 0;\n" -"}\n" -"```" -#: src/android/interoperability/with-c/rust.md:62 -msgid "_interoperability/rust/analyze/Android.bp_" -msgstr "_interoperability/rust/analyze/Android.bp_" +#: src/testing/googletest.md:43 +msgid "This just scratches the surface, there are many builtin matchers." +msgstr "" -#: src/android/interoperability/with-c/rust.md:64 +#: src/testing/googletest.md:45 msgid "" -"```javascript\n" -"cc_binary {\n" -" name: \"analyze_numbers\",\n" -" srcs: [\"main.c\"],\n" -" static_libs: [\"libanalyze_ffi\"],\n" -"}\n" -"```" +"A particularly nice feature is that mismatches in multi-line strings strings " +"are shown as a diff:" msgstr "" -"```javascript\n" -"cc_binary {\n" -" name: \"analyze_numbers\",\n" -" srcs: [\"main.c\"],\n" -" static_libs: [\"libanalyze_ffi\"],\n" -"}\n" -"```" -#: src/android/interoperability/with-c/rust.md:75 +#: src/testing/googletest.md:51 msgid "" -"```shell\n" -"m analyze_numbers\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/analyze_numbers\n" -"```" +"\"Memory safety found,\\n\\\n" +" Rust's strong typing guides the way,\\n\\\n" +" Secure code you'll write.\"" msgstr "" -"```shell\n" -"m analyze_numbers\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/analyze_numbers\n" -"```" -#: src/android/interoperability/with-c/rust.md:83 +#: src/testing/googletest.md:56 msgid "" -"`#[no_mangle]` disables Rust's usual name mangling, so the exported symbol " -"will just be the name of the function. You can also use `#[export_name = " -"\"some_name\"]` to specify whatever name you want." +"\"Memory safety found,\\n\\\n" +" Rust's silly humor guides the way,\\n\\\n" +" Secure code you'll write.\"" msgstr "" -"`#[no_mangle]` 禁用了 Rust 通常的名称重整，因此导出的符号将仅为函数的名称。你" -"还可以使用 `#[export_name = \"some_name\"]` 来指定任意你想要的名称。" -#: src/android/interoperability/cpp.md:3 +#: src/testing/googletest.md:63 +msgid "shows a color-coded diff (colors not shown here):" +msgstr "" + +#: src/testing/googletest.md:80 msgid "" -"The [CXX crate](https://cxx.rs/) makes it possible to do safe " -"interoperability between Rust and C++." +"The crate is a Rust port of [GoogleTest for C++](https://google.github.io/" +"googletest/)." msgstr "" -"[CXX crate](https://cxx.rs/) 使得在 Rust 和 C++ 之间进行安全的互操作成为可" -"能。" -#: src/android/interoperability/cpp.md:6 -msgid "The overall approach looks like this:" -msgstr "整体的方法如下：" +#: src/testing/googletest.md:85 +msgid "GoogleTest is available for use in AOSP." +msgstr "" -#: src/android/interoperability/cpp.md:10 +#: src/testing/mocking.md:3 msgid "" -"See the [CXX tutorial](https://cxx.rs/tutorial.html) for an full example of " -"using this." +"For mocking, [Mockall](https://docs.rs/mockall/) is a widely used library. " +"You need to refactor your code to use traits, which you can then quickly " +"mock:" msgstr "" -"请参阅 [CXX tutorial](https://cxx.rs/tutorial.html) ，了解有关使用的完整示" -"例。" -#: src/android/interoperability/cpp.md:14 +#: src/testing/mocking.md:26 msgid "" -"At this point, the instructor should switch to the [CXX tutorial](https://" -"cxx.rs/tutorial.html)." -msgstr "此时，讲师应该该切换到 [CXX tutorial](https://cxx.rs/tutorial.html)。" - -#: src/android/interoperability/cpp.md:16 -msgid "Walk the students through the tutorial step by step." -msgstr "逐步引导学生按照教程一步步操作。" +"The advice here is for Android (AOSP) where Mockall is the recommended " +"mocking library. There are other [mocking libraries available on crates.io]" +"(https://crates.io/keywords/mock), in particular in the area of mocking HTTP " +"services. The other mocking libraries work in a similar fashion as Mockall, " +"meaning that they make it easy to get a mock implementation of a given trait." +msgstr "" -#: src/android/interoperability/cpp.md:18 +#: src/testing/mocking.md:33 msgid "" -"Highlight how CXX presents a clean interface without unsafe code in _both " -"languages_." -msgstr "突出展示 CXX 在 _两种语言_ 中都提供了一个没有不安全代码的干净接口。" +"Note that mocking is somewhat _controversial_: mocks allow you to completely " +"isolate a test from its dependencies. The immediate result is faster and " +"more stable test execution. On the other hand, the mocks can be configured " +"wrongly and return output different from what the real dependencies would do." +msgstr "" -#: src/android/interoperability/cpp.md:20 +#: src/testing/mocking.md:38 msgid "" -"Show the correspondence between [Rust and C++ types](https://cxx.rs/bindings." -"html):" -msgstr "展示 [Rust 和 C++类型](https://cxx.rs/bindings.html) 之间的对应关系：" +"If at all possible, it is recommended that you use the real dependencies. As " +"an example, many databases allow you to configure an in-memory backend. This " +"means that you get the correct behavior in your tests, plus they are fast " +"and will automatically clean up after themselves." +msgstr "" -#: src/android/interoperability/cpp.md:22 +#: src/testing/mocking.md:43 msgid "" -"Explain how a Rust `String` cannot map to a C++ `std::string` (the latter " -"does not uphold the UTF-8 invariant). Show that despite being different " -"types, `rust::String` in C++ can be easily constructed from a C++ `std::" -"string`, making it very ergonomic to use." +"Similarly, many web frameworks allow you to start an in-process server which " +"binds to a random port on `localhost`. Always prefer this over mocking away " +"the framework since it helps you test your code in the real environment." msgstr "" -"解释 Rust 的 `String` 无法直接映射到 C++ 的 `std::string `（后者不符合UTF-8不" -"变性）。展示尽管类型不同，但在 C++ 中，可以很容易地从 C++ 的 `std::string` 构" -"造 `rust::String` ，使得使用起来非常方便。" -#: src/android/interoperability/cpp.md:28 +#: src/testing/mocking.md:47 msgid "" -"Explain that a Rust function returning `Result` becomes a function " -"which throws a `E` exception in C++ (and vice versa)." +"Mockall is not part of the Rust Playground, so you need to run this example " +"in a local environment. Use `cargo add mockall` to quickly add Mockall to an " +"existing Cargo project." msgstr "" -"解释 Rust 中返回 `Result ` 的函数在 C++ 中会变成抛出 `E` 异常的函数（反" -"之亦然）。" -#: src/android/interoperability/java.md:1 -msgid "Interoperability with Java" -msgstr "与 Java 的互操作性" +#: src/testing/mocking.md:51 +msgid "" +"Mockall has a lot more functionality. In particular, you can set up " +"expectations which depend on the arguments passed. Here we use this to mock " +"a cat which becomes hungry 3 hours after the last time it was fed:" +msgstr "" -#: src/android/interoperability/java.md:3 +#: src/testing/mocking.md:69 msgid "" -"Java can load shared objects via [Java Native Interface (JNI)](https://en." -"wikipedia.org/wiki/Java_Native_Interface). The [`jni` crate](https://docs.rs/" -"jni/) allows you to create a compatible library." +"You can use `.times(n)` to limit the number of times a mock method can be " +"called to `n` --- the mock will automatically panic when dropped if this " +"isn't satisfied." msgstr "" -"Java可以通过 [ Java 本地接口 (JNI)](https://en.wikipedia.org/wiki/" -"Java_Native_Interface) 加载共享对象。[`jni` crate](https://docs.rs/jni/) 允许" -"您创建一个兼容的库。" -#: src/android/interoperability/java.md:7 -msgid "First, we create a Rust function to export to Java:" -msgstr "首先，我们创建一个可以导出到 Java 的 Rust 函数：" +#: src/testing/lints.md:3 +msgid "" +"The Rust compiler produces fantastic error messages, as well as helpful " +"built-in lints. [Clippy](https://doc.rust-lang.org/clippy/) provides even " +"more lints, organized into groups that can be enabled per-project." +msgstr "" -#: src/android/interoperability/java.md:9 -msgid "_interoperability/java/src/lib.rs_:" -msgstr "_interoperability/java/src/lib.rs_:" +#: src/testing/lints.md:14 +msgid "\"X probably fits in a u16, right? {}\"" +msgstr "" -#: src/android/interoperability/java.md:11 +#: src/testing/lints.md:20 msgid "" -"```rust,compile_fail\n" -"//! Rust <-> Java FFI demo.\n" -"\n" -"use jni::objects::{JClass, JString};\n" -"use jni::sys::jstring;\n" -"use jni::JNIEnv;\n" -"\n" -"/// HelloWorld::hello method implementation.\n" -"#[no_mangle]\n" -"pub extern \"system\" fn Java_HelloWorld_hello(\n" -" env: JNIEnv,\n" -" _class: JClass,\n" -" name: JString,\n" -") -> jstring {\n" -" let input: String = env.get_string(name).unwrap().into();\n" -" let greeting = format!(\"Hello, {input}!\");\n" -" let output = env.new_string(greeting).unwrap();\n" -" output.into_inner()\n" -"}\n" -"```" +"Run the code sample and examine the error message. There are also lints " +"visible here, but those will not be shown once the code compiles. Switch to " +"the Playground site to show those lints." msgstr "" -"```rust,compile_fail\n" -"//! Rust <-> Java FFI demo.\n" -"\n" -"use jni::objects::{JClass, JString};\n" -"use jni::sys::jstring;\n" -"use jni::JNIEnv;\n" -"\n" -"/// HelloWorld::hello method implementation.\n" -"#[no_mangle]\n" -"pub extern \"system\" fn Java_HelloWorld_hello(\n" -" env: JNIEnv,\n" -" _class: JClass,\n" -" name: JString,\n" -") -> jstring {\n" -" let input: String = env.get_string(name).unwrap().into();\n" -" let greeting = format!(\"Hello, {input}!\");\n" -" let output = env.new_string(greeting).unwrap();\n" -" output.into_inner()\n" -"}\n" -"```" - -#: src/android/interoperability/java.md:32 -#: src/android/interoperability/java.md:62 -msgid "_interoperability/java/Android.bp_:" -msgstr "_interoperability/java/Android.bp_:" -#: src/android/interoperability/java.md:34 +#: src/testing/lints.md:24 msgid "" -"```javascript\n" -"rust_ffi_shared {\n" -" name: \"libhello_jni\",\n" -" crate_name: \"hello_jni\",\n" -" srcs: [\"src/lib.rs\"],\n" -" rustlibs: [\"libjni\"],\n" -"}\n" -"```" +"After resolving the lints, run `clippy` on the playground site to show " +"clippy warnings. Clippy has extensive documentation of its lints, and adds " +"new lints (including default-deny lints) all the time." msgstr "" -"```javascript\n" -"rust_ffi_shared {\n" -" name: \"libhello_jni\",\n" -" crate_name: \"hello_jni\",\n" -" srcs: [\"src/lib.rs\"],\n" -" rustlibs: [\"libjni\"],\n" -"}\n" -"```" -#: src/android/interoperability/java.md:43 -msgid "Finally, we can call this function from Java:" -msgstr "最后，我们可以从 Java 中调用这个函数：" +#: src/testing/lints.md:28 +msgid "" +"Note that errors or warnings with `help: ...` can be fixed with `cargo fix` " +"or via your editor." +msgstr "" -#: src/android/interoperability/java.md:45 -msgid "_interoperability/java/HelloWorld.java_:" -msgstr "_interoperability/java/HelloWorld.java_:" +#: src/testing/exercise.md:3 +msgid "Luhn Algorithm" +msgstr "卢恩算法" -#: src/android/interoperability/java.md:47 +#: src/testing/exercise.md:5 msgid "" -"```java\n" -"class HelloWorld {\n" -" private static native String hello(String name);\n" -"\n" -" static {\n" -" System.loadLibrary(\"hello_jni\");\n" -" }\n" -"\n" -" public static void main(String[] args) {\n" -" String output = HelloWorld.hello(\"Alice\");\n" -" System.out.println(output);\n" -" }\n" -"}\n" -"```" +"The [Luhn algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is used " +"to validate credit card numbers. The algorithm takes a string as input and " +"does the following to validate the credit card number:" msgstr "" -"```java\n" -"class HelloWorld {\n" -" private static native String hello(String name);\n" -"\n" -" static {\n" -" System.loadLibrary(\"hello_jni\");\n" -" }\n" -"\n" -" public static void main(String[] args) {\n" -" String output = HelloWorld.hello(\"Alice\");\n" -" System.out.println(output);\n" -" }\n" -"}\n" -"```" +"[卢恩算法](https://zh.wikipedia.org/wiki/卢恩算法)用于验证信用卡号。该算法将" +"字符串作为输入内容，并执行以下操作来验证信用卡号：" + +#: src/testing/exercise.md:9 +msgid "Ignore all spaces. Reject number with less than two digits." +msgstr "忽略所有空格。拒绝少于两位的号码。" -#: src/android/interoperability/java.md:64 +#: src/testing/exercise.md:11 msgid "" -"```javascript\n" -"java_binary {\n" -" name: \"helloworld_jni\",\n" -" srcs: [\"HelloWorld.java\"],\n" -" main_class: \"HelloWorld\",\n" -" required: [\"libhello_jni\"],\n" -"}\n" -"```" +"Moving from **right to left**, double every second digit: for the number " +"`1234`, we double `3` and `1`. For the number `98765`, we double `6` and `8`." msgstr "" -"```javascript\n" -"java_binary {\n" -" name: \"helloworld_jni\",\n" -" srcs: [\"HelloWorld.java\"],\n" -" main_class: \"HelloWorld\",\n" -" required: [\"libhello_jni\"],\n" -"}\n" -"```" - -#: src/android/interoperability/java.md:73 -msgid "Finally, you can build, sync, and run the binary:" -msgstr "最后，您可以构建、同步和运行二进制文件：" +"从**右到左**，将偶数位的数字乘二。对于数字“1234”，我们将“3”和“1”乘二；对于数" +"字“98765”，将“6”和“8”乘二。" -#: src/exercises/android/morning.md:3 +#: src/testing/exercise.md:14 msgid "" -"This is a group exercise: We will look at one of the projects you work with " -"and try to integrate some Rust into it. Some suggestions:" +"After doubling a digit, sum the digits if the result is greater than 9. So " +"doubling `7` becomes `14` which becomes `1 + 4 = 5`." msgstr "" -"这是一个小组练习：我们将查看你们正在处理的项目之一，并尝试将一些 Rust 代码集" -"成进去。以下是一些建议：" +"将一个数字乘二后，如果结果大于 9，则将每位数字相加。因此，将“7”乘二得“14”，然" +"后“1 + 4 = 5”。" -#: src/exercises/android/morning.md:6 -msgid "Call your AIDL service with a client written in Rust." -msgstr "使用 Rust 编写的客户端调用你的 AIDL 服务。" +#: src/testing/exercise.md:17 +msgid "Sum all the undoubled and doubled digits." +msgstr "将所有未乘二和已乘二的数字相加。" -#: src/exercises/android/morning.md:8 -msgid "Move a function from your project to Rust and call it." -msgstr "将你项目中的某个函数迁移到 Rust 中并调用它。" +#: src/testing/exercise.md:19 +msgid "The credit card number is valid if the sum ends with `0`." +msgstr "如果总和以“0”结尾，则信用卡号有效。" -#: src/exercises/android/morning.md:12 +#: src/testing/exercise.md:21 msgid "" -"No solution is provided here since this is open-ended: it relies on someone " -"in the class having a piece of code which you can turn in to Rust on the fly." -msgstr "" -"此处没有提供解决方案，因为这是开放式的：它依赖于班级中是否有人有一段您可以即" -"时转换成 Rust 的代码。" - -#: src/bare-metal.md:1 -msgid "Welcome to Bare Metal Rust" +"The provided code provides a buggy implementation of the luhn algorithm, " +"along with two basic unit tests that confirm that most the algorithm is " +"implemented correctly." msgstr "" -#: src/bare-metal.md:3 +#: src/testing/exercise.md:25 +#, fuzzy msgid "" -"This is a standalone one-day course about bare-metal Rust, aimed at people " -"who are familiar with the basics of Rust (perhaps from completing the " -"Comprehensive Rust course), and ideally also have some experience with bare-" -"metal programming in some other language such as C." +"Copy the code below to and write additional " +"tests to uncover bugs in the provided implementation, fixing any bugs you " +"find." msgstr "" +"将以下代码复制到 ，并填入缺少的函数和方法：" -#: src/bare-metal.md:7 -msgid "" -"Today we will talk about 'bare-metal' Rust: running Rust code without an OS " -"underneath us. This will be divided into several parts:" +#: src/testing/exercise.md:57 src/testing/solution.md:69 +msgid "\"4263 9826 4026 9299\"" msgstr "" -#: src/bare-metal.md:10 -msgid "What is `no_std` Rust?" +#: src/testing/exercise.md:58 src/testing/solution.md:70 +msgid "\"4539 3195 0343 6467\"" msgstr "" -#: src/bare-metal.md:11 -msgid "Writing firmware for microcontrollers." +#: src/testing/exercise.md:59 src/testing/solution.md:71 +msgid "\"7992 7398 713\"" msgstr "" -#: src/bare-metal.md:12 -msgid "Writing bootloader / kernel code for application processors." +#: src/testing/exercise.md:64 src/testing/solution.md:76 +msgid "\"4223 9826 4026 9299\"" msgstr "" -#: src/bare-metal.md:13 -msgid "Some useful crates for bare-metal Rust development." +#: src/testing/exercise.md:65 src/testing/solution.md:77 +msgid "\"4539 3195 0343 6476\"" msgstr "" -#: src/bare-metal.md:15 -msgid "" -"For the microcontroller part of the course we will use the [BBC micro:bit]" -"(https://microbit.org/) v2 as an example. It's a [development board](https://" -"tech.microbit.org/hardware/) based on the Nordic nRF51822 microcontroller " -"with some LEDs and buttons, an I2C-connected accelerometer and compass, and " -"an on-board SWD debugger." +#: src/testing/exercise.md:66 src/testing/solution.md:78 +msgid "\"8273 1232 7352 0569\"" msgstr "" -#: src/bare-metal.md:20 -msgid "" -"To get started, install some tools we'll need later. On gLinux or Debian:" +#: src/testing/solution.md:4 +msgid "// This is the buggy version that appears in the problem.\n" msgstr "" -#: src/bare-metal.md:30 -msgid "" -"And give users in the `plugdev` group access to the micro:bit programmer:" +#: src/testing/solution.md:27 +msgid "// This is the solution and passes all of the tests below.\n" msgstr "" -#: src/bare-metal.md:32 -msgid "" -"```bash\n" -"echo 'SUBSYSTEM==\"usb\", ATTR{idVendor}==\"0d28\", MODE=\"0664\", " -"GROUP=\"plugdev\"' |\\\n" -" sudo tee /etc/udev/rules.d/50-microbit.rules\n" -"sudo udevadm control --reload-rules\n" -"```" +#: src/testing/solution.md:56 +msgid "\"1234 5678 1234 5670\"" msgstr "" -#: src/bare-metal.md:38 -msgid "On MacOS:" +#: src/testing/solution.md:58 +msgid "\"Is {cc_number} a valid credit card number? {}\"" msgstr "" -#: src/bare-metal/no_std.md:1 -msgid "`no_std`" +#: src/testing/solution.md:59 +msgid "\"yes\"" msgstr "" -#: src/bare-metal/no_std.md:7 -msgid "`core`" +#: src/testing/solution.md:59 +msgid "\"no\"" msgstr "" -#: src/bare-metal/no_std.md:12 src/bare-metal/alloc.md:1 -msgid "`alloc`" +#: src/testing/solution.md:84 +msgid "\"foo 0 0\"" msgstr "" -#: src/bare-metal/no_std.md:17 -msgid "`std`" +#: src/testing/solution.md:90 +msgid "\" \"" msgstr "" -#: src/bare-metal/no_std.md:24 -msgid "Slices, `&str`, `CStr`" +#: src/testing/solution.md:91 +msgid "\" \"" msgstr "" -#: src/bare-metal/no_std.md:25 -msgid "`NonZeroU8`..." +#: src/testing/solution.md:92 +msgid "\" \"" msgstr "" -#: src/bare-metal/no_std.md:26 -msgid "`Option`, `Result`" +#: src/testing/solution.md:97 +msgid "\"0\"" msgstr "" -#: src/bare-metal/no_std.md:27 -msgid "`Display`, `Debug`, `write!`..." +#: src/testing/solution.md:102 +msgid "\" 0 0 \"" msgstr "" -#: src/bare-metal/no_std.md:29 -msgid "`panic!`, `assert_eq!`..." +#: src/error-handling/panics.md:3 +msgid "Rust handles fatal errors with a \"panic\"." msgstr "" -#: src/bare-metal/no_std.md:30 -msgid "`NonNull` and all the usual pointer-related functions" -msgstr "" +#: src/error-handling/panics.md:5 +msgid "Rust will trigger a panic if a fatal error happens at runtime:" +msgstr "如果运行时发生严重错误，Rust 会触发 panic：" -#: src/bare-metal/no_std.md:31 -msgid "`Future` and `async`/`await`" +#: src/error-handling/panics.md:10 +msgid "\"v[100]: {}\"" msgstr "" -#: src/bare-metal/no_std.md:32 -msgid "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." +#: src/error-handling/panics.md:14 +msgid "Panics are for unrecoverable and unexpected errors." +msgstr "Panic 用于指示不可恢复的意外错误。" + +#: src/error-handling/panics.md:15 +msgid "Panics are symptoms of bugs in the program." +msgstr "Panic反映了程序中的 bug 问题。" + +#: src/error-handling/panics.md:16 +msgid "Runtime failures like failed bounds checks can panic" msgstr "" -#: src/bare-metal/no_std.md:33 -msgid "`Duration`" +#: src/error-handling/panics.md:17 +msgid "Assertions (such as `assert!`) panic on failure" msgstr "" -#: src/bare-metal/no_std.md:38 -msgid "`Box`, `Cow`, `Arc`, `Rc`" +#: src/error-handling/panics.md:18 +msgid "Purpose-specific panics can use the `panic!` macro." msgstr "" -#: src/bare-metal/no_std.md:39 -msgid "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" +#: src/error-handling/panics.md:19 +msgid "" +"A panic will \"unwind\" the stack, dropping values just as if the functions " +"had returned." msgstr "" -#: src/bare-metal/no_std.md:40 -msgid "`String`, `CString`, `format!`" +#: src/error-handling/panics.md:21 +msgid "" +"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." +msgstr "如果崩溃不可接受，请使用不会触发 panic 的 API（例如 `Vec::get`）。" + +#: src/error-handling/panics.md:25 +msgid "" +"By default, a panic will cause the stack to unwind. The unwinding can be " +"caught:" +msgstr "默认情况下，panic 会导致堆栈展开。您可以捕获展开信息：" + +#: src/error-handling/panics.md:31 +msgid "\"No problem here!\"" msgstr "" -#: src/bare-metal/no_std.md:45 -msgid "`Error`" +#: src/error-handling/panics.md:32 src/error-handling/panics.md:37 +msgid "\"{result:?}\"" msgstr "" -#: src/bare-metal/no_std.md:47 -msgid "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" +#: src/error-handling/panics.md:35 +msgid "\"oh no!\"" msgstr "" -#: src/bare-metal/no_std.md:48 -msgid "`File` and the rest of `fs`" +#: src/error-handling/panics.md:41 +msgid "" +"Catching is unusual; do not attempt to implement exceptions with " +"`catch_unwind`!" msgstr "" -#: src/bare-metal/no_std.md:49 -msgid "`println!`, `Read`, `Write`, `Stdin`, `Stdout` and the rest of `io`" +#: src/error-handling/panics.md:43 +msgid "" +"This can be useful in servers which should keep running even if a single " +"request crashes." msgstr "" +"如果服务器需要持续运行（即使是在请求发生崩溃的情况下）， 此方法十分有用。" -#: src/bare-metal/no_std.md:50 -msgid "`Path`, `OsString`" +#: src/error-handling/panics.md:45 +msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." +msgstr "如果您在 `Cargo.toml` 中设置了 `panic = 'abort'`，此方法不会生效。" + +#: src/error-handling/try.md:3 +msgid "" +"Runtime errors like connection-refused or file-not-found are handled with " +"the `Result` type, but matching this type on every call can be cumbersome. " +"The try-operator `?` is used to return errors to the caller. It lets you " +"turn the common" msgstr "" -#: src/bare-metal/no_std.md:51 -msgid "`net`" +#: src/error-handling/try.md:15 +msgid "into the much simpler" +msgstr "转换成更简单的命令" + +#: src/error-handling/try.md:21 +#, fuzzy +msgid "We can use this to simplify our error handling code:" +msgstr "我们可以用它来简化错误处理代码：" + +#: src/error-handling/try.md:42 +msgid "//fs::write(\"config.dat\", \"alice\").unwrap();\n" msgstr "" -#: src/bare-metal/no_std.md:52 -msgid "`Command`, `Child`, `ExitCode`" +#: src/error-handling/try.md:43 src/error-handling/try-conversions.md:65 +#: src/error-handling/thiserror-and-anyhow.md:33 +msgid "\"config.dat\"" msgstr "" -#: src/bare-metal/no_std.md:53 -msgid "`spawn`, `sleep` and the rest of `thread`" +#: src/error-handling/try.md:44 src/error-handling/try-conversions.md:66 +msgid "\"username or error: {username:?}\"" msgstr "" -#: src/bare-metal/no_std.md:54 -msgid "`SystemTime`, `Instant`" +#: src/error-handling/try.md:50 +msgid "Simplify the `read_username` function to use `?`." msgstr "" -#: src/bare-metal/no_std.md:62 -msgid "`HashMap` depends on RNG." +#: src/error-handling/try.md:54 +msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." +msgstr "`username` 变量可以是 `Ok(string)` 或 `Err(error)`。" + +#: src/error-handling/try.md:55 +msgid "" +"Use the `fs::write` call to test out the different scenarios: no file, empty " +"file, file with username." msgstr "" +"可以使用 `fs::write` 调用来测试不同的场景：没有文件、空文件、包含用户名的文" +"件。" -#: src/bare-metal/no_std.md:63 -msgid "`std` re-exports the contents of both `core` and `alloc`." +#: src/error-handling/try.md:57 +msgid "" +"Note that `main` can return a `Result<(), E>` as long as it implements `std::" +"process:Termination`. In practice, this means that `E` implements `Debug`. " +"The executable will print the `Err` variant and return a nonzero exit status " +"on error." msgstr "" -#: src/bare-metal/minimal.md:1 -msgid "A minimal `no_std` program" +#: src/error-handling/try-conversions.md:3 +msgid "" +"The effective expansion of `?` is a little more complicated than previously " +"indicated:" +msgstr "`?` 的有效展开比前面介绍的内容略微复杂一些：" + +#: src/error-handling/try-conversions.md:10 +msgid "works the same as" +msgstr "效果等同于" + +#: src/error-handling/try-conversions.md:19 +#, fuzzy +msgid "" +"The `From::from` call here means we attempt to convert the error type to the " +"type returned by the function. This makes it easy to encapsulate errors into " +"higher-level errors." msgstr "" +"此处的 `From::from` 调用表示，我们尝试将错误类型转换为 函数返回的类型：" -#: src/bare-metal/minimal.md:17 -msgid "This will compile to an empty binary." +#: src/error-handling/try-conversions.md:42 +msgid "\"IO error: {e}\"" msgstr "" -#: src/bare-metal/minimal.md:18 -msgid "`std` provides a panic handler; without it we must provide our own." +#: src/error-handling/try-conversions.md:43 +msgid "\"Found no username in {path}\"" msgstr "" -#: src/bare-metal/minimal.md:19 -msgid "It can also be provided by another crate, such as `panic-halt`." +#: src/error-handling/try-conversions.md:64 +#: src/error-handling/thiserror-and-anyhow.md:32 +msgid "//fs::write(\"config.dat\", \"\").unwrap();\n" msgstr "" -#: src/bare-metal/minimal.md:20 +#: src/error-handling/try-conversions.md:72 msgid "" -"Depending on the target, you may need to compile with `panic = \"abort\"` to " -"avoid an error about `eh_personality`." +"The `?` operator must return a value compatible with the return type of the " +"function. For `Result`, it means that the error types have to be compatible. " +"A function that returns `Result` can only use `?` on a value " +"of type `Result` if `ErrorOuter` and `ErrorInner` are the " +"same type or if `ErrorOuter` implements `From`." msgstr "" -#: src/bare-metal/minimal.md:22 +#: src/error-handling/try-conversions.md:78 msgid "" -"Note that there is no `main` or any other entry point; it's up to you to " -"define your own entry point. This will typically involve a linker script and " -"some assembly code to set things up ready for Rust code to run." +"A common alternative to a `From` implementation is `Result::map_err`, " +"especially when the conversion only happens in one place." msgstr "" -#: src/bare-metal/alloc.md:3 +#: src/error-handling/try-conversions.md:81 msgid "" -"To use `alloc` you must implement a [global (heap) allocator](https://doc." -"rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html)." +"There is no compatibility requirement for `Option`. A function returning " +"`Option` can use the `?` operator on `Option` for arbitrary `T` and " +"`U` types." msgstr "" -#: src/bare-metal/alloc.md:6 +#: src/error-handling/try-conversions.md:85 msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate alloc;\n" -"extern crate panic_halt as _;\n" -"\n" -"use alloc::string::ToString;\n" -"use alloc::vec::Vec;\n" -"use buddy_system_allocator::LockedHeap;\n" -"\n" -"#[global_allocator]\n" -"static HEAP_ALLOCATOR: LockedHeap<32> = LockedHeap::<32>::new();\n" -"\n" -"static mut HEAP: [u8; 65536] = [0; 65536];\n" -"\n" -"pub fn entry() {\n" -" // Safe because `HEAP` is only used here and `entry` is only called " -"once.\n" -" unsafe {\n" -" // Give the allocator some memory to allocate.\n" -" HEAP_ALLOCATOR\n" -" .lock()\n" -" .init(HEAP.as_mut_ptr() as usize, HEAP.len());\n" -" }\n" -"\n" -" // Now we can do things that require heap allocation.\n" -" let mut v = Vec::new();\n" -" v.push(\"A string\".to_string());\n" -"}\n" -"```" +"A function that returns `Result` cannot use `?` on `Option` and vice versa. " +"However, `Option::ok_or` converts `Option` to `Result` whereas `Result::ok` " +"turns `Result` into `Option`." msgstr "" -#: src/bare-metal/alloc.md:39 +#: src/error-handling/error.md:1 +msgid "Dynamic Error Types" +msgstr "动态错误类型" + +#: src/error-handling/error.md:3 +#, fuzzy msgid "" -"`buddy_system_allocator` is a third-party crate implementing a basic buddy " -"system allocator. Other crates are available, or you can write your own or " -"hook into your existing allocator." +"Sometimes we want to allow any type of error to be returned without writing " +"our own enum covering all the different possibilities. The `std::error::" +"Error` trait makes it easy to create a trait object that can contain any " +"error." msgstr "" +"有时，我们需要允许返回任意类型的错误，但又不想自己手动编写枚举来涵盖所有不同" +"的可能性。 `std::error::Error` 可以让我们轻松做到这一点。" -#: src/bare-metal/alloc.md:41 -msgid "" -"The const parameter of `LockedHeap` is the max order of the allocator; i.e. " -"in this case it can allocate regions of up to 2\\*\\*32 bytes." +#: src/error-handling/error.md:20 src/error-handling/error.md:21 +msgid "\"count.dat\"" msgstr "" -#: src/bare-metal/alloc.md:43 -msgid "" -"If any crate in your dependency tree depends on `alloc` then you must have " -"exactly one global allocator defined in your binary. Usually this is done in " -"the top-level binary crate." +#: src/error-handling/error.md:20 +msgid "\"1i3\"" msgstr "" -#: src/bare-metal/alloc.md:45 -msgid "" -"`extern crate panic_halt as _` is necessary to ensure that the `panic_halt` " -"crate is linked in so we get its panic handler." +#: src/error-handling/error.md:22 +msgid "\"Count: {count}\"" msgstr "" -#: src/bare-metal/alloc.md:47 -msgid "This example will build but not run, as it doesn't have an entry point." +#: src/error-handling/error.md:23 +msgid "\"Error: {err}\"" msgstr "" -#: src/bare-metal/microcontrollers.md:3 +#: src/error-handling/error.md:30 msgid "" -"The `cortex_m_rt` crate provides (among other things) a reset handler for " -"Cortex M microcontrollers." +"The `read_count` function can return `std::io::Error` (from file operations) " +"or `std::num::ParseIntError` (from `String::parse`)." msgstr "" -#: src/bare-metal/microcontrollers.md:21 +#: src/error-handling/error.md:33 +#, fuzzy msgid "" -"Next we'll look at how to access peripherals, with increasing levels of " -"abstraction." +"Boxing errors saves on code, but gives up the ability to cleanly handle " +"different error cases differently in the program. As such it's generally not " +"a good idea to use `Box` in the public API of a library, but it " +"can be a good option in a program where you just want to display the error " +"message somewhere." msgstr "" +"虽然这可以省却编写代码的麻烦，但也会导致我们无法在程序中以不同的方式正常处理" +"不同的 错误情况。因此，在库的公共 API 中使用 `Box` 通常不是一个好" +"主意。 但是对于您只需要在某处显示错误消息的程序来说，这不失为一个 很好的选" +"择。" -#: src/bare-metal/microcontrollers.md:25 +#: src/error-handling/error.md:39 msgid "" -"The `cortex_m_rt::entry` macro requires that the function have type `fn() -" -"> !`, because returning to the reset handler doesn't make sense." +"Make sure to implement the `std::error::Error` trait when defining a custom " +"error type so it can be boxed. But if you need to support the `no_std` " +"attribute, keep in mind that the `std::error::Error` trait is currently " +"compatible with `no_std` in [nightly](https://github.com/rust-lang/rust/" +"issues/103765) only." msgstr "" -#: src/bare-metal/microcontrollers.md:27 -msgid "Run the example with `cargo embed --bin minimal`" +#: src/error-handling/thiserror-and-anyhow.md:3 +msgid "" +"The [`thiserror`](https://docs.rs/thiserror/) and [`anyhow`](https://docs.rs/" +"anyhow/) crates are widely used to simplify error handling. `thiserror` " +"helps create custom error types that implement `From`. `anyhow` helps " +"with error handling in functions, including adding contextual information to " +"your errors." msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:3 -msgid "" -"Most microcontrollers access peripherals via memory-mapped IO. Let's try " -"turning on an LED on our micro:bit:" -msgstr "" - -#: src/bare-metal/microcontrollers/mmio.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"mod interrupts;\n" -"\n" -"use core::mem::size_of;\n" -"use cortex_m_rt::entry;\n" -"\n" -"/// GPIO port 0 peripheral address\n" -"const GPIO_P0: usize = 0x5000_0000;\n" -"\n" -"// GPIO peripheral offsets\n" -"const PIN_CNF: usize = 0x700;\n" -"const OUTSET: usize = 0x508;\n" -"const OUTCLR: usize = 0x50c;\n" -"\n" -"// PIN_CNF fields\n" -"const DIR_OUTPUT: u32 = 0x1;\n" -"const INPUT_DISCONNECT: u32 = 0x1 << 1;\n" -"const PULL_DISABLED: u32 = 0x0 << 2;\n" -"const DRIVE_S0S1: u32 = 0x0 << 8;\n" -"const SENSE_DISABLED: u32 = 0x0 << 16;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" let pin_cnf_21 = (GPIO_P0 + PIN_CNF + 21 * size_of::()) as *mut " -"u32;\n" -" let pin_cnf_28 = (GPIO_P0 + PIN_CNF + 28 * size_of::()) as *mut " -"u32;\n" -" // Safe because the pointers are to valid peripheral control registers, " -"and\n" -" // no aliases exist.\n" -" unsafe {\n" -" pin_cnf_21.write_volatile(\n" -" DIR_OUTPUT | INPUT_DISCONNECT | PULL_DISABLED | DRIVE_S0S1 | " -"SENSE_DISABLED,\n" -" );\n" -" pin_cnf_28.write_volatile(\n" -" DIR_OUTPUT | INPUT_DISCONNECT | PULL_DISABLED | DRIVE_S0S1 | " -"SENSE_DISABLED,\n" -" );\n" -" }\n" -"\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" let gpio0_outset = (GPIO_P0 + OUTSET) as *mut u32;\n" -" let gpio0_outclr = (GPIO_P0 + OUTCLR) as *mut u32;\n" -" // Safe because the pointers are to valid peripheral control registers, " -"and\n" -" // no aliases exist.\n" -" unsafe {\n" -" gpio0_outclr.write_volatile(1 << 28);\n" -" gpio0_outset.write_volatile(1 << 21);\n" -" }\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling/thiserror-and-anyhow.md:16 +msgid "\"Found no username in {0}\"" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:64 -msgid "" -"GPIO 0 pin 21 is connected to the first column of the LED matrix, and pin 28 " -"to the first row." +#: src/error-handling/thiserror-and-anyhow.md:22 +msgid "\"Failed to open {path}\"" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:66 -#: src/bare-metal/microcontrollers/pacs.md:59 -#: src/bare-metal/microcontrollers/hals.md:43 -#: src/bare-metal/microcontrollers/board-support.md:34 -msgid "Run the example with:" +#: src/error-handling/thiserror-and-anyhow.md:24 +msgid "\"Failed to read\"" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:1 -msgid "Peripheral Access Crates" +#: src/error-handling/thiserror-and-anyhow.md:34 +msgid "\"Username: {username}\"" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:3 -msgid "" -"[`svd2rust`](https://crates.io/crates/svd2rust) generates mostly-safe Rust " -"wrappers for memory-mapped peripherals from [CMSIS-SVD](https://www.keil.com/" -"pack/doc/CMSIS/SVD/html/index.html) files." +#: src/error-handling/thiserror-and-anyhow.md:35 +msgid "\"Error: {err:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use cortex_m_rt::entry;\n" -"use nrf52833_pac::Peripherals;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -" let gpio0 = p.P0;\n" -"\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" gpio0.pin_cnf[21].write(|w| {\n" -" w.dir().output();\n" -" w.input().disconnect();\n" -" w.pull().disabled();\n" -" w.drive().s0s1();\n" -" w.sense().disabled();\n" -" w\n" -" });\n" -" gpio0.pin_cnf[28].write(|w| {\n" -" w.dir().output();\n" -" w.input().disconnect();\n" -" w.pull().disabled();\n" -" w.drive().s0s1();\n" -" w.sense().disabled();\n" -" w\n" -" });\n" -"\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" gpio0.outclr.write(|w| w.pin28().clear());\n" -" gpio0.outset.write(|w| w.pin21().set());\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling/thiserror-and-anyhow.md:42 +msgid "`thiserror`" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:49 +#: src/error-handling/thiserror-and-anyhow.md:44 msgid "" -"SVD (System View Description) files are XML files typically provided by " -"silicon vendors which describe the memory map of the device." +"The `Error` derive macro is provided by `thiserror`, and has lots of useful " +"attributes to help define error types in a compact way." msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:51 -msgid "" -"They are organised by peripheral, register, field and value, with names, " -"descriptions, addresses and so on." +#: src/error-handling/thiserror-and-anyhow.md:46 +msgid "The `std::error::Error` trait is derived automatically." msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:53 -msgid "" -"SVD files are often buggy and incomplete, so there are various projects " -"which patch the mistakes, add missing details, and publish the generated " -"crates." +#: src/error-handling/thiserror-and-anyhow.md:47 +msgid "The message from `#[error]` is used to derive the `Display` trait." msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:55 -msgid "`cortex-m-rt` provides the vector table, among other things." +#: src/error-handling/thiserror-and-anyhow.md:49 +msgid "`anyhow`" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:56 +#: src/error-handling/thiserror-and-anyhow.md:51 +#, fuzzy msgid "" -"If you `cargo install cargo-binutils` then you can run `cargo objdump --bin " -"pac -- -d --no-show-raw-insn` to see the resulting binary." -msgstr "" +"`anyhow::Error` is essentially a wrapper around `Box`. As such " +"it's again generally not a good choice for the public API of a library, but " +"is widely used in applications." +msgstr "”是“Result\\”的类型别名。" -#: src/bare-metal/microcontrollers/hals.md:1 -msgid "HAL crates" -msgstr "" +#: src/error-handling/thiserror-and-anyhow.md:54 +#, fuzzy +msgid "`anyhow::Result` is a type alias for `Result`." +msgstr "“anyhow::Result" -#: src/bare-metal/microcontrollers/hals.md:3 +#: src/error-handling/thiserror-and-anyhow.md:55 +#, fuzzy msgid "" -"[HAL crates](https://github.com/rust-embedded/awesome-embedded-rust#hal-" -"implementation-crates) for many microcontrollers provide wrappers around " -"various peripherals. These generally implement traits from [`embedded-hal`]" -"(https://crates.io/crates/embedded-hal)." -msgstr "" +"Actual error type inside of it can be extracted for examination if necessary." +msgstr "“anyhow::Error”本质上是“Box" -#: src/bare-metal/microcontrollers/hals.md:7 +#: src/error-handling/thiserror-and-anyhow.md:56 +#, fuzzy msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use cortex_m_rt::entry;\n" -"use nrf52833_hal::gpio::{p0, Level};\n" -"use nrf52833_hal::pac::Peripherals;\n" -"use nrf52833_hal::prelude::*;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -"\n" -" // Create HAL wrapper for GPIO port 0.\n" -" let gpio0 = p0::Parts::new(p.P0);\n" -"\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" let mut col1 = gpio0.p0_28.into_push_pull_output(Level::High);\n" -" let mut row1 = gpio0.p0_21.into_push_pull_output(Level::Low);\n" +"Functionality provided by `anyhow::Result` may be familiar to Go " +"developers, as it provides similar usage patterns and ergonomics to `(T, " +"error)` from Go." +msgstr "" +"”的封装容器。因此，就像前面提到的那样，在库的公共 API 中 使用它通常不是一个好" +"主意。但是它广泛用于应用中。\n" "\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" col1.set_low().unwrap();\n" -" row1.set_high().unwrap();\n" +"如果需要，可以提取其内部的实际错误类型进行检查。\n" "\n" -" loop {}\n" -"}\n" -"```" -msgstr "" - -#: src/bare-metal/microcontrollers/hals.md:39 -msgid "" -"`set_low` and `set_high` are methods on the `embedded_hal` `OutputPin` trait." -msgstr "" +"Go 开发者可能会十分熟悉 `anyhow::Result` 提供的功能， 因为它的使用模式和工" +"效学设计与 Go 的 `(T, error)` 方法十分相似。" -#: src/bare-metal/microcontrollers/hals.md:40 +#: src/error-handling/thiserror-and-anyhow.md:59 msgid "" -"HAL crates exist for many Cortex-M and RISC-V devices, including various " -"STM32, GD32, nRF, NXP, MSP430, AVR and PIC microcontrollers." +"`anyhow::Context` is a trait implemented for the standard `Result` and " +"`Option` types. `use anyhow::Context` is necessary to enable `.context()` " +"and `.with_context()` on those types." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:1 -msgid "Board support crates" +#: src/error-handling/exercise.md:1 +msgid "Exercise: Rewriting with Result" msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:3 +#: src/error-handling/exercise.md:3 msgid "" -"Board support crates provide a further level of wrapping for a specific " -"board for convenience." +"The following implements a very simple parser for an expression language. " +"However, it handles errors by panicking. Rewrite it to instead use idiomatic " +"error handling and propagate errors to a return from `main`. Feel free to " +"use `thiserror` and `anyhow`." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:28 +#: src/error-handling/exercise.md:8 msgid "" -"In this case the board support crate is just providing more useful names, " -"and a bit of initialisation." +"HINT: start by fixing error handling in the `parse` function. Once that is " +"working correctly, update `Tokenizer` to implement " +"`Iterator>` and handle that in the parser." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:30 -msgid "" -"The crate may also include drivers for some on-board devices outside of the " -"microcontroller itself." +#: src/error-handling/exercise.md:15 src/error-handling/solution.md:9 +msgid "/// An arithmetic operator.\n" msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:32 -msgid "`microbit-v2` includes a simple driver for the LED matrix." +#: src/error-handling/exercise.md:22 src/error-handling/solution.md:16 +msgid "/// A token in the expression language.\n" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:1 -msgid "The type state pattern" +#: src/error-handling/exercise.md:30 src/error-handling/solution.md:24 +msgid "/// An expression in the expression language.\n" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:3 -msgid "" -"```rust,editable,compile_fail\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -" let gpio0 = p0::Parts::new(p.P0);\n" -"\n" -" let pin: P0_01 = gpio0.p0_01;\n" -"\n" -" // let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" -" let pin_input: P0_01> = pin.into_floating_input();\n" -" if pin_input.is_high().unwrap() {\n" -" // ...\n" -" }\n" -" let mut pin_output: P0_01> = pin_input\n" -" .into_open_drain_output(OpenDrainConfig::Disconnect0Standard1, " -"Level::Low);\n" -" pin_output.set_high().unwrap();\n" -" // pin_input.is_high(); // Error, moved.\n" -"\n" -" let _pin2: P0_02> = gpio0\n" -" .p0_02\n" -" .into_open_drain_output(OpenDrainConfig::Disconnect0Standard1, " -"Level::Low);\n" -" let _pin3: P0_03> = gpio0.p0_03." -"into_push_pull_output(Level::Low);\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling/exercise.md:34 src/error-handling/solution.md:28 +msgid "/// A reference to a variable.\n" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:32 -msgid "" -"Pins don't implement `Copy` or `Clone`, so only one instance of each can " -"exist. Once a pin is moved out of the port struct nobody else can take it." +#: src/error-handling/exercise.md:36 src/error-handling/solution.md:30 +msgid "/// A literal number.\n" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:34 -msgid "" -"Changing the configuration of a pin consumes the old pin instance, so you " -"can’t keep use the old instance afterwards." +#: src/error-handling/exercise.md:38 src/error-handling/solution.md:32 +msgid "/// A binary operation.\n" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:36 -msgid "" -"The type of a value indicates the state that it is in: e.g. in this case, " -"the configuration state of a GPIO pin. This encodes the state machine into " -"the type system, and ensures that you don't try to use a pin in a certain " -"way without properly configuring it first. Illegal state transitions are " -"caught at compile time." +#: src/error-handling/exercise.md:62 src/error-handling/exercise.md:64 +#: src/error-handling/solution.md:62 src/error-handling/solution.md:64 +msgid "'z'" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:40 -msgid "" -"You can call `is_high` on an input pin and `set_high` on an output pin, but " -"not vice-versa." +#: src/error-handling/exercise.md:64 src/error-handling/solution.md:64 +msgid "'_'" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:41 -msgid "Many HAL crates follow this pattern." +#: src/error-handling/exercise.md:70 src/error-handling/solution.md:70 +msgid "'+'" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:1 -msgid "`embedded-hal`" +#: src/error-handling/exercise.md:71 src/error-handling/solution.md:71 +msgid "'-'" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:3 -msgid "" -"The [`embedded-hal`](https://crates.io/crates/embedded-hal) crate provides a " -"number of traits covering common microcontroller peripherals." +#: src/error-handling/exercise.md:72 +msgid "\"Unexpected character {c}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:6 -msgid "GPIO" +#: src/error-handling/exercise.md:82 src/error-handling/solution.md:81 +msgid "\"Unexpected end of input\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:7 -msgid "ADC" +#: src/error-handling/exercise.md:86 +msgid "\"Invalid 32-bit integer'\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:8 -msgid "I2C, SPI, UART, CAN" +#: src/error-handling/exercise.md:90 src/error-handling/exercise.md:100 +msgid "\"Unexpected token {tok:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:9 -msgid "RNG" +#: src/error-handling/exercise.md:92 src/error-handling/solution.md:104 +msgid "// Look ahead to parse a binary operation if present.\n" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:10 -msgid "Timers" +#: src/error-handling/exercise.md:108 src/error-handling/solution.md:121 +msgid "\"10+foo+20-30\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:11 -msgid "Watchdogs" +#: src/error-handling/exercise.md:109 src/error-handling/solution.md:122 +msgid "\"{expr:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:13 -msgid "" -"Other crates then implement [drivers](https://github.com/rust-embedded/" -"awesome-embedded-rust#driver-crates) in terms of these traits, e.g. an " -"accelerometer driver might need an I2C or SPI bus implementation." +#: src/error-handling/solution.md:42 +msgid "\"Unexpected character '{0}' in input\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:19 -msgid "" -"There are implementations for many microcontrollers, as well as other " -"platforms such as Linux on Raspberry Pi." +#: src/error-handling/solution.md:79 +msgid "\"Tokenizer error: {0}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:21 -msgid "" -"There is work in progress on an `async` version of `embedded-hal`, but it " -"isn't stable yet." +#: src/error-handling/solution.md:83 +msgid "\"Unexpected token {0:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:1 -msgid "`probe-rs`, `cargo-embed`" +#: src/error-handling/solution.md:85 +msgid "\"Invalid number\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:3 +#: src/unsafe-rust/unsafe.md:3 +msgid "The Rust language has two parts:" +msgstr "Rust 语言包含两个部分：" + +#: src/unsafe-rust/unsafe.md:5 +msgid "**Safe Rust:** memory safe, no undefined behavior possible." +msgstr "\\*\\*安全 Rust：\\*\\*内存安全，没有潜在的未定义行为。" + +#: src/unsafe-rust/unsafe.md:6 msgid "" -"[probe-rs](https://probe.rs/) is a handy toolset for embedded debugging, " -"like OpenOCD but better integrated." -msgstr "" +"**Unsafe Rust:** can trigger undefined behavior if preconditions are " +"violated." +msgstr "\\*\\*不安全 Rust：\\*\\*如果违反了前提条件，可能会触发未定义的行为。" -#: src/bare-metal/microcontrollers/probe-rs.md:6 +#: src/unsafe-rust/unsafe.md:8 +#, fuzzy msgid "" -"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" +"We saw mostly safe Rust in this course, but it's important to know what " +"Unsafe Rust is." msgstr "" +"本课程中出现的大多为“安全 Rust”，但是了解“不安全 Rust”的定义 非常重要。" -#: src/bare-metal/microcontrollers/probe-rs.md:7 -msgid "GDB stub and Microsoft DAP (Debug Adapter Protocol) server" +#: src/unsafe-rust/unsafe.md:11 +msgid "" +"Unsafe code is usually small and isolated, and its correctness should be " +"carefully documented. It is usually wrapped in a safe abstraction layer." msgstr "" +"不安全的代码通常内容很少而且与其他代码隔离， 其正确性也应得到仔细记录。这类代" +"码通常封装在安全的抽象层中。" -#: src/bare-metal/microcontrollers/probe-rs.md:8 -msgid "Cargo integration" -msgstr "" +#: src/unsafe-rust/unsafe.md:14 +msgid "Unsafe Rust gives you access to five new capabilities:" +msgstr "不安全 Rust 提供了五种新功能：" -#: src/bare-metal/microcontrollers/probe-rs.md:10 +#: src/unsafe-rust/unsafe.md:16 +msgid "Dereference raw pointers." +msgstr "解引用原始指针。" + +#: src/unsafe-rust/unsafe.md:17 +msgid "Access or modify mutable static variables." +msgstr "访问或修改可变的静态变量。" + +#: src/unsafe-rust/unsafe.md:18 +msgid "Access `union` fields." +msgstr "访问 `union` 字段。" + +#: src/unsafe-rust/unsafe.md:19 +msgid "Call `unsafe` functions, including `extern` functions." +msgstr "调用 `unsafe` 函数，包括 `extern` 函数。" + +#: src/unsafe-rust/unsafe.md:20 +msgid "Implement `unsafe` traits." +msgstr "实现 `unsafe` trait。" + +#: src/unsafe-rust/unsafe.md:22 msgid "" -"`cargo-embed` is a cargo subcommand to build and flash binaries, log RTT " -"(Real Time Transfers) output and connect GDB. It's configured by an `Embed." -"toml` file in your project directory." +"We will briefly cover unsafe capabilities next. For full details, please see " +"[Chapter 19.1 in the Rust Book](https://doc.rust-lang.org/book/ch19-01-" +"unsafe-rust.html) and the [Rustonomicon](https://doc.rust-lang.org/nomicon/)." msgstr "" +"下面，我们将简要介绍这些不安全功能。如需了解完整详情，请参阅 [《Rust 手册》" +"第 19.1 章](https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html) 和 " +"[Rustonomicon](https://doc.rust-lang.org/nomicon/)。" -#: src/bare-metal/microcontrollers/probe-rs.md:16 +#: src/unsafe-rust/unsafe.md:28 +#, fuzzy msgid "" -"[CMSIS-DAP](https://arm-software.github.io/CMSIS_5/DAP/html/index.html) is " -"an Arm standard protocol over USB for an in-circuit debugger to access the " -"CoreSight Debug Access Port of various Arm Cortex processors. It's what the " -"on-board debugger on the BBC micro:bit uses." +"Unsafe Rust does not mean the code is incorrect. It means that developers " +"have turned off some compiler safety features and have to write correct code " +"by themselves. It means the compiler no longer enforces Rust's memory-safety " +"rules." msgstr "" +"不安全 Rust 并不意味着代码不正确，而是这意味着开发者已停用 编译器的安全功能，" +"必须自行编写正确的 代码。也就是说，编译器不再强制执行 Rust 的内存安全规则。" -#: src/bare-metal/microcontrollers/probe-rs.md:19 -msgid "" -"ST-Link is a range of in-circuit debuggers from ST Microelectronics, J-Link " -"is a range from SEGGER." +#: src/unsafe-rust/dereferencing.md:3 +msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" +msgstr "创建指针是安全的操作，但解引用指针需要使用 `unsafe` 方法：" + +#: src/unsafe-rust/dereferencing.md:7 +msgid "\"careful!\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:21 +#: src/unsafe-rust/dereferencing.md:12 msgid "" -"The Debug Access Port is usually either a 5-pin JTAG interface or 2-pin " -"Serial Wire Debug." +"// Safe because r1 and r2 were obtained from references and so are\n" +" // guaranteed to be non-null and properly aligned, the objects " +"underlying\n" +" // the references from which they were obtained are live throughout the\n" +" // whole unsafe block, and they are not accessed either through the\n" +" // references or concurrently through any other pointers.\n" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:22 -msgid "" -"probe-rs is a library which you can integrate into your own tools if you " -"want to." +#: src/unsafe-rust/dereferencing.md:18 +msgid "\"r1 is: {}\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:23 -msgid "" -"The [Microsoft Debug Adapter Protocol](https://microsoft.github.io/debug-" -"adapter-protocol/) lets VSCode and other IDEs debug code running on any " -"supported microcontroller." +#: src/unsafe-rust/dereferencing.md:19 +msgid "\"uhoh\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:25 -msgid "cargo-embed is a binary built using the probe-rs library." +#: src/unsafe-rust/dereferencing.md:20 +msgid "\"r2 is: {}\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:26 +#: src/unsafe-rust/dereferencing.md:23 msgid "" -"RTT (Real Time Transfers) is a mechanism to transfer data between the debug " -"host and the target through a number of ringbuffers." -msgstr "" - -#: src/bare-metal/microcontrollers/debugging.md:3 -msgid "_Embed.toml_:" +"// NOT SAFE. DO NOT DO THIS.\n" +" /*\n" +" let r3: &String = unsafe { &*r1 };\n" +" drop(s);\n" +" println!(\"r3 is: {}\", *r3);\n" +" */" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:5 +#: src/unsafe-rust/dereferencing.md:34 msgid "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"```" +"It is good practice (and required by the Android Rust style guide) to write " +"a comment for each `unsafe` block explaining how the code inside it " +"satisfies the safety requirements of the unsafe operations it is doing." msgstr "" +"我们建议（而且 Android Rust 样式指南要求）为每个 `unsafe` 代码块编写一条注" +"释， 说明该代码块中的代码如何满足其所执行的不安全操作的 安全要求。" -#: src/bare-metal/microcontrollers/debugging.md:13 -msgid "In one terminal under `src/bare-metal/microcontrollers/examples/`:" +#: src/unsafe-rust/dereferencing.md:38 +msgid "" +"In the case of pointer dereferences, this means that the pointers must be " +"[_valid_](https://doc.rust-lang.org/std/ptr/index.html#safety), i.e.:" msgstr "" +"对于指针解除引用，这意味着指针必须为 [_valid_](https://doc.rust-lang.org/std/" +"ptr/index.html#safety)，即：" -#: src/bare-metal/microcontrollers/debugging.md:19 -msgid "In another terminal in the same directory:" -msgstr "" +#: src/unsafe-rust/dereferencing.md:41 +msgid "The pointer must be non-null." +msgstr "指针必须为非 null。" -#: src/bare-metal/microcontrollers/debugging.md:21 +#: src/unsafe-rust/dereferencing.md:42 msgid "" -"```sh\n" -"gdb-multiarch target/thumbv7em-none-eabihf/debug/board_support --eval-" -"command=\"target remote :1337\"\n" -"```" -msgstr "" +"The pointer must be _dereferenceable_ (within the bounds of a single " +"allocated object)." +msgstr "指针必须是 _dereferenceable_（在单个已分配对象的边界内）。" -#: src/bare-metal/microcontrollers/debugging.md:27 -msgid "In GDB, try running:" -msgstr "" +#: src/unsafe-rust/dereferencing.md:44 +msgid "The object must not have been deallocated." +msgstr "对象不得已取消分配。" -#: src/bare-metal/microcontrollers/other-projects.md:1 -#: src/bare-metal/aps/other-projects.md:1 -msgid "Other projects" -msgstr "" +#: src/unsafe-rust/dereferencing.md:45 +msgid "There must not be concurrent accesses to the same location." +msgstr "不得并发访问相同位置。" -#: src/bare-metal/microcontrollers/other-projects.md:3 -msgid "[RTIC](https://rtic.rs/)" +#: src/unsafe-rust/dereferencing.md:46 +msgid "" +"If the pointer was obtained by casting a reference, the underlying object " +"must be live and no reference may be used to access the memory." msgstr "" +"如果通过转换引用类型来获取指针，则底层对象必须处于活跃状态， 而且不得使用任何" +"引用来访问内存。" -#: src/bare-metal/microcontrollers/other-projects.md:4 -msgid "\"Real-Time Interrupt-driven Concurrency\"" -msgstr "" +#: src/unsafe-rust/dereferencing.md:49 +msgid "In most cases the pointer must also be properly aligned." +msgstr "在大多数情况下，指针还必须正确对齐。" -#: src/bare-metal/microcontrollers/other-projects.md:5 +#: src/unsafe-rust/dereferencing.md:51 msgid "" -"Shared resource management, message passing, task scheduling, timer queue" +"The \"NOT SAFE\" section gives an example of a common kind of UB bug: `*r1` " +"has the `'static` lifetime, so `r3` has type `&'static String`, and thus " +"outlives `s`. Creating a reference from a pointer requires _great care_." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:6 -msgid "[Embassy](https://embassy.dev/)" -msgstr "" +#: src/unsafe-rust/mutable-static.md:3 +msgid "It is safe to read an immutable static variable:" +msgstr "读取不可变的静态变量是安全的操作：" -#: src/bare-metal/microcontrollers/other-projects.md:7 -msgid "`async` executors with priorities, timers, networking, USB" -msgstr "" +#: src/unsafe-rust/mutable-static.md:6 +#, fuzzy +msgid "\"Hello, world!\"" +msgstr "Hello World!" -#: src/bare-metal/microcontrollers/other-projects.md:8 -msgid "[TockOS](https://www.tockos.org/documentation/getting-started)" +#: src/unsafe-rust/mutable-static.md:9 +msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:9 +#: src/unsafe-rust/mutable-static.md:13 msgid "" -"Security-focused RTOS with preemptive scheduling and Memory Protection Unit " -"support" -msgstr "" +"However, since data races can occur, it is unsafe to read and write mutable " +"static variables:" +msgstr "但是，读取和写入可变的静态变量是不安全的，因为这可能会 造成数据争用：" -#: src/bare-metal/microcontrollers/other-projects.md:10 -msgid "[Hubris](https://hubris.oxide.computer/)" +#: src/unsafe-rust/mutable-static.md:29 +msgid "\"COUNTER: {COUNTER}\"" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:11 +#: src/unsafe-rust/mutable-static.md:36 msgid "" -"Microkernel RTOS from Oxide Computer Company with memory protection, " -"unprivileged drivers, IPC" -msgstr "" - -#: src/bare-metal/microcontrollers/other-projects.md:12 -msgid "[Bindings for FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" +"The program here is safe because it is single-threaded. However, the Rust " +"compiler is conservative and will assume the worst. Try removing the " +"`unsafe` and see how the compiler explains that it is undefined behavior to " +"mutate a static from multiple threads." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:13 +#: src/unsafe-rust/mutable-static.md:41 msgid "" -"Some platforms have `std` implementations, e.g. [esp-idf](https://esp-rs." -"github.io/book/overview/using-the-standard-library.html)." +"Using a mutable static is generally a bad idea, but there are some cases " +"where it might make sense in low-level `no_std` code, such as implementing a " +"heap allocator or working with some C APIs." msgstr "" +"通常，我们不建议使用可变的静态变量，但在某些情况下，在低层级 `no_std` 代码中" +"可能需要这样做， 例如实现堆分配器或使用某些 C API。" -#: src/bare-metal/microcontrollers/other-projects.md:18 -msgid "RTIC can be considered either an RTOS or a concurrency framework." -msgstr "" +#: src/unsafe-rust/unions.md:3 +msgid "Unions are like enums, but you need to track the active field yourself:" +msgstr "联合体与枚举类似，但您需要自行跟踪活跃字段：" -#: src/bare-metal/microcontrollers/other-projects.md:19 -msgid "It doesn't include any HALs." +#: src/unsafe-rust/unions.md:14 +msgid "\"int: {}\"" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:20 -msgid "" -"It uses the Cortex-M NVIC (Nested Virtual Interrupt Controller) for " -"scheduling rather than a proper kernel." +#: src/unsafe-rust/unions.md:15 +msgid "\"bool: {}\"" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:22 -msgid "Cortex-M only." -msgstr "" +#: src/unsafe-rust/unions.md:15 +#, fuzzy +msgid "// Undefined behavior!\n" +msgstr "Rust 没有运行时未定义行为：" -#: src/bare-metal/microcontrollers/other-projects.md:23 +#: src/unsafe-rust/unions.md:21 msgid "" -"Google uses TockOS on the Haven microcontroller for Titan security keys." +"Unions are very rarely needed in Rust as you can usually use an enum. They " +"are occasionally needed for interacting with C library APIs." msgstr "" +"在 Rust 中很少需要用到联合体，因为您通常可以使用枚举。联合体只是偶尔用于 与 " +"C 库 API 进行交互。" -#: src/bare-metal/microcontrollers/other-projects.md:24 +#: src/unsafe-rust/unions.md:24 msgid "" -"FreeRTOS is mostly written in C, but there are Rust bindings for writing " -"applications." +"If you just want to reinterpret bytes as a different type, you probably want " +"[`std::mem::transmute`](https://doc.rust-lang.org/stable/std/mem/fn." +"transmute.html) or a safe wrapper such as the [`zerocopy`](https://crates.io/" +"crates/zerocopy) crate." msgstr "" +"如果您只是想将字节重新解释为其他类型，则可能需要使用 [`std::mem::transmute`]" +"(https://doc.rust-lang.org/stable/std/mem/fn.transmute.html) 或 安全的封装容" +"器，例如 [`zerocopy`](https://crates.io/crates/zerocopy) crate。" -#: src/exercises/bare-metal/morning.md:3 -msgid "" -"We will read the direction from an I2C compass, and log the readings to a " -"serial port." -msgstr "" +#: src/unsafe-rust/unsafe-functions.md:3 src/unsafe-rust/unsafe-functions.md:74 +msgid "Calling Unsafe Functions" +msgstr "调用 Unsafe 函数" -#: src/exercises/bare-metal/compass.md:3 +#: src/unsafe-rust/unsafe-functions.md:5 msgid "" -"We will read the direction from an I2C compass, and log the readings to a " -"serial port. If you have time, try displaying it on the LEDs somehow too, or " -"use the buttons somehow." +"A function or method can be marked `unsafe` if it has extra preconditions " +"you must uphold to avoid undefined behaviour:" msgstr "" +"如果函数或方法具有额外的前提条件，您必须遵守这些前提条件来避免未定义的行为， " +"则可以将该函数或方法标记为 `unsafe`：" -#: src/exercises/bare-metal/compass.md:6 -msgid "Hints:" +#: src/unsafe-rust/unsafe-functions.md:9 src/unsafe-rust/exercise.md:91 +#: src/unsafe-rust/solution.md:41 src/android/interoperability/with-c.md:9 +#: src/android/interoperability/with-c/rust.md:15 +#: src/android/interoperability/with-c/rust.md:30 +#: src/android/interoperability/cpp/cpp-bridge.md:29 +#: src/android/interoperability/cpp/cpp-bridge.md:38 +#: src/exercises/chromium/build-rules.md:8 +#: src/exercises/chromium/build-rules.md:21 +#: src/bare-metal/aps/inline-assembly.md:19 +#: src/bare-metal/aps/better-uart/using.md:24 +#: src/bare-metal/aps/logging/using.md:23 src/exercises/bare-metal/rtc.md:49 +#: src/exercises/bare-metal/rtc.md:104 src/exercises/bare-metal/rtc.md:110 +#: src/exercises/bare-metal/rtc.md:118 src/exercises/bare-metal/rtc.md:124 +#: src/exercises/bare-metal/rtc.md:130 src/exercises/bare-metal/rtc.md:136 +#: src/exercises/bare-metal/rtc.md:142 src/exercises/bare-metal/rtc.md:148 +#: src/exercises/bare-metal/solutions-afternoon.md:43 +msgid "\"C\"" msgstr "" -#: src/exercises/bare-metal/compass.md:8 -msgid "" -"Check the documentation for the [`lsm303agr`](https://docs.rs/lsm303agr/" -"latest/lsm303agr/) and [`microbit-v2`](https://docs.rs/microbit-v2/latest/" -"microbit/) crates, as well as the [micro:bit hardware](https://tech.microbit." -"org/hardware/)." +#: src/unsafe-rust/unsafe-functions.md:14 +msgid "\"🗻∈🌏\"" msgstr "" -#: src/exercises/bare-metal/compass.md:11 +#: src/unsafe-rust/unsafe-functions.md:16 msgid "" -"The LSM303AGR Inertial Measurement Unit is connected to the internal I2C bus." +"// Safe because the indices are in the correct order, within the bounds of\n" +" // the string slice, and lie on UTF-8 sequence boundaries.\n" msgstr "" -#: src/exercises/bare-metal/compass.md:12 -msgid "" -"TWI is another name for I2C, so the I2C master peripheral is called TWIM." +#: src/unsafe-rust/unsafe-functions.md:19 +#: src/unsafe-rust/unsafe-functions.md:20 +#: src/unsafe-rust/unsafe-functions.md:21 +msgid "\"emoji: {}\"" msgstr "" -#: src/exercises/bare-metal/compass.md:13 -msgid "" -"The LSM303AGR driver needs something implementing the `embedded_hal::" -"blocking::i2c::WriteRead` trait. The [`microbit::hal::Twim`](https://docs.rs/" -"microbit-v2/latest/microbit/hal/struct.Twim.html) struct implements this." +#: src/unsafe-rust/unsafe-functions.md:24 +msgid "\"char count: {}\"" msgstr "" -#: src/exercises/bare-metal/compass.md:17 -msgid "" -"You have a [`microbit::Board`](https://docs.rs/microbit-v2/latest/microbit/" -"struct.Board.html) struct with fields for the various pins and peripherals." -msgstr "" +#: src/unsafe-rust/unsafe-functions.md:27 +#, fuzzy +msgid "// Undefined behavior if abs misbehaves.\n" +msgstr "Rust 没有运行时未定义行为：" -#: src/exercises/bare-metal/compass.md:19 -msgid "" -"You can also look at the [nRF52833 datasheet](https://infocenter.nordicsemi." -"com/pdf/nRF52833_PS_v1.5.pdf) if you want, but it shouldn't be necessary for " -"this exercise." +#: src/unsafe-rust/unsafe-functions.md:28 +msgid "\"Absolute value of -3 according to C: {}\"" msgstr "" -#: src/exercises/bare-metal/compass.md:23 +#: src/unsafe-rust/unsafe-functions.md:31 msgid "" -"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " -"look in the `compass` directory for the following files." +"// Not upholding the UTF-8 encoding requirement breaks memory safety!\n" +" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" +" // println!(\"char count: {}\", count_chars(unsafe {\n" +" // emojis.get_unchecked(0..3) }));\n" msgstr "" -#: src/exercises/bare-metal/compass.md:26 src/exercises/bare-metal/rtc.md:19 -#, fuzzy -msgid "_src/main.rs_:" -msgstr "_hello_rust/src/main.rs_:" +#: src/unsafe-rust/unsafe-functions.md:42 +#: src/unsafe-rust/unsafe-functions.md:86 +msgid "Writing Unsafe Functions" +msgstr "编写 Unsafe 函数" -#: src/exercises/bare-metal/compass.md:30 +#: src/unsafe-rust/unsafe-functions.md:44 msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use core::fmt::Write;\n" -"use cortex_m_rt::entry;\n" -"use microbit::{hal::uarte::{Baudrate, Parity, Uarte}, Board};\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let board = Board::take().unwrap();\n" -"\n" -" // Configure serial port.\n" -" let mut serial = Uarte::new(\n" -" board.UARTE0,\n" -" board.uart.into(),\n" -" Parity::EXCLUDED,\n" -" Baudrate::BAUD115200,\n" -" );\n" -"\n" -" // Set up the I2C controller and Inertial Measurement Unit.\n" -" // TODO\n" -"\n" -" writeln!(serial, \"Ready.\").unwrap();\n" -"\n" -" loop {\n" -" // Read compass data and log it to the serial port.\n" -" // TODO\n" -" }\n" -"}\n" -"```" +"You can mark your own functions as `unsafe` if they require particular " +"conditions to avoid undefined behaviour." msgstr "" +"如果您自己编写的函数需要满足特定条件以避免未定义的行为， 您可以将这些函数标记" +"为 `unsafe`。" -#: src/exercises/bare-metal/compass.md:64 src/exercises/bare-metal/rtc.md:385 -msgid "_Cargo.toml_ (you shouldn't need to change this):" +#: src/unsafe-rust/unsafe-functions.md:48 +msgid "" +"/// Swaps the values pointed to by the given pointers.\n" +"///\n" +"/// # Safety\n" +"///\n" +"/// The pointers must be valid and properly aligned.\n" msgstr "" -#: src/exercises/bare-metal/compass.md:68 -msgid "" -"```toml\n" -"[workspace]\n" -"\n" -"[package]\n" -"name = \"compass\"\n" -"version = \"0.1.0\"\n" -"edition = \"2021\"\n" -"publish = false\n" -"\n" -"[dependencies]\n" -"cortex-m-rt = \"0.7.3\"\n" -"embedded-hal = \"0.2.6\"\n" -"lsm303agr = \"0.2.2\"\n" -"microbit-v2 = \"0.13.0\"\n" -"panic-halt = \"0.2.0\"\n" -"```" +#: src/unsafe-rust/unsafe-functions.md:63 +msgid "// Safe because ...\n" msgstr "" -#: src/exercises/bare-metal/compass.md:85 -msgid "_Embed.toml_ (you shouldn't need to change this):" +#: src/unsafe-rust/unsafe-functions.md:68 +msgid "\"a = {}, b = {}\"" msgstr "" -#: src/exercises/bare-metal/compass.md:89 +#: src/unsafe-rust/unsafe-functions.md:76 +#, fuzzy msgid "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"\n" -"[debug.reset]\n" -"halt_afterwards = true\n" -"```" +"`get_unchecked`, like most `_unchecked` functions, is unsafe, because it can " +"create UB if the range is incorrect. `abs` is incorrect for a different " +"reason: it is an external function (FFI). Calling external functions is " +"usually only a problem when those functions do things with pointers which " +"might violate Rust's memory model, but in general any C function might have " +"undefined behaviour under any arbitrary circumstances." msgstr "" +"这个问题通常仅存在于使用指针执行违反 Rust 内存模型的操作的外部函数中。 但一般" +"而言，任何 C 函数都有可能在任意情况下出现未定义行为。" -#: src/exercises/bare-metal/compass.md:100 src/exercises/bare-metal/rtc.md:985 -msgid "_.cargo/config.toml_ (you shouldn't need to change this):" +#: src/unsafe-rust/unsafe-functions.md:83 +msgid "" +"The `\"C\"` in this example is the ABI; [other ABIs are available too]" +"(https://doc.rust-lang.org/reference/items/external-blocks.html)." msgstr "" +"本例中的“C”是 ABI；[也可以使用其他 ABI](https://doc.rust-lang.org/reference/" +"items/external-blocks.html)。" -#: src/exercises/bare-metal/compass.md:104 +#: src/unsafe-rust/unsafe-functions.md:88 +#, fuzzy msgid "" -"```toml\n" -"[build]\n" -"target = \"thumbv7em-none-eabihf\" # Cortex-M4F\n" -"\n" -"[target.'cfg(all(target_arch = \"arm\", target_os = \"none\"))']\n" -"rustflags = [\"-C\", \"link-arg=-Tlink.x\"]\n" -"```" +"We wouldn't actually use pointers for a `swap` function - it can be done " +"safely with references." +msgstr "实际上，我们不会这样使用指针，因为使用引用可以安全地达到相同的目的。" + +#: src/unsafe-rust/unsafe-functions.md:91 +#, fuzzy +msgid "" +"Note that unsafe code is allowed within an unsafe function without an " +"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " +"Try adding it and see what happens. This will likely change in a future Rust " +"edition." msgstr "" +"请注意，在不安全函数中，可以在没有 `unsafe` 代码块的情况下使用不安全代码。我" +"们可以 使用 `#[deny(unsafe_op_in_unsafe_fn)]` 来禁止此行为。请尝试添加该命" +"令，看看会出现什么情况。" -#: src/exercises/bare-metal/compass.md:112 -msgid "See the serial output on Linux with:" +#: src/unsafe-rust/unsafe-traits.md:1 +msgid "Implementing Unsafe Traits" +msgstr "实现 Unsafe Trait" + +#: src/unsafe-rust/unsafe-traits.md:3 +msgid "" +"Like with functions, you can mark a trait as `unsafe` if the implementation " +"must guarantee particular conditions to avoid undefined behaviour." msgstr "" +"与函数一样，如果您在实现某个 trait 时必须保证特定条件来避免未定义的行为， 您" +"也可以将该 trait 标记为 `unsafe`。" -#: src/exercises/bare-metal/compass.md:118 +#: src/unsafe-rust/unsafe-traits.md:6 msgid "" -"Or on Mac OS something like (the device name may be slightly different):" +"For example, the `zerocopy` crate has an unsafe trait that looks [something " +"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" msgstr "" +"例如，`zerocopy` crate 包含一个不安全的 trait， [大致内容是这样的](https://" +"docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html)：" -#: src/exercises/bare-metal/compass.md:124 -msgid "Use Ctrl+A Ctrl+Q to quit picocom." +#: src/unsafe-rust/unsafe-traits.md:12 +msgid "" +"/// ...\n" +"/// # Safety\n" +"/// The type must have a defined representation and no padding.\n" msgstr "" -#: src/bare-metal/aps.md:1 -msgid "Application processors" +#: src/unsafe-rust/unsafe-traits.md:26 +msgid "// Safe because u32 has a defined representation and no padding.\n" msgstr "" -#: src/bare-metal/aps.md:3 +#: src/unsafe-rust/unsafe-traits.md:33 msgid "" -"So far we've talked about microcontrollers, such as the Arm Cortex-M series. " -"Now let's try writing something for Cortex-A. For simplicity we'll just work " -"with QEMU's aarch64 ['virt'](https://qemu-project.gitlab.io/qemu/system/arm/" -"virt.html) board." +"There should be a `# Safety` section on the Rustdoc for the trait explaining " +"the requirements for the trait to be safely implemented." msgstr "" +"在 Rustdoc 中有关 trait 的章节下，有一个标题为 `# 安全` 的部分介绍了 安全实" +"现 trait 的要求。" -#: src/bare-metal/aps.md:9 +#: src/unsafe-rust/unsafe-traits.md:36 msgid "" -"Broadly speaking, microcontrollers don't have an MMU or multiple levels of " -"privilege (exception levels on Arm CPUs, rings on x86), while application " -"processors do." -msgstr "" +"The actual safety section for `AsBytes` is rather longer and more " +"complicated." +msgstr "实际上，与 `AsBytes` 相关的安全说明远比这里展示的更详尽、更复杂。" + +#: src/unsafe-rust/unsafe-traits.md:38 +msgid "The built-in `Send` and `Sync` traits are unsafe." +msgstr "内置的 `Send` 和 `Sync` trait 都是不安全的。" + +#: src/unsafe-rust/exercise.md:1 +msgid "Safe FFI Wrapper" +msgstr "安全 FFI 封装容器" -#: src/bare-metal/aps.md:11 +#: src/unsafe-rust/exercise.md:3 msgid "" -"QEMU supports emulating various different machines or board models for each " -"architecture. The 'virt' board doesn't correspond to any particular real " -"hardware, but is designed purely for virtual machines." +"Rust has great support for calling functions through a _foreign function " +"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " +"functions you would use from C to read the names of files in a directory." msgstr "" -#: src/bare-metal/aps/entry-point.md:3 +#: src/unsafe-rust/exercise.md:7 +msgid "You will want to consult the manual pages:" +msgstr "建议您参考以下手册页面：" + +#: src/unsafe-rust/exercise.md:9 +msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" +msgstr "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" + +#: src/unsafe-rust/exercise.md:10 +msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" +msgstr "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" + +#: src/unsafe-rust/exercise.md:11 +msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" +msgstr "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" + +#: src/unsafe-rust/exercise.md:13 msgid "" -"Before we can start running Rust code, we need to do some initialisation." +"You will also want to browse the [`std::ffi`](https://doc.rust-lang.org/std/" +"ffi/) module. There you find a number of string types which you need for the " +"exercise:" msgstr "" +"您还需要浏览[“std::ffi”](https://doc.rust-lang.org/std/ffi/)模块。在下方，您" +"会发现完成这个练习所需的多种字符串类型：" -#: src/bare-metal/aps/entry-point.md:5 +#: src/unsafe-rust/exercise.md:16 +msgid "Encoding" +msgstr "编码" + +#: src/unsafe-rust/exercise.md:16 +msgid "Use" +msgstr "使用" + +#: src/unsafe-rust/exercise.md:18 msgid "" -"```armasm\n" -".section .init.entry, \"ax\"\n" -".global entry\n" -"entry:\n" -" /*\n" -" * Load and apply the memory management configuration, ready to enable " -"MMU and\n" -" * caches.\n" -" */\n" -" adrp x30, idmap\n" -" msr ttbr0_el1, x30\n" -"\n" -" mov_i x30, .Lmairval\n" -" msr mair_el1, x30\n" -"\n" -" mov_i x30, .Ltcrval\n" -" /* Copy the supported PA range into TCR_EL1.IPS. */\n" -" mrs x29, id_aa64mmfr0_el1\n" -" bfi x30, x29, #32, #4\n" -"\n" -" msr tcr_el1, x30\n" -"\n" -" mov_i x30, .Lsctlrval\n" -"\n" -" /*\n" -" * Ensure everything before this point has completed, then invalidate " -"any\n" -" * potentially stale local TLB entries before they start being used.\n" -" */\n" -" isb\n" -" tlbi vmalle1\n" -" ic iallu\n" -" dsb nsh\n" -" isb\n" -"\n" -" /*\n" -" * Configure sctlr_el1 to enable MMU and cache and don't proceed until " -"this\n" -" * has completed.\n" -" */\n" -" msr sctlr_el1, x30\n" -" isb\n" -"\n" -" /* Disable trapping floating point access in EL1. */\n" -" mrs x30, cpacr_el1\n" -" orr x30, x30, #(0x3 << 20)\n" -" msr cpacr_el1, x30\n" -" isb\n" -"\n" -" /* Zero out the bss section. */\n" -" adr_l x29, bss_begin\n" -" adr_l x30, bss_end\n" -"0: cmp x29, x30\n" -" b.hs 1f\n" -" stp xzr, xzr, [x29], #16\n" -" b 0b\n" -"\n" -"1: /* Prepare the stack. */\n" -" adr_l x30, boot_stack_end\n" -" mov sp, x30\n" -"\n" -" /* Set up exception vector. */\n" -" adr x30, vector_table_el1\n" -" msr vbar_el1, x30\n" -"\n" -" /* Call into Rust code. */\n" -" bl main\n" -"\n" -" /* Loop forever waiting for interrupts. */\n" -"2: wfi\n" -" b 2b\n" -"```" +"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" +"(https://doc.rust-lang.org/std/string/struct.String.html)" msgstr "" +"[“str”](https://doc.rust-lang.org/std/primitive.str.html)和[“String”]" +"(https://doc.rust-lang.org/std/string/struct.String.html)" -#: src/bare-metal/aps/entry-point.md:77 +#: src/unsafe-rust/exercise.md:18 +msgid "UTF-8" +msgstr "UTF-8" + +#: src/unsafe-rust/exercise.md:18 +msgid "Text processing in Rust" +msgstr "用 Rust 进行文本处理" + +#: src/unsafe-rust/exercise.md:19 msgid "" -"This is the same as it would be for C: initialising the processor state, " -"zeroing the BSS, and setting up the stack pointer." +"[`CStr`](https://doc.rust-lang.org/std/ffi/struct.CStr.html) and [`CString`]" +"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" msgstr "" +"[“CStr”](https://doc.rust-lang.org/std/ffi/struct.CStr.html)和[“CString”]" +"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" -#: src/bare-metal/aps/entry-point.md:79 +#: src/unsafe-rust/exercise.md:19 +msgid "NUL-terminated" +msgstr "以空字符结尾" + +#: src/unsafe-rust/exercise.md:19 +msgid "Communicating with C functions" +msgstr "与 C 函数通信" + +#: src/unsafe-rust/exercise.md:20 msgid "" -"The BSS (block starting symbol, for historical reasons) is the part of the " -"object file which containing statically allocated variables which are " -"initialised to zero. They are omitted from the image, to avoid wasting space " -"on zeroes. The compiler assumes that the loader will take care of zeroing " -"them." +"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " +"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" msgstr "" +"[“OsStr”](https://doc.rust-lang.org/std/ffi/struct.OsStr.html)和[“OsString”]" +"(https://doc.rust-lang.org/std/ffi/struct.OsString.html)" + +#: src/unsafe-rust/exercise.md:20 +msgid "OS-specific" +msgstr "特定于操作系统" -#: src/bare-metal/aps/entry-point.md:83 +#: src/unsafe-rust/exercise.md:20 +msgid "Communicating with the OS" +msgstr "与操作系统通信" + +#: src/unsafe-rust/exercise.md:22 +msgid "You will convert between all these types:" +msgstr "您将在以下所有类型之间进行转换：" + +#: src/unsafe-rust/exercise.md:24 msgid "" -"The BSS may already be zeroed, depending on how memory is initialised and " -"the image is loaded, but we zero it to be sure." -msgstr "" +"`&str` to `CString`: you need to allocate space for a trailing `\\0` " +"character," +msgstr "将 `&str` 转换为 `CString`：您需要为尾随 `\\0` 字符分配空格，" -#: src/bare-metal/aps/entry-point.md:85 +#: src/unsafe-rust/exercise.md:25 +msgid "`CString` to `*const i8`: you need a pointer to call C functions," +msgstr "将 `CString` 转换为 `\\*const i8` ：您需要一个指针来调用 C 函数，" + +#: src/unsafe-rust/exercise.md:26 msgid "" -"We need to enable the MMU and cache before reading or writing any memory. If " -"we don't:" +"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " +"character," msgstr "" +"将 `\\*const i8` 转换为 `&CStr` ：您需要一些能够找到尾随 `\\0` 字符的内容，" -#: src/bare-metal/aps/entry-point.md:86 +#: src/unsafe-rust/exercise.md:28 +#, fuzzy msgid "" -"Unaligned accesses will fault. We build the Rust code for the `aarch64-" -"unknown-none` target which sets `+strict-align` to prevent the compiler " -"generating unaligned accesses, so it should be fine in this case, but this " -"is not necessarily the case in general." +"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " +"unknown data\"," msgstr "" +"将 `&CStr` 转换为 `&\\[u8\\]` ：一个字节 Slice 是“一些未知数据”的通用接口，" -#: src/bare-metal/aps/entry-point.md:89 +#: src/unsafe-rust/exercise.md:30 msgid "" -"If it were running in a VM, this can lead to cache coherency issues. The " -"problem is that the VM is accessing memory directly with the cache disabled, " -"while the host has cacheable aliases to the same memory. Even if the host " -"doesn't explicitly access the memory, speculative accesses can lead to cache " -"fills, and then changes from one or the other will get lost when the cache " -"is cleaned or the VM enables the cache. (Cache is keyed by physical address, " -"not VA or IPA.)" +"`&[u8]` to `&OsStr`: `&OsStr` is a step towards `OsString`, use [`OsStrExt`]" +"(https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html) to create it," msgstr "" +"将 `&\\[u8\\]` 转换为 `&OsStr` ：`&OsStr` 是向 `OsString` 迈进的一步，请使用" +"[`OsStrExt`](https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html)来" +"创建它，" -#: src/bare-metal/aps/entry-point.md:94 +#: src/unsafe-rust/exercise.md:33 msgid "" -"For simplicity, we just use a hardcoded pagetable (see `idmap.S`) which " -"identity maps the first 1 GiB of address space for devices, the next 1 GiB " -"for DRAM, and another 1 GiB higher up for more devices. This matches the " -"memory layout that QEMU uses." +"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " +"return it and call `readdir` again." msgstr "" +"将“&OsStr”转换为“OsString”：您需要克隆“&OsStr”中的数据，以便能够返回它并再次" +"调用“readdir”。" -#: src/bare-metal/aps/entry-point.md:97 +#: src/unsafe-rust/exercise.md:36 msgid "" -"We also set up the exception vector (`vbar_el1`), which we'll see more about " -"later." +"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " +"useful chapter about FFI." msgstr "" +"[秘典](https://doc.rust-lang.org/nomicon/ffi.html) 中也有一个关于 FFI 的非常" +"实用的章节。" -#: src/bare-metal/aps/entry-point.md:98 +#: src/unsafe-rust/exercise.md:47 msgid "" -"All examples this afternoon assume we will be running at exception level 1 " -"(EL1). If you need to run at a different exception level you'll need to " -"modify `entry.S` accordingly." +"Copy the code below to and fill in the missing " +"functions and methods:" msgstr "" +"将以下代码复制到 ，并填入缺少的函数和方法：" -#: src/bare-metal/aps/inline-assembly.md:1 -msgid "Inline assembly" +#: src/unsafe-rust/exercise.md:56 src/unsafe-rust/exercise.md:69 +#: src/unsafe-rust/exercise.md:80 src/unsafe-rust/exercise.md:94 +#: src/unsafe-rust/exercise.md:102 src/unsafe-rust/solution.md:6 +#: src/unsafe-rust/solution.md:19 src/unsafe-rust/solution.md:30 +#: src/unsafe-rust/solution.md:44 src/unsafe-rust/solution.md:52 +msgid "\"macos\"" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:3 -msgid "" -"Sometimes we need to use assembly to do things that aren't possible with " -"Rust code. For example, to make an HVC (hypervisor call) to tell the " -"firmware to power off the system:" +#: src/unsafe-rust/exercise.md:59 src/unsafe-rust/solution.md:9 +msgid "// Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:6 +#: src/unsafe-rust/exercise.md:66 src/unsafe-rust/solution.md:16 msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"use core::arch::asm;\n" -"use core::panic::PanicInfo;\n" -"\n" -"mod exceptions;\n" -"\n" -"const PSCI_SYSTEM_OFF: u32 = 0x84000008;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(_x0: u64, _x1: u64, _x2: u64, _x3: u64) {\n" -" // Safe because this only uses the declared registers and doesn't do\n" -" // anything with memory.\n" -" unsafe {\n" -" asm!(\"hvc #0\",\n" -" inout(\"w0\") PSCI_SYSTEM_OFF => _,\n" -" inout(\"w1\") 0 => _,\n" -" inout(\"w2\") 0 => _,\n" -" inout(\"w3\") 0 => _,\n" -" inout(\"w4\") 0 => _,\n" -" inout(\"w5\") 0 => _,\n" -" inout(\"w6\") 0 => _,\n" -" inout(\"w7\") 0 => _,\n" -" options(nomem, nostack)\n" -" );\n" -" }\n" -"\n" -" loop {}\n" -"}\n" -"```" +"// Layout according to the Linux man page for readdir(3), where ino_t and\n" +" // off_t are resolved according to the definitions in\n" +" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:39 -msgid "" -"(If you actually want to do this, use the [`smccc`](https://crates.io/crates/" -"smccc) crate which has wrappers for all these functions.)" +#: src/unsafe-rust/exercise.md:79 src/unsafe-rust/solution.md:29 +msgid "// Layout according to the macOS man page for dir(5).\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:43 -msgid "" -"PSCI is the Arm Power State Coordination Interface, a standard set of " -"functions to manage system and CPU power states, among other things. It is " -"implemented by EL3 firmware and hypervisors on many systems." +#: src/unsafe-rust/exercise.md:94 src/unsafe-rust/exercise.md:102 +#: src/unsafe-rust/solution.md:44 src/unsafe-rust/solution.md:52 +msgid "\"x86_64\"" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:46 +#: src/unsafe-rust/exercise.md:97 src/unsafe-rust/solution.md:47 msgid "" -"The `0 => _` syntax means initialise the register to 0 before running the " -"inline assembly code, and ignore its contents afterwards. We need to use " -"`inout` rather than `in` because the call could potentially clobber the " -"contents of the registers." +"// See https://github.com/rust-lang/libc/issues/414 and the section on\n" +" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" +" //\n" +" // \"Platforms that existed before these updates were available\" " +"refers\n" +" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " +"PowerPC.\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:49 -msgid "" -"This `main` function needs to be `#[no_mangle]` and `extern \"C\"` because " -"it is called from our entry point in `entry.S`." +#: src/unsafe-rust/exercise.md:103 src/unsafe-rust/solution.md:53 +msgid "\"readdir$INODE64\"" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:51 +#: src/unsafe-rust/exercise.md:121 src/unsafe-rust/solution.md:71 msgid "" -"`_x0`–`_x3` are the values of registers `x0`–`x3`, which are conventionally " -"used by the bootloader to pass things like a pointer to the device tree. " -"According to the standard aarch64 calling convention (which is what `extern " -"\"C\"` specifies to use), registers `x0`–`x7` are used for the first 8 " -"arguments passed to a function, so `entry.S` doesn't need to do anything " -"special except make sure it doesn't change these registers." +"// Call opendir and return a Ok value if that worked,\n" +" // otherwise return Err with a message.\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:56 -msgid "" -"Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" -"examples`." -msgstr "" - -#: src/bare-metal/aps/mmio.md:1 -msgid "Volatile memory access for MMIO" +#: src/unsafe-rust/exercise.md:130 +msgid "// Keep calling readdir until we get a NULL pointer back.\n" msgstr "" -#: src/bare-metal/aps/mmio.md:3 -msgid "Use `pointer::read_volatile` and `pointer::write_volatile`." +#: src/unsafe-rust/exercise.md:137 src/unsafe-rust/solution.md:105 +msgid "// Call closedir as needed.\n" msgstr "" -#: src/bare-metal/aps/mmio.md:4 -msgid "Never hold a reference." +#: src/unsafe-rust/exercise.md:143 src/unsafe-rust/solution.md:116 +#: src/unsafe-rust/solution.md:140 src/unsafe-rust/solution.md:155 +#: src/android/interoperability/with-c/rust.md:44 +msgid "\".\"" msgstr "" -#: src/bare-metal/aps/mmio.md:5 -msgid "" -"`addr_of!` lets you get fields of structs without creating an intermediate " -"reference." +#: src/unsafe-rust/exercise.md:144 src/unsafe-rust/solution.md:117 +msgid "\"files: {:#?}\"" msgstr "" -#: src/bare-metal/aps/mmio.md:9 -msgid "" -"Volatile access: read or write operations may have side-effects, so prevent " -"the compiler or hardware from reordering, duplicating or eliding them." +#: src/unsafe-rust/solution.md:74 +msgid "\"Invalid path: {err}\"" msgstr "" -#: src/bare-metal/aps/mmio.md:11 -msgid "" -"Usually if you write and then read, e.g. via a mutable reference, the " -"compiler may assume that the value read is the same as the value just " -"written, and not bother actually reading memory." +#: src/unsafe-rust/solution.md:75 +msgid "// SAFETY: path.as_ptr() cannot be NULL.\n" msgstr "" -#: src/bare-metal/aps/mmio.md:13 -msgid "" -"Some existing crates for volatile access to hardware do hold references, but " -"this is unsound. Whenever a reference exist, the compiler may choose to " -"dereference it." +#: src/unsafe-rust/solution.md:78 +msgid "\"Could not open {:?}\"" msgstr "" -#: src/bare-metal/aps/mmio.md:15 +#: src/unsafe-rust/solution.md:88 msgid "" -"Use the `addr_of!` macro to get struct field pointers from a pointer to the " -"struct." +"// Keep calling readdir until we get a NULL pointer back.\n" +" // SAFETY: self.dir is never NULL.\n" msgstr "" -#: src/bare-metal/aps/uart.md:1 -msgid "Let's write a UART driver" +#: src/unsafe-rust/solution.md:92 +msgid "// We have reached the end of the directory.\n" msgstr "" -#: src/bare-metal/aps/uart.md:3 +#: src/unsafe-rust/solution.md:95 msgid "" -"The QEMU 'virt' machine has a [PL011](https://developer.arm.com/" -"documentation/ddi0183/g) UART, so let's write a driver for that." +"// SAFETY: dirent is not NULL and dirent.d_name is NUL\n" +" // terminated.\n" msgstr "" -#: src/bare-metal/aps/uart.md:5 -msgid "" -"```rust,editable\n" -"const FLAG_REGISTER_OFFSET: usize = 0x18;\n" -"const FR_BUSY: u8 = 1 << 3;\n" -"const FR_TXFF: u8 = 1 << 5;\n" -"\n" -"/// Minimal driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" base_address: *mut u8,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the 8 MMIO control registers of " -"a\n" -" /// PL011 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u8) -> Self {\n" -" Self { base_address }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register() & FR_TXFF != 0 {}\n" -"\n" -" // Safe because we know that the base address points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" self.base_address.write_volatile(byte);\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register() & FR_BUSY != 0 {}\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> u8 {\n" -" // Safe because we know that the base address points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { self.base_address.add(FLAG_REGISTER_OFFSET)." -"read_volatile() }\n" -" }\n" -"}\n" -"```" +#: src/unsafe-rust/solution.md:107 +msgid "// SAFETY: self.dir is not NULL.\n" msgstr "" -#: src/bare-metal/aps/uart.md:55 -msgid "" -"Note that `Uart::new` is unsafe while the other methods are safe. This is " -"because as long as the caller of `Uart::new` guarantees that its safety " -"requirements are met (i.e. that there is only ever one instance of the " -"driver for a given UART, and nothing else aliasing its address space), then " -"it is always safe to call `write_byte` later because we can assume the " -"necessary preconditions." +#: src/unsafe-rust/solution.md:109 +msgid "\"Could not close {:?}\"" msgstr "" -#: src/bare-metal/aps/uart.md:60 -msgid "" -"We could have done it the other way around (making `new` safe but " -"`write_byte` unsafe), but that would be much less convenient to use as every " -"place that calls `write_byte` would need to reason about the safety" +#: src/unsafe-rust/solution.md:128 +msgid "\"no-such-directory\"" msgstr "" -#: src/bare-metal/aps/uart.md:63 -msgid "" -"This is a common pattern for writing safe wrappers of unsafe code: moving " -"the burden of proof for soundness from a large number of places to a smaller " -"number of places." +#: src/unsafe-rust/solution.md:136 src/unsafe-rust/solution.md:151 +msgid "\"Non UTF-8 character in path\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:1 -msgid "More traits" +#: src/unsafe-rust/solution.md:140 src/unsafe-rust/solution.md:155 +msgid "\"..\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:3 -msgid "" -"We derived the `Debug` trait. It would be useful to implement a few more " -"traits too." +#: src/unsafe-rust/solution.md:147 src/unsafe-rust/solution.md:155 +msgid "\"foo.txt\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use core::fmt::{self, Write};\n" -"\n" -"impl Write for Uart {\n" -" fn write_str(&mut self, s: &str) -> fmt::Result {\n" -" for c in s.as_bytes() {\n" -" self.write_byte(*c);\n" -" }\n" -" Ok(())\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Uart {}\n" -"```" +#: src/unsafe-rust/solution.md:147 +msgid "\"The Foo Diaries\\n\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:24 -msgid "" -"Implementing `Write` lets us use the `write!` and `writeln!` macros with our " -"`Uart` type." +#: src/unsafe-rust/solution.md:148 src/unsafe-rust/solution.md:155 +msgid "\"bar.png\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:25 -msgid "" -"Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" -"examples`." +#: src/unsafe-rust/solution.md:148 +msgid "\"\\n\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:1 -msgid "A better UART driver" +#: src/unsafe-rust/solution.md:149 src/unsafe-rust/solution.md:155 +msgid "\"crab.rs\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:3 -msgid "" -"The PL011 actually has [a bunch more registers](https://developer.arm.com/" -"documentation/ddi0183/g/programmers-model/summary-of-registers), and adding " -"offsets to construct pointers to access them is error-prone and hard to " -"read. Plus, some of them are bit fields which would be nice to access in a " -"structured way." +#: src/unsafe-rust/solution.md:149 +msgid "\"//! Crab\\n\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:7 -msgid "Offset" -msgstr "" +#: src/android.md:1 +msgid "Welcome to Rust in Android" +msgstr "欢迎来到Android 中的Rust" -#: src/bare-metal/aps/better-uart.md:7 -msgid "Register name" +#: src/android.md:3 +#, fuzzy +msgid "" +"Rust is supported for system software on Android. This means that you can " +"write new services, libraries, drivers or even firmware in Rust (or improve " +"existing code as needed)." msgstr "" +"Rust 支持Android 的原生平台开发。这意味着您可以在Rust 中编写新的操作系统服" +"务，以及扩展现有服务。" -#: src/bare-metal/aps/better-uart.md:7 -msgid "Width" +#: src/android.md:7 +msgid "" +"We will attempt to call Rust from one of your own projects today. So try to " +"find a little corner of your code base where we can move some lines of code " +"to Rust. The fewer dependencies and \"exotic\" types the better. Something " +"that parses some raw bytes would be ideal." msgstr "" +"今天我们会尝试在你自己的项目中调用Rust。 所以试着在你的代码中找一小段来改成" +"Rust。 代码中越少依赖(dependencies)，越少“独特”的类型，越好。比如 一段解析原" +"始字符的代码就很理想。" -#: src/bare-metal/aps/better-uart.md:9 -msgid "0x00" +#: src/android.md:14 +msgid "" +"The speaker may mention any of the following given the increased use of Rust " +"in Android:" msgstr "" -#: src/bare-metal/aps/better-uart.md:9 -msgid "DR" +#: src/android.md:17 +msgid "" +"Service example: [DNS over HTTP](https://security.googleblog.com/2022/07/dns-" +"over-http3-in-android.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:9 -msgid "12" +#: src/android.md:20 +msgid "" +"Libraries: [Rutabaga Virtual Graphics Interface](https://crosvm.dev/book/" +"appendix/rutabaga_gfx.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "0x04" +#: src/android.md:23 +msgid "" +"Kernel Drivers: [Binder](https://lore.kernel.org/rust-for-linux/20231101-" +"rust-binder-v1-0-08ba9197f637@google.com/)" msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "RSR" +#: src/android.md:26 +msgid "" +"Firmware: [pKVM firmware](https://security.googleblog.com/2023/10/bare-metal-" +"rust-in-android.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "4" +#: src/android/setup.md:3 +#, fuzzy +msgid "" +"We will be using a Cuttlefish Android Virtual Device to test our code. Make " +"sure you have access to one or create a new one with:" msgstr "" +"我们将会使用Android 虚拟设备（Android Virtual Device）来测试我们的代码。 确保" +"你有权限访问一个，或者用以下命令创建一个新的：" -#: src/bare-metal/aps/better-uart.md:11 -msgid "0x18" +#: src/android/setup.md:12 +msgid "" +"Please see the [Android Developer Codelab](https://source.android.com/docs/" +"setup/start) for details." msgstr "" +"更多细节请参考 [Android Developer Codelab](https://source.android.com/docs/" +"setup/start)." -#: src/bare-metal/aps/better-uart.md:11 -msgid "FR" +#: src/android/setup.md:20 +msgid "" +"Cuttlefish is a reference Android device designed to work on generic Linux " +"desktops. MacOS support is also planned." msgstr "" -#: src/bare-metal/aps/better-uart.md:11 -msgid "9" +#: src/android/setup.md:23 +msgid "" +"The Cuttlefish system image maintains high fidelity to real devices, and is " +"the ideal emulator to run many Rust use cases." msgstr "" -#: src/bare-metal/aps/better-uart.md:12 -msgid "0x20" -msgstr "" +#: src/android/build-rules.md:3 +msgid "The Android build system (Soong) supports Rust via a number of modules:" +msgstr "Android 构建系统（Soong）通过一系列模块来支持Rust：" -#: src/bare-metal/aps/better-uart.md:12 -msgid "ILPR" +#: src/android/build-rules.md:5 +#, fuzzy +msgid "Module Type" msgstr "" +"\\| 模块类型 | 描" +"述 " +"| \\|—————————|——————————————————————————————————————————————————| \\| " +"`rust_binary` | Rust 二进制文" +"件。 " +"| \\| `rust_library` | 生成Rust 库，并且提供 `rlib` 和 `dylib` 变" +"体。 | \\| `rust_ffi` | 生成可由 cc 模块使用的 " +"Rust C 库，并提供静态和共享变体。 | \\| `rust_proc_macro` | 生成 proc-" +"macro Rust 库。 这些宏与编译器插件类似。 | \\| " +"`rust_test` | 生成使用标准 Rust 自动化测试框架的 Rust 测试二进制文" +"件。 | \\| `rust_fuzz` | 生成使用 " +"libfuzzer 的 Rust 模糊测试二进制文" +"件。 | \\| `rust_protobuf` | 生成源" +"代码，并生成为特定 protobuf 提供接口的 Rust 库。| \\| `rust_bindgen` | 生" +"成源代码，并生成包含与 C 库的 Rust 绑定的 Rust 库。｜" -#: src/bare-metal/aps/better-uart.md:12 src/bare-metal/aps/better-uart.md:15 -msgid "8" -msgstr "" +#: src/android/build-rules.md:5 +msgid "Description" +msgstr "描述" -#: src/bare-metal/aps/better-uart.md:13 -msgid "0x24" -msgstr "" +#: src/android/build-rules.md:7 +msgid "`rust_binary`" +msgstr "`rust_binary`" -#: src/bare-metal/aps/better-uart.md:13 -msgid "IBRD" -msgstr "" +#: src/android/build-rules.md:7 +msgid "Produces a Rust binary." +msgstr "生成一个Rust二进制文件。" -#: src/bare-metal/aps/better-uart.md:13 src/bare-metal/aps/better-uart.md:16 -msgid "16" -msgstr "" +#: src/android/build-rules.md:8 +msgid "`rust_library`" +msgstr "`rust_library`" -#: src/bare-metal/aps/better-uart.md:14 -msgid "0x28" -msgstr "" +#: src/android/build-rules.md:8 +msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." +msgstr "生成一个 Rust 库，并提供 `rlib` 和 `dylib` 两种变体。" -#: src/bare-metal/aps/better-uart.md:14 -msgid "FBRD" -msgstr "" +#: src/android/build-rules.md:9 +msgid "`rust_ffi`" +msgstr "`rust_ffi`" -#: src/bare-metal/aps/better-uart.md:14 src/bare-metal/aps/better-uart.md:17 -msgid "6" -msgstr "" +#: src/android/build-rules.md:9 +msgid "" +"Produces a Rust C library usable by `cc` modules, and provides both static " +"and shared variants." +msgstr "生成一个可由 `cc` 模块使用的 Rust C 库，并提供静态和共享两种变体。" -#: src/bare-metal/aps/better-uart.md:15 -msgid "0x2c" -msgstr "" +#: src/android/build-rules.md:10 +msgid "`rust_proc_macro`" +msgstr "`rust_proc_macro`" -#: src/bare-metal/aps/better-uart.md:15 -msgid "LCR_H" +#: src/android/build-rules.md:10 +msgid "" +"Produces a `proc-macro` Rust library. These are analogous to compiler " +"plugins." msgstr "" -#: src/bare-metal/aps/better-uart.md:16 -msgid "0x30" -msgstr "" +#: src/android/build-rules.md:11 +msgid "`rust_test`" +msgstr "`rust_test`" -#: src/bare-metal/aps/better-uart.md:16 -msgid "CR" -msgstr "" +#: src/android/build-rules.md:11 +msgid "Produces a Rust test binary that uses the standard Rust test harness." +msgstr "生成使用标准 Rust 测试框架的 Rust 测试二进制文件。" -#: src/bare-metal/aps/better-uart.md:17 -msgid "0x34" -msgstr "" +#: src/android/build-rules.md:12 +msgid "`rust_fuzz`" +msgstr "`rust_fuzz`" -#: src/bare-metal/aps/better-uart.md:17 -msgid "IFLS" +#: src/android/build-rules.md:12 +msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." msgstr "" -#: src/bare-metal/aps/better-uart.md:18 -msgid "0x38" -msgstr "" +#: src/android/build-rules.md:13 +msgid "`rust_protobuf`" +msgstr "`rust_protobuf`" -#: src/bare-metal/aps/better-uart.md:18 -msgid "IMSC" -msgstr "" +#: src/android/build-rules.md:13 +msgid "" +"Generates source and produces a Rust library that provides an interface for " +"a particular protobuf." +msgstr "生成源代码并生成为特定 protobuf 提供接口的 Rust 库。" -#: src/bare-metal/aps/better-uart.md:18 src/bare-metal/aps/better-uart.md:19 -#: src/bare-metal/aps/better-uart.md:20 src/bare-metal/aps/better-uart.md:21 -msgid "11" +#: src/android/build-rules.md:14 +msgid "`rust_bindgen`" msgstr "" -#: src/bare-metal/aps/better-uart.md:19 -msgid "0x3c" +#: src/android/build-rules.md:14 +msgid "" +"Generates source and produces a Rust library containing Rust bindings to C " +"libraries." +msgstr "生成源代码并生成包含 Rust 绑定到 C 库的 Rust 库。" + +#: src/android/build-rules.md:16 +msgid "We will look at `rust_binary` and `rust_library` next." +msgstr "下面我们来看看 `rust_binary` 和 `rust_library`。" + +#: src/android/build-rules.md:20 +msgid "Additional items speaker may mention:" msgstr "" -#: src/bare-metal/aps/better-uart.md:19 -msgid "RIS" +#: src/android/build-rules.md:22 +msgid "" +"Cargo is not optimized for multi-language repos, and also downloads packages " +"from the internet." msgstr "" -#: src/bare-metal/aps/better-uart.md:20 -msgid "0x40" +#: src/android/build-rules.md:25 +msgid "" +"For compliance and performance, Android must have crates in-tree. It must " +"also interop with C/C++/Java code. Soong fills that gap." msgstr "" -#: src/bare-metal/aps/better-uart.md:20 -msgid "MIS" +#: src/android/build-rules.md:28 +msgid "" +"Soong has many similarities to Bazel, which is the open-source variant of " +"Blaze (used in google3)." msgstr "" -#: src/bare-metal/aps/better-uart.md:21 -msgid "0x44" +#: src/android/build-rules.md:31 +msgid "" +"There is a plan to transition [Android](https://source.android.com/docs/" +"setup/build/bazel/introduction), [ChromeOS](https://chromium.googlesource." +"com/chromiumos/bazel/), and [Fuchsia](https://source.android.com/docs/setup/" +"build/bazel/introduction) to Bazel." msgstr "" -#: src/bare-metal/aps/better-uart.md:21 -msgid "ICR" +#: src/android/build-rules.md:37 +msgid "Learning Bazel-like build rules is useful for all Rust OS developers." msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "0x48" +#: src/android/build-rules.md:39 +msgid "Fun fact: Data from Star Trek is a Soong-type Android." msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "DMACR" +#: src/android/build-rules/binary.md:1 +msgid "Rust Binaries" +msgstr "Rust 二进制文件" + +#: src/android/build-rules/binary.md:3 +msgid "" +"Let us start with a simple application. At the root of an AOSP checkout, " +"create the following files:" +msgstr "让我们从一个简单的应用程序开始。在 AOSP 签出的根目录下，创建以下文件：" + +#: src/android/build-rules/binary.md:6 src/android/build-rules/library.md:13 +msgid "_hello_rust/Android.bp_:" +msgstr "_hello_rust/Android.bp_:" + +#: src/android/build-rules/binary.md:10 src/android/build-rules/binary.md:11 +msgid "\"hello_rust\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "3" +#: src/android/build-rules/binary.md:12 src/android/build-rules/library.md:19 +#: src/android/logging.md:12 +#, fuzzy +msgid "\"src/main.rs\"" +msgstr "_hello_rust/src/main.rs_:" + +#: src/android/build-rules/binary.md:16 src/android/build-rules/library.md:34 +msgid "_hello_rust/src/main.rs_:" +msgstr "_hello_rust/src/main.rs_:" + +#: src/android/build-rules/binary.md:19 src/android/build-rules/library.md:37 +msgid "//! Rust demo.\n" msgstr "" -#: src/bare-metal/aps/better-uart.md:26 -msgid "There are also some ID registers which have been omitted for brevity." +#: src/android/build-rules/binary.md:20 src/android/build-rules/library.md:41 +msgid "/// Prints a greeting to standard output.\n" msgstr "" -#: src/bare-metal/aps/better-uart/bitflags.md:3 -msgid "" -"The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " -"working with bitflags." +#: src/android/build-rules/binary.md:23 src/exercises/chromium/build-rules.md:9 +msgid "\"Hello from Rust!\"" msgstr "" -#: src/bare-metal/aps/better-uart/bitflags.md:5 +#: src/android/build-rules/binary.md:27 +msgid "You can now build, push, and run the binary:" +msgstr "你现在可以构建、推送和运行二进制文件：" + +#: src/android/build-rules/binary.md:29 +#, fuzzy msgid "" -"```rust,editable,compile_fail\n" -"use bitflags::bitflags;\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART flag register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct Flags: u16 {\n" -" /// Clear to send.\n" -" const CTS = 1 << 0;\n" -" /// Data set ready.\n" -" const DSR = 1 << 1;\n" -" /// Data carrier detect.\n" -" const DCD = 1 << 2;\n" -" /// UART busy transmitting data.\n" -" const BUSY = 1 << 3;\n" -" /// Receive FIFO is empty.\n" -" const RXFE = 1 << 4;\n" -" /// Transmit FIFO is full.\n" -" const TXFF = 1 << 5;\n" -" /// Receive FIFO is full.\n" -" const RXFF = 1 << 6;\n" -" /// Transmit FIFO is empty.\n" -" const TXFE = 1 << 7;\n" -" /// Ring indicator.\n" -" const RI = 1 << 8;\n" -" }\n" -"}\n" +"```shell\n" +"m hello_rust\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust\" /data/local/tmp\n" +"adb shell /data/local/tmp/hello_rust\n" "```" msgstr "" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/analyze_numbers\n" +"```" + +#: src/android/build-rules/library.md:1 +msgid "Rust Libraries" +msgstr "Rust 库" + +#: src/android/build-rules/library.md:3 +msgid "You use `rust_library` to create a new Rust library for Android." +msgstr "您可以使用 `rust_library` 为 Android 创建一个新的 Rust 库。" -#: src/bare-metal/aps/better-uart/bitflags.md:37 +#: src/android/build-rules/library.md:5 +msgid "Here we declare a dependency on two libraries:" +msgstr "在这里，我们声明了对两个库的依赖：" + +#: src/android/build-rules/library.md:7 +msgid "`libgreeting`, which we define below," +msgstr "`libgreeting`, 我们在下面进行了定义，" + +#: src/android/build-rules/library.md:8 msgid "" -"The `bitflags!` macro creates a newtype something like `Flags(u16)`, along " -"with a bunch of method implementations to get and set flags." +"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" +"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" +"crates/)." msgstr "" +"`libtextwrap`, 一个已经在 [`external/rust/crates/`](https://cs.android.com/" +"android/platform/superproject/+/master:external/rust/crates/) 中提供的 " +"crate。" -#: src/bare-metal/aps/better-uart/registers.md:1 -msgid "Multiple registers" +#: src/android/build-rules/library.md:17 src/android/build-rules/library.md:18 +msgid "\"hello_rust_with_dep\"" msgstr "" -#: src/bare-metal/aps/better-uart/registers.md:3 -msgid "" -"We can use a struct to represent the memory layout of the UART's registers." +#: src/android/build-rules/library.md:21 src/android/build-rules/library.md:28 +msgid "\"libgreetings\"" msgstr "" -#: src/bare-metal/aps/better-uart/registers.md:41 -msgid "" -"[`#[repr(C)]`](https://doc.rust-lang.org/reference/type-layout.html#the-c-" -"representation) tells the compiler to lay the struct fields out in order, " -"following the same rules as C. This is necessary for our struct to have a " -"predictable layout, as default Rust representation allows the compiler to " -"(among other things) reorder fields however it sees fit." +#: src/android/build-rules/library.md:22 +msgid "\"libtextwrap\"" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:3 -msgid "Now let's use the new `Registers` struct in our driver." +#: src/android/build-rules/library.md:24 +msgid "// Need this to avoid dynamic link error.\n" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"/// Driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the 8 MMIO control registers of " -"a\n" -" /// PL011 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register().contains(Flags::TXFF) {}\n" -"\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" addr_of_mut!((*self.registers).dr).write_volatile(byte.into());\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register().contains(Flags::BUSY) {}\n" -" }\n" -"\n" -" /// Reads and returns a pending byte, or `None` if nothing has been " -"received.\n" -" pub fn read_byte(&self) -> Option {\n" -" if self.read_flag_register().contains(Flags::RXFE) {\n" -" None\n" -" } else {\n" -" let data = unsafe { addr_of!((*self.registers).dr)." -"read_volatile() };\n" -" // TODO: Check for error conditions in bits 8-11.\n" -" Some(data as u8)\n" -" }\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> Flags {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).fr).read_volatile() }\n" -" }\n" -"}\n" -"```" +#: src/android/build-rules/library.md:29 +msgid "\"greetings\"" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:64 -msgid "" -"Note the use of `addr_of!` / `addr_of_mut!` to get pointers to individual " -"fields without creating an intermediate reference, which would be unsound." +#: src/android/build-rules/library.md:30 src/android/aidl/implementation.md:29 +#: src/android/interoperability/java.md:39 +#, fuzzy +msgid "\"src/lib.rs\"" +msgstr "_hello_rust/src/main.rs_:" + +#: src/android/build-rules/library.md:48 +msgid "_hello_rust/src/lib.rs_:" +msgstr "_hello_rust/src/lib.rs_:" + +#: src/android/build-rules/library.md:51 +msgid "//! Greeting library.\n" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:1 -#: src/bare-metal/aps/logging/using.md:1 -msgid "Using it" +#: src/android/build-rules/library.md:52 +msgid "/// Greet `name`.\n" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:3 -msgid "" -"Let's write a small program using our driver to write to the serial console, " -"and echo incoming bytes." +#: src/android/build-rules/library.md:55 +msgid "\"Hello {name}, it is very nice to meet you!\"" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:6 +#: src/android/build-rules/library.md:59 +msgid "You build, push, and run the binary like before:" +msgstr "您可以像之前一样构建、推送和运行二进制文件：" + +#: src/android/build-rules/library.md:61 +#, fuzzy msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use core::panic::PanicInfo;\n" -"use log::error;\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let mut uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -"\n" -" writeln!(uart, \"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\").unwrap();\n" -"\n" -" loop {\n" -" if let Some(byte) = uart.read_byte() {\n" -" uart.write_byte(byte);\n" -" match byte {\n" -" b'\\r' => {\n" -" uart.write_byte(b'\\n');\n" -" }\n" -" b'q' => break,\n" -" _ => {}\n" -" }\n" -" }\n" -" }\n" -"\n" -" writeln!(uart, \"Bye!\").unwrap();\n" -" system_off::().unwrap();\n" -"}\n" +"```shell\n" +"m hello_rust_with_dep\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep\" /data/local/" +"tmp\n" +"adb shell /data/local/tmp/hello_rust_with_dep\n" "```" msgstr "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" -#: src/bare-metal/aps/better-uart/using.md:51 +#: src/android/aidl.md:3 msgid "" -"As in the [inline assembly](../inline-assembly.md) example, this `main` " -"function is called from our entry point code in `entry.S`. See the speaker " -"notes there for details." +"The [Android Interface Definition Language (AIDL)](https://developer.android." +"com/guide/components/aidl) is supported in Rust:" msgstr "" +"Rust 支持 [Android 接口定义语言 (AIDL)](https://developer.android.com/guide/" +"components/aidl)：" -#: src/bare-metal/aps/better-uart/using.md:53 -msgid "" -"Run the example in QEMU with `make qemu` under `src/bare-metal/aps/examples`." -msgstr "" +#: src/android/aidl.md:8 +msgid "Rust code can call existing AIDL servers," +msgstr "Rust 代码可以调用现有的 AIDL 服务器，" -#: src/bare-metal/aps/logging.md:3 -msgid "" -"It would be nice to be able to use the logging macros from the [`log`]" -"(https://crates.io/crates/log) crate. We can do this by implementing the " -"`Log` trait." -msgstr "" +#: src/android/aidl.md:9 +msgid "You can create new AIDL servers in Rust." +msgstr "您可以在 Rust 中创建新的 AIDL 服务器。" + +#: src/android/aidl/interface.md:1 +msgid "AIDL Interfaces" +msgstr "AIDL 接口" -#: src/bare-metal/aps/logging.md:6 +#: src/android/aidl/interface.md:3 +msgid "You declare the API of your service using an AIDL interface:" +msgstr "您可以使用 AIDL 接口声明您的服务的 API：" + +#: src/android/aidl/interface.md:5 msgid "" -"```rust,editable,compile_fail\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use log::{LevelFilter, Log, Metadata, Record, SetLoggerError};\n" -"use spin::mutex::SpinMutex;\n" -"\n" -"static LOGGER: Logger = Logger {\n" -" uart: SpinMutex::new(None),\n" -"};\n" -"\n" -"struct Logger {\n" -" uart: SpinMutex>,\n" -"}\n" -"\n" -"impl Log for Logger {\n" -" fn enabled(&self, _metadata: &Metadata) -> bool {\n" -" true\n" -" }\n" -"\n" -" fn log(&self, record: &Record) {\n" -" writeln!(\n" -" self.uart.lock().as_mut().unwrap(),\n" -" \"[{}] {}\",\n" -" record.level(),\n" -" record.args()\n" -" )\n" -" .unwrap();\n" -" }\n" -"\n" -" fn flush(&self) {}\n" -"}\n" -"\n" -"/// Initialises UART logger.\n" -"pub fn init(uart: Uart, max_level: LevelFilter) -> Result<(), " -"SetLoggerError> {\n" -" LOGGER.uart.lock().replace(uart);\n" -"\n" -" log::set_logger(&LOGGER)?;\n" -" log::set_max_level(max_level);\n" -" Ok(())\n" -"}\n" -"```" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" msgstr "" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" -#: src/bare-metal/aps/logging.md:50 -msgid "" -"The unwrap in `log` is safe because we initialise `LOGGER` before calling " -"`set_logger`." +#: src/android/aidl/interface.md:9 src/android/aidl/changing.md:8 +msgid "/** Birthday service interface. */" msgstr "" -#: src/bare-metal/aps/logging/using.md:3 -msgid "We need to initialise the logger before we use it." +#: src/android/aidl/interface.md:12 src/android/aidl/changing.md:11 +msgid "/** Generate a Happy Birthday message. */" msgstr "" -#: src/bare-metal/aps/logging/using.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\");\n" -"\n" -" assert_eq!(x1, 42);\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" -"```" -msgstr "" +#: src/android/aidl/interface.md:17 +msgid "_birthday_service/aidl/Android.bp_:" +msgstr "_birthday_service/aidl/Android.bp_:" -#: src/bare-metal/aps/logging/using.md:46 -msgid "Note that our panic handler can now log details of panics." +#: src/android/aidl/interface.md:21 +msgid "\"com.example.birthdayservice\"" msgstr "" -#: src/bare-metal/aps/logging/using.md:47 -msgid "" -"Run the example in QEMU with `make qemu_logger` under `src/bare-metal/aps/" -"examples`." +#: src/android/aidl/interface.md:22 +#, fuzzy +msgid "\"com/example/birthdayservice/*.aidl\"" msgstr "" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" -#: src/bare-metal/aps/exceptions.md:3 -msgid "" -"AArch64 defines an exception vector table with 16 entries, for 4 types of " -"exceptions (synchronous, IRQ, FIQ, SError) from 4 states (current EL with " -"SP0, current EL with SPx, lower EL using AArch64, lower EL using AArch32). " -"We implement this in assembly to save volatile registers to the stack before " -"calling into Rust code:" +#: src/android/aidl/interface.md:25 +msgid "// Rust is not enabled by default\n" msgstr "" -#: src/bare-metal/aps/exceptions.md:8 +#: src/android/aidl/interface.md:32 msgid "" -"```rust,editable,compile_fail\n" -"use log::error;\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_exception_current(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_exception_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_current(_elr: u64, _spsr: u64) {\n" -" error!(\"irq_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_current(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_current(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"irq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"```" +"Add `vendor_available: true` if your AIDL file is used by a binary in the " +"vendor partition." msgstr "" +"如果供应商分区中的二进制文件使用了您的 AIDL 文件，请添加 `vendor_available: " +"true`。" -#: src/bare-metal/aps/exceptions.md:64 -msgid "EL is exception level; all our examples this afternoon run in EL1." -msgstr "" +#: src/android/aidl/implementation.md:1 +msgid "Service Implementation" +msgstr "服务实现" -#: src/bare-metal/aps/exceptions.md:65 -msgid "" -"For simplicity we aren't distinguishing between SP0 and SPx for the current " -"EL exceptions, or between AArch32 and AArch64 for the lower EL exceptions." +#: src/android/aidl/implementation.md:3 +msgid "We can now implement the AIDL service:" +msgstr "我们现在可以实现AIDL服务：" + +#: src/android/aidl/implementation.md:5 +msgid "_birthday_service/src/lib.rs_:" +msgstr "_birthday_service/src/lib.rs_:" + +#: src/android/aidl/implementation.md:8 +msgid "//! Implementation of the `IBirthdayService` AIDL interface.\n" msgstr "" -#: src/bare-metal/aps/exceptions.md:67 -msgid "" -"For this example we just log the exception and power down, as we don't " -"expect any of them to actually happen." +#: src/android/aidl/implementation.md:11 +#, fuzzy +msgid "/// The `IBirthdayService` implementation.\n" +msgstr "服务实现" + +#: src/android/aidl/implementation.md:19 +msgid "\"Happy Birthday {name}, congratulations with the {years} years!\"" msgstr "" -#: src/bare-metal/aps/exceptions.md:69 -msgid "" -"We can think of exception handlers and our main execution context more or " -"less like different threads. [`Send` and `Sync`](../../concurrency/send-sync." -"md) will control what we can share between them, just like with threads. For " -"example, if we want to share some value between exception handlers and the " -"rest of the program, and it's `Send` but not `Sync`, then we'll need to wrap " -"it in something like a `Mutex` and put it in a static." +#: src/android/aidl/implementation.md:24 src/android/aidl/server.md:28 +#: src/android/aidl/client.md:36 +msgid "_birthday_service/Android.bp_:" +msgstr "_birthday_service/Android.bp_:" + +#: src/android/aidl/implementation.md:28 src/android/aidl/server.md:38 +#, fuzzy +msgid "\"libbirthdayservice\"" +msgstr "_birthday_service/src/lib.rs_:" + +#: src/android/aidl/implementation.md:30 src/android/aidl/server.md:13 +#: src/android/aidl/client.md:12 +#, fuzzy +msgid "\"birthdayservice\"" +msgstr "_birthday_service/src/lib.rs_:" + +#: src/android/aidl/implementation.md:32 src/android/aidl/server.md:36 +#: src/android/aidl/client.md:44 +msgid "\"com.example.birthdayservice-rust\"" msgstr "" -#: src/bare-metal/aps/other-projects.md:3 -msgid "[oreboot](https://github.com/oreboot/oreboot)" +#: src/android/aidl/implementation.md:33 src/android/aidl/server.md:37 +#: src/android/aidl/client.md:45 +msgid "\"libbinder_rs\"" msgstr "" -#: src/bare-metal/aps/other-projects.md:4 -msgid "\"coreboot without the C\"" +#: src/android/aidl/server.md:1 +msgid "AIDL Server" +msgstr "AIDL 服务器" + +#: src/android/aidl/server.md:3 +msgid "Finally, we can create a server which exposes the service:" +msgstr "最后，我们可以创建一个暴露服务的服务器：" + +#: src/android/aidl/server.md:5 +msgid "_birthday_service/src/server.rs_:" +msgstr "_birthday_service/src/server.rs_:" + +#: src/android/aidl/server.md:8 src/android/aidl/client.md:8 +msgid "//! Birthday service.\n" msgstr "" -#: src/bare-metal/aps/other-projects.md:5 -msgid "Supports x86, aarch64 and RISC-V." +#: src/android/aidl/server.md:14 +msgid "/// Entry point for birthday service.\n" msgstr "" -#: src/bare-metal/aps/other-projects.md:6 -msgid "Relies on LinuxBoot rather than having many drivers itself." +#: src/android/aidl/server.md:23 +msgid "\"Failed to register service\"" msgstr "" -#: src/bare-metal/aps/other-projects.md:7 -msgid "" -"[Rust RaspberryPi OS tutorial](https://github.com/rust-embedded/rust-" -"raspberrypi-OS-tutorials)" +#: src/android/aidl/server.md:32 src/android/aidl/server.md:33 +#, fuzzy +msgid "\"birthday_server\"" +msgstr "_birthday_service/src/lib.rs_:" + +#: src/android/aidl/server.md:34 +#, fuzzy +msgid "\"src/server.rs\"" +msgstr "`src/bin/server.rs`:" + +#: src/android/aidl/server.md:40 src/android/aidl/client.md:47 +msgid "// To avoid dynamic link error.\n" msgstr "" -#: src/bare-metal/aps/other-projects.md:8 +#: src/android/aidl/deploy.md:3 +msgid "We can now build, push, and start the service:" +msgstr "我们现在可以构建、推送和启动服务：" + +#: src/android/aidl/deploy.md:5 +#, fuzzy msgid "" -"Initialisation, UART driver, simple bootloader, JTAG, exception levels, " -"exception handling, page tables" +"```shell\n" +"m birthday_server\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server\" /data/local/" +"tmp\n" +"adb root\n" +"adb shell /data/local/tmp/birthday_server\n" +"```" msgstr "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" -#: src/bare-metal/aps/other-projects.md:10 -msgid "" -"Some dodginess around cache maintenance and initialisation in Rust, not " -"necessarily a good example to copy for production code." +#: src/android/aidl/deploy.md:12 +msgid "In another terminal, check that the service runs:" +msgstr "在另一个终端中，检查该服务是否正在运行：" + +#: src/android/aidl/deploy.md:22 +msgid "You can also call the service with `service call`:" +msgstr "您还可以使用 `service call` 命令调用该服务：" + +#: src/android/aidl/client.md:1 +msgid "AIDL Client" +msgstr "AIDL 客户端" + +#: src/android/aidl/client.md:3 +msgid "Finally, we can create a Rust client for our new service." +msgstr "最后，我们可以为我们的新服务创建一个 Rust 客户端。" + +#: src/android/aidl/client.md:5 +msgid "_birthday_service/src/client.rs_:" +msgstr "_birthday_service/src/client.rs_:" + +#: src/android/aidl/client.md:13 +msgid "/// Connect to the BirthdayService.\n" msgstr "" -#: src/bare-metal/aps/other-projects.md:12 -msgid "[`cargo-call-stack`](https://crates.io/crates/cargo-call-stack)" +#: src/android/aidl/client.md:19 +msgid "/// Call the birthday service.\n" msgstr "" -#: src/bare-metal/aps/other-projects.md:13 -msgid "Static analysis to determine maximum stack usage." +#: src/android/aidl/client.md:29 +msgid "\"Failed to connect to BirthdayService\"" msgstr "" -#: src/bare-metal/aps/other-projects.md:17 -msgid "" -"The RaspberryPi OS tutorial runs Rust code before the MMU and caches are " -"enabled. This will read and write memory (e.g. the stack). However:" +#: src/android/aidl/client.md:31 +msgid "\"{msg}\"" msgstr "" -#: src/bare-metal/aps/other-projects.md:19 +#: src/android/aidl/client.md:40 src/android/aidl/client.md:41 +#, fuzzy +msgid "\"birthday_client\"" +msgstr "_birthday_service/src/client.rs_:" + +#: src/android/aidl/client.md:42 +#, fuzzy +msgid "\"src/client.rs\"" +msgstr "`src/bin/client.rs`:" + +#: src/android/aidl/client.md:51 +msgid "Notice that the client does not depend on `libbirthdayservice`." +msgstr "请注意，客户端不依赖于 `libbirthdayservice`。" + +#: src/android/aidl/client.md:53 +msgid "Build, push, and run the client on your device:" +msgstr "在您的设备上构建、推送并运行客户端：" + +#: src/android/aidl/client.md:55 +#, fuzzy msgid "" -"Without the MMU and cache, unaligned accesses will fault. It builds with " -"`aarch64-unknown-none` which sets `+strict-align` to prevent the compiler " -"generating unaligned accesses so it should be alright, but this is not " -"necessarily the case in general." +"```shell\n" +"m birthday_client\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client\" /data/local/" +"tmp\n" +"adb shell /data/local/tmp/birthday_client Charlie 60\n" +"```" msgstr "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" -#: src/bare-metal/aps/other-projects.md:22 +#: src/android/aidl/changing.md:3 msgid "" -"If it were running in a VM, this can lead to cache coherency issues. The " -"problem is that the VM is accessing memory directly with the cache disabled, " -"while the host has cacheable aliases to the same memory. Even if the host " -"doesn't explicitly access the memory, speculative accesses can lead to cache " -"fills, and then changes from one or the other will get lost. Again this is " -"alright in this particular case (running directly on the hardware with no " -"hypervisor), but isn't a good pattern in general." -msgstr "" +"Let us extend the API with more functionality: we want to let clients " +"specify a list of lines for the birthday card:" +msgstr "让我们扩展API以提供更多功能：我们希望允许客户端指定生日贺卡的行列表：" -#: src/bare-metal/useful-crates.md:3 +#: src/android/logging.md:3 msgid "" -"We'll go over a few crates which solve some common problems in bare-metal " -"programming." +"You should use the `log` crate to automatically log to `logcat` (on-device) " +"or `stdout` (on-host):" msgstr "" +"你应该使用 `log` crate 来自动记录日志到 `logcat` （设备上）或 `stdout`（主机" +"上）：" -#: src/bare-metal/useful-crates/zerocopy.md:1 -msgid "`zerocopy`" +#: src/android/logging.md:6 +msgid "_hello_rust_logs/Android.bp_:" +msgstr "_hello_rust_logs/Android.bp_:" + +#: src/android/logging.md:10 src/android/logging.md:11 +#, fuzzy +msgid "\"hello_rust_logs\"" +msgstr "_hello_rust_logs/Android.bp_:" + +#: src/android/logging.md:14 +msgid "\"liblog_rust\"" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:3 -msgid "" -"The [`zerocopy`](https://docs.rs/zerocopy/) crate (from Fuchsia) provides " -"traits and macros for safely converting between byte sequences and other " -"types." +#: src/android/logging.md:15 +msgid "\"liblogger\"" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:40 -msgid "" -"This is not suitable for MMIO (as it doesn't use volatile reads and writes), " -"but can be useful for working with structures shared with hardware e.g. by " -"DMA, or sent over some external interface." +#: src/android/logging.md:21 +msgid "_hello_rust_logs/src/main.rs_:" +msgstr "_hello_rust_logs/src/main.rs_:" + +#: src/android/logging.md:24 +msgid "//! Rust logging demo.\n" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:45 -msgid "" -"`FromBytes` can be implemented for types for which any byte pattern is " -"valid, and so can safely be converted from an untrusted sequence of bytes." +#: src/android/logging.md:27 +msgid "/// Logs a greeting.\n" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:47 -msgid "" -"Attempting to derive `FromBytes` for these types would fail, because " -"`RequestType` doesn't use all possible u32 values as discriminants, so not " -"all byte patterns are valid." +#: src/android/logging.md:32 +msgid "\"rust\"" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:49 -msgid "" -"`zerocopy::byteorder` has types for byte-order aware numeric primitives." +#: src/android/logging.md:35 +msgid "\"Starting program.\"" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:50 -msgid "" -"Run the example with `cargo run` under `src/bare-metal/useful-crates/" -"zerocopy-example/`. (It won't run in the Playground because of the crate " -"dependency.)" +#: src/android/logging.md:36 +msgid "\"Things are going fine.\"" msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:1 -msgid "`aarch64-paging`" +#: src/android/logging.md:37 +msgid "\"Something went wrong!\"" msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:3 -msgid "" -"The [`aarch64-paging`](https://crates.io/crates/aarch64-paging) crate lets " -"you create page tables according to the AArch64 Virtual Memory System " -"Architecture." -msgstr "" +#: src/android/logging.md:41 src/android/interoperability/with-c/bindgen.md:96 +#: src/android/interoperability/with-c/rust.md:72 +msgid "Build, push, and run the binary on your device:" +msgstr "在你的设备上构建，推送，并运行二进制文件 ：" -#: src/bare-metal/useful-crates/aarch64-paging.md:6 +#: src/android/logging.md:43 +#, fuzzy msgid "" -"```rust,editable,compile_fail\n" -"use aarch64_paging::{\n" -" idmap::IdMap,\n" -" paging::{Attributes, MemoryRegion},\n" -"};\n" -"\n" -"const ASID: usize = 1;\n" -"const ROOT_LEVEL: usize = 1;\n" -"\n" -"// Create a new page table with identity mapping.\n" -"let mut idmap = IdMap::new(ASID, ROOT_LEVEL);\n" -"// Map a 2 MiB region of memory as read-only.\n" -"idmap.map_range(\n" -" &MemoryRegion::new(0x80200000, 0x80400000),\n" -" Attributes::NORMAL | Attributes::NON_GLOBAL | Attributes::READ_ONLY,\n" -").unwrap();\n" -"// Set `TTBR0_EL1` to activate the page table.\n" -"idmap.activate();\n" +"```shell\n" +"m hello_rust_logs\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs\" /data/local/" +"tmp\n" +"adb shell /data/local/tmp/hello_rust_logs\n" "```" msgstr "" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/analyze_numbers\n" +"```" -#: src/bare-metal/useful-crates/aarch64-paging.md:28 +#: src/android/logging.md:49 +msgid "The logs show up in `adb logcat`:" +msgstr "日志将会在 `adb logcat` 中显示：" + +#: src/android/interoperability.md:3 msgid "" -"For now it only supports EL1, but support for other exception levels should " -"be straightforward to add." -msgstr "" +"Rust has excellent support for interoperability with other languages. This " +"means that you can:" +msgstr "Rust 对于与其他编程语言的互操作性有着出色的支持。这意味着您可以：" -#: src/bare-metal/useful-crates/aarch64-paging.md:30 +#: src/android/interoperability.md:6 +msgid "Call Rust functions from other languages." +msgstr "从其他语言调用 Rust 函数。" + +#: src/android/interoperability.md:7 +msgid "Call functions written in other languages from Rust." +msgstr "从 Rust 调用用其他语言编写的函数。" + +#: src/android/interoperability.md:9 msgid "" -"This is used in Android for the [Protected VM Firmware](https://cs.android." -"com/android/platform/superproject/+/master:packages/modules/Virtualization/" -"pvmfw/)." +"When you call functions in a foreign language we say that you're using a " +"_foreign function interface_, also known as FFI." msgstr "" +"当您从外部语言调用函数时，我们称之为使用 **外部函数接口**（*Foreign Function " +"Interface*， FFI）。" -#: src/bare-metal/useful-crates/aarch64-paging.md:31 +#: src/android/interoperability/with-c.md:1 +msgid "Interoperability with C" +msgstr "与 C 的互操作性" + +#: src/android/interoperability/with-c.md:3 msgid "" -"There's no easy way to run this example, as it needs to run on real hardware " -"or under QEMU." +"Rust has full support for linking object files with a C calling convention. " +"Similarly, you can export Rust functions and call them from C." msgstr "" +"Rust 对使用 C 调用约定链接目标文件提供了完整的支持。同样地，你可以导出 Rust " +"函数并从 C 中调用它们。" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:1 -msgid "`buddy_system_allocator`" +#: src/android/interoperability/with-c.md:6 +msgid "You can do it by hand if you want:" +msgstr "如果你愿意的话，你可以手工完成它：" + +#: src/android/interoperability/with-c.md:16 +msgid "\"{x}, {abs_x}\"" msgstr "" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:3 +#: src/android/interoperability/with-c.md:20 msgid "" -"[`buddy_system_allocator`](https://crates.io/crates/buddy_system_allocator) " -"is a third-party crate implementing a basic buddy system allocator. It can " -"be used both for [`LockedHeap`](https://docs.rs/buddy_system_allocator/0.9.0/" -"buddy_system_allocator/struct.LockedHeap.html) implementing [`GlobalAlloc`]" -"(https://doc.rust-lang.org/core/alloc/trait.GlobalAlloc.html) so you can use " -"the standard `alloc` crate (as we saw [before](../alloc.md)), or for " -"allocating other address space. For example, we might want to allocate MMIO " -"space for PCI BARs:" +"We already saw this in the [Safe FFI Wrapper exercise](../../exercises/day-3/" +"safe-ffi-wrapper.md)." msgstr "" +"我们已经在[安全 FFI 封装容器](../../exercises/day-3/safe-ffi-wrapper.md)练习" +"中看到了这个例子。" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:8 +#: src/android/interoperability/with-c.md:23 msgid "" -"```rust,editable,compile_fail\n" -"use buddy_system_allocator::FrameAllocator;\n" -"use core::alloc::Layout;\n" -"\n" -"fn main() {\n" -" let mut allocator = FrameAllocator::<32>::new();\n" -" allocator.add_frame(0x200_0000, 0x400_0000);\n" -"\n" -" let layout = Layout::from_size_align(0x100, 0x100).unwrap();\n" -" let bar = allocator\n" -" .alloc_aligned(layout)\n" -" .expect(\"Failed to allocate 0x100 byte MMIO region\");\n" -" println!(\"Allocated 0x100 byte MMIO region at {:#x}\", bar);\n" -"}\n" -"```" -msgstr "" +"This assumes full knowledge of the target platform. Not recommended for " +"production." +msgstr "这假设对目标平台拥有充分的了解，不建议用于生产环境。" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:26 -msgid "PCI BARs always have alignment equal to their size." -msgstr "" +#: src/android/interoperability/with-c.md:26 +msgid "We will look at better options next." +msgstr "接下来我们将探讨更好的选择。" + +#: src/android/interoperability/with-c/bindgen.md:1 +msgid "Using Bindgen" +msgstr "使用 Bindgen" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:27 +#: src/android/interoperability/with-c/bindgen.md:3 msgid "" -"Run the example with `cargo run` under `src/bare-metal/useful-crates/" -"allocator-example/`. (It won't run in the Playground because of the crate " -"dependency.)" +"The [bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) " +"tool can auto-generate bindings from a C header file." msgstr "" +"[bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) 工具可" +"以自动生成 C 头文件的绑定代码。" -#: src/bare-metal/useful-crates/tinyvec.md:1 -msgid "`tinyvec`" -msgstr "" +#: src/android/interoperability/with-c/bindgen.md:6 +msgid "First create a small C library:" +msgstr "首先创建一个小型的 C 语言库：" -#: src/bare-metal/useful-crates/tinyvec.md:3 -msgid "" -"Sometimes you want something which can be resized like a `Vec`, but without " -"heap allocation. [`tinyvec`](https://crates.io/crates/tinyvec) provides " -"this: a vector backed by an array or slice, which could be statically " -"allocated or on the stack, which keeps track of how many elements are used " -"and panics if you try to use more than are allocated." +#: src/android/interoperability/with-c/bindgen.md:8 +msgid "_interoperability/bindgen/libbirthday.h_:" +msgstr "interoperability/bindgen/libbirthday.h:" + +#: src/android/interoperability/with-c/bindgen.md:19 +msgid "_interoperability/bindgen/libbirthday.c_:" +msgstr "_interoperability/bindgen/libbirthday.c_:" + +#: src/android/interoperability/with-c/bindgen.md:22 +msgid "" msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:8 -msgid "" -"```rust,editable,compile_fail\n" -"use tinyvec::{array_vec, ArrayVec};\n" -"\n" -"fn main() {\n" -" let mut numbers: ArrayVec<[u32; 5]> = array_vec!(42, 66);\n" -" println!(\"{numbers:?}\");\n" -" numbers.push(7);\n" -" println!(\"{numbers:?}\");\n" -" numbers.remove(1);\n" -" println!(\"{numbers:?}\");\n" -"}\n" -"```" +#: src/android/interoperability/with-c/bindgen.md:23 +#: src/android/interoperability/with-c/bindgen.md:50 +#, fuzzy +msgid "\"libbirthday.h\"" msgstr "" +"```c\n" +"#include \"libbirthday.h\"\n" +"```" -#: src/bare-metal/useful-crates/tinyvec.md:23 -msgid "" -"`tinyvec` requires that the element type implement `Default` for " -"initialisation." +#: src/android/interoperability/with-c/bindgen.md:26 +#: src/android/interoperability/with-c/bindgen.md:29 +msgid "\"+--------------\\n\"" msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:24 -msgid "" -"The Rust Playground includes `tinyvec`, so this example will run fine inline." +#: src/android/interoperability/with-c/bindgen.md:27 +msgid "\"| Happy Birthday %s!\\n\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:1 -msgid "`spin`" +#: src/android/interoperability/with-c/bindgen.md:28 +msgid "\"| Congratulations with the %i years!\\n\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:3 -msgid "" -"`std::sync::Mutex` and the other synchronisation primitives from `std::sync` " -"are not available in `core` or `alloc`. How can we manage synchronisation or " -"interior mutability, such as for sharing state between different CPUs?" +#: src/android/interoperability/with-c/bindgen.md:33 +msgid "Add this to your `Android.bp` file:" +msgstr "将该库添加到你的 `Android.bp` 文件中：" + +#: src/android/interoperability/with-c/bindgen.md:35 +#: src/android/interoperability/with-c/bindgen.md:55 +#: src/android/interoperability/with-c/bindgen.md:69 +#: src/android/interoperability/with-c/bindgen.md:106 +msgid "_interoperability/bindgen/Android.bp_:" +msgstr "_interoperability/bindgen/Android.bp_:" + +#: src/android/interoperability/with-c/bindgen.md:39 +#: src/android/interoperability/with-c/bindgen.md:63 +msgid "\"libbirthday\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:7 -msgid "" -"The [`spin`](https://crates.io/crates/spin) crate provides spinlock-based " -"equivalents of many of these primitives." +#: src/android/interoperability/with-c/bindgen.md:40 +msgid "\"libbirthday.c\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:9 +#: src/android/interoperability/with-c/bindgen.md:44 msgid "" -"```rust,editable,compile_fail\n" -"use spin::mutex::SpinMutex;\n" -"\n" -"static counter: SpinMutex = SpinMutex::new(0);\n" -"\n" -"fn main() {\n" -" println!(\"count: {}\", counter.lock());\n" -" *counter.lock() += 2;\n" -" println!(\"count: {}\", counter.lock());\n" -"}\n" -"```" -msgstr "" +"Create a wrapper header file for the library (not strictly needed in this " +"example):" +msgstr "为该库创建一个包装头文件（在此示例中不是必需的）：" -#: src/bare-metal/useful-crates/spin.md:23 -msgid "Be careful to avoid deadlock if you take locks in interrupt handlers." +#: src/android/interoperability/with-c/bindgen.md:47 +msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" +msgstr "_interoperability/bindgen/libbirthday_wrapper.h_:" + +#: src/android/interoperability/with-c/bindgen.md:53 +msgid "You can now auto-generate the bindings:" +msgstr "您现在可以自动生成绑定代码：" + +#: src/android/interoperability/with-c/bindgen.md:59 +#: src/android/interoperability/with-c/bindgen.md:75 +msgid "\"libbirthday_bindgen\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:24 -msgid "" -"`spin` also has a ticket lock mutex implementation; equivalents of `RwLock`, " -"`Barrier` and `Once` from `std::sync`; and `Lazy` for lazy initialisation." +#: src/android/interoperability/with-c/bindgen.md:60 +msgid "\"birthday_bindgen\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:26 -msgid "" -"The [`once_cell`](https://crates.io/crates/once_cell) crate also has some " -"useful types for late initialisation with a slightly different approach to " -"`spin::once::Once`." +#: src/android/interoperability/with-c/bindgen.md:61 +msgid "\"libbirthday_wrapper.h\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:28 -msgid "" -"The Rust Playground includes `spin`, so this example will run fine inline." +#: src/android/interoperability/with-c/bindgen.md:62 +msgid "\"bindings\"" msgstr "" -#: src/bare-metal/android.md:3 -msgid "" -"To build a bare-metal Rust binary in AOSP, you need to use a " -"`rust_ffi_static` Soong rule to build your Rust code, then a `cc_binary` " -"with a linker script to produce the binary itself, and then a `raw_binary` " -"to convert the ELF to a raw binary ready to be run." +#: src/android/interoperability/with-c/bindgen.md:67 +msgid "Finally, we can use the bindings in our Rust program:" +msgstr "最后，我们可以在 Rust 程序中使用这些绑定：" + +#: src/android/interoperability/with-c/bindgen.md:73 +msgid "\"print_birthday_card\"" msgstr "" -#: src/bare-metal/android.md:7 -msgid "" -"```soong\n" -"rust_ffi_static {\n" -" name: \"libvmbase_example\",\n" -" defaults: [\"vmbase_ffi_defaults\"],\n" -" crate_name: \"vmbase_example\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"libvmbase\",\n" -" ],\n" -"}\n" -"\n" -"cc_binary {\n" -" name: \"vmbase_example\",\n" -" defaults: [\"vmbase_elf_defaults\"],\n" -" srcs: [\n" -" \"idmap.S\",\n" -" ],\n" -" static_libs: [\n" -" \"libvmbase_example\",\n" -" ],\n" -" linker_scripts: [\n" -" \"image.ld\",\n" -" \":vmbase_sections\",\n" -" ],\n" -"}\n" -"\n" -"raw_binary {\n" -" name: \"vmbase_example_bin\",\n" -" stem: \"vmbase_example.bin\",\n" -" src: \":vmbase_example\",\n" -" enabled: false,\n" -" target: {\n" -" android_arm64: {\n" -" enabled: true,\n" -" },\n" -" },\n" -"}\n" -"```" +#: src/android/interoperability/with-c/bindgen.md:74 +#, fuzzy +msgid "\"main.rs\"" +msgstr "`main.rs`:" + +#: src/android/interoperability/with-c/bindgen.md:79 +msgid "_interoperability/bindgen/main.rs_:" +msgstr "_interoperability/bindgen/main.rs_:" + +#: src/android/interoperability/with-c/bindgen.md:82 +msgid "//! Bindgen demo.\n" msgstr "" -#: src/bare-metal/android/vmbase.md:3 -msgid "" -"For VMs running under crosvm on aarch64, the [vmbase](https://android." -"googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/" -"master/vmbase/) library provides a linker script and useful defaults for the " -"build rules, along with an entry point, UART console logging and more." +#: src/android/interoperability/with-c/bindgen.md:89 +msgid "// SAFETY: `print_card` is safe to call with a valid `card` pointer.\n" msgstr "" -#: src/bare-metal/android/vmbase.md:6 +#: src/android/interoperability/with-c/bindgen.md:98 +#, fuzzy msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"use vmbase::{main, println};\n" -"\n" -"main!(main);\n" -"\n" -"pub fn main(arg0: u64, arg1: u64, arg2: u64, arg3: u64) {\n" -" println!(\"Hello world\");\n" -"}\n" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card\" /data/local/" +"tmp\n" +"adb shell /data/local/tmp/print_birthday_card\n" "```" msgstr "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" -#: src/bare-metal/android/vmbase.md:21 -msgid "" -"The `main!` macro marks your main function, to be called from the `vmbase` " -"entry point." -msgstr "" +#: src/android/interoperability/with-c/bindgen.md:104 +msgid "Finally, we can run auto-generated tests to ensure the bindings work:" +msgstr "最后，我们可以运行自动生成的测试来确保绑定代码正常工作：" -#: src/bare-metal/android/vmbase.md:22 -msgid "" -"The `vmbase` entry point handles console initialisation, and issues a " -"PSCI_SYSTEM_OFF to shutdown the VM if your main function returns." +#: src/android/interoperability/with-c/bindgen.md:110 +#: src/android/interoperability/with-c/bindgen.md:112 +msgid "\"libbirthday_bindgen_test\"" msgstr "" -#: src/exercises/bare-metal/afternoon.md:3 -msgid "We will write a driver for the PL031 real-time clock device." +#: src/android/interoperability/with-c/bindgen.md:111 +msgid "\":libbirthday_bindgen\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:1 -#: src/exercises/bare-metal/solutions-afternoon.md:3 -msgid "RTC driver" +#: src/android/interoperability/with-c/bindgen.md:113 +msgid "\"general-tests\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:3 -msgid "" -"The QEMU aarch64 virt machine has a [PL031](https://developer.arm.com/" -"documentation/ddi0224/c) real-time clock at 0x9010000. For this exercise, " -"you should write a driver for it." +#: src/android/interoperability/with-c/bindgen.md:115 +#: src/android/interoperability/with-c/bindgen.md:116 +msgid "\"none\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:6 -msgid "" -"Use it to print the current time to the serial console. You can use the " -"[`chrono`](https://crates.io/crates/chrono) crate for date/time formatting." +#: src/android/interoperability/with-c/bindgen.md:115 +msgid "// Generated file, skip linting\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:8 -msgid "" -"Use the match register and raw interrupt status to busy-wait until a given " -"time, e.g. 3 seconds in the future. (Call [`core::hint::spin_loop`](https://" -"doc.rust-lang.org/core/hint/fn.spin_loop.html) inside the loop.)" +#: src/android/interoperability/with-c/rust.md:1 +msgid "Calling Rust" +msgstr "调用 Rust" + +#: src/android/interoperability/with-c/rust.md:3 +msgid "Exporting Rust functions and types to C is easy:" +msgstr "将 Rust 函数和类型导出到 C 很简单：" + +#: src/android/interoperability/with-c/rust.md:5 +msgid "_interoperability/rust/libanalyze/analyze.rs_" +msgstr "_interoperability/rust/libanalyze/analyze.rs_" + +#: src/android/interoperability/with-c/rust.md:8 +msgid "//! Rust FFI demo.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:10 -msgid "" -"_Extension if you have time:_ Enable and handle the interrupt generated by " -"the RTC match. You can use the driver provided in the [`arm-gic`](https://" -"docs.rs/arm-gic/) crate to configure the Arm Generic Interrupt Controller." +#: src/android/interoperability/with-c/rust.md:12 +msgid "/// Analyze the numbers.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:12 -msgid "Use the RTC interrupt, which is wired to the GIC as `IntId::spi(2)`." +#: src/android/interoperability/with-c/rust.md:17 +msgid "\"x ({x}) is smallest!\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:13 -msgid "" -"Once the interrupt is enabled, you can put the core to sleep via `arm_gic::" -"wfi()`, which will cause the core to sleep until it receives an interrupt." +#: src/android/interoperability/with-c/rust.md:19 +msgid "\"y ({y}) is probably larger than x ({x})\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:16 -msgid "" -"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " -"look in the `rtc` directory for the following files." +#: src/android/interoperability/with-c/rust.md:24 +msgid "_interoperability/rust/libanalyze/analyze.h_" +msgstr "_interoperability/rust/libanalyze/analyze.h_" + +#: src/android/interoperability/with-c/rust.md:37 +msgid "_interoperability/rust/libanalyze/Android.bp_" +msgstr "_interoperability/rust/libanalyze/Android.bp_" + +#: src/android/interoperability/with-c/rust.md:41 +#: src/android/interoperability/with-c/rust.md:68 +msgid "\"libanalyze_ffi\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:42 +msgid "\"analyze_ffi\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:43 +msgid "\"analyze.rs\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:48 +msgid "We can now call this from a C binary:" +msgstr "我们现在可以从一个 C 二进制文件中调用它：" + +#: src/android/interoperability/with-c/rust.md:50 +msgid "_interoperability/rust/analyze/main.c_" +msgstr "_interoperability/rust/analyze/main.c_" + +#: src/android/interoperability/with-c/rust.md:53 +msgid "\"analyze.h\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:62 +msgid "_interoperability/rust/analyze/Android.bp_" +msgstr "_interoperability/rust/analyze/Android.bp_" + +#: src/android/interoperability/with-c/rust.md:66 +msgid "\"analyze_numbers\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:67 +msgid "\"main.c\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:23 +#: src/android/interoperability/with-c/rust.md:74 +#, fuzzy msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use arm_gic::gicv3::GicV3;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, trace, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base addresses of the GICv3.\n" -"const GICD_BASE_ADDRESS: *mut u64 = 0x800_0000 as _;\n" -"const GICR_BASE_ADDRESS: *mut u64 = 0x80A_0000 as _;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({:#x}, {:#x}, {:#x}, {:#x})\", x0, x1, x2, x3);\n" -"\n" -" // Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the " -"base\n" -" // addresses of a GICv3 distributor and redistributor respectively, and\n" -" // nothing else accesses those address ranges.\n" -" let mut gic = unsafe { GicV3::new(GICD_BASE_ADDRESS, " -"GICR_BASE_ADDRESS) };\n" -" gic.setup();\n" -"\n" -" // TODO: Create instance of RTC driver and print current time.\n" -"\n" -" // TODO: Wait for 3 seconds.\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers\" /data/local/" +"tmp\n" +"adb shell /data/local/tmp/analyze_numbers\n" "```" msgstr "" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/analyze_numbers\n" +"```" -#: src/exercises/bare-metal/rtc.md:75 +#: src/android/interoperability/with-c/rust.md:82 msgid "" -"_src/exceptions.rs_ (you should only need to change this for the 3rd part of " -"the exercise):" +"`#[no_mangle]` disables Rust's usual name mangling, so the exported symbol " +"will just be the name of the function. You can also use `#[export_name = " +"\"some_name\"]` to specify whatever name you want." msgstr "" +"`#[no_mangle]` 禁用了 Rust 通常的名称重整，因此导出的符号将仅为函数的名称。你" +"还可以使用 `#[export_name = \"some_name\"]` 来指定任意你想要的名称。" -#: src/exercises/bare-metal/rtc.md:79 +#: src/android/interoperability/cpp.md:1 +msgid "With C++" +msgstr "与 C++ 交互" + +#: src/android/interoperability/cpp.md:3 msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"use arm_gic::gicv3::GicV3;\n" -"use log::{error, info, trace};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_exception_current(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_exception_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_current(_elr: u64, _spsr: u64) {\n" -" trace!(\"irq_current\");\n" -" let intid = GicV3::get_and_acknowledge_interrupt().expect(\"No pending " -"interrupt\");\n" -" info!(\"IRQ {intid:?}\");\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_current(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_current(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"irq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"```" +"The [CXX crate](https://cxx.rs/) makes it possible to do safe " +"interoperability between Rust and C++." msgstr "" +"[CXX crate](https://cxx.rs/) 使得在 Rust 和 C++ 之间进行安全的互操作成为可" +"能。" -#: src/exercises/bare-metal/rtc.md:149 -msgid "_src/logger.rs_ (you shouldn't need to change this):" -msgstr "" +#: src/android/interoperability/cpp.md:6 +msgid "The overall approach looks like this:" +msgstr "整体的方法如下：" -#: src/exercises/bare-metal/rtc.md:153 +#: src/android/interoperability/cpp/bridge.md:3 msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"// ANCHOR: main\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use log::{LevelFilter, Log, Metadata, Record, SetLoggerError};\n" -"use spin::mutex::SpinMutex;\n" -"\n" -"static LOGGER: Logger = Logger {\n" -" uart: SpinMutex::new(None),\n" -"};\n" -"\n" -"struct Logger {\n" -" uart: SpinMutex>,\n" -"}\n" -"\n" -"impl Log for Logger {\n" -" fn enabled(&self, _metadata: &Metadata) -> bool {\n" -" true\n" -" }\n" -"\n" -" fn log(&self, record: &Record) {\n" -" writeln!(\n" -" self.uart.lock().as_mut().unwrap(),\n" -" \"[{}] {}\",\n" -" record.level(),\n" -" record.args()\n" -" )\n" -" .unwrap();\n" -" }\n" -"\n" -" fn flush(&self) {}\n" -"}\n" -"\n" -"/// Initialises UART logger.\n" -"pub fn init(uart: Uart, max_level: LevelFilter) -> Result<(), " -"SetLoggerError> {\n" -" LOGGER.uart.lock().replace(uart);\n" -"\n" -" log::set_logger(&LOGGER)?;\n" -" log::set_max_level(max_level);\n" -" Ok(())\n" -"}\n" -"```" +"CXX relies on a description of the function signatures that will be exposed " +"from each language to the other. You provide this description using extern " +"blocks in a Rust module annotated with the `#[cxx::bridge]` attribute macro." msgstr "" -#: src/exercises/bare-metal/rtc.md:210 -msgid "_src/pl011.rs_ (you shouldn't need to change this):" +#: src/android/interoperability/cpp/bridge.md:9 +msgid "\"org::blobstore\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:11 +msgid "// Shared structs with fields visible to both languages.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:17 +#: src/android/interoperability/cpp/generated-cpp.md:6 +msgid "// Rust types and signatures exposed to C++.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:18 +#: src/android/interoperability/cpp/rust-bridge.md:6 +#: src/android/interoperability/cpp/generated-cpp.md:7 +#: src/android/interoperability/cpp/rust-result.md:6 +#: src/chromium/interoperability-with-cpp/example-bindings.md:9 +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:10 +#: src/chromium/interoperability-with-cpp/error-handling-png.md:9 +#, fuzzy +msgid "\"Rust\"" +msgstr "Rustdoc" + +#: src/android/interoperability/cpp/bridge.md:24 +#: src/android/interoperability/cpp/cpp-bridge.md:6 +msgid "// C++ types and signatures exposed to Rust.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:214 +#: src/android/interoperability/cpp/bridge.md:25 +#: src/android/interoperability/cpp/cpp-bridge.md:7 +#: src/android/interoperability/cpp/cpp-exception.md:6 +#: src/chromium/interoperability-with-cpp/example-bindings.md:15 +msgid "\"C++\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:26 +#: src/android/interoperability/cpp/cpp-bridge.md:8 +msgid "\"include/blobstore.h\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:40 +msgid "The bridge is generally declared in an `ffi` module within your crate." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:41 msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"#![allow(unused)]\n" -"\n" -"use core::fmt::{self, Write};\n" -"use core::ptr::{addr_of, addr_of_mut};\n" -"\n" -"// ANCHOR: Flags\n" -"use bitflags::bitflags;\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART flag register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct Flags: u16 {\n" -" /// Clear to send.\n" -" const CTS = 1 << 0;\n" -" /// Data set ready.\n" -" const DSR = 1 << 1;\n" -" /// Data carrier detect.\n" -" const DCD = 1 << 2;\n" -" /// UART busy transmitting data.\n" -" const BUSY = 1 << 3;\n" -" /// Receive FIFO is empty.\n" -" const RXFE = 1 << 4;\n" -" /// Transmit FIFO is full.\n" -" const TXFF = 1 << 5;\n" -" /// Receive FIFO is full.\n" -" const RXFF = 1 << 6;\n" -" /// Transmit FIFO is empty.\n" -" const TXFE = 1 << 7;\n" -" /// Ring indicator.\n" -" const RI = 1 << 8;\n" -" }\n" -"}\n" -"// ANCHOR_END: Flags\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART Receive Status Register / Error Clear Register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct ReceiveStatus: u16 {\n" -" /// Framing error.\n" -" const FE = 1 << 0;\n" -" /// Parity error.\n" -" const PE = 1 << 1;\n" -" /// Break error.\n" -" const BE = 1 << 2;\n" -" /// Overrun error.\n" -" const OE = 1 << 3;\n" -" }\n" -"}\n" -"\n" -"// ANCHOR: Registers\n" -"#[repr(C, align(4))]\n" -"struct Registers {\n" -" dr: u16,\n" -" _reserved0: [u8; 2],\n" -" rsr: ReceiveStatus,\n" -" _reserved1: [u8; 19],\n" -" fr: Flags,\n" -" _reserved2: [u8; 6],\n" -" ilpr: u8,\n" -" _reserved3: [u8; 3],\n" -" ibrd: u16,\n" -" _reserved4: [u8; 2],\n" -" fbrd: u8,\n" -" _reserved5: [u8; 3],\n" -" lcr_h: u8,\n" -" _reserved6: [u8; 3],\n" -" cr: u16,\n" -" _reserved7: [u8; 3],\n" -" ifls: u8,\n" -" _reserved8: [u8; 3],\n" -" imsc: u16,\n" -" _reserved9: [u8; 2],\n" -" ris: u16,\n" -" _reserved10: [u8; 2],\n" -" mis: u16,\n" -" _reserved11: [u8; 2],\n" -" icr: u16,\n" -" _reserved12: [u8; 2],\n" -" dmacr: u8,\n" -" _reserved13: [u8; 3],\n" -"}\n" -"// ANCHOR_END: Registers\n" -"\n" -"// ANCHOR: Uart\n" -"/// Driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the MMIO control registers of " -"a\n" -" /// PL011 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register().contains(Flags::TXFF) {}\n" -"\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" addr_of_mut!((*self.registers).dr).write_volatile(byte.into());\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register().contains(Flags::BUSY) {}\n" -" }\n" -"\n" -" /// Reads and returns a pending byte, or `None` if nothing has been " -"received.\n" -" pub fn read_byte(&self) -> Option {\n" -" if self.read_flag_register().contains(Flags::RXFE) {\n" -" None\n" -" } else {\n" -" let data = unsafe { addr_of!((*self.registers).dr)." -"read_volatile() };\n" -" // TODO: Check for error conditions in bits 8-11.\n" -" Some(data as u8)\n" -" }\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> Flags {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).fr).read_volatile() }\n" -" }\n" -"}\n" -"// ANCHOR_END: Uart\n" -"\n" -"impl Write for Uart {\n" -" fn write_str(&mut self, s: &str) -> fmt::Result {\n" -" for c in s.as_bytes() {\n" -" self.write_byte(*c);\n" -" }\n" -" Ok(())\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Uart {}\n" -"```" +"From the declarations made in the bridge module, CXX will generate matching " +"Rust and C++ type/function definitions in order to expose those items to " +"both languages." msgstr "" -#: src/exercises/bare-metal/rtc.md:389 +#: src/android/interoperability/cpp/bridge.md:44 msgid "" -"```toml\n" -"[workspace]\n" -"\n" -"[package]\n" -"name = \"rtc\"\n" -"version = \"0.1.0\"\n" -"edition = \"2021\"\n" -"publish = false\n" -"\n" -"[dependencies]\n" -"arm-gic = \"0.1.0\"\n" -"bitflags = \"2.0.0\"\n" -"chrono = { version = \"0.4.24\", default-features = false }\n" -"log = \"0.4.17\"\n" -"smccc = \"0.1.1\"\n" -"spin = \"0.9.8\"\n" -"\n" -"[build-dependencies]\n" -"cc = \"1.0.73\"\n" -"```" +"To view the generated Rust code, use [cargo-expand](https://github.com/" +"dtolnay/cargo-expand) to view the expanded proc macro. For most of the " +"examples you would use `cargo expand ::ffi` to expand just the `ffi` module " +"(though this doesn't apply for Android projects)." msgstr "" -#: src/exercises/bare-metal/rtc.md:410 -msgid "_build.rs_ (you shouldn't need to change this):" +#: src/android/interoperability/cpp/bridge.md:47 +msgid "To view the generated C++ code, look in `target/cxxbridge`." msgstr "" -#: src/exercises/bare-metal/rtc.md:414 -msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"use cc::Build;\n" -"use std::env;\n" -"\n" -"fn main() {\n" -" #[cfg(target_os = \"linux\")]\n" -" env::set_var(\"CROSS_COMPILE\", \"aarch64-linux-gnu\");\n" -" #[cfg(not(target_os = \"linux\"))]\n" -" env::set_var(\"CROSS_COMPILE\", \"aarch64-none-elf\");\n" -"\n" -" Build::new()\n" -" .file(\"entry.S\")\n" -" .file(\"exceptions.S\")\n" -" .file(\"idmap.S\")\n" -" .compile(\"empty\")\n" -"}\n" -"```" +#: src/android/interoperability/cpp/rust-bridge.md:1 +msgid "Rust Bridge Declarations" msgstr "" -#: src/exercises/bare-metal/rtc.md:446 -msgid "_entry.S_ (you shouldn't need to change this):" +#: src/android/interoperability/cpp/rust-bridge.md:7 +msgid "// Opaque type\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:450 +#: src/android/interoperability/cpp/rust-bridge.md:8 +msgid "// Method on `MyType`\n" +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md:9 +#, fuzzy +msgid "// Free function\n" +msgstr "函数" + +#: src/android/interoperability/cpp/rust-bridge.md:28 +msgid "" +"Items declared in the `extern \"Rust\"` reference items that are in scope in " +"the parent module." +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md:30 +msgid "" +"The CXX code generator uses your `extern \"Rust\"` section(s) to produce a C+" +"+ header file containing the corresponding C++ declarations. The generated " +"header has the same path as the Rust source file containing the bridge, " +"except with a .rs.h file extension." +msgstr "" + +#: src/android/interoperability/cpp/generated-cpp.md:15 +msgid "Results in (roughly) the following C++:" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:1 +msgid "C++ Bridge Declarations" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:20 +msgid "Results in (roughly) the following Rust:" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:30 +msgid "\"org$blobstore$cxxbridge1$new_blobstore_client\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:39 +msgid "\"org$blobstore$cxxbridge1$BlobstoreClient$put\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:56 +msgid "" +"The programmer does not need to promise that the signatures they have typed " +"in are accurate. CXX performs static assertions that the signatures exactly " +"correspond with what is declared in C++." +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md:59 +msgid "" +"`unsafe extern` blocks allow you to declare C++ functions that are safe to " +"call from Rust." +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md:9 +msgid "// A=1, J=11, Q=12, K=13\n" +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md:23 +msgid "Only C-like (unit) enums are supported." +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md:24 +msgid "" +"A limited number of traits are supported for `#[derive()]` on shared types. " +"Corresponding functionality is also generated for the C++ code, e.g. if you " +"derive `Hash` also generates an implementation of `std::hash` for the " +"corresponding C++ type." +msgstr "" + +#: src/android/interoperability/cpp/shared-enums.md:15 +#, fuzzy +msgid "Generated Rust:" +msgstr "不安全 Rust" + +#: src/android/interoperability/cpp/shared-enums.md:33 +msgid "Generated C++:" +msgstr "" + +#: src/android/interoperability/cpp/shared-enums.md:46 +msgid "" +"On the Rust side, the code generated for shared enums is actually a struct " +"wrapping a numeric value. This is because it is not UB in C++ for an enum " +"class to hold a value different from all of the listed variants, and our " +"Rust representation needs to have the same behavior." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:13 +msgid "\"fallible1 requires depth > 0\"" +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:16 +msgid "\"Success!\"" +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:22 +msgid "" +"Rust functions that return `Result` are translated to exceptions on the C++ " +"side." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:24 +msgid "" +"The exception thrown will always be of type `rust::Error`, which primarily " +"exposes a way to get the error message string. The error message will come " +"from the error type's `Display` impl." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:27 +msgid "" +"A panic unwinding from Rust to C++ will always cause the process to " +"immediately terminate." +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md:7 +msgid "\"example/include/example.h\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md:14 +msgid "\"Error: {}\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md:22 +msgid "" +"C++ functions declared to return a `Result` will catch any thrown exception " +"on the C++ side and return it as an `Err` value to the calling Rust function." +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md:24 +msgid "" +"If an exception is thrown from an extern \"C++\" function that is not " +"declared by the CXX bridge to return `Result`, the program calls C++'s `std::" +"terminate`. The behavior is equivalent to the same exception being thrown " +"through a `noexcept` C++ function." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:3 +#, fuzzy +msgid "Rust Type" +msgstr "Rust 示例" + +#: src/android/interoperability/cpp/type-mapping.md:3 +#, fuzzy +msgid "C++ Type" +msgstr "C++ 示例" + +#: src/android/interoperability/cpp/type-mapping.md:5 +#, fuzzy +msgid "`rust::String`" +msgstr "String" + +#: src/android/interoperability/cpp/type-mapping.md:6 +msgid "`&str`" +msgstr "`&str`" + +#: src/android/interoperability/cpp/type-mapping.md:6 +#, fuzzy +msgid "`rust::Str`" +msgstr "`rust_test`" + +#: src/android/interoperability/cpp/type-mapping.md:7 +#, fuzzy +msgid "`CxxString`" +msgstr "String" + +#: src/android/interoperability/cpp/type-mapping.md:7 +#, fuzzy +msgid "`std::string`" +msgstr "String" + +#: src/android/interoperability/cpp/type-mapping.md:8 +msgid "`&[T]`/`&mut [T]`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:8 +#, fuzzy +msgid "`rust::Slice`" +msgstr "`rust_ffi`" + +#: src/android/interoperability/cpp/type-mapping.md:9 +msgid "`rust::Box`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:10 +msgid "`UniquePtr`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:10 +msgid "`std::unique_ptr`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:11 +#, fuzzy +msgid "`Vec`" +msgstr "`Vec`" + +#: src/android/interoperability/cpp/type-mapping.md:11 +#, fuzzy +msgid "`rust::Vec`" +msgstr "`mpsc::Receiver`" + +#: src/android/interoperability/cpp/type-mapping.md:12 +#, fuzzy +msgid "`CxxVector`" +msgstr "`Cell`" + +#: src/android/interoperability/cpp/type-mapping.md:12 +#, fuzzy +msgid "`std::vector`" +msgstr "`mpsc::Receiver`" + +#: src/android/interoperability/cpp/type-mapping.md:16 +msgid "" +"These types can be used in the fields of shared structs and the arguments " +"and returns of extern functions." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:18 +msgid "" +"Note that Rust's `String` does not map directly to `std::string`. There are " +"a few reasons for this:" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:20 +msgid "" +"`std::string` does not uphold the UTF-8 invariant that `String` requires." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:21 +msgid "" +"The two types have different layouts in memory and so can't be passed " +"directly between languages." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md:23 +msgid "" +"`std::string` requires move constructors that don't match Rust's move " +"semantics, so a `std::string` can't be passed by value to Rust." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:1 +#: src/android/interoperability/cpp/android-cpp-genrules.md:1 +#: src/android/interoperability/cpp/android-build-rust.md:1 +#, fuzzy +msgid "Building in Android" +msgstr "Android 中的 Rust" + +#: src/android/interoperability/cpp/android-build-cpp.md:3 +msgid "" +"Create a `cc_library_static` to build the C++ library, including the CXX " +"generated header and source file." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:8 +#: src/android/interoperability/cpp/android-build-rust.md:10 +msgid "\"libcxx_test_cpp\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:9 +msgid "\"cxx_test.cpp\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:11 +msgid "\"cxx-bridge-header\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:12 +#: src/android/interoperability/cpp/android-cpp-genrules.md:10 +msgid "\"libcxx_test_bridge_header\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:14 +#: src/android/interoperability/cpp/android-cpp-genrules.md:19 +msgid "\"libcxx_test_bridge_code\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:20 +msgid "" +"Point out that `libcxx_test_bridge_header` and `libcxx_test_bridge_code` are " +"the dependencies for the CXX-generated C++ bindings. We'll show how these " +"are setup on the next slide." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:23 +msgid "" +"Note that you also need to depend on the `cxx-bridge-header` library in " +"order to pull in common CXX definitions." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md:25 +msgid "" +"Full docs for using CXX in Android can be found in [the Android docs]" +"(https://source.android.com/docs/setup/build/rust/building-rust-modules/" +"android-rust-patterns#rust-cpp-interop-using-cxx). You may want to share " +"that link with the class so that students know where they can find these " +"instructions again in the future." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:3 +msgid "" +"Create two genrules: One to generate the CXX header, and one to generate the " +"CXX source file. These are then used as inputs to the `cc_library_static`." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:7 +msgid "" +"// Generate a C++ header containing the C++ bindings\n" +"// to the Rust exported functions in lib.rs.\n" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:11 +#: src/android/interoperability/cpp/android-cpp-genrules.md:20 +msgid "\"cxxbridge\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:12 +msgid "\"$(location cxxbridge) $(in) --header > $(out)\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:13 +#: src/android/interoperability/cpp/android-cpp-genrules.md:22 +#: src/android/interoperability/cpp/android-build-rust.md:8 +msgid "\"lib.rs\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:14 +msgid "\"lib.rs.h\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:16 +msgid "// Generate the C++ code that Rust calls into.\n" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:21 +msgid "\"$(location cxxbridge) $(in) > $(out)\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:23 +msgid "\"lib.rs.cc\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:29 +msgid "" +"The `cxxbridge` tool is a standalone tool that generates the C++ side of the " +"bridge module. It is included in Android and available as a Soong tool." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:31 +msgid "" +"By convention, if your Rust source file is `lib.rs` your header file will be " +"named `lib.rs.h` and your source file will be named `lib.rs.cc`. This naming " +"convention isn't enforced, though." +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md:3 +msgid "" +"Create a `rust_binary` that depends on `libcxx` and your `cc_library_static`." +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md:7 +msgid "\"cxx_test\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md:9 +msgid "\"libcxx\"" +msgstr "" + +#: src/android/interoperability/java.md:1 +msgid "Interoperability with Java" +msgstr "与 Java 的互操作性" + +#: src/android/interoperability/java.md:3 +msgid "" +"Java can load shared objects via [Java Native Interface (JNI)](https://en." +"wikipedia.org/wiki/Java_Native_Interface). The [`jni` crate](https://docs.rs/" +"jni/) allows you to create a compatible library." +msgstr "" +"Java可以通过 [ Java 本地接口 (JNI)](https://en.wikipedia.org/wiki/" +"Java_Native_Interface) 加载共享对象。[`jni` crate](https://docs.rs/jni/) 允许" +"您创建一个兼容的库。" + +#: src/android/interoperability/java.md:8 +msgid "First, we create a Rust function to export to Java:" +msgstr "首先，我们创建一个可以导出到 Java 的 Rust 函数：" + +#: src/android/interoperability/java.md:10 +msgid "_interoperability/java/src/lib.rs_:" +msgstr "_interoperability/java/src/lib.rs_:" + +#: src/android/interoperability/java.md:13 +msgid "//! Rust <-> Java FFI demo.\n" +msgstr "" + +#: src/android/interoperability/java.md:18 +msgid "/// HelloWorld::hello method implementation.\n" +msgstr "" + +#: src/android/interoperability/java.md:21 +msgid "\"system\"" +msgstr "" + +#: src/android/interoperability/java.md:27 +msgid "\"Hello, {input}!\"" +msgstr "" + +#: src/android/interoperability/java.md:33 +#: src/android/interoperability/java.md:63 +msgid "_interoperability/java/Android.bp_:" +msgstr "_interoperability/java/Android.bp_:" + +#: src/android/interoperability/java.md:37 +#: src/android/interoperability/java.md:70 +msgid "\"libhello_jni\"" +msgstr "" + +#: src/android/interoperability/java.md:38 +#: src/android/interoperability/java.md:53 +msgid "\"hello_jni\"" +msgstr "" + +#: src/android/interoperability/java.md:40 +msgid "\"libjni\"" +msgstr "" + +#: src/android/interoperability/java.md:44 +msgid "Finally, we can call this function from Java:" +msgstr "最后，我们可以从 Java 中调用这个函数：" + +#: src/android/interoperability/java.md:46 +msgid "_interoperability/java/HelloWorld.java_:" +msgstr "_interoperability/java/HelloWorld.java_:" + +#: src/android/interoperability/java.md:67 +msgid "\"helloworld_jni\"" +msgstr "" + +#: src/android/interoperability/java.md:68 +#, fuzzy +msgid "\"HelloWorld.java\"" +msgstr "Hello World!" + +#: src/android/interoperability/java.md:69 +#, fuzzy +msgid "\"HelloWorld\"" +msgstr "Hello World!" + +#: src/android/interoperability/java.md:74 +msgid "Finally, you can build, sync, and run the binary:" +msgstr "最后，您可以构建、同步和运行二进制文件：" + +#: src/exercises/android/morning.md:3 +msgid "" +"This is a group exercise: We will look at one of the projects you work with " +"and try to integrate some Rust into it. Some suggestions:" +msgstr "" +"这是一个小组练习：我们将查看你们正在处理的项目之一，并尝试将一些 Rust 代码集" +"成进去。以下是一些建议：" + +#: src/exercises/android/morning.md:6 +msgid "Call your AIDL service with a client written in Rust." +msgstr "使用 Rust 编写的客户端调用你的 AIDL 服务。" + +#: src/exercises/android/morning.md:8 +msgid "Move a function from your project to Rust and call it." +msgstr "将你项目中的某个函数迁移到 Rust 中并调用它。" + +#: src/exercises/android/morning.md:12 +msgid "" +"No solution is provided here since this is open-ended: it relies on someone " +"in the class having a piece of code which you can turn in to Rust on the fly." +msgstr "" +"此处没有提供解决方案，因为这是开放式的：它依赖于班级中是否有人有一段您可以即" +"时转换成 Rust 的代码。" + +#: src/chromium.md:1 +#, fuzzy +msgid "Welcome to Rust in Chromium" +msgstr "欢迎来到Android 中的Rust" + +#: src/chromium.md:3 +msgid "" +"Rust is supported for third-party libraries in Chromium, with first-party " +"glue code to connect between Rust and existing Chromium C++ code." +msgstr "" + +#: src/chromium.md:6 +msgid "" +"Today, we'll call into Rust to do something silly with strings. If you've " +"got a corner of the code where you're displaying a UTF8 string to the user, " +"feel free to follow this recipe in your part of the codebase instead of the " +"exact part we talk about." +msgstr "" + +#: src/chromium/setup.md:3 +msgid "" +"Make sure you can build and run Chromium. Any platform and set of build " +"flags is OK, so long as your code is relatively recent (commit position " +"1223636 onwards, corresponding to November 2023):" +msgstr "" + +#: src/chromium/setup.md:13 +msgid "" +"(A component, debug build is recommended for quickest iteration time. This " +"is the default!)" +msgstr "" + +#: src/chromium/setup.md:16 +msgid "" +"See [How to build Chromium](https://www.chromium.org/developers/how-tos/get-" +"the-code/) if you aren't already at that point. Be warned: setting up to " +"build Chromium takes time." +msgstr "" + +#: src/chromium/setup.md:21 +msgid "It's also recommended that you have Visual Studio code installed." +msgstr "" + +#: src/chromium/setup.md:23 +msgid "About the exercises" +msgstr "" + +#: src/chromium/setup.md:25 +msgid "" +"This part of the course has a series of exercises which build on each other. " +"We'll be doing them spread throughout the course instead of just at the end. " +"If you don't have time to complete a certain part, don't worry: you can " +"catch up in the next slot." +msgstr "" + +#: src/chromium/cargo.md:3 +msgid "" +"Rust community typically uses `cargo` and libraries from [crates.io](https://" +"crates.io/). Chromium is built using `gn` and `ninja` and a curated set of " +"dependencies." +msgstr "" + +#: src/chromium/cargo.md:6 +msgid "When writing code in Rust, your choices are:" +msgstr "" + +#: src/chromium/cargo.md:8 +msgid "" +"Use `gn` and `ninja` with the help of the templates from `//build/rust/*." +"gni` (e.g. `rust_static_library` that we'll meet later). This uses " +"Chromium's audited toolchain and crates." +msgstr "" + +#: src/chromium/cargo.md:11 +msgid "" +"Use `cargo`, but [restrict yourself to Chromium's audited toolchain and " +"crates](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/" +"docs/rust.md#Using-cargo)" +msgstr "" + +#: src/chromium/cargo.md:13 +msgid "" +"Use `cargo`, trusting a [toolchain](https://rustup.rs/) and/or [crates " +"downloaded from the internet](https://crates.io/)" +msgstr "" + +#: src/chromium/cargo.md:16 +msgid "" +"From here on we'll be focusing on `gn` and `ninja`, because this is how Rust " +"code can be built into the Chromium browser. At the same time, Cargo is an " +"important part of the Rust ecosystem and you should keep it in your toolbox." +msgstr "" + +#: src/chromium/cargo.md:20 +#, fuzzy +msgid "Mini exercise" +msgstr "习题" + +#: src/chromium/cargo.md:22 +msgid "Split into small groups and:" +msgstr "" + +#: src/chromium/cargo.md:24 +msgid "" +"Brainstorm scenarios where `cargo` may offer an advantage and assess the " +"risk profile of these scenarios." +msgstr "" + +#: src/chromium/cargo.md:26 +msgid "" +"Discuss which tools, libraries, and groups of people need to be trusted when " +"using `gn` and `ninja`, offline `cargo`, etc." +msgstr "" + +#: src/chromium/cargo.md:31 +msgid "" +"Ask students to avoid peeking at the speaker notes before completing the " +"exercise. Assuming folks taking the course are physically together, ask them " +"to discuss in small groups of 3-4 people." +msgstr "" + +#: src/chromium/cargo.md:35 +msgid "" +"Notes/hints related to the first part of the exercise (\"scenarios where " +"Cargo may offer an advantage\"):" +msgstr "" + +#: src/chromium/cargo.md:38 +msgid "" +"It's fantastic that when writing a tool, or prototyping a part of Chromium, " +"one has access to the rich ecosystem of crates.io libraries. There is a " +"crate for almost anything and they are usually quite pleasant to use. " +"(`clap` for command-line parsing, `serde` for serializing/deserializing to/" +"from various formats, `itertools` for working with iterators, etc.)." +msgstr "" + +#: src/chromium/cargo.md:44 +msgid "" +"`cargo` makes it easy to try a library (just add a single line to `Cargo." +"toml` and start writing code)" +msgstr "" + +#: src/chromium/cargo.md:46 +msgid "" +"It may be worth comparing how CPAN helped make `perl` a popular choice. Or " +"comparing with `python` + `pip`." +msgstr "" + +#: src/chromium/cargo.md:49 +msgid "" +"Development experience is made really nice not only by core Rust tools (e.g. " +"using `rustup` to switch to a different `rustc` version when testing a crate " +"that needs to work on nightly, current stable, and older stable) but also by " +"an ecosystem of third-party tools (e.g. Mozilla provides `cargo vet` for " +"streamlining and sharing security audits; `criterion` crate gives a " +"streamlined way to run benchmarks)." +msgstr "" + +#: src/chromium/cargo.md:56 +msgid "" +"`cargo` makes it easy to add a tool via `cargo install --locked cargo-vet`." +msgstr "" + +#: src/chromium/cargo.md:57 +msgid "It may be worth comparing with Chrome Extensions or VScode extensions." +msgstr "" + +#: src/chromium/cargo.md:59 +msgid "" +"Broad, generic examples of projects where `cargo` may be the right choice:" +msgstr "" + +#: src/chromium/cargo.md:61 +msgid "" +"Perhaps surprisingly, Rust is becoming increasingly popular in the industry " +"for writing command line tools. The breadth and ergonomics of libraries is " +"comparable to Python, while being more robust (thanks to the rich " +"typesystem) and running faster (as a compiled, rather than interpreted " +"language)." +msgstr "" + +#: src/chromium/cargo.md:66 +msgid "" +"Participating in the Rust ecosystem requires using standard Rust tools like " +"Cargo. Libraries that want to get external contributions, and want to be " +"used outside of Chromium (e.g. in Bazel or Android/Soong build environments) " +"should probably use Cargo." +msgstr "" + +#: src/chromium/cargo.md:71 +msgid "Examples of Chromium-related projects that are `cargo`\\-based:" +msgstr "" + +#: src/chromium/cargo.md:72 +msgid "" +"`serde_json_lenient` (experimented with in other parts of Google which " +"resulted in PRs with performance improvements)" +msgstr "" + +#: src/chromium/cargo.md:74 +msgid "Fontations libraries like `font-types`" +msgstr "" + +#: src/chromium/cargo.md:75 +msgid "" +"`gnrt` tool (we will meet it later in the course) which depends on `clap` " +"for command-line parsing and on `toml` for configuration files." +msgstr "" + +#: src/chromium/cargo.md:77 +msgid "" +"Disclaimer: a unique reason for using `cargo` was unavailability of `gn` " +"when building and bootstrapping Rust standard library when building Rust " +"toolchain.)" +msgstr "" + +#: src/chromium/cargo.md:80 +msgid "" +"`run_gnrt.py` uses Chromium's copy of `cargo` and `rustc`. `gnrt` depends on " +"third-party libraries downloaded from the internet, by `run_gnrt.py` asks " +"`cargo` that only `--locked` content is allowed via `Cargo.lock`.)" +msgstr "" + +#: src/chromium/cargo.md:84 +msgid "" +"Students may identify the following items as being implicitly or explicitly " +"trusted:" +msgstr "" + +#: src/chromium/cargo.md:87 +msgid "" +"`rustc` (the Rust compiler) which in turn depends on the LLVM libraries, the " +"Clang compiler, the `rustc` sources (fetched from GitHub, reviewed by Rust " +"compiler team), binary Rust compiler downloaded for bootstrapping" +msgstr "" + +#: src/chromium/cargo.md:90 +msgid "" +"`rustup` (it may be worth pointing out that `rustup` is developed under the " +"umbrella of the https://github.com/rust-lang/ organization - same as `rustc`)" +msgstr "" + +#: src/chromium/cargo.md:92 +msgid "`cargo`, `rustfmt`, etc." +msgstr "" + +#: src/chromium/cargo.md:93 +msgid "" +"Various internal infrastructure (bots that build `rustc`, system for " +"distributing the prebuilt toolchain to Chromium engineers, etc.)" +msgstr "" + +#: src/chromium/cargo.md:95 +msgid "Cargo tools like `cargo audit`, `cargo vet`, etc." +msgstr "" + +#: src/chromium/cargo.md:96 +msgid "" +"Rust libraries vendored into `//third_party/rust` (audited by " +"security@chromium.org)" +msgstr "" + +#: src/chromium/cargo.md:98 +msgid "Other Rust libraries (some niche, some quite popular and commonly used)" +msgstr "" + +#: src/chromium/policy.md:1 +msgid "Chromium Rust policy" +msgstr "" + +#: src/chromium/policy.md:3 +msgid "" +"Chromium does not yet allow first-party Rust except in rare cases as " +"approved by Chromium's [Area Tech Leads](https://source.chromium.org/" +"chromium/chromium/src/+/main:ATL_OWNERS)." +msgstr "" + +#: src/chromium/policy.md:7 +msgid "" +"Chromium's policy on third party libraries is outlined [here](https://" +"chromium.googlesource.com/chromium/src/+/main/docs/adding_to_third_party." +"md#rust) - Rust is allowed for third party libraries under various " +"circumstances, including if they're the best option for performance or for " +"security." +msgstr "" + +#: src/chromium/policy.md:12 +msgid "" +"Very few Rust libraries directly expose a C/C++ API, so that means that " +"nearly all such libraries will require a small amount of first-party glue " +"code." +msgstr "" + +#: src/chromium/policy.md:15 +#, fuzzy +msgid "" +"```bob\n" +"\"C++\" Rust\n" +".- - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": Existing Chromium : : Chromium Rust Existing " +"Rust :\n" +": \"C++\" : : \"wrapper\" " +"crate :\n" +": +---------------+ : : +----------------+ +-------------" +"+ :\n" +": | | : : | | | " +"| :\n" +": | o-----+-+-----------+-+-> o-+----------+--> " +"| :\n" +": | | : Language : | | Crate | " +"| :\n" +": +---------------+ : boundary : +----------------+ API +-------------" +"+ :\n" +": : : :\n" +"`- - - - - - - - - -' `- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" +msgstr "" +"```bob\n" +" 栈 堆\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"（无法访问）\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" + +#: src/chromium/policy.md:30 +msgid "" +"First-party Rust glue code for a particular third-party crate should " +"normally be kept in `third_party/rust///wrapper`." +msgstr "" + +#: src/chromium/policy.md:33 +msgid "Because of this, today's course will be heavily focused on:" +msgstr "" + +#: src/chromium/policy.md:35 +msgid "Bringing in third-party Rust libraries (\"crates\")" +msgstr "" + +#: src/chromium/policy.md:36 +msgid "Writing glue code to be able to use those crates from Chromium C++." +msgstr "" + +#: src/chromium/policy.md:38 +msgid "If this policy changes over time, the course will evolve to keep up." +msgstr "" + +#: src/chromium/build-rules.md:1 +#, fuzzy +msgid "Build rules" +msgstr "构建规则" + +#: src/chromium/build-rules.md:3 +msgid "" +"Rust code is usually built using `cargo`. Chromium builds with `gn` and " +"`ninja` for efficiency --- its static rules allow maximum parallelism. Rust " +"is no exception." +msgstr "" + +#: src/chromium/build-rules.md:7 +msgid "Adding Rust code to Chromium" +msgstr "" + +#: src/chromium/build-rules.md:9 +msgid "" +"In some existing Chromium `BUILD.gn` file, declare a `rust_static_library`:" +msgstr "" + +#: src/chromium/build-rules.md:11 +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules.md:20 +msgid "" +"You can also add `deps` on other Rust targets. Later we'll use this to " +"depend upon third party code." +msgstr "" + +#: src/chromium/build-rules.md:25 +msgid "" +"You must specify _both_ the crate root, _and_ a full list of sources. The " +"`crate_root` is the file given to the Rust compiler representing the root " +"file of the compilation unit --- typically `lib.rs`. `sources` is a complete " +"list of all source files which `ninja` needs in order to determine when " +"rebuilds are necessary." +msgstr "" + +#: src/chromium/build-rules.md:31 +msgid "" +"(There's no such thing as a Rust `source_set`, because in Rust, an entire " +"crate is a compilation unit. A `static_library` is the smallest unit.)" +msgstr "" + +#: src/chromium/build-rules.md:34 +msgid "" +"Students might be wondering why we need a gn template, rather than using " +"[gn's built-in support for Rust static libraries](https://gn.googlesource." +"com/gn/+/main/docs/reference.md#func_static_library). The answer is that " +"this template provides support for CXX interop, Rust features, and unit " +"tests, some of which we'll use later." +msgstr "" + +#: src/chromium/build-rules/unsafe.md:1 +msgid "Including `unsafe` Rust Code" +msgstr "" + +#: src/chromium/build-rules/unsafe.md:3 +msgid "" +"Unsafe Rust code is forbidden in `rust_static_library` by default --- it " +"won't compile. If you need unsafe Rust code, add `allow_unsafe = true` to " +"the gn target. (Later in the course we'll see circumstances where this is " +"necessary.)" +msgstr "" + +#: src/chromium/build-rules/unsafe.md:7 +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [\n" +" \"lib.rs\",\n" +" \"hippopotamus.rs\"\n" +" ]\n" +" allow_unsafe = true\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules/depending.md:3 +msgid "Simply add the above target to the `deps` of some Chromium C++ target." +msgstr "" + +#: src/chromium/build-rules/depending.md:5 +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"\n" +"# or source_set, static_library etc.\n" +"component(\"preexisting_cpp\") {\n" +" deps = [ \":my_rust_lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules/vscode.md:3 +msgid "" +"Types are elided in Rust code, which makes a good IDE even more useful than " +"for C++. Visual Studio code works well for Rust in Chromium. To use it," +msgstr "" + +#: src/chromium/build-rules/vscode.md:6 +msgid "" +"Ensure your VSCode has the `rust-analyzer` extension, not earlier forms of " +"Rust support" +msgstr "" + +#: src/chromium/build-rules/vscode.md:8 +msgid "" +"`gn gen out/Debug --export-rust-project` (or equivalent for your output " +"directory)" +msgstr "" + +#: src/chromium/build-rules/vscode.md:10 +msgid "`ln -s out/Debug/rust-project.json rust-project.json`" +msgstr "" + +#: src/chromium/build-rules/vscode.md:16 +msgid "" +"A demo of some of the code annotation and exploration features of rust-" +"analyzer might be beneficial if the audience are naturally skeptical of IDEs." +msgstr "" + +#: src/chromium/build-rules/vscode.md:19 +msgid "" +"The following steps may help with the demo (but feel free to instead use a " +"piece of Chromium-related Rust that you are most familiar with):" +msgstr "" + +#: src/chromium/build-rules/vscode.md:22 +msgid "Open `components/qr_code_generator/qr_code_generator_ffi_glue.rs`" +msgstr "" + +#: src/chromium/build-rules/vscode.md:23 +msgid "" +"Place the cursor over the `QrCode::new` call (around line 26) in " +"\\`qr_code_generator_ffi_glue.rs" +msgstr "" + +#: src/chromium/build-rules/vscode.md:25 +msgid "" +"Demo **show documentation** (typical bindings: vscode = ctrl k i; vim/CoC = " +"K)." +msgstr "" + +#: src/chromium/build-rules/vscode.md:27 +msgid "" +"Demo **go to definition** (typical bindings: vscode = F12; vim/CoC = g d). " +"(This will take you to `//third_party/rust/.../qr_code-.../src/lib.rs`.)" +msgstr "" + +#: src/chromium/build-rules/vscode.md:29 +msgid "" +"Demo **outline** and navigate to the `QrCode::with_bits` method (around line " +"164; the outline is in the file explorer pane in vscode; typical vim/CoC " +"bindings = space o)" +msgstr "" + +#: src/chromium/build-rules/vscode.md:32 +msgid "" +"Demo **type annotations** (there are quote a few nice examples in the " +"`QrCode::with_bits` method)" +msgstr "" + +#: src/chromium/build-rules/vscode.md:35 +msgid "" +"It may be worth pointing out that `gn gen ... --export-rust-project` will " +"need to be rerun after editing `BUILD.gn` files (which we will do a few " +"times throughout the exercises in this session)." +msgstr "" + +#: src/exercises/chromium/build-rules.md:1 +#, fuzzy +msgid "Build rules exercise" +msgstr "构建规则" + +#: src/exercises/chromium/build-rules.md:3 +msgid "" +"In your Chromium build, add a new Rust target to `//ui/base/BUILD.gn` " +"containing:" +msgstr "" + +#: src/exercises/chromium/build-rules.md:13 +msgid "" +"**Important**: note that `no_mangle` here is considered a type of unsafety " +"by the Rust compiler, so you'll need to to allow unsafe code in your `gn` " +"target." +msgstr "" + +#: src/exercises/chromium/build-rules.md:16 +msgid "" +"Add this new Rust target as a dependency of `//ui/base:base`. Declare this " +"function at the top of `ui/base/resource/resource_bundle.cc` (later, we'll " +"see how this can be automated by bindings generation tools):" +msgstr "" + +#: src/exercises/chromium/build-rules.md:24 +msgid "" +"Call this function from somewhere in `ui/base/resource/resource_bundle.cc` - " +"we suggest the top of `ResourceBundle::MaybeMangleLocalizedString`. Build " +"and run Chromium, and ensure that \"Hello from Rust!\" is printed lots of " +"times." +msgstr "" + +#: src/exercises/chromium/build-rules.md:28 +msgid "" +"If you use VSCode, now set up Rust to work well in VSCode. It will be useful " +"in subsequent exercises. If you've succeeded, you will be able to use right-" +"click \"Go to definition\" on `println!`." +msgstr "" + +#: src/exercises/chromium/build-rules.md:32 +#: src/exercises/chromium/interoperability-with-cpp.md:48 +msgid "Where to find help" +msgstr "" + +#: src/exercises/chromium/build-rules.md:34 +msgid "" +"The options available to the [`rust_static_library` gn template](https://" +"source.chromium.org/chromium/chromium/src/+/main:build/rust/" +"rust_static_library.gni;l=16)" +msgstr "" + +#: src/exercises/chromium/build-rules.md:35 +msgid "" +"Information about [`#[no_mangle]`](https://doc.rust-lang.org/beta/reference/" +"abi.html#the-no_mangle-attribute)" +msgstr "" + +#: src/exercises/chromium/build-rules.md:36 +msgid "" +"Information about [`extern \"C\"`](https://doc.rust-lang.org/std/keyword." +"extern.html)" +msgstr "" + +#: src/exercises/chromium/build-rules.md:37 +msgid "" +"Information about gn's [`--export-rust-project`](https://gn.googlesource.com/" +"gn/+/main/docs/reference.md#compilation-database) switch" +msgstr "" + +#: src/exercises/chromium/build-rules.md:38 +msgid "" +"[How to install rust-analyzer in VSCode](https://code.visualstudio.com/docs/" +"languages/rust)" +msgstr "" + +#: src/exercises/chromium/build-rules.md:44 +msgid "" +"This example is unusual because it boils down to the lowest-common-" +"denominator interop language, C. Both C++ and Rust can natively declare and " +"call C ABI functions. Later in the course, we'll connect C++ directly to " +"Rust." +msgstr "" + +#: src/exercises/chromium/build-rules.md:48 +msgid "" +"`allow_unsafe = true` is required here because `#[no_mangle]` might allow " +"Rust to generate two functions with the same name, and Rust can no longer " +"guarantee that the right one is called." +msgstr "" + +#: src/exercises/chromium/build-rules.md:52 +msgid "" +"If you need a pure Rust executable, you can also do that using the " +"`rust_executable` gn template." +msgstr "" + +#: src/chromium/testing.md:3 +msgid "" +"Rust community typically authors unit tests in a module placed in the same " +"source file as the code being tested. This was covered [earlier](../testing." +"md) in the course and looks like this:" +msgstr "" + +#: src/chromium/testing.md:17 +msgid "" +"In Chromium we place unit tests in a separate source file and we continue to " +"follow this practice for Rust --- this makes tests consistently discoverable " +"and helps to avoid rebuilding `.rs` files a second time (in the `test` " +"configuration)." +msgstr "" + +#: src/chromium/testing.md:22 +msgid "" +"This results in the following options for testing Rust code in Chromium:" +msgstr "" + +#: src/chromium/testing.md:24 +msgid "" +"Native Rust tests (i.e. `#[test]`). Discouraged outside of `//third_party/" +"rust`." +msgstr "" + +#: src/chromium/testing.md:26 +msgid "" +"`gtest` tests authored in C++ and exercising Rust via FFI calls. Sufficient " +"when Rust code is just a thin FFI layer and the existing unit tests provide " +"sufficient coverage for the feature." +msgstr "" + +#: src/chromium/testing.md:29 +msgid "" +"`gtest` tests authored in Rust and using the crate under test through its " +"public API (using `pub mod for_testing { ... }` if needed). This is the " +"subject of the next few slides." +msgstr "" + +#: src/chromium/testing.md:35 +msgid "" +"Mention that native Rust tests of third-party crates should eventually be " +"exercised by Chromium bots. (Such testing is needed rarely --- only after " +"adding or updating third-party crates.)" +msgstr "" + +#: src/chromium/testing.md:39 +msgid "" +"Some examples may help illustrate when C++ `gtest` vs Rust `gtest` should be " +"used:" +msgstr "" + +#: src/chromium/testing.md:42 +msgid "" +"QR has very little functionality in the first-party Rust layer (it's just a " +"thin FFI glue) and therefore uses the existing C++ unit tests for testing " +"both the C++ and the Rust implementation (parameterizing the tests so they " +"enable or disable Rust using a `ScopedFeatureList`)." +msgstr "" + +#: src/chromium/testing.md:47 +msgid "" +"Hypothetical/WIP PNG integration may need to implement memory-safe " +"implementation of pixel transformations that are provided by `libpng` but " +"missing in the `png` crate - e.g. RGBA => BGRA, or gamma correction. Such " +"functionality may benefit from separate tests authored in Rust." +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md:3 +msgid "" +"The [`rust_gtest_interop`](https://chromium.googlesource.com/chromium/src/+/" +"main/testing/rust_gtest_interop/README.md) library provides a way to:" +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md:5 +msgid "" +"Use a Rust function as a `gtest` testcase (using the `#[gtest(...)]` " +"attribute)" +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md:7 +msgid "" +"Use `expect_eq!` and similar macros (similar to `assert_eq!` but not " +"panicking and not terminating the test when the assertion fails)." +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md:10 +#, fuzzy +msgid "Example:" +msgstr "示例" + +#: src/chromium/testing/build-gn.md:3 +msgid "" +"The simplest way to build Rust `gtest` tests is to add them to an existing " +"test binary that already contains tests authored in C++. For example:" +msgstr "" + +#: src/chromium/testing/build-gn.md:6 +msgid "" +"```gn\n" +"test(\"ui_base_unittests\") {\n" +" ...\n" +" sources += [ \"my_rust_lib_unittest.rs\" ]\n" +" deps += [ \":my_rust_lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/testing/build-gn.md:14 +msgid "" +"Authoring Rust tests in a separate `static_library` also works, but requires " +"manually declaring the dependency on the support libraries:" +msgstr "" + +#: src/chromium/testing/build-gn.md:17 +msgid "" +"```gn\n" +"rust_static_library(\"my_rust_lib_unittests\") {\n" +" testonly = true\n" +" is_gtest_unittests = true\n" +" crate_root = \"my_rust_lib_unittest.rs\"\n" +" sources = [ \"my_rust_lib_unittest.rs\" ]\n" +" deps = [\n" +" \":my_rust_lib\",\n" +" \"//testing/rust_gtest_interop\",\n" +" ]\n" +"}\n" +"\n" +"test(\"ui_base_unittests\") {\n" +" ...\n" +" deps += [ \":my_rust_lib_unittests\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md:3 +msgid "" +"After adding `:my_rust_lib` to GN `deps`, we still need to learn how to " +"import and use `my_rust_lib` from `my_rust_lib_unittest.rs`. We haven't " +"provided an explicit `crate_name` for `my_rust_lib` so its crate name is " +"computed based on the full target path and name. Fortunately we can avoid " +"working with such an unwieldy name by using the `chromium::import!` macro " +"from the automatically-imported `chromium` crate:" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md:12 +msgid "\"//ui/base:my_rust_lib\"" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md:18 +msgid "Under the covers the macro expands to something similar to:" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md:26 +msgid "" +"More information can be found in [the doc comment](https://source.chromium." +"org/chromium/chromium/src/+/main:build/rust/chromium_prelude/" +"chromium_prelude.rs?q=f:chromium_prelude.rs%20pub.use.*%5Cbimport%5Cb;%20-f:" +"third_party&ss=chromium%2Fchromium%2Fsrc) of the `chromium::import` macro." +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md:31 +msgid "" +"`rust_static_library` supports specifying an explicit name via `crate_name` " +"property, but doing this is discouraged. And it is discouraged because the " +"crate name has to be globally unique. crates.io guarantees uniqueness of its " +"crate names so `cargo_crate` GN targets (generated by the `gnrt` tool " +"covered in a later section) use short crate names." +msgstr "" + +#: src/exercises/chromium/testing.md:1 +#, fuzzy +msgid "Testing exercise" +msgstr "习题" + +#: src/exercises/chromium/testing.md:3 +msgid "Time for another exercise!" +msgstr "" + +#: src/exercises/chromium/testing.md:5 +msgid "In your Chromium build:" +msgstr "" + +#: src/exercises/chromium/testing.md:7 +msgid "" +"Add a testable function next to `hello_from_rust`. Some suggestions: adding " +"two integers received as arguments, computing the nth Fibonacci number, " +"summing integers in a slice, etc." +msgstr "" + +#: src/exercises/chromium/testing.md:10 +msgid "Add a separate `..._unittest.rs` file with a test for the new function." +msgstr "" + +#: src/exercises/chromium/testing.md:11 +msgid "Add the new tests to `BUILD.gn`." +msgstr "" + +#: src/exercises/chromium/testing.md:12 +msgid "Build the tests, run them, and verify that the new test works." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:3 +msgid "" +"The Rust community offers multiple options for C++/Rust interop, with new " +"tools being developed all the time. At the moment, Chromium uses a tool " +"called CXX." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:6 +msgid "" +"You describe your whole language boundary in an interface definition " +"language (which looks a lot like Rust) and then CXX tools generate " +"declarations for functions and types in both Rust and C++." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:12 +#, fuzzy +msgid "" +"See the [CXX tutorial](https://cxx.rs/tutorial.html) for a full example of " +"using this." +msgstr "" +"请参阅 [CXX tutorial](https://cxx.rs/tutorial.html) ，了解有关使用的完整示" +"例。" + +#: src/chromium/interoperability-with-cpp.md:19 +msgid "" +"Talk through the diagram. Explain that behind the scenes, this is doing just " +"the same as you previously did. Point out that automating the process has " +"the following benefits:" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:23 +msgid "" +"The tool guarantees that the C++ and Rust sides match (e.g. you get compile " +"errors if the `#[cxx::bridge]` doesn't match the actual C++ or Rust " +"definitions, but with out-of-sync manual bindings you'd get Undefined " +"Behavior)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:27 +msgid "" +"The tool automates generation of FFI thunks (small, C-ABI-compatible, free " +"functions) for non-C features (e.g. enabling FFI calls into Rust or C++ " +"methods; manual bindings would require authoring such top-level, free " +"functions manually)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:31 +msgid "The tool and the library can handle a set of core types - for example:" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:32 +msgid "" +"`&[T]` can be passed across the FFI boundary, even though it doesn't " +"guarantee any particular ABI or memory layout. With manual bindings `std::" +"span` / `&[T]` have to be manually destructured and rebuilt out of a " +"pointer and length - this is error-prone given that each language represents " +"empty slices slightly differently)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:37 +msgid "" +"Smart pointers like `std::unique_ptr`, `std::shared_ptr`, and/or `Box` " +"are natively supported. With manual bindings, one would have to pass C-ABI-" +"compatible raw pointers, which would increase lifetime and memory-safety " +"risks." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md:41 +msgid "" +"`rust::String` and `CxxString` types understand and maintain differences in " +"string representation across the languages (e.g. `rust::String::lossy` can " +"build a Rust string from non-UTF8 input and `rust::String::c_str` can NUL-" +"terminate a string)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:3 +msgid "" +"CXX requires that the whole C++/Rust boundary is declared in `cxx::bridge` " +"modules inside `.rs` source code." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:16 +msgid "\"example/include/blobstore.h\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:24 +msgid "// Definitions of Rust types and functions go here\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:30 +msgid "Point out:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:32 +msgid "" +"Although this looks like a regular Rust `mod`, the `#[cxx::bridge]` " +"procedural macro does complex things to it. The generated code is quite a " +"bit more sophisticated - though this does still result in a `mod` called " +"`ffi` in your code." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:36 +msgid "Native support for C++'s `std::unique_ptr` in Rust" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:37 +#, fuzzy +msgid "Native support for Rust slices in C++" +msgstr "对测试的内置支持。" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:38 +msgid "Calls from C++ to Rust, and Rust types (in the top part)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:39 +msgid "Calls from Rust to C++, and C++ types (in the bottom part)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md:41 +msgid "" +"**Common misconception**: It _looks_ like a C++ header is being parsed by " +"Rust, but this is misleading. This header is never interpreted by Rust, but " +"simply `#include`d in the generated C++ code for the benefit of C++ " +"compilers." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:3 +#, fuzzy +msgid "" +"By far the most useful page when using CXX is the [type reference](https://" +"cxx.rs/bindings.html)." +msgstr "展示 [Rust 和 C++类型](https://cxx.rs/bindings.html) 之间的对应关系：" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:5 +msgid "CXX fundamentally suits cases where:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:7 +msgid "" +"Your Rust-C++ interface is sufficiently simple that you can declare all of " +"it." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:8 +msgid "" +"You're using only the types natively supported by CXX already, for example " +"`std::unique_ptr`, `std::string`, `&[u8]` etc." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:11 +msgid "" +"It has many limitations --- for example lack of support for Rust's `Option` " +"type." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:14 +msgid "" +"These limitations constrain us to using Rust in Chromium only for well " +"isolated \"leaf nodes\" rather than for arbitrary Rust-C++ interop. When " +"considering a use-case for Rust in Chromium, a good starting point is to " +"draft the CXX bindings for the language boundary to see if it appears simple " +"enough." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:26 +msgid "" +"You should also discuss some of the other sticky points with CXX, for " +"example:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:28 +msgid "" +"Its error handling is based around C++ exceptions (given on the next slide)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:29 +msgid "Function pointers are awkward to use." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:3 +msgid "" +"CXX's [support for `Result`](https://cxx.rs/binding/result.html) relies " +"on C++ exceptions, so we can't use that in Chromium. Alternatives:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:6 +msgid "The `T` part of `Result` can be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:7 +msgid "" +"Returned via out parameters (e.g. via `&mut T`). This requires that `T` can " +"be passed across the FFI boundary - for example `T` has to be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:9 +msgid "A primitive type (like `u32` or `usize`)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:10 +msgid "" +"A type natively supported by `cxx` (like `UniquePtr`) that has a suitable " +"default value to use in a failure case (_unlike_ `Box`)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:12 +msgid "" +"Retained on the Rust side, and exposed via reference. This may be needed " +"when `T` is a Rust type, which cannot be passed across the FFI boundary, and " +"cannot be stored in `UniquePtr`." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:16 +msgid "The `E` part of `Result` can be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:17 +msgid "" +"Returned as a boolean (e.g. `true` representing success, and `false` " +"representing failure)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md:19 +msgid "" +"Preserving error details is in theory possible, but so far hasn't been " +"needed in practice." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:1 +#, fuzzy +msgid "CXX Error Handling: QR Example" +msgstr "错误处理" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:3 +msgid "" +"The QR code generator is [an example](https://source.chromium.org/chromium/" +"chromium/src/+/main:components/qr_code_generator/qr_code_generator_ffi_glue." +"rs;l=13-18;drc=7bf1b75b910ca430501b9c6a74c1d18a0223ecca) where a boolean is " +"used to communicate success vs failure, and where the successful result can " +"be passed across the FFI boundary:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:8 +msgid "\"qr_code_generator\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:23 +msgid "" +"Students may be curious about the semantics of the `out_qr_size` output. " +"This is not the size of the vector, but the size of the QR code (and " +"admittedly it is a bit redundant - this is the square root of the size of " +"the vector)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:27 +msgid "" +"It may be worth pointing out the importance of initializing `out_qr_size` " +"before calling into the Rust function. Creation of a Rust reference that " +"points to uninitialized memory results in Undefined Behavior (unlike in C++, " +"when only the act of dereferencing such memory results in UB)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md:32 +msgid "" +"If students ask about `Pin`, then explain why CXX needs it for mutable " +"references to C++ data: the answer is that C++ data can’t be moved around " +"like Rust data, because it may contain self-referential pointers." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:1 +#, fuzzy +msgid "CXX Error Handling: PNG Example" +msgstr "错误处理" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:3 +msgid "" +"A prototype of a PNG decoder illustrates what can be done when the " +"successful result cannot be passed across the FFI boundary:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:7 +msgid "\"gfx::rust_bindings\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:10 +msgid "" +"/// This returns an FFI-friendly equivalent of `Result,\n" +" /// ()>`.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:14 +msgid "/// C++ bindings for the `crate::png::ResultOfPngReader` type.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:21 +msgid "/// C++ bindings for the `crate::png::PngReader` type.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:32 +msgid "" +"`PngReader` and `ResultOfPngReader` are Rust types --- objects of these " +"types cannot cross the FFI boundary without indirection of a `Box`. We " +"can't have an `out_parameter: &mut PngReader`, because CXX doesn't allow C++ " +"to store Rust objects by value." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md:37 +msgid "" +"This example illustrates that even though CXX doesn't support arbitrary " +"generics nor templates, we can still pass them across the FFI boundary by " +"manually specializing / monomorphizing them into a non-generic type. In the " +"example `ResultOfPngReader` is a non-generic type that forwards into " +"appropriate methods of `Result` (e.g. into `is_err`, `unwrap`, and/or " +"`as_mut`)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:1 +msgid "Using cxx in Chromium" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:3 +msgid "" +"In Chromium, we define an independent `#[cxx::bridge] mod` for each leaf-" +"node where we want to use Rust. You'd typically have one for each " +"`rust_static_library`. Just add" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:7 +msgid "" +"```gn\n" +"cxx_bindings = [ \"my_rust_file.rs\" ]\n" +" # list of files containing #[cxx::bridge], not all source files\n" +"allow_unsafe = true\n" +"```" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:13 +msgid "" +"to your existing `rust_static_library` target alongside `crate_root` and " +"`sources`." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:16 +msgid "C++ headers will be generated at a sensible location, so you can just" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:19 +msgid "\"ui/base/my_rust_file.rs.h\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:22 +msgid "" +"You will find some utility functions in `//base` to convert to/from Chromium " +"C++ types to CXX Rust types --- for example [`SpanToRustSlice`](https://" +"source.chromium.org/chromium/chromium/src/+/main:base/containers/span_rust.h;" +"l=21)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:27 +msgid "Students may ask --- why do we still need `allow_unsafe = true`?" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:29 +msgid "" +"The broad answer is that no C/C++ code is \"safe\" by the normal Rust " +"standards. Calling back and forth to C/C++ from Rust may do arbitrary things " +"to memory, and compromise the safety of Rust's own data layouts. Presence of " +"_too many_ `unsafe` keywords in C/C++ interop can harm the signal-to-noise " +"ratio of such a keyword, and is [controversial](https://steveklabnik.com/" +"writing/the-cxx-debate), but strictly, bringing any foreign code into a Rust " +"binary can cause unexpected behavior from Rust's perspective." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:36 +msgid "" +"The narrow answer lies in the diagram at the top of [this page](../" +"interoperability-with-cpp.md) --- behind the scenes, CXX generates Rust " +"`unsafe` and `extern \"C\"` functions just like we did manually in the " +"previous section." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:1 +#, fuzzy +msgid "Exercise: Interoperability with C++" +msgstr "与 C 的互操作性" + +#: src/exercises/chromium/interoperability-with-cpp.md:3 +msgid "Part one" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:5 +msgid "" +"In the Rust file you previously created, add a `#[cxx::bridge]` which " +"specifies a single function, to be called from C++, called " +"`hello_from_rust`, taking no parameters and returning no value." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:8 +msgid "" +"Modify your previous `hello_from_rust` function to remove `extern \"C\"` and " +"`#[no_mangle]`. This is now just a standard Rust function." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:10 +msgid "Modify your `gn` target to build these bindings." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:11 +msgid "" +"In your C++ code, remove the forward-declaration of `hello_from_rust`. " +"Instead, include the generated header file." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:13 +msgid "Build and run!" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:15 +msgid "Part two" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:17 +msgid "" +"It's a good idea to play with CXX a little. It helps you think about how " +"flexible Rust in Chromium actually is." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:20 +#, fuzzy +msgid "Some things to try:" +msgstr "一些注意事项：" + +#: src/exercises/chromium/interoperability-with-cpp.md:22 +msgid "Call back into C++ from Rust. You will need:" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:23 +msgid "" +"An additional header file which you can `include!` from your `cxx::bridge`. " +"You'll need to declare your C++ function in that new header file." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:25 +msgid "" +"An `unsafe` block to call such a function, or alternatively specify the " +"`unsafe` keyword in your `#[cxx::bridge]` [as described here](https://cxx.rs/" +"extern-c++.html#functions-and-member-functions)." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:27 +msgid "" +"You may also need to `#include \"third_party/rust/cxx/v1/crate/include/cxx." +"h\"`" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:29 +msgid "Pass a C++ string from C++ into Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:30 +msgid "Pass a reference to a C++ object into Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:31 +msgid "" +"Intentionally get the Rust function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:33 +msgid "" +"Intentionally get the C++ function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:35 +msgid "" +"Pass a `std::unique_ptr` of some type from C++ into Rust, so that Rust can " +"own some C++ object." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:37 +msgid "" +"Create a Rust object and pass it into C++, so that C++ owns it. (Hint: you " +"need a `Box`)." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:39 +msgid "Declare some methods on a C++ type. Call them from Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:40 +msgid "Declare some methods on a Rust type. Call them from C++." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:42 +msgid "Part three" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:44 +msgid "" +"Now you understand the strengths and limitations of CXX interop, think of a " +"couple of use-cases for Rust in Chromium where the interface would be " +"sufficiently simple. Sketch how you might define that interface." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:50 +#, fuzzy +msgid "The [`cxx` binding reference](https://cxx.rs/bindings.html)" +msgstr "展示 [Rust 和 C++类型](https://cxx.rs/bindings.html) 之间的对应关系：" + +#: src/exercises/chromium/interoperability-with-cpp.md:51 +msgid "" +"The [`rust_static_library` gn template](https://source.chromium.org/chromium/" +"chromium/src/+/main:build/rust/rust_static_library.gni;l=16)" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:57 +msgid "Some of the questions you may encounter:" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:59 +msgid "" +"I'm seeing a problem initializing a variable of type X with type Y, where X " +"and Y are both function types. This is because your C++ function doesn't " +"quite match the declaration in your `cxx::bridge`." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:62 +msgid "" +"I seem to be able to freely convert C++ references into Rust references. " +"Doesn't that risk UB? For CXX's _opaque_ types, no, because they are zero-" +"sized. For CXX trivial types yes, it's _possible_ to cause UB, although " +"CXX's design makes it quite difficult to craft such an example." +msgstr "" + +#: src/chromium/adding-third-party-crates.md:3 +msgid "" +"Rust libraries are called \"crates\" and are found at [crates.io](https://" +"crates.io). It's _very easy_ for Rust crates to depend upon one another. So " +"they do!" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:6 +#, fuzzy +msgid "C++ library" +msgstr "库" + +#: src/chromium/adding-third-party-crates.md:6 +#, fuzzy +msgid "Rust crate" +msgstr "Rust 生态系统" + +#: src/chromium/adding-third-party-crates.md:8 +#, fuzzy +msgid "Build system" +msgstr "Rust 生态系统" + +#: src/chromium/adding-third-party-crates.md:8 +#: src/chromium/adding-third-party-crates.md:10 +msgid "Lots" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:8 +msgid "Consistent: `Cargo.toml`" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:9 +msgid "Typical library size" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:9 +msgid "Large-ish" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:9 +msgid "Small" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:10 +msgid "Transitive dependencies" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:10 +msgid "Few" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:12 +msgid "For a Chromium engineer, this has pros and cons:" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:14 +msgid "" +"All crates use a common build system so we can automate their inclusion into " +"Chromium..." +msgstr "" + +#: src/chromium/adding-third-party-crates.md:16 +msgid "" +"... but, crates typically have transitive dependencies, so you will likely " +"have to bring in multiple libraries." +msgstr "" + +#: src/chromium/adding-third-party-crates.md:19 +msgid "We'll discuss:" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:21 +msgid "How to put a crate in the Chromium source code tree" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:22 +msgid "How to make `gn` build rules for it" +msgstr "" + +#: src/chromium/adding-third-party-crates.md:23 +msgid "How to audit its source code for sufficient safety." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:1 +msgid "Configuring the `Cargo.toml` file to add crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:3 +msgid "" +"Chromium has a single set of centrally-managed direct crate dependencies. " +"These are managed through a single [`Cargo.toml`](https://source.chromium." +"org/chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/Cargo." +"toml):" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:6 +msgid "" +"```toml\n" +"[dependencies]\n" +"bitflags = \"1\"\n" +"cfg-if = \"1\"\n" +"cxx = \"1\"\n" +"# lots more...\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:14 +msgid "" +"As with any other `Cargo.toml`, you can specify [more details about the " +"dependencies](https://doc.rust-lang.org/cargo/reference/specifying-" +"dependencies.html) --- most commonly, you'll want to specify the `features` " +"that you wish to enable in the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:18 +msgid "" +"When adding a crate to Chromium, you'll often need to provide some extra " +"information in an additional file, `gnrt_config.toml`, which we'll meet next." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:3 +msgid "" +"Alongside `Cargo.toml` is [`gnrt_config.toml`](https://source.chromium.org/" +"chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/gnrt_config." +"toml). This contains Chromium-specific extensions to crate handling." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:6 +msgid "" +"If you add a new crate, you should specify at least the `group`. This is one " +"of:" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:15 +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:15 +msgid "For instance," +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:22 +msgid "" +"Depending on the crate source code layout, you may also need to use this " +"file to specify where its `LICENSE` file(s) can be found." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:25 +msgid "" +"Later, we'll see some other things you will need to configure in this file " +"to resolve problems." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:3 +msgid "" +"A tool called `gnrt` knows how to download crates and how to generate `BUILD." +"gn` rules." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:6 +msgid "To start, download the crate you want like this:" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:13 +msgid "" +"Although the `gnrt` tool is part of the Chromium source code, by running " +"this command you will be downloading and running its dependencies from " +"`crates.io`. See [the earlier section](../cargo.md) discussing this security " +"decision." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:17 +msgid "This `vendor` command may download:" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:19 +#, fuzzy +msgid "Your crate" +msgstr "实用 crate" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:20 +msgid "Direct and transitive dependencies" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:21 +msgid "" +"New versions of other crates, as required by `cargo` to resolve the complete " +"set of crates required by Chromium." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md:24 +msgid "" +"Chromium maintains patches for some crates, kept in `//third_party/rust/" +"chromium_crates_io/patches`. These will be reapplied automatically, but if " +"patching fails you may need to take manual action." +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:3 +msgid "" +"Once you've downloaded the crate, generate the `BUILD.gn` files like this:" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:9 +msgid "Now run `git status`. You should find:" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:11 +msgid "" +"At least one new crate source code in `third_party/rust/chromium_crates_io/" +"vendor`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:13 +msgid "" +"At least one new `BUILD.gn` in `third_party/rust//v`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:15 +msgid "An appropriate `README.chromium`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:17 +#, fuzzy +msgid "" +"The \"major semver version\" is a [Rust \"semver\" version number](https://" +"doc.rust-lang.org/cargo/reference/semver.html)." +msgstr "" +"请参阅 [Rust 引用](https://doc.rust-lang.org/reference/type-layout.html)。" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:19 +msgid "" +"Take a close look, especially at the things generated in `third_party/rust`." +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:23 +msgid "" +"Talk a little about semver --- and specifically the way that in Chromium " +"it's to allow multiple incompatible versions of a crate, which is " +"discouraged but sometimes necessary in the Cargo ecosystem." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:3 +msgid "" +"If your build fails, it may be because of a `build.rs`: programs which do " +"arbitrary things at build time. This is fundamentally at odds with the " +"design of `gn` and `ninja` which aim for static, deterministic, build rules " +"to maximize parallelism and repeatability of builds." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:8 +msgid "" +"Some `build.rs` actions are automatically supported; others require action:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "build script effect" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "Supported by our gn templates" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "Work required by you" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +msgid "Checking rustc version to configure features on and off" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +msgid "None" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +msgid "Checking platform or CPU to configure features on and off" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +#, fuzzy +msgid "Generating code" +msgstr "泛型" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +msgid "Yes - specify in `gnrt_config.toml`" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +msgid "Building C/C++" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "Patch around it" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "Arbitrary other actions" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md:18 +msgid "" +"Fortunately, most crates don't contain a build script, and fortunately, most " +"build scripts only do the top two actions." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:3 +msgid "" +"If `ninja` complains about missing files, check the `build.rs` to see if it " +"writes source code files." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:6 +msgid "" +"If so, modify [`gnrt_config.toml`](../configuring-gnrt-config-toml.md) to " +"add `build-script-outputs` to the crate. If this is a transitive dependency, " +"that is, one on which Chromium code should not directly depend, also add " +"`allow-first-party-usage=false`. There are several examples already in that " +"file:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:11 +msgid "" +"```toml\n" +"[crate.unicode-linebreak]\n" +"allow-first-party-usage = false\n" +"build-script-outputs = [\"tables.rs\"]\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:17 +msgid "" +"Now rerun [`gnrt.py -- gen`](../generating-gn-build-rules.md) to regenerate " +"`BUILD.gn` files to inform ninja that this particular output file is input " +"to subsequent build steps." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:3 +msgid "" +"Some crates use the [`cc`](https://crates.io/crates/cc) crate to build and " +"link C/C++ libraries. Other crates parse C/C++ using [`bindgen`](https://" +"crates.io/crates/bindgen) within their build scripts. These actions can't be " +"supported in a Chromium context --- our gn, ninja and LLVM build system is " +"very specific in expressing relationships between build actions." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:8 +msgid "So, your options are:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:10 +msgid "Avoid these crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:11 +msgid "Apply a patch to the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:13 +msgid "" +"Patches should be kept in `third_party/rust/chromium_crates_io/patches/" +"` - see for example the [patches against the `cxx` crate](https://" +"source.chromium.org/chromium/chromium/src/+/main:third_party/rust/" +"chromium_crates_io/patches/cxx/) - and will be applied automatically by " +"`gnrt` each time it upgrades the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:3 +msgid "" +"Once you've added a third-party crate and generated build rules, depending " +"on a crate is simple. Find your `rust_static_library` target, and add a " +"`dep` on the `:lib` target within your crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:7 +#, fuzzy +msgid "Specifically," +msgstr "特定于操作系统" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:9 +msgid "" +"```bob\n" +" +------------+ +----------------------+\n" +"\"//third_party/rust\" | crate name | \"/v\" | major semver version | \":" +"lib\"\n" +" +------------+ +----------------------+\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:17 +msgid "" +"```gn\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +" deps = [ \"//third_party/rust/example_rust_crate/v1:lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:1 +msgid "Auditing Third Party Crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:3 +msgid "" +"Adding new libraries is subject to Chromium's standard [policies](https://" +"chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/rust." +"md#Third_party-review), but of course also subject to security review. As " +"you may be bringing in not just a single crate but also transitive " +"dependencies, there may be a lot of code to review. On the other hand, safe " +"Rust code can have limited negative side effects. How should you review it?" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:9 +msgid "" +"Over time Chromium aims to move to a process based around [cargo vet]" +"(https://mozilla.github.io/cargo-vet/)." +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:11 +msgid "" +"Meanwhile, for each new crate addition, we are checking for the following:" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:13 +msgid "" +"Understand why each crate is used. What's the relationship between crates? " +"If the build system for each crate contains a `build.rs` or procedural " +"macros, work out what they're for. Are they compatible with the way Chromium " +"is normally built?" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:17 +msgid "Check each crate seems to be reasonably well maintained" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:18 +msgid "" +"Use `cd third-party/rust/chromium_crates_io; cargo audit` to check for known " +"vulnerabilities (first you'll need to `cargo install cargo-audit`, which " +"ironically involves downloading lots of dependencies from the internet[2](../" +"cargo.md))" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:21 +msgid "" +"Ensure any `unsafe` code is good enough for the [Rule of Two](https://" +"chromium.googlesource.com/chromium/src/+/main/docs/security/rule-of-2." +"md#unsafe-code-in-safe-languages)" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:22 +msgid "Check for any use of `fs` or `net` APIs" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:23 +msgid "" +"Read all the code at a sufficient level to look for anything out of place " +"that might have been maliciously inserted. (You can't realistically aim for " +"100% perfection here: there's often just too much code.)" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:27 +msgid "" +"These are just guidelines --- work with reviewers from `security@chromium." +"org` to work out the right way to become confident of the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:1 +msgid "Checking Crates into Chromium Source Code" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:3 +msgid "`git status` should reveal:" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:5 +msgid "Crate code in `//third_party/rust/chromium_crates_io`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:6 +msgid "" +"Metadata (`BUILD.gn` and `README.chromium`) in `//third_party/rust//" +"`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:9 +msgid "Please also add an `OWNERS` file in the latter location." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:11 +msgid "" +"You should land all this, along with your `Cargo.toml` and `gnrt_config." +"toml` changes, into the Chromium repo." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:14 +msgid "" +"**Important**: you need to use `git add -f` because otherwise `.gitignore` " +"files may result in some files being skipped." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:17 +msgid "" +"As you do so, you might find presubmit checks fail because of non-inclusive " +"language. This is because Rust crate data tends to include names of git " +"branches, and many projects still use non-inclusive terminology there. So " +"you may need to run:" +msgstr "" + +#: src/chromium/adding-third-party-crates/keeping-up-to-date.md:3 +msgid "" +"As the OWNER of any third party Chromium dependency, you are [expected to " +"keep it up to date with any security fixes](https://chromium.googlesource." +"com/chromium/src/+/main/docs/adding_to_third_party.md#add-owners). It is " +"hoped that we will soon automate this for Rust crates, but for now, it's " +"still your responsibility just as it is for any other third party dependency." +msgstr "" + +#: src/exercises/chromium/third-party.md:3 +msgid "" +"Add [uwuify](https://crates.io/crates/uwuify) to Chromium, turning off the " +"crate's [default features](https://doc.rust-lang.org/cargo/reference/" +"features.html#the-default-feature). Assume that the crate will be used in " +"shipping Chromium, but won't be used to handle untrustworthy input." +msgstr "" + +#: src/exercises/chromium/third-party.md:7 +msgid "" +"(In the next exercise we'll use uwuify from Chromium, but feel free to skip " +"ahead and do that now if you like. Or, you could create a new " +"[`rust_executable` target](https://source.chromium.org/chromium/chromium/src/" +"+/main:build/rust/rust_executable.gni) which uses `uwuify`)." +msgstr "" + +#: src/exercises/chromium/third-party.md:13 +msgid "Students will need to download lots of transitive dependencies." +msgstr "" + +#: src/exercises/chromium/third-party.md:15 +msgid "The total crates needed are:" +msgstr "" + +#: src/exercises/chromium/third-party.md:17 +#, fuzzy +msgid "`instant`," +msgstr "常量" + +#: src/exercises/chromium/third-party.md:18 +msgid "`lock_api`," +msgstr "" + +#: src/exercises/chromium/third-party.md:19 +msgid "`parking_lot`," +msgstr "" + +#: src/exercises/chromium/third-party.md:20 +msgid "`parking_lot_core`," +msgstr "" + +#: src/exercises/chromium/third-party.md:21 +msgid "`redox_syscall`," +msgstr "" + +#: src/exercises/chromium/third-party.md:22 +msgid "`scopeguard`," +msgstr "" + +#: src/exercises/chromium/third-party.md:23 +msgid "`smallvec`, and" +msgstr "" + +#: src/exercises/chromium/third-party.md:24 +msgid "`uwuify`." +msgstr "" + +#: src/exercises/chromium/third-party.md:26 +msgid "" +"If students are downloading even more than that, they probably forgot to " +"turn off the default features." +msgstr "" + +#: src/exercises/chromium/third-party.md:29 +msgid "" +"Thanks to [Daniel Liu](https://github.com/Daniel-Liu-c0deb0t) for this crate!" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:1 +msgid "Bringing It Together --- Exercise" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:3 +msgid "" +"In this exercise, you're going to add a whole new Chromium feature, bringing " +"together everything you already learned." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:6 +msgid "The Brief from Product Management" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:8 +msgid "" +"A community of pixies has been discovered living in a remote rainforest. " +"It's important that we get Chromium for Pixies delivered to them as soon as " +"possible." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:11 +msgid "" +"The requirement is to translate all Chromium's UI strings into Pixie " +"language." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:13 +msgid "" +"There's not time to wait for proper translations, but fortunately pixie " +"language is very close to English, and it turns out there's a Rust crate " +"which does the translation." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:17 +msgid "" +"In fact, you already [imported that crate in the previous exercise](https://" +"crates.io/crates/uwuify)." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:19 +msgid "" +"(Obviously, real translations of Chrome require incredible care and " +"diligence. Don't ship this!)" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:22 +msgid "Steps" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:24 +msgid "" +"Modify `ResourceBundle::MaybeMangleLocalizedString` so that it uwuifies all " +"strings before display. In this special build of Chromium, it should always " +"do this irrespective of the setting of `mangle_localized_strings_`." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:28 +msgid "" +"If you've done everything right across all these exercises, congratulations, " +"you should have created Chrome for pixies!" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:36 +msgid "" +"UTF16 vs UTF8. Students should be aware that Rust strings are always UTF8, " +"and will probably decide that it's better to do the conversion on the C++ " +"side using `base::UTF16ToUTF8` and back again." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:39 +msgid "" +"If students decide to do the conversion on the Rust side, they'll need to " +"consider [`String::from_utf16`](https://doc.rust-lang.org/std/string/struct." +"String.html#method.from_utf16), consider error handling, and consider which " +"[CXX supported types can transfer a lot of u16s](https://cxx.rs/binding/" +"slice.html)." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:42 +msgid "" +"Students may design the C++/Rust boundary in several different ways, e.g. " +"taking and returning strings by value, or taking a mutable reference to a " +"string. If a mutable reference is used, CXX will likely tell the student " +"that they need to use [`Pin`](https://doc.rust-lang.org/std/pin/). You may " +"need to explain what `Pin` does, and then explain why CXX needs it for " +"mutable references to C++ data: the answer is that C++ data can't be moved " +"around like Rust data, because it may contain self-referential pointers." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:49 +msgid "" +"The C++ target containing `ResourceBundle::MaybeMangleLocalizedString` will " +"need to depend on a `rust_static_library` target. The student probably " +"already did this." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:52 +msgid "" +"The `rust_static_library` target will need to depend on `//third_party/rust/" +"uwuify/v0_2:lib`." +msgstr "" + +#: src/exercises/chromium/solutions.md:3 +msgid "" +"Solutions to the Chromium exercises can be found in [this series of CLs]" +"(https://chromium-review.googlesource.com/c/chromium/src/+/5096560)." +msgstr "" + +#: src/bare-metal.md:1 +msgid "Welcome to Bare Metal Rust" +msgstr "" + +#: src/bare-metal.md:3 +msgid "" +"This is a standalone one-day course about bare-metal Rust, aimed at people " +"who are familiar with the basics of Rust (perhaps from completing the " +"Comprehensive Rust course), and ideally also have some experience with bare-" +"metal programming in some other language such as C." +msgstr "" + +#: src/bare-metal.md:8 +msgid "" +"Today we will talk about 'bare-metal' Rust: running Rust code without an OS " +"underneath us. This will be divided into several parts:" +msgstr "" + +#: src/bare-metal.md:11 +msgid "What is `no_std` Rust?" +msgstr "" + +#: src/bare-metal.md:12 +msgid "Writing firmware for microcontrollers." +msgstr "" + +#: src/bare-metal.md:13 +msgid "Writing bootloader / kernel code for application processors." +msgstr "" + +#: src/bare-metal.md:14 +msgid "Some useful crates for bare-metal Rust development." +msgstr "" + +#: src/bare-metal.md:16 +msgid "" +"For the microcontroller part of the course we will use the [BBC micro:bit]" +"(https://microbit.org/) v2 as an example. It's a [development board](https://" +"tech.microbit.org/hardware/) based on the Nordic nRF51822 microcontroller " +"with some LEDs and buttons, an I2C-connected accelerometer and compass, and " +"an on-board SWD debugger." +msgstr "" + +#: src/bare-metal.md:22 +msgid "" +"To get started, install some tools we'll need later. On gLinux or Debian:" +msgstr "" + +#: src/bare-metal.md:34 +msgid "" +"And give users in the `plugdev` group access to the micro:bit programmer:" +msgstr "" + +#: src/bare-metal.md:44 src/bare-metal/microcontrollers/debugging.md:33 +msgid "On MacOS:" +msgstr "" + +#: src/bare-metal/no_std.md:7 +msgid "`core`" +msgstr "" + +#: src/bare-metal/no_std.md:17 +msgid "`std`" +msgstr "" + +#: src/bare-metal/no_std.md:24 +msgid "Slices, `&str`, `CStr`" +msgstr "" + +#: src/bare-metal/no_std.md:25 +msgid "`NonZeroU8`..." +msgstr "" + +#: src/bare-metal/no_std.md:26 +msgid "`Option`, `Result`" +msgstr "" + +#: src/bare-metal/no_std.md:27 +msgid "`Display`, `Debug`, `write!`..." +msgstr "" + +#: src/bare-metal/no_std.md:29 +msgid "`panic!`, `assert_eq!`..." +msgstr "" + +#: src/bare-metal/no_std.md:30 +msgid "`NonNull` and all the usual pointer-related functions" +msgstr "" + +#: src/bare-metal/no_std.md:31 +msgid "`Future` and `async`/`await`" +msgstr "" + +#: src/bare-metal/no_std.md:32 +msgid "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." +msgstr "" + +#: src/bare-metal/no_std.md:33 +msgid "`Duration`" +msgstr "" + +#: src/bare-metal/no_std.md:38 +msgid "`Box`, `Cow`, `Arc`, `Rc`" +msgstr "" + +#: src/bare-metal/no_std.md:39 +msgid "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" +msgstr "" + +#: src/bare-metal/no_std.md:40 +msgid "`String`, `CString`, `format!`" +msgstr "" + +#: src/bare-metal/no_std.md:45 +msgid "`Error`" +msgstr "" + +#: src/bare-metal/no_std.md:47 +msgid "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" +msgstr "" + +#: src/bare-metal/no_std.md:48 +msgid "`File` and the rest of `fs`" +msgstr "" + +#: src/bare-metal/no_std.md:49 +msgid "`println!`, `Read`, `Write`, `Stdin`, `Stdout` and the rest of `io`" +msgstr "" + +#: src/bare-metal/no_std.md:50 +msgid "`Path`, `OsString`" +msgstr "" + +#: src/bare-metal/no_std.md:51 +msgid "`net`" +msgstr "" + +#: src/bare-metal/no_std.md:52 +msgid "`Command`, `Child`, `ExitCode`" +msgstr "" + +#: src/bare-metal/no_std.md:53 +msgid "`spawn`, `sleep` and the rest of `thread`" +msgstr "" + +#: src/bare-metal/no_std.md:54 +msgid "`SystemTime`, `Instant`" +msgstr "" + +#: src/bare-metal/no_std.md:62 +msgid "`HashMap` depends on RNG." +msgstr "" + +#: src/bare-metal/no_std.md:63 +msgid "`std` re-exports the contents of both `core` and `alloc`." +msgstr "" + +#: src/bare-metal/minimal.md:1 +msgid "A minimal `no_std` program" +msgstr "" + +#: src/bare-metal/minimal.md:19 +msgid "This will compile to an empty binary." +msgstr "" + +#: src/bare-metal/minimal.md:20 +msgid "`std` provides a panic handler; without it we must provide our own." +msgstr "" + +#: src/bare-metal/minimal.md:21 +msgid "It can also be provided by another crate, such as `panic-halt`." +msgstr "" + +#: src/bare-metal/minimal.md:22 +msgid "" +"Depending on the target, you may need to compile with `panic = \"abort\"` to " +"avoid an error about `eh_personality`." +msgstr "" + +#: src/bare-metal/minimal.md:24 +msgid "" +"Note that there is no `main` or any other entry point; it's up to you to " +"define your own entry point. This will typically involve a linker script and " +"some assembly code to set things up ready for Rust code to run." +msgstr "" + +#: src/bare-metal/alloc.md:3 +msgid "" +"To use `alloc` you must implement a [global (heap) allocator](https://doc." +"rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html)." +msgstr "" + +#: src/bare-metal/alloc.md:23 +msgid "" +"// Safe because `HEAP` is only used here and `entry` is only called once.\n" +msgstr "" + +#: src/bare-metal/alloc.md:25 +msgid "// Give the allocator some memory to allocate.\n" +msgstr "" + +#: src/bare-metal/alloc.md:29 +msgid "// Now we can do things that require heap allocation.\n" +msgstr "" + +#: src/bare-metal/alloc.md:31 +#, fuzzy +msgid "\"A string\"" +msgstr "String" + +#: src/bare-metal/alloc.md:37 +msgid "" +"`buddy_system_allocator` is a third-party crate implementing a basic buddy " +"system allocator. Other crates are available, or you can write your own or " +"hook into your existing allocator." +msgstr "" + +#: src/bare-metal/alloc.md:40 +msgid "" +"The const parameter of `LockedHeap` is the max order of the allocator; i.e. " +"in this case it can allocate regions of up to 2\\*\\*32 bytes." +msgstr "" + +#: src/bare-metal/alloc.md:42 +msgid "" +"If any crate in your dependency tree depends on `alloc` then you must have " +"exactly one global allocator defined in your binary. Usually this is done in " +"the top-level binary crate." +msgstr "" + +#: src/bare-metal/alloc.md:45 +msgid "" +"`extern crate panic_halt as _` is necessary to ensure that the `panic_halt` " +"crate is linked in so we get its panic handler." +msgstr "" + +#: src/bare-metal/alloc.md:47 +msgid "This example will build but not run, as it doesn't have an entry point." +msgstr "" + +#: src/bare-metal/microcontrollers.md:3 +msgid "" +"The `cortex_m_rt` crate provides (among other things) a reset handler for " +"Cortex M microcontrollers." +msgstr "" + +#: src/bare-metal/microcontrollers.md:24 +msgid "" +"Next we'll look at how to access peripherals, with increasing levels of " +"abstraction." +msgstr "" + +#: src/bare-metal/microcontrollers.md:29 +msgid "" +"The `cortex_m_rt::entry` macro requires that the function have type `fn() -" +"> !`, because returning to the reset handler doesn't make sense." +msgstr "" + +#: src/bare-metal/microcontrollers.md:31 +msgid "Run the example with `cargo embed --bin minimal`" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:3 +msgid "" +"Most microcontrollers access peripherals via memory-mapped IO. Let's try " +"turning on an LED on our micro:bit:" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:16 +msgid "/// GPIO port 0 peripheral address\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:19 +msgid "// GPIO peripheral offsets\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:24 +msgid "// PIN_CNF fields\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:34 +#: src/bare-metal/microcontrollers/pacs.md:21 +#: src/bare-metal/microcontrollers/hals.md:26 +msgid "// Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:37 +#: src/bare-metal/microcontrollers/mmio.md:59 +msgid "" +"// Safe because the pointers are to valid peripheral control registers, and\n" +" // no aliases exist.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:56 +#: src/bare-metal/microcontrollers/pacs.md:39 +#: src/bare-metal/microcontrollers/hals.md:30 +msgid "// Set pin 28 low and pin 21 high to turn the LED on.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:72 +msgid "" +"GPIO 0 pin 21 is connected to the first column of the LED matrix, and pin 28 " +"to the first row." +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md:75 +#: src/bare-metal/microcontrollers/pacs.md:61 +#: src/bare-metal/microcontrollers/hals.md:44 +#: src/bare-metal/microcontrollers/board-support.md:37 +msgid "Run the example with:" +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:1 +msgid "Peripheral Access Crates" +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:3 +msgid "" +"[`svd2rust`](https://crates.io/crates/svd2rust) generates mostly-safe Rust " +"wrappers for memory-mapped peripherals from [CMSIS-SVD](https://www.keil.com/" +"pack/doc/CMSIS/SVD/html/index.html) files." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:49 +msgid "" +"SVD (System View Description) files are XML files typically provided by " +"silicon vendors which describe the memory map of the device." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:51 +msgid "" +"They are organised by peripheral, register, field and value, with names, " +"descriptions, addresses and so on." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:53 +msgid "" +"SVD files are often buggy and incomplete, so there are various projects " +"which patch the mistakes, add missing details, and publish the generated " +"crates." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:56 +msgid "`cortex-m-rt` provides the vector table, among other things." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md:57 +msgid "" +"If you `cargo install cargo-binutils` then you can run `cargo objdump --bin " +"pac -- -d --no-show-raw-insn` to see the resulting binary." +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md:1 +msgid "HAL crates" +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md:3 +msgid "" +"[HAL crates](https://github.com/rust-embedded/awesome-embedded-rust#hal-" +"implementation-crates) for many microcontrollers provide wrappers around " +"various peripherals. These generally implement traits from [`embedded-hal`]" +"(https://crates.io/crates/embedded-hal)." +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md:23 +msgid "// Create HAL wrapper for GPIO port 0.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md:40 +msgid "" +"`set_low` and `set_high` are methods on the `embedded_hal` `OutputPin` trait." +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md:41 +msgid "" +"HAL crates exist for many Cortex-M and RISC-V devices, including various " +"STM32, GD32, nRF, NXP, MSP430, AVR and PIC microcontrollers." +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md:1 +msgid "Board support crates" +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md:3 +msgid "" +"Board support crates provide a further level of wrapping for a specific " +"board for convenience." +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md:31 +msgid "" +"In this case the board support crate is just providing more useful names, " +"and a bit of initialisation." +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md:33 +msgid "" +"The crate may also include drivers for some on-board devices outside of the " +"microcontroller itself." +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md:35 +msgid "`microbit-v2` includes a simple driver for the LED matrix." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:1 +msgid "The type state pattern" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:11 +msgid "// let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:19 +msgid "// pin_input.is_high(); // Error, moved.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:33 +msgid "" +"Pins don't implement `Copy` or `Clone`, so only one instance of each can " +"exist. Once a pin is moved out of the port struct nobody else can take it." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:35 +msgid "" +"Changing the configuration of a pin consumes the old pin instance, so you " +"can’t keep use the old instance afterwards." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:37 +msgid "" +"The type of a value indicates the state that it is in: e.g. in this case, " +"the configuration state of a GPIO pin. This encodes the state machine into " +"the type system, and ensures that you don't try to use a pin in a certain " +"way without properly configuring it first. Illegal state transitions are " +"caught at compile time." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:42 +msgid "" +"You can call `is_high` on an input pin and `set_high` on an output pin, but " +"not vice-versa." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md:44 +msgid "Many HAL crates follow this pattern." +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:3 +msgid "" +"The [`embedded-hal`](https://crates.io/crates/embedded-hal) crate provides a " +"number of traits covering common microcontroller peripherals." +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:6 +msgid "GPIO" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:7 +msgid "ADC" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:8 +msgid "I2C, SPI, UART, CAN" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:9 +msgid "RNG" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:10 +msgid "Timers" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:11 +msgid "Watchdogs" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:13 +msgid "" +"Other crates then implement [drivers](https://github.com/rust-embedded/" +"awesome-embedded-rust#driver-crates) in terms of these traits, e.g. an " +"accelerometer driver might need an I2C or SPI bus implementation." +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:20 +msgid "" +"There are implementations for many microcontrollers, as well as other " +"platforms such as Linux on Raspberry Pi." +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md:22 +msgid "" +"There is work in progress on an `async` version of `embedded-hal`, but it " +"isn't stable yet." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:3 +msgid "" +"[probe-rs](https://probe.rs/) is a handy toolset for embedded debugging, " +"like OpenOCD but better integrated." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:6 +msgid "" +"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:7 +msgid "GDB stub and Microsoft DAP (Debug Adapter Protocol) server" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:8 +msgid "Cargo integration" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:10 +msgid "" +"`cargo-embed` is a cargo subcommand to build and flash binaries, log RTT " +"(Real Time Transfers) output and connect GDB. It's configured by an `Embed." +"toml` file in your project directory." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:16 +msgid "" +"[CMSIS-DAP](https://arm-software.github.io/CMSIS_5/DAP/html/index.html) is " +"an Arm standard protocol over USB for an in-circuit debugger to access the " +"CoreSight Debug Access Port of various Arm Cortex processors. It's what the " +"on-board debugger on the BBC micro:bit uses." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:20 +msgid "" +"ST-Link is a range of in-circuit debuggers from ST Microelectronics, J-Link " +"is a range from SEGGER." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:22 +msgid "" +"The Debug Access Port is usually either a 5-pin JTAG interface or 2-pin " +"Serial Wire Debug." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:24 +msgid "" +"probe-rs is a library which you can integrate into your own tools if you " +"want to." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:26 +msgid "" +"The [Microsoft Debug Adapter Protocol](https://microsoft.github.io/debug-" +"adapter-protocol/) lets VSCode and other IDEs debug code running on any " +"supported microcontroller." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:30 +msgid "cargo-embed is a binary built using the probe-rs library." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md:31 +msgid "" +"RTT (Real Time Transfers) is a mechanism to transfer data between the debug " +"host and the target through a number of ringbuffers." +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md:3 +msgid "_Embed.toml_:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md:15 +msgid "In one terminal under `src/bare-metal/microcontrollers/examples/`:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md:23 +msgid "In another terminal in the same directory:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md:25 +msgid "On gLinux or Debian:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md:43 +msgid "In GDB, try running:" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:1 +#: src/bare-metal/aps/other-projects.md:1 +msgid "Other projects" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:3 +msgid "[RTIC](https://rtic.rs/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:4 +msgid "\"Real-Time Interrupt-driven Concurrency\"" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:5 +msgid "" +"Shared resource management, message passing, task scheduling, timer queue" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:6 +msgid "[Embassy](https://embassy.dev/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:7 +msgid "`async` executors with priorities, timers, networking, USB" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:8 +msgid "[TockOS](https://www.tockos.org/documentation/getting-started)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:9 +msgid "" +"Security-focused RTOS with preemptive scheduling and Memory Protection Unit " +"support" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:11 +msgid "[Hubris](https://hubris.oxide.computer/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:12 +msgid "" +"Microkernel RTOS from Oxide Computer Company with memory protection, " +"unprivileged drivers, IPC" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:14 +msgid "[Bindings for FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:15 +msgid "" +"Some platforms have `std` implementations, e.g. [esp-idf](https://esp-rs." +"github.io/book/overview/using-the-standard-library.html)." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:20 +msgid "RTIC can be considered either an RTOS or a concurrency framework." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:21 +msgid "It doesn't include any HALs." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:22 +msgid "" +"It uses the Cortex-M NVIC (Nested Virtual Interrupt Controller) for " +"scheduling rather than a proper kernel." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:24 +msgid "Cortex-M only." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:25 +msgid "" +"Google uses TockOS on the Haven microcontroller for Titan security keys." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md:26 +msgid "" +"FreeRTOS is mostly written in C, but there are Rust bindings for writing " +"applications." +msgstr "" + +#: src/exercises/bare-metal/morning.md:3 +msgid "" +"We will read the direction from an I2C compass, and log the readings to a " +"serial port." +msgstr "" + +#: src/exercises/bare-metal/morning.md:8 +#: src/exercises/concurrency/morning.md:12 +#, fuzzy +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"morning.md) provided." +msgstr "读完习题后，可以阅读本书提供的 \\[题解\\]。" + +#: src/exercises/bare-metal/compass.md:3 +msgid "" +"We will read the direction from an I2C compass, and log the readings to a " +"serial port. If you have time, try displaying it on the LEDs somehow too, or " +"use the buttons somehow." +msgstr "" + +#: src/exercises/bare-metal/compass.md:7 +msgid "Hints:" +msgstr "" + +#: src/exercises/bare-metal/compass.md:9 +msgid "" +"Check the documentation for the [`lsm303agr`](https://docs.rs/lsm303agr/" +"latest/lsm303agr/) and [`microbit-v2`](https://docs.rs/microbit-v2/latest/" +"microbit/) crates, as well as the [micro:bit hardware](https://tech.microbit." +"org/hardware/)." +msgstr "" + +#: src/exercises/bare-metal/compass.md:13 +msgid "" +"The LSM303AGR Inertial Measurement Unit is connected to the internal I2C bus." +msgstr "" + +#: src/exercises/bare-metal/compass.md:14 +msgid "" +"TWI is another name for I2C, so the I2C master peripheral is called TWIM." +msgstr "" + +#: src/exercises/bare-metal/compass.md:15 +msgid "" +"The LSM303AGR driver needs something implementing the `embedded_hal::" +"blocking::i2c::WriteRead` trait. The [`microbit::hal::Twim`](https://docs.rs/" +"microbit-v2/latest/microbit/hal/struct.Twim.html) struct implements this." +msgstr "" + +#: src/exercises/bare-metal/compass.md:19 +msgid "" +"You have a [`microbit::Board`](https://docs.rs/microbit-v2/latest/microbit/" +"struct.Board.html) struct with fields for the various pins and peripherals." +msgstr "" + +#: src/exercises/bare-metal/compass.md:22 +msgid "" +"You can also look at the [nRF52833 datasheet](https://infocenter.nordicsemi." +"com/pdf/nRF52833_PS_v1.5.pdf) if you want, but it shouldn't be necessary for " +"this exercise." +msgstr "" + +#: src/exercises/bare-metal/compass.md:26 +msgid "" +"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " +"look in the `compass` directory for the following files." +msgstr "" + +#: src/exercises/bare-metal/compass.md:29 src/exercises/bare-metal/rtc.md:22 +#, fuzzy +msgid "_src/main.rs_:" +msgstr "_hello_rust/src/main.rs_:" + +#: src/exercises/bare-metal/compass.md:47 +#: src/exercises/bare-metal/solutions-morning.md:32 +msgid "// Configure serial port.\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md:55 +msgid "" +"// Set up the I2C controller and Inertial Measurement Unit.\n" +" // TODO\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md:58 +#: src/exercises/bare-metal/solutions-morning.md:56 +msgid "\"Ready.\"" +msgstr "" + +#: src/exercises/bare-metal/compass.md:61 +msgid "" +"// Read compass data and log it to the serial port.\n" +" // TODO\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md:67 src/exercises/bare-metal/rtc.md:387 +msgid "_Cargo.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md:89 +msgid "_Embed.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md:105 src/exercises/bare-metal/rtc.md:988 +msgid "_.cargo/config.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md:118 +msgid "See the serial output on Linux with:" +msgstr "" + +#: src/exercises/bare-metal/compass.md:126 +msgid "" +"Or on Mac OS something like (the device name may be slightly different):" +msgstr "" + +#: src/exercises/bare-metal/compass.md:134 +msgid "Use Ctrl+A Ctrl+Q to quit picocom." +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:1 +msgid "Bare Metal Rust Morning Exercise" +msgstr "裸机 Rust 上午练习" + +#: src/exercises/bare-metal/solutions-morning.md:5 +msgid "([back to exercise](compass.md))" +msgstr "([返回练习](compass.md))" + +#: src/exercises/bare-metal/solutions-morning.md:40 +msgid "// Set up the I2C controller and Inertial Measurement Unit.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:41 +msgid "\"Setting up IMU...\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:49 +msgid "// Set up display and timer.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:59 +msgid "// Read compass data and log it to the serial port.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:67 +msgid "\"{},{},{}\\t{},{},{}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:105 +msgid "" +"// If button A is pressed, switch to the next mode and briefly blink all " +"LEDs\n" +" // on.\n" +msgstr "" + +#: src/bare-metal/aps.md:1 +msgid "Application processors" +msgstr "" + +#: src/bare-metal/aps.md:3 +msgid "" +"So far we've talked about microcontrollers, such as the Arm Cortex-M series. " +"Now let's try writing something for Cortex-A. For simplicity we'll just work " +"with QEMU's aarch64 ['virt'](https://qemu-project.gitlab.io/qemu/system/arm/" +"virt.html) board." +msgstr "" + +#: src/bare-metal/aps.md:10 +msgid "" +"Broadly speaking, microcontrollers don't have an MMU or multiple levels of " +"privilege (exception levels on Arm CPUs, rings on x86), while application " +"processors do." +msgstr "" + +#: src/bare-metal/aps.md:13 +msgid "" +"QEMU supports emulating various different machines or board models for each " +"architecture. The 'virt' board doesn't correspond to any particular real " +"hardware, but is designed purely for virtual machines." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:3 +msgid "" +"Before we can start running Rust code, we need to do some initialisation." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:5 +msgid "" +"```armasm\n" +".section .init.entry, \"ax\"\n" +".global entry\n" +"entry:\n" +" /*\n" +" * Load and apply the memory management configuration, ready to enable " +"MMU and\n" +" * caches.\n" +" */\n" +" adrp x30, idmap\n" +" msr ttbr0_el1, x30\n" +"\n" +" mov_i x30, .Lmairval\n" +" msr mair_el1, x30\n" +"\n" +" mov_i x30, .Ltcrval\n" +" /* Copy the supported PA range into TCR_EL1.IPS. */\n" +" mrs x29, id_aa64mmfr0_el1\n" +" bfi x30, x29, #32, #4\n" +"\n" +" msr tcr_el1, x30\n" +"\n" +" mov_i x30, .Lsctlrval\n" +"\n" +" /*\n" +" * Ensure everything before this point has completed, then invalidate " +"any\n" +" * potentially stale local TLB entries before they start being used.\n" +" */\n" +" isb\n" +" tlbi vmalle1\n" +" ic iallu\n" +" dsb nsh\n" +" isb\n" +"\n" +" /*\n" +" * Configure sctlr_el1 to enable MMU and cache and don't proceed until " +"this\n" +" * has completed.\n" +" */\n" +" msr sctlr_el1, x30\n" +" isb\n" +"\n" +" /* Disable trapping floating point access in EL1. */\n" +" mrs x30, cpacr_el1\n" +" orr x30, x30, #(0x3 << 20)\n" +" msr cpacr_el1, x30\n" +" isb\n" +"\n" +" /* Zero out the bss section. */\n" +" adr_l x29, bss_begin\n" +" adr_l x30, bss_end\n" +"0: cmp x29, x30\n" +" b.hs 1f\n" +" stp xzr, xzr, [x29], #16\n" +" b 0b\n" +"\n" +"1: /* Prepare the stack. */\n" +" adr_l x30, boot_stack_end\n" +" mov sp, x30\n" +"\n" +" /* Set up exception vector. */\n" +" adr x30, vector_table_el1\n" +" msr vbar_el1, x30\n" +"\n" +" /* Call into Rust code. */\n" +" bl main\n" +"\n" +" /* Loop forever waiting for interrupts. */\n" +"2: wfi\n" +" b 2b\n" +"```" +msgstr "" + +#: src/bare-metal/aps/entry-point.md:77 +msgid "" +"This is the same as it would be for C: initialising the processor state, " +"zeroing the BSS, and setting up the stack pointer." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:79 +msgid "" +"The BSS (block starting symbol, for historical reasons) is the part of the " +"object file which containing statically allocated variables which are " +"initialised to zero. They are omitted from the image, to avoid wasting space " +"on zeroes. The compiler assumes that the loader will take care of zeroing " +"them." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:84 +msgid "" +"The BSS may already be zeroed, depending on how memory is initialised and " +"the image is loaded, but we zero it to be sure." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:86 +msgid "" +"We need to enable the MMU and cache before reading or writing any memory. If " +"we don't:" +msgstr "" + +#: src/bare-metal/aps/entry-point.md:88 +msgid "" +"Unaligned accesses will fault. We build the Rust code for the `aarch64-" +"unknown-none` target which sets `+strict-align` to prevent the compiler " +"generating unaligned accesses, so it should be fine in this case, but this " +"is not necessarily the case in general." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:92 +msgid "" +"If it were running in a VM, this can lead to cache coherency issues. The " +"problem is that the VM is accessing memory directly with the cache disabled, " +"while the host has cacheable aliases to the same memory. Even if the host " +"doesn't explicitly access the memory, speculative accesses can lead to cache " +"fills, and then changes from one or the other will get lost when the cache " +"is cleaned or the VM enables the cache. (Cache is keyed by physical address, " +"not VA or IPA.)" +msgstr "" + +#: src/bare-metal/aps/entry-point.md:99 +msgid "" +"For simplicity, we just use a hardcoded pagetable (see `idmap.S`) which " +"identity maps the first 1 GiB of address space for devices, the next 1 GiB " +"for DRAM, and another 1 GiB higher up for more devices. This matches the " +"memory layout that QEMU uses." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:103 +msgid "" +"We also set up the exception vector (`vbar_el1`), which we'll see more about " +"later." +msgstr "" + +#: src/bare-metal/aps/entry-point.md:105 +msgid "" +"All examples this afternoon assume we will be running at exception level 1 " +"(EL1). If you need to run at a different exception level you'll need to " +"modify `entry.S` accordingly." +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:1 +msgid "Inline assembly" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:3 +msgid "" +"Sometimes we need to use assembly to do things that aren't possible with " +"Rust code. For example, to make an HVC (hypervisor call) to tell the " +"firmware to power off the system:" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:20 +msgid "" +"// Safe because this only uses the declared registers and doesn't do\n" +" // anything with memory.\n" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:23 +msgid "\"hvc #0\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:24 +msgid "\"w0\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:25 +msgid "\"w1\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:26 +msgid "\"w2\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:27 +msgid "\"w3\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:28 +msgid "\"w4\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:29 +msgid "\"w5\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:30 +msgid "\"w6\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:31 +msgid "\"w7\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:40 +msgid "" +"(If you actually want to do this, use the [`smccc`](https://crates.io/crates/" +"smccc) crate which has wrappers for all these functions.)" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:45 +msgid "" +"PSCI is the Arm Power State Coordination Interface, a standard set of " +"functions to manage system and CPU power states, among other things. It is " +"implemented by EL3 firmware and hypervisors on many systems." +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:48 +msgid "" +"The `0 => _` syntax means initialise the register to 0 before running the " +"inline assembly code, and ignore its contents afterwards. We need to use " +"`inout` rather than `in` because the call could potentially clobber the " +"contents of the registers." +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:52 +msgid "" +"This `main` function needs to be `#[no_mangle]` and `extern \"C\"` because " +"it is called from our entry point in `entry.S`." +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:54 +msgid "" +"`_x0`–`_x3` are the values of registers `x0`–`x3`, which are conventionally " +"used by the bootloader to pass things like a pointer to the device tree. " +"According to the standard aarch64 calling convention (which is what `extern " +"\"C\"` specifies to use), registers `x0`–`x7` are used for the first 8 " +"arguments passed to a function, so `entry.S` doesn't need to do anything " +"special except make sure it doesn't change these registers." +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md:60 +msgid "" +"Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/mmio.md:1 +msgid "Volatile memory access for MMIO" +msgstr "" + +#: src/bare-metal/aps/mmio.md:3 +msgid "Use `pointer::read_volatile` and `pointer::write_volatile`." +msgstr "" + +#: src/bare-metal/aps/mmio.md:4 +msgid "Never hold a reference." +msgstr "" + +#: src/bare-metal/aps/mmio.md:5 +msgid "" +"`addr_of!` lets you get fields of structs without creating an intermediate " +"reference." +msgstr "" + +#: src/bare-metal/aps/mmio.md:10 +msgid "" +"Volatile access: read or write operations may have side-effects, so prevent " +"the compiler or hardware from reordering, duplicating or eliding them." +msgstr "" + +#: src/bare-metal/aps/mmio.md:12 +msgid "" +"Usually if you write and then read, e.g. via a mutable reference, the " +"compiler may assume that the value read is the same as the value just " +"written, and not bother actually reading memory." +msgstr "" + +#: src/bare-metal/aps/mmio.md:15 +msgid "" +"Some existing crates for volatile access to hardware do hold references, but " +"this is unsound. Whenever a reference exist, the compiler may choose to " +"dereference it." +msgstr "" + +#: src/bare-metal/aps/mmio.md:18 +msgid "" +"Use the `addr_of!` macro to get struct field pointers from a pointer to the " +"struct." +msgstr "" + +#: src/bare-metal/aps/uart.md:1 +msgid "Let's write a UART driver" +msgstr "" + +#: src/bare-metal/aps/uart.md:3 +msgid "" +"The QEMU 'virt' machine has a [PL011](https://developer.arm.com/" +"documentation/ddi0183/g) UART, so let's write a driver for that." +msgstr "" + +#: src/bare-metal/aps/uart.md:9 +msgid "/// Minimal driver for a PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:17 src/bare-metal/aps/better-uart/driver.md:13 +msgid "" +"/// Constructs a new instance of the UART driver for a PL011 device at the\n" +" /// given base address.\n" +" ///\n" +" /// # Safety\n" +" ///\n" +" /// The given base address must point to the 8 MMIO control registers of " +"a\n" +" /// PL011 device, which must be mapped into the address space of the " +"process\n" +" /// as device memory and not have any other aliases.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:29 src/bare-metal/aps/better-uart/driver.md:25 +#: src/exercises/bare-metal/rtc.md:337 +msgid "/// Writes a single byte to the UART.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:31 src/bare-metal/aps/better-uart/driver.md:27 +#: src/exercises/bare-metal/rtc.md:339 +msgid "// Wait until there is room in the TX buffer.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:34 src/bare-metal/aps/uart.md:46 +msgid "" +"// Safe because we know that the base address points to the control\n" +" // registers of a PL011 device which is appropriately mapped.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:37 src/bare-metal/aps/better-uart/driver.md:33 +#: src/exercises/bare-metal/rtc.md:345 +msgid "// Write to the TX buffer.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:41 src/bare-metal/aps/better-uart/driver.md:37 +#: src/exercises/bare-metal/rtc.md:349 +msgid "// Wait until the UART is no longer busy.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md:55 +msgid "" +"Note that `Uart::new` is unsafe while the other methods are safe. This is " +"because as long as the caller of `Uart::new` guarantees that its safety " +"requirements are met (i.e. that there is only ever one instance of the " +"driver for a given UART, and nothing else aliasing its address space), then " +"it is always safe to call `write_byte` later because we can assume the " +"necessary preconditions." +msgstr "" + +#: src/bare-metal/aps/uart.md:61 +msgid "" +"We could have done it the other way around (making `new` safe but " +"`write_byte` unsafe), but that would be much less convenient to use as every " +"place that calls `write_byte` would need to reason about the safety" +msgstr "" + +#: src/bare-metal/aps/uart.md:64 +msgid "" +"This is a common pattern for writing safe wrappers of unsafe code: moving " +"the burden of proof for soundness from a large number of places to a smaller " +"number of places." +msgstr "" + +#: src/bare-metal/aps/uart/traits.md:1 +msgid "More traits" +msgstr "" + +#: src/bare-metal/aps/uart/traits.md:3 +msgid "" +"We derived the `Debug` trait. It would be useful to implement a few more " +"traits too." +msgstr "" + +#: src/bare-metal/aps/uart/traits.md:17 src/exercises/bare-metal/rtc.md:381 +#: src/exercises/bare-metal/solutions-afternoon.md:223 +msgid "" +"// Safe because it just contains a pointer to device memory, which can be\n" +"// accessed from any context.\n" +msgstr "" + +#: src/bare-metal/aps/uart/traits.md:25 +msgid "" +"Implementing `Write` lets us use the `write!` and `writeln!` macros with our " +"`Uart` type." +msgstr "" + +#: src/bare-metal/aps/uart/traits.md:27 +msgid "" +"Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/better-uart.md:1 +msgid "A better UART driver" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:3 +msgid "" +"The PL011 actually has [a bunch more registers](https://developer.arm.com/" +"documentation/ddi0183/g/programmers-model/summary-of-registers), and adding " +"offsets to construct pointers to access them is error-prone and hard to " +"read. Plus, some of them are bit fields which would be nice to access in a " +"structured way." +msgstr "" + +#: src/bare-metal/aps/better-uart.md:7 +msgid "Offset" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:7 +msgid "Register name" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:7 +msgid "Width" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:9 +msgid "0x00" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:9 +msgid "DR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:9 +msgid "12" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:10 +msgid "0x04" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:10 +msgid "RSR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:11 +msgid "0x18" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:11 +msgid "FR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:11 +msgid "9" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:12 +msgid "0x20" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:12 +msgid "ILPR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:13 +msgid "0x24" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:13 +msgid "IBRD" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:13 src/bare-metal/aps/better-uart.md:16 +msgid "16" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:14 +msgid "0x28" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:14 +msgid "FBRD" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:15 +msgid "0x2c" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:15 +msgid "LCR_H" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:16 +msgid "0x30" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:16 +msgid "CR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:17 +msgid "0x34" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:17 +msgid "IFLS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:18 +msgid "0x38" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:18 +msgid "IMSC" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:18 src/bare-metal/aps/better-uart.md:19 +#: src/bare-metal/aps/better-uart.md:20 src/bare-metal/aps/better-uart.md:21 +msgid "11" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:19 +msgid "0x3c" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:19 +msgid "RIS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:20 +msgid "0x40" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:20 +msgid "MIS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:21 +msgid "0x44" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:21 +msgid "ICR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:22 +msgid "0x48" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:22 +msgid "DMACR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md:26 +msgid "There are also some ID registers which have been omitted for brevity." +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:3 +msgid "" +"The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " +"working with bitflags." +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:10 +#: src/exercises/bare-metal/rtc.md:241 +msgid "/// Flags from the UART flag register.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:14 +#: src/exercises/bare-metal/rtc.md:245 +msgid "/// Clear to send.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:16 +#: src/exercises/bare-metal/rtc.md:247 +msgid "/// Data set ready.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:18 +#: src/exercises/bare-metal/rtc.md:249 +msgid "/// Data carrier detect.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:20 +#: src/exercises/bare-metal/rtc.md:251 +msgid "/// UART busy transmitting data.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:22 +#: src/exercises/bare-metal/rtc.md:253 +msgid "/// Receive FIFO is empty.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:24 +#: src/exercises/bare-metal/rtc.md:255 +msgid "/// Transmit FIFO is full.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:26 +#: src/exercises/bare-metal/rtc.md:257 +msgid "/// Receive FIFO is full.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:28 +#: src/exercises/bare-metal/rtc.md:259 +msgid "/// Transmit FIFO is empty.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:30 +#: src/exercises/bare-metal/rtc.md:261 +msgid "/// Ring indicator.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md:38 +msgid "" +"The `bitflags!` macro creates a newtype something like `Flags(u16)`, along " +"with a bunch of method implementations to get and set flags." +msgstr "" + +#: src/bare-metal/aps/better-uart/registers.md:1 +msgid "Multiple registers" +msgstr "" + +#: src/bare-metal/aps/better-uart/registers.md:3 +msgid "" +"We can use a struct to represent the memory layout of the UART's registers." +msgstr "" + +#: src/bare-metal/aps/better-uart/registers.md:43 +msgid "" +"[`#[repr(C)]`](https://doc.rust-lang.org/reference/type-layout.html#the-c-" +"representation) tells the compiler to lay the struct fields out in order, " +"following the same rules as C. This is necessary for our struct to have a " +"predictable layout, as default Rust representation allows the compiler to " +"(among other things) reorder fields however it sees fit." +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:3 +msgid "Now let's use the new `Registers` struct in our driver." +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:6 +msgid "/// Driver for a PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:30 +#: src/bare-metal/aps/better-uart/driver.md:54 +#: src/exercises/bare-metal/rtc.md:342 src/exercises/bare-metal/rtc.md:366 +msgid "" +"// Safe because we know that self.registers points to the control\n" +" // registers of a PL011 device which is appropriately mapped.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:41 +#: src/exercises/bare-metal/rtc.md:353 +msgid "" +"/// Reads and returns a pending byte, or `None` if nothing has been\n" +" /// received.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:48 +#: src/exercises/bare-metal/rtc.md:360 +msgid "// TODO: Check for error conditions in bits 8-11.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md:63 +msgid "" +"Note the use of `addr_of!` / `addr_of_mut!` to get pointers to individual " +"fields without creating an intermediate reference, which would be unsound." +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:1 +#: src/bare-metal/aps/logging/using.md:1 +msgid "Using it" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:3 +msgid "" +"Let's write a small program using our driver to write to the serial console, " +"and echo incoming bytes." +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:19 +#: src/bare-metal/aps/logging/using.md:18 src/exercises/bare-metal/rtc.md:44 +#: src/exercises/bare-metal/solutions-afternoon.md:33 +msgid "/// Base address of the primary PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:25 +#: src/bare-metal/aps/logging/using.md:24 src/exercises/bare-metal/rtc.md:50 +#: src/exercises/bare-metal/solutions-afternoon.md:44 +msgid "" +"// Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 device,\n" +" // and nothing else accesses that address range.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:29 +#: src/bare-metal/aps/logging/using.md:29 +msgid "\"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\"" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:35 +msgid "b'\\r'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:36 +#: src/async/pitfalls/cancellation.md:27 +msgid "b'\\n'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:38 +msgid "b'q'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:44 +msgid "\"Bye!\"" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:51 +msgid "" +"As in the [inline assembly](../inline-assembly.md) example, this `main` " +"function is called from our entry point code in `entry.S`. See the speaker " +"notes there for details." +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md:54 +msgid "" +"Run the example in QEMU with `make qemu` under `src/bare-metal/aps/examples`." +msgstr "" + +#: src/bare-metal/aps/logging.md:3 +msgid "" +"It would be nice to be able to use the logging macros from the [`log`]" +"(https://crates.io/crates/log) crate. We can do this by implementing the " +"`Log` trait." +msgstr "" + +#: src/bare-metal/aps/logging.md:26 src/exercises/bare-metal/rtc.md:193 +msgid "\"[{}] {}\"" +msgstr "" + +#: src/bare-metal/aps/logging.md:35 src/exercises/bare-metal/rtc.md:202 +msgid "/// Initialises UART logger.\n" +msgstr "" + +#: src/bare-metal/aps/logging.md:48 +msgid "" +"The unwrap in `log` is safe because we initialise `LOGGER` before calling " +"`set_logger`." +msgstr "" + +#: src/bare-metal/aps/logging/using.md:3 +msgid "We need to initialise the logger before we use it." +msgstr "" + +#: src/bare-metal/aps/logging/using.md:38 src/exercises/bare-metal/rtc.md:72 +#: src/exercises/bare-metal/solutions-afternoon.md:115 +msgid "\"{info}\"" +msgstr "" + +#: src/bare-metal/aps/logging/using.md:46 +msgid "Note that our panic handler can now log details of panics." +msgstr "" + +#: src/bare-metal/aps/logging/using.md:47 +msgid "" +"Run the example in QEMU with `make qemu_logger` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/exceptions.md:3 +msgid "" +"AArch64 defines an exception vector table with 16 entries, for 4 types of " +"exceptions (synchronous, IRQ, FIQ, SError) from 4 states (current EL with " +"SP0, current EL with SPx, lower EL using AArch64, lower EL using AArch32). " +"We implement this in assembly to save volatile registers to the stack before " +"calling into Rust code:" +msgstr "" + +#: src/bare-metal/aps/exceptions.md:67 +msgid "EL is exception level; all our examples this afternoon run in EL1." +msgstr "" + +#: src/bare-metal/aps/exceptions.md:68 +msgid "" +"For simplicity we aren't distinguishing between SP0 and SPx for the current " +"EL exceptions, or between AArch32 and AArch64 for the lower EL exceptions." +msgstr "" + +#: src/bare-metal/aps/exceptions.md:70 +msgid "" +"For this example we just log the exception and power down, as we don't " +"expect any of them to actually happen." +msgstr "" + +#: src/bare-metal/aps/exceptions.md:72 +msgid "" +"We can think of exception handlers and our main execution context more or " +"less like different threads. [`Send` and `Sync`](../../concurrency/send-sync." +"md) will control what we can share between them, just like with threads. For " +"example, if we want to share some value between exception handlers and the " +"rest of the program, and it's `Send` but not `Sync`, then we'll need to wrap " +"it in something like a `Mutex` and put it in a static." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:3 +msgid "[oreboot](https://github.com/oreboot/oreboot)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:4 +msgid "\"coreboot without the C\"" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:5 +msgid "Supports x86, aarch64 and RISC-V." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:6 +msgid "Relies on LinuxBoot rather than having many drivers itself." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:7 +msgid "" +"[Rust RaspberryPi OS tutorial](https://github.com/rust-embedded/rust-" +"raspberrypi-OS-tutorials)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:8 +msgid "" +"Initialisation, UART driver, simple bootloader, JTAG, exception levels, " +"exception handling, page tables" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:10 +msgid "" +"Some dodginess around cache maintenance and initialisation in Rust, not " +"necessarily a good example to copy for production code." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:12 +msgid "[`cargo-call-stack`](https://crates.io/crates/cargo-call-stack)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:13 +msgid "Static analysis to determine maximum stack usage." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:17 +msgid "" +"The RaspberryPi OS tutorial runs Rust code before the MMU and caches are " +"enabled. This will read and write memory (e.g. the stack). However:" +msgstr "" + +#: src/bare-metal/aps/other-projects.md:19 +msgid "" +"Without the MMU and cache, unaligned accesses will fault. It builds with " +"`aarch64-unknown-none` which sets `+strict-align` to prevent the compiler " +"generating unaligned accesses so it should be alright, but this is not " +"necessarily the case in general." +msgstr "" + +#: src/bare-metal/aps/other-projects.md:23 +msgid "" +"If it were running in a VM, this can lead to cache coherency issues. The " +"problem is that the VM is accessing memory directly with the cache disabled, " +"while the host has cacheable aliases to the same memory. Even if the host " +"doesn't explicitly access the memory, speculative accesses can lead to cache " +"fills, and then changes from one or the other will get lost. Again this is " +"alright in this particular case (running directly on the hardware with no " +"hypervisor), but isn't a good pattern in general." +msgstr "" + +#: src/bare-metal/useful-crates.md:1 +msgid "Useful crates" +msgstr "实用 crate" + +#: src/bare-metal/useful-crates.md:3 +msgid "" +"We'll go over a few crates which solve some common problems in bare-metal " +"programming." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:3 +msgid "" +"The [`zerocopy`](https://docs.rs/zerocopy/) crate (from Fuchsia) provides " +"traits and macros for safely converting between byte sequences and other " +"types." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:42 +msgid "" +"This is not suitable for MMIO (as it doesn't use volatile reads and writes), " +"but can be useful for working with structures shared with hardware e.g. by " +"DMA, or sent over some external interface." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:48 +msgid "" +"`FromBytes` can be implemented for types for which any byte pattern is " +"valid, and so can safely be converted from an untrusted sequence of bytes." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:50 +msgid "" +"Attempting to derive `FromBytes` for these types would fail, because " +"`RequestType` doesn't use all possible u32 values as discriminants, so not " +"all byte patterns are valid." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:53 +msgid "" +"`zerocopy::byteorder` has types for byte-order aware numeric primitives." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md:54 +msgid "" +"Run the example with `cargo run` under `src/bare-metal/useful-crates/" +"zerocopy-example/`. (It won't run in the Playground because of the crate " +"dependency.)" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:3 +msgid "" +"The [`aarch64-paging`](https://crates.io/crates/aarch64-paging) crate lets " +"you create page tables according to the AArch64 Virtual Memory System " +"Architecture." +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:14 +msgid "// Create a new page table with identity mapping.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:16 +msgid "// Map a 2 MiB region of memory as read-only.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:21 +msgid "// Set `TTBR0_EL1` to activate the page table.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:28 +msgid "" +"For now it only supports EL1, but support for other exception levels should " +"be straightforward to add." +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:30 +msgid "" +"This is used in Android for the [Protected VM Firmware](https://cs.android." +"com/android/platform/superproject/+/master:packages/modules/Virtualization/" +"pvmfw/)." +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md:31 +msgid "" +"There's no easy way to run this example, as it needs to run on real hardware " +"or under QEMU." +msgstr "" + +#: src/bare-metal/useful-crates/buddy_system_allocator.md:3 +msgid "" +"[`buddy_system_allocator`](https://crates.io/crates/buddy_system_allocator) " +"is a third-party crate implementing a basic buddy system allocator. It can " +"be used both for [`LockedHeap`](https://docs.rs/buddy_system_allocator/0.9.0/" +"buddy_system_allocator/struct.LockedHeap.html) implementing [`GlobalAlloc`]" +"(https://doc.rust-lang.org/core/alloc/trait.GlobalAlloc.html) so you can use " +"the standard `alloc` crate (as we saw [before](../alloc.md)), or for " +"allocating other address space. For example, we might want to allocate MMIO " +"space for PCI BARs:" +msgstr "" + +#: src/bare-metal/useful-crates/buddy_system_allocator.md:29 +msgid "PCI BARs always have alignment equal to their size." +msgstr "" + +#: src/bare-metal/useful-crates/buddy_system_allocator.md:30 +msgid "" +"Run the example with `cargo run` under `src/bare-metal/useful-crates/" +"allocator-example/`. (It won't run in the Playground because of the crate " +"dependency.)" +msgstr "" + +#: src/bare-metal/useful-crates/tinyvec.md:3 +msgid "" +"Sometimes you want something which can be resized like a `Vec`, but without " +"heap allocation. [`tinyvec`](https://crates.io/crates/tinyvec) provides " +"this: a vector backed by an array or slice, which could be statically " +"allocated or on the stack, which keeps track of how many elements are used " +"and panics if you try to use more than are allocated." +msgstr "" + +#: src/bare-metal/useful-crates/tinyvec.md:25 +msgid "" +"`tinyvec` requires that the element type implement `Default` for " +"initialisation." +msgstr "" + +#: src/bare-metal/useful-crates/tinyvec.md:27 +msgid "" +"The Rust Playground includes `tinyvec`, so this example will run fine inline." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:3 +msgid "" +"`std::sync::Mutex` and the other synchronisation primitives from `std::sync` " +"are not available in `core` or `alloc`. How can we manage synchronisation or " +"interior mutability, such as for sharing state between different CPUs?" +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:7 +msgid "" +"The [`spin`](https://crates.io/crates/spin) crate provides spinlock-based " +"equivalents of many of these primitives." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:26 +msgid "Be careful to avoid deadlock if you take locks in interrupt handlers." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:27 +msgid "" +"`spin` also has a ticket lock mutex implementation; equivalents of `RwLock`, " +"`Barrier` and `Once` from `std::sync`; and `Lazy` for lazy initialisation." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:29 +msgid "" +"The [`once_cell`](https://crates.io/crates/once_cell) crate also has some " +"useful types for late initialisation with a slightly different approach to " +"`spin::once::Once`." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md:31 +msgid "" +"The Rust Playground includes `spin`, so this example will run fine inline." +msgstr "" + +#: src/bare-metal/android.md:3 +msgid "" +"To build a bare-metal Rust binary in AOSP, you need to use a " +"`rust_ffi_static` Soong rule to build your Rust code, then a `cc_binary` " +"with a linker script to produce the binary itself, and then a `raw_binary` " +"to convert the ELF to a raw binary ready to be run." +msgstr "" + +#: src/bare-metal/android/vmbase.md:1 +msgid "vmbase" +msgstr "vmbase" + +#: src/bare-metal/android/vmbase.md:3 +msgid "" +"For VMs running under crosvm on aarch64, the [vmbase](https://android." +"googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/" +"master/vmbase/) library provides a linker script and useful defaults for the " +"build rules, along with an entry point, UART console logging and more." +msgstr "" + +#: src/bare-metal/android/vmbase.md:24 +msgid "" +"The `main!` macro marks your main function, to be called from the `vmbase` " +"entry point." +msgstr "" + +#: src/bare-metal/android/vmbase.md:26 +msgid "" +"The `vmbase` entry point handles console initialisation, and issues a " +"PSCI_SYSTEM_OFF to shutdown the VM if your main function returns." +msgstr "" + +#: src/exercises/bare-metal/afternoon.md:3 +msgid "We will write a driver for the PL031 real-time clock device." +msgstr "" + +#: src/exercises/bare-metal/afternoon.md:7 +#: src/exercises/concurrency/afternoon.md:13 +#, fuzzy +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"afternoon.md) provided." +msgstr "读完习题后，可以阅读本书提供的 \\[题解\\]。" + +#: src/exercises/bare-metal/rtc.md:1 +#: src/exercises/bare-metal/solutions-afternoon.md:3 +msgid "RTC driver" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:3 +msgid "" +"The QEMU aarch64 virt machine has a [PL031](https://developer.arm.com/" +"documentation/ddi0224/c) real-time clock at 0x9010000. For this exercise, " +"you should write a driver for it." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:6 +msgid "" +"Use it to print the current time to the serial console. You can use the " +"[`chrono`](https://crates.io/crates/chrono) crate for date/time formatting." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:8 +msgid "" +"Use the match register and raw interrupt status to busy-wait until a given " +"time, e.g. 3 seconds in the future. (Call [`core::hint::spin_loop`](https://" +"doc.rust-lang.org/core/hint/fn.spin_loop.html) inside the loop.)" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:11 +msgid "" +"_Extension if you have time:_ Enable and handle the interrupt generated by " +"the RTC match. You can use the driver provided in the [`arm-gic`](https://" +"docs.rs/arm-gic/) crate to configure the Arm Generic Interrupt Controller." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:14 +msgid "Use the RTC interrupt, which is wired to the GIC as `IntId::spi(2)`." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:15 +msgid "" +"Once the interrupt is enabled, you can put the core to sleep via `arm_gic::" +"wfi()`, which will cause the core to sleep until it receives an interrupt." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:19 +msgid "" +"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " +"look in the `rtc` directory for the following files." +msgstr "" + +#: src/exercises/bare-metal/rtc.md:40 +#: src/exercises/bare-metal/solutions-afternoon.md:29 +msgid "/// Base addresses of the GICv3.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:55 +#: src/exercises/bare-metal/solutions-afternoon.md:49 +msgid "\"main({:#x}, {:#x}, {:#x}, {:#x})\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:57 +#: src/exercises/bare-metal/solutions-afternoon.md:51 +msgid "" +"// Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the base\n" +" // addresses of a GICv3 distributor and redistributor respectively, and\n" +" // nothing else accesses those address ranges.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:63 +msgid "// TODO: Create instance of RTC driver and print current time.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:65 +msgid "// TODO: Wait for 3 seconds.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:78 +msgid "" +"_src/exceptions.rs_ (you should only need to change this for the 3rd part of " +"the exercise):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:84 src/exercises/bare-metal/rtc.md:159 +#: src/exercises/bare-metal/rtc.md:218 src/exercises/bare-metal/rtc.md:418 +msgid "" +"// Copyright 2023 Google LLC\n" +"//\n" +"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" +"// you may not use this file except in compliance with the License.\n" +"// You may obtain a copy of the License at\n" +"//\n" +"// http://www.apache.org/licenses/LICENSE-2.0\n" +"//\n" +"// Unless required by applicable law or agreed to in writing, software\n" +"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" +"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" +"// See the License for the specific language governing permissions and\n" +"// limitations under the License.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:105 +msgid "\"sync_exception_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:111 +msgid "\"irq_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:113 +msgid "\"No pending interrupt\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:114 +msgid "\"IRQ {intid:?}\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:119 +msgid "\"fiq_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:125 +msgid "\"serr_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:131 +msgid "\"sync_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:137 +msgid "\"irq_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:143 +msgid "\"fiq_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:149 +msgid "\"serr_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:154 +msgid "_src/logger.rs_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:172 +msgid "// ANCHOR: main\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:213 +msgid "_src/pl011.rs_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:236 +msgid "// ANCHOR: Flags\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:264 +msgid "// ANCHOR_END: Flags\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:268 +msgid "" +"/// Flags from the UART Receive Status Register / Error Clear Register.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:272 +msgid "/// Framing error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:274 +msgid "/// Parity error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:276 +msgid "/// Break error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:278 +msgid "/// Overrun error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:282 +msgid "// ANCHOR: Registers\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:314 +msgid "// ANCHOR_END: Registers\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:316 +msgid "" +"// ANCHOR: Uart\n" +"/// Driver for a PL011 UART.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:325 +msgid "" +"/// Constructs a new instance of the UART driver for a PL011 device at the\n" +" /// given base address.\n" +" ///\n" +" /// # Safety\n" +" ///\n" +" /// The given base address must point to the MMIO control registers of " +"a\n" +" /// PL011 device, which must be mapped into the address space of the " +"process\n" +" /// as device memory and not have any other aliases.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:370 +msgid "// ANCHOR_END: Uart\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:413 +msgid "_build.rs_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:436 src/exercises/bare-metal/rtc.md:438 +msgid "\"linux\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:437 src/exercises/bare-metal/rtc.md:439 +msgid "\"CROSS_COMPILE\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:437 +#, fuzzy +msgid "\"aarch64-linux-gnu\"" +msgstr "aarch64-paging" + +#: src/exercises/bare-metal/rtc.md:439 +msgid "\"aarch64-none-elf\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:442 +msgid "\"entry.S\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:443 +#, fuzzy +msgid "\"exceptions.S\"" +msgstr "异常" + +#: src/exercises/bare-metal/rtc.md:444 +msgid "\"idmap.S\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:445 +msgid "\"empty\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:449 +msgid "_entry.S_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:453 msgid "" "```armasm\n" "/*\n" @@ -16333,11 +16945,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:595 +#: src/exercises/bare-metal/rtc.md:598 msgid "_exceptions.S_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:599 +#: src/exercises/bare-metal/rtc.md:602 msgid "" "```armasm\n" "/*\n" @@ -16531,11 +17143,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:780 +#: src/exercises/bare-metal/rtc.md:783 msgid "_idmap.S_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:784 +#: src/exercises/bare-metal/rtc.md:787 msgid "" "```armasm\n" "/*\n" @@ -16584,11 +17196,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:829 +#: src/exercises/bare-metal/rtc.md:832 msgid "_image.ld_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:833 +#: src/exercises/bare-metal/rtc.md:836 msgid "" "```ld\n" "/*\n" @@ -16699,66 +17311,192 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:940 -msgid "_Makefile_ (you shouldn't need to change this):" +#: src/exercises/bare-metal/rtc.md:943 +msgid "_Makefile_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:948 +msgid "# Copyright 2023 Google LLC" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:962 +msgid "$(shell uname -s)" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:964 +#, fuzzy +msgid "aarch64-linux-gnu" +msgstr "aarch64-paging" + +#: src/exercises/bare-metal/rtc.md:981 +msgid "stdio -display none -kernel $< -s" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:984 +msgid "cargo clean" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:999 +msgid "Run the code in QEMU with `make qemu`." +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:1 +msgid "Bare Metal Rust Afternoon" +msgstr "嵌入式 Rust：进阶篇" + +#: src/exercises/bare-metal/solutions-afternoon.md:5 +msgid "([back to exercise](rtc.md))" +msgstr "([返回练习](rtc.md))" + +#: src/exercises/bare-metal/solutions-afternoon.md:7 +#, fuzzy +msgid "_main.rs_:" +msgstr "`main.rs`:" + +#: src/exercises/bare-metal/solutions-afternoon.md:36 +msgid "/// Base address of the PL031 RTC.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:944 -msgid "" -"```makefile\n" -"# Copyright 2023 Google LLC\n" -"#\n" -"# Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"# you may not use this file except in compliance with the License.\n" -"# You may obtain a copy of the License at\n" -"#\n" -"# http://www.apache.org/licenses/LICENSE-2.0\n" -"#\n" -"# Unless required by applicable law or agreed to in writing, software\n" -"# distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"# See the License for the specific language governing permissions and\n" -"# limitations under the License.\n" -"\n" -"UNAME := $(shell uname -s)\n" -"ifeq ($(UNAME),Linux)\n" -"\tTARGET = aarch64-linux-gnu\n" -"else\n" -"\tTARGET = aarch64-none-elf\n" -"endif\n" -"OBJCOPY = $(TARGET)-objcopy\n" -"\n" -".PHONY: build qemu_minimal qemu qemu_logger\n" -"\n" -"all: rtc.bin\n" -"\n" -"build:\n" -"\tcargo build\n" -"\n" -"rtc.bin: build\n" -"\t$(OBJCOPY) -O binary target/aarch64-unknown-none/debug/rtc $@\n" -"\n" -"qemu: rtc.bin\n" -"\tqemu-system-aarch64 -machine virt,gic-version=3 -cpu max -serial mon:stdio " -"-display none -kernel $< -s\n" -"\n" -"clean:\n" -"\tcargo clean\n" -"\trm -f *.bin\n" -"```" +#: src/exercises/bare-metal/solutions-afternoon.md:38 +msgid "/// The IRQ used by the PL031 RTC.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:989 +#: src/exercises/bare-metal/solutions-afternoon.md:57 msgid "" -"```toml\n" -"[build]\n" -"target = \"aarch64-unknown-none\"\n" -"rustflags = [\"-C\", \"link-arg=-Timage.ld\"]\n" -"```" +"// Safe because `PL031_BASE_ADDRESS` is the base address of a PL031 device,\n" +" // and nothing else accesses that address range.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:995 -msgid "Run the code in QEMU with `make qemu`." +#: src/exercises/bare-metal/solutions-afternoon.md:62 +msgid "\"RTC: {time}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:70 +msgid "// Wait for 3 seconds, without interrupts.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:73 +#: src/exercises/bare-metal/solutions-afternoon.md:91 +msgid "\"Waiting for {}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:75 +#: src/exercises/bare-metal/solutions-afternoon.md:83 +#: src/exercises/bare-metal/solutions-afternoon.md:96 +#: src/exercises/bare-metal/solutions-afternoon.md:104 +msgid "\"matched={}, interrupt_pending={}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:87 +#: src/exercises/bare-metal/solutions-afternoon.md:108 +msgid "\"Finished waiting\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:89 +msgid "// Wait another 3 seconds for an interrupt.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:121 +msgid "_pl031.rs_:" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:128 +msgid "/// Data register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:130 +msgid "/// Match register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:132 +msgid "/// Load register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:134 +msgid "/// Control register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:137 +msgid "/// Interrupt Mask Set or Clear register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:140 +msgid "/// Raw Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:143 +msgid "/// Masked Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:146 +msgid "/// Interrupt Clear Register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:150 +msgid "/// Driver for a PL031 real-time clock.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:158 +msgid "" +"/// Constructs a new instance of the RTC driver for a PL031 device at the\n" +" /// given base address.\n" +" ///\n" +" /// # Safety\n" +" ///\n" +" /// The given base address must point to the MMIO control registers of " +"a\n" +" /// PL031 device, which must be mapped into the address space of the " +"process\n" +" /// as device memory and not have any other aliases.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:170 +msgid "/// Reads the current RTC value.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:172 +#: src/exercises/bare-metal/solutions-afternoon.md:180 +#: src/exercises/bare-metal/solutions-afternoon.md:188 +#: src/exercises/bare-metal/solutions-afternoon.md:199 +#: src/exercises/bare-metal/solutions-afternoon.md:211 +#: src/exercises/bare-metal/solutions-afternoon.md:218 +msgid "" +"// Safe because we know that self.registers points to the control\n" +" // registers of a PL031 device which is appropriately mapped.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:177 +msgid "" +"/// Writes a match value. When the RTC value matches this then an interrupt\n" +" /// will be generated (if it is enabled).\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:185 +msgid "" +"/// Returns whether the match register matches the RTC value, whether or " +"not\n" +" /// the interrupt is enabled.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:194 +msgid "" +"/// Returns whether there is currently an interrupt pending.\n" +" ///\n" +" /// This should be true if and only if `matched` returns true and the\n" +" /// interrupt is masked.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:205 +msgid "" +"/// Sets or clears the interrupt mask.\n" +" ///\n" +" /// When the mask is true the interrupt is enabled; when it is false " +"the\n" +" /// interrupt is disabled.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:216 +msgid "/// Clears a pending interrupt, if any.\n" msgstr "" #: src/concurrency.md:1 @@ -16784,45 +17522,13 @@ msgstr "" msgid "Rust threads work similarly to threads in other languages:" msgstr "Rust 线程的运作方式与其他语言中的线程类似：" -#: src/concurrency/threads.md:5 -msgid "" -"```rust,editable\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" thread::spawn(|| {\n" -" for i in 1..10 {\n" -" println!(\"Count in thread: {i}!\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -" });\n" -"\n" -" for i in 1..5 {\n" -" println!(\"Main thread: {i}\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -"}\n" -"```" +#: src/concurrency/threads.md:12 +msgid "\"Count in thread: {i}!\"" +msgstr "" + +#: src/concurrency/threads.md:18 +msgid "\"Main thread: {i}\"" msgstr "" -"```rust,editable\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" thread::spawn(|| {\n" -" for i in 1..10 {\n" -" println!(\"Count in thread: {i}!\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -" });\n" -"\n" -" for i in 1..5 {\n" -" println!(\"Main thread: {i}\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -"}\n" -"```" #: src/concurrency/threads.md:24 msgid "Threads are all daemon threads, the main thread does not wait for them." @@ -16837,9 +17543,10 @@ msgid "Panics can carry a payload, which can be unpacked with `downcast_ref`." msgstr "紧急警报可以携带载荷，并可以使用 `downcast_ref` 对载荷进行解压缩。" #: src/concurrency/threads.md:32 +#, fuzzy msgid "" -"Notice that the thread is stopped before it reaches 10 — the main thread is " -"not waiting." +"Notice that the thread is stopped before it reaches 10 --- the main thread " +"is not waiting." msgstr "请注意，线程在达到 10 之前就停止了，而主线程并 没有等待。" #: src/concurrency/threads.md:35 @@ -16867,36 +17574,6 @@ msgstr "" msgid "Normal threads cannot borrow from their environment:" msgstr "常规线程不能从它们所处的环境中借用：" -#: src/concurrency/scoped-threads.md:5 -#, fuzzy -msgid "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"\n" -"fn foo() {\n" -" let s = String::from(\"Hello\");\n" -" thread::spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -"}\n" -"\n" -"fn main() {\n" -" foo();\n" -"}\n" -"```" -msgstr "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let s = String::from(\"Hello\");\n" -"\n" -" thread::spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -"}\n" -"```" - #: src/concurrency/scoped-threads.md:20 msgid "" "However, you can use a [scoped thread](https://doc.rust-lang.org/std/thread/" @@ -16905,36 +17582,6 @@ msgstr "" "不过，你可以使用[范围线程](https://doc.rust-lang.org/std/thread/fn.scope." "html)来实现此目的：" -#: src/concurrency/scoped-threads.md:22 -msgid "" -"```rust,editable\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let s = String::from(\"Hello\");\n" -"\n" -" thread::scope(|scope| {\n" -" scope.spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -" });\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let s = String::from(\"Hello\");\n" -"\n" -" thread::scope(|scope| {\n" -" scope.spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -" });\n" -"}\n" -"```" - #: src/concurrency/scoped-threads.md:40 msgid "" "The reason for that is that when the `thread::scope` function completes, all " @@ -16943,7 +17590,7 @@ msgstr "" "其原因在于，在 `thread::scope` 函数完成后，可保证所有线程都已联结在一起，使得" "线程能够返回借用的数据。" -#: src/concurrency/scoped-threads.md:41 +#: src/concurrency/scoped-threads.md:42 msgid "" "Normal Rust borrowing rules apply: you can either borrow mutably by one " "thread, or immutably by any number of threads." @@ -16959,45 +17606,10 @@ msgstr "" "Rust 通道（Channel）包含两个部分：`Sender` 和 `Receiver`。这两个部分 通" "过通道进行连接，但你只能看到端点。" -#: src/concurrency/channels.md:6 -#, fuzzy -msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" tx.send(10).unwrap();\n" -" tx.send(20).unwrap();\n" -"\n" -" println!(\"Received: {:?}\", rx.recv());\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"\n" -" let tx2 = tx.clone();\n" -" tx2.send(30).unwrap();\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"}\n" -"```" +#: src/concurrency/channels.md:15 src/concurrency/channels.md:16 +#: src/concurrency/channels.md:20 +msgid "\"Received: {:?}\"" msgstr "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" tx.send(10).unwrap();\n" -" tx.send(20).unwrap();\n" -"\n" -" println!(\"Received: {:?}\", rx.recv());\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"\n" -" let tx2 = tx.clone();\n" -" tx2.send(30).unwrap();\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"}\n" -"```" #: src/concurrency/channels.md:26 msgid "" @@ -17008,7 +17620,7 @@ msgstr "" "`mpsc` 代表多个生产方，单个使用方。`Sender` 和 `SyncSender` 会实现 `Clone`" "（因此， 你可以设置多个生产方），但 `Receiver` 不会实现。" -#: src/concurrency/channels.md:28 +#: src/concurrency/channels.md:29 msgid "" "`send()` and `recv()` return `Result`. If they return `Err`, it means the " "counterpart `Sender` or `Receiver` is dropped and the channel is closed." @@ -17020,55 +17632,25 @@ msgstr "" msgid "You get an unbounded and asynchronous channel with `mpsc::channel()`:" msgstr "你可以使用 `mpsc::channel()` 获得无边界的异步通道：" -#: src/concurrency/channels/unbounded.md:5 -msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" +#: src/concurrency/channels/unbounded.md:16 +#: src/concurrency/channels/bounded.md:16 +msgid "\"Message {i}\"" +msgstr "" + +#: src/concurrency/channels/unbounded.md:17 +#: src/concurrency/channels/bounded.md:17 +msgid "\"{thread_id:?}: sent Message {i}\"" +msgstr "" + +#: src/concurrency/channels/unbounded.md:19 +#: src/concurrency/channels/bounded.md:19 +msgid "\"{thread_id:?}: done\"" +msgstr "" + +#: src/concurrency/channels/unbounded.md:24 +#: src/concurrency/channels/bounded.md:24 +msgid "\"Main: got {msg}\"" msgstr "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" #: src/concurrency/channels/bounded.md:3 #, fuzzy @@ -17076,56 +17658,6 @@ msgid "" "With bounded (synchronous) channels, `send` can block the current thread:" msgstr "有边界的同步通道会使 `send` 阻塞当前线程：" -#: src/concurrency/channels/bounded.md:5 -msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::sync_channel(3);\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" -msgstr "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::sync_channel(3);\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" - #: src/concurrency/channels/bounded.md:31 msgid "" "Calling `send` will block the current thread until there is space in the " @@ -17133,22 +17665,18 @@ msgid "" "is nobody who reads from the channel." msgstr "" -#: src/concurrency/channels/bounded.md:32 +#: src/concurrency/channels/bounded.md:34 msgid "" "A call to `send` will abort with an error (that is why it returns `Result`) " "if the channel is closed. A channel is closed when the receiver is dropped." msgstr "" -#: src/concurrency/channels/bounded.md:33 +#: src/concurrency/channels/bounded.md:36 msgid "" "A bounded channel with a size of zero is called a \"rendezvous channel\". " "Every send will block the current thread until another thread calls `read`." msgstr "" -#: src/concurrency/send-sync.md:1 -msgid "`Send` and `Sync`" -msgstr "`Send` 和 `Sync`" - #: src/concurrency/send-sync.md:3 #, fuzzy msgid "" @@ -17156,7 +17684,7 @@ msgid "" "two traits:" msgstr "Rust 如何知道要禁止跨线程共享访问？答案在于 Rust 的两个特征：" -#: src/concurrency/send-sync.md:5 +#: src/concurrency/send-sync.md:6 msgid "" "[`Send`](https://doc.rust-lang.org/std/marker/trait.Send.html): a type `T` " "is `Send` if it is safe to move a `T` across a thread boundary." @@ -17164,7 +17692,7 @@ msgstr "" "[`Send`](https://doc.rust-lang.org/std/marker/trait.Send.html)：如果跨线程边" "界移动 `T` 是安全的，则类型 `T` 为 `Send`。" -#: src/concurrency/send-sync.md:7 +#: src/concurrency/send-sync.md:8 msgid "" "[`Sync`](https://doc.rust-lang.org/std/marker/trait.Sync.html): a type `T` " "is `Sync` if it is safe to move a `&T` across a thread boundary." @@ -17172,7 +17700,7 @@ msgstr "" "[`Sync`](https://doc.rust-lang.org/std/marker/trait.Sync.html)：如果跨线程边" "界移动 `&T` 是安全的，则类型 `T` 为 `Sync`。" -#: src/concurrency/send-sync.md:10 +#: src/concurrency/send-sync.md:11 msgid "" "`Send` and `Sync` are [unsafe traits](../unsafe/unsafe-traits.md). The " "compiler will automatically derive them for your types as long as they only " @@ -17183,20 +17711,16 @@ msgstr "" "含 `Send` 和 `Sync` 类型，编译器就会自动为类型派生 这两种特征。你也可以手动实" "现它们（如果你确定这样 有效的话）。" -#: src/concurrency/send-sync.md:20 +#: src/concurrency/send-sync.md:21 msgid "" "One can think of these traits as markers that the type has certain thread-" "safety properties." msgstr "不妨将这些特征视为类型包含某些线程安全属性的标记。" -#: src/concurrency/send-sync.md:21 +#: src/concurrency/send-sync.md:23 msgid "They can be used in the generic constraints as normal traits." msgstr "它们可以在泛型约束中作为常规特征使用。" -#: src/concurrency/send-sync/send.md:1 -msgid "`Send`" -msgstr "`Send`" - #: src/concurrency/send-sync/send.md:3 msgid "" "A type `T` is [`Send`](https://doc.rust-lang.org/std/marker/trait.Send.html) " @@ -17220,10 +17744,6 @@ msgid "" "a single thread." msgstr "例如，与 SQLite 库的连接只能通过 单个线程访问。" -#: src/concurrency/send-sync/sync.md:1 -msgid "`Sync`" -msgstr "`Sync`" - #: src/concurrency/send-sync/sync.md:3 msgid "" "A type `T` is [`Sync`](https://doc.rust-lang.org/std/marker/trait.Sync.html) " @@ -17249,7 +17769,7 @@ msgstr "" "该语句实质上是一种简写形式，表示如果某个类型对于共享使用是线程安全的，那么跨" "线程传递对该类型的引用也是线程安全的。" -#: src/concurrency/send-sync/sync.md:16 +#: src/concurrency/send-sync/sync.md:18 msgid "" "This is because if a type is Sync it means that it can be shared across " "multiple threads without the risk of data races or other synchronization " @@ -17337,9 +17857,10 @@ msgid "" msgstr "这些类型是线程安全的，但它们不能移动到另一个线程：" #: src/concurrency/send-sync/examples.md:31 +#, fuzzy msgid "" -"`MutexGuard`: Uses OS level primitives which must be deallocated on the " -"thread which created them." +"`MutexGuard`: Uses OS level primitives which must be deallocated on " +"the thread which created them." msgstr "" "`MutexGuard`：使用操作系统级别的原语（必须在创建这些原语的线程上 取消分" "配）。" @@ -17389,10 +17910,6 @@ msgstr "" "[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html)：确保对 " "`T` 值的互斥访问。" -#: src/concurrency/shared_state/arc.md:1 -msgid "`Arc`" -msgstr "`Arc`" - #: src/concurrency/shared_state/arc.md:3 msgid "" "[`Arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html) allows shared " @@ -17401,47 +17918,15 @@ msgstr "" "[`Arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html) 允许通过 " "`Arc::clone` 实现共享只读权限：" -#: src/concurrency/shared_state/arc.md:5 -msgid "" -"```rust,editable\n" -"use std::thread;\n" -"use std::sync::Arc;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(vec![10, 20, 30]);\n" -" let mut handles = Vec::new();\n" -" for _ in 1..5 {\n" -" let v = Arc::clone(&v);\n" -" handles.push(thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" println!(\"{thread_id:?}: {v:?}\");\n" -" }));\n" -" }\n" -"\n" -" handles.into_iter().for_each(|h| h.join().unwrap());\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" +#: src/concurrency/shared_state/arc.md:16 +msgid "\"{thread_id:?}: {v:?}\"" +msgstr "" + +#: src/concurrency/shared_state/arc.md:21 +#: src/concurrency/shared_state/example.md:17 +#: src/concurrency/shared_state/example.md:45 +msgid "\"v: {v:?}\"" msgstr "" -"```rust,editable\n" -"use std::thread;\n" -"use std::sync::Arc;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(vec![10, 20, 30]);\n" -" let mut handles = Vec::new();\n" -" for _ in 1..5 {\n" -" let v = Arc::clone(&v);\n" -" handles.push(thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" println!(\"{thread_id:?}: {v:?}\");\n" -" }));\n" -" }\n" -"\n" -" handles.into_iter().for_each(|h| h.join().unwrap());\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" #: src/concurrency/shared_state/arc.md:29 msgid "" @@ -17472,14 +17957,10 @@ msgid "" "them." msgstr "请警惕引用循环，`Arc` 不会使用垃圾回收器检测引用循环。" -#: src/concurrency/shared_state/arc.md:36 +#: src/concurrency/shared_state/arc.md:37 msgid "`std::sync::Weak` can help." msgstr "`std::sync::Weak` 对此有所帮助。" -#: src/concurrency/shared_state/mutex.md:1 -msgid "`Mutex`" -msgstr "`互斥器 (Mutex)`" - #: src/concurrency/shared_state/mutex.md:3 msgid "" "[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html) ensures " @@ -17489,39 +17970,10 @@ msgstr "" "[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html) 能够确保互" "斥，并允许对只读接口 后面的 `T` 进行可变访问：" -#: src/concurrency/shared_state/mutex.md:6 -msgid "" -"```rust,editable\n" -"use std::sync::Mutex;\n" -"\n" -"fn main() {\n" -" let v = Mutex::new(vec![10, 20, 30]);\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"\n" -" {\n" -" let mut guard = v.lock().unwrap();\n" -" guard.push(40);\n" -" }\n" -"\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"}\n" -"```" +#: src/concurrency/shared_state/mutex.md:11 +#: src/concurrency/shared_state/mutex.md:18 +msgid "\"v: {:?}\"" msgstr "" -"```rust,editable\n" -"use std::sync::Mutex;\n" -"\n" -"fn main() {\n" -" let v = Mutex::new(vec![10, 20, 30]);\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"\n" -" {\n" -" let mut guard = v.lock().unwrap();\n" -" guard.push(40);\n" -" }\n" -"\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"}\n" -"```" #: src/concurrency/shared_state/mutex.md:22 msgid "" @@ -17533,19 +17985,20 @@ msgstr "" "org/std/sync/struct.Mutex.html#impl-Sync-for-Mutex%3CT%3E) 通用 实现。" #: src/concurrency/shared_state/mutex.md:31 +#, fuzzy msgid "" -"`Mutex` in Rust looks like a collection with just one element - the " +"`Mutex` in Rust looks like a collection with just one element --- the " "protected data." msgstr "" "Rust 中的互斥器看起来就像只包含一个元素的集合，其中的元素就是受保护的数据。" -#: src/concurrency/shared_state/mutex.md:32 +#: src/concurrency/shared_state/mutex.md:33 msgid "" "It is not possible to forget to acquire the mutex before accessing the " "protected data." msgstr "在访问受保护的数据之前不可能忘记获取互斥量。" -#: src/concurrency/shared_state/mutex.md:33 +#: src/concurrency/shared_state/mutex.md:35 msgid "" "You can get an `&mut T` from an `&Mutex` by taking the lock. The " "`MutexGuard` ensures that the `&mut T` doesn't outlive the lock being held." @@ -17553,22 +18006,24 @@ msgstr "" "你可以通过获取锁，从 `&Mutex` 中获取 `&mut T`。`MutexGuard` 能够确保 " "`&mut T` 存在的时间不会比持有锁的时间更长。" -#: src/concurrency/shared_state/mutex.md:35 +#: src/concurrency/shared_state/mutex.md:37 #, fuzzy msgid "" "`Mutex` implements both `Send` and `Sync` iff (if and only if) `T` " "implements `Send`." msgstr "如果 `T` 实现了 `Send`，`Mutex` 便会实现 `Send` 和 `Sync`。" -#: src/concurrency/shared_state/mutex.md:36 -msgid "A read-write lock counterpart - `RwLock`." +#: src/concurrency/shared_state/mutex.md:39 +#, fuzzy +msgid "A read-write lock counterpart: `RwLock`." msgstr "读写锁版本 - `RwLock`。" -#: src/concurrency/shared_state/mutex.md:37 -msgid "Why does `lock()` return a `Result`? " +#: src/concurrency/shared_state/mutex.md:40 +#, fuzzy +msgid "Why does `lock()` return a `Result`?" msgstr "为什么 `lock()` 会返回 `Result`？" -#: src/concurrency/shared_state/mutex.md:38 +#: src/concurrency/shared_state/mutex.md:41 msgid "" "If the thread that held the `Mutex` panicked, the `Mutex` becomes " "\"poisoned\" to signal that the data it protected might be in an " @@ -17581,97 +18036,17 @@ msgstr "" "[`PoisonError`](https://doc.rust-lang.org/std/sync/struct.PoisonError.html)。" "无论如何，你可以对该错误调用 `into_inner()` 来 恢复数据。" -#: src/concurrency/shared_state/example.md:3 -msgid "Let us see `Arc` and `Mutex` in action:" -msgstr "让我们看看 `Arc` 和 `Mutex` 的实际效果：" - -#: src/concurrency/shared_state/example.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"// use std::sync::{Arc, Mutex};\n" -"\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" let handle = thread::spawn(|| {\n" -" v.push(10);\n" -" });\n" -" v.push(1000);\n" -"\n" -" handle.join().unwrap();\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" -msgstr "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"// use std::sync::{Arc, Mutex};\n" -"\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" let handle = thread::spawn(|| {\n" -" v.push(10);\n" -" });\n" -" v.push(1000);\n" -"\n" -" handle.join().unwrap();\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" - -#: src/concurrency/shared_state/example.md:23 -msgid "Possible solution:" -msgstr "可能有用的解决方案：" - -#: src/concurrency/shared_state/example.md:25 -msgid "" -"```rust,editable\n" -"use std::sync::{Arc, Mutex};\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(Mutex::new(vec![10, 20, 30]));\n" -"\n" -" let v2 = Arc::clone(&v);\n" -" let handle = thread::spawn(move || {\n" -" let mut v2 = v2.lock().unwrap();\n" -" v2.push(10);\n" -" });\n" -"\n" -" {\n" -" let mut v = v.lock().unwrap();\n" -" v.push(1000);\n" -" }\n" -"\n" -" handle.join().unwrap();\n" -"\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" +#: src/concurrency/shared_state/example.md:3 +msgid "Let us see `Arc` and `Mutex` in action:" +msgstr "让我们看看 `Arc` 和 `Mutex` 的实际效果：" + +#: src/concurrency/shared_state/example.md:6 +msgid "// use std::sync::{Arc, Mutex};\n" msgstr "" -"```rust,editable\n" -"use std::sync::{Arc, Mutex};\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(Mutex::new(vec![10, 20, 30]));\n" -"\n" -" let v2 = Arc::clone(&v);\n" -" let handle = thread::spawn(move || {\n" -" let mut v2 = v2.lock().unwrap();\n" -" v2.push(10);\n" -" });\n" -"\n" -" {\n" -" let mut v = v.lock().unwrap();\n" -" v.push(1000);\n" -" }\n" -"\n" -" handle.join().unwrap();\n" -"\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" + +#: src/concurrency/shared_state/example.md:23 +msgid "Possible solution:" +msgstr "可能有用的解决方案：" #: src/concurrency/shared_state/example.md:49 msgid "Notable parts:" @@ -17683,13 +18058,13 @@ msgid "" "orthogonal." msgstr "`Arc` 和 `Mutex` 中都封装了 `v`，因为它们的关注点是正交的。" -#: src/concurrency/shared_state/example.md:52 +#: src/concurrency/shared_state/example.md:53 msgid "" "Wrapping a `Mutex` in an `Arc` is a common pattern to share mutable state " "between threads." msgstr "将 `Mutex` 封装在 `Arc` 中是一种在线程之间共享可变状态的常见模式。" -#: src/concurrency/shared_state/example.md:53 +#: src/concurrency/shared_state/example.md:55 msgid "" "`v: Arc<_>` needs to be cloned as `v2` before it can be moved into another " "thread. Note `move` was added to the lambda signature." @@ -17697,7 +18072,7 @@ msgstr "" "`v: Arc<_>` 必须先克隆为 `v2`，然后才能移动到另一个线程中。请注意，lambda 签" "名中添加了 `move`。" -#: src/concurrency/shared_state/example.md:54 +#: src/concurrency/shared_state/example.md:57 msgid "" "Blocks are introduced to narrow the scope of the `LockGuard` as much as " "possible." @@ -17740,49 +18115,89 @@ msgid "" "out the blanks, and test that `cargo run` does not deadlock:" msgstr "" -#: src/exercises/concurrency/dining-philosophers.md:19 +#: src/exercises/concurrency/dining-philosophers.md:28 +#: src/exercises/concurrency/dining-philosophers-async.md:23 msgid "" -"```rust,compile_fail\n" -"use std::sync::{mpsc, Arc, Mutex};\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" // left_fork: ...\n" +"// left_fork: ...\n" " // right_fork: ...\n" " // thoughts: ...\n" -"}\n" -"\n" -"impl Philosopher {\n" -" fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))\n" -" .unwrap();\n" -" }\n" -"\n" -" fn eat(&self) {\n" -" // Pick up forks...\n" -" println!(\"{} is eating...\", &self.name);\n" -" thread::sleep(Duration::from_millis(10));\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Plato\", \"Aristotle\", \"Thales\", \"Pythagoras\"];\n" -"\n" -"fn main() {\n" -" // Create forks\n" -"\n" -" // Create philosophers\n" -"\n" -" // Make each of them think and eat 100 times\n" -"\n" -" // Output their thoughts\n" -"}\n" -"```" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:36 +#: src/exercises/concurrency/solutions-morning.md:24 +#: src/exercises/concurrency/dining-philosophers-async.md:31 +#: src/exercises/concurrency/solutions-afternoon.md:25 +msgid "\"Eureka! {} has a new idea!\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:41 +#: src/exercises/concurrency/dining-philosophers-async.md:37 +#: src/exercises/concurrency/solutions-afternoon.md:31 +msgid "// Pick up forks...\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:42 +#: src/exercises/concurrency/solutions-morning.md:33 +#: src/exercises/concurrency/dining-philosophers-async.md:38 +#: src/exercises/concurrency/solutions-afternoon.md:38 +msgid "\"{} is eating...\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:44 +#: src/exercises/concurrency/solutions-afternoon.md:46 +msgid "\"Socrates\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:44 +#: src/exercises/concurrency/solutions-afternoon.md:46 +msgid "\"Hypatia\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:44 +#: src/exercises/concurrency/solutions-afternoon.md:46 +msgid "\"Plato\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:44 +#: src/exercises/concurrency/solutions-afternoon.md:46 +msgid "\"Aristotle\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:44 +#: src/exercises/concurrency/solutions-afternoon.md:46 +msgid "\"Pythagoras\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:51 +#: src/exercises/concurrency/dining-philosophers-async.md:48 +#: src/exercises/concurrency/solutions-afternoon.md:50 +msgid "// Create forks\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:53 +#: src/exercises/concurrency/dining-philosophers-async.md:50 +#: src/exercises/concurrency/solutions-afternoon.md:54 +msgid "// Create philosophers\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:55 +msgid "// Make each of them think and eat 100 times\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:57 +#: src/exercises/concurrency/dining-philosophers-async.md:54 +#: src/exercises/concurrency/solutions-afternoon.md:88 +msgid "// Output their thoughts\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:61 @@ -17863,92 +18278,117 @@ msgstr "" msgid "Your `src/main.rs` file should look something like this:" msgstr "" -#: src/exercises/concurrency/link-checker.md:57 -msgid "" -"```rust,compile_fail\n" -"use reqwest::{blocking::Client, Url};\n" -"use scraper::{Html, Selector};\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Error, Debug)]\n" -"enum Error {\n" -" #[error(\"request error: {0}\")]\n" -" ReqwestError(#[from] reqwest::Error),\n" -" #[error(\"bad http response: {0}\")]\n" -" BadResponse(String),\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct CrawlCommand {\n" -" url: Url,\n" -" extract_links: bool,\n" -"}\n" -"\n" -"fn visit_page(client: &Client, command: &CrawlCommand) -> Result, " -"Error> {\n" -" println!(\"Checking {:#}\", command.url);\n" -" let response = client.get(command.url.clone()).send()?;\n" -" if !response.status().is_success() {\n" -" return Err(Error::BadResponse(response.status().to_string()));\n" -" }\n" -"\n" -" let mut link_urls = Vec::new();\n" -" if !command.extract_links {\n" -" return Ok(link_urls);\n" -" }\n" -"\n" -" let base_url = response.url().to_owned();\n" -" let body_text = response.text()?;\n" -" let document = Html::parse_document(&body_text);\n" -"\n" -" let selector = Selector::parse(\"a\").unwrap();\n" -" let href_values = document\n" -" .select(&selector)\n" -" .filter_map(|element| element.value().attr(\"href\"));\n" -" for href in href_values {\n" -" match base_url.join(href) {\n" -" Ok(link_url) => {\n" -" link_urls.push(link_url);\n" -" }\n" -" Err(err) => {\n" -" println!(\"On {base_url:#}: ignored unparsable {href:?}: " -"{err}\");\n" -" }\n" -" }\n" -" }\n" -" Ok(link_urls)\n" -"}\n" -"\n" -"fn main() {\n" -" let client = Client::new();\n" -" let start_url = Url::parse(\"https://www.google.org\").unwrap();\n" -" let crawl_command = CrawlCommand{ url: start_url, extract_links: " -"true };\n" -" match visit_page(&client, &crawl_command) {\n" -" Ok(links) => println!(\"Links: {links:#?}\"),\n" -" Err(err) => println!(\"Could not extract links: {err:#}\"),\n" -" }\n" -"}\n" -"```" +#: src/exercises/concurrency/link-checker.md:65 +#: src/exercises/concurrency/solutions-morning.md:97 +msgid "\"request error: {0}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:67 +#: src/exercises/concurrency/solutions-morning.md:99 +msgid "\"bad http response: {0}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:78 +#: src/exercises/concurrency/solutions-morning.md:110 +msgid "\"Checking {:#}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:96 +#: src/exercises/concurrency/solutions-morning.md:128 +msgid "\"href\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:103 +#: src/exercises/concurrency/solutions-morning.md:135 +msgid "\"On {base_url:#}: ignored unparsable {href:?}: {err}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:112 +#: src/exercises/concurrency/solutions-morning.md:245 +msgid "\"https://www.google.org\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:115 +msgid "\"Links: {links:#?}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md:116 +msgid "\"Could not extract links: {err:#}\"" msgstr "" -#: src/exercises/concurrency/link-checker.md:120 +#: src/exercises/concurrency/link-checker.md:121 msgid "Run the code in `src/main.rs` with" msgstr "" -#: src/exercises/concurrency/link-checker.md:128 +#: src/exercises/concurrency/link-checker.md:129 msgid "" "Use threads to check the links in parallel: send the URLs to be checked to a " "channel and let a few threads check the URLs in parallel." msgstr "" -#: src/exercises/concurrency/link-checker.md:130 +#: src/exercises/concurrency/link-checker.md:131 msgid "" "Extend this to recursively extract links from all pages on the `www.google." "org` domain. Put an upper limit of 100 pages or so so that you don't end up " "being blocked by the site." msgstr "" +#: src/exercises/concurrency/solutions-morning.md:1 +msgid "Concurrency Morning Exercise" +msgstr "并发编程：上午练习" + +#: src/exercises/concurrency/solutions-morning.md:5 +msgid "([back to exercise](dining-philosophers.md))" +msgstr "([返回练习](dining-philosophers.md))" + +#: src/exercises/concurrency/solutions-morning.md:29 +msgid "\"{} is trying to eat\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:53 +msgid "" +"// To avoid a deadlock, we have to break the symmetry\n" +" // somewhere. This will swap the forks without deinitializing\n" +" // either of them.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:77 +msgid "\"{thought}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:82 +#, fuzzy +msgid "Link Checker" +msgstr "多线程链接检查器" + +#: src/exercises/concurrency/solutions-morning.md:84 +#, fuzzy +msgid "([back to exercise](link-checker.md))" +msgstr "([返回练习](luhn.md))" + +#: src/exercises/concurrency/solutions-morning.md:154 +msgid "" +"/// Determine whether links within the given page should be extracted.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:162 +msgid "" +"/// Mark the given page as visited, returning false if it had already\n" +" /// been visited.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:188 +msgid "// The sender got dropped. No more commands coming in.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:229 +msgid "\"Got crawling error: {:#}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:247 +msgid "\"Bad URLs: {:#?}\"" +msgstr "" + #: src/async.md:1 msgid "Async Rust" msgstr "" @@ -17976,10 +18416,6 @@ msgid "" "available." msgstr "" -#: src/async.md:17 -msgid "Comparisons" -msgstr "" - #: src/async.md:19 msgid "" "Python has a similar model in its `asyncio`. However, its `Future` type is " @@ -17994,35 +18430,14 @@ msgid "" "resolution are hidden." msgstr "" -#: src/async/async-await.md:1 -msgid "`async`/`await`" -msgstr "" - #: src/async/async-await.md:3 msgid "" "At a high level, async Rust code looks very much like \"normal\" sequential " "code:" msgstr "从高层次上看，异步 Rust 代码与“正常”的顺序代码非常类似：" -#: src/async/async-await.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use futures::executor::block_on;\n" -"\n" -"async fn count_to(count: i32) {\n" -" for i in 1..=count {\n" -" println!(\"Count is: {i}!\");\n" -" }\n" -"}\n" -"\n" -"async fn async_main(count: i32) {\n" -" count_to(count).await;\n" -"}\n" -"\n" -"fn main() {\n" -" block_on(async_main(10));\n" -"}\n" -"```" +#: src/async/async-await.md:10 +msgid "\"Count is: {i}!\"" msgstr "" #: src/async/async-await.md:27 @@ -18042,9 +18457,10 @@ msgid "Use `let future: () = async_main(10);` in `main` to see the type." msgstr "在 `main` 中使用 `let future: () = async_main(10);` 来查看类型。" #: src/async/async-await.md:33 +#, fuzzy msgid "" "The \"async\" keyword is syntactic sugar. The compiler replaces the return " -"type with a future. " +"type with a future." msgstr "\"async\" 关键字是语法糖。编译器会将返回类型替换为 future。" #: src/async/async-await.md:36 @@ -18056,9 +18472,10 @@ msgstr "" "返回的 future。" #: src/async/async-await.md:39 +#, fuzzy msgid "" "You need an executor to run async code. `block_on` blocks the current thread " -"until the provided future has run to completion. " +"until the provided future has run to completion." msgstr "" "你需要一个执行器来运行异步代码。`block_on`会阻塞当前线程，直到提供的future完" "成为止。 " @@ -18072,9 +18489,10 @@ msgstr "" "当前线程。" #: src/async/async-await.md:45 +#, fuzzy msgid "" "`.await` can only be used inside an `async` function (or block; these are " -"introduced later). " +"introduced later)." msgstr "`.await` 只能在 `async` 函数（或块，这些稍后会介绍）中使用。 " #: src/async/futures.md:3 @@ -18170,74 +18588,58 @@ msgid "" "used." msgstr "" -#: src/async/runtimes/tokio.md:4 -msgid "Tokio provides: " +#: src/async/runtimes/tokio.md:3 +msgid "Tokio provides:" msgstr "" -#: src/async/runtimes/tokio.md:6 +#: src/async/runtimes/tokio.md:5 msgid "A multi-threaded runtime for executing asynchronous code." msgstr "" -#: src/async/runtimes/tokio.md:7 +#: src/async/runtimes/tokio.md:6 msgid "An asynchronous version of the standard library." msgstr "" -#: src/async/runtimes/tokio.md:8 +#: src/async/runtimes/tokio.md:7 msgid "A large ecosystem of libraries." msgstr "" -#: src/async/runtimes/tokio.md:10 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::time;\n" -"\n" -"async fn count_to(count: i32) {\n" -" for i in 1..=count {\n" -" println!(\"Count in task: {i}!\");\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" tokio::spawn(count_to(10));\n" -"\n" -" for i in 1..5 {\n" -" println!(\"Main task: {i}\");\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"```" +#: src/async/runtimes/tokio.md:14 +msgid "\"Count in task: {i}!\"" +msgstr "" + +#: src/async/runtimes/tokio.md:24 +msgid "\"Main task: {i}\"" msgstr "" -#: src/async/runtimes/tokio.md:33 +#: src/async/runtimes/tokio.md:32 msgid "With the `tokio::main` macro we can now make `main` async." msgstr "" -#: src/async/runtimes/tokio.md:35 +#: src/async/runtimes/tokio.md:34 msgid "The `spawn` function creates a new, concurrent \"task\"." msgstr "" -#: src/async/runtimes/tokio.md:37 +#: src/async/runtimes/tokio.md:36 msgid "Note: `spawn` takes a `Future`, you don't call `.await` on `count_to`." msgstr "" -#: src/async/runtimes/tokio.md:39 +#: src/async/runtimes/tokio.md:38 msgid "**Further exploration:**" msgstr "" -#: src/async/runtimes/tokio.md:41 +#: src/async/runtimes/tokio.md:40 msgid "" "Why does `count_to` not (usually) get to 10? This is an example of async " "cancellation. `tokio::spawn` returns a handle which can be awaited to wait " "until it finishes." msgstr "" -#: src/async/runtimes/tokio.md:45 +#: src/async/runtimes/tokio.md:44 msgid "Try `count_to(10).await` instead of spawning." msgstr "" -#: src/async/runtimes/tokio.md:47 +#: src/async/runtimes/tokio.md:46 msgid "Try awaiting the task returned from `tokio::spawn`." msgstr "" @@ -18254,69 +18656,56 @@ msgid "" "and an I/O operation." msgstr "" -#: src/async/tasks.md:10 -msgid "" -"```rust,compile_fail\n" -"use tokio::io::{self, AsyncReadExt, AsyncWriteExt};\n" -"use tokio::net::TcpListener;\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> io::Result<()> {\n" -" let listener = TcpListener::bind(\"127.0.0.1:6142\").await?;\n" -"\tprintln!(\"listening on port 6142\");\n" -"\n" -" loop {\n" -" let (mut socket, addr) = listener.accept().await?;\n" -"\n" -" println!(\"connection from {addr:?}\");\n" -"\n" -" tokio::spawn(async move {\n" -" if let Err(e) = socket.write_all(b\"Who are you?\\n\").await {\n" -" println!(\"socket error: {e:?}\");\n" -" return;\n" -" }\n" -"\n" -" let mut buf = vec![0; 1024];\n" -" let reply = match socket.read(&mut buf).await {\n" -" Ok(n) => {\n" -" let name = std::str::from_utf8(&buf[..n]).unwrap()." -"trim();\n" -" format!(\"Thanks for dialing in, {name}!\\n\")\n" -" }\n" -" Err(e) => {\n" -" println!(\"socket error: {e:?}\");\n" -" return;\n" -" }\n" -" };\n" -"\n" -" if let Err(e) = socket.write_all(reply.as_bytes()).await {\n" -" println!(\"socket error: {e:?}\");\n" -" }\n" -" });\n" -" }\n" -"}\n" -"```" +#: src/async/tasks.md:16 +msgid "\"127.0.0.1:0\"" msgstr "" -#: src/async/tasks.md:52 src/async/control-flow/join.md:36 +#: src/async/tasks.md:17 +msgid "\"listening on port {}\"" +msgstr "" + +#: src/async/tasks.md:22 +msgid "\"connection from {addr:?}\"" +msgstr "" + +#: src/async/tasks.md:25 +msgid "b\"Who are you?\\n\"" +msgstr "" + +#: src/async/tasks.md:25 src/async/tasks.md:28 src/async/tasks.md:31 +msgid "\"socket error\"" +msgstr "" + +#: src/async/tasks.md:30 +msgid "\"Thanks for dialing in, {name}!\\n\"" +msgstr "" + +#: src/async/tasks.md:39 src/async/control-flow/join.md:36 msgid "" "Copy this example into your prepared `src/main.rs` and run it from there." msgstr "" -#: src/async/tasks.md:54 +#: src/async/tasks.md:41 +msgid "" +"Try connecting to it with a TCP connection tool like [nc](https://www.unix." +"com/man-page/linux/1/nc/) or [telnet](https://www.unix.com/man-page/linux/1/" +"telnet/)." +msgstr "" + +#: src/async/tasks.md:45 msgid "" "Ask students to visualize what the state of the example server would be with " "a few connected clients. What tasks exist? What are their Futures?" msgstr "" -#: src/async/tasks.md:57 +#: src/async/tasks.md:48 msgid "" "This is the first time we've seen an `async` block. This is similar to a " "closure, but does not take any arguments. Its return value is a Future, " -"similar to an `async fn`. " +"similar to an `async fn`." msgstr "" -#: src/async/tasks.md:61 +#: src/async/tasks.md:52 msgid "" "Refactor the async block into a function, and improve the error handling " "using `?`." @@ -18327,36 +18716,24 @@ msgid "" "Several crates have support for asynchronous channels. For instance `tokio`:" msgstr "" -#: src/async/channels.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::mpsc::{self, Receiver};\n" -"\n" -"async fn ping_handler(mut input: Receiver<()>) {\n" -" let mut count: usize = 0;\n" -"\n" -" while let Some(_) = input.recv().await {\n" -" count += 1;\n" -" println!(\"Received {count} pings so far.\");\n" -" }\n" -"\n" -" println!(\"ping_handler complete\");\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (sender, receiver) = mpsc::channel(32);\n" -" let ping_handler_task = tokio::spawn(ping_handler(receiver));\n" -" for i in 0..10 {\n" -" sender.send(()).await.expect(\"Failed to send ping.\");\n" -" println!(\"Sent {} pings so far.\", i + 1);\n" -" }\n" -"\n" -" drop(sender);\n" -" ping_handler_task.await.expect(\"Something went wrong in ping handler " -"task.\");\n" -"}\n" -"```" +#: src/async/channels.md:13 +msgid "\"Received {count} pings so far.\"" +msgstr "" + +#: src/async/channels.md:16 +msgid "\"ping_handler complete\"" +msgstr "" + +#: src/async/channels.md:24 +msgid "\"Failed to send ping.\"" +msgstr "" + +#: src/async/channels.md:25 +msgid "\"Sent {} pings so far.\"" +msgstr "" + +#: src/async/channels.md:29 +msgid "\"Something went wrong in ping handler task.\"" msgstr "" #: src/async/channels.md:35 @@ -18413,34 +18790,20 @@ msgid "" "JavaScript or `asyncio.gather` in Python." msgstr "" -#: src/async/control-flow/join.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"use anyhow::Result;\n" -"use futures::future;\n" -"use reqwest;\n" -"use std::collections::HashMap;\n" -"\n" -"async fn size_of_page(url: &str) -> Result {\n" -" let resp = reqwest::get(url).await?;\n" -" Ok(resp.text().await?.len())\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let urls: [&str; 4] = [\n" -" \"https://google.com\",\n" -" \"https://httpbin.org/ip\",\n" -" \"https://play.rust-lang.org/\",\n" -" \"BAD_URL\",\n" -" ];\n" -" let futures_iter = urls.into_iter().map(size_of_page);\n" -" let results = future::join_all(futures_iter).await;\n" -" let page_sizes_dict: HashMap<&str, Result> =\n" -" urls.into_iter().zip(results.into_iter()).collect();\n" -" println!(\"{:?}\", page_sizes_dict);\n" -"}\n" -"```" +#: src/async/control-flow/join.md:21 +msgid "\"https://google.com\"" +msgstr "" + +#: src/async/control-flow/join.md:22 +msgid "\"https://httpbin.org/ip\"" +msgstr "" + +#: src/async/control-flow/join.md:23 +msgid "\"https://play.rust-lang.org/\"" +msgstr "" + +#: src/async/control-flow/join.md:24 +msgid "\"BAD_URL\"" msgstr "" #: src/async/control-flow/join.md:38 @@ -18453,7 +18816,7 @@ msgstr "" #: src/async/control-flow/join.md:42 msgid "" "The risk of `join` is that one of the futures may never resolve, this would " -"cause your program to stall. " +"cause your program to stall." msgstr "" #: src/async/control-flow/join.md:45 @@ -18481,57 +18844,31 @@ msgid "" "the `future`'s result." msgstr "" -#: src/async/control-flow/select.md:13 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::mpsc::{self, Receiver};\n" -"use tokio::time::{sleep, Duration};\n" -"\n" -"#[derive(Debug, PartialEq)]\n" -"enum Animal {\n" -" Cat { name: String },\n" -" Dog { name: String },\n" -"}\n" -"\n" -"async fn first_animal_to_finish_race(\n" -" mut cat_rcv: Receiver,\n" -" mut dog_rcv: Receiver,\n" -") -> Option {\n" -" tokio::select! {\n" -" cat_name = cat_rcv.recv() => Some(Animal::Cat { name: cat_name? }),\n" -" dog_name = dog_rcv.recv() => Some(Animal::Dog { name: dog_name? })\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (cat_sender, cat_receiver) = mpsc::channel(32);\n" -" let (dog_sender, dog_receiver) = mpsc::channel(32);\n" -" tokio::spawn(async move {\n" -" sleep(Duration::from_millis(500)).await;\n" -" cat_sender\n" -" .send(String::from(\"Felix\"))\n" -" .await\n" -" .expect(\"Failed to send cat.\");\n" -" });\n" -" tokio::spawn(async move {\n" -" sleep(Duration::from_millis(50)).await;\n" -" dog_sender\n" -" .send(String::from(\"Rex\"))\n" -" .await\n" -" .expect(\"Failed to send dog.\");\n" -" });\n" -"\n" -" let winner = first_animal_to_finish_race(cat_receiver, dog_receiver)\n" -" .await\n" -" .expect(\"Failed to receive winner\");\n" -"\n" -" println!(\"Winner is {winner:?}\");\n" -"}\n" -"```" +#: src/async/control-flow/select.md:39 +msgid "\"Felix\"" +msgstr "" + +#: src/async/control-flow/select.md:39 +msgid "\"Failed to send cat.\"" +msgstr "" + +#: src/async/control-flow/select.md:43 +msgid "\"Rex\"" msgstr "" -#: src/async/control-flow/select.md:62 +#: src/async/control-flow/select.md:43 +msgid "\"Failed to send dog.\"" +msgstr "" + +#: src/async/control-flow/select.md:48 +msgid "\"Failed to receive winner\"" +msgstr "" + +#: src/async/control-flow/select.md:50 +msgid "\"Winner is {winner:?}\"" +msgstr "" + +#: src/async/control-flow/select.md:56 msgid "" "In this example, we have a race between a cat and a dog. " "`first_animal_to_finish_race` listens to both channels and will pick " @@ -18539,25 +18876,25 @@ msgid "" "that take 500ms." msgstr "" -#: src/async/control-flow/select.md:67 +#: src/async/control-flow/select.md:61 msgid "" "You can use `oneshot` channels in this example as the channels are supposed " "to receive only one `send`." msgstr "" -#: src/async/control-flow/select.md:70 +#: src/async/control-flow/select.md:64 msgid "" "Try adding a deadline to the race, demonstrating selecting different sorts " "of futures." msgstr "" -#: src/async/control-flow/select.md:73 +#: src/async/control-flow/select.md:67 msgid "" "Note that `select!` drops unmatched branches, which cancels their futures. " "It is easiest to use when every execution of `select!` creates new futures." msgstr "" -#: src/async/control-flow/select.md:76 +#: src/async/control-flow/select.md:70 msgid "" "An alternative is to pass `&mut future` instead of the future itself, but " "this can lead to issues, further discussed in the pinning slide." @@ -18575,19 +18912,19 @@ msgid "" "chapter:" msgstr "" -#: src/async/pitfalls.md:5 +#: src/async/pitfalls.md:7 msgid "[Blocking the Executor](pitfalls/blocking-executor.md)" msgstr "" -#: src/async/pitfalls.md:6 +#: src/async/pitfalls.md:8 msgid "[Pin](pitfalls/pin.md)" msgstr "" -#: src/async/pitfalls.md:7 +#: src/async/pitfalls.md:9 msgid "[Async Traits](pitfalls/async-traits.md)" msgstr "" -#: src/async/pitfalls.md:8 +#: src/async/pitfalls.md:10 msgid "[Cancellation](pitfalls/cancellation.md)" msgstr "" @@ -18603,27 +18940,12 @@ msgid "" "possible." msgstr "" -#: src/async/pitfalls/blocking-executor.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"use futures::future::join_all;\n" -"use std::time::Instant;\n" -"\n" -"async fn sleep_ms(start: &Instant, id: u64, duration_ms: u64) {\n" -" std::thread::sleep(std::time::Duration::from_millis(duration_ms));\n" -" println!(\n" -" \"future {id} slept for {duration_ms}ms, finished after {}ms\",\n" -" start.elapsed().as_millis()\n" -" );\n" -"}\n" -"\n" -"#[tokio::main(flavor = \"current_thread\")]\n" -"async fn main() {\n" -" let start = Instant::now();\n" -" let sleep_futures = (1..=10).map(|t| sleep_ms(&start, t, t * 10));\n" -" join_all(sleep_futures).await;\n" -"}\n" -"```" +#: src/async/pitfalls/blocking-executor.md:14 +msgid "\"future {id} slept for {duration_ms}ms, finished after {}ms\"" +msgstr "" + +#: src/async/pitfalls/blocking-executor.md:19 +msgid "\"current_thread\"" msgstr "" #: src/async/pitfalls/blocking-executor.md:29 @@ -18677,112 +18999,93 @@ msgstr "" #: src/async/pitfalls/pin.md:8 msgid "" "Therefore, you must guarantee that the addresses your future points to don't " -"change. That is why we need to `pin` futures. Using the same future " +"change. That is why we need to \"pin\" futures. Using the same future " "repeatedly in a `select!` often leads to issues with pinned values." msgstr "" -#: src/async/pitfalls/pin.md:12 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::{mpsc, oneshot};\n" -"use tokio::task::spawn;\n" -"use tokio::time::{sleep, Duration};\n" -"\n" -"// A work item. In this case, just sleep for the given time and respond\n" -"// with a message on the `respond_on` channel.\n" -"#[derive(Debug)]\n" -"struct Work {\n" -" input: u32,\n" -" respond_on: oneshot::Sender,\n" -"}\n" -"\n" -"// A worker which listens for work on a queue and performs it.\n" -"async fn worker(mut work_queue: mpsc::Receiver) {\n" -" let mut iterations = 0;\n" -" loop {\n" -" tokio::select! {\n" -" Some(work) = work_queue.recv() => {\n" -" sleep(Duration::from_millis(10)).await; // Pretend to work.\n" -" work.respond_on\n" -" .send(work.input * 1000)\n" -" .expect(\"failed to send response\");\n" -" iterations += 1;\n" -" }\n" -" // TODO: report number of iterations every 100ms\n" -" }\n" -" }\n" -"}\n" -"\n" -"// A requester which requests work and waits for it to complete.\n" -"async fn do_work(work_queue: &mpsc::Sender, input: u32) -> u32 {\n" -" let (tx, rx) = oneshot::channel();\n" -" work_queue\n" -" .send(Work {\n" -" input,\n" -" respond_on: tx,\n" -" })\n" -" .await\n" -" .expect(\"failed to send on work queue\");\n" -" rx.await.expect(\"failed waiting for response\")\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (tx, rx) = mpsc::channel(10);\n" -" spawn(worker(rx));\n" -" for i in 0..100 {\n" -" let resp = do_work(&tx, i).await;\n" -" println!(\"work result for iteration {i}: {resp}\");\n" -" }\n" -"}\n" -"```" +#: src/async/pitfalls/pin.md:16 +msgid "" +"// A work item. In this case, just sleep for the given time and respond\n" +"// with a message on the `respond_on` channel.\n" +msgstr "" + +#: src/async/pitfalls/pin.md:24 +msgid "// A worker which listens for work on a queue and performs it.\n" +msgstr "" + +#: src/async/pitfalls/pin.md:31 +msgid "// Pretend to work.\n" +msgstr "" + +#: src/async/pitfalls/pin.md:34 +msgid "\"failed to send response\"" +msgstr "" + +#: src/async/pitfalls/pin.md:37 +msgid "// TODO: report number of iterations every 100ms\n" +msgstr "" + +#: src/async/pitfalls/pin.md:41 +msgid "// A requester which requests work and waits for it to complete.\n" +msgstr "" + +#: src/async/pitfalls/pin.md:48 +msgid "\"failed to send on work queue\"" +msgstr "" + +#: src/async/pitfalls/pin.md:49 +msgid "\"failed waiting for response\"" +msgstr "" + +#: src/async/pitfalls/pin.md:58 +msgid "\"work result for iteration {i}: {resp}\"" msgstr "" -#: src/async/pitfalls/pin.md:68 +#: src/async/pitfalls/pin.md:65 msgid "" "You may recognize this as an example of the actor pattern. Actors typically " "call `select!` in a loop." msgstr "" -#: src/async/pitfalls/pin.md:71 +#: src/async/pitfalls/pin.md:68 msgid "" "This serves as a summation of a few of the previous lessons, so take your " "time with it." msgstr "" -#: src/async/pitfalls/pin.md:74 +#: src/async/pitfalls/pin.md:71 msgid "" "Naively add a `_ = sleep(Duration::from_millis(100)) => { println!(..) }` to " "the `select!`. This will never execute. Why?" msgstr "" -#: src/async/pitfalls/pin.md:77 +#: src/async/pitfalls/pin.md:74 msgid "" "Instead, add a `timeout_fut` containing that future outside of the `loop`:" msgstr "" -#: src/async/pitfalls/pin.md:88 +#: src/async/pitfalls/pin.md:85 msgid "" "This still doesn't work. Follow the compiler errors, adding `&mut` to the " "`timeout_fut` in the `select!` to work around the move, then using `Box::" "pin`:" msgstr "" -#: src/async/pitfalls/pin.md:102 +#: src/async/pitfalls/pin.md:99 msgid "" "This compiles, but once the timeout expires it is `Poll::Ready` on every " "iteration (a fused future would help with this). Update to reset " "`timeout_fut` every time it expires." msgstr "" -#: src/async/pitfalls/pin.md:106 +#: src/async/pitfalls/pin.md:103 msgid "" "Box allocates on the heap. In some cases, `std::pin::pin!` (only recently " "stabilized, with older code often using `tokio::pin!`) is also an option, " "but that is difficult to use for a future that is reassigned." msgstr "" -#: src/async/pitfalls/pin.md:110 +#: src/async/pitfalls/pin.md:107 msgid "" "Another alternative is to not use `pin` at all but spawn another task that " "will send to a `oneshot` channel every 100ms." @@ -18796,65 +19099,27 @@ msgid "" "nightly.html))" msgstr "" -#: src/async/pitfalls/async-traits.md:5 +#: src/async/pitfalls/async-traits.md:6 msgid "" "The crate [async_trait](https://docs.rs/async-trait/latest/async_trait/) " "provides a workaround through a macro:" msgstr "" -#: src/async/pitfalls/async-traits.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"use async_trait::async_trait;\n" -"use std::time::Instant;\n" -"use tokio::time::{sleep, Duration};\n" -"\n" -"#[async_trait]\n" -"trait Sleeper {\n" -" async fn sleep(&self);\n" -"}\n" -"\n" -"struct FixedSleeper {\n" -" sleep_ms: u64,\n" -"}\n" -"\n" -"#[async_trait]\n" -"impl Sleeper for FixedSleeper {\n" -" async fn sleep(&self) {\n" -" sleep(Duration::from_millis(self.sleep_ms)).await;\n" -" }\n" -"}\n" -"\n" -"async fn run_all_sleepers_multiple_times(sleepers: Vec>, " -"n_times: usize) {\n" -" for _ in 0..n_times {\n" -" println!(\"running all sleepers..\");\n" -" for sleeper in &sleepers {\n" -" let start = Instant::now();\n" -" sleeper.sleep().await;\n" -" println!(\"slept for {}ms\", start.elapsed().as_millis());\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let sleepers: Vec> = vec![\n" -" Box::new(FixedSleeper { sleep_ms: 50 }),\n" -" Box::new(FixedSleeper { sleep_ms: 100 }),\n" -" ];\n" -" run_all_sleepers_multiple_times(sleepers, 5).await;\n" -"}\n" -"```" +#: src/async/pitfalls/async-traits.md:35 +msgid "\"running all sleepers..\"" +msgstr "" + +#: src/async/pitfalls/async-traits.md:39 +msgid "\"slept for {}ms\"" msgstr "" -#: src/async/pitfalls/async-traits.md:51 +#: src/async/pitfalls/async-traits.md:56 msgid "" "`async_trait` is easy to use, but note that it's using heap allocations to " "achieve this. This heap allocation has performance overhead." msgstr "" -#: src/async/pitfalls/async-traits.md:54 +#: src/async/pitfalls/async-traits.md:59 msgid "" "The challenges in language support for `async trait` are deep Rust and " "probably not worth describing in-depth. Niko Matsakis did a good job of " @@ -18867,7 +19132,7 @@ msgstr "" "smallcultfollowing.com/babysteps/blog/2019/10/26/async-fn-in-traits-are-" "hard/)中对它们做了很好的解释。" -#: src/async/pitfalls/async-traits.md:60 +#: src/async/pitfalls/async-traits.md:65 msgid "" "Try creating a new sleeper struct that will sleep for a random amount of " "time and adding it to the Vec." @@ -18882,72 +19147,17 @@ msgid "" "example, it shouldn't deadlock or lose data." msgstr "" -#: src/async/pitfalls/cancellation.md:8 -msgid "" -"```rust,editable,compile_fail\n" -"use std::io::{self, ErrorKind};\n" -"use std::time::Duration;\n" -"use tokio::io::{AsyncReadExt, AsyncWriteExt, DuplexStream};\n" -"\n" -"struct LinesReader {\n" -" stream: DuplexStream,\n" -"}\n" -"\n" -"impl LinesReader {\n" -" fn new(stream: DuplexStream) -> Self {\n" -" Self { stream }\n" -" }\n" -"\n" -" async fn next(&mut self) -> io::Result> {\n" -" let mut bytes = Vec::new();\n" -" let mut buf = [0];\n" -" while self.stream.read(&mut buf[..]).await? != 0 {\n" -" bytes.push(buf[0]);\n" -" if buf[0] == b'\\n' {\n" -" break;\n" -" }\n" -" }\n" -" if bytes.is_empty() {\n" -" return Ok(None)\n" -" }\n" -" let s = String::from_utf8(bytes)\n" -" .map_err(|_| io::Error::new(ErrorKind::InvalidData, \"not " -"UTF-8\"))?;\n" -" Ok(Some(s))\n" -" }\n" -"}\n" -"\n" -"async fn slow_copy(source: String, mut dest: DuplexStream) -> std::io::" -"Result<()> {\n" -" for b in source.bytes() {\n" -" dest.write_u8(b).await?;\n" -" tokio::time::sleep(Duration::from_millis(10)).await\n" -" }\n" -" Ok(())\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> std::io::Result<()> {\n" -" let (client, server) = tokio::io::duplex(5);\n" -" let handle = tokio::spawn(slow_copy(\"hi\\nthere\\n\".to_owned(), " -"client));\n" -"\n" -" let mut lines = LinesReader::new(server);\n" -" let mut interval = tokio::time::interval(Duration::from_millis(60));\n" -" loop {\n" -" tokio::select! {\n" -" _ = interval.tick() => println!(\"tick!\"),\n" -" line = lines.next() => if let Some(l) = line? {\n" -" print!(\"{}\", l)\n" -" } else {\n" -" break\n" -" },\n" -" }\n" -" }\n" -" handle.await.unwrap()?;\n" -" Ok(())\n" -"}\n" -"```" +#: src/async/pitfalls/cancellation.md:35 +#, fuzzy +msgid "\"not UTF-8\"" +msgstr "UTF-8" + +#: src/async/pitfalls/cancellation.md:51 +msgid "\"hi\\nthere\\n\"" +msgstr "" + +#: src/async/pitfalls/cancellation.md:57 +msgid "\"tick!\"" msgstr "" #: src/async/pitfalls/cancellation.md:72 @@ -18972,37 +19182,17 @@ msgid "" "dropped." msgstr "" -#: src/async/pitfalls/cancellation.md:82 +#: src/async/pitfalls/cancellation.md:83 msgid "" "`LinesReader` can be made cancellation-safe by making `buf` part of the " "struct:" msgstr "" -#: src/async/pitfalls/cancellation.md:83 -msgid "" -"```rust,compile_fail\n" -"struct LinesReader {\n" -" stream: DuplexStream,\n" -" bytes: Vec,\n" -" buf: [u8; 1],\n" -"}\n" -"\n" -"impl LinesReader {\n" -" fn new(stream: DuplexStream) -> Self {\n" -" Self { stream, bytes: Vec::new(), buf: [0] }\n" -" }\n" -" async fn next(&mut self) -> io::Result> {\n" -" // prefix buf and bytes with self.\n" -" // ...\n" -" let raw = std::mem::take(&mut self.bytes);\n" -" let s = String::from_utf8(raw)\n" -" // ...\n" -" }\n" -"}\n" -"```" +#: src/async/pitfalls/cancellation.md:97 +msgid "// prefix buf and bytes with self.\n" msgstr "" -#: src/async/pitfalls/cancellation.md:104 +#: src/async/pitfalls/cancellation.md:106 #, fuzzy msgid "" "[`Interval::tick`](https://docs.rs/tokio/latest/tokio/time/struct.Interval." @@ -19012,7 +19202,7 @@ msgstr "" "[BufReader::read_line()](https://docs.rs/tokio/latest/tokio/io/struct.Lines." "html#method.next_line)：用于从标准输入异步读取用户消息。" -#: src/async/pitfalls/cancellation.md:107 +#: src/async/pitfalls/cancellation.md:110 #, fuzzy msgid "" "[`AsyncReadExt::read`](https://docs.rs/tokio/latest/tokio/io/trait." @@ -19022,7 +19212,7 @@ msgstr "" "[BufReader::read_line()](https://docs.rs/tokio/latest/tokio/io/struct.Lines." "html#method.next_line)：用于从标准输入异步读取用户消息。" -#: src/async/pitfalls/cancellation.md:110 +#: src/async/pitfalls/cancellation.md:113 #, fuzzy msgid "" "[`AsyncBufReadExt::read_line`](https://docs.rs/tokio/latest/tokio/io/trait." @@ -19052,7 +19242,8 @@ msgstr "广播聊天应用：这是一个更大的项目，允许您尝试更高 #: src/exercises/concurrency/dining-philosophers-async.md:1 #: src/exercises/concurrency/solutions-afternoon.md:3 -msgid "Dining Philosophers - Async" +#, fuzzy +msgid "Dining Philosophers --- Async" msgstr "哲学家进餐 - 异步" #: src/exercises/concurrency/dining-philosophers-async.md:3 @@ -19071,55 +19262,12 @@ msgstr "" "行这个练习。将下面的代码复制到一个名为 `src/main.rs` 的文件中，填写空白部分，" "并测试确保 `cargo run` 不会死锁：" -#: src/exercises/concurrency/dining-philosophers-async.md:13 -msgid "" -"```rust,compile_fail\n" -"use std::sync::Arc;\n" -"use tokio::time;\n" -"use tokio::sync::mpsc::{self, Sender};\n" -"use tokio::sync::Mutex;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" // left_fork: ...\n" -" // right_fork: ...\n" -" // thoughts: ...\n" -"}\n" -"\n" -"impl Philosopher {\n" -" async fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))." -"await\n" -" .unwrap();\n" -" }\n" -"\n" -" async fn eat(&self) {\n" -" // Pick up forks...\n" -" println!(\"{} is eating...\", &self.name);\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Plato\", \"Aristotle\", \"Thales\", \"Pythagoras\"];\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" // Create forks\n" -"\n" -" // Create philosophers\n" -"\n" -" // Make them think and eat\n" -"\n" -" // Output their thoughts\n" -"}\n" -"```" +#: src/exercises/concurrency/dining-philosophers-async.md:52 +#: src/exercises/concurrency/solutions-afternoon.md:78 +msgid "// Make them think and eat\n" msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md:57 +#: src/exercises/concurrency/dining-philosophers-async.md:58 msgid "" "Since this time you are using Async Rust, you'll need a `tokio` dependency. " "You can use the following `Cargo.toml`:" @@ -19127,7 +19275,7 @@ msgstr "" "因为这次您正在使用异步Rust，您将需要一个 `tokio` 依赖。您可以使用以下的 " "`Cargo.toml`：" -#: src/exercises/concurrency/dining-philosophers-async.md:62 +#: src/exercises/concurrency/dining-philosophers-async.md:63 msgid "" "```toml\n" "[package]\n" @@ -19136,19 +19284,20 @@ msgid "" "edition = \"2021\"\n" "\n" "[dependencies]\n" -"tokio = {version = \"1.26.0\", features = [\"sync\", \"time\", \"macros\", " -"\"rt-multi-thread\"]}\n" +"tokio = { version = \"1.26.0\", features = [\"sync\", \"time\", \"macros\", " +"\"rt-multi-thread\"] }\n" "```" msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md:72 +#: src/exercises/concurrency/dining-philosophers-async.md:73 msgid "" "Also note that this time you have to use the `Mutex` and the `mpsc` module " "from the `tokio` crate." msgstr "另外，请注意，这次您必须使用来自 `tokio` 包的 `Mutex` 和 `mpsc` 模块。" -#: src/exercises/concurrency/dining-philosophers-async.md:77 -msgid "Can you make your implementation single-threaded? " +#: src/exercises/concurrency/dining-philosophers-async.md:78 +#, fuzzy +msgid "Can you make your implementation single-threaded?" msgstr "您可以单线程化您的实现吗？" #: src/exercises/concurrency/chat-app.md:3 @@ -19168,24 +19317,24 @@ msgstr "" msgid "" "For this, we use [a broadcast channel](https://docs.rs/tokio/latest/tokio/" "sync/broadcast/fn.channel.html) on the server, and [`tokio_websockets`]" -"(https://docs.rs/tokio-websockets/0.4.0/tokio_websockets/) for the " -"communication between the client and the server." +"(https://docs.rs/tokio-websockets/) for the communication between the client " +"and the server." msgstr "" "为此，我们在服务器上使用一个[广播 channel](https://docs.rs/tokio/latest/" "tokio/sync/broadcast/fn.channel.html)，并使用[`tokio_websockets`](https://" "docs.rs/tokio-websockets/0.3.2/tokio_websockets/) 来进行客户端与服务器之间的" "通信。" -#: src/exercises/concurrency/chat-app.md:13 +#: src/exercises/concurrency/chat-app.md:12 msgid "Create a new Cargo project and add the following dependencies:" msgstr "创建一个新的 Cargo 项目并添加以下依赖：" -#: src/exercises/concurrency/chat-app.md:15 +#: src/exercises/concurrency/chat-app.md:14 #, fuzzy msgid "_Cargo.toml_:" msgstr "`Cargo.toml`：" -#: src/exercises/concurrency/chat-app.md:19 +#: src/exercises/concurrency/chat-app.md:18 msgid "" "```toml\n" "[package]\n" @@ -19194,15 +19343,15 @@ msgid "" "edition = \"2021\"\n" "\n" "[dependencies]\n" -"futures-util = { version = \"0.3.28\", features = [\"sink\"] }\n" -"http = \"0.2.9\"\n" +"futures-util = { version = \"0.3.30\", features = [\"sink\"] }\n" +"http = \"1.0.0\"\n" "tokio = { version = \"1.28.1\", features = [\"full\"] }\n" -"tokio-websockets = { version = \"0.4.0\", features = [\"client\", " +"tokio-websockets = { version = \"0.5.0\", features = [\"client\", " "\"fastrand\", \"server\", \"sha1_smol\"] }\n" "```" msgstr "" -#: src/exercises/concurrency/chat-app.md:32 +#: src/exercises/concurrency/chat-app.md:31 msgid "The required APIs" msgstr "所需的API" @@ -19210,9 +19359,8 @@ msgstr "所需的API" #, fuzzy msgid "" "You are going to need the following functions from `tokio` and " -"[`tokio_websockets`](https://docs.rs/tokio-websockets/0.4.0/" -"tokio_websockets/). Spend a few minutes to familiarize yourself with the " -"API. " +"[`tokio_websockets`](https://docs.rs/tokio-websockets/). Spend a few minutes " +"to familiarize yourself with the API." msgstr "" "您将需要来自 `tokio` 和 [`tokio_websockets`](https://docs.rs/tokio-" "websockets/0.3.2/tokio_websockets/) 的以下函数。请花几分钟时间熟悉这些 API。" @@ -19221,7 +19369,7 @@ msgstr "" #, fuzzy msgid "" "[StreamExt::next()](https://docs.rs/futures-util/0.3.28/futures_util/stream/" -"trait.StreamExt.html#method.next) implemented by `WebsocketStream`: for " +"trait.StreamExt.html#method.next) implemented by `WebSocketStream`: for " "asynchronously reading messages from a Websocket Stream." msgstr "" "[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" @@ -19229,9 +19377,10 @@ msgstr "" "异步发送消息。" #: src/exercises/concurrency/chat-app.md:39 +#, fuzzy msgid "" "[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" -"trait.SinkExt.html#method.send) implemented by `WebsocketStream`: for " +"trait.SinkExt.html#method.send) implemented by `WebSocketStream`: for " "asynchronously sending messages on a Websocket Stream." msgstr "" "[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" @@ -19256,11 +19405,12 @@ msgstr "" "[Sender::subscribe()](https://docs.rs/tokio/latest/tokio/sync/broadcast/" "struct.Sender.html#method.subscribe)：用于订阅广播频道。" -#: src/exercises/concurrency/chat-app.md:46 +#: src/exercises/concurrency/chat-app.md:45 msgid "Two binaries" msgstr "两个可执行文件" -#: src/exercises/concurrency/chat-app.md:48 +#: src/exercises/concurrency/chat-app.md:47 +#, fuzzy msgid "" "Normally in a Cargo project, you can have only one binary, and one `src/main." "rs` file. In this project, we need two binaries. One for the client, and one " @@ -19268,7 +19418,7 @@ msgid "" "but we are going to put them in a single Cargo project with two binaries. " "For this to work, the client and the server code should go under `src/bin` " "(see the [documentation](https://doc.rust-lang.org/cargo/reference/cargo-" -"targets.html#binaries)). " +"targets.html#binaries))." msgstr "" "通常在一个 Cargo 项目中，你只能有一个二进制文件，和一个 `src/main.rs` 文件。" "在这个项目中，我们需要两个二进制文件。一个用于客户端，另一个用于服务器。你可" @@ -19277,97 +19427,59 @@ msgstr "" "（参见[文档](https://doc.rust-lang.org/cargo/reference/cargo-targets." "html#binaries)）。" -#: src/exercises/concurrency/chat-app.md:55 +#: src/exercises/concurrency/chat-app.md:54 +#, fuzzy msgid "" "Copy the following server and client code into `src/bin/server.rs` and `src/" "bin/client.rs`, respectively. Your task is to complete these files as " -"described below. " +"described below." msgstr "" "将以下服务器和客户端代码分别复制到 `src/bin/server.rs` 和 `src/bin/client." "rs` 中。您的任务是按照下面的描述完成这些文件。" -#: src/exercises/concurrency/chat-app.md:59 +#: src/exercises/concurrency/chat-app.md:58 #: src/exercises/concurrency/solutions-afternoon.md:99 #, fuzzy msgid "_src/bin/server.rs_:" msgstr "`src/bin/server.rs`:" -#: src/exercises/concurrency/chat-app.md:63 -msgid "" -"```rust,compile_fail\n" -"use futures_util::sink::SinkExt;\n" -"use futures_util::stream::StreamExt;\n" -"use std::error::Error;\n" -"use std::net::SocketAddr;\n" -"use tokio::net::{TcpListener, TcpStream};\n" -"use tokio::sync::broadcast::{channel, Sender};\n" -"use tokio_websockets::{Message, ServerBuilder, WebsocketStream};\n" -"\n" -"async fn handle_connection(\n" -" addr: SocketAddr,\n" -" mut ws_stream: WebsocketStream,\n" -" bcast_tx: Sender,\n" -") -> Result<(), Box> {\n" -"\n" -" // TODO: For a hint, see the description of the task below.\n" -"\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), Box> {\n" -" let (bcast_tx, _) = channel(16);\n" -"\n" -" let listener = TcpListener::bind(\"127.0.0.1:2000\").await?;\n" -" println!(\"listening on port 2000\");\n" -"\n" -" loop {\n" -" let (socket, addr) = listener.accept().await?;\n" -" println!(\"New connection from {addr:?}\");\n" -" let bcast_tx = bcast_tx.clone();\n" -" tokio::spawn(async move {\n" -" // Wrap the raw TCP stream into a websocket.\n" -" let ws_stream = ServerBuilder::new().accept(socket).await?;\n" -"\n" -" handle_connection(addr, ws_stream, bcast_tx).await\n" -" });\n" -" }\n" -"}\n" -"```" +#: src/exercises/concurrency/chat-app.md:77 +#: src/exercises/concurrency/chat-app.md:124 +msgid "// TODO: For a hint, see the description of the task below.\n" +msgstr "" + +#: src/exercises/concurrency/chat-app.md:85 +#: src/exercises/concurrency/solutions-afternoon.md:147 +msgid "\"127.0.0.1:2000\"" +msgstr "" + +#: src/exercises/concurrency/chat-app.md:86 +#: src/exercises/concurrency/solutions-afternoon.md:148 +msgid "\"listening on port 2000\"" +msgstr "" + +#: src/exercises/concurrency/chat-app.md:90 +#: src/exercises/concurrency/solutions-afternoon.md:152 +msgid "\"New connection from {addr:?}\"" +msgstr "" + +#: src/exercises/concurrency/chat-app.md:93 +#: src/exercises/concurrency/solutions-afternoon.md:155 +msgid "// Wrap the raw TCP stream into a websocket.\n" msgstr "" -#: src/exercises/concurrency/chat-app.md:103 -#: src/exercises/concurrency/solutions-afternoon.md:166 +#: src/exercises/concurrency/chat-app.md:102 +#: src/exercises/concurrency/solutions-afternoon.md:164 #, fuzzy msgid "_src/bin/client.rs_:" msgstr "`src/bin/client.rs`:" -#: src/exercises/concurrency/chat-app.md:107 -msgid "" -"```rust,compile_fail\n" -"use futures_util::stream::StreamExt;\n" -"use futures_util::SinkExt;\n" -"use http::Uri;\n" -"use tokio::io::{AsyncBufReadExt, BufReader};\n" -"use tokio_websockets::{ClientBuilder, Message};\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), tokio_websockets::Error> {\n" -" let (mut ws_stream, _) =\n" -" ClientBuilder::from_uri(Uri::from_static(\"ws://127.0.0.1:2000\"))\n" -" .connect()\n" -" .await?;\n" -"\n" -" let stdin = tokio::io::stdin();\n" -" let mut stdin = BufReader::new(stdin).lines();\n" -"\n" -"\n" -" // TODO: For a hint, see the description of the task below.\n" -"\n" -"}\n" -"```" +#: src/exercises/concurrency/chat-app.md:116 +#: src/exercises/concurrency/solutions-afternoon.md:176 +msgid "\"ws://127.0.0.1:2000\"" msgstr "" -#: src/exercises/concurrency/chat-app.md:130 +#: src/exercises/concurrency/chat-app.md:129 msgid "Running the binaries" msgstr "运行可执行文件" @@ -19415,6 +19527,70 @@ msgid "" "clients, but the sender of the message." msgstr "可选：完成后，将代码更改为将消息广播给除消息发送者以外的所有客户端。" +#: src/exercises/concurrency/solutions-afternoon.md:1 +msgid "Concurrency Afternoon Exercise" +msgstr "并发编程：下午练习" + +#: src/exercises/concurrency/solutions-afternoon.md:5 +msgid "([back to exercise](dining-philosophers-async.md))" +msgstr "([返回练习](dining-philosophers-async.md))" + +#: src/exercises/concurrency/solutions-afternoon.md:33 +msgid "" +"// Add a delay before picking the second fork to allow the execution\n" +" // to transfer to another task\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:41 +msgid "// The locks are dropped here\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:61 +msgid "" +"// To avoid a deadlock, we have to break the symmetry\n" +" // somewhere. This will swap the forks without deinitializing\n" +" // either of them.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:75 +msgid "// tx is dropped here, so we don't need to explicitly drop it later\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:90 +msgid "\"Here is a thought: {thought}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:97 +msgid "([back to exercise](chat-app.md))" +msgstr "([返回练习](chat-app.md))" + +#: src/exercises/concurrency/solutions-afternoon.md:116 +msgid "\"Welcome to chat! Type a message\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:119 +#, fuzzy +msgid "" +"// A continuous loop for concurrently performing two tasks: (1) receiving\n" +" // messages from `ws_stream` and broadcasting them, and (2) receiving\n" +" // messages on `bcast_rx` and sending them to the client.\n" +msgstr "" +"提示：与之前一样，使用 `tokio::select!` 在一个连续的循环中并发执行两个任务：" +"(1) 从标准输入读取用户消息并发送给服务器，以及 (2) 从服务器接收消息并显示给用" +"户。" + +#: src/exercises/concurrency/solutions-afternoon.md:128 +msgid "\"From client {addr:?} {text:?}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:183 +msgid "// Continuous loop for concurrently sending and receiving messages.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md:190 +msgid "\"From server: {}\"" +msgstr "" + #: src/thanks.md:3 #, fuzzy msgid "" @@ -19447,313 +19623,438 @@ msgid "" msgstr "" #: src/glossary.md:32 -msgid "argument:" +msgid "" +"argument: \n" +"Information that is passed into a function or method." msgstr "" -#: src/glossary.md:33 -msgid "Bare-metal Rust: See [Bare-metal Rust](bare-metal.md)." +#: src/glossary.md:34 +msgid "" +"Bare-metal Rust: \n" +"Low-level Rust development, often deployed to a system without an operating " +"system. See [Bare-metal Rust](bare-metal.md)." msgstr "" -#: src/glossary.md:34 +#: src/glossary.md:37 msgid "" "block: \n" "See [Blocks](control-flow/blocks.md) and _scope_." msgstr "" -#: src/glossary.md:36 +#: src/glossary.md:39 msgid "" "borrow: \n" "See [Borrowing](ownership/borrowing.md)." msgstr "" -#: src/glossary.md:38 +#: src/glossary.md:41 msgid "" "borrow checker: \n" "The part of the Rust compiler which checks that all borrows are valid." msgstr "" -#: src/glossary.md:40 +#: src/glossary.md:43 msgid "" "brace: \n" "`{` and `}`. Also called _curly brace_, they delimit _blocks_." msgstr "" -#: src/glossary.md:42 -msgid "build:" +#: src/glossary.md:45 +msgid "" +"build: \n" +"The process of converting source code into executable code or a usable " +"program." msgstr "" -#: src/glossary.md:43 -msgid "call:" +#: src/glossary.md:48 +msgid "" +"call: \n" +"To invoke or execute a function or method." msgstr "" -#: src/glossary.md:44 +#: src/glossary.md:50 msgid "" "channel: \n" "Used to safely pass messages [between threads](concurrency/channels.md)." msgstr "" -#: src/glossary.md:46 +#: src/glossary.md:52 #, fuzzy msgid "" "Comprehensive Rust 🦀: \n" "The courses here are jointly called Comprehensive Rust 🦀." msgstr "欢迎来到 Comprehensive Rust 🦀" -#: src/glossary.md:48 -#, fuzzy -msgid "concurrency:" -msgstr "并发" +#: src/glossary.md:54 +msgid "" +"concurrency: \n" +"The execution of multiple tasks or processes at the same time." +msgstr "" -#: src/glossary.md:49 +#: src/glossary.md:56 #, fuzzy msgid "" "Concurrency in Rust: \n" "See [Concurrency in Rust](concurrency.md)." msgstr "欢迎了解 Rust 中的并发" -#: src/glossary.md:51 -#, fuzzy -msgid "constant:" -msgstr "`const`" +#: src/glossary.md:58 +msgid "" +"constant: \n" +"A value that does not change during the execution of a program." +msgstr "" -#: src/glossary.md:52 -#, fuzzy -msgid "control flow:" -msgstr "控制流" +#: src/glossary.md:60 +msgid "" +"control flow: \n" +"The order in which the individual statements or instructions are executed in " +"a program." +msgstr "" -#: src/glossary.md:53 -msgid "crash:" +#: src/glossary.md:63 +msgid "" +"crash: \n" +"An unexpected and unhandled failure or termination of a program." msgstr "" -#: src/glossary.md:54 -#, fuzzy -msgid "enumeration:" -msgstr "实现" +#: src/glossary.md:65 +msgid "" +"enumeration: \n" +"A data type that consists of named constant values." +msgstr "" -#: src/glossary.md:55 -msgid "error:" +#: src/glossary.md:67 +msgid "" +"error: \n" +"An unexpected condition or result that deviates from the expected behavior." msgstr "" -#: src/glossary.md:56 -#, fuzzy -msgid "error handling:" -msgstr "错误处理" +#: src/glossary.md:69 +msgid "" +"error handling: \n" +"The process of managing and responding to errors that occur during program " +"execution." +msgstr "" -#: src/glossary.md:57 -#, fuzzy -msgid "exercise:" -msgstr "习题" +#: src/glossary.md:72 +msgid "" +"exercise: \n" +"A task or problem designed to practice and test programming skills." +msgstr "" -#: src/glossary.md:58 -#, fuzzy -msgid "function:" -msgstr "函数" +#: src/glossary.md:74 +msgid "" +"function: \n" +"A reusable block of code that performs a specific task." +msgstr "" -#: src/glossary.md:59 -#, fuzzy -msgid "garbage collector:" -msgstr "垃圾回收" +#: src/glossary.md:76 +msgid "" +"garbage collector: \n" +"A mechanism that automatically frees up memory occupied by objects that are " +"no longer in use." +msgstr "" -#: src/glossary.md:60 -#, fuzzy -msgid "generics:" -msgstr "泛型" +#: src/glossary.md:79 +msgid "" +"generics: \n" +"A feature that allows writing code with placeholders for types, enabling " +"code reuse with different data types." +msgstr "" -#: src/glossary.md:61 -msgid "immutable:" +#: src/glossary.md:82 +msgid "" +"immutable: \n" +"Unable to be changed after creation." msgstr "" -#: src/glossary.md:62 -#, fuzzy -msgid "integration test:" -msgstr "集成测试" +#: src/glossary.md:84 +msgid "" +"integration test: \n" +"A type of test that verifies the interactions between different parts or " +"components of a system." +msgstr "" -#: src/glossary.md:63 -msgid "keyword:" +#: src/glossary.md:87 +msgid "" +"keyword: \n" +"A reserved word in a programming language that has a specific meaning and " +"cannot be used as an identifier." msgstr "" -#: src/glossary.md:64 -#, fuzzy -msgid "library:" -msgstr "库" +#: src/glossary.md:90 +msgid "" +"library: \n" +"A collection of precompiled routines or code that can be used by programs." +msgstr "" -#: src/glossary.md:65 -msgid "macro:" +#: src/glossary.md:92 +msgid "" +"macro: \n" +"Rust macros can be recognized by a `!` in the name. Macros are used when " +"normal functions are not enough. A typical example is `format!`, which takes " +"a variable number of arguments, which isn't supported by Rust functions." msgstr "" -#: src/glossary.md:66 -#, fuzzy -msgid "main function:" -msgstr "调用 Unsafe 函数" +#: src/glossary.md:96 +msgid "" +"`main` function: \n" +"Rust programs start executing with the `main` function." +msgstr "" -#: src/glossary.md:67 -msgid "match:" +#: src/glossary.md:98 +msgid "" +"match: \n" +"A control flow construct in Rust that allows for pattern matching on the " +"value of an expression." msgstr "" -#: src/glossary.md:68 -#, fuzzy -msgid "memory leak:" -msgstr "内存泄漏。" +#: src/glossary.md:101 +msgid "" +"memory leak: \n" +"A situation where a program fails to release memory that is no longer " +"needed, leading to a gradual increase in memory usage." +msgstr "" -#: src/glossary.md:69 -#, fuzzy -msgid "method:" -msgstr "方法" +#: src/glossary.md:104 +msgid "" +"method: \n" +"A function associated with an object or a type in Rust." +msgstr "" -#: src/glossary.md:70 -#, fuzzy -msgid "module:" -msgstr "模块" +#: src/glossary.md:106 +msgid "" +"module: \n" +"A namespace that contains definitions, such as functions, types, or traits, " +"to organize code in Rust." +msgstr "" -#: src/glossary.md:71 -msgid "move:" +#: src/glossary.md:109 +msgid "" +"move: \n" +"The transfer of ownership of a value from one variable to another in Rust." msgstr "" -#: src/glossary.md:72 -msgid "mutable:" -msgstr "可变：" +#: src/glossary.md:111 +msgid "" +"mutable: \n" +"A property in Rust that allows variables to be modified after they have been " +"declared." +msgstr "" -#: src/glossary.md:73 -#, fuzzy -msgid "ownership:" -msgstr "所有权" +#: src/glossary.md:114 +msgid "" +"ownership: \n" +"The concept in Rust that defines which part of the code is responsible for " +"managing the memory associated with a value." +msgstr "" -#: src/glossary.md:74 -#, fuzzy -msgid "panic:" -msgstr "Panics" +#: src/glossary.md:117 +msgid "" +"panic: \n" +"An unrecoverable error condition in Rust that results in the termination of " +"the program." +msgstr "" -#: src/glossary.md:75 -msgid "parameter:" +#: src/glossary.md:120 +msgid "" +"parameter: \n" +"A value that is passed into a function or method when it is called." msgstr "" -#: src/glossary.md:76 -msgid "pattern:" +#: src/glossary.md:122 +msgid "" +"pattern: \n" +"A combination of values, literals, or structures that can be matched against " +"an expression in Rust." msgstr "" -#: src/glossary.md:77 -msgid "payload:" +#: src/glossary.md:125 +msgid "" +"payload: \n" +"The data or information carried by a message, event, or data structure." msgstr "" -#: src/glossary.md:78 -msgid "program:" +#: src/glossary.md:127 +msgid "" +"program: \n" +"A set of instructions that a computer can execute to perform a specific task " +"or solve a particular problem." msgstr "" -#: src/glossary.md:79 -msgid "programming language:" +#: src/glossary.md:130 +msgid "" +"programming language: \n" +"A formal system used to communicate instructions to a computer, such as Rust." msgstr "" -#: src/glossary.md:80 -#, fuzzy -msgid "receiver:" -msgstr "驱动程序" +#: src/glossary.md:132 +msgid "" +"receiver: \n" +"The first parameter in a Rust method that represents the instance on which " +"the method is called." +msgstr "" -#: src/glossary.md:81 -#, fuzzy -msgid "reference counting:" -msgstr "解引用原始指针。" +#: src/glossary.md:135 +msgid "" +"reference counting: \n" +"A memory management technique in which the number of references to an object " +"is tracked, and the object is deallocated when the count reaches zero." +msgstr "" -#: src/glossary.md:82 -msgid "return:" +#: src/glossary.md:138 +msgid "" +"return: \n" +"A keyword in Rust used to indicate the value to be returned from a function." msgstr "" -#: src/glossary.md:83 -#, fuzzy -msgid "Rust:" -msgstr "Rustdoc" +#: src/glossary.md:140 +msgid "" +"Rust: \n" +"A systems programming language that focuses on safety, performance, and " +"concurrency." +msgstr "" -#: src/glossary.md:84 +#: src/glossary.md:143 msgid "" "Rust Fundamentals: \n" "Days 1 to 3 of this course." msgstr "" -#: src/glossary.md:86 +#: src/glossary.md:145 #, fuzzy msgid "" "Rust in Android: \n" "See [Rust in Android](android.md)." msgstr "欢迎来到Android 中的Rust" -#: src/glossary.md:88 -msgid "safe:" +#: src/glossary.md:147 +#, fuzzy +msgid "" +"Rust in Chromium: \n" +"See [Rust in Chromium](chromium.md)." +msgstr "欢迎来到Android 中的Rust" + +#: src/glossary.md:149 +msgid "" +"safe: \n" +"Refers to code that adheres to Rust's ownership and borrowing rules, " +"preventing memory-related errors." msgstr "" -#: src/glossary.md:89 -msgid "scope:" +#: src/glossary.md:152 +msgid "" +"scope: \n" +"The region of a program where a variable is valid and can be used." msgstr "" -#: src/glossary.md:90 -#, fuzzy -msgid "standard library:" -msgstr "标准库" +#: src/glossary.md:154 +msgid "" +"standard library: \n" +"A collection of modules providing essential functionality in Rust." +msgstr "" -#: src/glossary.md:91 -#, fuzzy -msgid "static:" -msgstr "`static`" +#: src/glossary.md:156 +msgid "" +"static: \n" +"A keyword in Rust used to define static variables or items with a `'static` " +"lifetime." +msgstr "" -#: src/glossary.md:92 -#, fuzzy -msgid "string:" -msgstr "String" +#: src/glossary.md:159 +msgid "" +"string: \n" +"A data type storing textual data. See [`String` vs `str`](basic-syntax/" +"string-slices.html) for more." +msgstr "" -#: src/glossary.md:93 -#, fuzzy -msgid "struct:" -msgstr "结构体" +#: src/glossary.md:162 +msgid "" +"struct: \n" +"A composite data type in Rust that groups together variables of different " +"types under a single name." +msgstr "" -#: src/glossary.md:94 -msgid "test:" +#: src/glossary.md:165 +msgid "" +"test: \n" +"A Rust module containing functions that test the correctness of other " +"functions." msgstr "" -#: src/glossary.md:95 -#, fuzzy -msgid "thread:" -msgstr "线程" +#: src/glossary.md:168 +msgid "" +"thread: \n" +"A separate sequence of execution in a program, allowing concurrent execution." +msgstr "" -#: src/glossary.md:96 -#, fuzzy -msgid "thread safety:" -msgstr "线程" +#: src/glossary.md:170 +msgid "" +"thread safety: \n" +"The property of a program that ensures correct behavior in a multithreaded " +"environment." +msgstr "" -#: src/glossary.md:97 -#, fuzzy -msgid "trait:" -msgstr "特征" +#: src/glossary.md:173 +msgid "" +"trait: \n" +"A collection of methods defined for an unknown type, providing a way to " +"achieve polymorphism in Rust." +msgstr "" -#: src/glossary.md:98 -msgid "type:" +#: src/glossary.md:176 +msgid "" +"trait bound: \n" +"An abstraction where you can require types to implement some traits of your " +"interest." msgstr "" -#: src/glossary.md:99 -#, fuzzy -msgid "type inference:" -msgstr "类型推导" +#: src/glossary.md:179 +msgid "" +"type: \n" +"A classification that specifies which operations can be performed on values " +"of a particular kind in Rust." +msgstr "" -#: src/glossary.md:100 -#, fuzzy -msgid "undefined behavior:" -msgstr "Rust 没有运行时未定义行为：" +#: src/glossary.md:182 +msgid "" +"type inference: \n" +"The ability of the Rust compiler to deduce the type of a variable or " +"expression." +msgstr "" -#: src/glossary.md:101 -#, fuzzy -msgid "union:" -msgstr "联合体" +#: src/glossary.md:185 +msgid "" +"undefined behavior: \n" +"Actions or conditions in Rust that have no specified result, often leading " +"to unpredictable program behavior." +msgstr "" -#: src/glossary.md:102 -#, fuzzy -msgid "unit test:" -msgstr "单元测试" +#: src/glossary.md:188 +msgid "" +"union: \n" +"A data type that can hold values of different types but only one at a time." +msgstr "" -#: src/glossary.md:103 -msgid "unsafe:" -msgstr "是（不安全）" +#: src/glossary.md:190 +msgid "" +"unit test: \n" +"Rust comes with built-in support for running small unit tests and larger " +"integration tests. See [Unit Tests](testing/unit-tests.html)." +msgstr "" -#: src/glossary.md:104 -#, fuzzy -msgid "variable:\\" -msgstr "变量" +#: src/glossary.md:193 +msgid "" +"unsafe: \n" +"The subset of Rust which allows you to trigger _undefined behavior_. See " +"[Unsafe Rust](unsafe.html)." +msgstr "" + +#: src/glossary.md:196 +msgid "" +"variable: \n" +"A memory location storing data. Variables are valid in a _scope_." +msgstr "" #: src/other-resources.md:1 msgid "Other Rust Resources" @@ -19863,7 +20164,7 @@ msgstr "" "[面向嵌入式 C 程序员的 Rust](https://docs.opentitan.org/doc/ug/rust_for_c/)：" "从使用 C 语言编写固件的开发者的角度介绍 Rust。" -#: src/other-resources.md:42 +#: src/other-resources.md:41 msgid "" "[Rust for professionals](https://overexact.com/rust-for-professionals/): " "covers the syntax of Rust using side-by-side comparisons with other " @@ -19873,7 +20174,7 @@ msgstr "" "for-professionals/)：通过与其他语言（例如 C、C++、Java、JavaScript 和 " "Python）进行并排比较，介绍 Rust 的语法。" -#: src/other-resources.md:45 +#: src/other-resources.md:44 msgid "" "[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " "you learn Rust." @@ -19881,7 +20182,7 @@ msgstr "" "[Rust on Exercism（在 Exercism 上学 Rust）](https://exercism.org/tracks/" "rust)：100 多项练习助您学习 Rust。" -#: src/other-resources.md:47 +#: src/other-resources.md:46 msgid "" "[Ferrous Teaching Material](https://ferrous-systems.github.io/teaching-" "material/index.html): a series of small presentations covering both basic " @@ -19892,7 +20193,7 @@ msgstr "" "material/index.html)：一系列小演示文稿，涵盖 Rust 语言的基础知识和高级部分。" "还涵盖了 WebAssembly 和 async/await 等其他主题。" -#: src/other-resources.md:52 +#: src/other-resources.md:50 msgid "" "[Beginner's Series to Rust](https://docs.microsoft.com/en-us/shows/beginners-" "series-to-rust/) and [Take your first steps with Rust](https://docs." @@ -19905,7 +20206,7 @@ msgstr "" "learn/paths/rust-first-steps/)：两个面向新手开发者的 Rust 指南。第一个指南包" "含 35 个视频，第二个指南包含 11 个模块，内容涵盖 Rust 语法和基本结构。" -#: src/other-resources.md:58 +#: src/other-resources.md:56 msgid "" "[Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial." "github.io/too-many-lists/): in-depth exploration of Rust's memory management " @@ -19914,7 +20215,7 @@ msgstr "" "[通过大量的链表学习Rust](https://rust-unofficial.github.io/too-many-lists/)：" "通过实现几种不同类型的列表结构，深入探索 Rust 的内存管理规则。" -#: src/other-resources.md:63 +#: src/other-resources.md:61 msgid "" "Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " "for even more Rust books." @@ -19982,2200 +20283,4299 @@ msgstr "" "[CXX](https://cxx.rs/) 的图片。如需了解详情（包括许可条款）， 请参阅 " "`third_party/cxx/` 目录。" -#: src/credits.md:34 -msgid "" -"The [Why Rust? - An Example in C](why-rust/an-example-in-c.md) section has " -"been taken from the presentation slides of [Colin Finck's Master Thesis]" -"(https://colinfinck.de/Master_Thesis_Colin_Finck.pdf). It has been " -"relicensed under the terms of the Apache 2.0 license for this course by the " -"author." -msgstr "" +#~ msgid "Small Example" +#~ msgstr "简短示例" -#: src/exercises/solutions.md:3 -msgid "You will find solutions to the exercises on the following pages." -msgstr "您将在下面的页面找到练习的解答。" +#~ msgid "Why Rust?" +#~ msgstr "为什么选择 Rust？" -#: src/exercises/solutions.md:5 -msgid "" -"Feel free to ask questions about the solutions [on GitHub](https://github." -"com/google/comprehensive-rust/discussions). Let us know if you have a " -"different or better solution than what is presented here." -msgstr "" -"欢迎您在 [GitHub](https://github.com/google/comprehensive-rust/discussions) " -"上提问关于解决方案的问题。如果您有与此处呈现的不同或更好的解决方案，请告诉我" -"们。" +#~ msgid "An Example in C" +#~ msgstr "C语言示例" -#: src/exercises/day-1/solutions-morning.md:1 -msgid "Day 1 Morning Exercises" -msgstr "第一天上午的练习" +#~ msgid "Compile Time Guarantees" +#~ msgstr "编译期保障" -#: src/exercises/day-1/solutions-morning.md:5 -msgid "([back to exercise](for-loops.md))" -msgstr "([返回练习](for-loops.md))" +#~ msgid "Runtime Guarantees" +#~ msgstr "运行时保障" -#: src/exercises/day-1/solutions-morning.md:7 -msgid "" -"```rust\n" -"fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" -" let mut result = [[0; 3]; 3];\n" -" for i in 0..3 {\n" -" for j in 0..3 {\n" -" result[j][i] = matrix[i][j];\n" -" }\n" -" }\n" -" return result;\n" -"}\n" -"\n" -"fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" -" for row in matrix {\n" -" println!(\"{row:?}\");\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_transpose() {\n" -" let matrix = [\n" -" [101, 102, 103], //\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -" let transposed = transpose(matrix);\n" -" assert_eq!(\n" -" transposed,\n" -" [\n" -" [101, 201, 301], //\n" -" [102, 202, 302],\n" -" [103, 203, 303],\n" -" ]\n" -" );\n" -"}\n" -"\n" -"fn main() {\n" -" let matrix = [\n" -" [101, 102, 103], // <-- the comment makes rustfmt add a newline\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -"\n" -" println!(\"matrix:\");\n" -" pretty_print(&matrix);\n" -"\n" -" let transposed = transpose(matrix);\n" -" println!(\"transposed:\");\n" -" pretty_print(&transposed);\n" -"}\n" -"```" -msgstr "" +#~ msgid "Modern Features" +#~ msgstr "现代特性" -#: src/exercises/day-1/solutions-morning.md:57 -msgid "Bonus question" -msgstr "附加问题" +#~ msgid "Basic Syntax" +#~ msgstr "基本语法" -#: src/exercises/day-1/solutions-morning.md:59 -msgid "" -"It requires more advanced concepts. It might seem that we could use a slice-" -"of-slices (`&[&[i32]]`) as the input type to transpose and thus make our " -"function handle any size of matrix. However, this quickly breaks down: the " -"return type cannot be `&[&[i32]]` since it needs to own the data you return." -msgstr "" -"这需要更高级的概念。看起来，我们可以使用切片的切片（`&[&[i32]]`）作为输入类型" -"来进行转置，从而使我们的函数能够处理任意大小的矩阵。然而，这很快就会崩溃：返" -"回类型不能是 `&[&[i32]]`，因为它需要拥有您返回的数据。" +#~ msgid "String vs str" +#~ msgstr "String vs str" -#: src/exercises/day-1/solutions-morning.md:61 -msgid "" -"You can attempt to use something like `Vec>`, but this doesn't work " -"out-of-the-box either: it's hard to convert from `Vec>` to " -"`&[&[i32]]` so now you cannot easily use `pretty_print` either." -msgstr "" -"您可以尝试使用类似 `Vec>` 的方式，但这也无法直接工作：从 " -"`Vec>` 转换为 `&[&[i32]]` 很困难，因此您现在也不能轻松使用 " -"`pretty_print`。" +#~ msgid "Rustdoc" +#~ msgstr "Rustdoc" -#: src/exercises/day-1/solutions-morning.md:63 -msgid "" -"Once we get to traits and generics, we'll be able to use the [`std::convert::" -"AsRef`](https://doc.rust-lang.org/std/convert/trait.AsRef.html) trait to " -"abstract over anything that can be referenced as a slice." -msgstr "" -"了解 trait 和泛型后，我们就可以使用[“std::convert::AsRef”](https://doc.rust-" -"lang.org/std/convert/trait.AsRef.html)trait 来抽象化任何可作为 Slice 引用的内" -"容了。" +#~ msgid "Overloading" +#~ msgstr "重载" -#: src/exercises/day-1/solutions-morning.md:65 -msgid "" -"```rust\n" -"use std::convert::AsRef;\n" -"use std::fmt::Debug;\n" -"\n" -"fn pretty_print(matrix: Matrix)\n" -"where\n" -" T: Debug,\n" -" // A line references a slice of items\n" -" Line: AsRef<[T]>,\n" -" // A matrix references a slice of lines\n" -" Matrix: AsRef<[Line]>\n" -"{\n" -" for row in matrix.as_ref() {\n" -" println!(\"{:?}\", row.as_ref());\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" // &[&[i32]]\n" -" pretty_print(&[&[1, 2, 3], &[4, 5, 6], &[7, 8, 9]]);\n" -" // [[&str; 2]; 2]\n" -" pretty_print([[\"a\", \"b\"], [\"c\", \"d\"]]);\n" -" // Vec>\n" -" pretty_print(vec![vec![1, 2], vec![3, 4]]);\n" -"}\n" -"```" -msgstr "" +#~ msgid "Arrays and for Loops" +#~ msgstr "数组与 for 循环" -#: src/exercises/day-1/solutions-morning.md:92 -msgid "" -"In addition, the type itself would not enforce that the child slices are of " -"the same length, so such variable could contain an invalid matrix." -msgstr "" -"此外，类型本身不会强制要求子切片具有相同的长度，因此这样的变量可能包含一个无" -"效的矩阵。" +#~ msgid "if expressions" +#~ msgstr "if 表达式" -#: src/exercises/day-1/solutions-afternoon.md:1 -msgid "Day 1 Afternoon Exercises" -msgstr "第一天下午的练习" +#~ msgid "for expressions" +#~ msgstr "for 表达式" -#: src/exercises/day-1/solutions-afternoon.md:5 -msgid "([back to exercise](luhn.md))" -msgstr "([返回练习](luhn.md))" +#~ msgid "while expressions" +#~ msgstr "while 表达式" -#: src/exercises/day-1/solutions-afternoon.md:7 -msgid "" -"```rust\n" -"pub fn luhn(cc_number: &str) -> bool {\n" -" let mut digits_seen = 0;\n" -" let mut sum = 0;\n" -" for (i, ch) in cc_number.chars().rev().filter(|&ch| ch != ' ')." -"enumerate() {\n" -" match ch.to_digit(10) {\n" -" Some(d) => {\n" -" sum += if i % 2 == 1 {\n" -" let dd = d * 2;\n" -" dd / 10 + dd % 10\n" -" } else {\n" -" d\n" -" };\n" -" digits_seen += 1;\n" -" }\n" -" None => return false,\n" -" }\n" -" }\n" -"\n" -" if digits_seen < 2 {\n" -" return false;\n" -" }\n" -"\n" -" sum % 10 == 0\n" -"}\n" -"\n" -"fn main() {\n" -" let cc_number = \"1234 5678 1234 5670\";\n" -" println!(\n" -" \"Is {cc_number} a valid credit card number? {}\",\n" -" if luhn(cc_number) { \"yes\" } else { \"no\" }\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_non_digit_cc_number() {\n" -" assert!(!luhn(\"foo\"));\n" -" assert!(!luhn(\"foo 0 0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty_cc_number() {\n" -" assert!(!luhn(\"\"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_digit_cc_number() {\n" -" assert!(!luhn(\"0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_two_digit_cc_number() {\n" -" assert!(luhn(\" 0 0 \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_valid_cc_number() {\n" -" assert!(luhn(\"4263 9826 4026 9299\"));\n" -" assert!(luhn(\"4539 3195 0343 6467\"));\n" -" assert!(luhn(\"7992 7398 713\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_invalid_cc_number() {\n" -" assert!(!luhn(\"4223 9826 4026 9299\"));\n" -" assert!(!luhn(\"4539 3195 0343 6476\"));\n" -" assert!(!luhn(\"8273 1232 7352 0569\"));\n" -"}\n" -"```" -msgstr "" +#~ msgid "break & continue" +#~ msgstr "break & continue" + +#~ msgid "loop expressions" +#~ msgstr "loop 表达式" + +#~ msgid "Variant Payloads" +#~ msgstr "变体载荷" + +#~ msgid "Enum Sizes" +#~ msgstr "枚举大小" + +#~ msgid "Novel Control Flow" +#~ msgstr "新式控制流" + +#~ msgid "if let expressions" +#~ msgstr "if let 表达式" + +#~ msgid "while let expressions" +#~ msgstr "while let 表达式" + +#~ msgid "match expressions" +#~ msgstr "match 表达式" + +#~ msgid "Destructuring Structs" +#~ msgstr "解构结构体" + +#~ msgid "Destructuring Arrays" +#~ msgstr "解构数组" + +#~ msgid "Match Guards" +#~ msgstr "匹配守卫" + +#~ msgid "Stack vs Heap" +#~ msgstr "栈 vs 堆" + +#~ msgid "Stack Memory" +#~ msgstr "栈内存" + +#~ msgid "Manual Memory Management" +#~ msgstr "手动内存管理" + +#~ msgid "Scope-Based Memory Management" +#~ msgstr "基于作用域的内存管理" + +#~ msgid "Garbage Collection" +#~ msgstr "垃圾回收" + +#~ msgid "Rust Memory Management" +#~ msgstr "Rust 内存管理" + +#~ msgid "Moved Strings in Rust" +#~ msgstr "Rust 中移动的字符串" + +#~ msgid "Double Frees in Modern C++" +#~ msgstr "现代 C++ 中的双重释放" + +#~ msgid "Moves in Function Calls" +#~ msgstr "函数调用中的移动" + +#~ msgid "Copying and Cloning" +#~ msgstr "复制和克隆" + +#~ msgid "Shared and Unique Borrows" +#~ msgstr "共享和唯一的借用" + +#~ msgid "Field Shorthand Syntax" +#~ msgstr "字段简写语法" + +#~ msgid "Method Receiver" +#~ msgstr "方法接收者" + +#~ msgid "Storing Books" +#~ msgstr "书籍存储" + +#~ msgid "Option and Result" +#~ msgstr "Option 和 Result" + +#~ msgid "Vec" +#~ msgstr "Vec" + +#~ msgid "HashMap" +#~ msgstr "哈希表" + +#~ msgid "Box" +#~ msgstr "Box" + +#~ msgid "Recursive Data Types" +#~ msgstr "递归数据类型" + +#~ msgid "Rc" +#~ msgstr "Rc" + +#~ msgid "Cell/RefCell" +#~ msgstr "Cell/RefCell" + +#~ msgid "Iterators and Ownership" +#~ msgstr "迭代器和所有权" + +#~ msgid "Strings and Iterators" +#~ msgstr "字符串和迭代器" + +#~ msgid "Generic Methods" +#~ msgstr "泛型方法" + +#~ msgid "Monomorphization" +#~ msgstr "单态化" + +#~ msgid "Default Methods" +#~ msgstr "默认方法" + +#~ msgid "impl Trait" +#~ msgstr "impl Trait" + +#~ msgid "Important Traits" +#~ msgstr "重要特征" + +#~ msgid "From and Into" +#~ msgstr "From 和 Into" + +#~ msgid "Default" +#~ msgstr "Default" + +#~ msgid "Operators: Add, Mul, ..." +#~ msgstr "运算符：Add、Mul..." + +#~ msgid "Closures: Fn, FnMut, FnOnce" +#~ msgstr "闭包：Fn、FnMut、FnOnce" + +#~ msgid "Points and Polygons" +#~ msgstr "点和多边形" + +#~ msgid "Catching Stack Unwinding" +#~ msgstr "捕获堆栈展开" + +#~ msgid "Structured Error Handling" +#~ msgstr "结构化错误处理" + +#~ msgid "Propagating Errors with ?" +#~ msgstr "使用 ? 传播错误" + +#~ msgid "Converting Error Types" +#~ msgstr "转换错误类型" + +#~ msgid "Deriving Error Enums" +#~ msgstr "派生错误枚举" + +#~ msgid "Adding Context to Errors" +#~ msgstr "为错误添加背景信息" + +#~ msgid "no_std" +#~ msgstr "no_std" + +#~ msgid "alloc" +#~ msgstr "alloc" + +#, fuzzy +#~ msgid "embedded-hal" +#~ msgstr "embedded-hal" + +#~ msgid "zerocopy" +#~ msgstr "zerocopy" + +#~ msgid "buddy_system_allocator" +#~ msgstr "buddy_system_allocator" + +#~ msgid "tinyvec" +#~ msgstr "tinyvec" + +#~ msgid "spin" +#~ msgstr "转动" + +#~ msgid "Send and Sync" +#~ msgstr "Send 和 Sync" + +#~ msgid "Send" +#~ msgstr "Send" + +#~ msgid "Sync" +#~ msgstr "Sync" + +#~ msgid "Arc" +#~ msgstr "Arc" + +#~ msgid "Mutex" +#~ msgstr "Mutex" + +#~ msgid "async/await" +#~ msgstr "async/await" + +#~ msgid "Pin" +#~ msgstr "固定" + +#~ msgid "Day 1 Morning" +#~ msgstr "第一天上午" + +#~ msgid "Day 1 Afternoon" +#~ msgstr "第一天下午" + +#~ msgid "Day 2 Morning" +#~ msgstr "第二天上午" + +#~ msgid "Day 2 Afternoon" +#~ msgstr "第二天下午" + +#~ msgid "Day 3 Morning" +#~ msgstr "第三天上午" + +#~ msgid "Day 3 Afternoon" +#~ msgstr "第三天下午" + +#~ msgid "Bare Metal Rust Morning" +#~ msgstr "嵌入式 Rust：入门篇" + +#~ msgid "Concurrency Morning" +#~ msgstr "并发编程：入门篇" + +#~ msgid "Concurrency Afternoon" +#~ msgstr "并发编程：进阶篇" + +#~ msgid "" +#~ "Day 1: Basic Rust, syntax, control flow, creating and consuming values." +#~ msgstr "第 1 天：Rust 基础知识、语法、控制流、创建及使用值。" + +#~ msgid "" +#~ "Day 2: Memory management, ownership, compound data types, and the " +#~ "standard library." +#~ msgstr "第 2 天：内存管理、所有权、复合数据类类型及标准库。" + +#~ msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." +#~ msgstr "第 3 天：泛型、trait、错误处理、测试和不安全 Rust。" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "Control flow constructs: `if`, `if let`, `while`, `while let`, `break`, " +#~ "and `continue`." +#~ msgstr "" +#~ "控制流的构造：`if`、`if let`、`while`、`while let`、`break` 和 " +#~ "`continue`。" + +#~ msgid "" +#~ "The idea for the first day is to show _just enough_ of Rust to be able to " +#~ "speak about the famous borrow checker. The way Rust handles memory is a " +#~ "major feature and we should show students this right away." +#~ msgstr "" +#~ "第一天的主要目标是要谈到著名的 borrow checker，其他方面点到为止。Rust 处理" +#~ "内存的方式是其主要特点，这点我们应该尽早展示给学生。" + +#~ msgid "" +#~ "If you're teaching this in a classroom, this is a good place to go over " +#~ "the schedule. We suggest splitting the day into two parts (following the " +#~ "slides):" +#~ msgstr "" +#~ "如果你是在教室里教授此课程，不妨在这里介绍一下时间安排。 这边建议是把每天" +#~ "分成两部分（跟着幻灯片来）：" + +#~ msgid "Morning: 9:00 to 12:00," +#~ msgstr "早上：9:00 到 12:00，" + +#~ msgid "Afternoon: 13:00 to 16:00." +#~ msgstr "下午：13:00 到 16:00。" + +#~ msgid "" +#~ "You can of course adjust this as necessary. Please make sure to include " +#~ "breaks, we recommend a break every hour!" +#~ msgstr "" +#~ "当然你也可以看情况调整时间。但是请务必记得提供休息时间。我们建议每个小时休" +#~ "息一次！" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Hello 🌍!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Hello 🌍!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "Here is a small example program in Rust:" +#~ msgstr "以下是一个简短的 Rust 示例程序：" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() { // Program entry point\n" +#~ " let mut x: i32 = 6; // Mutable variable binding\n" +#~ " print!(\"{x}\"); // Macro for printing, like printf\n" +#~ " while x != 1 { // No parenthesis around expression\n" +#~ " if x % 2 == 0 { // Math like in other languages\n" +#~ " x = x / 2;\n" +#~ " } else {\n" +#~ " x = 3 * x + 1;\n" +#~ " }\n" +#~ " print!(\" -> {x}\");\n" +#~ " }\n" +#~ " println!();\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() { // 程序入口\n" +#~ " let mut x: i32 = 6; // 可变变量绑定\n" +#~ " print!(\"{x}\"); // 与 printf 类似的输出宏\n" +#~ " while x != 1 { // 表达式周围没有括号\n" +#~ " if x % 2 == 0 { // 与其他语言类似的数值计算\n" +#~ " x = x / 2;\n" +#~ " } else {\n" +#~ " x = 3 * x + 1;\n" +#~ " }\n" +#~ " print!(\" -> {x}\");\n" +#~ " }\n" +#~ " println!();\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "The code implements the Collatz conjecture: it is believed that the loop " +#~ "will always end, but this is not yet proved. Edit the code and play with " +#~ "different inputs." +#~ msgstr "" +#~ "这段代码实现了 Collatz 猜想：猜想认为该循环总是会结束，但该猜想还没有被证" +#~ "明。可以编辑代码来尝试不同的输入。" + +#~ msgid "" +#~ "Explain that all variables are statically typed. Try removing `i32` to " +#~ "trigger type inference. Try with `i8` instead and trigger a runtime " +#~ "integer overflow." +#~ msgstr "" +#~ "说明所有变量的类型都是静态的。尝试删除 `i32` 来触发类型推断。尝试使用 " +#~ "`i8` 来触发运行时整数溢出。" + +#~ msgid "Change `let mut x` to `let x`, discuss the compiler error." +#~ msgstr "将 `let mut x` 改为 `let x`，讨论出现的编译错误。" + +#~ msgid "" +#~ "Show how `print!` gives a compilation error if the arguments don't match " +#~ "the format string." +#~ msgstr "展示 `print!` 在参数与格式字符串不匹配时产生的编译错误。" + +#~ msgid "" +#~ "Show how you need to use `{}` as a placeholder if you want to print an " +#~ "expression which is more complex than just a single variable." +#~ msgstr "展示如何使用 `{}` 作为占位符，来输出比单个变量更复杂的表达式。" + +#~ msgid "" +#~ "Show the students the standard library, show them how to search for `std::" +#~ "fmt` which has the rules of the formatting mini-language. It's important " +#~ "that the students become familiar with searching in the standard library." +#~ msgstr "" +#~ "向学生展示标准库，展示如何搜索 `std::fmt`，其中包含用于格式化字符串的微型" +#~ "语言规则。要点是让学生熟悉在标准库中搜索的过程。" + +#~ msgid "" +#~ "In a shell `rustup doc std::fmt` will open a browser on the local std::" +#~ "fmt documentation" +#~ msgstr "" +#~ "在 shell 中，运行 `rustup doc std::fmt` 会在浏览器中打开本地 std::fmt 文档" + +#~ msgid "Compile time memory safety." +#~ msgstr "编译期内存安全。" + +#~ msgid "Lack of undefined runtime behavior." +#~ msgstr "没有运行时未定义行为。" + +#~ msgid "Modern language features." +#~ msgstr "现代的编程语言特性。" + +#~ msgid "Let's consider the following \"minimum wrong example\" program in C:" +#~ msgstr "让我们查看以下 C 语言的“最小错误示例”程序：" + +#~ msgid "How many bugs do you spot?" +#~ msgstr "你发现了多少 bug？" + +#~ msgid "" +#~ "Despite just 29 lines of code, this C example contains serious bugs in at " +#~ "least 11:" +#~ msgstr "尽管该 C 语言示例仅有29行代码，但它却包含了至少11个严重 bug：" + +#~ msgid "Assignment `=` instead of equality comparison `==` (line 28)" +#~ msgstr "使用赋值 `=` 而非判断相等 `==`（第28行）" + +#~ msgid "Excess argument to `printf` (line 23)" +#~ msgstr "`printf` 有多余参数（第23行）" + +#~ msgid "File descriptor leak (after line 26)" +#~ msgstr "文件描述符泄露（第26行之后）" + +#~ msgid "Forgotten braces in multi-line `if` (line 22)" +#~ msgstr "多行 `if` 语句缺少花括号（第22行）" + +#~ msgid "Forgotten `break` in a `switch` statement (line 32)" +#~ msgstr "`switch` 语句忘记添加 `break`（第32行）" + +#~ msgid "" +#~ "Forgotten NUL-termination of the `buf` string, leading to a buffer " +#~ "overflow (line 29)" +#~ msgstr "`buf` 字符串忘记NUL终止符，从而导致缓冲区溢出（第29行）" + +#~ msgid "Memory leak by not freeing the `malloc`\\-allocated buffer (line 21)" +#~ msgstr "未释放由 `malloc` 分配的缓冲区，从而导致内存泄漏（第21行）" + +#~ msgid "Out-of-bounds access (line 17)" +#~ msgstr "越界访问（第17行）" + +#~ msgid "Unchecked cases in the `switch` statement (line 11)" +#~ msgstr "`switch` 语句存在未检查的情况（第11行）" + +#~ msgid "Unchecked return values of `stat` and `fopen` (lines 18 and 26)" +#~ msgstr "`stat` 和 `fopen` 存在未检查的返回值（第18行及第26行）" + +#~ msgid "" +#~ "_Shouldn't these bugs be obvious even for a C compiler?_ \n" +#~ "No, surprisingly this code compiles warning-free at the default warning " +#~ "level, even in the latest GCC version (13.2 as of writing)." +#~ msgstr "" +#~ "_即使对于 C 语言编译器，这些bug难道不应该是显而易见的吗？_ \n" +#~ "惊人的是，即便使用最新版本的GCC（截至撰文时为13.2），在默认警告等级下编译" +#~ "代码时也不出现任何警告。" + +#~ msgid "" +#~ "_Isn't this a highly unrealistic example?_ \n" +#~ "Absolutely not, these kind of bugs have lead to serious security " +#~ "vulnerabilities in the past. Some examples:" +#~ msgstr "" +#~ "_这是非常极端的示例吗？_ \n" +#~ "当然不是。这些类型的bug在过去曾引发一系列的安全漏洞，比如以下案例：" + +#~ msgid "" +#~ "Assignment `=` instead of equality comparison `==`: [The Linux Backdoor " +#~ "Attempt of 2003](https://freedom-to-tinker.com/2013/10/09/the-linux-" +#~ "backdoor-attempt-of-2003)" +#~ msgstr "" +#~ "使用赋值 `=` 而非判断相等 `==`：[2003年Linux后门尝试](https://freedom-to-" +#~ "tinker.com/2013/10/09/the-linux-backdoor-attempt-of-2003)" + +#~ msgid "" +#~ "Forgotten braces in multi-line `if`: [The Apple goto fail vulnerability]" +#~ "(https://dwheeler.com/essays/apple-goto-fail.html)" +#~ msgstr "" +#~ "多行 `if` 语句缺少花括号：[Apple goto失败漏洞](https://dwheeler.com/" +#~ "essays/apple-goto-fail.html)" + +#~ msgid "" +#~ "Forgotten `break` in a `switch` statement: [The break that broke sudo]" +#~ "(https://nakedsecurity.sophos.com/2012/05/21/anatomy-of-a-security-hole-" +#~ "the-break-that-broke-sudo)" +#~ msgstr "" +#~ "`switch` 语句忘记添加 `break`：[破坏sudo的break](https://nakedsecurity." +#~ "sophos.com/2012/05/21/anatomy-of-a-security-hole-the-break-that-broke-" +#~ "sudo)" + +#~ msgid "" +#~ "_How is Rust any better here?_ \n" +#~ "Safe Rust makes all of these bugs impossible:" +#~ msgstr "" +#~ "_Rust在这些方面表现得怎么样？_ \n" +#~ "安全Rust使这些bug的出现变得不可能：" + +#~ msgid "Assignments inside an `if` clause are not supported." +#~ msgstr "不支持 `if` 语句内赋值。" + +#~ msgid "Format strings are checked at compile-time." +#~ msgstr "编译时检查格式化字符串。" + +#~ msgid "Resources are freed at the end of scope via the `Drop` trait." +#~ msgstr "在作用域末尾，Rust通过 `Drop` trait 来释放资源。" + +#~ msgid "All `if` clauses require braces." +#~ msgstr "所有 `if` 语句必须有花括号。" + +#~ msgid "" +#~ "`match` (as the Rust equivalent to `switch`) does not fall-through, hence " +#~ "you can't accidentally forget a `break`." +#~ msgstr "" +#~ "`match` 语句（在 Rust 中相当于 `switch`）并不会落空，因此你不会意外忘记一" +#~ "个 `break`。" + +#~ msgid "Buffer slices carry their size and don't rely on a NUL terminator." +#~ msgstr "缓冲区切片自带它们的大小，且不依赖NUL终止符。" + +#~ msgid "" +#~ "Heap-allocated memory is freed via the `Drop` trait when the " +#~ "corresponding `Box` leaves the scope." +#~ msgstr "当相关 `Box` 离开作用域时，Rust 通过 `Drop` trait 释放堆分配内存。" + +#~ msgid "" +#~ "Out-of-bounds accesses cause a panic or can be checked via the `get` " +#~ "method of a slice." +#~ msgstr "" +#~ "越界访问会导致程序发生 panic 而终止，也可以用 `get` 方法来检查一个序列是否" +#~ "越界。" + +#~ msgid "`match` mandates that all cases are handled." +#~ msgstr "`match` 语句规定要处理所有情况。" + +#~ msgid "" +#~ "Fallible Rust functions return `Result` values that need to be unwrapped " +#~ "and thereby checked for success. Additionally, the compiler emits a " +#~ "warning if you miss to check the return value of a function marked with " +#~ "`#[must_use]`." +#~ msgstr "" +#~ "可出错的 Rust 函数返回的 `Result` 值需要拆箱并检查是否成功。此外，如果你忽" +#~ "略检查标注为 `#[must_use]` 的函数的返回值，编译器会发出警告。" + +#~ msgid "Static memory management at compile time:" +#~ msgstr "编译期静态内存管理：" + +#~ msgid "No memory leaks (_mostly_, see notes)." +#~ msgstr "不存在内存泄漏（_通常情况下_，见注释）。" + +#~ msgid "" +#~ "It is possible to produce memory leaks in (safe) Rust. Some examples are:" +#~ msgstr "在（安全的）Rust 中也有可能产生内存泄漏。例如：" + +#~ msgid "" +#~ "You can use [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." +#~ "html#method.leak) to leak a pointer. A use of this could be to get " +#~ "runtime-initialized and runtime-sized static variables" +#~ msgstr "" +#~ "可以使用 [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." +#~ "html#method.leak) 来泄漏一个指针。该方法可以用于得到在运行时决定大小和初始" +#~ "化的静态变量" + +#~ msgid "" +#~ "You can use [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn." +#~ "forget.html) to make the compiler \"forget\" about a value (meaning the " +#~ "destructor is never run)." +#~ msgstr "" +#~ "可以使用 [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." +#~ "html) 来让编译器“忘记”一个值（即其析构函数不会被执行）。" + +#~ msgid "" +#~ "You can also accidentally create a [reference cycle](https://doc.rust-" +#~ "lang.org/book/ch15-06-reference-cycles.html) with `Rc` or `Arc`." +#~ msgstr "" +#~ "可以使用 `Rc` 或 `Arc` 意外创建一个循环引用（[reference cycle](https://" +#~ "doc.rust-lang.org/book/ch15-06-reference-cycles.html)）。" + +#~ msgid "" +#~ "In fact, some will consider infinitely populating a collection a memory " +#~ "leak and Rust does not protect from those." +#~ msgstr "" +#~ "实际上，有人认为无限填充一个集合也是一种内存泄漏，而 Rust 对此没有保护。" + +#~ msgid "" +#~ "For the purpose of this course, \"No memory leaks\" should be understood " +#~ "as \"Pretty much no _accidental_ memory leaks\"." +#~ msgstr "就本课程而言，“不存在内存泄漏”应理解为“几乎没有 _意外_ 内存泄漏”。" + +#~ msgid "" +#~ "Integer overflow is defined via the [`overflow-checks`](https://doc.rust-" +#~ "lang.org/rustc/codegen-options/index.html#overflow-checks) compile-time " +#~ "flag. If enabled, the program will panic (a controlled crash of the " +#~ "program), otherwise you get wrap-around semantics. By default, you get " +#~ "panics in debug mode (`cargo build`) and wrap-around in release mode " +#~ "(`cargo build --release`)." +#~ msgstr "" +#~ "整数溢出的行为由编译时的标志指定。可以选择 panic（一种受控的程序崩溃）或使" +#~ "用“回绕（wrap-around）”语义。默认情况下，使用调试模式编译（`cargo build`）" +#~ "的行为为 panic，使用发布模式编译（`cargo build --release`）的行为为“回" +#~ "绕”。" + +#~ msgid "" +#~ "Bounds checking cannot be disabled with a compiler flag. It can also not " +#~ "be disabled directly with the `unsafe` keyword. However, `unsafe` allows " +#~ "you to call functions such as `slice::get_unchecked` which does not do " +#~ "bounds checking." +#~ msgstr "" +#~ "边界检查不能使用编译标志禁用，也不能直接通过 `unsafe` 关键字禁用。然而， " +#~ "`unsafe` 允许你调用 `slice::get_unchecked` 等不做边界检查的函数。" + +#~ msgid "Rust is built with all the experience gained in the last decades." +#~ msgstr "Rust 建立于过去几十年来所获得的经验之上。" + +#~ msgid "Language Features" +#~ msgstr "语言特性" + +#~ msgid "Tooling" +#~ msgstr "工具" + +#~ msgid "" +#~ "Zero-cost abstractions, similar to C++, means that you don't have to " +#~ "'pay' for higher-level programming constructs with memory or CPU. For " +#~ "example, writing a loop using `for` should result in roughly the same low " +#~ "level instructions as using the `.iter().fold()` construct." +#~ msgstr "" +#~ "与 C++ 类似的零成本抽象，意味着你不需要为高级程序语言的结构“付出”更多的内" +#~ "存和 CPU。例如使用 `for` 循环与使用 `.iter().fold()` 结构应该会生成大致相" +#~ "同的底层指令。" + +#~ msgid "" +#~ "It may be worth mentioning that Rust enums are 'Algebraic Data Types', " +#~ "also known as 'sum types', which allow the type system to express things " +#~ "like `Option` and `Result`." +#~ msgstr "" +#~ "值得一提的是，Rust 的枚举是“代数数据类型”（也叫“和类型”）。它使得类型系统" +#~ "可以表示 `Option` 和 `Result` 等结构。" + +#~ msgid "" +#~ "Remind people to read the errors --- many developers have gotten used to " +#~ "ignore lengthy compiler output. The Rust compiler is significantly more " +#~ "talkative than other compilers. It will often provide you with " +#~ "_actionable_ feedback, ready to copy-paste into your code." +#~ msgstr "" +#~ "提醒学生去阅读编译错误 --- 许多开发者已经习惯去忽略冗长的编译器输出。Rust " +#~ "编译器会比其它编译器更健谈。它通常会提供 _可操作的_ 反馈，可以直接复制粘贴" +#~ "到代码中。" + +#~ msgid "" +#~ "The Rust standard library is small compared to languages like Java, " +#~ "Python, and Go. Rust does not come with several things you might consider " +#~ "standard and essential:" +#~ msgstr "" +#~ "相比 Java、Python 和 Go 等语言，Rust 标准库较为精简。Rust 并没有内置一些你" +#~ "可能认为标准和必要的功能：" + +#~ msgid "a random number generator, but see [rand](https://docs.rs/rand/)." +#~ msgstr "随机数生成器，可以使用 [rand](https://docs.rs/rand/) 替代。" + +#~ msgid "support for SSL or TLS, but see [rusttls](https://docs.rs/rustls/)." +#~ msgstr "SSL 和 TLS 支持，可以使用 [rusttls](https://docs.rs/rustls/) 替代。" + +#~ msgid "support for JSON, but see [serde_json](https://docs.rs/serde_json/)." +#~ msgstr "" +#~ "JSON 支持，可以使用 [serde_json](https://docs.rs/serde_json/) 替代。" + +#~ msgid "" +#~ "The reasoning behind this is that functionality in the standard library " +#~ "cannot go away, so it has to be very stable. For the examples above, the " +#~ "Rust community is still working on finding the best solution --- and " +#~ "perhaps there isn't a single \"best solution\" for some of these things." +#~ msgstr "" +#~ "Rust 这么做的原因是标准库中的功能是无法去除的，因此该功能必须非常稳定。对" +#~ "于以上例子，Rust 社区仍在寻找最佳解决方案 --- 甚至对一些情况可能没有单一" +#~ "的“最佳解决方案”。" + +#~ msgid "" +#~ "Rust comes with a built-in package manager in the form of Cargo and this " +#~ "makes it trivial to download and compile third-party crates. A " +#~ "consequence of this is that the standard library can be smaller." +#~ msgstr "" +#~ "Rust 内置了一个包管理器 Cargo，使得下载和编译第三方 crate 变得简单。这也导" +#~ "致标准库可以更加精简。" + +#~ msgid "" +#~ "Discovering good third-party crates can be a problem. Sites like help with this by letting you compare health metrics for crates " +#~ "to find a good and trusted one." +#~ msgstr "" +#~ "发现高质量的第三方 crate 也许是一个问题。 等网站对此问题" +#~ "有所帮助。它能帮你比较 crate 的健康指标，以找到一个高质量并受信任的 " +#~ "crate。" + +#~ msgid "" +#~ "[rust-analyzer](https://rust-analyzer.github.io/) is a well supported LSP " +#~ "implementation used in major IDEs and text editors." +#~ msgstr "" +#~ "[rust-analyzer](https://rust-analyzer.github.io/) 是一个受到广泛支持的 " +#~ "LSP 实现，被主流的 IDE 和文本编辑器所使用。" + +#~ msgid "`\"foo\"`, `\"two\\nlines\"`" +#~ msgstr "`\"foo\"`、`“两\\n行”`" + +#~ msgid "Like C++, Rust has references:" +#~ msgstr "如同 C++ 一样，Rust 也提供了引用类型。" + +#~ msgid "" +#~ "We must dereference `ref_x` when assigning to it, similar to C and C++ " +#~ "pointers." +#~ msgstr "" +#~ "就像 C 与 C++ 中的指针一样，对引用 `ref_x` 进行赋值时，我们必须对其解引" +#~ "用。" + +#~ msgid "" +#~ "References that are declared as `mut` can be bound to different values " +#~ "over their lifetime." +#~ msgstr "" +#~ "如果引用值被声明为 `mut`（可变引用），那么这个引用值可以在它的生命周期内被" +#~ "绑定为不同的值。" + +#~ msgid "A reference is said to \"borrow\" the value it refers to." +#~ msgstr "一个引用被认为是“借用（borrow）”了它指向的值。" + +#~ msgid "" +#~ "Rust is tracking the lifetimes of all references to ensure they live long " +#~ "enough." +#~ msgstr "Rust 会跟踪所有引用的生命周期，以确保这些值的存活时间足够长。" + +#~ msgid "`String` vs `str`" +#~ msgstr "“String”与“str”的区别" + +#~ msgid "We can now understand the two string types in Rust:" +#~ msgstr "现在我们就可以理解 Rust 中的两种字符串类型：" + +#~ msgid "" +#~ "You can borrow `&str` slices from `String` via `&` and optionally range " +#~ "selection." +#~ msgstr "你可以通过 `&` 和可选的范围选择从 `String` 中借用 `&str` 切片。" + +#~ msgid "" +#~ "A Rust version of the famous [FizzBuzz](https://en.wikipedia.org/wiki/" +#~ "Fizz_buzz) interview question:" +#~ msgstr "" +#~ "一个 Rust 版本的著名 [FizzBuzz](https://en.wikipedia.org/wiki/Fizz_buzz) " +#~ "面试题：" + +#~ msgid "" +#~ "We refer in `main` to a function written below. Neither forward " +#~ "declarations nor headers are necessary. " +#~ msgstr "" +#~ "我们在 `main` 中引用了下面编写的一个函数。不需要提前声明或添加头文件。 " + +#~ msgid "" +#~ "The range expression in the `for` loop in `print_fizzbuzz_to()` contains " +#~ "`=n`, which causes it to include the upper bound." +#~ msgstr "" +#~ "`print_fizzbuzz_to()`函数中`for`循环的范围表达式（range expression）包含" +#~ "`=n`，这会导致它包括上限。" + +#~ msgid "" +#~ "All language items in Rust can be documented using special `///` syntax." +#~ msgstr "Rust 中的所有语言元素都可以通过特殊的 `///` 语法进行文档化。" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "/// Determine whether the first argument is divisible by the second " +#~ "argument.\n" +#~ "///\n" +#~ "/// If the second argument is zero, the result is false.\n" +#~ "///\n" +#~ "/// # Example\n" +#~ "/// ```\n" +#~ "/// assert!(is_divisible_by(42, 2));\n" +#~ "/// ```\n" +#~ "fn is_divisible_by(lhs: u32, rhs: u32) -> bool {\n" +#~ " if rhs == 0 {\n" +#~ " return false; // Corner case, early return\n" +#~ " }\n" +#~ " lhs % rhs == 0 // The last expression in a block is the return " +#~ "value\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "/// 判断第一个参数是否可以被第二个参数整除。\n" +#~ "///\n" +#~ "/// 如果第二个参数是 0，则返回结果为 false。\n" +#~ "fn is_divisible_by(lhs: u32, rhs: u32) -> bool {\n" +#~ " if rhs == 0 {\n" +#~ " return false; // 边界条件，直接返回\n" +#~ " }\n" +#~ " lhs % rhs == 0 // 代码块中的最后一个表达式就是它的返回值\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "This course does not include rustdoc on slides, just to save space, but " +#~ "in real code they should be present." +#~ msgstr "" +#~ "本课程的幻灯片中不包含 rustdoc，这是为了节省空间，但是在实际的代码中，应当" +#~ "编写相关的程序文档。" + +#~ msgid "" +#~ "Inner doc comments are discussed later (in the page on modules) and need " +#~ "not be addressed here." +#~ msgstr "内部文档注释将在稍后（在讲解模块的页面）讨论，这里无需进行说明。" + +#~ msgid "" +#~ "Rustdoc comments can contain code snippets that we can run and test using " +#~ "`cargo test`. We will discuss these tests in the [Testing section](../" +#~ "testing/doc-tests.html)." +#~ msgstr "" +#~ "Rustdoc 注释可以包含我们可使用“cargo test”运行和测试的代码段。我们将在[“测" +#~ "试”部分](../testing/doc-tests.html)中讨论这些测试。" + +#~ msgid "" +#~ "Methods are functions associated with a type. The `self` argument of a " +#~ "method is an instance of the type it is associated with:" +#~ msgstr "" +#~ "方法是与某种类型关联的函数。方法的 `self` 参数是与其关联类型的一个实例：" + +#~ msgid "" +#~ "We will look much more at methods in today's exercise and in tomorrow's " +#~ "class." +#~ msgstr "我们将在今天的练习和明天的课程中更深入地学习方法相关的概念。" + +#, fuzzy +#~ msgid "" +#~ "Add a static method called `Rectangle::new` and call this from `main`:" +#~ msgstr "新增一个 `Rectangle::new` 构造函数并在 `main` 函数中调用它:" + +#~ msgid "" +#~ "While _technically_, Rust does not have custom constructors, static " +#~ "methods are commonly used to initialize structs (but don't have to). The " +#~ "actual constructor, `Rectangle { width, height }`, could be called " +#~ "directly. See the [Rustnomicon](https://doc.rust-lang.org/nomicon/" +#~ "constructors.html)." +#~ msgstr "" +#~ "虽然从技术层面来讲，Rust 没有自定义构造函数，但静态方法通常用于初始化结构" +#~ "体（但并非必须这样做）。您可以直接调用实际构造函数“Rectangle { width, " +#~ "height }”。请参阅 [Rust 秘典](https://doc.rust-lang.org/nomicon/" +#~ "constructors.html)。" + +#, fuzzy +#~ msgid "" +#~ "Add a `Rectangle::square(width: u32)` constructor to illustrate that such " +#~ "static methods can take arbitrary parameters." +#~ msgstr "" +#~ "新增一个 `Rectangle::new_square(width: u32)` 构造函数来说明构造函数可以接" +#~ "受任意参数。" + +#~ msgid "Function Overloading" +#~ msgstr "函数重载" + +#~ msgid "Overloading is not supported:" +#~ msgstr "不支持重载：" + +#~ msgid "Always takes a fixed number of parameters." +#~ msgstr "始终接受固定个数的形参。" + +#~ msgid "Default values are not supported:" +#~ msgstr "不支持提供默认值：" + +#~ msgid "All call sites have the same number of arguments." +#~ msgstr "实参的数量在所有调用的地方都是一样的。" + +#~ msgid "Macros are sometimes used as an alternative." +#~ msgstr "有时可以用宏（Macro）作为替代。" + +#~ msgid "However, function parameters can be generic:" +#~ msgstr "然而，函数形参可以是泛型（generics）：" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn pick_one(a: T, b: T) -> T {\n" +#~ " if std::process::id() % 2 == 0 { a } else { b }\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " println!(\"coin toss: {}\", pick_one(\"heads\", \"tails\"));\n" +#~ " println!(\"cash prize: {}\", pick_one(500, 1000));\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn pick_one(a: T, b: T) -> T {\n" +#~ " if std::process::id() % 2 == 0 { a } else { b }\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " println!(\"coin toss: {}\", pick_one(\"heads\", \"tails\"));\n" +#~ " println!(\"cash prize: {}\", pick_one(500, 1000));\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "When using generics, the standard library's `Into` can provide a kind " +#~ "of limited polymorphism on argument types. We will see more details in a " +#~ "later section." +#~ msgstr "" +#~ "标准库中的 `Into` 通过泛型参数提供了一种具有有限多态性的参数类型。详见" +#~ "之后的章节。" + +#~ msgid "Day 1: Morning Exercises" +#~ msgstr "第一天上午习题" + +#~ msgid "In these exercises, we will explore two parts of Rust:" +#~ msgstr "在这些习题中，我们将探索 Rust 的两个部分：" + +#~ msgid "Implicit conversions between types." +#~ msgstr "类型之间的隐式转换。" + +#~ msgid "Arrays and `for` loops." +#~ msgstr "数组和 `for` 循环。" + +#~ msgid "A few things to consider while solving the exercises:" +#~ msgstr "在解题时要考虑几件事：" + +#~ msgid "" +#~ "Use a local Rust installation, if possible. This way you can get auto-" +#~ "completion in your editor. See the page about [Using Cargo](../../cargo." +#~ "md) for details on installing Rust." +#~ msgstr "" +#~ "最好使用本地安装的 Rust，以实现在编辑器中自动补全。关于安装 Rust 的细节，" +#~ "请参见 \\[使用 Cargo\\] 页面。" + +#~ msgid "Alternatively, use the Rust Playground." +#~ msgstr "也可以使用 Rust Playground 作为替代。" + +#~ msgid "" +#~ "The code snippets are not editable on purpose: the inline code snippets " +#~ "lose their state if you navigate away from the page." +#~ msgstr "" +#~ "页面内嵌的代码片段是不可编辑的：因为离开页面后内嵌代码片段中的修改会丢失。" + +#~ msgid "" +#~ "Rust will not automatically apply _implicit conversions_ between types " +#~ "([unlike C++](https://en.cppreference.com/w/cpp/language/" +#~ "implicit_conversion)). You can see this in a program like this:" +#~ msgstr "" +#~ "[与 C++ 不同](https://en.cppreference.com/w/cpp/language/" +#~ "implicit_conversion)，Rust 不会自动进行 _隐式类型转换_。例如，下面的程序中" +#~ "不存在隐式类型转换：" + +#~ msgid "" +#~ "The Rust integer types all implement the [`From`](https://doc.rust-" +#~ "lang.org/std/convert/trait.From.html) and [`Into`](https://doc.rust-" +#~ "lang.org/std/convert/trait.Into.html) traits to let us convert between " +#~ "them. The `From` trait has a single `from()` method and similarly, the " +#~ "`Into` trait has a single `into()` method. Implementing these traits " +#~ "is how a type expresses that it can be converted into another type." +#~ msgstr "" +#~ "Rust 的整数类型都实现了 [`From`](https://doc.rust-lang.org/std/convert/" +#~ "trait.From.html) 和 [`Into`](https://doc.rust-lang.org/std/convert/" +#~ "trait.Into.html) trait，使得我们可以在它们之间进行转换。`From` trait 包" +#~ "含 `from()` 方法，`Into` trait 包含 `into()` 方法。类型通过实现这些 " +#~ "trait 来表达它将被如何转换为另一个类型。" + +#~ msgid "" +#~ "The standard library has an implementation of `From for i16`, which " +#~ "means that we can convert a variable `x` of type `i8` to an `i16` by " +#~ "calling `i16::from(x)`. Or, simpler, with `x.into()`, because `From " +#~ "for i16` implementation automatically create an implementation of " +#~ "`Into for i8`." +#~ msgstr "" +#~ "标准库中包含 `From for i16` 的实现，即我们可以通过调用 `i16::from(x)` " +#~ "来将 `i8` 类型的变量 `x` 转换为 `i16`。或者也可以简单地使用 `x.into()`，因" +#~ "为 `From for i16` 的实现会自动创建 `Into for i8` 的实现。" + +#~ msgid "" +#~ "The same applies for your own `From` implementations for your own types, " +#~ "so it is sufficient to only implement `From` to get a respective `Into` " +#~ "implementation automatically." +#~ msgstr "" +#~ "这同样也适用于自定义类型的 `From` 实现，只需实现 `From` 就可以自动得到对应" +#~ "的 `Into` 实现。" + +#~ msgid "Execute the above program and look at the compiler error." +#~ msgstr "执行上述程序，并查看对应的编译错误。" + +#~ msgid "Update the code above to use `into()` to do the conversion." +#~ msgstr "修改代码，使用 `into()` 进行类型转换。" + +#~ msgid "" +#~ "Change the types of `x` and `y` to other things (such as `f32`, `bool`, " +#~ "`i128`) to see which types you can convert to which other types. Try " +#~ "converting small types to big types and the other way around. Check the " +#~ "[standard library documentation](https://doc.rust-lang.org/std/convert/" +#~ "trait.From.html) to see if `From` is implemented for the pairs you " +#~ "check." +#~ msgstr "" +#~ "修改 `x` 和 `y` 的类型（例如 `f32`, `bool`, `i128` 等）来了解哪些类型之间" +#~ "可以相互转换。尝试将较小的类型转换为较大的类型和将较大的类型转换为较小的类" +#~ "型。阅读 [标准库文档](https://doc.rust-lang.org/std/convert/trait.From." +#~ "html) 来了解对于你所尝试的两个类型 `From` 是否已被实现。" + +#~ msgid "Arrays and `for` Loops" +#~ msgstr "数组与 `for` 循环" + +#~ msgid "We saw that an array can be declared like this:" +#~ msgstr "我们可以这样声明一个数组：" + +#~ msgid "" +#~ "You can print such an array by asking for its debug representation with " +#~ "`{:?}`:" +#~ msgstr "你可以使用 `{:?}` 来打印这种数组的调试格式：" + +#~ msgid "" +#~ "Rust lets you iterate over things like arrays and ranges using the `for` " +#~ "keyword:" +#~ msgstr "在 Rust 中，可以使用 `for` 关键词遍历数组和区间等元素：" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let array = [10, 20, 30];\n" +#~ " print!(\"Iterating over array:\");\n" +#~ " for n in &array {\n" +#~ " print!(\" {n}\");\n" +#~ " }\n" +#~ " println!();\n" +#~ "\n" +#~ " print!(\"Iterating over range:\");\n" +#~ " for i in 0..3 {\n" +#~ " print!(\" {}\", array[i]);\n" +#~ " }\n" +#~ " println!();\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let array = [10, 20, 30];\n" +#~ " print!(\"Iterating over array:\");\n" +#~ " for n in array {\n" +#~ " print!(\" {n}\");\n" +#~ " }\n" +#~ " println!();\n" +#~ "\n" +#~ " print!(\"Iterating over range:\");\n" +#~ " for i in 0..3 {\n" +#~ " print!(\" {}\", array[i]);\n" +#~ " }\n" +#~ " println!();\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,should_panic\n" +#~ "// TODO: remove this when you're done with your implementation.\n" +#~ "#![allow(unused_variables, dead_code)]\n" +#~ "\n" +#~ "fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" +#~ " unimplemented!()\n" +#~ "}\n" +#~ "\n" +#~ "fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" +#~ " unimplemented!()\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let matrix = [\n" +#~ " [101, 102, 103], // <-- the comment makes rustfmt add a newline\n" +#~ " [201, 202, 203],\n" +#~ " [301, 302, 303],\n" +#~ " ];\n" +#~ "\n" +#~ " println!(\"matrix:\");\n" +#~ " pretty_print(&matrix);\n" +#~ "\n" +#~ " let transposed = transpose(matrix);\n" +#~ " println!(\"transposed:\");\n" +#~ " pretty_print(&transposed);\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,should_panic\n" +#~ "// TODO: 完成你的实现后移除此行。\n" +#~ "#![allow(unused_variables, dead_code)]\n" +#~ "\n" +#~ "fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" +#~ " unimplemented!()\n" +#~ "}\n" +#~ "\n" +#~ "fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" +#~ " unimplemented!()\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let matrix = [\n" +#~ " [101, 102, 103], // <-- 这个注释会让 rustfmt 添加一个新行\n" +#~ " [201, 202, 203],\n" +#~ " [301, 302, 303],\n" +#~ " ];\n" +#~ "\n" +#~ " println!(\"matrix:\");\n" +#~ " pretty_print(&matrix);\n" +#~ "\n" +#~ " let transposed = transpose(matrix);\n" +#~ " println!(\"transposed:\");\n" +#~ " pretty_print(&transposed);\n" +#~ "}\n" +#~ "```" + +#~ msgid "Bonus Question" +#~ msgstr "附加题" + +#~ msgid "" +#~ "Could you use `&[i32]` slices instead of hard-coded 3 × 3 matrices for " +#~ "your argument and return types? Something like `&[&[i32]]` for a two-" +#~ "dimensional slice-of-slices. Why or why not?" +#~ msgstr "" +#~ "是否可以使用 `&[i32]` 切片而不是硬编码的 3 × 3 矩阵作为函数的参数和返回类" +#~ "型？例如使用 `&[&[i32]]` 表示一个二维的切片的切片。为什么这样做是可行或不" +#~ "可行的？" + +#~ msgid "" +#~ "See the [`ndarray` crate](https://docs.rs/ndarray/) for a production " +#~ "quality implementation." +#~ msgstr "" +#~ "参考 [`ndarray` crate](https://docs.rs/ndarray/) 以了解该功能满足生产环境" +#~ "质量的实现。" + +#~ msgid "" +#~ "The solution and the answer to the bonus section are available in the " +#~ "[Solution](solutions-morning.md#arrays-and-for-loops) section." +#~ msgstr "" +#~ "题目解答和附加题的答案在 [题解](solutions-morning.md#arrays-and-for-" +#~ "loops) 章节中。" + +#~ msgid "" +#~ "The use of the reference `&array` within `for n in &array` is a subtle " +#~ "preview of issues of ownership that will come later in the afternoon." +#~ msgstr "" +#~ "在“for n in &array”中使用引用“&array”这一做法巧妙地预先展示了下午将谈到的" +#~ "所有权问题。" + +#~ msgid "Without the `&`..." +#~ msgstr "如果不使用“&”…" + +#~ msgid "" +#~ "The loop would have been one that consumes the array. This is a change " +#~ "[introduced in the 2021 Edition](https://doc.rust-lang.org/edition-guide/" +#~ "rust-2021/IntoIterator-for-arrays.html)." +#~ msgstr "" +#~ "循环将会是一个使用数组的循环。这是一项[在 2021 年版中引入](https://doc." +#~ "rust-lang.org/edition-guide/rust-2021/IntoIterator-for-arrays.html)的变" +#~ "更。" + +#~ msgid "" +#~ "An implicit array copy would have occurred. Since `i32` is a copy type, " +#~ "then `[i32; 3]` is also a copy type." +#~ msgstr "" +#~ "会发生隐式数组复制。由于“i32”是复制类型，因此“\\[i32; 3\\]”也是复制类型。" + +#~ msgid "" +#~ "As we have seen, `if` is an expression in Rust. It is used to " +#~ "conditionally evaluate one of two blocks, but the blocks can have a value " +#~ "which then becomes the value of the `if` expression. Other control flow " +#~ "expressions work similarly in Rust." +#~ msgstr "" +#~ "正如我们所知，`if` 是 Rust 中的一个表达式。它用于有条件地 评估两个块中的一" +#~ "个，但这些块可以有一个值， 然后成为 `if` 表达式的值。其他控制流表达式在 " +#~ "Rust 中也有类似 的运作方式。" + +#~ msgid "" +#~ "The same rule is used for functions: the value of the function body is " +#~ "the return value:" +#~ msgstr "同样的规则也适用于函数：函数主体的值 是返回值：" + +#~ msgid "" +#~ "The point of this slide is to show that blocks have a type and value in " +#~ "Rust. " +#~ msgstr "这张幻灯片的重点是说明在 Rust 中，块有类型和值。" + +#, fuzzy +#~ msgid "" +#~ "The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) is " +#~ "closely related to the [`while let` loop](while-let-expressions.md). It " +#~ "will automatically call `into_iter()` on the expression and then iterate " +#~ "over it:" +#~ msgstr "" +#~ "[`for` 循环](https://doc.rust-lang.org/std/keyword.for.html) 与 [`when " +#~ "let` 循环](when-let-expression.md)密切相关。它会 自动对表达式调用 " +#~ "`into_iter()`，然后对其进行迭代：" + +#~ msgid "You can use `break` and `continue` here as usual." +#~ msgstr "你可以在此照常使用 `break` 和 `continue`。" + +#~ msgid "Index iteration is not a special syntax in Rust for just that case." +#~ msgstr "在这种情况下，索引迭代在 Rust 中并不是一个特殊的语法。" + +#~ msgid "`(0..10)` is a range that implements an `Iterator` trait. " +#~ msgstr "`(0..10)` 是实现 `Iterator` trait 的区间。" + +#~ msgid "" +#~ "`step_by` is a method that returns another `Iterator` that skips every " +#~ "other element. " +#~ msgstr "" +#~ "`step_by` 是返回另一个 `Iterator` 的方法，用于逐一跳过所有其他元素。" + +#~ msgid "" +#~ "Modify the elements in the vector and explain the compiler errors. Change " +#~ "vector `v` to be mutable and the for loop to `for x in v.iter_mut()`." +#~ msgstr "" +#~ "修改矢量中的元素并说明编译器错误。将矢量 `v` 改为可变，并将 for 循环改为 " +#~ "`for x in v.iter_mut()`。" + +#~ msgid "`loop` expressions" +#~ msgstr "`loop` 表达式" + +#~ msgid "" +#~ "Finally, there is a [`loop` keyword](https://doc.rust-lang.org/reference/" +#~ "expressions/loop-expr.html#infinite-loops) which creates an endless loop." +#~ msgstr "" +#~ "最后是用于创建无限循环的 [`loop` 关键字](https://doc.rust-lang.org/" +#~ "reference/expressions/loop-expr.html#infinite-loops) 。" + +#~ msgid "Here you must either `break` or `return` to stop the loop:" +#~ msgstr "在下例中，你必须 `break` 或 `return` 才能停止循环：" + +#~ msgid "Break the `loop` with a value (e.g. `break 8`) and print it out." +#~ msgstr "用一个值（例如 `break 8`）来中断 `loop` 并将其输出。" + +#~ msgid "" +#~ "Due to type inference the `i32` is optional. We will gradually show the " +#~ "types less and less as the course progresses." +#~ msgstr "" +#~ "由于类型推导，`i32` 可以省略。随着课程推进，我们会越来越少地看到类型声明。" + +#, fuzzy +#~ msgid "" +#~ "The following code tells the compiler to copy into a certain generic " +#~ "container without the code ever explicitly specifying the contained type, " +#~ "using `_` as a placeholder:" +#~ msgstr "" +#~ "下面的代码通过使用 `_` 占位符来告诉编译器无需明确指定其类型就可以将对应数" +#~ "据拷贝到该容器： " + +#, fuzzy +#~ msgid "" +#~ "[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." +#~ "html#method.collect) relies on [`FromIterator`](https://doc.rust-lang.org/" +#~ "std/iter/trait.FromIterator.html), which [`HashSet`](https://doc.rust-" +#~ "lang.org/std/collections/struct.HashSet.html#impl-FromIterator%3CT%3E-for-" +#~ "HashSet%3CT,+S%3E) implements." +#~ msgstr "" +#~ "[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." +#~ "html#method.collect) 依赖 [`HashSet`](https://doc.rust-lang.org/std/iter/" +#~ "trait.FromIterator.html) 实现的 `FromIterator`。" + +#~ msgid "Static and Constant Variables" +#~ msgstr "静态变量和常量" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "static BANNER: &str = \"Welcome to RustOS 3.14\";\n" +#~ "\n" +#~ "fn main() {\n" +#~ " println!(\"{BANNER}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "static BANNER: &str = \"Welcome to RustOS 3.14\";\n" +#~ "\n" +#~ "fn main() {\n" +#~ " println!(\"{BANNER}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let a = 10;\n" +#~ " println!(\"before: {a}\");\n" +#~ "\n" +#~ " {\n" +#~ " let a = \"hello\";\n" +#~ " println!(\"inner scope: {a}\");\n" +#~ "\n" +#~ " let a = true;\n" +#~ " println!(\"shadowed in inner scope: {a}\");\n" +#~ " }\n" +#~ "\n" +#~ " println!(\"after: {a}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let a = 10;\n" +#~ " println!(\"before: {a}\");\n" +#~ "\n" +#~ " {\n" +#~ " let a = \"hello\";\n" +#~ " println!(\"inner scope: {a}\");\n" +#~ "\n" +#~ " let a = true;\n" +#~ " println!(\"shadowed in inner scope: {a}\");\n" +#~ " }\n" +#~ "\n" +#~ " println!(\"after: {a}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "The following code demonstrates why the compiler can't simply reuse " +#~ "memory locations when shadowing an immutable variable in a scope, even if " +#~ "the type does not change." +#~ msgstr "" +#~ "以下代码说明了为什么在作用域内隐藏一个不可变的变量时，即使是在变量类型没有" +#~ "改变的情况下，编译器也不能简单地重复利用之前的内存位置。" + +#, fuzzy +#~ msgid "" +#~ "This page offers an enum type `CoinFlip` with two variants `Heads` and " +#~ "`Tails`. You might note the namespace when using variants." +#~ msgstr "" +#~ "本页提供了一个枚举类型 `CoinFlip`，其中包含 `Heads` 和`Tail`两个变体。在使" +#~ "用变体时，你可能会注意到命名空间。" + +#~ msgid "In both, associated functions are defined within an `impl` block." +#~ msgstr "在这两者中，关联的函数都在 `impl` 块中定义。" + +#~ msgid "" +#~ "You can define richer enums where the variants carry data. You can then " +#~ "use the `match` statement to extract the data from each variant:" +#~ msgstr "" +#~ "你可以定义更丰富的枚举，其中变体会携带数据。然后，你可以使用 `match` 语句" +#~ "从每个变体中提取数据：" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "enum WebEvent {\n" +#~ " PageLoad, // Variant without payload\n" +#~ " KeyPress(char), // Tuple struct variant\n" +#~ " Click { x: i64, y: i64 }, // Full struct variant\n" +#~ "}\n" +#~ "\n" +#~ "#[rustfmt::skip]\n" +#~ "fn inspect(event: WebEvent) {\n" +#~ " match event {\n" +#~ " WebEvent::PageLoad => println!(\"page loaded\"),\n" +#~ " WebEvent::KeyPress(c) => println!(\"pressed '{c}'\"),\n" +#~ " WebEvent::Click { x, y } => println!(\"clicked at x={x}, " +#~ "y={y}\"),\n" +#~ " }\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let load = WebEvent::PageLoad;\n" +#~ " let press = WebEvent::KeyPress('x');\n" +#~ " let click = WebEvent::Click { x: 20, y: 80 };\n" +#~ "\n" +#~ " inspect(load);\n" +#~ " inspect(press);\n" +#~ " inspect(click);\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "enum WebEvent {\n" +#~ " PageLoad, // Variant without payload\n" +#~ " KeyPress(char), // Tuple struct variant\n" +#~ " Click { x: i64, y: i64 }, // Full struct variant\n" +#~ "}\n" +#~ "\n" +#~ "#[rustfmt::skip]\n" +#~ "fn inspect(event: WebEvent) {\n" +#~ " match event {\n" +#~ " WebEvent::PageLoad => println!(\"page loaded\"),\n" +#~ " WebEvent::KeyPress(c) => println!(\"pressed '{c}'\"),\n" +#~ " WebEvent::Click { x, y } => println!(\"clicked at x={x}, " +#~ "y={y}\"),\n" +#~ " }\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let load = WebEvent::PageLoad;\n" +#~ " let press = WebEvent::KeyPress('x');\n" +#~ " let click = WebEvent::Click { x: 20, y: 80 };\n" +#~ "\n" +#~ " inspect(load);\n" +#~ " inspect(press);\n" +#~ " inspect(click);\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "The expression is matched against the patterns from top to bottom. There " +#~ "is no fall-through like in C or C++." +#~ msgstr "表达式会从上到下与模式匹配。没有像 C 或 C++ 中那样的跳转。" + +#~ msgid "" +#~ "The match expression has a value. The value is the last expression in the " +#~ "match arm which was executed." +#~ msgstr "匹配表达式拥有一个值。值是 match 分支中被执行的最后一个表达式。" + +#~ msgid "" +#~ "Starting from the top we look for what pattern matches the value then run " +#~ "the code following the arrow. Once we find a match, we stop. " +#~ msgstr "" +#~ "从顶部开始，查找与该值匹配的模式，然后沿箭头运行代码。一旦找到匹配，我们便" +#~ "会停止。" + +#~ msgid "`match` inspects a hidden discriminant field in the `enum`." +#~ msgstr "`match` 会检查 `enum` 中的隐藏的判别字段。" + +#~ msgid "" +#~ "It is possible to retrieve the discriminant by calling `std::mem::" +#~ "discriminant()`" +#~ msgstr "可以通过调用 `std::mem::discriminant()` 来检索判别" + +#~ msgid "" +#~ "This is useful, for example, if implementing `PartialEq` for structs " +#~ "where comparing field values doesn't affect equality." +#~ msgstr "" +#~ "这很有用，例如如果为结构体实现 `PartialEq`，比较字段值不会影响等式。" + +#~ msgid "" +#~ "`WebEvent::Click { ... }` is not exactly the same as `WebEvent::" +#~ "Click(Click)` with a top level `struct Click { ... }`. The inlined " +#~ "version cannot implement traits, for example." +#~ msgstr "" +#~ "`WebEvent::Click { ... }` 与含顶层 `struct Click { ... }` 的 `WebEvent::" +#~ "Click(Click)` 不完全相同。例如，内嵌版本无法实现 trait。" + +#~ msgid "" +#~ "Rust enums are packed tightly, taking constraints due to alignment into " +#~ "account:" +#~ msgstr "Rust 枚举被紧密地打包，考虑到了对齐的影响，因此存在一些限制：" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::any::type_name;\n" +#~ "use std::mem::{align_of, size_of};\n" +#~ "\n" +#~ "fn dbg_size() {\n" +#~ " println!(\"{}: size {} bytes, align: {} bytes\",\n" +#~ " type_name::(), size_of::(), align_of::());\n" +#~ "}\n" +#~ "\n" +#~ "enum Foo {\n" +#~ " A,\n" +#~ " B,\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " dbg_size::();\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::mem::{align_of, size_of};\n" +#~ "\n" +#~ "macro_rules! dbg_size {\n" +#~ " ($t:ty) => {\n" +#~ " println!(\"{}: size {} bytes, align: {} bytes\",\n" +#~ " stringify!($t), size_of::<$t>(), align_of::<$t>());\n" +#~ " };\n" +#~ "}\n" +#~ "\n" +#~ "enum Foo {\n" +#~ " A,\n" +#~ " B,\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " dbg_size!(Foo);\n" +#~ "}\n" +#~ "```" + +#, fuzzy +#~ msgid "" +#~ "Internally Rust is using a field (discriminant) to keep track of the enum " +#~ "variant." +#~ msgstr "在内部，Rust 使用字段（判别）来跟踪枚举变体。" + +#, fuzzy +#~ msgid "Try out other types such as" +#~ msgstr "试试其他类型，例如：" + +#, fuzzy +#~ msgid "`dbg_size!(bool)`: size 1 bytes, align: 1 bytes," +#~ msgstr "`dbg_size!(bool)`：大小占用 1 个字节，对齐占用 1 个字节；" + +#, fuzzy +#~ msgid "" +#~ "`dbg_size!(Option)`: size 1 bytes, align: 1 bytes (niche " +#~ "optimization, see below)," +#~ msgstr "" +#~ "`dbg_size!(Option)`：大小占用 1 个字节，对齐占用 1 个字节（小众优" +#~ "化，请参阅下文）；" + +#, fuzzy +#~ msgid "" +#~ "`dbg_size!(&i32)`: size 8 bytes, align: 8 bytes (on a 64-bit machine)," +#~ msgstr "" +#~ "`dbg_size!(&i32)`：大小占用 8 个字节，对齐占用 8 个字节（在 64 位设备" +#~ "上）；" + +#, fuzzy +#~ msgid "" +#~ "`dbg_size!(Option<&i32>)`: size 8 bytes, align: 8 bytes (null pointer " +#~ "optimization, see below)." +#~ msgstr "" +#~ "`dbg_size!(Option<&i32>)`：大小占用 8 个字节，对齐占用 8 个字节（Null 指针" +#~ "优化，请参阅下文）。" + +#, fuzzy +#~ msgid "" +#~ "Niche optimization: Rust will merge unused bit patterns for the enum " +#~ "discriminant." +#~ msgstr "小众优化：Rust 将对枚举判别合并使用 未使用的位模式。" + +#~ msgid "" +#~ "More complex example if you want to discuss what happens when we chain " +#~ "more than 256 `Option`s together." +#~ msgstr "" +#~ "如果您想讨论将 256 多个“Option”链在一起时会发生什么情况，可以使用下方这个" +#~ "更复杂的示例。" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let arg = std::env::args().next();\n" +#~ " if let Some(value) = arg {\n" +#~ " println!(\"Program name: {value}\");\n" +#~ " } else {\n" +#~ " println!(\"Missing name?\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let arg = std::env::args().next();\n" +#~ " if let Some(value) = arg {\n" +#~ " println!(\"Program name: {value}\");\n" +#~ " } else {\n" +#~ " println!(\"Missing name?\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "See [pattern matching](../pattern-matching.md) for more details on " +#~ "patterns in Rust." +#~ msgstr "" +#~ "如需详细了解 Rust 中 的模式，请参阅[模式匹配](../pattern-matching.md)。" + +#, fuzzy +#~ msgid "" +#~ "Since 1.65, a similar [let-else](https://doc.rust-lang.org/rust-by-" +#~ "example/flow_control/let_else.html) construct allows to do a " +#~ "destructuring assignment, or if it fails, execute a block which is " +#~ "required to abort normal control flow (with `panic`/`return`/`break`/" +#~ "`continue`):" +#~ msgstr "" +#~ "自 1.65 版以来，类似的 [let-else](https://doc.rust-lang.org/rust-by-" +#~ "example/flow_control/let_else.html) 结构允许执行解构赋值，或者如果不满足条" +#~ "件，则有一个非返回块分支 (panic/return/break/continue)：" + +#~ msgid "" +#~ "The [`match` keyword](https://doc.rust-lang.org/reference/expressions/" +#~ "match-expr.html) is used to match a value against one or more patterns. " +#~ "In that sense, it works like a series of `if let` expressions:" +#~ msgstr "" +#~ "[`match` 关键字](https://doc.rust-lang.org/reference/expressions/match-" +#~ "expr.html) 用于将一个值与一个或多个模式进行匹配。从这个意义上讲，它的工作" +#~ "方式 类似于一系列的 `if let` 表达式：" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " match std::env::args().next().as_deref() {\n" +#~ " Some(\"cat\") => println!(\"Will do cat things\"),\n" +#~ " Some(\"ls\") => println!(\"Will ls some files\"),\n" +#~ " Some(\"mv\") => println!(\"Let's move some files\"),\n" +#~ " Some(\"rm\") => println!(\"Uh, dangerous!\"),\n" +#~ " None => println!(\"Hmm, no program name?\"),\n" +#~ " _ => println!(\"Unknown program name!\"),\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " match std::env::args().next().as_deref() {\n" +#~ " Some(\"cat\") => println!(\"Will do cat things\"),\n" +#~ " Some(\"ls\") => println!(\"Will ls some files\"),\n" +#~ " Some(\"mv\") => println!(\"Let's move some files\"),\n" +#~ " Some(\"rm\") => println!(\"Uh, dangerous!\"),\n" +#~ " None => println!(\"Hmm, no program name?\"),\n" +#~ " _ => println!(\"Unknown program name!\"),\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "Save the match expression to a variable and print it out." +#~ msgstr "将 match 表达式保存到一个变量中并输出结果。" + +#~ msgid "Remove `.as_deref()` and explain the error." +#~ msgstr "移除 `.as_deref()` 并说明错误。" + +#~ msgid "" +#~ "`std::env::args().next()` returns an `Option`, but we cannot " +#~ "match against `String`." +#~ msgstr "" +#~ "`std::env::args().next()` 会返回 `Option`，但无法与 `String` 进行" +#~ "匹配。" + +#~ msgid "" +#~ "`as_deref()` transforms an `Option` to `Option<&T::Target>`. In our " +#~ "case, this turns `Option` into `Option<&str>`." +#~ msgstr "" +#~ "`as_deref()` 会将 `Option` 转换为 `Option<&T::Target>`。在我们的示例" +#~ "中，这会将 `Option` 转换为 `Option<&str>`。" + +#~ msgid "" +#~ "We can now use pattern matching to match against the `&str` inside " +#~ "`Option`." +#~ msgstr "现在，我们可以使用模式匹配来匹配 `Option` 中的 `&str`。" + +#~ msgid "The `_` pattern is a wildcard pattern which matches any value." +#~ msgstr "模式 `_` 是外卡 (wildcard) 模式。它可以匹配任何值。" + +#~ msgid "" +#~ "It can be useful to show how binding works, by for instance replacing a " +#~ "wildcard character with a variable, or removing the quotes around `q`." +#~ msgstr "" +#~ "展示绑定的运作方式可能会很有帮助，例如通过用变量替换通配符或移除“q”周围的" +#~ "引号来展示。" + +#~ msgid "You can demonstrate matching on a reference." +#~ msgstr "您可以在参照项上演示如何匹配。" + +#~ msgid "" +#~ "This might be a good time to bring up the concept of irrefutable " +#~ "patterns, as the term can show up in error messages." +#~ msgstr "" +#~ "这时可能很适合提到“不可反驳的模式”这个概念，因为这个术语可能会出现在错误消" +#~ "息中。" + +#~ msgid "You can also destructure `structs`:" +#~ msgstr "您还可以解构“structs”：" + +#~ msgid "" +#~ "Destructuring of slices of unknown length also works with patterns of " +#~ "fixed length." +#~ msgstr "对未知长度的切片进行解构也可以使用固定长度的模式。" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " inspect(&[0, -2, 3]);\n" +#~ " inspect(&[0, -2, 3, 4]);\n" +#~ "}\n" +#~ "\n" +#~ "#[rustfmt::skip]\n" +#~ "fn inspect(slice: &[i32]) {\n" +#~ " println!(\"Tell me about {slice:?}\");\n" +#~ " match slice {\n" +#~ " &[0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" +#~ " &[1, ..] => println!(\"First is 1 and the rest were " +#~ "ignored\"),\n" +#~ " _ => println!(\"All elements were ignored\"),\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " inspect(&[0, -2, 3]);\n" +#~ " inspect(&[0, -2, 3, 4]);\n" +#~ "}\n" +#~ "\n" +#~ "#[rustfmt::skip]\n" +#~ "fn inspect(slice: &[i32]) {\n" +#~ " println!(\"Tell me about {slice:?}\");\n" +#~ " match slice {\n" +#~ " &[0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" +#~ " &[1, ..] => println!(\"First is 1 and the rest were " +#~ "ignored\"),\n" +#~ " _ => println!(\"All elements were ignored\"),\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "When matching, you can add a _guard_ to a pattern. This is an arbitrary " +#~ "Boolean expression which will be executed if the pattern matches:" +#~ msgstr "" +#~ "匹配时，您可以向模式中添加“守卫”。这是一个任意布尔表达式，如果模式匹配，就" +#~ "会执行该表达式：" + +#~ msgid "" +#~ "You can use the variables defined in the pattern in your if expression." +#~ msgstr "您可以在 if 表达式中使用模式中定义的变量。" + +#~ msgid "Day 1: Afternoon Exercises" +#~ msgstr "第 1 天：下午练习" + +#~ msgid "We will look at two things:" +#~ msgstr "我们将关注以下两方面：" + +#, fuzzy +#~ msgid "The Luhn algorithm," +#~ msgstr "Luhn 算法" + +#, fuzzy +#~ msgid "An exercise on pattern matching." +#~ msgstr "枚举和模式匹配。" + +#, fuzzy +#~ msgid "" +#~ "Copy the code below to and implement the " +#~ "function." +#~ msgstr "将下面的代码复制到 并实现上述函数：" + +#~ msgid "" +#~ "Try to solve the problem the \"simple\" way first, using `for` loops and " +#~ "integers. Then, revisit the solution and try to implement it with " +#~ "iterators." +#~ msgstr "" +#~ "使用“for”循环和整数，先尝试以简单的方式解决问题。然后，再次查看该解决方" +#~ "案，并尝试使用迭代器来实现它。" + +#~ msgid "" +#~ "Memory management: stack vs heap, manual memory management, scope-based " +#~ "memory management, and garbage collection." +#~ msgstr "" +#~ "内存管理：栈与堆，手动内存管理，基于作用域的内存管理，以及垃圾回收。" + +#~ msgid "" +#~ "Ownership: move semantics, copying and cloning, borrowing, and lifetimes." +#~ msgstr "" +#~ "所有权：移动（move）的语义，复制（copy）和克隆（clone），借用（borrow），" +#~ "以及生命周期。" + +#, fuzzy +#~ msgid "Structs and methods." +#~ msgstr "结构体（struct）, 枚举（enum）, 方法（method）。" + +#~ msgid "" +#~ "The Standard Library: `String`, `Option` and `Result`, `Vec`, `HashMap`, " +#~ "`Rc` and `Arc`." +#~ msgstr "" +#~ "标准库: `字符串（String）`, `选项（Option）` 和 `结果（Result）`, `动态数" +#~ "组（Vec）`, `散列表（HashMap）`, `引用计数（Rc）` 和 `共享引用计数（Arc）" +#~ "`。" + +#~ msgid "Modules: visibility, paths, and filesystem hierarchy." +#~ msgstr "模块: 可见性, 路径和文件系统的层次结构。" + +#~ msgid "First, let's refresh how memory management works." +#~ msgstr "首先，我们回顾一下内存管理的工作原理。" + +#~ msgid "The Stack vs The Heap" +#~ msgstr "栈与堆" -#: src/exercises/day-1/solutions-afternoon.md:80 #, fuzzy -msgid "Pattern matching" -msgstr "模式匹配" +#~ msgid "Stack and Heap Example" +#~ msgstr "栈 vs 堆" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let s1 = String::from(\"Hello\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let s1 = String::from(\"Hello\");\n" +#~ "}\n" +#~ "```" -#: src/exercises/day-1/solutions-afternoon.md:82 -msgid "" -"```rust\n" -"/// An operation to perform on two subexpressions.\n" -"#[derive(Debug)]\n" -"enum Operation {\n" -" Add,\n" -" Sub,\n" -" Mul,\n" -" Div,\n" -"}\n" -"\n" -"/// An expression, in tree form.\n" -"#[derive(Debug)]\n" -"enum Expression {\n" -" /// An operation on two subexpressions.\n" -" Op {\n" -" op: Operation,\n" -" left: Box,\n" -" right: Box,\n" -" },\n" -"\n" -" /// A literal value\n" -" Value(i64),\n" -"}\n" -"\n" -"/// The result of evaluating an expression.\n" -"#[derive(Debug, PartialEq, Eq)]\n" -"enum Res {\n" -" /// Evaluation was successful, with the given result.\n" -" Ok(i64),\n" -" /// Evaluation failed, with the given error message.\n" -" Err(String),\n" -"}\n" -"// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" -"use Res::{Err, Ok};\n" -"\n" -"fn eval(e: Expression) -> Res {\n" -" match e {\n" -" Expression::Op { op, left, right } => {\n" -" let left = match eval(*left) {\n" -" Ok(v) => v,\n" -" Err(msg) => return Err(msg),\n" -" };\n" -" let right = match eval(*right) {\n" -" Ok(v) => v,\n" -" Err(msg) => return Err(msg),\n" -" };\n" -" Ok(match op {\n" -" Operation::Add => left + right,\n" -" Operation::Sub => left - right,\n" -" Operation::Mul => left * right,\n" -" Operation::Div => {\n" -" if right == 0 {\n" -" return Err(String::from(\"division by zero\"));\n" -" } else {\n" -" left / right\n" -" }\n" -" }\n" -" })\n" -" }\n" -" Expression::Value(v) => Ok(v),\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_value() {\n" -" assert_eq!(eval(Expression::Value(19)), Ok(19));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_sum() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(20)),\n" -" }),\n" -" Ok(30)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_recursion() {\n" -" let term1 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(9)),\n" -" };\n" -" let term2 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(3)),\n" -" right: Box::new(Expression::Value(4)),\n" -" }),\n" -" right: Box::new(Expression::Value(5)),\n" -" };\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(term1),\n" -" right: Box::new(term2),\n" -" }),\n" -" Ok(85)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_error() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Div,\n" -" left: Box::new(Expression::Value(99)),\n" -" right: Box::new(Expression::Value(0)),\n" -" }),\n" -" Err(String::from(\"division by zero\"))\n" -" );\n" -"}\n" -"fn main() {\n" -" let expr = Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(20)),\n" -" right: Box::new(Expression::Value(10)),\n" -" };\n" -" println!(\"expr: {:?}\", expr);\n" -" println!(\"result: {:?}\", eval(expr));\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let mut s1 = String::from(\"Hello\");\n" +#~ " s1.push(' ');\n" +#~ " s1.push_str(\"world\");\n" +#~ " // DON'T DO THIS AT HOME! For educational purposes only.\n" +#~ " // String provides no guarantees about its layout, so this could lead " +#~ "to\n" +#~ " // undefined behavior.\n" +#~ " unsafe {\n" +#~ " let (ptr, capacity, len): (usize, usize, usize) = std::mem::" +#~ "transmute(s1);\n" +#~ " println!(\"ptr = {ptr:#x}, len = {len}, capacity = " +#~ "{capacity}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let mut s1 = String::from(\"Hello\");\n" +#~ " s1.push(' ');\n" +#~ " s1.push_str(\"world\");\n" +#~ " // DON'T DO THIS AT HOME! For educational purposes only.\n" +#~ " // String provides no guarantees about its layout, so this could lead " +#~ "to\n" +#~ " // undefined behavior.\n" +#~ " unsafe {\n" +#~ " let (capacity, ptr, len): (usize, usize, usize) = std::mem::" +#~ "transmute(s1);\n" +#~ " println!(\"ptr = {ptr:#x}, len = {len}, capacity = " +#~ "{capacity}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "You allocate and deallocate heap memory yourself." +#~ msgstr "你自己实现堆内存分配和释放。" + +#~ msgid "" +#~ "If not done with care, this can lead to crashes, bugs, security " +#~ "vulnerabilities, and memory leaks." +#~ msgstr "稍有不慎，这可能会导致崩溃、bug、安全漏洞和内存泄漏。" + +#~ msgid "C Example" +#~ msgstr "C++ 示例" + +#~ msgid "You must call `free` on every pointer you allocate with `malloc`:" +#~ msgstr "你必须对使用 `malloc` 分配的每个指针调用 `free`：" -#: src/exercises/day-2/solutions-morning.md:1 -msgid "Day 2 Morning Exercises" -msgstr "第二天上午的练习" +#, fuzzy +#~ msgid "" +#~ "```c\n" +#~ "void foo(size_t n) {\n" +#~ " int* int_array = malloc(n * sizeof(int));\n" +#~ " //\n" +#~ " // ... lots of code\n" +#~ " //\n" +#~ " free(int_array);\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```c\n" +#~ "void foo(size_t n) {\n" +#~ " int* int_array = (int*)malloc(n * sizeof(int));\n" +#~ " //\n" +#~ " // ... lots of code\n" +#~ " //\n" +#~ " free(int_array);\n" +#~ "}\n" +#~ "```" -#: src/exercises/day-2/solutions-morning.md:3 -msgid "Designing a Library" -msgstr "设计一个库" +#, fuzzy +#~ msgid "" +#~ "Memory is leaked if the function returns early between `malloc` and " +#~ "`free`: the pointer is lost and we cannot deallocate the memory. Worse, " +#~ "freeing the pointer twice, or accessing a freed pointer can lead to " +#~ "exploitable security vulnerabilities." +#~ msgstr "" +#~ "如果函数在 `malloc` 和 `free` 之间提前返回，则会导致内存泄漏： 指针丢失，" +#~ "而我们无法释放对应的内存。" + +#~ msgid "" +#~ "Constructors and destructors let you hook into the lifetime of an object." +#~ msgstr "构造函数和析构函数让你可以钩入对象的生命周期。" + +#~ msgid "" +#~ "By wrapping a pointer in an object, you can free memory when the object " +#~ "is destroyed. The compiler guarantees that this happens, even if an " +#~ "exception is raised." +#~ msgstr "" +#~ "通过将指针封装在对象中，你可以在该对象 被销毁时释放内存。编译器可保证这一" +#~ "点的实现，即使引发了异常也不例外。" + +#~ msgid "" +#~ "This is often called _resource acquisition is initialization_ (RAII) and " +#~ "gives you smart pointers." +#~ msgstr "" +#~ "这通常称为“资源获取即初始化 (resource acquisition is initialization, " +#~ "RAII)”， 并为你提供智能指针。" + +#~ msgid "" +#~ "```c++\n" +#~ "void say_hello(std::unique_ptr person) {\n" +#~ " std::cout << \"Hello \" << person->name << std::endl;\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```c++\n" +#~ "void say_hello(std::unique_ptr person) {\n" +#~ " std::cout << \"Hello \" << person->name << std::endl;\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "The `std::unique_ptr` object is allocated on the stack, and points to " +#~ "memory allocated on the heap." +#~ msgstr "`std::unique_ptr` 对象在栈上分配内存，并指向在堆上分配的内存。" + +#~ msgid "" +#~ "At the end of `say_hello`, the `std::unique_ptr` destructor will run." +#~ msgstr "在 `say_hello` 结束时，`std::unique_ptr` 析构函数将运行。" + +#~ msgid "The destructor frees the `Person` object it points to." +#~ msgstr "析构函数释放它所指向的 `Person` 对象。" + +#~ msgid "" +#~ "Special move constructors are used when passing ownership to a function:" +#~ msgstr "将所有权传递给函数时，使用特殊的 move 构造函数：" + +#~ msgid "" +#~ "An alternative to manual and scope-based memory management is automatic " +#~ "memory management:" +#~ msgstr "自动内存管理是手动和基于作用域的内存管理 的替代方案：" + +#~ msgid "The programmer never allocates or deallocates memory explicitly." +#~ msgstr "程序员从不显式分配或取消分配内存。" + +#~ msgid "" +#~ "A garbage collector finds unused memory and deallocates it for the " +#~ "programmer." +#~ msgstr "垃圾回收器找到未使用的内存，并为程序员将其取消分配。" + +#~ msgid "Java Example" +#~ msgstr "Java 示例" + +#~ msgid "The `person` object is not deallocated after `sayHello` returns:" +#~ msgstr "`sayHello` 返回后，`person` 对象未被取消分配：" + +#~ msgid "" +#~ "```java\n" +#~ "void sayHello(Person person) {\n" +#~ " System.out.println(\"Hello \" + person.getName());\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```java\n" +#~ "void sayHello(Person person) {\n" +#~ " System.out.println(\"Hello \" + person.getName());\n" +#~ "}\n" +#~ "```" + +#~ msgid "Memory Management in Rust" +#~ msgstr "Rust 中的内存管理" + +#~ msgid "Memory management in Rust is a mix:" +#~ msgstr "Rust 中的内存管理是一种混合模式：" + +#~ msgid "Safe and correct like Java, but without a garbage collector." +#~ msgstr "像 Java 一样安全又正确，但没有垃圾回收器。" + +#~ msgid "Scope-based like C++, but the compiler enforces full adherence." +#~ msgstr "像 C++ 一样基于作用域，但编译器会强制完全遵循规则。" + +#~ msgid "" +#~ "A Rust user can choose the right abstraction for the situation, some even " +#~ "have no cost at runtime like C." +#~ msgstr "" +#~ "Rust 用户可以根据具体情况选择合适的抽象，有些甚至没有像 C 那样的运行时开" +#~ "销。" -#: src/exercises/day-2/solutions-morning.md:5 -msgid "([back to exercise](book-library.md))" -msgstr "([返回练习](book-library.md))" +#, fuzzy +#~ msgid "Rust achieves this by modeling _ownership_ explicitly." +#~ msgstr "它通过对“所有权”进行显式建模来实现这一点。" + +#~ msgid "" +#~ "If asked how at this point, you can mention that in Rust this is usually " +#~ "handled by RAII wrapper types such as [Box](https://doc.rust-lang.org/std/" +#~ "boxed/struct.Box.html), [Vec](https://doc.rust-lang.org/std/vec/struct." +#~ "Vec.html), [Rc](https://doc.rust-lang.org/std/rc/struct.Rc.html), or [Arc]" +#~ "(https://doc.rust-lang.org/std/sync/struct.Arc.html). These encapsulate " +#~ "ownership and memory allocation via various means, and prevent the " +#~ "potential errors in C." +#~ msgstr "" +#~ "如果此时被问及如何操作，你可以提及在 Rust 中，这通常由 RAII 封装容器类型" +#~ "（例如 [Box](https://doc.rust-lang.org/std/boxed/struct.Box.html)、[Vec]" +#~ "(https://doc.rust-lang.org/std/vec/struct.Vec.html)、[Rc](https://doc." +#~ "rust-lang.org/std/rc/struct.Rc.html) 或 [Arc](https://doc.rust-lang.org/" +#~ "std/sync/struct.Arc.html)）处理。这些类型通过各种方式封装了所有权和内存分" +#~ "配，并防止了 C 中潜在错误的发生。" + +#~ msgid "" +#~ "You may be asked about destructors here, the [Drop](https://doc.rust-lang." +#~ "org/std/ops/trait.Drop.html) trait is the Rust equivalent." +#~ msgstr "" +#~ "你可能会被问及析构函数，此处 [Drop](https://doc.rust-lang.org/std/ops/" +#~ "trait.Drop.html) trait 是 Rust 等效项。" + +#~ msgid "A destructor can run here to free up resources." +#~ msgstr "析构函数可在此运行以释放资源。" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let s1: String = String::from(\"Hello!\");\n" +#~ " let s2: String = s1;\n" +#~ " println!(\"s2: {s2}\");\n" +#~ " // println!(\"s1: {s1}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let s1: String = String::from(\"Hello!\");\n" +#~ " let s2: String = s1;\n" +#~ " println!(\"s2: {s2}\");\n" +#~ " // println!(\"s1: {s1}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "There is always _exactly_ one variable binding which owns a value." +#~ msgstr "变量绑定在任一时刻有且“只有”一个值。" + +#~ msgid "The heap data from `s1` is reused for `s2`." +#~ msgstr "`s1` 中的堆数据会被 `s2` 重复使用。" + +#~ msgid "" +#~ "When `s1` goes out of scope, nothing happens (it has been moved from)." +#~ msgstr "当 `s1` 离开作用域时，什么都不会发生（它已被移出）。" + +#~ msgid "" +#~ "```c++\n" +#~ "std::string s1 = \"Cpp\";\n" +#~ "std::string s2 = s1; // Duplicate the data in s1.\n" +#~ "```" +#~ msgstr "" +#~ "```c++\n" +#~ "std::string s1 = \"Cpp\";\n" +#~ "std::string s2 = s1; // 复制 s1 中的数据。\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn say_hello(name: String) {\n" +#~ " println!(\"Hello {name}\")\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let name = String::from(\"Alice\");\n" +#~ " say_hello(name);\n" +#~ " // say_hello(name);\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn say_hello(name: String) {\n" +#~ " println!(\"Hello {name}\")\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let name = String::from(\"Alice\");\n" +#~ " say_hello(name);\n" +#~ " // say_hello(name);\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "If students ask about `derive`, it is sufficient to say that this is a " +#~ "way to generate code in Rust at compile time. In this case the default " +#~ "implementations of `Copy` and `Clone` traits are generated." +#~ msgstr "" +#~ "如果学员问起 `derive`，只需说这是一种 在编译时生成 Rust 代码的方法。在这种" +#~ "情况下，系统会生成 `Copy` 和 `Clone` trait 的默认实现。" + +#~ msgid "A borrowed value has a _lifetime_:" +#~ msgstr "借用的值是有“生命周期”的：" + +#~ msgid "" +#~ "The lifetime can be implicit: `add(p1: &Point, p2: &Point) -> Point`." +#~ msgstr "生命周期可以是隐式的：add(p1: &Point, p2: &Point) -> Point\\`。" + +#~ msgid "Lifetimes can also be explicit: `&'a Point`, `&'document str`." +#~ msgstr "生命周期也可以是显式的：`&'a Point`、`&'document str`。" + +#~ msgid "" +#~ "Read `&'a Point` as \"a borrowed `Point` which is valid for at least the " +#~ "lifetime `a`\"." +#~ msgstr "将 `&'a Point` 读取为“借用的 `Point，至少 在 `a\\` 生命周期内有效。" + +#~ msgid "" +#~ "Lifetimes are always inferred by the compiler: you cannot assign a " +#~ "lifetime yourself." +#~ msgstr "生命周期始终由编译器推断出来：你不能自行 分配生命周期。" + +#~ msgid "" +#~ "In addition to borrowing its arguments, a function can return a borrowed " +#~ "value:" +#~ msgstr "除了借用其参数之外，函数还可以返回借用的值：" + +#~ msgid "`'a` is a generic parameter, it is inferred by the compiler." +#~ msgstr "`'a` 是一个泛型形参，由编译器推断出来。" + +#~ msgid "Lifetimes start with `'` and `'a` is a typical default name." +#~ msgstr "以 `'` 和 `'a` 开头的生命周期是典型的默认名称。" + +#~ msgid "" +#~ "The _at least_ part is important when parameters are in different scopes." +#~ msgstr "当参数在不同的作用域时，“至少”部分至关重要。" + +#~ msgid "" +#~ "Move the declaration of `p2` and `p3` into a new scope (`{ ... }`), " +#~ "resulting in the following code:" +#~ msgstr "将 `p2` 和 `p3` 的声明移至新作用域 (`{ ... }`)，以产生以下代码：" + +#~ msgid "Note how this does not compile since `p3` outlives `p2`." +#~ msgstr "请注意：由于 `p3` 的生命周期比 `p2` 长，因此无法编译。" + +#~ msgid "" +#~ "Reset the workspace and change the function signature to `fn " +#~ "left_most<'a, 'b>(p1: &'a Point, p2: &'a Point) -> &'b Point`. This will " +#~ "not compile because the relationship between the lifetimes `'a` and `'b` " +#~ "is unclear." +#~ msgstr "" +#~ "重置工作区，然后将函数签名更改为 `fn left_most<'a, 'b>(p1: &'a Point, p2: " +#~ "&'a Point) -> &'b Point`。这不会被编译，因为 `'a` 和 `'b` 生命周期之间的关" +#~ "系不明确。" + +#~ msgid "Another way to explain it:" +#~ msgstr "另一种解释方式：" + +#~ msgid "" +#~ "Two references to two values are borrowed by a function and the function " +#~ "returns another reference." +#~ msgstr "对两个值的两个引用被一个函数借用，该函数返回 另一个引用。" + +#~ msgid "" +#~ "It must have come from one of those two inputs (or from a global " +#~ "variable)." +#~ msgstr "它必须是来自这两个输入中的一个（或来自一个全局变量）。" + +#~ msgid "" +#~ "Which one is it? The compiler needs to know, so at the call site the " +#~ "returned reference is not used for longer than a variable from where the " +#~ "reference came from." +#~ msgstr "" +#~ "是哪一个呢？编译器需要知道这一点，因此在调用点，返回的引用 的使用时间不会" +#~ "超过引用的来源中的变量。" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "#[derive(Debug)]\n" +#~ "struct Highlight<'doc>(&'doc str);\n" +#~ "\n" +#~ "fn erase(text: String) {\n" +#~ " println!(\"Bye {text}!\");\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let text = String::from(\"The quick brown fox jumps over the lazy dog." +#~ "\");\n" +#~ " let fox = Highlight(&text[4..19]);\n" +#~ " let dog = Highlight(&text[35..43]);\n" +#~ " // erase(text);\n" +#~ " println!(\"{fox:?}\");\n" +#~ " println!(\"{dog:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "#[derive(Debug)]\n" +#~ "struct Highlight<'doc>(&'doc str);\n" +#~ "\n" +#~ "fn erase(text: String) {\n" +#~ " println!(\"Bye {text}!\");\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let text = String::from(\"The quick brown fox jumps over the lazy dog." +#~ "\");\n" +#~ " let fox = Highlight(&text[4..19]);\n" +#~ " let dog = Highlight(&text[35..43]);\n" +#~ " // erase(text);\n" +#~ " println!(\"{fox:?}\");\n" +#~ " println!(\"{dog:?}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "Methods are defined in an `impl` block, which we will see in following " +#~ "slides." +#~ msgstr "方法是在“impl”块中进行定义的，我们将在后面的幻灯片中看到。" + +#~ msgid "" +#~ "The `new` function could be written using `Self` as a type, as it is " +#~ "interchangeable with the struct type name" +#~ msgstr "" +#~ "在编写“new”函数时可以使用“Self”作为类型，因为它可以与结构体类型名称互换" + +#~ msgid "" +#~ "Implement the `Default` trait for the struct. Define some fields and use " +#~ "the default values for the other fields." +#~ msgstr "为结构体实现“Default”trait。定义一些字段并对其他字段使用默认值。" + +#~ msgid "Methods are defined in the `impl` block." +#~ msgstr "方法是在“impl”块中进行定义的。" + +#~ msgid "" +#~ "Use struct update syntax to define a new structure using `peter`. Note " +#~ "that the variable `peter` will no longer be accessible afterwards." +#~ msgstr "" +#~ "使用结构体更新语法以利用“peter”定义一个新结构。请注意，之后将无法再访问变" +#~ "量“peter”。" + +#~ msgid "" +#~ "Use `{:#?}` when printing structs to request the `Debug` representation." +#~ msgstr "在输出结构体时，使用“{:#?}”来请求“Debug”表示法。" + +#~ msgid "We describe the distinction between method receivers next." +#~ msgstr "下面，我们将介绍方法接收器之间的区别。" + +#~ msgid "" +#~ "Consider emphasizing \"shared and immutable\" and \"unique and mutable\". " +#~ "These constraints always come together in Rust due to borrow checker " +#~ "rules, and `self` is no exception. It isn't possible to reference a " +#~ "struct from multiple locations and call a mutating (`&mut self`) method " +#~ "on it." +#~ msgstr "" +#~ "建议强调“共享且不可变”和“唯一且可变”。由于借用检查器规则的原因，这些约束" +#~ "在 Rust 中总是一起出现，而“self”也不例外。您无法从多个位置引用结构体并对其" +#~ "调用一项改变（“&mut self”）方法。" + +#~ msgid "All four methods here use a different method receiver." +#~ msgstr "这里的所有四种方法都使用一个不同的方法接收器。" + +#~ msgid "" +#~ "You can point out how that changes what the function can do with the " +#~ "variable values and if/how it can be used again in `main`." +#~ msgstr "" +#~ "您可以指出这会如何改变函数可对变量值采取的操作，以及是否/如何能够" +#~ "在“main”中再次使用该函数。" + +#~ msgid "" +#~ "You can showcase the error that appears when trying to call `finish` " +#~ "twice." +#~ msgstr "您可以展示在尝试调用“finish”两次时出现的错误。" + +#~ msgid "" +#~ "Note that although the method receivers are different, the non-static " +#~ "functions are called the same way in the main body. Rust enables " +#~ "automatic referencing and dereferencing when calling methods. Rust " +#~ "automatically adds in the `&`, `*`, `muts` so that that object matches " +#~ "the method signature." +#~ msgstr "" +#~ "请注意，尽管方法接收器不同，但是非静态函数在 main 函数体中的调用方式相同。" +#~ "Rust 支持在调用方法时自动引用和解引用，并会自动加入“&”“\\*”和“muts”以便该" +#~ "对象与方法签名匹配。" + +#~ msgid "" +#~ "You might point out that `print_laps` is using a vector that is iterated " +#~ "over. We describe vectors in more detail in the afternoon. " +#~ msgstr "" +#~ "您或许可以指出 `print_laps` 使用的是不断迭代的vector。我们将在下午详细说明" +#~ "这些vector。" + +#~ msgid "Day 2: Morning Exercises" +#~ msgstr "第二天上午习题" + +#~ msgid "We will look at implementing methods in two contexts:" +#~ msgstr "我们将考虑以下两种场景：" + +#~ msgid "Storing books and querying the collection" +#~ msgstr "存储图书和查询馆藏" + +#~ msgid "Keeping track of health statistics for patients" +#~ msgstr "跟踪患者的健康统计信息" -#: src/exercises/day-2/solutions-morning.md:7 -msgid "" -"```rust\n" -"struct Library {\n" -" books: Vec,\n" -"}\n" -"\n" -"struct Book {\n" -" title: String,\n" -" year: u16,\n" -"}\n" -"\n" -"impl Book {\n" -" // This is a constructor, used below.\n" -" fn new(title: &str, year: u16) -> Book {\n" -" Book {\n" -" title: String::from(title),\n" -" year,\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Implement the methods below. Notice how the `self` parameter\n" -"// changes type to indicate the method's required level of ownership\n" -"// over the object:\n" -"//\n" -"// - `&self` for shared read-only access,\n" -"// - `&mut self` for unique and mutable access,\n" -"// - `self` for unique access by value.\n" -"impl Library {\n" -"\n" -" fn new() -> Library {\n" -" Library { books: Vec::new() }\n" -" }\n" -"\n" -" fn len(&self) -> usize {\n" -" self.books.len()\n" -" }\n" -"\n" -" fn is_empty(&self) -> bool {\n" -" self.books.is_empty()\n" -" }\n" -"\n" -" fn add_book(&mut self, book: Book) {\n" -" self.books.push(book)\n" -" }\n" -"\n" -" fn print_books(&self) {\n" -" for book in &self.books {\n" -" println!(\"{}, published in {}\", book.title, book.year);\n" -" }\n" -" }\n" -"\n" -" fn oldest_book(&self) -> Option<&Book> {\n" -" // Using a closure and a built-in method:\n" -" // self.books.iter().min_by_key(|book| book.year)\n" -"\n" -" // Longer hand-written solution:\n" -" let mut oldest: Option<&Book> = None;\n" -" for book in self.books.iter() {\n" -" if oldest.is_none() || book.year < oldest.unwrap().year {\n" -" oldest = Some(book);\n" -" }\n" -" }\n" -"\n" -" oldest\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut library = Library::new();\n" -"\n" -" println!(\n" -" \"The library is empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -"\n" -" println!(\n" -" \"The library is no longer empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.print_books();\n" -"\n" -" match library.oldest_book() {\n" -" Some(book) => println!(\"The oldest book is {}\", book.title),\n" -" None => println!(\"The library is empty!\"),\n" -" }\n" -"\n" -" println!(\"The library has {} books\", library.len());\n" -" library.print_books();\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_len() {\n" -" let mut library = Library::new();\n" -" assert_eq!(library.len(), 0);\n" -" assert!(library.is_empty());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" assert_eq!(library.len(), 2);\n" -" assert!(!library.is_empty());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_is_empty() {\n" -" let mut library = Library::new();\n" -" assert!(library.is_empty());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" assert!(!library.is_empty());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_print_books() {\n" -" let mut library = Library::new();\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" // We could try and capture stdout, but let us just call the\n" -" // method to start with.\n" -" library.print_books();\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_oldest_book() {\n" -" let mut library = Library::new();\n" -" assert!(library.oldest_book().is_none());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" assert_eq!(\n" -" library.oldest_book().map(|b| b.title.as_str()),\n" -" Some(\"Lord of the Rings\")\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" assert_eq!(\n" -" library.oldest_book().map(|b| b.title.as_str()),\n" -" Some(\"Alice's Adventures in Wonderland\")\n" -" );\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "" +#~ "We will learn much more about structs and the `Vec` type tomorrow. For " +#~ "now, you just need to know part of its API:" +#~ msgstr "" +#~ "我们明天会更详细地介绍结构体和“Vec\n" +#~ "\n" +#~ "”类型。目前，您只需了解其 API 的一部分：" -#: src/exercises/day-2/solutions-morning.md:153 #, fuzzy -msgid "([back to exercise](health-statistics.md))" -msgstr "([返回练习](rtc.md))" +#~ msgid "" +#~ "Use this to model a library's book collection. Copy the code below to " +#~ " and update the types to make it compile:" +#~ msgstr "将下面的代码复制到 并实现上述函数：" -#: src/exercises/day-2/solutions-morning.md:155 -msgid "" -"```rust\n" -"pub struct User {\n" -" name: String,\n" -" age: u32,\n" -" height: f32,\n" -" visit_count: usize,\n" -" last_blood_pressure: Option<(u32, u32)>,\n" -"}\n" -"\n" -"pub struct Measurements {\n" -" height: f32,\n" -" blood_pressure: (u32, u32),\n" -"}\n" -"\n" -"pub struct HealthReport<'a> {\n" -" patient_name: &'a str,\n" -" visit_count: u32,\n" -" height_change: f32,\n" -" blood_pressure_change: Option<(i32, i32)>,\n" -"}\n" -"\n" -"impl User {\n" -" pub fn new(name: String, age: u32, height: f32) -> Self {\n" -" Self {\n" -" name,\n" -" age,\n" -" height,\n" -" visit_count: 0,\n" -" last_blood_pressure: None,\n" -" }\n" -" }\n" -"\n" -" pub fn name(&self) -> &str {\n" -" &self.name\n" -" }\n" -"\n" -" pub fn age(&self) -> u32 {\n" -" self.age\n" -" }\n" -"\n" -" pub fn height(&self) -> f32 {\n" -" self.height\n" -" }\n" -"\n" -" pub fn doctor_visits(&self) -> u32 {\n" -" self.visit_count as u32\n" -" }\n" -"\n" -" pub fn set_age(&mut self, new_age: u32) {\n" -" self.age = new_age\n" -" }\n" -"\n" -" pub fn set_height(&mut self, new_height: f32) {\n" -" self.height = new_height\n" -" }\n" -"\n" -" pub fn visit_doctor(&mut self, measurements: Measurements) -> " -"HealthReport {\n" -" self.visit_count += 1;\n" -" let bp = measurements.blood_pressure;\n" -" let report = HealthReport {\n" -" patient_name: &self.name,\n" -" visit_count: self.visit_count as u32,\n" -" height_change: measurements.height - self.height,\n" -" blood_pressure_change: match self.last_blood_pressure {\n" -" Some(lbp) => Some((\n" -" bp.0 as i32 - lbp.0 as i32,\n" -" bp.1 as i32 - lbp.1 as i32\n" -" )),\n" -" None => None,\n" -" }\n" -" };\n" -" self.height = measurements.height;\n" -" self.last_blood_pressure = Some(bp);\n" -" report\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" println!(\"I'm {} and my age is {}\", bob.name(), bob.age());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_height() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.height(), 155.2);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_set_age() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.age(), 32);\n" -" bob.set_age(33);\n" -" assert_eq!(bob.age(), 33);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_visit() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.doctor_visits(), 0);\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (120, 80),\n" -" });\n" -" assert_eq!(report.patient_name, \"Bob\");\n" -" assert_eq!(report.visit_count, 1);\n" -" assert_eq!(report.blood_pressure_change, None);\n" -"\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (115, 76),\n" -" });\n" -"\n" -" assert_eq!(report.visit_count, 2);\n" -" assert_eq!(report.blood_pressure_change, Some((-5, -4)));\n" -"}\n" -"```" -msgstr "" +#~ msgid "The common vocabulary types include:" +#~ msgstr "常见的词汇类型包括：" -#: src/exercises/day-2/solutions-afternoon.md:1 -msgid "Day 2 Afternoon Exercises" -msgstr "第二天下午的练习" +#~ msgid "" +#~ "[`Option` and `Result`](std/option-result.md) types: used for optional " +#~ "values and [error handling](error-handling.md)." +#~ msgstr "" +#~ "[`Option` 和 `Result`](std/option-result.md) 类型：用于可选值和 [错误处理]" +#~ "(error-handling.md)。" -#: src/exercises/day-2/solutions-afternoon.md:5 -msgid "([back to exercise](strings-iterators.md))" -msgstr "([返回练习](strings-iterators.md))" +#~ msgid "" +#~ "[`String`](std/string.md): the default string type used for owned data." +#~ msgstr "[`String`](std/string.md)：用于自有数据的默认字符串类型。" -#: src/exercises/day-2/solutions-afternoon.md:7 -msgid "" -"```rust\n" -"pub fn prefix_matches(prefix: &str, request_path: &str) -> bool {\n" -"\n" -" let mut request_segments = request_path.split('/');\n" -"\n" -" for prefix_segment in prefix.split('/') {\n" -" let Some(request_segment) = request_segments.next() else {\n" -" return false;\n" -" };\n" -" if request_segment != prefix_segment && prefix_segment != \"*\" {\n" -" return false;\n" -" }\n" -" }\n" -" true\n" -"\n" -" // Alternatively, Iterator::zip() lets us iterate simultaneously over " -"prefix\n" -" // and request segments. The zip() iterator is finished as soon as one " -"of\n" -" // the source iterators is finished, but we need to iterate over all " -"request\n" -" // segments. A neat trick that makes zip() work is to use map() and " -"chain()\n" -" // to produce an iterator that returns Some(str) for each pattern " -"segments,\n" -" // and then returns None indefinitely.\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_without_wildcard() {\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/" -"abc-123\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/abc/" -"books\"));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/publishersBooks\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/parent/" -"publishers\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_with_wildcard() {\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/bar/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books/book1\"\n" -" ));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers/*/books\", \"/v1/" -"publishers\"));\n" -" assert!(!prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/booksByAuthor\"\n" -" ));\n" -"}\n" -"\n" -"fn main() {}\n" -"```" -msgstr "" +#~ msgid "[`Vec`](std/vec.md): a standard extensible vector." +#~ msgstr "[`Vec`](std/vec.md)：标准的可扩展矢量。" -#: src/exercises/day-3/solutions-morning.md:1 -msgid "Day 3 Morning Exercise" -msgstr "第三天上午的练习" +#~ msgid "" +#~ "[`HashMap`](std/hashmap.md): a hash map type with a configurable hashing " +#~ "algorithm." +#~ msgstr "[`HashMap`](std/hashmap.md)：采用可配置哈希算法的哈希映射 类型。" -#: src/exercises/day-3/solutions-morning.md:5 -msgid "([back to exercise](simple-gui.md))" -msgstr "([返回练习](simple-gui.md))" +#~ msgid "[`Box`](std/box.md): an owned pointer for heap-allocated data." +#~ msgstr "[`Box`](std/box.md)：适用于堆分配数据的自有指针。" -#: src/exercises/day-3/solutions-morning.md:7 -msgid "" -"```rust\n" -"pub trait Widget {\n" -" /// Natural width of `self`.\n" -" fn width(&self) -> usize;\n" -"\n" -" /// Draw the widget into a buffer.\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write);\n" -"\n" -" /// Draw the widget on standard output.\n" -" fn draw(&self) {\n" -" let mut buffer = String::new();\n" -" self.draw_into(&mut buffer);\n" -" println!(\"{buffer}\");\n" -" }\n" -"}\n" -"\n" -"pub struct Label {\n" -" label: String,\n" -"}\n" -"\n" -"impl Label {\n" -" fn new(label: &str) -> Label {\n" -" Label {\n" -" label: label.to_owned(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Button {\n" -" label: Label,\n" -"}\n" -"\n" -"impl Button {\n" -" fn new(label: &str) -> Button {\n" -" Button {\n" -" label: Label::new(label),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Window {\n" -" title: String,\n" -" widgets: Vec>,\n" -"}\n" -"\n" -"impl Window {\n" -" fn new(title: &str) -> Window {\n" -" Window {\n" -" title: title.to_owned(),\n" -" widgets: Vec::new(),\n" -" }\n" -" }\n" -"\n" -" fn add_widget(&mut self, widget: Box) {\n" -" self.widgets.push(widget);\n" -" }\n" -"\n" -" fn inner_width(&self) -> usize {\n" -" std::cmp::max(\n" -" self.title.chars().count(),\n" -" self.widgets.iter().map(|w| w.width()).max().unwrap_or(0),\n" -" )\n" -" }\n" -"}\n" -"\n" -"\n" -"impl Widget for Window {\n" -" fn width(&self) -> usize {\n" -" // Add 4 paddings for borders\n" -" self.inner_width() + 4\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" let mut inner = String::new();\n" -" for widget in &self.widgets {\n" -" widget.draw_into(&mut inner);\n" -" }\n" -"\n" -" let inner_width = self.inner_width();\n" -"\n" -" // TODO: after learning about error handling, you can change\n" -" // draw_into to return Result<(), std::fmt::Error>. Then use\n" -" // the ?-operator here instead of .unwrap().\n" -" writeln!(buffer, \"+-{:- usize {\n" -" self.label.width() + 8 // add a bit of padding\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" let width = self.width();\n" -" let mut label = String::new();\n" -" self.label.draw_into(&mut label);\n" -"\n" -" writeln!(buffer, \"+{:- usize {\n" -" self.label\n" -" .lines()\n" -" .map(|line| line.chars().count())\n" -" .max()\n" -" .unwrap_or(0)\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" writeln!(buffer, \"{}\", &self.label).unwrap();\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut window = Window::new(\"Rust GUI Demo 1.23\");\n" -" window.add_widget(Box::new(Label::new(\"This is a small text GUI demo." -"\")));\n" -" window.add_widget(Box::new(Button::new(\n" -" \"Click me!\"\n" -" )));\n" -" window.draw();\n" -"}\n" -"```" -msgstr "" +#~ msgid "" +#~ "[`Rc`](std/rc.md): a shared reference-counted pointer for heap-allocated " +#~ "data." +#~ msgstr "[`Rc`](std/rc.md)：适用于堆分配数据的共享引用计数指针。" -#: src/exercises/day-3/solutions-morning.md:144 -msgid "([back to exercise](points-polygons.md))" -msgstr "([返回练习](points-polygons.md))" +#~ msgid "`Option` and `Result`" +#~ msgstr "`Option` 和 `Result`" -#: src/exercises/day-3/solutions-morning.md:146 -msgid "" -"```rust\n" -"#[derive(Debug, Copy, Clone, PartialEq, Eq)]\n" -"pub struct Point {\n" -" x: i32,\n" -" y: i32,\n" -"}\n" -"\n" -"impl Point {\n" -" pub fn new(x: i32, y: i32) -> Point {\n" -" Point { x, y }\n" -" }\n" -"\n" -" pub fn magnitude(self) -> f64 {\n" -" f64::from(self.x.pow(2) + self.y.pow(2)).sqrt()\n" -" }\n" -"\n" -" pub fn dist(self, other: Point) -> f64 {\n" -" (self - other).magnitude()\n" -" }\n" -"}\n" -"\n" -"impl std::ops::Add for Point {\n" -" type Output = Self;\n" -"\n" -" fn add(self, other: Self) -> Self::Output {\n" -" Self {\n" -" x: self.x + other.x,\n" -" y: self.y + other.y,\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl std::ops::Sub for Point {\n" -" type Output = Self;\n" -"\n" -" fn sub(self, other: Self) -> Self::Output {\n" -" Self {\n" -" x: self.x - other.x,\n" -" y: self.y - other.y,\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Polygon {\n" -" points: Vec,\n" -"}\n" -"\n" -"impl Polygon {\n" -" pub fn new() -> Polygon {\n" -" Polygon { points: Vec::new() }\n" -" }\n" -"\n" -" pub fn add_point(&mut self, point: Point) {\n" -" self.points.push(point);\n" -" }\n" -"\n" -" pub fn left_most_point(&self) -> Option {\n" -" self.points.iter().min_by_key(|p| p.x).copied()\n" -" }\n" -"\n" -" pub fn iter(&self) -> impl Iterator {\n" -" self.points.iter()\n" -" }\n" -"\n" -" pub fn length(&self) -> f64 {\n" -" if self.points.is_empty() {\n" -" return 0.0;\n" -" }\n" -"\n" -" let mut result = 0.0;\n" -" let mut last_point = self.points[0];\n" -" for point in &self.points[1..] {\n" -" result += last_point.dist(*point);\n" -" last_point = *point;\n" -" }\n" -" result += last_point.dist(self.points[0]);\n" -" result\n" -" // Alternatively, Iterator::zip() lets us iterate over the points as " -"pairs\n" -" // but we need to pair each point with the next one, and the last " -"point\n" -" // with the first point. The zip() iterator is finished as soon as " -"one of \n" -" // the source iterators is finished, a neat trick is to combine " -"Iterator::cycle\n" -" // with Iterator::skip to create the second iterator for the zip and " -"using map \n" -" // and sum to calculate the total length.\n" -" }\n" -"}\n" -"\n" -"pub struct Circle {\n" -" center: Point,\n" -" radius: i32,\n" -"}\n" -"\n" -"impl Circle {\n" -" pub fn new(center: Point, radius: i32) -> Circle {\n" -" Circle { center, radius }\n" -" }\n" -"\n" -" pub fn circumference(&self) -> f64 {\n" -" 2.0 * std::f64::consts::PI * f64::from(self.radius)\n" -" }\n" -"\n" -" pub fn dist(&self, other: &Self) -> f64 {\n" -" self.center.dist(other.center)\n" -" }\n" -"}\n" -"\n" -"pub enum Shape {\n" -" Polygon(Polygon),\n" -" Circle(Circle),\n" -"}\n" -"\n" -"impl From for Shape {\n" -" fn from(poly: Polygon) -> Self {\n" -" Shape::Polygon(poly)\n" -" }\n" -"}\n" -"\n" -"impl From for Shape {\n" -" fn from(circle: Circle) -> Self {\n" -" Shape::Circle(circle)\n" -" }\n" -"}\n" -"\n" -"impl Shape {\n" -" pub fn perimeter(&self) -> f64 {\n" -" match self {\n" -" Shape::Polygon(poly) => poly.length(),\n" -" Shape::Circle(circle) => circle.circumference(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" fn round_two_digits(x: f64) -> f64 {\n" -" (x * 100.0).round() / 100.0\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_magnitude() {\n" -" let p1 = Point::new(12, 13);\n" -" assert_eq!(round_two_digits(p1.magnitude()), 17.69);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_dist() {\n" -" let p1 = Point::new(10, 10);\n" -" let p2 = Point::new(14, 13);\n" -" assert_eq!(round_two_digits(p1.dist(p2)), 5.00);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_add() {\n" -" let p1 = Point::new(16, 16);\n" -" let p2 = p1 + Point::new(-4, 3);\n" -" assert_eq!(p2, Point::new(12, 19));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_left_most_point() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -" assert_eq!(poly.left_most_point(), Some(p1));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_iter() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -"\n" -" let points = poly.iter().cloned().collect::>();\n" -" assert_eq!(points, vec![Point::new(12, 13), Point::new(16, 16)]);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_shape_perimeters() {\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(Point::new(12, 13));\n" -" poly.add_point(Point::new(17, 11));\n" -" poly.add_point(Point::new(16, 16));\n" -" let shapes = vec![\n" -" Shape::from(poly),\n" -" Shape::from(Circle::new(Point::new(10, 20), 5)),\n" -" ];\n" -" let perimeters = shapes\n" -" .iter()\n" -" .map(Shape::perimeter)\n" -" .map(round_two_digits)\n" -" .collect::>();\n" -" assert_eq!(perimeters, vec![15.48, 31.42]);\n" -" }\n" -"}\n" -"\n" -"fn main() {}\n" -"```" -msgstr "" +#~ msgid "The types represent optional data:" +#~ msgstr "这些类型表示可选数据：" -#: src/exercises/day-3/solutions-afternoon.md:1 -msgid "Day 3 Afternoon Exercises" -msgstr "第三天下午的练习" +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let numbers = vec![10, 20, 30];\n" +#~ " let first: Option<&i8> = numbers.first();\n" +#~ " println!(\"first: {first:?}\");\n" +#~ "\n" +#~ " let arr: Result<[i8; 3], Vec> = numbers.try_into();\n" +#~ " println!(\"arr: {arr:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let v = vec![10, 20, 30];\n" +#~ " let mut iter = v.into_iter();\n" +#~ "\n" +#~ " while let Some(x) = iter.next() {\n" +#~ " println!(\"x: {x}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "`Option<&T>` has zero space overhead compared to `&T`." +#~ msgstr "相较于 `&T`，`Option<&T>` 的空间开销为零。" + +#~ msgid "" +#~ "Show iterating over a vector and mutating the value: `for e in &mut v " +#~ "{ *e += 50; }`" +#~ msgstr "介绍如何迭代矢量并更改它的值：“for e in &mut v { \\*e += 50; }”" + +#~ msgid "" +#~ "In the above example, you can even leave out the `*` in the `println!` " +#~ "statement thanks to `Deref`. " +#~ msgstr "" +#~ "在上面的示例中，因为有 `Deref`，您甚至可以在 `println!` 语句中省略 `*`。" + +#~ msgid "Box with Recursive Data Structures" +#~ msgstr "包含递归数据结构的 Box" + +#~ msgid "Day 2: Afternoon Exercises" +#~ msgstr "第二天下午习题" + +#~ msgid "" +#~ "The exercises for this afternoon will focus on strings and iterators." +#~ msgstr "今天下午的习题将重点关注字符串（string）和迭代器（iterator）。" + +#~ msgid "" +#~ "The ownership model of Rust affects many APIs. An example of this is the " +#~ "[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " +#~ "[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator." +#~ "html) traits." +#~ msgstr "" +#~ "Rust 的所有权模式会影响许多 API。例如，[“Iterator”](https://doc.rust-lang." +#~ "org/std/iter/trait.Iterator.html)和[“IntoIterator”](https://doc.rust-lang." +#~ "org/std/iter/trait.IntoIterator.html) trait。" + +#~ msgid "" +#~ "Traits are like interfaces: they describe behavior (methods) for a type. " +#~ "The `Iterator` trait simply says that you can call `next` until you get " +#~ "`None` back:" +#~ msgstr "" +#~ "trait 类似于接口：它们描述某类型的行为（方法）。`Iterator` trait 只是告知" +#~ "您可以调用 `next`，直到返回 `None`：" + +#~ msgid "You use this trait like this:" +#~ msgstr "您可以按如下方式使用此 trait：" + +#~ msgid "What is the type returned by the iterator? Test your answer here:" +#~ msgstr "迭代器返回的类型是什么？请在此测试您的答案：" + +#~ msgid "Why is this type used?" +#~ msgstr "为什么要使用此类型？" + +#~ msgid "Like before, what is the type returned by the iterator?" +#~ msgstr "和之前一样，迭代器返回的类型是什么？" + +#~ msgid "" +#~ "Now that we know both `Iterator` and `IntoIterator`, we can build `for` " +#~ "loops. They call `into_iter()` on an expression and iterates over the " +#~ "resulting iterator:" +#~ msgstr "" +#~ "现在，我们已了解了“Iterator”和“IntoIterator”，接下来可以构建“for”循环了。" +#~ "它们会针对表达式调用“into_iter()”，并对生成的迭代器进行迭代：" -#: src/exercises/day-3/solutions-afternoon.md:5 -msgid "([back to exercise](safe-ffi-wrapper.md))" -msgstr "([返回练习](safe-ffi-wrapper.md))" +#, fuzzy +#~ msgid "" +#~ "Experiment with the code above and then consult the documentation for " +#~ "[`impl IntoIterator for &Vec`](https://doc.rust-lang.org/std/vec/" +#~ "struct.Vec.html#impl-IntoIterator-for-%26'a+Vec%3CT,+A%3E) and [`impl " +#~ "IntoIterator for Vec`](https://doc.rust-lang.org/std/vec/struct.Vec." +#~ "html#impl-IntoIterator-for-Vec%3CT,+A%3E) to check your answers." +#~ msgstr "" +#~ "使用上方代码进行实验，然后参阅[“impl IntoIterator for &Vec\n" +#~ "\n" +#~ "”](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-" +#~ "for-%26'a+Vec%3CT,+A%3E)和[“impl IntoIterator for Vec\n" +#~ "\n" +#~ "”](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-" +#~ "for-Vec%3CT,+A%3E)的相关文档来检查您的答案。" + +#~ msgid "" +#~ "In this exercise, you are implementing a routing component of a web " +#~ "server. The server is configured with a number of _path prefixes_ which " +#~ "are matched against _request paths_. The path prefixes can contain a " +#~ "wildcard character which matches a full segment. See the unit tests below." +#~ msgstr "" +#~ "在本练习中，您将实现 Web 服务器的路由组件。服务器配置有多个路径前缀，这些" +#~ "前缀与请求路径匹配。路径前缀可以包含与完整段匹配的通配符。请参阅下面的单元" +#~ "测试。" + +#~ msgid "" +#~ "Traits: deriving traits, default methods, and important standard library " +#~ "traits." +#~ msgstr "trait：派生 trait、默认方法和重要的标准库 trait。" + +#~ msgid "" +#~ "Generics: generic data types, generic methods, monomorphization, and " +#~ "trait objects." +#~ msgstr "泛型：泛型数据类型、泛型方法、单态化和 trait 对象。" + +#~ msgid "Testing: unit tests, documentation tests, and integration tests." +#~ msgstr "测试：单元测试、文档测试和集成测试。" + +#~ msgid "" +#~ "Unsafe Rust: raw pointers, static variables, unsafe functions, and extern " +#~ "functions." +#~ msgstr "不安全 Rust：原始指针、静态变量、不安全函数和外部函数。" + +#~ msgid "Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`." +#~ msgstr "尝试声明一个新变量“let p = Point { x: 5, y: 10.0 };”。" + +#~ msgid "Fix the code to allow points that have elements of different types." +#~ msgstr "修正代码，以允许点具有不同类型的元素。" + +#~ msgid "You can declare a generic type on your `impl` block:" +#~ msgstr "您可以在 `impl` 块中声明通用类型：" + +#~ msgid "" +#~ "Generic code is turned into non-generic code based on the call sites:" +#~ msgstr "泛型代码根据调用位置转换为非泛型代码：" + +#~ msgid "behaves as if you wrote" +#~ msgstr "具体行为与您所编写的一样" + +#~ msgid "" +#~ "Rust derive macros work by automatically generating code that implements " +#~ "the specified traits for a data structure." +#~ msgstr "Rust 派生宏的运作方式是自动生成代码，用于实现数据结构的指定 trait。" -#: src/exercises/day-3/solutions-afternoon.md:7 -msgid "" -"```rust\n" -"mod ffi {\n" -" use std::os::raw::{c_char, c_int};\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" use std::os::raw::{c_long, c_ulong, c_ushort, c_uchar};\n" -"\n" -" // Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" -" #[repr(C)]\n" -" pub struct DIR {\n" -" _data: [u8; 0],\n" -" _marker: core::marker::PhantomData<(*mut u8, core::marker::" -"PhantomPinned)>,\n" -" }\n" -"\n" -" // Layout according to the Linux man page for readdir(3), where ino_t " -"and\n" -" // off_t are resolved according to the definitions in\n" -" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_ino: c_ulong,\n" -" pub d_off: c_long,\n" -" pub d_reclen: c_ushort,\n" -" pub d_type: c_uchar,\n" -" pub d_name: [c_char; 256],\n" -" }\n" -"\n" -" // Layout according to the macOS man page for dir(5).\n" -" #[cfg(all(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_fileno: u64,\n" -" pub d_seekoff: u64,\n" -" pub d_reclen: u16,\n" -" pub d_namlen: u16,\n" -" pub d_type: u8,\n" -" pub d_name: [c_char; 1024],\n" -" }\n" -"\n" -" extern \"C\" {\n" -" pub fn opendir(s: *const c_char) -> *mut DIR;\n" -"\n" -" #[cfg(not(all(target_os = \"macos\", target_arch = \"x86_64\")))]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" // See https://github.com/rust-lang/libc/issues/414 and the section " -"on\n" -" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" -" //\n" -" // \"Platforms that existed before these updates were available\" " -"refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " -"PowerPC.\n" -" #[cfg(all(target_os = \"macos\", target_arch = \"x86_64\"))]\n" -" #[link_name = \"readdir$INODE64\"]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" pub fn closedir(s: *mut DIR) -> c_int;\n" -" }\n" -"}\n" -"\n" -"use std::ffi::{CStr, CString, OsStr, OsString};\n" -"use std::os::unix::ffi::OsStrExt;\n" -"\n" -"#[derive(Debug)]\n" -"struct DirectoryIterator {\n" -" path: CString,\n" -" dir: *mut ffi::DIR,\n" -"}\n" -"\n" -"impl DirectoryIterator {\n" -" fn new(path: &str) -> Result {\n" -" // Call opendir and return a Ok value if that worked,\n" -" // otherwise return Err with a message.\n" -" let path = CString::new(path).map_err(|err| format!(\"Invalid path: " -"{err}\"))?;\n" -" // SAFETY: path.as_ptr() cannot be NULL.\n" -" let dir = unsafe { ffi::opendir(path.as_ptr()) };\n" -" if dir.is_null() {\n" -" Err(format!(\"Could not open {:?}\", path))\n" -" } else {\n" -" Ok(DirectoryIterator { path, dir })\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl Iterator for DirectoryIterator {\n" -" type Item = OsString;\n" -" fn next(&mut self) -> Option {\n" -" // Keep calling readdir until we get a NULL pointer back.\n" -" // SAFETY: self.dir is never NULL.\n" -" let dirent = unsafe { ffi::readdir(self.dir) };\n" -" if dirent.is_null() {\n" -" // We have reached the end of the directory.\n" -" return None;\n" -" }\n" -" // SAFETY: dirent is not NULL and dirent.d_name is NUL\n" -" // terminated.\n" -" let d_name = unsafe { CStr::from_ptr((*dirent).d_name.as_ptr()) };\n" -" let os_str = OsStr::from_bytes(d_name.to_bytes());\n" -" Some(os_str.to_owned())\n" -" }\n" -"}\n" -"\n" -"impl Drop for DirectoryIterator {\n" -" fn drop(&mut self) {\n" -" // Call closedir as needed.\n" -" if !self.dir.is_null() {\n" -" // SAFETY: self.dir is not NULL.\n" -" if unsafe { ffi::closedir(self.dir) } != 0 {\n" -" panic!(\"Could not close {:?}\", self.path);\n" -" }\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn main() -> Result<(), String> {\n" -" let iter = DirectoryIterator::new(\".\")?;\n" -" println!(\"files: {:#?}\", iter.collect::>());\n" -" Ok(())\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -" use std::error::Error;\n" -"\n" -" #[test]\n" -" fn test_nonexisting_directory() {\n" -" let iter = DirectoryIterator::new(\"no-such-directory\");\n" -" assert!(iter.is_err());\n" -" }\n" -"\n" -" #[test]\n" -" fn test_empty_directory() -> Result<(), Box> {\n" -" let tmp = tempfile::TempDir::new()?;\n" -" let iter = DirectoryIterator::new(\n" -" tmp.path().to_str().ok_or(\"Non UTF-8 character in path\")?,\n" -" )?;\n" -" let mut entries = iter.collect::>();\n" -" entries.sort();\n" -" assert_eq!(entries, &[\".\", \"..\"]);\n" -" Ok(())\n" -" }\n" -"\n" -" #[test]\n" -" fn test_nonempty_directory() -> Result<(), Box> {\n" -" let tmp = tempfile::TempDir::new()?;\n" -" std::fs::write(tmp.path().join(\"foo.txt\"), \"The Foo " -"Diaries\\n\")?;\n" -" std::fs::write(tmp.path().join(\"bar.png\"), \"\\n\")?;\n" -" std::fs::write(tmp.path().join(\"crab.rs\"), \"//! Crab\\n\")?;\n" -" let iter = DirectoryIterator::new(\n" -" tmp.path().to_str().ok_or(\"Non UTF-8 character in path\")?,\n" -" )?;\n" -" let mut entries = iter.collect::>();\n" -" entries.sort();\n" -" assert_eq!(entries, &[\".\", \"..\", \"bar.png\", \"crab.rs\", \"foo." -"txt\"]);\n" -" Ok(())\n" -" }\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "You can let the compiler derive a number of traits as follows:" +#~ msgstr "您可以让编译器派生多个特征：" + +#~ msgid "Traits can implement behavior in terms of other trait methods:" +#~ msgstr "特征可以依照其他特征方法来实现行为：" + +#~ msgid "Move method `not_equals` to a new trait `NotEquals`." +#~ msgstr "将方法“not_equals”移至新的 trait“NotEquals”。" + +#~ msgid "Make `Equals` a super trait for `NotEquals`." +#~ msgstr "将“Equals”设为“NotEquals”的超 trait。" + +#~ msgid "Provide a blanket implementation of `NotEquals` for `Equals`." +#~ msgstr "为“Equals”提供“NotEquals”的通用实现。" + +#~ msgid "" +#~ "With the blanket implementation, you no longer need `Equals` as a super " +#~ "trait for `NotEqual`." +#~ msgstr "借助通用实现，您不再需要将“Equals”作为“NotEqual”的超 trait。" + +#~ msgid "`impl Trait` allows you to work with types which you cannot name." +#~ msgstr "`impl Trait` 让您可使用无法命名的类型。" + +#~ msgid "" +#~ "This example is great, because it uses `impl Display` twice. It helps to " +#~ "explain that nothing here enforces that it is _the same_ `impl Display` " +#~ "type. If we used a single `T: Display`, it would enforce the constraint " +#~ "that input `T` and return `T` type are the same type. It would not work " +#~ "for this particular function, as the type we expect as input is likely " +#~ "not what `format!` returns. If we wanted to do the same via `: Display` " +#~ "syntax, we'd need two independent generic parameters." +#~ msgstr "" +#~ "这是一个非常棒的示例，因为它使用了两次 `impl Display`。这有助于说明 此处没" +#~ "有任何项目会强制使用相同的 `impl Display` 类型。如果我们使用单个 `T: " +#~ "Display`，它会强制限制输入 `T` 和返回 `T` 均为同一类型。 这并不适用于这个" +#~ "特定函数，因为我们预期作为输入的类型可能 不会是 `format!` 返回的值。如果我" +#~ "们希望通过 `: Display` 语法执行相同的操作，则需要两个 独立的泛型形参。" + +#~ msgid "" +#~ "We will now look at some of the most common traits of the Rust standard " +#~ "library:" +#~ msgstr "现在，我们来看看 Rust 标准库的一些最常见的特征：" + +#~ msgid "" +#~ "[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " +#~ "[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator." +#~ "html) used in `for` loops," +#~ msgstr "" +#~ "[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) 和 " +#~ "[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator." +#~ "html) 用于 `for` 循环中，" + +#~ msgid "" +#~ "[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) and " +#~ "[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) used to " +#~ "convert values," +#~ msgstr "" +#~ "[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 和 " +#~ "[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) 用于转换" +#~ "值，" + +#~ msgid "" +#~ "[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and [`Write`]" +#~ "(https://doc.rust-lang.org/std/io/trait.Write.html) used for IO," +#~ msgstr "" +#~ "[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) 和 [`Write`]" +#~ "(https://doc.rust-lang.org/std/io/trait.Write.html) 用于实现 IO。" + +#~ msgid "" +#~ "[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html), [`Mul`]" +#~ "(https://doc.rust-lang.org/std/ops/trait.Mul.html), ... used for operator " +#~ "overloading, and" +#~ msgstr "" +#~ "[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html)、[`Mul`]" +#~ "(https://doc.rust-lang.org/std/ops/trait.Mul.html) 等用于实现运算符重载，" + +#~ msgid "" +#~ "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) " +#~ "used to construct a default instance of a type." +#~ msgstr "" +#~ "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) 用于" +#~ "构建相应类型的默认实例。" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let primes = vec![2, 3, 5, 7];\n" +#~ " let prime_squares = primes\n" +#~ " .into_iter()\n" +#~ " .map(|prime| prime * prime)\n" +#~ " .collect::>();\n" +#~ " println!(\"prime_squares: {prime_squares:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " let v = vec![10, 20, 30];\n" +#~ " let mut iter = v.into_iter();\n" +#~ "\n" +#~ " while let Some(x) = iter.next() {\n" +#~ " println!(\"x: {x}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "`Iterator` implements `fn collect(self) -> B where B: " +#~ "FromIterator, Self: Sized`" +#~ msgstr "" +#~ "`Iterator` 会实现 `fn collect(self) -> B where B: FromIterator, Self: Sized`" + +#~ msgid "`Add`, `Mul`, ..." +#~ msgstr "` Add`Mul \\``…" + +#~ msgid "Day 3: Morning Exercises" +#~ msgstr "第 3 天：上午练习" + +#~ msgid "" +#~ "We will design a classical GUI library using traits and trait objects." +#~ msgstr "我们将使用 trait 和 trait 对象设计一个经典的 GUI 库。" + +#~ msgid "" +#~ "We will also look at enum dispatch with an exercise involving points and " +#~ "polygons." +#~ msgstr "我们还将通过点和多边形的相关练习，探讨枚举调度情况。" + +#, fuzzy +#~ msgid "Drawing A Simple GUI" +#~ msgstr "一个简单的 GUI 库" + +#~ msgid "Polygon Struct" +#~ msgstr "多边形结构体" + +#~ msgid "" +#~ "We will create a `Polygon` struct which contain some points. Copy the " +#~ "code below to and fill in the missing " +#~ "methods to make the tests pass:" +#~ msgstr "" +#~ "我们将创建一个包含一些点的“Polygon”结构体。将以下代码复制到 ，然后填入缺少的方法，设法通过测试：" + +#~ msgid "" +#~ "Since the method signatures are missing from the problem statements, the " +#~ "key part of the exercise is to specify those correctly. You don't have to " +#~ "modify the tests." +#~ msgstr "" +#~ "由于问题语句中缺少方法签名，因此练习的关键部分是正确指定这些内容。您无需修" +#~ "改测试。" + +#~ msgid "Other interesting parts of the exercise:" +#~ msgstr "练习的其他有趣部分：" + +#~ msgid "" +#~ "Derive a `Copy` trait for some structs, as in tests the methods sometimes " +#~ "don't borrow their arguments." +#~ msgstr "" +#~ "为某些结构体派生“Copy”trait，因为在测试中，方法有时不借用它们的参数。" + +#~ msgid "" +#~ "Discover that `Add` trait must be implemented for two objects to be " +#~ "addable via \"+\". Note that we do not discuss generics until Day 3." +#~ msgstr "" +#~ "发现必须实现“Add”trait 才能通过“+”添加两个对象。请注意，我们在第 3 天之前" +#~ "不会讨论泛型。" + +#~ msgid "Error handling in Rust is done using explicit control flow:" +#~ msgstr "Rust 中的错误处理是使用显式控制流来进行的：" + +#~ msgid "Functions that can have errors list this in their return type," +#~ msgstr "包含错误的函数会在返回类型中列出相关信息。" + +#~ msgid "There are no exceptions." +#~ msgstr "此规则没有例外。" + +#~ msgid "Catching the Stack Unwinding" +#~ msgstr "捕获堆栈展开" + +#~ msgid "" +#~ "We have already seen the `Result` enum. This is used pervasively when " +#~ "errors are expected as part of normal operation:" +#~ msgstr "" +#~ "在前面，我们看到了 `Result` 枚举。在遇到正常操作产生的预期错误时， 我们常" +#~ "会用到此方法：" + +#~ msgid "Propagating Errors with `?`" +#~ msgstr "使用 `?` 传播错误" + +#~ msgid "" +#~ "The try-operator `?` is used to return errors to the caller. It lets you " +#~ "turn the common" +#~ msgstr "try 操作符 `?` 用于将错误返回给调用方。它能把常用命令" + +#, fuzzy +#~ msgid "" +#~ "The return type of the function has to be compatible with the nested " +#~ "functions it calls. For instance, a function returning a `Result` " +#~ "can only apply the `?` operator on a function returning a `Result`. It cannot apply the `?` operator on a function returning an " +#~ "`Option` or `Result` unless `OtherErr` implements " +#~ "`From`. Reciprocally, a function returning an `Option` can only " +#~ "apply the `?` operator on a function returning an `Option`." +#~ msgstr "" +#~ "函数的返回值类型必须与其调用的嵌套函数兼容。例如，一个返回“Result\\”的函数只能对返回“Result\\”的函数应用“?”运算符。它无法对返" +#~ "回“Option\n" +#~ "\n" +#~ "”或“Result\\”的函数应用“?”运算符，除非“OtherErr”实现“From\n" +#~ "\n" +#~ "”。相反地，返回“Option\n" +#~ "\n" +#~ "”的函数只能对返回“Option\n" +#~ "\n" +#~ "”的函数应用“?”运算符。" + +#~ msgid "" +#~ "You can convert incompatible types into one another with the different " +#~ "`Option` and `Result` methods such as `Option::ok_or`, `Result::ok`, " +#~ "`Result::err`." +#~ msgstr "" +#~ "您可以使用其他“Option”和“Result”方法（例如“Option::ok_or”“Result::" +#~ "ok”“Result::err”）将不兼容的类型转换为另一种类型。" + +#~ msgid "" +#~ "It is good practice for all error types that don't need to be `no_std` to " +#~ "implement `std::error::Error`, which requires `Debug` and `Display`. The " +#~ "`Error` crate for `core` is only available in [nightly](https://github." +#~ "com/rust-lang/rust/issues/103765), so not fully `no_std` compatible yet." +#~ msgstr "" +#~ "对所有不需要是“no_std”的错误类型来说，实现“std::error::Error”是一种很好的" +#~ "做法，而这需要“Debug”和“Display”。“core”的“Error”crate 仅在 [nightly]" +#~ "(https://github.com/rust-lang/rust/issues/103765) 提供，因此尚未" +#~ "与“no_std”完全兼容。" + +#, fuzzy +#~ msgid "" +#~ "It's generally helpful for them to implement `Clone` and `Eq` too where " +#~ "possible, to make life easier for tests and consumers of your library. In " +#~ "this case we can't easily do so, because `io::Error` doesn't implement " +#~ "them." +#~ msgstr "" +#~ "对所有错误类型实现 `std::error::Error` 是一种很好的做法，而这需要结合使用 " +#~ "`Debug` 和 `Display` 方法。 通常，在可能的情况下实现 `Clone` 和 `Eq` 也十" +#~ "分有益， 可以让库的测试和使用变得更加简单。在本例中，我们无法轻松做到这一" +#~ "点， 因为 `io::Error` 不能实现这些方法。" + +#~ msgid "" +#~ "The [thiserror](https://docs.rs/thiserror/) crate is a popular way to " +#~ "create an error enum like we did on the previous page:" +#~ msgstr "" +#~ "[thiserror](https://docs.rs/thiserror/) crate 是创建错误枚举的常用方法， " +#~ "就像前一页中提供的示例一样：" + +#~ msgid "" +#~ "`thiserror`'s derive macro automatically implements `std::error::Error`, " +#~ "and optionally `Display` (if the `#[error(...)]` attributes are provided) " +#~ "and `From` (if the `#[from]` attribute is added). It also works for " +#~ "structs." +#~ msgstr "" +#~ "`thiserror` 的派生宏会自动实现 `std::error::Error`，并且可以选择性地实现 " +#~ "`Display` （如果提供了 `#[error(...)]` 属性）和 `From`（如果添加了 " +#~ "`#[from]` 属性）。 此规则也适用于结构体。" + +#~ msgid "" +#~ "It doesn't affect your public API, which makes it good for libraries." +#~ msgstr "但是，此规则不会影响公共 API，对于库而言，这非常理想。" + +#~ msgid "" +#~ "The widely used [anyhow](https://docs.rs/anyhow/) crate can help you add " +#~ "contextual information to your errors and allows you to have fewer custom " +#~ "error types:" +#~ msgstr "" +#~ "广泛使用的 [anyhow](https://docs.rs/anyhow/) crate 可以帮助我们为错误添加 " +#~ "背景信息，并减少自定义错误类型的 数量。" + +#~ msgid "Mark unit tests with `#[test]`:" +#~ msgstr "使用 `#[test]` 标记单元测试：" + +#~ msgid "Use `cargo test` to find and run the unit tests." +#~ msgstr "使用 `cargo test` 查找并运行单元测试。" + +#~ msgid "" +#~ "Unit tests are often put in a nested module (run tests on the [Playground]" +#~ "(https://play.rust-lang.org/)):" +#~ msgstr "" +#~ "单元测试通常会放在嵌套模块中（在 [Playground](https://play.rust-lang." +#~ "org/) 上运行测试）：" + +#~ msgid "Useful crates for writing tests" +#~ msgstr "用于编写测试的实用 crate" + +#~ msgid "Calling External Code" +#~ msgstr "调用外部代码" + +#~ msgid "" +#~ "Functions from other languages might violate the guarantees of Rust. " +#~ "Calling them is thus unsafe:" +#~ msgstr "" +#~ "基于其他语言的函数可能会违反 Rust 的保证。因此， 调用这类函数是不安全的：" + +#~ msgid "Day 3: Afternoon Exercises" +#~ msgstr "第 3 天：下午练习" + +#~ msgid "Let us build a safe wrapper for reading directory content!" +#~ msgstr "让我们构建一个用于读取目录内容的安全封装容器！" + +#~ msgid "" +#~ "For this exercise, we suggest using a local dev environment instead of " +#~ "the Playground. This will allow you to run your binary on your own " +#~ "machine." +#~ msgstr "" +#~ "在本练习中，我们建议您使用本地开发环境，而不是 Playground。这样，您就可以" +#~ "在自己的机器上运行二进制文件。" + +#~ msgid "" +#~ "To get started, follow the [running locally](../../cargo/running-locally." +#~ "md) instructions." +#~ msgstr "" +#~ "首先，请按照[在本地运行](../../cargo/running-locally.md)中的说明操作。" + +#~ msgid "" +#~ "After looking at the exercise, you can look at the [solution](solutions-" +#~ "afternoon.md) provided." +#~ msgstr "看过练习后，您可以查看所提供的[解题方法](solutions-afternoon.md)。" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust\",\n" +#~ " crate_name: \"hello_rust\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust\",\n" +#~ " crate_name: \"hello_rust\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust\n" +#~ "//! Rust demo.\n" +#~ "\n" +#~ "/// Prints a greeting to standard output.\n" +#~ "fn main() {\n" +#~ " println!(\"Hello from Rust!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust\n" +#~ "//! Rust demo.\n" +#~ "\n" +#~ "/// Prints a greeting to standard output.\n" +#~ "fn main() {\n" +#~ " println!(\"Hello from Rust!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust_with_dep\",\n" +#~ " crate_name: \"hello_rust_with_dep\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"libgreetings\",\n" +#~ " \"libtextwrap\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "\n" +#~ "rust_library {\n" +#~ " name: \"libgreetings\",\n" +#~ " crate_name: \"greetings\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust_with_dep\",\n" +#~ " crate_name: \"hello_rust_with_dep\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"libgreetings\",\n" +#~ " \"libtextwrap\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "\n" +#~ "rust_library {\n" +#~ " name: \"libgreetings\",\n" +#~ " crate_name: \"greetings\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Rust demo.\n" +#~ "\n" +#~ "use greetings::greeting;\n" +#~ "use textwrap::fill;\n" +#~ "\n" +#~ "/// Prints a greeting to standard output.\n" +#~ "fn main() {\n" +#~ " println!(\"{}\", fill(&greeting(\"Bob\"), 24));\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! Rust demo.\n" +#~ "\n" +#~ "use greetings::greeting;\n" +#~ "use textwrap::fill;\n" +#~ "\n" +#~ "/// Prints a greeting to standard output.\n" +#~ "fn main() {\n" +#~ " println!(\"{}\", fill(&greeting(\"Bob\"), 24));\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Greeting library.\n" +#~ "\n" +#~ "/// Greet `name`.\n" +#~ "pub fn greeting(name: &str) -> String {\n" +#~ " format!(\"Hello {name}, it is very nice to meet you!\")\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! Greeting library.\n" +#~ "\n" +#~ "/// Greet `name`.\n" +#~ "pub fn greeting(name: &str) -> String {\n" +#~ " format!(\"Hello {name}, it is very nice to meet you!\")\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "aidl_interface {\n" +#~ " name: \"com.example.birthdayservice\",\n" +#~ " srcs: [\"com/example/birthdayservice/*.aidl\"],\n" +#~ " unstable: true,\n" +#~ " backend: {\n" +#~ " rust: { // Rust is not enabled by default\n" +#~ " enabled: true,\n" +#~ " },\n" +#~ " },\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "aidl_interface {\n" +#~ " name: \"com.example.birthdayservice\",\n" +#~ " srcs: [\"com/example/birthdayservice/*.aidl\"],\n" +#~ " unstable: true,\n" +#~ " backend: {\n" +#~ " rust: { // 默认情况下不启用 Rust \n" +#~ " enabled: true,\n" +#~ " },\n" +#~ " },\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Implementation of the `IBirthdayService` AIDL interface.\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::IBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "/// The `IBirthdayService` implementation.\n" +#~ "pub struct BirthdayService;\n" +#~ "\n" +#~ "impl binder::Interface for BirthdayService {}\n" +#~ "\n" +#~ "impl IBirthdayService for BirthdayService {\n" +#~ " fn wishHappyBirthday(&self, name: &str, years: i32) -> binder::" +#~ "Result {\n" +#~ " Ok(format!(\n" +#~ " \"Happy Birthday {name}, congratulations with the {years} " +#~ "years!\"\n" +#~ " ))\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! 实现了 `IBirthdayService` AIDL 接口。\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::IBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "/// `IBirthdayService` 接口的具体实现。\n" +#~ "pub struct BirthdayService;\n" +#~ "\n" +#~ "impl binder::Interface for BirthdayService {}\n" +#~ "\n" +#~ "impl IBirthdayService for BirthdayService {\n" +#~ " fn wishHappyBirthday(&self, name: &str, years: i32) -> binder::" +#~ "Result {\n" +#~ " Ok(format!(\n" +#~ " \"Happy Birthday {name}, congratulations with the {years} " +#~ "years!\"\n" +#~ " ))\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_library {\n" +#~ " name: \"libbirthdayservice\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ " crate_name: \"birthdayservice\",\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " ],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_library {\n" +#~ " name: \"libbirthdayservice\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ " crate_name: \"birthdayservice\",\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " ],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Birthday service.\n" +#~ "use birthdayservice::BirthdayService;\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::BnBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" +#~ "\n" +#~ "/// Entry point for birthday service.\n" +#~ "fn main() {\n" +#~ " let birthday_service = BirthdayService;\n" +#~ " let birthday_service_binder = BnBirthdayService::new_binder(\n" +#~ " birthday_service,\n" +#~ " binder::BinderFeatures::default(),\n" +#~ " );\n" +#~ " binder::add_service(SERVICE_IDENTIFIER, birthday_service_binder." +#~ "as_binder())\n" +#~ " .expect(\"Failed to register service\");\n" +#~ " binder::ProcessState::join_thread_pool()\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! 生日服务。\n" +#~ "use birthdayservice::BirthdayService;\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::BnBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" +#~ "\n" +#~ "/// 生日服务的入口。\n" +#~ "fn main() {\n" +#~ " let birthday_service = BirthdayService;\n" +#~ " let birthday_service_binder = BnBirthdayService::new_binder(\n" +#~ " birthday_service,\n" +#~ " binder::BinderFeatures::default(),\n" +#~ " );\n" +#~ " binder::add_service(SERVICE_IDENTIFIER, birthday_service_binder." +#~ "as_binder())\n" +#~ " .expect(\"Failed to register service\");\n" +#~ " binder::ProcessState::join_thread_pool()\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"birthday_server\",\n" +#~ " crate_name: \"birthday_server\",\n" +#~ " srcs: [\"src/server.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " \"libbirthdayservice\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"birthday_server\",\n" +#~ " crate_name: \"birthday_server\",\n" +#~ " srcs: [\"src/server.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " \"libbirthdayservice\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Birthday service.\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::IBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" +#~ "\n" +#~ "/// Connect to the BirthdayService.\n" +#~ "pub fn connect() -> Result, binder::" +#~ "StatusCode> {\n" +#~ " binder::get_interface(SERVICE_IDENTIFIER)\n" +#~ "}\n" +#~ "\n" +#~ "/// Call the birthday service.\n" +#~ "fn main() -> Result<(), binder::Status> {\n" +#~ " let name = std::env::args()\n" +#~ " .nth(1)\n" +#~ " .unwrap_or_else(|| String::from(\"Bob\"));\n" +#~ " let years = std::env::args()\n" +#~ " .nth(2)\n" +#~ " .and_then(|arg| arg.parse::().ok())\n" +#~ " .unwrap_or(42);\n" +#~ "\n" +#~ " binder::ProcessState::start_thread_pool();\n" +#~ " let service = connect().expect(\"Failed to connect to " +#~ "BirthdayService\");\n" +#~ " let msg = service.wishHappyBirthday(&name, years)?;\n" +#~ " println!(\"{msg}\");\n" +#~ " Ok(())\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! 生日服务。\n" +#~ "use com_example_birthdayservice::aidl::com::example::birthdayservice::" +#~ "IBirthdayService::IBirthdayService;\n" +#~ "use com_example_birthdayservice::binder;\n" +#~ "\n" +#~ "const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" +#~ "\n" +#~ "/// 连接到 BirthdayService。\n" +#~ "pub fn connect() -> Result, binder::" +#~ "StatusCode> {\n" +#~ " binder::get_interface(SERVICE_IDENTIFIER)\n" +#~ "}\n" +#~ "\n" +#~ "/// 调用生日服务。\n" +#~ "fn main() -> Result<(), binder::Status> {\n" +#~ " let name = std::env::args()\n" +#~ " .nth(1)\n" +#~ " .unwrap_or_else(|| String::from(\"Bob\"));\n" +#~ " let years = std::env::args()\n" +#~ " .nth(2)\n" +#~ " .and_then(|arg| arg.parse::().ok())\n" +#~ " .unwrap_or(42);\n" +#~ "\n" +#~ " binder::ProcessState::start_thread_pool();\n" +#~ " let service = connect().expect(\"Failed to connect to " +#~ "BirthdayService\");\n" +#~ " let msg = service.wishHappyBirthday(&name, years)?;\n" +#~ " println!(\"{msg}\");\n" +#~ " Ok(())\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"birthday_client\",\n" +#~ " crate_name: \"birthday_client\",\n" +#~ " srcs: [\"src/client.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"birthday_client\",\n" +#~ " crate_name: \"birthday_client\",\n" +#~ " srcs: [\"src/client.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"com.example.birthdayservice-rust\",\n" +#~ " \"libbinder_rs\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust_logs\",\n" +#~ " crate_name: \"hello_rust_logs\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"liblog_rust\",\n" +#~ " \"liblogger\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ " host_supported: true,\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"hello_rust_logs\",\n" +#~ " crate_name: \"hello_rust_logs\",\n" +#~ " srcs: [\"src/main.rs\"],\n" +#~ " rustlibs: [\n" +#~ " \"liblog_rust\",\n" +#~ " \"liblogger\",\n" +#~ " ],\n" +#~ " prefer_rlib: true,\n" +#~ " host_supported: true,\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,ignore\n" +#~ "//! Rust logging demo.\n" +#~ "\n" +#~ "use log::{debug, error, info};\n" +#~ "\n" +#~ "/// Logs a greeting.\n" +#~ "fn main() {\n" +#~ " logger::init(\n" +#~ " logger::Config::default()\n" +#~ " .with_tag_on_device(\"rust\")\n" +#~ " .with_min_level(log::Level::Trace),\n" +#~ " );\n" +#~ " debug!(\"Starting program.\");\n" +#~ " info!(\"Things are going fine.\");\n" +#~ " error!(\"Something went wrong!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,ignore\n" +#~ "//! Rust logging demo.\n" +#~ "\n" +#~ "use log::{debug, error, info};\n" +#~ "\n" +#~ "/// Logs a greeting.\n" +#~ "fn main() {\n" +#~ " logger::init(\n" +#~ " logger::Config::default()\n" +#~ " .with_tag_on_device(\"rust\")\n" +#~ " .with_min_level(log::Level::Trace),\n" +#~ " );\n" +#~ " debug!(\"Starting program.\");\n" +#~ " info!(\"Things are going fine.\");\n" +#~ " error!(\"Something went wrong!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust\n" +#~ "extern \"C\" {\n" +#~ " fn abs(x: i32) -> i32;\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let x = -42;\n" +#~ " let abs_x = unsafe { abs(x) };\n" +#~ " println!(\"{x}, {abs_x}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust\n" +#~ "extern \"C\" {\n" +#~ " fn abs(x: i32) -> i32;\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let x = -42;\n" +#~ " let abs_x = unsafe { abs(x) };\n" +#~ " println!(\"{x}, {abs_x}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```c\n" +#~ "#include \n" +#~ "#include \"libbirthday.h\"\n" +#~ "\n" +#~ "void print_card(const card* card) {\n" +#~ " printf(\"+--------------\\n\");\n" +#~ " printf(\"| Happy Birthday %s!\\n\", card->name);\n" +#~ " printf(\"| Congratulations with the %i years!\\n\", card->years);\n" +#~ " printf(\"+--------------\\n\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```c\n" +#~ "#include \n" +#~ "#include \"libbirthday.h\"\n" +#~ "\n" +#~ "void print_card(const card* card) {\n" +#~ " printf(\"+--------------\\n\");\n" +#~ " printf(\"| Happy Birthday %s!\\n\", card->name);\n" +#~ " printf(\"| Congratulations with the %i years!\\n\", card->years);\n" +#~ " printf(\"+--------------\\n\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "cc_library {\n" +#~ " name: \"libbirthday\",\n" +#~ " srcs: [\"libbirthday.c\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "cc_library {\n" +#~ " name: \"libbirthday\",\n" +#~ " srcs: [\"libbirthday.c\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_bindgen {\n" +#~ " name: \"libbirthday_bindgen\",\n" +#~ " crate_name: \"birthday_bindgen\",\n" +#~ " wrapper_src: \"libbirthday_wrapper.h\",\n" +#~ " source_stem: \"bindings\",\n" +#~ " static_libs: [\"libbirthday\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_bindgen {\n" +#~ " name: \"libbirthday_bindgen\",\n" +#~ " crate_name: \"birthday_bindgen\",\n" +#~ " wrapper_src: \"libbirthday_wrapper.h\",\n" +#~ " source_stem: \"bindings\",\n" +#~ " static_libs: [\"libbirthday\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"print_birthday_card\",\n" +#~ " srcs: [\"main.rs\"],\n" +#~ " rustlibs: [\"libbirthday_bindgen\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_binary {\n" +#~ " name: \"print_birthday_card\",\n" +#~ " srcs: [\"main.rs\"],\n" +#~ " rustlibs: [\"libbirthday_bindgen\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,compile_fail\n" +#~ "//! Bindgen demo.\n" +#~ "\n" +#~ "use birthday_bindgen::{card, print_card};\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let name = std::ffi::CString::new(\"Peter\").unwrap();\n" +#~ " let card = card {\n" +#~ " name: name.as_ptr(),\n" +#~ " years: 42,\n" +#~ " };\n" +#~ " unsafe {\n" +#~ " print_card(&card as *const card);\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,compile_fail\n" +#~ "//! Bindgen demo.\n" +#~ "\n" +#~ "use birthday_bindgen::{card, print_card};\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let name = std::ffi::CString::new(\"Peter\").unwrap();\n" +#~ " let card = card {\n" +#~ " name: name.as_ptr(),\n" +#~ " years: 42,\n" +#~ " };\n" +#~ " unsafe {\n" +#~ " print_card(&card as *const card);\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_test {\n" +#~ " name: \"libbirthday_bindgen_test\",\n" +#~ " srcs: [\":libbirthday_bindgen\"],\n" +#~ " crate_name: \"libbirthday_bindgen_test\",\n" +#~ " test_suites: [\"general-tests\"],\n" +#~ " auto_gen_config: true,\n" +#~ " clippy_lints: \"none\", // Generated file, skip linting\n" +#~ " lints: \"none\",\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_test {\n" +#~ " name: \"libbirthday_bindgen_test\",\n" +#~ " srcs: [\":libbirthday_bindgen\"],\n" +#~ " crate_name: \"libbirthday_bindgen_test\",\n" +#~ " test_suites: [\"general-tests\"],\n" +#~ " auto_gen_config: true,\n" +#~ " clippy_lints: \"none\", // Generated file, skip linting\n" +#~ " lints: \"none\",\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "//! Rust FFI demo.\n" +#~ "#![deny(improper_ctypes_definitions)]\n" +#~ "\n" +#~ "use std::os::raw::c_int;\n" +#~ "\n" +#~ "/// Analyze the numbers.\n" +#~ "#[no_mangle]\n" +#~ "pub extern \"C\" fn analyze_numbers(x: c_int, y: c_int) {\n" +#~ " if x < y {\n" +#~ " println!(\"x ({x}) is smallest!\");\n" +#~ " } else {\n" +#~ " println!(\"y ({y}) is probably larger than x ({x})\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "//! Rust FFI demo.\n" +#~ "#![deny(improper_ctypes_definitions)]\n" +#~ "\n" +#~ "use std::os::raw::c_int;\n" +#~ "\n" +#~ "/// Analyze the numbers.\n" +#~ "#[no_mangle]\n" +#~ "pub extern \"C\" fn analyze_numbers(x: c_int, y: c_int) {\n" +#~ " if x < y {\n" +#~ " println!(\"x ({x}) is smallest!\");\n" +#~ " } else {\n" +#~ " println!(\"y ({y}) is probably larger than x ({x})\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```c\n" +#~ "#ifndef ANALYSE_H\n" +#~ "#define ANALYSE_H\n" +#~ "\n" +#~ "extern \"C\" {\n" +#~ "void analyze_numbers(int x, int y);\n" +#~ "}\n" +#~ "\n" +#~ "#endif\n" +#~ "```" +#~ msgstr "" +#~ "```c\n" +#~ "#ifndef ANALYSE_H\n" +#~ "#define ANALYSE_H\n" +#~ "\n" +#~ "extern \"C\" {\n" +#~ "void analyze_numbers(int x, int y);\n" +#~ "}\n" +#~ "\n" +#~ "#endif\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_ffi {\n" +#~ " name: \"libanalyze_ffi\",\n" +#~ " crate_name: \"analyze_ffi\",\n" +#~ " srcs: [\"analyze.rs\"],\n" +#~ " include_dirs: [\".\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_ffi {\n" +#~ " name: \"libanalyze_ffi\",\n" +#~ " crate_name: \"analyze_ffi\",\n" +#~ " srcs: [\"analyze.rs\"],\n" +#~ " include_dirs: [\".\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```c\n" +#~ "#include \"analyze.h\"\n" +#~ "\n" +#~ "int main() {\n" +#~ " analyze_numbers(10, 20);\n" +#~ " analyze_numbers(123, 123);\n" +#~ " return 0;\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```c\n" +#~ "#include \"analyze.h\"\n" +#~ "\n" +#~ "int main() {\n" +#~ " analyze_numbers(10, 20);\n" +#~ " analyze_numbers(123, 123);\n" +#~ " return 0;\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "cc_binary {\n" +#~ " name: \"analyze_numbers\",\n" +#~ " srcs: [\"main.c\"],\n" +#~ " static_libs: [\"libanalyze_ffi\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "cc_binary {\n" +#~ " name: \"analyze_numbers\",\n" +#~ " srcs: [\"main.c\"],\n" +#~ " static_libs: [\"libanalyze_ffi\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "At this point, the instructor should switch to the [CXX tutorial](https://" +#~ "cxx.rs/tutorial.html)." +#~ msgstr "" +#~ "此时，讲师应该该切换到 [CXX tutorial](https://cxx.rs/tutorial.html)。" + +#~ msgid "Walk the students through the tutorial step by step." +#~ msgstr "逐步引导学生按照教程一步步操作。" + +#~ msgid "" +#~ "Highlight how CXX presents a clean interface without unsafe code in _both " +#~ "languages_." +#~ msgstr "突出展示 CXX 在 _两种语言_ 中都提供了一个没有不安全代码的干净接口。" + +#~ msgid "" +#~ "Explain how a Rust `String` cannot map to a C++ `std::string` (the latter " +#~ "does not uphold the UTF-8 invariant). Show that despite being different " +#~ "types, `rust::String` in C++ can be easily constructed from a C++ `std::" +#~ "string`, making it very ergonomic to use." +#~ msgstr "" +#~ "解释 Rust 的 `String` 无法直接映射到 C++ 的 `std::string `（后者不符合" +#~ "UTF-8不变性）。展示尽管类型不同，但在 C++ 中，可以很容易地从 C++ 的 `std::" +#~ "string` 构造 `rust::String` ，使得使用起来非常方便。" + +#~ msgid "" +#~ "Explain that a Rust function returning `Result` becomes a function " +#~ "which throws a `E` exception in C++ (and vice versa)." +#~ msgstr "" +#~ "解释 Rust 中返回 `Result ` 的函数在 C++ 中会变成抛出 `E` 异常的函数" +#~ "（反之亦然）。" + +#~ msgid "" +#~ "```rust,compile_fail\n" +#~ "//! Rust <-> Java FFI demo.\n" +#~ "\n" +#~ "use jni::objects::{JClass, JString};\n" +#~ "use jni::sys::jstring;\n" +#~ "use jni::JNIEnv;\n" +#~ "\n" +#~ "/// HelloWorld::hello method implementation.\n" +#~ "#[no_mangle]\n" +#~ "pub extern \"system\" fn Java_HelloWorld_hello(\n" +#~ " env: JNIEnv,\n" +#~ " _class: JClass,\n" +#~ " name: JString,\n" +#~ ") -> jstring {\n" +#~ " let input: String = env.get_string(name).unwrap().into();\n" +#~ " let greeting = format!(\"Hello, {input}!\");\n" +#~ " let output = env.new_string(greeting).unwrap();\n" +#~ " output.into_inner()\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,compile_fail\n" +#~ "//! Rust <-> Java FFI demo.\n" +#~ "\n" +#~ "use jni::objects::{JClass, JString};\n" +#~ "use jni::sys::jstring;\n" +#~ "use jni::JNIEnv;\n" +#~ "\n" +#~ "/// HelloWorld::hello method implementation.\n" +#~ "#[no_mangle]\n" +#~ "pub extern \"system\" fn Java_HelloWorld_hello(\n" +#~ " env: JNIEnv,\n" +#~ " _class: JClass,\n" +#~ " name: JString,\n" +#~ ") -> jstring {\n" +#~ " let input: String = env.get_string(name).unwrap().into();\n" +#~ " let greeting = format!(\"Hello, {input}!\");\n" +#~ " let output = env.new_string(greeting).unwrap();\n" +#~ " output.into_inner()\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "rust_ffi_shared {\n" +#~ " name: \"libhello_jni\",\n" +#~ " crate_name: \"hello_jni\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ " rustlibs: [\"libjni\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "rust_ffi_shared {\n" +#~ " name: \"libhello_jni\",\n" +#~ " crate_name: \"hello_jni\",\n" +#~ " srcs: [\"src/lib.rs\"],\n" +#~ " rustlibs: [\"libjni\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```java\n" +#~ "class HelloWorld {\n" +#~ " private static native String hello(String name);\n" +#~ "\n" +#~ " static {\n" +#~ " System.loadLibrary(\"hello_jni\");\n" +#~ " }\n" +#~ "\n" +#~ " public static void main(String[] args) {\n" +#~ " String output = HelloWorld.hello(\"Alice\");\n" +#~ " System.out.println(output);\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```java\n" +#~ "class HelloWorld {\n" +#~ " private static native String hello(String name);\n" +#~ "\n" +#~ " static {\n" +#~ " System.loadLibrary(\"hello_jni\");\n" +#~ " }\n" +#~ "\n" +#~ " public static void main(String[] args) {\n" +#~ " String output = HelloWorld.hello(\"Alice\");\n" +#~ " System.out.println(output);\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```javascript\n" +#~ "java_binary {\n" +#~ " name: \"helloworld_jni\",\n" +#~ " srcs: [\"HelloWorld.java\"],\n" +#~ " main_class: \"HelloWorld\",\n" +#~ " required: [\"libhello_jni\"],\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```javascript\n" +#~ "java_binary {\n" +#~ " name: \"helloworld_jni\",\n" +#~ " srcs: [\"HelloWorld.java\"],\n" +#~ " main_class: \"HelloWorld\",\n" +#~ " required: [\"libhello_jni\"],\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " thread::spawn(|| {\n" +#~ " for i in 1..10 {\n" +#~ " println!(\"Count in thread: {i}!\");\n" +#~ " thread::sleep(Duration::from_millis(5));\n" +#~ " }\n" +#~ " });\n" +#~ "\n" +#~ " for i in 1..5 {\n" +#~ " println!(\"Main thread: {i}\");\n" +#~ " thread::sleep(Duration::from_millis(5));\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " thread::spawn(|| {\n" +#~ " for i in 1..10 {\n" +#~ " println!(\"Count in thread: {i}!\");\n" +#~ " thread::sleep(Duration::from_millis(5));\n" +#~ " }\n" +#~ " });\n" +#~ "\n" +#~ " for i in 1..5 {\n" +#~ " println!(\"Main thread: {i}\");\n" +#~ " thread::sleep(Duration::from_millis(5));\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable,compile_fail\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn foo() {\n" +#~ " let s = String::from(\"Hello\");\n" +#~ " thread::spawn(|| {\n" +#~ " println!(\"Length: {}\", s.len());\n" +#~ " });\n" +#~ "}\n" +#~ "\n" +#~ "fn main() {\n" +#~ " foo();\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable,compile_fail\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let s = String::from(\"Hello\");\n" +#~ "\n" +#~ " thread::spawn(|| {\n" +#~ " println!(\"Length: {}\", s.len());\n" +#~ " });\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let s = String::from(\"Hello\");\n" +#~ "\n" +#~ " thread::scope(|scope| {\n" +#~ " scope.spawn(|| {\n" +#~ " println!(\"Length: {}\", s.len());\n" +#~ " });\n" +#~ " });\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let s = String::from(\"Hello\");\n" +#~ "\n" +#~ " thread::scope(|scope| {\n" +#~ " scope.spawn(|| {\n" +#~ " println!(\"Length: {}\", s.len());\n" +#~ " });\n" +#~ " });\n" +#~ "}\n" +#~ "```" + +#, fuzzy +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::channel();\n" +#~ "\n" +#~ " tx.send(10).unwrap();\n" +#~ " tx.send(20).unwrap();\n" +#~ "\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ "\n" +#~ " let tx2 = tx.clone();\n" +#~ " tx2.send(30).unwrap();\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::channel();\n" +#~ "\n" +#~ " tx.send(10).unwrap();\n" +#~ " tx.send(20).unwrap();\n" +#~ "\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ "\n" +#~ " let tx2 = tx.clone();\n" +#~ " tx2.send(30).unwrap();\n" +#~ " println!(\"Received: {:?}\", rx.recv());\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::channel();\n" +#~ "\n" +#~ " thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " for i in 1..10 {\n" +#~ " tx.send(format!(\"Message {i}\")).unwrap();\n" +#~ " println!(\"{thread_id:?}: sent Message {i}\");\n" +#~ " }\n" +#~ " println!(\"{thread_id:?}: done\");\n" +#~ " });\n" +#~ " thread::sleep(Duration::from_millis(100));\n" +#~ "\n" +#~ " for msg in rx.iter() {\n" +#~ " println!(\"Main: got {msg}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::channel();\n" +#~ "\n" +#~ " thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " for i in 1..10 {\n" +#~ " tx.send(format!(\"Message {i}\")).unwrap();\n" +#~ " println!(\"{thread_id:?}: sent Message {i}\");\n" +#~ " }\n" +#~ " println!(\"{thread_id:?}: done\");\n" +#~ " });\n" +#~ " thread::sleep(Duration::from_millis(100));\n" +#~ "\n" +#~ " for msg in rx.iter() {\n" +#~ " println!(\"Main: got {msg}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::sync_channel(3);\n" +#~ "\n" +#~ " thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " for i in 1..10 {\n" +#~ " tx.send(format!(\"Message {i}\")).unwrap();\n" +#~ " println!(\"{thread_id:?}: sent Message {i}\");\n" +#~ " }\n" +#~ " println!(\"{thread_id:?}: done\");\n" +#~ " });\n" +#~ " thread::sleep(Duration::from_millis(100));\n" +#~ "\n" +#~ " for msg in rx.iter() {\n" +#~ " println!(\"Main: got {msg}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::sync::mpsc;\n" +#~ "use std::thread;\n" +#~ "use std::time::Duration;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let (tx, rx) = mpsc::sync_channel(3);\n" +#~ "\n" +#~ " thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " for i in 1..10 {\n" +#~ " tx.send(format!(\"Message {i}\")).unwrap();\n" +#~ " println!(\"{thread_id:?}: sent Message {i}\");\n" +#~ " }\n" +#~ " println!(\"{thread_id:?}: done\");\n" +#~ " });\n" +#~ " thread::sleep(Duration::from_millis(100));\n" +#~ "\n" +#~ " for msg in rx.iter() {\n" +#~ " println!(\"Main: got {msg}\");\n" +#~ " }\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "use std::sync::Arc;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Arc::new(vec![10, 20, 30]);\n" +#~ " let mut handles = Vec::new();\n" +#~ " for _ in 1..5 {\n" +#~ " let v = Arc::clone(&v);\n" +#~ " handles.push(thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " println!(\"{thread_id:?}: {v:?}\");\n" +#~ " }));\n" +#~ " }\n" +#~ "\n" +#~ " handles.into_iter().for_each(|h| h.join().unwrap());\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::thread;\n" +#~ "use std::sync::Arc;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Arc::new(vec![10, 20, 30]);\n" +#~ " let mut handles = Vec::new();\n" +#~ " for _ in 1..5 {\n" +#~ " let v = Arc::clone(&v);\n" +#~ " handles.push(thread::spawn(move || {\n" +#~ " let thread_id = thread::current().id();\n" +#~ " println!(\"{thread_id:?}: {v:?}\");\n" +#~ " }));\n" +#~ " }\n" +#~ "\n" +#~ " handles.into_iter().for_each(|h| h.join().unwrap());\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::sync::Mutex;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Mutex::new(vec![10, 20, 30]);\n" +#~ " println!(\"v: {:?}\", v.lock().unwrap());\n" +#~ "\n" +#~ " {\n" +#~ " let mut guard = v.lock().unwrap();\n" +#~ " guard.push(40);\n" +#~ " }\n" +#~ "\n" +#~ " println!(\"v: {:?}\", v.lock().unwrap());\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::sync::Mutex;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Mutex::new(vec![10, 20, 30]);\n" +#~ " println!(\"v: {:?}\", v.lock().unwrap());\n" +#~ "\n" +#~ " {\n" +#~ " let mut guard = v.lock().unwrap();\n" +#~ " guard.push(40);\n" +#~ " }\n" +#~ "\n" +#~ " println!(\"v: {:?}\", v.lock().unwrap());\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable,compile_fail\n" +#~ "use std::thread;\n" +#~ "// use std::sync::{Arc, Mutex};\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = vec![10, 20, 30];\n" +#~ " let handle = thread::spawn(|| {\n" +#~ " v.push(10);\n" +#~ " });\n" +#~ " v.push(1000);\n" +#~ "\n" +#~ " handle.join().unwrap();\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable,compile_fail\n" +#~ "use std::thread;\n" +#~ "// use std::sync::{Arc, Mutex};\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = vec![10, 20, 30];\n" +#~ " let handle = thread::spawn(|| {\n" +#~ " v.push(10);\n" +#~ " });\n" +#~ " v.push(1000);\n" +#~ "\n" +#~ " handle.join().unwrap();\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust,editable\n" +#~ "use std::sync::{Arc, Mutex};\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Arc::new(Mutex::new(vec![10, 20, 30]));\n" +#~ "\n" +#~ " let v2 = Arc::clone(&v);\n" +#~ " let handle = thread::spawn(move || {\n" +#~ " let mut v2 = v2.lock().unwrap();\n" +#~ " v2.push(10);\n" +#~ " });\n" +#~ "\n" +#~ " {\n" +#~ " let mut v = v.lock().unwrap();\n" +#~ " v.push(1000);\n" +#~ " }\n" +#~ "\n" +#~ " handle.join().unwrap();\n" +#~ "\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "use std::sync::{Arc, Mutex};\n" +#~ "use std::thread;\n" +#~ "\n" +#~ "fn main() {\n" +#~ " let v = Arc::new(Mutex::new(vec![10, 20, 30]));\n" +#~ "\n" +#~ " let v2 = Arc::clone(&v);\n" +#~ " let handle = thread::spawn(move || {\n" +#~ " let mut v2 = v2.lock().unwrap();\n" +#~ " v2.push(10);\n" +#~ " });\n" +#~ "\n" +#~ " {\n" +#~ " let mut v = v.lock().unwrap();\n" +#~ " v.push(1000);\n" +#~ " }\n" +#~ "\n" +#~ " handle.join().unwrap();\n" +#~ "\n" +#~ " println!(\"v: {v:?}\");\n" +#~ "}\n" +#~ "```" + +#, fuzzy +#~ msgid "concurrency:" +#~ msgstr "并发" + +#, fuzzy +#~ msgid "constant:" +#~ msgstr "`const`" + +#, fuzzy +#~ msgid "control flow:" +#~ msgstr "控制流" + +#, fuzzy +#~ msgid "enumeration:" +#~ msgstr "实现" -#: src/exercises/bare-metal/solutions-morning.md:1 -msgid "Bare Metal Rust Morning Exercise" -msgstr "裸机 Rust 上午练习" +#, fuzzy +#~ msgid "error handling:" +#~ msgstr "错误处理" -#: src/exercises/bare-metal/solutions-morning.md:5 -msgid "([back to exercise](compass.md))" -msgstr "([返回练习](compass.md))" +#, fuzzy +#~ msgid "garbage collector:" +#~ msgstr "垃圾回收" -#: src/exercises/bare-metal/solutions-morning.md:7 -msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use core::fmt::Write;\n" -"use cortex_m_rt::entry;\n" -"use core::cmp::{max, min};\n" -"use lsm303agr::{AccelOutputDataRate, Lsm303agr, MagOutputDataRate};\n" -"use microbit::display::blocking::Display;\n" -"use microbit::hal::prelude::*;\n" -"use microbit::hal::twim::Twim;\n" -"use microbit::hal::uarte::{Baudrate, Parity, Uarte};\n" -"use microbit::hal::Timer;\n" -"use microbit::pac::twim0::frequency::FREQUENCY_A;\n" -"use microbit::Board;\n" -"\n" -"const COMPASS_SCALE: i32 = 30000;\n" -"const ACCELEROMETER_SCALE: i32 = 700;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let board = Board::take().unwrap();\n" -"\n" -" // Configure serial port.\n" -" let mut serial = Uarte::new(\n" -" board.UARTE0,\n" -" board.uart.into(),\n" -" Parity::EXCLUDED,\n" -" Baudrate::BAUD115200,\n" -" );\n" -"\n" -" // Set up the I2C controller and Inertial Measurement Unit.\n" -" writeln!(serial, \"Setting up IMU...\").unwrap();\n" -" let i2c = Twim::new(board.TWIM0, board.i2c_internal.into(), FREQUENCY_A::" -"K100);\n" -" let mut imu = Lsm303agr::new_with_i2c(i2c);\n" -" imu.init().unwrap();\n" -" imu.set_mag_odr(MagOutputDataRate::Hz50).unwrap();\n" -" imu.set_accel_odr(AccelOutputDataRate::Hz50).unwrap();\n" -" let mut imu = imu.into_mag_continuous().ok().unwrap();\n" -"\n" -" // Set up display and timer.\n" -" let mut timer = Timer::new(board.TIMER0);\n" -" let mut display = Display::new(board.display_pins);\n" -"\n" -" let mut mode = Mode::Compass;\n" -" let mut button_pressed = false;\n" -"\n" -" writeln!(serial, \"Ready.\").unwrap();\n" -"\n" -" loop {\n" -" // Read compass data and log it to the serial port.\n" -" while !(imu.mag_status().unwrap().xyz_new_data\n" -" && imu.accel_status().unwrap().xyz_new_data)\n" -" {}\n" -" let compass_reading = imu.mag_data().unwrap();\n" -" let accelerometer_reading = imu.accel_data().unwrap();\n" -" writeln!(\n" -" serial,\n" -" \"{},{},{}\\t{},{},{}\",\n" -" compass_reading.x,\n" -" compass_reading.y,\n" -" compass_reading.z,\n" -" accelerometer_reading.x,\n" -" accelerometer_reading.y,\n" -" accelerometer_reading.z,\n" -" )\n" -" .unwrap();\n" -"\n" -" let mut image = [[0; 5]; 5];\n" -" let (x, y) = match mode {\n" -" Mode::Compass => (\n" -" scale(-compass_reading.x, -COMPASS_SCALE, COMPASS_SCALE, 0, " -"4) as usize,\n" -" scale(compass_reading.y, -COMPASS_SCALE, COMPASS_SCALE, 0, " -"4) as usize,\n" -" ),\n" -" Mode::Accelerometer => (\n" -" scale(\n" -" accelerometer_reading.x,\n" -" -ACCELEROMETER_SCALE,\n" -" ACCELEROMETER_SCALE,\n" -" 0,\n" -" 4,\n" -" ) as usize,\n" -" scale(\n" -" -accelerometer_reading.y,\n" -" -ACCELEROMETER_SCALE,\n" -" ACCELEROMETER_SCALE,\n" -" 0,\n" -" 4,\n" -" ) as usize,\n" -" ),\n" -" };\n" -" image[y][x] = 255;\n" -" display.show(&mut timer, image, 100);\n" -"\n" -" // If button A is pressed, switch to the next mode and briefly blink " -"all LEDs on.\n" -" if board.buttons.button_a.is_low().unwrap() {\n" -" if !button_pressed {\n" -" mode = mode.next();\n" -" display.show(&mut timer, [[255; 5]; 5], 200);\n" -" }\n" -" button_pressed = true;\n" -" } else {\n" -" button_pressed = false;\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -"enum Mode {\n" -" Compass,\n" -" Accelerometer,\n" -"}\n" -"\n" -"impl Mode {\n" -" fn next(self) -> Self {\n" -" match self {\n" -" Self::Compass => Self::Accelerometer,\n" -" Self::Accelerometer => Self::Compass,\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn scale(value: i32, min_in: i32, max_in: i32, min_out: i32, max_out: i32) -" -"> i32 {\n" -" let range_in = max_in - min_in;\n" -" let range_out = max_out - min_out;\n" -" cap(\n" -" min_out + range_out * (value - min_in) / range_in,\n" -" min_out,\n" -" max_out,\n" -" )\n" -"}\n" -"\n" -"fn cap(value: i32, min_value: i32, max_value: i32) -> i32 {\n" -" max(min_value, min(value, max_value))\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "generics:" +#~ msgstr "泛型" -#: src/exercises/bare-metal/solutions-afternoon.md:5 -msgid "([back to exercise](rtc.md))" -msgstr "([返回练习](rtc.md))" +#, fuzzy +#~ msgid "integration test:" +#~ msgstr "集成测试" -#: src/exercises/bare-metal/solutions-afternoon.md:7 #, fuzzy -msgid "_main.rs_:" -msgstr "`main.rs`:" +#~ msgid "main function:" +#~ msgstr "调用 Unsafe 函数" -#: src/exercises/bare-metal/solutions-afternoon.md:9 -msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"mod pl031;\n" -"\n" -"use crate::pl031::Rtc;\n" -"use arm_gic::gicv3::{IntId, Trigger};\n" -"use arm_gic::{irq_enable, wfi};\n" -"use chrono::{TimeZone, Utc};\n" -"use core::hint::spin_loop;\n" -"use crate::pl011::Uart;\n" -"use arm_gic::gicv3::GicV3;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, trace, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base addresses of the GICv3.\n" -"const GICD_BASE_ADDRESS: *mut u64 = 0x800_0000 as _;\n" -"const GICR_BASE_ADDRESS: *mut u64 = 0x80A_0000 as _;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"/// Base address of the PL031 RTC.\n" -"const PL031_BASE_ADDRESS: *mut u32 = 0x901_0000 as _;\n" -"/// The IRQ used by the PL031 RTC.\n" -"const PL031_IRQ: IntId = IntId::spi(2);\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({:#x}, {:#x}, {:#x}, {:#x})\", x0, x1, x2, x3);\n" -"\n" -" // Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the " -"base\n" -" // addresses of a GICv3 distributor and redistributor respectively, and\n" -" // nothing else accesses those address ranges.\n" -" let mut gic = unsafe { GicV3::new(GICD_BASE_ADDRESS, " -"GICR_BASE_ADDRESS) };\n" -" gic.setup();\n" -"\n" -" // Safe because `PL031_BASE_ADDRESS` is the base address of a PL031 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let mut rtc = unsafe { Rtc::new(PL031_BASE_ADDRESS) };\n" -" let timestamp = rtc.read();\n" -" let time = Utc.timestamp_opt(timestamp.into(), 0).unwrap();\n" -" info!(\"RTC: {time}\");\n" -"\n" -" GicV3::set_priority_mask(0xff);\n" -" gic.set_interrupt_priority(PL031_IRQ, 0x80);\n" -" gic.set_trigger(PL031_IRQ, Trigger::Level);\n" -" irq_enable();\n" -" gic.enable_interrupt(PL031_IRQ, true);\n" -"\n" -" // Wait for 3 seconds, without interrupts.\n" -" let target = timestamp + 3;\n" -" rtc.set_match(target);\n" -" info!(\n" -" \"Waiting for {}\",\n" -" Utc.timestamp_opt(target.into(), 0).unwrap()\n" -" );\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" while !rtc.matched() {\n" -" spin_loop();\n" -" }\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" info!(\"Finished waiting\");\n" -"\n" -" // Wait another 3 seconds for an interrupt.\n" -" let target = timestamp + 6;\n" -" info!(\n" -" \"Waiting for {}\",\n" -" Utc.timestamp_opt(target.into(), 0).unwrap()\n" -" );\n" -" rtc.set_match(target);\n" -" rtc.clear_interrupt();\n" -" rtc.enable_interrupt(true);\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" while !rtc.interrupt_pending() {\n" -" wfi();\n" -" }\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" info!(\"Finished waiting\");\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "memory leak:" +#~ msgstr "内存泄漏。" -#: src/exercises/bare-metal/solutions-afternoon.md:127 -msgid "_pl031.rs_:" -msgstr "" +#, fuzzy +#~ msgid "method:" +#~ msgstr "方法" -#: src/exercises/bare-metal/solutions-afternoon.md:129 -msgid "" -"```rust\n" -"use core::ptr::{addr_of, addr_of_mut};\n" -"\n" -"#[repr(C, align(4))]\n" -"struct Registers {\n" -" /// Data register\n" -" dr: u32,\n" -" /// Match register\n" -" mr: u32,\n" -" /// Load register\n" -" lr: u32,\n" -" /// Control register\n" -" cr: u8,\n" -" _reserved0: [u8; 3],\n" -" /// Interrupt Mask Set or Clear register\n" -" imsc: u8,\n" -" _reserved1: [u8; 3],\n" -" /// Raw Interrupt Status\n" -" ris: u8,\n" -" _reserved2: [u8; 3],\n" -" /// Masked Interrupt Status\n" -" mis: u8,\n" -" _reserved3: [u8; 3],\n" -" /// Interrupt Clear Register\n" -" icr: u8,\n" -" _reserved4: [u8; 3],\n" -"}\n" -"\n" -"/// Driver for a PL031 real-time clock.\n" -"#[derive(Debug)]\n" -"pub struct Rtc {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Rtc {\n" -" /// Constructs a new instance of the RTC driver for a PL031 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the MMIO control registers of " -"a\n" -" /// PL031 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Reads the current RTC value.\n" -" pub fn read(&self) -> u32 {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).dr).read_volatile() }\n" -" }\n" -"\n" -" /// Writes a match value. When the RTC value matches this then an " -"interrupt\n" -" /// will be generated (if it is enabled).\n" -" pub fn set_match(&mut self, value: u32) {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).mr).write_volatile(value) }\n" -" }\n" -"\n" -" /// Returns whether the match register matches the RTC value, whether or " -"not\n" -" /// the interrupt is enabled.\n" -" pub fn matched(&self) -> bool {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" let ris = unsafe { addr_of!((*self.registers).ris)." -"read_volatile() };\n" -" (ris & 0x01) != 0\n" -" }\n" -"\n" -" /// Returns whether there is currently an interrupt pending.\n" -" ///\n" -" /// This should be true if and only if `matched` returns true and the\n" -" /// interrupt is masked.\n" -" pub fn interrupt_pending(&self) -> bool {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" let ris = unsafe { addr_of!((*self.registers).mis)." -"read_volatile() };\n" -" (ris & 0x01) != 0\n" -" }\n" -"\n" -" /// Sets or clears the interrupt mask.\n" -" ///\n" -" /// When the mask is true the interrupt is enabled; when it is false " -"the\n" -" /// interrupt is disabled.\n" -" pub fn enable_interrupt(&mut self, mask: bool) {\n" -" let imsc = if mask { 0x01 } else { 0x00 };\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).imsc)." -"write_volatile(imsc) }\n" -" }\n" -"\n" -" /// Clears a pending interrupt, if any.\n" -" pub fn clear_interrupt(&mut self) {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).icr).write_volatile(0x01) }\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Rtc {}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "module:" +#~ msgstr "模块" -#: src/exercises/concurrency/solutions-morning.md:1 -msgid "Concurrency Morning Exercise" -msgstr "并发编程：上午练习" +#~ msgid "mutable:" +#~ msgstr "可变：" -#: src/exercises/concurrency/solutions-morning.md:5 -msgid "([back to exercise](dining-philosophers.md))" -msgstr "([返回练习](dining-philosophers.md))" +#, fuzzy +#~ msgid "ownership:" +#~ msgstr "所有权" -#: src/exercises/concurrency/solutions-morning.md:7 -msgid "" -"```rust\n" -"use std::sync::{mpsc, Arc, Mutex};\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" left_fork: Arc>,\n" -" right_fork: Arc>,\n" -" thoughts: mpsc::SyncSender,\n" -"}\n" -"\n" -"impl Philosopher {\n" -" fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))\n" -" .unwrap();\n" -" }\n" -"\n" -" fn eat(&self) {\n" -" println!(\"{} is trying to eat\", &self.name);\n" -" let left = self.left_fork.lock().unwrap();\n" -" let right = self.right_fork.lock().unwrap();\n" -"\n" -" println!(\"{} is eating...\", &self.name);\n" -" thread::sleep(Duration::from_millis(10));\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Plato\", \"Aristotle\", \"Thales\", \"Pythagoras\"];\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::sync_channel(10);\n" -"\n" -" let forks = (0..PHILOSOPHERS.len())\n" -" .map(|_| Arc::new(Mutex::new(Fork)))\n" -" .collect::>();\n" -"\n" -" for i in 0..forks.len() {\n" -" let tx = tx.clone();\n" -" let mut left_fork = Arc::clone(&forks[i]);\n" -" let mut right_fork = Arc::clone(&forks[(i + 1) % forks.len()]);\n" -"\n" -" // To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" -" if i == forks.len() - 1 {\n" -" std::mem::swap(&mut left_fork, &mut right_fork);\n" -" }\n" -"\n" -" let philosopher = Philosopher {\n" -" name: PHILOSOPHERS[i].to_string(),\n" -" thoughts: tx,\n" -" left_fork,\n" -" right_fork,\n" -" };\n" -"\n" -" thread::spawn(move || {\n" -" for _ in 0..100 {\n" -" philosopher.eat();\n" -" philosopher.think();\n" -" }\n" -" });\n" -" }\n" -"\n" -" drop(tx);\n" -" for thought in rx {\n" -" println!(\"{thought}\");\n" -" }\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "panic:" +#~ msgstr "Panics" -#: src/exercises/concurrency/solutions-morning.md:82 #, fuzzy -msgid "Link Checker" -msgstr "多线程链接检查器" +#~ msgid "receiver:" +#~ msgstr "驱动程序" -#: src/exercises/concurrency/solutions-morning.md:84 #, fuzzy -msgid "([back to exercise](link-checker.md))" -msgstr "([返回练习](luhn.md))" +#~ msgid "reference counting:" +#~ msgstr "解引用原始指针。" -#: src/exercises/concurrency/solutions-morning.md:86 -msgid "" -"```rust,compile_fail\n" -"use std::{sync::Arc, sync::Mutex, sync::mpsc, thread};\n" -"\n" -"use reqwest::{blocking::Client, Url};\n" -"use scraper::{Html, Selector};\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Error, Debug)]\n" -"enum Error {\n" -" #[error(\"request error: {0}\")]\n" -" ReqwestError(#[from] reqwest::Error),\n" -" #[error(\"bad http response: {0}\")]\n" -" BadResponse(String),\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct CrawlCommand {\n" -" url: Url,\n" -" extract_links: bool,\n" -"}\n" -"\n" -"fn visit_page(client: &Client, command: &CrawlCommand) -> Result, " -"Error> {\n" -" println!(\"Checking {:#}\", command.url);\n" -" let response = client.get(command.url.clone()).send()?;\n" -" if !response.status().is_success() {\n" -" return Err(Error::BadResponse(response.status().to_string()));\n" -" }\n" -"\n" -" let mut link_urls = Vec::new();\n" -" if !command.extract_links {\n" -" return Ok(link_urls);\n" -" }\n" -"\n" -" let base_url = response.url().to_owned();\n" -" let body_text = response.text()?;\n" -" let document = Html::parse_document(&body_text);\n" -"\n" -" let selector = Selector::parse(\"a\").unwrap();\n" -" let href_values = document\n" -" .select(&selector)\n" -" .filter_map(|element| element.value().attr(\"href\"));\n" -" for href in href_values {\n" -" match base_url.join(href) {\n" -" Ok(link_url) => {\n" -" link_urls.push(link_url);\n" -" }\n" -" Err(err) => {\n" -" println!(\"On {base_url:#}: ignored unparsable {href:?}: " -"{err}\");\n" -" }\n" -" }\n" -" }\n" -" Ok(link_urls)\n" -"}\n" -"\n" -"struct CrawlState {\n" -" domain: String,\n" -" visited_pages: std::collections::HashSet,\n" -"}\n" -"\n" -"impl CrawlState {\n" -" fn new(start_url: &Url) -> CrawlState {\n" -" let mut visited_pages = std::collections::HashSet::new();\n" -" visited_pages.insert(start_url.as_str().to_string());\n" -" CrawlState {\n" -" domain: start_url.domain().unwrap().to_string(),\n" -" visited_pages,\n" -" }\n" -" }\n" -"\n" -" /// Determine whether links within the given page should be extracted.\n" -" fn should_extract_links(&self, url: &Url) -> bool {\n" -" let Some(url_domain) = url.domain() else {\n" -" return false;\n" -" };\n" -" url_domain == self.domain\n" -" }\n" -"\n" -" /// Mark the given page as visited, returning true if it had already\n" -" /// been visited.\n" -" fn mark_visited(&mut self, url: &Url) -> bool {\n" -" self.visited_pages.insert(url.as_str().to_string())\n" -" }\n" -"}\n" -"\n" -"type CrawlResult = Result, (Url, Error)>;\n" -"fn spawn_crawler_threads(\n" -" command_receiver: mpsc::Receiver,\n" -" result_sender: mpsc::Sender,\n" -" thread_count: u32,\n" -") {\n" -" let command_receiver = Arc::new(Mutex::new(command_receiver));\n" -"\n" -" for _ in 0..thread_count {\n" -" let result_sender = result_sender.clone();\n" -" let command_receiver = command_receiver.clone();\n" -" thread::spawn(move || {\n" -" let client = Client::new();\n" -" loop {\n" -" let command_result = {\n" -" let receiver_guard = command_receiver.lock().unwrap();\n" -" receiver_guard.recv()\n" -" };\n" -" let Ok(crawl_command) = command_result else {\n" -" // The sender got dropped. No more commands coming in.\n" -" break;\n" -" };\n" -" let crawl_result = match visit_page(&client, &crawl_command) " -"{\n" -" Ok(link_urls) => Ok(link_urls),\n" -" Err(error) => Err((crawl_command.url, error)),\n" -" };\n" -" result_sender.send(crawl_result).unwrap();\n" -" }\n" -" });\n" -" }\n" -"}\n" -"\n" -"fn control_crawl(\n" -" start_url: Url,\n" -" command_sender: mpsc::Sender,\n" -" result_receiver: mpsc::Receiver,\n" -") -> Vec {\n" -" let mut crawl_state = CrawlState::new(&start_url);\n" -" let start_command = CrawlCommand { url: start_url, extract_links: " -"true };\n" -" command_sender.send(start_command).unwrap();\n" -" let mut pending_urls = 1;\n" -"\n" -" let mut bad_urls = Vec::new();\n" -" while pending_urls > 0 {\n" -" let crawl_result = result_receiver.recv().unwrap();\n" -" pending_urls -= 1;\n" -"\n" -" match crawl_result {\n" -" Ok(link_urls) => {\n" -" for url in link_urls {\n" -" if crawl_state.mark_visited(&url) {\n" -" let extract_links = crawl_state." -"should_extract_links(&url);\n" -" let crawl_command = CrawlCommand { url, " -"extract_links };\n" -" command_sender.send(crawl_command).unwrap();\n" -" pending_urls += 1;\n" -" }\n" -" }\n" -" }\n" -" Err((url, error)) => {\n" -" bad_urls.push(url);\n" -" println!(\"Got crawling error: {:#}\", error);\n" -" continue;\n" -" }\n" -" }\n" -" }\n" -" bad_urls\n" -"}\n" -"\n" -"fn check_links(start_url: Url) -> Vec {\n" -" let (result_sender, result_receiver) = mpsc::channel::();\n" -" let (command_sender, command_receiver) = mpsc::channel::" -"();\n" -" spawn_crawler_threads(command_receiver, result_sender, 16);\n" -" control_crawl(start_url, command_sender, result_receiver)\n" -"}\n" -"\n" -"fn main() {\n" -" let start_url = reqwest::Url::parse(\"https://www.google.org\")." -"unwrap();\n" -" let bad_urls = check_links(start_url);\n" -" println!(\"Bad URLs: {:#?}\", bad_urls);\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "standard library:" +#~ msgstr "标准库" -#: src/exercises/concurrency/solutions-afternoon.md:1 -msgid "Concurrency Afternoon Exercise" -msgstr "并发编程：下午练习" +#, fuzzy +#~ msgid "static:" +#~ msgstr "`static`" -#: src/exercises/concurrency/solutions-afternoon.md:5 -msgid "([back to exercise](dining-philosophers-async.md))" -msgstr "([返回练习](dining-philosophers-async.md))" +#, fuzzy +#~ msgid "struct:" +#~ msgstr "结构体" -#: src/exercises/concurrency/solutions-afternoon.md:7 -msgid "" -"```rust,compile_fail\n" -"use std::sync::Arc;\n" -"use tokio::time;\n" -"use tokio::sync::mpsc::{self, Sender};\n" -"use tokio::sync::Mutex;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" left_fork: Arc>,\n" -" right_fork: Arc>,\n" -" thoughts: Sender,\n" -"}\n" -"\n" -"impl Philosopher {\n" -" async fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))." -"await\n" -" .unwrap();\n" -" }\n" -"\n" -" async fn eat(&self) {\n" -" // Pick up forks...\n" -" let _first_lock = self.left_fork.lock().await;\n" -" // Add a delay before picking the second fork to allow the " -"execution\n" -" // to transfer to another task\n" -" time::sleep(time::Duration::from_millis(1)).await;\n" -" let _second_lock = self.right_fork.lock().await;\n" -"\n" -" println!(\"{} is eating...\", &self.name);\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -"\n" -" // The locks are dropped here\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Plato\", \"Aristotle\", \"Thales\", \"Pythagoras\"];\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" // Create forks\n" -" let mut forks = vec![];\n" -" (0..PHILOSOPHERS.len()).for_each(|_| forks.push(Arc::new(Mutex::" -"new(Fork))));\n" -"\n" -" // Create philosophers\n" -" let (philosophers, mut rx) = {\n" -" let mut philosophers = vec![];\n" -" let (tx, rx) = mpsc::channel(10);\n" -" for (i, name) in PHILOSOPHERS.iter().enumerate() {\n" -" let left_fork = Arc::clone(&forks[i]);\n" -" let right_fork = Arc::clone(&forks[(i + 1) % PHILOSOPHERS." -"len()]);\n" -" // To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" -" if i == 0 {\n" -" std::mem::swap(&mut left_fork, &mut right_fork);\n" -" }\n" -" philosophers.push(Philosopher {\n" -" name: name.to_string(),\n" -" left_fork,\n" -" right_fork,\n" -" thoughts: tx.clone(),\n" -" });\n" -" }\n" -" (philosophers, rx)\n" -" // tx is dropped here, so we don't need to explicitly drop it later\n" -" };\n" -"\n" -" // Make them think and eat\n" -" for phil in philosophers {\n" -" tokio::spawn(async move {\n" -" for _ in 0..100 {\n" -" phil.think().await;\n" -" phil.eat().await;\n" -" }\n" -" });\n" -"\n" -" }\n" -"\n" -" // Output their thoughts\n" -" while let Some(thought) = rx.recv().await {\n" -" println!(\"Here is a thought: {thought}\");\n" -" }\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "thread:" +#~ msgstr "线程" -#: src/exercises/concurrency/solutions-afternoon.md:97 -msgid "([back to exercise](chat-app.md))" -msgstr "([返回练习](chat-app.md))" +#, fuzzy +#~ msgid "thread safety:" +#~ msgstr "线程" -#: src/exercises/concurrency/solutions-afternoon.md:101 -msgid "" -"```rust,compile_fail\n" -"use futures_util::sink::SinkExt;\n" -"use futures_util::stream::StreamExt;\n" -"use std::error::Error;\n" -"use std::net::SocketAddr;\n" -"use tokio::net::{TcpListener, TcpStream};\n" -"use tokio::sync::broadcast::{channel, Sender};\n" -"use tokio_websockets::{Message, ServerBuilder, WebsocketStream};\n" -"\n" -"async fn handle_connection(\n" -" addr: SocketAddr,\n" -" mut ws_stream: WebsocketStream,\n" -" bcast_tx: Sender,\n" -") -> Result<(), Box> {\n" -"\n" -" ws_stream\n" -" .send(Message::text(\"Welcome to chat! Type a message\".into()))\n" -" .await?;\n" -" let mut bcast_rx = bcast_tx.subscribe();\n" -"\n" -" // A continuous loop for concurrently performing two tasks: (1) " -"receiving\n" -" // messages from `ws_stream` and broadcasting them, and (2) receiving\n" -" // messages on `bcast_rx` and sending them to the client.\n" -" loop {\n" -" tokio::select! {\n" -" incoming = ws_stream.next() => {\n" -" match incoming {\n" -" Some(Ok(msg)) => {\n" -" if let Some(text) = msg.as_text() {\n" -" println!(\"From client {addr:?} {text:?}\");\n" -" bcast_tx.send(text.into())?;\n" -" }\n" -" }\n" -" Some(Err(err)) => return Err(err.into()),\n" -" None => return Ok(()),\n" -" }\n" -" }\n" -" msg = bcast_rx.recv() => {\n" -" ws_stream.send(Message::text(msg?)).await?;\n" -" }\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), Box> {\n" -" let (bcast_tx, _) = channel(16);\n" -"\n" -" let listener = TcpListener::bind(\"127.0.0.1:2000\").await?;\n" -" println!(\"listening on port 2000\");\n" -"\n" -" loop {\n" -" let (socket, addr) = listener.accept().await?;\n" -" println!(\"New connection from {addr:?}\");\n" -" let bcast_tx = bcast_tx.clone();\n" -" tokio::spawn(async move {\n" -" // Wrap the raw TCP stream into a websocket.\n" -" let ws_stream = ServerBuilder::new().accept(socket).await?;\n" -"\n" -" handle_connection(addr, ws_stream, bcast_tx).await\n" -" });\n" -" }\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "trait:" +#~ msgstr "特征" -#: src/exercises/concurrency/solutions-afternoon.md:168 -msgid "" -"```rust,compile_fail\n" -"use futures_util::stream::StreamExt;\n" -"use futures_util::SinkExt;\n" -"use http::Uri;\n" -"use tokio::io::{AsyncBufReadExt, BufReader};\n" -"use tokio_websockets::{ClientBuilder, Message};\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), tokio_websockets::Error> {\n" -" let (mut ws_stream, _) =\n" -" ClientBuilder::from_uri(Uri::from_static(\"ws://127.0.0.1:2000\"))\n" -" .connect()\n" -" .await?;\n" -"\n" -" let stdin = tokio::io::stdin();\n" -" let mut stdin = BufReader::new(stdin).lines();\n" -"\n" -" // Continuous loop for concurrently sending and receiving messages.\n" -" loop {\n" -" tokio::select! {\n" -" incoming = ws_stream.next() => {\n" -" match incoming {\n" -" Some(Ok(msg)) => {\n" -" if let Some(text) = msg.as_text() {\n" -" println!(\"From server: {}\", text);\n" -" }\n" -" },\n" -" Some(Err(err)) => return Err(err.into()),\n" -" None => return Ok(()),\n" -" }\n" -" }\n" -" res = stdin.next_line() => {\n" -" match res {\n" -" Ok(None) => return Ok(()),\n" -" Ok(Some(line)) => ws_stream.send(Message::text(line." -"to_string())).await?,\n" -" Err(err) => return Err(err.into()),\n" -" }\n" -" }\n" -"\n" -" }\n" -" }\n" -"}\n" -"```" -msgstr "" +#, fuzzy +#~ msgid "union:" +#~ msgstr "联合体" + +#, fuzzy +#~ msgid "unit test:" +#~ msgstr "单元测试" + +#, fuzzy +#~ msgid "variable:\\" +#~ msgstr "变量" + +#~ msgid "You will find solutions to the exercises on the following pages." +#~ msgstr "您将在下面的页面找到练习的解答。" + +#~ msgid "" +#~ "Feel free to ask questions about the solutions [on GitHub](https://github." +#~ "com/google/comprehensive-rust/discussions). Let us know if you have a " +#~ "different or better solution than what is presented here." +#~ msgstr "" +#~ "欢迎您在 [GitHub](https://github.com/google/comprehensive-rust/" +#~ "discussions) 上提问关于解决方案的问题。如果您有与此处呈现的不同或更好的解" +#~ "决方案，请告诉我们。" + +#~ msgid "Day 1 Morning Exercises" +#~ msgstr "第一天上午的练习" + +#~ msgid "([back to exercise](for-loops.md))" +#~ msgstr "([返回练习](for-loops.md))" + +#~ msgid "Bonus question" +#~ msgstr "附加问题" + +#~ msgid "" +#~ "It requires more advanced concepts. It might seem that we could use a " +#~ "slice-of-slices (`&[&[i32]]`) as the input type to transpose and thus " +#~ "make our function handle any size of matrix. However, this quickly breaks " +#~ "down: the return type cannot be `&[&[i32]]` since it needs to own the " +#~ "data you return." +#~ msgstr "" +#~ "这需要更高级的概念。看起来，我们可以使用切片的切片（`&[&[i32]]`）作为输入" +#~ "类型来进行转置，从而使我们的函数能够处理任意大小的矩阵。然而，这很快就会崩" +#~ "溃：返回类型不能是 `&[&[i32]]`，因为它需要拥有您返回的数据。" + +#~ msgid "" +#~ "You can attempt to use something like `Vec>`, but this doesn't " +#~ "work out-of-the-box either: it's hard to convert from `Vec>` to " +#~ "`&[&[i32]]` so now you cannot easily use `pretty_print` either." +#~ msgstr "" +#~ "您可以尝试使用类似 `Vec>` 的方式，但这也无法直接工作：从 " +#~ "`Vec>` 转换为 `&[&[i32]]` 很困难，因此您现在也不能轻松使用 " +#~ "`pretty_print`。" + +#~ msgid "" +#~ "Once we get to traits and generics, we'll be able to use the [`std::" +#~ "convert::AsRef`](https://doc.rust-lang.org/std/convert/trait.AsRef.html) " +#~ "trait to abstract over anything that can be referenced as a slice." +#~ msgstr "" +#~ "了解 trait 和泛型后，我们就可以使用[“std::convert::AsRef”](https://doc." +#~ "rust-lang.org/std/convert/trait.AsRef.html)trait 来抽象化任何可作为 Slice " +#~ "引用的内容了。" + +#~ msgid "" +#~ "In addition, the type itself would not enforce that the child slices are " +#~ "of the same length, so such variable could contain an invalid matrix." +#~ msgstr "" +#~ "此外，类型本身不会强制要求子切片具有相同的长度，因此这样的变量可能包含一个" +#~ "无效的矩阵。" + +#~ msgid "Day 1 Afternoon Exercises" +#~ msgstr "第一天下午的练习" + +#~ msgid "([back to exercise](luhn.md))" +#~ msgstr "([返回练习](luhn.md))" + +#, fuzzy +#~ msgid "Pattern matching" +#~ msgstr "模式匹配" + +#~ msgid "Day 2 Morning Exercises" +#~ msgstr "第二天上午的练习" + +#~ msgid "Designing a Library" +#~ msgstr "设计一个库" + +#~ msgid "([back to exercise](book-library.md))" +#~ msgstr "([返回练习](book-library.md))" + +#, fuzzy +#~ msgid "([back to exercise](health-statistics.md))" +#~ msgstr "([返回练习](rtc.md))" + +#~ msgid "Day 2 Afternoon Exercises" +#~ msgstr "第二天下午的练习" + +#~ msgid "([back to exercise](strings-iterators.md))" +#~ msgstr "([返回练习](strings-iterators.md))" + +#~ msgid "Day 3 Morning Exercise" +#~ msgstr "第三天上午的练习" + +#~ msgid "([back to exercise](simple-gui.md))" +#~ msgstr "([返回练习](simple-gui.md))" + +#~ msgid "([back to exercise](points-polygons.md))" +#~ msgstr "([返回练习](points-polygons.md))" + +#~ msgid "Day 3 Afternoon Exercises" +#~ msgstr "第三天下午的练习" + +#~ msgid "([back to exercise](safe-ffi-wrapper.md))" +#~ msgstr "([返回练习](safe-ffi-wrapper.md))"