| msgid "" |
| msgstr "" |
| "Project-Id-Version: Rust By Example\n" |
| "POT-Creation-Date: 2025-07-03T23:05:52+08:00\n" |
| "PO-Revision-Date: 2024-08-17 22:13+0800\n" |
| "Last-Translator: Binlogo <binboy@live.com>\n" |
| "Language-Team: Chinese\n" |
| "Language: zh\n" |
| "MIME-Version: 1.0\n" |
| "Content-Type: text/plain; charset=UTF-8\n" |
| "Content-Transfer-Encoding: 8bit\n" |
| "Plural-Forms: nplurals=1; plural=0;\n" |
| |
| #: src/SUMMARY.md:1 |
| msgid "Summary" |
| msgstr "Summary" |
| |
| #: src/SUMMARY.md:3 |
| msgid "Introduction" |
| msgstr "介绍" |
| |
| #: src/SUMMARY.md:5 src/hello.md:1 |
| msgid "Hello World" |
| msgstr "Hello World" |
| |
| #: src/SUMMARY.md:6 src/hello/comment.md:1 |
| msgid "Comments" |
| msgstr "注释" |
| |
| #: src/SUMMARY.md:7 src/hello/print.md:1 |
| msgid "Formatted print" |
| msgstr "格式化打印" |
| |
| #: src/SUMMARY.md:8 src/hello/print/print_debug.md:1 |
| msgid "Debug" |
| msgstr "调试 Debug" |
| |
| #: src/SUMMARY.md:9 src/hello/print/print_display.md:1 |
| msgid "Display" |
| msgstr "显示 Display" |
| |
| #: src/SUMMARY.md:10 src/hello/print/print_display/testcase_list.md:1 |
| msgid "Testcase: List" |
| msgstr "测试实例：列表" |
| |
| #: src/SUMMARY.md:11 src/hello/print/fmt.md:1 |
| msgid "Formatting" |
| msgstr "格式化" |
| |
| #: src/SUMMARY.md:13 src/primitives.md:1 |
| msgid "Primitives" |
| msgstr "原生类型" |
| |
| #: src/SUMMARY.md:14 src/primitives/literals.md:1 |
| msgid "Literals and operators" |
| msgstr "字面量和运算符" |
| |
| #: src/SUMMARY.md:15 src/primitives/tuples.md:1 |
| msgid "Tuples" |
| msgstr "元组" |
| |
| #: src/SUMMARY.md:16 src/primitives/array.md:1 |
| msgid "Arrays and Slices" |
| msgstr "数组和切片" |
| |
| #: src/SUMMARY.md:18 src/custom_types.md:1 |
| msgid "Custom Types" |
| msgstr "自定义类型" |
| |
| #: src/SUMMARY.md:19 src/custom_types/structs.md:1 |
| msgid "Structures" |
| msgstr "结构体" |
| |
| #: src/SUMMARY.md:20 src/custom_types/enum.md:1 |
| msgid "Enums" |
| msgstr "枚举" |
| |
| #: src/SUMMARY.md:21 src/custom_types/enum/enum_use.md:1 |
| msgid "use" |
| msgstr "use" |
| |
| #: src/SUMMARY.md:22 src/custom_types/enum/c_like.md:1 |
| msgid "C-like" |
| msgstr "C 风格用法" |
| |
| #: src/SUMMARY.md:23 src/custom_types/enum/testcase_linked_list.md:1 |
| msgid "Testcase: linked-list" |
| msgstr "测试实例：链表" |
| |
| #: src/SUMMARY.md:24 src/custom_types/constants.md:1 |
| msgid "constants" |
| msgstr "常量" |
| |
| #: src/SUMMARY.md:26 src/variable_bindings.md:1 |
| msgid "Variable Bindings" |
| msgstr "变量绑定" |
| |
| #: src/SUMMARY.md:27 src/SUMMARY.md:120 src/SUMMARY.md:123 |
| #: src/variable_bindings/mut.md:1 src/scope/move/mut.md:1 |
| #: src/scope/borrow/mut.md:1 |
| msgid "Mutability" |
| msgstr "可变性" |
| |
| #: src/SUMMARY.md:28 src/variable_bindings/scope.md:1 |
| msgid "Scope and Shadowing" |
| msgstr "作用域和遮蔽" |
| |
| #: src/SUMMARY.md:29 src/variable_bindings/declare.md:1 |
| msgid "Declare first" |
| msgstr "先声明" |
| |
| #: src/SUMMARY.md:30 src/variable_bindings/freeze.md:1 |
| msgid "Freezing" |
| msgstr "冻结" |
| |
| #: src/SUMMARY.md:32 src/types.md:1 |
| msgid "Types" |
| msgstr "类型" |
| |
| #: src/SUMMARY.md:33 src/types/cast.md:1 |
| msgid "Casting" |
| msgstr "类型转换" |
| |
| #: src/SUMMARY.md:34 src/types/literals.md:1 |
| msgid "Literals" |
| msgstr "字面量" |
| |
| #: src/SUMMARY.md:35 src/types/inference.md:1 |
| msgid "Inference" |
| msgstr "类型推断" |
| |
| #: src/SUMMARY.md:36 src/SUMMARY.md:124 src/types/alias.md:1 |
| #: src/scope/borrow/alias.md:1 |
| msgid "Aliasing" |
| msgstr "别名" |
| |
| #: src/SUMMARY.md:38 src/conversion.md:1 |
| msgid "Conversion" |
| msgstr "转换" |
| |
| #: src/SUMMARY.md:39 src/conversion/from_into.md:1 |
| msgid "`From` and `Into`" |
| msgstr "`From` 和 `Into`" |
| |
| #: src/SUMMARY.md:40 src/conversion/try_from_try_into.md:1 |
| msgid "`TryFrom` and `TryInto`" |
| msgstr "`TryFrom` 和 `TryInto`" |
| |
| #: src/SUMMARY.md:41 |
| msgid "To and from `String`s" |
| msgstr "`String` 类型转换" |
| |
| #: src/SUMMARY.md:43 src/expression.md:1 |
| msgid "Expressions" |
| msgstr "表达式" |
| |
| #: src/SUMMARY.md:45 src/flow_control.md:1 |
| msgid "Flow of Control" |
| msgstr "控制流" |
| |
| #: src/SUMMARY.md:46 src/flow_control/if_else.md:1 |
| msgid "if/else" |
| msgstr "if/else" |
| |
| #: src/SUMMARY.md:47 src/flow_control/loop.md:1 |
| msgid "loop" |
| msgstr "loop" |
| |
| #: src/SUMMARY.md:48 src/flow_control/loop/nested.md:1 |
| msgid "Nesting and labels" |
| msgstr "嵌套和标签" |
| |
| #: src/SUMMARY.md:49 src/flow_control/loop/return.md:1 |
| msgid "Returning from loops" |
| msgstr "在 loop 中返回值" |
| |
| #: src/SUMMARY.md:50 src/flow_control/while.md:1 |
| msgid "while" |
| msgstr "while" |
| |
| #: src/SUMMARY.md:51 src/flow_control/for.md:3 |
| msgid "for and range" |
| msgstr "for 和 range" |
| |
| #: src/SUMMARY.md:52 src/flow_control/match.md:1 |
| msgid "match" |
| msgstr "match" |
| |
| #: src/SUMMARY.md:53 src/flow_control/match/destructuring.md:1 |
| msgid "Destructuring" |
| msgstr "解构" |
| |
| #: src/SUMMARY.md:54 |
| #: src/flow_control/match/destructuring/destructure_tuple.md:1 |
| msgid "tuples" |
| msgstr "元组" |
| |
| #: src/SUMMARY.md:55 |
| #: src/flow_control/match/destructuring/destructure_slice.md:1 |
| msgid "arrays/slices" |
| msgstr "数组/切片" |
| |
| #: src/SUMMARY.md:56 src/flow_control/match/destructuring/destructure_enum.md:1 |
| msgid "enums" |
| msgstr "枚举" |
| |
| #: src/SUMMARY.md:57 |
| #: src/flow_control/match/destructuring/destructure_pointers.md:1 |
| msgid "pointers/ref" |
| msgstr "指针/引用" |
| |
| #: src/SUMMARY.md:58 |
| #: src/flow_control/match/destructuring/destructure_structures.md:1 |
| msgid "structs" |
| msgstr "结构体" |
| |
| #: src/SUMMARY.md:59 src/flow_control/match/guard.md:1 |
| msgid "Guards" |
| msgstr "守卫" |
| |
| #: src/SUMMARY.md:60 src/flow_control/match/binding.md:1 |
| msgid "Binding" |
| msgstr "绑定" |
| |
| #: src/SUMMARY.md:61 src/flow_control/if_let.md:1 |
| msgid "if let" |
| msgstr "if let" |
| |
| #: src/SUMMARY.md:62 src/flow_control/let_else.md:1 |
| msgid "let-else" |
| msgstr "let-else" |
| |
| #: src/SUMMARY.md:63 src/flow_control/while_let.md:1 |
| msgid "while let" |
| msgstr "while let" |
| |
| #: src/SUMMARY.md:65 src/SUMMARY.md:103 src/SUMMARY.md:128 src/fn.md:1 |
| #: src/generics/gen_fn.md:1 src/scope/lifetime/fn.md:1 |
| msgid "Functions" |
| msgstr "函数" |
| |
| #: src/SUMMARY.md:66 src/SUMMARY.md:129 src/scope/lifetime/methods.md:1 |
| msgid "Methods" |
| msgstr "方法" |
| |
| #: src/SUMMARY.md:67 src/fn/closures.md:1 |
| msgid "Closures" |
| msgstr "闭包" |
| |
| #: src/SUMMARY.md:68 src/fn/closures/capture.md:1 |
| msgid "Capturing" |
| msgstr "捕获" |
| |
| #: src/SUMMARY.md:69 src/fn/closures/input_parameters.md:1 |
| msgid "As input parameters" |
| msgstr "作为输入参数" |
| |
| #: src/SUMMARY.md:70 src/fn/closures/anonymity.md:1 |
| msgid "Type anonymity" |
| msgstr "类型匿名" |
| |
| #: src/SUMMARY.md:71 src/fn/closures/input_functions.md:1 |
| msgid "Input functions" |
| msgstr "输入函数" |
| |
| #: src/SUMMARY.md:72 src/fn/closures/output_parameters.md:1 |
| msgid "As output parameters" |
| msgstr "作为输出参数" |
| |
| #: src/SUMMARY.md:73 src/fn/closures/closure_examples.md:1 |
| msgid "Examples in `std`" |
| msgstr "`std` 中的例子" |
| |
| #: src/SUMMARY.md:74 src/fn/closures/closure_examples/iter_any.md:1 |
| msgid "Iterator::any" |
| msgstr "Iterator::any" |
| |
| #: src/SUMMARY.md:75 src/fn/closures/closure_examples/iter_find.md:1 |
| msgid "Searching through iterators" |
| msgstr "通过迭代器搜索" |
| |
| #: src/SUMMARY.md:76 src/fn/hof.md:1 |
| msgid "Higher Order Functions" |
| msgstr "高阶函数" |
| |
| #: src/SUMMARY.md:77 src/fn/diverging.md:1 |
| msgid "Diverging functions" |
| msgstr "发散函数" |
| |
| #: src/SUMMARY.md:79 src/mod.md:1 |
| msgid "Modules" |
| msgstr "模块" |
| |
| #: src/SUMMARY.md:80 src/mod/visibility.md:1 |
| msgid "Visibility" |
| msgstr "可见性" |
| |
| #: src/SUMMARY.md:81 src/mod/struct_visibility.md:1 |
| msgid "Struct visibility" |
| msgstr "结构体可见性" |
| |
| #: src/SUMMARY.md:82 src/mod/use.md:1 |
| msgid "The `use` declaration" |
| msgstr "`use` 声明" |
| |
| #: src/SUMMARY.md:83 src/mod/super.md:1 |
| msgid "`super` and `self`" |
| msgstr "`super` 和 `self`" |
| |
| #: src/SUMMARY.md:84 src/mod/split.md:1 |
| msgid "File hierarchy" |
| msgstr "文件分层" |
| |
| #: src/SUMMARY.md:86 src/SUMMARY.md:98 src/crates.md:1 src/attribute/crate.md:1 |
| #: src/std_misc/arg.md:30 |
| msgid "Crates" |
| msgstr "Crates" |
| |
| #: src/SUMMARY.md:87 src/crates/lib.md:1 |
| msgid "Creating a Library" |
| msgstr "创建库" |
| |
| #: src/SUMMARY.md:88 src/crates/using_lib.md:1 |
| msgid "Using a Library" |
| msgstr "使用库" |
| |
| #: src/SUMMARY.md:90 src/cargo.md:1 |
| msgid "Cargo" |
| msgstr "Cargo" |
| |
| #: src/SUMMARY.md:91 src/cargo/deps.md:1 |
| msgid "Dependencies" |
| msgstr "依赖" |
| |
| #: src/SUMMARY.md:92 src/cargo/conventions.md:1 |
| msgid "Conventions" |
| msgstr "约定" |
| |
| #: src/SUMMARY.md:93 |
| msgid "Tests" |
| msgstr "测试" |
| |
| #: src/SUMMARY.md:94 src/cargo/build_scripts.md:1 |
| msgid "Build Scripts" |
| msgstr "构建脚本" |
| |
| #: src/SUMMARY.md:96 src/attribute.md:1 |
| msgid "Attributes" |
| msgstr "属性" |
| |
| #: src/SUMMARY.md:97 src/attribute/unused.md:1 |
| msgid "`dead_code`" |
| msgstr "`dead_code`" |
| |
| #: src/SUMMARY.md:99 src/attribute/cfg.md:1 |
| msgid "`cfg`" |
| msgstr "`cfg`" |
| |
| #: src/SUMMARY.md:100 src/attribute/cfg/custom.md:1 |
| msgid "Custom" |
| msgstr "自定义" |
| |
| #: src/SUMMARY.md:102 src/generics.md:1 |
| msgid "Generics" |
| msgstr "泛型" |
| |
| #: src/SUMMARY.md:104 src/generics/impl.md:1 |
| msgid "Implementation" |
| msgstr "实现" |
| |
| #: src/SUMMARY.md:105 src/SUMMARY.md:131 src/SUMMARY.md:137 |
| #: src/generics/gen_trait.md:1 src/scope/lifetime/trait.md:1 src/trait.md:1 |
| msgid "Traits" |
| msgstr "特质" |
| |
| #: src/SUMMARY.md:106 src/SUMMARY.md:132 src/generics/bounds.md:1 |
| #: src/scope/lifetime/lifetime_bounds.md:1 |
| msgid "Bounds" |
| msgstr "约束" |
| |
| #: src/SUMMARY.md:107 src/generics/bounds/testcase_empty.md:1 |
| msgid "Testcase: empty bounds" |
| msgstr "测试实例：空约束" |
| |
| #: src/SUMMARY.md:108 src/generics/multi_bounds.md:1 |
| msgid "Multiple bounds" |
| msgstr "多重约束" |
| |
| #: src/SUMMARY.md:109 src/generics/where.md:1 |
| msgid "Where clauses" |
| msgstr "Where 分句" |
| |
| #: src/SUMMARY.md:110 src/generics/new_types.md:1 |
| msgid "New Type Idiom" |
| msgstr "新类型惯用法" |
| |
| #: src/SUMMARY.md:111 src/generics/assoc_items.md:1 |
| msgid "Associated items" |
| msgstr "关联项" |
| |
| #: src/SUMMARY.md:112 src/generics/assoc_items/the_problem.md:1 |
| msgid "The Problem" |
| msgstr "问题" |
| |
| #: src/SUMMARY.md:113 src/generics/assoc_items/types.md:1 |
| msgid "Associated types" |
| msgstr "关联类型" |
| |
| #: src/SUMMARY.md:114 src/generics/phantom.md:1 |
| msgid "Phantom type parameters" |
| msgstr "虚类型参数" |
| |
| #: src/SUMMARY.md:115 src/generics/phantom/testcase_units.md:1 |
| msgid "Testcase: unit clarification" |
| msgstr "测试实例：单位澄清" |
| |
| #: src/SUMMARY.md:117 src/scope.md:1 |
| msgid "Scoping rules" |
| msgstr "作用域规则" |
| |
| #: src/SUMMARY.md:118 src/scope/raii.md:1 |
| msgid "RAII" |
| msgstr "RAII" |
| |
| #: src/SUMMARY.md:119 src/scope/move.md:1 |
| msgid "Ownership and moves" |
| msgstr "所有权和移动" |
| |
| #: src/SUMMARY.md:121 src/scope/move/partial_move.md:1 |
| msgid "Partial moves" |
| msgstr "部分移动" |
| |
| #: src/SUMMARY.md:122 src/scope/borrow.md:1 |
| msgid "Borrowing" |
| msgstr "借用" |
| |
| #: src/SUMMARY.md:125 src/scope/borrow/ref.md:1 |
| msgid "The ref pattern" |
| msgstr "ref 模式" |
| |
| #: src/SUMMARY.md:126 src/scope/lifetime.md:1 |
| msgid "Lifetimes" |
| msgstr "生命周期" |
| |
| #: src/SUMMARY.md:127 src/scope/lifetime/explicit.md:1 |
| msgid "Explicit annotation" |
| msgstr "显式注解" |
| |
| #: src/SUMMARY.md:130 src/scope/lifetime/struct.md:1 |
| msgid "Structs" |
| msgstr "结构体" |
| |
| #: src/SUMMARY.md:133 src/scope/lifetime/lifetime_coercion.md:1 |
| msgid "Coercion" |
| msgstr "强制转换" |
| |
| #: src/SUMMARY.md:134 src/scope/lifetime/static_lifetime.md:1 |
| msgid "Static" |
| msgstr "静态" |
| |
| #: src/SUMMARY.md:135 src/scope/lifetime/elision.md:1 |
| msgid "Elision" |
| msgstr "省略" |
| |
| #: src/SUMMARY.md:138 src/trait/derive.md:1 |
| msgid "Derive" |
| msgstr "派生" |
| |
| #: src/SUMMARY.md:139 src/trait/dyn.md:1 |
| msgid "Returning Traits with `dyn`" |
| msgstr "使用 `dyn` 返回 trait" |
| |
| #: src/SUMMARY.md:140 src/trait/ops.md:1 |
| msgid "Operator Overloading" |
| msgstr "运算符重载" |
| |
| #: src/SUMMARY.md:141 src/trait/drop.md:1 |
| msgid "Drop" |
| msgstr "Drop" |
| |
| #: src/SUMMARY.md:142 src/trait/iter.md:1 |
| msgid "Iterators" |
| msgstr "迭代器" |
| |
| #: src/SUMMARY.md:143 src/trait/impl_trait.md:1 |
| msgid "`impl Trait`" |
| msgstr "`impl Trait`" |
| |
| #: src/SUMMARY.md:144 src/trait/clone.md:1 |
| msgid "Clone" |
| msgstr "克隆" |
| |
| #: src/SUMMARY.md:145 src/trait/supertraits.md:1 |
| msgid "Supertraits" |
| msgstr "父特质" |
| |
| #: src/SUMMARY.md:146 src/trait/disambiguating.md:1 |
| msgid "Disambiguating overlapping traits" |
| msgstr "消除重叠特质的歧义" |
| |
| #: src/SUMMARY.md:148 |
| msgid "macro_rules!" |
| msgstr "macro_rules!" |
| |
| #: src/SUMMARY.md:149 src/macros/syntax.md:1 |
| msgid "Syntax" |
| msgstr "语法" |
| |
| #: src/SUMMARY.md:150 src/macros/designators.md:1 |
| msgid "Designators" |
| msgstr "指示符" |
| |
| #: src/SUMMARY.md:151 src/macros/overload.md:1 |
| msgid "Overload" |
| msgstr "重载" |
| |
| #: src/SUMMARY.md:152 src/macros/repeat.md:1 |
| msgid "Repeat" |
| msgstr "重复" |
| |
| #: src/SUMMARY.md:153 src/macros/dry.md:1 |
| msgid "DRY (Don't Repeat Yourself)" |
| msgstr "DRY(不要重复自己)" |
| |
| #: src/SUMMARY.md:154 |
| msgid "DSL (Domain Specific Languages)" |
| msgstr "DSL(领域特定语言)" |
| |
| #: src/SUMMARY.md:155 |
| msgid "Variadics" |
| msgstr "可变参数" |
| |
| #: src/SUMMARY.md:157 src/error.md:1 |
| msgid "Error handling" |
| msgstr "错误处理" |
| |
| #: src/SUMMARY.md:158 src/error/panic.md:1 |
| msgid "`panic`" |
| msgstr "`panic`" |
| |
| #: src/SUMMARY.md:159 |
| msgid "`abort` & `unwind`" |
| msgstr "`abort` 和 `unwind`" |
| |
| #: src/SUMMARY.md:160 src/error/option_unwrap.md:1 |
| msgid "`Option` & `unwrap`" |
| msgstr "`Option` 和 `unwrap`" |
| |
| #: src/SUMMARY.md:161 src/error/option_unwrap/question_mark.md:1 |
| msgid "Unpacking options with `?`" |
| msgstr "使用 `?` 解包 Option" |
| |
| #: src/SUMMARY.md:162 src/error/option_unwrap/map.md:1 |
| msgid "Combinators: `map`" |
| msgstr "组合器：`map`" |
| |
| #: src/SUMMARY.md:163 src/error/option_unwrap/and_then.md:1 |
| msgid "Combinators: `and_then`" |
| msgstr "组合器：`and_then`" |
| |
| #: src/SUMMARY.md:164 |
| msgid "Defaults: `or`, `or_else`, `get_or_insert`, `get_or_insert_with`" |
| msgstr "默认值：`or`、`or_else`、`get_or_insert`、`get_or_insert_with`" |
| |
| #: src/SUMMARY.md:165 src/SUMMARY.md:183 src/error/result.md:1 |
| #: src/std/result.md:1 |
| msgid "`Result`" |
| msgstr "`Result`" |
| |
| #: src/SUMMARY.md:166 src/error/result/result_map.md:1 |
| msgid "`map` for `Result`" |
| msgstr "`Result` 的 `map`" |
| |
| #: src/SUMMARY.md:167 src/error/result/result_alias.md:1 |
| msgid "aliases for `Result`" |
| msgstr "`Result` 的别名" |
| |
| #: src/SUMMARY.md:168 src/error/result/early_returns.md:1 |
| msgid "Early returns" |
| msgstr "提前返回" |
| |
| #: src/SUMMARY.md:169 src/error/result/enter_question_mark.md:1 |
| msgid "Introducing `?`" |
| msgstr "引入 `?`" |
| |
| #: src/SUMMARY.md:170 src/error/multiple_error_types.md:1 |
| msgid "Multiple error types" |
| msgstr "多种错误类型" |
| |
| #: src/SUMMARY.md:171 src/error/multiple_error_types/option_result.md:1 |
| msgid "Pulling `Result`s out of `Option`s" |
| msgstr "从 `Option` 中提取 `Result`" |
| |
| #: src/SUMMARY.md:172 src/error/multiple_error_types/define_error_type.md:1 |
| msgid "Defining an error type" |
| msgstr "定义错误类型" |
| |
| #: src/SUMMARY.md:173 src/error/multiple_error_types/boxing_errors.md:1 |
| msgid "`Box`ing errors" |
| msgstr "使用 `Box` 将错误装箱" |
| |
| #: src/SUMMARY.md:174 src/error/multiple_error_types/reenter_question_mark.md:1 |
| msgid "Other uses of `?`" |
| msgstr "`?` 的其他用途" |
| |
| #: src/SUMMARY.md:175 src/error/multiple_error_types/wrap_error.md:1 |
| msgid "Wrapping errors" |
| msgstr "包装错误" |
| |
| #: src/SUMMARY.md:176 src/error/iter_result.md:1 |
| msgid "Iterating over `Result`s" |
| msgstr "遍历 `Result`" |
| |
| #: src/SUMMARY.md:178 src/std.md:1 |
| msgid "Std library types" |
| msgstr "标准库类型" |
| |
| #: src/SUMMARY.md:179 src/std/box.md:1 |
| msgid "Box, stack and heap" |
| msgstr "Box、栈和堆" |
| |
| #: src/SUMMARY.md:180 src/std/vec.md:1 |
| msgid "Vectors" |
| msgstr "Vectors" |
| |
| #: src/SUMMARY.md:181 src/std/str.md:1 |
| msgid "Strings" |
| msgstr "字符串" |
| |
| #: src/SUMMARY.md:182 src/std/option.md:1 |
| msgid "`Option`" |
| msgstr "`Option`" |
| |
| #: src/SUMMARY.md:184 src/std/result/question_mark.md:1 |
| msgid "`?`" |
| msgstr "`?`" |
| |
| #: src/SUMMARY.md:185 src/std/panic.md:1 |
| msgid "`panic!`" |
| msgstr "`panic!`" |
| |
| #: src/SUMMARY.md:186 src/std/hash.md:1 |
| msgid "HashMap" |
| msgstr "HashMap" |
| |
| #: src/SUMMARY.md:187 src/std/hash/alt_key_types.md:1 |
| msgid "Alternate/custom key types" |
| msgstr "更改或自定义键类型" |
| |
| #: src/SUMMARY.md:188 src/std/hash/hashset.md:1 |
| msgid "HashSet" |
| msgstr "HashSet" |
| |
| #: src/SUMMARY.md:189 src/std/rc.md:1 |
| msgid "`Rc`" |
| msgstr "`Rc`" |
| |
| #: src/SUMMARY.md:190 |
| msgid "`Arc`" |
| msgstr "`Arc`" |
| |
| #: src/SUMMARY.md:192 src/std_misc.md:1 |
| msgid "Std misc" |
| msgstr "标准库中的其他内容" |
| |
| #: src/SUMMARY.md:193 src/std_misc.md:6 src/std_misc/threads.md:1 |
| msgid "Threads" |
| msgstr "线程" |
| |
| #: src/SUMMARY.md:194 src/std_misc/threads/testcase_mapreduce.md:1 |
| msgid "Testcase: map-reduce" |
| msgstr "测试实例：map-reduce" |
| |
| #: src/SUMMARY.md:195 src/std_misc.md:7 src/std_misc/channels.md:1 |
| msgid "Channels" |
| msgstr "信道" |
| |
| #: src/SUMMARY.md:196 src/std_misc/path.md:1 |
| msgid "Path" |
| msgstr "路径" |
| |
| #: src/SUMMARY.md:197 src/std_misc.md:8 src/std_misc/file.md:1 |
| msgid "File I/O" |
| msgstr "文件 I/O" |
| |
| #: src/SUMMARY.md:198 src/std_misc/file/open.md:1 |
| msgid "`open`" |
| msgstr "`open`" |
| |
| #: src/SUMMARY.md:199 src/std_misc/file/create.md:1 |
| msgid "`create`" |
| msgstr "`create`" |
| |
| #: src/SUMMARY.md:200 src/std_misc/file/read_lines.md:1 |
| msgid "`read_lines`" |
| msgstr "`read_lines`" |
| |
| #: src/SUMMARY.md:201 src/std_misc/process.md:1 |
| msgid "Child processes" |
| msgstr "子进程" |
| |
| #: src/SUMMARY.md:202 src/std_misc/process/pipe.md:1 |
| msgid "Pipes" |
| msgstr "管道" |
| |
| #: src/SUMMARY.md:203 src/std_misc/process/wait.md:1 |
| msgid "Wait" |
| msgstr "等待" |
| |
| #: src/SUMMARY.md:204 src/std_misc/fs.md:1 |
| msgid "Filesystem Operations" |
| msgstr "文件系统操作" |
| |
| #: src/SUMMARY.md:205 src/std_misc/arg.md:1 |
| msgid "Program arguments" |
| msgstr "程序参数" |
| |
| #: src/SUMMARY.md:206 src/std_misc/arg/matching.md:1 |
| msgid "Argument parsing" |
| msgstr "参数解析" |
| |
| #: src/SUMMARY.md:207 src/std_misc/ffi.md:1 |
| msgid "Foreign Function Interface" |
| msgstr "外部函数接口" |
| |
| #: src/SUMMARY.md:209 src/cargo/test.md:1 src/testing.md:1 |
| msgid "Testing" |
| msgstr "测试" |
| |
| #: src/SUMMARY.md:210 src/testing/unit_testing.md:1 |
| msgid "Unit testing" |
| msgstr "单元测试" |
| |
| #: src/SUMMARY.md:211 src/testing/doc_testing.md:1 |
| msgid "Documentation testing" |
| msgstr "文档测试" |
| |
| #: src/SUMMARY.md:212 src/testing/integration_testing.md:1 |
| msgid "Integration testing" |
| msgstr "集成测试" |
| |
| #: src/SUMMARY.md:213 |
| msgid "Dev-dependencies" |
| msgstr "开发依赖" |
| |
| #: src/SUMMARY.md:215 src/unsafe.md:1 |
| msgid "Unsafe Operations" |
| msgstr "不安全操作" |
| |
| #: src/SUMMARY.md:216 src/unsafe/asm.md:1 |
| msgid "Inline assembly" |
| msgstr "内联汇编" |
| |
| #: src/SUMMARY.md:218 src/compatibility.md:1 |
| msgid "Compatibility" |
| msgstr "兼容性" |
| |
| #: src/SUMMARY.md:219 src/compatibility/raw_identifiers.md:1 |
| msgid "Raw identifiers" |
| msgstr "原始标识符" |
| |
| #: src/SUMMARY.md:221 src/meta.md:1 |
| msgid "Meta" |
| msgstr "补充" |
| |
| #: src/SUMMARY.md:222 src/meta/doc.md:1 |
| msgid "Documentation" |
| msgstr "文档" |
| |
| #: src/SUMMARY.md:223 src/meta/playground.md:1 |
| msgid "Playground" |
| msgstr "Playground" |
| |
| #: src/index.md:1 |
| msgid "Rust by Example" |
| msgstr "Rust by Example" |
| |
| #: src/index.md:3 |
| msgid "" |
| "[Rust](https://www.rust-lang.org/) is a modern systems programming language " |
| "focusing on safety, speed, and concurrency. It accomplishes these goals by " |
| "being memory safe without using garbage collection." |
| msgstr "" |
| "[Rust](https://www.rust-lang.org/) 是一门现代系统编程语言，专注于安全性、速度" |
| "和并发性。通过内存安全而不使用垃圾回收来实现这些目标。" |
| |
| #: src/index.md:7 |
| msgid "" |
| "Rust by Example (RBE) is a collection of runnable examples that illustrate " |
| "various Rust concepts and standard libraries. To get even more out of these " |
| "examples, don't forget to [install Rust locally](https://www.rust-lang.org/" |
| "tools/install) and check out the [official docs](https://doc.rust-lang.org/" |
| "std/). Additionally for the curious, you can also [check out the source code " |
| "for this site](https://github.com/rust-lang/rust-by-example)." |
| msgstr "" |
| "《通过例子学 Rust》（Rust By Example, RBE）是一系列可运行的示例，它们展示了各" |
| "种 Rust 概念和标准库。为了更好地利用这些示例，请不要忘记[本地安装 Rust]" |
| "(https://www.rust-lang.org/tools/install)并查看[官方文档](https://doc.rust-" |
| "lang.org/)。此外，好奇的话，你也可以[查看这个网站的源代码](https://" |
| "github.com/rust-lang/rust-by-example)。" |
| |
| #: src/index.md:12 |
| msgid "Now let's begin!" |
| msgstr "现在让我们开始吧！" |
| |
| #: src/index.md:14 |
| msgid "[Hello World](hello.md) - Start with a traditional Hello World program." |
| msgstr "[Hello World](hello.md) - 从一个经典的 Hello World 程序开始。" |
| |
| #: src/index.md:16 |
| msgid "" |
| "[Primitives](primitives.md) - Learn about signed integers, unsigned integers " |
| "and other primitives." |
| msgstr "" |
| "[Primitives](primitives.md) - 学习有符号整数、无符号整数和其他原生类型。" |
| |
| #: src/index.md:18 |
| msgid "[Custom Types](custom_types.md) - `struct` and `enum`." |
| msgstr "[自定义类型](custom_types.md) - 结构体 `struct` 和枚举 `enum`。" |
| |
| #: src/index.md:20 |
| msgid "" |
| "[Variable Bindings](variable_bindings.md) - mutable bindings, scope, " |
| "shadowing." |
| msgstr "[变量绑定](variable_bindings.md) - 可变绑定、作用域、遮蔽。" |
| |
| #: src/index.md:22 |
| msgid "[Types](types.md) - Learn about changing and defining types." |
| msgstr "[类型](types.md) - 学习如何改变和定义类型。" |
| |
| #: src/index.md:24 |
| msgid "" |
| "[Conversion](conversion.md) - Convert between different types, such as " |
| "strings, integers, and floats." |
| msgstr "" |
| "[转换](conversion.md) - 在不同类型的数据之间进行转换，如字符串、整数和浮点" |
| "数。" |
| |
| #: src/index.md:26 |
| msgid "" |
| "[Expressions](expression.md) - Learn about Expressions & how to use them." |
| msgstr "[表达式](expression.md) - 学习表达式及其使用方法。" |
| |
| #: src/index.md:28 |
| msgid "[Flow of Control](flow_control.md) - `if`/`else`, `for`, and others." |
| msgstr "[控制流](flow_control.md) - `if`/`else`、`for` 等。" |
| |
| #: src/index.md:30 |
| msgid "" |
| "[Functions](fn.md) - Learn about Methods, Closures and Higher Order " |
| "Functions." |
| msgstr "[函数](fn.md) - 学习方法、闭包和高阶函数。" |
| |
| #: src/index.md:32 |
| msgid "[Modules](mod.md) - Organize code using modules" |
| msgstr "[模块](mod.md) - 使用模块组织代码" |
| |
| #: src/index.md:34 |
| msgid "" |
| "[Crates](crates.md) - A crate is a compilation unit in Rust. Learn to create " |
| "a library." |
| msgstr "[Crates](crates.md) - Crate 是 Rust 中的编译单元。学习如何创建库。" |
| |
| #: src/index.md:36 |
| msgid "" |
| "[Cargo](cargo.md) - Go through some basic features of the official Rust " |
| "package management tool." |
| msgstr "[Cargo](cargo.md) - 了解官方 Rust 包管理工具的一些基本功能。" |
| |
| #: src/index.md:38 |
| msgid "" |
| "[Attributes](attribute.md) - An attribute is metadata applied to some " |
| "module, crate or item." |
| msgstr "[属性](attribute.md) - 属性是应用于某些模块、crate 或项的元数据。" |
| |
| #: src/index.md:40 |
| msgid "" |
| "[Generics](generics.md) - Learn about writing a function or data type which " |
| "can work for multiple types of arguments." |
| msgstr "[泛型](generics.md) - 学习编写可以适用于多种类型参数的函数或数据类型。" |
| |
| #: src/index.md:42 |
| msgid "" |
| "[Scoping rules](scope.md) - Scopes play an important part in ownership, " |
| "borrowing, and lifetimes." |
| msgstr "" |
| "[作用域规则](scope.md) - 作用域在所有权（ownership）、借用（borrowing）和生命" |
| "周期（lifetime）中扮演重要角色。" |
| |
| #: src/index.md:44 |
| msgid "" |
| "[Traits](trait.md) - A trait is a collection of methods defined for an " |
| "unknown type: `Self`" |
| msgstr "[特质](trait.md) - 特质（trait）是为未知类型 `Self` 定义的一组方法。" |
| |
| #: src/index.md:46 |
| msgid "" |
| "[Macros](macros.md) - Macros are a way of writing code that writes other " |
| "code, which is known as metaprogramming." |
| msgstr "" |
| "[宏](macros.md) - 宏是一种编写代码以生成其他代码的方式，也被称为元编程。" |
| |
| #: src/index.md:48 |
| msgid "[Error handling](error.md) - Learn Rust way of handling failures." |
| msgstr "[错误处理](error.md) - 学习 Rust 处理失败的方式。" |
| |
| #: src/index.md:50 |
| msgid "" |
| "[Std library types](std.md) - Learn about some custom types provided by " |
| "`std` library." |
| msgstr "[标准库类型](std.md) - 学习 `std` 标准库提供的一些自定义类型。" |
| |
| #: src/index.md:52 |
| msgid "[Std misc](std_misc.md) - More custom types for file handling, threads." |
| msgstr "" |
| "[标准库中的其他内容](std_misc.md) - 更多关于文件处理、线程的自定义类型。" |
| |
| #: src/index.md:54 |
| msgid "[Testing](testing.md) - All sorts of testing in Rust." |
| msgstr "[测试](testing.md) - Rust 中的各种测试方法。" |
| |
| #: src/index.md:56 |
| msgid "" |
| "[Unsafe Operations](unsafe.md) - Learn about entering a block of unsafe " |
| "operations." |
| msgstr "[不安全操作](unsafe.md) - 学习如何编写和使用不安全代码块。" |
| |
| #: src/index.md:58 |
| msgid "" |
| "[Compatibility](compatibility.md) - Handling Rust's evolution and potential " |
| "compatibility issues." |
| msgstr "" |
| "[兼容性](compatibility.md) - 应对 Rust 语言的演进及可能出现的兼容性问题。" |
| |
| #: src/index.md:60 |
| msgid "[Meta](meta.md) - Documentation, Benchmarking." |
| msgstr "[补充](meta.md) - 文档，基准测试。" |
| |
| #: src/hello.md:3 |
| msgid "This is the source code of the traditional Hello World program." |
| msgstr "这是经典的 Hello World 程序的源代码。" |
| |
| #: src/hello.md:6 |
| msgid "" |
| "// This is a comment, and is ignored by the compiler.\n" |
| "// You can test this code by clicking the \"Run\" button over there ->\n" |
| "// or if you prefer to use your keyboard, you can use the \"Ctrl + Enter\"\n" |
| "// shortcut.\n" |
| msgstr "" |
| "// 这是一行注释，编译器会忽略它。\n" |
| "// 你可以点击右侧的 \"Run\" 按钮来测试这段代码 ->\n" |
| "// 如果你更习惯使用键盘，也可以使用\"Ctrl + Enter\"快捷键来运行。\n" |
| |
| #: src/hello.md:10 |
| msgid "" |
| "// This code is editable, feel free to hack it!\n" |
| "// You can always return to the original code by clicking the \"Reset\" " |
| "button ->\n" |
| msgstr "" |
| "// 这段代码是可以编辑的，请随意修改！\n" |
| "// 你可以随时点击 \"Reset\" 按钮恢复到初始代码 ->\n" |
| |
| #: src/hello.md:13 |
| msgid "// This is the main function.\n" |
| msgstr "// 这是主函数。\n" |
| |
| #: src/hello.md:16 |
| msgid "// Statements here are executed when the compiled binary is called.\n" |
| msgstr "// 当运行编译后的程序时，这里的语句会被执行。\n" |
| |
| #: src/hello.md:18 |
| msgid "// Print text to the console.\n" |
| msgstr "// 在控制台打印文本。\n" |
| |
| #: src/hello.md:19 src/error/result.md:55 src/meta/playground.md:12 |
| msgid "\"Hello World!\"" |
| msgstr "\"Hello World!\"" |
| |
| #: src/hello.md:23 |
| msgid "`println!` is a [_macro_](macros.md) that prints text to the console." |
| msgstr "`println!` 是一个用于在控制台打印文本的[宏](macros.md)。" |
| |
| #: src/hello.md:26 |
| msgid "A binary can be generated using the Rust compiler: `rustc`." |
| msgstr "可以使用 Rust 编译器 `rustc` 来生成可执行文件。" |
| |
| #: src/hello.md:32 |
| msgid "`rustc` will produce a `hello` binary that can be executed." |
| msgstr "`rustc` 将生成一个名为 `hello` 的可执行文件。" |
| |
| #: src/hello.md:39 src/hello/print/print_display.md:107 |
| #: src/hello/print/print_display/testcase_list.md:53 src/hello/print/fmt.md:70 |
| #: src/primitives/tuples.md:64 src/custom_types/structs.md:89 |
| msgid "Activity" |
| msgstr "练习" |
| |
| #: src/hello.md:41 |
| msgid "" |
| "Click 'Run' above to see the expected output. Next, add a new line with a " |
| "second `println!` macro so that the output shows:" |
| msgstr "" |
| "点击上方的\"运行\"按钮查看预期输出。接下来，添加一行新代码，再次使用 " |
| "`println!` 宏，输出显示如下内容：" |
| |
| #: src/hello/comment.md:3 |
| msgid "" |
| "Any program requires comments, and Rust supports a few different varieties:" |
| msgstr "每个程序都需要注释，Rust 支持几种不同类型的注释：" |
| |
| #: src/hello/comment.md:6 |
| msgid "_Regular comments_ which are ignored by the compiler:" |
| msgstr "**普通注释**：编译器会忽略这些注释" |
| |
| #: src/hello/comment.md:7 |
| msgid "`// Line comments which go to the end of the line.`" |
| msgstr "`// 行注释，从双斜杠开始到行尾。`" |
| |
| #: src/hello/comment.md:8 |
| msgid "`/* Block comments which go to the closing delimiter. */`" |
| msgstr "`/* 块注释，从开始符号到结束符号。 */`" |
| |
| #: src/hello/comment.md:9 |
| msgid "" |
| "_Doc comments_ which are parsed into HTML library [documentation](../meta/" |
| "doc.md):" |
| msgstr "**文档注释**：这些注释会被解析成 HTML 格式的[库文档](../meta/doc.md)" |
| |
| #: src/hello/comment.md:10 |
| msgid "`/// Generate library docs for the following item.`" |
| msgstr "`/// 为接下来的项生成库文档。`" |
| |
| #: src/hello/comment.md:11 |
| msgid "`//! Generate library docs for the enclosing item.`" |
| msgstr "`//! 为当前项（如 crate、模块或函数）生成库文档。`" |
| |
| #: src/hello/comment.md:15 |
| msgid "" |
| "// This is an example of a line comment.\n" |
| " // There are two slashes at the beginning of the line.\n" |
| " // And nothing written after these will be read by the compiler.\n" |
| msgstr "" |
| "// 这是行注释的一个例子。\n" |
| " // 在行首有两个斜杠。\n" |
| " // 斜杠后面的内容编译器不会读取。\n" |
| |
| #: src/hello/comment.md:19 |
| msgid "// println!(\"Hello, world!\");\n" |
| msgstr "// println!(\"Hello, world!\");\n" |
| |
| #: src/hello/comment.md:21 |
| msgid "// Run it. See? Now try deleting the two slashes, and run it again.\n" |
| msgstr "// 运行看看。明白了吗？现在试着删除这两个斜杠，再运行一次。\n" |
| |
| #: src/hello/comment.md:23 |
| msgid "" |
| "/*\n" |
| " * This is another type of comment, a block comment. In general,\n" |
| " * line comments are the recommended comment style. But block comments\n" |
| " * are extremely useful for temporarily disabling chunks of code.\n" |
| " * /* Block comments can be /* nested, */ */ so it takes only a few\n" |
| " * keystrokes to comment out everything in this main() function.\n" |
| " * /*/*/* Try it yourself! */*/*/\n" |
| " */" |
| msgstr "" |
| "/*\n" |
| " * 这是另一种类型的注释，称为块注释。一般来说，推荐使用行注释。\n" |
| " * 但是块注释在临时禁用大段代码时非常有用。\n" |
| " * /* 块注释可以 /* 嵌套， */ */ 因此只需几次按键就能\n" |
| " * 注释掉 main() 函数中的所有内容。\n" |
| " * /*/*/* 你可以自己试试！ */*/*/\n" |
| " */" |
| |
| #: src/hello/comment.md:32 |
| msgid "" |
| "/*\n" |
| " Note: The previous column of `*` was entirely for style. There's\n" |
| " no actual need for it.\n" |
| " */" |
| msgstr "" |
| "/*\n" |
| " 注意：前面的 `*` 列纯粹是为了样式美观。实际上并不需要。\n" |
| " */" |
| |
| #: src/hello/comment.md:37 |
| msgid "" |
| "// Here's another powerful use of block comments: you can uncomment\n" |
| " // and comment a whole block by simply adding or removing a single\n" |
| " // '/' character:\n" |
| msgstr "" |
| "// 这里展示块注释的另一个强大用途：你可以通过添加或删除单个\n" |
| " // '/' 字符来取消注释或注释整个代码块：\n" |
| |
| #: src/hello/comment.md:41 |
| msgid "" |
| "/* <- add another '/' before the 1st one to uncomment the whole block\n" |
| "\n" |
| " println!(\"Now\");\n" |
| " println!(\"everything\");\n" |
| " println!(\"executes!\");\n" |
| " // line comments inside are not affected by either state\n" |
| "\n" |
| " // */" |
| msgstr "" |
| "/* <- 在第一个字符前再添加一个 '/' 来取消注释整个代码块\n" |
| "\n" |
| " println!(\"Now\");\n" |
| " println!(\"everything\");\n" |
| " println!(\"executes!\");\n" |
| " // 内部的行注释不受任何状态影响\n" |
| "\n" |
| " // */" |
| |
| #: src/hello/comment.md:50 |
| msgid "" |
| "// You can manipulate expressions more easily with block comments\n" |
| " // than with line comments. Try deleting the comment delimiters\n" |
| " // to change the result:\n" |
| msgstr "" |
| "// 块注释比行注释更方便地操作表达式\n" |
| " // 试试删除注释符号，看看结果会有什么变化：\n" |
| |
| #: src/hello/comment.md:53 |
| msgid "/* 90 + */" |
| msgstr "/* 90 + */" |
| |
| #: src/hello/comment.md:54 |
| msgid "\"Is `x` 10 or 100? x = {}\"" |
| msgstr "\"`x` 是 10 还是 100？x = {}\"" |
| |
| #: src/hello/comment.md:58 src/hello/print.md:103 |
| #: src/hello/print/print_debug.md:75 src/hello/print/print_display.md:118 |
| #: src/hello/print/print_display/testcase_list.md:62 src/hello/print/fmt.md:89 |
| #: src/primitives.md:64 src/custom_types/enum.md:100 |
| #: src/custom_types/enum/enum_use.md:45 src/custom_types/enum/c_like.md:33 |
| #: src/custom_types/enum/testcase_linked_list.md:78 |
| #: src/custom_types/constants.md:35 src/types/alias.md:30 |
| #: src/flow_control/for.md:121 |
| #: src/flow_control/match/destructuring/destructure_tuple.md:25 |
| #: src/flow_control/match/destructuring/destructure_slice.md:46 |
| #: src/flow_control/match/destructuring/destructure_enum.md:48 |
| #: src/flow_control/match/destructuring/destructure_pointers.md:63 |
| #: src/flow_control/match/destructuring/destructure_structures.md:45 |
| #: src/flow_control/match/guard.md:43 src/flow_control/match/binding.md:49 |
| #: src/flow_control/if_let.md:118 src/flow_control/let_else.md:55 |
| #: src/flow_control/while_let.md:56 src/fn/closures/capture.md:110 |
| #: src/fn/closures/input_parameters.md:84 src/fn/closures/anonymity.md:47 |
| #: src/fn/closures/input_functions.md:32 |
| #: src/fn/closures/output_parameters.md:49 |
| #: src/fn/closures/closure_examples/iter_any.md:50 |
| #: src/fn/closures/closure_examples/iter_find.md:68 |
| #: src/mod/struct_visibility.md:53 src/attribute/cfg.md:39 src/generics.md:59 |
| #: src/generics/gen_fn.md:54 src/generics/impl.md:48 |
| #: src/generics/gen_trait.md:39 src/generics/bounds.md:73 |
| #: src/generics/bounds/testcase_empty.md:37 src/generics/multi_bounds.md:32 |
| #: src/generics/where.md:49 src/generics/new_types.md:54 |
| #: src/generics/assoc_items.md:10 src/generics/assoc_items/the_problem.md:62 |
| #: src/generics/phantom.md:56 src/generics/phantom/testcase_units.md:75 |
| #: src/scope/raii.md:92 src/scope/move/partial_move.md:57 |
| #: src/scope/borrow/mut.md:56 src/scope/lifetime/explicit.md:68 |
| #: src/scope/lifetime/fn.md:58 src/scope/lifetime/methods.md:24 |
| #: src/scope/lifetime/struct.md:41 src/scope/lifetime/trait.md:28 |
| #: src/scope/lifetime/lifetime_bounds.md:46 |
| #: src/scope/lifetime/static_lifetime.md:133 src/scope/lifetime/elision.md:39 |
| #: src/trait/derive.md:65 src/trait/supertraits.md:40 |
| #: src/trait/disambiguating.md:60 src/error/option_unwrap/map.md:79 |
| #: src/error/option_unwrap/and_then.md:73 |
| #: src/error/option_unwrap/defaults.md:115 src/error/result/result_alias.md:41 |
| #: src/error/multiple_error_types/boxing_errors.md:57 |
| #: src/error/multiple_error_types/reenter_question_mark.md:74 |
| #: src/error/multiple_error_types/wrap_error.md:91 src/std.md:12 |
| #: src/std/rc.md:55 src/std_misc.md:12 |
| #: src/std_misc/threads/testcase_mapreduce.md:129 src/std_misc/path.md:54 |
| #: src/std_misc/fs.md:150 src/meta/doc.md:109 src/meta/playground.md:49 |
| msgid "See also:" |
| msgstr "另请参阅：" |
| |
| #: src/hello/comment.md:60 |
| msgid "[Library documentation](../meta/doc.md)" |
| msgstr "[库文档](../meta/doc.md)" |
| |
| #: src/hello/print.md:3 |
| msgid "" |
| "Printing is handled by a series of [`macros`](../macros.md) defined in " |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/) some of which are:" |
| msgstr "" |
| "打印功能由 [`std::fmt`](https://doc.rust-lang.org/std/fmt/) 中定义的一系列[`" |
| "宏`](../macros.md)处理，其中包括：" |
| |
| #: src/hello/print.md:6 |
| msgid "`format!`: write formatted text to [`String`](../std/str.md)" |
| msgstr "`format!`：将格式化文本写入 [`String`](../std/str.md)" |
| |
| #: src/hello/print.md:7 |
| msgid "" |
| "`print!`: same as `format!` but the text is printed to the console " |
| "(io::stdout)." |
| msgstr "`print!`：与 `format!` 类似，但文本会打印到控制台（io::stdout）" |
| |
| #: src/hello/print.md:9 |
| msgid "`println!`: same as `print!` but a newline is appended." |
| msgstr "`println!`：与 `print!` 类似，但会在末尾添加换行符" |
| |
| #: src/hello/print.md:10 |
| msgid "" |
| "`eprint!`: same as `print!` but the text is printed to the standard error " |
| "(io::stderr)." |
| msgstr "`eprint!`：与 `print!` 类似，但文本会打印到标准错误输出（io::stderr）" |
| |
| #: src/hello/print.md:12 |
| msgid "`eprintln!`: same as `eprint!` but a newline is appended." |
| msgstr "`eprintln!`：与 `eprint!` 类似，但会在末尾添加换行符" |
| |
| #: src/hello/print.md:14 |
| msgid "" |
| "All parse text in the same fashion. As a plus, Rust checks formatting " |
| "correctness at compile time." |
| msgstr "" |
| "所有这些宏都以相同的方式解析文本。此外，Rust 会在编译时检查格式化的正确性。" |
| |
| #: src/hello/print.md:19 |
| msgid "" |
| "// In general, the `{}` will be automatically replaced with any\n" |
| " // arguments. These will be stringified.\n" |
| msgstr "" |
| "// 通常，`{}` 会被自动替换为任何参数。\n" |
| " // 这些参数会被转换为字符串。\n" |
| |
| #: src/hello/print.md:21 |
| msgid "\"{} days\"" |
| msgstr "\"{} 天\"" |
| |
| #: src/hello/print.md:23 |
| msgid "" |
| "// Positional arguments can be used. Specifying an integer inside `{}`\n" |
| " // determines which additional argument will be replaced. Arguments " |
| "start\n" |
| " // at 0 immediately after the format string.\n" |
| msgstr "" |
| "// 可以使用位置参数。在 `{}` 中指定一个整数\n" |
| " // 来决定替换哪个额外的参数。参数编号\n" |
| " // 从格式字符串后立即开始，从 0 开始。\n" |
| |
| #: src/hello/print.md:26 |
| msgid "\"{0}, this is {1}. {1}, this is {0}\"" |
| msgstr "\"{0}，这是 {1}。{1}，这是 {0}\"" |
| |
| #: src/hello/print.md:26 src/scope/move/partial_move.md:31 |
| msgid "\"Alice\"" |
| msgstr "\"Alice\"" |
| |
| #: src/hello/print.md:26 src/flow_control/for.md:65 src/flow_control/for.md:85 |
| #: src/flow_control/for.md:104 |
| msgid "\"Bob\"" |
| msgstr "\"Bob\"" |
| |
| #: src/hello/print.md:28 |
| msgid "// As can named arguments.\n" |
| msgstr "// 还可以使用命名参数。\n" |
| |
| #: src/hello/print.md:29 |
| msgid "\"{subject} {verb} {object}\"" |
| msgstr "\"{subject} {verb} {object}\"" |
| |
| #: src/hello/print.md:30 |
| msgid "\"the lazy dog\"" |
| msgstr "\"那只懒惰的狗\"" |
| |
| #: src/hello/print.md:31 |
| msgid "\"the quick brown fox\"" |
| msgstr "\"那只敏捷的棕色狐狸\"" |
| |
| #: src/hello/print.md:32 |
| msgid "\"jumps over\"" |
| msgstr "\"跳过\"" |
| |
| #: src/hello/print.md:34 |
| msgid "" |
| "// Different formatting can be invoked by specifying the format character\n" |
| " // after a `:`.\n" |
| msgstr "" |
| "// 在 `:` 后指定格式字符，\n" |
| " // 可以调用不同的格式化方式。\n" |
| |
| #: src/hello/print.md:36 |
| msgid "\"Base 10: {}\"" |
| msgstr "\"十进制： {}\"" |
| |
| #: src/hello/print.md:36 |
| msgid "// 69420\n" |
| msgstr "// 69420\n" |
| |
| #: src/hello/print.md:37 |
| msgid "\"Base 2 (binary): {:b}\"" |
| msgstr "\"二进制： {:b}\"" |
| |
| #: src/hello/print.md:37 |
| msgid "// 10000111100101100\n" |
| msgstr "// 10000111100101100\n" |
| |
| #: src/hello/print.md:38 |
| msgid "\"Base 8 (octal): {:o}\"" |
| msgstr "\"八进制： {:o}\"" |
| |
| #: src/hello/print.md:38 |
| msgid "// 207454\n" |
| msgstr "// 207454\n" |
| |
| #: src/hello/print.md:39 |
| msgid "\"Base 16 (hexadecimal): {:x}\"" |
| msgstr "\"十六进制： {:x}\"" |
| |
| #: src/hello/print.md:39 |
| msgid "// 10f2c\n" |
| msgstr "// 10f2c\n" |
| |
| #: src/hello/print.md:41 |
| msgid "" |
| "// You can right-justify text with a specified width. This will\n" |
| " // output \" 1\". (Four white spaces and a \"1\", for a total width " |
| "of 5.)\n" |
| msgstr "" |
| "// 可以指定宽度来右对齐文本。这将输出\n" |
| " // \" 1\"。（四个空格和一个 \"1\"，总宽度为 5。）\n" |
| |
| #: src/hello/print.md:43 |
| msgid "\"{number:>5}\"" |
| msgstr "\"{number:>5}\"" |
| |
| #: src/hello/print.md:45 |
| msgid "// You can pad numbers with extra zeroes,\n" |
| msgstr "// 可以用额外的零来填充数字，\n" |
| |
| #: src/hello/print.md:46 |
| msgid "\"{number:0>5}\"" |
| msgstr "\"{number:0>5}\"" |
| |
| #: src/hello/print.md:46 |
| msgid "" |
| "// 00001\n" |
| " // and left-adjust by flipping the sign. This will output \"10000\".\n" |
| msgstr "" |
| "// 00001\n" |
| " // 通过翻转符号来左对齐。这将输出 \"10000\"。\n" |
| |
| #: src/hello/print.md:48 |
| msgid "\"{number:0<5}\"" |
| msgstr "\"{number:0<5}\"" |
| |
| #: src/hello/print.md:48 |
| msgid "// 10000\n" |
| msgstr "// 10000\n" |
| |
| #: src/hello/print.md:50 |
| msgid "" |
| "// You can use named arguments in the format specifier by appending a `$`.\n" |
| msgstr "// 在格式说明符后添加 `$` 可以使用命名参数。\n" |
| |
| #: src/hello/print.md:51 |
| msgid "\"{number:0>width$}\"" |
| msgstr "\"{number:0>width$}\"" |
| |
| #: src/hello/print.md:53 |
| msgid "" |
| "// Rust even checks to make sure the correct number of arguments are used.\n" |
| msgstr "// Rust 甚至会检查使用的参数数量是否正确。\n" |
| |
| #: src/hello/print.md:54 |
| msgid "\"My name is {0}, {1} {0}\"" |
| msgstr "\"我的名字是 {0}，{1} {0}\"" |
| |
| #: src/hello/print.md:54 |
| msgid "\"Bond\"" |
| msgstr "\"Bond\"" |
| |
| #: src/hello/print.md:55 |
| msgid "// FIXME ^ Add the missing argument: \"James\"\n" |
| msgstr "// FIXME ^ 添加缺失的参数：\"James\"\n" |
| |
| #: src/hello/print.md:57 |
| msgid "" |
| "// Only types that implement fmt::Display can be formatted with `{}`. User-\n" |
| " // defined types do not implement fmt::Display by default.\n" |
| msgstr "" |
| "// 只有实现了 fmt::Display 的类型才能用 `{}` 格式化。\n" |
| " // 用户定义的类型默认不实现 fmt::Display。\n" |
| |
| #: src/hello/print.md:60 |
| msgid "// disable `dead_code` which warn against unused module\n" |
| msgstr "// 禁用 `dead_code`，它会警告未使用的模块\n" |
| |
| #: src/hello/print.md:63 |
| msgid "" |
| "// This will not compile because `Structure` does not implement\n" |
| " // fmt::Display.\n" |
| " // println!(\"This struct `{}` won't print...\", Structure(3));\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 这无法编译，因为 `Structure` 没有实现 fmt::Display。\n" |
| " // println!(\"这个结构体 `{}` 无法打印...\", Structure(3));\n" |
| " // TODO ^ 尝试取消注释这一行\n" |
| |
| #: src/hello/print.md:68 |
| msgid "" |
| "// For Rust 1.58 and above, you can directly capture the argument from a\n" |
| " // surrounding variable. Just like the above, this will output\n" |
| " // \" 1\", 4 white spaces and a \"1\".\n" |
| msgstr "" |
| "// 在 Rust 1.58 及以上版本，你可以直接从周围的变量捕获参数。\n" |
| " // 就像上面一样，这将输出 \" 1\"，4 个空格和一个 \"1\"。\n" |
| |
| #: src/hello/print.md:73 |
| msgid "\"{number:>width$}\"" |
| msgstr "\"{number:>width$}\"" |
| |
| #: src/hello/print.md:77 |
| msgid "" |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/) contains many [`traits`]" |
| "(https://doc.rust-lang.org/std/fmt/#formatting-traits) which govern the " |
| "display of text. The base form of two important ones are listed below:" |
| msgstr "" |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/) 包含许多控制文本显示的 " |
| "[`traits`](https://doc.rust-lang.org/std/fmt/#formatting-traits)。下面列出了" |
| "两个重要的基本形式：" |
| |
| #: src/hello/print.md:80 |
| msgid "" |
| "`fmt::Debug`: Uses the `{:?}` marker. Format text for debugging purposes." |
| msgstr "`fmt::Debug`: 使用 `{:?}` 标记。用于调试目的的文本格式化。" |
| |
| #: src/hello/print.md:81 |
| msgid "" |
| "`fmt::Display`: Uses the `{}` marker. Format text in a more elegant, user " |
| "friendly fashion." |
| msgstr "`fmt::Display`: 使用 `{}` 标记。以更优雅、用户友好的方式格式化文本。" |
| |
| #: src/hello/print.md:84 |
| msgid "" |
| "Here, we used `fmt::Display` because the std library provides " |
| "implementations for these types. To print text for custom types, more steps " |
| "are required." |
| msgstr "" |
| "这里我们使用 `fmt::Display`，因为标准库为这些类型提供了实现。要打印自定义类型" |
| "的文本，需要额外的步骤。" |
| |
| #: src/hello/print.md:87 |
| msgid "" |
| "Implementing the `fmt::Display` trait automatically implements the " |
| "[`ToString`](https://doc.rust-lang.org/std/string/trait.ToString.html) trait " |
| "which allows us to [convert](../conversion/string.md) the type to [`String`]" |
| "(../std/str.md)." |
| msgstr "" |
| "实现 `fmt::Display` 特性会自动实现 [`ToString`](https://doc.rust-lang.org/" |
| "std/string/trait.ToString.html) 特性，这允许我们将该类型[转换](../conversion/" |
| "string.md)为[`String`](../std/str.md)。" |
| |
| #: src/hello/print.md:90 |
| msgid "" |
| "In _line 43_, `#[allow(dead_code)]` is an [attribute](../attribute.md) which " |
| "only applies to the module after it." |
| msgstr "" |
| "在 _43 行_，`#[allow(dead_code)]`是一个 [属性(attribute)](../attribute.md)，" |
| "它只适用于它之后的模块。" |
| |
| #: src/hello/print.md:92 |
| msgid "Activities" |
| msgstr "练习" |
| |
| #: src/hello/print.md:94 |
| msgid "" |
| "Fix the issue in the above code (see FIXME) so that it runs without error." |
| msgstr "修复上述代码中的问题（参见 FIXME 注释），使其能够正常运行。" |
| |
| #: src/hello/print.md:96 |
| msgid "" |
| "Try uncommenting the line that attempts to format the `Structure` struct " |
| "(see TODO)" |
| msgstr "尝试取消注释那行尝试格式化 `Structure` 结构体的代码（参见 TODO 注释）" |
| |
| #: src/hello/print.md:98 |
| msgid "" |
| "Add a `println!` macro call that prints: `Pi is roughly 3.142` by " |
| "controlling the number of decimal places shown. For the purposes of this " |
| "exercise, use `let pi = 3.141592` as an estimate for pi. (Hint: you may need " |
| "to check the [`std::fmt`](https://doc.rust-lang.org/std/fmt/) documentation " |
| "for setting the number of decimals to display)" |
| msgstr "" |
| "添加一个 `println!` 宏调用，打印：`Pi 约等于 3.142`，通过控制显示的小数位数来" |
| "实现。\n" |
| "在本练习中，使用 `let pi = 3.141592` 作为 pi 的近似值。（提示：你可能需要查" |
| "阅\n" |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/) 文档来了解如何设置显示的小数" |
| "位数）" |
| |
| #: src/hello/print.md:105 |
| msgid "" |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/), [`macros`](../macros.md), " |
| "[`struct`](../custom_types/structs.md), [`traits`](https://doc.rust-lang.org/" |
| "std/fmt/#formatting-traits), and [`dead_code`](../attribute/unused.md)" |
| msgstr "" |
| "[`std::fmt`](https://doc.rust-lang.org/std/fmt/)、[`macros`](../" |
| "macros.md)、\n" |
| "[`struct`](../custom_types/structs.md)、[`traits`](https://doc.rust-lang.org/" |
| "std/fmt/#formatting-traits) 和 [`dead_code`](../attribute/unused.md)" |
| |
| #: src/hello/print/print_debug.md:3 |
| msgid "" |
| "All types which want to use `std::fmt` formatting `traits` require an " |
| "implementation to be printable. Automatic implementations are only provided " |
| "for types such as in the `std` library. All others _must_ be manually " |
| "implemented somehow." |
| msgstr "" |
| "所有想要使用 `std::fmt` 格式化 `traits` 的类型都需要实现才能打印。\n" |
| "自动实现仅为 `std` 库中的类型提供。所有其他类型都**必须**以某种方式手动实现。" |
| |
| #: src/hello/print/print_debug.md:8 |
| msgid "" |
| "The `fmt::Debug` `trait` makes this very straightforward. _All_ types can " |
| "`derive` (automatically create) the `fmt::Debug` implementation. This is not " |
| "true for `fmt::Display` which must be manually implemented." |
| msgstr "" |
| "`fmt::Debug` trait 使这变得非常简单。**所有**类型都可以 `derive`（自动创" |
| "建）\n" |
| "`fmt::Debug` 实现。但这对 `fmt::Display` 不适用，后者必须手动实现。" |
| |
| #: src/hello/print/print_debug.md:13 |
| msgid "" |
| "// This structure cannot be printed either with `fmt::Display` or\n" |
| "// with `fmt::Debug`.\n" |
| msgstr "// 这个结构体无法通过 `fmt::Display` 或 `fmt::Debug` 打印。\n" |
| |
| #: src/hello/print/print_debug.md:16 |
| msgid "" |
| "// The `derive` attribute automatically creates the implementation\n" |
| "// required to make this `struct` printable with `fmt::Debug`.\n" |
| msgstr "" |
| "// `derive` 属性自动创建使这个 `struct` 可以用 `fmt::Debug` 打印的实现。\n" |
| |
| #: src/hello/print/print_debug.md:23 |
| msgid "All `std` library types are automatically printable with `{:?}` too:" |
| msgstr "所有 `std` 库类型也可以自动使用 `{:?}` 打印：" |
| |
| #: src/hello/print/print_debug.md:26 |
| msgid "" |
| "// Derive the `fmt::Debug` implementation for `Structure`. `Structure`\n" |
| "// is a structure which contains a single `i32`.\n" |
| msgstr "" |
| "// 为 `Structure` 派生 `fmt::Debug` 实现。`Structure` 是一个包含单个 `i32` 的" |
| "结构体。\n" |
| |
| #: src/hello/print/print_debug.md:30 |
| msgid "" |
| "// Put a `Structure` inside of the structure `Deep`. Make it printable\n" |
| "// also.\n" |
| msgstr "// 在 `Deep` 结构体中放入一个 `Structure`。使其也可打印。\n" |
| |
| #: src/hello/print/print_debug.md:37 |
| msgid "// Printing with `{:?}` is similar to with `{}`.\n" |
| msgstr "// 使用 `{:?}` 打印类似于使用 `{}`。\n" |
| |
| #: src/hello/print/print_debug.md:38 |
| msgid "\"{:?} months in a year.\"" |
| msgstr "\"{:?} 个月在一年中。\"" |
| |
| #: src/hello/print/print_debug.md:39 |
| msgid "\"{1:?} {0:?} is the {actor:?} name.\"" |
| msgstr "\"{1:?} {0:?} 是这个 {actor:?} 的名字。\"" |
| |
| #: src/hello/print/print_debug.md:40 |
| msgid "\"Slater\"" |
| msgstr "\"Slater\"" |
| |
| #: src/hello/print/print_debug.md:41 |
| msgid "\"Christian\"" |
| msgstr "\"Christian\"" |
| |
| #: src/hello/print/print_debug.md:42 |
| msgid "\"actor's\"" |
| msgstr "\"演员\"" |
| |
| #: src/hello/print/print_debug.md:44 |
| msgid "// `Structure` is printable!\n" |
| msgstr "// `Structure` 现在可以打印了！\n" |
| |
| #: src/hello/print/print_debug.md:45 src/hello/print/print_debug.md:49 |
| msgid "\"Now {:?} will print!\"" |
| msgstr "\"现在 {:?} 将会打印！\"" |
| |
| #: src/hello/print/print_debug.md:47 |
| msgid "" |
| "// The problem with `derive` is there is no control over how\n" |
| " // the results look. What if I want this to just show a `7`?\n" |
| msgstr "" |
| "// `derive` 的问题是无法控制输出的样式。\n" |
| " // 如果我只想显示一个 `7` 怎么办？\n" |
| |
| #: src/hello/print/print_debug.md:53 |
| msgid "" |
| "So `fmt::Debug` definitely makes this printable but sacrifices some " |
| "elegance. Rust also provides \"pretty printing\" with `{:#?}`." |
| msgstr "" |
| "所以 `fmt::Debug` 确实使其可打印，但牺牲了一些优雅。\n" |
| "Rust 还提供了使用 `{:#?}` 进行\"美化打印\"的功能。" |
| |
| #: src/hello/print/print_debug.md:64 src/custom_types/structs.md:42 |
| msgid "\"Peter\"" |
| msgstr "\"Peter\"" |
| |
| #: src/hello/print/print_debug.md:68 |
| msgid "// Pretty print\n" |
| msgstr "// 美化打印\n" |
| |
| #: src/hello/print/print_debug.md:69 |
| msgid "\"{:#?}\"" |
| msgstr "\"{:#?}\"" |
| |
| #: src/hello/print/print_debug.md:73 |
| msgid "One can manually implement `fmt::Display` to control the display." |
| msgstr "可以手动实现 `fmt::Display` 来控制显示方式。" |
| |
| #: src/hello/print/print_debug.md:77 |
| msgid "" |
| "[`attributes`](https://doc.rust-lang.org/reference/attributes.html), " |
| "[`derive`](../../trait/derive.md), [`std::fmt`](https://doc.rust-lang.org/" |
| "std/fmt/), and [`struct`](../../custom_types/structs.md)" |
| msgstr "" |
| "[`attributes`](https://doc.rust-lang.org/reference/attributes.html)、\n" |
| "[`derive`](../../trait/derive.md)、[`std::fmt`](https://doc.rust-lang.org/" |
| "std/fmt/) \n" |
| "和 [`struct`](../../custom_types/structs.md)" |
| |
| #: src/hello/print/print_display.md:3 |
| msgid "" |
| "`fmt::Debug` hardly looks compact and clean, so it is often advantageous to " |
| "customize the output appearance. This is done by manually implementing " |
| "[`fmt::Display`](https://doc.rust-lang.org/std/fmt/), which uses the `{}` " |
| "print marker. Implementing it looks like this:" |
| msgstr "" |
| "`fmt::Debug` 的输出往往不够简洁清晰，因此自定义输出外观通常更有优势。\n" |
| "这可以通过手动实现 [`fmt::Display`](https://doc.rust-lang.org/std/fmt/) 来完" |
| "成，\n" |
| "它使用 `{}` 打印标记。实现方式如下：" |
| |
| #: src/hello/print/print_display.md:9 |
| msgid "// Import (via `use`) the `fmt` module to make it available.\n" |
| msgstr "// 通过 `use` 导入 `fmt` 模块使其可用。\n" |
| |
| #: src/hello/print/print_display.md:11 |
| msgid "" |
| "// Define a structure for which `fmt::Display` will be implemented. This is\n" |
| "// a tuple struct named `Structure` that contains an `i32`.\n" |
| msgstr "" |
| "// 定义一个结构体，我们将为其实现 `fmt::Display`。\n" |
| "// 这是一个名为 `Structure` 的元组结构体，包含一个 `i32`。\n" |
| |
| #: src/hello/print/print_display.md:15 |
| msgid "" |
| "// To use the `{}` marker, the trait `fmt::Display` must be implemented\n" |
| "// manually for the type.\n" |
| msgstr "// 要使用 `{}` 标记，必须为该类型手动实现 `fmt::Display` trait。\n" |
| |
| #: src/hello/print/print_display.md:19 |
| msgid "// This trait requires `fmt` with this exact signature.\n" |
| msgstr "// 这个 trait 要求 `fmt` 方法具有确切的签名。\n" |
| |
| #: src/hello/print/print_display.md:21 |
| msgid "" |
| "// Write strictly the first element into the supplied output\n" |
| " // stream: `f`. Returns `fmt::Result` which indicates whether the\n" |
| " // operation succeeded or failed. Note that `write!` uses syntax " |
| "which\n" |
| " // is very similar to `println!`.\n" |
| msgstr "" |
| "// 将第一个元素严格写入提供的输出流 `f`。\n" |
| " // 返回 `fmt::Result`，表示操作是否成功。\n" |
| " // 注意 `write!` 的语法与 `println!` 非常相似。\n" |
| |
| #: src/hello/print/print_display.md:25 |
| #: src/hello/print/print_display/testcase_list.md:13 |
| #: src/hello/print/print_display/testcase_list.md:39 |
| #: src/hello/print/print_display/testcase_list.md:49 src/hello/print/fmt.md:53 |
| #: src/custom_types/enum/testcase_linked_list.md:74 src/conversion/string.md:25 |
| #: src/flow_control/loop.md:26 src/flow_control/while.md:21 |
| #: src/flow_control/for.md:23 src/flow_control/for.md:43 src/fn.md:40 |
| #: src/fn/closures/capture.md:96 src/fn/closures/capture.md:97 |
| #: src/fn/closures/anonymity.md:41 src/generics/bounds.md:12 |
| #: src/macros/repeat.md:24 src/macros/repeat.md:25 src/macros/repeat.md:26 |
| #: src/error/result.md:73 src/std/str.md:92 src/std/str.md:102 |
| #: src/std/str.md:106 src/std/str.md:111 src/std/result.md:72 |
| #: src/std/result/question_mark.md:57 src/std/result/question_mark.md:65 |
| #: src/std_misc/file/read_lines.md:60 src/std_misc/arg/matching.md:9 |
| #: src/std_misc/arg/matching.md:13 |
| msgid "\"{}\"" |
| msgstr "\"{}\"" |
| |
| #: src/hello/print/print_display.md:30 |
| msgid "" |
| "`fmt::Display` may be cleaner than `fmt::Debug` but this presents a problem " |
| "for the `std` library. How should ambiguous types be displayed? For example, " |
| "if the `std` library implemented a single style for all `Vec<T>`, what style " |
| "should it be? Would it be either of these two?" |
| msgstr "" |
| "`fmt::Display` 可能比 `fmt::Debug` 更简洁，但这给 `std` 库带来了一个问题：如" |
| "何显示歧义类型？例如，如果 `std` 库为所有 `Vec<T>` 实现统一的样式，应该采用哪" |
| "种样式？是以下两种之一吗？" |
| |
| #: src/hello/print/print_display.md:35 |
| msgid "`Vec<path>`: `/:/etc:/home/username:/bin` (split on `:`)" |
| msgstr "`Vec<path>`：`/:/etc:/home/username:/bin`（以 `:` 分隔）" |
| |
| #: src/hello/print/print_display.md:36 |
| msgid "`Vec<number>`: `1,2,3` (split on `,`)" |
| msgstr "`Vec<number>`：`1,2,3`（以 `,` 分隔）" |
| |
| #: src/hello/print/print_display.md:38 |
| msgid "" |
| "No, because there is no ideal style for all types and the `std` library " |
| "doesn't presume to dictate one. `fmt::Display` is not implemented for " |
| "`Vec<T>` or for any other generic containers. `fmt::Debug` must then be used " |
| "for these generic cases." |
| msgstr "" |
| "答案是否定的。因为不存在适用于所有类型的理想样式，`std` 库也不应擅自规定一" |
| "种。因此，`fmt::Display` 并未为 `Vec<T>` 或其他泛型容器实现。在这些泛型情况" |
| "下，必须使用 `fmt::Debug`。" |
| |
| #: src/hello/print/print_display.md:43 |
| msgid "" |
| "This is not a problem though because for any new _container_ type which is " |
| "_not_ generic, `fmt::Display` can be implemented." |
| msgstr "" |
| "不过，这不是问题。对于任何新的非泛型容器类型，都可以实现 `fmt::Display`。" |
| |
| #: src/hello/print/print_display.md:47 |
| msgid "// Import `fmt`\n" |
| msgstr "// 导入 `fmt`\n" |
| |
| #: src/hello/print/print_display.md:48 |
| msgid "" |
| "// A structure holding two numbers. `Debug` will be derived so the results " |
| "can\n" |
| "// be contrasted with `Display`.\n" |
| msgstr "" |
| "// 定义一个包含两个数字的结构体。派生 `Debug` 特性，\n" |
| "// 以便与 `Display` 的结果进行对比。\n" |
| |
| #: src/hello/print/print_display.md:53 |
| msgid "// Implement `Display` for `MinMax`.\n" |
| msgstr "// 为 `MinMax` 实现 `Display` 特性。\n" |
| |
| #: src/hello/print/print_display.md:57 |
| msgid "// Use `self.number` to refer to each positional data point.\n" |
| msgstr "// 使用 `self.number` 引用每个位置的数据点。\n" |
| |
| #: src/hello/print/print_display.md:58 |
| msgid "\"({}, {})\"" |
| msgstr "\"({}, {})\"" |
| |
| #: src/hello/print/print_display.md:61 |
| msgid "// Define a structure where the fields are nameable for comparison.\n" |
| msgstr "// 定义一个结构体，其字段可命名以便比较。\n" |
| |
| #: src/hello/print/print_display.md:68 |
| msgid "// Similarly, implement `Display` for `Point2D`.\n" |
| msgstr "// 同样，为 `Point2D` 实现 `Display` 特性。\n" |
| |
| #: src/hello/print/print_display.md:72 |
| msgid "// Customize so only `x` and `y` are denoted.\n" |
| msgstr "// 自定义实现，只显示 `x` 和 `y`。\n" |
| |
| #: src/hello/print/print_display.md:73 |
| msgid "\"x: {}, y: {}\"" |
| msgstr "\"x: {}, y: {}\"" |
| |
| #: src/hello/print/print_display.md:80 |
| msgid "\"Compare structures:\"" |
| msgstr "\"比较结构体：\"" |
| |
| #: src/hello/print/print_display.md:81 src/hello/print/print_display.md:94 |
| msgid "\"Display: {}\"" |
| msgstr "\"Display：{}\"" |
| |
| #: src/hello/print/print_display.md:82 src/hello/print/print_display.md:95 |
| msgid "\"Debug: {:?}\"" |
| msgstr "\"Debug：{:?}\"" |
| |
| #: src/hello/print/print_display.md:87 |
| msgid "\"The big range is {big} and the small is {small}\"" |
| msgstr "\"大范围是 {big}，小范围是 {small}\"" |
| |
| #: src/hello/print/print_display.md:93 |
| msgid "\"Compare points:\"" |
| msgstr "\"比较点：\"" |
| |
| #: src/hello/print/print_display.md:97 |
| msgid "" |
| "// Error. Both `Debug` and `Display` were implemented, but `{:b}`\n" |
| " // requires `fmt::Binary` to be implemented. This will not work.\n" |
| " // println!(\"What does Point2D look like in binary: {:b}?\", point);\n" |
| msgstr "" |
| "// 错误。虽然实现了 `Debug` 和 `Display`，但 `{:b}` 需要\n" |
| " // 实现 `fmt::Binary`。这行代码无法工作。\n" |
| " // println!(\"Point2D 的二进制表示是什么：{:b}？\", point);\n" |
| |
| #: src/hello/print/print_display.md:103 |
| msgid "" |
| "So, `fmt::Display` has been implemented but `fmt::Binary` has not, and " |
| "therefore cannot be used. `std::fmt` has many such [`traits`](https://" |
| "doc.rust-lang.org/std/fmt/#formatting-traits) and each requires its own " |
| "implementation. This is detailed further in [`std::fmt`](https://doc.rust-" |
| "lang.org/std/fmt/)." |
| msgstr "" |
| "因此，虽然实现了 `fmt::Display`，但未实现 `fmt::Binary`，所以无法使用。" |
| "`std::fmt` 包含许多这样的[`traits`](https://doc.rust-lang.org/std/fmt/" |
| "#formatting-traits)，每个都需要单独实现。更多详情请参阅 [`std::fmt`](https://" |
| "doc.rust-lang.org/std/fmt/)。" |
| |
| #: src/hello/print/print_display.md:109 |
| msgid "" |
| "After checking the output of the above example, use the `Point2D` struct as " |
| "a guide to add a `Complex` struct to the example. When printed in the same " |
| "way, the output should be:" |
| msgstr "" |
| "查看上述示例的输出后，参考 `Point2D` 结构体，向示例中添加一个 `Complex` 结构" |
| "体。以相同方式打印时，输出应为：" |
| |
| #: src/hello/print/print_display.md:120 |
| msgid "" |
| "[`derive`](../../trait/derive.md), [`std::fmt`](https://doc.rust-lang.org/" |
| "std/fmt/), [`macros`](../../macros.md), [`struct`](../../custom_types/" |
| "structs.md), [`trait`](https://doc.rust-lang.org/std/fmt/#formatting-" |
| "traits), and [`use`](../../mod/use.md)" |
| msgstr "" |
| "[`derive`](../../trait/derive.md)、[`std::fmt`](https://doc.rust-lang.org/" |
| "std/fmt/)、[`macros`](../../macros.md)、[`struct`](../../custom_types/" |
| "structs.md)、[`trait`](https://doc.rust-lang.org/std/fmt/#formatting-traits) " |
| "和 [`use`](../../mod/use.md)" |
| |
| #: src/hello/print/print_display/testcase_list.md:3 |
| msgid "" |
| "Implementing `fmt::Display` for a structure where the elements must each be " |
| "handled sequentially is tricky. The problem is that each `write!` generates " |
| "a `fmt::Result`. Proper handling of this requires dealing with _all_ the " |
| "results. Rust provides the `?` operator for exactly this purpose." |
| msgstr "" |
| "为一个需要顺序处理元素的结构体实现 `fmt::Display` 是棘手的。问题在于每个 " |
| "`write!` 都会生成一个 `fmt::Result`。正确处理这种情况需要处理所有的结果。" |
| "Rust 提供了 `?` 运算符专门用于此目的。" |
| |
| #: src/hello/print/print_display/testcase_list.md:8 |
| msgid "Using `?` on `write!` looks like this:" |
| msgstr "在 `write!` 上使用 `?` 的示例如下：" |
| |
| #: src/hello/print/print_display/testcase_list.md:11 |
| msgid "" |
| "// Try `write!` to see if it errors. If it errors, return\n" |
| "// the error. Otherwise continue.\n" |
| msgstr "" |
| "// 尝试执行 `write!`，检查是否出错。如果出错，返回错误。\n" |
| "// 否则继续执行。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:16 |
| msgid "" |
| "With `?` available, implementing `fmt::Display` for a `Vec` is " |
| "straightforward:" |
| msgstr "有了 `?` 运算符，为 `Vec` 实现 `fmt::Display` 就变得简单明了：" |
| |
| #: src/hello/print/print_display/testcase_list.md:20 |
| msgid "// Import the `fmt` module.\n" |
| msgstr "// 导入 `fmt` 模块。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:21 |
| msgid "// Define a structure named `List` containing a `Vec`.\n" |
| msgstr "// 定义一个名为 `List` 的结构体，包含一个 `Vec`。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:27 |
| msgid "" |
| "// Extract the value using tuple indexing,\n" |
| " // and create a reference to `vec`.\n" |
| msgstr "" |
| "// 使用元组索引提取值，\n" |
| " // 并创建一个指向 `vec` 的引用。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:31 |
| msgid "\"[\"" |
| msgstr "\"[\"" |
| |
| #: src/hello/print/print_display/testcase_list.md:33 |
| msgid "" |
| "// Iterate over `v` in `vec` while enumerating the iteration\n" |
| " // index in `index`.\n" |
| msgstr "" |
| "// 遍历 `vec` 中的 `v`，同时用 `index` 枚举迭代索引。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:36 |
| msgid "" |
| "// For every element except the first, add a comma.\n" |
| " // Use the ? operator to return on errors.\n" |
| msgstr "" |
| "// 除第一个元素外，为每个元素添加逗号。\n" |
| " // 使用 ? 运算符在出错时返回。\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:38 src/std/str.md:36 |
| msgid "\", \"" |
| msgstr "\", \"" |
| |
| #: src/hello/print/print_display/testcase_list.md:42 |
| msgid "// Close the opened bracket and return a fmt::Result value.\n" |
| msgstr "// 闭合左括号并返回 fmt::Result 值\n" |
| |
| #: src/hello/print/print_display/testcase_list.md:43 |
| msgid "\"]\"" |
| msgstr "\"]\"" |
| |
| #: src/hello/print/print_display/testcase_list.md:55 |
| msgid "" |
| "Try changing the program so that the index of each element in the vector is " |
| "also printed. The new output should look like this:" |
| msgstr "" |
| "尝试修改程序，使向量中每个元素的索引也被打印出来。新的输出应该如下所示：" |
| |
| #: src/hello/print/print_display/testcase_list.md:64 |
| msgid "" |
| "[`for`](../../../flow_control/for.md), [`ref`](../../../scope/borrow/" |
| "ref.md), [`Result`](../../../std/result.md), [`struct`](../../../" |
| "custom_types/structs.md), [`?`](../../../std/result/question_mark.md), and " |
| "[`vec!`](../../../std/vec.md)" |
| msgstr "" |
| "[`for`](../../../flow_control/for.md)、[`ref`](../../../scope/borrow/" |
| "ref.md)、[`Result`](../../../std/result.md)、[`struct`](../../../" |
| "custom_types/structs.md)、[`?`](../../../std/result/question_mark.md) 和 " |
| "[`vec!`](../../../std/vec.md)" |
| |
| #: src/hello/print/fmt.md:3 |
| msgid "We've seen that formatting is specified via a _format string_:" |
| msgstr "我们已经看到，格式化是通过一个_格式字符串_来指定的：" |
| |
| #: src/hello/print/fmt.md:5 |
| msgid "`format!(\"{}\", foo)` -> `\"3735928559\"`" |
| msgstr "`format!(\"{}\", foo)` -> `\"3735928559\"`" |
| |
| #: src/hello/print/fmt.md:6 |
| msgid "" |
| "`format!(\"0x{:X}\", foo)` -> [`\"0xDEADBEEF\"`](https://en.wikipedia.org/" |
| "wiki/Deadbeef#Magic_debug_values)" |
| msgstr "" |
| "`format!(\"0x{:X}\", foo)` -> [`\"0xDEADBEEF\"`](https://en.wikipedia.org/" |
| "wiki/Deadbeef#Magic_debug_values)" |
| |
| #: src/hello/print/fmt.md:7 |
| msgid "`format!(\"0o{:o}\", foo)` -> `\"0o33653337357\"`" |
| msgstr "`format!(\"0o{:o}\", foo)` -> `\"0o33653337357\"`" |
| |
| #: src/hello/print/fmt.md:9 |
| msgid "" |
| "The same variable (`foo`) can be formatted differently depending on which " |
| "_argument type_ is used: `X` vs `o` vs _unspecified_." |
| msgstr "" |
| "同一个变量（`foo`）可以根据使用的**参数类型**而有不同的格式化方式：`X`、`o` " |
| "或**未指定**。" |
| |
| #: src/hello/print/fmt.md:12 |
| msgid "" |
| "This formatting functionality is implemented via traits, and there is one " |
| "trait for each argument type. The most common formatting trait is `Display`, " |
| "which handles cases where the argument type is left unspecified: `{}` for " |
| "instance." |
| msgstr "" |
| "这种格式化功能是通过 trait 实现的，每种参数类型都对应一个 trait。最常用的格式" |
| "化 trait 是 `Display`，它处理参数类型未指定的情况，例如 `{}`。" |
| |
| #: src/hello/print/fmt.md:21 |
| msgid "// Latitude\n" |
| msgstr "// 纬度\n" |
| |
| #: src/hello/print/fmt.md:23 |
| msgid "// Longitude\n" |
| msgstr "// 经度\n" |
| |
| #: src/hello/print/fmt.md:28 |
| msgid "" |
| "// `f` is a buffer, and this method must write the formatted string into " |
| "it.\n" |
| msgstr "// `f` 是一个缓冲区，此方法必须将格式化的字符串写入其中。\n" |
| |
| #: src/hello/print/fmt.md:30 |
| msgid "'N'" |
| msgstr "'N'" |
| |
| #: src/hello/print/fmt.md:30 |
| msgid "'S'" |
| msgstr "'S'" |
| |
| #: src/hello/print/fmt.md:31 |
| msgid "'E'" |
| msgstr "'E'" |
| |
| #: src/hello/print/fmt.md:31 |
| msgid "'W'" |
| msgstr "'W'" |
| |
| #: src/hello/print/fmt.md:33 |
| msgid "" |
| "// `write!` is like `format!`, but it will write the formatted string\n" |
| " // into a buffer (the first argument).\n" |
| msgstr "" |
| "// `write!` 类似于 `format!`，但它会将格式化后的字符串\n" |
| " // 写入一个缓冲区（第一个参数）。\n" |
| |
| #: src/hello/print/fmt.md:35 |
| msgid "\"{}: {:.3}°{} {:.3}°{}\"" |
| msgstr "\"{}: {:.3}°{} {:.3}°{}\"" |
| |
| #: src/hello/print/fmt.md:49 |
| msgid "\"Dublin\"" |
| msgstr "\"Dublin\"" |
| |
| #: src/hello/print/fmt.md:50 |
| msgid "\"Oslo\"" |
| msgstr "\"Oslo\"" |
| |
| #: src/hello/print/fmt.md:51 |
| msgid "\"Vancouver\"" |
| msgstr "\"Vancouver\"" |
| |
| #: src/hello/print/fmt.md:60 |
| msgid "" |
| "// Switch this to use {} once you've added an implementation\n" |
| " // for fmt::Display.\n" |
| msgstr "// 一旦你为 fmt::Display 添加了实现，就把这里改成使用 {}。\n" |
| |
| #: src/hello/print/fmt.md:62 src/primitives/tuples.md:60 |
| #: src/custom_types/structs.md:47 src/types/inference.md:23 |
| #: src/conversion/string.md:76 src/generics/bounds.md:49 |
| #: src/generics/where.md:38 src/std/str.md:137 src/std/result.md:59 |
| #: src/std/result.md:61 src/std/result.md:63 src/std/arc.md:26 |
| #: src/std_misc/channels.md:53 |
| msgid "\"{:?}\"" |
| msgstr "\"{:?}\"" |
| |
| #: src/hello/print/fmt.md:67 |
| msgid "" |
| "You can view a [full list of formatting traits](https://doc.rust-lang.org/" |
| "std/fmt/#formatting-traits) and their argument types in the [`std::fmt`]" |
| "(https://doc.rust-lang.org/std/fmt/) documentation." |
| msgstr "" |
| "你可以在 [`std::fmt`](https://doc.rust-lang.org/std/fmt/) 文档中查看[格式化 " |
| "trait 的完整列表](https://doc.rust-lang.org/std/fmt/#formatting-traits)及其参" |
| "数类型。" |
| |
| #: src/hello/print/fmt.md:72 |
| msgid "" |
| "Add an implementation of the `fmt::Display` trait for the `Color` struct " |
| "above so that the output displays as:" |
| msgstr "为上面的 `Color` 结构体实现 `fmt::Display` trait，使输出显示如下：" |
| |
| #: src/hello/print/fmt.md:81 |
| msgid "Three hints if you get stuck:" |
| msgstr "如果你遇到困难，这里有三个提示：" |
| |
| #: src/hello/print/fmt.md:83 |
| msgid "" |
| "The formula for calculating a color in the RGB color space is: `RGB = " |
| "(R*65536)+(G*256)+B , (when R is RED, G is GREEN and B is BLUE)`. For more " |
| "see [RGB color format & calculation](https://www.rapidtables.com/web/color/" |
| "RGB_Color.html#rgb-format)." |
| msgstr "" |
| "RGB 颜色空间中颜色的计算公式是：`RGB = (R*65536)+(G*256)+B，（其中 R 是红色，" |
| "G 是绿色，B 是蓝色）`。更多信息请参见 [RGB 颜色格式和计算](https://" |
| "www.rapidtables.com/web/color/RGB_Color.html#rgb-format)。" |
| |
| #: src/hello/print/fmt.md:86 |
| msgid "" |
| "You [may need to list each color more than once](https://doc.rust-lang.org/" |
| "std/fmt/#named-parameters)." |
| msgstr "" |
| "你[可能需要多次列出每种颜色](https://doc.rust-lang.org/std/fmt/#named-" |
| "parameters)。" |
| |
| #: src/hello/print/fmt.md:87 |
| msgid "" |
| "You can [pad with zeros to a width of 2](https://doc.rust-lang.org/std/fmt/" |
| "#width) with `:0>2`." |
| msgstr "" |
| "你可以使用 `:0>2` [用零填充到宽度为 2](https://doc.rust-lang.org/std/fmt/" |
| "#width)。" |
| |
| #: src/hello/print/fmt.md:91 |
| msgid "[`std::fmt`](https://doc.rust-lang.org/std/fmt/)" |
| msgstr "[`std::fmt`](https://doc.rust-lang.org/std/fmt/)" |
| |
| #: src/primitives.md:3 |
| msgid "" |
| "Rust provides access to a wide variety of `primitives`. A sample includes:" |
| msgstr "Rust 提供了多种`原生类型`。以下是一些示例：" |
| |
| #: src/primitives.md:5 |
| msgid "Scalar Types" |
| msgstr "标量类型" |
| |
| #: src/primitives.md:7 |
| msgid "" |
| "Signed integers: `i8`, `i16`, `i32`, `i64`, `i128` and `isize` (pointer size)" |
| msgstr "有符号整数：`i8`、`i16`、`i32`、`i64`、`i128` 和 `isize`（指针大小）" |
| |
| #: src/primitives.md:8 |
| msgid "" |
| "Unsigned integers: `u8`, `u16`, `u32`, `u64`, `u128` and `usize` (pointer " |
| "size)" |
| msgstr "无符号整数：`u8`、`u16`、`u32`、`u64`、`u128` 和 `usize`（指针大小）" |
| |
| #: src/primitives.md:10 |
| msgid "Floating point: `f32`, `f64`" |
| msgstr "浮点数：`f32`、`f64`" |
| |
| #: src/primitives.md:11 |
| msgid "`char` Unicode scalar values like `'a'`, `'α'` and `'∞'` (4 bytes each)" |
| msgstr "`char` Unicode 标量值，如 `'a'`、`'α'` 和 `'∞'`（每个都是 4 字节）" |
| |
| #: src/primitives.md:12 |
| msgid "`bool` either `true` or `false`" |
| msgstr "`bool` 值为 `true` 或 `false`" |
| |
| #: src/primitives.md:13 |
| msgid "The unit type `()`, whose only possible value is an empty tuple: `()`" |
| msgstr "单元类型 `()`，其唯一可能的值是空元组：`()`" |
| |
| #: src/primitives.md:15 |
| msgid "" |
| "Despite the value of a unit type being a tuple, it is not considered a " |
| "compound type because it does not contain multiple values." |
| msgstr "尽管单元类型的值是一个元组，但它不被视为复合类型，因为它不包含多个值。" |
| |
| #: src/primitives.md:18 |
| msgid "Compound Types" |
| msgstr "复合类型" |
| |
| #: src/primitives.md:20 |
| msgid "Arrays like `[1, 2, 3]`" |
| msgstr "数组，如 `[1, 2, 3]`" |
| |
| #: src/primitives.md:21 |
| msgid "Tuples like `(1, true)`" |
| msgstr "元组，如 `(1, true)`" |
| |
| #: src/primitives.md:23 |
| msgid "" |
| "Variables can always be _type annotated_. Numbers may additionally be " |
| "annotated via a _suffix_ or _by default_. Integers default to `i32` and " |
| "floats to `f64`. Note that Rust can also infer types from context." |
| msgstr "" |
| "变量总是可以进行**类型标注**。数字还可以通过**后缀**或**默认方式**来标注。整" |
| "数默认为 `i32` 类型，浮点数默认为 `f64` 类型。请注意，Rust 也可以从上下文中推" |
| "断类型。" |
| |
| #: src/primitives.md:29 |
| msgid "// Variables can be type annotated.\n" |
| msgstr "// 变量可以被类型标注。\n" |
| |
| #: src/primitives.md:32 |
| msgid "// Regular annotation\n" |
| msgstr "// 常规标注\n" |
| |
| #: src/primitives.md:33 |
| msgid "// Suffix annotation\n" |
| msgstr "// 后缀标注\n" |
| |
| #: src/primitives.md:35 |
| msgid "// Or a default will be used.\n" |
| msgstr "// 或者使用默认类型。\n" |
| |
| #: src/primitives.md:36 |
| msgid "// `f64`\n" |
| msgstr "// `f64`\n" |
| |
| #: src/primitives.md:37 |
| msgid "// `i32`\n" |
| msgstr "// `i32`\n" |
| |
| #: src/primitives.md:39 |
| msgid "// A type can also be inferred from context.\n" |
| msgstr "// 类型也可以从上下文中推断。\n" |
| |
| #: src/primitives.md:40 |
| msgid "// Type i64 is inferred from another line.\n" |
| msgstr "// 从另一行推断出类型为 i64。\n" |
| |
| #: src/primitives.md:43 |
| msgid "// A mutable variable's value can be changed.\n" |
| msgstr "// 可变变量的值可以改变。\n" |
| |
| #: src/primitives.md:44 |
| msgid "// Mutable `i32`\n" |
| msgstr "// 可变的 `i32`\n" |
| |
| #: src/primitives.md:47 |
| msgid "// Error! The type of a variable can't be changed.\n" |
| msgstr "// 报错！变量的类型不能改变。\n" |
| |
| #: src/primitives.md:50 |
| msgid "// Variables can be overwritten with shadowing.\n" |
| msgstr "// 变量可以通过遮蔽（shadowing）来覆盖。\n" |
| |
| #: src/primitives.md:53 |
| msgid "/* Compound types - Array and Tuple */" |
| msgstr "/* 复合类型 - 数组和元组 */" |
| |
| #: src/primitives.md:55 |
| msgid "// Array signature consists of Type T and length as [T; length].\n" |
| msgstr "// 数组的签名由类型 T 和长度组成，表示为 [T; length]。\n" |
| |
| #: src/primitives.md:58 |
| msgid "" |
| "// Tuple is a collection of values of different types \n" |
| " // and is constructed using parentheses ().\n" |
| msgstr "" |
| "// 元组是不同类型值的集合，\n" |
| " // 使用圆括号 () 构造。\n" |
| |
| #: src/primitives.md:66 |
| msgid "" |
| "[the `std` library](https://doc.rust-lang.org/std/), [`mut`]" |
| "(variable_bindings/mut.md), [`inference`](types/inference.md), and " |
| "[`shadowing`](variable_bindings/scope.md)" |
| msgstr "" |
| "[`std` 库](https://doc.rust-lang.org/std/)、[`mut`](variable_bindings/" |
| "mut.md)、[`inference`](types/inference.md) 和 [`shadowing`]" |
| "(variable_bindings/scope.md)" |
| |
| #: src/primitives/literals.md:3 |
| msgid "" |
| "Integers `1`, floats `1.2`, characters `'a'`, strings `\"abc\"`, booleans " |
| "`true` and the unit type `()` can be expressed using literals." |
| msgstr "" |
| "整数 `1`、浮点数 `1.2`、字符 `'a'`、字符串 `\"abc\"`、布尔值 `true` 和单元类" |
| "型 `()` 可以用字面值表示。" |
| |
| #: src/primitives/literals.md:6 |
| msgid "" |
| "Integers can, alternatively, be expressed using hexadecimal, octal or binary " |
| "notation using these prefixes respectively: `0x`, `0o` or `0b`." |
| msgstr "" |
| "整数也可以使用十六进制、八进制或二进制表示法，分别使用这些前缀：`0x`、`0o` " |
| "或 `0b`。" |
| |
| #: src/primitives/literals.md:9 |
| msgid "" |
| "Underscores can be inserted in numeric literals to improve readability, e.g. " |
| "`1_000` is the same as `1000`, and `0.000_001` is the same as `0.000001`." |
| msgstr "" |
| "可以在数字字面值中插入下划线以提高可读性，例如 `1_000` 与 `1000` 相同，" |
| "`0.000_001` 与 `0.000001` 相同。" |
| |
| #: src/primitives/literals.md:12 |
| msgid "" |
| "Rust also supports scientific [E-notation](https://en.wikipedia.org/wiki/" |
| "Scientific_notation#E_notation), e.g. `1e6`, `7.6e-4`. The associated type " |
| "is `f64`." |
| msgstr "" |
| "Rust 还支持科学计数法 [E-notation](https://en.wikipedia.org/wiki/" |
| "Scientific_notation#E_notation)，例如 `1e6`、`7.6e-4`。相关类型是 `f64`。" |
| |
| #: src/primitives/literals.md:15 |
| msgid "" |
| "We need to tell the compiler the type of the literals we use. For now, we'll " |
| "use the `u32` suffix to indicate that the literal is an unsigned 32-bit " |
| "integer, and the `i32` suffix to indicate that it's a signed 32-bit integer." |
| msgstr "" |
| "我们需要告诉编译器我们使用的字面值的类型。现在，我们将使用 `u32` 后缀来表示该" |
| "字面值是一个无符号 32 位整数，使用 `i32` 后缀来表示它是一个有符号 32 位整数。" |
| |
| #: src/primitives/literals.md:19 |
| msgid "" |
| "The operators available and their precedence [in Rust](https://doc.rust-" |
| "lang.org/reference/expressions.html#expression-precedence) are similar to " |
| "other [C-like languages](https://en.wikipedia.org/wiki/" |
| "Operator_precedence#Programming_languages)." |
| msgstr "" |
| "[Rust 中](https://doc.rust-lang.org/reference/expressions.html#expression-" |
| "precedence)可用的运算符及其优先级与其他 [类 C 语言](https://en.wikipedia.org/" |
| "wiki/Operator_precedence#Programming_languages) 类似。" |
| |
| #: src/primitives/literals.md:24 |
| msgid "// Integer addition\n" |
| msgstr "// 整数加法\n" |
| |
| #: src/primitives/literals.md:25 |
| msgid "\"1 + 2 = {}\"" |
| msgstr "\"1 + 2 = {}\"" |
| |
| #: src/primitives/literals.md:27 |
| msgid "// Integer subtraction\n" |
| msgstr "// 整数减法\n" |
| |
| #: src/primitives/literals.md:28 |
| msgid "\"1 - 2 = {}\"" |
| msgstr "\"1 - 2 = {}\"" |
| |
| #: src/primitives/literals.md:29 |
| msgid "" |
| "// TODO ^ Try changing `1i32` to `1u32` to see why the type is important\n" |
| msgstr "// TODO ^ 尝试将 `1i32` 改为 `1u32`，看看为什么类型很重要\n" |
| |
| #: src/primitives/literals.md:31 |
| msgid "// Scientific notation\n" |
| msgstr "// 科学记数法\n" |
| |
| #: src/primitives/literals.md:32 |
| msgid "\"1e4 is {}, -2.5e-3 is {}\"" |
| msgstr "\"1e4 is {}, -2.5e-3 is {}\"" |
| |
| #: src/primitives/literals.md:34 |
| msgid "// Short-circuiting boolean logic\n" |
| msgstr "// 短路布尔逻辑\n" |
| |
| #: src/primitives/literals.md:35 |
| msgid "\"true AND false is {}\"" |
| msgstr "\"true AND false is {}\"" |
| |
| #: src/primitives/literals.md:36 |
| msgid "\"true OR false is {}\"" |
| msgstr "\"true OR false is {}\"" |
| |
| #: src/primitives/literals.md:37 |
| msgid "\"NOT true is {}\"" |
| msgstr "\"NOT true is {}\"" |
| |
| #: src/primitives/literals.md:39 |
| msgid "// Bitwise operations\n" |
| msgstr "// 位运算\n" |
| |
| #: src/primitives/literals.md:40 |
| msgid "\"0011 AND 0101 is {:04b}\"" |
| msgstr "\"0011 AND 0101 is {:04b}\"" |
| |
| #: src/primitives/literals.md:41 |
| msgid "\"0011 OR 0101 is {:04b}\"" |
| msgstr "\"0011 OR 0101 is {:04b}\"" |
| |
| #: src/primitives/literals.md:42 |
| msgid "\"0011 XOR 0101 is {:04b}\"" |
| msgstr "\"0011 XOR 0101 is {:04b}\"" |
| |
| #: src/primitives/literals.md:43 |
| msgid "\"1 << 5 is {}\"" |
| msgstr "\"1 << 5 is {}\"" |
| |
| #: src/primitives/literals.md:44 |
| msgid "\"0x80 >> 2 is 0x{:x}\"" |
| msgstr "\"0x80 >> 2 is 0x{:x}\"" |
| |
| #: src/primitives/literals.md:46 |
| msgid "// Use underscores to improve readability!\n" |
| msgstr "// 使用下划线来提高可读性！\n" |
| |
| #: src/primitives/literals.md:47 |
| msgid "\"One million is written as {}\"" |
| msgstr "\"One million is written as {}\"" |
| |
| #: src/primitives/tuples.md:3 |
| msgid "" |
| "A tuple is a collection of values of different types. Tuples are constructed " |
| "using parentheses `()`, and each tuple itself is a value with type signature " |
| "`(T1, T2, ...)`, where `T1`, `T2` are the types of its members. Functions " |
| "can use tuples to return multiple values, as tuples can hold any number of " |
| "values." |
| msgstr "" |
| "元组是一个可以包含各种类型的值的集合。元组使用圆括号 `()` 来构造，而且每个元" |
| "组本身是一个类型标记为 `(T1, T2, ...)` 的值，其中 `T1`、`T2` 是其成员的类型。" |
| "函数可以使用元组来返回多个值，因为元组可以存储任意数量的值。" |
| |
| #: src/primitives/tuples.md:9 |
| msgid "// Tuples can be used as function arguments and as return values.\n" |
| msgstr "// 元组可以用作函数参数和返回值。\n" |
| |
| #: src/primitives/tuples.md:11 |
| msgid "// `let` can be used to bind the members of a tuple to variables.\n" |
| msgstr "// `let` 可以用来把元组的成员绑定到变量。\n" |
| |
| #: src/primitives/tuples.md:16 |
| msgid "// The following struct is for the activity.\n" |
| msgstr "// 以下结构体将用于后续练习。\n" |
| |
| #: src/primitives/tuples.md:22 |
| msgid "// A tuple with a bunch of different types.\n" |
| msgstr "// 一个包含多种不同类型的元组。\n" |
| |
| #: src/primitives/tuples.md:26 src/generics.md:50 src/generics.md:55 |
| #: src/generics/gen_fn.md:47 |
| msgid "'a'" |
| msgstr "'a'" |
| |
| #: src/primitives/tuples.md:28 |
| msgid "// Values can be extracted from the tuple using tuple indexing.\n" |
| msgstr "// 可以使用元组索引来提取元组中的值。\n" |
| |
| #: src/primitives/tuples.md:29 |
| msgid "\"Long tuple first value: {}\"" |
| msgstr "\"长元组的第一个值：{}\"" |
| |
| #: src/primitives/tuples.md:30 |
| msgid "\"Long tuple second value: {}\"" |
| msgstr "\"长元组的第二个值：{}\"" |
| |
| #: src/primitives/tuples.md:32 |
| msgid "// Tuples can be tuple members.\n" |
| msgstr "// 元组可以作为元组的成员。\n" |
| |
| #: src/primitives/tuples.md:35 |
| msgid "// Tuples are printable.\n" |
| msgstr "// 元组是可打印的。\n" |
| |
| #: src/primitives/tuples.md:36 |
| msgid "\"tuple of tuples: {:?}\"" |
| msgstr "\"元组的元组：{:?}\"" |
| |
| #: src/primitives/tuples.md:38 |
| msgid "" |
| "// But long Tuples (more than 12 elements) cannot be printed.\n" |
| " //let too_long_tuple = (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13);\n" |
| " //println!(\"Too long tuple: {:?}\", too_long_tuple);\n" |
| " // TODO ^ Uncomment the above 2 lines to see the compiler error\n" |
| msgstr "" |
| "// 但长元组（超过 12 个元素）无法打印。\n" |
| " //let too_long_tuple = (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13);\n" |
| " //println!(\"过长的元组：{:?}\", too_long_tuple);\n" |
| " // TODO ^ 取消上面两行的注释以查看编译器错误\n" |
| |
| #: src/primitives/tuples.md:44 |
| msgid "\"Pair is {:?}\"" |
| msgstr "\"对组是 {:?}\"" |
| |
| #: src/primitives/tuples.md:46 |
| msgid "\"The reversed pair is {:?}\"" |
| msgstr "\"反转后的对组是 {:?}\"" |
| |
| #: src/primitives/tuples.md:48 |
| msgid "" |
| "// To create one element tuples, the comma is required to tell them apart\n" |
| " // from a literal surrounded by parentheses.\n" |
| msgstr "" |
| "// 创建单元素元组时，需要使用逗号来区分它们\n" |
| " // 与被括号包围的字面量。\n" |
| |
| #: src/primitives/tuples.md:50 |
| msgid "\"One element tuple: {:?}\"" |
| msgstr "\"单元素元组：{:?}\"" |
| |
| #: src/primitives/tuples.md:51 |
| msgid "\"Just an integer: {:?}\"" |
| msgstr "\"仅是一个整数：{:?}\"" |
| |
| #: src/primitives/tuples.md:53 |
| msgid "// Tuples can be destructured to create bindings.\n" |
| msgstr "// 可以通过解构元组来创建绑定。\n" |
| |
| #: src/primitives/tuples.md:54 src/conversion/from_into.md:17 |
| #: src/fn/closures/input_parameters.md:52 src/std_misc/fs.md:51 |
| msgid "\"hello\"" |
| msgstr "\"hello\"" |
| |
| #: src/primitives/tuples.md:57 |
| msgid "\"{:?}, {:?}, {:?}, {:?}\"" |
| msgstr "\"{:?}、{:?}、{:?}、{:?}\"" |
| |
| #: src/primitives/tuples.md:66 |
| msgid "" |
| "_Recap_: Add the `fmt::Display` trait to the `Matrix` struct in the above " |
| "example, so that if you switch from printing the debug format `{:?}` to the " |
| "display format `{}`, you see the following output:" |
| msgstr "" |
| "**复习**：为上面示例中的 `Matrix` 结构体添加 `fmt::Display` trait，\n" |
| "这样当你从打印调试格式 `{:?}` 切换到显示格式 `{}` 时，\n" |
| "你会看到以下输出：" |
| |
| #: src/primitives/tuples.md:75 |
| msgid "" |
| "You may want to refer back to the example for [print display](../hello/print/" |
| "print_display.md)." |
| msgstr "" |
| "你可能需要回顾一下 [打印显示](../hello/print/print_display.md) 的示例。" |
| |
| #: src/primitives/tuples.md:76 |
| msgid "" |
| "Add a `transpose` function using the `reverse` function as a template, which " |
| "accepts a matrix as an argument, and returns a matrix in which two elements " |
| "have been swapped. For example:" |
| msgstr "" |
| "参考 `reverse` 函数的模板，添加一个 `transpose` 函数。\n" |
| "该函数接受一个矩阵作为参数，并返回一个交换了两个元素的矩阵。例如：" |
| |
| #: src/primitives/tuples.md:81 |
| msgid "\"Matrix:\\n{}\"" |
| msgstr "\"矩阵：\\n{}\"" |
| |
| #: src/primitives/tuples.md:82 |
| msgid "\"Transpose:\\n{}\"" |
| msgstr "\"转置：\\n{}\"" |
| |
| #: src/primitives/tuples.md:85 |
| msgid "Results in the output:" |
| msgstr "输出结果为：" |
| |
| #: src/primitives/array.md:3 |
| msgid "" |
| "An array is a collection of objects of the same type `T`, stored in " |
| "contiguous memory. Arrays are created using brackets `[]`, and their length, " |
| "which is known at compile time, is part of their type signature `[T; " |
| "length]`." |
| msgstr "" |
| "数组是一种存储在连续内存中的相同类型 `T` 的对象集合。\n" |
| "数组使用方括号 `[]` 创建，其长度在编译时已知，\n" |
| "是其类型签名 `[T; length]` 的一部分。" |
| |
| #: src/primitives/array.md:7 |
| msgid "" |
| "Slices are similar to arrays, but their length is not known at compile time. " |
| "Instead, a slice is a two-word object; the first word is a pointer to the " |
| "data, the second word is the length of the slice. The word size is the same " |
| "as usize, determined by the processor architecture, e.g. 64 bits on an " |
| "x86-64. Slices can be used to borrow a section of an array and have the type " |
| "signature `&[T]`." |
| msgstr "" |
| "切片类似于数组，但其长度在编译时未知。切片是一个双字对象：\n" |
| "第一个字是指向数据的指针，第二个字是切片的长度。字的大小与 usize 相同，\n" |
| "由处理器架构决定，例如在 x86-64 上是 64 位。切片可用于借用数组的一部分，\n" |
| "其类型签名为 `&[T]`。" |
| |
| #: src/primitives/array.md:15 |
| msgid "// This function borrows a slice.\n" |
| msgstr "// 此函数借用一个切片。\n" |
| |
| #: src/primitives/array.md:18 |
| msgid "\"First element of the slice: {}\"" |
| msgstr "\"切片的第一个元素：{}\"" |
| |
| #: src/primitives/array.md:19 |
| msgid "\"The slice has {} elements\"" |
| msgstr "\"切片有 {} 个元素\"" |
| |
| #: src/primitives/array.md:23 |
| msgid "// Fixed-size array (type signature is superfluous).\n" |
| msgstr "// 固定大小的数组（类型签名是多余的）。\n" |
| |
| #: src/primitives/array.md:26 |
| msgid "// All elements can be initialized to the same value.\n" |
| msgstr "// 所有元素可以初始化为相同的值。\n" |
| |
| #: src/primitives/array.md:29 |
| msgid "// Indexing starts at 0.\n" |
| msgstr "// 索引从 0 开始。\n" |
| |
| #: src/primitives/array.md:30 |
| msgid "\"First element of the array: {}\"" |
| msgstr "\"数组的第一个元素：{}\"" |
| |
| #: src/primitives/array.md:31 |
| msgid "\"Second element of the array: {}\"" |
| msgstr "\"数组的第二个元素：{}\"" |
| |
| #: src/primitives/array.md:33 |
| msgid "// `len` returns the count of elements in the array.\n" |
| msgstr "// `len` 返回数组中元素的数量。\n" |
| |
| #: src/primitives/array.md:34 |
| msgid "\"Number of elements in array: {}\"" |
| msgstr "\"数组中的元素数量：{}\"" |
| |
| #: src/primitives/array.md:36 |
| msgid "// Arrays are stack allocated.\n" |
| msgstr "// 数组是栈分配的。\n" |
| |
| #: src/primitives/array.md:37 |
| msgid "\"Array occupies {} bytes\"" |
| msgstr "\"数组占用 {} 字节\"" |
| |
| #: src/primitives/array.md:39 |
| msgid "// Arrays can be automatically borrowed as slices.\n" |
| msgstr "// 数组可以自动借用为切片。\n" |
| |
| #: src/primitives/array.md:40 |
| msgid "\"Borrow the whole array as a slice.\"" |
| msgstr "\"将整个数组借用为切片。\"" |
| |
| #: src/primitives/array.md:43 |
| msgid "" |
| "// Slices can point to a section of an array.\n" |
| " // They are of the form [starting_index..ending_index].\n" |
| " // `starting_index` is the first position in the slice.\n" |
| " // `ending_index` is one more than the last position in the slice.\n" |
| msgstr "" |
| "// 切片可以指向数组的一部分。\n" |
| " // 它们的形式是 [起始索引..结束索引]。\n" |
| " // `起始索引` 是切片中的第一个位置。\n" |
| " // `结束索引` 是切片中最后一个位置的后一个位置。\n" |
| |
| #: src/primitives/array.md:47 |
| msgid "\"Borrow a section of the array as a slice.\"" |
| msgstr "\"借用数组的一部分作为切片。\"" |
| |
| #: src/primitives/array.md:50 |
| msgid "// Example of empty slice `&[]`:\n" |
| msgstr "// 空切片 `&[]` 的示例：\n" |
| |
| #: src/primitives/array.md:53 |
| msgid "// Same but more verbose\n" |
| msgstr "// 同样的操作，但更详细\n" |
| |
| #: src/primitives/array.md:55 |
| msgid "" |
| "// Arrays can be safely accessed using `.get`, which returns an\n" |
| " // `Option`. This can be matched as shown below, or used with\n" |
| " // `.expect()` if you would like the program to exit with a nice\n" |
| " // message instead of happily continue.\n" |
| msgstr "" |
| "// 可以使用 `.get` 安全地访问数组，它返回一个 `Option`。\n" |
| " // 可以像下面这样对其进行匹配，或者使用 `.expect()`。\n" |
| " // 如果你希望程序在访问越界时优雅地退出而不是继续执行，\n" |
| " // 可以使用 `.expect()`。\n" |
| |
| #: src/primitives/array.md:59 |
| msgid "// Oops, one element too far!\n" |
| msgstr "// 糟糕，访问超出了数组范围！\n" |
| |
| #: src/primitives/array.md:61 |
| msgid "\"{}: {}\"" |
| msgstr "\"{}: {}\"" |
| |
| #: src/primitives/array.md:62 |
| msgid "\"Slow down! {} is too far!\"" |
| msgstr "\"慢着！{} 超出范围了！\"" |
| |
| #: src/primitives/array.md:66 |
| msgid "" |
| "// Out of bound indexing on array with constant value causes compile time " |
| "error.\n" |
| " //println!(\"{}\", xs[5]);\n" |
| " // Out of bound indexing on slice causes runtime error.\n" |
| " //println!(\"{}\", xs[..][5]);\n" |
| msgstr "" |
| "// 使用常量值对数组的越界索引会导致编译时错误。\n" |
| " //println!(\"{}\", xs[5]);\n" |
| " // 对切片的越界索引会导致运行时错误。\n" |
| " //println!(\"{}\", xs[..][5]);\n" |
| |
| #: src/custom_types.md:3 |
| msgid "Rust custom data types are formed mainly through the two keywords:" |
| msgstr "Rust 的自定义数据类型主要通过以下两个关键字来创建：" |
| |
| #: src/custom_types.md:5 |
| msgid "`struct`: define a structure" |
| msgstr "`struct`：定义结构体" |
| |
| #: src/custom_types.md:6 |
| msgid "`enum`: define an enumeration" |
| msgstr "`enum`：定义枚举" |
| |
| #: src/custom_types.md:8 |
| msgid "Constants can also be created via the `const` and `static` keywords." |
| msgstr "常量也可以通过 `const` 和 `static` 关键字来创建。" |
| |
| #: src/custom_types/structs.md:3 |
| msgid "" |
| "There are three types of structures (\"structs\") that can be created using " |
| "the `struct` keyword:" |
| msgstr "使用 `struct` 关键字可以创建三种类型的结构体（\"structs\"）：" |
| |
| #: src/custom_types/structs.md:6 |
| msgid "Tuple structs, which are, basically, named tuples." |
| msgstr "元组结构体：本质上是具名元组。" |
| |
| #: src/custom_types/structs.md:7 |
| msgid "" |
| "The classic [C structs](https://en.wikipedia.org/wiki/" |
| "Struct_(C_programming_language))" |
| msgstr "" |
| "经典的 [C 语言风格结构体](https://en.wikipedia.org/wiki/" |
| "Struct_(C_programming_language))" |
| |
| #: src/custom_types/structs.md:8 |
| msgid "Unit structs, which are field-less, are useful for generics." |
| msgstr "单元结构体：没有字段，在泛型中很有用。" |
| |
| #: src/custom_types/structs.md:11 src/custom_types/enum/enum_use.md:6 |
| #: src/custom_types/enum/c_like.md:6 |
| msgid "// An attribute to hide warnings for unused code.\n" |
| msgstr "// 这个属性用于隐藏未使用代码的警告。\n" |
| |
| #: src/custom_types/structs.md:19 |
| msgid "// A unit struct\n" |
| msgstr "// 单元结构体\n" |
| |
| #: src/custom_types/structs.md:22 |
| msgid "// A tuple struct\n" |
| msgstr "// 元组结构体\n" |
| |
| #: src/custom_types/structs.md:25 |
| msgid "// A struct with two fields\n" |
| msgstr "// 带有两个字段的结构体\n" |
| |
| #: src/custom_types/structs.md:31 |
| msgid "// Structs can be reused as fields of another struct\n" |
| msgstr "// 结构体可以作为另一个结构体的字段\n" |
| |
| #: src/custom_types/structs.md:34 |
| msgid "" |
| "// A rectangle can be specified by where the top left and bottom right\n" |
| " // corners are in space.\n" |
| msgstr "" |
| "// 可以通过指定左上角和右下角的位置\n" |
| " // 来定义一个矩形。\n" |
| |
| #: src/custom_types/structs.md:41 |
| msgid "// Create struct with field init shorthand\n" |
| msgstr "// 使用字段初始化简写语法创建结构体\n" |
| |
| #: src/custom_types/structs.md:46 |
| msgid "// Print debug struct\n" |
| msgstr "// 打印结构体的调试信息\n" |
| |
| #: src/custom_types/structs.md:49 |
| msgid "// Instantiate a `Point`\n" |
| msgstr "// 实例化一个 `Point`\n" |
| |
| #: src/custom_types/structs.md:53 |
| msgid "// Access the fields of the point\n" |
| msgstr "// 访问点的字段\n" |
| |
| #: src/custom_types/structs.md:54 |
| msgid "\"point coordinates: ({}, {})\"" |
| msgstr "\"点的坐标：({}, {})\"" |
| |
| #: src/custom_types/structs.md:56 |
| msgid "" |
| "// Make a new point by using struct update syntax to use the fields of our\n" |
| " // other one\n" |
| msgstr "" |
| "// 使用结构体更新语法创建新的点，\n" |
| " // 复用之前创建的点的字段\n" |
| |
| #: src/custom_types/structs.md:60 |
| msgid "" |
| "// `bottom_right.y` will be the same as `another_point.y` because we used " |
| "that field\n" |
| " // from `another_point`\n" |
| msgstr "" |
| "// `bottom_right.y` 与 `another_point.y` 相同，\n" |
| " // 因为我们使用了 `another_point` 的该字段\n" |
| |
| #: src/custom_types/structs.md:62 |
| msgid "\"second point: ({}, {})\"" |
| msgstr "\"第二个点：({}, {})\"" |
| |
| #: src/custom_types/structs.md:64 |
| msgid "// Destructure the point using a `let` binding\n" |
| msgstr "// 使用 `let` 绑定解构点\n" |
| |
| #: src/custom_types/structs.md:68 |
| msgid "// struct instantiation is an expression too\n" |
| msgstr "// 结构体实例化也是一个表达式\n" |
| |
| #: src/custom_types/structs.md:73 |
| msgid "// Instantiate a unit struct\n" |
| msgstr "// 实例化一个单元结构体\n" |
| |
| #: src/custom_types/structs.md:76 |
| msgid "// Instantiate a tuple struct\n" |
| msgstr "// 实例化一个元组结构体\n" |
| |
| #: src/custom_types/structs.md:79 |
| msgid "// Access the fields of a tuple struct\n" |
| msgstr "// 访问元组结构体的字段\n" |
| |
| #: src/custom_types/structs.md:80 src/custom_types/structs.md:85 |
| msgid "\"pair contains {:?} and {:?}\"" |
| msgstr "\"pair 包含 {:?} 和 {:?}\"" |
| |
| #: src/custom_types/structs.md:82 |
| msgid "// Destructure a tuple struct\n" |
| msgstr "// 解构一个元组结构体\n" |
| |
| #: src/custom_types/structs.md:91 |
| msgid "" |
| "Add a function `rect_area` which calculates the area of a `Rectangle` (try " |
| "using nested destructuring)." |
| msgstr "" |
| "添加一个 `rect_area` 函数来计算 `Rectangle` 的面积（尝试使用嵌套解构）。" |
| |
| #: src/custom_types/structs.md:93 |
| msgid "" |
| "Add a function `square` which takes a `Point` and a `f32` as arguments, and " |
| "returns a `Rectangle` with its top left corner on the point, and a width and " |
| "height corresponding to the `f32`." |
| msgstr "" |
| "添加一个 `square` 函数，它接受一个 `Point` 和一个 `f32` 作为参数，返回一个 " |
| "`Rectangle`，其左上角在该点上，宽度和高度都等于 `f32` 参数。" |
| |
| #: src/custom_types/structs.md:97 |
| msgid "See also" |
| msgstr "另请参阅" |
| |
| #: src/custom_types/structs.md:99 |
| msgid "" |
| "[`attributes`](../attribute.md), [raw identifiers](../compatibility/" |
| "raw_identifiers.md) and [destructuring](../flow_control/match/" |
| "destructuring.md)" |
| msgstr "" |
| "[`属性`](../attribute.md)、[原始标识符](../compatibility/raw_identifiers.md)" |
| "和[解构](../flow_control/match/destructuring.md)" |
| |
| #: src/custom_types/enum.md:3 |
| msgid "" |
| "The `enum` keyword allows the creation of a type which may be one of a few " |
| "different variants. Any variant which is valid as a `struct` is also valid " |
| "in an `enum`." |
| msgstr "" |
| "`enum` 关键字允许创建一个可能是几种不同变体之一的类型。任何作为 `struct` 有效" |
| "的变体在 `enum` 中也是有效的。" |
| |
| #: src/custom_types/enum.md:8 |
| msgid "" |
| "// Create an `enum` to classify a web event. Note how both\n" |
| "// names and type information together specify the variant:\n" |
| "// `PageLoad != PageUnload` and `KeyPress(char) != Paste(String)`.\n" |
| "// Each is different and independent.\n" |
| msgstr "" |
| "// 创建一个 `enum` 来分类网页事件。注意名称和类型信息如何共同指定变体：\n" |
| "// `PageLoad != PageUnload` 且 `KeyPress(char) != Paste(String)`。\n" |
| "// 每个变体都是不同且独立的。\n" |
| |
| #: src/custom_types/enum.md:13 |
| msgid "// An `enum` variant may either be `unit-like`,\n" |
| msgstr "// `enum` 变体可以类似单元结构体（`unit-like`），\n" |
| |
| #: src/custom_types/enum.md:16 |
| msgid "// like tuple structs,\n" |
| msgstr "// 类似元组结构体，\n" |
| |
| #: src/custom_types/enum.md:19 |
| msgid "// or c-like structures.\n" |
| msgstr "// 或类似 C 语言的结构体。\n" |
| |
| #: src/custom_types/enum.md:22 |
| msgid "" |
| "// A function which takes a `WebEvent` enum as an argument and\n" |
| "// returns nothing.\n" |
| msgstr "// 一个接受 `WebEvent` 枚举作为参数且不返回任何值的函数。\n" |
| |
| #: src/custom_types/enum.md:27 |
| msgid "\"page loaded\"" |
| msgstr "\"页面已加载\"" |
| |
| #: src/custom_types/enum.md:28 |
| msgid "\"page unloaded\"" |
| msgstr "\"页面已卸载\"" |
| |
| #: src/custom_types/enum.md:29 |
| msgid "// Destructure `c` from inside the `enum` variant.\n" |
| msgstr "// 从 `enum` 变体内部解构 `c`。\n" |
| |
| #: src/custom_types/enum.md:30 |
| msgid "\"pressed '{}'.\"" |
| msgstr "\"按下了'{}'键。\"" |
| |
| #: src/custom_types/enum.md:31 |
| msgid "\"pasted \\\"{}\\\".\"" |
| msgstr "\"粘贴了\\\"{}\\\"。\"" |
| |
| #: src/custom_types/enum.md:32 |
| msgid "// Destructure `Click` into `x` and `y`.\n" |
| msgstr "// 将 `Click` 解构为 `x` 和 `y`。\n" |
| |
| #: src/custom_types/enum.md:34 |
| msgid "\"clicked at x={}, y={}.\"" |
| msgstr "\"点击坐标：x={}, y={}。\"" |
| |
| #: src/custom_types/enum.md:40 |
| msgid "'x'" |
| msgstr "'x'" |
| |
| #: src/custom_types/enum.md:41 |
| msgid "// `to_owned()` creates an owned `String` from a string slice.\n" |
| msgstr "// `to_owned()` 从字符串切片创建一个拥有所有权的 `String`。\n" |
| |
| #: src/custom_types/enum.md:42 |
| msgid "\"my text\"" |
| msgstr "\"我的文本\"" |
| |
| #: src/custom_types/enum.md:56 |
| msgid "Type aliases" |
| msgstr "类型别名" |
| |
| #: src/custom_types/enum.md:58 |
| msgid "" |
| "If you use a type alias, you can refer to each enum variant via its alias. " |
| "This might be useful if the enum's name is too long or too generic, and you " |
| "want to rename it." |
| msgstr "" |
| "使用类型别名可以通过别名引用每个枚举变体。当枚举名称过长或过于泛化，而你想重" |
| "命名它时，这会很有用。" |
| |
| #: src/custom_types/enum.md:67 |
| msgid "// Creates a type alias\n" |
| msgstr "// 创建类型别名\n" |
| |
| #: src/custom_types/enum.md:72 |
| msgid "" |
| "// We can refer to each variant via its alias, not its long and " |
| "inconvenient\n" |
| " // name.\n" |
| msgstr "// 我们可以通过别名引用每个变体，而不是使用又长又不便的名称。\n" |
| |
| #: src/custom_types/enum.md:78 |
| msgid "" |
| "The most common place you'll see this is in `impl` blocks using the `Self` " |
| "alias." |
| msgstr "你最常见到这种用法的地方是在使用 `Self` 别名的 `impl` 块中。" |
| |
| #: src/custom_types/enum.md:96 |
| msgid "" |
| "To learn more about enums and type aliases, you can read the [stabilization " |
| "report](https://github.com/rust-lang/rust/pull/61682/" |
| "#issuecomment-502472847) from when this feature was stabilized into Rust." |
| msgstr "" |
| "要了解更多关于枚举和类型别名的信息，你可以阅读这个特性被稳定到 Rust 时的[稳定" |
| "化报告](https://github.com/rust-lang/rust/pull/61682/" |
| "#issuecomment-502472847)。" |
| |
| #: src/custom_types/enum.md:102 |
| msgid "" |
| "[`match`](../flow_control/match.md), [`fn`](../fn.md), and [`String`](../std/" |
| "str.md), [\"Type alias enum variants\" RFC](https://rust-lang.github.io/rfcs/" |
| "2338-type-alias-enum-variants.html)" |
| msgstr "" |
| "[`match`](../flow_control/match.md)、[`fn`](../fn.md)、[`String`](../std/" |
| "str.md) 和 [\"类型别名枚举变体\" RFC](https://rust-lang.github.io/rfcs/2338-" |
| "type-alias-enum-variants.html)" |
| |
| #: src/custom_types/enum/enum_use.md:3 |
| msgid "The `use` declaration can be used so manual scoping isn't needed:" |
| msgstr "`use` 声明可以用来避免手动作用域限定：" |
| |
| #: src/custom_types/enum/enum_use.md:20 |
| msgid "" |
| "// Explicitly `use` each name so they are available without\n" |
| " // manual scoping.\n" |
| msgstr "" |
| "// 显式 `use` 每个名称，使它们可以不需要\n" |
| " // 手动作用域限定就能使用。\n" |
| |
| #: src/custom_types/enum/enum_use.md:23 |
| msgid "// Automatically `use` each name inside `Role`.\n" |
| msgstr "// 自动 `use` `Role` 内的每个名称。\n" |
| |
| #: src/custom_types/enum/enum_use.md:26 |
| msgid "// Equivalent to `Stage::Beginner`.\n" |
| msgstr "// 等同于 `Stage::Beginner`。\n" |
| |
| #: src/custom_types/enum/enum_use.md:28 |
| msgid "// Equivalent to `Role::Student`.\n" |
| msgstr "// 等同于 `Role::Student`。\n" |
| |
| #: src/custom_types/enum/enum_use.md:32 |
| msgid "// Note the lack of scoping because of the explicit `use` above.\n" |
| msgstr "// 注意由于上面的显式 `use`，这里不需要作用域限定。\n" |
| |
| #: src/custom_types/enum/enum_use.md:33 |
| msgid "\"Beginners are starting their learning journey!\"" |
| msgstr "\"初学者正在开始他们的学习之旅！\"" |
| |
| #: src/custom_types/enum/enum_use.md:34 |
| msgid "\"Advanced learners are mastering their subjects...\"" |
| msgstr "\"高级学习者正在掌握他们的科目...\"" |
| |
| #: src/custom_types/enum/enum_use.md:38 |
| msgid "// Note again the lack of scoping.\n" |
| msgstr "// 再次注意这里不需要作用域限定。\n" |
| |
| #: src/custom_types/enum/enum_use.md:39 |
| msgid "\"Students are acquiring knowledge!\"" |
| msgstr "\"学生正在获取知识！\"" |
| |
| #: src/custom_types/enum/enum_use.md:40 |
| msgid "\"Teachers are spreading knowledge!\"" |
| msgstr "\"教师正在传播知识！\"" |
| |
| #: src/custom_types/enum/enum_use.md:47 |
| msgid "[`match`](../../flow_control/match.md) and [`use`](../../mod/use.md)" |
| msgstr "[`match`](../../flow_control/match.md) 和 [`use`](../../mod/use.md)" |
| |
| #: src/custom_types/enum/c_like.md:3 |
| msgid "`enum` can also be used as C-like enums." |
| msgstr "`enum` 也可以像 C 语言那样使用。" |
| |
| #: src/custom_types/enum/c_like.md:8 |
| msgid "// enum with implicit discriminator (starts at 0)\n" |
| msgstr "// 带隐式判别值的枚举（从 0 开始）\n" |
| |
| #: src/custom_types/enum/c_like.md:15 |
| msgid "// enum with explicit discriminator\n" |
| msgstr "// 带显式判别值的枚举\n" |
| |
| #: src/custom_types/enum/c_like.md:24 |
| msgid "// `enums` can be cast as integers.\n" |
| msgstr "// `enum` 可以转换为整数。\n" |
| |
| #: src/custom_types/enum/c_like.md:25 |
| msgid "\"zero is {}\"" |
| msgstr "\"zero 的值是 {}\"" |
| |
| #: src/custom_types/enum/c_like.md:26 |
| msgid "\"one is {}\"" |
| msgstr "\"one 的值是 {}\"" |
| |
| #: src/custom_types/enum/c_like.md:28 |
| msgid "\"roses are #{:06x}\"" |
| msgstr "\"玫瑰的颜色是 #{:06x}\"" |
| |
| #: src/custom_types/enum/c_like.md:29 |
| msgid "\"violets are #{:06x}\"" |
| msgstr "\"紫罗兰的颜色是 #{:06x}\"" |
| |
| #: src/custom_types/enum/c_like.md:35 |
| msgid "[casting](../../types/cast.md)" |
| msgstr "[类型转换](../../types/cast.md)" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:3 |
| msgid "A common way to implement a linked-list is via `enums`:" |
| msgstr "使用 `enum` 是实现链表的常见方法：" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:9 |
| msgid "" |
| "// Cons: Tuple struct that wraps an element and a pointer to the next node\n" |
| msgstr "// Cons：包含一个元素和指向下一节点指针的元组结构体\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:11 |
| msgid "// Nil: A node that signifies the end of the linked list\n" |
| msgstr "// Nil：表示链表末尾的节点\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:14 |
| msgid "// Methods can be attached to an enum\n" |
| msgstr "// 可以为枚举实现方法\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:17 |
| msgid "// Create an empty list\n" |
| msgstr "// 创建空链表\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:19 |
| msgid "// `Nil` has type `List`\n" |
| msgstr "// `Nil` 的类型是 `List`\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:23 |
| msgid "" |
| "// Consume a list, and return the same list with a new element at its front\n" |
| msgstr "// 消耗一个链表，并返回在其头部添加新元素后的链表\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:25 |
| msgid "// `Cons` also has type List\n" |
| msgstr "// `Cons` 的类型也是 List\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:29 |
| msgid "// Return the length of the list\n" |
| msgstr "// 返回链表长度\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:31 |
| msgid "" |
| "// `self` has to be matched, because the behavior of this method\n" |
| " // depends on the variant of `self`\n" |
| " // `self` has type `&List`, and `*self` has type `List`, matching on " |
| "a\n" |
| " // concrete type `T` is preferred over a match on a reference `&T`\n" |
| " // after Rust 2018 you can use self here and tail (with no ref) " |
| "below as well,\n" |
| " // rust will infer &s and ref tail. \n" |
| " // See https://doc.rust-lang.org/edition-guide/rust-2018/ownership-" |
| "and-lifetimes/default-match-bindings.html\n" |
| msgstr "" |
| "// 需要对 `self` 进行匹配，因为方法的行为取决于 `self` 的变体\n" |
| " // `self` 的类型是 `&List`，而 `*self` 的类型是 `List`\n" |
| " // 匹配具体类型 `T` 优于匹配引用 `&T`\n" |
| " // 在 Rust 2018 版本后，这里可以直接使用 self，下面可以使用 tail（无" |
| "需 ref）\n" |
| " // Rust 会自动推断为 &s 和 ref tail\n" |
| " // 参见 https://doc.rust-lang.org/edition-guide/rust-2018/ownership-" |
| "and-lifetimes/default-match-bindings.html\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:39 |
| msgid "" |
| "// Can't take ownership of the tail, because `self` is borrowed;\n" |
| " // instead take a reference to the tail\n" |
| " // And it'a a non-tail recursive call which may cause stack " |
| "overflow for long lists.\n" |
| msgstr "" |
| "// 无法获取 tail 的所有权，因为 `self` 是借用的；\n" |
| " // 所以取 tail 的引用\n" |
| " // 这是一个非尾递归调用，对于长列表可能导致栈溢出。\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:43 |
| msgid "// Base Case: An empty list has zero length\n" |
| msgstr "// 基本情况：空链表长度为零\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:48 |
| msgid "// Return representation of the list as a (heap allocated) string\n" |
| msgstr "// 返回链表的字符串表示（堆分配）\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:52 |
| msgid "" |
| "// `format!` is similar to `print!`, but returns a heap\n" |
| " // allocated string instead of printing to the console\n" |
| msgstr "" |
| "// `format!` 类似于 `print!`，但返回堆分配的字符串，\n" |
| " // 而不是打印到控制台\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:54 src/generics/impl.md:44 |
| msgid "\"{}, {}\"" |
| msgstr "\"{}, {}\"" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:57 |
| msgid "\"Nil\"" |
| msgstr "\"Nil\"" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:64 |
| msgid "// Create an empty linked list\n" |
| msgstr "// 创建空链表\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:67 |
| msgid "// Prepend some elements\n" |
| msgstr "// 在头部添加一些元素\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:72 |
| msgid "// Show the final state of the list\n" |
| msgstr "// 显示链表的最终状态\n" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:73 |
| msgid "\"linked list has length: {}\"" |
| msgstr "\"链表长度为：{}\"" |
| |
| #: src/custom_types/enum/testcase_linked_list.md:80 |
| msgid "[`Box`](../../std/box.md) and [methods](../../fn/methods.md)" |
| msgstr "[`Box`](../../std/box.md) 和[方法](../../fn/methods.md)" |
| |
| #: src/custom_types/constants.md:3 |
| msgid "" |
| "Rust has two different types of constants which can be declared in any scope " |
| "including global. Both require explicit type annotation:" |
| msgstr "" |
| "Rust 有两种常量类型，可以在任何作用域（包括全局作用域）中声明。两者都需要显式" |
| "类型标注：" |
| |
| #: src/custom_types/constants.md:6 |
| msgid "`const`: An unchangeable value (the common case)." |
| msgstr "`const`：不可变值（常见用法）。" |
| |
| #: src/custom_types/constants.md:7 |
| msgid "" |
| "`static`: A possibly mutable variable with [`'static`](../scope/lifetime/" |
| "static_lifetime.md) lifetime. The static lifetime is inferred and does not " |
| "have to be specified. Accessing or modifying a mutable static variable is " |
| "[`unsafe`](../unsafe.md)." |
| msgstr "" |
| "`static`：具有 [`'static`](../scope/lifetime/static_lifetime.md) 生命周期的可" |
| "能可变变量。静态生命周期会被自动推断，无需明确指定。访问或修改可变静态变量是 " |
| "[`unsafe`](../unsafe.md) 的。" |
| |
| #: src/custom_types/constants.md:12 |
| msgid "// Globals are declared outside all other scopes.\n" |
| msgstr "// 全局变量在所有其他作用域之外声明。\n" |
| |
| #: src/custom_types/constants.md:13 |
| msgid "\"Rust\"" |
| msgstr "\"Rust\"" |
| |
| #: src/custom_types/constants.md:17 |
| msgid "// Access constant in some function\n" |
| msgstr "// 在函数中访问常量\n" |
| |
| #: src/custom_types/constants.md:24 |
| msgid "// Access constant in the main thread\n" |
| msgstr "// 在主线程中访问常量\n" |
| |
| #: src/custom_types/constants.md:25 |
| msgid "\"This is {}\"" |
| msgstr "\"这是 {}\"" |
| |
| #: src/custom_types/constants.md:26 |
| msgid "\"The threshold is {}\"" |
| msgstr "\"阈值为 {}\"" |
| |
| #: src/custom_types/constants.md:27 |
| msgid "\"{} is {}\"" |
| msgstr "\"{} 是 {}\"" |
| |
| #: src/custom_types/constants.md:27 |
| msgid "\"big\"" |
| msgstr "\"大的\"" |
| |
| #: src/custom_types/constants.md:27 |
| msgid "\"small\"" |
| msgstr "\"小的\"" |
| |
| #: src/custom_types/constants.md:29 |
| msgid "// Error! Cannot modify a `const`.\n" |
| msgstr "// 错误！不能修改 `const`。\n" |
| |
| #: src/custom_types/constants.md:31 src/variable_bindings/scope.md:22 |
| #: src/variable_bindings/declare.md:27 src/variable_bindings/freeze.md:16 |
| #: src/types/cast.md:19 src/types/cast.md:28 src/flow_control/for.md:95 |
| #: src/scope/borrow.md:41 src/scope/borrow/mut.md:52 src/std/vec.md:32 |
| #: src/std/vec.md:45 src/std/hash/hashset.md:48 |
| msgid "// FIXME ^ Comment out this line\n" |
| msgstr "// 修复：^ 注释掉此行\n" |
| |
| #: src/custom_types/constants.md:37 |
| msgid "" |
| "[The `const`/`static` RFC](https://github.com/rust-lang/rfcs/blob/master/" |
| "text/0246-const-vs-static.md), [`'static` lifetime](../scope/lifetime/" |
| "static_lifetime.md)" |
| msgstr "" |
| "[`const`/`static` RFC](https://github.com/rust-lang/rfcs/blob/master/text/" |
| "0246-const-vs-static.md)，[`'static` 生命周期](../scope/lifetime/" |
| "static_lifetime.md)" |
| |
| #: src/variable_bindings.md:3 |
| msgid "" |
| "Rust provides type safety via static typing. Variable bindings can be type " |
| "annotated when declared. However, in most cases, the compiler will be able " |
| "to infer the type of the variable from the context, heavily reducing the " |
| "annotation burden." |
| msgstr "" |
| "Rust 通过静态类型提供类型安全。变量绑定在声明时可以添加类型注解。然而，在大多" |
| "数情况下，编译器能够从上下文推断出变量类型，大大减少了类型注解的负担。" |
| |
| #: src/variable_bindings.md:8 |
| msgid "" |
| "Values (like literals) can be bound to variables, using the `let` binding." |
| msgstr "可以使用 `let` 关键字将值（如字面量）绑定到变量。" |
| |
| #: src/variable_bindings.md:16 |
| msgid "// copy `an_integer` into `copied_integer`\n" |
| msgstr "// 将 `an_integer` 复制到 `copied_integer`\n" |
| |
| #: src/variable_bindings.md:19 |
| msgid "\"An integer: {:?}\"" |
| msgstr "\"整数：{:?}\"" |
| |
| #: src/variable_bindings.md:20 |
| msgid "\"A boolean: {:?}\"" |
| msgstr "\"布尔值：{:?}\"" |
| |
| #: src/variable_bindings.md:21 |
| msgid "\"Meet the unit value: {:?}\"" |
| msgstr "\"单元值：{:?}\"" |
| |
| #: src/variable_bindings.md:23 |
| msgid "" |
| "// The compiler warns about unused variable bindings; these warnings can\n" |
| " // be silenced by prefixing the variable name with an underscore\n" |
| msgstr "" |
| "// 编译器会对未使用的变量绑定发出警告\n" |
| " // 可以通过在变量名前加下划线来消除这些警告\n" |
| |
| #: src/variable_bindings.md:28 |
| msgid "" |
| "// FIXME ^ Prefix with an underscore to suppress the warning\n" |
| " // Please note that warnings may not be shown in a browser\n" |
| msgstr "" |
| "// 修复：^ 在变量名前加下划线以消除警告\n" |
| " // 注意：在浏览器中可能不会显示警告\n" |
| |
| #: src/variable_bindings/mut.md:3 |
| msgid "" |
| "Variable bindings are immutable by default, but this can be overridden using " |
| "the `mut` modifier." |
| msgstr "变量绑定默认是不可变的，但可以使用 `mut` 修饰符来改变这一行为。" |
| |
| #: src/variable_bindings/mut.md:11 |
| msgid "\"Before mutation: {}\"" |
| msgstr "\"修改前：{}\"" |
| |
| #: src/variable_bindings/mut.md:13 |
| msgid "// Ok\n" |
| msgstr "// 正确\n" |
| |
| #: src/variable_bindings/mut.md:16 |
| msgid "\"After mutation: {}\"" |
| msgstr "\"修改后：{}\"" |
| |
| #: src/variable_bindings/mut.md:18 |
| msgid "// Error! Cannot assign a new value to an immutable variable\n" |
| msgstr "// 错误！不能给不可变变量赋新值\n" |
| |
| #: src/variable_bindings/mut.md:23 |
| msgid "The compiler will throw a detailed diagnostic about mutability errors." |
| msgstr "编译器会对可变性错误给出详细的诊断信息。" |
| |
| #: src/variable_bindings/scope.md:3 |
| msgid "" |
| "Variable bindings have a scope, and are constrained to live in a _block_. A " |
| "block is a collection of statements enclosed by braces `{}`." |
| msgstr "" |
| "变量绑定有作用域，它们被限制在一个**代码块**中生存。代码块是由花括号 `{}` 包" |
| "围的一系列语句。" |
| |
| #: src/variable_bindings/scope.md:8 |
| msgid "// This binding lives in the main function\n" |
| msgstr "// 这个绑定存在于 main 函数中\n" |
| |
| #: src/variable_bindings/scope.md:11 |
| msgid "// This is a block, and has a smaller scope than the main function\n" |
| msgstr "// 这是一个代码块，它的作用域比 main 函数小\n" |
| |
| #: src/variable_bindings/scope.md:13 |
| msgid "// This binding only exists in this block\n" |
| msgstr "// 这个绑定只存在于此代码块中\n" |
| |
| #: src/variable_bindings/scope.md:16 |
| msgid "\"inner short: {}\"" |
| msgstr "\"内部 short：{}\"" |
| |
| #: src/variable_bindings/scope.md:18 |
| msgid "// End of the block\n" |
| msgstr "// 代码块结束\n" |
| |
| #: src/variable_bindings/scope.md:20 |
| msgid "// Error! `short_lived_binding` doesn't exist in this scope\n" |
| msgstr "// 错误！`short_lived_binding` 在此作用域中不存在\n" |
| |
| #: src/variable_bindings/scope.md:21 |
| msgid "\"outer short: {}\"" |
| msgstr "\"外部 short：{}\"" |
| |
| #: src/variable_bindings/scope.md:24 |
| msgid "\"outer long: {}\"" |
| msgstr "\"外部 long：{}\"" |
| |
| #: src/variable_bindings/scope.md:28 |
| msgid "" |
| "Also, [variable shadowing](https://en.wikipedia.org/wiki/Variable_shadowing) " |
| "is allowed." |
| msgstr "" |
| "此外，Rust 允许[变量遮蔽](https://en.wikipedia.org/wiki/Variable_shadowing)。" |
| |
| #: src/variable_bindings/scope.md:35 |
| msgid "\"before being shadowed: {}\"" |
| msgstr "\"被遮蔽前：{}\"" |
| |
| #: src/variable_bindings/scope.md:37 |
| msgid "// This binding *shadows* the outer one\n" |
| msgstr "// 这个绑定*遮蔽*了外部的绑定\n" |
| |
| #: src/variable_bindings/scope.md:38 |
| msgid "\"abc\"" |
| msgstr "\"abc\"" |
| |
| #: src/variable_bindings/scope.md:40 |
| msgid "\"shadowed in inner block: {}\"" |
| msgstr "\"内部代码块中被遮蔽：{}\"" |
| |
| #: src/variable_bindings/scope.md:42 |
| msgid "\"outside inner block: {}\"" |
| msgstr "\"内部代码块外：{}\"" |
| |
| #: src/variable_bindings/scope.md:44 |
| msgid "// This binding *shadows* the previous binding\n" |
| msgstr "// 这个绑定*遮蔽*了之前的绑定\n" |
| |
| #: src/variable_bindings/scope.md:46 |
| msgid "\"shadowed in outer block: {}\"" |
| msgstr "\"外部代码块中被遮蔽：{}\"" |
| |
| #: src/variable_bindings/declare.md:3 |
| msgid "" |
| "It is possible to declare variable bindings first and initialize them later, " |
| "but all variable bindings must be initialized before they are used: the " |
| "compiler forbids use of uninitialized variable bindings, as it would lead to " |
| "undefined behavior." |
| msgstr "" |
| "可以先声明变量绑定然后再初始化，但所有变量绑定在使用前必须先初始化：编译器禁" |
| "止使用未初始化的变量绑定，因为这会导致未定义行为。" |
| |
| #: src/variable_bindings/declare.md:5 |
| msgid "" |
| "It is not common to declare a variable binding and initialize it later in " |
| "the function. It is more difficult for a reader to find the initialization " |
| "when initialization is separated from declaration. It is common to declare " |
| "and initialize a variable binding near where the variable will be used." |
| msgstr "" |
| "在函数中先声明变量绑定而稍后再初始化的做法并不常见。当初始化与声明分离时，读" |
| "者更难找到初始化的位置。更常见的做法是在变量即将使用的地方附近声明并初始化变" |
| "量绑定。" |
| |
| #: src/variable_bindings/declare.md:11 |
| msgid "// Declare a variable binding\n" |
| msgstr "// 声明一个变量绑定\n" |
| |
| #: src/variable_bindings/declare.md:17 |
| msgid "// Initialize the binding\n" |
| msgstr "// 初始化绑定\n" |
| |
| #: src/variable_bindings/declare.md:21 |
| msgid "\"a binding: {}\"" |
| msgstr "\"绑定：{}\"" |
| |
| #: src/variable_bindings/declare.md:25 |
| msgid "// Error! Use of uninitialized binding\n" |
| msgstr "// 错误！使用未初始化的绑定\n" |
| |
| #: src/variable_bindings/declare.md:26 src/variable_bindings/declare.md:31 |
| msgid "\"another binding: {}\"" |
| msgstr "\"另一个绑定：{}\"" |
| |
| #: src/variable_bindings/freeze.md:3 |
| msgid "" |
| "When data is bound by the same name immutably, it also _freezes_. _Frozen_ " |
| "data can't be modified until the immutable binding goes out of scope:" |
| msgstr "" |
| "当数据以相同名称被不可变地绑定时，它也会**冻结**。被冻结的数据在不可变绑定离" |
| "开作用域之前不能被修改：" |
| |
| #: src/variable_bindings/freeze.md:11 |
| msgid "// Shadowing by immutable `_mutable_integer`\n" |
| msgstr "// 通过不可变的 `_mutable_integer` 进行遮蔽\n" |
| |
| #: src/variable_bindings/freeze.md:14 |
| msgid "// Error! `_mutable_integer` is frozen in this scope\n" |
| msgstr "// 错误！`_mutable_integer` 在此作用域中被冻结\n" |
| |
| #: src/variable_bindings/freeze.md:18 |
| msgid "// `_mutable_integer` goes out of scope\n" |
| msgstr "// `_mutable_integer` 离开作用域\n" |
| |
| #: src/variable_bindings/freeze.md:21 |
| msgid "// Ok! `_mutable_integer` is not frozen in this scope\n" |
| msgstr "// 正确！`_mutable_integer` 在此作用域中未被冻结\n" |
| |
| #: src/types.md:3 |
| msgid "" |
| "Rust provides several mechanisms to change or define the type of primitive " |
| "and user defined types. The following sections cover:" |
| msgstr "" |
| "Rust 提供了几种机制来更改或定义原生类型和用户定义类型。以下部分将介绍：" |
| |
| #: src/types.md:6 |
| msgid "[Casting](types/cast.md) between primitive types" |
| msgstr "原生类型之间的[类型转换](types/cast.md)" |
| |
| #: src/types.md:7 |
| msgid "Specifying the desired type of [literals](types/literals.md)" |
| msgstr "指定[字面量](types/literals.md)的类型" |
| |
| #: src/types.md:8 |
| msgid "Using [type inference](types/inference.md)" |
| msgstr "使用[类型推断](types/inference.md)" |
| |
| #: src/types.md:9 |
| msgid "[Aliasing](types/alias.md) types" |
| msgstr "类型[别名](types/alias.md)" |
| |
| #: src/types/cast.md:3 |
| msgid "" |
| "Rust provides no implicit type conversion (coercion) between primitive " |
| "types. But, explicit type conversion (casting) can be performed using the " |
| "`as` keyword." |
| msgstr "" |
| "Rust 不支持原始类型之间的隐式类型转换（强制转换）。但可以使用 `as` 关键字进行" |
| "显式类型转换（转型）。" |
| |
| #: src/types/cast.md:6 |
| msgid "" |
| "Rules for converting between integral types follow C conventions generally, " |
| "except in cases where C has undefined behavior. The behavior of all casts " |
| "between integral types is well defined in Rust." |
| msgstr "" |
| "整数类型之间的转换规则通常遵循 C 语言惯例，但 C 中存在未定义行为的情况除外。" |
| "在 Rust 中，所有整数类型之间的转换行为都有明确定义。" |
| |
| #: src/types/cast.md:11 |
| msgid "// Suppress all warnings from casts which overflow.\n" |
| msgstr "// 抑制所有由溢出转换引起的警告。\n" |
| |
| #: src/types/cast.md:17 |
| msgid "// Error! No implicit conversion\n" |
| msgstr "// 错误！不允许隐式转换\n" |
| |
| #: src/types/cast.md:21 |
| msgid "// Explicit conversion\n" |
| msgstr "// 显式转换\n" |
| |
| #: src/types/cast.md:25 |
| msgid "" |
| "// Error! There are limitations in conversion rules.\n" |
| " // A float cannot be directly converted to a char.\n" |
| msgstr "" |
| "// 错误！转换规则有限制。\n" |
| " // 浮点数不能直接转换为字符。\n" |
| |
| #: src/types/cast.md:30 |
| msgid "\"Casting: {} -> {} -> {}\"" |
| msgstr "\"类型转换：{} -> {} -> {}\"" |
| |
| #: src/types/cast.md:32 |
| msgid "" |
| "// when casting any value to an unsigned type, T,\n" |
| " // T::MAX + 1 is added or subtracted until the value\n" |
| " // fits into the new type\n" |
| msgstr "" |
| "// 当将任何值转换为无符号类型 T 时，\n" |
| " // 会反复加上或减去 T::MAX + 1，直到该值\n" |
| " // 适合新类型\n" |
| |
| #: src/types/cast.md:36 |
| msgid "// 1000 already fits in a u16\n" |
| msgstr "// 1000 已经适合 u16\n" |
| |
| #: src/types/cast.md:37 |
| msgid "\"1000 as a u16 is: {}\"" |
| msgstr "\"1000 转换为 u16 是：{}\"" |
| |
| #: src/types/cast.md:39 |
| msgid "" |
| "// 1000 - 256 - 256 - 256 = 232\n" |
| " // Under the hood, the first 8 least significant bits (LSB) are kept,\n" |
| " // while the rest towards the most significant bit (MSB) get truncated.\n" |
| msgstr "" |
| "// 1000 - 256 - 256 - 256 = 232\n" |
| " // 实际上，保留了最低有效位（LSB）的前 8 位，\n" |
| " // 而朝最高有效位（MSB）方向的其余位被截断。\n" |
| |
| #: src/types/cast.md:42 src/types/cast.md:61 |
| msgid "\"1000 as a u8 is : {}\"" |
| msgstr "\"1000 转换为 u8 是：{}\"" |
| |
| #: src/types/cast.md:43 |
| msgid "// -1 + 256 = 255\n" |
| msgstr "// -1 + 256 = 255\n" |
| |
| #: src/types/cast.md:44 |
| msgid "\" -1 as a u8 is : {}\"" |
| msgstr "\" -1 转换为 u8 是：{}\"" |
| |
| #: src/types/cast.md:46 |
| msgid "// For positive numbers, this is the same as the modulus\n" |
| msgstr "// 对于正数，这等同于取模运算\n" |
| |
| #: src/types/cast.md:47 |
| msgid "\"1000 mod 256 is : {}\"" |
| msgstr "\"1000 对 256 取模是：{}\"" |
| |
| #: src/types/cast.md:49 |
| msgid "" |
| "// When casting to a signed type, the (bitwise) result is the same as\n" |
| " // first casting to the corresponding unsigned type. If the most " |
| "significant\n" |
| " // bit of that value is 1, then the value is negative.\n" |
| msgstr "" |
| "// 当转换为有符号类型时，（按位）结果等同于\n" |
| " // 先转换为对应的无符号类型。如果该值的最高有效位\n" |
| " // 为 1，则该值为负数。\n" |
| |
| #: src/types/cast.md:53 |
| msgid "// Unless it already fits, of course.\n" |
| msgstr "// 当然，如果已经适合的话就不需要转换。\n" |
| |
| #: src/types/cast.md:54 |
| msgid "\" 128 as a i16 is: {}\"" |
| msgstr "\" 128 转换为 i16 是：{}\"" |
| |
| #: src/types/cast.md:56 |
| msgid "" |
| "// In boundary case 128 value in 8-bit two's complement representation is " |
| "-128\n" |
| msgstr "// 边界情况：128 在 8 位二进制补码表示中为 -128\n" |
| |
| #: src/types/cast.md:57 |
| msgid "\" 128 as a i8 is : {}\"" |
| msgstr "\" 128 转换为 i8 是：{}\"" |
| |
| #: src/types/cast.md:59 |
| msgid "" |
| "// repeating the example above\n" |
| " // 1000 as u8 -> 232\n" |
| msgstr "" |
| "// 重复上面的例子\n" |
| " // 1000 转换为 u8 -> 232\n" |
| |
| #: src/types/cast.md:62 |
| msgid "" |
| "// and the value of 232 in 8-bit two's complement representation is -24\n" |
| msgstr "// 而 232 在 8 位二进制补码表示中为 -24\n" |
| |
| #: src/types/cast.md:63 |
| msgid "\" 232 as a i8 is : {}\"" |
| msgstr "\" 232 转换为 i8 是：{}\"" |
| |
| #: src/types/cast.md:65 |
| msgid "" |
| "// Since Rust 1.45, the `as` keyword performs a *saturating cast*\n" |
| " // when casting from float to int. If the floating point value exceeds\n" |
| " // the upper bound or is less than the lower bound, the returned value\n" |
| " // will be equal to the bound crossed.\n" |
| msgstr "" |
| "// 从 Rust 1.45 开始，`as` 关键字在浮点数转整数时执行*饱和转换*\n" |
| " // 如果浮点值超出上界或低于下界，返回值\n" |
| " // 将等于所越过的边界值。\n" |
| |
| #: src/types/cast.md:70 |
| msgid "// 300.0 as u8 is 255\n" |
| msgstr "// 300.0 转换为 u8 是 255\n" |
| |
| #: src/types/cast.md:71 src/types/cast.md:82 |
| msgid "\" 300.0 as u8 is : {}\"" |
| msgstr "\" 300.0 转换为 u8 是：{}\"" |
| |
| #: src/types/cast.md:72 |
| msgid "// -100.0 as u8 is 0\n" |
| msgstr "// -100.0 转换为 u8 是 0\n" |
| |
| #: src/types/cast.md:73 src/types/cast.md:84 |
| msgid "\"-100.0 as u8 is : {}\"" |
| msgstr "\"-100.0 转换为 u8 是：{}\"" |
| |
| #: src/types/cast.md:74 src/types/cast.md:85 |
| msgid "// nan as u8 is 0\n" |
| msgstr "// NaN 转换为 u8 是 0\n" |
| |
| #: src/types/cast.md:75 src/types/cast.md:86 |
| msgid "\" nan as u8 is : {}\"" |
| msgstr "\" NaN 转换为 u8 是：{}\"" |
| |
| #: src/types/cast.md:77 |
| msgid "" |
| "// This behavior incurs a small runtime cost and can be avoided\n" |
| " // with unsafe methods, however the results might overflow and\n" |
| " // return **unsound values**. Use these methods wisely:\n" |
| msgstr "" |
| "// 这种行为会产生少量运行时开销，可以通过不安全方法避免，\n" |
| " // 但结果可能溢出并返回**不可靠的值**。请谨慎使用这些方法：\n" |
| |
| #: src/types/cast.md:81 |
| msgid "// 300.0 as u8 is 44\n" |
| msgstr "// 300.0 转换为 u8 是 44\n" |
| |
| #: src/types/cast.md:83 |
| msgid "// -100.0 as u8 is 156\n" |
| msgstr "// -100.0 转换为 u8 是 156\n" |
| |
| #: src/types/literals.md:3 |
| msgid "" |
| "Numeric literals can be type annotated by adding the type as a suffix. As an " |
| "example, to specify that the literal `42` should have the type `i32`, write " |
| "`42i32`." |
| msgstr "" |
| "数字字面值可以通过添加类型后缀进行类型标注。例如，要指定字面值 `42` 的类型为 " |
| "`i32`，可以写成 `42i32`。" |
| |
| #: src/types/literals.md:6 |
| msgid "" |
| "The type of unsuffixed numeric literals will depend on how they are used. If " |
| "no constraint exists, the compiler will use `i32` for integers, and `f64` " |
| "for floating-point numbers." |
| msgstr "" |
| "无后缀数字字面值的类型取决于其使用方式。如果没有约束，编译器将对整数使用 " |
| "`i32`，对浮点数使用 `f64`。" |
| |
| #: src/types/literals.md:12 |
| msgid "// Suffixed literals, their types are known at initialization\n" |
| msgstr "// 带后缀的字面值，其类型在初始化时确定\n" |
| |
| #: src/types/literals.md:17 |
| msgid "// Unsuffixed literals, their types depend on how they are used\n" |
| msgstr "// 无后缀的字面值，其类型取决于使用方式\n" |
| |
| #: src/types/literals.md:21 |
| msgid "// `size_of_val` returns the size of a variable in bytes\n" |
| msgstr "// `size_of_val` 返回变量的字节大小\n" |
| |
| #: src/types/literals.md:22 |
| msgid "\"size of `x` in bytes: {}\"" |
| msgstr "\"`x` 的字节大小：{}\"" |
| |
| #: src/types/literals.md:23 |
| msgid "\"size of `y` in bytes: {}\"" |
| msgstr "\"`y` 的字节大小：{}\"" |
| |
| #: src/types/literals.md:24 |
| msgid "\"size of `z` in bytes: {}\"" |
| msgstr "\"`z` 的字节大小：{}\"" |
| |
| #: src/types/literals.md:25 |
| msgid "\"size of `i` in bytes: {}\"" |
| msgstr "\"`i` 的字节大小：{}\"" |
| |
| #: src/types/literals.md:26 |
| msgid "\"size of `f` in bytes: {}\"" |
| msgstr "\"`f` 的字节大小：{}\"" |
| |
| #: src/types/literals.md:30 |
| msgid "" |
| "There are some concepts used in the previous code that haven't been " |
| "explained yet, here's a brief explanation for the impatient readers:" |
| msgstr "" |
| "前面的代码中使用了一些尚未解释的概念。为了满足迫不及待的读者，这里简要说明如" |
| "下：" |
| |
| #: src/types/literals.md:33 |
| msgid "" |
| "`std::mem::size_of_val` is a function, but called with its _full path_. Code " |
| "can be split in logical units called _modules_. In this case, the " |
| "`size_of_val` function is defined in the `mem` module, and the `mem` module " |
| "is defined in the `std` _crate_. For more details, see [modules](../mod.md) " |
| "and [crates](../crates.md)." |
| msgstr "" |
| "`std::mem::size_of_val` 是一个函数，这里使用了它的\"完整路径\"来调用。代码可" |
| "以被划分为称为\"模块\"的逻辑单元。在这个例子中，`size_of_val` 函数定义在 " |
| "`mem` 模块中，而 `mem` 模块则定义在 `std` crate 中。更多详情请参阅[模块](../" |
| "mod.md)和[crate](../crates.md)。" |
| |
| #: src/types/inference.md:3 |
| msgid "" |
| "The type inference engine is pretty smart. It does more than looking at the " |
| "type of the value expression during an initialization. It also looks at how " |
| "the variable is used afterwards to infer its type. Here's an advanced " |
| "example of type inference:" |
| msgstr "" |
| "类型推断引擎相当智能。它不仅在初始化时分析值表达式的类型，还会根据变量后续的" |
| "使用方式来推断其类型。下面是一个类型推断的高级示例：" |
| |
| #: src/types/inference.md:10 |
| msgid "" |
| "// Because of the annotation, the compiler knows that `elem` has type u8.\n" |
| msgstr "// 通过类型注解，编译器得知 `elem` 的类型为 u8 \n" |
| |
| #: src/types/inference.md:13 |
| msgid "// Create an empty vector (a growable array).\n" |
| msgstr "// 创建一个空向量（可增长的数组）\n" |
| |
| #: src/types/inference.md:15 |
| msgid "" |
| "// At this point the compiler doesn't know the exact type of `vec`, it\n" |
| " // just knows that it's a vector of something (`Vec<_>`).\n" |
| msgstr "" |
| "// 此时编译器还不知道 `vec` 的具体类型，\n" |
| " // 只知道它是某种类型的向量（`Vec<_>`）。\n" |
| |
| #: src/types/inference.md:18 |
| msgid "// Insert `elem` in the vector.\n" |
| msgstr "// 将 `elem` 插入向量中\n" |
| |
| #: src/types/inference.md:20 |
| msgid "" |
| "// Aha! Now the compiler knows that `vec` is a vector of `u8`s (`Vec<u8>`)\n" |
| " // TODO ^ Try commenting out the `vec.push(elem)` line\n" |
| msgstr "" |
| "// 啊哈！现在编译器知道 `vec` 是 `u8` 类型的向量（`Vec<u8>`）\n" |
| " // TODO ^ 尝试注释掉 `vec.push(elem)` 这一行\n" |
| |
| #: src/types/inference.md:27 |
| msgid "" |
| "No type annotation of variables was needed, the compiler is happy and so is " |
| "the programmer!" |
| msgstr "无需为变量添加类型注解，编译器和程序员都很满意！" |
| |
| #: src/types/alias.md:3 |
| msgid "" |
| "The `type` statement can be used to give a new name to an existing type. " |
| "Types must have `UpperCamelCase` names, or the compiler will raise a " |
| "warning. The exception to this rule are the primitive types: `usize`, `f32`, " |
| "etc." |
| msgstr "" |
| "`type` 语句用于为现有类型创建新名称。类型名必须使用 `UpperCamelCase`（大驼" |
| "峰）命名，否则编译器会发出警告。此规则的例外是原始类型，如 `usize`、`f32` " |
| "等。" |
| |
| #: src/types/alias.md:8 |
| msgid "// `NanoSecond`, `Inch`, and `U64` are new names for `u64`.\n" |
| msgstr "// `NanoSecond`、`Inch` 和 `U64` 都是 `u64` 的新名称。\n" |
| |
| #: src/types/alias.md:14 |
| msgid "// `NanoSecond` = `Inch` = `U64` = `u64`.\n" |
| msgstr "// `NanoSecond` = `Inch` = `U64` = `u64`。\n" |
| |
| #: src/types/alias.md:18 |
| msgid "" |
| "// Note that type aliases *don't* provide any extra type safety, because\n" |
| " // aliases are *not* new types\n" |
| msgstr "// 注意，类型别名*不会*提供额外的类型安全性，因为别名*不是*新类型\n" |
| |
| #: src/types/alias.md:20 |
| msgid "\"{} nanoseconds + {} inches = {} unit?\"" |
| msgstr "\"{} 纳秒 + {} 英寸 = {} 单位？\"" |
| |
| #: src/types/alias.md:27 |
| msgid "" |
| "The main use of aliases is to reduce boilerplate; for example the " |
| "`io::Result<T>` type is an alias for the `Result<T, io::Error>` type." |
| msgstr "" |
| "别名的主要用途是减少重复代码。例如，`io::Result<T>` 类型是 `Result<T, " |
| "io::Error>` 类型的别名。" |
| |
| #: src/types/alias.md:32 |
| msgid "[Attributes](../attribute.md)" |
| msgstr "[属性](../attribute.md)" |
| |
| #: src/conversion.md:3 |
| msgid "" |
| "Primitive types can be converted to each other through [casting](types/" |
| "cast.md)." |
| msgstr "原始类型可以通过[类型转换](types/cast.md)相互转换。" |
| |
| #: src/conversion.md:5 |
| msgid "" |
| "Rust addresses conversion between custom types (i.e., `struct` and `enum`) " |
| "by the use of [traits](trait.md). The generic conversions will use 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. However " |
| "there are more specific ones for the more common cases, in particular when " |
| "converting to and from `String`s." |
| msgstr "" |
| "Rust 通过使用[特质](trait.md)来处理自定义类型（如 `struct` 和 `enum`）之间的" |
| "转换。通用转换使用 [`From`](https://doc.rust-lang.org/std/convert/" |
| "trait.From.html) 和 [`Into`](https://doc.rust-lang.org/std/convert/" |
| "trait.Into.html) 特质。然而，对于更常见的情况，特别是与 `String` 相互转换时，" |
| "还有一些更具体的特质。" |
| |
| #: src/conversion/from_into.md:3 |
| msgid "" |
| "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 are " |
| "inherently linked, and this is actually part of its implementation. If you " |
| "are able to convert type A from type B, then it should be easy to believe " |
| "that we should be able to convert type B to type A." |
| msgstr "" |
| "[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 和 [`Into`]" |
| "(https://doc.rust-lang.org/std/convert/trait.Into.html) 特质本质上是相互关联" |
| "的，这实际上是其实现的一部分。如果你能将类型 A 从类型 B 转换，那么我们也应该" |
| "能够将类型 B 转换为类型 A。" |
| |
| #: src/conversion/from_into.md:7 |
| msgid "`From`" |
| msgstr "`From`" |
| |
| #: src/conversion/from_into.md:9 |
| msgid "" |
| "The [`From`](https://doc.rust-lang.org/std/convert/trait.From.html) trait " |
| "allows for a type to define how to create itself from another type, hence " |
| "providing a very simple mechanism for converting between several types. " |
| "There are numerous implementations of this trait within the standard library " |
| "for conversion of primitive and common types." |
| msgstr "" |
| "[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) 特质允许一个" |
| "类型定义如何从另一个类型创建自身，从而提供了一种非常简单的机制来在多种类型之" |
| "间进行转换。标准库中有许多这个特质的实现，用于原始类型和常见类型的转换。" |
| |
| #: src/conversion/from_into.md:14 |
| msgid "For example we can easily convert a `str` into a `String`" |
| msgstr "例如，我们可以轻松地将 `str` 转换为 `String`" |
| |
| #: src/conversion/from_into.md:21 |
| msgid "We can do something similar for defining a conversion for our own type." |
| msgstr "我们可以为自己的类型定义类似的转换。" |
| |
| #: src/conversion/from_into.md:39 src/conversion/from_into.md:68 |
| #: src/conversion/from_into.md:98 |
| msgid "\"My number is {:?}\"" |
| msgstr "\"我的数字是 {:?}\"" |
| |
| #: src/conversion/from_into.md:43 |
| msgid "`Into`" |
| msgstr "`Into`" |
| |
| #: src/conversion/from_into.md:45 |
| msgid "" |
| "The [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) trait is " |
| "simply the reciprocal of the `From` trait. It defines how to convert a type " |
| "into another type." |
| msgstr "" |
| "[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) 特质简单来说" |
| "就是 `From` 特质的反向操作。它定义了如何将一个类型转换为另一个类型。" |
| |
| #: src/conversion/from_into.md:48 |
| msgid "" |
| "Calling `into()` typically requires us to specify the result type as the " |
| "compiler is unable to determine this most of the time." |
| msgstr "" |
| "调用 `into()` 通常需要我们指定结果类型，因为编译器大多数时候无法确定这一点。" |
| |
| #: src/conversion/from_into.md:66 |
| msgid "// Try removing the type annotation\n" |
| msgstr "// 尝试移除类型标注\n" |
| |
| #: src/conversion/from_into.md:72 |
| msgid "`From` and `Into` are interchangeable" |
| msgstr "`From` 和 `Into` 是可互换的" |
| |
| #: src/conversion/from_into.md:74 |
| msgid "" |
| "`From` and `Into` are designed to be complementary. We do not need to " |
| "provide an implementation for both traits. If you have implemented the " |
| "`From` trait for your type, `Into` will call it when necessary. Note, " |
| "however, that the converse is not true: implementing `Into` for your type " |
| "will not automatically provide it with an implementation of `From`." |
| msgstr "" |
| "`From` 和 `Into` 被设计为互补的。我们不需要为两个特质都提供实现。如果你为你的" |
| "类型实现了 `From` 特质，`Into` 会在必要时调用它。但请注意，反过来并不成立：为" |
| "你的类型实现 `Into` 不会自动为它提供 `From` 的实现。" |
| |
| #: src/conversion/from_into.md:86 |
| msgid "// Define `From`\n" |
| msgstr "// 定义 `From`\n" |
| |
| #: src/conversion/from_into.md:96 |
| msgid "// use `Into`\n" |
| msgstr "// 使用 `Into`\n" |
| |
| #: src/conversion/try_from_try_into.md:3 |
| msgid "" |
| "Similar to [`From` and `Into`](from_into.html), [`TryFrom`](https://doc.rust-" |
| "lang.org/std/convert/trait.TryFrom.html) and [`TryInto`](https://doc.rust-" |
| "lang.org/std/convert/trait.TryInto.html) are generic traits for converting " |
| "between types. Unlike `From`/`Into`, the `TryFrom`/`TryInto` traits are used " |
| "for fallible conversions, and as such, return [`Result`](https://doc.rust-" |
| "lang.org/std/result/enum.Result.html)s." |
| msgstr "" |
| "与 [`From` 和 `Into`](from_into.html) 类似，[`TryFrom`] 和 [`TryInto`] 是用于" |
| "类型转换的泛型特质。与 `From`/`Into` 不同，`TryFrom`/`TryInto` 特质用于可能失" |
| "败的转换，因此返回 [`Result`]。\n" |
| "\n" |
| "[`TryFrom`]: https://doc.rust-lang.org/std/convert/trait.TryFrom.html\n" |
| "[`TryInto`]: https://doc.rust-lang.org/std/convert/trait.TryInto.html\n" |
| "[`Result`]: https://doc.rust-lang.org/std/result/enum.Result.html" |
| |
| #: src/conversion/try_from_try_into.md:33 |
| msgid "// TryFrom\n" |
| msgstr "// TryFrom\n" |
| |
| #: src/conversion/try_from_try_into.md:38 |
| msgid "// TryInto\n" |
| msgstr "// TryInto\n" |
| |
| #: src/conversion/string.md:1 |
| msgid "To and from Strings" |
| msgstr "字符串的转换" |
| |
| #: src/conversion/string.md:3 |
| msgid "Converting to String" |
| msgstr "转换为字符串" |
| |
| #: src/conversion/string.md:5 |
| msgid "" |
| "To convert any type to a `String` is as simple as implementing the " |
| "[`ToString`](https://doc.rust-lang.org/std/string/trait.ToString.html) trait " |
| "for the type. Rather than doing so directly, you should implement the " |
| "[`fmt::Display`](https://doc.rust-lang.org/std/fmt/trait.Display.html) trait " |
| "which automatically provides [`ToString`](https://doc.rust-lang.org/std/" |
| "string/trait.ToString.html) and also allows printing the type as discussed " |
| "in the section on [`print!`](../hello/print.md)." |
| msgstr "" |
| "要将任何类型转换为 `String`，只需为该类型实现 [`ToString`](https://doc.rust-" |
| "lang.org/std/string/trait.ToString.html) 特质即可。但更好的做法是实现 " |
| "[`fmt::Display`](https://doc.rust-lang.org/std/fmt/trait.Display.html) 特质，" |
| "它不仅会自动提供 [`ToString`](https://doc.rust-lang.org/std/string/trait." |
| "ToString.html)，还允许打印该类型，就像在 [`print!`](../hello/print.md) 部分" |
| "讨论的那样。" |
| |
| #: src/conversion/string.md:19 |
| msgid "\"Circle of radius {}\"" |
| msgstr "\"半径为 {} 的圆\"" |
| |
| #: src/conversion/string.md:29 |
| msgid "Parsing a String" |
| msgstr "解析字符串" |
| |
| #: src/conversion/string.md:31 |
| msgid "" |
| "It's useful to convert strings into many types, but one of the more common " |
| "string operations is to convert them from string to number. The idiomatic " |
| "approach to this is to use the [`parse`](https://doc.rust-lang.org/std/" |
| "primitive.str.html#method.parse) function and either to arrange for type " |
| "inference or to specify the type to parse using the 'turbofish' syntax. Both " |
| "alternatives are shown in the following example." |
| msgstr "" |
| "将字符串转换为其他类型很有用，其中最常见的操作之一是将字符串转换为数字。惯用" |
| "的方法是使用 [`parse`] 函数，可以通过类型推断或使用\"涡轮鱼\"语法指定要解析的" |
| "类型。以下示例展示了这两种方法。\n" |
| "\n" |
| "[`parse`]: https://doc.rust-lang.org/std/primitive.str.html#method.parse" |
| |
| #: src/conversion/string.md:37 |
| msgid "" |
| "This will convert the string into the type specified as long as the " |
| "[`FromStr`](https://doc.rust-lang.org/std/str/trait.FromStr.html) trait is " |
| "implemented for that type. This is implemented for numerous types within the " |
| "standard library." |
| msgstr "" |
| "只要为目标类型实现了 [`FromStr`] 特质，就可以将字符串转换为指定的类型。标准库" |
| "中为许多类型实现了这个特质。\n" |
| "\n" |
| "[`FromStr`]: https://doc.rust-lang.org/std/str/trait.FromStr.html" |
| |
| #: src/conversion/string.md:43 src/std_misc/process/wait.md:10 |
| msgid "\"5\"" |
| msgstr "\"5\"" |
| |
| #: src/conversion/string.md:44 src/error/result.md:33 src/error/result.md:68 |
| #: src/error/result/result_map.md:42 src/error/result/result_map.md:75 |
| #: src/error/result/result_alias.md:36 src/error/result/early_returns.md:36 |
| #: src/error/result/enter_question_mark.md:34 |
| #: src/error/result/enter_question_mark.md:67 |
| msgid "\"10\"" |
| msgstr "\"10\"" |
| |
| #: src/conversion/string.md:47 |
| msgid "\"Sum: {:?}\"" |
| msgstr "\"总和：{:?}\"" |
| |
| #: src/conversion/string.md:51 |
| msgid "" |
| "To obtain this functionality on a user defined type simply implement the " |
| "[`FromStr`](https://doc.rust-lang.org/std/str/trait.FromStr.html) trait for " |
| "that type." |
| msgstr "" |
| "要在自定义类型上获得这个功能，只需为该类型实现 [`FromStr`] 特质。\n" |
| "\n" |
| "[`FromStr`]: https://doc.rust-lang.org/std/str/trait.FromStr.html" |
| |
| #: src/conversion/string.md:74 |
| msgid "\" 3 \"" |
| msgstr "\" 3 \"" |
| |
| #: src/expression.md:3 |
| msgid "A Rust program is (mostly) made up of a series of statements:" |
| msgstr "Rust 程序（主要）由一系列语句组成：" |
| |
| #: src/expression.md:7 |
| msgid "" |
| "// statement\n" |
| " // statement\n" |
| " // statement\n" |
| msgstr "" |
| "// 语句\n" |
| " // 语句\n" |
| " // 语句\n" |
| |
| #: src/expression.md:13 |
| msgid "" |
| "There are a few kinds of statements in Rust. The most common two are " |
| "declaring a variable binding, and using a `;` with an expression:" |
| msgstr "" |
| "Rust 中有几种语句。最常见的两种是声明变量绑定，以及在表达式后使用分号 `;`：" |
| |
| #: src/expression.md:18 |
| msgid "// variable binding\n" |
| msgstr "// 变量绑定\n" |
| |
| #: src/expression.md:21 |
| msgid "// expression;\n" |
| msgstr "// 表达式;\n" |
| |
| #: src/expression.md:28 |
| msgid "" |
| "Blocks are expressions too, so they can be used as values in assignments. " |
| "The last expression in the block will be assigned to the place expression " |
| "such as a local variable. However, if the last expression of the block ends " |
| "with a semicolon, the return value will be `()`." |
| msgstr "" |
| "代码块也是表达式，因此可以在赋值中作为值使用。代码块中的最后一个表达式会被赋" |
| "值给左值表达式（如局部变量）。但是，如果代码块的最后一个表达式以分号结尾，返" |
| "回值将是 `()`。" |
| |
| #: src/expression.md:41 |
| msgid "// This expression will be assigned to `y`\n" |
| msgstr "// 这个表达式将被赋值给 `y`\n" |
| |
| #: src/expression.md:46 |
| msgid "" |
| "// The semicolon suppresses this expression and `()` is assigned to `z`\n" |
| msgstr "// 分号抑制了这个表达式，`()` 被赋值给 `z`\n" |
| |
| #: src/expression.md:50 |
| msgid "\"x is {:?}\"" |
| msgstr "\"x 是 {:?}\"" |
| |
| #: src/expression.md:51 |
| msgid "\"y is {:?}\"" |
| msgstr "\"y 是 {:?}\"" |
| |
| #: src/expression.md:52 |
| msgid "\"z is {:?}\"" |
| msgstr "\"z 是 {:?}\"" |
| |
| #: src/flow_control.md:3 |
| msgid "" |
| "An integral part of any programming language are ways to modify control " |
| "flow: `if`/`else`, `for`, and others. Let's talk about them in Rust." |
| msgstr "" |
| "控制流是任何编程语言的重要组成部分，如 `if`/`else`、`for` 等。让我们来讨论 " |
| "Rust 中的这些内容。" |
| |
| #: src/flow_control/if_else.md:3 |
| msgid "" |
| "Branching with `if`\\-`else` is similar to other languages. Unlike many of " |
| "them, the boolean condition doesn't need to be surrounded by parentheses, " |
| "and each condition is followed by a block. `if`\\-`else` conditionals are " |
| "expressions, and, all branches must return the same type." |
| msgstr "" |
| "`if`-`else` 分支结构与其他语言类似。不同之处在于，布尔条件不需要用括号括起" |
| "来，每个条件后面都跟着一个代码块。`if`-`else` 条件是表达式，所有分支必须返回" |
| "相同的类型。" |
| |
| #: src/flow_control/if_else.md:13 |
| msgid "\"{} is negative\"" |
| msgstr "\"{} 是负数\"" |
| |
| #: src/flow_control/if_else.md:15 |
| msgid "\"{} is positive\"" |
| msgstr "\"{} 是正数\"" |
| |
| #: src/flow_control/if_else.md:17 |
| msgid "\"{} is zero\"" |
| msgstr "\"{} 是零\"" |
| |
| #: src/flow_control/if_else.md:22 |
| msgid "\", and is a small number, increase ten-fold\"" |
| msgstr "\"，是一个小数字，扩大十倍\"" |
| |
| #: src/flow_control/if_else.md:24 |
| msgid "// This expression returns an `i32`.\n" |
| msgstr "// 这个表达式返回 `i32` 类型。\n" |
| |
| #: src/flow_control/if_else.md:27 |
| msgid "\", and is a big number, halve the number\"" |
| msgstr "\"，是一个大数字，将数字减半\"" |
| |
| #: src/flow_control/if_else.md:29 |
| msgid "// This expression must return an `i32` as well.\n" |
| msgstr "// 这个表达式也必须返回 `i32` 类型。\n" |
| |
| #: src/flow_control/if_else.md:31 |
| msgid "// TODO ^ Try suppressing this expression with a semicolon.\n" |
| msgstr "// TODO ^ 尝试用分号结束这个表达式。\n" |
| |
| #: src/flow_control/if_else.md:33 |
| msgid "" |
| "// ^ Don't forget to put a semicolon here! All `let` bindings need it.\n" |
| msgstr "// ^ 别忘了在这里加分号！所有 `let` 绑定都需要它。\n" |
| |
| #: src/flow_control/if_else.md:35 src/flow_control/match.md:35 |
| msgid "\"{} -> {}\"" |
| msgstr "\"{} -> {}\"" |
| |
| #: src/flow_control/loop.md:3 |
| msgid "Rust provides a `loop` keyword to indicate an infinite loop." |
| msgstr "Rust 提供 `loop` 关键字来表示无限循环。" |
| |
| #: src/flow_control/loop.md:5 |
| msgid "" |
| "The `break` statement can be used to exit a loop at anytime, whereas the " |
| "`continue` statement can be used to skip the rest of the iteration and start " |
| "a new one." |
| msgstr "" |
| "`break` 语句可以随时退出循环，而 `continue` 语句可以跳过当前迭代的剩余部分并" |
| "开始下一次迭代。" |
| |
| #: src/flow_control/loop.md:13 |
| msgid "\"Let's count until infinity!\"" |
| msgstr "\"让我们数到无穷大！\"" |
| |
| #: src/flow_control/loop.md:15 |
| msgid "// Infinite loop\n" |
| msgstr "// 无限循环\n" |
| |
| #: src/flow_control/loop.md:20 |
| msgid "\"three\"" |
| msgstr "\"three\"" |
| |
| #: src/flow_control/loop.md:22 |
| msgid "// Skip the rest of this iteration\n" |
| msgstr "// 跳过本次迭代的剩余部分\n" |
| |
| #: src/flow_control/loop.md:29 |
| msgid "\"OK, that's enough\"" |
| msgstr "\"好了，够了\"" |
| |
| #: src/flow_control/loop.md:31 |
| msgid "// Exit this loop\n" |
| msgstr "// 退出这个循环\n" |
| |
| #: src/flow_control/loop/nested.md:3 |
| msgid "" |
| "It's possible to `break` or `continue` outer loops when dealing with nested " |
| "loops. In these cases, the loops must be annotated with some `'label`, and " |
| "the label must be passed to the `break`/`continue` statement." |
| msgstr "" |
| "在处理嵌套循环时，可以 `break` 或 `continue` 外层循环。这种情况下，循环必须" |
| "用 `'label` 标记，并且必须将标签传递给 `break`/`continue` 语句。" |
| |
| #: src/flow_control/loop/nested.md:12 |
| msgid "\"Entered the outer loop\"" |
| msgstr "\"进入外层循环\"" |
| |
| #: src/flow_control/loop/nested.md:15 |
| msgid "\"Entered the inner loop\"" |
| msgstr "\"进入内层循环\"" |
| |
| #: src/flow_control/loop/nested.md:17 |
| msgid "" |
| "// This would break only the inner loop\n" |
| " //break;\n" |
| msgstr "" |
| "// 这只会中断内层循环\n" |
| " //break;\n" |
| |
| #: src/flow_control/loop/nested.md:20 |
| msgid "// This breaks the outer loop\n" |
| msgstr "// 这会中断外层循环\n" |
| |
| #: src/flow_control/loop/nested.md:24 |
| msgid "\"This point will never be reached\"" |
| msgstr "\"这一点永远不会到达\"" |
| |
| #: src/flow_control/loop/nested.md:27 |
| msgid "\"Exited the outer loop\"" |
| msgstr "\"退出外层循环\"" |
| |
| #: src/flow_control/loop/return.md:3 |
| msgid "" |
| "One of the uses of a `loop` is to retry an operation until it succeeds. If " |
| "the operation returns a value though, you might need to pass it to the rest " |
| "of the code: put it after the `break`, and it will be returned by the `loop` " |
| "expression." |
| msgstr "" |
| "`loop` 的一个用途是重试操作直到成功。如果操作返回一个值，你可能需要将它传递给" |
| "代码的其余部分：将它放在 `break` 之后，它将被 `loop` 表达式返回。" |
| |
| #: src/flow_control/while.md:3 |
| msgid "" |
| "The `while` keyword can be used to run a loop while a condition is true." |
| msgstr "`while` 关键字用于在条件为真时运行循环。" |
| |
| #: src/flow_control/while.md:5 |
| msgid "" |
| "Let's write the infamous [FizzBuzz](https://en.wikipedia.org/wiki/Fizz_buzz) " |
| "using a `while` loop." |
| msgstr "" |
| "让我们用 `while` 循环来编写著名的 [FizzBuzz](https://en.wikipedia.org/wiki/" |
| "Fizz_buzz) 程序。" |
| |
| #: src/flow_control/while.md:9 |
| msgid "// A counter variable\n" |
| msgstr "// 计数器变量\n" |
| |
| #: src/flow_control/while.md:12 |
| msgid "// Loop while `n` is less than 101\n" |
| msgstr "// 当 `n` 小于 101 时继续循环\n" |
| |
| #: src/flow_control/while.md:15 src/flow_control/for.md:17 |
| #: src/flow_control/for.md:37 src/fn.md:34 |
| msgid "\"fizzbuzz\"" |
| msgstr "\"fizzbuzz\"" |
| |
| #: src/flow_control/while.md:17 src/flow_control/for.md:19 |
| #: src/flow_control/for.md:39 src/fn.md:36 |
| msgid "\"fizz\"" |
| msgstr "\"fizz\"" |
| |
| #: src/flow_control/while.md:19 src/flow_control/for.md:21 |
| #: src/flow_control/for.md:41 src/fn.md:38 |
| msgid "\"buzz\"" |
| msgstr "\"buzz\"" |
| |
| #: src/flow_control/while.md:24 |
| msgid "// Increment counter\n" |
| msgstr "// 计数器递增\n" |
| |
| #: src/flow_control/for.md:1 |
| msgid "for loops" |
| msgstr "for 循环" |
| |
| #: src/flow_control/for.md:5 |
| msgid "" |
| "The `for in` construct can be used to iterate through an `Iterator`. One of " |
| "the easiest ways to create an iterator is to use the range notation `a..b`. " |
| "This yields values from `a` (inclusive) to `b` (exclusive) in steps of one." |
| msgstr "" |
| "`for in` 结构可用于遍历 `Iterator`。创建迭代器最简单的方法之一是使用区间表示" |
| "法 `a..b`。这会生成从 `a`（包含）到 `b`（不包含）的值，步长为 1。" |
| |
| #: src/flow_control/for.md:10 |
| msgid "Let's write FizzBuzz using `for` instead of `while`." |
| msgstr "让我们用 `for` 而不是 `while` 来编写 FizzBuzz。" |
| |
| #: src/flow_control/for.md:14 src/flow_control/for.md:34 |
| msgid "// `n` will take the values: 1, 2, ..., 100 in each iteration\n" |
| msgstr "// `n` 在每次迭代中将取值：1, 2, ..., 100\n" |
| |
| #: src/flow_control/for.md:29 |
| msgid "" |
| "Alternatively, `a..=b` can be used for a range that is inclusive on both " |
| "ends. The above can be written as:" |
| msgstr "另外，可以使用 `a..=b` 表示两端都包含的范围。上面的代码可以改写为：" |
| |
| #: src/flow_control/for.md:49 |
| msgid "for and iterators" |
| msgstr "for 与迭代器" |
| |
| #: src/flow_control/for.md:51 |
| msgid "" |
| "The `for in` construct is able to interact with an `Iterator` in several " |
| "ways. As discussed in the section on the [Iterator](../trait/iter.md) trait, " |
| "by default the `for` loop will apply the `into_iter` function to the " |
| "collection. However, this is not the only means of converting collections " |
| "into iterators." |
| msgstr "" |
| "`for in` 结构能以多种方式与 `Iterator` 交互。正如在 [Iterator](../trait/" |
| "iter.md) 特质一节中讨论的那样，默认情况下 `for` 循环会对集合应用 `into_iter` " |
| "函数。然而，这并不是将集合转换为迭代器的唯一方法。" |
| |
| #: src/flow_control/for.md:56 |
| msgid "" |
| "`into_iter`, `iter` and `iter_mut` all handle the conversion of a collection " |
| "into an iterator in different ways, by providing different views on the data " |
| "within." |
| msgstr "" |
| "`into_iter`、`iter` 和 `iter_mut` 都以不同的方式处理集合到迭代器的转换，通过" |
| "提供对数据的不同视图。" |
| |
| #: src/flow_control/for.md:60 |
| msgid "" |
| "`iter` - This borrows each element of the collection through each iteration. " |
| "Thus leaving the collection untouched and available for reuse after the loop." |
| msgstr "" |
| "`iter` - 在每次迭代中借用集合的每个元素。因此，集合保持不变，并且在循环之后可" |
| "以重复使用。" |
| |
| #: src/flow_control/for.md:65 src/flow_control/for.md:85 |
| #: src/flow_control/for.md:104 |
| msgid "\"Frank\"" |
| msgstr "\"Frank\"" |
| |
| #: src/flow_control/for.md:65 src/flow_control/for.md:69 |
| #: src/flow_control/for.md:85 src/flow_control/for.md:89 |
| #: src/flow_control/for.md:104 src/flow_control/for.md:108 |
| msgid "\"Ferris\"" |
| msgstr "\"Ferris\"" |
| |
| #: src/flow_control/for.md:69 src/flow_control/for.md:89 |
| #: src/flow_control/for.md:108 |
| msgid "\"There is a rustacean among us!\"" |
| msgstr "\"我们中间有一个 Rustacean！\"" |
| |
| #: src/flow_control/for.md:70 |
| msgid "// TODO ^ Try deleting the & and matching just \"Ferris\"\n" |
| msgstr "// TODO ^ 尝试删除 & 并只匹配 \"Ferris\"\n" |
| |
| #: src/flow_control/for.md:71 src/flow_control/for.md:90 |
| msgid "\"Hello {}\"" |
| msgstr "\"你好 {}\"" |
| |
| #: src/flow_control/for.md:75 src/flow_control/for.md:94 |
| #: src/flow_control/for.md:113 |
| msgid "\"names: {:?}\"" |
| msgstr "\"names: {:?}\"" |
| |
| #: src/flow_control/for.md:79 |
| msgid "" |
| "`into_iter` - This consumes the collection so that on each iteration the " |
| "exact data is provided. Once the collection has been consumed it is no " |
| "longer available for reuse as it has been 'moved' within the loop." |
| msgstr "" |
| "`into_iter` - 这会消耗集合，使得在每次迭代中提供确切的数据。一旦集合被消耗，" |
| "它就不再可用于重复使用，因为它已经在循环中被\"移动\"了。" |
| |
| #: src/flow_control/for.md:99 |
| msgid "" |
| "`iter_mut` - This mutably borrows each element of the collection, allowing " |
| "for the collection to be modified in place." |
| msgstr "`iter_mut` - 这会可变地借用集合的每个元素，允许在原地修改集合。" |
| |
| #: src/flow_control/for.md:109 |
| msgid "\"Hello\"" |
| msgstr "\"你好\"" |
| |
| #: src/flow_control/for.md:117 |
| msgid "" |
| "In the above snippets note the type of `match` branch, that is the key " |
| "difference in the types of iteration. The difference in type then of course " |
| "implies differing actions that are able to be performed." |
| msgstr "" |
| "在上面的代码片段中，注意 `match` 分支的类型，这是迭代类型的关键区别。类型的差" |
| "异意味着可以执行不同的操作。" |
| |
| #: src/flow_control/for.md:123 |
| msgid "[Iterator](../trait/iter.md)" |
| msgstr "[迭代器](../trait/iter.md)" |
| |
| #: src/flow_control/match.md:3 |
| msgid "" |
| "Rust provides pattern matching via the `match` keyword, which can be used " |
| "like a C `switch`. The first matching arm is evaluated and all possible " |
| "values must be covered." |
| msgstr "" |
| "Rust 通过 `match` 关键字提供模式匹配，类似于 C 语言的 `switch`。第一个匹配的" |
| "分支会被求值，并且必须覆盖所有可能的值。" |
| |
| #: src/flow_control/match.md:10 |
| msgid "// TODO ^ Try different values for `number`\n" |
| msgstr "// TODO ^ 尝试为 `number` 赋不同的值\n" |
| |
| #: src/flow_control/match.md:12 |
| msgid "\"Tell me about {}\"" |
| msgstr "\"告诉我关于 {} 的信息\"" |
| |
| #: src/flow_control/match.md:14 |
| msgid "// Match a single value\n" |
| msgstr "// 匹配单个值\n" |
| |
| #: src/flow_control/match.md:15 |
| msgid "\"One!\"" |
| msgstr "\"一！\"" |
| |
| #: src/flow_control/match.md:16 |
| msgid "// Match several values\n" |
| msgstr "// 匹配多个值\n" |
| |
| #: src/flow_control/match.md:17 |
| msgid "\"This is a prime\"" |
| msgstr "\"这是个质数\"" |
| |
| #: src/flow_control/match.md:18 |
| msgid "" |
| "// TODO ^ Try adding 13 to the list of prime values\n" |
| " // Match an inclusive range\n" |
| msgstr "" |
| "// TODO ^ 尝试将 13 添加到质数列表中\n" |
| " // 匹配一个闭区间范围\n" |
| |
| #: src/flow_control/match.md:20 |
| msgid "\"A teen\"" |
| msgstr "\"一个青少年\"" |
| |
| #: src/flow_control/match.md:21 |
| msgid "// Handle the rest of cases\n" |
| msgstr "// 处理其余情况\n" |
| |
| #: src/flow_control/match.md:22 |
| msgid "\"Ain't special\"" |
| msgstr "\"没什么特别的\"" |
| |
| #: src/flow_control/match.md:23 |
| msgid "// TODO ^ Try commenting out this catch-all arm\n" |
| msgstr "// TODO ^ 尝试注释掉这个匹配所有情况的分支\n" |
| |
| #: src/flow_control/match.md:27 |
| msgid "// Match is an expression too\n" |
| msgstr "// match 也是一个表达式\n" |
| |
| #: src/flow_control/match.md:29 |
| msgid "// The arms of a match must cover all the possible values\n" |
| msgstr "// match 的分支必须覆盖所有可能的值\n" |
| |
| #: src/flow_control/match.md:32 |
| msgid "// TODO ^ Try commenting out one of these arms\n" |
| msgstr "// TODO ^ 尝试注释掉其中一个分支\n" |
| |
| #: src/flow_control/match/destructuring.md:3 |
| msgid "A `match` block can destructure items in a variety of ways." |
| msgstr "`match` 块可以以多种方式解构项。" |
| |
| #: src/flow_control/match/destructuring.md:5 |
| msgid "[Destructuring Tuples](destructuring/destructure_tuple.md)" |
| msgstr "[解构元组](destructuring/destructure_tuple.md)" |
| |
| #: src/flow_control/match/destructuring.md:6 |
| msgid "[Destructuring Arrays and Slices](destructuring/destructure_slice.md)" |
| msgstr "[解构数组和切片](destructuring/destructure_slice.md)" |
| |
| #: src/flow_control/match/destructuring.md:7 |
| msgid "[Destructuring Enums](destructuring/destructure_enum.md)" |
| msgstr "[解构枚举](destructuring/destructure_enum.md)" |
| |
| #: src/flow_control/match/destructuring.md:8 |
| msgid "[Destructuring Pointers](destructuring/destructure_pointers.md)" |
| msgstr "[解构指针](destructuring/destructure_pointers.md)" |
| |
| #: src/flow_control/match/destructuring.md:9 |
| msgid "[Destructuring Structures](destructuring/destructure_structures.md)" |
| msgstr "[解构结构体](destructuring/destructure_structures.md)" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:3 |
| msgid "Tuples can be destructured in a `match` as follows:" |
| msgstr "元组可以在 `match` 中按如下方式解构：" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:8 |
| msgid "// TODO ^ Try different values for `triple`\n" |
| msgstr "// TODO ^ 尝试为 `triple` 赋不同的值\n" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:10 |
| msgid "\"Tell me about {:?}\"" |
| msgstr "\"告诉我关于 {:?} 的信息\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:11 |
| msgid "// Match can be used to destructure a tuple\n" |
| msgstr "// match 可用于解构元组\n" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:13 |
| msgid "// Destructure the second and third elements\n" |
| msgstr "// 解构第二和第三个元素\n" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:14 |
| msgid "\"First is `0`, `y` is {:?}, and `z` is {:?}\"" |
| msgstr "\"第一个是 `0`，`y` 是 {:?}，`z` 是 {:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:15 |
| msgid "\"First is `1` and the rest doesn't matter\"" |
| msgstr "\"第一个是 `1`，其余的不重要\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:16 |
| msgid "\"last is `2` and the rest doesn't matter\"" |
| msgstr "\"最后一个是 `2`，其余的不重要\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:17 |
| msgid "\"First is `3`, last is `4`, and the rest doesn't matter\"" |
| msgstr "\"第一个是 `3`，最后一个是 `4`，其余的不重要\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:18 |
| msgid "// `..` can be used to ignore the rest of the tuple\n" |
| msgstr "// `..` 可用于忽略元组中的其余部分\n" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:19 |
| msgid "\"It doesn't matter what they are\"" |
| msgstr "\"它们是什么并不重要\"" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:20 |
| msgid "// `_` means don't bind the value to a variable\n" |
| msgstr "// `_` 表示不将值绑定到变量\n" |
| |
| #: src/flow_control/match/destructuring/destructure_tuple.md:27 |
| msgid "[Tuples](../../../primitives/tuples.md)" |
| msgstr "[元组](../../../primitives/tuples.md)" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:3 |
| msgid "Like tuples, arrays and slices can be destructured this way:" |
| msgstr "与元组类似，数组和切片也可以用这种方式解构：" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:7 |
| msgid "// Try changing the values in the array, or make it a slice!\n" |
| msgstr "// 尝试改变数组中的值，或将其变成切片！\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:11 |
| msgid "" |
| "// Binds the second and the third elements to the respective variables\n" |
| msgstr "// 将第二个和第三个元素分别绑定到相应的变量\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:13 |
| msgid "\"array[0] = 0, array[1] = {}, array[2] = {}\"" |
| msgstr "\"array[0] = 0，array[1] = {}，array[2] = {}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:15 |
| msgid "// Single values can be ignored with _\n" |
| msgstr "// 单个值可以用 _ 忽略\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:17 |
| msgid "\"array[0] = 1, array[2] = {} and array[1] was ignored\"" |
| msgstr "\"array[0] = 1，array[2] = {}，array[1] 被忽略了\"" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:21 |
| msgid "// You can also bind some and ignore the rest\n" |
| msgstr "// 你也可以绑定一部分值并忽略其余的\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:23 |
| msgid "\"array[0] = -1, array[1] = {} and all the other ones were ignored\"" |
| msgstr "\"array[0] = -1，array[1] = {}，其他所有的都被忽略了\"" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:26 |
| msgid "" |
| "// The code below would not compile\n" |
| " // [-1, second] => ...\n" |
| msgstr "" |
| "// 下面的代码无法编译\n" |
| " // [-1, second] => ...\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:29 |
| msgid "" |
| "// Or store them in another array/slice (the type depends on\n" |
| " // that of the value that is being matched against)\n" |
| msgstr "" |
| "// 或者将它们存储在另一个数组/切片中（类型取决于\n" |
| " // 正在匹配的值的类型）\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:32 |
| msgid "\"array[0] = 3, array[1] = {} and the other elements were {:?}\"" |
| msgstr "\"array[0] = 3，array[1] = {}，其他元素是 {:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:36 |
| msgid "" |
| "// Combining these patterns, we can, for example, bind the first and\n" |
| " // last values, and store the rest of them in a single array\n" |
| msgstr "" |
| "// 结合这些模式，我们可以，例如，绑定第一个和\n" |
| " // 最后一个值，并将其余的存储在一个单独的数组中\n" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:39 |
| msgid "\"array[0] = {}, middle = {:?}, array[2] = {}\"" |
| msgstr "\"array[0] = {}，中间部分 = {:?}，array[2] = {}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_slice.md:48 |
| msgid "" |
| "[Arrays and Slices](../../../primitives/array.md) and [Binding](../" |
| "binding.md) for `@` sigil" |
| msgstr "" |
| "关于 `@` 符号的更多信息，请参阅[数组和切片](../../../primitives/array.md)和" |
| "[绑定](../binding.md)" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:3 |
| msgid "An `enum` is destructured similarly:" |
| msgstr "`enum` 的解构方式类似：" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:6 |
| msgid "" |
| "// `allow` required to silence warnings because only\n" |
| "// one variant is used.\n" |
| msgstr "// 使用 `allow` 来抑制警告，因为只使用了一个变体。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:10 |
| msgid "// These 3 are specified solely by their name.\n" |
| msgstr "// 这 3 个仅通过名称指定。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:14 |
| msgid "// These likewise tie `u32` tuples to different names: color models.\n" |
| msgstr "// 这些同样将 `u32` 元组与不同的名称（颜色模型）关联。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:24 |
| msgid "// TODO ^ Try different variants for `color`\n" |
| msgstr "// TODO ^ 尝试为 `color` 使用不同的变体\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:26 |
| msgid "\"What color is it?\"" |
| msgstr "\"这是什么颜色？\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:27 |
| msgid "// An `enum` can be destructured using a `match`.\n" |
| msgstr "// 可以使用 `match` 来解构 `enum`。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:29 |
| msgid "\"The color is Red!\"" |
| msgstr "\"颜色是红色！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:30 |
| msgid "\"The color is Blue!\"" |
| msgstr "\"颜色是蓝色！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:31 |
| msgid "\"The color is Green!\"" |
| msgstr "\"颜色是绿色！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:33 |
| msgid "\"Red: {}, green: {}, and blue: {}!\"" |
| msgstr "\"红：{}，绿：{}，蓝：{}！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:35 |
| msgid "\"Hue: {}, saturation: {}, value: {}!\"" |
| msgstr "\"色相：{}，饱和度：{}，明度：{}！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:37 |
| msgid "\"Hue: {}, saturation: {}, lightness: {}!\"" |
| msgstr "\"色相：{}，饱和度：{}，亮度：{}！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:39 |
| msgid "\"Cyan: {}, magenta: {}, yellow: {}!\"" |
| msgstr "\"青：{}，品红：{}，黄：{}！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:41 |
| msgid "\"Cyan: {}, magenta: {}, yellow: {}, key (black): {}!\"" |
| msgstr "\"青：{}，品红：{}，黄：{}，黑（K）：{}！\"" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:43 |
| msgid "// Don't need another arm because all variants have been examined\n" |
| msgstr "// 不需要其他分支，因为所有变体都已检查\n" |
| |
| #: src/flow_control/match/destructuring/destructure_enum.md:50 |
| msgid "" |
| "[`#[allow(...)]`](../../../attribute/unused.md), [color models](https://" |
| "en.wikipedia.org/wiki/Color_model) and [`enum`](../../../custom_types/" |
| "enum.md)" |
| msgstr "" |
| "[`#[allow(...)]`](../../../attribute/unused.md)、[颜色模型](https://" |
| "en.wikipedia.org/wiki/Color_model)和[`enum`](../../../custom_types/enum.md)" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:3 |
| msgid "" |
| "For pointers, a distinction needs to be made between destructuring and " |
| "dereferencing as they are different concepts which are used differently from " |
| "languages like C/C++." |
| msgstr "" |
| "对于指针，需要区分解构和解引用，因为它们是不同的概念，其用法与 C/C++ 等语言不" |
| "同。" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:7 |
| msgid "Dereferencing uses `*`" |
| msgstr "解引用使用 `*`" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:8 |
| msgid "Destructuring uses `&`, `ref`, and `ref mut`" |
| msgstr "解构使用 `&`、`ref` 和 `ref mut`" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:12 |
| msgid "" |
| "// Assign a reference of type `i32`. The `&` signifies there\n" |
| " // is a reference being assigned.\n" |
| msgstr "" |
| "// 分配一个 `i32` 类型的引用。`&` 表示\n" |
| " // 正在分配一个引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:17 |
| msgid "" |
| "// If `reference` is pattern matched against `&val`, it results\n" |
| " // in a comparison like:\n" |
| " // `&i32`\n" |
| " // `&val`\n" |
| " // ^ We see that if the matching `&`s are dropped, then the `i32`\n" |
| " // should be assigned to `val`.\n" |
| msgstr "" |
| "// 如果 `reference` 与 `&val` 进行模式匹配，结果\n" |
| " // 就像这样的比较：\n" |
| " // `&i32`\n" |
| " // `&val`\n" |
| " // ^ 我们可以看到，如果去掉匹配的 `&`，那么 `i32`\n" |
| " // 应该被赋值给 `val`。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:23 |
| msgid "\"Got a value via destructuring: {:?}\"" |
| msgstr "\"通过解构获得的值：{:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:26 |
| msgid "// To avoid the `&`, you dereference before matching.\n" |
| msgstr "// 为了避免 `&`，你可以在匹配前解引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:28 |
| msgid "\"Got a value via dereferencing: {:?}\"" |
| msgstr "\"通过解引用获得的值：{:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:31 |
| msgid "" |
| "// What if you don't start with a reference? `reference` was a `&`\n" |
| " // because the right side was already a reference. This is not\n" |
| " // a reference because the right side is not one.\n" |
| msgstr "" |
| "// 如果你一开始没有引用怎么办？`reference` 是一个 `&`\n" |
| " // 因为右侧已经是一个引用。这不是\n" |
| " // 一个引用，因为右侧不是引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:36 |
| msgid "" |
| "// Rust provides `ref` for exactly this purpose. It modifies the\n" |
| " // assignment so that a reference is created for the element; this\n" |
| " // reference is assigned.\n" |
| msgstr "" |
| "// Rust 提供 `ref` 正是为了这个目的。它修改了\n" |
| " // 赋值，为元素创建一个引用；\n" |
| " // 这个引用被赋值。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:41 |
| msgid "" |
| "// Accordingly, by defining 2 values without references, references\n" |
| " // can be retrieved via `ref` and `ref mut`.\n" |
| msgstr "" |
| "// 相应地，通过定义两个没有引用的值，\n" |
| " // 可以通过 `ref` 和 `ref mut` 获取引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:46 |
| msgid "// Use `ref` keyword to create a reference.\n" |
| msgstr "// 使用 `ref` 关键字创建引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:48 |
| msgid "\"Got a reference to a value: {:?}\"" |
| msgstr "\"获得了一个值的引用：{:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:51 |
| msgid "// Use `ref mut` similarly.\n" |
| msgstr "// 类似地使用 `ref mut`。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:54 |
| msgid "" |
| "// Got a reference. Gotta dereference it before we can\n" |
| " // add anything to it.\n" |
| msgstr "" |
| "// 获得了一个引用。在我们能够\n" |
| " // 对其进行任何添加操作之前，必须先解引用。\n" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:57 |
| msgid "\"We added 10. `mut_value`: {:?}\"" |
| msgstr "\"我们加了 10。`mut_value`：{:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_pointers.md:65 |
| msgid "[The ref pattern](../../../scope/borrow/ref.md)" |
| msgstr "[ref 模式](../../../scope/borrow/ref.md)" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:3 |
| msgid "Similarly, a `struct` can be destructured as shown:" |
| msgstr "同样，`struct` 可以按如下方式解构：" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:12 |
| msgid "// Try changing the values in the struct to see what happens\n" |
| msgstr "// 尝试更改结构体中的值，看看会发生什么\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:16 |
| msgid "\"First of x is 1, b = {}, y = {} \"" |
| msgstr "\"x 的第一个元素是 1，b = {}，y = {}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:18 |
| msgid "" |
| "// you can destructure structs and rename the variables,\n" |
| " // the order is not important\n" |
| msgstr "" |
| "// 你可以解构结构体并重命名变量，\n" |
| " // 顺序并不重要\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:20 |
| msgid "\"y is 2, i = {:?}\"" |
| msgstr "\"y 为 2，i = {:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:22 |
| msgid "// and you can also ignore some variables:\n" |
| msgstr "// 你也可以忽略某些变量：\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:23 |
| msgid "\"y = {}, we don't care about x\"" |
| msgstr "\"y = {}，我们不关心 x 的值\"" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:24 |
| msgid "" |
| "// this will give an error: pattern does not mention field `x`\n" |
| " //Foo { y } => println!(\"y = {}\", y),\n" |
| msgstr "" |
| "// 这会导致错误：模式中未提及字段 `x`\n" |
| " //Foo { y } => println!(\"y = {}\", y),\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:30 |
| msgid "// You do not need a match block to destructure structs:\n" |
| msgstr "// 解构结构体不一定需要 match 块：\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:32 |
| msgid "\"Outside: x0 = {x0:?}, y0 = {y0}\"" |
| msgstr "\"外部：x0 = {x0:?}，y0 = {y0}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:34 |
| msgid "// Destructuring works with nested structs as well:\n" |
| msgstr "// 解构也适用于嵌套结构体：\n" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:41 |
| msgid "\"Nested: nested_x = {nested_x:?}, nested_y = {nested_y:?}\"" |
| msgstr "\"嵌套：nested_x = {nested_x:?}，nested_y = {nested_y:?}\"" |
| |
| #: src/flow_control/match/destructuring/destructure_structures.md:47 |
| msgid "[Structs](../../../custom_types/structs.md)" |
| msgstr "[结构体](../../../custom_types/structs.md)" |
| |
| #: src/flow_control/match/guard.md:3 |
| msgid "A `match` _guard_ can be added to filter the arm." |
| msgstr "`match` 分支可以使用**守卫**进行额外的筛选。" |
| |
| #: src/flow_control/match/guard.md:14 |
| msgid "// ^ TODO try different values for `temperature`\n" |
| msgstr "// ^ TODO：尝试为 `temperature` 赋予不同的值\n" |
| |
| #: src/flow_control/match/guard.md:17 |
| msgid "\"{}C is above 30 Celsius\"" |
| msgstr "\"{}°C 高于 30°C\"" |
| |
| #: src/flow_control/match/guard.md:18 |
| msgid "// The `if condition` part ^ is a guard\n" |
| msgstr "// `if condition` 部分 ^ 就是守卫\n" |
| |
| #: src/flow_control/match/guard.md:19 |
| msgid "\"{}C is equal to or below 30 Celsius\"" |
| msgstr "\"{}°C 不高于 30°C\"" |
| |
| #: src/flow_control/match/guard.md:21 |
| msgid "\"{}F is above 86 Fahrenheit\"" |
| msgstr "\"{}°F 高于 86°F\"" |
| |
| #: src/flow_control/match/guard.md:22 |
| msgid "\"{}F is equal to or below 86 Fahrenheit\"" |
| msgstr "\"{}°F 不高于 86°F\"" |
| |
| #: src/flow_control/match/guard.md:27 |
| msgid "" |
| "Note that the compiler won't take guard conditions into account when " |
| "checking if all patterns are covered by the match expression." |
| msgstr "" |
| "注意，编译器在检查 match 表达式是否涵盖了所有模式时，不会考虑守卫条件。" |
| |
| #: src/flow_control/match/guard.md:35 |
| msgid "\"Zero\"" |
| msgstr "\"零\"" |
| |
| #: src/flow_control/match/guard.md:36 |
| msgid "\"Greater than zero\"" |
| msgstr "\"大于零\"" |
| |
| #: src/flow_control/match/guard.md:37 |
| msgid "" |
| "// _ => unreachable!(\"Should never happen.\"),\n" |
| " // TODO ^ uncomment to fix compilation\n" |
| msgstr "" |
| "// _ => unreachable!(\"不应该发生。\"),\n" |
| " // TODO ^ 取消注释以修复编译错误\n" |
| |
| #: src/flow_control/match/guard.md:45 |
| msgid "" |
| "[Tuples](../../primitives/tuples.md) [Enums](../../custom_types/enum.md)" |
| msgstr "[元组](../../primitives/tuples.md) [枚举](../../custom_types/enum.md)" |
| |
| #: src/flow_control/match/binding.md:3 |
| msgid "" |
| "Indirectly accessing a variable makes it impossible to branch and use that " |
| "variable without re-binding. `match` provides the `@` sigil for binding " |
| "values to names:" |
| msgstr "" |
| "间接访问变量时，无法在分支中使用该变量而不重新绑定。`match` 提供了 `@` 符号，" |
| "用于将值绑定到名称：" |
| |
| #: src/flow_control/match/binding.md:8 |
| msgid "// A function `age` which returns a `u32`.\n" |
| msgstr "// 一个返回 `u32` 的 `age` 函数。\n" |
| |
| #: src/flow_control/match/binding.md:14 |
| msgid "\"Tell me what type of person you are\"" |
| msgstr "\"告诉我你是什么类型的人\"" |
| |
| #: src/flow_control/match/binding.md:17 |
| msgid "\"I haven't celebrated my first birthday yet\"" |
| msgstr "\"我还没有过第一个生日\"" |
| |
| #: src/flow_control/match/binding.md:18 |
| msgid "" |
| "// Could `match` 1 ..= 12 directly but then what age\n" |
| " // would the child be? Instead, bind to `n` for the\n" |
| " // sequence of 1 ..= 12. Now the age can be reported.\n" |
| msgstr "" |
| "// 可以直接匹配 1 ..= 12，但那样无法知道具体年龄\n" |
| " // 相反，我们将 1 ..= 12 的序列绑定到 `n`\n" |
| " // 现在就可以报告具体年龄了\n" |
| |
| #: src/flow_control/match/binding.md:21 |
| msgid "\"I'm a child of age {:?}\"" |
| msgstr "\"我是 {:?} 岁的儿童\"" |
| |
| #: src/flow_control/match/binding.md:22 |
| msgid "\"I'm a teen of age {:?}\"" |
| msgstr "\"我是 {:?} 岁的青少年\"" |
| |
| #: src/flow_control/match/binding.md:23 |
| msgid "// Nothing bound. Return the result.\n" |
| msgstr "// 没有绑定。直接返回结果。\n" |
| |
| #: src/flow_control/match/binding.md:24 |
| msgid "\"I'm an old person of age {:?}\"" |
| msgstr "\"我是 {:?} 岁的老年人\"" |
| |
| #: src/flow_control/match/binding.md:29 |
| msgid "" |
| "You can also use binding to \"destructure\" `enum` variants, such as " |
| "`Option`:" |
| msgstr "你也可以使用绑定来\"解构\" `enum` 变体，例如 `Option`：" |
| |
| #: src/flow_control/match/binding.md:38 |
| msgid "" |
| "// Got `Some` variant, match if its value, bound to `n`,\n" |
| " // is equal to 42.\n" |
| msgstr "// 获得 `Some` 变体，检查其值（绑定到 `n`）是否等于 42\n" |
| |
| #: src/flow_control/match/binding.md:40 |
| msgid "\"The Answer: {}!\"" |
| msgstr "\"答案是：{}！\"" |
| |
| #: src/flow_control/match/binding.md:41 |
| msgid "// Match any other number.\n" |
| msgstr "// 匹配任何其他数字\n" |
| |
| #: src/flow_control/match/binding.md:42 |
| msgid "\"Not interesting... {}\"" |
| msgstr "\"不感兴趣... {}\"" |
| |
| #: src/flow_control/match/binding.md:43 |
| msgid "// Match anything else (`None` variant).\n" |
| msgstr "// 匹配其他任何情况（`None` 变体）\n" |
| |
| #: src/flow_control/match/binding.md:51 |
| msgid "" |
| "[`functions`](../../fn.md), [`enums`](../../custom_types/enum.md) and " |
| "[`Option`](../../std/option.md)" |
| msgstr "" |
| "[`函数`](../../fn.md)、[`枚举`](../../custom_types/enum.md) 和 [`Option`]" |
| "(../../std/option.md)" |
| |
| #: src/flow_control/if_let.md:3 |
| msgid "" |
| "For some use cases, when matching enums, `match` is awkward. For example:" |
| msgstr "在某些情况下，使用 `match` 匹配枚举可能会显得繁琐。例如：" |
| |
| #: src/flow_control/if_let.md:6 src/flow_control/while_let.md:7 |
| #: src/flow_control/while_let.md:35 |
| msgid "// Make `optional` of type `Option<i32>`\n" |
| msgstr "// 创建 `Option<i32>` 类型的 `optional`\n" |
| |
| #: src/flow_control/if_let.md:10 |
| msgid "\"This is a really long string and `{:?}`\"" |
| msgstr "\"这是一个很长的字符串，其中包含 `{:?}`\"" |
| |
| #: src/flow_control/if_let.md:12 |
| msgid "" |
| "// ^ Required because `match` is exhaustive. Doesn't it seem\n" |
| " // like wasted space?\n" |
| msgstr "" |
| "// ^ 这是必需的，因为 `match` 要求穷举所有情况。\n" |
| " // 是不是觉得有些浪费空间？\n" |
| |
| #: src/flow_control/if_let.md:18 |
| msgid "" |
| "`if let` is cleaner for this use case and in addition allows various failure " |
| "options to be specified:" |
| msgstr "对于这种情况，`if let` 更加简洁，而且还允许指定各种失败时的处理选项：" |
| |
| #: src/flow_control/if_let.md:23 |
| msgid "// All have type `Option<i32>`\n" |
| msgstr "// 以下都是 `Option<i32>` 类型\n" |
| |
| #: src/flow_control/if_let.md:28 |
| msgid "" |
| "// The `if let` construct reads: \"if `let` destructures `number` into\n" |
| " // `Some(i)`, evaluate the block (`{}`).\n" |
| msgstr "" |
| "// `if let` 结构的含义是：如果 `let` 能将 `number` 解构为\n" |
| " // `Some(i)`，则执行代码块（`{}`）。\n" |
| |
| #: src/flow_control/if_let.md:31 src/flow_control/if_let.md:36 |
| #: src/flow_control/if_let.md:46 |
| msgid "\"Matched {:?}!\"" |
| msgstr "\"匹配到 {:?}！\"" |
| |
| #: src/flow_control/if_let.md:34 |
| msgid "// If you need to specify a failure, use an else:\n" |
| msgstr "// 如果需要指定匹配失败的情况，可以使用 else：\n" |
| |
| #: src/flow_control/if_let.md:38 |
| msgid "// Destructure failed. Change to the failure case.\n" |
| msgstr "// 解构失败。转到失败处理的情况。\n" |
| |
| #: src/flow_control/if_let.md:39 src/flow_control/if_let.md:50 |
| msgid "\"Didn't match a number. Let's go with a letter!\"" |
| msgstr "\"没有匹配到数字。那就用一个字母吧！\"" |
| |
| #: src/flow_control/if_let.md:42 |
| msgid "// Provide an altered failing condition.\n" |
| msgstr "// 提供一个修改后的失败条件。\n" |
| |
| #: src/flow_control/if_let.md:47 |
| msgid "" |
| "// Destructure failed. Evaluate an `else if` condition to see if the\n" |
| " // alternate failure branch should be taken:\n" |
| msgstr "// 解构失败。评估 `else if` 条件，看是否应该执行替代的失败分支：\n" |
| |
| #: src/flow_control/if_let.md:52 |
| msgid "// The condition evaluated false. This branch is the default:\n" |
| msgstr "// 条件判断为假。这个分支是默认情况：\n" |
| |
| #: src/flow_control/if_let.md:53 |
| msgid "\"I don't like letters. Let's go with an emoticon :)!\"" |
| msgstr "\"我不喜欢字母。那就用个表情符号吧 :)！\"" |
| |
| #: src/flow_control/if_let.md:58 |
| msgid "In the same way, `if let` can be used to match any enum value:" |
| msgstr "同样地，`if let` 可以用来匹配任何枚举值：" |
| |
| #: src/flow_control/if_let.md:61 |
| msgid "// Our example enum\n" |
| msgstr "// 我们的示例枚举\n" |
| |
| #: src/flow_control/if_let.md:69 |
| msgid "// Create example variables\n" |
| msgstr "// 创建示例变量\n" |
| |
| #: src/flow_control/if_let.md:74 src/flow_control/if_let.md:110 |
| msgid "// Variable a matches Foo::Bar\n" |
| msgstr "// 变量 a 匹配 Foo::Bar\n" |
| |
| #: src/flow_control/if_let.md:76 src/flow_control/if_let.md:113 |
| msgid "\"a is foobar\"" |
| msgstr "\"a 是 foobar\"" |
| |
| #: src/flow_control/if_let.md:79 |
| msgid "" |
| "// Variable b does not match Foo::Bar\n" |
| " // So this will print nothing\n" |
| msgstr "" |
| "// 变量 b 不匹配 Foo::Bar\n" |
| " // 所以这里不会打印任何内容\n" |
| |
| #: src/flow_control/if_let.md:82 |
| msgid "\"b is foobar\"" |
| msgstr "\"b 是 foobar\"" |
| |
| #: src/flow_control/if_let.md:85 |
| msgid "" |
| "// Variable c matches Foo::Qux which has a value\n" |
| " // Similar to Some() in the previous example\n" |
| msgstr "" |
| "// 变量 c 匹配 Foo::Qux，它包含一个值\n" |
| " // 类似于前面例子中的 Some()\n" |
| |
| #: src/flow_control/if_let.md:88 |
| msgid "\"c is {}\"" |
| msgstr "\"c 是 {}\"" |
| |
| #: src/flow_control/if_let.md:91 |
| msgid "// Binding also works with `if let`\n" |
| msgstr "// `if let` 也可以进行绑定\n" |
| |
| #: src/flow_control/if_let.md:93 |
| msgid "\"c is one hundred\"" |
| msgstr "\"c 是一百\"" |
| |
| #: src/flow_control/if_let.md:98 |
| msgid "" |
| "Another benefit is that `if let` allows us to match non-parameterized enum " |
| "variants. This is true even in cases where the enum doesn't implement or " |
| "derive `PartialEq`. In such cases `if Foo::Bar == a` would fail to compile, " |
| "because instances of the enum cannot be equated, however `if let` will " |
| "continue to work." |
| msgstr "" |
| "`if let` 的另一个优点是它允许我们匹配非参数化的枚举变体。即使在枚举没有实现或" |
| "派生 `PartialEq` 的情况下也是如此。在这种情况下，`if Foo::Bar == a` 将无法编" |
| "译，因为枚举的实例无法进行相等比较，但 `if let` 仍然可以正常工作。" |
| |
| #: src/flow_control/if_let.md:100 |
| msgid "Would you like a challenge? Fix the following example to use `if let`:" |
| msgstr "想要挑战一下吗？请修改以下示例，使用 `if let`：" |
| |
| #: src/flow_control/if_let.md:103 |
| msgid "" |
| "// This enum purposely neither implements nor derives PartialEq.\n" |
| "// That is why comparing Foo::Bar == a fails below.\n" |
| msgstr "" |
| "// 这个枚举故意既不实现也不派生 PartialEq。\n" |
| "// 这就是为什么下面比较 Foo::Bar == a 会失败。\n" |
| |
| #: src/flow_control/if_let.md:112 |
| msgid "// ^-- this causes a compile-time error. Use `if let` instead.\n" |
| msgstr "// ^-- 这会导致编译时错误。请改用 `if let`。\n" |
| |
| #: src/flow_control/if_let.md:120 |
| msgid "" |
| "[`enum`](../custom_types/enum.md), [`Option`](../std/option.md), and the " |
| "[RFC](https://github.com/rust-lang/rfcs/pull/160)" |
| msgstr "" |
| "[`枚举`](../custom_types/enum.md)、[`Option`](../std/option.md) 和 [RFC]" |
| "(https://github.com/rust-lang/rfcs/pull/160)" |
| |
| #: src/flow_control/let_else.md:3 |
| msgid "🛈 stable since: rust 1.65" |
| msgstr "🛈 自 Rust 1.65 版本起稳定" |
| |
| #: src/flow_control/let_else.md:5 |
| msgid "" |
| "🛈 you can target specific edition by compiling like this `rustc --" |
| "edition=2021 main.rs`" |
| msgstr "🛈 你可以通过这种方式编译来指定特定版本：`rustc --edition=2021 main.rs`" |
| |
| #: src/flow_control/let_else.md:8 |
| msgid "" |
| "With `let`\\-`else`, a refutable pattern can match and bind variables in the " |
| "surrounding scope like a normal `let`, or else diverge (e.g. `break`, " |
| "`return`, `panic!`) when the pattern doesn't match." |
| msgstr "" |
| "`let`-`else` 语法允许可能失败的模式匹配像普通 `let` 一样绑定变量到当前作用" |
| "域，或在匹配失败时执行中断操作（如 `break`、`return`、`panic!`）。" |
| |
| #: src/flow_control/let_else.md:16 src/flow_control/let_else.md:39 |
| #: src/std/str.md:41 |
| msgid "' '" |
| msgstr "' '" |
| |
| #: src/flow_control/let_else.md:18 src/flow_control/let_else.md:42 |
| msgid "\"Can't segment count item pair: '{s}'\"" |
| msgstr "\"无法分割计数项对：'{s}'\"" |
| |
| #: src/flow_control/let_else.md:21 src/flow_control/let_else.md:47 |
| msgid "\"Can't parse integer: '{count_str}'\"" |
| msgstr "\"无法解析整数：'{count_str}'\"" |
| |
| #: src/flow_control/let_else.md:27 src/flow_control/let_else.md:52 |
| msgid "\"3 chairs\"" |
| msgstr "\"3 chairs\"" |
| |
| #: src/flow_control/let_else.md:27 src/flow_control/let_else.md:52 |
| msgid "\"chairs\"" |
| msgstr "\"chairs\"" |
| |
| #: src/flow_control/let_else.md:31 |
| msgid "" |
| "The scope of name bindings is the main thing that makes this different from " |
| "`match` or `if let`\\-`else` expressions. You could previously approximate " |
| "these patterns with an unfortunate bit of repetition and an outer `let`:" |
| msgstr "" |
| "名称绑定的作用域是使其区别于 `match` 或 `if let`-`else` 表达式的主要特点。在" |
| "此之前，你可能需要通过一些冗余的重复和外部 `let` 来近似实现这些模式：" |
| |
| #: src/flow_control/let_else.md:57 |
| msgid "" |
| "[option](../std/option.md), [match](./match.md), [if let](./if_let.md) and " |
| "the [let-else RFC](https://rust-lang.github.io/rfcs/3137-let-else.html)." |
| msgstr "" |
| "[Option](../std/option.md)、[match](./match.md)、[if let](./if_let.md) 和 " |
| "[let-else RFC](https://rust-lang.github.io/rfcs/3137-let-else.html)。" |
| |
| #: src/flow_control/while_let.md:3 |
| msgid "" |
| "Similar to `if let`, `while let` can make awkward `match` sequences more " |
| "tolerable. Consider the following sequence that increments `i`:" |
| msgstr "" |
| "与 `if let` 类似，`while let` 可以简化繁琐的 `match` 序列。让我们来看一个递" |
| "增 `i` 的例子：" |
| |
| #: src/flow_control/while_let.md:9 |
| msgid "// Repeatedly try this test.\n" |
| msgstr "// 重复执行此测试。\n" |
| |
| #: src/flow_control/while_let.md:13 |
| msgid "// If `optional` destructures, evaluate the block.\n" |
| msgstr "// 如果 `optional` 解构成功，则执行代码块。\n" |
| |
| #: src/flow_control/while_let.md:16 src/flow_control/while_let.md:42 |
| msgid "\"Greater than 9, quit!\"" |
| msgstr "\"大于 9，退出！\"" |
| |
| #: src/flow_control/while_let.md:19 src/flow_control/while_let.md:45 |
| msgid "\"`i` is `{:?}`. Try again.\"" |
| msgstr "\"`i` 是 `{:?}`。再试一次。\"" |
| |
| #: src/flow_control/while_let.md:22 |
| msgid "// ^ Requires 3 indentations!\n" |
| msgstr "// ^ 需要 3 层缩进！\n" |
| |
| #: src/flow_control/while_let.md:24 |
| msgid "// Quit the loop when the destructure fails:\n" |
| msgstr "// 当解构失败时退出循环：\n" |
| |
| #: src/flow_control/while_let.md:26 |
| msgid "// ^ Why should this be required? There must be a better way!\n" |
| msgstr "// ^ 为什么需要这样？一定有更好的方法！\n" |
| |
| #: src/flow_control/while_let.md:31 |
| msgid "Using `while let` makes this sequence much nicer:" |
| msgstr "使用 `while let` 可以让这个序列更加简洁：" |
| |
| #: src/flow_control/while_let.md:38 |
| msgid "" |
| "// This reads: \"while `let` destructures `optional` into\n" |
| " // `Some(i)`, evaluate the block (`{}`). Else `break`.\n" |
| msgstr "" |
| "// 这段代码的含义是：当 `let` 将 `optional` 解构为 `Some(i)` 时，\n" |
| " // 执行代码块 `{}`，否则 `break`。\n" |
| |
| #: src/flow_control/while_let.md:48 |
| msgid "" |
| "// ^ Less rightward drift and doesn't require\n" |
| " // explicitly handling the failing case.\n" |
| msgstr "// ^ 减少了代码缩进右移，无需显式处理失败情况\n" |
| |
| #: src/flow_control/while_let.md:51 |
| msgid "" |
| "// ^ `if let` had additional optional `else`/`else if`\n" |
| " // clauses. `while let` does not have these.\n" |
| msgstr "" |
| "// ^ `if let` 可以有额外的 `else`/`else if` 子句，`while let` 则没有。\n" |
| |
| #: src/flow_control/while_let.md:58 |
| msgid "" |
| "[`enum`](../custom_types/enum.md), [`Option`](../std/option.md), and the " |
| "[RFC](https://github.com/rust-lang/rfcs/pull/214)" |
| msgstr "" |
| "[`enum`](../custom_types/enum.md)、[`Option`](../std/option.md) 和 [RFC]" |
| "(https://github.com/rust-lang/rfcs/pull/214)" |
| |
| #: src/fn.md:3 |
| msgid "" |
| "Functions are declared using the `fn` keyword. Its arguments are type " |
| "annotated, just like variables, and, if the function returns a value, the " |
| "return type must be specified after an arrow `->`." |
| msgstr "" |
| "函数使用 `fn` 关键字声明。函数参数需要标注类型，就像变量一样。如果函数返回" |
| "值，则必须在箭头 `->` 后指定返回类型。" |
| |
| #: src/fn.md:7 |
| msgid "" |
| "The final expression in the function will be used as return value. " |
| "Alternatively, the `return` statement can be used to return a value earlier " |
| "from within the function, even from inside loops or `if` statements." |
| msgstr "" |
| "函数的最后一个表达式将作为返回值。另外，可以使用 `return` 语句在函数内部提前" |
| "返回值，甚至可以在循环或 `if` 语句内部使用。" |
| |
| #: src/fn.md:11 |
| msgid "Let's rewrite FizzBuzz using functions!" |
| msgstr "让我们用函数重写 FizzBuzz 吧！" |
| |
| #: src/fn.md:14 |
| msgid "" |
| "// Unlike C/C++, there's no restriction on the order of function " |
| "definitions\n" |
| msgstr "// 与 C/C++ 不同，Rust 中函数定义的顺序没有限制\n" |
| |
| #: src/fn.md:16 |
| msgid "// We can use this function here, and define it somewhere later\n" |
| msgstr "// 我们可以在这里使用函数，并在稍后的某处定义它\n" |
| |
| #: src/fn.md:19 |
| msgid "// Function that returns a boolean value\n" |
| msgstr "// 返回布尔值的函数\n" |
| |
| #: src/fn.md:22 |
| msgid "// Corner case, early return\n" |
| msgstr "// 特殊情况，提前返回\n" |
| |
| #: src/fn.md:27 |
| msgid "// This is an expression, the `return` keyword is not necessary here\n" |
| msgstr "// 这是一个表达式，此处不需要 `return` 关键字\n" |
| |
| #: src/fn.md:30 |
| msgid "" |
| "// Functions that \"don't\" return a value, actually return the unit type " |
| "`()`\n" |
| msgstr "// \"无返回值\"的函数实际上返回单元类型 `()`\n" |
| |
| #: src/fn.md:43 |
| msgid "" |
| "// When a function returns `()`, the return type can be omitted from the\n" |
| "// signature\n" |
| msgstr "// 当函数返回 `()` 时，可以在函数签名中省略返回类型\n" |
| |
| #: src/fn/methods.md:1 |
| msgid "Associated functions & Methods" |
| msgstr "关联函数和方法" |
| |
| #: src/fn/methods.md:3 |
| msgid "" |
| "Some functions are connected to a particular type. These come in two forms: " |
| "associated functions, and methods. Associated functions are functions that " |
| "are defined on a type generally, while methods are associated functions that " |
| "are called on a particular instance of a type." |
| msgstr "" |
| "某些函数与特定类型相关联。这些函数有两种形式：关联函数和方法。关联函数是在类" |
| "型上定义的函数，而方法是在类型的特定实例上调用的关联函数。" |
| |
| #: src/fn/methods.md:13 |
| msgid "" |
| "// Implementation block, all `Point` associated functions & methods go in " |
| "here\n" |
| msgstr "// 实现块，所有 `Point` 的关联函数和方法都在此处定义\n" |
| |
| #: src/fn/methods.md:16 |
| msgid "" |
| "// This is an \"associated function\" because this function is associated " |
| "with\n" |
| " // a particular type, that is, Point.\n" |
| " //\n" |
| " // Associated functions don't need to be called with an instance.\n" |
| " // These functions are generally used like constructors.\n" |
| msgstr "" |
| "// 这是一个\"关联函数\"，因为这个函数与特定类型 Point 相关联。\n" |
| " //\n" |
| " // 关联函数不需要通过实例来调用。\n" |
| " // 这些函数通常用作构造函数。\n" |
| |
| #: src/fn/methods.md:25 |
| msgid "// Another associated function, taking two arguments:\n" |
| msgstr "// 另一个接受两个参数的关联函数：\n" |
| |
| #: src/fn/methods.md:37 |
| msgid "" |
| "// This is a method\n" |
| " // `&self` is sugar for `self: &Self`, where `Self` is the type of the\n" |
| " // caller object. In this case `Self` = `Rectangle`\n" |
| msgstr "" |
| "// 这是一个方法\n" |
| " // `&self` 是 `self: &Self` 的语法糖，其中 `Self` 是调用者对象的类型。\n" |
| " // 在这个例子中 `Self` = `Rectangle`\n" |
| |
| #: src/fn/methods.md:41 |
| msgid "// `self` gives access to the struct fields via the dot operator\n" |
| msgstr "// `self` 通过点运算符访问结构体字段\n" |
| |
| #: src/fn/methods.md:45 |
| msgid "" |
| "// `abs` is a `f64` method that returns the absolute value of the\n" |
| " // caller\n" |
| msgstr "// `abs` 是 `f64` 类型的方法，返回调用者的绝对值\n" |
| |
| #: src/fn/methods.md:57 |
| msgid "" |
| "// This method requires the caller object to be mutable\n" |
| " // `&mut self` desugars to `self: &mut Self`\n" |
| msgstr "" |
| "// 这个方法要求调用对象是可变的\n" |
| " // `&mut self` 是 `self: &mut Self` 的语法糖\n" |
| |
| #: src/fn/methods.md:67 |
| msgid "// `Pair` owns resources: two heap allocated integers\n" |
| msgstr "// `Pair` 拥有两个堆分配的整数资源\n" |
| |
| #: src/fn/methods.md:72 |
| msgid "" |
| "// This method \"consumes\" the resources of the caller object\n" |
| " // `self` desugars to `self: Self`\n" |
| msgstr "" |
| "// 这个方法会\"消耗\"调用对象的资源\n" |
| " // `self` 是 `self: Self` 的语法糖\n" |
| |
| #: src/fn/methods.md:75 |
| msgid "// Destructure `self`\n" |
| msgstr "// 解构 `self`\n" |
| |
| #: src/fn/methods.md:78 |
| msgid "\"Destroying Pair({}, {})\"" |
| msgstr "\"正在销毁 Pair({}, {})\"" |
| |
| #: src/fn/methods.md:80 |
| msgid "// `first` and `second` go out of scope and get freed\n" |
| msgstr "// `first` 和 `second` 超出作用域并被释放\n" |
| |
| #: src/fn/methods.md:86 |
| msgid "// Associated functions are called using double colons\n" |
| msgstr "// 使用双冒号调用关联函数\n" |
| |
| #: src/fn/methods.md:91 |
| msgid "" |
| "// Methods are called using the dot operator\n" |
| " // Note that the first argument `&self` is implicitly passed, i.e.\n" |
| " // `rectangle.perimeter()` === `Rectangle::perimeter(&rectangle)`\n" |
| msgstr "" |
| "// 使用点运算符调用方法\n" |
| " // 注意，第一个参数 `&self` 是隐式传递的\n" |
| " // 即 `rectangle.perimeter()` 等同于 `Rectangle::perimeter(&rectangle)`\n" |
| |
| #: src/fn/methods.md:94 |
| msgid "\"Rectangle perimeter: {}\"" |
| msgstr "\"矩形周长：{}\"" |
| |
| #: src/fn/methods.md:95 |
| msgid "\"Rectangle area: {}\"" |
| msgstr "\"矩形面积：{}\"" |
| |
| #: src/fn/methods.md:102 |
| msgid "" |
| "// Error! `rectangle` is immutable, but this method requires a mutable\n" |
| " // object\n" |
| " //rectangle.translate(1.0, 0.0);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`rectangle` 是不可变的，但这个方法需要可变对象\n" |
| " //rectangle.translate(1.0, 0.0);\n" |
| " // TODO ^ 尝试取消这行的注释\n" |
| |
| #: src/fn/methods.md:107 |
| msgid "// Okay! Mutable objects can call mutable methods\n" |
| msgstr "// 正确！可变对象可以调用可变方法\n" |
| |
| #: src/fn/methods.md:114 |
| msgid "" |
| "// Error! Previous `destroy` call \"consumed\" `pair`\n" |
| " //pair.destroy();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 报错！之前的 `destroy` 调用已经\"消耗\"了 `pair`\n" |
| " //pair.destroy();\n" |
| " // TODO ^ 尝试取消注释这一行\n" |
| |
| #: src/fn/closures.md:3 |
| msgid "" |
| "Closures are functions that can capture the enclosing environment. For " |
| "example, a closure that captures the `x` variable:" |
| msgstr "闭包是可以捕获周围环境的函数。例如，下面是一个捕获变量 `x` 的闭包：" |
| |
| #: src/fn/closures.md:10 |
| msgid "" |
| "The syntax and capabilities of closures make them very convenient for on the " |
| "fly usage. Calling a closure is exactly like calling a function. However, " |
| "both input and return types _can_ be inferred and input variable names " |
| "_must_ be specified." |
| msgstr "" |
| "闭包的语法和功能使其非常适合即时使用。调用闭包与调用函数完全相同。不过，闭包" |
| "的输入和返回类型**可以**被推断，而输入变量名**必须**指定。" |
| |
| #: src/fn/closures.md:15 |
| msgid "Other characteristics of closures include:" |
| msgstr "闭包的其他特点包括：" |
| |
| #: src/fn/closures.md:17 |
| msgid "using `||` instead of `()` around input variables." |
| msgstr "使用 `||` 而不是 `()` 来包围输入变量。" |
| |
| #: src/fn/closures.md:18 |
| msgid "" |
| "optional body delimitation (`{}`) for a single line expression (mandatory " |
| "otherwise)." |
| msgstr "单行表达式可省略函数体定界符（`{}`），其他情况则必须使用" |
| |
| #: src/fn/closures.md:19 |
| msgid "the ability to capture the outer environment variables." |
| msgstr "能够捕获外部环境的变量" |
| |
| #: src/fn/closures.md:25 |
| msgid "" |
| "// A regular function can't refer to variables in the enclosing environment\n" |
| " //fn function(i: i32) -> i32 { i + outer_var }\n" |
| " // TODO: uncomment the line above and see the compiler error. The " |
| "compiler\n" |
| " // suggests that we define a closure instead.\n" |
| msgstr "" |
| "// 常规函数无法引用外部环境的变量\n" |
| " //fn function(i: i32) -> i32 { i + outer_var }\n" |
| " // TODO：取消上面这行的注释，查看编译器错误\n" |
| " // 编译器会建议我们定义一个闭包来替代\n" |
| |
| #: src/fn/closures.md:30 |
| msgid "" |
| "// Closures are anonymous, here we are binding them to references.\n" |
| " // Annotation is identical to function annotation but is optional\n" |
| " // as are the `{}` wrapping the body. These nameless functions\n" |
| " // are assigned to appropriately named variables.\n" |
| msgstr "" |
| "// 闭包是匿名的，这里我们将它们绑定到引用\n" |
| " // 注解与函数注解相同，但是可选的\n" |
| " // 包裹函数体的 `{}` 也是可选的\n" |
| " // 这些无名函数被赋值给适当命名的变量\n" |
| |
| #: src/fn/closures.md:37 |
| msgid "// Call the closures.\n" |
| msgstr "// 调用闭包\n" |
| |
| #: src/fn/closures.md:38 |
| msgid "\"closure_annotated: {}\"" |
| msgstr "\"closure_annotated：{}\"" |
| |
| #: src/fn/closures.md:39 |
| msgid "\"closure_inferred: {}\"" |
| msgstr "\"closure_inferred：{}\"" |
| |
| #: src/fn/closures.md:40 |
| msgid "" |
| "// Once closure's type has been inferred, it cannot be inferred again with " |
| "another type.\n" |
| " //println!(\"cannot reuse closure_inferred with another type: {}\", " |
| "closure_inferred(42i64));\n" |
| " // TODO: uncomment the line above and see the compiler error.\n" |
| msgstr "" |
| "// 闭包类型一旦被推断，就不能再用其他类型重新推断。\n" |
| " //println!(\"不能用其他类型重用 closure_inferred：{}\", " |
| "closure_inferred(42i64));\n" |
| " // TODO：取消上面这行的注释，观察编译器错误。\n" |
| |
| #: src/fn/closures.md:44 |
| msgid "" |
| "// A closure taking no arguments which returns an `i32`.\n" |
| " // The return type is inferred.\n" |
| msgstr "" |
| "// 一个无参数并返回 `i32` 的闭包。\n" |
| " // 返回类型是推断的。\n" |
| |
| #: src/fn/closures.md:47 |
| msgid "\"closure returning one: {}\"" |
| msgstr "\"返回 1 的闭包：{}\"" |
| |
| #: src/fn/closures/capture.md:3 |
| msgid "" |
| "Closures are inherently flexible and will do what the functionality requires " |
| "to make the closure work without annotation. This allows capturing to " |
| "flexibly adapt to the use case, sometimes moving and sometimes borrowing. " |
| "Closures can capture variables:" |
| msgstr "" |
| "闭包本质上很灵活，无需注解就能根据功能需求自动适应。这使得捕获可以灵活地适应" |
| "不同场景，有时移动，有时借用。闭包可以通过以下方式捕获变量：" |
| |
| #: src/fn/closures/capture.md:8 |
| msgid "by reference: `&T`" |
| msgstr "通过引用：`&T`" |
| |
| #: src/fn/closures/capture.md:9 |
| msgid "by mutable reference: `&mut T`" |
| msgstr "通过可变引用：`&mut T`" |
| |
| #: src/fn/closures/capture.md:10 |
| msgid "by value: `T`" |
| msgstr "通过值：`T`" |
| |
| #: src/fn/closures/capture.md:12 |
| msgid "" |
| "They preferentially capture variables by reference and only go lower when " |
| "required." |
| msgstr "闭包优先通过引用捕获变量，仅在必要时才使用更底部的的捕获方式。" |
| |
| #: src/fn/closures/capture.md:19 |
| msgid "\"green\"" |
| msgstr "\"green\"" |
| |
| #: src/fn/closures/capture.md:21 |
| msgid "" |
| "// A closure to print `color` which immediately borrows (`&`) `color` and\n" |
| " // stores the borrow and closure in the `print` variable. It will " |
| "remain\n" |
| " // borrowed until `print` is used the last time. \n" |
| " //\n" |
| " // `println!` only requires arguments by immutable reference so it " |
| "doesn't\n" |
| " // impose anything more restrictive.\n" |
| msgstr "" |
| "// 打印 `color` 的闭包，立即借用（`&`）`color` 并\n" |
| " // 将借用和闭包存储在 `print` 变量中。借用状态\n" |
| " // 将持续到 `print` 最后一次使用。\n" |
| " //\n" |
| " // `println!` 只需要不可变引用参数，所以\n" |
| " // 不会施加更多限制。\n" |
| |
| #: src/fn/closures/capture.md:27 |
| msgid "\"`color`: {}\"" |
| msgstr "\"`color`: {}\"" |
| |
| #: src/fn/closures/capture.md:29 |
| msgid "// Call the closure using the borrow.\n" |
| msgstr "// 使用借用调用闭包。\n" |
| |
| #: src/fn/closures/capture.md:32 |
| msgid "" |
| "// `color` can be borrowed immutably again, because the closure only holds\n" |
| " // an immutable reference to `color`. \n" |
| msgstr "" |
| "// `color` 可以再次被不可变借用，因为闭包只持有\n" |
| " // `color` 的不可变引用。\n" |
| |
| #: src/fn/closures/capture.md:37 |
| msgid "// A move or reborrow is allowed after the final use of `print`\n" |
| msgstr "// `print` 最后一次使用后，允许移动或重新借用\n" |
| |
| #: src/fn/closures/capture.md:42 |
| msgid "" |
| "// A closure to increment `count` could take either `&mut count` or `count`\n" |
| " // but `&mut count` is less restrictive so it takes that. Immediately\n" |
| " // borrows `count`.\n" |
| " //\n" |
| " // A `mut` is required on `inc` because a `&mut` is stored inside. " |
| "Thus,\n" |
| " // calling the closure mutates `count` which requires a `mut`.\n" |
| msgstr "" |
| "// 增加 `count` 的闭包可以接受 `&mut count` 或 `count`，\n" |
| " // 但 `&mut count` 限制更少，所以选择它。立即\n" |
| " // 借用 `count`。\n" |
| " //\n" |
| " // `inc` 需要 `mut` 因为内部存储了 `&mut`。因此，\n" |
| " // 调用闭包会修改 `count`，这需要 `mut`。\n" |
| |
| #: src/fn/closures/capture.md:50 |
| msgid "\"`count`: {}\"" |
| msgstr "\"`count`: {}\"" |
| |
| #: src/fn/closures/capture.md:53 |
| msgid "// Call the closure using a mutable borrow.\n" |
| msgstr "// 使用可变借用调用闭包。\n" |
| |
| #: src/fn/closures/capture.md:56 |
| msgid "" |
| "// The closure still mutably borrows `count` because it is called later.\n" |
| " // An attempt to reborrow will lead to an error.\n" |
| " // let _reborrow = &count; \n" |
| " // ^ TODO: try uncommenting this line.\n" |
| msgstr "" |
| "// 闭包仍然可变借用 `count`，因为它稍后会被调用。\n" |
| " // 尝试重新借用会导致错误。\n" |
| " // let _reborrow = &count; \n" |
| " // ^ TODO：尝试取消注释这行。\n" |
| |
| #: src/fn/closures/capture.md:62 |
| msgid "" |
| "// The closure no longer needs to borrow `&mut count`. Therefore, it is\n" |
| " // possible to reborrow without an error\n" |
| msgstr "" |
| "// 闭包不再需要借用 `&mut count`。因此，\n" |
| " // 可以在没有错误的情况下重新借用\n" |
| |
| #: src/fn/closures/capture.md:67 |
| msgid "// A non-copy type.\n" |
| msgstr "// 不可复制类型。\n" |
| |
| #: src/fn/closures/capture.md:70 |
| msgid "" |
| "// `mem::drop` requires `T` so this must take by value. A copy type\n" |
| " // would copy into the closure leaving the original untouched.\n" |
| " // A non-copy must move and so `movable` immediately moves into\n" |
| " // the closure.\n" |
| msgstr "" |
| "// `mem::drop` 需要 `T`，所以这里必须通过值获取。可复制类型\n" |
| " // 会被复制到闭包中，原始值保持不变。\n" |
| " // 不可复制类型必须移动，所以 `movable` 立即移动到闭包中。\n" |
| |
| #: src/fn/closures/capture.md:75 |
| msgid "\"`movable`: {:?}\"" |
| msgstr "\"`movable`: {:?}\"" |
| |
| #: src/fn/closures/capture.md:79 |
| msgid "// `consume` consumes the variable so this can only be called once.\n" |
| msgstr "// `consume` 消耗了变量，所以只能调用一次。\n" |
| |
| #: src/fn/closures/capture.md:81 |
| msgid "" |
| "// consume();\n" |
| " // ^ TODO: Try uncommenting this line.\n" |
| msgstr "" |
| "// consume();\n" |
| " // ^ TODO：尝试取消注释这行。\n" |
| |
| #: src/fn/closures/capture.md:86 |
| msgid "" |
| "Using `move` before vertical pipes forces closure to take ownership of " |
| "captured variables:" |
| msgstr "在竖线前使用 `move` 强制闭包获取捕获变量的所有权：" |
| |
| #: src/fn/closures/capture.md:91 |
| msgid "// `Vec` has non-copy semantics.\n" |
| msgstr "// `Vec` 是非复制语义。\n" |
| |
| #: src/fn/closures/capture.md:99 |
| msgid "" |
| "// println!(\"There're {} elements in vec\", haystack.len());\n" |
| " // ^ Uncommenting above line will result in compile-time error\n" |
| " // because borrow checker doesn't allow re-using variable after it\n" |
| " // has been moved.\n" |
| msgstr "" |
| "// println!(\"vec 中有 {} 个元素\", haystack.len());\n" |
| " // ^ 取消上面这行的注释会导致编译时错误\n" |
| " // 因为借用检查器不允许在变量被移动后重用。\n" |
| " \n" |
| |
| #: src/fn/closures/capture.md:104 |
| msgid "" |
| "// Removing `move` from closure's signature will cause closure\n" |
| " // to borrow _haystack_ variable immutably, hence _haystack_ is still\n" |
| " // available and uncommenting above line will not cause an error.\n" |
| msgstr "" |
| "// 从闭包签名中移除 `move` 将导致闭包\n" |
| " // 不可变借用 _haystack_ 变量，因此 _haystack_ 仍可用，\n" |
| " // 取消注释上面的行不会导致错误。\n" |
| |
| #: src/fn/closures/capture.md:112 |
| msgid "" |
| "[`Box`](../../std/box.md) and [`std::mem::drop`](https://doc.rust-lang.org/" |
| "std/mem/fn.drop.html)" |
| msgstr "" |
| "[`Box`](../../std/box.md) 和 [`std::mem::drop`](https://doc.rust-lang.org/" |
| "std/mem/fn.drop.html)" |
| |
| #: src/fn/closures/input_parameters.md:3 |
| msgid "" |
| "While Rust chooses how to capture variables on the fly mostly without type " |
| "annotation, this ambiguity is not allowed when writing functions. When " |
| "taking a closure as an input parameter, the closure's complete type must be " |
| "annotated using one of a few `traits`, and they're determined by what the " |
| "closure does with captured value. In order of decreasing restriction, they " |
| "are:" |
| msgstr "" |
| "Rust 通常能自动选择如何捕获变量，无需类型标注。但在编写函数时，这种模糊性是不" |
| "允许的。当将闭包作为输入参数时，必须使用特定的 `trait` 来注解闭包的完整类型。" |
| "这些 trait 由闭包对捕获值的处理方式决定。按限制程度从高到低排列如下：" |
| |
| #: src/fn/closures/input_parameters.md:10 |
| msgid "`Fn`: the closure uses the captured value by reference (`&T`)" |
| msgstr "`Fn`：闭包通过引用使用捕获的值（`&T`）" |
| |
| #: src/fn/closures/input_parameters.md:11 |
| msgid "" |
| "`FnMut`: the closure uses the captured value by mutable reference (`&mut T`)" |
| msgstr "`FnMut`：闭包通过可变引用使用捕获的值（`&mut T`）" |
| |
| #: src/fn/closures/input_parameters.md:12 |
| msgid "`FnOnce`: the closure uses the captured value by value (`T`)" |
| msgstr "`FnOnce`：闭包通过值使用捕获的值（`T`）" |
| |
| #: src/fn/closures/input_parameters.md:14 |
| msgid "" |
| "On a variable-by-variable basis, the compiler will capture variables in the " |
| "least restrictive manner possible." |
| msgstr "编译器会以尽可能最少限制的方式逐个捕获变量。" |
| |
| #: src/fn/closures/input_parameters.md:17 |
| msgid "" |
| "For instance, consider a parameter annotated as `FnOnce`. This specifies " |
| "that the closure _may_ capture by `&T`, `&mut T`, or `T`, but the compiler " |
| "will ultimately choose based on how the captured variables are used in the " |
| "closure." |
| msgstr "" |
| "例如，考虑一个注解为 `FnOnce` 的参数。这表示闭包**可能**通过 `&T`、`&mut T` " |
| "或 `T` 进行捕获，但编译器最终会根据捕获变量在闭包中的使用方式来决定。" |
| |
| #: src/fn/closures/input_parameters.md:22 |
| msgid "" |
| "This is because if a move is possible, then any type of borrow should also " |
| "be possible. Note that the reverse is not true. If the parameter is " |
| "annotated as `Fn`, then capturing variables by `&mut T` or `T` are not " |
| "allowed. However, `&T` is allowed." |
| msgstr "" |
| "这是因为如果可以移动，那么任何类型的借用也应该是可能的。注意反过来并不成立。" |
| "如果参数被注解为 `Fn`，那么通过 `&mut T` 或 `T` 捕获变量是不允许的。但 `&T` " |
| "是允许的。" |
| |
| #: src/fn/closures/input_parameters.md:27 |
| msgid "" |
| "In the following example, try swapping the usage of `Fn`, `FnMut`, and " |
| "`FnOnce` to see what happens:" |
| msgstr "" |
| "在下面的例子中，尝试交换 `Fn`、`FnMut` 和 `FnOnce` 的用法，看看会发生什么：" |
| |
| #: src/fn/closures/input_parameters.md:31 |
| msgid "" |
| "// A function which takes a closure as an argument and calls it.\n" |
| "// <F> denotes that F is a \"Generic type parameter\"\n" |
| msgstr "" |
| "// 这个函数接受一个闭包作为参数并调用它\n" |
| "// <F> 表示 F 是一个\"泛型类型参数\"\n" |
| |
| #: src/fn/closures/input_parameters.md:34 |
| msgid "// The closure takes no input and returns nothing.\n" |
| msgstr "// 这个闭包不接受输入也不返回任何值\n" |
| |
| #: src/fn/closures/input_parameters.md:36 |
| msgid "// ^ TODO: Try changing this to `Fn` or `FnMut`.\n" |
| msgstr "// ^ TODO：试着将其改为 `Fn` 或 `FnMut`\n" |
| |
| #: src/fn/closures/input_parameters.md:40 |
| msgid "// A function which takes a closure and returns an `i32`.\n" |
| msgstr "// 这个函数接受一个闭包并返回 `i32`\n" |
| |
| #: src/fn/closures/input_parameters.md:43 |
| msgid "// The closure takes an `i32` and returns an `i32`.\n" |
| msgstr "// 这个闭包接受一个 `i32` 并返回一个 `i32`\n" |
| |
| #: src/fn/closures/input_parameters.md:53 |
| msgid "" |
| "// A non-copy type.\n" |
| " // `to_owned` creates owned data from borrowed one\n" |
| msgstr "" |
| "// 一个非复制类型\n" |
| " // `to_owned` 从借用的数据创建拥有所有权的数据\n" |
| |
| #: src/fn/closures/input_parameters.md:55 |
| msgid "\"goodbye\"" |
| msgstr "\"goodbye\"" |
| |
| #: src/fn/closures/input_parameters.md:57 |
| msgid "" |
| "// Capture 2 variables: `greeting` by reference and\n" |
| " // `farewell` by value.\n" |
| msgstr "" |
| "// 捕获两个变量：通过引用捕获 `greeting`，\n" |
| " // 通过值捕获 `farewell`\n" |
| |
| #: src/fn/closures/input_parameters.md:60 |
| msgid "// `greeting` is by reference: requires `Fn`.\n" |
| msgstr "// `greeting` 是通过引用捕获的：需要 `Fn`\n" |
| |
| #: src/fn/closures/input_parameters.md:61 |
| msgid "\"I said {}.\"" |
| msgstr "\"我说{}。\"" |
| |
| #: src/fn/closures/input_parameters.md:63 |
| msgid "" |
| "// Mutation forces `farewell` to be captured by\n" |
| " // mutable reference. Now requires `FnMut`.\n" |
| msgstr "" |
| "// 修改强制 `farewell` 通过可变引用捕获\n" |
| " // 现在需要 `FnMut`\n" |
| |
| #: src/fn/closures/input_parameters.md:65 |
| msgid "\"!!!\"" |
| msgstr "\"！！！\"" |
| |
| #: src/fn/closures/input_parameters.md:66 |
| msgid "\"Then I screamed {}.\"" |
| msgstr "\"然后我喊{}。\"" |
| |
| #: src/fn/closures/input_parameters.md:67 |
| msgid "\"Now I can sleep. zzzzz\"" |
| msgstr "\"现在我可以睡觉了。呼呼\"" |
| |
| #: src/fn/closures/input_parameters.md:69 |
| msgid "" |
| "// Manually calling drop forces `farewell` to\n" |
| " // be captured by value. Now requires `FnOnce`.\n" |
| msgstr "" |
| "// 手动调用 drop 强制 `farewell` 通过值捕获\n" |
| " // 现在需要 `FnOnce`\n" |
| |
| #: src/fn/closures/input_parameters.md:74 |
| msgid "// Call the function which applies the closure.\n" |
| msgstr "// 调用应用闭包的函数\n" |
| |
| #: src/fn/closures/input_parameters.md:77 |
| msgid "// `double` satisfies `apply_to_3`'s trait bound\n" |
| msgstr "// `double` 满足 `apply_to_3` 的 trait 约束\n" |
| |
| #: src/fn/closures/input_parameters.md:80 |
| msgid "\"3 doubled: {}\"" |
| msgstr "\"3 的两倍是：{}\"" |
| |
| #: src/fn/closures/input_parameters.md:86 |
| msgid "" |
| "[`std::mem::drop`](https://doc.rust-lang.org/std/mem/fn.drop.html), [`Fn`]" |
| "(https://doc.rust-lang.org/std/ops/trait.Fn.html), [`FnMut`](https://" |
| "doc.rust-lang.org/std/ops/trait.FnMut.html), [Generics](../../generics.md), " |
| "[where](../../generics/where.md) and [`FnOnce`](https://doc.rust-lang.org/" |
| "std/ops/trait.FnOnce.html)" |
| msgstr "" |
| "[`std::mem::drop`](https://doc.rust-lang.org/std/mem/fn.drop.html)、[`Fn`]" |
| "(https://doc.rust-lang.org/std/ops/trait.Fn.html)、[`FnMut`](https://" |
| "doc.rust-lang.org/std/ops/trait.FnMut.html)、[泛型](../../generics.md)、" |
| "[where](../../generics/where.md) 和 [`FnOnce`](https://doc.rust-lang.org/std/" |
| "ops/trait.FnOnce.html)" |
| |
| #: src/fn/closures/anonymity.md:3 |
| msgid "" |
| "Closures succinctly capture variables from enclosing scopes. Does this have " |
| "any consequences? It surely does. Observe how using a closure as a function " |
| "parameter requires [generics](../../generics.md), which is necessary because " |
| "of how they are defined:" |
| msgstr "" |
| "闭包能简洁地从外部作用域捕获变量。这会有什么影响吗？当然会有。注意观察如何将" |
| "闭包作为函数参数使用时需要[泛型](../../generics.md)，这是由于闭包的定义方式所" |
| "决定的：" |
| |
| #: src/fn/closures/anonymity.md:9 |
| msgid "// `F` must be generic.\n" |
| msgstr "// `F` 必须是泛型\n" |
| |
| #: src/fn/closures/anonymity.md:16 |
| msgid "" |
| "When a closure is defined, the compiler implicitly creates a new anonymous " |
| "structure to store the captured variables inside, meanwhile implementing the " |
| "functionality via one of the `traits`: `Fn`, `FnMut`, or `FnOnce` for this " |
| "unknown type. This type is assigned to the variable which is stored until " |
| "calling." |
| msgstr "" |
| "当定义一个闭包时，编译器会隐式创建一个新的匿名结构来存储内部捕获的变量，同时" |
| "通过 `Fn`、`FnMut` 或 `FnOnce` 这些 `trait` 之一为这个未知类型实现功能。这个" |
| "类型被赋给变量并存储，直到被调用。" |
| |
| #: src/fn/closures/anonymity.md:22 |
| msgid "" |
| "Since this new type is of unknown type, any usage in a function will require " |
| "generics. However, an unbounded type parameter `<T>` would still be " |
| "ambiguous and not be allowed. Thus, bounding by one of the `traits`: `Fn`, " |
| "`FnMut`, or `FnOnce` (which it implements) is sufficient to specify its type." |
| msgstr "" |
| "由于这个新类型是未知类型，在函数中使用时就需要泛型。然而，一个无界的类型参数 " |
| "`<T>` 仍然会是模糊的，不被允许。因此，通过 `Fn`、`FnMut` 或 `FnOnce` 这些 " |
| "`trait` 之一（它实现的）来约束就足以指定其类型。" |
| |
| #: src/fn/closures/anonymity.md:28 |
| msgid "" |
| "// `F` must implement `Fn` for a closure which takes no\n" |
| "// inputs and returns nothing - exactly what is required\n" |
| "// for `print`.\n" |
| msgstr "" |
| "// `F` 必须实现 `Fn` 用于一个不接受输入且不返回任何内容的闭包\n" |
| "// - 这正是 `print` 所需要的\n" |
| |
| #: src/fn/closures/anonymity.md:39 |
| msgid "" |
| "// Capture `x` into an anonymous type and implement\n" |
| " // `Fn` for it. Store it in `print`.\n" |
| msgstr "" |
| "// 将 `x` 捕获到一个匿名类型中并为其实现 `Fn`\n" |
| " // 将其存储在 `print` 中\n" |
| |
| #: src/fn/closures/anonymity.md:49 |
| msgid "" |
| "[A thorough analysis](https://huonw.github.io/blog/2015/05/finding-closure-" |
| "in-rust/), [`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)" |
| msgstr "" |
| "[深入分析](https://huonw.github.io/blog/2015/05/finding-closure-in-rust/)、" |
| "[`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/fn/closures/input_functions.md:3 |
| msgid "" |
| "Since closures may be used as arguments, you might wonder if the same can be " |
| "said about functions. And indeed they can! If you declare a function that " |
| "takes a closure as parameter, then any function that satisfies the trait " |
| "bound of that closure can be passed as a parameter." |
| msgstr "" |
| "既然闭包可以作为参数使用，你可能会想知道函数是否也可以这样。确实可以！如果你" |
| "声明一个函数，它接受一个闭包作为参数，那么任何满足该闭包 trait 约束的函数都可" |
| "以作为参数传递。" |
| |
| #: src/fn/closures/input_functions.md:9 |
| msgid "" |
| "// Define a function which takes a generic `F` argument\n" |
| "// bounded by `Fn`, and calls it\n" |
| msgstr "// 定义一个函数，它接受一个由 `Fn` 约束的泛型参数 `F`，并调用它\n" |
| |
| #: src/fn/closures/input_functions.md:14 |
| msgid "// Define a wrapper function satisfying the `Fn` bound\n" |
| msgstr "// 定义一个满足 `Fn` 约束的包装函数\n" |
| |
| #: src/fn/closures/input_functions.md:17 |
| msgid "\"I'm a function!\"" |
| msgstr "\"我是函数！\"" |
| |
| #: src/fn/closures/input_functions.md:21 |
| msgid "// Define a closure satisfying the `Fn` bound\n" |
| msgstr "// 定义一个满足 `Fn` 约束的闭包\n" |
| |
| #: src/fn/closures/input_functions.md:22 |
| msgid "\"I'm a closure!\"" |
| msgstr "\"我是闭包！\"" |
| |
| #: src/fn/closures/input_functions.md:29 |
| msgid "" |
| "As an additional note, the `Fn`, `FnMut`, and `FnOnce` `traits` dictate how " |
| "a closure captures variables from the enclosing scope." |
| msgstr "" |
| "另外需要注意的是，`Fn`、`FnMut` 和 `FnOnce` 这些 trait 决定了闭包如何从外部作" |
| "用域捕获变量。" |
| |
| #: src/fn/closures/input_functions.md:34 |
| msgid "" |
| "[`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)" |
| msgstr "" |
| "[`Fn`]、[`FnMut`] 和 [`FnOnce`]\n" |
| "\n" |
| "[`Fn`]: https://doc.rust-lang.org/std/ops/trait.Fn.html\n" |
| "[`FnMut`]: https://doc.rust-lang.org/std/ops/trait.FnMut.html\n" |
| "[`FnOnce`]: https://doc.rust-lang.org/std/ops/trait.FnOnce.html" |
| |
| #: src/fn/closures/output_parameters.md:3 |
| msgid "" |
| "Closures as input parameters are possible, so returning closures as output " |
| "parameters should also be possible. However, anonymous closure types are, by " |
| "definition, unknown, so we have to use `impl Trait` to return them." |
| msgstr "" |
| "既然闭包可以作为输入参数，那么将闭包作为输出参数返回也应该是可行的。然而，匿" |
| "名闭包类型本质上是未知的，因此我们必须使用 `impl Trait` 来返回它们。" |
| |
| #: src/fn/closures/output_parameters.md:8 |
| msgid "The valid traits for returning a closure are:" |
| msgstr "可用于返回闭包的有效 trait 包括：" |
| |
| #: src/fn/closures/output_parameters.md:10 |
| msgid "`Fn`" |
| msgstr "`Fn`" |
| |
| #: src/fn/closures/output_parameters.md:11 |
| msgid "`FnMut`" |
| msgstr "`FnMut`" |
| |
| #: src/fn/closures/output_parameters.md:12 |
| msgid "`FnOnce`" |
| msgstr "`FnOnce`" |
| |
| #: src/fn/closures/output_parameters.md:14 |
| msgid "" |
| "Beyond this, the `move` keyword must be used, which signals that all " |
| "captures occur by value. This is required because any captures by reference " |
| "would be dropped as soon as the function exited, leaving invalid references " |
| "in the closure." |
| msgstr "" |
| "此外，必须使用 `move` 关键字，它表示所有捕获都是按值进行的。这是必要的，因为" |
| "任何通过引用捕获的变量都会在函数退出时被丢弃，从而在闭包中留下无效的引用。" |
| |
| #: src/fn/closures/output_parameters.md:21 |
| msgid "\"Fn\"" |
| msgstr "\"Fn\"" |
| |
| #: src/fn/closures/output_parameters.md:23 |
| #: src/fn/closures/output_parameters.md:29 |
| #: src/fn/closures/output_parameters.md:35 |
| msgid "\"This is a: {}\"" |
| msgstr "\"这是一个：{}\"" |
| |
| #: src/fn/closures/output_parameters.md:27 |
| msgid "\"FnMut\"" |
| msgstr "\"FnMut\"" |
| |
| #: src/fn/closures/output_parameters.md:33 |
| msgid "\"FnOnce\"" |
| msgstr "\"FnOnce\"" |
| |
| #: src/fn/closures/output_parameters.md:51 |
| msgid "" |
| "[`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn.html), [`FnMut`](https://" |
| "doc.rust-lang.org/std/ops/trait.FnMut.html), [Generics](../../generics.md) " |
| "and [impl Trait](../../trait/impl_trait.md)." |
| msgstr "" |
| "[`Fn`]、[`FnMut`]、[泛型]和 [impl Trait]\n" |
| "\n" |
| "[`Fn`]: https://doc.rust-lang.org/std/ops/trait.Fn.html\n" |
| "[`FnMut`]: https://doc.rust-lang.org/std/ops/trait.FnMut.html\n" |
| "[泛型]: ../../generics.md\n" |
| "[impl Trait]: ../../trait/impl_trait.md" |
| |
| #: src/fn/closures/closure_examples.md:3 |
| msgid "" |
| "This section contains a few examples of using closures from the `std` " |
| "library." |
| msgstr "本节包含一些使用 `std` 库中闭包的示例。" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:3 |
| msgid "" |
| "`Iterator::any` is a function which when passed an iterator, will return " |
| "`true` if any element satisfies the predicate. Otherwise `false`. Its " |
| "signature:" |
| msgstr "" |
| "`Iterator::any` 是一个函数，它接受一个迭代器作为参数。如果任何元素满足给定的" |
| "条件，则返回 `true`，否则返回 `false`。其签名如下：" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:9 |
| #: src/fn/closures/closure_examples/iter_find.md:9 |
| msgid "// The type being iterated over.\n" |
| msgstr "// 被迭代的类型\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:12 |
| msgid "" |
| "// `any` takes `&mut self` meaning the caller may be borrowed\n" |
| " // and modified, but not consumed.\n" |
| msgstr "" |
| "// `any` 接受 `&mut self`，意味着调用者可能被借用\n" |
| " // 和修改，但不会被消耗\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:15 |
| msgid "" |
| "// `FnMut` meaning any captured variable may at most be\n" |
| " // modified, not consumed. `Self::Item` states it takes\n" |
| " // arguments to the closure by value.\n" |
| msgstr "" |
| "// `FnMut` 表示任何捕获的变量最多只能被修改，不能被消耗\n" |
| " // `Self::Item` 表示它通过值将参数传递给闭包\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:27 |
| msgid "// `iter()` for vecs yields `&i32`. Destructure to `i32`.\n" |
| msgstr "// 对 vec 使用 `iter()` 产生 `&i32`，解构为 `i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:28 |
| msgid "\"2 in vec1: {}\"" |
| msgstr "\"2 在 vec1 中：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:29 |
| msgid "// `into_iter()` for vecs yields `i32`. No destructuring required.\n" |
| msgstr "// 对 vec 使用 `into_iter()` 产生 `i32`，无需解构\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:30 |
| msgid "\"2 in vec2: {}\"" |
| msgstr "\"2 在 vec2 中：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:32 |
| msgid "" |
| "// `iter()` only borrows `vec1` and its elements, so they can be used again\n" |
| msgstr "// `iter()` 只借用 `vec1` 及其元素，所以它们可以再次使用\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:33 |
| msgid "\"vec1 len: {}\"" |
| msgstr "\"vec1 长度：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:34 |
| msgid "\"First element of vec1 is: {}\"" |
| msgstr "\"vec1 的第一个元素是：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:35 |
| msgid "" |
| "// `into_iter()` does move `vec2` and its elements, so they cannot be used " |
| "again\n" |
| " // println!(\"First element of vec2 is: {}\", vec2[0]);\n" |
| " // println!(\"vec2 len: {}\", vec2.len());\n" |
| " // TODO: uncomment two lines above and see compiler errors.\n" |
| msgstr "" |
| "// `into_iter()` 会移动 `vec2` 及其元素，所以它们不能再次使用\n" |
| " // println!(\"vec2 的第一个元素是：{}\", vec2[0]);\n" |
| " // println!(\"vec2 长度：{}\", vec2.len());\n" |
| " // TODO：取消上面两行的注释，观察编译器错误\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:43 |
| msgid "// `iter()` for arrays yields `&i32`.\n" |
| msgstr "// 对数组使用 `iter()` 产生 `&i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:44 |
| msgid "\"2 in array1: {}\"" |
| msgstr "\"2 在 array1 中：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:45 |
| msgid "// `into_iter()` for arrays yields `i32`.\n" |
| msgstr "// 对数组使用 `into_iter()` 产生 `i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:46 |
| msgid "\"2 in array2: {}\"" |
| msgstr "\"2 在 array2 中：{}\"" |
| |
| #: src/fn/closures/closure_examples/iter_any.md:52 |
| msgid "" |
| "[`std::iter::Iterator::any`](https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.any)" |
| msgstr "" |
| "[`std::iter::Iterator::any`]\n" |
| "\n" |
| "[`std::iter::Iterator::any`]: https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.any" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:3 |
| msgid "" |
| "`Iterator::find` is a function which iterates over an iterator and searches " |
| "for the first value which satisfies some condition. If none of the values " |
| "satisfy the condition, it returns `None`. Its signature:" |
| msgstr "" |
| "`Iterator::find` 是一个函数，它遍历迭代器并搜索满足特定条件的第一个值。如果没" |
| "有值满足条件，则返回 `None`。其签名如下：" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:12 |
| msgid "" |
| "// `find` takes `&mut self` meaning the caller may be borrowed\n" |
| " // and modified, but not consumed.\n" |
| msgstr "" |
| "// `find` 接受 `&mut self`，这意味着调用者可能被借用\n" |
| " // 和修改，但不会被消耗。\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:15 |
| msgid "" |
| "// `FnMut` meaning any captured variable may at most be\n" |
| " // modified, not consumed. `&Self::Item` states it takes\n" |
| " // arguments to the closure by reference.\n" |
| msgstr "" |
| "// `FnMut` 表示任何捕获的变量最多只能被修改，不能被消耗。\n" |
| " // `&Self::Item` 表示它通过引用将参数传递给闭包。\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:27 |
| msgid "// `iter()` for vecs yields `&i32`.\n" |
| msgstr "// 对 vec 使用 `iter()` 会产生 `&i32`。\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:29 |
| msgid "// `into_iter()` for vecs yields `i32`.\n" |
| msgstr "// 对 vec 使用 `into_iter()` 会产生 `i32`。\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:32 |
| msgid "" |
| "// `iter()` for vecs yields `&i32`, and we want to reference one of its\n" |
| " // items, so we have to destructure `&&i32` to `i32`\n" |
| msgstr "" |
| "// 对 vec 使用 `iter()` 会产生 `&i32`，而我们想要引用其中的一个\n" |
| " // 元素，所以我们必须将 `&&i32` 解构为 `i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:34 |
| msgid "\"Find 2 in vec1: {:?}\"" |
| msgstr "\"在 vec1 中查找 2：{:?}\"" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:35 |
| msgid "" |
| "// `into_iter()` for vecs yields `i32`, and we want to reference one of\n" |
| " // its items, so we have to destructure `&i32` to `i32`\n" |
| msgstr "" |
| "// 对 vec 使用 `into_iter()` 会产生 `i32`，而我们想要引用其中的\n" |
| " // 一个元素，所以我们必须将 `&i32` 解构为 `i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:37 |
| msgid "\"Find 2 in vec2: {:?}\"" |
| msgstr "\"在 vec2 中查找 2：{:?}\"" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:42 |
| msgid "// `iter()` for arrays yields `&&i32`\n" |
| msgstr "// 对数组使用 `iter()` 会产生 `&&i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:43 |
| msgid "\"Find 2 in array1: {:?}\"" |
| msgstr "\"在 array1 中查找 2：{:?}\"" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:44 |
| msgid "// `into_iter()` for arrays yields `&i32`\n" |
| msgstr "// 对数组使用 `into_iter()` 会产生 `&i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:45 |
| msgid "\"Find 2 in array2: {:?}\"" |
| msgstr "\"在 array2 中查找 2：{:?}\"" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:49 |
| msgid "" |
| "`Iterator::find` gives you a reference to the item. But if you want the " |
| "_index_ of the item, use `Iterator::position`." |
| msgstr "" |
| "`Iterator::find` 返回元素的引用。如果需获取元素的**索引**，则使用 " |
| "`Iterator::position`。" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:56 |
| msgid "" |
| "// `iter()` for vecs yields `&i32` and `position()` does not take a " |
| "reference, so\n" |
| " // we have to destructure `&i32` to `i32`\n" |
| msgstr "" |
| "// 对 vec 使用 `iter()` 会产生 `&i32`，而 `position()` 不接受引用，所以\n" |
| " // 我们必须将 `&i32` 解构为 `i32`\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:61 |
| msgid "" |
| "// `into_iter()` for vecs yields `i32` and `position()` does not take a " |
| "reference, so\n" |
| " // we do not have to destructure \n" |
| msgstr "" |
| "// 对 vec 使用 `into_iter()` 会产生 `i32`，而 `position()` 不接受引用，所以\n" |
| " // 我们不需要进行解构\n" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:70 |
| msgid "" |
| "[`std::iter::Iterator::find`](https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.find)" |
| msgstr "" |
| "[`std::iter::Iterator::find`]\n" |
| "\n" |
| "[`std::iter::Iterator::find`]: https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.find" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:72 |
| msgid "" |
| "[`std::iter::Iterator::find_map`](https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.find_map)" |
| msgstr "" |
| "[`std::iter::Iterator::find_map`]\n" |
| "\n" |
| "[`std::iter::Iterator::find_map`]: https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.find_map" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:74 |
| msgid "" |
| "[`std::iter::Iterator::position`](https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.position)" |
| msgstr "" |
| "[`std::iter::Iterator::position`]\n" |
| "\n" |
| "[`std::iter::Iterator::position`]: https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.position" |
| |
| #: src/fn/closures/closure_examples/iter_find.md:76 |
| msgid "" |
| "[`std::iter::Iterator::rposition`](https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.rposition)" |
| msgstr "" |
| "[`std::iter::Iterator::rposition`]\n" |
| "\n" |
| "[`std::iter::Iterator::rposition`]: https://doc.rust-lang.org/std/iter/" |
| "trait.Iterator.html#method.rposition" |
| |
| #: src/fn/hof.md:3 |
| msgid "" |
| "Rust provides Higher Order Functions (HOF). These are functions that take " |
| "one or more functions and/or produce a more useful function. HOFs and lazy " |
| "iterators give Rust its functional flavor." |
| msgstr "" |
| "Rust 提供了高阶函数（Higher Order Functions，HOF）。这些函数接受一个或多个函" |
| "数作为参数，并/或产生一个更有用的函数。HOF 和惰性迭代器赋予了 Rust 函数式编程" |
| "的特性。" |
| |
| #: src/fn/hof.md:13 |
| msgid "\"Find the sum of all the numbers with odd squares under 1000\"" |
| msgstr "\"找出所有平方为奇数且小于 1000 的数字之和\"" |
| |
| #: src/fn/hof.md:16 |
| msgid "" |
| "// Imperative approach\n" |
| " // Declare accumulator variable\n" |
| msgstr "" |
| "// 命令式方法\n" |
| " // 声明累加器变量\n" |
| |
| #: src/fn/hof.md:19 |
| msgid "// Iterate: 0, 1, 2, ... to infinity\n" |
| msgstr "// 迭代：从 0, 1, 2, ... 到无穷大\n" |
| |
| #: src/fn/hof.md:21 |
| msgid "// Square the number\n" |
| msgstr "// 计算数字的平方\n" |
| |
| #: src/fn/hof.md:25 |
| msgid "// Break loop if exceeded the upper limit\n" |
| msgstr "// 如果超过上限则跳出循环\n" |
| |
| #: src/fn/hof.md:28 |
| msgid "// Accumulate value, if it's odd\n" |
| msgstr "// 如果是奇数，则累加值\n" |
| |
| #: src/fn/hof.md:32 |
| msgid "\"imperative style: {}\"" |
| msgstr "\"命令式风格：{}\"" |
| |
| #: src/fn/hof.md:34 |
| msgid "// Functional approach\n" |
| msgstr "// 函数式方法\n" |
| |
| #: src/fn/hof.md:36 |
| msgid "// All natural numbers squared\n" |
| msgstr "// 所有自然数的平方\n" |
| |
| #: src/fn/hof.md:37 |
| msgid "// Below upper limit\n" |
| msgstr "// 小于上限\n" |
| |
| #: src/fn/hof.md:38 |
| msgid "// That are odd\n" |
| msgstr "// 筛选奇数\n" |
| |
| #: src/fn/hof.md:39 |
| msgid "// Sum them\n" |
| msgstr "// 求和\n" |
| |
| #: src/fn/hof.md:40 |
| msgid "\"functional style: {}\"" |
| msgstr "\"函数式风格：{}\"" |
| |
| #: src/fn/hof.md:44 |
| msgid "" |
| "[Option](https://doc.rust-lang.org/core/option/enum.Option.html) and " |
| "[Iterator](https://doc.rust-lang.org/core/iter/trait.Iterator.html) " |
| "implement their fair share of HOFs." |
| msgstr "" |
| "[Option] 和 [Iterator] 实现了相当多的高阶函数。\n" |
| "\n" |
| "[Option]: https://doc.rust-lang.org/core/option/enum.Option.html\n" |
| "[Iterator]: https://doc.rust-lang.org/core/iter/trait.Iterator.html" |
| |
| #: src/fn/diverging.md:3 |
| msgid "" |
| "Diverging functions never return. They are marked using `!`, which is an " |
| "empty type." |
| msgstr "发散函数永不返回。它们使用 `!` 标记，这是一个空类型。" |
| |
| #: src/fn/diverging.md:7 src/fn/diverging.md:35 |
| msgid "\"This call never returns.\"" |
| msgstr "\"此调用永不返回。\"" |
| |
| #: src/fn/diverging.md:11 |
| msgid "" |
| "As opposed to all the other types, this one cannot be instantiated, because " |
| "the set of all possible values this type can have is empty. Note that, it is " |
| "different from the `()` type, which has exactly one possible value." |
| msgstr "" |
| "与所有其他类型相反，这个类型不能被实例化，因为这个类型可能拥有的所有可能值的" |
| "集合是空的。注意，它与 `()` 类型不同，后者恰好有一个可能的值。" |
| |
| #: src/fn/diverging.md:15 |
| msgid "" |
| "For example, this function returns as usual, although there is no " |
| "information in the return value." |
| msgstr "例如，这个函数像往常一样返回，尽管返回值中没有任何信息。" |
| |
| #: src/fn/diverging.md:25 |
| msgid "\"This function returns and you can see this line.\"" |
| msgstr "\"这个函数返回了，你可以看到这一行。\"" |
| |
| #: src/fn/diverging.md:29 |
| msgid "" |
| "As opposed to this function, which will never return the control back to the " |
| "caller." |
| msgstr "与之相对的是这个函数，它永远不会将控制权返回给调用者。" |
| |
| #: src/fn/diverging.md:36 |
| msgid "\"You will never see this line!\"" |
| msgstr "\"你永远不会看到这一行！\"" |
| |
| #: src/fn/diverging.md:40 |
| msgid "" |
| "Although this might seem like an abstract concept, it is actually very " |
| "useful and often handy. The main advantage of this type is that it can be " |
| "cast to any other type, making it versatile in situations where an exact " |
| "type is required, such as in match branches. This flexibility allows us to " |
| "write code like this:" |
| msgstr "" |
| "虽然这看起来像是一个抽象概念，但它实际上非常有用且经常派上用场。这种类型的主" |
| "要优势是它可以被转换为任何其他类型，这使得它在需要精确类型的情况下非常灵活，" |
| "比如在 match 分支中。这种灵活性允许我们编写如下代码：" |
| |
| #: src/fn/diverging.md:50 |
| msgid "" |
| "// Notice that the return type of this match expression must be u32\n" |
| " // because of the type of the \"addition\" variable.\n" |
| msgstr "" |
| "// 注意这个 match 表达式的返回类型必须是 u32，\n" |
| " // 因为 \"addition\" 变量的类型是 u32。\n" |
| |
| #: src/fn/diverging.md:53 |
| msgid "// The \"i\" variable is of type u32, which is perfectly fine.\n" |
| msgstr "// \"i\" 变量的类型是 u32，这完全没问题。\n" |
| |
| #: src/fn/diverging.md:55 |
| msgid "" |
| "// On the other hand, the \"continue\" expression does not return\n" |
| " // u32, but it is still fine, because it never returns and " |
| "therefore\n" |
| " // does not violate the type requirements of the match " |
| "expression.\n" |
| msgstr "" |
| "// 另一方面，\"continue\" 表达式不返回 u32，\n" |
| " // 但这仍然可以，因为它永远不会返回，\n" |
| " // 因此不违反 match 表达式的类型要求。\n" |
| |
| #: src/fn/diverging.md:64 |
| msgid "\"Sum of odd numbers up to 9 (excluding): {}\"" |
| msgstr "\"9 以下（不包括 9）的奇数之和：{}\"" |
| |
| #: src/fn/diverging.md:68 |
| msgid "" |
| "It is also the return type of functions that loop forever (e.g. `loop {}`) " |
| "like network servers or functions that terminate the process (e.g. `exit()`)." |
| msgstr "" |
| "它也是永远循环的函数（例如 `loop {}`）的返回类型，比如网络服务器，或终止进程" |
| "的函数（例如 `exit()`）。" |
| |
| #: src/mod.md:3 |
| msgid "" |
| "Rust provides a powerful module system that can be used to hierarchically " |
| "split code in logical units (modules), and manage visibility (public/" |
| "private) between them." |
| msgstr "" |
| "Rust 提供了一个强大的模块系统，可以用来将代码分层地拆分成逻辑单元（模块），并" |
| "管理它们之间的可见性（公有/私有）。" |
| |
| #: src/mod.md:7 |
| msgid "" |
| "A module is a collection of items: functions, structs, traits, `impl` " |
| "blocks, and even other modules." |
| msgstr "" |
| "一个模块是一系列项的集合：函数、结构体、trait、`impl` 块，甚至其他模块。" |
| |
| #: src/mod/visibility.md:3 |
| msgid "" |
| "By default, the items in a module have private visibility, but this can be " |
| "overridden with the `pub` modifier. Only the public items of a module can be " |
| "accessed from outside the module scope." |
| msgstr "" |
| "默认情况下，模块中的项具有私有可见性，但可以使用 `pub` 修饰符来覆盖这一默认行" |
| "为。只有模块中的公有项可以从模块作用域外部访问。" |
| |
| #: src/mod/visibility.md:8 |
| msgid "// A module named `my_mod`\n" |
| msgstr "// 一个名为 `my_mod` 的模块\n" |
| |
| #: src/mod/visibility.md:10 |
| msgid "// Items in modules default to private visibility.\n" |
| msgstr "// 模块中的项默认为私有可见性。\n" |
| |
| #: src/mod/visibility.md:12 |
| msgid "\"called `my_mod::private_function()`\"" |
| msgstr "\"调用了 `my_mod::private_function()`\"" |
| |
| #: src/mod/visibility.md:15 |
| msgid "// Use the `pub` modifier to override default visibility.\n" |
| msgstr "// 使用 `pub` 修饰符来覆盖默认的可见性。\n" |
| |
| #: src/mod/visibility.md:17 |
| msgid "\"called `my_mod::function()`\"" |
| msgstr "\"调用了 `my_mod::function()`\"" |
| |
| #: src/mod/visibility.md:20 |
| msgid "" |
| "// Items can access other items in the same module,\n" |
| " // even when private.\n" |
| msgstr "" |
| "// 同一模块中的项可以访问其他项，\n" |
| " // 即使是私有的。\n" |
| |
| #: src/mod/visibility.md:23 |
| msgid "\"called `my_mod::indirect_access()`, that\\n> \"" |
| msgstr "\"调用了 `my_mod::indirect_access()`，它\\n> \"" |
| |
| #: src/mod/visibility.md:27 |
| msgid "// Modules can also be nested\n" |
| msgstr "// 模块也可以嵌套\n" |
| |
| #: src/mod/visibility.md:30 |
| msgid "\"called `my_mod::nested::function()`\"" |
| msgstr "\"调用了 `my_mod::nested::function()`\"" |
| |
| #: src/mod/visibility.md:35 |
| msgid "\"called `my_mod::nested::private_function()`\"" |
| msgstr "\"调用了 `my_mod::nested::private_function()`\"" |
| |
| #: src/mod/visibility.md:38 |
| msgid "" |
| "// Functions declared using `pub(in path)` syntax are only visible\n" |
| " // within the given path. `path` must be a parent or ancestor " |
| "module\n" |
| msgstr "" |
| "// 使用 `pub(in path)` 语法声明的函数只在给定的路径中可见。\n" |
| " // `path` 必须是父模块或祖先模块\n" |
| |
| #: src/mod/visibility.md:41 |
| msgid "\"called `my_mod::nested::public_function_in_my_mod()`, that\\n> \"" |
| msgstr "\"调用了 `my_mod::nested::public_function_in_my_mod()`，它\\n> \"" |
| |
| #: src/mod/visibility.md:45 |
| msgid "" |
| "// Functions declared using `pub(self)` syntax are only visible within\n" |
| " // the current module, which is the same as leaving them private\n" |
| msgstr "" |
| "// 使用 `pub(self)` 语法声明的函数只在当前模块中可见，\n" |
| " // 这与将它们保持为私有是一样的\n" |
| |
| #: src/mod/visibility.md:48 |
| msgid "\"called `my_mod::nested::public_function_in_nested()`\"" |
| msgstr "\"调用了 `my_mod::nested::public_function_in_nested()`\"" |
| |
| #: src/mod/visibility.md:51 |
| msgid "" |
| "// Functions declared using `pub(super)` syntax are only visible within\n" |
| " // the parent module\n" |
| msgstr "" |
| "// 使用 `pub(super)` 语法声明的函数仅在父模块中可见\n" |
| " \n" |
| |
| #: src/mod/visibility.md:54 |
| msgid "\"called `my_mod::nested::public_function_in_super_mod()`\"" |
| msgstr "\"调用了 `my_mod::nested::public_function_in_super_mod()`\"" |
| |
| #: src/mod/visibility.md:59 |
| msgid "\"called `my_mod::call_public_function_in_my_mod()`, that\\n> \"" |
| msgstr "\"调用了 `my_mod::call_public_function_in_my_mod()`，它\\n> \"" |
| |
| #: src/mod/visibility.md:61 |
| msgid "\"> \"" |
| msgstr "\"> \"" |
| |
| #: src/mod/visibility.md:65 |
| msgid "// pub(crate) makes functions visible only within the current crate\n" |
| msgstr "// pub(crate) 使函数仅在当前 crate 内可见\n" |
| |
| #: src/mod/visibility.md:67 |
| msgid "\"called `my_mod::public_function_in_crate()`\"" |
| msgstr "\"调用了 `my_mod::public_function_in_crate()`\"" |
| |
| #: src/mod/visibility.md:70 |
| msgid "// Nested modules follow the same rules for visibility\n" |
| msgstr "// 嵌套模块遵循相同的可见性规则\n" |
| |
| #: src/mod/visibility.md:74 |
| msgid "\"called `my_mod::private_nested::function()`\"" |
| msgstr "\"调用了 `my_mod::private_nested::function()`\"" |
| |
| #: src/mod/visibility.md:77 |
| msgid "" |
| "// Private parent items will still restrict the visibility of a child item,\n" |
| " // even if it is declared as visible within a bigger scope.\n" |
| msgstr "" |
| "// 私有父项仍会限制子项的可见性，\n" |
| " // 即使子项被声明为在更大范围内可见。\n" |
| |
| #: src/mod/visibility.md:81 |
| msgid "\"called `my_mod::private_nested::restricted_function()`\"" |
| msgstr "\"调用了 `my_mod::private_nested::restricted_function()`\"" |
| |
| #: src/mod/visibility.md:87 src/mod/use.md:25 src/mod/super.md:8 |
| #: src/mod/split.md:24 |
| msgid "\"called `function()`\"" |
| msgstr "\"调用了 `function()`\"" |
| |
| #: src/mod/visibility.md:91 |
| msgid "" |
| "// Modules allow disambiguation between items that have the same name.\n" |
| msgstr "// 模块允许消除同名项之间的歧义。\n" |
| |
| #: src/mod/visibility.md:95 |
| msgid "" |
| "// Public items, including those inside nested modules, can be\n" |
| " // accessed from outside the parent module.\n" |
| msgstr "// 公有项（包括嵌套模块内的）可以从父模块外部访问。\n" |
| |
| #: src/mod/visibility.md:101 |
| msgid "// pub(crate) items can be called from anywhere in the same crate\n" |
| msgstr "// pub(crate) 项可以在同一个 crate 的任何地方调用\n" |
| |
| #: src/mod/visibility.md:104 |
| msgid "" |
| "// pub(in path) items can only be called from within the module specified\n" |
| " // Error! function `public_function_in_my_mod` is private\n" |
| " //my_mod::nested::public_function_in_my_mod();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// pub(in path) 项只能在指定的模块内调用\n" |
| " // 错误！函数 `public_function_in_my_mod` 是私有的\n" |
| " //my_mod::nested::public_function_in_my_mod();\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/visibility.md:109 |
| msgid "" |
| "// Private items of a module cannot be directly accessed, even if\n" |
| " // nested in a public module:\n" |
| msgstr "// 模块的私有项不能被直接访问，即使它们嵌套在公有模块中：\n" |
| |
| #: src/mod/visibility.md:112 |
| msgid "" |
| "// Error! `private_function` is private\n" |
| " //my_mod::private_function();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`private_function` 是私有的\n" |
| " //my_mod::private_function();\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/visibility.md:116 |
| msgid "" |
| "// Error! `private_function` is private\n" |
| " //my_mod::nested::private_function();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`private_function` 是私有的\n" |
| " //my_mod::nested::private_function();\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/visibility.md:120 |
| msgid "" |
| "// Error! `private_nested` is a private module\n" |
| " //my_mod::private_nested::function();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`private_nested` 是一个私有模块\n" |
| " //my_mod::private_nested::function();\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/visibility.md:124 |
| msgid "" |
| "// Error! `private_nested` is a private module\n" |
| " //my_mod::private_nested::restricted_function();\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`private_nested` 是一个私有模块\n" |
| " //my_mod::private_nested::restricted_function();\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/struct_visibility.md:3 |
| msgid "" |
| "Structs have an extra level of visibility with their fields. The visibility " |
| "defaults to private, and can be overridden with the `pub` modifier. This " |
| "visibility only matters when a struct is accessed from outside the module " |
| "where it is defined, and has the goal of hiding information (encapsulation)." |
| msgstr "" |
| "结构体的字段具有额外的可见性级别。字段默认为私有，可以使用 `pub` 修饰符来覆" |
| "盖。这种可见性只在从结构体定义模块外部访问时才有意义，其目的是实现信息隐藏" |
| "（封装）。" |
| |
| #: src/mod/struct_visibility.md:10 |
| msgid "// A public struct with a public field of generic type `T`\n" |
| msgstr "// 一个具有泛型类型 `T` 公有字段的公有结构体\n" |
| |
| #: src/mod/struct_visibility.md:15 |
| msgid "// A public struct with a private field of generic type `T`\n" |
| msgstr "// 一个具有泛型类型 `T` 私有字段的公有结构体\n" |
| |
| #: src/mod/struct_visibility.md:21 |
| msgid "// A public constructor method\n" |
| msgstr "// 一个公有的构造方法\n" |
| |
| #: src/mod/struct_visibility.md:31 |
| msgid "// Public structs with public fields can be constructed as usual\n" |
| msgstr "// 具有公有字段的公有结构体可以正常构造\n" |
| |
| #: src/mod/struct_visibility.md:32 |
| msgid "\"public information\"" |
| msgstr "\"公开信息\"" |
| |
| #: src/mod/struct_visibility.md:34 |
| msgid "// and their fields can be normally accessed.\n" |
| msgstr "// 且可以正常访问其字段。\n" |
| |
| #: src/mod/struct_visibility.md:35 |
| msgid "\"The open box contains: {}\"" |
| msgstr "\"打开的盒子包含：{}\"" |
| |
| #: src/mod/struct_visibility.md:37 |
| msgid "" |
| "// Public structs with private fields cannot be constructed using field " |
| "names.\n" |
| " // Error! `ClosedBox` has private fields\n" |
| " //let closed_box = my::ClosedBox { contents: \"classified " |
| "information\" };\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 具有私有字段的公有结构体不能使用字段名来构造。\n" |
| " // 错误！`ClosedBox` 有私有字段\n" |
| " //let closed_box = my::ClosedBox { contents: \"机密信息\" };\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/struct_visibility.md:42 |
| msgid "" |
| "// However, structs with private fields can be created using\n" |
| " // public constructors\n" |
| msgstr "// 然而，具有私有字段的结构体可以使用公有构造函数创建\n" |
| |
| #: src/mod/struct_visibility.md:44 |
| msgid "\"classified information\"" |
| msgstr "\"机密信息\"" |
| |
| #: src/mod/struct_visibility.md:46 |
| msgid "" |
| "// and the private fields of a public struct cannot be accessed.\n" |
| " // Error! The `contents` field is private\n" |
| " //println!(\"The closed box contains: {}\", _closed_box.contents);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 且无法访问公有结构体的私有字段。\n" |
| " // 错误！`contents` 字段是私有的\n" |
| " //println!(\"封闭的盒子包含：{}\", _closed_box.contents);\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/mod/struct_visibility.md:55 |
| msgid "[generics](../generics.md) and [methods](../fn/methods.md)" |
| msgstr "[泛型](../generics.md)和[方法](../fn/methods.md)" |
| |
| #: src/mod/use.md:3 |
| msgid "" |
| "The `use` declaration can be used to bind a full path to a new name, for " |
| "easier access. It is often used like this:" |
| msgstr "" |
| "`use` 声明可以将完整路径绑定到新名称，以便更轻松地访问。它通常这样使用：" |
| |
| #: src/mod/use.md:18 |
| msgid "You can use the `as` keyword to bind imports to a different name:" |
| msgstr "你可以使用 `as` 关键字将导入绑定到不同的名称：" |
| |
| #: src/mod/use.md:21 |
| msgid "// Bind the `deeply::nested::function` path to `other_function`.\n" |
| msgstr "// 将 `deeply::nested::function` 路径绑定到 `other_function`。\n" |
| |
| #: src/mod/use.md:31 |
| msgid "\"called `deeply::nested::function()`\"" |
| msgstr "\"调用了 `deeply::nested::function()`\"" |
| |
| #: src/mod/use.md:37 |
| msgid "// Easier access to `deeply::nested::function`\n" |
| msgstr "// 更方便地访问 `deeply::nested::function`\n" |
| |
| #: src/mod/use.md:40 |
| msgid "\"Entering block\"" |
| msgstr "\"进入代码块\"" |
| |
| #: src/mod/use.md:42 |
| msgid "" |
| "// This is equivalent to `use deeply::nested::function as function`.\n" |
| " // This `function()` will shadow the outer one.\n" |
| msgstr "" |
| "// 这等同于 `use deeply::nested::function as function`。\n" |
| " // 这个 `function()` 将遮蔽外部的同名函数。\n" |
| |
| #: src/mod/use.md:46 |
| msgid "" |
| "// `use` bindings have a local scope. In this case, the\n" |
| " // shadowing of `function()` is only in this block.\n" |
| msgstr "" |
| "// `use` 绑定具有局部作用域。在这种情况下，\n" |
| " // `function()` 的遮蔽仅在此代码块内有效。\n" |
| |
| #: src/mod/use.md:50 |
| msgid "\"Leaving block\"" |
| msgstr "\"离开代码块\"" |
| |
| #: src/mod/super.md:3 |
| msgid "" |
| "The `super` and `self` keywords can be used in the path to remove ambiguity " |
| "when accessing items and to prevent unnecessary hardcoding of paths." |
| msgstr "" |
| "`super` 和 `self` 关键字可以在路径中使用，以消除访问项目时的歧义，并避免不必" |
| "要的路径硬编码。" |
| |
| #: src/mod/super.md:13 |
| msgid "\"called `cool::function()`\"" |
| msgstr "\"调用了 `cool::function()`\"" |
| |
| #: src/mod/super.md:19 src/mod/split.md:49 |
| msgid "\"called `my::function()`\"" |
| msgstr "\"调用了 `my::function()`\"" |
| |
| #: src/mod/super.md:24 |
| msgid "\"called `my::cool::function()`\"" |
| msgstr "\"调用了 `my::cool::function()`\"" |
| |
| #: src/mod/super.md:29 |
| msgid "// Let's access all the functions named `function` from this scope!\n" |
| msgstr "// 让我们从这个作用域访问所有名为 `function` 的函数！\n" |
| |
| #: src/mod/super.md:30 |
| msgid "\"called `my::indirect_call()`, that\\n> \"" |
| msgstr "\"调用了 `my::indirect_call()`，它\\n> \"" |
| |
| #: src/mod/super.md:32 |
| msgid "" |
| "// The `self` keyword refers to the current module scope - in this case " |
| "`my`.\n" |
| " // Calling `self::function()` and calling `function()` directly both " |
| "give\n" |
| " // the same result, because they refer to the same function.\n" |
| msgstr "" |
| "// `self` 关键字指的是当前模块作用域 - 在这里是 `my`。\n" |
| " // 调用 `self::function()` 和直接调用 `function()` 都会\n" |
| " // 得到相同的结果，因为它们指向同一个函数。\n" |
| |
| #: src/mod/super.md:38 |
| msgid "// We can also use `self` to access another module inside `my`:\n" |
| msgstr "// 我们也可以使用 `self` 来访问 `my` 内的另一个模块：\n" |
| |
| #: src/mod/super.md:41 |
| msgid "" |
| "// The `super` keyword refers to the parent scope (outside the `my` " |
| "module).\n" |
| msgstr "// `super` 关键字指的是父作用域（`my` 模块之外）。\n" |
| |
| #: src/mod/super.md:44 |
| msgid "" |
| "// This will bind to the `cool::function` in the *crate* scope.\n" |
| " // In this case the crate scope is the outermost scope.\n" |
| msgstr "" |
| "// 这将绑定到 *crate* 作用域中的 `cool::function`。\n" |
| " // 在这种情况下，crate 作用域是最外层作用域。\n" |
| |
| #: src/mod/split.md:3 |
| msgid "" |
| "Modules can be mapped to a file/directory hierarchy. Let's break down the " |
| "[visibility example](visibility.md) in files:" |
| msgstr "" |
| "模块可以映射到文件/目录层次结构。让我们将[可见性示例](visibility.md)拆分成多" |
| "个文件：" |
| |
| #: src/mod/split.md:16 |
| msgid "In `split.rs`:" |
| msgstr "在 `split.rs` 文件中：" |
| |
| #: src/mod/split.md:19 |
| msgid "" |
| "// This declaration will look for a file named `my.rs` and will\n" |
| "// insert its contents inside a module named `my` under this scope\n" |
| msgstr "" |
| "// 这个声明会查找名为 `my.rs` 的文件，并将其内容\n" |
| "// 插入到当前作用域下名为 `my` 的模块中\n" |
| |
| #: src/mod/split.md:39 |
| msgid "In `my.rs`:" |
| msgstr "在 `my.rs` 文件中：" |
| |
| #: src/mod/split.md:42 |
| msgid "" |
| "// Similarly `mod inaccessible` and `mod nested` will locate the " |
| "`nested.rs`\n" |
| "// and `inaccessible.rs` files and insert them here under their respective\n" |
| "// modules\n" |
| msgstr "" |
| "// 同样，`mod inaccessible` 和 `mod nested` 会分别定位到\n" |
| "// `nested.rs` 和 `inaccessible.rs` 文件，\n" |
| "// 并将它们的内容插入到这里对应的模块中\n" |
| |
| #: src/mod/split.md:53 |
| msgid "\"called `my::private_function()`\"" |
| msgstr "\"调用了 `my::private_function()`\"" |
| |
| #: src/mod/split.md:57 |
| msgid "\"called `my::indirect_access()`, that\\n> \"" |
| msgstr "\"调用了 `my::indirect_access()`，它\\n> \"" |
| |
| #: src/mod/split.md:63 |
| msgid "In `my/nested.rs`:" |
| msgstr "在 `my/nested.rs` 文件中：" |
| |
| #: src/mod/split.md:67 |
| msgid "\"called `my::nested::function()`\"" |
| msgstr "\"调用了 `my::nested::function()`\"" |
| |
| #: src/mod/split.md:72 |
| msgid "\"called `my::nested::private_function()`\"" |
| msgstr "\"调用了 `my::nested::private_function()`\"" |
| |
| #: src/mod/split.md:76 |
| msgid "In `my/inaccessible.rs`:" |
| msgstr "在 `my/inaccessible.rs` 文件中：" |
| |
| #: src/mod/split.md:81 |
| msgid "\"called `my::inaccessible::public_function()`\"" |
| msgstr "\"调用了 `my::inaccessible::public_function()`\"" |
| |
| #: src/mod/split.md:85 |
| msgid "Let's check that things still work as before:" |
| msgstr "让我们检查一下是否一切仍然如之前一样正常运行：" |
| |
| #: src/crates.md:3 |
| msgid "" |
| "A crate is a compilation unit in Rust. Whenever `rustc some_file.rs` is " |
| "called, `some_file.rs` is treated as the _crate file_. If `some_file.rs` has " |
| "`mod` declarations in it, then the contents of the module files would be " |
| "inserted in places where `mod` declarations in the crate file are found, " |
| "_before_ running the compiler over it. In other words, modules do _not_ get " |
| "compiled individually, only crates get compiled." |
| msgstr "" |
| "在 Rust 中，crate 是一个编译单元。每当执行 `rustc some_file.rs` 时，" |
| "`some_file.rs` 就被视为**crate 文件**。如果 `some_file.rs` 中包含 `mod` 声" |
| "明，那么模块文件的内容会在编译器处理之前被插入到 crate 文件中 `mod` 声明的位" |
| "置。换句话说，模块**不会**被单独编译，只有 crate 才会被编译。" |
| |
| #: src/crates.md:10 |
| msgid "" |
| "A crate can be compiled into a binary or into a library. By default, `rustc` " |
| "will produce a binary from a crate. This behavior can be overridden by " |
| "passing the `--crate-type` flag to `lib`." |
| msgstr "" |
| "一个 crate 可以被编译成二进制文件或库。默认情况下，`rustc` 会将 crate 编译成" |
| "二进制文件。通过向 `rustc` 传递 `--crate-type` 标志并指定 `lib`，可以改变这一" |
| "默认行为。" |
| |
| #: src/crates/lib.md:3 |
| msgid "Let's create a library, and then see how to link it to another crate." |
| msgstr "让我们创建一个库，然后看看如何将它链接到另一个 crate。" |
| |
| #: src/crates/lib.md:5 |
| msgid "In `rary.rs`:" |
| msgstr "在 `rary.rs` 文件中：" |
| |
| #: src/crates/lib.md:9 src/attribute/crate.md:19 |
| msgid "\"called rary's `public_function()`\"" |
| msgstr "\"调用了 rary 的 `public_function()`\"" |
| |
| #: src/crates/lib.md:13 src/attribute/crate.md:23 |
| msgid "\"called rary's `private_function()`\"" |
| msgstr "\"调用了 rary 的 `private_function()`\"" |
| |
| #: src/crates/lib.md:17 src/attribute/crate.md:27 |
| msgid "\"called rary's `indirect_access()`, that\\n> \"" |
| msgstr "\"调用了 rary 的 `indirect_access()`，它\\n> \"" |
| |
| #: src/crates/lib.md:29 |
| msgid "" |
| "Libraries get prefixed with \"lib\", and by default they get named after " |
| "their crate file, but this default name can be overridden by passing the `--" |
| "crate-name` option to `rustc` or by using the [`crate_name` attribute](../" |
| "attribute/crate.md)." |
| msgstr "" |
| "库文件名会自动添加 \"lib\" 前缀，默认使用 crate 文件的名称。但可以通过向 " |
| "`rustc` 传递 `--crate-name` 选项或使用 [`crate_name` 属性](../attribute/" |
| "crate.md) 来覆盖这个默认名称。" |
| |
| #: src/crates/using_lib.md:3 |
| msgid "" |
| "To link a crate to this new library you may use `rustc`'s `--extern` flag. " |
| "All of its items will then be imported under a module named the same as the " |
| "library. This module generally behaves the same way as any other module." |
| msgstr "" |
| "要将 crate 链接到这个新库，可以使用 `rustc` 的 `--extern` 标志。库中的所有项" |
| "目都会被导入到一个与库同名的模块下。这个模块的行为通常与其他模块相同。" |
| |
| #: src/crates/using_lib.md:8 |
| msgid "" |
| "// extern crate rary; // May be required for Rust 2015 edition or earlier\n" |
| msgstr "// extern crate rary; // Rust 2015 版本或更早版本可能需要此声明\n" |
| |
| #: src/crates/using_lib.md:13 |
| msgid "" |
| "// Error! `private_function` is private\n" |
| " //rary::private_function();\n" |
| msgstr "" |
| "// 错误！`private_function` 是私有的\n" |
| " //rary::private_function();\n" |
| |
| #: src/cargo.md:3 |
| msgid "" |
| "`cargo` is the official Rust package management tool. It has lots of really " |
| "useful features to improve code quality and developer velocity! These include" |
| msgstr "" |
| "`cargo` 是 Rust 的官方包管理工具。它提供了许多非常有用的功能，可以提高代码质" |
| "量和开发效率！这些功能包括：" |
| |
| #: src/cargo.md:6 |
| msgid "" |
| "Dependency management and integration with [crates.io](https://crates.io) " |
| "(the official Rust package registry)" |
| msgstr "" |
| "依赖管理和与 [crates.io](https://crates.io)（Rust 官方包注册中心）的集成" |
| |
| #: src/cargo.md:8 |
| msgid "Awareness of unit tests" |
| msgstr "支持单元测试" |
| |
| #: src/cargo.md:9 |
| msgid "Awareness of benchmarks" |
| msgstr "支持基准测试" |
| |
| #: src/cargo.md:11 |
| msgid "" |
| "This chapter will go through some quick basics, but you can find the " |
| "comprehensive docs in [The Cargo Book](https://doc.rust-lang.org/cargo/)." |
| msgstr "" |
| "本章将快速介绍一些基础知识，更全面的文档可以在 [Cargo 手册](https://doc.rust-" |
| "lang.org/cargo/) 中找到。" |
| |
| #: src/cargo/deps.md:3 |
| msgid "" |
| "Most programs have dependencies on some libraries. If you have ever managed " |
| "dependencies by hand, you know how much of a pain this can be. Luckily, the " |
| "Rust ecosystem comes standard with `cargo`! `cargo` can manage dependencies " |
| "for a project." |
| msgstr "" |
| "大多数程序都依赖于一些库。如果你曾经手动管理过依赖，你就知道这有多么痛苦。幸" |
| "运的是，Rust 生态系统标配了 `cargo`！`cargo` 可以为项目管理依赖。" |
| |
| #: src/cargo/deps.md:8 |
| msgid "To create a new Rust project," |
| msgstr "要创建一个新的 Rust 项目，可以使用以下命令：" |
| |
| #: src/cargo/deps.md:11 |
| msgid "# A binary\n" |
| msgstr "# 创建二进制项目\n" |
| |
| #: src/cargo/deps.md:13 |
| msgid "# A library\n" |
| msgstr "# 创建库项目\n" |
| |
| #: src/cargo/deps.md:18 |
| msgid "" |
| "For the rest of this chapter, let's assume we are making a binary, rather " |
| "than a library, but all of the concepts are the same." |
| msgstr "" |
| "在本章的剩余部分，我们假设我们正在创建一个二进制项目，而不是一个库项目，但所" |
| "有的概念都是相同的。" |
| |
| #: src/cargo/deps.md:21 |
| msgid "After the above commands, you should see a file hierarchy like this:" |
| msgstr "执行上述命令后，你应该会看到如下的文件结构：" |
| |
| #: src/cargo/deps.md:35 |
| msgid "" |
| "The `main.rs` is the root source file for your new `foo` project -- nothing " |
| "new there. The `Cargo.toml` is the config file for `cargo` for this project. " |
| "If you look inside it, you should see something like this:" |
| msgstr "" |
| "`main.rs` 是你新建的 `foo` 项目的主源文件 —— 这一点没什么新鲜的。" |
| "`Cargo.toml` 则是这个项目的 `cargo` 配置文件。如果你查看它的内容，应该会看到" |
| "类似这样的内容：" |
| |
| #: src/cargo/deps.md:39 |
| msgid "" |
| "```toml\n" |
| "[package]\n" |
| "name = \"foo\"\n" |
| "version = \"0.1.0\"\n" |
| "authors = [\"mark\"]\n" |
| "\n" |
| "[dependencies]\n" |
| "```" |
| msgstr "" |
| "```toml\n" |
| "[package]\n" |
| "name = \"foo\"\n" |
| "version = \"0.1.0\"\n" |
| "authors = [\"mark\"]\n" |
| "\n" |
| "[dependencies]\n" |
| "```" |
| |
| #: src/cargo/deps.md:48 |
| msgid "" |
| "The `name` field under `[package]` determines the name of the project. This " |
| "is used by `crates.io` if you publish the crate (more later). It is also the " |
| "name of the output binary when you compile." |
| msgstr "" |
| "`[package]` 下的 `name` 字段决定了项目的名称。如果你将 crate 发布到 " |
| "`crates.io`（稍后会详细介绍），这个名称将被使用。同时，它也是编译时生成的二进" |
| "制文件的名称。" |
| |
| #: src/cargo/deps.md:52 |
| msgid "" |
| "The `version` field is a crate version number using [Semantic Versioning]" |
| "(http://semver.org/)." |
| msgstr "" |
| "`version` 字段是使用[语义化版本控制](http://semver.org/)的 crate 版本号。" |
| |
| #: src/cargo/deps.md:55 |
| msgid "" |
| "The `authors` field is a list of authors used when publishing the crate." |
| msgstr "`authors` 字段是发布 crate 时使用的作者列表。" |
| |
| #: src/cargo/deps.md:57 |
| msgid "" |
| "The `[dependencies]` section lets you add dependencies for your project." |
| msgstr "`[dependencies]` 部分允许你为项目添加依赖。" |
| |
| #: src/cargo/deps.md:59 |
| msgid "" |
| "For example, suppose that we want our program to have a great CLI. You can " |
| "find lots of great packages on [crates.io](https://crates.io) (the official " |
| "Rust package registry). One popular choice is [clap](https://crates.io/" |
| "crates/clap). As of this writing, the most recent published version of " |
| "`clap` is `2.27.1`. To add a dependency to our program, we can simply add " |
| "the following to our `Cargo.toml` under `[dependencies]`: `clap = " |
| "\"2.27.1\"`. And that's it! You can start using `clap` in your program." |
| msgstr "" |
| "举个例子，假设我们想让程序拥有一个出色的命令行界面（CLI）。你可以在 " |
| "[crates.io](https://crates.io)（Rust 官方包注册中心）上找到许多优秀的包。其" |
| "中，[clap](https://crates.io/crates/clap) 是一个广受欢迎的选择。在撰写本文" |
| "时，`clap` 的最新发布版本是 `2.27.1`。要在我们的程序中添加这个依赖，只需在 " |
| "`Cargo.toml` 的 `[dependencies]` 下添加：`clap = \"2.27.1\"`。就这么简单！现" |
| "在你就可以在程序中使用 `clap` 了。" |
| |
| #: src/cargo/deps.md:67 |
| msgid "" |
| "`cargo` also supports [other types of dependencies](https://doc.rust-" |
| "lang.org/cargo/reference/specifying-dependencies.html). Here is just a small " |
| "sampling:" |
| msgstr "" |
| "`cargo` 还支持[其他类型的依赖](https://doc.rust-lang.org/cargo/reference/" |
| "specifying-dependencies.html)。这里给出一个简单的示例：" |
| |
| #: src/cargo/deps.md:70 |
| msgid "" |
| "```toml\n" |
| "[package]\n" |
| "name = \"foo\"\n" |
| "version = \"0.1.0\"\n" |
| "authors = [\"mark\"]\n" |
| "\n" |
| "[dependencies]\n" |
| "clap = \"2.27.1\" # from crates.io\n" |
| "rand = { git = \"https://github.com/rust-lang-nursery/rand\" } # from online " |
| "repo\n" |
| "bar = { path = \"../bar\" } # from a path in the local filesystem\n" |
| "```" |
| msgstr "" |
| "```toml\n" |
| "[package]\n" |
| "name = \"foo\"\n" |
| "version = \"0.1.0\"\n" |
| "authors = [\"mark\"]\n" |
| "\n" |
| "[dependencies]\n" |
| "clap = \"2.27.1\" # 来自 crates.io\n" |
| "rand = { git = \"https://github.com/rust-lang-nursery/rand\" } # 来自在线仓" |
| "库\n" |
| "bar = { path = \"../bar\" } # 来自本地文件系统的路径\n" |
| "```" |
| |
| #: src/cargo/deps.md:82 |
| msgid "" |
| "`cargo` is more than a dependency manager. All of the available " |
| "configuration options are listed in the [format specification](https://" |
| "doc.rust-lang.org/cargo/reference/manifest.html) of `Cargo.toml`." |
| msgstr "" |
| "`cargo` 不仅仅是一个依赖管理器。`Cargo.toml` 的[格式规范](https://doc.rust-" |
| "lang.org/cargo/reference/manifest.html)中列出了所有可用的配置选项。" |
| |
| #: src/cargo/deps.md:86 |
| msgid "" |
| "To build our project we can execute `cargo build` anywhere in the project " |
| "directory (including subdirectories!). We can also do `cargo run` to build " |
| "and run. Notice that these commands will resolve all dependencies, download " |
| "crates if needed, and build everything, including your crate. (Note that it " |
| "only rebuilds what it has not already built, similar to `make`)." |
| msgstr "" |
| "我们可以在项目目录的任何位置（包括子目录！）执行 `cargo build` 来构建项目。也" |
| "可以使用 `cargo run` 来构建并运行。请注意，这些命令会解析所有依赖，必要时下" |
| "载 crate，并构建所有内容，包括你的 crate。（值得一提的是，它只会重新构建尚未" |
| "构建的部分，类似于 `make`）。" |
| |
| #: src/cargo/deps.md:92 |
| msgid "Voila! That's all there is to it!" |
| msgstr "瞧！就是这么简单！" |
| |
| #: src/cargo/conventions.md:3 |
| msgid "In the previous chapter, we saw the following directory hierarchy:" |
| msgstr "在上一章中，我们看到了如下目录结构：" |
| |
| #: src/cargo/conventions.md:12 |
| msgid "" |
| "Suppose that we wanted to have two binaries in the same project, though. " |
| "What then?" |
| msgstr "那么，如果我们想在同一个项目中包含两个二进制文件，该怎么办呢？" |
| |
| #: src/cargo/conventions.md:15 |
| msgid "" |
| "It turns out that `cargo` supports this. The default binary name is `main`, " |
| "as we saw before, but you can add additional binaries by placing them in a " |
| "`bin/` directory:" |
| msgstr "" |
| "`cargo` 实际上支持这种需求。如我们之前所见，默认的二进制文件名是 `main`，但你" |
| "可以通过在 `bin/` 目录中放置额外的文件来添加其他二进制文件：" |
| |
| #: src/cargo/conventions.md:28 |
| msgid "" |
| "To tell `cargo` to only compile or run this binary, we just pass `cargo` the " |
| "`--bin my_other_bin` flag, where `my_other_bin` is the name of the binary we " |
| "want to work with." |
| msgstr "" |
| "如果要指示 `cargo` 只编译或运行特定的二进制文件，只需传递 `--bin " |
| "my_other_bin` 标志，其中 `my_other_bin` 是我们想要处理的二进制文件的名称。" |
| |
| #: src/cargo/conventions.md:32 |
| msgid "" |
| "In addition to extra binaries, `cargo` supports [more features](https://" |
| "doc.rust-lang.org/cargo/guide/project-layout.html) such as benchmarks, " |
| "tests, and examples." |
| msgstr "" |
| "除了额外的二进制文件，`cargo` 还支持[更多功能](https://doc.rust-lang.org/" |
| "cargo/guide/project-layout.html)，如基准测试、测试和示例。" |
| |
| #: src/cargo/conventions.md:35 |
| msgid "In the next chapter, we will look more closely at tests." |
| msgstr "在下一章中，我们将更详细地探讨测试。" |
| |
| #: src/cargo/test.md:3 |
| msgid "" |
| "As we know testing is integral to any piece of software! Rust has first-" |
| "class support for unit and integration testing ([see this chapter](https://" |
| "doc.rust-lang.org/book/ch11-00-testing.html) in TRPL)." |
| msgstr "" |
| "众所周知，测试是任何软件不可或缺的一部分！Rust 为单元测试和集成测试提供了一流" |
| "的支持（参见《Rust 程序设计语言》中的[这一章](https://doc.rust-lang.org/book/" |
| "ch11-00-testing.html)）。" |
| |
| #: src/cargo/test.md:7 |
| msgid "" |
| "From the testing chapters linked above, we see how to write unit tests and " |
| "integration tests. Organizationally, we can place unit tests in the modules " |
| "they test and integration tests in their own `tests/` directory:" |
| msgstr "" |
| "从上面链接的测试章节中，我们了解了如何编写单元测试和集成测试。在组织结构上，" |
| "我们可以将单元测试放在它们所测试的模块中，而将集成测试放在专门的 `tests/` 目" |
| "录中：" |
| |
| #: src/cargo/test.md:22 |
| msgid "" |
| "Each file in `tests` is a separate [integration test](https://doc.rust-" |
| "lang.org/book/ch11-03-test-organization.html#integration-tests), i.e. a test " |
| "that is meant to test your library as if it were being called from a " |
| "dependent crate." |
| msgstr "" |
| "`tests` 目录中的每个文件都是一个独立的[集成测试](https://doc.rust-lang.org/" |
| "book/ch11-03-test-organization.html#integration-tests)，即旨在测试你的库，就" |
| "像它被依赖的 crate 调用一样。" |
| |
| #: src/cargo/test.md:27 |
| msgid "" |
| "The [Testing](../testing.md) chapter elaborates on the three different " |
| "testing styles: [Unit](../testing/unit_testing.md), [Doc](../testing/" |
| "doc_testing.md), and [Integration](../testing/integration_testing.md)." |
| msgstr "" |
| "[测试](../testing.md)章节详细阐述了三种不同的测试风格：[单元测试](../testing/" |
| "unit_testing.md)、[文档测试](../testing/doc_testing.md)和[集成测试](../" |
| "testing/integration_testing.md)。" |
| |
| #: src/cargo/test.md:30 |
| msgid "`cargo` naturally provides an easy way to run all of your tests!" |
| msgstr "`cargo` 自然提供了一种简便的方式来运行所有测试！" |
| |
| #: src/cargo/test.md:36 |
| msgid "You should see output like this:" |
| msgstr "你将看到类似这样的输出：" |
| |
| #: src/cargo/test.md:38 |
| msgid "" |
| "```shell\n" |
| "$ cargo test\n" |
| " Compiling blah v0.1.0 (file:///nobackup/blah)\n" |
| " Finished dev [unoptimized + debuginfo] target(s) in 0.89 secs\n" |
| " Running target/debug/deps/blah-d3b32b97275ec472\n" |
| "\n" |
| "running 4 tests\n" |
| "test test_bar ... ok\n" |
| "test test_baz ... ok\n" |
| "test test_foo_bar ... ok\n" |
| "test test_foo ... ok\n" |
| "\n" |
| "test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ cargo test\n" |
| " Compiling blah v0.1.0 (file:///nobackup/blah)\n" |
| " Finished dev [unoptimized + debuginfo] target(s) in 0.89 secs\n" |
| " Running target/debug/deps/blah-d3b32b97275ec472\n" |
| "\n" |
| "running 4 tests\n" |
| "test test_bar ... ok\n" |
| "test test_baz ... ok\n" |
| "test test_foo_bar ... ok\n" |
| "test test_foo ... ok\n" |
| "\n" |
| "test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out\n" |
| "```" |
| |
| #: src/cargo/test.md:53 |
| msgid "You can also run tests whose name matches a pattern:" |
| msgstr "你还可以运行名称匹配特定模式的测试：" |
| |
| #: src/cargo/test.md:59 |
| msgid "" |
| "```shell\n" |
| "$ cargo test test_foo\n" |
| " Compiling blah v0.1.0 (file:///nobackup/blah)\n" |
| " Finished dev [unoptimized + debuginfo] target(s) in 0.35 secs\n" |
| " Running target/debug/deps/blah-d3b32b97275ec472\n" |
| "\n" |
| "running 2 tests\n" |
| "test test_foo ... ok\n" |
| "test test_foo_bar ... ok\n" |
| "\n" |
| "test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 2 filtered out\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ cargo test test_foo\n" |
| " Compiling blah v0.1.0 (file:///nobackup/blah)\n" |
| " Finished dev [unoptimized + debuginfo] target(s) in 0.35 secs\n" |
| " Running target/debug/deps/blah-d3b32b97275ec472\n" |
| "\n" |
| "running 2 tests\n" |
| "test test_foo ... ok\n" |
| "test test_foo_bar ... ok\n" |
| "\n" |
| "test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 2 filtered out\n" |
| "```" |
| |
| #: src/cargo/test.md:72 |
| msgid "" |
| "One word of caution: Cargo may run multiple tests concurrently, so make sure " |
| "that they don't race with each other." |
| msgstr "" |
| "需要注意：Cargo 可能会并发运行多个测试，因此请确保它们之间不会产生竞态条件。" |
| |
| #: src/cargo/test.md:75 |
| msgid "" |
| "One example of this concurrency causing issues is if two tests output to a " |
| "file, such as below:" |
| msgstr "" |
| "并发可能导致问题的一个例子是，如果两个测试同时输出到同一个文件，如下所示：" |
| |
| #: src/cargo/test.md:81 |
| msgid "// Import the necessary modules\n" |
| msgstr "// 导入必要的模块\n" |
| |
| #: src/cargo/test.md:85 |
| msgid "// This test writes to a file\n" |
| msgstr "// 这个测试向文件写入内容\n" |
| |
| #: src/cargo/test.md:88 src/cargo/test.md:105 |
| msgid "// Opens the file ferris.txt or creates one if it doesn't exist.\n" |
| msgstr "// 打开 ferris.txt 文件，如果不存在则创建一个\n" |
| |
| #: src/cargo/test.md:92 src/cargo/test.md:109 |
| msgid "\"ferris.txt\"" |
| msgstr "\"ferris.txt\"" |
| |
| #: src/cargo/test.md:93 src/cargo/test.md:110 |
| msgid "\"Failed to open ferris.txt\"" |
| msgstr "\"无法打开 ferris.txt\"" |
| |
| #: src/cargo/test.md:95 |
| msgid "// Print \"Ferris\" 5 times.\n" |
| msgstr "// 循环打印 \"Ferris\" 5 次\n" |
| |
| #: src/cargo/test.md:97 |
| msgid "\"Ferris\\n\"" |
| msgstr "\"Ferris\\n\"" |
| |
| #: src/cargo/test.md:98 src/cargo/test.md:115 |
| msgid "\"Could not write to ferris.txt\"" |
| msgstr "\"无法写入 ferris.txt\"" |
| |
| #: src/cargo/test.md:102 |
| msgid "// This test tries to write to the same file\n" |
| msgstr "// 这个测试尝试写入同一个文件\n" |
| |
| #: src/cargo/test.md:112 |
| msgid "// Print \"Corro\" 5 times.\n" |
| msgstr "// 循环打印 \"Corro\" 5 次\n" |
| |
| #: src/cargo/test.md:114 |
| msgid "\"Corro\\n\"" |
| msgstr "\"Corro\\n\"" |
| |
| #: src/cargo/test.md:121 |
| msgid "Although the intent is to get the following:" |
| msgstr "尽管预期结果应该是：" |
| |
| #: src/cargo/test.md:137 |
| msgid "What actually gets put into `ferris.txt` is this:" |
| msgstr "但实际写入 `ferris.txt` 的内容可能是这样的：" |
| |
| #: src/cargo/build_scripts.md:3 |
| msgid "" |
| "Sometimes a normal build from `cargo` is not enough. Perhaps your crate " |
| "needs some pre-requisites before `cargo` will successfully compile, things " |
| "like code generation, or some native code that needs to be compiled. To " |
| "solve this problem we have build scripts that Cargo can run." |
| msgstr "" |
| "有时候，`cargo` 的常规构建可能不足以满足需求。你的 crate 可能在 `cargo` 成功" |
| "编译之前需要一些先决条件，比如代码生成，或者需要编译一些本地代码。为了解决这" |
| "个问题，我们可以使用 Cargo 能够运行的构建脚本。" |
| |
| #: src/cargo/build_scripts.md:8 |
| msgid "" |
| "To add a build script to your package it can either be specified in the " |
| "`Cargo.toml` as follows:" |
| msgstr "要为你的包添加构建脚本，可以在 `Cargo.toml` 中指定，如下所示：" |
| |
| #: src/cargo/build_scripts.md:11 |
| msgid "" |
| "```toml\n" |
| "[package]\n" |
| "...\n" |
| "build = \"build.rs\"\n" |
| "```" |
| msgstr "" |
| "```toml\n" |
| "[package]\n" |
| "...\n" |
| "build = \"build.rs\"\n" |
| "```" |
| |
| #: src/cargo/build_scripts.md:17 |
| msgid "" |
| "Otherwise Cargo will look for a `build.rs` file in the project directory by " |
| "default." |
| msgstr "如果没有指定，Cargo 默认会在项目目录中查找 `build.rs` 文件。" |
| |
| #: src/cargo/build_scripts.md:20 |
| msgid "How to use a build script" |
| msgstr "如何使用构建脚本" |
| |
| #: src/cargo/build_scripts.md:22 |
| msgid "" |
| "The build script is simply another Rust file that will be compiled and " |
| "invoked prior to compiling anything else in the package. Hence it can be " |
| "used to fulfill pre-requisites of your crate." |
| msgstr "" |
| "构建脚本只是另一个 Rust 文件，它会在编译包中的其他内容之前被编译和调用。因" |
| "此，它可以用来满足你的 crate 的先决条件。" |
| |
| #: src/cargo/build_scripts.md:26 |
| msgid "" |
| "Cargo provides the script with inputs via environment variables [specified " |
| "here](https://doc.rust-lang.org/cargo/reference/environment-" |
| "variables.html#environment-variables-cargo-sets-for-build-scripts) that can " |
| "be used." |
| msgstr "" |
| "Cargo 通过环境变量为脚本提供输入，这些环境变量可以被使用。具体参见[这里的说" |
| "明](https://doc.rust-lang.org/cargo/reference/environment-" |
| "variables.html#environment-variables-cargo-sets-for-build-scripts)。" |
| |
| #: src/cargo/build_scripts.md:29 |
| msgid "" |
| "The script provides output via stdout. All lines printed are written to " |
| "`target/debug/build/<pkg>/output`. Further, lines prefixed with `cargo:` " |
| "will be interpreted by Cargo directly and hence can be used to define " |
| "parameters for the package's compilation." |
| msgstr "" |
| "脚本通过标准输出提供输出。所有打印的行都会被写入 `target/debug/build/<pkg>/" |
| "output`。此外，以 `cargo:` 为前缀的行会被 Cargo 直接解释，因此可以用来为包的" |
| "编译定义参数。" |
| |
| #: src/cargo/build_scripts.md:34 |
| msgid "" |
| "For further specification and examples have a read of the [Cargo " |
| "specification](https://doc.rust-lang.org/cargo/reference/build-scripts.html)." |
| msgstr "" |
| "如需了解更多详细规范和示例，请参阅 [Cargo 构建脚本规范](https://doc.rust-" |
| "lang.org/cargo/reference/build-scripts.html)。" |
| |
| #: src/attribute.md:3 |
| msgid "" |
| "An attribute is metadata applied to some module, crate or item. This " |
| "metadata can be used to/for:" |
| msgstr "属性是应用于模块、crate 或条目的元数据。这些元数据可用于以下目的：" |
| |
| #: src/attribute.md:8 |
| msgid "[conditional compilation of code](attribute/cfg.md)" |
| msgstr "[代码的条件编译](attribute/cfg.md)" |
| |
| #: src/attribute.md:9 |
| msgid "" |
| "[set crate name, version and type (binary or library)](attribute/crate.md)" |
| msgstr "[设置 crate 的名称、版本和类型（二进制或库）](attribute/crate.md)" |
| |
| #: src/attribute.md:10 |
| msgid "" |
| "disable [lints](https://en.wikipedia.org/wiki/Lint_%28software%29) (warnings)" |
| msgstr "" |
| "禁用 [代码检查](https://en.wikipedia.org/wiki/Lint_%28software%29)（警告）" |
| |
| #: src/attribute.md:11 |
| msgid "enable compiler features (macros, glob imports, etc.)" |
| msgstr "启用编译器特性（如宏、全局导入等）" |
| |
| #: src/attribute.md:12 |
| msgid "link to a foreign library" |
| msgstr "链接外部库" |
| |
| #: src/attribute.md:13 |
| msgid "mark functions as unit tests" |
| msgstr "将函数标记为单元测试" |
| |
| #: src/attribute.md:14 |
| msgid "mark functions that will be part of a benchmark" |
| msgstr "将函数标记为基准测试的一部分" |
| |
| #: src/attribute.md:15 |
| msgid "" |
| "[attribute like macros](https://doc.rust-lang.org/book/ch19-06-" |
| "macros.html#attribute-like-macros)" |
| msgstr "" |
| "[类属性宏](https://doc.rust-lang.org/book/ch19-06-macros.html#attribute-like-" |
| "macros)" |
| |
| #: src/attribute.md:17 |
| msgid "" |
| "Attributes look like `#[outer_attribute]` or `#![inner_attribute]`, with the " |
| "difference between them being where they apply." |
| msgstr "" |
| "属性的形式为 `#[outer_attribute]`（外部属性）或 `#![inner_attribute]`（内部属" |
| "性），它们的区别在于应用的位置。" |
| |
| #: src/attribute.md:20 |
| msgid "" |
| "`#[outer_attribute]` applies to the [item](https://doc.rust-lang.org/stable/" |
| "reference/items.html) immediately following it. Some examples of items are: " |
| "a function, a module declaration, a constant, a structure, an enum. Here is " |
| "an example where attribute `#[derive(Debug)]` applies to the struct " |
| "`Rectangle`:" |
| msgstr "" |
| "`#[outer_attribute]` 应用于紧随其后的[条目](https://doc.rust-lang.org/stable/" |
| "reference/items.html)。条目的例子包括：函数、模块声明、常量、结构体、枚举等。" |
| "以下是一个示例，其中属性 `#[derive(Debug)]` 应用于结构体 `Rectangle`：" |
| |
| #: src/attribute.md:34 |
| msgid "" |
| "`#![inner_attribute]` applies to the enclosing [item](https://doc.rust-" |
| "lang.org/stable/reference/items.html) (typically a module or a crate). In " |
| "other words, this attribute is interpreted as applying to the entire scope " |
| "in which it's placed. Here is an example where `#![allow(unused_variables)]` " |
| "applies to the whole crate (if placed in `main.rs`):" |
| msgstr "" |
| "`#![inner_attribute]` 应用于包含它的[条目](https://doc.rust-lang.org/stable/" |
| "reference/items.html)（通常是模块或 crate）。换句话说，这种属性被解释为应用于" |
| "它所在的整个作用域。以下是一个示例，其中 `#![allow(unused_variables)]` 应用于" |
| "整个 crate（如果放置在 `main.rs` 中）：" |
| |
| #: src/attribute.md:44 |
| msgid "// This would normally warn about an unused variable.\n" |
| msgstr "// 这通常会警告未使用的变量。\n" |
| |
| #: src/attribute.md:48 |
| msgid "Attributes can take arguments with different syntaxes:" |
| msgstr "属性可以使用不同的语法接受参数：" |
| |
| #: src/attribute.md:50 |
| msgid "`#[attribute = \"value\"]`" |
| msgstr "`#[attribute = \"value\"]`" |
| |
| #: src/attribute.md:51 |
| msgid "`#[attribute(key = \"value\")]`" |
| msgstr "`#[attribute(key = \"value\")]`" |
| |
| #: src/attribute.md:52 |
| msgid "`#[attribute(value)]`" |
| msgstr "`#[attribute(value)]`" |
| |
| #: src/attribute.md:54 |
| msgid "" |
| "Attributes can have multiple values and can be separated over multiple " |
| "lines, too:" |
| msgstr "属性可以有多个值，也可以跨多行分隔：" |
| |
| #: src/attribute/unused.md:3 |
| msgid "" |
| "The compiler provides a `dead_code` [_lint_](https://en.wikipedia.org/wiki/" |
| "Lint_%28software%29) that will warn about unused functions. An _attribute_ " |
| "can be used to disable the lint." |
| msgstr "" |
| "编译器提供了一个 `dead_code` [lint](https://en.wikipedia.org/wiki/" |
| "Lint_%28software%29)，用于警告未使用的函数。可以使用**属性**来禁用这个 lint。" |
| |
| #: src/attribute/unused.md:9 |
| msgid "" |
| "// `#[allow(dead_code)]` is an attribute that disables the `dead_code` lint\n" |
| msgstr "// `#[allow(dead_code)]` 是一个用于禁用 `dead_code` lint 的属性\n" |
| |
| #: src/attribute/unused.md:14 |
| msgid "// FIXME ^ Add an attribute to suppress the warning\n" |
| msgstr "// FIXME ^ 添加一个属性来抑制警告\n" |
| |
| #: src/attribute/unused.md:22 |
| msgid "" |
| "Note that in real programs, you should eliminate dead code. In these " |
| "examples we'll allow dead code in some places because of the interactive " |
| "nature of the examples." |
| msgstr "" |
| "注意，在实际程序中，你应该消除无用代码。在这些示例中，我们会在某些地方允许存" |
| "在无用代码，这是因为这些示例具有交互性质。" |
| |
| #: src/attribute/crate.md:3 |
| msgid "" |
| "The `crate_type` attribute can be used to tell the compiler whether a crate " |
| "is a binary or a library (and even which type of library), and the " |
| "`crate_name` attribute can be used to set the name of the crate." |
| msgstr "" |
| "`crate_type` 属性可用于告诉编译器一个 crate 是二进制文件还是库（甚至是哪种类" |
| "型的库），而 `crate_name` 属性可用于设置 crate 的名称。" |
| |
| #: src/attribute/crate.md:7 |
| msgid "" |
| "However, it is important to note that both the `crate_type` and `crate_name` " |
| "attributes have **no** effect whatsoever when using Cargo, the Rust package " |
| "manager. Since Cargo is used for the majority of Rust projects, this means " |
| "real-world uses of `crate_type` and `crate_name` are relatively limited." |
| msgstr "" |
| "然而，需要注意的是，当使用 Rust 的包管理器 Cargo 时，`crate_type` 和 " |
| "`crate_name` 属性**完全不起作用**。由于大多数 Rust 项目都使用 Cargo，这意味" |
| "着 `crate_type` 和 `crate_name` 在实际使用中的应用相对有限。" |
| |
| #: src/attribute/crate.md:13 |
| msgid "// This crate is a library\n" |
| msgstr "// 这个 crate 是一个库\n" |
| |
| #: src/attribute/crate.md:14 |
| msgid "\"lib\"" |
| msgstr "\"lib\"" |
| |
| #: src/attribute/crate.md:14 |
| msgid "// The library is named \"rary\"\n" |
| msgstr "// 这个库的名称是 \"rary\"\n" |
| |
| #: src/attribute/crate.md:16 |
| msgid "\"rary\"" |
| msgstr "\"rary\"" |
| |
| #: src/attribute/crate.md:33 |
| msgid "" |
| "When the `crate_type` attribute is used, we no longer need to pass the `--" |
| "crate-type` flag to `rustc`." |
| msgstr "" |
| "当使用 `crate_type` 属性时，我们就不再需要向 `rustc` 传递 `--crate-type` 标" |
| "志。" |
| |
| #: src/attribute/cfg.md:3 |
| msgid "" |
| "Configuration conditional checks are possible through two different " |
| "operators:" |
| msgstr "配置条件检查可以通过两种不同的操作符实现：" |
| |
| #: src/attribute/cfg.md:5 |
| msgid "the `cfg` attribute: `#[cfg(...)]` in attribute position" |
| msgstr "`cfg` 属性：在属性位置使用 `#[cfg(...)]`" |
| |
| #: src/attribute/cfg.md:6 |
| msgid "the `cfg!` macro: `cfg!(...)` in boolean expressions" |
| msgstr "`cfg!` 宏：在布尔表达式中使用 `cfg!(...)`" |
| |
| #: src/attribute/cfg.md:8 |
| msgid "" |
| "While the former enables conditional compilation, the latter conditionally " |
| "evaluates to `true` or `false` literals allowing for checks at run-time. " |
| "Both utilize identical argument syntax." |
| msgstr "" |
| "前者启用条件编译，后者在运行时条件性地求值为 `true` 或 `false` 字面量，允许在" |
| "运行时进行检查。两者使用相同的参数语法。" |
| |
| #: src/attribute/cfg.md:12 |
| msgid "" |
| "`cfg!`, unlike `#[cfg]`, does not remove any code and only evaluates to true " |
| "or false. For example, all blocks in an if/else expression need to be valid " |
| "when `cfg!` is used for the condition, regardless of what `cfg!` is " |
| "evaluating." |
| msgstr "" |
| "`cfg!` 与 `#[cfg]` 不同，它不会移除任何代码，只会求值为 true 或 false。例如，" |
| "当 `cfg!` 用于条件时，if/else 表达式中的所有代码块都需要是有效的，无论 `cfg!" |
| "` 正在评估什么。" |
| |
| #: src/attribute/cfg.md:15 |
| msgid "// This function only gets compiled if the target OS is linux\n" |
| msgstr "// 这个函数只有在目标操作系统是 linux 时才会被编译\n" |
| |
| #: src/attribute/cfg.md:16 src/attribute/cfg.md:22 src/attribute/cfg.md:31 |
| msgid "\"linux\"" |
| msgstr "\"linux\"" |
| |
| #: src/attribute/cfg.md:18 |
| msgid "\"You are running linux!\"" |
| msgstr "\"你正在运行 Linux！\"" |
| |
| #: src/attribute/cfg.md:20 |
| msgid "" |
| "// And this function only gets compiled if the target OS is *not* linux\n" |
| msgstr "// 而这个函数只有在目标操作系统**不是** Linux 时才会被编译\n" |
| |
| #: src/attribute/cfg.md:24 |
| msgid "\"You are *not* running linux!\"" |
| msgstr "\"你**不是**在运行 Linux！\"" |
| |
| #: src/attribute/cfg.md:30 |
| msgid "\"Are you sure?\"" |
| msgstr "\"你确定吗？\"" |
| |
| #: src/attribute/cfg.md:32 |
| msgid "\"Yes. It's definitely linux!\"" |
| msgstr "\"是的，这绝对是 Linux！\"" |
| |
| #: src/attribute/cfg.md:34 |
| msgid "\"Yes. It's definitely *not* linux!\"" |
| msgstr "\"是的，这绝对**不是** Linux！\"" |
| |
| #: src/attribute/cfg.md:41 |
| msgid "" |
| "[the reference](https://doc.rust-lang.org/reference/" |
| "attributes.html#conditional-compilation), [`cfg!`](https://doc.rust-lang.org/" |
| "std/macro.cfg!.html), and [macros](../macros.md)." |
| msgstr "" |
| "[参考文档](https://doc.rust-lang.org/reference/attributes.html#conditional-" |
| "compilation)、[`cfg!` 宏](https://doc.rust-lang.org/std/macro.cfg!.html)和" |
| "[宏](../macros.md)。" |
| |
| #: src/attribute/cfg/custom.md:3 |
| msgid "" |
| "Some conditionals like `target_os` are implicitly provided by `rustc`, but " |
| "custom conditionals must be passed to `rustc` using the `--cfg` flag." |
| msgstr "" |
| "一些条件（如 `target_os`）是由 `rustc` 隐式提供的，但自定义条件必须通过 `--" |
| "cfg` 标志传递给 `rustc`。" |
| |
| #: src/attribute/cfg/custom.md:9 |
| msgid "\"condition met!\"" |
| msgstr "\"条件满足！\"" |
| |
| #: src/attribute/cfg/custom.md:17 |
| msgid "Try to run this to see what happens without the custom `cfg` flag." |
| msgstr "尝试运行这段代码，看看没有自定义 `cfg` 标志会发生什么。" |
| |
| #: src/attribute/cfg/custom.md:19 |
| msgid "With the custom `cfg` flag:" |
| msgstr "使用自定义 `cfg` 标志：" |
| |
| #: src/generics.md:3 |
| msgid "" |
| "_Generics_ is the topic of generalizing types and functionalities to broader " |
| "cases. This is extremely useful for reducing code duplication in many ways, " |
| "but can call for rather involved syntax. Namely, being generic requires " |
| "taking great care to specify over which types a generic type is actually " |
| "considered valid. The simplest and most common use of generics is for type " |
| "parameters." |
| msgstr "" |
| "**泛型**是一个关于将类型和功能泛化以适用于更广泛情况的主题。这在多方面都非常" |
| "有用，可以大大减少代码重复，但可能需要相对复杂的语法。具体来说，使用泛型需要" |
| "非常谨慎地指定泛型类型在哪些类型上是有效的。泛型最简单和最常见的用途是类型参" |
| "数。" |
| |
| #: src/generics.md:10 |
| msgid "" |
| "A type parameter is specified as generic by the use of angle brackets and " |
| "upper [camel case](https://en.wikipedia.org/wiki/CamelCase): `<Aaa, " |
| "Bbb, ...>`. \"Generic type parameters\" are typically represented as `<T>`. " |
| "In Rust, \"generic\" also describes anything that accepts one or more " |
| "generic type parameters `<T>`. Any type specified as a generic type " |
| "parameter is generic, and everything else is concrete (non-generic)." |
| msgstr "" |
| "类型参数通过使用尖括号和大写[驼峰命名法](https://en.wikipedia.org/wiki/" |
| "CamelCase)来指定为泛型：`<Aaa, Bbb, ...>`。\"泛型类型参数\"通常表示为 `<T>`。" |
| "在 Rust 中，\"泛型\"也用来描述任何接受一个或多个泛型类型参数 `<T>` 的东西。任" |
| "何被指定为泛型类型参数的类型都是泛型的，而其他所有类型都是具体的（非泛型）。" |
| |
| #: src/generics.md:16 |
| msgid "" |
| "For example, defining a _generic function_ named `foo` that takes an " |
| "argument `T` of any type:" |
| msgstr "" |
| "例如，定义一个名为 `foo` 的**泛型函数**，它接受一个任意类型的参数 `T`：" |
| |
| #: src/generics.md:23 |
| msgid "" |
| "Because `T` has been specified as a generic type parameter using `<T>`, it " |
| "is considered generic when used here as `(arg: T)`. This is the case even if " |
| "`T` has previously been defined as a `struct`." |
| msgstr "" |
| "因为 `T` 已经使用 `<T>` 指定为泛型类型参数，所以在这里用作 `(arg: T)` 时被视" |
| "为泛型。即使 `T` 之前已被定义为一个 `struct`，这种情况也成立。" |
| |
| #: src/generics.md:27 |
| msgid "This example shows some of the syntax in action:" |
| msgstr "下面的例子展示了一些泛型语法的实际应用：" |
| |
| #: src/generics.md:30 |
| msgid "// A concrete type `A`.\n" |
| msgstr "// 具体类型 `A`\n" |
| |
| #: src/generics.md:32 |
| msgid "" |
| "// In defining the type `Single`, the first use of `A` is not preceded by " |
| "`<A>`.\n" |
| "// Therefore, `Single` is a concrete type, and `A` is defined as above.\n" |
| msgstr "" |
| "// 定义 `Single` 类型时，首次使用 `A` 前没有 `<A>`\n" |
| "// 因此，`Single` 是具体类型，`A` 即上面定义的类型\n" |
| |
| #: src/generics.md:35 |
| msgid "// ^ Here is `Single`s first use of the type `A`.\n" |
| msgstr "// ^ 这里是 `Single` 首次使用 `A` 类型\n" |
| |
| #: src/generics.md:37 |
| msgid "" |
| "// Here, `<T>` precedes the first use of `T`, so `SingleGen` is a generic " |
| "type.\n" |
| "// Because the type parameter `T` is generic, it could be anything, " |
| "including\n" |
| "// the concrete type `A` defined at the top.\n" |
| msgstr "" |
| "// 这里 `<T>` 在首次使用 `T` 之前，所以 `SingleGen` 是泛型\n" |
| "// 由于类型参数 `T` 是泛型，它可以是任何类型\n" |
| "// 包括上面定义的具体类型 `A`\n" |
| |
| #: src/generics.md:44 |
| msgid "// `Single` is concrete and explicitly takes `A`.\n" |
| msgstr "// `Single` 是具体类型，明确接受 `A`\n" |
| |
| #: src/generics.md:47 |
| msgid "" |
| "// Create a variable `_char` of type `SingleGen<char>`\n" |
| " // and give it the value `SingleGen('a')`.\n" |
| " // Here, `SingleGen` has a type parameter explicitly specified.\n" |
| msgstr "" |
| "// 创建 `SingleGen<char>` 类型的变量 `_char`\n" |
| " // 并赋值为 `SingleGen('a')`\n" |
| " // 这里 `SingleGen` 明确指定了类型参数\n" |
| |
| #: src/generics.md:52 |
| msgid "// `SingleGen` can also have a type parameter implicitly specified:\n" |
| msgstr "// `SingleGen` 也可以隐式指定类型参数：\n" |
| |
| #: src/generics.md:53 |
| msgid "// Uses `A` defined at the top.\n" |
| msgstr "// 使用上面定义的 `A`\n" |
| |
| #: src/generics.md:54 |
| msgid "// Uses `i32`.\n" |
| msgstr "// 使用 `i32`\n" |
| |
| #: src/generics.md:55 |
| msgid "// Uses `char`.\n" |
| msgstr "// 使用 `char`\n" |
| |
| #: src/generics.md:61 |
| msgid "[`structs`](custom_types/structs.md)" |
| msgstr "[`结构体`](custom_types/structs.md)" |
| |
| #: src/generics/gen_fn.md:3 |
| msgid "" |
| "The same set of rules can be applied to functions: a type `T` becomes " |
| "generic when preceded by `<T>`." |
| msgstr "同样的规则也适用于函数：当类型 `T` 前面加上 `<T>` 时，它就变成了泛型。" |
| |
| #: src/generics/gen_fn.md:6 |
| msgid "" |
| "Using generic functions sometimes requires explicitly specifying type " |
| "parameters. This may be the case if the function is called where the return " |
| "type is generic, or if the compiler doesn't have enough information to infer " |
| "the necessary type parameters." |
| msgstr "" |
| "使用泛型函数有时需要明确指定类型参数。这种情况可能出现在函数返回类型是泛型" |
| "时，或者编译器没有足够信息推断必要的类型参数时。" |
| |
| #: src/generics/gen_fn.md:11 |
| msgid "" |
| "A function call with explicitly specified type parameters looks like: `fun::" |
| "<A, B, ...>()`." |
| msgstr "明确指定类型参数的函数调用看起来像这样：`fun::<A, B, ...>()`。" |
| |
| #: src/generics/gen_fn.md:15 |
| msgid "// Concrete type `A`.\n" |
| msgstr "// 具体类型 `A`\n" |
| |
| #: src/generics/gen_fn.md:16 |
| msgid "// Concrete type `S`.\n" |
| msgstr "// 具体类型 `S`\n" |
| |
| #: src/generics/gen_fn.md:17 |
| msgid "// Generic type `SGen`.\n" |
| msgstr "// 泛型 `SGen`\n" |
| |
| #: src/generics/gen_fn.md:18 |
| msgid "" |
| "// The following functions all take ownership of the variable passed into\n" |
| "// them and immediately go out of scope, freeing the variable.\n" |
| msgstr "" |
| "// 以下函数都获取传入变量的所有权\n" |
| "// 并立即离开作用域，释放该变量\n" |
| |
| #: src/generics/gen_fn.md:21 |
| msgid "" |
| "// Define a function `reg_fn` that takes an argument `_s` of type `S`.\n" |
| "// This has no `<T>` so this is not a generic function.\n" |
| msgstr "" |
| "// 定义函数 `reg_fn`，接受一个 `S` 类型的参数 `_s`\n" |
| "// 由于没有 `<T>`，所以这不是泛型函数\n" |
| |
| #: src/generics/gen_fn.md:25 |
| msgid "" |
| "// Define a function `gen_spec_t` that takes an argument `_s` of type " |
| "`SGen<T>`.\n" |
| "// It has been explicitly given the type parameter `A`, but because `A` has " |
| "not \n" |
| "// been specified as a generic type parameter for `gen_spec_t`, it is not " |
| "generic.\n" |
| msgstr "" |
| "// 定义函数 `gen_spec_t`，接受一个 `SGen<T>` 类型的参数 `_s`\n" |
| "// 虽然明确给定了类型参数 `A`，但因为 `A` 并未被指定为\n" |
| "// `gen_spec_t` 的泛型类型参数，所以这个函数不是泛型的\n" |
| |
| #: src/generics/gen_fn.md:30 |
| msgid "" |
| "// Define a function `gen_spec_i32` that takes an argument `_s` of type " |
| "`SGen<i32>`.\n" |
| "// It has been explicitly given the type parameter `i32`, which is a " |
| "specific type.\n" |
| "// Because `i32` is not a generic type, this function is also not generic.\n" |
| msgstr "" |
| "// 定义函数 `gen_spec_i32`，接受一个 `SGen<i32>` 类型的参数 `_s`\n" |
| "// 明确指定了类型参数 `i32`，这是一个具体类型\n" |
| "// 由于 `i32` 不是泛型类型，所以这个函数也不是泛型的\n" |
| |
| #: src/generics/gen_fn.md:35 |
| msgid "" |
| "// Define a function `generic` that takes an argument `_s` of type " |
| "`SGen<T>`.\n" |
| "// Because `SGen<T>` is preceded by `<T>`, this function is generic over " |
| "`T`.\n" |
| msgstr "" |
| "// 定义函数 `generic`，接受一个 `SGen<T>` 类型的参数 `_s`\n" |
| "// 由于 `SGen<T>` 前面有 `<T>`，所以这个函数是关于 `T` 的泛型函数\n" |
| |
| #: src/generics/gen_fn.md:41 |
| msgid "// Using the non-generic functions\n" |
| msgstr "// 使用非泛型函数\n" |
| |
| #: src/generics/gen_fn.md:42 |
| msgid "// Concrete type.\n" |
| msgstr "// 具体类型\n" |
| |
| #: src/generics/gen_fn.md:43 |
| msgid "// Implicitly specified type parameter `A`.\n" |
| msgstr "// 隐式指定类型参数 `A`\n" |
| |
| #: src/generics/gen_fn.md:44 |
| msgid "// Implicitly specified type parameter `i32`.\n" |
| msgstr "// 隐式指定类型参数 `i32`\n" |
| |
| #: src/generics/gen_fn.md:46 |
| msgid "// Explicitly specified type parameter `char` to `generic()`.\n" |
| msgstr "// 为 `generic()` 显式指定类型参数 `char`\n" |
| |
| #: src/generics/gen_fn.md:49 |
| msgid "// Implicitly specified type parameter `char` to `generic()`.\n" |
| msgstr "// 为 `generic()` 隐式指定类型参数 `char`\n" |
| |
| #: src/generics/gen_fn.md:50 |
| msgid "'c'" |
| msgstr "'c'" |
| |
| #: src/generics/gen_fn.md:56 |
| msgid "[functions](../fn.md) and [`struct`s](../custom_types/structs.md)" |
| msgstr "[函数](../fn.md)和[`结构体`](../custom_types/structs.md)" |
| |
| #: src/generics/impl.md:3 |
| msgid "Similar to functions, implementations require care to remain generic." |
| msgstr "与函数类似，实现（`impl`）在涉及泛型时也需要谨慎处理。" |
| |
| #: src/generics/impl.md:6 |
| msgid "// Concrete type `S`\n" |
| msgstr "// 具体类型 `S`\n" |
| |
| #: src/generics/impl.md:7 |
| msgid "// Generic type `GenericVal`\n" |
| msgstr "// 泛型类型 `GenericVal`\n" |
| |
| #: src/generics/impl.md:8 |
| msgid "// impl of GenericVal where we explicitly specify type parameters:\n" |
| msgstr "// GenericVal 的实现，这里我们显式指定类型参数：\n" |
| |
| #: src/generics/impl.md:10 |
| msgid "// Specify `f32`\n" |
| msgstr "// 指定 `f32`\n" |
| |
| #: src/generics/impl.md:11 |
| msgid "// Specify `S` as defined above\n" |
| msgstr "// 指定上面定义的 `S`\n" |
| |
| #: src/generics/impl.md:12 |
| msgid "// `<T>` Must precede the type to remain generic\n" |
| msgstr "// `<T>` 必须放在类型前面以保持泛型\n" |
| |
| #: src/generics/impl.md:25 |
| msgid "// impl of Val\n" |
| msgstr "// Val 的实现\n" |
| |
| #: src/generics/impl.md:32 |
| msgid "// impl of GenVal for a generic type `T`\n" |
| msgstr "// 为泛型类型 `T` 实现 GenVal\n" |
| |
| #: src/generics/impl.md:50 |
| msgid "" |
| "[functions returning references](../scope/lifetime/fn.md), [`impl`](../fn/" |
| "methods.md), and [`struct`](../custom_types/structs.md)" |
| msgstr "" |
| "[返回引用的函数](../scope/lifetime/fn.md)、[`impl`](../fn/methods.md) 和[结构" |
| "体](../custom_types/structs.md)" |
| |
| #: src/generics/gen_trait.md:3 |
| msgid "" |
| "Of course `trait`s can also be generic. Here we define one which " |
| "reimplements the `Drop` `trait` as a generic method to `drop` itself and an " |
| "input." |
| msgstr "" |
| "当然，`trait` 也可以是泛型的。这里我们定义了一个泛型 trait，它重新实现了 " |
| "`Drop` trait，用于释放自身和一个输入参数。" |
| |
| #: src/generics/gen_trait.md:7 |
| msgid "// Non-copyable types.\n" |
| msgstr "// 不可复制的类型。\n" |
| |
| #: src/generics/gen_trait.md:10 |
| msgid "// A trait generic over `T`.\n" |
| msgstr "// 一个泛型 trait，使用类型参数 `T`。\n" |
| |
| #: src/generics/gen_trait.md:13 |
| msgid "" |
| "// Define a method on the caller type which takes an\n" |
| " // additional single parameter `T` and does nothing with it.\n" |
| msgstr "" |
| "// 在调用者类型上定义一个方法，该方法接受一个\n" |
| " // 额外的类型为 `T` 的参数，但不对其进行任何操作。\n" |
| |
| #: src/generics/gen_trait.md:17 |
| msgid "" |
| "// Implement `DoubleDrop<T>` for any generic parameter `T` and\n" |
| "// caller `U`.\n" |
| msgstr "// 为任意泛型参数 `T` 和调用者 `U` 实现 `DoubleDrop<T>`。\n" |
| |
| #: src/generics/gen_trait.md:21 |
| msgid "" |
| "// This method takes ownership of both passed arguments,\n" |
| " // deallocating both.\n" |
| msgstr "" |
| "// 此方法获取两个传入参数的所有权，\n" |
| " // 并释放它们的内存。\n" |
| |
| #: src/generics/gen_trait.md:30 |
| msgid "// Deallocate `empty` and `null`.\n" |
| msgstr "// 释放 `empty` 和 `null` 的内存。\n" |
| |
| #: src/generics/gen_trait.md:33 |
| msgid "" |
| "//empty;\n" |
| " //null;\n" |
| " // ^ TODO: Try uncommenting these lines.\n" |
| msgstr "" |
| "//empty;\n" |
| " //null;\n" |
| " // ^ TODO：尝试取消这些行的注释。\n" |
| |
| #: src/generics/gen_trait.md:41 |
| msgid "" |
| "[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html), [`struct`](../" |
| "custom_types/structs.md), and [`trait`](../trait.md)" |
| msgstr "" |
| "[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html)、[`struct`](../" |
| "custom_types/structs.md) 和 [`trait`](../trait.md)" |
| |
| #: src/generics/bounds.md:3 |
| msgid "" |
| "When working with generics, the type parameters often must use traits as " |
| "_bounds_ to stipulate what functionality a type implements. For example, the " |
| "following example uses the trait `Display` to print and so it requires `T` " |
| "to be bound by `Display`; that is, `T` _must_ implement `Display`." |
| msgstr "" |
| "在使用泛型时，类型参数通常需要使用 trait 作为**约束**，以规定类型应实现哪些功" |
| "能。例如，下面的示例使用 `Display` trait 来打印，因此它要求 `T` 必须受 " |
| "`Display` 约束；换句话说，`T` **必须**实现 `Display`。" |
| |
| #: src/generics/bounds.md:9 |
| msgid "" |
| "// Define a function `printer` that takes a generic type `T` which\n" |
| "// must implement trait `Display`.\n" |
| msgstr "" |
| "// 定义一个函数 `printer`，它接受一个泛型类型 `T`，\n" |
| "// 该类型必须实现 `Display` trait。\n" |
| |
| #: src/generics/bounds.md:16 |
| msgid "" |
| "Bounding restricts the generic to types that conform to the bounds. That is:" |
| msgstr "约束将泛型限制为符合约束条件的类型。也就是说：" |
| |
| #: src/generics/bounds.md:20 |
| msgid "" |
| "// Error! `Vec<T>` does not implement `Display`. This\n" |
| "// specialization will fail.\n" |
| msgstr "" |
| "// 错误！`Vec<T>` 没有实现 `Display`。\n" |
| "// 这个特化将会失败。\n" |
| |
| #: src/generics/bounds.md:26 |
| msgid "" |
| "Another effect of bounding is that generic instances are allowed to access " |
| "the [methods](../fn/methods.md) of traits specified in the bounds. For " |
| "example:" |
| msgstr "" |
| "约束的另一个作用是允许泛型实例访问约束中指定的 trait 的[方法](../fn/" |
| "methods.md)。例如：" |
| |
| #: src/generics/bounds.md:30 |
| msgid "// A trait which implements the print marker: `{:?}`.\n" |
| msgstr "// 实现打印标记 `{:?}` 的 trait。\n" |
| |
| #: src/generics/bounds.md:45 |
| msgid "" |
| "// The generic `T` must implement `Debug`. Regardless\n" |
| "// of the type, this will work properly.\n" |
| msgstr "" |
| "// 泛型 `T` 必须实现 `Debug`。无论 `T` 是什么类型，\n" |
| "// 这个函数都能正常工作。\n" |
| |
| #: src/generics/bounds.md:51 |
| msgid "" |
| "// `T` must implement `HasArea`. Any type which meets\n" |
| "// the bound can access `HasArea`'s function `area`.\n" |
| msgstr "" |
| "// `T` 必须实现 `HasArea`。任何满足这个约束的类型\n" |
| "// 都可以访问 `HasArea` 的 `area` 方法。\n" |
| |
| #: src/generics/bounds.md:61 |
| msgid "\"Area: {}\"" |
| msgstr "\"面积：{}\"" |
| |
| #: src/generics/bounds.md:63 |
| msgid "" |
| "//print_debug(&_triangle);\n" |
| " //println!(\"Area: {}\", area(&_triangle));\n" |
| " // ^ TODO: Try uncommenting these.\n" |
| " // | Error: Does not implement either `Debug` or `HasArea`. \n" |
| msgstr "" |
| "//print_debug(&_triangle);\n" |
| " //println!(\"面积：{}\", area(&_triangle));\n" |
| " // ^ TODO：尝试取消这些注释。\n" |
| " // | 错误：未实现 `Debug` 或 `HasArea`。\n" |
| |
| #: src/generics/bounds.md:70 |
| msgid "" |
| "As an additional note, [`where`](../generics/where.md) clauses can also be " |
| "used to apply bounds in some cases to be more expressive." |
| msgstr "" |
| "另外值得注意的是，在某些情况下可以使用 [`where`](../generics/where.md) 子句来" |
| "应用约束，以使表达更加清晰。" |
| |
| #: src/generics/bounds.md:75 |
| msgid "" |
| "[`std::fmt`](../hello/print.md), [`struct`s](../custom_types/structs.md), " |
| "and [`trait`s](../trait.md)" |
| msgstr "" |
| "[`std::fmt`](../hello/print.md)、[`struct`](../custom_types/structs.md)和 " |
| "[`trait`](../trait.md)" |
| |
| #: src/generics/bounds/testcase_empty.md:3 |
| msgid "" |
| "A consequence of how bounds work is that even if a `trait` doesn't include " |
| "any functionality, you can still use it as a bound. `Eq` and `Copy` are " |
| "examples of such `trait`s from the `std` library." |
| msgstr "" |
| "约束的工作机制导致即使一个 `trait` 不包含任何功能，你仍然可以将其用作约束。" |
| "`std` 库中的 `Eq` 和 `Copy` 就是这种 `trait` 的例子。" |
| |
| #: src/generics/bounds/testcase_empty.md:17 |
| msgid "" |
| "// These functions are only valid for types which implement these\n" |
| "// traits. The fact that the traits are empty is irrelevant.\n" |
| msgstr "" |
| "// 这些函数只对实现了这些 trait 的类型有效。\n" |
| "// 这些 trait 是否为空并不重要。\n" |
| |
| #: src/generics/bounds/testcase_empty.md:20 |
| msgid "\"red\"" |
| msgstr "\"红色\"" |
| |
| #: src/generics/bounds/testcase_empty.md:21 |
| msgid "\"blue\"" |
| msgstr "\"蓝色\"" |
| |
| #: src/generics/bounds/testcase_empty.md:28 |
| msgid "" |
| "// `red()` won't work on a blue jay nor vice versa\n" |
| " // because of the bounds.\n" |
| msgstr "// 由于约束的存在，`red()` 不能用于蓝松鸟，反之亦然。\n" |
| |
| #: src/generics/bounds/testcase_empty.md:30 |
| msgid "\"A cardinal is {}\"" |
| msgstr "\"红雀是{}\"" |
| |
| #: src/generics/bounds/testcase_empty.md:31 |
| msgid "\"A blue jay is {}\"" |
| msgstr "\"蓝松鸟是{}\"" |
| |
| #: src/generics/bounds/testcase_empty.md:32 |
| msgid "" |
| "//println!(\"A turkey is {}\", red(&_turkey));\n" |
| " // ^ TODO: Try uncommenting this line.\n" |
| msgstr "" |
| "//println!(\"火鸡是{}\", red(&_turkey));\n" |
| " // ^ TODO：尝试取消这行的注释。\n" |
| |
| #: src/generics/bounds/testcase_empty.md:39 |
| msgid "" |
| "[`std::cmp::Eq`](https://doc.rust-lang.org/std/cmp/trait.Eq.html), " |
| "[`std::marker::Copy`](https://doc.rust-lang.org/std/marker/trait.Copy.html), " |
| "and [`trait`s](../../trait.md)" |
| msgstr "" |
| "[`std::cmp::Eq`](https://doc.rust-lang.org/std/cmp/trait.Eq.html)、" |
| "[`std::marker::Copy`](https://doc.rust-lang.org/std/marker/trait.Copy.html) " |
| "和 [`trait`](../../trait.md)" |
| |
| #: src/generics/multi_bounds.md:3 |
| msgid "" |
| "Multiple bounds for a single type can be applied with a `+`. Like normal, " |
| "different types are separated with `,`." |
| msgstr "可以使用 `+` 为单个类型指定多个约束。按照惯例，不同的类型用 `,` 分隔。" |
| |
| #: src/generics/multi_bounds.md:10 |
| msgid "\"Debug: `{:?}`\"" |
| msgstr "\"Debug：`{:?}`\"" |
| |
| #: src/generics/multi_bounds.md:11 |
| msgid "\"Display: `{}`\"" |
| msgstr "\"Display：`{}`\"" |
| |
| #: src/generics/multi_bounds.md:15 |
| msgid "\"t: `{:?}`\"" |
| msgstr "\"t：`{:?}`\"" |
| |
| #: src/generics/multi_bounds.md:16 |
| msgid "\"u: `{:?}`\"" |
| msgstr "\"u：`{:?}`\"" |
| |
| #: src/generics/multi_bounds.md:20 |
| msgid "\"words\"" |
| msgstr "\"words\"" |
| |
| #: src/generics/multi_bounds.md:25 |
| msgid "" |
| "//compare_prints(&array);\n" |
| " // TODO ^ Try uncommenting this.\n" |
| msgstr "" |
| "//compare_prints(&array);\n" |
| " // TODO：尝试取消此行注释。\n" |
| |
| #: src/generics/multi_bounds.md:34 |
| msgid "[`std::fmt`](../hello/print.md) and [`trait`s](../trait.md)" |
| msgstr "[`std::fmt`](../hello/print.md) 和 [`trait`](../trait.md)" |
| |
| #: src/generics/where.md:3 |
| msgid "" |
| "A bound can also be expressed using a `where` clause immediately before the " |
| "opening `{`, rather than at the type's first mention. Additionally, `where` " |
| "clauses can apply bounds to arbitrary types, rather than just to type " |
| "parameters." |
| msgstr "" |
| "约束也可以使用 `where` 子句来表达，它位于开括号 `{` 之前，而不是在类型首次提" |
| "及时。此外，`where` 子句可以将约束应用于任意类型，而不仅限于类型参数。" |
| |
| #: src/generics/where.md:8 |
| msgid "Some cases that a `where` clause is useful:" |
| msgstr "`where` 子句在以下情况下特别有用：" |
| |
| #: src/generics/where.md:10 |
| msgid "When specifying generic types and bounds separately is clearer:" |
| msgstr "当单独指定泛型类型和约束更清晰时：" |
| |
| #: src/generics/where.md:14 |
| msgid "// Expressing bounds with a `where` clause\n" |
| msgstr "// 使用 `where` 子句表达约束\n" |
| |
| #: src/generics/where.md:21 |
| msgid "" |
| "When using a `where` clause is more expressive than using normal syntax. The " |
| "`impl` in this example cannot be directly expressed without a `where` clause:" |
| msgstr "" |
| "当使用 `where` 子句比使用普通语法更具表现力时。这个例子中的 `impl` 如果不使" |
| "用 `where` 子句就无法直接表达：" |
| |
| #: src/generics/where.md:30 |
| msgid "" |
| "// Because we would otherwise have to express this as `T: Debug` or \n" |
| "// use another method of indirect approach, this requires a `where` clause:\n" |
| msgstr "" |
| "// 这里需要一个 `where` 子句：否则就必须将其表达为 `T: Debug` 或\n" |
| "// 使用另一种间接方法，\n" |
| |
| #: src/generics/where.md:35 |
| msgid "" |
| "// We want `Option<T>: Debug` as our bound because that is what's\n" |
| " // being printed. Doing otherwise would be using the wrong bound.\n" |
| msgstr "" |
| "// 我们需要 `Option<T>: Debug` 作为我们的约束，因为这是\n" |
| " // 正在被打印的内容。否则就会使用错误的约束。\n" |
| |
| #: src/generics/where.md:51 |
| msgid "" |
| "[RFC](https://github.com/rust-lang/rfcs/blob/master/text/0135-where.md), " |
| "[`struct`](../custom_types/structs.md), and [`trait`](../trait.md)" |
| msgstr "" |
| "[RFC](https://github.com/rust-lang/rfcs/blob/master/text/0135-where.md)、" |
| "[`struct`](../custom_types/structs.md) 和 [`trait`](../trait.md)" |
| |
| #: src/generics/new_types.md:3 |
| msgid "" |
| "The `newtype` idiom gives compile time guarantees that the right type of " |
| "value is supplied to a program." |
| msgstr "`newtype` 模式在编译时保证了程序接收到正确类型的值。" |
| |
| #: src/generics/new_types.md:6 |
| msgid "" |
| "For example, an age verification function that checks age in years, _must_ " |
| "be given a value of type `Years`." |
| msgstr "" |
| "例如，一个检查年龄（以年为单位）的年龄验证函数，**必须**接收 `Years` 类型的" |
| "值。" |
| |
| #: src/generics/new_types.md:21 |
| msgid "/// truncates partial years\n" |
| msgstr "/// 截断不足一年的部分\n" |
| |
| #: src/generics/new_types.md:34 src/generics/new_types.md:35 |
| msgid "\"Is an adult? {}\"" |
| msgstr "\"是否成年？{}\"" |
| |
| #: src/generics/new_types.md:36 |
| msgid "// println!(\"Is an adult? {}\", is_adult(&age_days));\n" |
| msgstr "// println!(\"是否成年？{}\", is_adult(&age_days));\n" |
| |
| #: src/generics/new_types.md:40 |
| msgid "" |
| "Uncomment the last print statement to observe that the type supplied must be " |
| "`Years`." |
| msgstr "取消最后一个 print 语句的注释，你会发现所提供的类型必须是 `Years`。" |
| |
| #: src/generics/new_types.md:42 |
| msgid "" |
| "To obtain the `newtype`'s value as the base type, you may use the tuple or " |
| "destructuring syntax like so:" |
| msgstr "" |
| "要获取 `newtype` 的基本类型值，你可以使用元组语法或解构语法，如下所示：" |
| |
| #: src/generics/new_types.md:49 |
| msgid "// Tuple\n" |
| msgstr "// 元组语法\n" |
| |
| #: src/generics/new_types.md:50 |
| msgid "// Destructuring\n" |
| msgstr "// 解构语法\n" |
| |
| #: src/generics/new_types.md:56 |
| msgid "[`structs`](../custom_types/structs.md)" |
| msgstr "[`struct`](../custom_types/structs.md)" |
| |
| #: src/generics/assoc_items.md:3 |
| msgid "" |
| "\"Associated Items\" refers to a set of rules pertaining to [`item`](https://" |
| "doc.rust-lang.org/reference/items.html)s of various types. It is an " |
| "extension to `trait` generics, and allows `trait`s to internally define new " |
| "items." |
| msgstr "" |
| "\"关联项\"是指与各种类型的[`项`](https://doc.rust-lang.org/reference/" |
| "items.html)相关的一组规则。它是 `trait` 泛型的扩展，允许 `trait` 在内部定义新" |
| "的项。" |
| |
| #: src/generics/assoc_items.md:7 |
| msgid "" |
| "One such item is called an _associated type_, providing simpler usage " |
| "patterns when the `trait` is generic over its container type." |
| msgstr "" |
| "其中一种项被称为**关联类型**，当 `trait` 对其容器类型是泛型时，它提供了更简洁" |
| "的使用模式。" |
| |
| #: src/generics/assoc_items.md:12 |
| msgid "" |
| "[RFC](https://github.com/rust-lang/rfcs/blob/master/text/0195-associated-" |
| "items.md)" |
| msgstr "" |
| "[RFC](https://github.com/rust-lang/rfcs/blob/master/text/0195-associated-" |
| "items.md)" |
| |
| #: src/generics/assoc_items/the_problem.md:3 |
| msgid "" |
| "A `trait` that is generic over its container type has type specification " |
| "requirements - users of the `trait` _must_ specify all of its generic types." |
| msgstr "" |
| "对于容器类型是泛型的 `trait`，有类型规范要求 —— `trait` 的使用者**必须**指定" |
| "所有的泛型类型。" |
| |
| #: src/generics/assoc_items/the_problem.md:6 |
| msgid "" |
| "In the example below, the `Contains` `trait` allows the use of the generic " |
| "types `A` and `B`. The trait is then implemented for the `Container` type, " |
| "specifying `i32` for `A` and `B` so that it can be used with `fn " |
| "difference()`." |
| msgstr "" |
| "在下面的例子中，`Contains` trait 允许使用泛型类型 `A` 和 `B`。然后为 " |
| "`Container` 类型实现该 trait，将 `A` 和 `B` 指定为 `i32`，以便与 `fn " |
| "difference()` 一起使用。" |
| |
| #: src/generics/assoc_items/the_problem.md:10 |
| msgid "" |
| "Because `Contains` is generic, we are forced to explicitly state _all_ of " |
| "the generic types for `fn difference()`. In practice, we want a way to " |
| "express that `A` and `B` are determined by the _input_ `C`. As you will see " |
| "in the next section, associated types provide exactly that capability." |
| msgstr "" |
| "由于 `Contains` 是泛型的，我们不得不为 `fn difference()` 显式声明**所有**泛型" |
| "类型。实际上，我们希望有一种方法来表达 `A` 和 `B` 是由**输入** `C` 决定的。正" |
| "如你将在下一节中看到的，关联类型恰好提供了这种能力。" |
| |
| #: src/generics/assoc_items/the_problem.md:17 |
| #: src/generics/assoc_items/types.md:36 |
| msgid "" |
| "// A trait which checks if 2 items are stored inside of container.\n" |
| "// Also retrieves first or last value.\n" |
| msgstr "" |
| "// 一个检查容器内是否存储了两个项的 trait。\n" |
| "// 同时可以检索第一个或最后一个值。\n" |
| |
| #: src/generics/assoc_items/the_problem.md:21 |
| msgid "// Explicitly requires `A` and `B`.\n" |
| msgstr "// 显式要求 `A` 和 `B`\n" |
| |
| #: src/generics/assoc_items/the_problem.md:22 |
| #: src/generics/assoc_items/the_problem.md:23 |
| msgid "// Doesn't explicitly require `A` or `B`.\n" |
| msgstr "// 不需要显式指定 `A` 或 `B`\n" |
| |
| #: src/generics/assoc_items/the_problem.md:27 |
| msgid "// True if the numbers stored are equal.\n" |
| msgstr "// 如果存储的数字相等则返回 true\n" |
| |
| #: src/generics/assoc_items/the_problem.md:32 |
| #: src/generics/assoc_items/types.md:60 |
| msgid "// Grab the first number.\n" |
| msgstr "// 获取第一个数字\n" |
| |
| #: src/generics/assoc_items/the_problem.md:35 |
| #: src/generics/assoc_items/types.md:63 |
| msgid "// Grab the last number.\n" |
| msgstr "// 获取最后一个数字\n" |
| |
| #: src/generics/assoc_items/the_problem.md:38 |
| msgid "" |
| "// `C` contains `A` and `B`. In light of that, having to express `A` and\n" |
| "// `B` again is a nuisance.\n" |
| msgstr "" |
| "// `C` 已经包含了 `A` 和 `B`。考虑到这一点，\n" |
| "// 再次指定 `A` 和 `B` 就显得多余且麻烦。\n" |
| |
| #: src/generics/assoc_items/the_problem.md:52 |
| #: src/generics/assoc_items/types.md:77 |
| msgid "\"Does container contain {} and {}: {}\"" |
| msgstr "\"容器是否包含 {} 和 {}：{}\"" |
| |
| #: src/generics/assoc_items/the_problem.md:55 |
| #: src/generics/assoc_items/types.md:80 |
| msgid "\"First number: {}\"" |
| msgstr "\"第一个数字：{}\"" |
| |
| #: src/generics/assoc_items/the_problem.md:56 |
| #: src/generics/assoc_items/types.md:81 |
| msgid "\"Last number: {}\"" |
| msgstr "\"最后一个数字：{}\"" |
| |
| #: src/generics/assoc_items/the_problem.md:58 |
| #: src/generics/assoc_items/types.md:83 |
| msgid "\"The difference is: {}\"" |
| msgstr "\"差值为：{}\"" |
| |
| #: src/generics/assoc_items/the_problem.md:64 |
| msgid "" |
| "[`struct`s](../../custom_types/structs.md), and [`trait`s](../../trait.md)" |
| msgstr "[`struct`](../../custom_types/structs.md) 和 [`trait`](../../trait.md)" |
| |
| #: src/generics/assoc_items/types.md:3 |
| msgid "" |
| "The use of \"Associated types\" improves the overall readability of code by " |
| "moving inner types locally into a trait as _output_ types. Syntax for the " |
| "`trait` definition is as follows:" |
| msgstr "" |
| "使用\"关联类型\"通过将内部类型局部移动到 trait 中作为**输出**类型，提高了代码" |
| "的整体可读性。trait 定义的语法如下：" |
| |
| #: src/generics/assoc_items/types.md:8 |
| msgid "" |
| "// `A` and `B` are defined in the trait via the `type` keyword.\n" |
| "// (Note: `type` in this context is different from `type` when used for\n" |
| "// aliases).\n" |
| msgstr "" |
| "// `A` 和 `B` 在 trait 中通过 `type` 关键字定义。\n" |
| "// （注意：这里的 `type` 与用于类型别名的 `type` 不同）\n" |
| |
| #: src/generics/assoc_items/types.md:15 |
| msgid "// Updated syntax to refer to these new types generically.\n" |
| msgstr "// 更新后的语法，用于泛型地引用这些新类型\n" |
| |
| #: src/generics/assoc_items/types.md:20 |
| msgid "" |
| "Note that functions that use the `trait` `Contains` are no longer required " |
| "to express `A` or `B` at all:" |
| msgstr "注意，使用 `Contains` trait 的函数不再需要显式指定 `A` 或 `B`：" |
| |
| #: src/generics/assoc_items/types.md:24 |
| msgid "// Without using associated types\n" |
| msgstr "// 不使用关联类型\n" |
| |
| #: src/generics/assoc_items/types.md:27 |
| msgid "// Using associated types\n" |
| msgstr "// 使用关联类型\n" |
| |
| #: src/generics/assoc_items/types.md:32 |
| msgid "" |
| "Let's rewrite the example from the previous section using associated types:" |
| msgstr "让我们使用关联类型重写上一节的示例：" |
| |
| #: src/generics/assoc_items/types.md:40 |
| msgid "// Define generic types here which methods will be able to utilize.\n" |
| msgstr "// 在此定义泛型类型，方法将能够使用这些类型\n" |
| |
| #: src/generics/assoc_items/types.md:50 |
| msgid "" |
| "// Specify what types `A` and `B` are. If the `input` type\n" |
| " // is `Container(i32, i32)`, the `output` types are determined\n" |
| " // as `i32` and `i32`.\n" |
| msgstr "" |
| "// 指定 `A` 和 `B` 的具体类型。如果 `input` 类型\n" |
| " // 是 `Container(i32, i32)`，那么 `output` 类型\n" |
| " // 就被确定为 `i32` 和 `i32`\n" |
| |
| #: src/generics/assoc_items/types.md:56 |
| msgid "// `&Self::A` and `&Self::B` are also valid here.\n" |
| msgstr "// 在这里使用 `&Self::A` 和 `&Self::B` 也是有效的。\n" |
| |
| #: src/generics/phantom.md:3 |
| msgid "" |
| "A phantom type parameter is one that doesn't show up at runtime, but is " |
| "checked statically (and only) at compile time." |
| msgstr "虚类型参数是一种在运行时不会出现，但在编译时会进行静态检查的类型参数。" |
| |
| #: src/generics/phantom.md:6 |
| msgid "" |
| "Data types can use extra generic type parameters to act as markers or to " |
| "perform type checking at compile time. These extra parameters hold no " |
| "storage values, and have no runtime behavior." |
| msgstr "" |
| "数据类型可以使用额外的泛型类型参数作为标记，或在编译时进行类型检查。这些额外" |
| "的参数不占用存储空间，也没有运行时行为。" |
| |
| #: src/generics/phantom.md:10 |
| msgid "" |
| "In the following example, we combine [std::marker::PhantomData](https://" |
| "doc.rust-lang.org/std/marker/struct.PhantomData.html) with the phantom type " |
| "parameter concept to create tuples containing different data types." |
| msgstr "" |
| "在下面的示例中，我们将 [`std::marker::PhantomData`](https://doc.rust-" |
| "lang.org/std/marker/struct.PhantomData.html) 与虚类型参数的概念结合，创建包含" |
| "不同数据类型的元组。" |
| |
| #: src/generics/phantom.md:16 |
| msgid "" |
| "// A phantom tuple struct which is generic over `A` with hidden parameter " |
| "`B`.\n" |
| msgstr "// 一个虚元组结构体，它在 `A` 上是泛型的，带有隐藏参数 `B`。\n" |
| |
| #: src/generics/phantom.md:18 src/generics/phantom.md:22 |
| msgid "// Allow equality test for this type.\n" |
| msgstr "// 允许对此类型进行相等性测试。\n" |
| |
| #: src/generics/phantom.md:20 |
| msgid "" |
| "// A phantom type struct which is generic over `A` with hidden parameter " |
| "`B`.\n" |
| msgstr "// 一个虚类型结构体，它在 `A` 上是泛型的，带有隐藏参数 `B`。\n" |
| |
| #: src/generics/phantom.md:24 |
| msgid "" |
| "// Note: Storage is allocated for generic type `A`, but not for `B`.\n" |
| "// Therefore, `B` cannot be used in computations.\n" |
| msgstr "" |
| "// 注意：为泛型类型 `A` 分配了存储空间，但没有为 `B` 分配。\n" |
| "// 因此，`B` 不能用于计算。\n" |
| |
| #: src/generics/phantom.md:29 |
| msgid "" |
| "// Here, `f32` and `f64` are the hidden parameters.\n" |
| " // PhantomTuple type specified as `<char, f32>`.\n" |
| msgstr "" |
| "// 这里，`f32` 和 `f64` 是隐藏参数。\n" |
| " // PhantomTuple 类型指定为 `<char, f32>`。\n" |
| |
| #: src/generics/phantom.md:31 src/generics/phantom.md:33 |
| #: src/generics/phantom.md:37 src/generics/phantom.md:42 |
| #: src/scope/borrow/ref.md:12 |
| msgid "'Q'" |
| msgstr "'Q'" |
| |
| #: src/generics/phantom.md:32 |
| msgid "// PhantomTuple type specified as `<char, f64>`.\n" |
| msgstr "// PhantomTuple 类型指定为 `<char, f64>`。\n" |
| |
| #: src/generics/phantom.md:35 |
| msgid "// Type specified as `<char, f32>`.\n" |
| msgstr "// 类型指定为 `<char, f32>`。\n" |
| |
| #: src/generics/phantom.md:40 |
| msgid "// Type specified as `<char, f64>`.\n" |
| msgstr "// 类型指定为 `<char, f64>`。\n" |
| |
| #: src/generics/phantom.md:46 |
| msgid "" |
| "// Compile-time Error! Type mismatch so these cannot be compared:\n" |
| " // println!(\"_tuple1 == _tuple2 yields: {}\",\n" |
| " // _tuple1 == _tuple2);\n" |
| msgstr "" |
| "// 编译时错误！类型不匹配，无法比较：\n" |
| " // println!(\"_tuple1 == _tuple2 的结果是：{}\",\n" |
| " // _tuple1 == _tuple2);\n" |
| |
| #: src/generics/phantom.md:50 |
| msgid "" |
| "// Compile-time Error! Type mismatch so these cannot be compared:\n" |
| " // println!(\"_struct1 == _struct2 yields: {}\",\n" |
| " // _struct1 == _struct2);\n" |
| msgstr "" |
| "// 编译时错误！类型不匹配，无法比较：\n" |
| " // println!(\"_struct1 == _struct2 的结果是：{}\",\n" |
| " // _struct1 == _struct2);\n" |
| |
| #: src/generics/phantom.md:58 |
| msgid "" |
| "[Derive](../trait/derive.md), [struct](../custom_types/structs.md), and " |
| "[TupleStructs](../custom_types/structs.md)" |
| msgstr "" |
| "[派生（Derive）](../trait/derive.md)、[结构体（struct）](../custom_types/" |
| "structs.md)和[元组结构体（TupleStructs）](../custom_types/structs.md)" |
| |
| #: src/generics/phantom/testcase_units.md:3 |
| msgid "" |
| "A useful method of unit conversions can be examined by implementing `Add` " |
| "with a phantom type parameter. The `Add` `trait` is examined below:" |
| msgstr "" |
| "通过使用虚类型参数实现 `Add` trait，我们可以探索一种有用的单位转换方法。下面" |
| "我们来看看 `Add` trait：" |
| |
| #: src/generics/phantom/testcase_units.md:7 |
| msgid "" |
| "// This construction would impose: `Self + RHS = Output`\n" |
| "// where RHS defaults to Self if not specified in the implementation.\n" |
| msgstr "" |
| "// 这个结构会强制要求：`Self + RHS = Output`\n" |
| "// 其中，如果在实现中未指定 RHS，它将默认为 Self。\n" |
| |
| #: src/generics/phantom/testcase_units.md:14 |
| msgid "// `Output` must be `T<U>` so that `T<U> + T<U> = T<U>`.\n" |
| msgstr "// `Output` 必须是 `T<U>`，以确保 `T<U> + T<U> = T<U>`。\n" |
| |
| #: src/generics/phantom/testcase_units.md:22 |
| msgid "The whole implementation:" |
| msgstr "完整实现如下：" |
| |
| #: src/generics/phantom/testcase_units.md:27 |
| msgid "/// Create void enumerations to define unit types.\n" |
| msgstr "/// 创建空枚举以定义单位类型。\n" |
| |
| #: src/generics/phantom/testcase_units.md:33 |
| msgid "" |
| "/// `Length` is a type with phantom type parameter `Unit`,\n" |
| "/// and is not generic over the length type (that is `f64`).\n" |
| "///\n" |
| "/// `f64` already implements the `Clone` and `Copy` traits.\n" |
| msgstr "" |
| "/// `Length` 是一个带有虚类型参数 `Unit` 的类型，\n" |
| "/// 它不是长度类型（即 `f64`）的泛型。\n" |
| "///\n" |
| "/// `f64` 已经实现了 `Clone` 和 `Copy` trait。\n" |
| |
| #: src/generics/phantom/testcase_units.md:40 |
| msgid "/// The `Add` trait defines the behavior of the `+` operator.\n" |
| msgstr "/// `Add` trait 定义了 `+` 运算符的行为。\n" |
| |
| #: src/generics/phantom/testcase_units.md:45 |
| msgid "// add() returns a new `Length` struct containing the sum.\n" |
| msgstr "// add() 返回一个包含和的新 `Length` 结构体。\n" |
| |
| #: src/generics/phantom/testcase_units.md:47 |
| msgid "// `+` calls the `Add` implementation for `f64`.\n" |
| msgstr "// `+` 调用 `f64` 的 `Add` 实现。\n" |
| |
| #: src/generics/phantom/testcase_units.md:53 |
| msgid "// Specifies `one_foot` to have phantom type parameter `Inch`.\n" |
| msgstr "// 指定 `one_foot` 具有虚类型参数 `Inch`。\n" |
| |
| #: src/generics/phantom/testcase_units.md:55 |
| msgid "// `one_meter` has phantom type parameter `Mm`.\n" |
| msgstr "// `one_meter` 具有虚类型参数 `Mm`。\n" |
| |
| #: src/generics/phantom/testcase_units.md:58 |
| msgid "" |
| "// `+` calls the `add()` method we implemented for `Length<Unit>`.\n" |
| " //\n" |
| " // Since `Length` implements `Copy`, `add()` does not consume\n" |
| " // `one_foot` and `one_meter` but copies them into `self` and `rhs`.\n" |
| msgstr "" |
| "// `+` 调用我们为 `Length<Unit>` 实现的 `add()` 方法。\n" |
| " //\n" |
| " // 由于 `Length` 实现了 `Copy`，`add()` 不会消耗\n" |
| " // `one_foot` 和 `one_meter`，而是将它们复制到 `self` 和 `rhs` 中。\n" |
| |
| #: src/generics/phantom/testcase_units.md:65 |
| msgid "// Addition works.\n" |
| msgstr "// 加法运算正常工作。\n" |
| |
| #: src/generics/phantom/testcase_units.md:66 |
| msgid "\"one foot + one_foot = {:?} in\"" |
| msgstr "\"一英尺 + 一英尺 = {:?} 英寸\"" |
| |
| #: src/generics/phantom/testcase_units.md:67 |
| msgid "\"one meter + one_meter = {:?} mm\"" |
| msgstr "\"一米 + 一米 = {:?} 毫米\"" |
| |
| #: src/generics/phantom/testcase_units.md:69 |
| msgid "" |
| "// Nonsensical operations fail as they should:\n" |
| " // Compile-time Error: type mismatch.\n" |
| " //let one_feter = one_foot + one_meter;\n" |
| msgstr "" |
| "// 无意义的操作会按预期失败：\n" |
| " // 编译时错误：类型不匹配。\n" |
| " //let one_feter = one_foot + one_meter;\n" |
| |
| #: src/generics/phantom/testcase_units.md:77 |
| msgid "" |
| "[Borrowing (`&`)](../../scope/borrow.md), [Bounds (`X: Y`)](../../generics/" |
| "bounds.md), [enum](../../custom_types/enum.md), [impl & self](../../fn/" |
| "methods.md), [Overloading](../../trait/ops.md), [ref](../../scope/borrow/" |
| "ref.md), [Traits (`X for Y`)](../../trait.md), and [TupleStructs](../../" |
| "custom_types/structs.md)." |
| msgstr "" |
| "[借用（`&`）](../../scope/borrow.md)、[约束（`X: Y`）](../../generics/" |
| "bounds.md)、[枚举](../../custom_types/enum.md)、[impl 和 self](../../fn/" |
| "methods.md)、[运算符重载](../../trait/ops.md)、[ref](../../scope/borrow/" |
| "ref.md)、[trait（`X for Y`）](../../trait.md)以及[元组结构体](../../" |
| "custom_types/structs.md)。" |
| |
| #: src/scope.md:3 |
| msgid "" |
| "Scopes play an important part in ownership, borrowing, and lifetimes. That " |
| "is, they indicate to the compiler when borrows are valid, when resources can " |
| "be freed, and when variables are created or destroyed." |
| msgstr "" |
| "作用域在所有权、借用和生命周期中扮演着重要角色。它们向编译器指示借用何时有" |
| "效、资源何时可以被释放，以及变量何时被创建或销毁。" |
| |
| #: src/scope/raii.md:3 |
| msgid "" |
| "Variables in Rust do more than just hold data in the stack: they also _own_ " |
| "resources, e.g. `Box<T>` owns memory in the heap. Rust enforces [RAII]" |
| "(https://en.wikipedia.org/wiki/Resource_Acquisition_Is_Initialization) " |
| "(Resource Acquisition Is Initialization), so whenever an object goes out of " |
| "scope, its destructor is called and its owned resources are freed." |
| msgstr "" |
| "Rust 中的变量不仅仅是在栈上保存数据：它们还**拥有**资源，例如 `Box<T>` 拥有堆" |
| "上的内存。Rust 强制执行 [RAII](https://en.wikipedia.org/wiki/" |
| "Resource_Acquisition_Is_Initialization)（资源获取即初始化），因此每当一个对象" |
| "离开作用域时，它的析构函数就会被调用，它拥有的资源也会被释放。" |
| |
| #: src/scope/raii.md:8 |
| msgid "" |
| "This behavior shields against _resource leak_ bugs, so you'll never have to " |
| "manually free memory or worry about memory leaks again! Here's a quick " |
| "showcase:" |
| msgstr "" |
| "这种行为可以防止**资源泄漏**错误，因此你再也不用手动释放内存或担心内存泄漏" |
| "了！以下是一个简单示例：" |
| |
| #: src/scope/raii.md:12 |
| msgid "// raii.rs\n" |
| msgstr "// raii.rs\n" |
| |
| #: src/scope/raii.md:14 src/scope/raii.md:21 src/scope/raii.md:26 |
| msgid "// Allocate an integer on the heap\n" |
| msgstr "// 在堆上分配一个整数\n" |
| |
| #: src/scope/raii.md:17 |
| msgid "// `_box1` is destroyed here, and memory gets freed\n" |
| msgstr "// `_box1` 在此处被销毁，内存被释放\n" |
| |
| #: src/scope/raii.md:24 |
| msgid "// A nested scope:\n" |
| msgstr "// 一个嵌套的作用域：\n" |
| |
| #: src/scope/raii.md:29 |
| msgid "// `_box3` is destroyed here, and memory gets freed\n" |
| msgstr "// `_box3` 在此处被销毁，内存被释放\n" |
| |
| #: src/scope/raii.md:32 |
| msgid "" |
| "// Creating lots of boxes just for fun\n" |
| " // There's no need to manually free memory!\n" |
| msgstr "" |
| "// 创建大量的 box（仅为演示）\n" |
| " // 无需手动释放内存！\n" |
| |
| #: src/scope/raii.md:38 |
| msgid "// `_box2` is destroyed here, and memory gets freed\n" |
| msgstr "// `_box2` 在此处被销毁，内存被释放\n" |
| |
| #: src/scope/raii.md:42 |
| msgid "" |
| "Of course, we can double check for memory errors using [`valgrind`](http://" |
| "valgrind.org/info/):" |
| msgstr "" |
| "当然，我们可以使用 [`valgrind`](http://valgrind.org/info/) 来再次检查内存错" |
| "误：" |
| |
| #: src/scope/raii.md:65 |
| msgid "No leaks here!" |
| msgstr "这里没有内存泄漏！" |
| |
| #: src/scope/raii.md:67 |
| msgid "Destructor" |
| msgstr "析构函数" |
| |
| #: src/scope/raii.md:69 |
| msgid "" |
| "The notion of a destructor in Rust is provided through the [`Drop`](https://" |
| "doc.rust-lang.org/std/ops/trait.Drop.html) trait. The destructor is called " |
| "when the resource goes out of scope. This trait is not required to be " |
| "implemented for every type, only implement it for your type if you require " |
| "its own destructor logic." |
| msgstr "" |
| "Rust 中的析构函数概念是通过 [`Drop`](https://doc.rust-lang.org/std/ops/" |
| "trait.Drop.html) trait 提供的。当资源离开作用域时，析构函数会被调用。并非每种" |
| "类型都需要实现这个 trait，只有当你需要为自己的类型实现特定的析构逻辑时才需要" |
| "实现它。" |
| |
| #: src/scope/raii.md:74 |
| msgid "" |
| "Run the below example to see how the [`Drop`](https://doc.rust-lang.org/std/" |
| "ops/trait.Drop.html) trait works. When the variable in the `main` function " |
| "goes out of scope the custom destructor will be invoked." |
| msgstr "" |
| "运行下面的示例来了解 [`Drop`](https://doc.rust-lang.org/std/ops/" |
| "trait.Drop.html) trait 是如何工作的。当 `main` 函数中的变量离开作用域时，自定" |
| "义的析构函数将被调用。" |
| |
| #: src/scope/raii.md:82 |
| msgid "\"ToDrop is being dropped\"" |
| msgstr "\"ToDrop 正在被丢弃\"" |
| |
| #: src/scope/raii.md:88 |
| msgid "\"Made a ToDrop!\"" |
| msgstr "\"创建了一个 ToDrop！\"" |
| |
| #: src/scope/raii.md:94 |
| msgid "[Box](../std/box.md)" |
| msgstr "[Box](../std/box.md)" |
| |
| #: src/scope/move.md:3 |
| msgid "" |
| "Because variables are in charge of freeing their own resources, **resources " |
| "can only have one owner**. This prevents resources from being freed more " |
| "than once. Note that not all variables own resources (e.g. [references](../" |
| "flow_control/match/destructuring/destructure_pointers.md))." |
| msgstr "" |
| "由于变量负责释放它们自己的资源，**资源只能有一个所有者**。这可以防止资源被多" |
| "次释放。请注意，并非所有变量都拥有资源（例如[引用](../flow_control/match/" |
| "destructuring/destructure_pointers.md)）。" |
| |
| #: src/scope/move.md:8 |
| msgid "" |
| "When doing assignments (`let x = y`) or passing function arguments by value " |
| "(`foo(x)`), the _ownership_ of the resources is transferred. In Rust-speak, " |
| "this is known as a _move_." |
| msgstr "" |
| "当进行赋值（`let x = y`）或按值传递函数参数（`foo(x)`）时，资源的**所有权**会" |
| "被转移。在 Rust 中，这被称为**移动**（move）。" |
| |
| #: src/scope/move.md:12 |
| msgid "" |
| "After moving resources, the previous owner can no longer be used. This " |
| "avoids creating dangling pointers." |
| msgstr "资源移动后，原所有者将无法再被使用。这避免了悬垂指针的产生。" |
| |
| #: src/scope/move.md:16 |
| msgid "// This function takes ownership of the heap allocated memory\n" |
| msgstr "// 此函数获取堆分配内存的所有权\n" |
| |
| #: src/scope/move.md:18 |
| msgid "\"Destroying a box that contains {}\"" |
| msgstr "\"正在销毁一个包含 {} 的 box\"" |
| |
| #: src/scope/move.md:20 |
| msgid "// `c` is destroyed and the memory freed\n" |
| msgstr "// `c` 被销毁，内存被释放\n" |
| |
| #: src/scope/move.md:24 |
| msgid "// _Stack_ allocated integer\n" |
| msgstr "// **栈**分配的整数\n" |
| |
| #: src/scope/move.md:27 |
| msgid "// *Copy* `x` into `y` - no resources are moved\n" |
| msgstr "// 将 `x` **复制**到 `y` - 没有资源被移动\n" |
| |
| #: src/scope/move.md:30 |
| msgid "// Both values can be independently used\n" |
| msgstr "// 两个值可以独立使用\n" |
| |
| #: src/scope/move.md:31 |
| msgid "\"x is {}, and y is {}\"" |
| msgstr "\"x 是 {}，y 是 {}\"" |
| |
| #: src/scope/move.md:33 |
| msgid "// `a` is a pointer to a _heap_ allocated integer\n" |
| msgstr "// `a` 是指向**堆**分配整数的指针\n" |
| |
| #: src/scope/move.md:36 |
| msgid "\"a contains: {}\"" |
| msgstr "\"a 包含：{}\"" |
| |
| #: src/scope/move.md:38 |
| msgid "// *Move* `a` into `b`\n" |
| msgstr "// 将 `a` **移动**到 `b`\n" |
| |
| #: src/scope/move.md:40 |
| msgid "" |
| "// The pointer address of `a` is copied (not the data) into `b`.\n" |
| " // Both are now pointers to the same heap allocated data, but\n" |
| " // `b` now owns it.\n" |
| msgstr "" |
| "// `a` 的指针地址（而非数据）被复制到 `b`\n" |
| " // 现在两者都指向同一块堆分配的数据\n" |
| " // 但 `b` 现在拥有它\n" |
| |
| #: src/scope/move.md:44 |
| msgid "" |
| "// Error! `a` can no longer access the data, because it no longer owns the\n" |
| " // heap memory\n" |
| " //println!(\"a contains: {}\", a);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`a` 不再拥有堆内存，因此无法访问数据\n" |
| " //println!(\"a 包含：{}\", a);\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/scope/move.md:49 |
| msgid "" |
| "// This function takes ownership of the heap allocated memory from `b`\n" |
| msgstr "// 此函数从 `b` 获取堆分配内存的所有权\n" |
| |
| #: src/scope/move.md:52 |
| msgid "" |
| "// Since the heap memory has been freed at this point, this action would\n" |
| " // result in dereferencing freed memory, but it's forbidden by the " |
| "compiler\n" |
| " // Error! Same reason as the previous Error\n" |
| " //println!(\"b contains: {}\", b);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 此时堆内存已被释放，这个操作会导致解引用已释放的内存\n" |
| " // 但编译器禁止这样做\n" |
| " // 错误！原因与前面的错误相同\n" |
| " //println!(\"b 包含：{}\", b);\n" |
| " // TODO ^ 尝试取消此行注释\n" |
| |
| #: src/scope/move/mut.md:3 |
| msgid "Mutability of data can be changed when ownership is transferred." |
| msgstr "当所有权转移时，数据的可变性可以改变。" |
| |
| #: src/scope/move/mut.md:9 |
| msgid "\"immutable_box contains {}\"" |
| msgstr "\"immutable_box 包含 {}\"" |
| |
| #: src/scope/move/mut.md:11 |
| msgid "" |
| "// Mutability error\n" |
| " //*immutable_box = 4;\n" |
| msgstr "" |
| "// 可变性错误\n" |
| " //*immutable_box = 4;\n" |
| |
| #: src/scope/move/mut.md:14 |
| msgid "// *Move* the box, changing the ownership (and mutability)\n" |
| msgstr "// *移动*盒子，改变所有权（和可变性）\n" |
| |
| #: src/scope/move/mut.md:17 |
| msgid "\"mutable_box contains {}\"" |
| msgstr "\"mutable_box 包含 {}\"" |
| |
| #: src/scope/move/mut.md:19 |
| msgid "// Modify the contents of the box\n" |
| msgstr "// 修改盒子的内容\n" |
| |
| #: src/scope/move/mut.md:22 |
| msgid "\"mutable_box now contains {}\"" |
| msgstr "\"mutable_box 现在包含 {}\"" |
| |
| #: src/scope/move/partial_move.md:3 |
| msgid "" |
| "Within the [destructuring](../../flow_control/match/destructuring.md) of a " |
| "single variable, both `by-move` and `by-reference` pattern bindings can be " |
| "used at the same time. Doing this will result in a _partial move_ of the " |
| "variable, which means that parts of the variable will be moved while other " |
| "parts stay. In such a case, the parent variable cannot be used afterwards as " |
| "a whole, however the parts that are only referenced (and not moved) can " |
| "still be used. Note that types that implement the [`Drop` trait](../../trait/" |
| "drop.md) cannot be partially moved from, because its `drop` method would use " |
| "it afterwards as a whole." |
| msgstr "" |
| "在对单个变量进行[解构](../../flow_control/match/destructuring.md)时，可以同时" |
| "使用 `by-move` 和 `by-reference` 模式绑定。这样做会导致变量的**部分移动**，这" |
| "意味着变量的一部分会被移动，而其他部分保持不变。在这种情况下，父级变量之后不" |
| "能作为一个整体使用，但是仍然可以使用只被引用（而不是被移动）的部分。注意，实" |
| "现了 [`Drop` 特质](../../trait/drop.md) 的类型不能被部分移动，因为其 `drop` " |
| "方法会在之后将其作为整体使用。" |
| |
| #: src/scope/move/partial_move.md:22 |
| msgid "" |
| "// Error! cannot move out of a type which implements the `Drop` trait\n" |
| " //impl Drop for Person {\n" |
| " // fn drop(&mut self) {\n" |
| " // println!(\"Dropping the person struct {:?}\", self)\n" |
| " // }\n" |
| " //}\n" |
| " // TODO ^ Try uncommenting these lines\n" |
| msgstr "" |
| "// 错误！无法从实现了 `Drop` 特质的类型中移动\n" |
| " //impl Drop for Person {\n" |
| " // fn drop(&mut self) {\n" |
| " // println!(\"Dropping the person struct {:?}\", self)\n" |
| " // }\n" |
| " //}\n" |
| " // TODO ^ 尝试取消注释这些行\n" |
| |
| #: src/scope/move/partial_move.md:35 |
| msgid "// `name` is moved out of person, but `age` is referenced\n" |
| msgstr "// `name` 从 person 中被移出，但 `age` 只是被引用\n" |
| |
| #: src/scope/move/partial_move.md:38 |
| msgid "\"The person's age is {}\"" |
| msgstr "\"此人的年龄是 {}\"" |
| |
| #: src/scope/move/partial_move.md:40 |
| msgid "\"The person's name is {}\"" |
| msgstr "\"此人的姓名是 {}\"" |
| |
| #: src/scope/move/partial_move.md:42 |
| msgid "" |
| "// Error! borrow of partially moved value: `person` partial move occurs\n" |
| " //println!(\"The person struct is {:?}\", person);\n" |
| msgstr "" |
| "// 错误！借用部分移动的值：`person` 发生部分移动\n" |
| " //println!(\"person 结构体是 {:?}\", person);\n" |
| |
| #: src/scope/move/partial_move.md:45 |
| msgid "" |
| "// `person` cannot be used but `person.age` can be used as it is not moved\n" |
| msgstr "// `person` 不能使用，但 `person.age` 可以使用，因为它没有被移动\n" |
| |
| #: src/scope/move/partial_move.md:46 |
| msgid "\"The person's age from person struct is {}\"" |
| msgstr "\"从 person 结构体中获取的年龄是 {}\"" |
| |
| #: src/scope/move/partial_move.md:50 |
| msgid "" |
| "(In this example, we store the `age` variable on the heap to illustrate the " |
| "partial move: deleting `ref` in the above code would give an error as the " |
| "ownership of `person.age` would be moved to the variable `age`. If " |
| "`Person.age` were stored on the stack, `ref` would not be required as the " |
| "definition of `age` would copy the data from `person.age` without moving it.)" |
| msgstr "" |
| "（在这个例子中，我们将 `age` 变量存储在堆上以说明部分移动：删除上面代码中的 " |
| "`ref` 会导致错误，因为 `person.age` 的所有权会被移动到变量 `age`。如果 " |
| "`Person.age` 存储在栈上，就不需要 `ref`，因为 `age` 的定义会从 `person.age` " |
| "复制数据而不是移动它。）" |
| |
| #: src/scope/move/partial_move.md:59 |
| msgid "[destructuring](../../flow_control/match/destructuring.md)" |
| msgstr "[解构](../../flow_control/match/destructuring.md)" |
| |
| #: src/scope/borrow.md:3 |
| msgid "" |
| "Most of the time, we'd like to access data without taking ownership over it. " |
| "To accomplish this, Rust uses a _borrowing_ mechanism. Instead of passing " |
| "objects by value (`T`), objects can be passed by reference (`&T`)." |
| msgstr "" |
| "大多数情况下，我们希望访问数据而不获取其所有权。为了实现这一点，Rust 使用了**" |
| "借用**机制。对象可以通过引用（`&T`）传递，而不是按值（`T`）传递。" |
| |
| #: src/scope/borrow.md:7 |
| msgid "" |
| "The compiler statically guarantees (via its borrow checker) that references " |
| "_always_ point to valid objects. That is, while references to an object " |
| "exist, the object cannot be destroyed." |
| msgstr "" |
| "编译器通过其借用检查器静态地保证引用**始终**指向有效的对象。也就是说，当存在" |
| "指向一个对象的引用时，该对象就不能被销毁。" |
| |
| #: src/scope/borrow.md:12 |
| msgid "// This function takes ownership of a box and destroys it\n" |
| msgstr "// 此函数获取一个盒子的所有权并销毁它\n" |
| |
| #: src/scope/borrow.md:14 |
| msgid "\"Destroying box that contains {}\"" |
| msgstr "\"正在销毁包含 {} 的盒子\"" |
| |
| #: src/scope/borrow.md:16 |
| msgid "// This function borrows an i32\n" |
| msgstr "// 此函数借用一个 i32\n" |
| |
| #: src/scope/borrow.md:19 |
| msgid "\"This int is: {}\"" |
| msgstr "\"这个整数是：{}\"" |
| |
| #: src/scope/borrow.md:23 |
| msgid "" |
| "// Create a boxed i32 in the heap, and a i32 on the stack\n" |
| " // Remember: numbers can have arbitrary underscores added for " |
| "readability\n" |
| " // 5_i32 is the same as 5i32\n" |
| msgstr "" |
| "// 在堆上创建一个装箱的 i32，在栈上创建一个 i32\n" |
| " // 注意：数字可以添加任意下划线以提高可读性\n" |
| " // 5_i32 与 5i32 相同\n" |
| |
| #: src/scope/borrow.md:29 |
| msgid "" |
| "// Borrow the contents of the box. Ownership is not taken,\n" |
| " // so the contents can be borrowed again.\n" |
| msgstr "" |
| "// 借用盒子的数据。所有权未被获取，\n" |
| " // 所以数据可以再次被借用。\n" |
| |
| #: src/scope/borrow.md:35 |
| msgid "// Take a reference to the data contained inside the box\n" |
| msgstr "// 获取盒子内数据的引用\n" |
| |
| #: src/scope/borrow.md:38 |
| msgid "" |
| "// Error!\n" |
| " // Can't destroy `boxed_i32` while the inner value is borrowed later " |
| "in scope.\n" |
| msgstr "" |
| "// 错误！\n" |
| " // 当内部值在作用域内稍后被借用时，不能销毁 `boxed_i32`。\n" |
| |
| #: src/scope/borrow.md:43 |
| msgid "// Attempt to borrow `_ref_to_i32` after inner value is destroyed\n" |
| msgstr "// 尝试在内部值被销毁后借用 `_ref_to_i32`\n" |
| |
| #: src/scope/borrow.md:45 |
| msgid "// `_ref_to_i32` goes out of scope and is no longer borrowed.\n" |
| msgstr "// `_ref_to_i32` 超出作用域，不再被借用。\n" |
| |
| #: src/scope/borrow.md:48 |
| msgid "" |
| "// `boxed_i32` can now give up ownership to `eat_box_i32` and be destroyed\n" |
| msgstr "// `boxed_i32` 现在可以将所有权交给 `eat_box_i32` 并被销毁\n" |
| |
| #: src/scope/borrow/mut.md:3 |
| msgid "" |
| "Mutable data can be mutably borrowed using `&mut T`. This is called a " |
| "_mutable reference_ and gives read/write access to the borrower. In " |
| "contrast, `&T` borrows the data via an immutable reference, and the borrower " |
| "can read the data but not modify it:" |
| msgstr "" |
| "可变数据可以使用 `&mut T` 进行可变借用。这被称为**可变引用**，并给予借用者读" |
| "写访问权。相比之下，`&T` 通过不可变引用借用数据，借用者可以读取数据但不能修改" |
| "它：" |
| |
| #: src/scope/borrow/mut.md:12 |
| msgid "" |
| "// `&'static str` is a reference to a string allocated in read only memory\n" |
| msgstr "// `&'static str` 是对分配在只读内存中的字符串的引用\n" |
| |
| #: src/scope/borrow/mut.md:17 |
| msgid "// This function takes a reference to a book\n" |
| msgstr "// 此函数接受一个对 Book 类型的引用\n" |
| |
| #: src/scope/borrow/mut.md:20 |
| msgid "\"I immutably borrowed {} - {} edition\"" |
| msgstr "\"我不可变地借用了《{}》- {} 版\"" |
| |
| #: src/scope/borrow/mut.md:22 |
| msgid "" |
| "// This function takes a reference to a mutable book and changes `year` to " |
| "2014\n" |
| msgstr "// 此函数接受一个对可变 Book 的引用，并将 `year` 改为 2014\n" |
| |
| #: src/scope/borrow/mut.md:26 |
| msgid "\"I mutably borrowed {} - {} edition\"" |
| msgstr "\"我可变地借用了《{}》- {} 版\"" |
| |
| #: src/scope/borrow/mut.md:30 |
| msgid "// Create an immutable Book named `immutabook`\n" |
| msgstr "// 创建一个名为 `immutabook` 的不可变 Book 实例\n" |
| |
| #: src/scope/borrow/mut.md:32 |
| msgid "// string literals have type `&'static str`\n" |
| msgstr "// 字符串字面量的类型是 `&'static str`\n" |
| |
| #: src/scope/borrow/mut.md:33 |
| msgid "\"Douglas Hofstadter\"" |
| msgstr "\"Douglas Hofstadter\"" |
| |
| #: src/scope/borrow/mut.md:34 |
| msgid "\"Gödel, Escher, Bach\"" |
| msgstr "\"哥德尔、埃舍尔、巴赫\"" |
| |
| #: src/scope/borrow/mut.md:38 |
| msgid "// Create a mutable copy of `immutabook` and call it `mutabook`\n" |
| msgstr "// 创建 `immutabook` 的可变副本，并命名为 `mutabook`\n" |
| |
| #: src/scope/borrow/mut.md:41 |
| msgid "// Immutably borrow an immutable object\n" |
| msgstr "// 不可变地借用一个不可变对象\n" |
| |
| #: src/scope/borrow/mut.md:44 |
| msgid "// Immutably borrow a mutable object\n" |
| msgstr "// 不可变地借用一个可变对象\n" |
| |
| #: src/scope/borrow/mut.md:47 |
| msgid "// Borrow a mutable object as mutable\n" |
| msgstr "// 可变地借用一个可变对象\n" |
| |
| #: src/scope/borrow/mut.md:50 |
| msgid "// Error! Cannot borrow an immutable object as mutable\n" |
| msgstr "// 错误！不能将不可变对象作为可变对象借用\n" |
| |
| #: src/scope/borrow/mut.md:58 |
| msgid "[`static`](../lifetime/static_lifetime.md)" |
| msgstr "[`static`](../lifetime/static_lifetime.md)" |
| |
| #: src/scope/borrow/alias.md:3 |
| msgid "" |
| "Data can be immutably borrowed any number of times, but while immutably " |
| "borrowed, the original data can't be mutably borrowed. On the other hand, " |
| "only _one_ mutable borrow is allowed at a time. The original data can be " |
| "borrowed again only _after_ the mutable reference has been used for the last " |
| "time." |
| msgstr "" |
| "数据可以被不可变借用任意次数，但在不可变借用期间，原始数据不能被可变借用。另" |
| "一方面，同一时间只允许**一个**可变借用。只有在可变引用最后一次使用之后，原始" |
| "数据才能再次被借用。" |
| |
| #: src/scope/borrow/alias.md:17 |
| msgid "// Data can be accessed via the references and the original owner\n" |
| msgstr "// 可以通过引用和原始所有者访问数据\n" |
| |
| #: src/scope/borrow/alias.md:18 src/scope/borrow/alias.md:27 |
| #: src/scope/borrow/alias.md:49 |
| msgid "\"Point has coordinates: ({}, {}, {})\"" |
| msgstr "\"点的坐标为：({}, {}, {})\"" |
| |
| #: src/scope/borrow/alias.md:21 |
| msgid "" |
| "// Error! Can't borrow `point` as mutable because it's currently\n" |
| " // borrowed as immutable.\n" |
| " // let mutable_borrow = &mut point;\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！不能将 `point` 作为可变借用，因为它当前被不可变借用。\n" |
| " // let mutable_borrow = &mut point;\n" |
| " // TODO ^ 尝试取消注释此行\n" |
| |
| #: src/scope/borrow/alias.md:26 |
| msgid "// The borrowed values are used again here\n" |
| msgstr "// 这里再次使用了借用的值\n" |
| |
| #: src/scope/borrow/alias.md:30 |
| msgid "" |
| "// The immutable references are no longer used for the rest of the code so\n" |
| " // it is possible to reborrow with a mutable reference.\n" |
| msgstr "" |
| "// 不可变引用在代码的剩余部分不再使用\n" |
| " // 因此可以用可变引用重新借用。\n" |
| |
| #: src/scope/borrow/alias.md:34 |
| msgid "// Change data via mutable reference\n" |
| msgstr "// 通过可变引用修改数据\n" |
| |
| #: src/scope/borrow/alias.md:39 |
| msgid "" |
| "// Error! Can't borrow `point` as immutable because it's currently\n" |
| " // borrowed as mutable.\n" |
| " // let y = &point.y;\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！不能将 `point` 作为不可变借用，因为它当前被可变借用。\n" |
| " // let y = &point.y;\n" |
| " // TODO ^ 尝试取消注释此行\n" |
| |
| #: src/scope/borrow/alias.md:44 |
| msgid "" |
| "// Error! Can't print because `println!` takes an immutable reference.\n" |
| " // println!(\"Point Z coordinate is {}\", point.z);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！无法打印，因为 `println!` 需要一个不可变引用。\n" |
| " // println!(\"点的 Z 坐标是 {}\", point.z);\n" |
| " // TODO ^ 尝试取消注释此行\n" |
| |
| #: src/scope/borrow/alias.md:48 |
| msgid "// Ok! Mutable references can be passed as immutable to `println!`\n" |
| msgstr "// 正确！可变引用可以作为不可变引用传递给 `println!`\n" |
| |
| #: src/scope/borrow/alias.md:52 |
| msgid "" |
| "// The mutable reference is no longer used for the rest of the code so it\n" |
| " // is possible to reborrow\n" |
| msgstr "// 可变引用在代码的剩余部分不再使用，所以可以重新借用\n" |
| |
| #: src/scope/borrow/alias.md:55 |
| msgid "\"Point now has coordinates: ({}, {}, {})\"" |
| msgstr "\"点现在的坐标为：({}, {}, {})\"" |
| |
| #: src/scope/borrow/ref.md:3 |
| msgid "" |
| "When doing pattern matching or destructuring via the `let` binding, the " |
| "`ref` keyword can be used to take references to the fields of a struct/" |
| "tuple. The example below shows a few instances where this can be useful:" |
| msgstr "" |
| "在使用 `let` 绑定进行模式匹配或解构时，可以使用 `ref` 关键字来获取结构体或元" |
| "组字段的引用。以下示例展示了几个这种用法有用的场景：" |
| |
| #: src/scope/borrow/ref.md:14 |
| msgid "" |
| "// A `ref` borrow on the left side of an assignment is equivalent to\n" |
| " // an `&` borrow on the right side.\n" |
| msgstr "// 赋值左侧的 `ref` 借用等同于右侧的 `&` 借用。\n" |
| |
| #: src/scope/borrow/ref.md:19 |
| msgid "\"ref_c1 equals ref_c2: {}\"" |
| msgstr "\"ref_c1 等于 ref_c2：{}\"" |
| |
| #: src/scope/borrow/ref.md:23 |
| msgid "// `ref` is also valid when destructuring a struct.\n" |
| msgstr "// 在解构结构体时，`ref` 也是有效的。\n" |
| |
| #: src/scope/borrow/ref.md:25 |
| msgid "// `ref_to_x` is a reference to the `x` field of `point`.\n" |
| msgstr "// `ref_to_x` 是 `point` 的 `x` 字段的引用。\n" |
| |
| #: src/scope/borrow/ref.md:28 |
| msgid "// Return a copy of the `x` field of `point`.\n" |
| msgstr "// 返回 `point` 的 `x` 字段的副本。\n" |
| |
| #: src/scope/borrow/ref.md:32 |
| msgid "// A mutable copy of `point`\n" |
| msgstr "// `point` 的可变副本\n" |
| |
| #: src/scope/borrow/ref.md:36 |
| msgid "// `ref` can be paired with `mut` to take mutable references.\n" |
| msgstr "// `ref` 可以与 `mut` 配合使用来获取可变引用。\n" |
| |
| #: src/scope/borrow/ref.md:39 |
| msgid "// Mutate the `y` field of `mutable_point` via a mutable reference.\n" |
| msgstr "// 通过可变引用修改 `mutable_point` 的 `y` 字段。\n" |
| |
| #: src/scope/borrow/ref.md:43 |
| msgid "\"point is ({}, {})\"" |
| msgstr "\"point 的坐标是 ({}, {})\"" |
| |
| #: src/scope/borrow/ref.md:44 |
| msgid "\"mutable_point is ({}, {})\"" |
| msgstr "\"mutable_point 的坐标是 ({}, {})\"" |
| |
| #: src/scope/borrow/ref.md:46 |
| msgid "// A mutable tuple that includes a pointer\n" |
| msgstr "// 包含指针的可变元组\n" |
| |
| #: src/scope/borrow/ref.md:50 |
| msgid "// Destructure `mutable_tuple` to change the value of `last`.\n" |
| msgstr "// 解构 `mutable_tuple` 以修改 `last` 的值。\n" |
| |
| #: src/scope/borrow/ref.md:55 |
| msgid "\"tuple is {:?}\"" |
| msgstr "\"元组是 {:?}\"" |
| |
| #: src/scope/lifetime.md:3 |
| msgid "" |
| "A _lifetime_ is a construct the compiler (or more specifically, its _borrow " |
| "checker_) uses to ensure all borrows are valid. Specifically, a variable's " |
| "lifetime begins when it is created and ends when it is destroyed. While " |
| "lifetimes and scopes are often referred to together, they are not the same." |
| msgstr "" |
| "**生命周期**是编译器（更具体地说是其**借用检查器**）用来确保所有借用都有效的" |
| "一种机制。具体来说，变量的生命周期从创建时开始，到销毁时结束。尽管生命周期和" |
| "作用域经常被一同提及，但它们并不完全相同。" |
| |
| #: src/scope/lifetime.md:8 |
| msgid "" |
| "Take, for example, the case where we borrow a variable via `&`. The borrow " |
| "has a lifetime that is determined by where it is declared. As a result, the " |
| "borrow is valid as long as it ends before the lender is destroyed. However, " |
| "the scope of the borrow is determined by where the reference is used." |
| msgstr "" |
| "举个例子，当我们通过 `&` 借用一个变量时，这个借用的生命周期由其声明位置决定。" |
| "因此，只要借用在出借者被销毁之前结束，它就是有效的。然而，借用的作用域则由引" |
| "用使用的位置决定。" |
| |
| #: src/scope/lifetime.md:13 |
| msgid "" |
| "In the following example and in the rest of this section, we will see how " |
| "lifetimes relate to scopes, as well as how the two differ." |
| msgstr "" |
| "在接下来的例子和本节的其余部分中，我们将看到生命周期如何与作用域相关联，以及" |
| "两者之间的区别。" |
| |
| #: src/scope/lifetime.md:17 |
| msgid "" |
| "// Lifetimes are annotated below with lines denoting the creation\n" |
| "// and destruction of each variable.\n" |
| "// `i` has the longest lifetime because its scope entirely encloses \n" |
| "// both `borrow1` and `borrow2`. The duration of `borrow1` compared \n" |
| "// to `borrow2` is irrelevant since they are disjoint.\n" |
| msgstr "" |
| "// 下面用线条标注了每个变量的创建和销毁，以表示生命周期。\n" |
| "// `i` 的生命周期最长，因为它的作用域完全包含了 `borrow1` 和 `borrow2`。\n" |
| "// `borrow1` 相对于 `borrow2` 的持续时间是无关紧要的，因为它们是不相交的。\n" |
| "// （译注：为避免中文的宽度显示问题，下面注释没有翻译） \n" |
| |
| #: src/scope/lifetime.md:23 |
| msgid "" |
| "// Lifetime for `i` starts. ────────────────┐\n" |
| " // │\n" |
| msgstr "" |
| "// Lifetime for `i` starts. ────────────────┐\n" |
| " // │\n" |
| |
| #: src/scope/lifetime.md:25 src/scope/lifetime.md:32 |
| msgid "// │\n" |
| msgstr "// │\n" |
| |
| #: src/scope/lifetime.md:26 |
| msgid "" |
| "// `borrow1` lifetime starts. ──┐│\n" |
| " // ││\n" |
| msgstr "" |
| "// `borrow1` lifetime starts. ──┐│\n" |
| " // ││\n" |
| |
| #: src/scope/lifetime.md:28 |
| msgid "\"borrow1: {}\"" |
| msgstr "\"borrow1: {}\"" |
| |
| #: src/scope/lifetime.md:28 src/scope/lifetime.md:35 |
| msgid "// ││\n" |
| msgstr "// ││\n" |
| |
| #: src/scope/lifetime.md:29 |
| msgid "" |
| "// `borrow1` ends. ─────────────────────────────────┘│\n" |
| " // │\n" |
| " // │\n" |
| msgstr "" |
| "// `borrow1` ends. ─────────────────────────────────┘│\n" |
| " // │\n" |
| " // │\n" |
| |
| #: src/scope/lifetime.md:33 |
| msgid "" |
| "// `borrow2` lifetime starts. ──┐│\n" |
| " // ││\n" |
| msgstr "" |
| "// `borrow2` lifetime starts. ──┐│\n" |
| " // ││\n" |
| |
| #: src/scope/lifetime.md:35 |
| msgid "\"borrow2: {}\"" |
| msgstr "\"borrow2: {}\"" |
| |
| #: src/scope/lifetime.md:36 |
| msgid "" |
| "// `borrow2` ends. ─────────────────────────────────┘│\n" |
| " // │\n" |
| msgstr "" |
| "// `borrow2` ends. ─────────────────────────────────┘│\n" |
| " // │\n" |
| |
| #: src/scope/lifetime.md:38 |
| msgid "// Lifetime ends. ─────────────────────────────────────┘\n" |
| msgstr "// Lifetime ends. ─────────────────────────────────────┘\n" |
| |
| #: src/scope/lifetime.md:41 |
| msgid "" |
| "Note that no names or types are assigned to label lifetimes. This restricts " |
| "how lifetimes will be able to be used as we will see." |
| msgstr "" |
| "请注意，生命周期标签没有被赋予名称或类型。这限制了生命周期的使用方式，我们将" |
| "在后面看到这一点。" |
| |
| #: src/scope/lifetime/explicit.md:3 |
| msgid "" |
| "The borrow checker uses explicit lifetime annotations to determine how long " |
| "references should be valid. In cases where lifetimes are not elided[^1], " |
| "Rust requires explicit annotations to determine what the lifetime of a " |
| "reference should be. The syntax for explicitly annotating a lifetime uses an " |
| "apostrophe character as follows:" |
| msgstr "" |
| "借用检查器使用显式生命周期注解来确定引用应该有效多长时间。在生命周期没有被省" |
| "略[^1]的情况下，Rust 需要显式注解来确定引用的生命周期。显式注解生命周期的语法" |
| "使用撇号字符，如下所示：" |
| |
| #: src/scope/lifetime/explicit.md:10 |
| msgid "// `foo` has a lifetime parameter `'a`\n" |
| msgstr "// `foo` 有一个生命周期参数 `'a`\n" |
| |
| #: src/scope/lifetime/explicit.md:14 |
| msgid "" |
| "Similar to [closures](../../fn/closures/anonymity.md), using lifetimes " |
| "requires generics. Additionally, this lifetime syntax indicates that the " |
| "lifetime of `foo` may not exceed that of `'a`. Explicit annotation of a type " |
| "has the form `&'a T` where `'a` has already been introduced." |
| msgstr "" |
| "类似于[闭包](../../fn/closures/anonymity.md)，使用生命周期需要泛型。此外，这" |
| "种生命周期语法表示 `foo` 的生命周期不能超过 `'a` 的生命周期。类型的显式注解形" |
| "式为 `&'a T`，其中 `'a` 已经被引入。" |
| |
| #: src/scope/lifetime/explicit.md:19 |
| msgid "In cases with multiple lifetimes, the syntax is similar:" |
| msgstr "在有多个生命周期的情况下，语法类似：" |
| |
| #: src/scope/lifetime/explicit.md:22 |
| msgid "// `foo` has lifetime parameters `'a` and `'b`\n" |
| msgstr "// `foo` 有生命周期参数 `'a` 和 `'b`\n" |
| |
| #: src/scope/lifetime/explicit.md:26 |
| msgid "" |
| "In this case, the lifetime of `foo` cannot exceed that of either `'a` _or_ " |
| "`'b`." |
| msgstr "在这种情况下，`foo` 的生命周期不能超过 `'a` **或** `'b` 的生命周期。" |
| |
| #: src/scope/lifetime/explicit.md:28 |
| msgid "See the following example for explicit lifetime annotation in use:" |
| msgstr "请看下面的例子，展示了显式生命周期注解的使用：" |
| |
| #: src/scope/lifetime/explicit.md:31 |
| msgid "" |
| "// `print_refs` takes two references to `i32` which have different\n" |
| "// lifetimes `'a` and `'b`. These two lifetimes must both be at\n" |
| "// least as long as the function `print_refs`.\n" |
| msgstr "" |
| "// `print_refs` 接受两个 `i32` 的引用，它们有不同的\n" |
| "// 生命周期 `'a` 和 `'b`。这两个生命周期都必须\n" |
| "// 至少和函数 `print_refs` 一样长。\n" |
| |
| #: src/scope/lifetime/explicit.md:35 |
| msgid "\"x is {} and y is {}\"" |
| msgstr "\"x 是 {}，y 是 {}\"" |
| |
| #: src/scope/lifetime/explicit.md:37 |
| msgid "" |
| "// A function which takes no arguments, but has a lifetime parameter `'a`.\n" |
| msgstr "// 一个没有参数但有生命周期参数 `'a` 的函数。\n" |
| |
| #: src/scope/lifetime/explicit.md:42 |
| msgid "// ERROR: `_x` does not live long enough\n" |
| msgstr "// 错误：`_x` 的生命周期不够长\n" |
| |
| #: src/scope/lifetime/explicit.md:44 |
| msgid "" |
| "// Attempting to use the lifetime `'a` as an explicit type annotation \n" |
| " // inside the function will fail because the lifetime of `&_x` is " |
| "shorter\n" |
| " // than that of `_y`. A short lifetime cannot be coerced into a longer " |
| "one.\n" |
| msgstr "" |
| "// 尝试在函数内部使用生命周期 `'a` 作为显式类型标注会失败，\n" |
| " // 因为 `&_x` 的生命周期比 `_y` 的短。\n" |
| " // 短生命周期无法强制转换为长生命周期。\n" |
| |
| #: src/scope/lifetime/explicit.md:50 |
| msgid "// Create variables to be borrowed below.\n" |
| msgstr "// 创建将要被借用的变量。\n" |
| |
| #: src/scope/lifetime/explicit.md:53 |
| msgid "// Borrows (`&`) of both variables are passed into the function.\n" |
| msgstr "// 将两个变量的借用（`&`）传递给函数。\n" |
| |
| #: src/scope/lifetime/explicit.md:55 |
| msgid "" |
| "// Any input which is borrowed must outlive the borrower. \n" |
| " // In other words, the lifetime of `four` and `nine` must \n" |
| " // be longer than that of `print_refs`.\n" |
| msgstr "" |
| "// 任何被借用的输入必须比借用者存活更久。\n" |
| " // 换句话说，`four` 和 `nine` 的生命周期必须\n" |
| " // 比 `print_refs` 的生命周期更长。\n" |
| |
| #: src/scope/lifetime/explicit.md:60 |
| msgid "" |
| "// `failed_borrow` contains no references to force `'a` to be \n" |
| " // longer than the lifetime of the function, but `'a` is longer.\n" |
| " // Because the lifetime is never constrained, it defaults to `'static`.\n" |
| msgstr "" |
| "// `failed_borrow` 不包含任何引用来强制 `'a` 比函数的生命周期更长，\n" |
| " // 但 `'a` 实际上更长。\n" |
| " // 因为生命周期从未被约束，它默认为 `'static`。\n" |
| |
| #: src/scope/lifetime/explicit.md:66 |
| msgid "" |
| "[elision](elision.md) implicitly annotates lifetimes and so is different." |
| msgstr "[省略（elision）](elision.md)隐式地注解生命周期，因此与显式注解不同。" |
| |
| #: src/scope/lifetime/explicit.md:70 |
| msgid "[generics](../../generics.md) and [closures](../../fn/closures.md)" |
| msgstr "" |
| "[泛型（generics）](../../generics.md)和[闭包（closures）](../../fn/" |
| "closures.md)" |
| |
| #: src/scope/lifetime/fn.md:3 |
| msgid "" |
| "Ignoring [elision](elision.md), function signatures with lifetimes have a " |
| "few constraints:" |
| msgstr "" |
| "排除[省略（elision）](elision.md)的情况，带有生命周期的函数签名有以下几个约" |
| "束：" |
| |
| #: src/scope/lifetime/fn.md:5 |
| msgid "any reference _must_ have an annotated lifetime." |
| msgstr "任何引用**必须**有一个标注的生命周期。" |
| |
| #: src/scope/lifetime/fn.md:6 |
| msgid "" |
| "any reference being returned _must_ have the same lifetime as an input or be " |
| "`static`." |
| msgstr "任何被返回的引用**必须**具有与输入相同的生命周期或者是 `static`。" |
| |
| #: src/scope/lifetime/fn.md:9 |
| msgid "" |
| "Additionally, note that returning references without input is banned if it " |
| "would result in returning references to invalid data. The following example " |
| "shows off some valid forms of functions with lifetimes:" |
| msgstr "" |
| "此外，请注意，如果返回引用而没有输入会导致返回指向无效数据的引用，这是被禁止" |
| "的。以下示例展示了一些带有生命周期的有效函数形式：" |
| |
| #: src/scope/lifetime/fn.md:14 |
| msgid "" |
| "// One input reference with lifetime `'a` which must live\n" |
| "// at least as long as the function.\n" |
| msgstr "// 一个具有生命周期 `'a` 的输入引用，它必须至少与函数存活一样长。\n" |
| |
| #: src/scope/lifetime/fn.md:17 |
| msgid "\"`print_one`: x is {}\"" |
| msgstr "\"`print_one`：x 是 {}\"" |
| |
| #: src/scope/lifetime/fn.md:19 |
| msgid "// Mutable references are possible with lifetimes as well.\n" |
| msgstr "// 可变引用也可以有生命周期。\n" |
| |
| #: src/scope/lifetime/fn.md:24 |
| msgid "" |
| "// Multiple elements with different lifetimes. In this case, it\n" |
| "// would be fine for both to have the same lifetime `'a`, but\n" |
| "// in more complex cases, different lifetimes may be required.\n" |
| msgstr "" |
| "// 多个具有不同生命周期的元素。在这种情况下，\n" |
| "// 两者都有相同的生命周期 `'a` 是可以的，但\n" |
| "// 在更复杂的情况下，可能需要不同的生命周期。\n" |
| |
| #: src/scope/lifetime/fn.md:29 |
| msgid "\"`print_multi`: x is {}, y is {}\"" |
| msgstr "\"`print_multi`：x 是 {}，y 是 {}\"" |
| |
| #: src/scope/lifetime/fn.md:31 |
| msgid "" |
| "// Returning references that have been passed in is acceptable.\n" |
| "// However, the correct lifetime must be returned.\n" |
| msgstr "" |
| "// 返回已传入的引用是可以接受的。\n" |
| "// 但是，必须返回正确的生命周期。\n" |
| |
| #: src/scope/lifetime/fn.md:35 |
| msgid "" |
| "//fn invalid_output<'a>() -> &'a String { &String::from(\"foo\") }\n" |
| "// The above is invalid: `'a` must live longer than the function.\n" |
| "// Here, `&String::from(\"foo\")` would create a `String`, followed by a\n" |
| "// reference. Then the data is dropped upon exiting the scope, leaving\n" |
| "// a reference to invalid data to be returned.\n" |
| msgstr "" |
| "//fn invalid_output<'a>() -> &'a String { &String::from(\"foo\") }\n" |
| "// 上面的代码是无效的：`'a` 必须比函数存活更长。\n" |
| "// 这里的 `&String::from(\"foo\")` 会创建一个 `String`，然后创建一个引用。\n" |
| "// 接着，在退出作用域时数据被丢弃，导致返回一个指向无效数据的引用。\n" |
| |
| #: src/scope/lifetime/fn.md:60 |
| msgid "[Functions](../../fn.md)" |
| msgstr "[函数](../../fn.md)" |
| |
| #: src/scope/lifetime/methods.md:3 |
| msgid "Methods are annotated similarly to functions:" |
| msgstr "方法的生命周期注解与函数类似：" |
| |
| #: src/scope/lifetime/methods.md:9 |
| msgid "// Annotate lifetimes as in a standalone function.\n" |
| msgstr "// 像独立函数一样注解生命周期。\n" |
| |
| #: src/scope/lifetime/methods.md:12 |
| msgid "\"`print`: {}\"" |
| msgstr "\"`print`：{}\"" |
| |
| #: src/scope/lifetime/methods.md:26 |
| msgid "[methods](../../fn/methods.md)" |
| msgstr "[方法](../../fn/methods.md)" |
| |
| #: src/scope/lifetime/struct.md:3 |
| msgid "Annotation of lifetimes in structures are also similar to functions:" |
| msgstr "结构体中生命周期的注解也与函数类似：" |
| |
| #: src/scope/lifetime/struct.md:6 |
| msgid "" |
| "// A type `Borrowed` which houses a reference to an\n" |
| "// `i32`. The reference to `i32` must outlive `Borrowed`.\n" |
| msgstr "" |
| "// `Borrowed` 类型包含一个 `i32` 的引用。\n" |
| "// 这个 `i32` 的引用必须比 `Borrowed` 存活更久。\n" |
| |
| #: src/scope/lifetime/struct.md:10 |
| msgid "// Similarly, both references here must outlive this structure.\n" |
| msgstr "// 同样，这里的两个引用都必须比这个结构体存活更久。\n" |
| |
| #: src/scope/lifetime/struct.md:17 |
| msgid "// An enum which is either an `i32` or a reference to one.\n" |
| msgstr "// 一个枚举，可以是 `i32`，或者是 `i32` 的引用。\n" |
| |
| #: src/scope/lifetime/struct.md:34 src/scope/lifetime/struct.md:36 |
| msgid "\"x is borrowed in {:?}\"" |
| msgstr "\"x 在 {:?} 中被借用\"" |
| |
| #: src/scope/lifetime/struct.md:35 |
| msgid "\"x and y are borrowed in {:?}\"" |
| msgstr "\"x 和 y 在 {:?} 中被借用\"" |
| |
| #: src/scope/lifetime/struct.md:37 |
| msgid "\"y is *not* borrowed in {:?}\"" |
| msgstr "\"y 在 {:?} 中**没有**被借用\"" |
| |
| #: src/scope/lifetime/struct.md:43 |
| msgid "[`struct`s](../../custom_types/structs.md)" |
| msgstr "[`struct`（结构体）](../../custom_types/structs.md)" |
| |
| #: src/scope/lifetime/trait.md:3 |
| msgid "" |
| "Annotation of lifetimes in trait methods basically are similar to functions. " |
| "Note that `impl` may have annotation of lifetimes too." |
| msgstr "" |
| "trait 方法中的生命周期注解基本上与函数类似。注意，`impl` 也可能需要生命周期注" |
| "解。" |
| |
| #: src/scope/lifetime/trait.md:7 |
| msgid "// A struct with annotation of lifetimes.\n" |
| msgstr "// 一个带有生命周期注解的结构体。\n" |
| |
| #: src/scope/lifetime/trait.md:12 |
| msgid "// Annotate lifetimes to impl.\n" |
| msgstr "// 为 impl 添加生命周期注解。\n" |
| |
| #: src/scope/lifetime/trait.md:24 |
| msgid "\"b is {:?}\"" |
| msgstr "\"b 是 {:?}\"" |
| |
| #: src/scope/lifetime/trait.md:30 |
| msgid "[`trait`s](../../trait.md)" |
| msgstr "[`trait`](../../trait.md)" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:3 |
| msgid "" |
| "Just like generic types can be bounded, lifetimes (themselves generic) use " |
| "bounds as well. The `:` character has a slightly different meaning here, but " |
| "`+` is the same. Note how the following read:" |
| msgstr "" |
| "正如泛型类型可以被约束一样，生命周期（本身也是泛型）也可以使用约束。这里的 " |
| "`:` 符号含义略有不同，但 `+` 的用法相同。请注意以下表达的含义：" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:7 |
| msgid "`T: 'a`: _All_ references in `T` must outlive lifetime `'a`." |
| msgstr "`T: 'a`：`T` 中的**所有**引用必须比生命周期 `'a` 存活更久。" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:8 |
| msgid "" |
| "`T: Trait + 'a`: Type `T` must implement trait `Trait` and _all_ references " |
| "in `T` must outlive `'a`." |
| msgstr "" |
| "`T: Trait + 'a`：类型 `T` 必须实现 trait `Trait`，并且 `T` 中的**所有**引用必" |
| "须比 `'a` 存活更久。" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:11 |
| msgid "" |
| "The example below shows the above syntax in action used after keyword " |
| "`where`:" |
| msgstr "下面的例子展示了上述语法在 `where` 关键字之后的实际应用：" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:14 |
| msgid "// Trait to bound with.\n" |
| msgstr "// 用于约束的 trait。\n" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:17 |
| msgid "" |
| "// `Ref` contains a reference to a generic type `T` that has\n" |
| "// some lifetime `'a` unknown by `Ref`. `T` is bounded such that any\n" |
| "// *references* in `T` must outlive `'a`. Additionally, the lifetime\n" |
| "// of `Ref` may not exceed `'a`.\n" |
| msgstr "" |
| "// `Ref` 包含一个指向泛型类型 `T` 的引用，`T` 具有一个 `Ref` 未知的\n" |
| "// 生命周期 `'a`。`T` 受到约束，使得 `T` 中的任何*引用*必须比 `'a` 存活更" |
| "久。\n" |
| "// 此外，`Ref` 的生命周期不能超过 `'a`。\n" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:22 |
| msgid "// A generic function which prints using the `Debug` trait.\n" |
| msgstr "// 一个使用 `Debug` trait 进行打印的泛型函数。\n" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:26 |
| msgid "\"`print`: t is {:?}\"" |
| msgstr "\"`print`: t 是 {:?}\"" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:28 |
| msgid "" |
| "// Here a reference to `T` is taken where `T` implements\n" |
| "// `Debug` and all *references* in `T` outlive `'a`. In\n" |
| "// addition, `'a` must outlive the function.\n" |
| msgstr "" |
| "// 这里取了一个 `T` 的引用，其中 `T` 实现了\n" |
| "// `Debug` 并且 `T` 中的所有*引用*都比 `'a` 存活更久。\n" |
| "// 此外，`'a` 必须比函数存活更久。\n" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:34 |
| msgid "\"`print_ref`: t is {:?}\"" |
| msgstr "\"`print_ref`: t 是 {:?}\"" |
| |
| #: src/scope/lifetime/lifetime_bounds.md:48 |
| msgid "" |
| "[generics](../../generics.md), [bounds in generics](../../generics/" |
| "bounds.md), and [multiple bounds in generics](../../generics/multi_bounds.md)" |
| msgstr "" |
| "[泛型](../../generics.md)、[泛型中的约束](../../generics/bounds.md)和[泛型中" |
| "的多重约束](../../generics/multi_bounds.md)" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:3 |
| msgid "" |
| "A longer lifetime can be coerced into a shorter one so that it works inside " |
| "a scope it normally wouldn't work in. This comes in the form of inferred " |
| "coercion by the Rust compiler, and also in the form of declaring a lifetime " |
| "difference:" |
| msgstr "" |
| "一个较长的生命周期可以被强制转换为一个较短的生命周期，使其能在通常无法工作的" |
| "作用域内工作。这种转换可以通过 Rust 编译器的推断自动完成，也可以通过声明不同" |
| "的生命周期的形式实现：" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:9 |
| msgid "" |
| "// Here, Rust infers a lifetime that is as short as possible.\n" |
| "// The two references are then coerced to that lifetime.\n" |
| msgstr "" |
| "// 在这里，Rust 推断出一个尽可能短的生命周期。\n" |
| "// 然后两个引用被强制转换为该生命周期。\n" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:14 |
| msgid "" |
| "// `<'a: 'b, 'b>` reads as lifetime `'a` is at least as long as `'b`.\n" |
| "// Here, we take in an `&'a i32` and return a `&'b i32` as a result of " |
| "coercion.\n" |
| msgstr "" |
| "// `<'a: 'b, 'b>` 表示生命周期 `'a` 至少和 `'b` 一样长。\n" |
| "// 这里，我们接收一个 `&'a i32` 并返回一个 `&'b i32` 作为强制转换的结果。\n" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:22 |
| msgid "// Longer lifetime\n" |
| msgstr "// 较长的生命周期\n" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:25 |
| msgid "// Shorter lifetime\n" |
| msgstr "// 较短的生命周期\n" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:27 |
| msgid "\"The product is {}\"" |
| msgstr "\"乘积是 {}\"" |
| |
| #: src/scope/lifetime/lifetime_coercion.md:28 |
| msgid "\"{} is the first\"" |
| msgstr "\"{} 是第一个\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:3 |
| msgid "" |
| "Rust has a few reserved lifetime names. One of those is `'static`. You might " |
| "encounter it in two situations:" |
| msgstr "" |
| "Rust 有几个保留的生命周期名称。其中之一是 `'static`。你可能在两种情况下遇到" |
| "它：" |
| |
| #: src/scope/lifetime/static_lifetime.md:7 |
| msgid "// A reference with 'static lifetime:\n" |
| msgstr "// 具有 'static 生命周期的引用：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:8 |
| msgid "\"hello world\"" |
| msgstr "\"你好，世界\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:9 |
| msgid "// 'static as part of a trait bound:\n" |
| msgstr "// 'static 作为 trait 约束的一部分：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:14 |
| msgid "" |
| "Both are related but subtly different and this is a common source for " |
| "confusion when learning Rust. Here are some examples for each situation:" |
| msgstr "" |
| "这两种情况虽然相关但有微妙的区别，这也是学习 Rust 时常见的困惑来源。以下是每" |
| "种情况的一些例子：" |
| |
| #: src/scope/lifetime/static_lifetime.md:17 |
| msgid "Reference lifetime" |
| msgstr "引用生命周期" |
| |
| #: src/scope/lifetime/static_lifetime.md:19 |
| msgid "" |
| "As a reference lifetime `'static` indicates that the data pointed to by the " |
| "reference lives for the remaining lifetime of the running program. It can " |
| "still be coerced to a shorter lifetime." |
| msgstr "" |
| "作为引用生命周期，`'static` 表示该引用指向的数据在程序的整个剩余运行期间都有" |
| "效。它仍然可以被强制转换为更短的生命周期。" |
| |
| #: src/scope/lifetime/static_lifetime.md:23 |
| msgid "" |
| "There are two common ways to make a variable with `'static` lifetime, and " |
| "both are stored in the read-only memory of the binary:" |
| msgstr "" |
| "有两种常见的方法可以创建具有 `'static` 生命周期的变量，它们都存储在二进制文件" |
| "的只读内存中：" |
| |
| #: src/scope/lifetime/static_lifetime.md:26 |
| msgid "Make a constant with the `static` declaration." |
| msgstr "使用 `static` 声明创建一个常量。" |
| |
| #: src/scope/lifetime/static_lifetime.md:27 |
| msgid "Make a `string` literal which has type: `&'static str`." |
| msgstr "创建一个字符串字面量，其类型为：`&'static str`。" |
| |
| #: src/scope/lifetime/static_lifetime.md:29 |
| msgid "See the following example for a display of each method:" |
| msgstr "请看下面的例子，展示了这些方法：" |
| |
| #: src/scope/lifetime/static_lifetime.md:32 |
| msgid "// Make a constant with `'static` lifetime.\n" |
| msgstr "// 创建一个具有 `'static` 生命周期的常量。\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:34 |
| msgid "" |
| "// Returns a reference to `NUM` where its `'static`\n" |
| "// lifetime is coerced to that of the input argument.\n" |
| msgstr "" |
| "// 返回一个指向 `NUM` 的引用，其中 `'static` 生命周期\n" |
| "// 被强制转换为输入参数的生命周期。\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:43 |
| msgid "// Make a `string` literal and print it:\n" |
| msgstr "// 创建一个字符串字面量并打印它：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:44 |
| msgid "\"I'm in read-only memory\"" |
| msgstr "\"我存储在只读内存中\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:45 |
| msgid "\"static_string: {}\"" |
| msgstr "\"static_string 的值：{}\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:47 |
| msgid "" |
| "// When `static_string` goes out of scope, the reference\n" |
| " // can no longer be used, but the data remains in the binary.\n" |
| msgstr "" |
| "// 当 `static_string` 离开作用域时，该引用\n" |
| " // 不能再被使用，但数据仍然保留在二进制文件中。\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:52 |
| msgid "// Make an integer to use for `coerce_static`:\n" |
| msgstr "// 创建一个整数用于 `coerce_static` 函数：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:55 |
| msgid "// Coerce `NUM` to lifetime of `lifetime_num`:\n" |
| msgstr "// 将 `NUM` 的生命周期强制转换为与 `lifetime_num` 一致：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:58 |
| msgid "\"coerced_static: {}\"" |
| msgstr "\"coerced_static: {}\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:61 |
| msgid "\"NUM: {} stays accessible!\"" |
| msgstr "\"NUM：{} 仍然可以访问！\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:65 |
| msgid "" |
| "Since `'static` references only need to be valid for the _remainder_ of a " |
| "program's life, they can be created while the program is executed. Just to " |
| "demonstrate, the below example uses [`Box::leak`](https://doc.rust-lang.org/" |
| "std/boxed/struct.Box.html#method.leak) to dynamically create `'static` " |
| "references. In that case it definitely doesn't live for the entire duration, " |
| "but only from the leaking point onward." |
| msgstr "" |
| "`'static` 引用只需在程序生命周期的**剩余部分**有效，因此可以在程序执行过程中" |
| "创建。为了演示这一点，下面的例子使用 [`Box::leak`](https://doc.rust-lang.org/" |
| "std/boxed/struct.Box.html#method.leak) 动态创建 `'static` 引用。在这种情况" |
| "下，它显然不会存在于整个程序生命周期，而只是从泄漏点开始存在。" |
| |
| #: src/scope/lifetime/static_lifetime.md:90 |
| msgid "Trait bound" |
| msgstr "Trait 约束" |
| |
| #: src/scope/lifetime/static_lifetime.md:92 |
| msgid "" |
| "As a trait bound, it means the type does not contain any non-static " |
| "references. Eg. the receiver can hold on to the type for as long as they " |
| "want and it will never become invalid until they drop it." |
| msgstr "" |
| "作为 trait 约束时，它表示该类型不包含任何非静态引用。例如，接收者可以随意持有" |
| "该类型，直到主动丢弃之前，它都不会变为无效。" |
| |
| #: src/scope/lifetime/static_lifetime.md:96 |
| msgid "" |
| "It's important to understand this means that any owned data always passes a " |
| "`'static` lifetime bound, but a reference to that owned data generally does " |
| "not:" |
| msgstr "" |
| "理解这一点很重要：任何拥有所有权的数据总是满足 `'static` 生命周期约束，但对该" |
| "数据的引用通常不满足：" |
| |
| #: src/scope/lifetime/static_lifetime.md:104 |
| msgid "\"'static value passed in is: {:?}\"" |
| msgstr "\"传入的 'static 值是：{:?}\"" |
| |
| #: src/scope/lifetime/static_lifetime.md:108 |
| msgid "// i is owned and contains no references, thus it's 'static:\n" |
| msgstr "// i 拥有所有权且不包含任何引用，因此它是 'static 的：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:112 |
| msgid "" |
| "// oops, &i only has the lifetime defined by the scope of\n" |
| " // main(), so it's not 'static:\n" |
| msgstr "" |
| "// 糟糕，&i 的生命周期仅由 main() 的作用域定义，\n" |
| " // 所以它不是 'static 的：\n" |
| |
| #: src/scope/lifetime/static_lifetime.md:118 |
| msgid "The compiler will tell you:" |
| msgstr "编译器会提示你：" |
| |
| #: src/scope/lifetime/static_lifetime.md:135 |
| msgid "[`'static` constants](../../custom_types/constants.md)" |
| msgstr "[`'static` 常量](../../custom_types/constants.md)" |
| |
| #: src/scope/lifetime/elision.md:3 |
| msgid "" |
| "Some lifetime patterns are overwhelmingly common and so the borrow checker " |
| "will allow you to omit them to save typing and to improve readability. This " |
| "is known as elision. Elision exists in Rust solely because these patterns " |
| "are common." |
| msgstr "" |
| "有些生命周期模式非常常见，因此借用检查器允许省略它们以减少代码量并提高可读" |
| "性。这被称为省略。Rust 中的省略存在的唯一原因是这些模式很常见。" |
| |
| #: src/scope/lifetime/elision.md:8 |
| msgid "" |
| "The following code shows a few examples of elision. For a more comprehensive " |
| "description of elision, see [lifetime elision](https://doc.rust-lang.org/" |
| "book/ch10-03-lifetime-syntax.html#lifetime-elision) in the book." |
| msgstr "" |
| "以下代码展示了一些省略的例子。要更全面地了解省略，请参阅 Rust 程序设计语言中" |
| "的[生命周期省略](https://doc.rust-lang.org/book/ch10-03-lifetime-" |
| "syntax.html#lifetime-elision)章节。" |
| |
| #: src/scope/lifetime/elision.md:12 |
| msgid "" |
| "// `elided_input` and `annotated_input` essentially have identical " |
| "signatures\n" |
| "// because the lifetime of `elided_input` is inferred by the compiler:\n" |
| msgstr "" |
| "// `elided_input` 和 `annotated_input` 本质上具有相同的签名\n" |
| "// 因为 `elided_input` 的生命周期是由编译器推断的：\n" |
| |
| #: src/scope/lifetime/elision.md:15 |
| msgid "\"`elided_input`: {}\"" |
| msgstr "\"`elided_input`: {}\"" |
| |
| #: src/scope/lifetime/elision.md:19 |
| msgid "\"`annotated_input`: {}\"" |
| msgstr "\"`annotated_input`: {}\"" |
| |
| #: src/scope/lifetime/elision.md:21 |
| msgid "" |
| "// Similarly, `elided_pass` and `annotated_pass` have identical signatures\n" |
| "// because the lifetime is added implicitly to `elided_pass`:\n" |
| msgstr "" |
| "// 同样，`elided_pass` 和 `annotated_pass` 具有相同的签名\n" |
| "// 因为生命周期被隐式地添加到 `elided_pass`：\n" |
| |
| #: src/scope/lifetime/elision.md:34 |
| msgid "\"`elided_pass`: {}\"" |
| msgstr "\"`elided_pass`: {}\"" |
| |
| #: src/scope/lifetime/elision.md:35 |
| msgid "\"`annotated_pass`: {}\"" |
| msgstr "\"`annotated_pass`: {}\"" |
| |
| #: src/scope/lifetime/elision.md:41 |
| msgid "" |
| "[elision](https://doc.rust-lang.org/book/ch10-03-lifetime-" |
| "syntax.html#lifetime-elision)" |
| msgstr "" |
| "[省略](https://doc.rust-lang.org/book/ch10-03-lifetime-syntax.html#lifetime-" |
| "elision)" |
| |
| #: src/trait.md:3 |
| msgid "" |
| "A `trait` is a collection of methods defined for an unknown type: `Self`. " |
| "They can access other methods declared in the same trait." |
| msgstr "" |
| "`trait` 是为未知类型 `Self` 定义的一组方法集合。这些方法可以访问同一 trait 中" |
| "声明的其他方法。" |
| |
| #: src/trait.md:6 |
| msgid "" |
| "Traits can be implemented for any data type. In the example below, we define " |
| "`Animal`, a group of methods. The `Animal` `trait` is then implemented for " |
| "the `Sheep` data type, allowing the use of methods from `Animal` with a " |
| "`Sheep`." |
| msgstr "" |
| "trait 可以为任何数据类型实现。在下面的例子中，我们定义了 `Animal`，一组方法的" |
| "集合。然后为 `Sheep` 数据类型实现 `Animal` trait，这样就可以对 `Sheep` 使用 " |
| "`Animal` 中的方法。" |
| |
| #: src/trait.md:15 |
| msgid "" |
| "// Associated function signature; `Self` refers to the implementor type.\n" |
| msgstr "// 关联函数签名；`Self` 指代实现者类型。\n" |
| |
| #: src/trait.md:18 |
| msgid "// Method signatures; these will return a string.\n" |
| msgstr "// 方法签名；这些方法将返回一个字符串。\n" |
| |
| #: src/trait.md:22 |
| msgid "// Traits can provide default method definitions.\n" |
| msgstr "// trait 可以提供默认的方法实现。\n" |
| |
| #: src/trait.md:24 |
| msgid "\"{} says {}\"" |
| msgstr "\"{} 说 {}\"" |
| |
| #: src/trait.md:35 |
| msgid "// Implementor methods can use the implementor's trait methods.\n" |
| msgstr "// 实现者的方法可以使用实现者的 trait 方法。\n" |
| |
| #: src/trait.md:36 |
| msgid "\"{} is already naked...\"" |
| msgstr "\"{} 已经剃过毛了...\"" |
| |
| #: src/trait.md:38 |
| msgid "\"{} gets a haircut!\"" |
| msgstr "\"{} 剃了个毛！\"" |
| |
| #: src/trait.md:44 src/trait/dyn.md:25 |
| msgid "// Implement the `Animal` trait for `Sheep`.\n" |
| msgstr "// 为 `Sheep` 实现 `Animal` trait\n" |
| |
| #: src/trait.md:47 |
| msgid "// `Self` is the implementor type: `Sheep`.\n" |
| msgstr "// `Self` 是实现者类型，即 `Sheep`\n" |
| |
| #: src/trait.md:58 |
| msgid "\"baaaaah?\"" |
| msgstr "\"咩～？\"" |
| |
| #: src/trait.md:60 src/trait/dyn.md:29 |
| msgid "\"baaaaah!\"" |
| msgstr "\"咩～！\"" |
| |
| #: src/trait.md:64 |
| msgid "// Default trait methods can be overridden.\n" |
| msgstr "// 可以重写默认的 trait 方法\n" |
| |
| #: src/trait.md:66 |
| msgid "// For example, we can add some quiet contemplation.\n" |
| msgstr "// 例如，我们可以添加一些安静的思考\n" |
| |
| #: src/trait.md:67 |
| msgid "\"{} pauses briefly... {}\"" |
| msgstr "\"{} 短暂停顿…… {}\"" |
| |
| #: src/trait.md:72 |
| msgid "// Type annotation is necessary in this case.\n" |
| msgstr "// 在这种情况下需要类型标注\n" |
| |
| #: src/trait.md:73 |
| msgid "\"Dolly\"" |
| msgstr "\"多莉\"" |
| |
| #: src/trait.md:74 |
| msgid "// TODO ^ Try removing the type annotations.\n" |
| msgstr "// TODO ^ 尝试移除类型标注\n" |
| |
| #: src/trait/derive.md:3 |
| msgid "" |
| "The compiler is capable of providing basic implementations for some traits " |
| "via the `#[derive]` [attribute](../attribute.md). These traits can still be " |
| "manually implemented if a more complex behavior is required." |
| msgstr "" |
| "编译器可以通过 `#[derive]` [属性](../attribute.md)为某些 trait 提供基本实现。" |
| "如果需要更复杂的行为，这些 trait 仍然可以手动实现。" |
| |
| #: src/trait/derive.md:7 |
| msgid "The following is a list of derivable traits:" |
| msgstr "以下是可派生的 trait 列表：" |
| |
| #: src/trait/derive.md:9 |
| msgid "" |
| "Comparison traits: [`Eq`](https://doc.rust-lang.org/std/cmp/trait.Eq.html), " |
| "[`PartialEq`](https://doc.rust-lang.org/std/cmp/trait.PartialEq.html), " |
| "[`Ord`](https://doc.rust-lang.org/std/cmp/trait.Ord.html), [`PartialOrd`]" |
| "(https://doc.rust-lang.org/std/cmp/trait.PartialOrd.html)." |
| msgstr "" |
| "比较 trait：[`Eq`](https://doc.rust-lang.org/std/cmp/trait.Eq.html)、" |
| "[`PartialEq`](https://doc.rust-lang.org/std/cmp/trait.PartialEq.html)、" |
| "[`Ord`](https://doc.rust-lang.org/std/cmp/trait.Ord.html)、[`PartialOrd`]" |
| "(https://doc.rust-lang.org/std/cmp/trait.PartialOrd.html)。" |
| |
| #: src/trait/derive.md:11 |
| msgid "" |
| "[`Clone`](https://doc.rust-lang.org/std/clone/trait.Clone.html), to create " |
| "`T` from `&T` via a copy." |
| msgstr "" |
| "[`Clone`](https://doc.rust-lang.org/std/clone/trait.Clone.html)，通过复制 " |
| "`&T` 创建 `T`。" |
| |
| #: src/trait/derive.md:12 |
| msgid "" |
| "[`Copy`](https://doc.rust-lang.org/core/marker/trait.Copy.html), to give a " |
| "type 'copy semantics' instead of 'move semantics'." |
| msgstr "" |
| "[`Copy`](https://doc.rust-lang.org/core/marker/trait.Copy.html)，使类型具备" |
| "\"复制语义\"而不是\"移动语义\"。" |
| |
| #: src/trait/derive.md:13 |
| msgid "" |
| "[`Hash`](https://doc.rust-lang.org/std/hash/trait.Hash.html), to compute a " |
| "hash from `&T`." |
| msgstr "" |
| "[`Hash`](https://doc.rust-lang.org/std/hash/trait.Hash.html)，从 `&T` 计算哈" |
| "希值。" |
| |
| #: src/trait/derive.md:14 |
| msgid "" |
| "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html), to " |
| "create an empty instance of a data type." |
| msgstr "" |
| "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html)，创建一" |
| "个数据类型的空实例。" |
| |
| #: src/trait/derive.md:15 |
| msgid "" |
| "[`Debug`](https://doc.rust-lang.org/std/fmt/trait.Debug.html), to format a " |
| "value using the `{:?}` formatter." |
| msgstr "" |
| "[`Debug`](https://doc.rust-lang.org/std/fmt/trait.Debug.html)，使用 `{:?}` 格" |
| "式化器来格式化一个值。" |
| |
| #: src/trait/derive.md:18 |
| msgid "// `Centimeters`, a tuple struct that can be compared\n" |
| msgstr "// `Centimeters`，一个可比较的元组结构体\n" |
| |
| #: src/trait/derive.md:21 |
| msgid "// `Inches`, a tuple struct that can be printed\n" |
| msgstr "// `Inches`，一个可打印的元组结构体\n" |
| |
| #: src/trait/derive.md:33 |
| msgid "// `Seconds`, a tuple struct with no additional attributes\n" |
| msgstr "// `Seconds`，一个没有额外属性的元组结构体\n" |
| |
| #: src/trait/derive.md:40 |
| msgid "" |
| "// Error: `Seconds` can't be printed; it doesn't implement the `Debug` " |
| "trait\n" |
| " //println!(\"One second looks like: {:?}\", _one_second);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误：`Seconds` 无法打印，因为它没有实现 `Debug` trait\n" |
| " //println!(\"One second looks like: {:?}\", _one_second);\n" |
| " // TODO ^ 尝试取消这行的注释\n" |
| |
| #: src/trait/derive.md:44 |
| msgid "" |
| "// Error: `Seconds` can't be compared; it doesn't implement the `PartialEq` " |
| "trait\n" |
| " //let _this_is_true = (_one_second == _one_second);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误：`Seconds` 无法比较，因为它没有实现 `PartialEq` trait\n" |
| " //let _this_is_true = (_one_second == _one_second);\n" |
| " // TODO ^ 尝试取消这行的注释\n" |
| |
| #: src/trait/derive.md:50 |
| msgid "\"One foot equals {:?}\"" |
| msgstr "\"一英尺等于 {:?}\"" |
| |
| #: src/trait/derive.md:56 |
| msgid "\"smaller\"" |
| msgstr "\"更小\"" |
| |
| #: src/trait/derive.md:58 |
| msgid "\"bigger\"" |
| msgstr "\"更大\"" |
| |
| #: src/trait/derive.md:61 |
| msgid "\"One foot is {} than one meter.\"" |
| msgstr "\"一英尺比一米{}\"" |
| |
| #: src/trait/derive.md:67 |
| msgid "[`derive`](https://doc.rust-lang.org/reference/attributes.html#derive)" |
| msgstr "[`derive`](https://doc.rust-lang.org/reference/attributes.html#derive)" |
| |
| #: src/trait/dyn.md:3 |
| msgid "" |
| "The Rust compiler needs to know how much space every function's return type " |
| "requires. This means all your functions have to return a concrete type. " |
| "Unlike other languages, if you have a trait like `Animal`, you can't write a " |
| "function that returns `Animal`, because its different implementations will " |
| "need different amounts of memory." |
| msgstr "" |
| "Rust 编译器需要知道每个函数的返回类型所需的内存空间。这意味着所有函数都必须返" |
| "回一个具体类型。与其他语言不同，如果你有一个像 `Animal` 这样的 trait，你不能" |
| "编写一个直接返回 `Animal` 的函数，因为它的不同实现可能需要不同大小的内存。" |
| |
| #: src/trait/dyn.md:8 |
| msgid "" |
| "However, there's an easy workaround. Instead of returning a trait object " |
| "directly, our functions return a `Box` which _contains_ some `Animal`. A " |
| "`box` is just a reference to some memory in the heap. Because a reference " |
| "has a statically-known size, and the compiler can guarantee it points to a " |
| "heap-allocated `Animal`, we can return a trait from our function!" |
| msgstr "" |
| "然而，有一个简单的解决方法。我们可以让函数返回一个**包含** `Animal` 的 " |
| "`Box`，而不是直接返回 trait 对象。`Box` 本质上是一个指向堆内存的引用。由于引" |
| "用的大小是静态已知的，且编译器可以保证它指向堆上分配的 `Animal`，这样我们就能" |
| "从函数中返回一个 trait 了！" |
| |
| #: src/trait/dyn.md:13 |
| msgid "" |
| "Rust tries to be as explicit as possible whenever it allocates memory on the " |
| "heap. So if your function returns a pointer-to-trait-on-heap in this way, " |
| "you need to write the return type with the `dyn` keyword, e.g. `Box<dyn " |
| "Animal>`." |
| msgstr "" |
| "Rust 在堆上分配内存时力求明确。因此，如果你的函数以这种方式返回一个指向堆上 " |
| "trait 的指针，你需要在返回类型中使用 `dyn` 关键字，例如 `Box<dyn Animal>`。" |
| |
| #: src/trait/dyn.md:22 |
| msgid "// Instance method signature\n" |
| msgstr "// 实例方法签名\n" |
| |
| #: src/trait/dyn.md:32 |
| msgid "// Implement the `Animal` trait for `Cow`.\n" |
| msgstr "// 为 `Cow` 实现 `Animal` trait\n" |
| |
| #: src/trait/dyn.md:36 |
| msgid "\"moooooo!\"" |
| msgstr "\"哞~哞~哞~\"" |
| |
| #: src/trait/dyn.md:39 |
| msgid "" |
| "// Returns some struct that implements Animal, but we don't know which one " |
| "at compile time.\n" |
| msgstr "" |
| "// 返回某个实现了 Animal 的结构体，但在编译时我们并不知道具体是哪一个\n" |
| |
| #: src/trait/dyn.md:52 |
| msgid "\"You've randomly chosen an animal, and it says {}\"" |
| msgstr "\"你随机选择了一个动物，它说：{}\"" |
| |
| #: src/trait/ops.md:3 |
| msgid "" |
| "In Rust, many of the operators can be overloaded via traits. That is, some " |
| "operators can be used to accomplish different tasks based on their input " |
| "arguments. This is possible because operators are syntactic sugar for method " |
| "calls. For example, the `+` operator in `a + b` calls the `add` method (as " |
| "in `a.add(b)`). This `add` method is part of the `Add` trait. Hence, the `+` " |
| "operator can be used by any implementor of the `Add` trait." |
| msgstr "" |
| "在 Rust 中，许多运算符可以通过 trait 进行重载。这意味着某些运算符可以根据输入" |
| "参数执行不同的任务。之所以可能，是因为运算符实际上是方法调用的语法糖。例如，" |
| "`a + b` 中的 `+` 运算符会调用 `add` 方法（相当于 `a.add(b)`）。这个 `add` 方" |
| "法是 `Add` trait 的一部分。因此，任何实现了 `Add` trait 的类型都可以使用 `+` " |
| "运算符。" |
| |
| #: src/trait/ops.md:9 |
| msgid "" |
| "A list of the traits, such as `Add`, that overload operators can be found in " |
| "[`core::ops`](https://doc.rust-lang.org/core/ops/)." |
| msgstr "" |
| "可以在 [`core::ops`](https://doc.rust-lang.org/core/ops/) 模块中找到用于重载" |
| "运算符的 trait 列表，如 `Add` 等。" |
| |
| #: src/trait/ops.md:22 |
| msgid "" |
| "// The `std::ops::Add` trait is used to specify the functionality of `+`.\n" |
| "// Here, we make `Add<Bar>` - the trait for addition with a RHS of type " |
| "`Bar`.\n" |
| "// The following block implements the operation: Foo + Bar = FooBar\n" |
| msgstr "" |
| "// `std::ops::Add` trait 用于指定 `+` 的功能\n" |
| "// 这里我们实现 `Add<Bar>` - 这个 trait 用于与 `Bar` 类型的右操作数相加\n" |
| "// 下面的代码块实现了操作：Foo + Bar = FooBar\n" |
| |
| #: src/trait/ops.md:30 |
| msgid "\"> Foo.add(Bar) was called\"" |
| msgstr "\"> 调用了 Foo.add(Bar)\"" |
| |
| #: src/trait/ops.md:35 |
| msgid "" |
| "// By reversing the types, we end up implementing non-commutative addition.\n" |
| "// Here, we make `Add<Foo>` - the trait for addition with a RHS of type " |
| "`Foo`.\n" |
| "// This block implements the operation: Bar + Foo = BarFoo\n" |
| msgstr "" |
| "// 通过交换类型顺序，我们实现了非交换加法。\n" |
| "// 这里我们实现 `Add<Foo>` trait —— 用于处理右操作数类型为 `Foo` 的加法。\n" |
| "// 此代码块实现了如下操作：Bar + Foo = BarFoo\n" |
| |
| #: src/trait/ops.md:43 |
| msgid "\"> Bar.add(Foo) was called\"" |
| msgstr "\"> 调用了 Bar.add(Foo)\"" |
| |
| #: src/trait/ops.md:50 |
| msgid "\"Foo + Bar = {:?}\"" |
| msgstr "\"Foo + Bar = {:?}\"" |
| |
| #: src/trait/ops.md:51 |
| msgid "\"Bar + Foo = {:?}\"" |
| msgstr "\"Bar + Foo = {:?}\"" |
| |
| #: src/trait/ops.md:55 src/testing.md:16 src/testing/doc_testing.md:105 |
| #: src/testing/dev_dependencies.md:36 |
| msgid "See Also" |
| msgstr "参见" |
| |
| #: src/trait/ops.md:57 |
| msgid "" |
| "[Add](https://doc.rust-lang.org/core/ops/trait.Add.html), [Syntax Index]" |
| "(https://doc.rust-lang.org/book/appendix-02-operators.html)" |
| msgstr "" |
| "[Add](https://doc.rust-lang.org/core/ops/trait.Add.html)，[语法索引](https://" |
| "doc.rust-lang.org/book/appendix-02-operators.html)" |
| |
| #: src/trait/drop.md:3 |
| msgid "" |
| "The [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) trait only " |
| "has one method: `drop`, which is called automatically when an object goes " |
| "out of scope. The main use of the `Drop` trait is to free the resources that " |
| "the implementor instance owns." |
| msgstr "" |
| "[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) trait 只有一个方" |
| "法：`drop`，它会在对象离开作用域时自动调用。`Drop` trait 的主要用途是释放实现" |
| "该 trait 的实例所拥有的资源。" |
| |
| #: src/trait/drop.md:7 |
| msgid "" |
| "`Box`, `Vec`, `String`, `File`, and `Process` are some examples of types " |
| "that implement the `Drop` trait to free resources. The `Drop` trait can also " |
| "be manually implemented for any custom data type." |
| msgstr "" |
| "`Box`、`Vec`、`String`、`File` 和 `Process` 是一些实现了 `Drop` trait 以释放" |
| "资源的类型示例。你也可以为任何自定义数据类型手动实现 `Drop` trait。" |
| |
| #: src/trait/drop.md:11 |
| msgid "" |
| "The following example adds a print to console to the `drop` function to " |
| "announce when it is called." |
| msgstr "" |
| "下面的例子在 `drop` 函数中添加了一个控制台打印，用于宣告它被调用的时机。" |
| |
| #: src/trait/drop.md:18 |
| msgid "// This trivial implementation of `drop` adds a print to console.\n" |
| msgstr "// 这个简单的 `drop` 实现添加了一个控制台打印\n" |
| |
| #: src/trait/drop.md:22 |
| msgid "\"> Dropping {}\"" |
| msgstr "\"> 正在释放 {}\"" |
| |
| #: src/trait/drop.md:27 src/std_misc/path.md:33 src/std_misc/fs.md:44 |
| #: src/std_misc/fs.md:87 |
| msgid "\"a\"" |
| msgstr "\"a\"" |
| |
| #: src/trait/drop.md:29 |
| msgid "// block A\n" |
| msgstr "// 块 A\n" |
| |
| #: src/trait/drop.md:31 src/std_misc/path.md:33 |
| msgid "\"b\"" |
| msgstr "\"b\"" |
| |
| #: src/trait/drop.md:33 |
| msgid "// block B\n" |
| msgstr "// 块 B\n" |
| |
| #: src/trait/drop.md:35 src/std_misc/path.md:36 |
| msgid "\"c\"" |
| msgstr "\"c\"" |
| |
| #: src/trait/drop.md:36 |
| msgid "\"d\"" |
| msgstr "\"d\"" |
| |
| #: src/trait/drop.md:38 |
| msgid "\"Exiting block B\"" |
| msgstr "\"正在退出块 B\"" |
| |
| #: src/trait/drop.md:40 |
| msgid "\"Just exited block B\"" |
| msgstr "\"刚刚退出了块 B\"" |
| |
| #: src/trait/drop.md:42 |
| msgid "\"Exiting block A\"" |
| msgstr "\"正在退出块 A\"" |
| |
| #: src/trait/drop.md:44 |
| msgid "\"Just exited block A\"" |
| msgstr "\"刚刚退出了块 A\"" |
| |
| #: src/trait/drop.md:46 |
| msgid "// Variable can be manually dropped using the `drop` function\n" |
| msgstr "// 可以使用 `drop` 函数手动释放变量\n" |
| |
| #: src/trait/drop.md:48 |
| msgid "// TODO ^ Try commenting this line\n" |
| msgstr "// TODO ^ 试试注释掉这一行\n" |
| |
| #: src/trait/drop.md:50 |
| msgid "\"end of the main function\"" |
| msgstr "\"main 函数结束\"" |
| |
| #: src/trait/drop.md:52 |
| msgid "" |
| "// `_a` *won't* be `drop`ed again here, because it already has been\n" |
| " // (manually) `drop`ed\n" |
| msgstr "" |
| "// `_a` 在这里**不会**被再次 `drop`，因为它已经\n" |
| " // 被（手动）`drop` 过了\n" |
| |
| #: src/trait/drop.md:57 |
| msgid "" |
| "For a more practical example, here's how the `Drop` trait can be used to " |
| "automatically clean up temporary files when they're no longer needed:" |
| msgstr "" |
| "下面是一个更实用的例子，展示如何使用 `Drop` 特质在不再需要临时文件时自动清理" |
| "它们：" |
| |
| #: src/trait/drop.md:71 |
| msgid "// Note: File::create() will overwrite existing files\n" |
| msgstr "// 注意：File::create() 会覆盖现有文件\n" |
| |
| #: src/trait/drop.md:77 |
| msgid "" |
| "// When TempFile is dropped:\n" |
| "// 1. First, the File will be automatically closed (Drop for File)\n" |
| "// 2. Then our drop implementation will remove the file\n" |
| msgstr "" |
| "// 当 TempFile 被丢弃时：\n" |
| "// 1. 首先，File 会自动关闭（File 的 Drop 实现）\n" |
| "// 2. 然后我们的 drop 实现会删除文件\n" |
| |
| #: src/trait/drop.md:83 |
| msgid "// Note: File is already closed at this point\n" |
| msgstr "// 注意：文件在此时已经关闭\n" |
| |
| #: src/trait/drop.md:85 |
| msgid "\"Failed to remove temporary file: {}\"" |
| msgstr "\"删除临时文件失败：{}\"" |
| |
| #: src/trait/drop.md:87 |
| msgid "\"> Dropped temporary file: {:?}\"" |
| msgstr "\"> 已丢弃临时文件：{:?}\"" |
| |
| #: src/trait/drop.md:92 |
| msgid "// Create a new scope to demonstrate drop behavior\n" |
| msgstr "// 创建新作用域来演示丢弃行为\n" |
| |
| #: src/trait/drop.md:94 |
| msgid "\"test.txt\"" |
| msgstr "\"test.txt\"" |
| |
| #: src/trait/drop.md:95 |
| msgid "\"Temporary file created\"" |
| msgstr "\"已创建临时文件\"" |
| |
| #: src/trait/drop.md:96 |
| msgid "// File will be automatically cleaned up when temp goes out of scope\n" |
| msgstr "// 当 temp 超出作用域时，文件会自动清理\n" |
| |
| #: src/trait/drop.md:98 |
| msgid "\"End of scope - file should be cleaned up\"" |
| msgstr "\"作用域结束 - 文件应该被清理\"" |
| |
| #: src/trait/drop.md:100 |
| msgid "// We can also manually drop if needed\n" |
| msgstr "// 如果需要，我们也可以手动丢弃\n" |
| |
| #: src/trait/drop.md:101 |
| msgid "\"another_test.txt\"" |
| msgstr "\"another_test.txt\"" |
| |
| #: src/trait/drop.md:102 |
| msgid "// Explicitly drop the file\n" |
| msgstr "// 显式丢弃文件\n" |
| |
| #: src/trait/drop.md:103 |
| msgid "\"Manually dropped file\"" |
| msgstr "\"手动丢弃的文件\"" |
| |
| #: src/trait/iter.md:3 |
| msgid "" |
| "The [`Iterator`](https://doc.rust-lang.org/core/iter/trait.Iterator.html) " |
| "trait is used to implement iterators over collections such as arrays." |
| msgstr "" |
| "[`Iterator`](https://doc.rust-lang.org/core/iter/trait.Iterator.html) trait " |
| "用于实现对数组等集合的迭代器。" |
| |
| #: src/trait/iter.md:6 |
| msgid "" |
| "The trait requires only a method to be defined for the `next` element, which " |
| "may be manually defined in an `impl` block or automatically defined (as in " |
| "arrays and ranges)." |
| msgstr "" |
| "该 trait 只要求为 `next` 元素定义一个方法，这个方法可以在 `impl` 块中手动定" |
| "义，也可以自动定义（如在数组和区间中）。" |
| |
| #: src/trait/iter.md:10 |
| msgid "" |
| "As a point of convenience for common situations, the `for` construct turns " |
| "some collections into iterators using the [`.into_iter()`](https://doc.rust-" |
| "lang.org/std/iter/trait.IntoIterator.html) method." |
| msgstr "" |
| "为了在常见情况下提供便利，`for` 结构使用 [`.into_iter()`](https://doc.rust-" |
| "lang.org/std/iter/trait.IntoIterator.html) 方法将某些集合转换为迭代器。" |
| |
| #: src/trait/iter.md:18 |
| msgid "" |
| "// Implement `Iterator` for `Fibonacci`.\n" |
| "// The `Iterator` trait only requires a method to be defined for the `next` " |
| "element,\n" |
| "// and an `associated type` to declare the return type of the iterator.\n" |
| msgstr "" |
| "// 为 `Fibonacci` 实现 `Iterator`。\n" |
| "// `Iterator` 特质只要求为 `next` 元素定义一个方法，\n" |
| "// 并需要一个`关联类型`来声明迭代器的返回类型。\n" |
| |
| #: src/trait/iter.md:23 |
| msgid "// We can refer to this type using Self::Item\n" |
| msgstr "// 我们可以使用 Self::Item 引用这个类型\n" |
| |
| #: src/trait/iter.md:26 |
| msgid "" |
| "// Here, we define the sequence using `.curr` and `.next`.\n" |
| " // The return type is `Option<T>`:\n" |
| " // * When the `Iterator` is finished, `None` is returned.\n" |
| " // * Otherwise, the next value is wrapped in `Some` and returned.\n" |
| " // We use Self::Item in the return type, so we can change\n" |
| " // the type without having to update the function signatures.\n" |
| msgstr "" |
| "// 这里，我们使用 `.curr` 和 `.next` 定义序列。\n" |
| " // 返回类型是 `Option<T>`：\n" |
| " // * 当 `Iterator` 结束时，返回 `None`。\n" |
| " // * 否则，将下一个值包装在 `Some` 中并返回。\n" |
| " // 我们在返回类型中使用 Self::Item，这样可以更改\n" |
| " // 类型而无需更新函数签名。\n" |
| |
| #: src/trait/iter.md:38 |
| msgid "" |
| "// Since there's no endpoint to a Fibonacci sequence, the `Iterator` \n" |
| " // will never return `None`, and `Some` is always returned.\n" |
| msgstr "" |
| "// 由于斐波那契序列没有终点，`Iterator` \n" |
| " // 永远不会返回 `None`，始终返回 `Some`。\n" |
| |
| #: src/trait/iter.md:43 |
| msgid "// Returns a Fibonacci sequence generator\n" |
| msgstr "// 返回一个斐波那契序列生成器\n" |
| |
| #: src/trait/iter.md:50 |
| msgid "// `0..3` is an `Iterator` that generates: 0, 1, and 2.\n" |
| msgstr "// `0..3` 是一个生成 0、1 和 2 的 `Iterator`。\n" |
| |
| #: src/trait/iter.md:53 |
| msgid "\"Four consecutive `next` calls on 0..3\"" |
| msgstr "\"对 0..3 连续调用四次 `next`\"" |
| |
| #: src/trait/iter.md:54 src/trait/iter.md:55 src/trait/iter.md:56 |
| #: src/trait/iter.md:57 src/std_misc/fs.md:90 |
| msgid "\"> {:?}\"" |
| msgstr "\"> {:?}\"" |
| |
| #: src/trait/iter.md:59 |
| msgid "" |
| "// `for` works through an `Iterator` until it returns `None`.\n" |
| " // Each `Some` value is unwrapped and bound to a variable (here, `i`).\n" |
| msgstr "" |
| "// `for` 遍历 `Iterator` 直到它返回 `None`。\n" |
| " // 每个 `Some` 值被解包并绑定到一个变量（这里是 `i`）。\n" |
| |
| #: src/trait/iter.md:61 |
| msgid "\"Iterate through 0..3 using `for`\"" |
| msgstr "\"使用 `for` 遍历 0..3\"" |
| |
| #: src/trait/iter.md:63 src/trait/iter.md:69 src/trait/iter.md:75 |
| #: src/trait/iter.md:83 src/std/vec.md:50 src/std/str.md:22 |
| #: src/std_misc/fs.md:82 |
| msgid "\"> {}\"" |
| msgstr "\"> {}\"" |
| |
| #: src/trait/iter.md:66 |
| msgid "// The `take(n)` method reduces an `Iterator` to its first `n` terms.\n" |
| msgstr "// `take(n)` 方法将 `Iterator` 限制为其前 `n` 项。\n" |
| |
| #: src/trait/iter.md:67 |
| msgid "\"The first four terms of the Fibonacci sequence are: \"" |
| msgstr "\"斐波那契序列的前四项是：\"" |
| |
| #: src/trait/iter.md:72 |
| msgid "" |
| "// The `skip(n)` method shortens an `Iterator` by dropping its first `n` " |
| "terms.\n" |
| msgstr "// `skip(n)` 方法通过跳过前 `n` 项来缩短 `Iterator`。\n" |
| |
| #: src/trait/iter.md:73 |
| msgid "\"The next four terms of the Fibonacci sequence are: \"" |
| msgstr "\"斐波那契序列的接下来四项是：\"" |
| |
| #: src/trait/iter.md:80 |
| msgid "// The `iter` method produces an `Iterator` over an array/slice.\n" |
| msgstr "// `iter` 方法为数组/切片创建一个 `Iterator`。\n" |
| |
| #: src/trait/iter.md:81 |
| msgid "\"Iterate the following array {:?}\"" |
| msgstr "\"遍历以下数组 {:?}\"" |
| |
| #: src/trait/impl_trait.md:3 |
| msgid "`impl Trait` can be used in two locations:" |
| msgstr "`impl Trait` 可以在两个位置使用：" |
| |
| #: src/trait/impl_trait.md:5 |
| msgid "as an argument type" |
| msgstr "作为参数类型" |
| |
| #: src/trait/impl_trait.md:6 |
| msgid "as a return type" |
| msgstr "作为返回类型" |
| |
| #: src/trait/impl_trait.md:8 |
| msgid "As an argument type" |
| msgstr "作为参数类型" |
| |
| #: src/trait/impl_trait.md:10 |
| msgid "" |
| "If your function is generic over a trait but you don't mind the specific " |
| "type, you can simplify the function declaration using `impl Trait` as the " |
| "type of the argument." |
| msgstr "" |
| "如果你的函数对某个 trait 是泛型的，但不关心具体类型，你可以使用 `impl Trait` " |
| "作为参数类型来简化函数声明。" |
| |
| #: src/trait/impl_trait.md:12 |
| msgid "For example, consider the following code:" |
| msgstr "例如，考虑以下代码：" |
| |
| #: src/trait/impl_trait.md:18 src/trait/impl_trait.md:37 |
| msgid "// For each line in the source\n" |
| msgstr "// 遍历数据源中的每一行\n" |
| |
| #: src/trait/impl_trait.md:20 src/trait/impl_trait.md:39 |
| msgid "" |
| "// If the line was read successfully, process it, if not, return the error\n" |
| msgstr "// 如果成功读取行，则处理它；否则，返回错误\n" |
| |
| #: src/trait/impl_trait.md:21 src/trait/impl_trait.md:40 src/std/str.md:41 |
| msgid "','" |
| msgstr "','" |
| |
| #: src/trait/impl_trait.md:21 src/trait/impl_trait.md:40 |
| msgid "// Split the line separated by commas\n" |
| msgstr "// 按逗号分割行\n" |
| |
| #: src/trait/impl_trait.md:22 src/trait/impl_trait.md:41 |
| msgid "// Remove leading and trailing whitespace\n" |
| msgstr "// 去除首尾空白\n" |
| |
| #: src/trait/impl_trait.md:23 src/trait/impl_trait.md:42 |
| msgid "// Collect all strings in a row into a Vec<String>\n" |
| msgstr "// 将该行的所有字符串收集到 Vec<String> 中\n" |
| |
| #: src/trait/impl_trait.md:26 src/trait/impl_trait.md:45 |
| msgid "// Collect all lines into a Vec<Vec<String>>\n" |
| msgstr "// 将所有行收集到 Vec<Vec<String>> 中\n" |
| |
| #: src/trait/impl_trait.md:30 |
| msgid "" |
| "`parse_csv_document` is generic, allowing it to take any type which " |
| "implements BufRead, such as `BufReader<File>` or `[u8]`, but it's not " |
| "important what type `R` is, and `R` is only used to declare the type of " |
| "`src`, so the function can also be written as:" |
| msgstr "" |
| "`parse_csv_document` 是泛型函数，可以接受任何实现了 `BufRead` 的类型，如 " |
| "`BufReader<File>` 或 `[u8]`。但具体的 `R` 类型并不重要，`R` 仅用于声明 `src` " |
| "的类型。因此，这个函数也可以写成：" |
| |
| #: src/trait/impl_trait.md:49 |
| msgid "" |
| "Note that using `impl Trait` as an argument type means that you cannot " |
| "explicitly state what form of the function you use, i.e. " |
| "`parse_csv_document::<std::io::Empty>(std::io::empty())` will not work with " |
| "the second example." |
| msgstr "" |
| "注意，使用 `impl Trait` 作为参数类型意味着你无法显式指定使用的函数形式。例" |
| "如，`parse_csv_document::<std::io::Empty>(std::io::empty())` 在第二个例子中将" |
| "无法工作。" |
| |
| #: src/trait/impl_trait.md:51 |
| msgid "As a return type" |
| msgstr "作为返回类型" |
| |
| #: src/trait/impl_trait.md:53 |
| msgid "" |
| "If your function returns a type that implements `MyTrait`, you can write its " |
| "return type as `-> impl MyTrait`. This can help simplify your type " |
| "signatures quite a lot!" |
| msgstr "" |
| "如果函数返回一个实现了 `MyTrait` 的类型，你可以将其返回类型写为 `-> impl " |
| "MyTrait`。这可以大大简化类型签名！" |
| |
| #: src/trait/impl_trait.md:59 |
| msgid "" |
| "// This function combines two `Vec<i32>` and returns an iterator over it.\n" |
| "// Look how complicated its return type is!\n" |
| msgstr "" |
| "// 这个函数合并两个 `Vec<i32>` 并返回一个迭代器。\n" |
| "// 看看它的返回类型有多复杂！\n" |
| |
| #: src/trait/impl_trait.md:68 |
| msgid "" |
| "// This is the exact same function, but its return type uses `impl Trait`.\n" |
| "// Look how much simpler it is!\n" |
| msgstr "" |
| "// 这是完全相同的函数，但它的返回类型使用了 `impl Trait`。\n" |
| "// 看看它变得多么简单！\n" |
| |
| #: src/trait/impl_trait.md:87 |
| msgid "\"all done\"" |
| msgstr "\"全部完成\"" |
| |
| #: src/trait/impl_trait.md:91 |
| msgid "" |
| "More importantly, some Rust types can't be written out. For example, every " |
| "closure has its own unnamed concrete type. Before `impl Trait` syntax, you " |
| "had to allocate on the heap in order to return a closure. But now you can do " |
| "it all statically, like this:" |
| msgstr "" |
| "更重要的是，某些 Rust 类型无法直接写出。例如，每个闭包都有自己的未命名具体类" |
| "型。在 `impl Trait` 语法出现之前，你必须在堆上分配内存才能返回闭包。但现在你" |
| "可以完全静态地做到这一点，像这样：" |
| |
| #: src/trait/impl_trait.md:97 |
| msgid "// Returns a function that adds `y` to its input\n" |
| msgstr "// 返回一个将 `y` 加到输入值上的函数\n" |
| |
| #: src/trait/impl_trait.md:109 |
| msgid "" |
| "You can also use `impl Trait` to return an iterator that uses `map` or " |
| "`filter` closures! This makes using `map` and `filter` easier. Because " |
| "closure types don't have names, you can't write out an explicit return type " |
| "if your function returns iterators with closures. But with `impl Trait` you " |
| "can do this easily:" |
| msgstr "" |
| "你还可以使用 `impl Trait` 返回一个使用 `map` 或 `filter` 闭包的迭代器！这使得" |
| "使用 `map` 和 `filter` 更加容易。由于闭包类型没有名称，如果你的函数返回带有闭" |
| "包的迭代器，你无法写出显式的返回类型。但使用 `impl Trait`，你可以轻松实现：" |
| |
| #: src/trait/clone.md:3 |
| msgid "" |
| "When dealing with resources, the default behavior is to transfer them during " |
| "assignments or function calls. However, sometimes we need to make a copy of " |
| "the resource as well." |
| msgstr "" |
| "在处理资源时，默认行为是在赋值或函数调用期间转移它们。然而，有时我们也需要复" |
| "制资源。" |
| |
| #: src/trait/clone.md:7 |
| msgid "" |
| "The [`Clone`](https://doc.rust-lang.org/std/clone/trait.Clone.html) trait " |
| "helps us do exactly this. Most commonly, we can use the `.clone()` method " |
| "defined by the `Clone` trait." |
| msgstr "" |
| "[`Clone`](https://doc.rust-lang.org/std/clone/trait.Clone.html) trait 帮助我" |
| "们实现这一点。最常见的是，我们可以使用 `Clone` trait 定义的 `.clone()` 方法。" |
| |
| #: src/trait/clone.md:11 |
| msgid "// A unit struct without resources\n" |
| msgstr "// 一个不包含资源的单元结构体\n" |
| |
| #: src/trait/clone.md:14 |
| msgid "// A tuple struct with resources that implements the `Clone` trait\n" |
| msgstr "// 一个包含资源并实现了 `Clone` trait 的元组结构体\n" |
| |
| #: src/trait/clone.md:20 |
| msgid "// Instantiate `Unit`\n" |
| msgstr "// 实例化 `Unit`\n" |
| |
| #: src/trait/clone.md:22 |
| msgid "// Copy `Unit`, there are no resources to move\n" |
| msgstr "// 复制 `Unit`，没有资源需要移动\n" |
| |
| #: src/trait/clone.md:25 |
| msgid "// Both `Unit`s can be used independently\n" |
| msgstr "// 两个 `Unit` 可以独立使用\n" |
| |
| #: src/trait/clone.md:26 src/trait/clone.md:31 |
| msgid "\"original: {:?}\"" |
| msgstr "\"原始: {:?}\"" |
| |
| #: src/trait/clone.md:27 |
| msgid "\"copy: {:?}\"" |
| msgstr "\"复制: {:?}\"" |
| |
| #: src/trait/clone.md:29 |
| msgid "// Instantiate `Pair`\n" |
| msgstr "// 实例化 `Pair`\n" |
| |
| #: src/trait/clone.md:33 |
| msgid "// Move `pair` into `moved_pair`, moves resources\n" |
| msgstr "// 将 `pair` 移动到 `moved_pair`，资源也随之移动\n" |
| |
| #: src/trait/clone.md:35 |
| msgid "\"moved: {:?}\"" |
| msgstr "\"已移动: {:?}\"" |
| |
| #: src/trait/clone.md:37 |
| msgid "" |
| "// Error! `pair` has lost its resources\n" |
| " //println!(\"original: {:?}\", pair);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`pair` 已失去其资源\n" |
| " //println!(\"原始: {:?}\", pair);\n" |
| " // TODO ^ 尝试取消注释此行\n" |
| |
| #: src/trait/clone.md:41 |
| msgid "// Clone `moved_pair` into `cloned_pair` (resources are included)\n" |
| msgstr "// 将 `moved_pair` 克隆到 `cloned_pair`（包括资源）\n" |
| |
| #: src/trait/clone.md:43 |
| msgid "// Drop the moved original pair using std::mem::drop\n" |
| msgstr "// 使用 std::mem::drop 丢弃已移动的原始对\n" |
| |
| #: src/trait/clone.md:46 |
| msgid "" |
| "// Error! `moved_pair` has been dropped\n" |
| " //println!(\"moved and dropped: {:?}\", moved_pair);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`moved_pair` 已被丢弃\n" |
| " //println!(\"已移动并丢弃: {:?}\", moved_pair);\n" |
| " // TODO ^ 尝试取消注释此行\n" |
| |
| #: src/trait/clone.md:50 |
| msgid "// The result from .clone() can still be used!\n" |
| msgstr "// .clone() 的结果仍然可以使用！\n" |
| |
| #: src/trait/clone.md:51 |
| msgid "\"clone: {:?}\"" |
| msgstr "\"克隆: {:?}\"" |
| |
| #: src/trait/supertraits.md:3 |
| msgid "" |
| "Rust doesn't have \"inheritance\", but you can define a trait as being a " |
| "superset of another trait. For example:" |
| msgstr "" |
| "Rust 没有“继承”，但你可以将一个 trait 定义为另一个 trait 的超集。例如：" |
| |
| #: src/trait/supertraits.md:10 |
| msgid "" |
| "// Person is a supertrait of Student.\n" |
| "// Implementing Student requires you to also impl Person.\n" |
| msgstr "" |
| "// Person 是 Student 的超 trait。\n" |
| "// 实现 Student 需要你同时实现 Person。\n" |
| |
| #: src/trait/supertraits.md:20 |
| msgid "" |
| "// CompSciStudent (computer science student) is a subtrait of both " |
| "Programmer \n" |
| "// and Student. Implementing CompSciStudent requires you to impl both " |
| "supertraits.\n" |
| msgstr "" |
| "// CompSciStudent（计算机科学学生）是 Programmer 和 Student 的子 trait。\n" |
| "// 实现 CompSciStudent 需要你实现两个超 trait。\n" |
| |
| #: src/trait/supertraits.md:29 |
| msgid "" |
| "\"My name is {} and I attend {}. My favorite language is {}. My Git username " |
| "is {}\"" |
| msgstr "" |
| "\"我的名字是 {}，我就读于 {}。我最喜欢的语言是 {}。我的 Git 用户名是 {}\"" |
| |
| #: src/trait/supertraits.md:42 |
| msgid "" |
| "[The Rust Programming Language chapter on supertraits](https://doc.rust-" |
| "lang.org/book/ch19-03-advanced-traits.html#using-supertraits-to-require-one-" |
| "traits-functionality-within-another-trait)" |
| msgstr "" |
| "[《Rust 程序设计语言》中关于超 trait 的章节](https://doc.rust-lang.org/book/" |
| "ch19-03-advanced-traits.html#using-supertraits-to-require-one-traits-" |
| "functionality-within-another-trait)" |
| |
| #: src/trait/disambiguating.md:3 |
| msgid "" |
| "A type can implement many different traits. What if two traits both require " |
| "the same name for a function? For example, many traits might have a method " |
| "named `get()`. They might even have different return types!" |
| msgstr "" |
| "一个类型可以实现多个不同的 trait。如果两个 trait 都要求函数使用相同的名称，该" |
| "怎么办？例如，许多 trait 可能都有一个名为 `get()` 的方法，它们甚至可能有不同" |
| "的返回类型！" |
| |
| #: src/trait/disambiguating.md:7 |
| msgid "" |
| "Good news: because each trait implementation gets its own `impl` block, it's " |
| "clear which trait's `get` method you're implementing." |
| msgstr "" |
| "好消息是：由于每个 trait 实现都有自己的 `impl` 块，因此很容易分清楚你正在实现" |
| "哪个 trait 的 `get` 方法。" |
| |
| #: src/trait/disambiguating.md:10 |
| msgid "" |
| "What about when it comes time to _call_ those methods? To disambiguate " |
| "between them, we have to use Fully Qualified Syntax." |
| msgstr "" |
| "那么在调用这些方法时又该如何处理呢？为了消除它们之间的歧义，我们必须使用完全" |
| "限定语法。" |
| |
| #: src/trait/disambiguating.md:15 |
| msgid "// Get the selected username out of this widget\n" |
| msgstr "// 从这个小部件中获取选定的用户名\n" |
| |
| #: src/trait/disambiguating.md:20 |
| msgid "// Get the selected age out of this widget\n" |
| msgstr "// 从这个小部件中获取选定的年龄\n" |
| |
| #: src/trait/disambiguating.md:23 |
| msgid "// A form with both a UsernameWidget and an AgeWidget\n" |
| msgstr "// 一个同时包含 UsernameWidget 和 AgeWidget 的表单\n" |
| |
| #: src/trait/disambiguating.md:44 src/trait/disambiguating.md:54 |
| msgid "\"rustacean\"" |
| msgstr "\"rustacean\"" |
| |
| #: src/trait/disambiguating.md:48 |
| msgid "" |
| "// If you uncomment this line, you'll get an error saying\n" |
| " // \"multiple `get` found\". Because, after all, there are multiple " |
| "methods\n" |
| " // named `get`.\n" |
| " // println!(\"{}\", form.get());\n" |
| msgstr "" |
| "// 如果你取消注释这一行，你会得到一个错误，提示\n" |
| " // \"找到多个 `get`\"。这是因为确实存在多个\n" |
| " // 名为 `get` 的方法。\n" |
| " // println!(\"{}\", form.get());\n" |
| |
| #: src/trait/disambiguating.md:62 |
| msgid "" |
| "[The Rust Programming Language chapter on Fully Qualified syntax](https://" |
| "doc.rust-lang.org/book/ch19-03-advanced-traits.html#fully-qualified-syntax-" |
| "for-disambiguation-calling-methods-with-the-same-name)" |
| msgstr "" |
| "[《Rust 程序设计语言》中关于完全限定语法的章节](https://doc.rust-lang.org/" |
| "book/ch19-03-advanced-traits.html#fully-qualified-syntax-for-disambiguation-" |
| "calling-methods-with-the-same-name)" |
| |
| #: src/macros.md:1 |
| msgid "`macro_rules!`" |
| msgstr "`macro_rules!`" |
| |
| #: src/macros.md:3 |
| msgid "" |
| "Rust provides a powerful macro system that allows metaprogramming. As you've " |
| "seen in previous chapters, macros look like functions, except that their " |
| "name ends with a bang `!`, but instead of generating a function call, macros " |
| "are expanded into source code that gets compiled with the rest of the " |
| "program. However, unlike macros in C and other languages, Rust macros are " |
| "expanded into abstract syntax trees, rather than string preprocessing, so " |
| "you don't get unexpected precedence bugs." |
| msgstr "" |
| "Rust 提供了一个强大的宏系统，支持元编程。正如你在前面章节中所看到的，宏看起来" |
| "像函数，只是它们的名字以感叹号 `!` 结尾。但与生成函数调用不同，宏会展开成源代" |
| "码，然后与程序的其余部分一起编译。与 C 和其他语言中的宏不同，Rust 宏展开成抽" |
| "象语法树，而不是进行字符串预处理，因此你不会遇到意外的优先级错误。" |
| |
| #: src/macros.md:11 |
| msgid "Macros are created using the `macro_rules!` macro." |
| msgstr "宏是使用 `macro_rules!` 宏来创建的。" |
| |
| #: src/macros.md:14 |
| msgid "// This is a simple macro named `say_hello`.\n" |
| msgstr "// 这是一个名为 `say_hello` 的简单宏。\n" |
| |
| #: src/macros.md:16 |
| msgid "// `()` indicates that the macro takes no argument.\n" |
| msgstr "// `()` 表示该宏不接受任何参数。\n" |
| |
| #: src/macros.md:18 |
| msgid "// The macro will expand into the contents of this block.\n" |
| msgstr "// 宏将展开成这个代码块的内容。\n" |
| |
| #: src/macros.md:19 |
| msgid "\"Hello!\"" |
| msgstr "\"Hello!\"" |
| |
| #: src/macros.md:24 |
| msgid "// This call will expand into `println!(\"Hello!\")`\n" |
| msgstr "// 这个调用将展开成 `println!(\"Hello!\")`\n" |
| |
| #: src/macros.md:29 |
| msgid "So why are macros useful?" |
| msgstr "那么，为什么宏是有用的呢？" |
| |
| #: src/macros.md:31 |
| msgid "" |
| "Don't repeat yourself. There are many cases where you may need similar " |
| "functionality in multiple places but with different types. Often, writing a " |
| "macro is a useful way to avoid repeating code. (More on this later)" |
| msgstr "" |
| "不要重复自己。在许多情况下，你可能需要在多个地方使用相似的功能，但类型不同。" |
| "通常，编写宏是避免代码重复的有效方法。（稍后会详细介绍）" |
| |
| #: src/macros.md:35 |
| msgid "" |
| "Domain-specific languages. Macros allow you to define special syntax for a " |
| "specific purpose. (More on this later)" |
| msgstr "领域特定语言。宏允许你为特定目的定义专门的语法。（稍后会详细介绍）" |
| |
| #: src/macros.md:38 |
| msgid "" |
| "Variadic interfaces. Sometimes you want to define an interface that takes a " |
| "variable number of arguments. An example is `println!` which could take any " |
| "number of arguments, depending on the format string. (More on this later)" |
| msgstr "" |
| "可变参数接口。有时你可能想定义一个接受可变数量参数的接口。例如 `println!`，它" |
| "可以根据格式字符串接受任意数量的参数。（稍后会详细介绍）" |
| |
| #: src/macros/syntax.md:3 |
| msgid "" |
| "In following subsections, we will show how to define macros in Rust. There " |
| "are three basic ideas:" |
| msgstr "在接下来的小节中，我们将展示如何在 Rust 中定义宏。有三个基本概念：" |
| |
| #: src/macros/syntax.md:6 |
| msgid "[Patterns and Designators](designators.md)" |
| msgstr "[模式和指示符](designators.md)" |
| |
| #: src/macros/syntax.md:7 |
| msgid "[Overloading](overload.md)" |
| msgstr "[重载](overload.md)" |
| |
| #: src/macros/syntax.md:8 |
| msgid "[Repetition](repeat.md)" |
| msgstr "[重复](repeat.md)" |
| |
| #: src/macros/designators.md:3 |
| msgid "" |
| "The arguments of a macro are prefixed by a dollar sign `$` and type " |
| "annotated with a _designator_:" |
| msgstr "宏的参数以美元符号 `$` 为前缀，并用**指示符**来标注类型：" |
| |
| #: src/macros/designators.md:8 |
| msgid "" |
| "// This macro takes an argument of designator `ident` and\n" |
| " // creates a function named `$func_name`.\n" |
| " // The `ident` designator is used for variable/function names.\n" |
| msgstr "" |
| "// 这个宏接受一个 `ident` 指示符的参数，\n" |
| " // 并创建一个名为 `$func_name` 的函数。\n" |
| " // `ident` 指示符用于变量/函数名。\n" |
| |
| #: src/macros/designators.md:13 |
| msgid "// The `stringify!` macro converts an `ident` into a string.\n" |
| msgstr "// `stringify!` 宏将 `ident` 转换为字符串。\n" |
| |
| #: src/macros/designators.md:14 |
| msgid "\"You called {:?}()\"" |
| msgstr "\"你调用了 {:?}()\"" |
| |
| #: src/macros/designators.md:19 |
| msgid "// Create functions named `foo` and `bar` with the above macro.\n" |
| msgstr "// 使用上面的宏创建名为 `foo` 和 `bar` 的函数。\n" |
| |
| #: src/macros/designators.md:25 |
| msgid "" |
| "// This macro takes an expression of type `expr` and prints\n" |
| " // it as a string along with its result.\n" |
| " // The `expr` designator is used for expressions.\n" |
| msgstr "" |
| "// 这个宏接受一个 `expr` 类型的表达式，\n" |
| " // 并将其作为字符串打印出来，同时打印其结果。\n" |
| " // `expr` 指示符用于表达式。\n" |
| |
| #: src/macros/designators.md:29 |
| msgid "// `stringify!` will convert the expression *as it is* into a string.\n" |
| msgstr "// `stringify!` 将表达式**原样**转换为字符串。\n" |
| |
| #: src/macros/designators.md:30 |
| msgid "\"{:?} = {:?}\"" |
| msgstr "\"{:?} = {:?}\"" |
| |
| #: src/macros/designators.md:42 |
| msgid "// Recall that blocks are expressions too!\n" |
| msgstr "// 记住，代码块也是表达式！\n" |
| |
| #: src/macros/designators.md:51 |
| msgid "These are some of the available designators:" |
| msgstr "以下是一些可用的指示符：" |
| |
| #: src/macros/designators.md:53 |
| msgid "`block`" |
| msgstr "`block`" |
| |
| #: src/macros/designators.md:54 |
| msgid "`expr` is used for expressions" |
| msgstr "`expr` 用于表达式" |
| |
| #: src/macros/designators.md:55 |
| msgid "`ident` is used for variable/function names" |
| msgstr "`ident` 用于变量/函数名" |
| |
| #: src/macros/designators.md:56 |
| msgid "`item`" |
| msgstr "`item`" |
| |
| #: src/macros/designators.md:57 |
| msgid "`literal` is used for literal constants" |
| msgstr "`literal` 用于字面常量" |
| |
| #: src/macros/designators.md:58 |
| msgid "`pat` (_pattern_)" |
| msgstr "`pat`（**模式** _pattern_）" |
| |
| #: src/macros/designators.md:59 |
| msgid "`path`" |
| msgstr "`path`" |
| |
| #: src/macros/designators.md:60 |
| msgid "`stmt` (_statement_)" |
| msgstr "`stmt`（**语句** _statement_）" |
| |
| #: src/macros/designators.md:61 |
| msgid "`tt` (_token tree_)" |
| msgstr "`tt`（**标记树** _token tree_）" |
| |
| #: src/macros/designators.md:62 |
| msgid "`ty` (_type_)" |
| msgstr "`ty`（**类型** _type_）" |
| |
| #: src/macros/designators.md:63 |
| msgid "`vis` (_visibility qualifier_)" |
| msgstr "`vis`（**可见性限定符** _visibility qualifier_）" |
| |
| #: src/macros/designators.md:65 |
| msgid "" |
| "For a complete list, see the [Rust Reference](https://doc.rust-lang.org/" |
| "reference/macros-by-example.html)." |
| msgstr "" |
| "完整列表请参阅 [Rust 参考手册](https://doc.rust-lang.org/reference/macros-by-" |
| "example.html)。" |
| |
| #: src/macros/overload.md:3 |
| msgid "" |
| "Macros can be overloaded to accept different combinations of arguments. In " |
| "that regard, `macro_rules!` can work similarly to a match block:" |
| msgstr "" |
| "宏可以被重载以接受不同的参数组合。在这方面，`macro_rules!` 的工作方式类似于 " |
| "match 块：" |
| |
| #: src/macros/overload.md:7 |
| msgid "" |
| "// `test!` will compare `$left` and `$right`\n" |
| "// in different ways depending on how you invoke it:\n" |
| msgstr "" |
| "// `test!` 将以不同的方式比较 `$left` 和 `$right`\n" |
| "// 具体取决于你如何调用它：\n" |
| |
| #: src/macros/overload.md:10 |
| msgid "" |
| "// Arguments don't need to be separated by a comma.\n" |
| " // Any template can be used!\n" |
| msgstr "" |
| "// 参数不需要用逗号分隔。\n" |
| " // 可以使用任何模板！\n" |
| |
| #: src/macros/overload.md:13 |
| msgid "\"{:?} and {:?} is {:?}\"" |
| msgstr "\"{:?} 和 {:?} 是 {:?}\"" |
| |
| #: src/macros/overload.md:18 |
| msgid "// ^ each arm must end with a semicolon.\n" |
| msgstr "// ^ 每个分支必须以分号结束。\n" |
| |
| #: src/macros/overload.md:20 |
| msgid "\"{:?} or {:?} is {:?}\"" |
| msgstr "\"{:?} 或 {:?} 是 {:?}\"" |
| |
| #: src/macros/repeat.md:3 |
| msgid "" |
| "Macros can use `+` in the argument list to indicate that an argument may " |
| "repeat at least once, or `*`, to indicate that the argument may repeat zero " |
| "or more times." |
| msgstr "" |
| "宏可以在参数列表中使用 `+` 来表示一个参数可能重复至少一次，或使用 `*` 来表示" |
| "一个参数可能重复零次或多次。" |
| |
| #: src/macros/repeat.md:7 |
| msgid "" |
| "In the following example, surrounding the matcher with `$(...),+` will match " |
| "one or more expression, separated by commas. Also note that the semicolon is " |
| "optional on the last case." |
| msgstr "" |
| "在下面的例子中，用 `$(...),+` 包围匹配器将匹配一个或多个由逗号分隔的表达式。" |
| "另外请注意，最后一个情况的分号是可选的。" |
| |
| #: src/macros/repeat.md:12 |
| msgid "// `find_min!` will calculate the minimum of any number of arguments.\n" |
| msgstr "// `find_min!` 将计算任意数量参数中的最小值。\n" |
| |
| #: src/macros/repeat.md:14 |
| msgid "// Base case:\n" |
| msgstr "// 基本情况：\n" |
| |
| #: src/macros/repeat.md:16 |
| msgid "// `$x` followed by at least one `$y,`\n" |
| msgstr "// `$x` 后面至少跟着一个 `$y,`\n" |
| |
| #: src/macros/repeat.md:18 |
| msgid "// Call `find_min!` on the tail `$y`\n" |
| msgstr "// 对剩余的 `$y` 递归调用 `find_min!`\n" |
| |
| #: src/macros/dry.md:3 |
| msgid "" |
| "Macros allow writing DRY code by factoring out the common parts of functions " |
| "and/or test suites. Here is an example that implements and tests the `+=`, " |
| "`*=` and `-=` operators on `Vec<T>`:" |
| msgstr "" |
| "宏通过提取函数和/或测试套件的共同部分，使我们能够编写符合 DRY（Don't Repeat " |
| "Yourself）原则的代码。下面是一个在 `Vec<T>` 上实现并测试 `+=`、`*=` 和 `-=` " |
| "运算符的示例：" |
| |
| #: src/macros/dry.md:11 |
| msgid "" |
| "// The `tt` (token tree) designator is used for\n" |
| " // operators and tokens.\n" |
| msgstr "" |
| "// `tt`（token tree，标记树）指示符用于\n" |
| " // 运算符和标记。\n" |
| |
| #: src/macros/dry.md:15 |
| msgid "\"{:?}: dimension mismatch: {:?} {:?} {:?}\"" |
| msgstr "\"{:?}：维度不匹配：{:?} {:?} {:?}\"" |
| |
| #: src/macros/dry.md:30 |
| msgid "// *x = x.$method(*y);\n" |
| msgstr "// *x = x.$method(*y);\n" |
| |
| #: src/macros/dry.md:35 |
| msgid "// Implement `add_assign`, `mul_assign`, and `sub_assign` functions.\n" |
| msgstr "// 实现 `add_assign`、`mul_assign` 和 `sub_assign` 函数。\n" |
| |
| #: src/macros/dry.md:60 |
| msgid "// Test `add_assign`, `mul_assign`, and `sub_assign`.\n" |
| msgstr "// 测试 `add_assign`、`mul_assign` 和 `sub_assign`。\n" |
| |
| #: src/macros/dsl.md:1 |
| msgid "Domain Specific Languages (DSLs)" |
| msgstr "领域特定语言（DSL）" |
| |
| #: src/macros/dsl.md:3 |
| msgid "" |
| "A DSL is a mini \"language\" embedded in a Rust macro. It is completely " |
| "valid Rust because the macro system expands into normal Rust constructs, but " |
| "it looks like a small language. This allows you to define concise or " |
| "intuitive syntax for some special functionality (within bounds)." |
| msgstr "" |
| "DSL 是嵌入在 Rust 宏中的一种微型\"语言\"。它是完全有效的 Rust 代码，因为宏系" |
| "统会将其展开为普通的 Rust 结构，但它看起来像一种小型语言。这使你能够为某些特" |
| "定功能定义简洁或直观的语法（在一定范围内）。" |
| |
| #: src/macros/dsl.md:8 |
| msgid "" |
| "Suppose that I want to define a little calculator API. I would like to " |
| "supply an expression and have the output printed to console." |
| msgstr "" |
| "假设我想定义一个简单的计算器 API。我希望提供一个表达式，并将计算结果打印到控" |
| "制台。" |
| |
| #: src/macros/dsl.md:15 |
| msgid "// Force types to be unsigned integers\n" |
| msgstr "// 强制类型为无符号整数\n" |
| |
| #: src/macros/dsl.md:16 src/macros/variadics.md:15 |
| msgid "\"{} = {}\"" |
| msgstr "\"{} = {}\"" |
| |
| #: src/macros/dsl.md:23 |
| msgid "// hehehe `eval` is _not_ a Rust keyword!\n" |
| msgstr "// 嘿嘿，`eval` 可不是 Rust 的关键字哦！\n" |
| |
| #: src/macros/dsl.md:32 src/macros/variadics.md:35 |
| msgid "Output:" |
| msgstr "输出：" |
| |
| #: src/macros/dsl.md:39 |
| msgid "" |
| "This was a very simple example, but much more complex interfaces have been " |
| "developed, such as [`lazy_static`](https://crates.io/crates/lazy_static) or " |
| "[`clap`](https://crates.io/crates/clap)." |
| msgstr "" |
| "这个例子非常简单，但已经有很多利用宏开发的复杂接口，比如 [`lazy_static`]" |
| "(https://crates.io/crates/lazy_static) 或 [`clap`](https://crates.io/crates/" |
| "clap)。" |
| |
| #: src/macros/dsl.md:43 |
| msgid "" |
| "Also, note the two pairs of braces in the macro. The outer ones are part of " |
| "the syntax of `macro_rules!`, in addition to `()` or `[]`." |
| msgstr "" |
| "另外，注意宏中的两对大括号。外层的大括号是 `macro_rules!` 语法的一部分，除此" |
| "之外还可以使用 `()` 或 `[]`。" |
| |
| #: src/macros/variadics.md:1 |
| msgid "Variadic Interfaces" |
| msgstr "可变参数接口" |
| |
| #: src/macros/variadics.md:3 |
| msgid "" |
| "A _variadic_ interface takes an arbitrary number of arguments. For example, " |
| "`println!` can take an arbitrary number of arguments, as determined by the " |
| "format string." |
| msgstr "" |
| "**可变参数**接口可以接受任意数量的参数。例如，`println!` 可以接受任意数量的参" |
| "数，这由格式字符串决定。" |
| |
| #: src/macros/variadics.md:7 |
| msgid "" |
| "We can extend our `calculate!` macro from the previous section to be " |
| "variadic:" |
| msgstr "我们可以将上一节的 `calculate!` 宏扩展为可变参数的形式：" |
| |
| #: src/macros/variadics.md:11 |
| msgid "// The pattern for a single `eval`\n" |
| msgstr "// 单个 `eval` 的模式\n" |
| |
| #: src/macros/variadics.md:14 |
| msgid "// Force types to be integers\n" |
| msgstr "// 强制类型为整数\n" |
| |
| #: src/macros/variadics.md:19 |
| msgid "// Decompose multiple `eval`s recursively\n" |
| msgstr "// 递归分解多个 `eval`\n" |
| |
| #: src/macros/variadics.md:27 |
| msgid "// Look ma! Variadic `calculate!`!\n" |
| msgstr "// 瞧瞧！这是可变参数的 `calculate!`！\n" |
| |
| #: src/error.md:3 |
| msgid "" |
| "Error handling is the process of handling the possibility of failure. For " |
| "example, failing to read a file and then continuing to use that _bad_ input " |
| "would clearly be problematic. Noticing and explicitly managing those errors " |
| "saves the rest of the program from various pitfalls." |
| msgstr "" |
| "错误处理是处理可能出现失败情况的过程。例如，读取文件失败后继续使用那个**错误" |
| "的**输入显然会导致问题。注意并明确管理这些错误可以使程序的其他部分避免各种陷" |
| "阱。" |
| |
| #: src/error.md:8 |
| msgid "" |
| "There are various ways to deal with errors in Rust, which are described in " |
| "the following subchapters. They all have more or less subtle differences and " |
| "different use cases. As a rule of thumb:" |
| msgstr "" |
| "Rust 中有多种处理错误的方法，这些方法将在接下来的小节中详细介绍。它们或多或少" |
| "都有一些细微的差别和不同的使用场景。一般来说：" |
| |
| #: src/error.md:12 |
| msgid "" |
| "An explicit `panic` is mainly useful for tests and dealing with " |
| "unrecoverable errors. For prototyping it can be useful, for example when " |
| "dealing with functions that haven't been implemented yet, but in those cases " |
| "the more descriptive `unimplemented` is better. In tests `panic` is a " |
| "reasonable way to explicitly fail." |
| msgstr "" |
| "显式的 `panic` 主要用于测试和处理不可恢复的错误。在原型开发中，它可能会有用，" |
| "例如在处理尚未实现的函数时。但在这些情况下，使用更具描述性的 `unimplemented` " |
| "会更好。在测试中，`panic` 是一种合理的显式失败方式。" |
| |
| #: src/error.md:17 |
| msgid "" |
| "The `Option` type is for when a value is optional or when the lack of a " |
| "value is not an error condition. For example the parent of a directory - `/` " |
| "and `C:` don't have one. When dealing with `Option`s, `unwrap` is fine for " |
| "prototyping and cases where it's absolutely certain that there is guaranteed " |
| "to be a value. However `expect` is more useful since it lets you specify an " |
| "error message in case something goes wrong anyway." |
| msgstr "" |
| "`Option` 类型用于值是可选的情况，或者缺少值不构成错误条件的情况。例如目录的父" |
| "目录 - `/` 和 `C:` 就没有父目录。在处理 `Option` 时，对于原型设计和绝对确定有" |
| "值的情况，使用 `unwrap` 是可以的。然而，`expect` 更有用，因为它允许你指定一个" |
| "错误消息，以防万一出错。" |
| |
| #: src/error.md:24 |
| msgid "" |
| "When there is a chance that things do go wrong and the caller has to deal " |
| "with the problem, use `Result`. You can `unwrap` and `expect` them as well " |
| "(please don't do that unless it's a test or quick prototype)." |
| msgstr "" |
| "当有可能出错且调用者必须处理问题时，请使用 `Result`。你也可以对它们使用 " |
| "`unwrap` 和 `expect`（除非是测试或快速原型，否则请不要这样做）。" |
| |
| #: src/error.md:28 |
| msgid "" |
| "For a more rigorous discussion of error handling, refer to the error " |
| "handling section in the [official book](https://doc.rust-lang.org/book/" |
| "ch09-00-error-handling.html)." |
| msgstr "" |
| "关于错误处理更详尽的讨论，请参阅[官方文档](https://doc.rust-lang.org/book/" |
| "ch09-00-error-handling.html)中的错误处理章节。" |
| |
| #: src/error/panic.md:3 |
| msgid "" |
| "The simplest error handling mechanism we will see is `panic`. It prints an " |
| "error message, starts unwinding the stack, and usually exits the program. " |
| "Here, we explicitly call `panic` on our error condition:" |
| msgstr "" |
| "我们将看到的最简单的错误处理机制是 `panic`。它会打印一条错误消息，开始展开" |
| "栈，并通常会退出程序。在这里，我们在错误条件下显式调用 `panic`：" |
| |
| #: src/error/panic.md:9 |
| msgid "// You shouldn't drink too many sugary beverages.\n" |
| msgstr "// 你不应该喝太多含糖饮料。\n" |
| |
| #: src/error/panic.md:10 src/error/panic.md:17 src/error/abort_unwind.md:10 |
| #: src/error/abort_unwind.md:23 src/error/abort_unwind.md:41 |
| #: src/error/abort_unwind.md:50 src/error/option_unwrap.md:32 |
| #: src/error/option_unwrap.md:43 src/error/option_unwrap.md:50 |
| msgid "\"lemonade\"" |
| msgstr "\"柠檬水\"" |
| |
| #: src/error/panic.md:10 src/error/option_unwrap.md:43 |
| msgid "\"AAAaaaaa!!!!\"" |
| msgstr "\"啊啊啊啊啊！！！！\"" |
| |
| #: src/error/panic.md:12 src/error/abort_unwind.md:17 |
| #: src/error/abort_unwind.md:44 |
| msgid "\"Some refreshing {} is all I need.\"" |
| msgstr "\"来点清爽的{}就是我现在需要的。\"" |
| |
| #: src/error/panic.md:16 src/error/abort_unwind.md:22 |
| #: src/error/abort_unwind.md:49 src/error/option_unwrap.md:49 |
| msgid "\"water\"" |
| msgstr "\"水\"" |
| |
| #: src/error/panic.md:18 |
| msgid "\"still water\"" |
| msgstr "\"纯净水\"" |
| |
| #: src/error/panic.md:22 |
| msgid "" |
| "The first call to `drink` works. The second panics and thus the third is " |
| "never called." |
| msgstr "" |
| "第一次调用 `drink` 正常执行。第二次调用会引发 panic，因此第三次调用永远不会被" |
| "执行。" |
| |
| #: src/error/abort_unwind.md:1 |
| msgid "`abort` and `unwind`" |
| msgstr "`abort` 和 `unwind`" |
| |
| #: src/error/abort_unwind.md:3 |
| msgid "" |
| "The previous section illustrates the error handling mechanism `panic`. " |
| "Different code paths can be conditionally compiled based on the panic " |
| "setting. The current values available are `unwind` and `abort`." |
| msgstr "" |
| "上一节介绍了错误处理机制 `panic`。可以根据 panic 设置有条件地编译不同的代码路" |
| "径。当前可用的值有 `unwind` 和 `abort`。" |
| |
| #: src/error/abort_unwind.md:5 |
| msgid "" |
| "Building on the prior lemonade example, we explicitly use the panic strategy " |
| "to exercise different lines of code." |
| msgstr "基于之前的柠檬水示例，我们明确使用 panic 策略来执行不同的代码行。" |
| |
| #: src/error/abort_unwind.md:9 |
| msgid "// You shouldn't drink too much sugary beverages.\n" |
| msgstr "// 你不应该喝太多含糖饮料。\n" |
| |
| #: src/error/abort_unwind.md:11 |
| msgid "\"abort\"" |
| msgstr "\"中止\"" |
| |
| #: src/error/abort_unwind.md:12 src/error/abort_unwind.md:37 |
| msgid "\"This is not your party. Run!!!!\"" |
| msgstr "\"这不是你的派对。快跑！！！！\"" |
| |
| #: src/error/abort_unwind.md:14 src/error/abort_unwind.md:32 |
| msgid "\"Spit it out!!!!\"" |
| msgstr "\"快吐出来！！！！\"" |
| |
| #: src/error/abort_unwind.md:27 |
| msgid "" |
| "Here is another example focusing on rewriting `drink()` and explicitly use " |
| "the `unwind` keyword." |
| msgstr "" |
| "这里是另一个示例，重点是重写 `drink()` 函数并明确使用 `unwind` 关键字。" |
| |
| #: src/error/abort_unwind.md:30 src/error/abort_unwind.md:35 |
| msgid "\"unwind\"" |
| msgstr "\"unwind\"" |
| |
| #: src/error/abort_unwind.md:54 |
| msgid "" |
| "The panic strategy can be set from the command line by using `abort` or " |
| "`unwind`." |
| msgstr "可以通过命令行使用 `abort` 或 `unwind` 来设置 panic 策略。" |
| |
| #: src/error/option_unwrap.md:3 |
| msgid "" |
| "In the last example, we showed that we can induce program failure at will. " |
| "We told our program to `panic` if we drink a sugary lemonade. But what if we " |
| "expect _some_ drink but don't receive one? That case would be just as bad, " |
| "so it needs to be handled!" |
| msgstr "" |
| "在上一个例子中，我们展示了如何主动引发程序失败。我们让程序在喝含糖柠檬水时触" |
| "发 `panic`。但如果我们期望得到**某种**饮料却没有收到呢？这种情况同样糟糕，所" |
| "以需要处理！" |
| |
| #: src/error/option_unwrap.md:8 |
| msgid "" |
| "We _could_ test this against the null string (`\"\"`) as we do with a " |
| "lemonade. Since we're using Rust, let's instead have the compiler point out " |
| "cases where there's no drink." |
| msgstr "" |
| "我们**可以**像处理柠檬水那样对空字符串（`\"\"`）进行测试。但既然我们使用的是 " |
| "Rust，不如让编译器指出没有饮料的情况。" |
| |
| #: src/error/option_unwrap.md:12 |
| msgid "" |
| "An `enum` called `Option<T>` in the `std` library is used when absence is a " |
| "possibility. It manifests itself as one of two \"options\":" |
| msgstr "" |
| "`std` 库中的 `Option<T>` 枚举用于处理可能存在缺失的情况。它表现为两个\"选项" |
| "\"之一：" |
| |
| #: src/error/option_unwrap.md:15 |
| msgid "`Some(T)`: An element of type `T` was found" |
| msgstr "`Some(T)`：找到了一个 `T` 类型的元素" |
| |
| #: src/error/option_unwrap.md:16 |
| msgid "`None`: No element was found" |
| msgstr "`None`：没有找到元素" |
| |
| #: src/error/option_unwrap.md:18 |
| msgid "" |
| "These cases can either be explicitly handled via `match` or implicitly with " |
| "`unwrap`. Implicit handling will either return the inner element or `panic`." |
| msgstr "" |
| "这些情况可以通过 `match` 显式处理，也可以用 `unwrap` 隐式处理。隐式处理要么返" |
| "回内部元素，要么触发 `panic`。" |
| |
| #: src/error/option_unwrap.md:21 |
| msgid "" |
| "Note that it's possible to manually customize `panic` with [expect](https://" |
| "doc.rust-lang.org/std/option/enum.Option.html#method.expect), but `unwrap` " |
| "otherwise leaves us with a less meaningful output than explicit handling. In " |
| "the following example, explicit handling yields a more controlled result " |
| "while retaining the option to `panic` if desired." |
| msgstr "" |
| "注意，可以使用 [`expect`](https://doc.rust-lang.org/std/option/" |
| "enum.Option.html#method.expect) 手动自定义 `panic`，但 `unwrap` 相比显式处理" |
| "会产生一个不太有意义的输出。在下面的例子中，显式处理产生了一个更可控的结果，" |
| "同时保留了在需要时触发 `panic` 的选项。" |
| |
| #: src/error/option_unwrap.md:27 |
| msgid "" |
| "// The adult has seen it all, and can handle any drink well.\n" |
| "// All drinks are handled explicitly using `match`.\n" |
| msgstr "" |
| "// 成年人见多识广，可以很好地处理任何饮料。\n" |
| "// 所有饮料都使用 `match` 显式处理。\n" |
| |
| #: src/error/option_unwrap.md:30 |
| msgid "// Specify a course of action for each case.\n" |
| msgstr "// 为每种情况指定一个处理方案。\n" |
| |
| #: src/error/option_unwrap.md:32 |
| msgid "\"Yuck! Too sugary.\"" |
| msgstr "\"呸！太甜了。\"" |
| |
| #: src/error/option_unwrap.md:33 |
| msgid "\"{}? How nice.\"" |
| msgstr "\"{}？真不错。\"" |
| |
| #: src/error/option_unwrap.md:34 |
| msgid "\"No drink? Oh well.\"" |
| msgstr "\"没有饮料？好吧。\"" |
| |
| #: src/error/option_unwrap.md:37 |
| msgid "" |
| "// Others will `panic` before drinking sugary drinks.\n" |
| "// All drinks are handled implicitly using `unwrap`.\n" |
| msgstr "" |
| "// 其他人在喝含糖饮料前会触发 `panic`。\n" |
| "// 所有饮料都使用 `unwrap` 隐式处理。\n" |
| |
| #: src/error/option_unwrap.md:41 |
| msgid "// `unwrap` returns a `panic` when it receives a `None`.\n" |
| msgstr "// 当 `unwrap` 收到 `None` 时会触发 `panic`。\n" |
| |
| #: src/error/option_unwrap.md:45 |
| msgid "\"I love {}s!!!!!\"" |
| msgstr "\"我超爱{}！！！！！\"" |
| |
| #: src/error/option_unwrap.md:57 |
| msgid "\"coffee\"" |
| msgstr "\"咖啡\"" |
| |
| #: src/error/option_unwrap/question_mark.md:3 |
| msgid "" |
| "You can unpack `Option`s by using `match` statements, but it's often easier " |
| "to use the `?` operator. If `x` is an `Option`, then evaluating `x?` will " |
| "return the underlying value if `x` is `Some`, otherwise it will terminate " |
| "whatever function is being executed and return `None`." |
| msgstr "" |
| "你可以使用 `match` 语句来解包 `Option`，但使用 `?` 运算符通常更简便。如果 " |
| "`x` 是一个 `Option`，那么求值 `x?` 将在 `x` 是 `Some` 时返回其内部值，否则它" |
| "将终止当前执行的函数并返回 `None`。" |
| |
| #: src/error/option_unwrap/question_mark.md:10 |
| msgid "" |
| "// If `current_age` is `None`, this returns `None`.\n" |
| " // If `current_age` is `Some`, the inner `u8` value + 1\n" |
| " // gets assigned to `next_age`\n" |
| msgstr "" |
| "// 如果 `current_age` 是 `None`，这将返回 `None`。\n" |
| " // 如果 `current_age` 是 `Some`，内部的 `u8` 值加 1\n" |
| " // 后被赋值给 `next_age`\n" |
| |
| #: src/error/option_unwrap/question_mark.md:14 |
| msgid "\"Next year I will be {}\"" |
| msgstr "\"明年我将会 {} 岁\"" |
| |
| #: src/error/option_unwrap/question_mark.md:18 |
| msgid "You can chain many `?`s together to make your code much more readable." |
| msgstr "你可以将多个 `?` 链接在一起，使你的代码更易读。" |
| |
| #: src/error/option_unwrap/question_mark.md:38 |
| msgid "" |
| "// Gets the area code of the phone number of the person's job, if it " |
| "exists.\n" |
| msgstr "// 如果存在，获取此人工作电话号码的区号。\n" |
| |
| #: src/error/option_unwrap/question_mark.md:40 |
| msgid "" |
| "// This would need many nested `match` statements without the `?` operator.\n" |
| " // It would take a lot more code - try writing it yourself and see " |
| "which\n" |
| " // is easier.\n" |
| msgstr "" |
| "// 如果没有 `?` 运算符，这将需要许多嵌套的 `match` 语句。\n" |
| " // 这将需要更多的代码 - 试着自己写一下，看看哪种方式\n" |
| " // 更容易。\n" |
| |
| #: src/error/option_unwrap/map.md:3 |
| msgid "" |
| "`match` is a valid method for handling `Option`s. However, you may " |
| "eventually find heavy usage tedious, especially with operations only valid " |
| "with an input. In these cases, [combinators](https://doc.rust-lang.org/" |
| "reference/glossary.html#combinator) can be used to manage control flow in a " |
| "modular fashion." |
| msgstr "" |
| "`match` 是处理 `Option` 的有效方法。然而，频繁使用可能会让人感到繁琐，尤其是" |
| "在只有输入时才有效的操作中。在这些情况下，可以使用[组合器](https://doc.rust-" |
| "lang.org/reference/glossary.html#combinator)以模块化的方式管理控制流。" |
| |
| #: src/error/option_unwrap/map.md:8 |
| msgid "" |
| "`Option` has a built in method called `map()`, a combinator for the simple " |
| "mapping of `Some -> Some` and `None -> None`. Multiple `map()` calls can be " |
| "chained together for even more flexibility." |
| msgstr "" |
| "`Option` 有一个内置方法 `map()`，这是一个用于简单映射 `Some -> Some` 和 " |
| "`None -> None` 的组合器。多个 `map()` 调用可以链式使用，从而提供更大的灵活" |
| "性。" |
| |
| #: src/error/option_unwrap/map.md:12 |
| msgid "" |
| "In the following example, `process()` replaces all functions previous to it " |
| "while staying compact." |
| msgstr "在下面的例子中，`process()` 函数以简洁的方式替代了之前的所有函数。" |
| |
| #: src/error/option_unwrap/map.md:23 |
| msgid "" |
| "// Peeling food. If there isn't any, then return `None`.\n" |
| "// Otherwise, return the peeled food.\n" |
| msgstr "" |
| "// 剥皮食物。如果没有食物，则返回 `None`。\n" |
| "// 否则，返回剥皮后的食物。\n" |
| |
| #: src/error/option_unwrap/map.md:32 |
| msgid "" |
| "// Chopping food. If there isn't any, then return `None`.\n" |
| "// Otherwise, return the chopped food.\n" |
| msgstr "" |
| "// 切碎食物。如果没有食物，则返回 `None`。\n" |
| "// 否则，返回切碎后的食物。\n" |
| |
| #: src/error/option_unwrap/map.md:41 |
| msgid "" |
| "// Cooking food. Here, we showcase `map()` instead of `match` for case " |
| "handling.\n" |
| msgstr "" |
| "// 烹饪食物。这里我们展示了使用 `map()` 而非 `match` 来处理不同情况。\n" |
| |
| #: src/error/option_unwrap/map.md:46 |
| msgid "" |
| "// A function to peel, chop, and cook food all in sequence.\n" |
| "// We chain multiple uses of `map()` to simplify the code.\n" |
| msgstr "" |
| "// 一个按顺序剥皮、切碎和烹饪食物的函数。\n" |
| "// 我们通过链式调用多个 `map()` 来简化代码。\n" |
| |
| #: src/error/option_unwrap/map.md:54 |
| msgid "// Check whether there's food or not before trying to eat it!\n" |
| msgstr "// 在尝试吃之前，先检查是否有食物！\n" |
| |
| #: src/error/option_unwrap/map.md:58 |
| msgid "\"Mmm. I love {:?}\"" |
| msgstr "\"嗯，我喜欢 {:?}\"" |
| |
| #: src/error/option_unwrap/map.md:59 |
| msgid "\"Oh no! It wasn't edible.\"" |
| msgstr "\"哎呀！这不能吃。\"" |
| |
| #: src/error/option_unwrap/map.md:70 |
| msgid "// Let's try the simpler looking `process()` now.\n" |
| msgstr "// 现在让我们试试看起来更简洁的 `process()` 函数。\n" |
| |
| #: src/error/option_unwrap/map.md:81 |
| msgid "" |
| "[closures](../../fn/closures.md), [`Option`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html), [`Option::map()`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html#method.map)" |
| msgstr "" |
| "[闭包](../../fn/closures.md)、[`Option`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html)、[`Option::map()`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html#method.map)" |
| |
| #: src/error/option_unwrap/and_then.md:3 |
| msgid "" |
| "`map()` was described as a chainable way to simplify `match` statements. " |
| "However, using `map()` on a function that returns an `Option<T>` results in " |
| "the nested `Option<Option<T>>`. Chaining multiple calls together can then " |
| "become confusing. That's where another combinator called `and_then()`, known " |
| "in some languages as flatmap, comes in." |
| msgstr "" |
| "`map()` 被描述为一种可链式调用的方式来简化 `match` 语句。然而，在返回 " |
| "`Option<T>` 的函数上使用 `map()` 会导致嵌套的 `Option<Option<T>>`。链式调用多" |
| "个这样的函数可能会变得令人困惑。这时，另一个称为 `and_then()` 的组合器（在某" |
| "些语言中称为 flatmap）就派上用场了。" |
| |
| #: src/error/option_unwrap/and_then.md:9 |
| msgid "" |
| "`and_then()` calls its function input with the wrapped value and returns the " |
| "result. If the `Option` is `None`, then it returns `None` instead." |
| msgstr "" |
| "`and_then()` 使用包装的值调用其函数输入并返回结果。如果 `Option` 是 `None`，" |
| "则直接返回 `None`。" |
| |
| #: src/error/option_unwrap/and_then.md:11 |
| msgid "" |
| "In the following example, `cookable_v3()` results in an `Option<Food>`. " |
| "Using `map()` instead of `and_then()` would have given an " |
| "`Option<Option<Food>>`, which is an invalid type for `eat()`." |
| msgstr "" |
| "在下面的例子中，`cookable_v3()` 返回一个 `Option<Food>`。如果使用 `map()` 而" |
| "不是 `and_then()`，将会得到一个 `Option<Option<Food>>`，这对于 `eat()` 函数来" |
| "说是一个无效的类型。" |
| |
| #: src/error/option_unwrap/and_then.md:20 |
| msgid "// We don't have the ingredients to make Sushi.\n" |
| msgstr "// 我们没有制作寿司的原料。\n" |
| |
| #: src/error/option_unwrap/and_then.md:28 |
| msgid "// We have the recipe for everything except Cordon Bleu.\n" |
| msgstr "// 我们有除了蓝带猪排以外所有菜品的食谱。\n" |
| |
| #: src/error/option_unwrap/and_then.md:36 |
| msgid "" |
| "// To make a dish, we need both the recipe and the ingredients.\n" |
| "// We can represent the logic with a chain of `match`es:\n" |
| msgstr "" |
| "// 要做一道菜，我们需要食谱和原料。\n" |
| "// 我们可以用一系列的 `match` 来表示这个逻辑：\n" |
| |
| #: src/error/option_unwrap/and_then.md:45 |
| msgid "" |
| "// This can conveniently be rewritten more compactly with `and_then()`:\n" |
| msgstr "// 这可以使用 `and_then()` 更简洁地重写：\n" |
| |
| #: src/error/option_unwrap/and_then.md:50 |
| msgid "" |
| "// Otherwise we'd need to `flatten()` an `Option<Option<Food>>`\n" |
| "// to get an `Option<Food>`:\n" |
| msgstr "" |
| "// 否则我们需要对 `Option<Option<Food>>` 使用 `flatten()`\n" |
| "// 来获得 `Option<Food>`：\n" |
| |
| #: src/error/option_unwrap/and_then.md:59 |
| msgid "\"Yay! On {:?} we get to eat {:?}.\"" |
| msgstr "\"太好了！在 {:?} 我们可以吃到 {:?}。\"" |
| |
| #: src/error/option_unwrap/and_then.md:60 |
| msgid "\"Oh no. We don't get to eat on {:?}?\"" |
| msgstr "\"哦不。我们在 {:?} 没有东西吃吗？\"" |
| |
| #: src/error/option_unwrap/and_then.md:75 |
| msgid "" |
| "[closures](../../fn/closures.md), [`Option`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html), [`Option::and_then()`](https://doc.rust-lang.org/" |
| "std/option/enum.Option.html#method.and_then), and [`Option::flatten()`]" |
| "(https://doc.rust-lang.org/std/option/enum.Option.html#method.flatten)" |
| msgstr "" |
| "[闭包](../../fn/closures.md)、[`Option`](https://doc.rust-lang.org/std/" |
| "option/enum.Option.html)、[`Option::and_then()`](https://doc.rust-lang.org/" |
| "std/option/enum.Option.html#method.and_then) 和 [`Option::flatten()`]" |
| "(https://doc.rust-lang.org/std/option/enum.Option.html#method.flatten)" |
| |
| #: src/error/option_unwrap/defaults.md:1 |
| msgid "Unpacking options and defaults" |
| msgstr "解包 Option 和设置默认值" |
| |
| #: src/error/option_unwrap/defaults.md:3 |
| msgid "" |
| "There is more than one way to unpack an `Option` and fall back on a default " |
| "if it is `None`. To choose the one that meets our needs, we need to consider " |
| "the following:" |
| msgstr "" |
| "有多种方法可以解包 `Option` 并在其为 `None` 时使用默认值。为了选择满足我们需" |
| "求的方法，我们需要考虑以下几点：" |
| |
| #: src/error/option_unwrap/defaults.md:5 |
| msgid "do we need eager or lazy evaluation?" |
| msgstr "我们需要立即求值还是惰性求值？" |
| |
| #: src/error/option_unwrap/defaults.md:6 |
| msgid "" |
| "do we need to keep the original empty value intact, or modify it in place?" |
| msgstr "我们需要保持原始的空值不变，还是就地修改它？" |
| |
| #: src/error/option_unwrap/defaults.md:8 |
| msgid "`or()` is chainable, evaluates eagerly, keeps empty value intact" |
| msgstr "`or()` 可链式调用，立即求值，保持空值不变" |
| |
| #: src/error/option_unwrap/defaults.md:10 |
| msgid "" |
| "`or()`is chainable and eagerly evaluates its argument, as is shown in the " |
| "following example. Note that because `or`'s arguments are evaluated eagerly, " |
| "the variable passed to `or` is moved." |
| msgstr "" |
| "`or()` 可以链式调用，并且会立即求值其参数，如下例所示。注意，由于 `or` 的参数" |
| "是立即求值的，传递给 `or` 的变量会被移动。" |
| |
| #: src/error/option_unwrap/defaults.md:22 |
| #: src/error/option_unwrap/defaults.md:55 |
| msgid "\"first_available_fruit: {:?}\"" |
| msgstr "\"第一个可用的水果：{:?}\"" |
| |
| #: src/error/option_unwrap/defaults.md:23 |
| msgid "// first_available_fruit: Some(Orange)\n" |
| msgstr "// first_available_fruit: Some(Orange)\n" |
| |
| #: src/error/option_unwrap/defaults.md:25 |
| msgid "" |
| "// `or` moves its argument.\n" |
| " // In the example above, `or(orange)` returned a `Some`, so `or(apple)` " |
| "was not invoked.\n" |
| " // But the variable named `apple` has been moved regardless, and cannot " |
| "be used anymore.\n" |
| " // println!(\"Variable apple was moved, so this line won't compile: {:?}" |
| "\", apple);\n" |
| " // TODO: uncomment the line above to see the compiler error\n" |
| msgstr "" |
| "// `or` 会移动其参数。\n" |
| " // 在上面的例子中，`or(orange)` 返回了 `Some`，所以 `or(apple)` 没有被调" |
| "用。\n" |
| " // 但是名为 `apple` 的变量无论如何都被移动了，不能再使用。\n" |
| " // println!(\"变量 apple 被移动了，所以这行不会编译：{:?}\", apple);\n" |
| " // TODO：取消上面这行的注释来查看编译器错误\n" |
| |
| #: src/error/option_unwrap/defaults.md:33 |
| msgid "`or_else()` is chainable, evaluates lazily, keeps empty value intact" |
| msgstr "`or_else()` 可以链式调用，惰性求值，保持空值不变" |
| |
| #: src/error/option_unwrap/defaults.md:35 |
| msgid "" |
| "Another alternative is to use `or_else`, which is also chainable, and " |
| "evaluates lazily, as is shown in the following example:" |
| msgstr "" |
| "另一种选择是使用 `or_else`，它同样支持链式调用，并且采用惰性求值。以下是一个" |
| "示例：" |
| |
| #: src/error/option_unwrap/defaults.md:44 |
| msgid "\"Providing kiwi as fallback\"" |
| msgstr "\"提供猕猴桃作为备选\"" |
| |
| #: src/error/option_unwrap/defaults.md:48 |
| #: src/error/option_unwrap/defaults.md:93 |
| msgid "\"Providing lemon as fallback\"" |
| msgstr "\"提供柠檬作为备选\"" |
| |
| #: src/error/option_unwrap/defaults.md:56 |
| msgid "" |
| "// Providing kiwi as fallback\n" |
| " // first_available_fruit: Some(Kiwi)\n" |
| msgstr "" |
| "// 提供猕猴桃作为备选\n" |
| " // first_available_fruit: Some(Kiwi)\n" |
| |
| #: src/error/option_unwrap/defaults.md:61 |
| msgid "`get_or_insert()` evaluates eagerly, modifies empty value in place" |
| msgstr "`get_or_insert()` 立即求值，原地修改空值" |
| |
| #: src/error/option_unwrap/defaults.md:63 |
| msgid "" |
| "To make sure that an `Option` contains a value, we can use `get_or_insert` " |
| "to modify it in place with a fallback value, as is shown in the following " |
| "example. Note that `get_or_insert` eagerly evaluates its parameter, so " |
| "variable `apple` is moved:" |
| msgstr "" |
| "为确保 `Option` 包含一个值，我们可以使用 `get_or_insert` 来原地修改它，提供一" |
| "个备选值。下面的例子展示了这一点。请注意，`get_or_insert` 会立即求值其参数，" |
| "因此变量 `apple` 会被移动：" |
| |
| #: src/error/option_unwrap/defaults.md:73 |
| #: src/error/option_unwrap/defaults.md:98 |
| msgid "\"first_available_fruit is: {:?}\"" |
| msgstr "\"第一个可用的水果是：{:?}\"" |
| |
| #: src/error/option_unwrap/defaults.md:74 |
| #: src/error/option_unwrap/defaults.md:99 |
| msgid "\"my_fruit is: {:?}\"" |
| msgstr "\"我的水果是：{:?}\"" |
| |
| #: src/error/option_unwrap/defaults.md:75 |
| msgid "" |
| "// first_available_fruit is: Apple\n" |
| " // my_fruit is: Some(Apple)\n" |
| " //println!(\"Variable named `apple` is moved: {:?}\", apple);\n" |
| " // TODO: uncomment the line above to see the compiler error\n" |
| msgstr "" |
| "// first_available_fruit is: Apple\n" |
| " // my_fruit is: Some(Apple)\n" |
| " //println!(\"名为 `apple` 的变量已被移动：{:?}\", apple);\n" |
| " // TODO：取消上面这行的注释以查看编译器错误\n" |
| |
| #: src/error/option_unwrap/defaults.md:82 |
| msgid "`get_or_insert_with()` evaluates lazily, modifies empty value in place" |
| msgstr "`get_or_insert_with()` 惰性求值，原地修改空值" |
| |
| #: src/error/option_unwrap/defaults.md:84 |
| msgid "" |
| "Instead of explicitly providing a value to fall back on, we can pass a " |
| "closure to `get_or_insert_with`, as follows:" |
| msgstr "" |
| "我们可以向 `get_or_insert_with` 传递一个闭包，而不是显式提供一个备选值。示例" |
| "如下：" |
| |
| #: src/error/option_unwrap/defaults.md:100 |
| msgid "" |
| "// Providing lemon as fallback\n" |
| " // first_available_fruit is: Lemon\n" |
| " // my_fruit is: Some(Lemon)\n" |
| msgstr "" |
| "// 提供柠檬作为备选\n" |
| " // first_available_fruit is: Lemon\n" |
| " // my_fruit is: Some(Lemon)\n" |
| |
| #: src/error/option_unwrap/defaults.md:104 |
| msgid "" |
| "// If the Option has a value, it is left unchanged, and the closure is not " |
| "invoked\n" |
| msgstr "// 如果 Option 已有值，它将保持不变，闭包不会被调用\n" |
| |
| #: src/error/option_unwrap/defaults.md:107 |
| msgid "\"should_be_apple is: {:?}\"" |
| msgstr "\"should_be_apple 的值为：{:?}\"" |
| |
| #: src/error/option_unwrap/defaults.md:108 |
| msgid "\"my_apple is unchanged: {:?}\"" |
| msgstr "\"my_apple 保持不变：{:?}\"" |
| |
| #: src/error/option_unwrap/defaults.md:109 |
| msgid "" |
| "// The output is a follows. Note that the closure `get_lemon_as_fallback` is " |
| "not invoked\n" |
| " // should_be_apple is: Apple\n" |
| " // my_apple is unchanged: Some(Apple)\n" |
| msgstr "" |
| "// 输出如下。注意闭包 `get_lemon_as_fallback` 并未被调用\n" |
| " // should_be_apple is: Apple\n" |
| " // my_apple is unchanged: Some(Apple)\n" |
| |
| #: src/error/option_unwrap/defaults.md:117 |
| msgid "" |
| "[`closures`](https://doc.rust-lang.org/book/ch13-01-closures.html), " |
| "[`get_or_insert`](https://doc.rust-lang.org/core/option/" |
| "enum.Option.html#method.get_or_insert), [`get_or_insert_with`](https://" |
| "doc.rust-lang.org/core/option/enum.Option.html#method.get_or_insert_with), " |
| "[`moved variables`](https://doc.rust-lang.org/book/ch04-02-references-and-" |
| "borrowing.html), [`or`](https://doc.rust-lang.org/core/option/" |
| "enum.Option.html#method.or), [`or_else`](https://doc.rust-lang.org/core/" |
| "option/enum.Option.html#method.or_else)" |
| msgstr "" |
| "[`闭包`](https://doc.rust-lang.org/book/ch13-01-closures.html)、" |
| "[`get_or_insert`](https://doc.rust-lang.org/core/option/" |
| "enum.Option.html#method.get_or_insert)、[`get_or_insert_with`](https://" |
| "doc.rust-lang.org/core/option/enum.Option.html#method.get_or_insert_with)、[`" |
| "变量移动`](https://doc.rust-lang.org/book/ch04-02-references-and-" |
| "borrowing.html)、[`or`](https://doc.rust-lang.org/core/option/" |
| "enum.Option.html#method.or)、[`or_else`](https://doc.rust-lang.org/core/" |
| "option/enum.Option.html#method.or_else)" |
| |
| #: src/error/result.md:3 |
| msgid "" |
| "[`Result`](https://doc.rust-lang.org/std/result/enum.Result.html) is a " |
| "richer version of the [`Option`](https://doc.rust-lang.org/std/option/" |
| "enum.Option.html) type that describes possible _error_ instead of possible " |
| "_absence_." |
| msgstr "" |
| "[`Result`](https://doc.rust-lang.org/std/result/enum.Result.html) 是 " |
| "[`Option`](https://doc.rust-lang.org/std/option/enum.Option.html) 类型的增强" |
| "版，它描述可能的**错误**而非可能的**缺失**。" |
| |
| #: src/error/result.md:6 |
| msgid "That is, `Result<T, E>` could have one of two outcomes:" |
| msgstr "也就是说，`Result<T, E>` 可能有两种结果之一：" |
| |
| #: src/error/result.md:8 |
| msgid "`Ok(T)`: An element `T` was found" |
| msgstr "`Ok(T)`：找到了一个 `T` 类型的元素" |
| |
| #: src/error/result.md:9 |
| msgid "`Err(E)`: An error was found with element `E`" |
| msgstr "`Err(E)`：发生了一个 `E` 类型的错误" |
| |
| #: src/error/result.md:11 |
| msgid "" |
| "By convention, the expected outcome is `Ok` while the unexpected outcome is " |
| "`Err`." |
| msgstr "按照惯例，预期的结果是 `Ok`，而意外的结果是 `Err`。" |
| |
| #: src/error/result.md:13 |
| msgid "" |
| "Like `Option`, `Result` has many methods associated with it. `unwrap()`, for " |
| "example, either yields the element `T` or `panic`s. For case handling, there " |
| "are many combinators between `Result` and `Option` that overlap." |
| msgstr "" |
| "与 `Option` 类似，`Result` 也有许多关联方法。例如，`unwrap()` 要么返回元素 " |
| "`T`，要么触发 `panic`。对于情况处理，`Result` 和 `Option` 之间有许多重叠的组" |
| "合子。" |
| |
| #: src/error/result.md:17 |
| msgid "" |
| "In working with Rust, you will likely encounter methods that return the " |
| "`Result` type, such as the [`parse()`](https://doc.rust-lang.org/std/" |
| "primitive.str.html#method.parse) method. It might not always be possible to " |
| "parse a string into the other type, so `parse()` returns a `Result` " |
| "indicating possible failure." |
| msgstr "" |
| "在使用 Rust 时，你可能会遇到返回 `Result` 类型的方法，比如 [`parse()`]" |
| "(https://doc.rust-lang.org/std/primitive.str.html#method.parse) 方法。将字符" |
| "串解析为其他类型并非总是可行，因此 `parse()` 返回一个 `Result` 来表示可能的失" |
| "败。" |
| |
| #: src/error/result.md:22 |
| msgid "" |
| "Let's see what happens when we successfully and unsuccessfully `parse()` a " |
| "string:" |
| msgstr "让我们看看成功和失败地 `parse()` 一个字符串会发生什么：" |
| |
| #: src/error/result.md:26 |
| msgid "// Let's try using `unwrap()` to get the number out. Will it bite us?\n" |
| msgstr "// 让我们尝试使用 `unwrap()` 来获取数字。这样做会有问题吗？\n" |
| |
| #: src/error/result.md:33 src/error/result.md:36 |
| #: src/error/result/result_map.md:42 src/error/result/result_map.md:46 |
| #: src/error/result/result_map.md:75 src/error/result/result_map.md:79 |
| #: src/error/result/result_alias.md:36 src/error/result/result_alias.md:37 |
| #: src/error/result/early_returns.md:36 src/error/result/early_returns.md:37 |
| #: src/error/result/enter_question_mark.md:34 |
| #: src/error/result/enter_question_mark.md:35 |
| #: src/error/result/enter_question_mark.md:67 |
| #: src/error/result/enter_question_mark.md:68 |
| msgid "\"2\"" |
| msgstr "\"2\"" |
| |
| #: src/error/result.md:34 src/error/result.md:37 |
| msgid "\"double is {}\"" |
| msgstr "\"double is {}\"" |
| |
| #: src/error/result.md:36 src/error/result/result_map.md:46 |
| #: src/error/result/result_map.md:79 src/error/result/result_alias.md:37 |
| #: src/error/result/early_returns.md:37 |
| #: src/error/result/enter_question_mark.md:35 |
| #: src/error/result/enter_question_mark.md:68 |
| msgid "\"t\"" |
| msgstr "\"t\"" |
| |
| #: src/error/result.md:41 |
| msgid "" |
| "In the unsuccessful case, `parse()` leaves us with an error for `unwrap()` " |
| "to `panic` on. Additionally, the `panic` exits our program and provides an " |
| "unpleasant error message." |
| msgstr "" |
| "在解析失败的情况下，`parse()` 会返回一个错误，导致 `unwrap()` 触发 panic。此" |
| "外，panic 会终止程序并输出一条不友好的错误信息。" |
| |
| #: src/error/result.md:45 |
| msgid "" |
| "To improve the quality of our error message, we should be more specific " |
| "about the return type and consider explicitly handling the error." |
| msgstr "" |
| "为了提高错误信息的质量，我们应该更明确地指定返回类型，并考虑显式地处理错误。" |
| |
| #: src/error/result.md:48 |
| msgid "Using `Result` in `main`" |
| msgstr "在 `main` 函数中使用 `Result`" |
| |
| #: src/error/result.md:50 |
| msgid "" |
| "The `Result` type can also be the return type of the `main` function if " |
| "specified explicitly. Typically the `main` function will be of the form:" |
| msgstr "" |
| "如果显式指定，`Result` 类型也可以作为 `main` 函数的返回类型。通常，`main` 函" |
| "数的形式如下：" |
| |
| #: src/error/result.md:59 |
| msgid "" |
| "However `main` is also able to have a return type of `Result`. If an error " |
| "occurs within the `main` function it will return an error code and print a " |
| "debug representation of the error (using the [`Debug`](https://doc.rust-" |
| "lang.org/std/fmt/trait.Debug.html) trait). The following example shows such " |
| "a scenario and touches on aspects covered in [the following section](result/" |
| "early_returns.md)." |
| msgstr "" |
| "然而，`main` 函数也可以返回 `Result` 类型。如果 `main` 函数内发生错误，它将返" |
| "回一个错误代码并打印该错误的调试表示（使用 [`Debug`] trait）。以下示例展示了" |
| "这种情况，并涉及了[下一节]中讨论的内容。\n" |
| "\n" |
| "[`Debug`]: https://doc.rust-lang.org/std/fmt/trait.Debug.html\n" |
| "[下一节]: result/early_returns.md" |
| |
| #: src/error/result/result_map.md:3 |
| msgid "" |
| "Panicking in the previous example's `multiply` does not make for robust " |
| "code. Generally, we want to return the error to the caller so it can decide " |
| "what is the right way to respond to errors." |
| msgstr "" |
| "在前面示例的 `multiply` 函数中使用 panic 并不能产生健壮的代码。通常，我们希望" |
| "将错误返回给调用者，让它决定如何正确地处理错误。" |
| |
| #: src/error/result/result_map.md:7 |
| msgid "" |
| "We first need to know what kind of error type we are dealing with. To " |
| "determine the `Err` type, we look to [`parse()`](https://doc.rust-lang.org/" |
| "std/primitive.str.html#method.parse), which is implemented with the " |
| "[`FromStr`](https://doc.rust-lang.org/std/str/trait.FromStr.html) trait for " |
| "[`i32`](https://doc.rust-lang.org/std/primitive.i32.html). As a result, the " |
| "`Err` type is specified as [`ParseIntError`](https://doc.rust-lang.org/std/" |
| "num/struct.ParseIntError.html)." |
| msgstr "" |
| "首先，我们需要知道我们正在处理的错误类型。要确定 `Err` 类型，我们可以查看 " |
| "[`parse()`] 方法，它是通过 [`FromStr`] trait 为 [`i32`] 实现的。因此，`Err` " |
| "类型被指定为 [`ParseIntError`]。\n" |
| "\n" |
| "[`parse()`]: https://doc.rust-lang.org/std/primitive.str.html#method.parse\n" |
| "[`FromStr`]: https://doc.rust-lang.org/std/str/trait.FromStr.html\n" |
| "[`i32`]: https://doc.rust-lang.org/std/primitive.i32.html\n" |
| "[`ParseIntError`]: https://doc.rust-lang.org/std/num/" |
| "struct.ParseIntError.html" |
| |
| #: src/error/result/result_map.md:12 |
| msgid "" |
| "In the example below, the straightforward `match` statement leads to code " |
| "that is overall more cumbersome." |
| msgstr "在下面的示例中，直接使用 `match` 语句会导致整体代码更加繁琐。" |
| |
| #: src/error/result/result_map.md:17 |
| msgid "" |
| "// With the return type rewritten, we use pattern matching without " |
| "`unwrap()`.\n" |
| msgstr "// 重写返回类型后，我们使用模式匹配而不是 `unwrap()`。\n" |
| |
| #: src/error/result/result_map.md:35 src/error/result/result_map.md:68 |
| #: src/error/result/result_alias.md:30 src/error/result/early_returns.md:30 |
| #: src/error/result/enter_question_mark.md:28 |
| #: src/error/result/enter_question_mark.md:61 |
| msgid "\"n is {}\"" |
| msgstr "\"n 是 {}\"" |
| |
| #: src/error/result/result_map.md:36 src/error/result/result_map.md:69 |
| #: src/error/result/result_alias.md:31 src/error/result/early_returns.md:31 |
| #: src/error/result/enter_question_mark.md:29 |
| #: src/error/result/enter_question_mark.md:62 |
| #: src/error/multiple_error_types/define_error_type.md:55 |
| #: src/error/multiple_error_types/boxing_errors.md:42 |
| #: src/error/multiple_error_types/reenter_question_mark.md:54 |
| #: src/error/multiple_error_types/wrap_error.md:68 |
| msgid "\"Error: {}\"" |
| msgstr "\"错误：{}\"" |
| |
| #: src/error/result/result_map.md:41 src/error/result/result_map.md:74 |
| msgid "// This still presents a reasonable answer.\n" |
| msgstr "// 这仍然给出了一个合理的答案。\n" |
| |
| #: src/error/result/result_map.md:45 src/error/result/result_map.md:78 |
| msgid "// The following now provides a much more helpful error message.\n" |
| msgstr "// 以下代码现在提供了一个更有帮助的错误消息。\n" |
| |
| #: src/error/result/result_map.md:51 |
| msgid "" |
| "Luckily, `Option`'s `map`, `and_then`, and many other combinators are also " |
| "implemented for `Result`. [`Result`](https://doc.rust-lang.org/std/result/" |
| "enum.Result.html) contains a complete listing." |
| msgstr "" |
| "幸运的是，`Option` 的 `map`、`and_then` 以及许多其他组合器也为 `Result` 实现" |
| "了。[`Result`](https://doc.rust-lang.org/std/result/enum.Result.html) 文档中" |
| "包含了完整的列表。" |
| |
| #: src/error/result/result_map.md:56 |
| msgid "" |
| "// As with `Option`, we can use combinators such as `map()`.\n" |
| "// This function is otherwise identical to the one above and reads:\n" |
| "// Multiply if both values can be parsed from str, otherwise pass on the " |
| "error.\n" |
| msgstr "" |
| "// 与 `Option` 类似，我们可以使用诸如 `map()` 之类的组合器。\n" |
| "// 这个函数除此之外与上面的函数相同，其含义为：\n" |
| "// 如果两个值都可以从字符串解析，则相乘；否则传递错误。\n" |
| |
| #: src/error/result/result_alias.md:3 |
| msgid "" |
| "How about when we want to reuse a specific `Result` type many times? Recall " |
| "that Rust allows us to create [aliases](../../types/alias.md). Conveniently, " |
| "we can define one for the specific `Result` in question." |
| msgstr "" |
| "如果我们想多次重用特定的 `Result` 类型，该怎么办？回想一下，Rust 允许我们创建" |
| "[别名](../../types/alias.md)。方便的是，我们可以为特定的 `Result` 定义一个别" |
| "名。" |
| |
| #: src/error/result/result_alias.md:7 |
| msgid "" |
| "At a module level, creating aliases can be particularly helpful. Errors " |
| "found in a specific module often have the same `Err` type, so a single alias " |
| "can succinctly define _all_ associated `Results`. This is so useful that the " |
| "`std` library even supplies one: [`io::Result`](https://doc.rust-lang.org/" |
| "std/io/type.Result.html)!" |
| msgstr "" |
| "在模块级别，创建别名特别有用。在特定模块中发现的错误通常具有相同的 `Err` 类" |
| "型，因此单个别名可以简洁地定义**所有**相关的 `Result`。这非常实用，以至于 " |
| "`std` 库甚至提供了一个：[`io::Result`](https://doc.rust-lang.org/std/io/" |
| "type.Result.html)！" |
| |
| #: src/error/result/result_alias.md:12 |
| msgid "Here's a quick example to show off the syntax:" |
| msgstr "这里有一个简单的例子来展示语法：" |
| |
| #: src/error/result/result_alias.md:16 |
| msgid "" |
| "// Define a generic alias for a `Result` with the error type " |
| "`ParseIntError`.\n" |
| msgstr "// 为错误类型为 `ParseIntError` 的 `Result` 定义一个泛型别名。\n" |
| |
| #: src/error/result/result_alias.md:19 |
| msgid "// Use the above alias to refer to our specific `Result` type.\n" |
| msgstr "// 使用上面定义的别名来引用我们特定的 `Result` 类型。\n" |
| |
| #: src/error/result/result_alias.md:26 |
| msgid "// Here, the alias again allows us to save some space.\n" |
| msgstr "// 在这里，别名再次让我们节省了一些代码空间。\n" |
| |
| #: src/error/result/result_alias.md:43 |
| msgid "[`io::Result`](https://doc.rust-lang.org/std/io/type.Result.html)" |
| msgstr "[`io::Result`](https://doc.rust-lang.org/std/io/type.Result.html)" |
| |
| #: src/error/result/early_returns.md:3 |
| msgid "" |
| "In the previous example, we explicitly handled the errors using combinators. " |
| "Another way to deal with this case analysis is to use a combination of " |
| "`match` statements and _early returns_." |
| msgstr "" |
| "在前面的例子中，我们使用组合器显式地处理了错误。处理这种情况分析的另一种方法" |
| "是使用 `match` 语句和**提前返回**的组合。" |
| |
| #: src/error/result/early_returns.md:7 |
| msgid "" |
| "That is, we can simply stop executing the function and return the error if " |
| "one occurs. For some, this form of code can be easier to both read and " |
| "write. Consider this version of the previous example, rewritten using early " |
| "returns:" |
| msgstr "" |
| "也就是说，如果发生错误，我们可以简单地停止执行函数并返回错误。对某些人来说，" |
| "这种形式的代码可能更容易阅读和编写。考虑使用提前返回重写的前面示例的这个版" |
| "本：" |
| |
| #: src/error/result/early_returns.md:41 |
| msgid "" |
| "At this point, we've learned to explicitly handle errors using combinators " |
| "and early returns. While we generally want to avoid panicking, explicitly " |
| "handling all of our errors is cumbersome." |
| msgstr "" |
| "到目前为止，我们已经学会了使用组合器和提前返回来显式处理错误。虽然我们通常想" |
| "避免 panic，但显式处理所有错误是很繁琐的。" |
| |
| #: src/error/result/early_returns.md:45 |
| msgid "" |
| "In the next section, we'll introduce `?` for the cases where we simply need " |
| "to `unwrap` without possibly inducing `panic`." |
| msgstr "" |
| "在下一节中，我们将介绍 `?` 运算符，用于我们只需要 `unwrap` 而不可能引发 " |
| "`panic` 的情况。" |
| |
| #: src/error/result/enter_question_mark.md:3 |
| msgid "" |
| "Sometimes we just want the simplicity of `unwrap` without the possibility of " |
| "a `panic`. Until now, `unwrap` has forced us to nest deeper and deeper when " |
| "what we really wanted was to get the variable _out_. This is exactly the " |
| "purpose of `?`." |
| msgstr "" |
| "有时我们只想要 `unwrap` 的简单性，而不希望有 `panic` 的可能。到目前为止，当我" |
| "们真正想要的是获取变量**值**时，`unwrap` 迫使我们不断地增加嵌套。这正是 `?` " |
| "运算符的目的。" |
| |
| #: src/error/result/enter_question_mark.md:7 |
| msgid "Upon finding an `Err`, there are two valid actions to take:" |
| msgstr "当遇到 `Err` 时，有两种可行的处理方式：" |
| |
| #: src/error/result/enter_question_mark.md:9 |
| msgid "`panic!` which we already decided to try to avoid if possible" |
| msgstr "1. 使用 `panic!`（我们已经决定尽可能避免这种方式）" |
| |
| #: src/error/result/enter_question_mark.md:10 |
| msgid "`return` because an `Err` means it cannot be handled" |
| msgstr "2. 使用 `return`（因为 `Err` 表示无法处理该错误）" |
| |
| #: src/error/result/enter_question_mark.md:12 |
| msgid "" |
| "`?` is _almost_[^†] exactly equivalent to an `unwrap` which `return`s " |
| "instead of `panic`king on `Err`s. Let's see how we can simplify the earlier " |
| "example that used combinators:" |
| msgstr "" |
| "`?` 运算符**几乎**[^†]等同于在遇到 `Err` 时执行 `return` 而非 `panic` 的 " |
| "`unwrap`。让我们看看如何简化之前使用组合器的例子：" |
| |
| #: src/error/result/enter_question_mark.md:39 |
| msgid "The `try!` macro" |
| msgstr "`try!` 宏" |
| |
| #: src/error/result/enter_question_mark.md:41 |
| msgid "" |
| "Before there was `?`, the same functionality was achieved with the `try!` " |
| "macro. The `?` operator is now recommended, but you may still find `try!` " |
| "when looking at older code. The same `multiply` function from the previous " |
| "example would look like this using `try!`:" |
| msgstr "" |
| "在 `?` 运算符出现之前，相同的功能是通过 `try!` 宏实现的。现在推荐使用 `?` 运" |
| "算符，但在查看旧代码时，你可能仍会遇到 `try!`。使用 `try!` 宏，前面例子中的 " |
| "`multiply` 函数会是这样的：" |
| |
| #: src/error/result/enter_question_mark.md:47 |
| msgid "" |
| "// To compile and run this example without errors, while using Cargo, change " |
| "the value \n" |
| "// of the `edition` field, in the `[package]` section of the `Cargo.toml` " |
| "file, to \"2015\".\n" |
| msgstr "" |
| "// 要使用 Cargo 编译并运行此示例而不出错，请将 `Cargo.toml` 文件中\n" |
| "// `[package]` 部分的 `edition` 字段值更改为 \"2015\"。\n" |
| |
| #: src/error/result/enter_question_mark.md:72 |
| msgid "" |
| "See [re-enter ?](../multiple_error_types/reenter_question_mark.md) for more " |
| "details." |
| msgstr "" |
| "更多详情请参阅[重新认识 ?](../multiple_error_types/" |
| "reenter_question_mark.md)。" |
| |
| #: src/error/multiple_error_types.md:3 |
| msgid "" |
| "The previous examples have always been very convenient; `Result`s interact " |
| "with other `Result`s and `Option`s interact with other `Option`s." |
| msgstr "" |
| "前面的例子一直都很方便：`Result` 与 `Result` 交互，`Option` 与 `Option` 交" |
| "互。" |
| |
| #: src/error/multiple_error_types.md:6 |
| msgid "" |
| "Sometimes an `Option` needs to interact with a `Result`, or a `Result<T, " |
| "Error1>` needs to interact with a `Result<T, Error2>`. In those cases, we " |
| "want to manage our different error types in a way that makes them composable " |
| "and easy to interact with." |
| msgstr "" |
| "有时，`Option` 需要与 `Result` 交互，或者 `Result<T, Error1>` 需要与 " |
| "`Result<T, Error2>` 交互。在这些情况下，我们希望以一种使不同错误类型可组合且" |
| "易于交互的方式来管理它们。" |
| |
| #: src/error/multiple_error_types.md:11 |
| msgid "" |
| "In the following code, two instances of `unwrap` generate different error " |
| "types. `Vec::first` returns an `Option`, while `parse::<i32>` returns a " |
| "`Result<i32, ParseIntError>`:" |
| msgstr "" |
| "在下面的代码中，两个 `unwrap` 实例生成了不同的错误类型。`Vec::first` 返回一" |
| "个 `Option`，而 `parse::<i32>` 返回一个 `Result<i32, ParseIntError>`：" |
| |
| #: src/error/multiple_error_types.md:17 |
| msgid "// Generate error 1\n" |
| msgstr "// 生成错误 1\n" |
| |
| #: src/error/multiple_error_types.md:18 |
| msgid "// Generate error 2\n" |
| msgstr "// 生成错误 2\n" |
| |
| #: src/error/multiple_error_types.md:22 |
| #: src/error/multiple_error_types/option_result.md:16 |
| #: src/error/multiple_error_types/option_result.md:45 |
| #: src/error/multiple_error_types/define_error_type.md:60 |
| #: src/error/multiple_error_types/boxing_errors.md:47 |
| #: src/error/multiple_error_types/reenter_question_mark.md:59 |
| #: src/error/multiple_error_types/wrap_error.md:77 src/error/iter_result.md:40 |
| msgid "\"42\"" |
| msgstr "\"42\"" |
| |
| #: src/error/multiple_error_types.md:22 src/error/multiple_error_types.md:24 |
| #: src/error/multiple_error_types/option_result.md:16 |
| #: src/error/multiple_error_types/option_result.md:18 |
| #: src/error/multiple_error_types/option_result.md:45 |
| #: src/error/multiple_error_types/option_result.md:47 |
| #: src/error/multiple_error_types/define_error_type.md:60 |
| #: src/error/multiple_error_types/define_error_type.md:62 |
| #: src/error/multiple_error_types/boxing_errors.md:47 |
| #: src/error/multiple_error_types/boxing_errors.md:49 |
| #: src/error/multiple_error_types/reenter_question_mark.md:59 |
| #: src/error/multiple_error_types/reenter_question_mark.md:61 |
| #: src/error/multiple_error_types/wrap_error.md:77 |
| #: src/error/multiple_error_types/wrap_error.md:79 src/error/iter_result.md:7 |
| #: src/error/iter_result.md:24 src/error/iter_result.md:40 |
| #: src/error/iter_result.md:60 src/error/iter_result.md:75 |
| #: src/error/iter_result.md:90 |
| msgid "\"93\"" |
| msgstr "\"93\"" |
| |
| #: src/error/multiple_error_types.md:22 src/error/multiple_error_types.md:24 |
| #: src/error/multiple_error_types/option_result.md:16 |
| #: src/error/multiple_error_types/option_result.md:18 |
| #: src/error/multiple_error_types/option_result.md:45 |
| #: src/error/multiple_error_types/option_result.md:47 |
| #: src/error/multiple_error_types/define_error_type.md:60 |
| #: src/error/multiple_error_types/define_error_type.md:62 |
| #: src/error/multiple_error_types/boxing_errors.md:47 |
| #: src/error/multiple_error_types/boxing_errors.md:49 |
| #: src/error/multiple_error_types/reenter_question_mark.md:59 |
| #: src/error/multiple_error_types/reenter_question_mark.md:61 |
| #: src/error/multiple_error_types/wrap_error.md:77 |
| #: src/error/multiple_error_types/wrap_error.md:79 src/error/iter_result.md:7 |
| #: src/error/iter_result.md:24 src/error/iter_result.md:40 |
| #: src/error/iter_result.md:60 src/error/iter_result.md:75 |
| #: src/error/iter_result.md:90 |
| msgid "\"18\"" |
| msgstr "\"18\"" |
| |
| #: src/error/multiple_error_types.md:24 |
| #: src/error/multiple_error_types/option_result.md:18 |
| #: src/error/multiple_error_types/option_result.md:47 |
| #: src/error/multiple_error_types/define_error_type.md:62 |
| #: src/error/multiple_error_types/boxing_errors.md:49 |
| #: src/error/multiple_error_types/reenter_question_mark.md:61 |
| #: src/error/multiple_error_types/wrap_error.md:79 src/error/iter_result.md:7 |
| #: src/error/iter_result.md:24 src/error/iter_result.md:40 |
| #: src/error/iter_result.md:60 src/error/iter_result.md:75 |
| #: src/error/iter_result.md:90 |
| msgid "\"tofu\"" |
| msgstr "\"tofu\"" |
| |
| #: src/error/multiple_error_types.md:26 src/error/multiple_error_types.md:28 |
| #: src/error/multiple_error_types.md:31 |
| #: src/error/multiple_error_types/define_error_type.md:54 |
| #: src/error/multiple_error_types/boxing_errors.md:41 |
| #: src/error/multiple_error_types/reenter_question_mark.md:53 |
| #: src/error/multiple_error_types/wrap_error.md:66 |
| msgid "\"The first doubled is {}\"" |
| msgstr "\"第一个数的两倍是 {}\"" |
| |
| #: src/error/multiple_error_types.md:29 |
| #: src/error/multiple_error_types/option_result.md:23 |
| msgid "// Error 1: the input vector is empty\n" |
| msgstr "// 错误 1：输入向量为空\n" |
| |
| #: src/error/multiple_error_types.md:32 |
| #: src/error/multiple_error_types/option_result.md:26 |
| msgid "// Error 2: the element doesn't parse to a number\n" |
| msgstr "// 错误 2：元素无法解析为数字\n" |
| |
| #: src/error/multiple_error_types.md:36 |
| msgid "" |
| "Over the next sections, we'll see several strategies for handling these kind " |
| "of problems." |
| msgstr "在接下来的章节中，我们将探讨几种处理此类问题的策略。" |
| |
| #: src/error/multiple_error_types/option_result.md:3 |
| msgid "" |
| "The most basic way of handling mixed error types is to just embed them in " |
| "each other." |
| msgstr "处理混合错误类型最基本的方法是将它们相互嵌套。" |
| |
| #: src/error/multiple_error_types/option_result.md:20 |
| #: src/error/multiple_error_types/option_result.md:22 |
| #: src/error/multiple_error_types/option_result.md:25 |
| #: src/error/multiple_error_types/option_result.md:49 |
| #: src/error/multiple_error_types/option_result.md:50 |
| #: src/error/multiple_error_types/option_result.md:51 |
| msgid "\"The first doubled is {:?}\"" |
| msgstr "\"第一个数的两倍是 {:?}\"" |
| |
| #: src/error/multiple_error_types/option_result.md:30 |
| msgid "" |
| "There are times when we'll want to stop processing on errors (like with [`?`]" |
| "(../result/enter_question_mark.md)) but keep going when the `Option` is " |
| "`None`. The `transpose` function comes in handy to swap the `Result` and " |
| "`Option`." |
| msgstr "" |
| "有时我们希望在遇到错误时停止处理（例如使用 [`?`](../result/" |
| "enter_question_mark.md)），但在 `Option` 为 `None` 时继续执行。这时 " |
| "`transpose` 函数就派上用场了，它可以方便地交换 `Result` 和 `Option`。" |
| |
| #: src/error/multiple_error_types/define_error_type.md:3 |
| msgid "" |
| "Sometimes it simplifies the code to mask all of the different errors with a " |
| "single type of error. We'll show this with a custom error." |
| msgstr "" |
| "有时，用单一类型的错误来掩盖所有不同的错误可以简化代码。我们将通过自定义错误" |
| "来演示这一点。" |
| |
| #: src/error/multiple_error_types/define_error_type.md:6 |
| msgid "" |
| "Rust allows us to define our own error types. In general, a \"good\" error " |
| "type:" |
| msgstr "Rust 允许我们定义自己的错误类型。通常，一个\"好的\"错误类型应该：" |
| |
| #: src/error/multiple_error_types/define_error_type.md:8 |
| msgid "Represents different errors with the same type" |
| msgstr "用同一类型表示不同的错误" |
| |
| #: src/error/multiple_error_types/define_error_type.md:9 |
| msgid "Presents nice error messages to the user" |
| msgstr "向用户展示友好的错误消息" |
| |
| #: src/error/multiple_error_types/define_error_type.md:10 |
| msgid "Is easy to compare with other types" |
| msgstr "易于与其他类型进行比较" |
| |
| #: src/error/multiple_error_types/define_error_type.md:11 |
| msgid "Good: `Err(EmptyVec)`" |
| msgstr "好的示例：`Err(EmptyVec)`" |
| |
| #: src/error/multiple_error_types/define_error_type.md:12 |
| msgid "" |
| "Bad: `Err(\"Please use a vector with at least one element\".to_owned())`" |
| msgstr "不好的示例：`Err(\"请使用至少包含一个元素的向量\".to_owned())`" |
| |
| #: src/error/multiple_error_types/define_error_type.md:13 |
| msgid "Can hold information about the error" |
| msgstr "能够保存错误的相关信息" |
| |
| #: src/error/multiple_error_types/define_error_type.md:14 |
| msgid "Good: `Err(BadChar(c, position))`" |
| msgstr "好的示例：`Err(BadChar(c, position))`" |
| |
| #: src/error/multiple_error_types/define_error_type.md:15 |
| msgid "Bad: `Err(\"+ cannot be used here\".to_owned())`" |
| msgstr "不好的示例：`Err(\"此处不能使用 +\".to_owned())`" |
| |
| #: src/error/multiple_error_types/define_error_type.md:16 |
| msgid "Composes well with other errors" |
| msgstr "能够与其他错误很好地组合" |
| |
| #: src/error/multiple_error_types/define_error_type.md:22 |
| msgid "" |
| "// Define our error types. These may be customized for our error handling " |
| "cases.\n" |
| "// Now we will be able to write our own errors, defer to an underlying " |
| "error\n" |
| "// implementation, or do something in between.\n" |
| msgstr "" |
| "// 定义我们的错误类型。这些可以根据我们的错误处理情况进行自定义。\n" |
| "// 现在我们可以编写自己的错误，依赖底层的错误实现，\n" |
| "// 或者在两者之间做一些处理。\n" |
| |
| #: src/error/multiple_error_types/define_error_type.md:28 |
| msgid "" |
| "// Generation of an error is completely separate from how it is displayed.\n" |
| "// There's no need to be concerned about cluttering complex logic with the " |
| "display style.\n" |
| "//\n" |
| "// Note that we don't store any extra info about the errors. This means we " |
| "can't state\n" |
| "// which string failed to parse without modifying our types to carry that " |
| "information.\n" |
| msgstr "" |
| "// 错误的生成与其显示方式是完全分离的。\n" |
| "// 无需担心显示样式会使复杂的逻辑变得混乱。\n" |
| "//\n" |
| "// 注意，我们没有存储关于错误的任何额外信息。这意味着如果不修改类型\n" |
| "// 来携带相关信息，我们就无法指出具体是哪个字符串解析失败了。\n" |
| |
| #: src/error/multiple_error_types/define_error_type.md:36 |
| #: src/error/multiple_error_types/boxing_errors.md:23 |
| #: src/error/multiple_error_types/reenter_question_mark.md:37 |
| msgid "\"invalid first item to double\"" |
| msgstr "\"无效的第一个待加倍项\"" |
| |
| #: src/error/multiple_error_types/define_error_type.md:42 |
| msgid "// Change the error to our new type.\n" |
| msgstr "// 将错误更改为我们的新类型。\n" |
| |
| #: src/error/multiple_error_types/define_error_type.md:46 |
| msgid "// Update to the new error type here also.\n" |
| msgstr "// 这里也更新为新的错误类型。\n" |
| |
| #: src/error/multiple_error_types/boxing_errors.md:3 |
| msgid "" |
| "A way to write simple code while preserving the original errors is to [`Box`]" |
| "(https://doc.rust-lang.org/std/boxed/struct.Box.html) them. The drawback is " |
| "that the underlying error type is only known at runtime and not [statically " |
| "determined](https://doc.rust-lang.org/book/ch17-02-trait-objects.html#trait-" |
| "objects-perform-dynamic-dispatch)." |
| msgstr "" |
| "一种既能编写简洁代码又能保留原始错误信息的方法是使用 [`Box`](https://" |
| "doc.rust-lang.org/std/boxed/struct.Box.html) 将它们装箱。这种方法的缺点是底层" |
| "错误类型只能在运行时确定，而不是[静态确定](https://doc.rust-lang.org/book/" |
| "ch17-02-trait-objects.html#trait-objects-perform-dynamic-dispatch)的。" |
| |
| #: src/error/multiple_error_types/boxing_errors.md:7 |
| msgid "" |
| "The stdlib helps in boxing our errors by having `Box` implement conversion " |
| "from any type that implements the `Error` trait into the trait object " |
| "`Box<Error>`, via [`From`](https://doc.rust-lang.org/std/convert/" |
| "trait.From.html)." |
| msgstr "" |
| "标准库通过让 `Box` 实现从任何实现了 `Error` trait 的类型到 trait 对象 " |
| "`Box<Error>` 的转换来帮助我们装箱错误，这是通过 [`From`](https://doc.rust-" |
| "lang.org/std/convert/trait.From.html) 实现的。" |
| |
| #: src/error/multiple_error_types/boxing_errors.md:14 |
| #: src/error/multiple_error_types/reenter_question_mark.md:28 |
| msgid "// Change the alias to use `Box<dyn error::Error>`.\n" |
| msgstr "// 将别名改为使用 `Box<dyn error::Error>`。\n" |
| |
| #: src/error/multiple_error_types/boxing_errors.md:31 |
| #: src/error/multiple_error_types/boxing_errors.md:34 |
| msgid "// Converts to Box\n" |
| msgstr "// 转换为 Box\n" |
| |
| #: src/error/multiple_error_types/boxing_errors.md:59 |
| msgid "" |
| "[Dynamic dispatch](https://doc.rust-lang.org/book/ch17-02-trait-" |
| "objects.html#trait-objects-perform-dynamic-dispatch) and [`Error` trait]" |
| "(https://doc.rust-lang.org/std/error/trait.Error.html)" |
| msgstr "" |
| "[动态分发](https://doc.rust-lang.org/book/ch17-02-trait-objects.html#trait-" |
| "objects-perform-dynamic-dispatch)和 [`Error` trait](https://doc.rust-" |
| "lang.org/std/error/trait.Error.html)" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:3 |
| msgid "" |
| "Notice in the previous example that our immediate reaction to calling " |
| "`parse` is to `map` the error from a library error into a boxed error:" |
| msgstr "" |
| "注意在前面的例子中，我们对调用 `parse` 的直接反应是将库错误通过 `map` 转换为" |
| "一个装箱的错误：" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:12 |
| msgid "" |
| "Since this is a simple and common operation, it would be convenient if it " |
| "could be elided. Alas, because `and_then` is not sufficiently flexible, it " |
| "cannot. However, we can instead use `?`." |
| msgstr "" |
| "由于这是一个简单且常见的操作，如果能够省略就会很方便。可惜的是，由于 " |
| "`and_then` 不够灵活，所以无法实现这一点。不过，我们可以使用 `?` 来替代。" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:16 |
| msgid "" |
| "`?` was previously explained as either `unwrap` or `return Err(err)`. This " |
| "is only mostly true. It actually means `unwrap` or `return " |
| "Err(From::from(err))`. Since `From::from` is a conversion utility between " |
| "different types, this means that if you `?` where the error is convertible " |
| "to the return type, it will convert automatically." |
| msgstr "" |
| "之前我们将 `?` 解释为 `unwrap` 或 `return Err(err)`。这只是大致正确。实际上，" |
| "它的含义是 `unwrap` 或 `return Err(From::from(err))`。由于 `From::from` 是不" |
| "同类型之间的转换工具，这意味着如果你在错误可转换为返回类型的地方使用 `?`，它" |
| "将自动进行转换。" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:22 |
| msgid "" |
| "Here, we rewrite the previous example using `?`. As a result, the `map_err` " |
| "will go away when `From::from` is implemented for our error type:" |
| msgstr "" |
| "在这里，我们使用 `?` 重写了前面的例子。当为我们的错误类型实现 `From::from` " |
| "后，`map_err` 就不再需要了：" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:42 |
| msgid "" |
| "// The same structure as before but rather than chain all `Results`\n" |
| "// and `Options` along, we `?` to get the inner value out immediately.\n" |
| msgstr "" |
| "// 结构与之前相同，但不再链式处理所有的 `Result` 和 `Option`，\n" |
| "// 而是使用 `?` 立即获取内部值。\n" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:69 |
| msgid "" |
| "This is actually fairly clean now. Compared with the original `panic`, it is " |
| "very similar to replacing the `unwrap` calls with `?` except that the return " |
| "types are `Result`. As a result, they must be destructured at the top level." |
| msgstr "" |
| "现在代码变得相当简洁了。与原来使用 `panic` 的版本相比，这种方法非常类似于用 " |
| "`?` 替换 `unwrap` 调用，只是返回类型变成了 `Result`。因此，需要在顶层对结果进" |
| "行解构。" |
| |
| #: src/error/multiple_error_types/reenter_question_mark.md:76 |
| msgid "" |
| "[`From::from`](https://doc.rust-lang.org/std/convert/trait.From.html) and [`?" |
| "`](https://doc.rust-lang.org/reference/expressions/operator-expr.html#the-" |
| "question-mark-operator)" |
| msgstr "" |
| "[`From::from`](https://doc.rust-lang.org/std/convert/trait.From.html)和[`?`运" |
| "算符](https://doc.rust-lang.org/reference/expressions/operator-expr.html#the-" |
| "question-mark-operator)" |
| |
| #: src/error/multiple_error_types/wrap_error.md:3 |
| msgid "An alternative to boxing errors is to wrap them in your own error type." |
| msgstr "除了将错误装箱外，另一种方法是将它们包装在你自定义的错误类型中。" |
| |
| #: src/error/multiple_error_types/wrap_error.md:16 |
| msgid "" |
| "// We will defer to the parse error implementation for their error.\n" |
| " // Supplying extra info requires adding more data to the type.\n" |
| msgstr "" |
| "// 我们将使用解析错误的实现来处理它们的错误。\n" |
| " // 提供额外信息需要向类型添加更多数据。\n" |
| |
| #: src/error/multiple_error_types/wrap_error.md:25 |
| msgid "\"please use a vector with at least one element\"" |
| msgstr "\"请使用至少包含一个元素的向量\"" |
| |
| #: src/error/multiple_error_types/wrap_error.md:26 |
| msgid "" |
| "// The wrapped error contains additional information and is available\n" |
| " // via the source() method.\n" |
| msgstr "// 包装的错误包含额外信息，可通过 source() 方法获取。\n" |
| |
| #: src/error/multiple_error_types/wrap_error.md:29 |
| msgid "\"the provided string could not be parsed as int\"" |
| msgstr "\"提供的字符串无法解析为整数\"" |
| |
| #: src/error/multiple_error_types/wrap_error.md:38 |
| msgid "" |
| "// The cause is the underlying implementation error type. Is implicitly\n" |
| " // cast to the trait object `&error::Error`. This works because " |
| "the\n" |
| " // underlying type already implements the `Error` trait.\n" |
| msgstr "" |
| "// 错误原因是底层实现的错误类型。它被隐式地\n" |
| " // 转换为 trait 对象 `&error::Error`。这是可行的，因为\n" |
| " // 底层类型已经实现了 `Error` trait。\n" |
| |
| #: src/error/multiple_error_types/wrap_error.md:45 |
| msgid "" |
| "// Implement the conversion from `ParseIntError` to `DoubleError`.\n" |
| "// This will be automatically called by `?` if a `ParseIntError`\n" |
| "// needs to be converted into a `DoubleError`.\n" |
| msgstr "" |
| "// 实现从 `ParseIntError` 到 `DoubleError` 的转换。\n" |
| "// 当需要将 `ParseIntError` 转换为 `DoubleError` 时，\n" |
| "// `?` 运算符会自动调用这个转换。\n" |
| |
| #: src/error/multiple_error_types/wrap_error.md:57 |
| msgid "" |
| "// Here we implicitly use the `ParseIntError` implementation of `From` " |
| "(which\n" |
| " // we defined above) in order to create a `DoubleError`.\n" |
| msgstr "" |
| "// 这里我们隐式使用了 `ParseIntError` 的 `From` 实现（我们在上面定义的）\n" |
| " // 来创建一个 `DoubleError`。\n" |
| |
| #: src/error/multiple_error_types/wrap_error.md:70 |
| msgid "\" Caused by: {}\"" |
| msgstr "\" 错误原因：{}\"" |
| |
| #: src/error/multiple_error_types/wrap_error.md:87 |
| msgid "" |
| "This adds a bit more boilerplate for handling errors and might not be needed " |
| "in all applications. There are some libraries that can take care of the " |
| "boilerplate for you." |
| msgstr "" |
| "这种方法增加了一些处理错误的样板代码，可能并非所有应用程序都需要。有一些库可" |
| "以帮你处理这些样板代码。" |
| |
| #: src/error/multiple_error_types/wrap_error.md:93 |
| msgid "" |
| "[`From::from`](https://doc.rust-lang.org/std/convert/trait.From.html) and " |
| "[`Enums`](../../custom_types/enum.md)" |
| msgstr "" |
| "[`From::from`](https://doc.rust-lang.org/std/convert/trait.From.html) 和[`枚" |
| "举`](../../custom_types/enum.md)" |
| |
| #: src/error/multiple_error_types/wrap_error.md:95 |
| msgid "" |
| "[`Crates for handling errors`](https://crates.io/keywords/error-handling)" |
| msgstr "[处理错误的 crate](https://crates.io/keywords/error-handling)" |
| |
| #: src/error/iter_result.md:3 |
| msgid "An `Iter::map` operation might fail, for example:" |
| msgstr "`Iter::map` 操作可能会失败，例如：" |
| |
| #: src/error/iter_result.md:12 src/error/iter_result.md:29 |
| #: src/error/iter_result.md:65 |
| msgid "\"Results: {:?}\"" |
| msgstr "\"结果：{:?}\"" |
| |
| #: src/error/iter_result.md:16 |
| msgid "Let's step through strategies for handling this." |
| msgstr "让我们逐步介绍处理这种情况的策略。" |
| |
| #: src/error/iter_result.md:18 |
| msgid "Ignore the failed items with `filter_map()`" |
| msgstr "使用 `filter_map()` 忽略失败的项" |
| |
| #: src/error/iter_result.md:20 |
| msgid "" |
| "`filter_map` calls a function and filters out the results that are `None`." |
| msgstr "`filter_map` 调用一个函数并过滤掉结果为 `None` 的项。" |
| |
| #: src/error/iter_result.md:33 |
| msgid "Collect the failed items with `map_err()` and `filter_map()`" |
| msgstr "使用 `map_err()` 和 `filter_map()` 收集失败的项" |
| |
| #: src/error/iter_result.md:35 |
| msgid "" |
| "`map_err` calls a function with the error, so by adding that to the previous " |
| "`filter_map` solution we can save them off to the side while iterating." |
| msgstr "" |
| "`map_err` 会对错误调用一个函数，因此将其添加到之前的 `filter_map` 解决方案" |
| "中，我们可以在迭代时将错误项保存到一旁。" |
| |
| #: src/error/iter_result.md:40 |
| msgid "\"999\"" |
| msgstr "\"999\"" |
| |
| #: src/error/iter_result.md:47 src/error/iter_result.md:80 |
| #: src/error/iter_result.md:97 |
| msgid "\"Numbers: {:?}\"" |
| msgstr "\"数字：{:?}\"" |
| |
| #: src/error/iter_result.md:48 src/error/iter_result.md:81 |
| #: src/error/iter_result.md:98 |
| msgid "\"Errors: {:?}\"" |
| msgstr "\"错误：{:?}\"" |
| |
| #: src/error/iter_result.md:52 |
| msgid "Fail the entire operation with `collect()`" |
| msgstr "使用 `collect()` 使整个操作失败" |
| |
| #: src/error/iter_result.md:54 |
| msgid "" |
| "`Result` implements `FromIterator` so that a vector of results " |
| "(`Vec<Result<T, E>>`) can be turned into a result with a vector " |
| "(`Result<Vec<T>, E>`). Once an `Result::Err` is found, the iteration will " |
| "terminate." |
| msgstr "" |
| "`Result` 实现了 `FromIterator` trait，因此结果的向量（`Vec<Result<T, E>>`）可" |
| "以转换为包含向量的结果（`Result<Vec<T>, E>`）。一旦遇到 `Result::Err`，迭代就" |
| "会终止。" |
| |
| #: src/error/iter_result.md:69 |
| msgid "This same technique can be used with `Option`." |
| msgstr "这种技巧同样适用于 `Option`。" |
| |
| #: src/error/iter_result.md:71 |
| msgid "Collect all valid values and failures with `partition()`" |
| msgstr "使用 `partition()` 收集所有有效值和失败项" |
| |
| #: src/error/iter_result.md:85 |
| msgid "" |
| "When you look at the results, you'll note that everything is still wrapped " |
| "in `Result`. A little more boilerplate is needed for this." |
| msgstr "" |
| "当你查看结果时，你会注意到所有内容仍然被包装在 `Result` 中。这需要一些额外的" |
| "样板代码。" |
| |
| #: src/std.md:3 |
| msgid "" |
| "The `std` library provides many custom types which expands drastically on " |
| "the `primitives`. Some of these include:" |
| msgstr "`std` 库提供了许多自定义类型，大大扩展了\"原生类型\"的功能。其中包括：" |
| |
| #: src/std.md:6 |
| msgid "growable `String`s like: `\"hello world\"`" |
| msgstr "可增长的 `String`，例如：`\"hello world\"`" |
| |
| #: src/std.md:7 |
| msgid "growable vectors: `[1, 2, 3]`" |
| msgstr "可增长的向量（vector）：`[1, 2, 3]`" |
| |
| #: src/std.md:8 |
| msgid "optional types: `Option<i32>`" |
| msgstr "可选类型：`Option<i32>`" |
| |
| #: src/std.md:9 |
| msgid "error handling types: `Result<i32, i32>`" |
| msgstr "错误处理类型：`Result<i32, i32>`" |
| |
| #: src/std.md:10 |
| msgid "heap allocated pointers: `Box<i32>`" |
| msgstr "堆分配的指针：`Box<i32>`" |
| |
| #: src/std.md:14 src/std_misc.md:14 |
| msgid "" |
| "[primitives](primitives.md) and [the std library](https://doc.rust-lang.org/" |
| "std/)" |
| msgstr "[原生类型](primitives.md)和[标准库](https://doc.rust-lang.org/std/)" |
| |
| #: src/std/box.md:3 |
| msgid "" |
| "All values in Rust are stack allocated by default. Values can be _boxed_ " |
| "(allocated on the heap) by creating a `Box<T>`. A box is a smart pointer to " |
| "a heap allocated value of type `T`. When a box goes out of scope, its " |
| "destructor is called, the inner object is destroyed, and the memory on the " |
| "heap is freed." |
| msgstr "" |
| "在 Rust 中，所有值默认都是栈分配的。通过创建 `Box<T>`，可以将值**装箱**（在堆" |
| "上分配）。Box 是指向堆分配的 `T` 类型值的智能指针。当 Box 离开作用域时，会调" |
| "用其析构函数，内部对象被销毁，堆上的内存被释放。" |
| |
| #: src/std/box.md:8 |
| msgid "" |
| "Boxed values can be dereferenced using the `*` operator; this removes one " |
| "layer of indirection." |
| msgstr "可以使用 `*` 运算符解引用装箱的值，这会移除一层间接引用。" |
| |
| #: src/std/box.md:20 |
| msgid "" |
| "// A Rectangle can be specified by where its top left and bottom right \n" |
| "// corners are in space\n" |
| msgstr "// 可以通过指定左上角和右下角在空间中的位置来定义矩形\n" |
| |
| #: src/std/box.md:34 |
| msgid "// Allocate this point on the heap, and return a pointer to it\n" |
| msgstr "// 在堆上分配这个点，并返回指向它的指针\n" |
| |
| #: src/std/box.md:39 |
| msgid "" |
| "// (all the type annotations are superfluous)\n" |
| " // Stack allocated variables\n" |
| msgstr "" |
| "// （所有的类型标注都不是必须的）\n" |
| " // 栈分配的变量\n" |
| |
| #: src/std/box.md:47 |
| msgid "// Heap allocated rectangle\n" |
| msgstr "// 堆分配的矩形\n" |
| |
| #: src/std/box.md:53 |
| msgid "// The output of functions can be boxed\n" |
| msgstr "// 函数的输出可以被装箱\n" |
| |
| #: src/std/box.md:56 |
| msgid "// Double indirection\n" |
| msgstr "// 双重间接引用\n" |
| |
| #: src/std/box.md:59 |
| msgid "\"Point occupies {} bytes on the stack\"" |
| msgstr "\"Point 在栈上占用 {} 字节\"" |
| |
| #: src/std/box.md:61 |
| msgid "\"Rectangle occupies {} bytes on the stack\"" |
| msgstr "\"Rectangle 在栈上占用 {} 字节\"" |
| |
| #: src/std/box.md:64 |
| msgid "// box size == pointer size\n" |
| msgstr "// box 大小 == 指针大小\n" |
| |
| #: src/std/box.md:65 |
| msgid "\"Boxed point occupies {} bytes on the stack\"" |
| msgstr "\"装箱的 point 在栈上占用 {} 字节\"" |
| |
| #: src/std/box.md:67 |
| msgid "\"Boxed rectangle occupies {} bytes on the stack\"" |
| msgstr "\"装箱的 rectangle 在栈上占用 {} 字节\"" |
| |
| #: src/std/box.md:69 |
| msgid "\"Boxed box occupies {} bytes on the stack\"" |
| msgstr "\"装箱的 box 在栈上占用 {} 字节\"" |
| |
| #: src/std/box.md:72 |
| msgid "// Copy the data contained in `boxed_point` into `unboxed_point`\n" |
| msgstr "// 将 `boxed_point` 中的数据复制到 `unboxed_point`\n" |
| |
| #: src/std/box.md:74 |
| msgid "\"Unboxed point occupies {} bytes on the stack\"" |
| msgstr "\"未装箱的 point 在栈上占用 {} 字节\"" |
| |
| #: src/std/vec.md:3 |
| msgid "" |
| "Vectors are re-sizable arrays. Like slices, their size is not known at " |
| "compile time, but they can grow or shrink at any time. A vector is " |
| "represented using 3 parameters:" |
| msgstr "" |
| "向量（Vector）是可调整大小的数组。与切片（Slice）类似，它们的大小在编译时是未" |
| "知的，但可以随时增长或缩小。向量由 3 个参数表示：" |
| |
| #: src/std/vec.md:7 |
| msgid "pointer to the data" |
| msgstr "指向数据的指针" |
| |
| #: src/std/vec.md:8 |
| msgid "length" |
| msgstr "长度" |
| |
| #: src/std/vec.md:9 |
| msgid "capacity" |
| msgstr "容量" |
| |
| #: src/std/vec.md:11 |
| msgid "" |
| "The capacity indicates how much memory is reserved for the vector. The " |
| "vector can grow as long as the length is smaller than the capacity. When " |
| "this threshold needs to be surpassed, the vector is reallocated with a " |
| "larger capacity." |
| msgstr "" |
| "容量表示为向量预留的内存量。只要长度小于容量，向量就可以增长。当需要超过这个" |
| "阈值时，向量会被重新分配更大的容量。" |
| |
| #: src/std/vec.md:17 |
| msgid "// Iterators can be collected into vectors\n" |
| msgstr "// 迭代器可以被收集到向量中\n" |
| |
| #: src/std/vec.md:19 |
| msgid "\"Collected (0..10) into: {:?}\"" |
| msgstr "\"将 (0..10) 收集到：{:?}\"" |
| |
| #: src/std/vec.md:21 |
| msgid "// The `vec!` macro can be used to initialize a vector\n" |
| msgstr "// 可以使用 `vec!` 宏初始化向量\n" |
| |
| #: src/std/vec.md:23 |
| msgid "\"Initial vector: {:?}\"" |
| msgstr "\"初始向量：{:?}\"" |
| |
| #: src/std/vec.md:25 |
| msgid "// Insert new element at the end of the vector\n" |
| msgstr "// 在向量末尾插入新元素\n" |
| |
| #: src/std/vec.md:26 |
| msgid "\"Push 4 into the vector\"" |
| msgstr "\"将 4 推入向量\"" |
| |
| #: src/std/vec.md:28 |
| msgid "\"Vector: {:?}\"" |
| msgstr "\"向量：{:?}\"" |
| |
| #: src/std/vec.md:30 |
| msgid "// Error! Immutable vectors can't grow\n" |
| msgstr "// 错误！不可变向量无法增长\n" |
| |
| #: src/std/vec.md:34 |
| msgid "" |
| "// The `len` method yields the number of elements currently stored in a " |
| "vector\n" |
| msgstr "// `len` 方法返回当前存储在向量中的元素数量\n" |
| |
| #: src/std/vec.md:35 |
| msgid "\"Vector length: {}\"" |
| msgstr "\"向量长度：{}\"" |
| |
| #: src/std/vec.md:37 |
| msgid "// Indexing is done using the square brackets (indexing starts at 0)\n" |
| msgstr "// 使用方括号进行索引（索引从 0 开始）\n" |
| |
| #: src/std/vec.md:38 |
| msgid "\"Second element: {}\"" |
| msgstr "\"第二个元素：{}\"" |
| |
| #: src/std/vec.md:40 |
| msgid "// `pop` removes the last element from the vector and returns it\n" |
| msgstr "// `pop` 移除并返回向量的最后一个元素\n" |
| |
| #: src/std/vec.md:41 |
| msgid "\"Pop last element: {:?}\"" |
| msgstr "\"弹出最后一个元素：{:?}\"" |
| |
| #: src/std/vec.md:43 |
| msgid "// Out of bounds indexing yields a panic\n" |
| msgstr "// 越界索引会导致 panic\n" |
| |
| #: src/std/vec.md:44 |
| msgid "\"Fourth element: {}\"" |
| msgstr "\"第四个元素：{}\"" |
| |
| #: src/std/vec.md:47 |
| msgid "// `Vector`s can be easily iterated over\n" |
| msgstr "// 可以轻松地遍历 `Vector`\n" |
| |
| #: src/std/vec.md:48 |
| msgid "\"Contents of xs:\"" |
| msgstr "\"xs 的内容：\"" |
| |
| #: src/std/vec.md:53 |
| msgid "" |
| "// A `Vector` can also be iterated over while the iteration\n" |
| " // count is enumerated in a separate variable (`i`)\n" |
| msgstr "" |
| "// 遍历 `Vector` 时，可以同时用一个单独的变量（`i`）\n" |
| " // 来枚举迭代计数\n" |
| |
| #: src/std/vec.md:56 |
| msgid "\"In position {} we have value {}\"" |
| msgstr "\"在位置 {} 的值是 {}\"" |
| |
| #: src/std/vec.md:59 |
| msgid "" |
| "// Thanks to `iter_mut`, mutable `Vector`s can also be iterated\n" |
| " // over in a way that allows modifying each value\n" |
| msgstr "" |
| "// 借助 `iter_mut`，可变的 `Vector` 也可以被遍历，\n" |
| " // 并且允许修改每个值\n" |
| |
| #: src/std/vec.md:64 |
| msgid "\"Updated vector: {:?}\"" |
| msgstr "\"更新后的向量：{:?}\"" |
| |
| #: src/std/vec.md:68 |
| msgid "" |
| "More `Vec` methods can be found under the [std::vec](https://doc.rust-" |
| "lang.org/std/vec/) module" |
| msgstr "" |
| "更多 `Vec` 方法可以在 [std::vec](https://doc.rust-lang.org/std/vec/) 模块中找" |
| "到" |
| |
| #: src/std/str.md:3 |
| msgid "The two most used string types in Rust are `String` and `&str`." |
| msgstr "Rust 中最常用的两种字符串类型是 `String` 和 `&str`。" |
| |
| #: src/std/str.md:5 |
| msgid "" |
| "A `String` is stored as a vector of bytes (`Vec<u8>`), but guaranteed to " |
| "always be a valid UTF-8 sequence. `String` is heap allocated, growable and " |
| "not null terminated." |
| msgstr "" |
| "`String` 存储为字节向量（`Vec<u8>`），但保证始终是有效的 UTF-8 序列。" |
| "`String` 在堆上分配，可增长，且不以 null 结尾。" |
| |
| #: src/std/str.md:9 |
| msgid "" |
| "`&str` is a slice (`&[u8]`) that always points to a valid UTF-8 sequence, " |
| "and can be used to view into a `String`, just like `&[T]` is a view into " |
| "`Vec<T>`." |
| msgstr "" |
| "`&str` 是一个切片（`&[u8]`），它始终指向一个有效的 UTF-8 序列，可以用来查看 " |
| "`String`，就像 `&[T]` 是 `Vec<T>` 的一个视图一样。" |
| |
| #: src/std/str.md:14 |
| msgid "" |
| "// (all the type annotations are superfluous)\n" |
| " // A reference to a string allocated in read only memory\n" |
| msgstr "" |
| "// （所有的类型注解都不是必须的）\n" |
| " // 一个指向只读内存中分配的字符串的引用\n" |
| |
| #: src/std/str.md:16 |
| msgid "\"the quick brown fox jumps over the lazy dog\"" |
| msgstr "\"敏捷的棕色狐狸跳过懒惰的狗\"" |
| |
| #: src/std/str.md:17 |
| msgid "\"Pangram: {}\"" |
| msgstr "\"全字母句：{}\"" |
| |
| #: src/std/str.md:19 |
| msgid "// Iterate over words in reverse, no new string is allocated\n" |
| msgstr "// 反向遍历单词，不会分配新的字符串\n" |
| |
| #: src/std/str.md:20 |
| msgid "\"Words in reverse\"" |
| msgstr "\"单词逆序\"" |
| |
| #: src/std/str.md:25 |
| msgid "// Copy chars into a vector, sort and remove duplicates\n" |
| msgstr "// 将字符复制到向量中，排序并去重\n" |
| |
| #: src/std/str.md:30 |
| msgid "// Create an empty and growable `String`\n" |
| msgstr "// 创建一个空的、可增长的 `String`\n" |
| |
| #: src/std/str.md:33 |
| msgid "// Insert a char at the end of string\n" |
| msgstr "// 在字符串末尾插入一个字符\n" |
| |
| #: src/std/str.md:35 |
| msgid "// Insert a string at the end of string\n" |
| msgstr "// 在字符串末尾追加另一个字符串\n" |
| |
| #: src/std/str.md:39 |
| msgid "" |
| "// The trimmed string is a slice to the original string, hence no new\n" |
| " // allocation is performed\n" |
| msgstr "// 修剪后的字符串是原始字符串的一个切片，因此不会进行新的内存分配\n" |
| |
| #: src/std/str.md:43 |
| msgid "\"Used characters: {}\"" |
| msgstr "\"使用的字符：{}\"" |
| |
| #: src/std/str.md:45 |
| msgid "// Heap allocate a string\n" |
| msgstr "// 在堆上分配一个字符串\n" |
| |
| #: src/std/str.md:46 |
| msgid "\"I like dogs\"" |
| msgstr "\"我喜欢狗\"" |
| |
| #: src/std/str.md:47 |
| msgid "// Allocate new memory and store the modified string there\n" |
| msgstr "// 分配新的内存并在其中存储修改后的字符串\n" |
| |
| #: src/std/str.md:48 |
| msgid "\"dog\"" |
| msgstr "\"狗\"" |
| |
| #: src/std/str.md:48 |
| msgid "\"cat\"" |
| msgstr "\"猫\"" |
| |
| #: src/std/str.md:50 |
| msgid "\"Alice says: {}\"" |
| msgstr "\"爱丽丝说：{}\"" |
| |
| #: src/std/str.md:51 |
| msgid "\"Bob says: {}\"" |
| msgstr "\"鲍勃说：{}\"" |
| |
| #: src/std/str.md:55 |
| msgid "" |
| "More `str`/`String` methods can be found under the [std::str](https://" |
| "doc.rust-lang.org/std/str/) and [std::string](https://doc.rust-lang.org/std/" |
| "string/) modules" |
| msgstr "" |
| "更多 `str` 和 `String` 的方法可以在 [std::str](https://doc.rust-lang.org/std/" |
| "str/) 和 [std::string](https://doc.rust-lang.org/std/string/) 模块中找到" |
| |
| #: src/std/str.md:60 |
| msgid "Literals and escapes" |
| msgstr "字面值和转义字符" |
| |
| #: src/std/str.md:62 |
| msgid "" |
| "There are multiple ways to write string literals with special characters in " |
| "them. All result in a similar `&str` so it's best to use the form that is " |
| "the most convenient to write. Similarly there are multiple ways to write " |
| "byte string literals, which all result in `&[u8; N]`." |
| msgstr "" |
| "有多种方式可以编写包含特殊字符的字符串字面值。所有方式都会产生类似的 `&str`，" |
| "因此最好使用最方便编写的形式。同样，也有多种方式可以编写字节字符串字面值，它" |
| "们都会产生 `&[u8; N]` 类型。" |
| |
| #: src/std/str.md:67 |
| msgid "" |
| "Generally special characters are escaped with a backslash character: `\\`. " |
| "This way you can add any character to your string, even unprintable ones and " |
| "ones that you don't know how to type. If you want a literal backslash, " |
| "escape it with another one: `\\\\`" |
| msgstr "" |
| "通常，特殊字符用反斜杠（`\\`）进行转义。这样你可以在字符串中添加任何字符，包" |
| "括不可打印的字符和你不知道如何输入的字符。如果你想要一个字面的反斜杠，用另一" |
| "个反斜杠转义它：`\\\\`" |
| |
| #: src/std/str.md:72 |
| msgid "" |
| "String or character literal delimiters occurring within a literal must be " |
| "escaped: `\"\\\"\"`, `'\\''`." |
| msgstr "" |
| "出现在字面值内的字符串或字符字面值分隔符必须被转义：`\"\\\"\"` 和 `'\\''`。" |
| |
| #: src/std/str.md:76 |
| msgid "// You can use escapes to write bytes by their hexadecimal values...\n" |
| msgstr "// 你可以使用转义来通过十六进制值写入字节...\n" |
| |
| #: src/std/str.md:77 |
| msgid "\"I'm writing \\x52\\x75\\x73\\x74!\"" |
| msgstr "\"我正在写 \\x52\\x75\\x73\\x74！\"" |
| |
| #: src/std/str.md:78 |
| msgid "\"What are you doing\\x3F (\\\\x3F means ?) {}\"" |
| msgstr "\"你在做什么\\x3F（\\\\x3F 表示 ?）{}\"" |
| |
| #: src/std/str.md:80 |
| msgid "// ...or Unicode code points.\n" |
| msgstr "// ...或 Unicode 码点。\n" |
| |
| #: src/std/str.md:81 |
| msgid "\"\\u{211D}\"" |
| msgstr "\"\\u{211D}\"" |
| |
| #: src/std/str.md:82 |
| msgid "\"\\\"DOUBLE-STRUCK CAPITAL R\\\"\"" |
| msgstr "\"\\\"双线大写 R\\\"\"" |
| |
| #: src/std/str.md:84 |
| msgid "\"Unicode character {} (U+211D) is called {}\"" |
| msgstr "\"Unicode 字符 {} (U+211D) 被称为 {}\"" |
| |
| #: src/std/str.md:88 |
| msgid "" |
| "\"String literals\n" |
| " can span multiple lines.\n" |
| " The linebreak and indentation here ->\\\n" |
| " <- can be escaped too!\"" |
| msgstr "" |
| "\"字符串字面值\n" |
| " 可以跨越多行。\n" |
| " 这里的换行和缩进 ->\\\n" |
| " <- 也可以被转义！\"" |
| |
| #: src/std/str.md:96 |
| msgid "" |
| "Sometimes there are just too many characters that need to be escaped or it's " |
| "just much more convenient to write a string out as-is. This is where raw " |
| "string literals come into play." |
| msgstr "" |
| "有时需要转义的字符太多，或者直接按原样写出字符串会更方便。这时就可以使用原始" |
| "字符串字面值。" |
| |
| #: src/std/str.md:101 |
| msgid "r\"Escapes don't work here: \\x3F \\u{211D}\"" |
| msgstr "r\"转义在这里不起作用：\\x3F \\u{211D}\"" |
| |
| #: src/std/str.md:104 |
| msgid "// If you need quotes in a raw string, add a pair of #s\n" |
| msgstr "// 如果你需要在原始字符串中使用引号，可以添加一对 #\n" |
| |
| #: src/std/str.md:105 |
| msgid "r#\"And then I said: \"There is no escape!\"\"#" |
| msgstr "r#\"然后我说：\"无处可逃！\"\"#" |
| |
| #: src/std/str.md:108 |
| msgid "" |
| "// If you need \"# in your string, just use more #s in the delimiter.\n" |
| " // You can use up to 255 #s.\n" |
| msgstr "" |
| "// 如果你需要在字符串中使用 \"#，只需在分隔符中使用更多的 #。\n" |
| " // 你最多可以使用 255 个 #。\n" |
| |
| #: src/std/str.md:110 |
| msgid "r###\"A string with \"# in it. And even \"##!\"###" |
| msgstr "r###\"一个包含 \"# 的字符串。甚至还有 \"##！\"###" |
| |
| #: src/std/str.md:115 |
| msgid "" |
| "Want a string that's not UTF-8? (Remember, `str` and `String` must be valid " |
| "UTF-8). Or maybe you want an array of bytes that's mostly text? Byte strings " |
| "to the rescue!" |
| msgstr "" |
| "想要一个非 UTF-8 的字符串吗？（请记住，`str` 和 `String` 必须是有效的 " |
| "UTF-8）。或者你想要一个主要是文本的字节数组？字节字符串来帮忙！" |
| |
| #: src/std/str.md:122 |
| msgid "// Note that this is not actually a `&str`\n" |
| msgstr "// 注意，这实际上不是一个 `&str`\n" |
| |
| #: src/std/str.md:123 |
| msgid "b\"this is a byte string\"" |
| msgstr "b\"这是一个字节字符串\"" |
| |
| #: src/std/str.md:125 |
| msgid "" |
| "// Byte arrays don't have the `Display` trait, so printing them is a bit " |
| "limited\n" |
| msgstr "// 字节数组没有 `Display` trait，所以打印它们有一些限制\n" |
| |
| #: src/std/str.md:126 |
| msgid "\"A byte string: {:?}\"" |
| msgstr "\"一个字节字符串：{:?}\"" |
| |
| #: src/std/str.md:128 |
| msgid "// Byte strings can have byte escapes...\n" |
| msgstr "// 字节字符串可以包含字节转义...\n" |
| |
| #: src/std/str.md:129 |
| msgid "b\"\\x52\\x75\\x73\\x74 as bytes\"" |
| msgstr "b\"\\x52\\x75\\x73\\x74 作为字节\"" |
| |
| #: src/std/str.md:130 |
| msgid "" |
| "// ...but no unicode escapes\n" |
| " // let escaped = b\"\\u{211D} is not allowed\";\n" |
| msgstr "" |
| "// ...但不允许 Unicode 转义\n" |
| " // let escaped = b\"\\u{211D} 是不允许的\";\n" |
| |
| #: src/std/str.md:132 |
| msgid "\"Some escaped bytes: {:?}\"" |
| msgstr "\"一些转义的字节：{:?}\"" |
| |
| #: src/std/str.md:135 |
| msgid "// Raw byte strings work just like raw strings\n" |
| msgstr "// 原始字节字符串的工作方式与原始字符串相同\n" |
| |
| #: src/std/str.md:136 |
| msgid "br\"\\u{211D} is not escaped here\"" |
| msgstr "br\"\\u{211D} 在这里不会被转义\"" |
| |
| #: src/std/str.md:139 |
| msgid "// Converting a byte array to `str` can fail\n" |
| msgstr "// 将字节数组转换为 `str` 可能会失败\n" |
| |
| #: src/std/str.md:141 |
| msgid "\"And the same as text: '{}'\"" |
| msgstr "\"作为文本的相同内容：'{}'\"" |
| |
| #: src/std/str.md:144 |
| msgid "" |
| "br#\"You can also use \"fancier\" formatting, \\\n" |
| " like with normal raw strings\"#" |
| msgstr "" |
| "br#\"你也可以使用\"更花哨的\"格式，\\\n" |
| " 就像普通的原始字符串一样\"#" |
| |
| #: src/std/str.md:147 |
| msgid "// Byte strings don't have to be UTF-8\n" |
| msgstr "// 字节字符串不必是 UTF-8 编码\n" |
| |
| #: src/std/str.md:148 |
| msgid "b\"\\x82\\xe6\\x82\\xa8\\x82\\xb1\\x82\\xbb\"" |
| msgstr "b\"\\x82\\xe6\\x82\\xa8\\x82\\xb1\\x82\\xbb\"" |
| |
| #: src/std/str.md:148 |
| msgid "// \"ようこそ\" in SHIFT-JIS\n" |
| msgstr "// SHIFT-JIS 编码的 \"ようこそ\"\n" |
| |
| #: src/std/str.md:150 |
| msgid "// But then they can't always be converted to `str`\n" |
| msgstr "// 但它们并不总是能被转换为 `str`\n" |
| |
| #: src/std/str.md:152 |
| msgid "\"Conversion successful: '{}'\"" |
| msgstr "\"转换成功：'{}'\"" |
| |
| #: src/std/str.md:153 |
| msgid "\"Conversion failed: {:?}\"" |
| msgstr "\"转换失败：{:?}\"" |
| |
| #: src/std/str.md:158 |
| msgid "" |
| "For conversions between character encodings check out the [encoding](https://" |
| "crates.io/crates/encoding) crate." |
| msgstr "" |
| "对于字符编码之间的转换，请查看 [encoding](https://crates.io/crates/encoding) " |
| "crate。" |
| |
| #: src/std/str.md:160 |
| msgid "" |
| "A more detailed listing of the ways to write string literals and escape " |
| "characters is given in the ['Tokens' chapter](https://doc.rust-lang.org/" |
| "reference/tokens.html) of the Rust Reference." |
| msgstr "" |
| "关于编写字符串字面值和转义字符的更详细说明，请参阅 Rust 参考手册的[「标记」章" |
| "节](https://doc.rust-lang.org/reference/tokens.html)。" |
| |
| #: src/std/option.md:3 |
| msgid "" |
| "Sometimes it's desirable to catch the failure of some parts of a program " |
| "instead of calling `panic!`; this can be accomplished using the `Option` " |
| "enum." |
| msgstr "" |
| "有时我们希望捕获程序某些部分的失败，而不是调用 `panic!`。这可以通过使用 " |
| "`Option` 枚举来实现。" |
| |
| #: src/std/option.md:6 |
| msgid "The `Option<T>` enum has two variants:" |
| msgstr "`Option<T>` 枚举有两个变体：" |
| |
| #: src/std/option.md:8 |
| msgid "`None`, to indicate failure or lack of value, and" |
| msgstr "`None`：表示失败或缺少值，以及" |
| |
| #: src/std/option.md:9 |
| msgid "`Some(value)`, a tuple struct that wraps a `value` with type `T`." |
| msgstr "`Some(value)`：一个元组结构体，包装了类型为 `T` 的 `value`。" |
| |
| #: src/std/option.md:12 |
| msgid "// An integer division that doesn't `panic!`\n" |
| msgstr "// 一个不会触发 `panic!` 的整数除法\n" |
| |
| #: src/std/option.md:15 |
| msgid "// Failure is represented as the `None` variant\n" |
| msgstr "// 失败用 `None` 变体表示\n" |
| |
| #: src/std/option.md:18 |
| msgid "// Result is wrapped in a `Some` variant\n" |
| msgstr "// 结果被包装在 `Some` 变体中\n" |
| |
| #: src/std/option.md:22 |
| msgid "// This function handles a division that may not succeed\n" |
| msgstr "// 这个函数处理可能不成功的除法运算\n" |
| |
| #: src/std/option.md:25 |
| msgid "// `Option` values can be pattern matched, just like other enums\n" |
| msgstr "// `Option` 值可以进行模式匹配，就像其他枚举一样\n" |
| |
| #: src/std/option.md:27 |
| msgid "\"{} / {} failed!\"" |
| msgstr "\"{} / {} 失败！\"" |
| |
| #: src/std/option.md:29 |
| msgid "\"{} / {} = {}\"" |
| msgstr "\"{} / {} = {}\"" |
| |
| #: src/std/option.md:38 |
| msgid "// Binding `None` to a variable needs to be type annotated\n" |
| msgstr "// 将 `None` 绑定到变量时需要进行类型注解\n" |
| |
| #: src/std/option.md:44 |
| msgid "// Unwrapping a `Some` variant will extract the value wrapped.\n" |
| msgstr "// 解包 `Some` 变体将提取其中包装的值。\n" |
| |
| #: src/std/option.md:45 src/std/option.md:48 |
| msgid "\"{:?} unwraps to {:?}\"" |
| msgstr "\"{:?} 解包后得到 {:?}\"" |
| |
| #: src/std/option.md:47 |
| msgid "// Unwrapping a `None` variant will `panic!`\n" |
| msgstr "// 解包 `None` 变体将触发 `panic!`\n" |
| |
| #: src/std/result.md:3 |
| msgid "" |
| "We've seen that the `Option` enum can be used as a return value from " |
| "functions that may fail, where `None` can be returned to indicate failure. " |
| "However, sometimes it is important to express _why_ an operation failed. To " |
| "do this we have the `Result` enum." |
| msgstr "" |
| "我们已经看到 `Option` 枚举可以用作可能失败的函数的返回值，其中 `None` 用于表" |
| "示失败。\n" |
| "然而，有时表达操作失败的**原因**很重要。为此，我们有 `Result` 枚举。" |
| |
| #: src/std/result.md:8 |
| msgid "The `Result<T, E>` enum has two variants:" |
| msgstr "`Result<T, E>` 枚举有两个变体：" |
| |
| #: src/std/result.md:10 |
| msgid "" |
| "`Ok(value)` which indicates that the operation succeeded, and wraps the " |
| "`value` returned by the operation. (`value` has type `T`)" |
| msgstr "" |
| "`Ok(value)`：表示操作成功，并包装了操作返回的 `value`。（`value` 的类型为 " |
| "`T`）" |
| |
| #: src/std/result.md:12 |
| msgid "" |
| "`Err(why)`, which indicates that the operation failed, and wraps `why`, " |
| "which (hopefully) explains the cause of the failure. (`why` has type `E`)" |
| msgstr "" |
| "`Err(why)`：表示操作失败，并包装了 `why`，它（希望）解释了失败的原因。" |
| "（`why` 的类型为 `E`）" |
| |
| #: src/std/result.md:17 |
| msgid "// Mathematical \"errors\" we want to catch\n" |
| msgstr "// 我们想要捕获的数学\"错误\"\n" |
| |
| #: src/std/result.md:29 |
| msgid "" |
| "// This operation would `fail`, instead let's return the reason of\n" |
| " // the failure wrapped in `Err`\n" |
| msgstr "// 这个操作会\"失败\"，所以我们返回包装在 `Err` 中的失败原因\n" |
| |
| #: src/std/result.md:33 |
| msgid "// This operation is valid, return the result wrapped in `Ok`\n" |
| msgstr "// 这个操作是有效的，返回包装在 `Ok` 中的结果\n" |
| |
| #: src/std/result.md:54 |
| msgid "// `op(x, y)` === `sqrt(ln(x / y))`\n" |
| msgstr "// `op(x, y)` === `sqrt(ln(x / y))`\n" |
| |
| #: src/std/result.md:57 |
| msgid "// This is a three level match pyramid!\n" |
| msgstr "// 这是一个三层的匹配金字塔！\n" |
| |
| #: src/std/result.md:71 |
| msgid "// Will this fail?\n" |
| msgstr "// 这会失败吗？\n" |
| |
| #: src/std/result/question_mark.md:3 |
| msgid "" |
| "Chaining results using match can get pretty untidy; luckily, the `?` " |
| "operator can be used to make things pretty again. `?` is used at the end of " |
| "an expression returning a `Result`, and is equivalent to a match expression, " |
| "where the `Err(err)` branch expands to an early `return " |
| "Err(From::from(err))`, and the `Ok(ok)` branch expands to an `ok` expression." |
| msgstr "" |
| "使用 match 链式处理结果可能会变得相当混乱；幸运的是，我们可以使用 `?` 运算符" |
| "来让代码变得整洁。`?` 运算符用在返回 `Result` 的表达式末尾，等效于一个 match " |
| "表达式。在这个表达式中，`Err(err)` 分支会展开为提前返回的 `return " |
| "Err(From::from(err))`，而 `Ok(ok)` 分支则展开为 `ok` 表达式。" |
| |
| #: src/std/result/question_mark.md:44 |
| msgid "// Intermediate function\n" |
| msgstr "// 中间函数\n" |
| |
| #: src/std/result/question_mark.md:46 |
| msgid "// if `div` \"fails\", then `DivisionByZero` will be `return`ed\n" |
| msgstr "// 如果 `div` \"失败\"，则会 `return` `DivisionByZero`\n" |
| |
| #: src/std/result/question_mark.md:49 |
| msgid "// if `ln` \"fails\", then `NonPositiveLogarithm` will be `return`ed\n" |
| msgstr "// 如果 `ln` \"失败\"，则会 `return` `NonPositiveLogarithm`\n" |
| |
| #: src/std/result/question_mark.md:59 |
| msgid "\"logarithm of non-positive number\"" |
| msgstr "\"非正数的对数\"" |
| |
| #: src/std/result/question_mark.md:61 src/std/panic.md:15 |
| msgid "\"division by zero\"" |
| msgstr "\"除以零\"" |
| |
| #: src/std/result/question_mark.md:63 |
| msgid "\"square root of negative number\"" |
| msgstr "\"负数的平方根\"" |
| |
| #: src/std/result/question_mark.md:75 |
| msgid "" |
| "Be sure to check the [documentation](https://doc.rust-lang.org/std/result/" |
| "index.html), as there are many methods to map/compose `Result`." |
| msgstr "" |
| "请务必查阅 [文档](https://doc.rust-lang.org/std/result/index.html)，其中包含" |
| "了许多用于映射和组合 `Result` 的方法。" |
| |
| #: src/std/panic.md:3 |
| msgid "" |
| "The `panic!` macro can be used to generate a panic and start unwinding its " |
| "stack. While unwinding, the runtime will take care of freeing all the " |
| "resources _owned_ by the thread by calling the destructor of all its objects." |
| msgstr "" |
| "`panic!` 宏可用于生成一个 panic 并开始展开其栈。在展开过程中，运行时会通过调" |
| "用该线程所有对象的析构函数来释放线程**拥有**的所有资源。" |
| |
| #: src/std/panic.md:7 |
| msgid "" |
| "Since we are dealing with programs with only one thread, `panic!` will cause " |
| "the program to report the panic message and exit." |
| msgstr "" |
| "由于我们处理的是只有一个线程的程序，`panic!` 会导致程序报告 panic 消息并退" |
| "出。" |
| |
| #: src/std/panic.md:11 |
| msgid "// Re-implementation of integer division (/)\n" |
| msgstr "// 重新实现整数除法（/）\n" |
| |
| #: src/std/panic.md:14 |
| msgid "// Division by zero triggers a panic\n" |
| msgstr "// 除以零会触发 panic\n" |
| |
| #: src/std/panic.md:20 |
| msgid "// The `main` task\n" |
| msgstr "// `main` 任务\n" |
| |
| #: src/std/panic.md:23 |
| msgid "// Heap allocated integer\n" |
| msgstr "// 堆分配的整数\n" |
| |
| #: src/std/panic.md:26 |
| msgid "// This operation will trigger a task failure\n" |
| msgstr "// 这个操作将触发任务失败\n" |
| |
| #: src/std/panic.md:29 |
| msgid "\"This point won't be reached!\"" |
| msgstr "\"这个点不会被执行到！\"" |
| |
| #: src/std/panic.md:31 |
| msgid "// `_x` should get destroyed at this point\n" |
| msgstr "// `_x` 应该在此处被销毁\n" |
| |
| #: src/std/panic.md:35 |
| msgid "Let's check that `panic!` doesn't leak memory." |
| msgstr "让我们验证 `panic!` 不会导致内存泄漏。" |
| |
| #: src/std/hash.md:3 |
| msgid "" |
| "Where vectors store values by an integer index, `HashMap`s store values by " |
| "key. `HashMap` keys can be booleans, integers, strings, or any other type " |
| "that implements the `Eq` and `Hash` traits. More on this in the next section." |
| msgstr "" |
| "向量（Vector）通过整数索引存储值，而 `HashMap` 则通过键存储值。`HashMap` 的键" |
| "可以是布尔值、整数、字符串，或任何其他实现了 `Eq` 和 `Hash` trait 的类型。下" |
| "一节将详细介绍这一点。" |
| |
| #: src/std/hash.md:8 |
| msgid "" |
| "Like vectors, `HashMap`s are growable, but HashMaps can also shrink " |
| "themselves when they have excess space. You can create a HashMap with a " |
| "certain starting capacity using `HashMap::with_capacity(uint)`, or use " |
| "`HashMap::new()` to get a HashMap with a default initial capacity " |
| "(recommended)." |
| msgstr "" |
| "与向量类似，`HashMap` 也可以增长，但当有多余空间时，HashMap 还能自动收缩。你" |
| "可以使用 `HashMap::with_capacity(uint)` 创建一个具有指定初始容量的 HashMap，" |
| "或使用 `HashMap::new()` 来获得一个具有默认初始容量的 HashMap（推荐）。" |
| |
| #: src/std/hash.md:19 src/std/hash.md:30 |
| msgid "\"798-1364\"" |
| msgstr "\"798-1364\"" |
| |
| #: src/std/hash.md:19 |
| msgid "" |
| "\"We're sorry, the call cannot be completed as dialed. \n" |
| " Please hang up and try again.\"" |
| msgstr "" |
| "\"很抱歉，无法接通您拨打的电话。\n" |
| " 请挂机后重试。\"" |
| |
| #: src/std/hash.md:21 src/std/hash.md:31 |
| msgid "\"645-7689\"" |
| msgstr "\"645-7689\"" |
| |
| #: src/std/hash.md:21 |
| msgid "" |
| "\"Hello, this is Mr. Awesome's Pizza. My name is Fred.\n" |
| " What can I get for you today?\"" |
| msgstr "" |
| "\"您好，这里是 Awesome 先生的披萨店。我是 Fred。\n" |
| " 请问今天您想点些什么？\"" |
| |
| #: src/std/hash.md:23 |
| msgid "\"Hi! Who is this again?\"" |
| msgstr "\"嗨！请问是哪位？\"" |
| |
| #: src/std/hash.md:30 src/std/hash.md:36 src/std/hash.md:43 |
| msgid "\"Daniel\"" |
| msgstr "\"Daniel\"" |
| |
| #: src/std/hash.md:31 src/std/hash.md:45 src/std/hash.md:50 |
| msgid "\"Ashley\"" |
| msgstr "\"Ashley\"" |
| |
| #: src/std/hash.md:32 |
| msgid "\"Katie\"" |
| msgstr "\"Katie\"" |
| |
| #: src/std/hash.md:32 |
| msgid "\"435-8291\"" |
| msgstr "\"435-8291\"" |
| |
| #: src/std/hash.md:33 |
| msgid "\"Robert\"" |
| msgstr "\"Robert\"" |
| |
| #: src/std/hash.md:33 |
| msgid "\"956-1745\"" |
| msgstr "\"956-1745\"" |
| |
| #: src/std/hash.md:35 |
| msgid "// Takes a reference and returns Option<&V>\n" |
| msgstr "// 接受一个引用并返回 Option<&V>\n" |
| |
| #: src/std/hash.md:37 |
| msgid "\"Calling Daniel: {}\"" |
| msgstr "\"正在呼叫 Daniel：{}\"" |
| |
| #: src/std/hash.md:38 |
| msgid "\"Don't have Daniel's number.\"" |
| msgstr "\"没有 Daniel 的电话号码。\"" |
| |
| #: src/std/hash.md:41 |
| msgid "" |
| "// `HashMap::insert()` returns `None`\n" |
| " // if the inserted value is new, `Some(value)` otherwise\n" |
| msgstr "" |
| "// 如果插入的值是新的，`HashMap::insert()` 返回 `None`\n" |
| " // 否则返回 `Some(value)`\n" |
| |
| #: src/std/hash.md:43 |
| msgid "\"164-6743\"" |
| msgstr "\"164-6743\"" |
| |
| #: src/std/hash.md:46 |
| msgid "\"Calling Ashley: {}\"" |
| msgstr "\"正在呼叫 Ashley：{}\"" |
| |
| #: src/std/hash.md:47 |
| msgid "\"Don't have Ashley's number.\"" |
| msgstr "\"没有 Ashley 的电话号码。\"" |
| |
| #: src/std/hash.md:52 |
| msgid "" |
| "// `HashMap::iter()` returns an iterator that yields \n" |
| " // (&'a key, &'a value) pairs in arbitrary order.\n" |
| msgstr "" |
| "// `HashMap::iter()` 返回一个迭代器，该迭代器以任意顺序生成\n" |
| " // (&'a key, &'a value) 键值对。\n" |
| |
| #: src/std/hash.md:55 |
| msgid "\"Calling {}: {}\"" |
| msgstr "\"正在呼叫{}：{}\"" |
| |
| #: src/std/hash.md:60 |
| msgid "" |
| "For more information on how hashing and hash maps (sometimes called hash " |
| "tables) work, have a look at [Hash Table Wikipedia](https://en.wikipedia.org/" |
| "wiki/Hash_table)" |
| msgstr "" |
| "要了解更多关于哈希和哈希映射（有时称为哈希表）的工作原理，请参阅[哈希表的维基" |
| "百科页面](https://en.wikipedia.org/wiki/Hash_table)" |
| |
| #: src/std/hash/alt_key_types.md:3 |
| msgid "" |
| "Any type that implements the `Eq` and `Hash` traits can be a key in " |
| "`HashMap`. This includes:" |
| msgstr "" |
| "任何实现了 `Eq` 和 `Hash` trait 的类型都可以作为 `HashMap` 的键。这包括：" |
| |
| #: src/std/hash/alt_key_types.md:6 |
| msgid "`bool` (though not very useful since there are only two possible keys)" |
| msgstr "`bool`（虽然用处不大，因为只有两个可能的键值）" |
| |
| #: src/std/hash/alt_key_types.md:7 |
| msgid "`int`, `uint`, and all variations thereof" |
| msgstr "`int`、`uint` 及其所有变体" |
| |
| #: src/std/hash/alt_key_types.md:8 |
| msgid "" |
| "`String` and `&str` (protip: you can have a `HashMap` keyed by `String` and " |
| "call `.get()` with an `&str`)" |
| msgstr "" |
| "`String` 和 `&str`（专业提示：你可以使用 `String` 作为 `HashMap` 的键，并用 " |
| "`&str` 调用 `.get()` 方法）" |
| |
| #: src/std/hash/alt_key_types.md:11 |
| msgid "" |
| "Note that `f32` and `f64` do _not_ implement `Hash`, likely because " |
| "[floating-point precision errors](https://en.wikipedia.org/wiki/" |
| "Floating_point#Accuracy_problems) would make using them as hashmap keys " |
| "horribly error-prone." |
| msgstr "" |
| "注意，`f32` 和 `f64` **并未**实现 `Hash` trait，这很可能是因为[浮点数精度误" |
| "差](https://en.wikipedia.org/wiki/Floating_point#Accuracy_problems)会导致将它" |
| "们用作哈希映射的键时极易出错。" |
| |
| #: src/std/hash/alt_key_types.md:15 |
| msgid "" |
| "All collection classes implement `Eq` and `Hash` if their contained type " |
| "also respectively implements `Eq` and `Hash`. For example, `Vec<T>` will " |
| "implement `Hash` if `T` implements `Hash`." |
| msgstr "" |
| "如果集合类中包含的类型分别实现了 `Eq` 和 `Hash`，那么这些集合类也会实现 `Eq` " |
| "和 `Hash`。例如，如果 `T` 实现了 `Hash`，那么 `Vec<T>` 也会实现 `Hash`。" |
| |
| #: src/std/hash/alt_key_types.md:19 |
| msgid "" |
| "You can easily implement `Eq` and `Hash` for a custom type with just one " |
| "line: `#[derive(PartialEq, Eq, Hash)]`" |
| msgstr "" |
| "你可以通过一行代码轻松地为自定义类型实现 `Eq` 和 `Hash`：" |
| "`#[derive(PartialEq, Eq, Hash)]`" |
| |
| #: src/std/hash/alt_key_types.md:22 |
| msgid "" |
| "The compiler will do the rest. If you want more control over the details, " |
| "you can implement `Eq` and/or `Hash` yourself. This guide will not cover the " |
| "specifics of implementing `Hash`." |
| msgstr "" |
| "编译器会完成剩余的工作。如果你想对细节有更多控制，可以自己实现 `Eq` 和/或 " |
| "`Hash`。本指南不会涉及实现 `Hash` 的具体细节。" |
| |
| #: src/std/hash/alt_key_types.md:26 |
| msgid "" |
| "To play around with using a `struct` in `HashMap`, let's try making a very " |
| "simple user logon system:" |
| msgstr "" |
| "为了尝试在 `HashMap` 中使用 `struct`，让我们来创建一个非常简单的用户登录系" |
| "统：" |
| |
| #: src/std/hash/alt_key_types.md:31 |
| msgid "// Eq requires that you derive PartialEq on the type.\n" |
| msgstr "// Eq 要求你在类型上派生 PartialEq。\n" |
| |
| #: src/std/hash/alt_key_types.md:48 |
| msgid "\"Username: {}\"" |
| msgstr "\"用户名：{}\"" |
| |
| #: src/std/hash/alt_key_types.md:49 |
| msgid "\"Password: {}\"" |
| msgstr "\"密码：{}\"" |
| |
| #: src/std/hash/alt_key_types.md:50 |
| msgid "\"Attempting logon...\"" |
| msgstr "\"正在尝试登录...\"" |
| |
| #: src/std/hash/alt_key_types.md:59 |
| msgid "\"Successful logon!\"" |
| msgstr "\"登录成功！\"" |
| |
| #: src/std/hash/alt_key_types.md:60 |
| msgid "\"Name: {}\"" |
| msgstr "\"姓名：{}\"" |
| |
| #: src/std/hash/alt_key_types.md:61 |
| msgid "\"Email: {}\"" |
| msgstr "\"电子邮箱：{}\"" |
| |
| #: src/std/hash/alt_key_types.md:63 |
| msgid "\"Login failed!\"" |
| msgstr "\"登录失败！\"" |
| |
| #: src/std/hash/alt_key_types.md:71 src/std/hash/alt_key_types.md:82 |
| #: src/std/hash/alt_key_types.md:84 |
| msgid "\"j.everyman\"" |
| msgstr "\"j.everyman\"" |
| |
| #: src/std/hash/alt_key_types.md:72 src/std/hash/alt_key_types.md:84 |
| msgid "\"password123\"" |
| msgstr "\"password123\"" |
| |
| #: src/std/hash/alt_key_types.md:76 |
| msgid "\"John Everyman\"" |
| msgstr "\"John Everyman\"" |
| |
| #: src/std/hash/alt_key_types.md:77 |
| msgid "\"j.everyman@email.com\"" |
| msgstr "\"j.everyman@email.com\"" |
| |
| #: src/std/hash/alt_key_types.md:82 |
| msgid "\"psasword123\"" |
| msgstr "\"psasword123\"" |
| |
| #: src/std/hash/hashset.md:3 |
| msgid "" |
| "Consider a `HashSet` as a `HashMap` where we just care about the keys " |
| "( `HashSet<T>` is, in actuality, just a wrapper around `HashMap<T, ()>`)." |
| msgstr "" |
| "可以将 `HashSet` 视为一个只关心键的 `HashMap`（实际上，`HashSet<T>` 只是 " |
| "`HashMap<T, ()>` 的封装）。" |
| |
| #: src/std/hash/hashset.md:6 |
| msgid "" |
| "\"What's the point of that?\" you ask. \"I could just store the keys in a " |
| "`Vec`.\"" |
| msgstr "你可能会问：\"这有什么意义？我可以直接把键存储在 `Vec` 中啊。\"" |
| |
| #: src/std/hash/hashset.md:8 |
| msgid "" |
| "A `HashSet`'s unique feature is that it is guaranteed to not have duplicate " |
| "elements. That's the contract that any set collection fulfills. `HashSet` is " |
| "just one implementation. (see also: [`BTreeSet`](https://doc.rust-lang.org/" |
| "std/collections/struct.BTreeSet.html))" |
| msgstr "" |
| "`HashSet` 的独特之处在于它保证不会有重复元素。这是所有集合类型都应满足的约" |
| "定。`HashSet` 只是其中一种实现。（另请参阅：[`BTreeSet`](https://doc.rust-" |
| "lang.org/std/collections/struct.BTreeSet.html)）" |
| |
| #: src/std/hash/hashset.md:13 |
| msgid "" |
| "If you insert a value that is already present in the `HashSet`, (i.e. the " |
| "new value is equal to the existing and they both have the same hash), then " |
| "the new value will replace the old." |
| msgstr "" |
| "如果你插入一个已存在于 `HashSet` 中的值（即新值等于现有值，且它们的哈希值相" |
| "同），那么新值将替换旧值。" |
| |
| #: src/std/hash/hashset.md:17 |
| msgid "" |
| "This is great for when you never want more than one of something, or when " |
| "you want to know if you've already got something." |
| msgstr "" |
| "当你不希望某个元素出现多次，或者想知道是否已经拥有某个元素时，这非常有用。" |
| |
| #: src/std/hash/hashset.md:20 |
| msgid "But sets can do more than that." |
| msgstr "但是集合的功能不仅限于此。" |
| |
| #: src/std/hash/hashset.md:22 |
| msgid "" |
| "Sets have 4 primary operations (all of the following calls return an " |
| "iterator):" |
| msgstr "集合有 4 种主要操作（以下所有调用都返回一个迭代器）：" |
| |
| #: src/std/hash/hashset.md:24 |
| msgid "`union`: get all the unique elements in both sets." |
| msgstr "并集（`union`）：获取两个集合中的所有唯一元素。" |
| |
| #: src/std/hash/hashset.md:26 |
| msgid "" |
| "`difference`: get all the elements that are in the first set but not the " |
| "second." |
| msgstr "" |
| "差集（`difference`）：获取存在于第一个集合但不在第二个集合中的所有元素。" |
| |
| #: src/std/hash/hashset.md:28 |
| msgid "`intersection`: get all the elements that are only in _both_ sets." |
| msgstr "交集（`intersection`）：获取**同时**存在于两个集合中的所有元素。" |
| |
| #: src/std/hash/hashset.md:30 |
| msgid "" |
| "`symmetric_difference`: get all the elements that are in one set or the " |
| "other, but _not_ both." |
| msgstr "" |
| "对称差（`symmetric_difference`）：获取存在于其中一个集合中，但**不**同时存在" |
| "于两个集合中的所有元素。" |
| |
| #: src/std/hash/hashset.md:33 |
| msgid "Try all of these in the following example:" |
| msgstr "在下面的例子中尝试这些操作：" |
| |
| #: src/std/hash/hashset.md:45 |
| msgid "" |
| "// `HashSet::insert()` returns false if\n" |
| " // there was a value already present.\n" |
| msgstr "// 如果集合中已存在该值，`HashSet::insert()` 将返回 false。\n" |
| |
| #: src/std/hash/hashset.md:47 |
| msgid "\"Value 4 is already in set B!\"" |
| msgstr "\"值 4 已存在于集合 B 中！\"" |
| |
| #: src/std/hash/hashset.md:52 |
| msgid "" |
| "// If a collection's element type implements `Debug`,\n" |
| " // then the collection implements `Debug`.\n" |
| " // It usually prints its elements in the format `[elem1, elem2, ...]`\n" |
| msgstr "" |
| "// 如果集合的元素类型实现了 `Debug` 特征，\n" |
| " // 那么该集合也会实现 `Debug` 特征。\n" |
| " // 通常会以 `[elem1, elem2, ...]` 的格式打印其元素\n" |
| |
| #: src/std/hash/hashset.md:55 |
| msgid "\"A: {:?}\"" |
| msgstr "\"A：{:?}\"" |
| |
| #: src/std/hash/hashset.md:56 |
| msgid "\"B: {:?}\"" |
| msgstr "\"B：{:?}\"" |
| |
| #: src/std/hash/hashset.md:58 |
| msgid "// Print [1, 2, 3, 4, 5] in arbitrary order\n" |
| msgstr "// 以任意顺序打印 [1, 2, 3, 4, 5]\n" |
| |
| #: src/std/hash/hashset.md:59 |
| msgid "\"Union: {:?}\"" |
| msgstr "\"并集：{:?}\"" |
| |
| #: src/std/hash/hashset.md:61 |
| msgid "// This should print [1]\n" |
| msgstr "// 这里应该打印 [1]\n" |
| |
| #: src/std/hash/hashset.md:62 |
| msgid "\"Difference: {:?}\"" |
| msgstr "\"差集：{:?}\"" |
| |
| #: src/std/hash/hashset.md:64 |
| msgid "// Print [2, 3, 4] in arbitrary order.\n" |
| msgstr "// 以任意顺序打印 [2, 3, 4]\n" |
| |
| #: src/std/hash/hashset.md:65 |
| msgid "\"Intersection: {:?}\"" |
| msgstr "\"交集：{:?}\"" |
| |
| #: src/std/hash/hashset.md:67 |
| msgid "// Print [1, 5]\n" |
| msgstr "// 打印 [1, 5]\n" |
| |
| #: src/std/hash/hashset.md:68 |
| msgid "\"Symmetric Difference: {:?}\"" |
| msgstr "\"对称差：{:?}\"" |
| |
| #: src/std/hash/hashset.md:73 |
| msgid "" |
| "(Examples are adapted from the [documentation.](https://doc.rust-lang.org/" |
| "std/collections/struct.HashSet.html#method.difference))" |
| msgstr "" |
| "（示例改编自[官方文档](https://doc.rust-lang.org/std/collections/" |
| "struct.HashSet.html#method.difference)）" |
| |
| #: src/std/rc.md:3 |
| msgid "" |
| "When multiple ownership is needed, `Rc`(Reference Counting) can be used. " |
| "`Rc` keeps track of the number of the references which means the number of " |
| "owners of the value wrapped inside an `Rc`." |
| msgstr "" |
| "当需要多重所有权时，可以使用 `Rc`（引用计数，Reference Counting）。`Rc` 会跟" |
| "踪引用的数量，即包裹在 `Rc` 内部的值的所有者数量。" |
| |
| #: src/std/rc.md:7 |
| msgid "" |
| "Reference count of an `Rc` increases by 1 whenever an `Rc` is cloned, and " |
| "decreases by 1 whenever one cloned `Rc` is dropped out of the scope. When an " |
| "`Rc`'s reference count becomes zero (which means there are no remaining " |
| "owners), both the `Rc` and the value are all dropped." |
| msgstr "" |
| "每当克隆一个 `Rc` 时，其引用计数就会增加 1；每当一个克隆的 `Rc` 离开作用域" |
| "时，引用计数就会减少 1。当 `Rc` 的引用计数变为零（意味着没有剩余的所有者）" |
| "时，`Rc` 及其包含的值都会被丢弃。" |
| |
| #: src/std/rc.md:12 |
| msgid "" |
| "Cloning an `Rc` never performs a deep copy. Cloning creates just another " |
| "pointer to the wrapped value, and increments the count." |
| msgstr "" |
| "克隆 `Rc` 从不执行深拷贝。克隆只是创建另一个指向被包裹值的指针，并增加计数。" |
| |
| #: src/std/rc.md:19 |
| msgid "\"Rc examples\"" |
| msgstr "\"Rc 示例\"" |
| |
| #: src/std/rc.md:21 |
| msgid "\"--- rc_a is created ---\"" |
| msgstr "\"--- rc_a 已创建 ---\"" |
| |
| #: src/std/rc.md:24 src/std/rc.md:31 src/std/rc.md:43 |
| msgid "\"Reference Count of rc_a: {}\"" |
| msgstr "\"rc_a 的引用计数：{}\"" |
| |
| #: src/std/rc.md:27 |
| msgid "\"--- rc_a is cloned to rc_b ---\"" |
| msgstr "\"--- rc_a 被克隆为 rc_b ---\"" |
| |
| #: src/std/rc.md:30 |
| msgid "\"Reference Count of rc_b: {}\"" |
| msgstr "\"rc_b 的引用计数：{}\"" |
| |
| #: src/std/rc.md:33 |
| msgid "// Two `Rc`s are equal if their inner values are equal\n" |
| msgstr "// 两个 `Rc` 如果内部值相等，则它们相等\n" |
| |
| #: src/std/rc.md:34 |
| msgid "\"rc_a and rc_b are equal: {}\"" |
| msgstr "\"rc_a 和 rc_b 是否相等：{}\"" |
| |
| #: src/std/rc.md:36 |
| msgid "// We can use methods of a value directly\n" |
| msgstr "// 我们可以直接使用值的方法\n" |
| |
| #: src/std/rc.md:37 |
| msgid "\"Length of the value inside rc_a: {}\"" |
| msgstr "\"rc_a 内部值的长度：{}\"" |
| |
| #: src/std/rc.md:38 |
| msgid "\"Value of rc_b: {}\"" |
| msgstr "\"rc_b 的值：{}\"" |
| |
| #: src/std/rc.md:40 |
| msgid "\"--- rc_b is dropped out of scope ---\"" |
| msgstr "\"--- rc_b 超出作用域被释放 ---\"" |
| |
| #: src/std/rc.md:45 |
| msgid "\"--- rc_a is dropped out of scope ---\"" |
| msgstr "\"--- rc_a 超出作用域被释放 ---\"" |
| |
| #: src/std/rc.md:48 |
| msgid "" |
| "// Error! `rc_examples` already moved into `rc_a`\n" |
| " // And when `rc_a` is dropped, `rc_examples` is dropped together\n" |
| " // println!(\"rc_examples: {}\", rc_examples);\n" |
| " // TODO ^ Try uncommenting this line\n" |
| msgstr "" |
| "// 错误！`rc_examples` 已经被移动到 `rc_a` 中\n" |
| " // 当 `rc_a` 被释放时，`rc_examples` 也会一同被释放\n" |
| " // println!(\"rc_examples: {}\", rc_examples);\n" |
| " // TODO：尝试取消注释上面这行\n" |
| |
| #: src/std/rc.md:57 |
| msgid "" |
| "[std::rc](https://doc.rust-lang.org/std/rc/index.html) and [std::sync::arc]" |
| "(https://doc.rust-lang.org/std/sync/struct.Arc.html)." |
| msgstr "" |
| "[`std::rc`](https://doc.rust-lang.org/std/rc/index.html) 和 " |
| "[`std::sync::arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html)。" |
| |
| #: src/std/arc.md:1 |
| msgid "Arc" |
| msgstr "Arc（原子引用计数）" |
| |
| #: src/std/arc.md:3 |
| msgid "" |
| "When shared ownership between threads is needed, `Arc`(Atomically Reference " |
| "Counted) can be used. This struct, via the `Clone` implementation can create " |
| "a reference pointer for the location of a value in the memory heap while " |
| "increasing the reference counter. As it shares ownership between threads, " |
| "when the last reference pointer to a value is out of scope, the variable is " |
| "dropped." |
| msgstr "" |
| "当需要在线程间共享所有权时，可以使用 `Arc`（原子引用计数，Atomically " |
| "Reference Counted）。通过 `Clone` 实现，这个结构体可以为堆内存中值的位置创建" |
| "一个引用指针，同时增加引用计数。由于它在线程间共享所有权，当指向某个值的最后" |
| "一个引用指针超出作用域时，该变量就会被释放。" |
| |
| #: src/std/arc.md:15 |
| msgid "// This variable declaration is where its value is specified.\n" |
| msgstr "// 在这个变量声明中指定了它的值。\n" |
| |
| #: src/std/arc.md:16 |
| msgid "\"the same apple\"" |
| msgstr "\"同一个苹果\"" |
| |
| #: src/std/arc.md:19 |
| msgid "" |
| "// Here there is no value specification as it is a pointer to a\n" |
| " // reference in the memory heap.\n" |
| msgstr "// 这里没有指定值，因为它是指向堆内存中引用的指针。\n" |
| |
| #: src/std/arc.md:24 |
| msgid "" |
| "// As Arc was used, threads can be spawned using the value allocated\n" |
| " // in the Arc variable pointer's location.\n" |
| msgstr "// 由于使用了 Arc，可以使用 Arc 变量指针所指向的值来生成线程。\n" |
| |
| #: src/std/arc.md:30 |
| msgid "// Make sure all Arc instances are printed from spawned threads.\n" |
| msgstr "// 确保所有 Arc 实例都从生成的线程中打印出来。\n" |
| |
| #: src/std_misc.md:3 |
| msgid "" |
| "Many other types are provided by the std library to support things such as:" |
| msgstr "标准库提供了许多其他类型来支持各种功能，例如：" |
| |
| #: src/std_misc.md:10 |
| msgid "These expand beyond what the [primitives](primitives.md) provide." |
| msgstr "这些类型扩展了[基本类型](primitives.md)所提供的功能。" |
| |
| #: src/std_misc/threads.md:3 |
| msgid "" |
| "Rust provides a mechanism for spawning native OS threads via the `spawn` " |
| "function, the argument of this function is a moving closure." |
| msgstr "" |
| "Rust 通过 `spawn` 函数提供了一种生成原生操作系统线程的机制，该函数的参数是一" |
| "个移动闭包。" |
| |
| #: src/std_misc/threads.md:10 src/std_misc/threads/testcase_mapreduce.md:28 |
| msgid "// This is the `main` thread\n" |
| msgstr "// 这是主线程\n" |
| |
| #: src/std_misc/threads.md:13 |
| msgid "// Make a vector to hold the children which are spawned.\n" |
| msgstr "// 创建一个向量来存储生成的子线程\n" |
| |
| #: src/std_misc/threads.md:17 |
| msgid "// Spin up another thread\n" |
| msgstr "// 启动一个新线程\n" |
| |
| #: src/std_misc/threads.md:19 |
| msgid "\"this is thread number {}\"" |
| msgstr "\"这是第 {} 号线程\"" |
| |
| #: src/std_misc/threads.md:24 |
| msgid "// Wait for the thread to finish. Returns a result.\n" |
| msgstr "// 等待线程完成，返回一个结果\n" |
| |
| #: src/std_misc/threads.md:30 |
| msgid "These threads will be scheduled by the OS." |
| msgstr "这些线程将由操作系统进行调度。" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:3 |
| msgid "" |
| "Rust makes it very easy to parallelize data processing, without many of the " |
| "headaches traditionally associated with such an attempt." |
| msgstr "Rust 使并行数据处理变得非常简单，避免了传统并行处理中常见的诸多问题。" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:5 |
| msgid "" |
| "The standard library provides great threading primitives out of the box. " |
| "These, combined with Rust's concept of Ownership and aliasing rules, " |
| "automatically prevent data races." |
| msgstr "" |
| "标准库提供了开箱即用的优秀线程原语。这些原语结合 Rust 的所有权概念和别名规" |
| "则，自动防止了数据竞争。" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:9 |
| msgid "" |
| "The aliasing rules (one writable reference XOR many readable references) " |
| "automatically prevent you from manipulating state that is visible to other " |
| "threads. (Where synchronization is needed, there are synchronization " |
| "primitives like `Mutex`es or `Channel`s.)" |
| msgstr "" |
| "别名规则（一个可写引用异或多个可读引用）自动防止你操作对其他线程可见的状态。" |
| "（在需要同步的情况下，可以使用 `Mutex` 或 `Channel` 等同步原语。）" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:14 |
| msgid "" |
| "In this example, we will calculate the sum of all digits in a block of " |
| "numbers. We will do this by parcelling out chunks of the block into " |
| "different threads. Each thread will sum its tiny block of digits, and " |
| "subsequently we will sum the intermediate sums produced by each thread." |
| msgstr "" |
| "在这个例子中，我们将计算一个数字块中所有数字的总和。我们通过将数字块分成小块" |
| "并分配给不同的线程来完成这个任务。每个线程将计算其小块数字的总和，随后我们将" |
| "汇总每个线程产生的中间结果。" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:19 |
| msgid "" |
| "Note that, although we're passing references across thread boundaries, Rust " |
| "understands that we're only passing read-only references, and that thus no " |
| "unsafety or data races can occur. Also because the references we're passing " |
| "have `'static` lifetimes, Rust understands that our data won't be destroyed " |
| "while these threads are still running. (When you need to share non-`static` " |
| "data between threads, you can use a smart pointer like `Arc` to keep the " |
| "data alive and avoid non-`static` lifetimes.)" |
| msgstr "" |
| "注意，尽管我们在线程间传递引用，但 Rust 理解我们只是传递只读引用，因此不会发" |
| "生不安全操作或数据竞争。此外，由于我们传递的引用具有 `'static` 生命周期，" |
| "Rust 确保这些线程运行时数据不会被销毁。（当需要在线程间共享非 `static` 数据" |
| "时，可以使用 `Arc` 等智能指针来保持数据存活并避免非 `static` 生命周期。）" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:32 |
| msgid "" |
| "// This is our data to process.\n" |
| " // We will calculate the sum of all digits via a threaded map-reduce " |
| "algorithm.\n" |
| " // Each whitespace separated chunk will be handled in a different " |
| "thread.\n" |
| " //\n" |
| " // TODO: see what happens to the output if you insert spaces!\n" |
| msgstr "" |
| "// 这是我们要处理的数据\n" |
| " // 我们将通过一个线程化的 map-reduce 算法计算所有数字的总和\n" |
| " // 每个由空格分隔的块将在不同的线程中处理\n" |
| " //\n" |
| " // TODO：试试插入空格会对输出有什么影响！\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:37 |
| msgid "" |
| "\"86967897737416471853297327050364959\n" |
| "11861322575564723963297542624962850\n" |
| "70856234701860851907960690014725639\n" |
| "38397966707106094172783238747669219\n" |
| "52380795257888236525459303330302837\n" |
| "58495327135744041048897885734297812\n" |
| "69920216438980873548808413720956532\n" |
| "16278424637452589860345374828574668\"" |
| msgstr "" |
| "\"86967897737416471853297327050364959\n" |
| "11861322575564723963297542624962850\n" |
| "70856234701860851907960690014725639\n" |
| "38397966707106094172783238747669219\n" |
| "52380795257888236525459303330302837\n" |
| "58495327135744041048897885734297812\n" |
| "69920216438980873548808413720956532\n" |
| "16278424637452589860345374828574668\"" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:46 |
| msgid "// Make a vector to hold the child-threads which we will spawn.\n" |
| msgstr "// 创建一个向量来存储我们将要生成的子线程。\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:49 |
| msgid "" |
| "/*************************************************************************\n" |
| " * \"Map\" phase\n" |
| " *\n" |
| " * Divide our data into segments, and apply initial processing\n" |
| " ************************************************************************/" |
| msgstr "" |
| "/*************************************************************************\n" |
| " * \"Map\"阶段\n" |
| " *\n" |
| " * 将数据分割成多个段，并进行初步处理\n" |
| " ************************************************************************/" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:55 |
| msgid "" |
| "// split our data into segments for individual calculation\n" |
| " // each chunk will be a reference (&str) into the actual data\n" |
| msgstr "" |
| "// 将数据分割成多个段以进行单独计算\n" |
| " // 每个数据块都是指向实际数据的引用（&str）\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:59 |
| msgid "" |
| "// Iterate over the data segments.\n" |
| " // .enumerate() adds the current loop index to whatever is iterated\n" |
| " // the resulting tuple \"(index, element)\" is then immediately\n" |
| " // \"destructured\" into two variables, \"i\" and \"data_segment\" with " |
| "a\n" |
| " // \"destructuring assignment\"\n" |
| msgstr "" |
| "// 遍历数据段\n" |
| " // .enumerate() 为迭代的每个元素添加当前循环索引\n" |
| " // 生成的元组\"(索引, 元素)\"随后立即通过\n" |
| " // \"解构赋值\"被\"解构\"为两个变量：\"i\"和\"data_segment\"\n" |
| " // \n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:65 |
| msgid "\"data segment {} is \\\"{}\\\"\"" |
| msgstr "\"数据段 {} 是\\\"{}\\\"\"" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:67 |
| msgid "" |
| "// Process each data segment in a separate thread\n" |
| " //\n" |
| " // spawn() returns a handle to the new thread,\n" |
| " // which we MUST keep to access the returned value\n" |
| " //\n" |
| " // 'move || -> u32' is syntax for a closure that:\n" |
| " // * takes no arguments ('||')\n" |
| " // * takes ownership of its captured variables ('move') and\n" |
| " // * returns an unsigned 32-bit integer ('-> u32')\n" |
| " //\n" |
| " // Rust is smart enough to infer the '-> u32' from\n" |
| " // the closure itself so we could have left that out.\n" |
| " //\n" |
| " // TODO: try removing the 'move' and see what happens\n" |
| msgstr "" |
| "// 在单独的线程中处理每个数据段\n" |
| " //\n" |
| " // spawn() 返回新线程的句柄，\n" |
| " // 我们必须保留该句柄以访问返回值\n" |
| " //\n" |
| " // 'move || -> u32' 是一个闭包的语法，它：\n" |
| " // * 不接受参数（'||'）\n" |
| " // * 获取其捕获变量的所有权（'move'）\n" |
| " // * 返回一个无符号 32 位整数（'-> u32'）\n" |
| " //\n" |
| " // Rust 足够智能，能从闭包本身推断出 '-> u32'，\n" |
| " // 所以我们可以省略它。\n" |
| " //\n" |
| " // TODO：尝试移除 'move' 并观察结果\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:82 |
| msgid "// Calculate the intermediate sum of this segment:\n" |
| msgstr "// 计算此段的中间和：\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:84 |
| msgid "// iterate over the characters of our segment..\n" |
| msgstr "// 遍历此段中的字符...\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:86 |
| msgid "// .. convert text-characters to their number value..\n" |
| msgstr "// ...将文本字符转换为对应的数值...\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:87 |
| msgid "\"should be a digit\"" |
| msgstr "\"应该是一个数字\"" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:88 |
| msgid "// .. and sum the resulting iterator of numbers\n" |
| msgstr "// ...并对结果数字迭代器求和\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:91 |
| msgid "// println! locks stdout, so no text-interleaving occurs\n" |
| msgstr "// println! 会锁定标准输出，因此不会出现文本交错\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:92 |
| msgid "\"processed segment {}, result={}\"" |
| msgstr "\"已处理段 {}，结果={}\"" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:94 |
| msgid "" |
| "// \"return\" not needed, because Rust is an \"expression language\", the\n" |
| " // last evaluated expression in each block is automatically its " |
| "value.\n" |
| msgstr "" |
| "// 不需要使用 \"return\"，因为 Rust 是一种\"表达式语言\"，\n" |
| "// 每个代码块中最后求值的表达式会自动成为该块的返回值。\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:102 |
| msgid "" |
| "/*************************************************************************\n" |
| " * \"Reduce\" phase\n" |
| " *\n" |
| " * Collect our intermediate results, and combine them into a final " |
| "result\n" |
| " ************************************************************************/" |
| msgstr "" |
| "/*************************************************************************\n" |
| " * \"归约\"阶段\n" |
| " *\n" |
| " * 收集中间结果，并将它们合并成最终结果\n" |
| " ************************************************************************/" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:108 |
| msgid "" |
| "// combine each thread's intermediate results into a single final sum.\n" |
| " //\n" |
| " // we use the \"turbofish\" ::<> to provide sum() with a type hint.\n" |
| " //\n" |
| " // TODO: try without the turbofish, by instead explicitly\n" |
| " // specifying the type of final_result\n" |
| msgstr "" |
| "// 将每个线程的中间结果合并成一个最终总和。\n" |
| " //\n" |
| " // 我们使用 \"turbofish\" ::<> 为 sum() 提供类型提示。\n" |
| " //\n" |
| " // TODO：尝试不使用 turbofish，而是显式\n" |
| " // 指定 final_result 的类型\n" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:116 |
| msgid "\"Final sum result: {}\"" |
| msgstr "\"最终求和结果：{}\"" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:122 |
| msgid "Assignments" |
| msgstr "练习" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:124 |
| msgid "" |
| "It is not wise to let our number of threads depend on user inputted data. " |
| "What if the user decides to insert a lot of spaces? Do we _really_ want to " |
| "spawn 2,000 threads? Modify the program so that the data is always chunked " |
| "into a limited number of chunks, defined by a static constant at the " |
| "beginning of the program." |
| msgstr "" |
| "让线程数量依赖于用户输入的数据并不明智。如果用户决定插入大量空格，我们真的想" |
| "要创建 2,000 个线程吗？修改程序，使数据始终被分割成固定数量的块，这个数量应由" |
| "程序开头定义的静态常量来确定。" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:131 |
| msgid "[Threads](../threads.md)" |
| msgstr "[线程](../threads.md)" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:132 |
| msgid "[vectors](../../std/vec.md) and [iterators](../../trait/iter.md)" |
| msgstr "[向量](../../std/vec.md)和[迭代器](../../trait/iter.md)" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:133 |
| msgid "" |
| "[closures](../../fn/closures.md), [move](../../scope/move.md) semantics and " |
| "[`move` closures](https://doc.rust-lang.org/book/ch13-01-" |
| "closures.html#closures-can-capture-their-environment)" |
| msgstr "" |
| "[闭包](../../fn/closures.md)、[move](../../scope/move.md) 语义和 [`move` 闭" |
| "包](https://doc.rust-lang.org/book/ch13-01-closures.html#closures-can-" |
| "capture-their-environment)" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:134 |
| msgid "" |
| "[destructuring](https://doc.rust-lang.org/book/ch18-03-pattern-" |
| "syntax.html#destructuring-to-break-apart-values) assignments" |
| msgstr "" |
| "[解构](https://doc.rust-lang.org/book/ch18-03-pattern-" |
| "syntax.html#destructuring-to-break-apart-values)赋值" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:135 |
| msgid "" |
| "[turbofish notation](https://doc.rust-lang.org/book/appendix-02-" |
| "operators.html?highlight=turbofish) to help type inference" |
| msgstr "" |
| "[涡轮鱼符号](https://doc.rust-lang.org/book/appendix-02-operators.html?" |
| "highlight=turbofish)用于辅助类型推断" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:136 |
| msgid "[unwrap vs. expect](../../error/option_unwrap.md)" |
| msgstr "[unwrap 与 expect](../../error/option_unwrap.md)" |
| |
| #: src/std_misc/threads/testcase_mapreduce.md:137 |
| msgid "[enumerate](https://doc.rust-lang.org/book/loops.html#enumerate)" |
| msgstr "[enumerate](https://doc.rust-lang.org/book/loops.html#enumerate)" |
| |
| #: src/std_misc/channels.md:3 |
| msgid "" |
| "Rust provides asynchronous `channels` for communication between threads. " |
| "Channels allow a unidirectional flow of information between two end-points: " |
| "the `Sender` and the `Receiver`." |
| msgstr "" |
| "Rust 提供异步通道（`channels`）用于线程间通信。通道允许信息在两个端点之间单向" |
| "流动：发送端（`Sender`）和接收端（`Receiver`）。" |
| |
| #: src/std_misc/channels.md:15 |
| msgid "" |
| "// Channels have two endpoints: the `Sender<T>` and the `Receiver<T>`,\n" |
| " // where `T` is the type of the message to be transferred\n" |
| " // (type annotation is superfluous)\n" |
| msgstr "" |
| "// 通道有两个端点：`Sender<T>` 和 `Receiver<T>`，\n" |
| " // 其中 `T` 是要传输的消息类型\n" |
| " // （此处的类型注解是多余的）\n" |
| |
| #: src/std_misc/channels.md:22 |
| msgid "// The sender endpoint can be copied\n" |
| msgstr "// 发送端可以被复制\n" |
| |
| #: src/std_misc/channels.md:25 |
| msgid "// Each thread will send its id via the channel\n" |
| msgstr "// 每个线程将通过通道发送其 ID\n" |
| |
| #: src/std_misc/channels.md:27 |
| msgid "" |
| "// The thread takes ownership over `thread_tx`\n" |
| " // Each thread queues a message in the channel\n" |
| msgstr "" |
| "// 线程获取 `thread_tx` 的所有权\n" |
| " // 每个线程在通道中排队一条消息\n" |
| |
| #: src/std_misc/channels.md:31 |
| msgid "" |
| "// Sending is a non-blocking operation, the thread will continue\n" |
| " // immediately after sending its message\n" |
| msgstr "" |
| "// 发送是非阻塞操作，线程在发送消息后\n" |
| " // 会立即继续执行\n" |
| |
| #: src/std_misc/channels.md:33 |
| msgid "\"thread {} finished\"" |
| msgstr "\"线程 {} 已完成\"" |
| |
| #: src/std_misc/channels.md:39 |
| msgid "// Here, all the messages are collected\n" |
| msgstr "// 在这里收集所有消息\n" |
| |
| #: src/std_misc/channels.md:42 |
| msgid "" |
| "// The `recv` method picks a message from the channel\n" |
| " // `recv` will block the current thread if there are no messages " |
| "available\n" |
| msgstr "" |
| "// `recv` 方法从通道中获取一条消息\n" |
| " // 如果没有可用消息，`recv` 将阻塞当前线程\n" |
| |
| #: src/std_misc/channels.md:47 |
| msgid "// Wait for the threads to complete any remaining work\n" |
| msgstr "// 等待线程完成所有剩余工作\n" |
| |
| #: src/std_misc/channels.md:49 |
| msgid "\"oops! the child thread panicked\"" |
| msgstr "\"糟糕！子线程发生了 panic\"" |
| |
| #: src/std_misc/channels.md:52 |
| msgid "// Show the order in which the messages were sent\n" |
| msgstr "// 显示消息发送的顺序\n" |
| |
| #: src/std_misc/path.md:3 |
| msgid "" |
| "The `Path` struct represents file paths in the underlying filesystem. There " |
| "are two flavors of `Path`: `posix::Path`, for UNIX-like systems, and " |
| "`windows::Path`, for Windows. The prelude exports the appropriate platform-" |
| "specific `Path` variant." |
| msgstr "" |
| "`Path` 结构体表示底层文件系统中的文件路径。`Path` 有两种变体：用于类 UNIX 系" |
| "统的 `posix::Path` 和用于 Windows 的 `windows::Path`。prelude 会导出适合特定" |
| "平台的 `Path` 变体。" |
| |
| #: src/std_misc/path.md:8 |
| msgid "" |
| "A `Path` can be created from an `OsStr`, and provides several methods to get " |
| "information from the file/directory the path points to." |
| msgstr "" |
| "`Path` 可以从 `OsStr` 创建，并提供多种方法来获取路径所指向的文件或目录的信" |
| "息。" |
| |
| #: src/std_misc/path.md:11 |
| msgid "" |
| "A `Path` is immutable. The owned version of `Path` is `PathBuf`. The " |
| "relation between `Path` and `PathBuf` is similar to that of `str` and " |
| "`String`: a `PathBuf` can be mutated in-place, and can be dereferenced to a " |
| "`Path`." |
| msgstr "" |
| "`Path` 是不可变的。`Path` 的所有权版本是 `PathBuf`。`Path` 和 `PathBuf` 之间" |
| "的关系类似于 `str` 和 `String`：`PathBuf` 可以原地修改，并且可以解引用为 " |
| "`Path`。" |
| |
| #: src/std_misc/path.md:15 |
| msgid "" |
| "Note that a `Path` is _not_ internally represented as an UTF-8 string, but " |
| "instead is stored as an `OsString`. Therefore, converting a `Path` to a " |
| "`&str` is _not_ free and may fail (an `Option` is returned). However, a " |
| "`Path` can be freely converted to an `OsString` or `&OsStr` using " |
| "`into_os_string` and `as_os_str`, respectively." |
| msgstr "" |
| "注意，`Path` 在内部**并非**表示为 UTF-8 字符串，而是存储为 `OsString`。因此，" |
| "将 `Path` 转换为 `&str` **并非**零开销操作，且可能失败（返回一个 `Option`）。" |
| "然而，`Path` 可以自由地转换为 `OsString` 或 `&OsStr`，分别使用 " |
| "`into_os_string` 和 `as_os_str` 方法。" |
| |
| #: src/std_misc/path.md:25 |
| msgid "// Create a `Path` from an `&'static str`\n" |
| msgstr "// 从 `&'static str` 创建一个 `Path`\n" |
| |
| #: src/std_misc/path.md:26 |
| msgid "\".\"" |
| msgstr "\".\"" |
| |
| #: src/std_misc/path.md:28 |
| msgid "// The `display` method returns a `Display`able structure\n" |
| msgstr "// `display` 方法返回一个可用于显示的结构体\n" |
| |
| #: src/std_misc/path.md:31 |
| msgid "" |
| "// `join` merges a path with a byte container using the OS specific\n" |
| " // separator, and returns a `PathBuf`\n" |
| msgstr "" |
| "// `join` 使用操作系统特定的分隔符将路径与字节容器合并，\n" |
| " // 并返回一个 `PathBuf`\n" |
| |
| #: src/std_misc/path.md:35 |
| msgid "// `push` extends the `PathBuf` with a `&Path`\n" |
| msgstr "// `push` 使用 `&Path` 扩展 `PathBuf`\n" |
| |
| #: src/std_misc/path.md:37 |
| msgid "\"myfile.tar.gz\"" |
| msgstr "\"myfile.tar.gz\"" |
| |
| #: src/std_misc/path.md:39 |
| msgid "// `set_file_name` updates the file name of the `PathBuf`\n" |
| msgstr "// `set_file_name` 更新 `PathBuf` 的文件名\n" |
| |
| #: src/std_misc/path.md:40 |
| msgid "\"package.tgz\"" |
| msgstr "\"package.tgz\"" |
| |
| #: src/std_misc/path.md:42 |
| msgid "// Convert the `PathBuf` into a string slice\n" |
| msgstr "// 将 `PathBuf` 转换为字符串切片\n" |
| |
| #: src/std_misc/path.md:44 |
| msgid "\"new path is not a valid UTF-8 sequence\"" |
| msgstr "\"新路径不是有效的 UTF-8 序列\"" |
| |
| #: src/std_misc/path.md:45 |
| msgid "\"new path is {}\"" |
| msgstr "\"新路径是 {}\"" |
| |
| #: src/std_misc/path.md:51 |
| msgid "" |
| "Be sure to check at other `Path` methods (`posix::Path` or `windows::Path`) " |
| "and the `Metadata` struct." |
| msgstr "" |
| "请务必查看其他 `Path` 方法（`posix::Path` 或 `windows::Path`）以及 " |
| "`Metadata` 结构体。" |
| |
| #: src/std_misc/path.md:56 |
| msgid "" |
| "[OsStr](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and [Metadata]" |
| "(https://doc.rust-lang.org/std/fs/struct.Metadata.html)." |
| msgstr "" |
| "[OsStr](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) 和 [Metadata]" |
| "(https://doc.rust-lang.org/std/fs/struct.Metadata.html)。" |
| |
| #: src/std_misc/file.md:3 |
| msgid "" |
| "The `File` struct represents a file that has been opened (it wraps a file " |
| "descriptor), and gives read and/or write access to the underlying file." |
| msgstr "" |
| "`File` 结构体表示一个已打开的文件（它封装了一个文件描述符），并提供对底层文件" |
| "的读取和/或写入访问。" |
| |
| #: src/std_misc/file.md:6 |
| msgid "" |
| "Since many things can go wrong when doing file I/O, all the `File` methods " |
| "return the `io::Result<T>` type, which is an alias for `Result<T, " |
| "io::Error>`." |
| msgstr "" |
| "由于文件 I/O 操作可能会出现多种错误，所有 `File` 方法都返回 `io::Result<T>` " |
| "类型，这是 `Result<T, io::Error>` 的别名。" |
| |
| #: src/std_misc/file.md:9 |
| msgid "" |
| "This makes the failure of all I/O operations _explicit_. Thanks to this, the " |
| "programmer can see all the failure paths, and is encouraged to handle them " |
| "in a proactive manner." |
| msgstr "" |
| "这使得所有 I/O 操作的失败都变得**显式**。得益于此，程序员可以看到所有可能的失" |
| "败路径，并被鼓励主动处理这些情况。" |
| |
| #: src/std_misc/file/open.md:3 |
| msgid "The `open` function can be used to open a file in read-only mode." |
| msgstr "`open` 函数可用于以只读模式打开文件。" |
| |
| #: src/std_misc/file/open.md:5 |
| msgid "" |
| "A `File` owns a resource, the file descriptor and takes care of closing the " |
| "file when it is `drop`ed." |
| msgstr "`File` 拥有一个资源（即文件描述符），并在被 `drop` 时负责关闭文件。" |
| |
| #: src/std_misc/file/open.md:14 |
| msgid "// Create a path to the desired file\n" |
| msgstr "// 创建指向目标文件的路径\n" |
| |
| #: src/std_misc/file/open.md:15 |
| msgid "\"hello.txt\"" |
| msgstr "\"hello.txt\"" |
| |
| #: src/std_misc/file/open.md:18 |
| msgid "// Open the path in read-only mode, returns `io::Result<File>`\n" |
| msgstr "// 以只读模式打开路径，返回 `io::Result<File>`\n" |
| |
| #: src/std_misc/file/open.md:20 |
| msgid "\"couldn't open {}: {}\"" |
| msgstr "\"无法打开 {}: {}\"" |
| |
| #: src/std_misc/file/open.md:24 |
| msgid "// Read the file contents into a string, returns `io::Result<usize>`\n" |
| msgstr "// 将文件内容读入字符串，返回 `io::Result<usize>`\n" |
| |
| #: src/std_misc/file/open.md:27 |
| msgid "\"couldn't read {}: {}\"" |
| msgstr "\"无法读取 {}: {}\"" |
| |
| #: src/std_misc/file/open.md:28 |
| msgid "\"{} contains:\\n{}\"" |
| msgstr "\"{} 的内容：\\n{}\"" |
| |
| #: src/std_misc/file/open.md:31 |
| msgid "// `file` goes out of scope, and the \"hello.txt\" file gets closed\n" |
| msgstr "// `file` 超出作用域，\"hello.txt\" 文件随之关闭\n" |
| |
| #: src/std_misc/file/open.md:35 src/std_misc/file/create.md:39 |
| #: src/std_misc/fs.md:109 |
| msgid "Here's the expected successful output:" |
| msgstr "以下是预期的成功输出：" |
| |
| #: src/std_misc/file/open.md:37 |
| msgid "" |
| "```shell\n" |
| "$ echo \"Hello World!\" > hello.txt\n" |
| "$ rustc open.rs && ./open\n" |
| "hello.txt contains:\n" |
| "Hello World!\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ echo \"Hello World!\" > hello.txt\n" |
| "$ rustc open.rs && ./open\n" |
| "hello.txt 的内容：\n" |
| "Hello World!\n" |
| "```" |
| |
| #: src/std_misc/file/open.md:44 |
| msgid "" |
| "(You are encouraged to test the previous example under different failure " |
| "conditions: `hello.txt` doesn't exist, or `hello.txt` is not readable, etc.)" |
| msgstr "" |
| "（建议您在不同的失败情况下测试上述示例：例如 `hello.txt` 不存在，或 " |
| "`hello.txt` 不可读等。）" |
| |
| #: src/std_misc/file/create.md:3 |
| msgid "" |
| "The `create` function opens a file in write-only mode. If the file already " |
| "existed, the old content is destroyed. Otherwise, a new file is created." |
| msgstr "" |
| "`create` 函数以只写模式打开文件。如果文件已存在，旧内容会被清除；否则，会创建" |
| "一个新文件。" |
| |
| #: src/std_misc/file/create.md:9 |
| msgid "" |
| "\"Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod\n" |
| "tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim " |
| "veniam,\n" |
| "quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo\n" |
| "consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse\n" |
| "cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat " |
| "non\n" |
| "proident, sunt in culpa qui officia deserunt mollit anim id est laborum.\n" |
| "\"" |
| msgstr "" |
| "\"Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod\n" |
| "tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim " |
| "veniam,\n" |
| "quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo\n" |
| "consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse\n" |
| "cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat " |
| "non\n" |
| "proident, sunt in culpa qui officia deserunt mollit anim id est laborum.\n" |
| "\"" |
| |
| #: src/std_misc/file/create.md:22 |
| msgid "\"lorem_ipsum.txt\"" |
| msgstr "\"lorem_ipsum.txt\"" |
| |
| #: src/std_misc/file/create.md:25 |
| msgid "// Open a file in write-only mode, returns `io::Result<File>`\n" |
| msgstr "// 以只写模式打开文件，返回 `io::Result<File>`\n" |
| |
| #: src/std_misc/file/create.md:27 |
| msgid "\"couldn't create {}: {}\"" |
| msgstr "\"无法创建 {}: {}\"" |
| |
| #: src/std_misc/file/create.md:31 |
| msgid "// Write the `LOREM_IPSUM` string to `file`, returns `io::Result<()>`\n" |
| msgstr "// 将 `LOREM_IPSUM` 字符串写入 `file`，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/file/create.md:33 |
| msgid "\"couldn't write to {}: {}\"" |
| msgstr "\"无法写入 {}: {}\"" |
| |
| #: src/std_misc/file/create.md:34 |
| msgid "\"successfully wrote to {}\"" |
| msgstr "\"成功写入 {}\"" |
| |
| #: src/std_misc/file/create.md:54 |
| msgid "" |
| "(As in the previous example, you are encouraged to test this example under " |
| "failure conditions.)" |
| msgstr "（与前面的示例类似，建议您在失败情况下测试此示例。）" |
| |
| #: src/std_misc/file/create.md:57 |
| msgid "" |
| "The [`OpenOptions`](https://doc.rust-lang.org/std/fs/" |
| "struct.OpenOptions.html) struct can be used to configure how a file is " |
| "opened." |
| msgstr "" |
| "[`OpenOptions`](https://doc.rust-lang.org/std/fs/struct.OpenOptions.html) 结" |
| "构体可用于配置文件的打开方式。" |
| |
| #: src/std_misc/file/read_lines.md:3 |
| msgid "A naive approach" |
| msgstr "一种简单的方法" |
| |
| #: src/std_misc/file/read_lines.md:5 |
| msgid "" |
| "This might be a reasonable first attempt for a beginner's first " |
| "implementation for reading lines from a file." |
| msgstr "对于初学者来说，这可能是从文件中读取行的一个合理的初步尝试。" |
| |
| #: src/std_misc/file/read_lines.md:22 |
| msgid "" |
| "Since the method `lines()` returns an iterator over the lines in the file, " |
| "we can also perform a map inline and collect the results, yielding a more " |
| "concise and fluent expression." |
| msgstr "" |
| "由于 `lines()` 方法返回文件中各行的迭代器，我们可以内联执行 map 并收集结果，" |
| "从而得到一个更简洁流畅的表达式。" |
| |
| #: src/std_misc/file/read_lines.md:31 |
| msgid "// panic on possible file-reading errors\n" |
| msgstr "// 遇到可能的文件读取错误时 panic\n" |
| |
| #: src/std_misc/file/read_lines.md:32 |
| msgid "// split the string into an iterator of string slices\n" |
| msgstr "// 将字符串分割成字符串切片的迭代器\n" |
| |
| #: src/std_misc/file/read_lines.md:33 |
| msgid "// make each slice into a string\n" |
| msgstr "// 将每个切片转换为字符串\n" |
| |
| #: src/std_misc/file/read_lines.md:34 |
| msgid "// gather them together into a vector\n" |
| msgstr "// 将它们收集到一个向量中\n" |
| |
| #: src/std_misc/file/read_lines.md:38 |
| msgid "" |
| "Note that in both examples above, we must convert the `&str` reference " |
| "returned from `lines()` to the owned type `String`, using `.to_string()` and " |
| "`String::from` respectively." |
| msgstr "" |
| "注意，在上述两个示例中，我们都必须将 `lines()` 返回的 `&str` 引用转换为拥有所" |
| "有权的 `String` 类型，分别使用 `.to_string()` 和 `String::from`。" |
| |
| #: src/std_misc/file/read_lines.md:42 |
| msgid "A more efficient approach" |
| msgstr "一种更高效的方法" |
| |
| #: src/std_misc/file/read_lines.md:44 |
| msgid "" |
| "Here we pass ownership of the open `File` to a `BufReader` struct. " |
| "`BufReader` uses an internal buffer to reduce intermediate allocations." |
| msgstr "" |
| "在这里，我们将打开的 `File` 的所有权传递给 `BufReader` 结构体。`BufReader` 使" |
| "用内部缓冲区来减少中间分配。" |
| |
| #: src/std_misc/file/read_lines.md:47 |
| msgid "" |
| "We also update `read_lines` to return an iterator instead of allocating new " |
| "`String` objects in memory for each line." |
| msgstr "" |
| "我们还对 `read_lines` 函数进行了改进，使其返回一个迭代器，而不是为每行内容在" |
| "内存中分配新的 `String` 对象。" |
| |
| #: src/std_misc/file/read_lines.md:56 |
| msgid "// File hosts.txt must exist in the current path\n" |
| msgstr "// 文件 hosts.txt 必须存在于当前路径下\n" |
| |
| #: src/std_misc/file/read_lines.md:57 |
| msgid "\"./hosts.txt\"" |
| msgstr "\"./hosts.txt\"" |
| |
| #: src/std_misc/file/read_lines.md:58 |
| msgid "// Consumes the iterator, returns an (Optional) String\n" |
| msgstr "// 消耗迭代器，返回一个（可选的）String\n" |
| |
| #: src/std_misc/file/read_lines.md:64 |
| msgid "" |
| "// The output is wrapped in a Result to allow matching on errors.\n" |
| "// Returns an Iterator to the Reader of the lines of the file.\n" |
| msgstr "" |
| "// 输出被包装在 Result 中以便于错误匹配。\n" |
| "// 返回一个指向文件行读取器的迭代器。\n" |
| |
| #: src/std_misc/file/read_lines.md:74 |
| msgid "Running this program simply prints the lines individually." |
| msgstr "运行此程序将逐行打印文件内容。" |
| |
| #: src/std_misc/file/read_lines.md:76 |
| msgid "" |
| "```shell\n" |
| "$ echo -e \"127.0.0.1\\n192.168.0.1\\n\" > hosts.txt\n" |
| "$ rustc read_lines.rs && ./read_lines\n" |
| "127.0.0.1\n" |
| "192.168.0.1\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ echo -e \"127.0.0.1\\n192.168.0.1\\n\" > hosts.txt\n" |
| "$ rustc read_lines.rs && ./read_lines\n" |
| "127.0.0.1\n" |
| "192.168.0.1\n" |
| "```" |
| |
| #: src/std_misc/file/read_lines.md:83 |
| msgid "" |
| "(Note that since `File::open` expects a generic `AsRef<Path>` as argument, " |
| "we define our generic `read_lines()` method with the same generic " |
| "constraint, using the `where` keyword.)" |
| msgstr "" |
| "（注意，由于 `File::open` 需要一个泛型 `AsRef<Path>` 作为参数，我们使用 " |
| "`where` 关键字为 `read_lines()` 方法定义了相同的泛型约束。）" |
| |
| #: src/std_misc/file/read_lines.md:86 |
| msgid "" |
| "This process is more efficient than creating a `String` in memory with all " |
| "of the file's contents. This can especially cause performance issues when " |
| "working with larger files." |
| msgstr "" |
| "这种方法比在内存中创建包含整个文件内容的 `String` 更加高效。特别是在处理大文" |
| "件时，后者可能会导致性能问题。" |
| |
| #: src/std_misc/process.md:3 |
| msgid "" |
| "The `process::Output` struct represents the output of a finished child " |
| "process, and the `process::Command` struct is a process builder." |
| msgstr "" |
| "`process::Output` 结构体表示已完成子进程的输出，而 `process::Command` 结构体" |
| "是一个进程构建器。" |
| |
| #: src/std_misc/process.md:10 |
| msgid "\"rustc\"" |
| msgstr "\"rustc\"" |
| |
| #: src/std_misc/process.md:11 |
| msgid "\"--version\"" |
| msgstr "\"--version\"" |
| |
| #: src/std_misc/process.md:13 |
| msgid "\"failed to execute process: {}\"" |
| msgstr "\"执行进程失败：{}\"" |
| |
| #: src/std_misc/process.md:19 |
| msgid "\"rustc succeeded and stdout was:\\n{}\"" |
| msgstr "\"rustc 执行成功，标准输出为：\\n{}\"" |
| |
| #: src/std_misc/process.md:23 |
| msgid "\"rustc failed and stderr was:\\n{}\"" |
| msgstr "\"rustc 执行失败，标准错误输出为：\\n{}\"" |
| |
| #: src/std_misc/process.md:28 |
| msgid "" |
| "(You are encouraged to try the previous example with an incorrect flag " |
| "passed to `rustc`)" |
| msgstr "（建议您尝试在上述示例中向 `rustc` 传递一个错误的标志）" |
| |
| #: src/std_misc/process/pipe.md:3 |
| msgid "" |
| "The `std::process::Child` struct represents a child process, and exposes the " |
| "`stdin`, `stdout` and `stderr` handles for interaction with the underlying " |
| "process via pipes." |
| msgstr "" |
| "`std::process::Child` 结构体代表一个子进程，它暴露了 `stdin`、`stdout` 和 " |
| "`stderr` 句柄，允许通过管道与底层进程进行交互。" |
| |
| #: src/std_misc/process/pipe.md:11 |
| msgid "\"the quick brown fox jumps over the lazy dog\\n\"" |
| msgstr "\"the quick brown fox jumps over the lazy dog\\n\"" |
| |
| #: src/std_misc/process/pipe.md:15 |
| msgid "// Spawn the `wc` command\n" |
| msgstr "// 启动 `wc` 命令\n" |
| |
| #: src/std_misc/process/pipe.md:16 src/std_misc/fs.md:12 src/std_misc/fs.md:73 |
| #: src/std_misc/ffi.md:11 |
| msgid "\"windows\"" |
| msgstr "\"windows\"" |
| |
| #: src/std_misc/process/pipe.md:17 |
| msgid "\"powershell\"" |
| msgstr "\"powershell\"" |
| |
| #: src/std_misc/process/pipe.md:18 |
| msgid "\"-Command\"" |
| msgstr "\"-Command\"" |
| |
| #: src/std_misc/process/pipe.md:18 |
| msgid "\"$input | Measure-Object -Line -Word -Character\"" |
| msgstr "\"$input | Measure-Object -Line -Word -Character\"" |
| |
| #: src/std_misc/process/pipe.md:21 |
| msgid "\"wc\"" |
| msgstr "\"wc\"" |
| |
| #: src/std_misc/process/pipe.md:27 |
| msgid "\"couldn't spawn wc: {}\"" |
| msgstr "\"无法启动 wc：{}\"" |
| |
| #: src/std_misc/process/pipe.md:31 |
| msgid "" |
| "// Write a string to the `stdin` of `wc`.\n" |
| " //\n" |
| " // `stdin` has type `Option<ChildStdin>`, but since we know this " |
| "instance\n" |
| " // must have one, we can directly `unwrap` it.\n" |
| msgstr "" |
| "// 向 `wc` 的 `stdin` 写入字符串。\n" |
| " //\n" |
| " // `stdin` 的类型是 `Option<ChildStdin>`，但我们知道这个实例\n" |
| " // 必定存在，所以可以直接 `unwrap` 它。\n" |
| |
| #: src/std_misc/process/pipe.md:36 |
| msgid "\"couldn't write to wc stdin: {}\"" |
| msgstr "\"无法写入 wc 的标准输入：{}\"" |
| |
| #: src/std_misc/process/pipe.md:37 |
| msgid "\"sent pangram to wc\"" |
| msgstr "\"已将 pangram 发送给 wc\"" |
| |
| #: src/std_misc/process/pipe.md:40 |
| msgid "" |
| "// Because `stdin` does not live after the above calls, it is `drop`ed,\n" |
| " // and the pipe is closed.\n" |
| " //\n" |
| " // This is very important, otherwise `wc` wouldn't start processing the\n" |
| " // input we just sent.\n" |
| msgstr "" |
| "// 由于 `stdin` 在上述调用后不再存活，它会被 `drop`，\n" |
| " // 管道随之关闭。\n" |
| " //\n" |
| " // 这一点非常重要，否则 `wc` 不会开始处理\n" |
| " // 我们刚刚发送的输入。\n" |
| |
| #: src/std_misc/process/pipe.md:46 |
| msgid "" |
| "// The `stdout` field also has type `Option<ChildStdout>` so must be " |
| "unwrapped.\n" |
| msgstr "// `stdout` 字段的类型也是 `Option<ChildStdout>`，因此必须解包。\n" |
| |
| #: src/std_misc/process/pipe.md:49 |
| msgid "\"couldn't read wc stdout: {}\"" |
| msgstr "\"无法读取 wc 的标准输出：{}\"" |
| |
| #: src/std_misc/process/pipe.md:50 |
| msgid "\"wc responded with:\\n{}\"" |
| msgstr "\"wc 的响应为：\\n{}\"" |
| |
| #: src/std_misc/process/wait.md:3 |
| msgid "" |
| "If you'd like to wait for a `process::Child` to finish, you must call " |
| "`Child::wait`, which will return a `process::ExitStatus`." |
| msgstr "" |
| "如果你想等待一个 `process::Child` 完成，你必须调用 `Child::wait`，它会返回一" |
| "个 `process::ExitStatus`。" |
| |
| #: src/std_misc/process/wait.md:10 |
| msgid "\"sleep\"" |
| msgstr "\"sleep\"" |
| |
| #: src/std_misc/process/wait.md:13 |
| msgid "\"reached end of main\"" |
| msgstr "\"到达 main 函数末尾\"" |
| |
| #: src/std_misc/process/wait.md:18 |
| msgid "" |
| "# `wait` keeps running for 5 seconds until the `sleep 5` command finishes\n" |
| msgstr "# `wait` 会持续运行 5 秒，直到 `sleep 5` 命令执行完毕\n" |
| |
| #: src/std_misc/fs.md:3 |
| msgid "" |
| "The `std::fs` module contains several functions that deal with the " |
| "filesystem." |
| msgstr "`std::fs` 模块包含多个用于处理文件系统的函数。" |
| |
| #: src/std_misc/fs.md:10 src/std_misc/fs.md:68 src/std_misc/ffi.md:20 |
| msgid "\"unix\"" |
| msgstr "\"unix\"" |
| |
| #: src/std_misc/fs.md:15 |
| msgid "// A simple implementation of `% cat path`\n" |
| msgstr "// `% cat path` 命令的简单实现\n" |
| |
| #: src/std_misc/fs.md:25 |
| msgid "// A simple implementation of `% echo s > path`\n" |
| msgstr "// `% echo s > path` 命令的简单实现\n" |
| |
| #: src/std_misc/fs.md:32 |
| msgid "// A simple implementation of `% touch path` (ignores existing files)\n" |
| msgstr "// `% touch path` 命令的简单实现（忽略已存在的文件）\n" |
| |
| #: src/std_misc/fs.md:42 |
| msgid "\"`mkdir a`\"" |
| msgstr "\"`mkdir a`\"" |
| |
| #: src/std_misc/fs.md:43 |
| msgid "// Create a directory, returns `io::Result<()>`\n" |
| msgstr "// 创建目录，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/fs.md:45 src/std_misc/fs.md:52 src/std_misc/fs.md:58 |
| #: src/std_misc/fs.md:63 src/std_misc/fs.md:70 src/std_misc/fs.md:75 |
| #: src/std_misc/fs.md:81 src/std_misc/fs.md:88 src/std_misc/fs.md:97 |
| #: src/std_misc/fs.md:103 |
| msgid "\"! {:?}\"" |
| msgstr "\"! {:?}\"" |
| |
| #: src/std_misc/fs.md:49 |
| msgid "\"`echo hello > a/b.txt`\"" |
| msgstr "\"`echo hello > a/b.txt`\"" |
| |
| #: src/std_misc/fs.md:50 |
| msgid "" |
| "// The previous match can be simplified using the `unwrap_or_else` method\n" |
| msgstr "// 可以使用 `unwrap_or_else` 方法简化之前的匹配\n" |
| |
| #: src/std_misc/fs.md:51 |
| msgid "\"a/b.txt\"" |
| msgstr "\"a/b.txt\"" |
| |
| #: src/std_misc/fs.md:55 |
| msgid "\"`mkdir -p a/c/d`\"" |
| msgstr "\"`mkdir -p a/c/d`\"" |
| |
| #: src/std_misc/fs.md:56 |
| msgid "// Recursively create a directory, returns `io::Result<()>`\n" |
| msgstr "// 递归创建目录，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/fs.md:57 src/std_misc/fs.md:102 |
| msgid "\"a/c/d\"" |
| msgstr "\"a/c/d\"" |
| |
| #: src/std_misc/fs.md:61 |
| msgid "\"`touch a/c/e.txt`\"" |
| msgstr "\"`touch a/c/e.txt`\"" |
| |
| #: src/std_misc/fs.md:62 src/std_misc/fs.md:96 |
| msgid "\"a/c/e.txt\"" |
| msgstr "\"a/c/e.txt\"" |
| |
| #: src/std_misc/fs.md:66 |
| msgid "\"`ln -s ../b.txt a/c/b.txt`\"" |
| msgstr "\"`ln -s ../b.txt a/c/b.txt`\"" |
| |
| #: src/std_misc/fs.md:67 |
| msgid "// Create a symbolic link, returns `io::Result<()>`\n" |
| msgstr "// 创建符号链接，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/fs.md:69 src/std_misc/fs.md:74 |
| msgid "\"../b.txt\"" |
| msgstr "\"../b.txt\"" |
| |
| #: src/std_misc/fs.md:69 src/std_misc/fs.md:74 src/std_misc/fs.md:80 |
| msgid "\"a/c/b.txt\"" |
| msgstr "\"a/c/b.txt\"" |
| |
| #: src/std_misc/fs.md:79 |
| msgid "\"`cat a/c/b.txt`\"" |
| msgstr "\"`cat a/c/b.txt`\"" |
| |
| #: src/std_misc/fs.md:85 |
| msgid "\"`ls a`\"" |
| msgstr "\"`ls a`\"" |
| |
| #: src/std_misc/fs.md:86 |
| msgid "// Read the contents of a directory, returns `io::Result<Vec<Path>>`\n" |
| msgstr "// 读取目录内容，返回 `io::Result<Vec<Path>>`\n" |
| |
| #: src/std_misc/fs.md:94 |
| msgid "\"`rm a/c/e.txt`\"" |
| msgstr "\"`rm a/c/e.txt`\"" |
| |
| #: src/std_misc/fs.md:95 |
| msgid "// Remove a file, returns `io::Result<()>`\n" |
| msgstr "// 删除文件，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/fs.md:100 |
| msgid "\"`rmdir a/c/d`\"" |
| msgstr "\"`rmdir a/c/d`\"" |
| |
| #: src/std_misc/fs.md:101 |
| msgid "// Remove an empty directory, returns `io::Result<()>`\n" |
| msgstr "// 删除空目录，返回 `io::Result<()>`\n" |
| |
| #: src/std_misc/fs.md:111 |
| msgid "" |
| "```shell\n" |
| "$ rustc fs.rs && ./fs\n" |
| "`mkdir a`\n" |
| "`echo hello > a/b.txt`\n" |
| "`mkdir -p a/c/d`\n" |
| "`touch a/c/e.txt`\n" |
| "`ln -s ../b.txt a/c/b.txt`\n" |
| "`cat a/c/b.txt`\n" |
| "> hello\n" |
| "`ls a`\n" |
| "> \"a/b.txt\"\n" |
| "> \"a/c\"\n" |
| "`rm a/c/e.txt`\n" |
| "`rmdir a/c/d`\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ rustc fs.rs && ./fs\n" |
| "`mkdir a`\n" |
| "`echo hello > a/b.txt`\n" |
| "`mkdir -p a/c/d`\n" |
| "`touch a/c/e.txt`\n" |
| "`ln -s ../b.txt a/c/b.txt`\n" |
| "`cat a/c/b.txt`\n" |
| "> hello\n" |
| "`ls a`\n" |
| "> \"a/b.txt\"\n" |
| "> \"a/c\"\n" |
| "`rm a/c/e.txt`\n" |
| "`rmdir a/c/d`\n" |
| "```" |
| |
| #: src/std_misc/fs.md:127 |
| msgid "And the final state of the `a` directory is:" |
| msgstr "最终 `a` 目录的状态如下：" |
| |
| #: src/std_misc/fs.md:139 |
| msgid "An alternative way to define the function `cat` is with `?` notation:" |
| msgstr "另一种定义 `cat` 函数的方法是使用 `?` 运算符：" |
| |
| #: src/std_misc/fs.md:152 |
| msgid "[`cfg!`](../attribute/cfg.md)" |
| msgstr "[`cfg!`](../attribute/cfg.md)" |
| |
| #: src/std_misc/arg.md:3 |
| msgid "Standard Library" |
| msgstr "标准库" |
| |
| #: src/std_misc/arg.md:5 |
| msgid "" |
| "The command line arguments can be accessed using `std::env::args`, which " |
| "returns an iterator that yields a `String` for each argument:" |
| msgstr "" |
| "可以使用 `std::env::args` 访问命令行参数，它返回一个迭代器，为每个参数生成一" |
| "个 `String`：" |
| |
| #: src/std_misc/arg.md:14 |
| msgid "// The first argument is the path that was used to call the program.\n" |
| msgstr "// 第一个参数是用于调用程序的路径\n" |
| |
| #: src/std_misc/arg.md:15 |
| msgid "\"My path is {}.\"" |
| msgstr "\"我的路径是 {}。\"" |
| |
| #: src/std_misc/arg.md:17 |
| msgid "" |
| "// The rest of the arguments are the passed command line parameters.\n" |
| " // Call the program like this:\n" |
| " // $ ./args arg1 arg2\n" |
| msgstr "" |
| "// 其余参数是传递的命令行参数\n" |
| " // 像这样调用程序：\n" |
| " // $ ./args arg1 arg2\n" |
| |
| #: src/std_misc/arg.md:20 |
| msgid "\"I got {:?} arguments: {:?}.\"" |
| msgstr "\"我获得了 {:?} 个参数：{:?}。\"" |
| |
| #: src/std_misc/arg.md:24 |
| msgid "" |
| "```shell\n" |
| "$ ./args 1 2 3\n" |
| "My path is ./args.\n" |
| "I got 3 arguments: [\"1\", \"2\", \"3\"].\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ ./args 1 2 3\n" |
| "程序路径：./args\n" |
| "接收到 3 个参数：[\"1\"、\"2\"、\"3\"]\n" |
| "```" |
| |
| #: src/std_misc/arg.md:32 |
| msgid "" |
| "Alternatively, there are numerous crates that can provide extra " |
| "functionality when creating command-line applications. One of the more " |
| "popular command line argument crates being [`clap`](https://rust-" |
| "cli.github.io/book/tutorial/cli-args.html#parsing-cli-arguments-with-clap)." |
| msgstr "" |
| "此外，在开发命令行应用程序时，还有许多 crate 可以提供额外的功能。其中，" |
| "[`clap`](https://rust-cli.github.io/book/tutorial/cli-args.html#parsing-cli-" |
| "arguments-with-clap) 是一个广受欢迎的命令行参数处理 crate。" |
| |
| #: src/std_misc/arg/matching.md:3 |
| msgid "Matching can be used to parse simple arguments:" |
| msgstr "可以使用模式匹配来解析简单的参数：" |
| |
| #: src/std_misc/arg/matching.md:17 |
| msgid "" |
| "\"usage:\n" |
| "match_args <string>\n" |
| " Check whether given string is the answer.\n" |
| "match_args {{increase|decrease}} <integer>\n" |
| " Increase or decrease given integer by one.\"" |
| msgstr "" |
| "\"用法：\n" |
| "match_args <字符串>\n" |
| " 检查给定的字符串是否为正确答案。\n" |
| "match_args {{increase|decrease}} <整数>\n" |
| " 将给定的整数增加或减少 1。\"" |
| |
| #: src/std_misc/arg/matching.md:28 |
| msgid "// no arguments passed\n" |
| msgstr "// 未传递参数\n" |
| |
| #: src/std_misc/arg/matching.md:30 |
| msgid "\"My name is 'match_args'. Try passing some arguments!\"" |
| msgstr "\"我的名字是 'match_args'。试试传递一些参数吧！\"" |
| |
| #: src/std_misc/arg/matching.md:32 |
| msgid "// one argument passed\n" |
| msgstr "// 传递了一个参数\n" |
| |
| #: src/std_misc/arg/matching.md:35 |
| msgid "\"This is the answer!\"" |
| msgstr "\"这就是正确答案！\"" |
| |
| #: src/std_misc/arg/matching.md:36 |
| msgid "\"This is not the answer.\"" |
| msgstr "\"这不是正确答案。\"" |
| |
| #: src/std_misc/arg/matching.md:39 |
| msgid "// one command and one argument passed\n" |
| msgstr "// 传递了一个命令和一个参数\n" |
| |
| #: src/std_misc/arg/matching.md:43 |
| msgid "// parse the number\n" |
| msgstr "// 解析数字\n" |
| |
| #: src/std_misc/arg/matching.md:49 |
| msgid "\"error: second argument not an integer\"" |
| msgstr "\"错误：第二个参数不是整数\"" |
| |
| #: src/std_misc/arg/matching.md:54 |
| msgid "// parse the command\n" |
| msgstr "// 解析命令\n" |
| |
| #: src/std_misc/arg/matching.md:56 |
| msgid "\"increase\"" |
| msgstr "\"increase\"" |
| |
| #: src/std_misc/arg/matching.md:57 |
| msgid "\"decrease\"" |
| msgstr "\"decrease\"" |
| |
| #: src/std_misc/arg/matching.md:59 |
| msgid "\"error: invalid command\"" |
| msgstr "\"错误：无效的命令\"" |
| |
| #: src/std_misc/arg/matching.md:64 |
| msgid "// all the other cases\n" |
| msgstr "// 所有其他情况\n" |
| |
| #: src/std_misc/arg/matching.md:66 |
| msgid "// show a help message\n" |
| msgstr "// 显示帮助信息\n" |
| |
| #: src/std_misc/arg/matching.md:73 |
| msgid "" |
| "If you named your program `match_args.rs` and compile it like this `rustc " |
| "match_args.rs`, you can execute it as follows:" |
| msgstr "" |
| "如果你将程序命名为 `match_args.rs` 并使用 `rustc match_args.rs` 编译它，你可" |
| "以按以下方式执行：" |
| |
| #: src/std_misc/ffi.md:3 |
| msgid "" |
| "Rust provides a Foreign Function Interface (FFI) to C libraries. Foreign " |
| "functions must be declared inside an `extern` block annotated with a " |
| "`#[link]` attribute containing the name of the foreign library." |
| msgstr "" |
| "Rust 提供了与 C 库交互的外部函数接口（FFI）。外部函数必须在 `extern` 块内声" |
| "明，并使用 `#[link]` 属性标注外部库的名称。" |
| |
| #: src/std_misc/ffi.md:9 |
| msgid "// this extern block links to the libm library\n" |
| msgstr "// 此 extern 块链接到 libm 库\n" |
| |
| #: src/std_misc/ffi.md:12 |
| msgid "\"msvcrt\"" |
| msgstr "\"msvcrt\"" |
| |
| #: src/std_misc/ffi.md:14 src/std_misc/ffi.md:23 |
| msgid "" |
| "// this is a foreign function\n" |
| " // that computes the square root of a single precision complex number\n" |
| msgstr "" |
| "// 这是一个外部函数\n" |
| " // 用于计算单精度复数的平方根\n" |
| |
| #: src/std_misc/ffi.md:21 |
| msgid "\"m\"" |
| msgstr "\"m\"" |
| |
| #: src/std_misc/ffi.md:29 |
| msgid "" |
| "// Since calling foreign functions is considered unsafe,\n" |
| "// it's common to write safe wrappers around them.\n" |
| msgstr "" |
| "// 由于调用外部函数被认为是不安全的，\n" |
| "// 通常会为它们编写安全的包装函数。\n" |
| |
| #: src/std_misc/ffi.md:37 |
| msgid "// z = -1 + 0i\n" |
| msgstr "// z = -1 + 0i\n" |
| |
| #: src/std_misc/ffi.md:40 |
| msgid "// calling a foreign function is an unsafe operation\n" |
| msgstr "// 调用外部函数是一个不安全的操作\n" |
| |
| #: src/std_misc/ffi.md:43 |
| msgid "\"the square root of {:?} is {:?}\"" |
| msgstr "\"{:?} 的平方根是 {:?}\"" |
| |
| #: src/std_misc/ffi.md:45 |
| msgid "// calling safe API wrapped around unsafe operation\n" |
| msgstr "// 调用封装了不安全操作的安全 API\n" |
| |
| #: src/std_misc/ffi.md:46 |
| msgid "\"cos({:?}) = {:?}\"" |
| msgstr "\"cos({:?}) = {:?}\"" |
| |
| #: src/std_misc/ffi.md:48 |
| msgid "// Minimal implementation of single precision complex numbers\n" |
| msgstr "// 单精度复数的最小实现\n" |
| |
| #: src/std_misc/ffi.md:60 |
| msgid "\"{}-{}i\"" |
| msgstr "\"{}-{}i\"" |
| |
| #: src/std_misc/ffi.md:62 |
| msgid "\"{}+{}i\"" |
| msgstr "\"{}+{}i\"" |
| |
| #: src/testing.md:3 |
| msgid "" |
| "Rust is a programming language that cares a lot about correctness and it " |
| "includes support for writing software tests within the language itself." |
| msgstr "Rust 是一种非常注重正确性的编程语言，它内置了编写软件测试的支持。" |
| |
| #: src/testing.md:6 |
| msgid "Testing comes in three styles:" |
| msgstr "测试分为三种类型：" |
| |
| #: src/testing.md:8 |
| msgid "[Unit](testing/unit_testing.md) testing." |
| msgstr "[单元测试](testing/unit_testing.md)" |
| |
| #: src/testing.md:9 |
| msgid "[Doc](testing/doc_testing.md) testing." |
| msgstr "[文档测试](testing/doc_testing.md)" |
| |
| #: src/testing.md:10 |
| msgid "[Integration](testing/integration_testing.md) testing." |
| msgstr "[集成测试](testing/integration_testing.md)" |
| |
| #: src/testing.md:12 |
| msgid "Also Rust has support for specifying additional dependencies for tests:" |
| msgstr "此外，Rust 还支持为测试指定额外的依赖项：" |
| |
| #: src/testing.md:14 |
| msgid "[Dev-dependencies](testing/dev_dependencies.md)" |
| msgstr "[开发依赖](testing/dev_dependencies.md)" |
| |
| #: src/testing.md:18 |
| msgid "" |
| "[The Book](https://doc.rust-lang.org/book/ch11-00-testing.html) chapter on " |
| "testing" |
| msgstr "" |
| "《Rust 程序设计语言》中[关于测试的章节](https://doc.rust-lang.org/book/" |
| "ch11-00-testing.html)" |
| |
| #: src/testing.md:19 |
| msgid "" |
| "[API Guidelines](https://rust-lang-nursery.github.io/api-guidelines/" |
| "documentation.html) on doc-testing" |
| msgstr "" |
| "API 指南中[关于文档测试的内容](https://rust-lang-nursery.github.io/api-" |
| "guidelines/documentation.html)" |
| |
| #: src/testing/unit_testing.md:3 |
| msgid "" |
| "Tests are Rust functions that verify that the non-test code is functioning " |
| "in the expected manner. The bodies of test functions typically perform some " |
| "setup, run the code we want to test, then assert whether the results are " |
| "what we expect." |
| msgstr "" |
| "测试是 Rust 函数，用于验证非测试代码是否按预期方式运行。测试函数的主体通常包" |
| "括一些准备工作，运行待测试的代码，然后断言结果是否符合预期。" |
| |
| #: src/testing/unit_testing.md:8 |
| msgid "" |
| "Most unit tests go into a `tests` [mod](../mod.md) with the `#[cfg(test)]` " |
| "[attribute](../attribute.md). Test functions are marked with the `#[test]` " |
| "attribute." |
| msgstr "" |
| "大多数单元测试都放在带有 `#[cfg(test)]` [属性](../attribute.md)的 `tests` [模" |
| "块](../mod.md)中。测试函数用 `#[test]` 属性标记。" |
| |
| #: src/testing/unit_testing.md:11 |
| msgid "" |
| "Tests fail when something in the test function [panics](../std/panic.md). " |
| "There are some helper [macros](../macros.md):" |
| msgstr "" |
| "当测试函数中出现[恐慌（panic）](../std/panic.md)时，测试就会失败。以下是一些" |
| "辅助[宏](../macros.md)：" |
| |
| #: src/testing/unit_testing.md:14 |
| msgid "`assert!(expression)` - panics if expression evaluates to `false`." |
| msgstr "`assert!(expression)` - 如果表达式求值为 `false`，则会触发 panic。" |
| |
| #: src/testing/unit_testing.md:15 |
| msgid "" |
| "`assert_eq!(left, right)` and `assert_ne!(left, right)` - testing left and " |
| "right expressions for equality and inequality respectively." |
| msgstr "" |
| "`assert_eq!(left, right)` 和 `assert_ne!(left, right)` - 分别用于测试左右表达" |
| "式的相等性和不相等性。" |
| |
| #: src/testing/unit_testing.md:22 |
| msgid "" |
| "// This is a really bad adding function, its purpose is to fail in this\n" |
| "// example.\n" |
| msgstr "// 这是一个非常糟糕的加法函数，它的目的是在这个例子中失败。\n" |
| |
| #: src/testing/unit_testing.md:32 |
| msgid "" |
| "// Note this useful idiom: importing names from outer (for mod tests) " |
| "scope.\n" |
| msgstr "" |
| "// 注意这个有用的惯用法：从外部作用域（对于 mod tests 而言）导入名称。\n" |
| |
| #: src/testing/unit_testing.md:42 |
| msgid "" |
| "// This assert would fire and test will fail.\n" |
| " // Please note, that private functions can be tested too!\n" |
| msgstr "" |
| "// 这个断言会触发，测试将失败。\n" |
| " // 请注意，私有函数也可以被测试！\n" |
| |
| #: src/testing/unit_testing.md:49 |
| msgid "Tests can be run with `cargo test`." |
| msgstr "可以使用 `cargo test` 命令运行测试。" |
| |
| #: src/testing/unit_testing.md:73 |
| msgid "Tests and `?`" |
| msgstr "测试与 `?` 运算符" |
| |
| #: src/testing/unit_testing.md:75 |
| msgid "" |
| "None of the previous unit test examples had a return type. But in Rust 2018, " |
| "your unit tests can return `Result<()>`, which lets you use `?` in them! " |
| "This can make them much more concise." |
| msgstr "" |
| "之前的单元测试示例都没有返回类型。但在 Rust 2018 版本中，你的单元测试可以返" |
| "回 `Result<()>`，这使得你可以在测试中使用 `?` 运算符！这可以使测试代码更加简" |
| "洁。" |
| |
| #: src/testing/unit_testing.md:84 |
| msgid "\"negative floats don't have square roots\"" |
| msgstr "\"负浮点数没有平方根\"" |
| |
| #: src/testing/unit_testing.md:101 |
| msgid "" |
| "See [\"The Edition Guide\"](https://doc.rust-lang.org/edition-guide/" |
| "rust-2018/error-handling-and-panics/question-mark-in-main-and-tests.html) " |
| "for more details." |
| msgstr "" |
| "更多详情请参阅[《版本指南》](https://doc.rust-lang.org/edition-guide/" |
| "rust-2018/error-handling-and-panics/question-mark-in-main-and-tests.html)。" |
| |
| #: src/testing/unit_testing.md:103 |
| msgid "Testing panics" |
| msgstr "测试 panic" |
| |
| #: src/testing/unit_testing.md:105 |
| msgid "" |
| "To check functions that should panic under certain circumstances, use " |
| "attribute `#[should_panic]`. This attribute accepts optional parameter " |
| "`expected = ` with the text of the panic message. If your function can panic " |
| "in multiple ways, it helps make sure your test is testing the correct panic." |
| msgstr "" |
| "要检查在某些情况下应该触发恐慌的函数，可以使用 `#[should_panic]` 属性。这个属" |
| "性接受可选参数 `expected = `，用于指定预期的恐慌消息文本。如果你的函数可能以" |
| "多种方式触发 panic，这有助于确保你的测试正在检查正确的 panic 情况。" |
| |
| #: src/testing/unit_testing.md:110 |
| msgid "" |
| "**Note**: Rust also allows a shorthand form `#[should_panic = \"message\"]`, " |
| "which works exactly like `#[should_panic(expected = \"message\")]`. Both are " |
| "valid; the latter is more commonly used and is considered more explicit." |
| msgstr "" |
| "**注意**：Rust 还允许使用简写形式 `#[should_panic = \"message\"]`，其功能与 " |
| "`#[should_panic(expected = \"message\")]` 完全相同。两种形式都有效；后者更常" |
| "用，被认为更明确。" |
| |
| #: src/testing/unit_testing.md:117 src/testing/doc_testing.md:46 |
| msgid "\"Divide-by-zero error\"" |
| msgstr "\"除以零错误\"" |
| |
| #: src/testing/unit_testing.md:119 src/testing/unit_testing.md:140 |
| #: src/testing/unit_testing.md:146 |
| msgid "\"Divide result is zero\"" |
| msgstr "\"除法结果为零\"" |
| |
| #: src/testing/unit_testing.md:146 |
| msgid "// This also works\n" |
| msgstr "// 这样也可以\n" |
| |
| #: src/testing/unit_testing.md:153 |
| msgid "Running these tests gives us:" |
| msgstr "运行这些测试会得到以下结果：" |
| |
| #: src/testing/unit_testing.md:173 |
| msgid "Running specific tests" |
| msgstr "运行特定测试" |
| |
| #: src/testing/unit_testing.md:175 |
| msgid "" |
| "To run specific tests one may specify the test name to `cargo test` command." |
| msgstr "要运行特定的测试，可以在 `cargo test` 命令中指定测试名称。" |
| |
| #: src/testing/unit_testing.md:191 |
| msgid "" |
| "To run multiple tests one may specify part of a test name that matches all " |
| "the tests that should be run." |
| msgstr "" |
| "要运行多个测试，可以指定测试名称的一部分，该部分匹配所有应该运行的测试。" |
| |
| #: src/testing/unit_testing.md:209 |
| msgid "Ignoring tests" |
| msgstr "忽略测试" |
| |
| #: src/testing/unit_testing.md:211 |
| msgid "" |
| "Tests can be marked with the `#[ignore]` attribute to exclude some tests. Or " |
| "to run them with command `cargo test -- --ignored`" |
| msgstr "" |
| "可以使用 `#[ignore]` 属性标记测试以排除某些测试。或者使用命令 `cargo test -- " |
| "--ignored` 来运行这些被忽略的测试。" |
| |
| #: src/testing/doc_testing.md:3 |
| msgid "" |
| "The primary way of documenting a Rust project is through annotating the " |
| "source code. Documentation comments are written in [CommonMark Markdown " |
| "specification](https://commonmark.org/) and support code blocks in them. " |
| "Rust takes care about correctness, so these code blocks are compiled and " |
| "used as documentation tests." |
| msgstr "" |
| "Rust 项目的主要文档编写方式是通过在源代码中添加注释。文档注释使用 " |
| "[CommonMark Markdown 规范](https://commonmark.org/)编写，并支持其中的代码块。" |
| "Rust 注重正确性，因此这些代码块会被编译并用作文档测试。" |
| |
| #: src/testing/doc_testing.md:10 |
| msgid "" |
| "/// First line is a short summary describing function.\n" |
| "///\n" |
| "/// The next lines present detailed documentation. Code blocks start with\n" |
| "/// triple backquotes and have implicit `fn main()` inside\n" |
| "/// and `extern crate <cratename>`. Assume we're testing a `playground` " |
| "library\n" |
| "/// crate or using the Playground's Test action:\n" |
| "///\n" |
| "/// ```\n" |
| "/// let result = playground::add(2, 3);\n" |
| "/// assert_eq!(result, 5);\n" |
| "/// ```\n" |
| msgstr "" |
| "/// 第一行是函数的简要描述。\n" |
| "///\n" |
| "/// 接下来的几行是详细文档。代码块以三个反引号开始，\n" |
| "/// 并隐含了 `fn main()` 函数和 `extern crate <cratename>` 声明。\n" |
| "/// 假设我们正在测试 `playground` crate：\n" |
| "///\n" |
| "/// ```\n" |
| "/// let result = playground::add(2, 3);\n" |
| "/// assert_eq!(result, 5);\n" |
| "/// ```\n" |
| |
| #: src/testing/doc_testing.md:24 |
| msgid "" |
| "/// Usually doc comments may include sections \"Examples\", \"Panics\" and " |
| "\"Failures\".\n" |
| "///\n" |
| "/// The next function divides two numbers.\n" |
| "///\n" |
| "/// # Examples\n" |
| "///\n" |
| "/// ```\n" |
| "/// let result = playground::div(10, 2);\n" |
| "/// assert_eq!(result, 5);\n" |
| "/// ```\n" |
| "///\n" |
| "/// # Panics\n" |
| "///\n" |
| "/// The function panics if the second argument is zero.\n" |
| "///\n" |
| "/// ```rust,should_panic\n" |
| "/// // panics on division by zero\n" |
| "/// playground::div(10, 0);\n" |
| "/// ```\n" |
| msgstr "" |
| "/// 文档注释通常包含\"示例\"、\"异常\"和\"错误\"等部分。\n" |
| "///\n" |
| "/// 下面的函数用于两数相除。\n" |
| "///\n" |
| "/// # 示例\n" |
| "///\n" |
| "/// ```\n" |
| "/// let result = playground::div(10, 2);\n" |
| "/// assert_eq!(result, 5);\n" |
| "/// ```\n" |
| "///\n" |
| "/// # 异常\n" |
| "///\n" |
| "/// 当第二个参数为零时，函数会触发异常。\n" |
| "///\n" |
| "/// ```rust,should_panic\n" |
| "/// // 除以零会触发异常\n" |
| "/// playground::div(10, 0);\n" |
| "/// ```\n" |
| |
| #: src/testing/doc_testing.md:53 |
| msgid "" |
| "Code blocks in documentation are automatically tested when running the " |
| "regular `cargo test` command:" |
| msgstr "运行常规的 `cargo test` 命令时，文档中的代码块会自动进行测试：" |
| |
| #: src/testing/doc_testing.md:72 |
| msgid "Motivation behind documentation tests" |
| msgstr "文档测试的动机" |
| |
| #: src/testing/doc_testing.md:74 |
| msgid "" |
| "The main purpose of documentation tests is to serve as examples that " |
| "exercise the functionality, which is one of the most important [guidelines]" |
| "(https://rust-lang-nursery.github.io/api-guidelines/" |
| "documentation.html#examples-use--not-try-not-unwrap-c-question-mark). It " |
| "allows using examples from docs as complete code snippets. But using `?` " |
| "makes compilation fail since `main` returns `unit`. The ability to hide some " |
| "source lines from documentation comes to the rescue: one may write `fn " |
| "try_main() -> Result<(), ErrorType>`, hide it and `unwrap` it in hidden " |
| "`main`. Sounds complicated? Here's an example:" |
| msgstr "" |
| "文档测试的主要目的是提供功能演示的示例，这是最重要的[指导原则](https://rust-" |
| "lang-nursery.github.io/api-guidelines/documentation.html#examples-use--not-" |
| "try-not-unwrap-c-question-mark)之一。它允许将文档中的示例作为完整的代码片段使" |
| "用。但是使用 `?` 会导致编译失败，因为 `main` 函数返回 `unit` 类型。这时，隐藏" |
| "文档中的某些源代码行就派上用场了：可以编写 `fn try_main() -> Result<(), " |
| "ErrorType>`，将其隐藏，并在隐藏的 `main` 函数中 `unwrap` 它。听起来很复杂？这" |
| "里有一个例子：" |
| |
| #: src/testing/doc_testing.md:83 |
| msgid "" |
| "/// Using hidden `try_main` in doc tests.\n" |
| "///\n" |
| "/// ```\n" |
| "/// # // hidden lines start with `#` symbol, but they're still compilable!\n" |
| "/// # fn try_main() -> Result<(), String> { // line that wraps the body " |
| "shown in doc\n" |
| "/// let res = playground::try_div(10, 2)?;\n" |
| "/// # Ok(()) // returning from try_main\n" |
| "/// # }\n" |
| "/// # fn main() { // starting main that'll unwrap()\n" |
| "/// # try_main().unwrap(); // calling try_main and unwrapping\n" |
| "/// # // so that test will panic in case of error\n" |
| "/// # }\n" |
| "/// ```\n" |
| msgstr "" |
| "/// 在文档测试中使用隐藏的 `try_main` 函数。\n" |
| "///\n" |
| "/// ```\n" |
| "/// # // 以 `#` 开头的行在文档中是隐藏的，但它们仍然可以编译！\n" |
| "/// # fn try_main() -> Result<(), String> { // 这行包装了文档中显示的函数体\n" |
| "/// let res = playground::try_div(10, 2)?;\n" |
| "/// # Ok(()) // 从 try_main 返回\n" |
| "/// # }\n" |
| "/// # fn main() { // 开始会调用 unwrap() 的 main 函数\n" |
| "/// # try_main().unwrap(); // 调用 try_main 并解包\n" |
| "/// # // 这样在出错时测试会触发 panic\n" |
| "/// # }\n" |
| "/// ```\n" |
| |
| #: src/testing/doc_testing.md:98 |
| msgid "\"Divide-by-zero\"" |
| msgstr "\"除以零错误\"" |
| |
| #: src/testing/doc_testing.md:107 |
| msgid "" |
| "[RFC505](https://github.com/rust-lang/rfcs/blob/master/text/0505-api-comment-" |
| "conventions.md) on documentation style" |
| msgstr "" |
| "关于文档风格的 [RFC505](https://github.com/rust-lang/rfcs/blob/master/text/" |
| "0505-api-comment-conventions.md)" |
| |
| #: src/testing/doc_testing.md:108 |
| msgid "" |
| "[API Guidelines](https://rust-lang-nursery.github.io/api-guidelines/" |
| "documentation.html) on documentation guidelines" |
| msgstr "" |
| "关于文档指南的 [API 指南](https://rust-lang-nursery.github.io/api-guidelines/" |
| "documentation.html)" |
| |
| #: src/testing/integration_testing.md:3 |
| msgid "" |
| "[Unit tests](unit_testing.md) are testing one module in isolation at a time: " |
| "they're small and can test private code. Integration tests are external to " |
| "your crate and use only its public interface in the same way any other code " |
| "would. Their purpose is to test that many parts of your library work " |
| "correctly together." |
| msgstr "" |
| "[单元测试](unit_testing.md)每次只隔离测试一个模块：它们规模小，可以测试私有代" |
| "码。集成测试则位于 crate 外部，仅使用其公共接口，就像其他代码一样。集成测试的" |
| "目的是验证库的多个部分能否正确协同工作。" |
| |
| #: src/testing/integration_testing.md:8 |
| msgid "Cargo looks for integration tests in `tests` directory next to `src`." |
| msgstr "Cargo 在 `src` 目录旁的 `tests` 目录中查找集成测试。" |
| |
| #: src/testing/integration_testing.md:10 src/testing/dev_dependencies.md:17 |
| msgid "File `src/lib.rs`:" |
| msgstr "文件 `src/lib.rs`：" |
| |
| #: src/testing/integration_testing.md:13 |
| msgid "// Define this in a crate called `adder`.\n" |
| msgstr "// 在名为 `adder` 的 crate 中定义此内容。\n" |
| |
| #: src/testing/integration_testing.md:19 |
| msgid "File with test: `tests/integration_test.rs`:" |
| msgstr "测试文件：`tests/integration_test.rs`：" |
| |
| #: src/testing/integration_testing.md:28 |
| msgid "Running tests with `cargo test` command:" |
| msgstr "使用 `cargo test` 命令运行测试：" |
| |
| #: src/testing/integration_testing.md:50 |
| msgid "" |
| "Each Rust source file in the `tests` directory is compiled as a separate " |
| "crate. In order to share some code between integration tests we can make a " |
| "module with public functions, importing and using it within tests." |
| msgstr "" |
| "`tests` 目录中的每个 Rust 源文件都被编译为独立的 crate。为了在集成测试之间共" |
| "享代码，我们可以创建一个包含公共函数的模块，然后在测试中导入并使用它。" |
| |
| #: src/testing/integration_testing.md:54 |
| msgid "File `tests/common/mod.rs`:" |
| msgstr "文件 `tests/common/mod.rs`：" |
| |
| #: src/testing/integration_testing.md:58 |
| msgid "" |
| "// some setup code, like creating required files/directories, starting\n" |
| " // servers, etc.\n" |
| msgstr "" |
| "// 一些设置代码，如创建必要的文件/目录，启动\n" |
| " // 服务器等。\n" |
| |
| #: src/testing/integration_testing.md:63 |
| msgid "File with test: `tests/integration_test.rs`" |
| msgstr "测试文件：`tests/integration_test.rs`" |
| |
| #: src/testing/integration_testing.md:66 |
| msgid "// importing common module.\n" |
| msgstr "// 导入 common 模块。\n" |
| |
| #: src/testing/integration_testing.md:71 |
| msgid "// using common code.\n" |
| msgstr "// 使用公共代码。\n" |
| |
| #: src/testing/integration_testing.md:77 |
| msgid "" |
| "Creating the module as `tests/common.rs` also works, but is not recommended " |
| "because the test runner will treat the file as a test crate and try to run " |
| "tests inside it." |
| msgstr "" |
| "将模块创建为 `tests/common.rs` 也可行，但不推荐，因为测试运行器会将该文件视为" |
| "测试 crate 并尝试运行其中的测试。" |
| |
| #: src/testing/dev_dependencies.md:1 |
| msgid "Development dependencies" |
| msgstr "开发依赖" |
| |
| #: src/testing/dev_dependencies.md:3 |
| msgid "" |
| "Sometimes there is a need to have dependencies for tests (or examples, or " |
| "benchmarks) only. Such dependencies are added to `Cargo.toml` in the `[dev-" |
| "dependencies]` section. These dependencies are not propagated to other " |
| "packages which depend on this package." |
| msgstr "" |
| "有时我们需要仅用于测试（或示例、基准测试）的依赖项。这些依赖项添加在 " |
| "`Cargo.toml` 的 `[dev-dependencies]` 部分。这些依赖项不会传递给依赖于本包的其" |
| "他包。" |
| |
| #: src/testing/dev_dependencies.md:8 |
| msgid "" |
| "One such example is [`pretty_assertions`](https://docs.rs/pretty_assertions/" |
| "1.0.0/pretty_assertions/index.html), which extends standard `assert_eq!` and " |
| "`assert_ne!` macros, to provide colorful diff. \n" |
| "File `Cargo.toml`:" |
| msgstr "" |
| "例如 [`pretty_assertions`](https://docs.rs/pretty_assertions/1.0.0/" |
| "pretty_assertions/index.html)，它扩展了标准的 `assert_eq!` 和 `assert_ne!` " |
| "宏，提供彩色差异对比。 \n" |
| "文件 `Cargo.toml`：" |
| |
| #: src/testing/dev_dependencies.md:11 |
| msgid "" |
| "```toml\n" |
| "# standard crate data is left out\n" |
| "[dev-dependencies]\n" |
| "pretty_assertions = \"1\"\n" |
| "```" |
| msgstr "" |
| "```toml\n" |
| "# 省略标准的 crate 数据\n" |
| "[dev-dependencies]\n" |
| "pretty_assertions = \"1\"\n" |
| "```" |
| |
| #: src/testing/dev_dependencies.md:27 |
| msgid "// crate for test-only use. Cannot be used in non-test code.\n" |
| msgstr "// 仅用于测试的 crate。不能在非测试代码中使用。\n" |
| |
| #: src/testing/dev_dependencies.md:38 |
| msgid "" |
| "[Cargo](http://doc.crates.io/specifying-dependencies.html) docs on " |
| "specifying dependencies." |
| msgstr "" |
| "[Cargo 文档](http://doc.crates.io/specifying-dependencies.html)中关于指定依赖" |
| "项的说明。" |
| |
| #: src/unsafe.md:3 |
| msgid "" |
| "As an introduction to this section, to borrow from [the official docs]" |
| "(https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html), \"one should try " |
| "to minimize the amount of unsafe code in a code base.\" With that in mind, " |
| "let's get started! Unsafe annotations in Rust are used to bypass protections " |
| "put in place by the compiler; specifically, there are four primary things " |
| "that unsafe is used for:" |
| msgstr "" |
| "作为本节的引言，借用[官方文档](https://doc.rust-lang.org/book/ch19-01-unsafe-" |
| "rust.html)的话说：\"应该尽量减少代码库中不安全代码的数量。\"牢记这一点，让我" |
| "们开始吧！Rust 中的不安全标注用于绕过编译器设置的保护机制。具体来说，不安全主" |
| "要用于以下四个方面：" |
| |
| #: src/unsafe.md:9 |
| msgid "dereferencing raw pointers" |
| msgstr "解引用裸指针" |
| |
| #: src/unsafe.md:10 |
| msgid "" |
| "calling functions or methods which are `unsafe` (including calling a " |
| "function over FFI, see [a previous chapter](std_misc/ffi.md) of the book)" |
| msgstr "" |
| "调用被标记为 `unsafe` 的函数或方法（包括通过 FFI 调用函数，参见本书[前面的章" |
| "节](std_misc/ffi.md)）" |
| |
| #: src/unsafe.md:12 |
| msgid "accessing or modifying static mutable variables" |
| msgstr "访问或修改静态可变变量" |
| |
| #: src/unsafe.md:13 |
| msgid "implementing unsafe traits" |
| msgstr "实现不安全特征" |
| |
| #: src/unsafe.md:15 |
| msgid "Raw Pointers" |
| msgstr "裸指针" |
| |
| #: src/unsafe.md:17 |
| msgid "" |
| "Raw pointers `*` and references `&T` function similarly, but references are " |
| "always safe because they are guaranteed to point to valid data due to the " |
| "borrow checker. Dereferencing a raw pointer can only be done through an " |
| "unsafe block." |
| msgstr "" |
| "裸指针 `*` 和引用 `&T` 的功能类似，但引用总是安全的，因为借用检查器保证它们指" |
| "向有效数据。解引用裸指针只能在 unsafe 块中进行。" |
| |
| #: src/unsafe.md:32 |
| msgid "Calling Unsafe Functions" |
| msgstr "调用不安全函数" |
| |
| #: src/unsafe.md:34 |
| msgid "" |
| "Some functions can be declared as `unsafe`, meaning it is the programmer's " |
| "responsibility to ensure correctness instead of the compiler's. One example " |
| "of this is [`std::slice::from_raw_parts`](https://doc.rust-lang.org/std/" |
| "slice/fn.from_raw_parts.html) which will create a slice given a pointer to " |
| "the first element and a length." |
| msgstr "" |
| "某些函数可以被声明为 `unsafe`，这意味着确保其正确性是程序员的责任，而不是编译" |
| "器的责任。一个例子是 [`std::slice::from_raw_parts`](https://doc.rust-" |
| "lang.org/std/slice/fn.from_raw_parts.html)，它根据指向第一个元素的指针和长度" |
| "创建一个切片。" |
| |
| #: src/unsafe.md:56 |
| msgid "" |
| "For `slice::from_raw_parts`, one of the assumptions which _must_ be upheld " |
| "is that the pointer passed in points to valid memory and that the memory " |
| "pointed to is of the correct type. If these invariants aren't upheld then " |
| "the program's behaviour is undefined and there is no knowing what will " |
| "happen." |
| msgstr "" |
| "对于 `slice::from_raw_parts`，**必须**遵守的一个假设是：传入的指针指向有效内" |
| "存，且指向的内存类型正确。如果这些不变量未被遵守，那么程序的行为将是未定义" |
| "的，无法预知会发生什么。" |
| |
| #: src/unsafe/asm.md:3 |
| msgid "" |
| "Rust provides support for inline assembly via the `asm!` macro. It can be " |
| "used to embed handwritten assembly in the assembly output generated by the " |
| "compiler. Generally this should not be necessary, but might be where the " |
| "required performance or timing cannot be otherwise achieved. Accessing low " |
| "level hardware primitives, e.g. in kernel code, may also demand this " |
| "functionality." |
| msgstr "" |
| "Rust 通过 `asm!` 宏提供了内联汇编支持。它可以用于在编译器生成的汇编输出中嵌入" |
| "手写的汇编代码。通常这不是必需的，但在无法通过其他方式实现所需性能或时序要求" |
| "时可能会用到。访问底层硬件原语（例如在内核代码中）也可能需要这个功能。" |
| |
| #: src/unsafe/asm.md:8 |
| msgid "" |
| "**Note**: the examples here are given in x86/x86-64 assembly, but other " |
| "architectures are also supported." |
| msgstr "**注意**：这里的示例使用 x86/x86-64 汇编，但也支持其他架构。" |
| |
| #: src/unsafe/asm.md:10 |
| msgid "Inline assembly is currently supported on the following architectures:" |
| msgstr "目前支持内联汇编的架构包括：" |
| |
| #: src/unsafe/asm.md:12 |
| msgid "x86 and x86-64" |
| msgstr "x86 和 x86-64" |
| |
| #: src/unsafe/asm.md:13 |
| msgid "ARM" |
| msgstr "ARM" |
| |
| #: src/unsafe/asm.md:14 |
| msgid "AArch64" |
| msgstr "AArch64" |
| |
| #: src/unsafe/asm.md:15 |
| msgid "RISC-V" |
| msgstr "RISC-V" |
| |
| #: src/unsafe/asm.md:17 |
| msgid "Basic usage" |
| msgstr "基本用法" |
| |
| #: src/unsafe/asm.md:19 |
| msgid "Let us start with the simplest possible example:" |
| msgstr "让我们从最简单的例子开始：" |
| |
| #: src/unsafe/asm.md:22 src/unsafe/asm.md:42 src/unsafe/asm.md:69 |
| #: src/unsafe/asm.md:107 src/unsafe/asm.md:124 src/unsafe/asm.md:149 |
| #: src/unsafe/asm.md:183 src/unsafe/asm.md:204 src/unsafe/asm.md:221 |
| #: src/unsafe/asm.md:260 src/unsafe/asm.md:296 src/unsafe/asm.md:312 |
| #: src/unsafe/asm.md:338 src/unsafe/asm.md:376 src/unsafe/asm.md:403 |
| #: src/unsafe/asm.md:427 src/unsafe/asm.md:465 |
| msgid "\"x86_64\"" |
| msgstr "\"x86_64\"" |
| |
| #: src/unsafe/asm.md:26 |
| msgid "\"nop\"" |
| msgstr "\"nop\"" |
| |
| #: src/unsafe/asm.md:31 |
| msgid "" |
| "This will insert a NOP (no operation) instruction into the assembly " |
| "generated by the compiler. Note that all `asm!` invocations have to be " |
| "inside an `unsafe` block, as they could insert arbitrary instructions and " |
| "break various invariants. The instructions to be inserted are listed in the " |
| "first argument of the `asm!` macro as a string literal." |
| msgstr "" |
| "这将在编译器生成的汇编代码中插入一条 NOP（无操作）指令。请注意，所有 `asm!` " |
| "调用都必须放在 `unsafe` 块内，因为它们可能插入任意指令并破坏各种不变量。要插" |
| "入的指令以字符串字面量的形式列在 `asm!` 宏的第一个参数中。" |
| |
| #: src/unsafe/asm.md:36 |
| msgid "Inputs and outputs" |
| msgstr "输入和输出" |
| |
| #: src/unsafe/asm.md:38 |
| msgid "" |
| "Now inserting an instruction that does nothing is rather boring. Let us do " |
| "something that actually acts on data:" |
| msgstr "插入一个什么都不做的指令相当无聊。让我们来做些实际操作数据的事情：" |
| |
| #: src/unsafe/asm.md:47 |
| msgid "\"mov {}, 5\"" |
| msgstr "\"mov {}, 5\"" |
| |
| #: src/unsafe/asm.md:53 |
| msgid "" |
| "This will write the value `5` into the `u64` variable `x`. You can see that " |
| "the string literal we use to specify instructions is actually a template " |
| "string. It is governed by the same rules as Rust [format strings](https://" |
| "doc.rust-lang.org/std/fmt/#syntax). The arguments that are inserted into the " |
| "template however look a bit different than you may be familiar with. First " |
| "we need to specify if the variable is an input or an output of the inline " |
| "assembly. In this case it is an output. We declared this by writing `out`. " |
| "We also need to specify in what kind of register the assembly expects the " |
| "variable. In this case we put it in an arbitrary general purpose register by " |
| "specifying `reg`. The compiler will choose an appropriate register to insert " |
| "into the template and will read the variable from there after the inline " |
| "assembly finishes executing." |
| msgstr "" |
| "这将把值 `5` 写入 `u64` 类型的变量 `x`。你可以看到，我们用来指定指令的字符串" |
| "字面量实际上是一个模板字符串。它遵循与 Rust [格式化字符串](https://doc.rust-" |
| "lang.org/std/fmt/#syntax)相同的规则。然而，插入到模板中的参数看起来可能与你熟" |
| "悉的有些不同。首先，我们需要指定变量是内联汇编的输入还是输出。在这个例子中，" |
| "它是一个输出。我们通过写 `out` 来声明这一点。我们还需要指定汇编期望变量在什么" |
| "类型的寄存器中。这里我们通过指定 `reg` 将其放在任意通用寄存器中。编译器将选择" |
| "一个合适的寄存器插入到模板中，并在内联汇编执行完成后从该寄存器读取变量的值。" |
| |
| #: src/unsafe/asm.md:66 |
| msgid "Let us see another example that also uses an input:" |
| msgstr "让我们再看一个使用输入的例子：" |
| |
| #: src/unsafe/asm.md:76 |
| msgid "\"mov {0}, {1}\"" |
| msgstr "\"mov {0}, {1}\"" |
| |
| #: src/unsafe/asm.md:77 src/unsafe/asm.md:112 src/unsafe/asm.md:130 |
| msgid "\"add {0}, 5\"" |
| msgstr "\"add {0}, 5\"" |
| |
| #: src/unsafe/asm.md:86 |
| msgid "" |
| "This will add `5` to the input in variable `i` and write the result to " |
| "variable `o`. The particular way this assembly does this is first copying " |
| "the value from `i` to the output, and then adding `5` to it." |
| msgstr "" |
| "这段代码会将 `5` 加到变量 `i` 的值上，然后将结果写入变量 `o`。具体的汇编实现" |
| "是先将 `i` 的值复制到输出寄存器，然后再加上 `5`。" |
| |
| #: src/unsafe/asm.md:90 |
| msgid "The example shows a few things:" |
| msgstr "这个例子展示了几个要点：" |
| |
| #: src/unsafe/asm.md:92 |
| msgid "" |
| "First, we can see that `asm!` allows multiple template string arguments; " |
| "each one is treated as a separate line of assembly code, as if they were all " |
| "joined together with newlines between them. This makes it easy to format " |
| "assembly code." |
| msgstr "" |
| "`asm!` 宏支持多个模板字符串参数，每个参数都被视为独立的汇编代码行，就像它们之" |
| "间用换行符连接一样。这使得格式化汇编代码变得简单。" |
| |
| #: src/unsafe/asm.md:97 |
| msgid "" |
| "Second, we can see that inputs are declared by writing `in` instead of `out`." |
| msgstr "其次，我们可以看到输入参数使用 `in` 声明，而不是 `out`。" |
| |
| #: src/unsafe/asm.md:99 |
| msgid "" |
| "Third, we can see that we can specify an argument number, or name as in any " |
| "format string. For inline assembly templates this is particularly useful as " |
| "arguments are often used more than once. For more complex inline assembly " |
| "using this facility is generally recommended, as it improves readability, " |
| "and allows reordering instructions without changing the argument order." |
| msgstr "" |
| "第三，我们可以像在任何格式字符串中一样指定参数编号或名称。这在内联汇编模板中" |
| "特别有用，因为参数通常会被多次使用。对于更复杂的内联汇编，建议使用这种方式，" |
| "因为它提高了可读性，并且允许在不改变参数顺序的情况下重新排列指令。" |
| |
| #: src/unsafe/asm.md:104 |
| msgid "We can further refine the above example to avoid the `mov` instruction:" |
| msgstr "我们可以进一步优化上面的例子，避免使用 `mov` 指令：" |
| |
| #: src/unsafe/asm.md:118 |
| msgid "" |
| "We can see that `inout` is used to specify an argument that is both input " |
| "and output. This is different from specifying an input and output separately " |
| "in that it is guaranteed to assign both to the same register." |
| msgstr "" |
| "我们可以看到 `inout` 用于指定既作为输入又作为输出的参数。这与分别指定输入和输" |
| "出不同，它保证将两者分配到同一个寄存器。" |
| |
| #: src/unsafe/asm.md:121 |
| msgid "" |
| "It is also possible to specify different variables for the input and output " |
| "parts of an `inout` operand:" |
| msgstr "也可以为 `inout` 操作数的输入和输出部分指定不同的变量：" |
| |
| #: src/unsafe/asm.md:136 |
| msgid "Late output operands" |
| msgstr "延迟输出操作数" |
| |
| #: src/unsafe/asm.md:138 |
| msgid "" |
| "The Rust compiler is conservative with its allocation of operands. It is " |
| "assumed that an `out` can be written at any time, and can therefore not " |
| "share its location with any other argument. However, to guarantee optimal " |
| "performance it is important to use as few registers as possible, so they " |
| "won't have to be saved and reloaded around the inline assembly block. To " |
| "achieve this Rust provides a `lateout` specifier. This can be used on any " |
| "output that is written only after all inputs have been consumed. There is " |
| "also an `inlateout` variant of this specifier." |
| msgstr "" |
| "Rust 编译器在分配操作数时采取保守策略。它假设 `out` 可以在任何时候被写入，因" |
| "此不能与其他参数共享位置。然而，为了保证最佳性能，使用尽可能少的寄存器很重" |
| "要，这样就不必在内联汇编块前后保存和重新加载寄存器。为此，Rust 提供了 " |
| "`lateout` 说明符。这可以用于任何在所有输入被消耗后才写入的输出。此外还有一个 " |
| "`inlateout` 变体。" |
| |
| #: src/unsafe/asm.md:146 |
| msgid "" |
| "Here is an example where `inlateout` _cannot_ be used in `release` mode or " |
| "other optimized cases:" |
| msgstr "" |
| "以下是一个在 `release` 模式或其他优化情况下 _不能_ 使用 `inlateout` 的例子：" |
| |
| #: src/unsafe/asm.md:157 src/unsafe/asm.md:189 src/unsafe/asm.md:472 |
| msgid "\"add {0}, {1}\"" |
| msgstr "\"add {0}, {1}\"" |
| |
| #: src/unsafe/asm.md:158 |
| msgid "\"add {0}, {2}\"" |
| msgstr "\"add {0}, {2}\"" |
| |
| #: src/unsafe/asm.md:168 |
| msgid "" |
| "In unoptimized cases (e.g. `Debug` mode), replacing `inout(reg) a` with " |
| "`inlateout(reg) a` in the above example can continue to give the expected " |
| "result. However, with `release` mode or other optimized cases, using " |
| "`inlateout(reg) a` can instead lead to the final value `a = 16`, causing the " |
| "assertion to fail." |
| msgstr "" |
| "在未优化的情况下（如 `Debug` 模式），将上述例子中的 `inout(reg) a` 替换为 " |
| "`inlateout(reg) a` 仍能得到预期结果。但在 `release` 模式或其他优化情况下，使" |
| "用 `inlateout(reg) a` 可能导致最终值 `a = 16`，使断言失败。" |
| |
| #: src/unsafe/asm.md:173 |
| msgid "" |
| "This is because in optimized cases, the compiler is free to allocate the " |
| "same register for inputs `b` and `c` since it knows that they have the same " |
| "value. Furthermore, when `inlateout` is used, `a` and `c` could be allocated " |
| "to the same register, in which case the first `add` instruction would " |
| "overwrite the initial load from variable `c`. This is in contrast to how " |
| "using `inout(reg) a` ensures a separate register is allocated for `a`." |
| msgstr "" |
| "这是因为在优化情况下，编译器可以为输入 `b` 和 `c` 分配相同的寄存器，因为它知" |
| "道它们具有相同的值。此外，当使用 `inlateout` 时，`a` 和 `c` 可能被分配到同一" |
| "个寄存器，这种情况下，第一条 `add` 指令会覆盖从变量 `c` 初始加载的值。相比之" |
| "下，使用 `inout(reg) a` 可以确保为 `a` 分配一个单独的寄存器。" |
| |
| #: src/unsafe/asm.md:179 |
| msgid "" |
| "However, the following example can use `inlateout` since the output is only " |
| "modified after all input registers have been read:" |
| msgstr "" |
| "然而，以下示例可以使用 `inlateout`，因为输出仅在读取所有输入寄存器后才被修" |
| "改：" |
| |
| #: src/unsafe/asm.md:195 |
| msgid "" |
| "As you can see, this assembly fragment will still work correctly if `a` and " |
| "`b` are assigned to the same register." |
| msgstr "" |
| "如你所见，即使 `a` 和 `b` 被分配到同一个寄存器，这段汇编代码片段仍能正确运" |
| "行。" |
| |
| #: src/unsafe/asm.md:197 |
| msgid "Explicit register operands" |
| msgstr "显式寄存器操作数" |
| |
| #: src/unsafe/asm.md:199 |
| msgid "" |
| "Some instructions require that the operands be in a specific register. " |
| "Therefore, Rust inline assembly provides some more specific constraint " |
| "specifiers. While `reg` is generally available on any architecture, explicit " |
| "registers are highly architecture specific. E.g. for x86 the general purpose " |
| "registers `eax`, `ebx`, `ecx`, `edx`, `ebp`, `esi`, and `edi` among others " |
| "can be addressed by their name." |
| msgstr "" |
| "某些指令要求操作数必须位于特定寄存器中。因此，Rust 内联汇编提供了一些更具体的" |
| "约束说明符。虽然 `reg` 通常适用于任何架构，但显式寄存器高度依赖于特定架构。例" |
| "如，对于 x86 架构，通用寄存器如 `eax`、`ebx`、`ecx`、`edx`、`ebp`、`esi` 和 " |
| "`edi` 等可以直接通过名称进行寻址。" |
| |
| #: src/unsafe/asm.md:209 |
| msgid "\"out 0x64, eax\"" |
| msgstr "\"out 0x64, eax\"" |
| |
| #: src/unsafe/asm.md:209 src/unsafe/asm.md:285 |
| msgid "\"eax\"" |
| msgstr "\"eax\"" |
| |
| #: src/unsafe/asm.md:214 |
| msgid "" |
| "In this example we call the `out` instruction to output the content of the " |
| "`cmd` variable to port `0x64`. Since the `out` instruction only accepts " |
| "`eax` (and its sub registers) as operand we had to use the `eax` constraint " |
| "specifier." |
| msgstr "" |
| "在这个例子中，我们调用 `out` 指令将 `cmd` 变量的内容输出到端口 `0x64`。由于 " |
| "`out` 指令只接受 `eax`（及其子寄存器）作为操作数，我们必须使用 `eax` 约束说明" |
| "符。" |
| |
| #: src/unsafe/asm.md:216 |
| msgid "" |
| "**Note**: unlike other operand types, explicit register operands cannot be " |
| "used in the template string: you can't use `{}` and should write the " |
| "register name directly instead. Also, they must appear at the end of the " |
| "operand list after all other operand types." |
| msgstr "" |
| "**注意**：与其他操作数类型不同，显式寄存器操作数不能在模板字符串中使用。你不" |
| "能使用 `{}`，而应直接写入寄存器名称。此外，它们必须出现在操作数列表的末尾，位" |
| "于所有其他操作数类型之后。" |
| |
| #: src/unsafe/asm.md:218 |
| msgid "Consider this example which uses the x86 `mul` instruction:" |
| msgstr "考虑以下使用 x86 `mul` 指令的例子：" |
| |
| #: src/unsafe/asm.md:230 |
| msgid "" |
| "// The x86 mul instruction takes rax as an implicit input and writes\n" |
| " // the 128-bit result of the multiplication to rax:rdx.\n" |
| " \"mul {}\"" |
| msgstr "" |
| "// x86 的 mul 指令将 rax 作为隐式输入，\n" |
| " // 并将乘法的 128 位结果写入 rax:rdx。\n" |
| " \"mul {}\"" |
| |
| #: src/unsafe/asm.md:234 src/unsafe/asm.md:356 |
| msgid "\"rax\"" |
| msgstr "\"rax\"" |
| |
| #: src/unsafe/asm.md:235 |
| msgid "\"rdx\"" |
| msgstr "\"rdx\"" |
| |
| #: src/unsafe/asm.md:244 |
| msgid "" |
| "This uses the `mul` instruction to multiply two 64-bit inputs with a 128-bit " |
| "result. The only explicit operand is a register, that we fill from the " |
| "variable `a`. The second operand is implicit, and must be the `rax` " |
| "register, which we fill from the variable `b`. The lower 64 bits of the " |
| "result are stored in `rax` from which we fill the variable `lo`. The higher " |
| "64 bits are stored in `rdx` from which we fill the variable `hi`." |
| msgstr "" |
| "这里使用 `mul` 指令将两个 64 位输入相乘，得到一个 128 位的结果。唯一的显式操" |
| "作数是一个寄存器，我们用变量 `a` 填充它。第二个操作数是隐式的，必须是 `rax` " |
| "寄存器，我们用变量 `b` 填充它。结果的低 64 位存储在 `rax` 中，用于填充变量 " |
| "`lo`。高 64 位存储在 `rdx` 中，用于填充变量 `hi`。" |
| |
| #: src/unsafe/asm.md:250 |
| msgid "Clobbered registers" |
| msgstr "被破坏的寄存器" |
| |
| #: src/unsafe/asm.md:252 |
| msgid "" |
| "In many cases inline assembly will modify state that is not needed as an " |
| "output. Usually this is either because we have to use a scratch register in " |
| "the assembly or because instructions modify state that we don't need to " |
| "further examine. This state is generally referred to as being \"clobbered\". " |
| "We need to tell the compiler about this since it may need to save and " |
| "restore this state around the inline assembly block." |
| msgstr "" |
| "在许多情况下，内联汇编会修改不需要作为输出的状态。这通常是因为我们必须在汇编" |
| "中使用临时寄存器，或者因为指令修改了我们不需要进一步检查的状态。这种状态通常" |
| "被称为\"被破坏\"。我们需要告知编译器这一点，因为它可能需要在内联汇编块前后保" |
| "存和恢复这种状态。" |
| |
| #: src/unsafe/asm.md:262 |
| msgid "// three entries of four bytes each\n" |
| msgstr "// 三个条目，每个四字节\n" |
| |
| #: src/unsafe/asm.md:264 |
| msgid "" |
| "// String is stored as ascii in ebx, edx, ecx in order\n" |
| " // Because ebx is reserved, the asm needs to preserve the value of it.\n" |
| " // So we push and pop it around the main asm.\n" |
| " // 64 bit mode on 64 bit processors does not allow pushing/popping of\n" |
| " // 32 bit registers (like ebx), so we have to use the extended rbx " |
| "register instead.\n" |
| msgstr "" |
| "// 字符串按顺序以 ASCII 格式存储在 ebx、edx、ecx 中\n" |
| " // 由于 ebx 是保留寄存器，汇编需要保留其值\n" |
| " // 因此我们在主要汇编代码前后执行 push 和 pop 操作\n" |
| " // 64 位处理器的 64 位模式不允许对 32 位寄存器（如 ebx）进行 push/pop 操" |
| "作\n" |
| " // 所以我们必须使用扩展的 rbx 寄存器\n" |
| |
| #: src/unsafe/asm.md:272 |
| msgid "\"push rbx\"" |
| msgstr "\"push rbx\"" |
| |
| #: src/unsafe/asm.md:273 |
| msgid "\"cpuid\"" |
| msgstr "\"cpuid\"" |
| |
| #: src/unsafe/asm.md:274 |
| msgid "\"mov [rdi], ebx\"" |
| msgstr "\"mov [rdi], ebx\"" |
| |
| #: src/unsafe/asm.md:275 |
| msgid "\"mov [rdi + 4], edx\"" |
| msgstr "\"mov [rdi + 4], edx\"" |
| |
| #: src/unsafe/asm.md:276 |
| msgid "\"mov [rdi + 8], ecx\"" |
| msgstr "\"mov [rdi + 8], ecx\"" |
| |
| #: src/unsafe/asm.md:277 |
| msgid "\"pop rbx\"" |
| msgstr "\"pop rbx\"" |
| |
| #: src/unsafe/asm.md:278 |
| msgid "" |
| "// We use a pointer to an array for storing the values to simplify\n" |
| " // the Rust code at the cost of a couple more asm instructions\n" |
| " // This is more explicit with how the asm works however, as " |
| "opposed\n" |
| " // to explicit register outputs such as `out(\"ecx\") val`\n" |
| " // The *pointer itself* is only an input even though it's " |
| "written behind\n" |
| msgstr "" |
| "// 我们使用指向数组的指针来存储值，以简化 Rust 代码\n" |
| " // 虽然这会增加几条汇编指令，但更清晰地展示了汇编的工作方式\n" |
| " // 相比于使用显式寄存器输出（如 `out(\"ecx\") val`）\n" |
| " // *指针本身*只是一个输入，尽管它在背后被写入\n" |
| |
| #: src/unsafe/asm.md:283 src/unsafe/asm.md:354 |
| msgid "\"rdi\"" |
| msgstr "\"rdi\"" |
| |
| #: src/unsafe/asm.md:284 |
| msgid "// select cpuid 0, also specify eax as clobbered\n" |
| msgstr "// 选择 cpuid 0，同时指定 eax 为被修改寄存器\n" |
| |
| #: src/unsafe/asm.md:286 |
| msgid "// cpuid clobbers these registers too\n" |
| msgstr "// cpuid 也会修改这些寄存器\n" |
| |
| #: src/unsafe/asm.md:287 |
| msgid "\"ecx\"" |
| msgstr "\"ecx\"" |
| |
| #: src/unsafe/asm.md:288 |
| msgid "\"edx\"" |
| msgstr "\"edx\"" |
| |
| #: src/unsafe/asm.md:293 |
| msgid "\"CPU Manufacturer ID: {}\"" |
| msgstr "\"CPU 制造商 ID：{}\"" |
| |
| #: src/unsafe/asm.md:300 |
| msgid "" |
| "In the example above we use the `cpuid` instruction to read the CPU " |
| "manufacturer ID. This instruction writes to `eax` with the maximum supported " |
| "`cpuid` argument and `ebx`, `edx`, and `ecx` with the CPU manufacturer ID as " |
| "ASCII bytes in that order." |
| msgstr "" |
| "在上面的示例中，我们使用 `cpuid` 指令读取 CPU 制造商 ID。该指令将最大支持的 " |
| "`cpuid` 参数写入 `eax`，并按顺序将 CPU 制造商 ID 的 ASCII 字节写入 `ebx`、" |
| "`edx` 和 `ecx`。" |
| |
| #: src/unsafe/asm.md:303 |
| msgid "" |
| "Even though `eax` is never read we still need to tell the compiler that the " |
| "register has been modified so that the compiler can save any values that " |
| "were in these registers before the asm. This is done by declaring it as an " |
| "output but with `_` instead of a variable name, which indicates that the " |
| "output value is to be discarded." |
| msgstr "" |
| "尽管 `eax` 从未被读取，我们仍需要告知编译器该寄存器已被修改，这样编译器就可以" |
| "保存汇编前这些寄存器中的任何值。我们通过将其声明为输出来实现这一点，但使用 " |
| "`_` 而非变量名，表示输出值将被丢弃。" |
| |
| #: src/unsafe/asm.md:305 |
| msgid "" |
| "This code also works around the limitation that `ebx` is a reserved register " |
| "by LLVM. That means that LLVM assumes that it has full control over the " |
| "register and it must be restored to its original state before exiting the " |
| "asm block, so it cannot be used as an input or output **except** if the " |
| "compiler uses it to fulfill a general register class (e.g. `in(reg)`). This " |
| "makes `reg` operands dangerous when using reserved registers as we could " |
| "unknowingly corrupt our input or output because they share the same register." |
| msgstr "" |
| "这段代码还解决了 LLVM 将 `ebx` 视为保留寄存器的限制。这意味着 LLVM 假定它对该" |
| "寄存器拥有完全控制权，并且必须在退出汇编块之前将其恢复到原始状态。因此，" |
| "`ebx` 不能用作输入或输出，**除非**编译器将其用于满足通用寄存器类（如 " |
| "`in(reg)`）。这使得在使用保留寄存器时，`reg` 操作数变得危险，因为我们可能会在" |
| "不知情的情况下破坏输入或输出，原因是它们共享同一个寄存器。" |
| |
| #: src/unsafe/asm.md:307 |
| msgid "" |
| "To work around this we use `rdi` to store the pointer to the output array, " |
| "save `ebx` via `push`, read from `ebx` inside the asm block into the array " |
| "and then restore `ebx` to its original state via `pop`. The `push` and `pop` " |
| "use the full 64-bit `rbx` version of the register to ensure that the entire " |
| "register is saved. On 32 bit targets the code would instead use `ebx` in the " |
| "`push`/`pop`." |
| msgstr "" |
| "为了解决这个问题，我们采用以下策略：使用 `rdi` 存储输出数组的指针；通过 " |
| "`push` 保存 `ebx`；在汇编块内从 `ebx` 读取数据到数组中；然后通过 `pop` 将 " |
| "`ebx` 恢复到原始状态。`push` 和 `pop` 操作使用完整的 64 位 `rbx` 寄存器版本，" |
| "以确保整个寄存器被保存。在 32 位目标上，代码会在 `push`/`pop` 操作中使用 " |
| "`ebx`。" |
| |
| #: src/unsafe/asm.md:309 |
| msgid "" |
| "This can also be used with a general register class to obtain a scratch " |
| "register for use inside the asm code:" |
| msgstr "" |
| "这种技术还可以与通用寄存器类一起使用，以获得一个临时寄存器在汇编代码内使用：" |
| |
| #: src/unsafe/asm.md:314 |
| msgid "// Multiply x by 6 using shifts and adds\n" |
| msgstr "// 使用移位和加法将 x 乘以 6\n" |
| |
| #: src/unsafe/asm.md:319 |
| msgid "\"mov {tmp}, {x}\"" |
| msgstr "\"mov {tmp}, {x}\"" |
| |
| #: src/unsafe/asm.md:320 |
| msgid "\"shl {tmp}, 1\"" |
| msgstr "\"shl {tmp}, 1\"" |
| |
| #: src/unsafe/asm.md:321 |
| msgid "\"shl {x}, 2\"" |
| msgstr "\"shl {x}, 2\"" |
| |
| #: src/unsafe/asm.md:322 |
| msgid "\"add {x}, {tmp}\"" |
| msgstr "\"add {x}, {tmp}\"" |
| |
| #: src/unsafe/asm.md:331 |
| msgid "Symbol operands and ABI clobbers" |
| msgstr "符号操作数和 ABI 破坏" |
| |
| #: src/unsafe/asm.md:333 |
| msgid "" |
| "By default, `asm!` assumes that any register not specified as an output will " |
| "have its contents preserved by the assembly code. The [`clobber_abi`]" |
| "(https://doc.rust-lang.org/stable/reference/inline-assembly.html#abi-" |
| "clobbers) argument to `asm!` tells the compiler to automatically insert the " |
| "necessary clobber operands according to the given calling convention ABI: " |
| "any register which is not fully preserved in that ABI will be treated as " |
| "clobbered. Multiple `clobber_abi` arguments may be provided and all " |
| "clobbers from all specified ABIs will be inserted." |
| msgstr "" |
| "默认情况下，`asm!` 假定汇编代码会保留所有未指定为输出的寄存器的内容。`asm!` " |
| "的 [`clobber_abi`](https://doc.rust-lang.org/stable/reference/inline-" |
| "assembly.html#abi-clobbers) 参数告诉编译器根据给定的调用约定 ABI 自动插入必要" |
| "的破坏操作数：任何在该 ABI 中未完全保留的寄存器都将被视为被破坏。可以提供多" |
| "个 `clobber_abi` 参数，所有指定 ABI 的破坏都将被插入。" |
| |
| #: src/unsafe/asm.md:341 src/unsafe/asm.md:359 |
| msgid "\"C\"" |
| msgstr "\"C\"" |
| |
| #: src/unsafe/asm.md:342 |
| msgid "\"arg = {}\"" |
| msgstr "\"arg = {}\"" |
| |
| #: src/unsafe/asm.md:350 |
| msgid "\"call {}\"" |
| msgstr "\"call {}\"" |
| |
| #: src/unsafe/asm.md:351 |
| msgid "// Function pointer to call\n" |
| msgstr "// 要调用的函数指针\n" |
| |
| #: src/unsafe/asm.md:353 |
| msgid "// 1st argument in rdi\n" |
| msgstr "// 第一个参数在 rdi 中\n" |
| |
| #: src/unsafe/asm.md:355 |
| msgid "// Return value in rax\n" |
| msgstr "// 返回值在 rax 中\n" |
| |
| #: src/unsafe/asm.md:357 |
| msgid "" |
| "// Mark all registers which are not preserved by the \"C\" calling\n" |
| " // convention as clobbered.\n" |
| msgstr "" |
| "// 将所有不被 \"C\" 调用约定保留的寄存器\n" |
| " // 标记为被破坏\n" |
| |
| #: src/unsafe/asm.md:367 |
| msgid "Register template modifiers" |
| msgstr "寄存器模板修饰符" |
| |
| #: src/unsafe/asm.md:369 |
| msgid "" |
| "In some cases, fine control is needed over the way a register name is " |
| "formatted when inserted into the template string. This is needed when an " |
| "architecture's assembly language has several names for the same register, " |
| "each typically being a \"view\" over a subset of the register (e.g. the low " |
| "32 bits of a 64-bit register)." |
| msgstr "" |
| "在某些情况下，需要对寄存器名称插入模板字符串时的格式进行精细控制。当一个架构" |
| "的汇编语言对同一个寄存器有多个名称时，这种控制尤为必要。每个名称通常代表寄存" |
| "器的一个子集\"视图\"（例如，64 位寄存器的低 32 位）。" |
| |
| #: src/unsafe/asm.md:371 |
| msgid "" |
| "By default the compiler will always choose the name that refers to the full " |
| "register size (e.g. `rax` on x86-64, `eax` on x86, etc)." |
| msgstr "" |
| "默认情况下，编译器总是会选择引用完整寄存器大小的名称（例如，在 x86-64 上是 " |
| "`rax`，在 x86 上是 `eax` 等）。" |
| |
| #: src/unsafe/asm.md:373 |
| msgid "" |
| "This default can be overridden by using modifiers on the template string " |
| "operands, just like you would with format strings:" |
| msgstr "" |
| "可以通过在模板字符串操作数上使用修饰符来覆盖这个默认设置，类似于格式字符串的" |
| "用法：" |
| |
| #: src/unsafe/asm.md:382 |
| msgid "\"mov {0:h}, {0:l}\"" |
| msgstr "\"mov {0:h}, {0:l}\"" |
| |
| #: src/unsafe/asm.md:389 |
| msgid "" |
| "In this example, we use the `reg_abcd` register class to restrict the " |
| "register allocator to the 4 legacy x86 registers (`ax`, `bx`, `cx`, `dx`) of " |
| "which the first two bytes can be addressed independently." |
| msgstr "" |
| "在这个例子中，我们使用 `reg_abcd` 寄存器类来限制寄存器分配器只使用 4 个传统" |
| "的 x86 寄存器（`ax`、`bx`、`cx`、`dx`）。这些寄存器的前两个字节可以独立寻址。" |
| |
| #: src/unsafe/asm.md:391 |
| msgid "" |
| "Let us assume that the register allocator has chosen to allocate `x` in the " |
| "`ax` register. The `h` modifier will emit the register name for the high " |
| "byte of that register and the `l` modifier will emit the register name for " |
| "the low byte. The asm code will therefore be expanded as `mov ah, al` which " |
| "copies the low byte of the value into the high byte." |
| msgstr "" |
| "假设寄存器分配器选择将 `x` 分配到 `ax` 寄存器。`h` 修饰符将生成该寄存器高字节" |
| "的名称，而 `l` 修饰符将生成低字节的名称。因此，汇编代码将被展开为 `mov ah, " |
| "al`，这条指令将值的低字节复制到高字节。" |
| |
| #: src/unsafe/asm.md:394 |
| msgid "" |
| "If you use a smaller data type (e.g. `u16`) with an operand and forget to " |
| "use template modifiers, the compiler will emit a warning and suggest the " |
| "correct modifier to use." |
| msgstr "" |
| "如果你对操作数使用较小的数据类型（例如 `u16`）并忘记使用模板修饰符，编译器将" |
| "发出警告并建议使用正确的修饰符。" |
| |
| #: src/unsafe/asm.md:396 |
| msgid "Memory address operands" |
| msgstr "内存地址操作数" |
| |
| #: src/unsafe/asm.md:398 |
| msgid "" |
| "Sometimes assembly instructions require operands passed via memory addresses/" |
| "memory locations. You have to manually use the memory address syntax " |
| "specified by the target architecture. For example, on x86/x86_64 using Intel " |
| "assembly syntax, you should wrap inputs/outputs in `[]` to indicate they are " |
| "memory operands:" |
| msgstr "" |
| "有时汇编指令需要通过内存地址或内存位置传递操作数。你必须手动使用目标架构指定" |
| "的内存地址语法。例如，在使用 Intel 汇编语法的 x86/x86_64 架构上，你应该用 " |
| "`[]` 包裹输入/输出，以表明它们是内存操作数：" |
| |
| #: src/unsafe/asm.md:408 |
| msgid "\"fldcw [{}]\"" |
| msgstr "\"fldcw [{}]\"" |
| |
| #: src/unsafe/asm.md:414 |
| msgid "Labels" |
| msgstr "标签" |
| |
| #: src/unsafe/asm.md:416 |
| msgid "" |
| "Any reuse of a named label, local or otherwise, can result in an assembler " |
| "or linker error or may cause other strange behavior. Reuse of a named label " |
| "can happen in a variety of ways including:" |
| msgstr "" |
| "重复使用命名标签（无论是局部的还是其他类型的）可能导致汇编器或链接器错误，或" |
| "引起其他异常行为。命名标签的重用可能以多种方式发生，包括：" |
| |
| #: src/unsafe/asm.md:418 |
| msgid "" |
| "explicitly: using a label more than once in one `asm!` block, or multiple " |
| "times across blocks." |
| msgstr "显式重用：在一个 `asm!` 块中多次使用同一标签，或在多个块之间重复使用。" |
| |
| #: src/unsafe/asm.md:419 |
| msgid "" |
| "implicitly via inlining: the compiler is allowed to instantiate multiple " |
| "copies of an `asm!` block, for example when the function containing it is " |
| "inlined in multiple places." |
| msgstr "" |
| "通过内联隐式重用：编译器可能会创建 `asm!` 块的多个副本，例如当包含该块的函数" |
| "在多处被内联时。" |
| |
| #: src/unsafe/asm.md:420 |
| msgid "" |
| "implicitly via LTO: LTO can cause code from _other crates_ to be placed in " |
| "the same codegen unit, and so could bring in arbitrary labels." |
| msgstr "" |
| "通过 LTO 隐式重用：链接时优化（LTO）可能导致**其他 crate** 的代码被放置在同一" |
| "代码生成单元中，从而可能引入任意标签。" |
| |
| #: src/unsafe/asm.md:422 |
| msgid "" |
| "As a consequence, you should only use GNU assembler **numeric** [local " |
| "labels](https://sourceware.org/binutils/docs/as/Symbol-Names.html#Local-" |
| "Labels) inside inline assembly code. Defining symbols in assembly code may " |
| "lead to assembler and/or linker errors due to duplicate symbol definitions." |
| msgstr "" |
| "因此，你应该只在内联汇编代码中使用 GNU 汇编器的**数字**[局部标签](https://" |
| "sourceware.org/binutils/docs/as/Symbol-Names.html#Local-Labels)。在汇编代码中" |
| "定义符号可能会由于重复的符号定义而导致汇编器和/或链接器错误。" |
| |
| #: src/unsafe/asm.md:424 |
| msgid "" |
| "Moreover, on x86 when using the default Intel syntax, due to [an LLVM bug]" |
| "(https://bugs.llvm.org/show_bug.cgi?id=36144), you shouldn't use labels " |
| "exclusively made of `0` and `1` digits, e.g. `0`, `11` or `101010`, as they " |
| "may end up being interpreted as binary values. Using `options(att_syntax)` " |
| "will avoid any ambiguity, but that affects the syntax of the _entire_ `asm!` " |
| "block. (See [Options](#options), below, for more on `options`.)" |
| msgstr "" |
| "此外，在 x86 架构上使用默认的 Intel 语法时，由于[一个 LLVM 的 bug](https://" |
| "bugs.llvm.org/show_bug.cgi?id=36144)，你不应使用仅由 `0` 和 `1` 组成的标签，" |
| "如 `0`、`11` 或 `101010`，因为它们可能被误解为二进制值。使用 " |
| "`options(att_syntax)` 可以避免这种歧义，但这会影响*整个* `asm!` 块的语法。" |
| "（关于 `options` 的更多信息，请参见下文的[选项](#options)。）" |
| |
| #: src/unsafe/asm.md:433 |
| msgid "\"mov {0}, 10\"" |
| msgstr "\"mov {0}, 10\"" |
| |
| #: src/unsafe/asm.md:434 src/unsafe/asm.md:439 |
| msgid "\"2:\"" |
| msgstr "\"2:\"" |
| |
| #: src/unsafe/asm.md:435 |
| msgid "\"sub {0}, 1\"" |
| msgstr "\"sub {0}, 1\"" |
| |
| #: src/unsafe/asm.md:436 |
| msgid "\"cmp {0}, 3\"" |
| msgstr "\"cmp {0}, 3\"" |
| |
| #: src/unsafe/asm.md:437 |
| msgid "\"jle 2f\"" |
| msgstr "\"jle 2f\"" |
| |
| #: src/unsafe/asm.md:438 |
| msgid "\"jmp 2b\"" |
| msgstr "\"jmp 2b\"" |
| |
| #: src/unsafe/asm.md:440 |
| msgid "\"add {0}, 2\"" |
| msgstr "\"add {0}, 2\"" |
| |
| #: src/unsafe/asm.md:448 |
| msgid "" |
| "This will decrement the `{0}` register value from 10 to 3, then add 2 and " |
| "store it in `a`." |
| msgstr "" |
| "这段代码会将 `{0}` 寄存器的值从 10 递减到 3，然后加 2 并将结果存储在 `a` 中。" |
| |
| #: src/unsafe/asm.md:450 |
| msgid "This example shows a few things:" |
| msgstr "这个例子展示了几个要点：" |
| |
| #: src/unsafe/asm.md:452 |
| msgid "" |
| "First, that the same number can be used as a label multiple times in the " |
| "same inline block." |
| msgstr "首先，同一个数字可以在同一个内联块中多次用作标签。" |
| |
| #: src/unsafe/asm.md:453 |
| |
| msgid "" |
| "Second, that when a numeric label is used as a reference (as an instruction " |
| "operand, for example), the suffixes “b” (“backward”) or ”f” (“forward”) " |
| "should be added to the numeric label. It will then refer to the nearest " |
| "label defined by this number in this direction." |
| msgstr "" |
| "其次，当数字标签被用作引用（例如作为指令操作数）时，应在数字标签后添加后缀 " |
| "\"b\"（\"backward\"，向后）或 \"f\"（\"forward\"，向前）。这样它将引用该方向" |
| "上由这个数字定义的最近的标签。" |
| |
| #: src/unsafe/asm.md:458 |
| msgid "Options" |
| msgstr "选项" |
| |
| #: src/unsafe/asm.md:460 |
| msgid "" |
| "By default, an inline assembly block is treated the same way as an external " |
| "FFI function call with a custom calling convention: it may read/write " |
| "memory, have observable side effects, etc. However, in many cases it is " |
| "desirable to give the compiler more information about what the assembly code " |
| "is actually doing so that it can optimize better." |
| msgstr "" |
| "默认情况下，内联汇编块的处理方式与具有自定义调用约定的外部 FFI 函数调用相同：" |
| "它可能读写内存，产生可观察的副作用等。然而，在许多情况下，我们希望向编译器提" |
| "供更多关于汇编代码实际行为的信息，以便编译器能够进行更好的优化。" |
| |
| #: src/unsafe/asm.md:462 |
| msgid "Let's take our previous example of an `add` instruction:" |
| msgstr "让我们回顾一下之前 `add` 指令的例子：" |
| |
| #: src/unsafe/asm.md:481 |
| msgid "" |
| "Options can be provided as an optional final argument to the `asm!` macro. " |
| "We specified three options here:" |
| msgstr "" |
| "可以将选项作为可选的最后一个参数传递给 `asm!` 宏。在这个例子中，我们指定了三" |
| "个选项：" |
| |
| #: src/unsafe/asm.md:483 |
| msgid "" |
| "`pure` means that the asm code has no observable side effects and that its " |
| "output depends only on its inputs. This allows the compiler optimizer to " |
| "call the inline asm fewer times or even eliminate it entirely." |
| msgstr "" |
| "`pure`：表示汇编代码没有可观察的副作用，其输出仅依赖于输入。这使得编译器优化" |
| "器能够减少内联汇编的调用次数，甚至完全消除它。" |
| |
| #: src/unsafe/asm.md:484 |
| msgid "" |
| "`nomem` means that the asm code does not read or write to memory. By default " |
| "the compiler will assume that inline assembly can read or write any memory " |
| "address that is accessible to it (e.g. through a pointer passed as an " |
| "operand, or a global)." |
| msgstr "" |
| "`nomem`：表示汇编代码不读取或写入内存。默认情况下，编译器会假设内联汇编可以读" |
| "写任何它可访问的内存地址（例如通过作为操作数传递的指针或全局变量）。" |
| |
| #: src/unsafe/asm.md:485 |
| msgid "" |
| "`nostack` means that the asm code does not push any data onto the stack. " |
| "This allows the compiler to use optimizations such as the stack red zone on " |
| "x86-64 to avoid stack pointer adjustments." |
| msgstr "" |
| "`nostack`：表示汇编代码不会向栈中压入任何数据。这允许编译器使用诸如 x86-64 上" |
| "的栈红区等优化技术，以避免栈指针调整。" |
| |
| #: src/unsafe/asm.md:487 |
| msgid "" |
| "These allow the compiler to better optimize code using `asm!`, for example " |
| "by eliminating pure `asm!` blocks whose outputs are not needed." |
| msgstr "" |
| "这些选项使编译器能够更好地优化使用 `asm!` 的代码，例如消除那些输出未被使用的" |
| "纯 `asm!` 块。" |
| |
| #: src/unsafe/asm.md:489 |
| msgid "" |
| "See the [reference](https://doc.rust-lang.org/stable/reference/inline-" |
| "assembly.html) for the full list of available options and their effects." |
| msgstr "" |
| "有关可用选项的完整列表及其效果，请参阅[参考文档](https://doc.rust-lang.org/" |
| "stable/reference/inline-assembly.html)。" |
| |
| #: src/compatibility.md:3 |
| msgid "" |
| "The Rust language is evolving rapidly, and because of this certain " |
| "compatibility issues can arise, despite efforts to ensure forwards-" |
| "compatibility wherever possible." |
| msgstr "" |
| "Rust 语言正在快速发展，因此某些兼容性问题可能会出现，尽管我们努力确保尽可能" |
| "的向前兼容。" |
| |
| #: src/compatibility.md:7 |
| msgid "[Raw identifiers](compatibility/raw_identifiers.md)" |
| msgstr "[原始标识符](compatibility/raw_identifiers.md)" |
| |
| #: src/compatibility/raw_identifiers.md:3 |
| msgid "" |
| "Rust, like many programming languages, has the concept of \"keywords\". " |
| "These identifiers mean something to the language, and so you cannot use them " |
| "in places like variable names, function names, and other places. Raw " |
| "identifiers let you use keywords where they would not normally be allowed. " |
| "This is particularly useful when Rust introduces new keywords, and a library " |
| "using an older edition of Rust has a variable or function with the same name " |
| "as a keyword introduced in a newer edition." |
| msgstr "" |
| "Rust 和许多编程语言一样，有\"关键字\"的概念。这些标识符在语言中具有特殊含义，" |
| "因此你不能在变量名、函数名等地方使用它们。原始标识符允许你在通常不允许使用关" |
| "键字的地方使用它们。这在 Rust 引入新关键字，而使用旧版本 Rust 的库中有与新版" |
| "本引入的关键字同名的变量或函数时特别有用。" |
| |
| #: src/compatibility/raw_identifiers.md:11 |
| msgid "" |
| "For example, consider a crate `foo` compiled with the 2015 edition of Rust " |
| "that exports a function named `try`. This keyword is reserved for a new " |
| "feature in the 2018 edition, so without raw identifiers, we would have no " |
| "way to name the function." |
| msgstr "" |
| "例如，假设有一个使用 Rust 2015 版编译的 crate `foo`，它导出了一个名为 `try` " |
| "的函数。这个关键字在 2018 版中被保留用于新特性，如果没有原始标识符，我们就无" |
| "法命名这个函数。" |
| |
| #: src/compatibility/raw_identifiers.md:24 |
| msgid "You'll get this error:" |
| msgstr "你会得到这个错误：" |
| |
| #: src/compatibility/raw_identifiers.md:34 |
| msgid "You can write this with a raw identifier:" |
| msgstr "你可以使用原始标识符这样写：" |
| |
| #: src/meta.md:3 |
| msgid "" |
| "Some topics aren't exactly relevant to how you program runs but provide you " |
| "tooling or infrastructure support which just makes things better for " |
| "everyone. These topics include:" |
| msgstr "" |
| "有些主题虽然与程序如何运行不直接相关，但它们提供了工具或基础设施支持，使得整" |
| "个开发生态变得更好。这些主题包括：" |
| |
| #: src/meta.md:7 |
| msgid "" |
| "[Documentation](meta/doc.md): Generate library documentation for users via " |
| "the included `rustdoc`." |
| msgstr "[文档](meta/doc.md)：使用内置的 `rustdoc` 为用户生成库文档。" |
| |
| #: src/meta.md:9 |
| msgid "" |
| "[Playground](meta/playground.md): Integrate the Rust Playground in your " |
| "documentation." |
| msgstr "[Playground](meta/playground.md)：在文档中集成 Rust Playground。" |
| |
| #: src/meta/doc.md:3 |
| msgid "" |
| "Use `cargo doc` to build documentation in `target/doc`, `cargo doc --open` " |
| "will automatically open it in your web browser." |
| msgstr "" |
| "使用 `cargo doc` 在 `target/doc` 目录下构建文档。运行 `cargo doc --open` 将自" |
| "动在浏览器中打开文档。" |
| |
| #: src/meta/doc.md:6 |
| msgid "" |
| "Use `cargo test` to run all tests (including documentation tests), and " |
| "`cargo test --doc` to only run documentation tests." |
| msgstr "" |
| "使用 `cargo test` 运行所有测试（包括文档测试）。如果只想运行文档测试，请使用 " |
| "`cargo test --doc`。" |
| |
| #: src/meta/doc.md:9 |
| msgid "" |
| "These commands will appropriately invoke `rustdoc` (and `rustc`) as required." |
| msgstr "这些命令会根据需要适当地调用 `rustdoc`（和 `rustc`）。" |
| |
| #: src/meta/doc.md:11 |
| msgid "Doc comments" |
| msgstr "文档注释" |
| |
| #: src/meta/doc.md:13 |
| msgid "" |
| "Doc comments are very useful for big projects that require documentation. " |
| "When running `rustdoc`, these are the comments that get compiled into " |
| "documentation. They are denoted by a `///`, and support [Markdown](https://" |
| "en.wikipedia.org/wiki/Markdown)." |
| msgstr "" |
| "文档注释对需要文档的大型项目非常有用。运行 `rustdoc` 时，这些注释会被编译成文" |
| "档。文档注释以 `///` 开头，并支持 [Markdown](https://zh.wikipedia.org/wiki/" |
| "Markdown) 语法。" |
| |
| #: src/meta/doc.md:18 |
| msgid "\"doc\"" |
| msgstr "\"doc\"" |
| |
| #: src/meta/doc.md:19 |
| msgid "/// A human being is represented here\n" |
| msgstr "/// 这里表示一个人类\n" |
| |
| #: src/meta/doc.md:22 |
| msgid "/// A person must have a name, no matter how much Juliet may hate it\n" |
| msgstr "/// 一个人必须有名字，不管朱丽叶有多么讨厌这一点\n" |
| |
| #: src/meta/doc.md:27 |
| msgid "" |
| "/// Creates a person with the given name.\n" |
| " ///\n" |
| " /// # Examples\n" |
| " ///\n" |
| " /// ```\n" |
| " /// // You can have rust code between fences inside the comments\n" |
| " /// // If you pass --test to `rustdoc`, it will even test it for you!\n" |
| " /// use doc::Person;\n" |
| " /// let person = Person::new(\"name\");\n" |
| " /// ```\n" |
| msgstr "" |
| "/// 创建一个具有给定名字的人。\n" |
| " ///\n" |
| " /// # 示例\n" |
| " ///\n" |
| " /// ```\n" |
| " /// // 你可以在注释中的代码块里编写 Rust 代码\n" |
| " /// // 如果向 `rustdoc` 传递 --test 参数，它甚至会为你测试这段代码！\n" |
| " /// use doc::Person;\n" |
| " /// let person = Person::new(\"name\");\n" |
| " /// ```\n" |
| |
| #: src/meta/doc.md:43 |
| msgid "" |
| "/// Gives a friendly hello!\n" |
| " ///\n" |
| " /// Says \"Hello, [name](Person::name)\" to the `Person` it is called " |
| "on.\n" |
| msgstr "" |
| "/// 给出友好的问候！\n" |
| " ///\n" |
| " /// 对调用此方法的 `Person` 说 \"Hello, [name](Person::name)\"。\n" |
| |
| #: src/meta/doc.md:47 |
| msgid "\"Hello, {}!\"" |
| msgstr "\"Hello, {}!\"" |
| |
| #: src/meta/doc.md:52 |
| msgid "\"John\"" |
| msgstr "\"John\"" |
| |
| #: src/meta/doc.md:58 |
| msgid "" |
| "To run the tests, first build the code as a library, then tell `rustdoc` " |
| "where to find the library so it can link it into each doctest program:" |
| msgstr "" |
| "要运行测试，首先将代码构建为库，然后告诉 `rustdoc` 库的位置，以便它可以将库链" |
| "接到每个文档测试程序中：" |
| |
| #: src/meta/doc.md:61 |
| msgid "" |
| "```shell\n" |
| "$ rustc doc.rs --crate-type lib\n" |
| "$ rustdoc --test --extern doc=\"libdoc.rlib\" doc.rs\n" |
| "```" |
| msgstr "" |
| "```shell\n" |
| "$ rustc doc.rs --crate-type lib\n" |
| "$ rustdoc --test --extern doc=\"libdoc.rlib\" doc.rs\n" |
| "```" |
| |
| #: src/meta/doc.md:66 |
| msgid "Doc attributes" |
| msgstr "文档属性" |
| |
| #: src/meta/doc.md:68 |
| msgid "" |
| "Below are a few examples of the most common `#[doc]` attributes used with " |
| "`rustdoc`." |
| msgstr "以下是几个与 `rustdoc` 配合使用的最常见 `#[doc]` 属性示例。" |
| |
| #: src/meta/doc.md:71 |
| msgid "`inline`" |
| msgstr "`inline`" |
| |
| #: src/meta/doc.md:73 |
| msgid "Used to inline docs, instead of linking out to separate page." |
| msgstr "用于内联文档，而非链接到单独的页面。" |
| |
| #: src/meta/doc.md:78 |
| msgid "/// bar docs\n" |
| msgstr "/// bar 的文档\n" |
| |
| #: src/meta/doc.md:81 |
| msgid "/// the docs for Bar\n" |
| msgstr "/// Bar 的文档\n" |
| |
| #: src/meta/doc.md:86 |
| msgid "`no_inline`" |
| msgstr "`no_inline`" |
| |
| #: src/meta/doc.md:88 |
| msgid "Used to prevent linking out to separate page or anywhere." |
| msgstr "用于防止链接到单独页面或其他任何地方。" |
| |
| #: src/meta/doc.md:91 |
| msgid "// Example from libcore/prelude\n" |
| msgstr "// libcore/prelude 中的示例\n" |
| |
| #: src/meta/doc.md:96 |
| msgid "`hidden`" |
| msgstr "`hidden`" |
| |
| #: src/meta/doc.md:98 |
| msgid "Using this tells `rustdoc` not to include this in documentation:" |
| msgstr "使用此属性告诉 `rustdoc` 不要在文档中包含此内容：" |
| |
| #: src/meta/doc.md:101 |
| msgid "// Example from the futures-rs library\n" |
| msgstr "// futures-rs 库中的示例\n" |
| |
| #: src/meta/doc.md:106 |
| msgid "" |
| "For documentation, `rustdoc` is widely used by the community. It's what is " |
| "used to generate the [std library docs](https://doc.rust-lang.org/std/)." |
| msgstr "" |
| "在文档生成方面，`rustdoc` 被社区广泛使用。它是用来生成 [标准库文档](https://" |
| "doc.rust-lang.org/std/) 的工具。" |
| |
| #: src/meta/doc.md:111 |
| msgid "" |
| "[The Rust Book: Making Useful Documentation Comments](https://doc.rust-" |
| "lang.org/book/ch14-02-publishing-to-crates-io.html#making-useful-" |
| "documentation-comments)" |
| msgstr "" |
| "[《Rust 程序设计语言》：编写有用的文档注释](https://doc.rust-lang.org/book/" |
| "ch14-02-publishing-to-crates-io.html#making-useful-documentation-comments)" |
| |
| #: src/meta/doc.md:112 |
| msgid "[The rustdoc Book](https://doc.rust-lang.org/rustdoc/index.html)" |
| msgstr "[rustdoc 手册](https://doc.rust-lang.org/rustdoc/index.html)" |
| |
| #: src/meta/doc.md:113 |
| msgid "" |
| "[The Reference: Doc comments](https://doc.rust-lang.org/stable/reference/" |
| "comments.html#doc-comments)" |
| msgstr "" |
| "[Rust 参考手册：文档注释](https://doc.rust-lang.org/stable/reference/" |
| "comments.html#doc-comments)" |
| |
| #: src/meta/doc.md:114 |
| msgid "" |
| "[RFC 1574: API Documentation Conventions](https://rust-lang.github.io/rfcs/" |
| "1574-more-api-documentation-conventions.html#appendix-a-full-conventions-" |
| "text)" |
| msgstr "" |
| "[RFC 1574：API 文档约定](https://rust-lang.github.io/rfcs/1574-more-api-" |
| "documentation-conventions.html#appendix-a-full-conventions-text)" |
| |
| #: src/meta/doc.md:115 |
| msgid "" |
| "[RFC 1946: Relative links to other items from doc comments (intra-rustdoc " |
| "links)](https://rust-lang.github.io/rfcs/1946-intra-rustdoc-links.html)" |
| msgstr "" |
| "[RFC 1946：文档注释中的相对链接（rustdoc 内部链接）](https://rust-" |
| "lang.github.io/rfcs/1946-intra-rustdoc-links.html)" |
| |
| #: src/meta/doc.md:116 |
| msgid "" |
| "[Is there any documentation style guide for comments? (reddit)](https://" |
| "www.reddit.com/r/rust/comments/ahb50s/" |
| "is_there_any_documentation_style_guide_for/)" |
| msgstr "" |
| "[有关注释的文档风格指南？（Reddit 讨论）](https://www.reddit.com/r/rust/" |
| "comments/ahb50s/is_there_any_documentation_style_guide_for/)" |
| |
| #: src/meta/playground.md:3 |
| msgid "" |
| "The [Rust Playground](https://play.rust-lang.org/) is a way to experiment " |
| "with Rust code through a web interface." |
| msgstr "" |
| "[Rust Playground](https://play.rust-lang.org/) 是一个通过网页界面体验 Rust 代" |
| "码的平台。" |
| |
| #: src/meta/playground.md:6 |
| msgid "Using it with `mdbook`" |
| msgstr "在 `mdbook` 中使用 Playground" |
| |
| #: src/meta/playground.md:8 |
| msgid "" |
| "In [`mdbook`](https://github.com/rust-lang/mdBook), you can make code " |
| "examples playable and editable." |
| msgstr "" |
| "在 [`mdbook`](https://github.com/rust-lang/mdBook) 中，你可以让代码示例变得可" |
| "运行和可编辑。" |
| |
| #: src/meta/playground.md:16 |
| msgid "" |
| "This allows the reader to both run your code sample, but also modify and " |
| "tweak it. The key here is the adding of the word `editable` to your " |
| "codefence block separated by a comma." |
| msgstr "" |
| "这不仅允许读者运行你的代码示例，还能修改和调整它。关键是在代码块标记中添加 " |
| "`editable` 关键字，用逗号分隔。" |
| |
| #: src/meta/playground.md:26 |
| msgid "" |
| "Additionally, you can add `ignore` if you want `mdbook` to skip your code " |
| "when it builds and tests." |
| msgstr "" |
| "此外，如果你希望 `mdbook` 在构建和测试时跳过某段代码，可以添加 `ignore` 关键" |
| "字。" |
| |
| #: src/meta/playground.md:35 |
| msgid "Using it with docs" |
| msgstr "在文档中使用 Playground" |
| |
| #: src/meta/playground.md:37 |
| msgid "" |
| "You may have noticed in some of the [official Rust docs](https://doc.rust-" |
| "lang.org/core/) a button that says \"Run\", which opens the code sample up " |
| "in a new tab in Rust Playground. This feature is enabled if you use the " |
| "`#[doc]` attribute called [`html_playground_url`](https://doc.rust-lang.org/" |
| "rustdoc/write-documentation/the-doc-attribute.html#html_playground_url)." |
| msgstr "" |
| "你可能注意到在一些[官方 Rust 文档](https://doc.rust-lang.org/core/)中有一个" |
| "\"运行\"按钮，点击后会在 Rust Playground 的新标签页中打开代码示例。要启用此功" |
| "能，需要使用 `#[doc]` 属性中的 [`html_playground_url`](https://doc.rust-" |
| "lang.org/rustdoc/write-documentation/the-doc-" |
| "attribute.html#html_playground_url)。" |
| |
| #: src/meta/playground.md:42 |
| msgid "" |
| "````text\n" |
| "#![doc(html_playground_url = \"https://play.rust-lang.org/\")]\n" |
| "//! ```\n" |
| "//! println!(\"Hello World\");\n" |
| "//! ```\n" |
| "````" |
| msgstr "" |
| "````text\n" |
| "#![doc(html_playground_url = \"https://play.rust-lang.org/\")]\n" |
| "//! ```\n" |
| "//! println!(\"Hello World\");\n" |
| "//! ```\n" |
| "````" |
| |
| #: src/meta/playground.md:51 |
| msgid "[The Rust Playground](https://play.rust-lang.org/)" |
| msgstr "[Rust Playground](https://play.rust-lang.org/)" |
| |
| #: src/meta/playground.md:52 |
| msgid "" |
| "[The Rust Playground On Github](https://github.com/integer32llc/rust-" |
| "playground/)" |
| msgstr "" |
| "[GitHub 上的 Rust Playground](https://github.com/integer32llc/rust-" |
| "playground/)" |
| |
| #: src/meta/playground.md:53 |
| msgid "" |
| "[The rustdoc Book](https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html)" |
| msgstr "[rustdoc 手册](https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html)" |
| |
| #~ msgid "" |
| #~ "The compiler forbids use of uninitialized variables, as this would lead " |
| #~ "to undefined behavior." |
| #~ msgstr "编译器禁止使用未初始化的变量，因为这会导致未定义行为。" |
