diff --git a/po/da.po b/po/da.po index 58fdaa4d7fdc..2518438a25d4 100644 --- a/po/da.po +++ b/po/da.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: Comprehensive Rust 🦀\n" -"POT-Creation-Date: 2023-09-27T15:38:22+02:00\n" +"POT-Creation-Date: 2023-11-30T15:58:18+01:00\n" "PO-Revision-Date: \n" "Last-Translator: \n" "Language-Team: \n" @@ -11,39 +11,39 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" -#: src/SUMMARY.md:4 src/index.md:1 +#: src/SUMMARY.md:2 src/index.md:1 msgid "Welcome to Comprehensive Rust 🦀" msgstr "Velkommen til Comprehensive Rust 🦀" -#: src/SUMMARY.md:5 src/running-the-course.md:1 +#: src/SUMMARY.md:3 src/running-the-course.md:1 msgid "Running the Course" msgstr "Afvikling af kurset" -#: src/SUMMARY.md:6 src/running-the-course/course-structure.md:1 +#: src/SUMMARY.md:4 src/running-the-course/course-structure.md:1 msgid "Course Structure" msgstr "Kursets struktur" -#: src/SUMMARY.md:7 src/running-the-course/keyboard-shortcuts.md:1 +#: src/SUMMARY.md:5 src/running-the-course/keyboard-shortcuts.md:1 msgid "Keyboard Shortcuts" msgstr "Genvejstaster" -#: src/SUMMARY.md:8 src/running-the-course/translations.md:1 +#: src/SUMMARY.md:6 src/running-the-course/translations.md:1 msgid "Translations" msgstr "Oversættelser" -#: src/SUMMARY.md:9 src/cargo.md:1 +#: src/SUMMARY.md:7 src/cargo.md:1 msgid "Using Cargo" msgstr "Brug af Cargo" -#: src/SUMMARY.md:10 +#: src/SUMMARY.md:8 msgid "Rust Ecosystem" msgstr "Rust's økosystem" -#: src/SUMMARY.md:11 +#: src/SUMMARY.md:9 msgid "Code Samples" msgstr "Kodeeksempler" -#: src/SUMMARY.md:12 +#: src/SUMMARY.md:10 msgid "Running Cargo Locally" msgstr "" @@ -51,979 +51,1153 @@ msgstr "" msgid "Day 1: Morning" msgstr "Dag 1: Formiddag" -#: src/SUMMARY.md:19 src/SUMMARY.md:79 src/SUMMARY.md:134 src/SUMMARY.md:192 -#: src/SUMMARY.md:218 src/SUMMARY.md:268 +#: src/SUMMARY.md:17 src/SUMMARY.md:43 src/SUMMARY.md:69 src/SUMMARY.md:92 +#: src/SUMMARY.md:118 src/SUMMARY.md:137 src/SUMMARY.md:157 src/SUMMARY.md:182 +#: src/SUMMARY.md:205 src/SUMMARY.md:244 src/SUMMARY.md:279 src/SUMMARY.md:331 msgid "Welcome" msgstr "Velkommen" -#: src/SUMMARY.md:20 src/welcome-day-1/what-is-rust.md:1 +#: src/SUMMARY.md:18 src/SUMMARY.md:20 src/hello-world.md:1 +#: src/hello-world/hello-world.md:1 +#, fuzzy +msgid "Hello, World" +msgstr "Hej verden!" + +#: src/SUMMARY.md:19 src/hello-world/what-is-rust.md:1 msgid "What is Rust?" msgstr "Hvad er Rust?" -#: src/SUMMARY.md:21 src/hello-world.md:1 -msgid "Hello World!" -msgstr "Hej verden!" +#: src/SUMMARY.md:21 src/hello-world/benefits.md:1 +msgid "Benefits of Rust" +msgstr "" -#: src/SUMMARY.md:22 src/hello-world/small-example.md:1 -msgid "Small Example" -msgstr "Et little eksempel" +#: src/SUMMARY.md:22 src/hello-world/playground.md:1 +msgid "Playground" +msgstr "" -#: src/SUMMARY.md:23 src/why-rust.md:1 -msgid "Why Rust?" -msgstr "Hvorfor bruge Rust?" +#: src/SUMMARY.md:23 src/types-and-values.md:1 +msgid "Types and Values" +msgstr "" -#: src/SUMMARY.md:24 src/why-rust/compile-time.md:1 -msgid "Compile Time Guarantees" -msgstr "Garantier før programudføring" +#: src/SUMMARY.md:24 src/types-and-values/variables.md:1 +msgid "Variables" +msgstr "Variabler" -#: src/SUMMARY.md:25 src/why-rust/runtime.md:1 -msgid "Runtime Guarantees" -msgstr "Garantier under programudføring" +#: src/SUMMARY.md:25 src/types-and-values/values.md:1 +msgid "Values" +msgstr "" -#: src/SUMMARY.md:26 src/why-rust/modern.md:1 -msgid "Modern Features" -msgstr "Moderne faciliteter" +#: src/SUMMARY.md:26 src/types-and-values/arithmetic.md:1 +msgid "Arithmetic" +msgstr "" -#: src/SUMMARY.md:27 src/basic-syntax.md:1 -msgid "Basic Syntax" -msgstr "Grundlæggende syntaks" +#: src/SUMMARY.md:27 src/types-and-values/strings.md:1 +msgid "Strings" +msgstr "" -#: src/SUMMARY.md:28 src/basic-syntax/scalar-types.md:1 -msgid "Scalar Types" -msgstr "Skalartyper" +#: src/SUMMARY.md:28 src/types-and-values/inference.md:1 +msgid "Type Inference" +msgstr "Typeudledning" -#: src/SUMMARY.md:29 src/basic-syntax/compound-types.md:1 -msgid "Compound Types" -msgstr "Sammensatte typer" +#: src/SUMMARY.md:29 src/types-and-values/exercise.md:1 +msgid "Exercise: Fibonacci" +msgstr "" + +#: src/SUMMARY.md:30 src/SUMMARY.md:39 src/SUMMARY.md:50 src/SUMMARY.md:55 +#: src/SUMMARY.md:63 src/SUMMARY.md:74 src/SUMMARY.md:81 src/SUMMARY.md:88 +#: src/SUMMARY.md:102 src/SUMMARY.md:112 src/SUMMARY.md:128 src/SUMMARY.md:133 +#: src/SUMMARY.md:143 src/SUMMARY.md:151 src/SUMMARY.md:163 src/SUMMARY.md:170 +#: src/SUMMARY.md:178 src/SUMMARY.md:190 src/SUMMARY.md:199 +#: src/types-and-values/solution.md:1 src/control-flow-basics/solution.md:1 +#: src/tuples-and-arrays/solution.md:1 src/references/solution.md:1 +#: src/user-defined-types/solution.md:1 src/pattern-matching/solution.md:1 +#: src/methods-and-traits/solution.md:1 src/generics/solution.md:1 +#: src/std-types/solution.md:1 src/std-traits/solution.md:1 +#: src/memory-management/solution.md:1 src/smart-pointers/solution.md:1 +#: src/borrowing/solution.md:1 src/slices-and-lifetimes/solution.md:1 +#: src/iterators/solution.md:1 src/modules/solution.md:1 +#: src/testing/solution.md:1 src/error-handling/solution.md:1 +#: src/unsafe-rust/solution.md:1 +#, fuzzy +msgid "Solution" +msgstr "Løsninger" -#: src/SUMMARY.md:30 src/basic-syntax/references.md:1 -msgid "References" -msgstr "Referencer" +#: src/SUMMARY.md:31 src/control-flow-basics.md:1 +#, fuzzy +msgid "Control Flow Basics" +msgstr "Forgreninger" -#: src/SUMMARY.md:31 src/basic-syntax/references-dangling.md:1 -msgid "Dangling References" -msgstr "Hængende referencer" +#: src/SUMMARY.md:32 src/control-flow-basics/conditionals.md:1 +msgid "Conditionals" +msgstr "" -#: src/SUMMARY.md:32 src/basic-syntax/slices.md:1 -msgid "Slices" -msgstr "Arraysegmenter" +#: src/SUMMARY.md:33 src/control-flow-basics/loops.md:1 +#, fuzzy +msgid "Loops" +msgstr "`for`\\-løkker" + +#: src/SUMMARY.md:34 src/control-flow-basics/break-continue.md:1 +msgid "`break` and `continue`" +msgstr "" -#: src/SUMMARY.md:33 -msgid "String vs str" -msgstr "String og str" +#: src/SUMMARY.md:35 src/control-flow-basics/blocks-and-scopes.md:1 +msgid "Blocks and Scopes" +msgstr "" -#: src/SUMMARY.md:34 src/basic-syntax/functions.md:1 +#: src/SUMMARY.md:36 src/control-flow-basics/functions.md:1 msgid "Functions" msgstr "Funktioner" -#: src/SUMMARY.md:35 src/basic-syntax/rustdoc.md:1 -msgid "Rustdoc" +#: src/SUMMARY.md:37 src/control-flow-basics/macros.md:1 +msgid "Macros" msgstr "" -#: src/SUMMARY.md:36 src/SUMMARY.md:102 src/basic-syntax/methods.md:1 -#: src/methods.md:1 -msgid "Methods" -msgstr "Metoder" - -#: src/SUMMARY.md:37 -msgid "Overloading" -msgstr "Funktionsoverlæsning" - -#: src/SUMMARY.md:38 src/SUMMARY.md:71 src/SUMMARY.md:105 src/SUMMARY.md:125 -#: src/SUMMARY.md:154 src/SUMMARY.md:184 src/SUMMARY.md:211 src/SUMMARY.md:232 -#: src/SUMMARY.md:260 src/SUMMARY.md:282 src/SUMMARY.md:303 -#: src/exercises/android/morning.md:1 src/exercises/bare-metal/morning.md:1 -#: src/exercises/bare-metal/afternoon.md:1 -#: src/exercises/concurrency/morning.md:1 -#: src/exercises/concurrency/afternoon.md:1 -msgid "Exercises" -msgstr "Øvelser" - -#: src/SUMMARY.md:39 src/exercises/day-1/implicit-conversions.md:1 -msgid "Implicit Conversions" -msgstr "Implicitte konverteringer" - -#: src/SUMMARY.md:40 -msgid "Arrays and for Loops" -msgstr "Arrays og for-løkker" +#: src/SUMMARY.md:38 +msgid "Exercise: Collatz conjecture" +msgstr "" -#: src/SUMMARY.md:42 +#: src/SUMMARY.md:41 msgid "Day 1: Afternoon" msgstr "Dag 1: Eftermiddag" -#: src/SUMMARY.md:44 src/SUMMARY.md:295 src/control-flow.md:1 -msgid "Control Flow" -msgstr "Forgreninger" - -#: src/SUMMARY.md:45 src/control-flow/blocks.md:1 -msgid "Blocks" -msgstr "Blokke" - -#: src/SUMMARY.md:46 -msgid "if expressions" -msgstr "if udtryk" - -#: src/SUMMARY.md:47 -msgid "for expressions" -msgstr "for udtryk" - -#: src/SUMMARY.md:48 -msgid "while expressions" -msgstr "while udtryk" - -#: src/SUMMARY.md:49 -msgid "break & continue" -msgstr "break og continue" - -#: src/SUMMARY.md:50 -msgid "loop expressions" -msgstr "loop udtryk" - -#: src/SUMMARY.md:52 src/basic-syntax/variables.md:1 -msgid "Variables" -msgstr "Variabler" - -#: src/SUMMARY.md:53 src/basic-syntax/type-inference.md:1 -msgid "Type Inference" -msgstr "Typeudledning" - -#: src/SUMMARY.md:54 -msgid "static & const" -msgstr "static & const" - -#: src/SUMMARY.md:55 src/basic-syntax/scopes-shadowing.md:1 -msgid "Scopes and Shadowing" -msgstr "Virkefelt og overskyggede variabler" - -#: src/SUMMARY.md:56 src/enums.md:1 -msgid "Enums" -msgstr "Enumerationer" - -#: src/SUMMARY.md:57 src/enums/variant-payloads.md:1 -msgid "Variant Payloads" -msgstr "Nyttelast i varianter" - -#: src/SUMMARY.md:58 src/enums/sizes.md:1 -msgid "Enum Sizes" -msgstr "Størrelse af enumerationer" - -#: src/SUMMARY.md:60 src/control-flow/novel.md:1 -msgid "Novel Control Flow" -msgstr "Usædvanlige forgreninger" - -#: src/SUMMARY.md:61 -msgid "if let expressions" -msgstr "if let udtryk" - -#: src/SUMMARY.md:62 -msgid "while let expressions" -msgstr "while let udtryk" +#: src/SUMMARY.md:44 src/SUMMARY.md:45 src/tuples-and-arrays.md:1 +#: src/tuples-and-arrays/tuples-and-arrays.md:1 +msgid "Tuples and Arrays" +msgstr "" -#: src/SUMMARY.md:63 -msgid "match expressions" -msgstr "match udtryk" +#: src/SUMMARY.md:46 src/tuples-and-arrays/iteration.md:1 +msgid "Array Iteration" +msgstr "" -#: src/SUMMARY.md:65 src/SUMMARY.md:73 src/pattern-matching.md:1 +#: src/SUMMARY.md:47 src/SUMMARY.md:70 src/tuples-and-arrays/match.md:1 +#: src/pattern-matching.md:1 msgid "Pattern Matching" msgstr "Mønstergenkendelse" -#: src/SUMMARY.md:66 src/pattern-matching/destructuring-enums.md:1 -msgid "Destructuring Enums" +#: src/SUMMARY.md:48 src/SUMMARY.md:71 src/tuples-and-arrays/destructuring.md:1 +#: src/pattern-matching/destructuring.md:1 +#, fuzzy +msgid "Destructuring" msgstr "Dekonstruktion af enumerationer" -#: src/SUMMARY.md:67 src/pattern-matching/destructuring-structs.md:1 -msgid "Destructuring Structs" -msgstr "Dekonstruktion af strukturer" - -#: src/SUMMARY.md:68 src/pattern-matching/destructuring-arrays.md:1 -msgid "Destructuring Arrays" -msgstr "Dekonstruktion af arrays" - -#: src/SUMMARY.md:69 src/pattern-matching/match-guards.md:1 -msgid "Match Guards" +#: src/SUMMARY.md:49 src/tuples-and-arrays/exercise.md:1 +msgid "Exercise: Nested Arrays" msgstr "" -#: src/SUMMARY.md:72 src/exercises/day-1/luhn.md:1 -#: src/exercises/day-1/solutions-afternoon.md:3 -msgid "Luhn Algorithm" -msgstr "Luhn-algorithmen" - -#: src/SUMMARY.md:75 -msgid "Day 2: Morning" -msgstr "Dag 2: Formiddag" +#: src/SUMMARY.md:51 src/references.md:1 +msgid "References" +msgstr "Referencer" -#: src/SUMMARY.md:81 src/memory-management.md:1 -msgid "Memory Management" -msgstr "Håndtering af hukommelse" +#: src/SUMMARY.md:52 src/references/shared.md:1 +#, fuzzy +msgid "Shared References" +msgstr "Referencer" -#: src/SUMMARY.md:82 -msgid "Stack vs Heap" -msgstr "Stak og heap" +#: src/SUMMARY.md:53 src/references/exclusive.md:1 +#, fuzzy +msgid "Exclusive References" +msgstr "Hængende referencer" -#: src/SUMMARY.md:83 -msgid "Stack Memory" -msgstr "Stakhukommelse" +#: src/SUMMARY.md:54 src/references/exercise.md:1 +msgid "Exercise: Geometry" +msgstr "" -#: src/SUMMARY.md:84 src/memory-management/manual.md:1 -msgid "Manual Memory Management" -msgstr "Manuel hukommelseshåndtering" +#: src/SUMMARY.md:56 src/user-defined-types.md:1 +msgid "User-Defined Types" +msgstr "" -#: src/SUMMARY.md:85 src/memory-management/scope-based.md:1 -msgid "Scope-Based Memory Management" -msgstr "Hukommelseshåndtering baseret på virkefelt" +#: src/SUMMARY.md:57 src/user-defined-types/named-structs.md:1 +#, fuzzy +msgid "Named Structs" +msgstr "Strukturer" -#: src/SUMMARY.md:86 -msgid "Garbage Collection" -msgstr "Automatisk hukommelseshåndtering" +#: src/SUMMARY.md:58 src/user-defined-types/tuple-structs.md:4 +msgid "Tuple Structs" +msgstr "Tuple-strukturer" -#: src/SUMMARY.md:87 -msgid "Rust Memory Management" -msgstr "Hukommelseshåndtering i Rust" +#: src/SUMMARY.md:59 src/user-defined-types/enums.md:1 +#: src/pattern-matching/destructuring.md:23 +#: src/pattern-matching/destructuring.md:66 +msgid "Enums" +msgstr "Enumerationer" -#: src/SUMMARY.md:88 src/ownership.md:1 -msgid "Ownership" -msgstr "Ejerskab" +#: src/SUMMARY.md:60 src/user-defined-types/static-and-const.md:1 +#, fuzzy +msgid "Static and Const" +msgstr "static & const" -#: src/SUMMARY.md:89 src/ownership/move-semantics.md:1 -msgid "Move Semantics" -msgstr "Overførselssemantik" +#: src/SUMMARY.md:61 src/user-defined-types/aliases.md:1 +msgid "Type Aliases" +msgstr "" -#: src/SUMMARY.md:90 src/ownership/moved-strings-rust.md:1 -msgid "Moved Strings in Rust" -msgstr "Overførte strenge i Rust" +#: src/SUMMARY.md:62 src/user-defined-types/exercise.md:1 +msgid "Exercise: Elevator Events" +msgstr "" -#: src/SUMMARY.md:91 -msgid "Double Frees in Modern C++" -msgstr "Dobbeltfrigivelser i moderne C++" +#: src/SUMMARY.md:67 +msgid "Day 2: Morning" +msgstr "Dag 2: Formiddag" -#: src/SUMMARY.md:92 src/ownership/moves-function-calls.md:1 -msgid "Moves in Function Calls" -msgstr "Overførsel af ejerskab i funktionskald" +#: src/SUMMARY.md:72 src/pattern-matching/let-control-flow.md:1 +#, fuzzy +msgid "Let Control Flow" +msgstr "Forgreninger" -#: src/SUMMARY.md:93 src/ownership/copy-clone.md:1 -msgid "Copying and Cloning" -msgstr "Kopiering og kloning" +#: src/SUMMARY.md:73 src/pattern-matching/exercise.md:1 +msgid "Exercise: Expression Evaluation" +msgstr "" -#: src/SUMMARY.md:94 src/ownership/borrowing.md:1 -msgid "Borrowing" -msgstr "Lån af variabler" +#: src/SUMMARY.md:75 src/methods-and-traits.md:1 +#, fuzzy +msgid "Methods and Traits" +msgstr "Asynkrone egenskaber (eng. Traits)" -#: src/SUMMARY.md:95 src/ownership/shared-unique-borrows.md:1 -msgid "Shared and Unique Borrows" -msgstr "Delte og unikke lån" +#: src/SUMMARY.md:76 src/methods-and-traits/methods.md:1 +msgid "Methods" +msgstr "Metoder" -#: src/SUMMARY.md:96 src/ownership/lifetimes.md:1 -msgid "Lifetimes" -msgstr "Livstider" +#: src/SUMMARY.md:77 src/methods-and-traits/traits.md:1 +msgid "Traits" +msgstr "" -#: src/SUMMARY.md:97 src/ownership/lifetimes-function-calls.md:1 -msgid "Lifetimes in Function Calls" -msgstr "Livstider i funktionskald" +#: src/SUMMARY.md:78 src/methods-and-traits/deriving.md:1 +msgid "Deriving" +msgstr "" -#: src/SUMMARY.md:98 src/ownership/lifetimes-data-structures.md:1 -msgid "Lifetimes in Data Structures" -msgstr "Livstider i datastrukturer" +#: src/SUMMARY.md:79 src/methods-and-traits/trait-objects.md:1 +msgid "Trait Objects" +msgstr "" -#: src/SUMMARY.md:99 src/structs.md:1 -msgid "Structs" -msgstr "Strukturer" +#: src/SUMMARY.md:80 src/methods-and-traits/exercise.md:1 +msgid "Exercise: GUI Library" +msgstr "" -#: src/SUMMARY.md:100 src/structs/tuple-structs.md:1 -msgid "Tuple Structs" -msgstr "Tuple-strukturer" +#: src/SUMMARY.md:82 src/generics.md:1 +msgid "Generics" +msgstr "" -#: src/SUMMARY.md:101 src/structs/field-shorthand.md:1 -msgid "Field Shorthand Syntax" -msgstr "Forenklet strukturinitialisering" +#: src/SUMMARY.md:83 src/generics/generic-functions.md:1 +#, fuzzy +msgid "Generic Functions" +msgstr "Funktioner" -#: src/SUMMARY.md:103 src/methods/receiver.md:1 -msgid "Method Receiver" -msgstr "Modtager af funktionskald" +#: src/SUMMARY.md:84 +msgid "Generic Data types" +msgstr "" -#: src/SUMMARY.md:104 src/SUMMARY.md:166 src/SUMMARY.md:281 -#: src/methods/example.md:1 src/concurrency/shared_state/example.md:1 -msgid "Example" -msgstr "Eksempel" +#: src/SUMMARY.md:85 src/generics/trait-bounds.md:1 +msgid "Trait Bounds" +msgstr "" -#: src/SUMMARY.md:106 src/exercises/day-2/book-library.md:1 -msgid "Storing Books" -msgstr "Lagring af bøger" +#: src/SUMMARY.md:86 +#, fuzzy +msgid "Impl Trait" +msgstr "`impl Trait`" -#: src/SUMMARY.md:107 src/exercises/day-2/health-statistics.md:1 -#: src/exercises/day-2/solutions-morning.md:151 -msgid "Health Statistics" +#: src/SUMMARY.md:87 src/generics/exercise.md:1 +msgid "Exercise: Generic `min`" msgstr "" -#: src/SUMMARY.md:109 +#: src/SUMMARY.md:90 msgid "Day 2: Afternoon" msgstr "Dag 2: Eftermiddag" -#: src/SUMMARY.md:111 src/std.md:1 +#: src/SUMMARY.md:93 src/std-types.md:1 +msgid "Standard Library Types" +msgstr "" + +#: src/SUMMARY.md:94 src/std-types/std.md:1 msgid "Standard Library" msgstr "" -#: src/SUMMARY.md:112 -msgid "Option and Result" +#: src/SUMMARY.md:95 src/std-types/docs.md:1 +msgid "Language Docs" +msgstr "" + +#: src/SUMMARY.md:96 src/std-types/option.md:1 +#, fuzzy +msgid "Option" +msgstr "Undtagelser" + +#: src/SUMMARY.md:97 src/std-types/result.md:1 +msgid "Result" msgstr "" -#: src/SUMMARY.md:113 src/std/string.md:1 +#: src/SUMMARY.md:98 src/std-types/string.md:1 msgid "String" msgstr "" -#: src/SUMMARY.md:114 +#: src/SUMMARY.md:99 msgid "Vec" msgstr "" -#: src/SUMMARY.md:115 +#: src/SUMMARY.md:100 msgid "HashMap" msgstr "" -#: src/SUMMARY.md:116 -msgid "Box" -msgstr "" +#: src/SUMMARY.md:101 src/std-types/exercise.md:1 +#, fuzzy +msgid "Exercise: Counter" +msgstr "Øvelser" -#: src/SUMMARY.md:117 -msgid "Recursive Data Types" +#: src/SUMMARY.md:103 src/std-traits.md:1 +msgid "Standard Library Traits" msgstr "" -#: src/SUMMARY.md:118 src/std/box-niche.md:1 -msgid "Niche Optimization" -msgstr "" +#: src/SUMMARY.md:104 src/std-traits/comparisons.md:1 src/async.md:17 +msgid "Comparisons" +msgstr "Sammenligninger" -#: src/SUMMARY.md:119 -msgid "Rc" -msgstr "" +#: src/SUMMARY.md:105 src/std-traits/operators.md:1 +#, fuzzy +msgid "Operators" +msgstr "Iteratorer" -#: src/SUMMARY.md:120 -msgid "Cell/RefCell" +#: src/SUMMARY.md:106 +msgid "From and Into" msgstr "" -#: src/SUMMARY.md:121 src/modules.md:1 -msgid "Modules" +#: src/SUMMARY.md:107 src/std-traits/casting.md:1 +msgid "Casting" msgstr "" -#: src/SUMMARY.md:122 src/modules/visibility.md:1 -msgid "Visibility" +#: src/SUMMARY.md:108 +msgid "Read and Write" msgstr "" -#: src/SUMMARY.md:123 src/modules/paths.md:1 -msgid "Paths" +#: src/SUMMARY.md:109 +msgid "`Default`, struct update syntax" msgstr "" -#: src/SUMMARY.md:124 src/modules/filesystem.md:1 -msgid "Filesystem Hierarchy" +#: src/SUMMARY.md:110 src/std-traits/closures.md:1 +msgid "Closures" msgstr "" -#: src/SUMMARY.md:126 src/exercises/day-2/iterators-and-ownership.md:1 -msgid "Iterators and Ownership" -msgstr "Iteratorer og ejerskab" - -#: src/SUMMARY.md:127 src/exercises/day-2/strings-iterators.md:1 -#: src/exercises/day-2/solutions-afternoon.md:3 -msgid "Strings and Iterators" -msgstr "Strenge og iteratorer" +#: src/SUMMARY.md:111 src/std-traits/exercise.md:1 +#, fuzzy +msgid "Exercise: ROT13" +msgstr "Øvelser" -#: src/SUMMARY.md:130 +#: src/SUMMARY.md:116 msgid "Day 3: Morning" msgstr "" -#: src/SUMMARY.md:135 src/generics.md:1 -msgid "Generics" -msgstr "" +#: src/SUMMARY.md:119 src/memory-management.md:1 +msgid "Memory Management" +msgstr "Håndtering af hukommelse" -#: src/SUMMARY.md:136 src/generics/data-types.md:1 -msgid "Generic Data Types" +#: src/SUMMARY.md:120 src/memory-management/review.md:1 +msgid "Review of Program Memory" msgstr "" -#: src/SUMMARY.md:137 src/generics/methods.md:1 -msgid "Generic Methods" -msgstr "" +#: src/SUMMARY.md:121 src/memory-management/approaches.md:1 +#, fuzzy +msgid "Approaches to Memory Management" +msgstr "Hukommelseshåndtering i Rust" -#: src/SUMMARY.md:138 src/generics/monomorphization.md:1 -msgid "Monomorphization" +#: src/SUMMARY.md:122 src/memory-management/ownership.md:1 +msgid "Ownership" +msgstr "Ejerskab" + +#: src/SUMMARY.md:123 +#, fuzzy +msgid "Move semantics" +msgstr "Overførselssemantik" + +#: src/SUMMARY.md:124 src/memory-management/clone.md:1 +msgid "Clone" msgstr "" -#: src/SUMMARY.md:139 src/traits.md:1 -msgid "Traits" +#: src/SUMMARY.md:125 src/memory-management/copy-types.md:4 +#, fuzzy +msgid "Copy Types" +msgstr "Sammensatte typer" + +#: src/SUMMARY.md:126 +msgid "Drop" msgstr "" -#: src/SUMMARY.md:140 src/traits/trait-objects.md:1 -msgid "Trait Objects" +#: src/SUMMARY.md:127 src/memory-management/exercise.md:1 +msgid "Exercise: Builder Type" msgstr "" -#: src/SUMMARY.md:141 src/traits/deriving-traits.md:1 -msgid "Deriving Traits" +#: src/SUMMARY.md:129 src/smart-pointers.md:1 +msgid "Smart Pointers" msgstr "" -#: src/SUMMARY.md:142 src/traits/default-methods.md:1 -msgid "Default Methods" +#: src/SUMMARY.md:130 +msgid "\\[Box" msgstr "" -#: src/SUMMARY.md:143 src/traits/trait-bounds.md:1 -msgid "Trait Bounds" +#: src/SUMMARY.md:130 +msgid "\\](smart-pointers/box.md)" msgstr "" -#: src/SUMMARY.md:144 -msgid "impl Trait" +#: src/SUMMARY.md:131 +msgid "Rc" msgstr "" -#: src/SUMMARY.md:145 src/traits/important-traits.md:1 -msgid "Important Traits" +#: src/SUMMARY.md:132 src/smart-pointers/exercise.md:1 +msgid "Exercise: Binary Tree" msgstr "" -#: src/SUMMARY.md:146 -msgid "Iterator" +#: src/SUMMARY.md:135 +msgid "Day 3: Afternoon" msgstr "" -#: src/SUMMARY.md:147 src/traits/from-iterator.md:1 -msgid "FromIterator" +#: src/SUMMARY.md:138 src/borrowing.md:1 +msgid "Borrowing" +msgstr "Lån af variabler" + +#: src/SUMMARY.md:139 src/borrowing/shared.md:1 +#, fuzzy +msgid "Borrowing a Value" +msgstr "Lån af variabler" + +#: src/SUMMARY.md:140 src/borrowing/borrowck.md:1 +#, fuzzy +msgid "Borrow Checking" +msgstr "Lån af variabler" + +#: src/SUMMARY.md:141 src/borrowing/interior-mutability.md:4 +msgid "Interior Mutability" msgstr "" +#: src/SUMMARY.md:142 src/borrowing/exercise.md:1 +#, fuzzy +msgid "Exercise: Health Statistics" +msgstr "([tilbage til øvelsen](health-statistics.md))" + +#: src/SUMMARY.md:144 src/slices-and-lifetimes.md:1 +#, fuzzy +msgid "Slices and Lifetimes" +msgstr "Livstider" + +#: src/SUMMARY.md:145 +#, fuzzy +msgid "Slices: `&[T]`" +msgstr "Arraysegmenter" + +#: src/SUMMARY.md:146 src/slices-and-lifetimes/str.md:4 +#, fuzzy +msgid "String References" +msgstr "Hængende referencer" + +#: src/SUMMARY.md:147 +#, fuzzy +msgid "Lifetime Annotations" +msgstr "Livstider i funktionskald" + #: src/SUMMARY.md:148 -msgid "From and Into" -msgstr "" +#, fuzzy +msgid "Lifetime Elision" +msgstr "Livstider" #: src/SUMMARY.md:149 -msgid "Read and Write" -msgstr "" +#, fuzzy +msgid "Struct Lifetimes" +msgstr "Livstider" -#: src/SUMMARY.md:150 -msgid "Drop" +#: src/SUMMARY.md:150 src/slices-and-lifetimes/exercise.md:1 +msgid "Exercise: Protobuf Parsing" msgstr "" -#: src/SUMMARY.md:151 -msgid "Default" -msgstr "" +#: src/SUMMARY.md:155 +#, fuzzy +msgid "Day 4: Morning" +msgstr "Dag 1: Formiddag" -#: src/SUMMARY.md:152 -msgid "Operators: Add, Mul, ..." -msgstr "" +#: src/SUMMARY.md:158 src/SUMMARY.md:159 src/iterators.md:1 +#: src/iterators/iterators.md:4 +msgid "Iterators" +msgstr "Iteratorer" -#: src/SUMMARY.md:153 -msgid "Closures: Fn, FnMut, FnOnce" -msgstr "" +#: src/SUMMARY.md:160 +#, fuzzy +msgid "IntoIterator" +msgstr "`IntoIterator`" -#: src/SUMMARY.md:155 src/exercises/day-3/simple-gui.md:1 -#: src/exercises/day-3/solutions-morning.md:3 -msgid "A Simple GUI Library" +#: src/SUMMARY.md:161 src/iterators/fromiterator.md:1 +msgid "FromIterator" msgstr "" -#: src/SUMMARY.md:156 src/exercises/day-3/solutions-morning.md:145 -msgid "Points and Polygons" -msgstr "Punkter og polygoner" - -#: src/SUMMARY.md:158 -msgid "Day 3: Afternoon" +#: src/SUMMARY.md:162 src/iterators/exercise.md:1 +msgid "Exercise: Iterator Method Chaining" msgstr "" -#: src/SUMMARY.md:160 src/error-handling.md:1 -msgid "Error Handling" +#: src/SUMMARY.md:164 src/SUMMARY.md:165 src/modules.md:1 +#: src/modules/modules.md:1 +msgid "Modules" msgstr "" -#: src/SUMMARY.md:161 src/error-handling/panics.md:1 -msgid "Panics" +#: src/SUMMARY.md:166 src/modules/filesystem.md:1 +msgid "Filesystem Hierarchy" msgstr "" -#: src/SUMMARY.md:162 -msgid "Catching Stack Unwinding" +#: src/SUMMARY.md:167 src/modules/visibility.md:1 +msgid "Visibility" msgstr "" -#: src/SUMMARY.md:163 -msgid "Structured Error Handling" +#: src/SUMMARY.md:168 src/modules/paths.md:1 +msgid "use, super, self" msgstr "" -#: src/SUMMARY.md:164 -msgid "Propagating Errors with ?" +#: src/SUMMARY.md:169 src/modules/exercise.md:1 +msgid "Exercise: Modules for the GUI Library" msgstr "" -#: src/SUMMARY.md:165 src/error-handling/converting-error-types.md:1 -#: src/error-handling/converting-error-types-example.md:1 -msgid "Converting Error Types" +#: src/SUMMARY.md:171 src/testing.md:1 +msgid "Testing" msgstr "" -#: src/SUMMARY.md:167 src/error-handling/deriving-error-enums.md:1 -msgid "Deriving Error Enums" +#: src/SUMMARY.md:172 +msgid "Test Modules" msgstr "" -#: src/SUMMARY.md:168 src/error-handling/dynamic-errors.md:1 -msgid "Dynamic Error Types" +#: src/SUMMARY.md:173 src/testing/other.md:1 +#, fuzzy +msgid "Other Types of Tests" +msgstr "Andre projekter" + +#: src/SUMMARY.md:174 src/SUMMARY.md:314 src/testing/useful-crates.md:1 +msgid "Useful Crates" msgstr "" -#: src/SUMMARY.md:169 src/error-handling/error-contexts.md:1 -msgid "Adding Context to Errors" +#: src/SUMMARY.md:175 src/testing/googletest.md:1 +msgid "GoogleTest" msgstr "" -#: src/SUMMARY.md:170 src/testing.md:1 -msgid "Testing" +#: src/SUMMARY.md:176 +msgid "Compiler lints and Clippy" msgstr "" -#: src/SUMMARY.md:171 src/testing/unit-tests.md:1 -msgid "Unit Tests" +#: src/SUMMARY.md:177 src/testing/exercise.md:1 +#, fuzzy +msgid "Exercise: Luhn Algorithm" +msgstr "Luhn-algorithmen" + +#: src/SUMMARY.md:180 +#, fuzzy +msgid "Day 4: Afternoon" +msgstr "Dag 1: Eftermiddag" + +#: src/SUMMARY.md:183 src/error-handling.md:1 +msgid "Error Handling" msgstr "" -#: src/SUMMARY.md:172 src/testing/test-modules.md:1 -msgid "Test Modules" +#: src/SUMMARY.md:184 src/error-handling/panics.md:1 +msgid "Panics" msgstr "" -#: src/SUMMARY.md:173 src/testing/doc-tests.md:1 -msgid "Documentation Tests" +#: src/SUMMARY.md:185 +#, fuzzy +msgid "Try operator" +msgstr "Egenskab" + +#: src/SUMMARY.md:186 src/error-handling/try-conversions.md:1 +#, fuzzy +msgid "Try Conversions" +msgstr "Implicitte konverteringer" + +#: src/SUMMARY.md:187 +msgid "Error Trait" msgstr "" -#: src/SUMMARY.md:174 src/testing/integration-tests.md:1 -msgid "Integration Tests" +#: src/SUMMARY.md:188 +msgid "thiserror and anyhow" msgstr "" -#: src/SUMMARY.md:175 src/bare-metal/useful-crates.md:1 -msgid "Useful crates" +#: src/SUMMARY.md:189 src/error-handling/exercise.md:1 +msgid "Exercise: Rewriting with Result" msgstr "" -#: src/SUMMARY.md:176 src/unsafe.md:1 +#: src/SUMMARY.md:191 src/unsafe-rust.md:1 src/unsafe-rust/unsafe.md:1 msgid "Unsafe Rust" msgstr "" -#: src/SUMMARY.md:177 src/unsafe/raw-pointers.md:1 +#: src/SUMMARY.md:192 +msgid "Unsafe" +msgstr "" + +#: src/SUMMARY.md:193 src/unsafe-rust/dereferencing.md:1 msgid "Dereferencing Raw Pointers" msgstr "" -#: src/SUMMARY.md:178 src/unsafe/mutable-static-variables.md:1 +#: src/SUMMARY.md:194 src/unsafe-rust/mutable-static.md:1 msgid "Mutable Static Variables" msgstr "" -#: src/SUMMARY.md:179 src/unsafe/unions.md:1 +#: src/SUMMARY.md:195 src/unsafe-rust/unions.md:1 msgid "Unions" msgstr "" -#: src/SUMMARY.md:180 src/unsafe/calling-unsafe-functions.md:1 -msgid "Calling Unsafe Functions" -msgstr "" - -#: src/SUMMARY.md:181 src/unsafe/writing-unsafe-functions.md:1 -msgid "Writing Unsafe Functions" -msgstr "" - -#: src/SUMMARY.md:182 -msgid "Extern Functions" -msgstr "" +#: src/SUMMARY.md:196 src/unsafe-rust/unsafe-functions.md:1 +#, fuzzy +msgid "Unsafe Functions" +msgstr "Funktioner" -#: src/SUMMARY.md:183 src/unsafe/unsafe-traits.md:1 -msgid "Implementing Unsafe Traits" -msgstr "" +#: src/SUMMARY.md:197 +#, fuzzy +msgid "Unsafe Traits" +msgstr "Asynkrone egenskaber (eng. Traits)" -#: src/SUMMARY.md:185 src/exercises/day-3/safe-ffi-wrapper.md:1 -#: src/exercises/day-3/solutions-afternoon.md:3 -msgid "Safe FFI Wrapper" +#: src/SUMMARY.md:198 +msgid "Exercise: FFI Wrapper" msgstr "" -#: src/SUMMARY.md:188 src/SUMMARY.md:258 src/bare-metal/android.md:1 +#: src/SUMMARY.md:201 src/SUMMARY.md:320 src/bare-metal/android.md:1 msgid "Android" msgstr "Android" -#: src/SUMMARY.md:193 src/android/setup.md:1 +#: src/SUMMARY.md:206 src/SUMMARY.md:245 src/android/setup.md:1 +#: src/chromium/setup.md:1 msgid "Setup" msgstr "" -#: src/SUMMARY.md:194 src/android/build-rules.md:1 +#: src/SUMMARY.md:207 src/SUMMARY.md:248 src/android/build-rules.md:1 msgid "Build Rules" msgstr "" -#: src/SUMMARY.md:195 +#: src/SUMMARY.md:208 msgid "Binary" msgstr "" -#: src/SUMMARY.md:196 +#: src/SUMMARY.md:209 msgid "Library" msgstr "" -#: src/SUMMARY.md:197 src/android/aidl.md:1 +#: src/SUMMARY.md:210 src/android/aidl.md:1 msgid "AIDL" msgstr "" -#: src/SUMMARY.md:198 +#: src/SUMMARY.md:211 msgid "Interface" msgstr "" -#: src/SUMMARY.md:199 +#: src/SUMMARY.md:212 msgid "Implementation" msgstr "" -#: src/SUMMARY.md:200 +#: src/SUMMARY.md:213 msgid "Server" msgstr "" -#: src/SUMMARY.md:201 src/android/aidl/deploy.md:1 +#: src/SUMMARY.md:214 src/android/aidl/deploy.md:1 msgid "Deploy" msgstr "" -#: src/SUMMARY.md:202 +#: src/SUMMARY.md:215 msgid "Client" msgstr "" -#: src/SUMMARY.md:203 src/android/aidl/changing.md:1 +#: src/SUMMARY.md:216 src/android/aidl/changing.md:1 msgid "Changing API" msgstr "" -#: src/SUMMARY.md:204 src/SUMMARY.md:248 src/android/logging.md:1 +#: src/SUMMARY.md:217 src/SUMMARY.md:310 src/android/logging.md:1 #: src/bare-metal/aps/logging.md:1 msgid "Logging" msgstr "" -#: src/SUMMARY.md:205 src/android/interoperability.md:1 +#: src/SUMMARY.md:218 src/android/interoperability.md:1 msgid "Interoperability" msgstr "" -#: src/SUMMARY.md:206 +#: src/SUMMARY.md:219 msgid "With C" msgstr "" -#: src/SUMMARY.md:207 +#: src/SUMMARY.md:220 msgid "Calling C with Bindgen" msgstr "" -#: src/SUMMARY.md:208 +#: src/SUMMARY.md:221 msgid "Calling Rust from C" msgstr "" -#: src/SUMMARY.md:209 src/android/interoperability/cpp.md:1 -msgid "With C++" +#: src/SUMMARY.md:222 +msgid "With C++)" +msgstr "" + +#: src/SUMMARY.md:223 src/android/interoperability/cpp/bridge.md:1 +msgid "The Bridge Module" +msgstr "" + +#: src/SUMMARY.md:224 +#, fuzzy +msgid "Rust Bridge" +msgstr "Rust i Android" + +#: src/SUMMARY.md:225 src/android/interoperability/cpp/generated-cpp.md:1 +msgid "Generated C++" +msgstr "" + +#: src/SUMMARY.md:226 +msgid "C++ Bridge" +msgstr "" + +#: src/SUMMARY.md:227 src/android/interoperability/cpp/shared-types.md:1 +#, fuzzy +msgid "Shared Types" +msgstr "Skalartyper" + +#: src/SUMMARY.md:228 src/android/interoperability/cpp/shared-enums.md:1 +msgid "Shared Enums" +msgstr "" + +#: src/SUMMARY.md:229 src/android/interoperability/cpp/rust-result.md:1 +msgid "Rust Error Handling" +msgstr "" + +#: src/SUMMARY.md:230 src/android/interoperability/cpp/cpp-exception.md:1 +msgid "C++ Error Handling" +msgstr "" + +#: src/SUMMARY.md:231 src/android/interoperability/cpp/type-mapping.md:1 +msgid "Additional Types" +msgstr "" + +#: src/SUMMARY.md:232 +msgid "Building for Android: C++" +msgstr "" + +#: src/SUMMARY.md:233 +msgid "Building for Android: Genrules" +msgstr "" + +#: src/SUMMARY.md:234 +msgid "Building for Android: Rust" msgstr "" -#: src/SUMMARY.md:210 +#: src/SUMMARY.md:235 msgid "With Java" msgstr "" -#: src/SUMMARY.md:214 +#: src/SUMMARY.md:236 src/SUMMARY.md:293 src/SUMMARY.md:322 src/SUMMARY.md:345 +#: src/SUMMARY.md:367 src/exercises/android/morning.md:1 +#: src/exercises/bare-metal/morning.md:1 +#: src/exercises/bare-metal/afternoon.md:1 +#: src/exercises/concurrency/morning.md:1 +#: src/exercises/concurrency/afternoon.md:1 +msgid "Exercises" +msgstr "Øvelser" + +#: src/SUMMARY.md:240 +msgid "Chromium" +msgstr "" + +#: src/SUMMARY.md:246 src/chromium/cargo.md:1 +msgid "Using cargo for experimental tools" +msgstr "" + +#: src/SUMMARY.md:247 +msgid "Policy" +msgstr "" + +#: src/SUMMARY.md:249 +msgid "Unsafe code" +msgstr "" + +#: src/SUMMARY.md:250 src/chromium/build-rules/depending.md:1 +msgid "Depending on Rust code from Chromium C++" +msgstr "" + +#: src/SUMMARY.md:251 src/chromium/build-rules/vscode.md:1 +msgid "Visual Studio code" +msgstr "" + +#: src/SUMMARY.md:252 src/SUMMARY.md:258 src/SUMMARY.md:271 +#: src/exercises/chromium/third-party.md:1 +#, fuzzy +msgid "Exercise" +msgstr "Øvelser" + +#: src/SUMMARY.md:253 src/chromium/interoperability-with-cpp.md:1 +msgid "Interoperability with C++" +msgstr "" + +#: src/SUMMARY.md:254 +#: src/chromium/interoperability-with-cpp/example-bindings.md:1 +#, fuzzy +msgid "Example bindings" +msgstr "Eksempler" + +#: src/SUMMARY.md:255 +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:1 +msgid "Limitations of cxx" +msgstr "" + +#: src/SUMMARY.md:256 +#: src/chromium/interoperability-with-cpp/error-handling.md:1 +msgid "cxx error handling" +msgstr "" + +#: src/SUMMARY.md:257 +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:1 +msgid "Using cxx in Chromium" +msgstr "" + +#: src/SUMMARY.md:259 src/chromium/adding-third-party-crates.md:1 +msgid "Adding third party crates" +msgstr "" + +#: src/SUMMARY.md:260 +msgid "Configuring Cargo.toml" +msgstr "" + +#: src/SUMMARY.md:261 +msgid "Configuring gnrt_config.toml" +msgstr "" + +#: src/SUMMARY.md:262 +#: src/chromium/adding-third-party-crates/downloading-crates.md:1 +msgid "Downloading crates" +msgstr "" + +#: src/SUMMARY.md:263 +msgid "Generating gn build rules" +msgstr "" + +#: src/SUMMARY.md:264 +#: src/chromium/adding-third-party-crates/resolving-problems.md:1 +msgid "Resolving problems" +msgstr "" + +#: src/SUMMARY.md:265 +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:1 +msgid "Build scripts which generate code" +msgstr "" + +#: src/SUMMARY.md:266 +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:1 +msgid "Build scripts which build C++ or take arbitrary actions" +msgstr "" + +#: src/SUMMARY.md:267 +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:1 +msgid "Depending on a crate" +msgstr "" + +#: src/SUMMARY.md:268 +msgid "Reviews and audits" +msgstr "" + +#: src/SUMMARY.md:269 +msgid "Checking into Chromium source code" +msgstr "" + +#: src/SUMMARY.md:270 +#: src/chromium/adding-third-party-crates/keeping-up-to-date.md:1 +msgid "Keeping crates up to date" +msgstr "" + +#: src/SUMMARY.md:272 +msgid "Bringing it together - Exercise" +msgstr "" + +#: src/SUMMARY.md:275 msgid "Bare Metal: Morning" msgstr "Rå jern: Formiddag" -#: src/SUMMARY.md:219 +#: src/SUMMARY.md:280 msgid "no_std" msgstr "no_std" -#: src/SUMMARY.md:220 +#: src/SUMMARY.md:281 msgid "A Minimal Example" msgstr "Et minimalt eksempel" -#: src/SUMMARY.md:221 +#: src/SUMMARY.md:282 msgid "alloc" msgstr "alloc" -#: src/SUMMARY.md:222 src/bare-metal/microcontrollers.md:1 +#: src/SUMMARY.md:283 src/bare-metal/microcontrollers.md:1 msgid "Microcontrollers" msgstr "" -#: src/SUMMARY.md:223 src/bare-metal/microcontrollers/mmio.md:1 +#: src/SUMMARY.md:284 src/bare-metal/microcontrollers/mmio.md:1 msgid "Raw MMIO" msgstr "Rå MMIO" -#: src/SUMMARY.md:224 +#: src/SUMMARY.md:285 msgid "PACs" msgstr "PAC'er" -#: src/SUMMARY.md:225 +#: src/SUMMARY.md:286 msgid "HAL Crates" msgstr "" -#: src/SUMMARY.md:226 +#: src/SUMMARY.md:287 msgid "Board Support Crates" msgstr "" -#: src/SUMMARY.md:227 +#: src/SUMMARY.md:288 msgid "The Type State Pattern" msgstr "" -#: src/SUMMARY.md:228 +#: src/SUMMARY.md:289 msgid "embedded-hal" msgstr "embedded-hal" -#: src/SUMMARY.md:229 +#: src/SUMMARY.md:290 msgid "probe-rs, cargo-embed" msgstr "probe-rs, cargo-embed" -#: src/SUMMARY.md:230 src/bare-metal/microcontrollers/debugging.md:1 +#: src/SUMMARY.md:291 src/bare-metal/microcontrollers/debugging.md:1 msgid "Debugging" msgstr "Fejlfinding" -#: src/SUMMARY.md:231 src/SUMMARY.md:251 +#: src/SUMMARY.md:292 src/SUMMARY.md:313 msgid "Other Projects" msgstr "Andre projekter" -#: src/SUMMARY.md:233 src/exercises/bare-metal/compass.md:1 +#: src/SUMMARY.md:294 src/exercises/bare-metal/compass.md:1 #: src/exercises/bare-metal/solutions-morning.md:3 msgid "Compass" msgstr "Kompas" -#: src/SUMMARY.md:235 +#: src/SUMMARY.md:295 src/SUMMARY.md:324 src/SUMMARY.md:348 src/SUMMARY.md:370 +msgid "Solutions" +msgstr "Løsninger" + +#: src/SUMMARY.md:297 msgid "Bare Metal: Afternoon" msgstr "Rå jern: Eftermiddag" -#: src/SUMMARY.md:237 +#: src/SUMMARY.md:299 msgid "Application Processors" msgstr "" -#: src/SUMMARY.md:238 src/bare-metal/aps/entry-point.md:1 +#: src/SUMMARY.md:300 src/bare-metal/aps/entry-point.md:1 msgid "Getting Ready to Rust" msgstr "" -#: src/SUMMARY.md:239 +#: src/SUMMARY.md:301 msgid "Inline Assembly" msgstr "" -#: src/SUMMARY.md:240 +#: src/SUMMARY.md:302 msgid "MMIO" msgstr "MMIO" -#: src/SUMMARY.md:241 +#: src/SUMMARY.md:303 msgid "Let's Write a UART Driver" msgstr "" -#: src/SUMMARY.md:242 +#: src/SUMMARY.md:304 msgid "More Traits" msgstr "" -#: src/SUMMARY.md:243 +#: src/SUMMARY.md:305 msgid "A Better UART Driver" msgstr "" -#: src/SUMMARY.md:244 src/bare-metal/aps/better-uart/bitflags.md:1 +#: src/SUMMARY.md:306 src/bare-metal/aps/better-uart/bitflags.md:1 msgid "Bitflags" msgstr "Bitflag" -#: src/SUMMARY.md:245 +#: src/SUMMARY.md:307 msgid "Multiple Registers" msgstr "" -#: src/SUMMARY.md:246 src/bare-metal/aps/better-uart/driver.md:1 +#: src/SUMMARY.md:308 src/bare-metal/aps/better-uart/driver.md:1 msgid "Driver" msgstr "Driver" -#: src/SUMMARY.md:247 src/SUMMARY.md:249 +#: src/SUMMARY.md:309 src/SUMMARY.md:311 msgid "Using It" msgstr "Anvendelse" -#: src/SUMMARY.md:250 src/bare-metal/aps/exceptions.md:1 +#: src/SUMMARY.md:312 src/bare-metal/aps/exceptions.md:1 msgid "Exceptions" msgstr "Undtagelser" -#: src/SUMMARY.md:252 -msgid "Useful Crates" -msgstr "" - -#: src/SUMMARY.md:253 +#: src/SUMMARY.md:315 msgid "zerocopy" msgstr "zerocopy" -#: src/SUMMARY.md:254 +#: src/SUMMARY.md:316 msgid "aarch64-paging" msgstr "aarch64-paging" -#: src/SUMMARY.md:255 +#: src/SUMMARY.md:317 msgid "buddy_system_allocator" msgstr "buddy_system_allocator" -#: src/SUMMARY.md:256 +#: src/SUMMARY.md:318 msgid "tinyvec" msgstr "tinyvec" -#: src/SUMMARY.md:257 +#: src/SUMMARY.md:319 msgid "spin" msgstr "spin" -#: src/SUMMARY.md:259 src/bare-metal/android/vmbase.md:1 +#: src/SUMMARY.md:321 src/bare-metal/android/vmbase.md:1 msgid "vmbase" msgstr "vmbase" -#: src/SUMMARY.md:261 +#: src/SUMMARY.md:323 msgid "RTC Driver" msgstr "" -#: src/SUMMARY.md:264 +#: src/SUMMARY.md:327 msgid "Concurrency: Morning" msgstr "" -#: src/SUMMARY.md:269 src/concurrency/threads.md:1 +#: src/SUMMARY.md:332 src/concurrency/threads.md:1 msgid "Threads" msgstr "Tråde" -#: src/SUMMARY.md:270 src/concurrency/scoped-threads.md:1 +#: src/SUMMARY.md:333 src/concurrency/scoped-threads.md:1 msgid "Scoped Threads" msgstr "Tråde med virkefelt" -#: src/SUMMARY.md:271 src/concurrency/channels.md:1 +#: src/SUMMARY.md:334 src/concurrency/channels.md:1 msgid "Channels" msgstr "Kanaler" -#: src/SUMMARY.md:272 src/concurrency/channels/unbounded.md:1 +#: src/SUMMARY.md:335 src/concurrency/channels/unbounded.md:1 msgid "Unbounded Channels" msgstr "Ubegrænsede kanaler" -#: src/SUMMARY.md:273 src/concurrency/channels/bounded.md:1 +#: src/SUMMARY.md:336 src/concurrency/channels/bounded.md:1 msgid "Bounded Channels" msgstr "Begrænsede kanaler" -#: src/SUMMARY.md:274 +#: src/SUMMARY.md:337 msgid "Send and Sync" msgstr "Send og Sync" -#: src/SUMMARY.md:274 +#: src/SUMMARY.md:338 msgid "Send" msgstr "Send" -#: src/SUMMARY.md:274 +#: src/SUMMARY.md:339 msgid "Sync" msgstr "Sync" -#: src/SUMMARY.md:277 src/concurrency/send-sync/examples.md:1 +#: src/SUMMARY.md:340 src/concurrency/send-sync/examples.md:1 msgid "Examples" msgstr "Eksempler" -#: src/SUMMARY.md:278 src/concurrency/shared_state.md:1 +#: src/SUMMARY.md:341 src/concurrency/shared_state.md:1 msgid "Shared State" msgstr "Delt tilstand" -#: src/SUMMARY.md:279 +#: src/SUMMARY.md:342 msgid "Arc" msgstr "Arc" -#: src/SUMMARY.md:280 +#: src/SUMMARY.md:343 msgid "Mutex" msgstr "Mutex" -#: src/SUMMARY.md:283 src/SUMMARY.md:304 +#: src/SUMMARY.md:344 src/memory-management/review.md:16 +#: src/error-handling/try-conversions.md:22 +#: src/concurrency/shared_state/example.md:1 +msgid "Example" +msgstr "Eksempel" + +#: src/SUMMARY.md:346 src/SUMMARY.md:368 #: src/exercises/concurrency/dining-philosophers.md:1 #: src/exercises/concurrency/solutions-morning.md:3 msgid "Dining Philosophers" msgstr "Filosoffer omkring spisebordet" -#: src/SUMMARY.md:284 src/exercises/concurrency/link-checker.md:1 +#: src/SUMMARY.md:347 src/exercises/concurrency/link-checker.md:1 msgid "Multi-threaded Link Checker" msgstr "Flertrådet linktjekker" -#: src/SUMMARY.md:286 +#: src/SUMMARY.md:350 msgid "Concurrency: Afternoon" msgstr "Concurrency: Eftermiddag" -#: src/SUMMARY.md:288 +#: src/SUMMARY.md:352 msgid "Async Basics" msgstr "Grundlæggende Async" -#: src/SUMMARY.md:289 +#: src/SUMMARY.md:353 msgid "async/await" msgstr "async/await" -#: src/SUMMARY.md:290 src/async/futures.md:1 +#: src/SUMMARY.md:354 src/async/futures.md:1 msgid "Futures" msgstr "Fremtidige resultater (eng. Futures)" -#: src/SUMMARY.md:291 src/async/runtimes.md:1 +#: src/SUMMARY.md:355 src/async/runtimes.md:1 msgid "Runtimes" msgstr "" -#: src/SUMMARY.md:292 src/async/runtimes/tokio.md:1 +#: src/SUMMARY.md:356 src/async/runtimes/tokio.md:1 msgid "Tokio" msgstr "Tokio" -#: src/SUMMARY.md:293 src/exercises/concurrency/link-checker.md:126 +#: src/SUMMARY.md:357 src/exercises/concurrency/link-checker.md:126 #: src/async/tasks.md:1 src/exercises/concurrency/chat-app.md:143 msgid "Tasks" msgstr "Opgaver (eng. Tasks)" -#: src/SUMMARY.md:294 src/async/channels.md:1 +#: src/SUMMARY.md:358 src/async/channels.md:1 msgid "Async Channels" msgstr "Asynkrone kanaler" -#: src/SUMMARY.md:296 src/async/control-flow/join.md:1 +#: src/SUMMARY.md:359 +msgid "Control Flow" +msgstr "Forgreninger" + +#: src/SUMMARY.md:360 src/async/control-flow/join.md:1 msgid "Join" msgstr "Join" -#: src/SUMMARY.md:297 src/async/control-flow/select.md:1 +#: src/SUMMARY.md:361 src/async/control-flow/select.md:1 msgid "Select" msgstr "Select" -#: src/SUMMARY.md:298 +#: src/SUMMARY.md:362 msgid "Pitfalls" msgstr "Faldgruber" -#: src/SUMMARY.md:299 +#: src/SUMMARY.md:363 msgid "Blocking the Executor" msgstr "" -#: src/SUMMARY.md:300 src/async/pitfalls/pin.md:1 +#: src/SUMMARY.md:364 src/async/pitfalls/pin.md:1 msgid "Pin" msgstr "Pin" -#: src/SUMMARY.md:301 src/async/pitfalls/async-traits.md:1 +#: src/SUMMARY.md:365 src/async/pitfalls/async-traits.md:1 msgid "Async Traits" msgstr "Asynkrone egenskaber (eng. Traits)" -#: src/SUMMARY.md:302 src/async/pitfalls/cancellation.md:1 +#: src/SUMMARY.md:366 src/async/pitfalls/cancellation.md:1 msgid "Cancellation" msgstr "Annulering" -#: src/SUMMARY.md:305 src/exercises/concurrency/chat-app.md:1 +#: src/SUMMARY.md:369 src/exercises/concurrency/chat-app.md:1 #: src/exercises/concurrency/solutions-afternoon.md:95 msgid "Broadcast Chat Application" msgstr "Broadcast chat-applikation" -#: src/SUMMARY.md:308 +#: src/SUMMARY.md:373 msgid "Final Words" msgstr "Afsluttende bemærkninger" -#: src/SUMMARY.md:312 src/thanks.md:1 +#: src/SUMMARY.md:377 src/thanks.md:1 msgid "Thanks!" msgstr "Tak!" -#: src/SUMMARY.md:313 +#: src/SUMMARY.md:378 src/glossary.md:1 +msgid "Glossary" +msgstr "" + +#: src/SUMMARY.md:379 msgid "Other Resources" msgstr "Andre resourcer" -#: src/SUMMARY.md:314 src/credits.md:1 +#: src/SUMMARY.md:380 src/credits.md:1 msgid "Credits" msgstr "Anerkendelser" -#: src/SUMMARY.md:317 src/exercises/solutions.md:1 -msgid "Solutions" -msgstr "Løsninger" - -#: src/SUMMARY.md:322 -msgid "Day 1 Morning" -msgstr "Dag 1 Formiddag" - -#: src/SUMMARY.md:323 -msgid "Day 1 Afternoon" -msgstr "Dag 1 Eftermiddag" - -#: src/SUMMARY.md:324 -msgid "Day 2 Morning" -msgstr "Dag 2 Formiddag" - -#: src/SUMMARY.md:325 -msgid "Day 2 Afternoon" -msgstr "Dag 2 Eftermiddag" - -#: src/SUMMARY.md:326 -msgid "Day 3 Morning" -msgstr "Dag 3 Formiddag" - -#: src/SUMMARY.md:327 -msgid "Day 3 Afternoon" -msgstr "Dag 3 Eftermiddag" - -#: src/SUMMARY.md:328 -msgid "Bare Metal Rust Morning" -msgstr "Rå jern Rust formiddag" - -#: src/SUMMARY.md:329 src/exercises/bare-metal/solutions-afternoon.md:1 -msgid "Bare Metal Rust Afternoon" -msgstr "Rå jern Rust eftermiddag" - -#: src/SUMMARY.md:330 -msgid "Concurrency Morning" -msgstr "Parallelprogrammering formiddag" - -#: src/SUMMARY.md:331 -msgid "Concurrency Afternoon" -msgstr "Parallelprogrammering eftermiddag" - #: src/index.md:3 msgid "" "[![Build workflow](https://img.shields.io/github/actions/workflow/status/" @@ -1084,7 +1258,8 @@ msgid "Show you common Rust idioms." msgstr "Vise dig idiomatisk Rust." #: src/index.md:22 -msgid "We call the first three course days Rust Fundamentals." +#, fuzzy +msgid "We call the first four course days Rust Fundamentals." msgstr "" "Vi kalder de første tre kursusdage Grundlæggende Rust (_Rust Fundamentals_)." @@ -1105,6 +1280,17 @@ msgstr "" "C, C++ og Java." #: src/index.md:28 +#, fuzzy +msgid "" +"[Chromium](chromium.md): a half-day course on using Rust within Chromium " +"based browsers. This includes interoperability with C++ and how to include " +"third-party crates in Chromium." +msgstr "" +"[Android](android.md): en halv kursusdag om at bruge Rust til " +"platformudvikling i Android (AOSP). Dette inkluderer interoperabilitet med " +"C, C++ og Java." + +#: src/index.md:31 msgid "" "[Bare-metal](bare-metal.md): a whole-day class on using Rust for bare-metal " "(embedded) development. Both microcontrollers and application processors are " @@ -1114,7 +1300,7 @@ msgstr "" "på det rå jern og indlejrede (_bare metal and embedded_) systemer. Dækker " "både mikroprocessorer og applikationsprocessorer." -#: src/index.md:31 +#: src/index.md:34 msgid "" "[Concurrency](concurrency.md): a whole-day class on concurrency in Rust. We " "cover both classical concurrency (preemptively scheduling using threads and " @@ -1126,11 +1312,11 @@ msgstr "" "multitasking ved hjælp af tråde og mutexes) og async/await samtidighed " "(kooperativ multitasking ved hjælp af _futures_)." -#: src/index.md:37 +#: src/index.md:40 msgid "Non-Goals" msgstr "Ting som ikke dækkes" -#: src/index.md:39 +#: src/index.md:42 msgid "" "Rust is a large language and we won't be able to cover all of it in a few " "days. Some non-goals of this course are:" @@ -1138,7 +1324,7 @@ msgstr "" "Rust er et stort sprog og vi vil ikke være i stand til at dække det hele på " "et par dage. Nogle ting som vi ikke dækker er:" -#: src/index.md:42 +#: src/index.md:45 msgid "" "Learning how to develop macros: please see [Chapter 19.5 in the Rust Book]" "(https://doc.rust-lang.org/book/ch19-06-macros.html) and [Rust by Example]" @@ -1148,11 +1334,11 @@ msgstr "" "(https://doc.rust-lang.org/book/ch19-06-macros.html) og [Rust by Example]" "(https://doc.rust-lang.org/rust-by-example/macros.html) i stedet." -#: src/index.md:46 +#: src/index.md:49 msgid "Assumptions" msgstr "Antagelser" -#: src/index.md:48 +#: src/index.md:51 msgid "" "The course assumes that you already know how to program. Rust is a " "statically-typed language and we will sometimes make comparisons with C and " @@ -1162,7 +1348,7 @@ msgstr "" "statisk typet sprog og vi vil nogle gange sammenligne med C og C++ for bedre " "at kunne forklare Rust's tilgangsvinkel." -#: src/index.md:52 +#: src/index.md:55 msgid "" "If you know how to program in a dynamically-typed language such as Python or " "JavaScript, then you will be able to follow along just fine too." @@ -1170,7 +1356,7 @@ msgstr "" "Hvis du ved hvordan man programmerer i et dynamisk typet sprog såsom Python " "eller JavaScript, så vil du også fint kunne følge med." -#: src/index.md:57 +#: src/index.md:60 msgid "" "This is an example of a _speaker note_. We will use these to add additional " "information to the slides. This could be key points which the instructor " @@ -1193,19 +1379,17 @@ msgstr "" #: src/running-the-course.md:8 msgid "" -"We typically run classes from 10:00 am to 4:00 pm, with a 1 hour lunch break " -"in the middle. This leaves 2.5 hours for the morning class and 2.5 hours for " -"the afternoon class. Note that this is just a recommendation: you can also " -"spend 3 hour on the morning session to give people more time for exercises. " -"The downside of longer session is that people can become very tired after 6 " -"full hours of class in the afternoon." +"We typically run classes from 9:00 am to 4:00 pm, with a 1 hour lunch break " +"in the middle. This leaves 3 hours for the morning class and 3 hours for the " +"afternoon class. Both sessions contain multiple breaks and time for students " +"to work on exercises." msgstr "" -#: src/running-the-course.md:16 +#: src/running-the-course.md:13 msgid "Before you run the course, you will want to:" msgstr "" -#: src/running-the-course.md:18 +#: src/running-the-course.md:15 msgid "" "Make yourself familiar with the course material. We've included speaker " "notes to help highlight the key points (please help us by contributing more " @@ -1214,7 +1398,7 @@ msgid "" "Notes\"). This way you have a clean screen to present to the class." msgstr "" -#: src/running-the-course.md:24 +#: src/running-the-course.md:21 msgid "" "Decide on the dates. Since the course takes at least three full days, we " "recommend that you schedule the days over two weeks. Course participants " @@ -1222,7 +1406,7 @@ msgid "" "helps them process all the information we give them." msgstr "" -#: src/running-the-course.md:29 +#: src/running-the-course.md:26 msgid "" "Find a room large enough for your in-person participants. We recommend a " "class size of 15-25 people. That's small enough that people are comfortable " @@ -1233,7 +1417,7 @@ msgid "" "instructor, so a lectern won't be very helpful for you." msgstr "" -#: src/running-the-course.md:37 +#: src/running-the-course.md:34 msgid "" "On the day of your course, show up to the room a little early to set things " "up. We recommend presenting directly using `mdbook serve` running on your " @@ -1243,7 +1427,7 @@ msgid "" "you or the course participants spot them." msgstr "" -#: src/running-the-course.md:43 +#: src/running-the-course.md:40 msgid "" "Let people solve the exercises by themselves or in small groups. We " "typically spend 30-45 minutes on exercises in the morning and in the " @@ -1254,13 +1438,13 @@ msgid "" "information in the standard library." msgstr "" -#: src/running-the-course.md:51 +#: src/running-the-course.md:48 msgid "" "That is all, good luck running the course! We hope it will be as much fun " "for you as it has been for us!" msgstr "" -#: src/running-the-course.md:54 +#: src/running-the-course.md:51 msgid "" "Please [provide feedback](https://github.com/google/comprehensive-rust/" "discussions/86) afterwards so that we can keep improving the course. We " @@ -1276,129 +1460,269 @@ msgstr "" #: src/running-the-course/course-structure.md:7 msgid "" "The first three days make up [Rust Fundaments](../welcome-day-1.md). The " -"days are fast paced and we cover a lot of ground:" +"days are fast paced and we cover a lot of ground!" msgstr "" #: src/running-the-course/course-structure.md:10 -msgid "Day 1: Basic Rust, syntax, control flow, creating and consuming values." -msgstr "" +#, fuzzy +msgid "Course schedule:" +msgstr "Kursets struktur" #: src/running-the-course/course-structure.md:11 -msgid "" -"Day 2: Memory management, ownership, compound data types, and the standard " -"library." +msgid "Day 1 Morning (3 hours, including breaks)" msgstr "" #: src/running-the-course/course-structure.md:12 -msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." +msgid "[Welcome](../welcome-day-1.md) (5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:13 +msgid "[Hello, World](../hello-world.md) (20 minutes)" msgstr "" #: src/running-the-course/course-structure.md:14 -msgid "Deep Dives" +msgid "[Types and Values](../types-and-values.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:15 +msgid "[Control Flow Basics](../control-flow-basics.md) (1 hour)" msgstr "" #: src/running-the-course/course-structure.md:16 -msgid "" -"In addition to the 3-day class on Rust Fundamentals, we cover some more " -"specialized topics:" +msgid "Day 1 Afternoon (2 hours and 55 minutes, including breaks)" msgstr "" -"Ud over kurset på tre dage om Grundlæggende Rust, dækker vi mere " -"specialiserede emner:" -#: src/running-the-course/course-structure.md:19 -msgid "Rust in Android" -msgstr "Rust i Android" +#: src/running-the-course/course-structure.md:17 +msgid "[Tuples and Arrays](../tuples-and-arrays.md) (1 hour)" +msgstr "" -#: src/running-the-course/course-structure.md:21 -msgid "" -"The [Rust in Android](../android.md) deep dive is a half-day course on using " -"Rust for Android platform development. This includes interoperability with " -"C, C++, and Java." +#: src/running-the-course/course-structure.md:18 +msgid "[References](../references.md) (50 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:25 -msgid "" -"You will need an [AOSP checkout](https://source.android.com/docs/setup/" -"download/downloading). Make a checkout of the [course repository](https://" -"github.com/google/comprehensive-rust) on the same machine and move the `src/" -"android/` directory into the root of your AOSP checkout. This will ensure " -"that the Android build system sees the `Android.bp` files in `src/android/`." +#: src/running-the-course/course-structure.md:19 +msgid "[User-Defined Types](../user-defined-types.md) (50 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:30 -msgid "" -"Ensure that `adb sync` works with your emulator or real device and pre-build " -"all Android examples using `src/android/build_all.sh`. Read the script to " -"see the commands it runs and make sure they work when you run them by hand." +#: src/running-the-course/course-structure.md:20 +msgid "Day 2 Morning (3 hours and 15 minutes, including breaks)" msgstr "" -#: src/running-the-course/course-structure.md:37 -msgid "Bare-Metal Rust" -msgstr "Bare-Metal Rust" +#: src/running-the-course/course-structure.md:21 +msgid "[Welcome](../welcome-day-2.md) (3 minutes)" +msgstr "" -#: src/running-the-course/course-structure.md:39 -msgid "" -"The [Bare-Metal Rust](../bare-metal.md) deep dive is a full day class on " -"using Rust for bare-metal (embedded) development. Both microcontrollers and " -"application processors are covered." +#: src/running-the-course/course-structure.md:22 +msgid "[Pattern Matching](../pattern-matching.md) (50 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:43 -msgid "" -"For the microcontroller part, you will need to buy the [BBC micro:bit]" -"(https://microbit.org/) v2 development board ahead of time. Everybody will " -"need to install a number of packages as described on the [welcome page](../" -"bare-metal.md)." +#: src/running-the-course/course-structure.md:23 +msgid "[Methods and Traits](../methods-and-traits.md) (1 hour and 5 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:48 -msgid "Concurrency in Rust" -msgstr "Samtidighed i Rust" +#: src/running-the-course/course-structure.md:24 +msgid "[Generics](../generics.md) (45 minutes)" +msgstr "" -#: src/running-the-course/course-structure.md:50 -msgid "" -"The [Concurrency in Rust](../concurrency.md) deep dive is a full day class " -"on classical as well as `async`/`await` concurrency." +#: src/running-the-course/course-structure.md:25 +msgid "Day 2 Afternoon (3 hours, including breaks)" msgstr "" -#: src/running-the-course/course-structure.md:53 -msgid "" -"You will need a fresh crate set up and the dependencies downloaded and ready " -"to go. You can then copy/paste the examples into `src/main.rs` to experiment " -"with them:" +#: src/running-the-course/course-structure.md:26 +msgid "[Standard Library Types](../std-types.md) (1 hour and 10 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:64 -msgid "Format" +#: src/running-the-course/course-structure.md:27 +msgid "[Standard Library Traits](../std-traits.md) (1 hour and 40 minutes)" msgstr "" -#: src/running-the-course/course-structure.md:66 -msgid "" -"The course is meant to be very interactive and we recommend letting the " -"questions drive the exploration of Rust!" +#: src/running-the-course/course-structure.md:28 +msgid "Day 3 Morning (2 hours and 15 minutes, including breaks)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:3 -msgid "There are several useful keyboard shortcuts in mdBook:" +#: src/running-the-course/course-structure.md:29 +msgid "[Welcome](../welcome-day-3.md) (3 minutes)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:5 -msgid "Arrow-Left" +#: src/running-the-course/course-structure.md:30 +msgid "[Memory Management](../memory-management.md) (1 hour and 10 minutes)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:5 -msgid ": Navigate to the previous page." +#: src/running-the-course/course-structure.md:31 +msgid "[Smart Pointers](../smart-pointers.md) (45 minutes)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:6 -msgid "Arrow-Right" +#: src/running-the-course/course-structure.md:32 +msgid "Day 3 Afternoon (2 hours and 20 minutes, including breaks)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:6 -msgid ": Navigate to the next page." +#: src/running-the-course/course-structure.md:33 +msgid "[Borrowing](../borrowing.md) (1 hour)" msgstr "" -#: src/running-the-course/keyboard-shortcuts.md:7 src/cargo/code-samples.md:19 +#: src/running-the-course/course-structure.md:34 +msgid "" +"[Slices and Lifetimes](../slices-and-lifetimes.md) (1 hour and 10 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:35 +msgid "Day 4 Morning (3 hours and 5 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md:36 +msgid "[Welcome](../welcome-day-4.md) (3 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:37 +msgid "[Iterators](../iterators.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:38 +msgid "[Modules](../modules.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:39 +msgid "[Testing](../testing.md) (1 hour)" +msgstr "" + +#: src/running-the-course/course-structure.md:40 +msgid "Day 4 Afternoon (2 hours, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md:41 +msgid "[Error Handling](../error-handling.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:42 +msgid "[Unsafe Rust](../unsafe-rust.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md:45 +msgid "Deep Dives" +msgstr "" + +#: src/running-the-course/course-structure.md:47 +msgid "" +"In addition to the 3-day class on Rust Fundamentals, we cover some more " +"specialized topics:" +msgstr "" +"Ud over kurset på tre dage om Grundlæggende Rust, dækker vi mere " +"specialiserede emner:" + +#: src/running-the-course/course-structure.md:50 +msgid "Rust in Android" +msgstr "Rust i Android" + +#: src/running-the-course/course-structure.md:52 +msgid "" +"The [Rust in Android](../android.md) deep dive is a half-day course on using " +"Rust for Android platform development. This includes interoperability with " +"C, C++, and Java." +msgstr "" + +#: src/running-the-course/course-structure.md:56 +msgid "" +"You will need an [AOSP checkout](https://source.android.com/docs/setup/" +"download/downloading). Make a checkout of the [course repository](https://" +"github.com/google/comprehensive-rust) on the same machine and move the `src/" +"android/` directory into the root of your AOSP checkout. This will ensure " +"that the Android build system sees the `Android.bp` files in `src/android/`." +msgstr "" + +#: src/running-the-course/course-structure.md:61 +msgid "" +"Ensure that `adb sync` works with your emulator or real device and pre-build " +"all Android examples using `src/android/build_all.sh`. Read the script to " +"see the commands it runs and make sure they work when you run them by hand." +msgstr "" + +#: src/running-the-course/course-structure.md:68 +#, fuzzy +msgid "Rust in Chromium" +msgstr "Rust i Android" + +#: src/running-the-course/course-structure.md:70 +msgid "" +"The [Rust in Chromium](../chromium.md) deep dive is a half-day course on " +"using Rust as part of the Chromium browser. It includes using Rust in " +"Chromium's `gn` build system, bringing in third-party libraries (\"crates\") " +"and C++ interoperability." +msgstr "" + +#: src/running-the-course/course-structure.md:75 +msgid "" +"You will need to be able to build Chromium --- a debug, component build is " +"[recommended](../chromium/setup.md) for speed but any build will work. " +"Ensure that you can run the Chromium browser that you've built." +msgstr "" + +#: src/running-the-course/course-structure.md:79 +msgid "Bare-Metal Rust" +msgstr "Bare-Metal Rust" + +#: src/running-the-course/course-structure.md:81 +msgid "" +"The [Bare-Metal Rust](../bare-metal.md) deep dive is a full day class on " +"using Rust for bare-metal (embedded) development. Both microcontrollers and " +"application processors are covered." +msgstr "" + +#: src/running-the-course/course-structure.md:85 +msgid "" +"For the microcontroller part, you will need to buy the [BBC micro:bit]" +"(https://microbit.org/) v2 development board ahead of time. Everybody will " +"need to install a number of packages as described on the [welcome page](../" +"bare-metal.md)." +msgstr "" + +#: src/running-the-course/course-structure.md:90 +msgid "Concurrency in Rust" +msgstr "Samtidighed i Rust" + +#: src/running-the-course/course-structure.md:92 +msgid "" +"The [Concurrency in Rust](../concurrency.md) deep dive is a full day class " +"on classical as well as `async`/`await` concurrency." +msgstr "" + +#: src/running-the-course/course-structure.md:95 +msgid "" +"You will need a fresh crate set up and the dependencies downloaded and ready " +"to go. You can then copy/paste the examples into `src/main.rs` to experiment " +"with them:" +msgstr "" + +#: src/running-the-course/course-structure.md:106 +msgid "Format" +msgstr "" + +#: src/running-the-course/course-structure.md:108 +msgid "" +"The course is meant to be very interactive and we recommend letting the " +"questions drive the exploration of Rust!" +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:3 +msgid "There are several useful keyboard shortcuts in mdBook:" +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:5 +msgid "Arrow-Left" +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:5 +msgid ": Navigate to the previous page." +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:6 +msgid "Arrow-Right" +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:6 +msgid ": Navigate to the next page." +msgstr "" + +#: src/running-the-course/keyboard-shortcuts.md:7 src/cargo/code-samples.md:19 msgid "Ctrl + Enter" msgstr "Ctrl + Enter" @@ -1430,55 +1754,57 @@ msgstr "" #: src/running-the-course/translations.md:7 msgid "" +"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " +"by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" +"wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/" +"kongy), [@noahdragon](https://github.com/noahdragon), [@superwhd](https://" +"github.com/superwhd), [@SketchK](https://github.com/SketchK), and [@nodmp]" +"(https://github.com/nodmp)." +msgstr "" + +#: src/running-the-course/translations.md:8 +msgid "" +"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " +"by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" +"victorhsieh), [@mingyc](https://github.com/mingyc), [@kuanhungchen](https://" +"github.com/kuanhungchen), and [@johnathan79717](https://github.com/" +"johnathan79717)." +msgstr "" + +#: src/running-the-course/translations.md:9 +msgid "" "[Korean](https://google.github.io/comprehensive-rust/ko/) by [@keispace]" "(https://github.com/keispace), [@jiyongp](https://github.com/jiyongp), and " "[@jooyunghan](https://github.com/jooyunghan)." msgstr "" -#: src/running-the-course/translations.md:8 +#: src/running-the-course/translations.md:10 msgid "" "[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid]" "(https://github.com/deavid)." msgstr "" -#: src/running-the-course/translations.md:10 +#: src/running-the-course/translations.md:12 msgid "" "Use the language picker in the top-right corner to switch between languages." msgstr "" -#: src/running-the-course/translations.md:12 +#: src/running-the-course/translations.md:14 msgid "Incomplete Translations" msgstr "Ufuldstændige oversættelser" -#: src/running-the-course/translations.md:14 +#: src/running-the-course/translations.md:16 msgid "" "There is a large number of in-progress translations. We link to the most " "recently updated translations:" msgstr "" -#: src/running-the-course/translations.md:17 +#: src/running-the-course/translations.md:19 msgid "" "[Bengali](https://google.github.io/comprehensive-rust/bn/) by [@raselmandol]" "(https://github.com/raselmandol)." msgstr "" -#: src/running-the-course/translations.md:18 -msgid "" -"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " -"by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" -"victorhsieh), [@mingyc](https://github.com/mingyc), and [@johnathan79717]" -"(https://github.com/johnathan79717)." -msgstr "" - -#: src/running-the-course/translations.md:19 -msgid "" -"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " -"by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" -"wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/" -"kongy), [@noahdragon](https://github.com/noahdragon), and [@superwhd]" -"(https://github.com/superwhd)." -msgstr "" - #: src/running-the-course/translations.md:20 msgid "" "[French](https://google.github.io/comprehensive-rust/fr/) by [@KookaS]" @@ -1575,20 +1901,16 @@ msgstr "" #: src/cargo/rust-ecosystem.md:13 msgid "" "`rustup`: the Rust toolchain installer and updater. This tool is used to " -"install and update `rustc` and `cargo` when new versions of Rust is " +"install and update `rustc` and `cargo` when new versions of Rust are " "released. In addition, `rustup` can also download documentation for the " "standard library. You can have multiple versions of Rust installed at once " "and `rustup` will let you switch between them as needed." msgstr "" -#: src/cargo/rust-ecosystem.md:21 src/hello-world.md:25 -#: src/hello-world/small-example.md:27 src/why-rust/runtime.md:10 -#: src/why-rust/modern.md:21 src/basic-syntax/compound-types.md:32 -#: src/basic-syntax/references.md:24 -#: src/pattern-matching/destructuring-enums.md:35 -#: src/ownership/double-free-modern-cpp.md:55 -#: src/error-handling/try-operator.md:48 -#: src/error-handling/converting-error-types-example.md:50 +#: src/cargo/rust-ecosystem.md:21 src/hello-world/hello-world.md:26 +#: src/tuples-and-arrays/tuples-and-arrays.md:37 src/references/exclusive.md:19 +#: src/pattern-matching/destructuring.md:68 src/memory-management/move.md:147 +#: src/error-handling/try.md:53 src/android/setup.md:17 #: src/concurrency/threads.md:30 src/async/async-await.md:25 msgid "Key points:" msgstr "Nøglepunkter:" @@ -1720,7 +2042,8 @@ msgid "You can use " msgstr "Du kan bruge " #: src/cargo/code-samples.md:19 -msgid "to execute the code when focus is in the text box." +#, fuzzy +msgid " to execute the code when focus is in the text box." msgstr "for at afvikle koden når tekstboksen er i fokus." #: src/cargo/code-samples.md:24 @@ -1831,214 +2154,271 @@ msgid "" "references, functions, and methods." msgstr "" +#: src/welcome-day-1.md:8 +#, fuzzy +msgid "Types and type inference." +msgstr "Typeudledning" + #: src/welcome-day-1.md:9 -msgid "" -"Control flow constructs: `if`, `if let`, `while`, `while let`, `break`, and " -"`continue`." +msgid "Control flow constructs: loops, conditionals, and so on." +msgstr "" + +#: src/welcome-day-1.md:10 +msgid "User-defined types: structs and enums." msgstr "" -#: src/welcome-day-1.md:12 +#: src/welcome-day-1.md:11 msgid "Pattern matching: destructuring enums, structs, and arrays." msgstr "" +#: src/welcome-day-1.md:13 src/welcome-day-2.md:12 src/welcome-day-3.md:8 +#: src/welcome-day-4.md:11 +msgid "Schedule" +msgstr "" + +#: src/welcome-day-1.md:15 src/welcome-day-1-afternoon.md:3 +#: src/welcome-day-2.md:14 src/welcome-day-2-afternoon.md:3 +#: src/welcome-day-3.md:10 src/welcome-day-3-afternoon.md:3 +#: src/welcome-day-4.md:13 src/welcome-day-4-afternoon.md:3 +msgid "In this session:" +msgstr "" + #: src/welcome-day-1.md:16 -msgid "Please remind the students that:" +msgid "[Welcome](./welcome-day-1.md) (5 minutes)" +msgstr "" + +#: src/welcome-day-1.md:17 +msgid "[Hello, World](./hello-world.md) (20 minutes)" msgstr "" #: src/welcome-day-1.md:18 +msgid "[Types and Values](./types-and-values.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/welcome-day-1.md:19 +msgid "[Control Flow Basics](./control-flow-basics.md) (1 hour)" +msgstr "" + +#: src/welcome-day-1.md:21 src/welcome-day-2-afternoon.md:7 +msgid "Including 10 minute breaks, this session should take about 3 hours" +msgstr "" + +#: src/welcome-day-1.md:27 +msgid "Please remind the students that:" +msgstr "" + +#: src/welcome-day-1.md:29 msgid "" "They should ask questions when they get them, don't save them to the end." msgstr "" -#: src/welcome-day-1.md:19 +#: src/welcome-day-1.md:30 msgid "" "The class is meant to be interactive and discussions are very much " "encouraged!" msgstr "" -#: src/welcome-day-1.md:20 +#: src/welcome-day-1.md:31 msgid "" "As an instructor, you should try to keep the discussions relevant, i.e., " -"keep the discussions related to how Rust does things vs some other " -"language. It can be hard to find the right balance, but err on the side of " -"allowing discussions since they engage people much more than one-way " -"communication." +"keep the discussions related to how Rust does things vs some other language. " +"It can be hard to find the right balance, but err on the side of allowing " +"discussions since they engage people much more than one-way communication." msgstr "" -#: src/welcome-day-1.md:24 +#: src/welcome-day-1.md:35 msgid "" "The questions will likely mean that we talk about things ahead of the slides." msgstr "" -#: src/welcome-day-1.md:25 +#: src/welcome-day-1.md:36 msgid "" "This is perfectly okay! Repetition is an important part of learning. " "Remember that the slides are just a support and you are free to skip them as " "you like." msgstr "" -#: src/welcome-day-1.md:29 +#: src/welcome-day-1.md:40 msgid "" -"The idea for the first day is to show _just enough_ of Rust to be able to " -"speak about the famous borrow checker. The way Rust handles memory is a " -"major feature and we should show students this right away." +"The idea for the first day is to show the \"basic\" things in Rust that " +"should have immediate parallels in other languages. The more advanced parts " +"of Rust come on the subsequent days." msgstr "" -#: src/welcome-day-1.md:33 +#: src/welcome-day-1.md:44 msgid "" "If you're teaching this in a classroom, this is a good place to go over the " -"schedule. We suggest splitting the day into two parts (following the slides):" +"schedule. Note that there is an exercise at the end of each segment, " +"followed by a break. Plan to cover the exercise solution after the break. " +"The times listed here are a suggestion in order to keep the course on " +"schedule. Feel free to be flexible and adjust as necessary!" msgstr "" -#: src/welcome-day-1.md:36 -msgid "Morning: 9:00 to 12:00," +#: src/hello-world.md:3 src/types-and-values.md:3 src/control-flow-basics.md:3 +#: src/tuples-and-arrays.md:3 src/references.md:3 src/user-defined-types.md:3 +#: src/pattern-matching.md:3 src/methods-and-traits.md:3 src/generics.md:3 +#: src/std-types.md:3 src/std-traits.md:3 src/memory-management.md:3 +#: src/smart-pointers.md:3 src/borrowing.md:3 src/slices-and-lifetimes.md:3 +#: src/iterators.md:3 src/modules.md:3 src/testing.md:3 src/error-handling.md:3 +#: src/unsafe-rust.md:3 +msgid "In this segment:" msgstr "" -#: src/welcome-day-1.md:37 -msgid "Afternoon: 13:00 to 16:00." +#: src/hello-world.md:4 +msgid "[What is Rust?](./hello-world/what-is-rust.md) (10 minutes)" msgstr "" -#: src/welcome-day-1.md:39 -msgid "" -"You can of course adjust this as necessary. Please make sure to include " -"breaks, we recommend a break every hour!" +#: src/hello-world.md:5 +msgid "[Hello, World](./hello-world/hello-world.md) (5 minutes)" +msgstr "" + +#: src/hello-world.md:6 +msgid "[Benefits of Rust](./hello-world/benefits.md) (3 minutes)" msgstr "" -#: src/welcome-day-1/what-is-rust.md:3 +#: src/hello-world.md:7 +msgid "[Playground](./hello-world/playground.md) (2 minutes)" +msgstr "" + +#: src/hello-world.md:9 +msgid "This segment should take about 20 minutes" +msgstr "" + +#: src/hello-world/what-is-rust.md:3 msgid "" "Rust is a new programming language which had its [1.0 release in 2015]" "(https://blog.rust-lang.org/2015/05/15/Rust-1.0.html):" msgstr "" -#: src/welcome-day-1/what-is-rust.md:5 +#: src/hello-world/what-is-rust.md:5 msgid "Rust is a statically compiled language in a similar role as C++" msgstr "" -#: src/welcome-day-1/what-is-rust.md:6 +#: src/hello-world/what-is-rust.md:6 msgid "`rustc` uses LLVM as its backend." msgstr "" -#: src/welcome-day-1/what-is-rust.md:7 +#: src/hello-world/what-is-rust.md:7 msgid "" "Rust supports many [platforms and architectures](https://doc.rust-lang.org/" "nightly/rustc/platform-support.html):" msgstr "" -#: src/welcome-day-1/what-is-rust.md:9 +#: src/hello-world/what-is-rust.md:9 msgid "x86, ARM, WebAssembly, ..." msgstr "" -#: src/welcome-day-1/what-is-rust.md:10 +#: src/hello-world/what-is-rust.md:10 msgid "Linux, Mac, Windows, ..." msgstr "" -#: src/welcome-day-1/what-is-rust.md:11 +#: src/hello-world/what-is-rust.md:11 msgid "Rust is used for a wide range of devices:" msgstr "" -#: src/welcome-day-1/what-is-rust.md:12 +#: src/hello-world/what-is-rust.md:12 msgid "firmware and boot loaders," msgstr "" -#: src/welcome-day-1/what-is-rust.md:13 +#: src/hello-world/what-is-rust.md:13 msgid "smart displays," msgstr "" -#: src/welcome-day-1/what-is-rust.md:14 +#: src/hello-world/what-is-rust.md:14 msgid "mobile phones," msgstr "" -#: src/welcome-day-1/what-is-rust.md:15 +#: src/hello-world/what-is-rust.md:15 msgid "desktops," msgstr "" -#: src/welcome-day-1/what-is-rust.md:16 +#: src/hello-world/what-is-rust.md:16 msgid "servers." msgstr "" -#: src/welcome-day-1/what-is-rust.md:21 +#: src/hello-world/what-is-rust.md:22 msgid "Rust fits in the same area as C++:" msgstr "Rust har det samme anvendelsesområde som C++:" -#: src/welcome-day-1/what-is-rust.md:23 +#: src/hello-world/what-is-rust.md:24 msgid "High flexibility." msgstr "" -#: src/welcome-day-1/what-is-rust.md:24 +#: src/hello-world/what-is-rust.md:25 msgid "High level of control." msgstr "" -#: src/welcome-day-1/what-is-rust.md:25 +#: src/hello-world/what-is-rust.md:26 msgid "" "Can be scaled down to very constrained devices such as microcontrollers." msgstr "" -#: src/welcome-day-1/what-is-rust.md:26 +#: src/hello-world/what-is-rust.md:27 msgid "Has no runtime or garbage collection." msgstr "" -#: src/welcome-day-1/what-is-rust.md:27 +#: src/hello-world/what-is-rust.md:28 msgid "Focuses on reliability and safety without sacrificing performance." msgstr "" -#: src/hello-world.md:3 +#: src/hello-world/hello-world.md:3 msgid "" "Let us jump into the simplest possible Rust program, a classic Hello World " "program:" msgstr "" -#: src/hello-world.md:8 +#: src/hello-world/hello-world.md:8 msgid "\"Hello 🌍!\"" msgstr "\"Hallo 🌍!\"" -#: src/hello-world.md:12 +#: src/hello-world/hello-world.md:12 msgid "What you see:" msgstr "Hvad du ser:" -#: src/hello-world.md:14 +#: src/hello-world/hello-world.md:14 msgid "Functions are introduced with `fn`." msgstr "" -#: src/hello-world.md:15 +#: src/hello-world/hello-world.md:15 msgid "Blocks are delimited by curly braces like in C and C++." msgstr "" -#: src/hello-world.md:16 +#: src/hello-world/hello-world.md:16 msgid "The `main` function is the entry point of the program." msgstr "" -#: src/hello-world.md:17 +#: src/hello-world/hello-world.md:17 msgid "Rust has hygienic macros, `println!` is an example of this." msgstr "" -#: src/hello-world.md:18 +#: src/hello-world/hello-world.md:18 msgid "Rust strings are UTF-8 encoded and can contain any Unicode character." msgstr "" -#: src/hello-world.md:22 +#: src/hello-world/hello-world.md:23 msgid "" "This slide tries to make the students comfortable with Rust code. They will " "see a ton of it over the next three days so we start small with something " "familiar." msgstr "" -#: src/hello-world.md:27 +#: src/hello-world/hello-world.md:28 msgid "" "Rust is very much like other languages in the C/C++/Java tradition. It is " "imperative and it doesn't try to reinvent things unless absolutely necessary." msgstr "" -#: src/hello-world.md:31 +#: src/hello-world/hello-world.md:32 msgid "Rust is modern with full support for things like Unicode." msgstr "" -#: src/hello-world.md:33 +#: src/hello-world/hello-world.md:34 msgid "" "Rust uses macros for situations where you want to have a variable number of " "arguments (no function [overloading](basic-syntax/functions-interlude.md))." msgstr "" -#: src/hello-world.md:36 +#: src/hello-world/hello-world.md:37 msgid "" "Macros being 'hygienic' means they don't accidentally capture identifiers " "from the scope they are used in. Rust macros are actually only [partially " @@ -2046,7 +2426,7 @@ msgid "" "html)." msgstr "" -#: src/hello-world.md:40 +#: src/hello-world/hello-world.md:41 msgid "" "Rust is multi-paradigm. For example, it has powerful [object-oriented " "programming features](https://doc.rust-lang.org/book/ch17-00-oop.html), and, " @@ -2054,104 +2434,109 @@ msgid "" "concepts](https://doc.rust-lang.org/book/ch13-00-functional-features.html)." msgstr "" -#: src/hello-world/small-example.md:3 -msgid "Here is a small example program in Rust:" -msgstr "Her er et lille eksempel på et program i Rust:" +#: src/hello-world/benefits.md:3 +msgid "Some unique selling points of Rust:" +msgstr "" + +#: src/hello-world/benefits.md:5 +msgid "" +"_Compile time memory safety_ - whole classes of memory bugs are prevented at " +"compile time" +msgstr "" -#: src/hello-world/small-example.md:6 -msgid "// Program entry point\n" +#: src/hello-world/benefits.md:6 +msgid "No uninitialized variables." msgstr "" -#: src/hello-world/small-example.md:7 -msgid "// Mutable variable binding\n" +#: src/hello-world/benefits.md:7 +msgid "No double-frees." msgstr "" -#: src/hello-world/small-example.md:8 src/traits/impl-trait.md:15 -msgid "\"{x}\"" -msgstr "\"{x}\"" +#: src/hello-world/benefits.md:8 +msgid "No use-after-free." +msgstr "" -#: src/hello-world/small-example.md:8 -msgid "// Macro for printing, like printf\n" +#: src/hello-world/benefits.md:9 +msgid "No `NULL` pointers." msgstr "" -#: src/hello-world/small-example.md:9 -msgid "// No parenthesis around expression\n" +#: src/hello-world/benefits.md:10 +msgid "No forgotten locked mutexes." msgstr "" -#: src/hello-world/small-example.md:10 -msgid "// Math like in other languages\n" +#: src/hello-world/benefits.md:11 +msgid "No data races between threads." msgstr "" -#: src/hello-world/small-example.md:15 -msgid "\" -> {x}\"" -msgstr "\" -> {x}\"" +#: src/hello-world/benefits.md:12 +msgid "No iterator invalidation." +msgstr "" -#: src/hello-world/small-example.md:23 +#: src/hello-world/benefits.md:14 msgid "" -"The code implements the Collatz conjecture: it is believed that the loop " -"will always end, but this is not yet proved. Edit the code and play with " -"different inputs." +"_No undefined runtime behavior_ - what a Rust statement does is never left " +"unspecified" msgstr "" -#: src/hello-world/small-example.md:29 -msgid "" -"Explain that all variables are statically typed. Try removing `i32` to " -"trigger type inference. Try with `i8` instead and trigger a runtime integer " -"overflow." +#: src/hello-world/benefits.md:16 +msgid "Array access is bounds checked." msgstr "" -#: src/hello-world/small-example.md:32 -msgid "Change `let mut x` to `let x`, discuss the compiler error." +#: src/hello-world/benefits.md:17 +msgid "Integer overflow is defined (panic or wrap-around)." msgstr "" -#: src/hello-world/small-example.md:34 +#: src/hello-world/benefits.md:19 msgid "" -"Show how `print!` gives a compilation error if the arguments don't match the " -"format string." +"_Modern language features_ - as expressive and ergonomic as higher-level " +"languages" msgstr "" -#: src/hello-world/small-example.md:37 -msgid "" -"Show how you need to use `{}` as a placeholder if you want to print an " -"expression which is more complex than just a single variable." +#: src/hello-world/benefits.md:21 +msgid "Enums and pattern matching." msgstr "" -#: src/hello-world/small-example.md:40 -msgid "" -"Show the students the standard library, show them how to search for `std::" -"fmt` which has the rules of the formatting mini-language. It's important " -"that the students become familiar with searching in the standard library." +#: src/hello-world/benefits.md:22 +msgid "Generics." msgstr "" -#: src/hello-world/small-example.md:44 -msgid "" -"In a shell `rustup doc std::fmt` will open a browser on the local std::fmt " -"documentation" +#: src/hello-world/benefits.md:23 +msgid "No overhead FFI." msgstr "" -#: src/why-rust.md:3 -msgid "Some unique selling points of Rust:" +#: src/hello-world/benefits.md:24 +msgid "Zero-cost abstractions." +msgstr "" + +#: src/hello-world/benefits.md:25 +msgid "Great compiler errors." +msgstr "" + +#: src/hello-world/benefits.md:26 +msgid "Built-in dependency manager." msgstr "" -#: src/why-rust.md:5 -msgid "Compile time memory safety." +#: src/hello-world/benefits.md:27 +msgid "Built-in support for testing." msgstr "" -#: src/why-rust.md:6 -msgid "Lack of undefined runtime behavior." +#: src/hello-world/benefits.md:28 +msgid "Excellent Language Server Protocol support." msgstr "" -#: src/why-rust.md:7 -msgid "Modern language features." +#: src/hello-world/benefits.md:33 +msgid "" +"Do not spend much time here. All of these points will be covered in more " +"depth later." msgstr "" -#: src/why-rust.md:11 +#: src/hello-world/benefits.md:36 msgid "" "Make sure to ask the class which languages they have experience with. " "Depending on the answer you can highlight different features of Rust:" msgstr "" -#: src/why-rust.md:14 +#: src/hello-world/benefits.md:39 msgid "" "Experience with C or C++: Rust eliminates a whole class of _runtime errors_ " "via the borrow checker. You get performance like in C and C++, but you don't " @@ -2159,7 +2544,7 @@ msgid "" "constructs like pattern matching and built-in dependency management." msgstr "" -#: src/why-rust.md:19 +#: src/hello-world/benefits.md:44 msgid "" "Experience with Java, Go, Python, JavaScript...: You get the same memory " "safety as in those languages, plus a similar high-level language feeling. In " @@ -2167,7930 +2552,11315 @@ msgid "" "collector) as well as access to low-level hardware (should you need it)" msgstr "" -#: src/why-rust/compile-time.md:3 -msgid "Static memory management at compile time:" +#: src/hello-world/playground.md:3 +msgid "" +"The [Rust Playground](https://play.rust-lang.org/) provides an easy way to " +"run short Rust programs, and is the basis for the examples and exercises in " +"this course. Try running the \"hello-world\" program it starts with. It " +"comes with a few handy features:" msgstr "" -#: src/why-rust/compile-time.md:5 -msgid "No uninitialized variables." +#: src/hello-world/playground.md:8 +msgid "" +"Under \"Tools\", use the `rustfmt` option to format your code in the " +"\"standard\" way." msgstr "" -#: src/why-rust/compile-time.md:6 -msgid "No memory leaks (_mostly_, see notes)." +#: src/hello-world/playground.md:11 +msgid "" +"Rust has two main \"profiles\" for generating code: Debug (extra runtime " +"checks, less optimization) and Release (fewer runtime checks, lots of " +"optimization). These are accessible under \"Debug\" at the top." msgstr "" -#: src/why-rust/compile-time.md:7 -msgid "No double-frees." +#: src/hello-world/playground.md:15 +msgid "" +"If you're interested, use \"ASM\" under \"...\" to see the generated " +"assembly code." msgstr "" -#: src/why-rust/compile-time.md:8 -msgid "No use-after-free." +#: src/hello-world/playground.md:21 +msgid "" +"As students head into the break, encourage them to open up the playground " +"and experiment a little. Encourage them to keep the tab open and try things " +"out during the rest of the course. This is particularly helpful for advanced " +"students who want to know more about Rust's optimzations or generated " +"assembly." msgstr "" -#: src/why-rust/compile-time.md:9 -msgid "No `NULL` pointers." +#: src/types-and-values.md:4 +msgid "[Variables](./types-and-values/variables.md) (5 minutes)" msgstr "" -#: src/why-rust/compile-time.md:10 -msgid "No forgotten locked mutexes." +#: src/types-and-values.md:5 +msgid "[Values](./types-and-values/values.md) (10 minutes)" msgstr "" -#: src/why-rust/compile-time.md:11 -msgid "No data races between threads." +#: src/types-and-values.md:6 +msgid "[Arithmetic](./types-and-values/arithmetic.md) (5 minutes)" msgstr "" -#: src/why-rust/compile-time.md:12 -msgid "No iterator invalidation." +#: src/types-and-values.md:7 +msgid "[Strings](./types-and-values/strings.md) (10 minutes)" msgstr "" -#: src/why-rust/compile-time.md:16 -msgid "" -"It is possible to produce memory leaks in (safe) Rust. Some examples are:" +#: src/types-and-values.md:8 +msgid "[Type Inference](./types-and-values/inference.md) (5 minutes)" msgstr "" -#: src/why-rust/compile-time.md:19 -msgid "" -"You can use [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." -"html#method.leak) to leak a pointer. A use of this could be to get runtime-" -"initialized and runtime-sized static variables" +#: src/types-and-values.md:9 +msgid "[Exercise: Fibonacci](./types-and-values/exercise.md) (30 minutes)" msgstr "" -#: src/why-rust/compile-time.md:21 -msgid "" -"You can use [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." -"html) to make the compiler \"forget\" about a value (meaning the destructor " -"is never run)." +#: src/types-and-values.md:11 src/methods-and-traits.md:10 +#: src/unsafe-rust.md:12 +msgid "This segment should take about 1 hour and 5 minutes" msgstr "" -#: src/why-rust/compile-time.md:23 +#: src/types-and-values/variables.md:3 msgid "" -"You can also accidentally create a [reference cycle](https://doc.rust-lang." -"org/book/ch15-06-reference-cycles.html) with `Rc` or `Arc`." +"Rust provides type safety via static typing. Variable bindings are made with " +"`let`:" msgstr "" -#: src/why-rust/compile-time.md:25 +#: src/types-and-values/variables.md:9 src/control-flow-basics/loops.md:29 +#: src/control-flow-basics/break-continue.md:33 +#: src/control-flow-basics/blocks-and-scopes.md:17 +#, fuzzy +msgid "\"x: {x}\"" +msgstr "\"{x}\"" + +#: src/types-and-values/variables.md:10 msgid "" -"In fact, some will consider infinitely populating a collection a memory leak " -"and Rust does not protect from those." +"// x = 20;\n" +" // println!(\"x: {x}\");\n" msgstr "" -#: src/why-rust/compile-time.md:28 +#: src/types-and-values/variables.md:18 msgid "" -"For the purpose of this course, \"No memory leaks\" should be understood as " -"\"Pretty much no _accidental_ memory leaks\"." +"Uncomment the `x = 20` to demonstrate that variables are immutable by " +"default. Add the `mut` keyword to allow changes." msgstr "" -#: src/why-rust/runtime.md:3 -msgid "No undefined behavior at runtime:" +#: src/types-and-values/variables.md:21 +msgid "" +"The `i32` here is the type of the variable. This must be known at compile " +"time, but type inference (covered later) allows the programmer to omit it in " +"many cases." msgstr "" -#: src/why-rust/runtime.md:5 -msgid "Array access is bounds checked." +#: src/types-and-values/values.md:3 +msgid "" +"Here are some basic built-in types, and the syntax for literal values of " +"each type." msgstr "" -#: src/why-rust/runtime.md:6 -msgid "Integer overflow is defined (panic or wrap-around)." +#: src/types-and-values/values.md:5 +#: src/tuples-and-arrays/tuples-and-arrays.md:7 src/unsafe-rust/exercise.md:16 +msgid "Types" msgstr "" -#: src/why-rust/runtime.md:12 -msgid "" -"Integer overflow is defined via the [`overflow-checks`](https://doc.rust-" -"lang.org/rustc/codegen-options/index.html#overflow-checks) compile-time " -"flag. If enabled, the program will panic (a controlled crash of the " -"program), otherwise you get wrap-around semantics. By default, you get " -"panics in debug mode (`cargo build`) and wrap-around in release mode (`cargo " -"build --release`)." +#: src/types-and-values/values.md:5 +#: src/tuples-and-arrays/tuples-and-arrays.md:7 +msgid "Literals" msgstr "" -#: src/why-rust/runtime.md:18 -msgid "" -"Bounds checking cannot be disabled with a compiler flag. It can also not be " -"disabled directly with the `unsafe` keyword. However, `unsafe` allows you to " -"call functions such as `slice::get_unchecked` which does not do bounds " -"checking." +#: src/types-and-values/values.md:7 +msgid "Signed integers" msgstr "" -#: src/why-rust/modern.md:3 -msgid "Rust is built with all the experience gained in the last decades." +#: src/types-and-values/values.md:7 +msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" msgstr "" -#: src/why-rust/modern.md:5 -msgid "Language Features" +#: src/types-and-values/values.md:7 +msgid "`-10`, `0`, `1_000`, `123_i64`" msgstr "" -#: src/why-rust/modern.md:7 -msgid "Enums and pattern matching." +#: src/types-and-values/values.md:8 +msgid "Unsigned integers" msgstr "" -#: src/why-rust/modern.md:8 -msgid "Generics." +#: src/types-and-values/values.md:8 +msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" msgstr "" -#: src/why-rust/modern.md:9 -msgid "No overhead FFI." +#: src/types-and-values/values.md:8 +msgid "`0`, `123`, `10_u16`" msgstr "" -#: src/why-rust/modern.md:10 -msgid "Zero-cost abstractions." +#: src/types-and-values/values.md:9 +msgid "Floating point numbers" msgstr "" -#: src/why-rust/modern.md:12 -msgid "Tooling" +#: src/types-and-values/values.md:9 +msgid "`f32`, `f64`" msgstr "" -#: src/why-rust/modern.md:14 -msgid "Great compiler errors." +#: src/types-and-values/values.md:9 +msgid "`3.14`, `-10.0e20`, `2_f32`" msgstr "" -#: src/why-rust/modern.md:15 -msgid "Built-in dependency manager." +#: src/types-and-values/values.md:10 +msgid "Unicode scalar values" msgstr "" -#: src/why-rust/modern.md:16 -msgid "Built-in support for testing." +#: src/types-and-values/values.md:10 +msgid "`char`" msgstr "" -#: src/why-rust/modern.md:17 -msgid "Excellent Language Server Protocol support." +#: src/types-and-values/values.md:10 +msgid "`'a'`, `'α'`, `'∞'`" msgstr "" -#: src/why-rust/modern.md:23 -msgid "" -"Zero-cost abstractions, similar to C++, means that you don't have to 'pay' " -"for higher-level programming constructs with memory or CPU. For example, " -"writing a loop using `for` should result in roughly the same low level " -"instructions as using the `.iter().fold()` construct." +#: src/types-and-values/values.md:11 +msgid "Booleans" msgstr "" -#: src/why-rust/modern.md:28 -msgid "" -"It may be worth mentioning that Rust enums are 'Algebraic Data Types', also " -"known as 'sum types', which allow the type system to express things like " -"`Option` and `Result`." +#: src/types-and-values/values.md:11 +msgid "`bool`" msgstr "" -#: src/why-rust/modern.md:32 -msgid "" -"Remind people to read the errors --- many developers have gotten used to " -"ignore lengthy compiler output. The Rust compiler is significantly more " -"talkative than other compilers. It will often provide you with _actionable_ " -"feedback, ready to copy-paste into your code." +#: src/types-and-values/values.md:11 +msgid "`true`, `false`" msgstr "" -#: src/why-rust/modern.md:37 -msgid "" -"The Rust standard library is small compared to languages like Java, Python, " -"and Go. Rust does not come with several things you might consider standard " -"and essential:" +#: src/types-and-values/values.md:13 +msgid "The types have widths as follows:" msgstr "" -#: src/why-rust/modern.md:41 -msgid "a random number generator, but see [rand](https://docs.rs/rand/)." +#: src/types-and-values/values.md:15 +msgid "`iN`, `uN`, and `fN` are _N_ bits wide," msgstr "" -#: src/why-rust/modern.md:42 -msgid "support for SSL or TLS, but see [rusttls](https://docs.rs/rustls/)." +#: src/types-and-values/values.md:16 +msgid "`isize` and `usize` are the width of a pointer," msgstr "" -#: src/why-rust/modern.md:43 -msgid "support for JSON, but see [serde_json](https://docs.rs/serde_json/)." +#: src/types-and-values/values.md:17 +msgid "`char` is 32 bits wide," msgstr "" -#: src/why-rust/modern.md:45 -msgid "" -"The reasoning behind this is that functionality in the standard library " -"cannot go away, so it has to be very stable. For the examples above, the " -"Rust community is still working on finding the best solution --- and perhaps " -"there isn't a single \"best solution\" for some of these things." +#: src/types-and-values/values.md:18 +msgid "`bool` is 8 bits wide." msgstr "" -#: src/why-rust/modern.md:50 -msgid "" -"Rust comes with a built-in package manager in the form of Cargo and this " -"makes it trivial to download and compile third-party crates. A consequence " -"of this is that the standard library can be smaller." +#: src/types-and-values/values.md:23 +msgid "There are a few syntaxes which are not shown above:" msgstr "" -#: src/why-rust/modern.md:54 +#: src/types-and-values/values.md:25 msgid "" -"Discovering good third-party crates can be a problem. Sites like help with this by letting you compare health metrics for crates to " -"find a good and trusted one." +"All underscores in numbers can be left out, they are for legibility only. So " +"`1_000` can be written as `1000` (or `10_00`), and `123_i64` can be written " +"as `123i64`." msgstr "" -#: src/why-rust/modern.md:58 -msgid "" -"[rust-analyzer](https://rust-analyzer.github.io/) is a well supported LSP " -"implementation used in major IDEs and text editors." -msgstr "" +#: src/types-and-values/arithmetic.md:9 +#, fuzzy +msgid "\"result: {}\"" +msgstr "\"result: {:?}\"" -#: src/basic-syntax.md:3 -msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" +#: src/types-and-values/arithmetic.md:16 +msgid "" +"This is the first time we've seen a function other than `main`, but the " +"meaning should be clear: it takes three integers, and returns an integer. " +"Functions will be covered in more detail later." msgstr "" -#: src/basic-syntax.md:5 -msgid "Blocks and scopes are delimited by curly braces." +#: src/types-and-values/arithmetic.md:20 +msgid "Arithmetic is very similar to other languages, with similar precedence." msgstr "" -#: src/basic-syntax.md:6 +#: src/types-and-values/arithmetic.md:22 msgid "" -"Line comments are started with `//`, block comments are delimited by `/* ... " -"*/`." +"What about integer overflow? In C and C++ overflow of _signed_ integers is " +"actually undefined, and might do different things on different platforms or " +"compilers. In Rust, it's defined." msgstr "" -#: src/basic-syntax.md:8 -msgid "Keywords like `if` and `while` work the same." +#: src/types-and-values/arithmetic.md:26 +msgid "" +"Change the `i32`'s to `i16` to see an integer overflow, which panics " +"(checked) in a debug build and wraps in a release build. There are other " +"options, such as overflowing, saturating, and carrying. These are accessed " +"with method syntax, e.g., `(a * b).saturating_add(b * c).saturating_add(c * " +"a)`." msgstr "" -#: src/basic-syntax.md:9 -msgid "Variable assignment is done with `=`, comparison is done with `==`." +#: src/types-and-values/arithmetic.md:31 +msgid "" +"In fact, the compiler will detect overflow of constant expressions, which is " +"why the example requires a separate function." msgstr "" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Types" +#: src/types-and-values/strings.md:3 +msgid "" +"Rust has two types to represent strings, both of which will be covered in " +"more depth later. Both _always_ store UTF-8 encoded strings." msgstr "" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 -msgid "Literals" +#: src/types-and-values/strings.md:6 +msgid "`String` - a modifiable, owned string." msgstr "" -#: src/basic-syntax/scalar-types.md:5 -msgid "Signed integers" +#: src/types-and-values/strings.md:7 +msgid "`&str` - a read-only string. String literals have this type." msgstr "" -#: src/basic-syntax/scalar-types.md:5 -msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" -msgstr "" +#: src/types-and-values/strings.md:11 +#, fuzzy +msgid "\"Greetings\"" +msgstr "\"greetings\"" -#: src/basic-syntax/scalar-types.md:5 -msgid "`-10`, `0`, `1_000`, `123_i64`" +#: src/types-and-values/strings.md:12 +msgid "\"🪐\"" msgstr "" -#: src/basic-syntax/scalar-types.md:6 -msgid "Unsigned integers" +#: src/types-and-values/strings.md:15 +msgid "\", \"" msgstr "" -#: src/basic-syntax/scalar-types.md:6 -msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" -msgstr "" +#: src/types-and-values/strings.md:17 +#, fuzzy +msgid "\"final sentence: {}\"" +msgstr "\"indre blok: {a}\"" -#: src/basic-syntax/scalar-types.md:6 -msgid "`0`, `123`, `10_u16`" -msgstr "" +#: src/types-and-values/strings.md:18 src/async/control-flow/join.md:30 +msgid "\"{:?}\"" +msgstr "\"{:?}\"" -#: src/basic-syntax/scalar-types.md:7 -msgid "Floating point numbers" +#: src/types-and-values/strings.md:19 +msgid "//println!(\"{:?}\", &sentence[12..13]);\n" msgstr "" -#: src/basic-syntax/scalar-types.md:7 -msgid "`f32`, `f64`" +#: src/types-and-values/strings.md:26 +msgid "" +"This slide introduces strings. Everything here will be covered in more depth " +"later, but this is enough for subsequent slides and exercises to use strings." msgstr "" -#: src/basic-syntax/scalar-types.md:7 -msgid "`3.14`, `-10.0e20`, `2_f32`" +#: src/types-and-values/strings.md:29 +msgid "Invalid UTF-8 in a string is UB, and this not allowed in safe Rust." msgstr "" -#: src/basic-syntax/scalar-types.md:8 -msgid "Strings" +#: src/types-and-values/strings.md:31 +msgid "" +"`String` is a user-defined type with a constructor (`::new()`) and methods " +"like `s.push_str(..)`." msgstr "" -#: src/basic-syntax/scalar-types.md:8 -msgid "`&str`" +#: src/types-and-values/strings.md:33 +msgid "" +"The `&` in `&str` indicates that this is a reference. We will cover " +"references later, so for now just think of `&str` as a unit meaning \"a read-" +"only string\"." msgstr "" -#: src/basic-syntax/scalar-types.md:8 -msgid "`\"foo\"`, `\"two\\nlines\"`" +#: src/types-and-values/strings.md:36 +msgid "" +"The commented-out line is indexing into the string by byte position. " +"`12..13` does not end on a character boundary, so the program panics. Adjust " +"it to a range that does, based on the error message." msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "Unicode scalar values" +#: src/types-and-values/strings.md:40 +msgid "" +"Raw strings allow you to create a `&str` value with escapes disabled: " +"`r\"\\n\" == \"\\\\n\"`. You can embed double-quotes by using an equal " +"amount of `#` on either side of the quotes:" msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "`char`" +#: src/types-and-values/inference.md:3 +msgid "Rust will look at how the variable is _used_ to determine the type:" msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "`'a'`, `'α'`, `'∞'`" +#: src/types-and-values/inference.md:28 +msgid "" +"This slide demonstrates how the Rust compiler infers types based on " +"constraints given by variable declarations and usages." msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "Booleans" +#: src/types-and-values/inference.md:30 +msgid "" +"It is very important to emphasize that variables declared like this are not " +"of some sort of dynamic \"any type\" that can hold any data. The machine " +"code generated by such declaration is identical to the explicit declaration " +"of a type. The compiler does the job for us and helps us write more concise " +"code." msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "`bool`" +#: src/types-and-values/inference.md:34 +msgid "" +"When nothing constrains the type of an integer literal, Rust defaults to " +"`i32`. This sometimes appears as `{integer}` in error messages. Similarly, " +"floating-point literals default to `f64`." msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "`true`, `false`" +#: src/types-and-values/inference.md:43 +msgid "// ERROR: no implementation for `{float} == {integer}`\n" msgstr "" -#: src/basic-syntax/scalar-types.md:12 -msgid "The types have widths as follows:" +#: src/types-and-values/exercise.md:3 +msgid "" +"The first and second Fibonacci numbers are both `1`. For n>2, he n'th " +"Fibonacci number is calculated recursively as the sum of the n-1'th and " +"n-2'th Fibonacci numbers." msgstr "" -#: src/basic-syntax/scalar-types.md:14 -msgid "`iN`, `uN`, and `fN` are _N_ bits wide," +#: src/types-and-values/exercise.md:7 +msgid "" +"Write a function `fib(n)` that calculates the n'th Fibonacci number. When " +"will this function panic?" msgstr "" -#: src/basic-syntax/scalar-types.md:15 -msgid "`isize` and `usize` are the width of a pointer," +#: src/types-and-values/exercise.md:13 +msgid "// The base case.\n" msgstr "" -#: src/basic-syntax/scalar-types.md:16 -msgid "`char` is 32 bits wide," +#: src/types-and-values/exercise.md:14 src/types-and-values/exercise.md:17 +#: src/control-flow-basics/exercise.md:26 +#: src/control-flow-basics/exercise.md:30 +msgid "\"Implement this\"" msgstr "" -#: src/basic-syntax/scalar-types.md:17 -msgid "`bool` is 8 bits wide." +#: src/types-and-values/exercise.md:16 +msgid "// The recursive case.\n" msgstr "" -#: src/basic-syntax/scalar-types.md:21 -msgid "There are a few syntaxes which are not shown above:" -msgstr "" +#: src/types-and-values/exercise.md:23 src/types-and-values/solution.md:14 +#, fuzzy +msgid "\"fib(n) = {}\"" +msgstr "\"fib({i}): {n}\"" -#: src/basic-syntax/scalar-types.md:23 -msgid "" -"Raw strings allow you to create a `&str` value with escapes disabled: " -"`r\"\\n\" == \"\\\\n\"`. You can embed double-quotes by using an equal " -"amount of `#` on either side of the quotes:" +#: src/control-flow-basics.md:4 +msgid "[Conditionals](./control-flow-basics/conditionals.md) (5 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:35 -msgid "Byte strings allow you to create a `&[u8]` value directly:" +#: src/control-flow-basics.md:5 +msgid "[Loops](./control-flow-basics/loops.md) (5 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:45 +#: src/control-flow-basics.md:6 msgid "" -"All underscores in numbers can be left out, they are for legibility only. So " -"`1_000` can be written as `1000` (or `10_00`), and `123_i64` can be written " -"as `123i64`." +"[break and continue](./control-flow-basics/break-continue.md) (5 minutes)" msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "Arrays" +#: src/control-flow-basics.md:7 +msgid "" +"[Blocks and Scopes](./control-flow-basics/blocks-and-scopes.md) (10 minutes)" msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "`[T; N]`" +#: src/control-flow-basics.md:8 +msgid "[Functions](./control-flow-basics/functions.md) (3 minutes)" msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "`[20, 30, 40]`, `[0; 3]`" +#: src/control-flow-basics.md:9 +msgid "[Macros](./control-flow-basics/macros.md) (2 minutes)" msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "Tuples" +#: src/control-flow-basics.md:10 +msgid "" +"[Exercise: Collatz conjecture](./control-flow-basics/exercise.md) (30 " +"minutes)" msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "`()`, `(T,)`, `(T1, T2)`, ..." +#: src/control-flow-basics.md:12 src/tuples-and-arrays.md:10 src/borrowing.md:9 +#: src/testing.md:11 +msgid "This segment should take about 1 hour" msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "`()`, `('x',)`, `('x', 1.2)`, ..." +#: src/control-flow-basics/conditionals.md:3 +msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" msgstr "" -#: src/basic-syntax/compound-types.md:8 -msgid "Array assignment and access:" +#: src/control-flow-basics/conditionals.md:5 +msgid "Blocks are delimited by curly braces." msgstr "" -#: src/basic-syntax/compound-types.md:19 -msgid "Tuple assignment and access:" +#: src/control-flow-basics/conditionals.md:6 +msgid "" +"Line comments are started with `//`, block comments are delimited by `/* ... " +"*/`." msgstr "" -#: src/basic-syntax/compound-types.md:34 -msgid "Arrays:" +#: src/control-flow-basics/conditionals.md:8 +msgid "Keywords like `if` and `while` work the same." msgstr "" -#: src/basic-syntax/compound-types.md:36 -msgid "" -"A value of the array type `[T; N]` holds `N` (a compile-time constant) " -"elements of the same type `T`. Note that the length of the array is _part of " -"its type_, which means that `[u8; 3]` and `[u8; 4]` are considered two " -"different types." +#: src/control-flow-basics/conditionals.md:9 +msgid "Variable assignment is done with `=`, comparison is done with `==`." msgstr "" -#: src/basic-syntax/compound-types.md:40 -msgid "We can use literals to assign values to arrays." +#: src/control-flow-basics/conditionals.md:11 +msgid "`if` expressions" msgstr "" -#: src/basic-syntax/compound-types.md:42 +#: src/control-flow-basics/conditionals.md:13 msgid "" -"In the main function, the print statement asks for the debug implementation " -"with the `?` format parameter: `{}` gives the default output, `{:?}` gives " -"the debug output. We could also have used `{a}` and `{a:?}` without " -"specifying the value after the format string." +"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" +"if-expr.html#if-expressions) exactly like `if` statements in other languages:" msgstr "" -#: src/basic-syntax/compound-types.md:47 -msgid "" -"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " -"easier to read." +#: src/control-flow-basics/conditionals.md:21 +#: src/control-flow-basics/conditionals.md:38 +msgid "\"small\"" msgstr "" -#: src/basic-syntax/compound-types.md:49 -msgid "Tuples:" +#: src/control-flow-basics/conditionals.md:23 +msgid "\"biggish\"" msgstr "" -#: src/basic-syntax/compound-types.md:51 -msgid "Like arrays, tuples have a fixed length." +#: src/control-flow-basics/conditionals.md:25 +msgid "\"huge\"" msgstr "" -#: src/basic-syntax/compound-types.md:53 -msgid "Tuples group together values of different types into a compound type." +#: src/control-flow-basics/conditionals.md:30 +msgid "" +"In addition, you can use `if` as an expression. The last expression of each " +"block becomes the value of the `if` expression:" msgstr "" -#: src/basic-syntax/compound-types.md:55 -msgid "" -"Fields of a tuple can be accessed by the period and the index of the value, " -"e.g. `t.0`, `t.1`." +#: src/control-flow-basics/conditionals.md:40 +msgid "\"large\"" msgstr "" -#: src/basic-syntax/compound-types.md:57 +#: src/control-flow-basics/conditionals.md:42 +#, fuzzy +msgid "\"number size: {}\"" +msgstr "\"{numbers:?}\"" + +#: src/control-flow-basics/conditionals.md:49 msgid "" -"The empty tuple `()` is also known as the \"unit type\". It is both a type, " -"and the only valid value of that type - that is to say both the type and its " -"value are expressed as `()`. It is used to indicate, for example, that a " -"function or expression has no return value, as we'll see in a future slide. " +"Because `if` is an expression and must have a particular type, both of its " +"branch blocks must have the same type. Show what happens if you add `;` " +"after `\"small\"` in the second example." msgstr "" -#: src/basic-syntax/compound-types.md:61 +#: src/control-flow-basics/conditionals.md:51 msgid "" -"You can think of it as `void` that can be familiar to you from other " -"programming languages." +"When `if` is used in an expression, the expression must have a `;` to " +"separate it from the next statement. Remove the `;` before `println!` to see " +"the compiler error." msgstr "" -#: src/basic-syntax/references.md:3 -msgid "Like C++, Rust has references:" +#: src/control-flow-basics/loops.md:3 +msgid "There are three looping keywords in Rust: `while`, `loop`, and `for`:" msgstr "" -#: src/basic-syntax/references.md:15 -msgid "Some notes:" +#: src/control-flow-basics/loops.md:5 +msgid "`while`" msgstr "" -#: src/basic-syntax/references.md:17 +#: src/control-flow-basics/loops.md:7 msgid "" -"We must dereference `ref_x` when assigning to it, similar to C and C++ " -"pointers." +"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" +"expr.html#predicate-loops) works much like in other languages, executing the " +"loop body as long as the condition is true." msgstr "" -#: src/basic-syntax/references.md:18 -msgid "" -"Rust will auto-dereference in some cases, in particular when invoking " -"methods (try `ref_x.count_ones()`)." -msgstr "" +#: src/control-flow-basics/loops.md:17 +#, fuzzy +msgid "\"Final x: {x}\"" +msgstr "\" -> {x}\"" -#: src/basic-syntax/references.md:20 -msgid "" -"References that are declared as `mut` can be bound to different values over " -"their lifetime." -msgstr "" +#: src/control-flow-basics/loops.md:21 +#, fuzzy +msgid "`for`" +msgstr "`for`\\-løkker" -#: src/basic-syntax/references.md:26 +#: src/control-flow-basics/loops.md:23 msgid "" -"Be sure to note the difference between `let mut ref_x: &i32` and `let ref_x: " -"&mut i32`. The first one represents a mutable reference which can be bound " -"to different values, while the second represents a reference to a mutable " -"value." -msgstr "" - -#: src/basic-syntax/references-dangling.md:3 -msgid "Rust will statically forbid dangling references:" +"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) iterates " +"over ranges of values:" msgstr "" -#: src/basic-syntax/references-dangling.md:17 -msgid "A reference is said to \"borrow\" the value it refers to." +#: src/control-flow-basics/loops.md:34 +msgid "`loop`" msgstr "" -#: src/basic-syntax/references-dangling.md:18 +#: src/control-flow-basics/loops.md:36 msgid "" -"Rust is tracking the lifetimes of all references to ensure they live long " -"enough." +"The [`loop` statement](https://doc.rust-lang.org/std/keyword.loop.html) just " +"loops forever, until a `break`." msgstr "" -#: src/basic-syntax/references-dangling.md:20 -msgid "We will talk more about borrowing when we get to ownership." +#: src/control-flow-basics/loops.md:44 +msgid "\"{i}\"" msgstr "" -#: src/basic-syntax/slices.md:3 -msgid "A slice gives you a view into a larger collection:" +#: src/control-flow-basics/loops.md:55 +msgid "" +"We will discuss iteration later; for now, just stick to range expressions." msgstr "" -#: src/basic-syntax/slices.md:17 -msgid "Slices borrow data from the sliced type." +#: src/control-flow-basics/loops.md:56 +msgid "" +"Note that the `for` loop only iterates to `4`. Show the `1..=5` syntax for " +"an inclusive range." msgstr "" -#: src/basic-syntax/slices.md:18 -msgid "Question: What happens if you modify `a[3]` right before printing `s`?" +#: src/control-flow-basics/break-continue.md:3 +msgid "" +"If you want to exit any kind of loop early, use [`break`](https://doc.rust-" +"lang.org/reference/expressions/loop-expr.html#break-expressions). For " +"`loop`, this can take an optional expression that becomes the value of the " +"`loop` expression." msgstr "" -#: src/basic-syntax/slices.md:22 +#: src/control-flow-basics/break-continue.md:7 msgid "" -"We create a slice by borrowing `a` and specifying the starting and ending " -"indexes in brackets." +"If you want to immediately start the next iteration use [`continue`](https://" +"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." msgstr "" -#: src/basic-syntax/slices.md:24 +#: src/control-flow-basics/break-continue.md:23 +#, fuzzy +msgid "\"{result}\"" +msgstr "\"result: {:?}\"" + +#: src/control-flow-basics/break-continue.md:27 msgid "" -"If the slice starts at index 0, Rust’s range syntax allows us to drop the " -"starting index, meaning that `&a[0..a.len()]` and `&a[..a.len()]` are " -"identical." +"Both `continue` and `break` can optionally take a label argument which is " +"used to break out of nested loops:" msgstr "" -#: src/basic-syntax/slices.md:26 +#: src/control-flow-basics/break-continue.md:36 +#, fuzzy +msgid "\"x: {x}, i: {i}\"" +msgstr "\"{x}, {abs_x}\"" + +#: src/control-flow-basics/break-continue.md:46 msgid "" -"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " -"identical." +"In this case we break the outer loop after 3 iterations of the inner loop." msgstr "" -#: src/basic-syntax/slices.md:28 +#: src/control-flow-basics/break-continue.md:51 msgid "" -"To easily create a slice of the full array, we can therefore use `&a[..]`." +"Note that `loop` is the only looping construct which returns a non-trivial " +"value. This is because it's guaranteed to be entered at least once (unlike " +"`while` and `for` loops)." msgstr "" -#: src/basic-syntax/slices.md:30 +#: src/control-flow-basics/blocks-and-scopes.md:3 +msgid "Blocks" +msgstr "Blokke" + +#: src/control-flow-basics/blocks-and-scopes.md:5 msgid "" -"`s` is a reference to a slice of `i32`s. Notice that the type of `s` " -"(`&[i32]`) no longer mentions the array length. This allows us to perform " -"computation on slices of different sizes." +"A block in Rust contains a sequence of expressions. Each block has a value " +"and a type, which are those of the last expression of the block:" msgstr "" -#: src/basic-syntax/slices.md:32 -msgid "" -"Slices always borrow from another object. In this example, `a` has to remain " -"'alive' (in scope) for at least as long as our slice. " +#: src/control-flow-basics/blocks-and-scopes.md:14 +msgid "\"y: {y}\"" msgstr "" -#: src/basic-syntax/slices.md:34 +#: src/control-flow-basics/blocks-and-scopes.md:21 msgid "" -"The question about modifying `a[3]` can spark an interesting discussion, but " -"the answer is that for memory safety reasons you cannot do it through `a` at " -"this point in the execution, but you can read the data from both `a` and `s` " -"safely. It works before you created the slice, and again after the " -"`println`, when the slice is no longer used. More details will be explained " -"in the borrow checker section." +"If the last expression ends with `;`, then the resulting value and type is " +"`()`." msgstr "" -#: src/basic-syntax/string-slices.md:1 -msgid "`String` vs `str`" -msgstr "" +#: src/control-flow-basics/blocks-and-scopes.md:23 +msgid "Scopes and Shadowing" +msgstr "Virkefelt og overskyggede variabler" -#: src/basic-syntax/string-slices.md:3 -msgid "We can now understand the two string types in Rust:" +#: src/control-flow-basics/blocks-and-scopes.md:25 +msgid "A variable's scope is limited to the enclosing block." msgstr "" -#: src/basic-syntax/string-slices.md:7 src/traits/read-write.md:36 -#: src/testing/test-modules.md:12 -msgid "\"World\"" -msgstr "\"Verden\"" +#: src/control-flow-basics/blocks-and-scopes.md:27 +msgid "" +"You can shadow variables, both those from outer scopes and variables from " +"the same scope:" +msgstr "" -#: src/basic-syntax/string-slices.md:8 -msgid "\"s1: {s1}\"" -msgstr "\"s1: {s1}\"" +#: src/control-flow-basics/blocks-and-scopes.md:33 +msgid "\"before: {a}\"" +msgstr "\"før: {a}\"" -#: src/basic-syntax/string-slices.md:10 src/memory-management/scope-based.md:16 -#: src/memory-management/garbage-collection.md:15 -msgid "\"Hello \"" -msgstr "\"Hallo \"" +#: src/control-flow-basics/blocks-and-scopes.md:35 +#: src/std-traits/from-and-into.md:7 src/std-traits/from-and-into.md:19 +#: src/slices-and-lifetimes/solution.md:216 +msgid "\"hello\"" +msgstr "\"hallo\"" -#: src/basic-syntax/string-slices.md:11 src/basic-syntax/string-slices.md:13 -#: src/ownership/move-semantics.md:9 -msgid "\"s2: {s2}\"" -msgstr "\"s2: {s2}\"" +#: src/control-flow-basics/blocks-and-scopes.md:36 +msgid "\"inner scope: {a}\"" +msgstr "\"indre blok: {a}\"" -#: src/basic-syntax/string-slices.md:16 -msgid "\"s3: {s3}\"" -msgstr "\"s3: {s3}\"" +#: src/control-flow-basics/blocks-and-scopes.md:39 +msgid "\"shadowed in inner scope: {a}\"" +msgstr "\"overskygget i indre blok: {a}\"" -#: src/basic-syntax/string-slices.md:20 -msgid "Rust terminology:" -msgstr "" +#: src/control-flow-basics/blocks-and-scopes.md:42 +msgid "\"after: {a}\"" +msgstr "\"efter: {a}\"" -#: src/basic-syntax/string-slices.md:22 -msgid "`&str` an immutable reference to a string slice." +#: src/control-flow-basics/blocks-and-scopes.md:49 +msgid "" +"You can show how the value of the block changes by changing the last line in " +"the block. For instance, adding/removing a semicolon or using a `return`." msgstr "" -#: src/basic-syntax/string-slices.md:23 -msgid "`String` a mutable string buffer." +#: src/control-flow-basics/blocks-and-scopes.md:50 +msgid "" +"Show that a variable's scope is limited by adding a b\\` in the inner block " +"in the last example, and then trying to access it outside that block." msgstr "" -#: src/basic-syntax/string-slices.md:27 +#: src/control-flow-basics/blocks-and-scopes.md:51 msgid "" -"`&str` introduces a string slice, which is an immutable reference to UTF-8 " -"encoded string data stored in a block of memory. String literals " -"(`”Hello”`), are stored in the program’s binary." +"Shadowing is different from mutation, because after shadowing both " +"variable's memory locations exist at the same time. Both are available under " +"the same name, depending where you use it in the code." msgstr "" -#: src/basic-syntax/string-slices.md:30 -msgid "" -"Rust’s `String` type is a wrapper around a vector of bytes. As with a " -"`Vec`, it is owned." +#: src/control-flow-basics/blocks-and-scopes.md:52 +msgid "A shadowing variable can have a different type." msgstr "" -#: src/basic-syntax/string-slices.md:32 +#: src/control-flow-basics/blocks-and-scopes.md:53 msgid "" -"As with many other types `String::from()` creates a string from a string " -"literal; `String::new()` creates a new empty string, to which string data " -"can be added using the `push()` and `push_str()` methods." +"Shadowing looks obscure at first, but is convenient for holding on to values " +"after `.unwrap()`." msgstr "" -#: src/basic-syntax/string-slices.md:35 +#: src/control-flow-basics/functions.md:21 msgid "" -"The `format!()` macro is a convenient way to generate an owned string from " -"dynamic values. It accepts the same format specification as `println!()`." +"Declaration parameters are followed by a type (the reverse of some " +"programming languages), then a return type." msgstr "" -#: src/basic-syntax/string-slices.md:38 +#: src/control-flow-basics/functions.md:22 msgid "" -"You can borrow `&str` slices from `String` via `&` and optionally range " -"selection." +"The last expression in a function body (or any block) becomes the return " +"value. Simply omit the `;` at the end of the expression. The `return` " +"keyword can be used for early return, but the \"bare value\" form is " +"idiomatic at the end of a function (refactor `gcd` to use a `return`)." msgstr "" -#: src/basic-syntax/string-slices.md:40 +#: src/control-flow-basics/functions.md:24 msgid "" -"For C++ programmers: think of `&str` as `const char*` from C++, but the one " -"that always points to a valid string in memory. Rust `String` is a rough " -"equivalent of `std::string` from C++ (main difference: it can only contain " -"UTF-8 encoded bytes and will never use a small-string optimization)." +"Some functions have no return value, and return the 'unit type', `()`. The " +"compiler will infer this if the `-> ()` return type is omitted." msgstr "" -#: src/basic-syntax/functions.md:3 +#: src/control-flow-basics/functions.md:25 msgid "" -"A Rust version of the famous [FizzBuzz](https://en.wikipedia.org/wiki/" -"Fizz_buzz) interview question:" +"Overloading is not supported -- each function has a single implementation." msgstr "" -#: src/basic-syntax/functions.md:36 +#: src/control-flow-basics/functions.md:26 msgid "" -"We refer in `main` to a function written below. Neither forward declarations " -"nor headers are necessary. " +"Always takes a fixed number of parameters. Default arguments are not " +"supported. Macros can be used to support variadic functions." msgstr "" -#: src/basic-syntax/functions.md:37 +#: src/control-flow-basics/functions.md:27 msgid "" -"Declaration parameters are followed by a type (the reverse of some " -"programming languages), then a return type." +"Always takes a single set of parameter types. These types can be generic, " +"which will be covered later." msgstr "" -#: src/basic-syntax/functions.md:38 +#: src/control-flow-basics/macros.md:3 msgid "" -"The last expression in a function body (or any block) becomes the return " -"value. Simply omit the `;` at the end of the expression." +"Macros are expanded into Rust code during compilation, and can take a " +"variable number of arguments. They are distinguished by a `!` at the end. " +"The Rust standard library includes an assortment of useful macros." msgstr "" -#: src/basic-syntax/functions.md:39 +#: src/control-flow-basics/macros.md:7 msgid "" -"Some functions have no return value, and return the 'unit type', `()`. The " -"compiler will infer this if the `-> ()` return type is omitted." +"`println!(format, ..)` prints a line to standard output, applying formatting " +"described in [`std::fmt`](https://doc.rust-lang.org/std/fmt/index.html)." msgstr "" -#: src/basic-syntax/functions.md:40 +#: src/control-flow-basics/macros.md:8 msgid "" -"The range expression in the `for` loop in `print_fizzbuzz_to()` contains " -"`=n`, which causes it to include the upper bound." +"`format!(format, ..)` works just like `println!` but returns the result as a " +"string." msgstr "" -#: src/basic-syntax/rustdoc.md:3 -msgid "" -"All language items in Rust can be documented using special `///` syntax." +#: src/control-flow-basics/macros.md:9 +msgid "`dbg!(expression)` logs the value of the expression and returns it." msgstr "" -#: src/basic-syntax/rustdoc.md:6 +#: src/control-flow-basics/macros.md:10 msgid "" -"/// Determine whether the first argument is divisible by the second " -"argument.\n" -"///\n" -"/// If the second argument is zero, the result is false.\n" +"`todo!()` marks a bit of code as not-yet-implemented. If executed, it will " +"panic." msgstr "" -#: src/basic-syntax/rustdoc.md:11 -msgid "// Corner case, early return\n" +#: src/control-flow-basics/macros.md:11 +msgid "" +"`unreachable!()` marks a bit of code as unreachable. If executed, it will " +"panic." msgstr "" -#: src/basic-syntax/rustdoc.md:13 -msgid "// The last expression in a block is the return value\n" -msgstr "" +#: src/control-flow-basics/macros.md:28 +#, fuzzy +msgid "\"{n}! = {}\"" +msgstr "\"{} {}\"" -#: src/basic-syntax/rustdoc.md:17 +#: src/control-flow-basics/macros.md:35 msgid "" -"The contents are treated as Markdown. All published Rust library crates are " -"automatically documented at [`docs.rs`](https://docs.rs) using the [rustdoc]" -"(https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is " -"idiomatic to document all public items in an API using this pattern." +"The takeaway from this section is that these common conveniences exist, and " +"how to use them. Why they are defined as macros, and what they expand to, is " +"not especially critical." msgstr "" -#: src/basic-syntax/rustdoc.md:24 +#: src/control-flow-basics/macros.md:39 msgid "" -"Show students the generated docs for the `rand` crate at [`docs.rs/rand`]" -"(https://docs.rs/rand)." +"The course does not cover defining macros, but a later section will describe " +"use of derive macros." msgstr "" -#: src/basic-syntax/rustdoc.md:27 -msgid "" -"This course does not include rustdoc on slides, just to save space, but in " -"real code they should be present." +#: src/control-flow-basics/exercise.md:1 +msgid "Exercise: Collatz Sequence" msgstr "" -#: src/basic-syntax/rustdoc.md:30 +#: src/control-flow-basics/exercise.md:3 msgid "" -"Inner doc comments are discussed later (in the page on modules) and need not " -"be addressed here." +"The [Collatz Sequence](https://en.wikipedia.org/wiki/Collatz_conjecture) is " +"defined as follows, for an arbitrary n" msgstr "" -#: src/basic-syntax/rustdoc.md:33 -msgid "" -"Rustdoc comments can contain code snippets that we can run and test using " -"`cargo test`. We will discuss these tests in the [Testing section](../" -"testing/doc-tests.html)." +#: src/control-flow-basics/exercise.md:4 src/control-flow-basics/exercise.md:10 +msgid "1" msgstr "" -#: src/basic-syntax/methods.md:3 -msgid "" -"Methods are functions associated with a type. The `self` argument of a " -"method is an instance of the type it is associated with:" +#: src/control-flow-basics/exercise.md:4 +msgid " greater than zero:" msgstr "" -#: src/basic-syntax/methods.md:24 -msgid "\"old area: {}\"" -msgstr "\"gammelt areal: {}\"" +#: src/control-flow-basics/exercise.md:6 src/control-flow-basics/exercise.md:7 +#: src/control-flow-basics/exercise.md:8 +msgid "If _n" +msgstr "" -#: src/basic-syntax/methods.md:26 -msgid "\"new area: {}\"" -msgstr "\"nyt areal: {}\"" +#: src/control-flow-basics/exercise.md:6 src/control-flow-basics/exercise.md:7 +#: src/control-flow-basics/exercise.md:8 +msgid "i" +msgstr "" -#: src/basic-syntax/methods.md:30 -msgid "" -"We will look much more at methods in today's exercise and in tomorrow's " -"class." +#: src/control-flow-basics/exercise.md:6 +msgid "_ is 1, then the sequence terminates at _n" msgstr "" -#: src/basic-syntax/methods.md:34 -msgid "Add a static method called `Rectangle::new` and call this from `main`:" +#: src/control-flow-basics/exercise.md:6 +msgid "_." msgstr "" -#: src/basic-syntax/methods.md:42 -msgid "" -"While _technically_, Rust does not have custom constructors, static methods " -"are commonly used to initialize structs (but don't have to). The actual " -"constructor, `Rectangle { width, height }`, could be called directly. See " -"the [Rustnomicon](https://doc.rust-lang.org/nomicon/constructors.html)." +#: src/control-flow-basics/exercise.md:7 +msgid "_ is even, then _n" msgstr "" -#: src/basic-syntax/methods.md:45 -msgid "" -"Add a `Rectangle::square(width: u32)` constructor to illustrate that such " -"static methods can take arbitrary parameters." +#: src/control-flow-basics/exercise.md:7 src/control-flow-basics/exercise.md:8 +msgid "i+1" msgstr "" -#: src/basic-syntax/functions-interlude.md:1 -msgid "Function Overloading" +#: src/control-flow-basics/exercise.md:7 +msgid " = n" msgstr "" -#: src/basic-syntax/functions-interlude.md:3 -msgid "Overloading is not supported:" +#: src/control-flow-basics/exercise.md:7 +msgid " / 2_." msgstr "" -#: src/basic-syntax/functions-interlude.md:5 -msgid "Each function has a single implementation:" +#: src/control-flow-basics/exercise.md:8 +msgid "_ is odd, then _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:6 -msgid "Always takes a fixed number of parameters." +#: src/control-flow-basics/exercise.md:8 +msgid " = 3 * n" msgstr "" -#: src/basic-syntax/functions-interlude.md:7 -msgid "Always takes a single set of parameter types." +#: src/control-flow-basics/exercise.md:8 +msgid " + 1_." msgstr "" -#: src/basic-syntax/functions-interlude.md:8 -msgid "Default values are not supported:" +#: src/control-flow-basics/exercise.md:10 +msgid "For example, beginning with _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:9 -msgid "All call sites have the same number of arguments." +#: src/control-flow-basics/exercise.md:10 +msgid "_ = 3:" msgstr "" -#: src/basic-syntax/functions-interlude.md:10 -msgid "Macros are sometimes used as an alternative." +#: src/control-flow-basics/exercise.md:11 +msgid "3 is odd, so _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:12 -msgid "However, function parameters can be generic:" +#: src/control-flow-basics/exercise.md:11 +msgid "2" msgstr "" -#: src/basic-syntax/functions-interlude.md:20 -msgid "\"coin toss: {}\"" -msgstr "\"mønt kast: {}\"" +#: src/control-flow-basics/exercise.md:11 +msgid "_ = 3 * 3 + 1 = 10;" +msgstr "" -#: src/basic-syntax/functions-interlude.md:20 -msgid "\"heads\"" -msgstr "\"plat\"" +#: src/control-flow-basics/exercise.md:12 +msgid "10 is even, so _n" +msgstr "" -#: src/basic-syntax/functions-interlude.md:20 -msgid "\"tails\"" -msgstr "\"krone\"" +#: src/control-flow-basics/exercise.md:12 src/bare-metal/aps/better-uart.md:22 +msgid "3" +msgstr "" -#: src/basic-syntax/functions-interlude.md:21 -msgid "\"cash prize: {}\"" -msgstr "\"pengepremie: {}\"" +#: src/control-flow-basics/exercise.md:12 +msgid "_ = 10 / 2 = 5;" +msgstr "" -#: src/basic-syntax/functions-interlude.md:27 -msgid "" -"When using generics, the standard library's `Into` can provide a kind of " -"limited polymorphism on argument types. We will see more details in a later " -"section." +#: src/control-flow-basics/exercise.md:13 +msgid "5 is odd, so _n" msgstr "" -#: src/exercises/day-1/morning.md:1 -msgid "Day 1: Morning Exercises" -msgstr "Dag 1: formiddagsøvelser" +#: src/control-flow-basics/exercise.md:13 src/bare-metal/aps/better-uart.md:10 +msgid "4" +msgstr "" -#: src/exercises/day-1/morning.md:3 -msgid "In these exercises, we will explore two parts of Rust:" +#: src/control-flow-basics/exercise.md:13 +msgid "_ = 3 * 15 + 1 = 16;" msgstr "" -#: src/exercises/day-1/morning.md:5 -msgid "Implicit conversions between types." +#: src/control-flow-basics/exercise.md:14 +msgid "16 is even, so _n" msgstr "" -#: src/exercises/day-1/morning.md:7 -msgid "Arrays and `for` loops." +#: src/control-flow-basics/exercise.md:14 +msgid "5" msgstr "" -#: src/exercises/day-1/morning.md:11 -msgid "A few things to consider while solving the exercises:" +#: src/control-flow-basics/exercise.md:14 +msgid "_ = 16 / 2 = 8;" msgstr "" -#: src/exercises/day-1/morning.md:13 -msgid "" -"Use a local Rust installation, if possible. This way you can get auto-" -"completion in your editor. See the page about [Using Cargo](../../cargo.md) " -"for details on installing Rust." +#: src/control-flow-basics/exercise.md:15 +msgid "8 is even, so _n" msgstr "" -#: src/exercises/day-1/morning.md:17 -msgid "Alternatively, use the Rust Playground." +#: src/control-flow-basics/exercise.md:15 src/bare-metal/aps/better-uart.md:14 +#: src/bare-metal/aps/better-uart.md:17 +msgid "6" msgstr "" -#: src/exercises/day-1/morning.md:19 -msgid "" -"The code snippets are not editable on purpose: the inline code snippets lose " -"their state if you navigate away from the page." +#: src/control-flow-basics/exercise.md:15 +msgid "_ = 8 / 2 = 4;" msgstr "" -#: src/exercises/day-1/morning.md:22 src/exercises/day-2/morning.md:11 -#: src/exercises/day-3/morning.md:9 src/exercises/bare-metal/morning.md:7 -#: src/exercises/concurrency/morning.md:12 -msgid "" -"After looking at the exercises, you can look at the [solutions](solutions-" -"morning.md) provided." +#: src/control-flow-basics/exercise.md:16 +msgid "4 is even, so _n" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:3 -msgid "" -"Rust will not automatically apply _implicit conversions_ between types " -"([unlike C++](https://en.cppreference.com/w/cpp/language/" -"implicit_conversion)). You can see this in a program like this:" +#: src/control-flow-basics/exercise.md:16 +msgid "7" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:20 -msgid "" -"The Rust integer types all implement the [`From`](https://doc.rust-lang." -"org/std/convert/trait.From.html) and [`Into`](https://doc.rust-lang.org/" -"std/convert/trait.Into.html) traits to let us convert between them. The " -"`From` trait has a single `from()` method and similarly, the `Into` " -"trait has a single `into()` method. Implementing these traits is how a type " -"expresses that it can be converted into another type." +#: src/control-flow-basics/exercise.md:16 +msgid "_ = 4 / 2 = 2;" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:26 -msgid "" -"The standard library has an implementation of `From for i16`, which " -"means that we can convert a variable `x` of type `i8` to an `i16` by " -"calling `i16::from(x)`. Or, simpler, with `x.into()`, because `From for " -"i16` implementation automatically create an implementation of `Into for " -"i8`." +#: src/control-flow-basics/exercise.md:17 +msgid "2 is even, so _n" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:31 -msgid "" -"The same applies for your own `From` implementations for your own types, so " -"it is sufficient to only implement `From` to get a respective `Into` " -"implementation automatically." +#: src/control-flow-basics/exercise.md:17 src/bare-metal/aps/better-uart.md:12 +#: src/bare-metal/aps/better-uart.md:15 +msgid "8" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:34 -msgid "Execute the above program and look at the compiler error." +#: src/control-flow-basics/exercise.md:17 +msgid "_ = 1; and" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:36 -msgid "Update the code above to use `into()` to do the conversion." +#: src/control-flow-basics/exercise.md:18 +msgid "the sequence terminates." msgstr "" -#: src/exercises/day-1/implicit-conversions.md:38 +#: src/control-flow-basics/exercise.md:20 msgid "" -"Change the types of `x` and `y` to other things (such as `f32`, `bool`, " -"`i128`) to see which types you can convert to which other types. Try " -"converting small types to big types and the other way around. Check the " -"[standard library documentation](https://doc.rust-lang.org/std/convert/trait." -"From.html) to see if `From` is implemented for the pairs you check." +"Write a function to calculate the length of the collatz sequence for a given " +"initial `n`." +msgstr "" + +#: src/control-flow-basics/exercise.md:24 src/control-flow-basics/solution.md:4 +msgid "/// Determine the length of the collatz sequence beginning at `n`.\n" +msgstr "" + +#: src/control-flow-basics/solution.md:20 src/concurrency/scoped-threads.md:11 +#: src/concurrency/scoped-threads.md:30 +msgid "\"Length: {}\"" +msgstr "\"Længde: {}\"" + +#: src/welcome-day-1-afternoon.md:1 src/welcome-day-2-afternoon.md:1 +#: src/welcome-day-3-afternoon.md:1 src/welcome-day-4-afternoon.md:1 +#, fuzzy +msgid "Welcome Back" +msgstr "Velkommen" + +#: src/welcome-day-1-afternoon.md:4 +msgid "[Tuples and Arrays](./tuples-and-arrays.md) (1 hour)" msgstr "" -#: src/exercises/day-1/for-loops.md:1 -#: src/exercises/day-1/solutions-morning.md:3 -msgid "Arrays and `for` Loops" +#: src/welcome-day-1-afternoon.md:5 +msgid "[References](./references.md) (50 minutes)" msgstr "" -#: src/exercises/day-1/for-loops.md:3 -msgid "We saw that an array can be declared like this:" +#: src/welcome-day-1-afternoon.md:6 +msgid "[User-Defined Types](./user-defined-types.md) (50 minutes)" msgstr "" -#: src/exercises/day-1/for-loops.md:9 +#: src/welcome-day-1-afternoon.md:8 msgid "" -"You can print such an array by asking for its debug representation with `{:?}" -"`:" +"Including 10 minute breaks, this session should take about 2 hours and 55 " +"minutes" msgstr "" -#: src/exercises/day-1/for-loops.md:19 +#: src/tuples-and-arrays.md:4 msgid "" -"Rust lets you iterate over things like arrays and ranges using the `for` " -"keyword:" +"[Tuples and Arrays](./tuples-and-arrays/tuples-and-arrays.md) (10 minutes)" msgstr "" -#: src/exercises/day-1/for-loops.md:25 -msgid "\"Iterating over array:\"" +#: src/tuples-and-arrays.md:5 +msgid "[Array Iteration](./tuples-and-arrays/iteration.md) (3 minutes)" msgstr "" -#: src/exercises/day-1/for-loops.md:27 -msgid "\" {n}\"" -msgstr "\" {n}\"" +#: src/tuples-and-arrays.md:6 +msgid "[Pattern Matching](./tuples-and-arrays/match.md) (10 minutes)" +msgstr "" -#: src/exercises/day-1/for-loops.md:31 -msgid "\"Iterating over range:\"" +#: src/tuples-and-arrays.md:7 +msgid "[Destructuring](./tuples-and-arrays/destructuring.md) (5 minutes)" msgstr "" -#: src/exercises/day-1/for-loops.md:33 -msgid "\" {}\"" -msgstr "\" {}\"" +#: src/tuples-and-arrays.md:8 +msgid "[Exercise: Nested Arrays](./tuples-and-arrays/exercise.md) (30 minutes)" +msgstr "" -#: src/exercises/day-1/for-loops.md:39 +#: src/tuples-and-arrays/tuples-and-arrays.md:3 msgid "" -"Use the above to write a function `pretty_print` which pretty-print a matrix " -"and a function `transpose` which will transpose a matrix (turn rows into " -"columns):" +"Tuples and arrays are the first \"compound\" types we have seen. All " +"elements of an array have the same type, while tuples can accommodate " +"different types. Both types have a size fixed at compile time." msgstr "" -#: src/exercises/day-1/for-loops.md:49 -msgid "Hard-code both functions to operate on 3 × 3 matrices." +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +#: src/tuples-and-arrays/destructuring.md:27 +msgid "Arrays" msgstr "" -#: src/exercises/day-1/for-loops.md:51 -msgid "" -"Copy the code below to and implement the " -"functions:" +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +msgid "`[T; N]`" msgstr "" -#: src/exercises/day-1/for-loops.md:55 src/exercises/day-1/luhn.md:26 -#: src/exercises/day-2/health-statistics.md:14 -#: src/exercises/day-2/strings-iterators.md:13 -#: src/exercises/day-3/simple-gui.md:19 -#: src/exercises/day-3/points-polygons.md:8 -#: src/exercises/day-3/safe-ffi-wrapper.md:49 -msgid "// TODO: remove this when you're done with your implementation.\n" +#: src/tuples-and-arrays/tuples-and-arrays.md:9 +msgid "`[20, 30, 40]`, `[0; 3]`" msgstr "" -#: src/exercises/day-1/for-loops.md:68 -#: src/exercises/day-1/solutions-morning.md:44 -msgid "// <-- the comment makes rustfmt add a newline\n" +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +#: src/tuples-and-arrays/destructuring.md:9 +msgid "Tuples" msgstr "" -#: src/exercises/day-1/for-loops.md:73 -#: src/exercises/day-1/solutions-morning.md:49 -msgid "\"matrix:\"" -msgstr "\"matrix:\"" +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +msgid "`()`, `(T,)`, `(T1, T2)`, ..." +msgstr "" -#: src/exercises/day-1/for-loops.md:77 -#: src/exercises/day-1/solutions-morning.md:53 -msgid "\"transposed:\"" -msgstr "\"transponeret:\"" +#: src/tuples-and-arrays/tuples-and-arrays.md:10 +msgid "`()`, `('x',)`, `('x', 1.2)`, ..." +msgstr "" -#: src/exercises/day-1/for-loops.md:82 -msgid "Bonus Question" +#: src/tuples-and-arrays/tuples-and-arrays.md:12 +msgid "Array assignment and access:" msgstr "" -#: src/exercises/day-1/for-loops.md:84 -msgid "" -"Could you use `&[i32]` slices instead of hard-coded 3 × 3 matrices for your " -"argument and return types? Something like `&[&[i32]]` for a two-dimensional " -"slice-of-slices. Why or why not?" +#: src/tuples-and-arrays/tuples-and-arrays.md:23 +msgid "Tuple assignment and access:" msgstr "" -#: src/exercises/day-1/for-loops.md:89 -msgid "" -"See the [`ndarray` crate](https://docs.rs/ndarray/) for a production quality " -"implementation." +#: src/tuples-and-arrays/tuples-and-arrays.md:39 +msgid "Arrays:" msgstr "" -#: src/exercises/day-1/for-loops.md:94 +#: src/tuples-and-arrays/tuples-and-arrays.md:41 msgid "" -"The solution and the answer to the bonus section are available in the " -"[Solution](solutions-morning.md#arrays-and-for-loops) section." +"A value of the array type `[T; N]` holds `N` (a compile-time constant) " +"elements of the same type `T`. Note that the length of the array is _part of " +"its type_, which means that `[u8; 3]` and `[u8; 4]` are considered two " +"different types. Slices, which have a size determined at runtime, are " +"covered later." msgstr "" -#: src/exercises/day-1/for-loops.md:97 +#: src/tuples-and-arrays/tuples-and-arrays.md:46 msgid "" -"The use of the reference `&array` within `for n in &array` is a subtle " -"preview of issues of ownership that will come later in the afternoon." +"Try accessing an out-of-bounds array element. Array accesses are checked at " +"runtime. Rust can usually optimize these checks away, and they can be " +"avoided using unsafe Rust." msgstr "" -#: src/exercises/day-1/for-loops.md:100 -msgid "Without the `&`..." +#: src/tuples-and-arrays/tuples-and-arrays.md:50 +msgid "We can use literals to assign values to arrays." msgstr "" -#: src/exercises/day-1/for-loops.md:101 +#: src/tuples-and-arrays/tuples-and-arrays.md:52 msgid "" -"The loop would have been one that consumes the array. This is a change " -"[introduced in the 2021 Edition](https://doc.rust-lang.org/edition-guide/" -"rust-2021/IntoIterator-for-arrays.html)." +"The `println!` macro asks for the debug implementation with the `?` format " +"parameter: `{}` gives the default output, `{:?}` gives the debug output. " +"Types such as integers and strings implement the default output, but arrays " +"only implement the debug output. This means that we must use debug output " +"here." msgstr "" -#: src/exercises/day-1/for-loops.md:104 +#: src/tuples-and-arrays/tuples-and-arrays.md:57 msgid "" -"An implicit array copy would have occurred. Since `i32` is a copy type, " -"then `[i32; 3]` is also a copy type." +"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " +"easier to read." msgstr "" -#: src/control-flow.md:3 -msgid "" -"As we have seen, `if` is an expression in Rust. It is used to conditionally " -"evaluate one of two blocks, but the blocks can have a value which then " -"becomes the value of the `if` expression. Other control flow expressions " -"work similarly in Rust." +#: src/tuples-and-arrays/tuples-and-arrays.md:59 +msgid "Tuples:" msgstr "" -#: src/control-flow/blocks.md:3 -msgid "" -"A block in Rust contains a sequence of expressions. Each block has a value " -"and a type, which are those of the last expression of the block:" +#: src/tuples-and-arrays/tuples-and-arrays.md:61 +msgid "Like arrays, tuples have a fixed length." msgstr "" -#: src/control-flow/blocks.md:27 -msgid "" -"If the last expression ends with `;`, then the resulting value and type is " -"`()`." +#: src/tuples-and-arrays/tuples-and-arrays.md:63 +msgid "Tuples group together values of different types into a compound type." msgstr "" -#: src/control-flow/blocks.md:29 +#: src/tuples-and-arrays/tuples-and-arrays.md:65 msgid "" -"The same rule is used for functions: the value of the function body is the " -"return value:" -msgstr "" - -#: src/control-flow/blocks.md:45 src/enums.md:34 src/enums/sizes.md:28 -#: src/pattern-matching.md:25 src/pattern-matching/match-guards.md:22 -#: src/structs.md:31 src/methods.md:30 src/methods/example.md:46 -msgid "Key Points:" +"Fields of a tuple can be accessed by the period and the index of the value, " +"e.g. `t.0`, `t.1`." msgstr "" -#: src/control-flow/blocks.md:46 +#: src/tuples-and-arrays/tuples-and-arrays.md:67 msgid "" -"The point of this slide is to show that blocks have a type and value in " -"Rust. " +"The empty tuple `()` is also known as the \"unit type\". It is both a type, " +"and the only valid value of that type --- that is to say both the type and " +"its value are expressed as `()`. It is used to indicate, for example, that a " +"function or expression has no return value, as we'll see in a future slide." msgstr "" -#: src/control-flow/blocks.md:47 +#: src/tuples-and-arrays/tuples-and-arrays.md:71 msgid "" -"You can show how the value of the block changes by changing the last line in " -"the block. For instance, adding/removing a semicolon or using a `return`." +"You can think of it as `void` that can be familiar to you from other " +"programming languages." msgstr "" -#: src/control-flow/if-expressions.md:1 -msgid "`if` expressions" +#: src/tuples-and-arrays/iteration.md:3 +msgid "The `for` statement supports iterating over arrays (but not tuples)." msgstr "" -#: src/control-flow/if-expressions.md:3 +#: src/tuples-and-arrays/iteration.md:19 msgid "" -"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" -"if-expr.html#if-expressions) exactly like `if` statements in other languages:" +"This functionality uses the `IntoIterator` trait, but we haven't covered " +"that yet." msgstr "" -#: src/control-flow/if-expressions.md:18 +#: src/tuples-and-arrays/iteration.md:21 msgid "" -"In addition, you can use `if` as an expression. The last expression of each " -"block becomes the value of the `if` expression:" +"The `assert_ne!` macro is new here. There are also `assert_eq!` and `assert!" +"` macros. These are always checked while, debug-only variants like " +"`debug_assert!` compile to nothing in release builds." msgstr "" -#: src/control-flow/if-expressions.md:35 +#: src/tuples-and-arrays/match.md:3 msgid "" -"Because `if` is an expression and must have a particular type, both of its " -"branch blocks must have the same type. Consider showing what happens if you " -"add `;` after `x / 2` in the second example." +"The `match` keyword lets you match a value against one or more _patterns_. " +"The comparisons are done from top to bottom and the first match wins." msgstr "" -#: src/control-flow/for-expressions.md:1 -msgid "`for` loops" +#: src/tuples-and-arrays/match.md:6 +msgid "The patterns can be simple values, similarly to `switch` in C and C++:" msgstr "" -#: src/control-flow/for-expressions.md:3 -msgid "" -"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) is closely " -"related to the [`while let` loop](while-let-expressions.md). It will " -"automatically call `into_iter()` on the expression and then iterate over it:" -msgstr "" +#: src/tuples-and-arrays/match.md:10 +msgid "'x'" +msgstr "'x'" -#: src/control-flow/for-expressions.md:22 -msgid "You can use `break` and `continue` here as usual." -msgstr "" +#: src/tuples-and-arrays/match.md:12 +msgid "'q'" +msgstr "'q'" -#: src/control-flow/for-expressions.md:26 -msgid "Index iteration is not a special syntax in Rust for just that case." +#: src/tuples-and-arrays/match.md:12 +msgid "\"Quitting\"" msgstr "" -#: src/control-flow/for-expressions.md:27 -msgid "`(0..10)` is a range that implements an `Iterator` trait. " +#: src/tuples-and-arrays/match.md:13 src/std-traits/solution.md:16 +#: src/error-handling/exercise.md:64 src/error-handling/exercise.md:66 +#: src/error-handling/solution.md:63 src/error-handling/solution.md:65 +msgid "'a'" +msgstr "'a'" + +#: src/tuples-and-arrays/match.md:13 +msgid "'s'" +msgstr "'s'" + +#: src/tuples-and-arrays/match.md:13 +msgid "'w'" +msgstr "'w'" + +#: src/tuples-and-arrays/match.md:13 +msgid "'d'" +msgstr "'d'" + +#: src/tuples-and-arrays/match.md:13 +msgid "\"Moving around\"" msgstr "" -#: src/control-flow/for-expressions.md:28 -msgid "" -"`step_by` is a method that returns another `Iterator` that skips every other " -"element. " +#: src/tuples-and-arrays/match.md:14 src/error-handling/exercise.md:56 +#: src/error-handling/exercise.md:58 src/error-handling/exercise.md:66 +#: src/error-handling/solution.md:55 src/error-handling/solution.md:57 +#: src/error-handling/solution.md:65 +msgid "'0'" +msgstr "'0'" + +#: src/tuples-and-arrays/match.md:14 src/error-handling/exercise.md:56 +#: src/error-handling/exercise.md:58 src/error-handling/exercise.md:66 +#: src/error-handling/solution.md:55 src/error-handling/solution.md:57 +#: src/error-handling/solution.md:65 +msgid "'9'" +msgstr "'9'" + +#: src/tuples-and-arrays/match.md:14 +msgid "\"Number input\"" msgstr "" -#: src/control-flow/for-expressions.md:29 -msgid "" -"Modify the elements in the vector and explain the compiler errors. Change " -"vector `v` to be mutable and the for loop to `for x in v.iter_mut()`." +#: src/tuples-and-arrays/match.md:15 +msgid "\"Lowercase: {key}\"" msgstr "" -#: src/control-flow/while-expressions.md:1 -msgid "`while` loops" +#: src/tuples-and-arrays/match.md:16 +msgid "\"Something else\"" msgstr "" -#: src/control-flow/while-expressions.md:3 +#: src/tuples-and-arrays/match.md:21 msgid "" -"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" -"expr.html#predicate-loops) works very similar to other languages:" +"The `_` pattern is a wildcard pattern which matches any value. The " +"expressions _must_ be irrefutable, meaning that it covers every possibility, " +"so `_` is often used as the final catch-all case." msgstr "" -#: src/control-flow/break-continue.md:1 -msgid "`break` and `continue`" +#: src/tuples-and-arrays/match.md:25 +msgid "" +"Match can be used as an expression. Just like like `if`, each match arm must " +"have the same type. The type is the last expression of the block, if any. In " +"the example above, the type is `()`." msgstr "" -#: src/control-flow/break-continue.md:3 +#: src/tuples-and-arrays/match.md:28 msgid "" -"If you want to exit a loop early, use [`break`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#break-expressions)," +"A variable in the pattern (`key` in this example) will create a binding that " +"can be used within the match arm." msgstr "" -#: src/control-flow/break-continue.md:4 -msgid "" -"If you want to immediately start the next iteration use [`continue`](https://" -"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." +#: src/tuples-and-arrays/match.md:31 +msgid "A match guard causes the arm to match only if the condition is true." msgstr "" -#: src/control-flow/break-continue.md:7 -msgid "" -"Both `continue` and `break` can optionally take a label argument which is " -"used to break out of nested loops:" +#: src/tuples-and-arrays/match.md:36 src/user-defined-types/named-structs.md:41 +#: src/user-defined-types/enums.md:29 src/methods-and-traits/methods.md:65 +msgid "Key Points:" msgstr "" -#: src/control-flow/break-continue.md:29 +#: src/tuples-and-arrays/match.md:37 msgid "" -"In this case we break the outer loop after 3 iterations of the inner loop." +"You might point out how some specific characters are being used when in a " +"pattern" msgstr "" -#: src/control-flow/loop-expressions.md:1 -msgid "`loop` expressions" +#: src/tuples-and-arrays/match.md:38 +msgid "`|` as an `or`" msgstr "" -#: src/control-flow/loop-expressions.md:3 -msgid "" -"Finally, there is a [`loop` keyword](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#infinite-loops) which creates an endless loop." +#: src/tuples-and-arrays/match.md:39 +msgid "`..` can expand as much as it needs to be" msgstr "" -#: src/control-flow/loop-expressions.md:6 -msgid "Here you must either `break` or `return` to stop the loop:" +#: src/tuples-and-arrays/match.md:40 +msgid "`1..=5` represents an inclusive range" msgstr "" -#: src/control-flow/loop-expressions.md:28 -msgid "Break the `loop` with a value (e.g. `break 8`) and print it out." +#: src/tuples-and-arrays/match.md:41 +msgid "`_` is a wild card" msgstr "" -#: src/control-flow/loop-expressions.md:29 +#: src/tuples-and-arrays/match.md:43 msgid "" -"Note that `loop` is the only looping construct which returns a non-trivial " -"value. This is because it's guaranteed to be entered at least once (unlike " -"`while` and `for` loops)." +"Match guards as a separate syntax feature are important and necessary when " +"we wish to concisely express more complex ideas than patterns alone would " +"allow." msgstr "" -#: src/basic-syntax/variables.md:3 +#: src/tuples-and-arrays/match.md:44 msgid "" -"Rust provides type safety via static typing. Variable bindings are immutable " -"by default:" +"They are not the same as separate `if` expression inside of the match arm. " +"An `if` expression inside of the branch block (after `=>`) happens after the " +"match arm is selected. Failing the `if` condition inside of that block won't " +"result in other arms of the original `match` expression being considered." msgstr "" -#: src/basic-syntax/variables.md:18 +#: src/tuples-and-arrays/match.md:46 msgid "" -"Due to type inference the `i32` is optional. We will gradually show the " -"types less and less as the course progresses." +"The condition defined in the guard applies to every expression in a pattern " +"with an `|`." msgstr "" -#: src/basic-syntax/type-inference.md:3 -msgid "Rust will look at how the variable is _used_ to determine the type:" +#: src/tuples-and-arrays/destructuring.md:3 +msgid "" +"Destructuring is a way of extracting data from a data structure by writing a " +"pattern that is matched up to the data structure, binding variables to " +"subcomponents of the data structure." msgstr "" -#: src/basic-syntax/type-inference.md:27 -msgid "" -"This slide demonstrates how the Rust compiler infers types based on " -"constraints given by variable declarations and usages." +#: src/tuples-and-arrays/destructuring.md:7 +msgid "You can destructure tuples and arrays by matching on their elements:" msgstr "" -#: src/basic-syntax/type-inference.md:29 -msgid "" -"It is very important to emphasize that variables declared like this are not " -"of some sort of dynamic \"any type\" that can hold any data. The machine " -"code generated by such declaration is identical to the explicit declaration " -"of a type. The compiler does the job for us and helps us write more concise " -"code." +#: src/tuples-and-arrays/destructuring.md:18 +msgid "\"on Y axis\"" msgstr "" -#: src/basic-syntax/type-inference.md:33 -msgid "" -"The following code tells the compiler to copy into a certain generic " -"container without the code ever explicitly specifying the contained type, " -"using `_` as a placeholder:" +#: src/tuples-and-arrays/destructuring.md:19 +msgid "\"on X axis\"" msgstr "" -#: src/basic-syntax/type-inference.md:48 -msgid "" -"[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." -"html#method.collect) relies on [`FromIterator`](https://doc.rust-lang.org/" -"std/iter/trait.FromIterator.html), which [`HashSet`](https://doc.rust-lang." -"org/std/collections/struct.HashSet.html#impl-FromIterator%3CT%3E-for-" -"HashSet%3CT,+S%3E) implements." +#: src/tuples-and-arrays/destructuring.md:20 +msgid "\"left of Y axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:1 -msgid "Static and Constant Variables" +#: src/tuples-and-arrays/destructuring.md:21 +msgid "\"below X axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:3 -msgid "" -"Static and constant variables are two different ways to create globally-" -"scoped values that cannot be moved or reallocated during the execution of " -"the program. " +#: src/tuples-and-arrays/destructuring.md:22 +msgid "\"first quadrant\"" msgstr "" -#: src/basic-syntax/static-and-const.md:6 -msgid "`const`" +#: src/tuples-and-arrays/destructuring.md:33 +msgid "\"Tell me about {triple:?}\"" +msgstr "\"Fortæl mig om {triple:?}\"" + +#: src/tuples-and-arrays/destructuring.md:35 +msgid "\"First is 0, y = {y}, and z = {z}\"" msgstr "" -#: src/basic-syntax/static-and-const.md:8 -msgid "" -"Constant variables are evaluated at compile time and their values are " -"inlined wherever they are used:" +#: src/tuples-and-arrays/destructuring.md:36 +msgid "\"First is 1 and the rest were ignored\"" msgstr "" -#: src/basic-syntax/static-and-const.md:30 -msgid "" -"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html) these are inlined upon use." +#: src/tuples-and-arrays/destructuring.md:37 +msgid "\"All elements were ignored\"" msgstr "" -#: src/basic-syntax/static-and-const.md:32 -msgid "" -"Only functions marked `const` can be called at compile time to generate " -"`const` values. `const` functions can however be called at runtime." +#: src/tuples-and-arrays/destructuring.md:45 +msgid "Create a new array pattern using `_` to represent an element." msgstr "" -#: src/basic-syntax/static-and-const.md:34 -msgid "`static`" +#: src/tuples-and-arrays/destructuring.md:46 +msgid "Add more values to the array." msgstr "" -#: src/basic-syntax/static-and-const.md:36 +#: src/tuples-and-arrays/destructuring.md:47 msgid "" -"Static variables will live during the whole execution of the program, and " -"therefore will not move:" +"Point out that how `..` will expand to account for different number of " +"elements." msgstr "" -#: src/basic-syntax/static-and-const.md:39 -msgid "\"Welcome to RustOS 3.14\"" -msgstr "\"Velkommen til RustOS 3.14\"" +#: src/tuples-and-arrays/destructuring.md:48 +msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" +msgstr "" -#: src/basic-syntax/static-and-const.md:42 -msgid "\"{BANNER}\"" -msgstr "\"{BANNER}\"" +#: src/tuples-and-arrays/exercise.md:3 +msgid "Arrays can contain other arrays:" +msgstr "" -#: src/basic-syntax/static-and-const.md:46 -msgid "" -"As noted in the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html), these are not inlined upon use and have an actual " -"associated memory location. This is useful for unsafe and embedded code, " -"and the variable lives through the entirety of the program execution. When a " -"globally-scoped value does not have a reason to need object identity, " -"`const` is generally preferred." +#: src/tuples-and-arrays/exercise.md:9 +msgid "What is the type of this variable?" msgstr "" -#: src/basic-syntax/static-and-const.md:50 +#: src/tuples-and-arrays/exercise.md:11 msgid "" -"Because `static` variables are accessible from any thread, they must be " -"`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" -"lang.org/std/sync/struct.Mutex.html), atomic or similar. It is also possible " -"to have mutable statics, but they require manual synchronisation so any " -"access to them requires `unsafe` code. We will look at [mutable statics](../" -"unsafe/mutable-static-variables.md) in the chapter on Unsafe Rust." +"Use an array such as the above to write a function `transpose` which will " +"transpose a matrix (turn rows into columns):" msgstr "" -#: src/basic-syntax/static-and-const.md:58 -msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." +#: src/tuples-and-arrays/exercise.md:21 +msgid "Hard-code both functions to operate on 3 × 3 matrices." msgstr "" -#: src/basic-syntax/static-and-const.md:59 +#: src/tuples-and-arrays/exercise.md:23 msgid "" -"`static`, on the other hand, is much more similar to a `const` or mutable " -"global variable in C++." +"Copy the code below to and implement the " +"functions:" msgstr "" -#: src/basic-syntax/static-and-const.md:60 -msgid "" -"`static` provides object identity: an address in memory and state as " -"required by types with interior mutability such as `Mutex`." +#: src/tuples-and-arrays/exercise.md:27 src/methods-and-traits/exercise.md:20 +#: src/borrowing/exercise.md:14 src/unsafe-rust/exercise.md:49 +msgid "// TODO: remove this when you're done with your implementation.\n" +msgstr "" + +#: src/tuples-and-arrays/exercise.md:36 src/tuples-and-arrays/solution.md:34 +msgid "// <-- the comment makes rustfmt add a newline\n" msgstr "" -#: src/basic-syntax/static-and-const.md:61 +#: src/tuples-and-arrays/exercise.md:41 src/tuples-and-arrays/solution.md:39 +#, fuzzy +msgid "\"matrix: {:#?}\"" +msgstr "\"matrix:\"" + +#: src/tuples-and-arrays/exercise.md:43 src/tuples-and-arrays/solution.md:41 +#, fuzzy +msgid "\"transposed: {:#?}\"" +msgstr "\"transponeret:\"" + +#: src/tuples-and-arrays/exercise.md:50 msgid "" -"It isn't super common that one would need a runtime evaluated constant, but " -"it is helpful and safer than using a static." +"The `transpose` function takes its argument by value, but we haven't covered " +"ownership yet. Try printing a matrix after it has been transposed, to show " +"the \"value has been moved\" error, as a preview of ownership and move " +"semantics." msgstr "" -#: src/basic-syntax/static-and-const.md:62 -msgid "`thread_local` data can be created with the macro `std::thread_local`." +#: src/tuples-and-arrays/solution.md:17 src/tuples-and-arrays/solution.md:25 +msgid "//\n" msgstr "" -#: src/basic-syntax/static-and-const.md:64 -msgid "Properties table:" +#: src/references.md:4 +msgid "[Shared References](./references/shared.md) (10 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:66 -msgid "Property" -msgstr "Egenskab" - -#: src/basic-syntax/static-and-const.md:66 -msgid "Static" -msgstr "Statisk" - -#: src/basic-syntax/static-and-const.md:66 -msgid "Constant" -msgstr "Konstant" - -#: src/basic-syntax/static-and-const.md:68 -msgid "Has an address in memory" -msgstr "Har en adresse i hukommelsen" - -#: src/basic-syntax/static-and-const.md:68 -#: src/basic-syntax/static-and-const.md:69 -#: src/basic-syntax/static-and-const.md:71 -#: src/basic-syntax/static-and-const.md:72 -msgid "Yes" -msgstr "Ja" - -#: src/basic-syntax/static-and-const.md:68 -msgid "No (inlined)" -msgstr "Nej (inlinet)" - -#: src/basic-syntax/static-and-const.md:69 -msgid "Lives for the entire duration of the program" +#: src/references.md:5 +msgid "[Exclusive References](./references/exclusive.md) (10 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:69 -#: src/basic-syntax/static-and-const.md:70 -#: src/basic-syntax/static-and-const.md:72 -msgid "No" -msgstr "Nej" - -#: src/basic-syntax/static-and-const.md:70 -msgid "Can be mutable" +#: src/references.md:6 +msgid "[Exercise: Geometry](./references/exercise.md) (30 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:70 -msgid "Yes (unsafe)" -msgstr "Ja (_unsafe_)" - -#: src/basic-syntax/static-and-const.md:71 -msgid "Evaluated at compile time" -msgstr "Evalueret ved kompileringstid" - -#: src/basic-syntax/static-and-const.md:71 -msgid "Yes (initialised at compile time)" -msgstr "Ja (initialiseret ved kompileringstid)" - -#: src/basic-syntax/static-and-const.md:72 -msgid "Inlined wherever it is used" +#: src/references.md:8 src/user-defined-types.md:11 src/pattern-matching.md:8 +msgid "This segment should take about 50 minutes" msgstr "" -#: src/basic-syntax/scopes-shadowing.md:3 +#: src/references/shared.md:3 msgid "" -"You can shadow variables, both those from outer scopes and variables from " -"the same scope:" +"A reference provides a way to access another value without taking " +"responsibility for the value, and is also called \"borrowing\". Shared " +"references are read-only, and the referenced data cannot change." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:9 -msgid "\"before: {a}\"" -msgstr "\"før: {a}\"" - -#: src/basic-syntax/scopes-shadowing.md:12 src/traits/from-into.md:7 -#: src/traits/from-into.md:19 -msgid "\"hello\"" -msgstr "\"hallo\"" - -#: src/basic-syntax/scopes-shadowing.md:13 -msgid "\"inner scope: {a}\"" -msgstr "\"indre blok: {a}\"" - -#: src/basic-syntax/scopes-shadowing.md:16 -msgid "\"shadowed in inner scope: {a}\"" -msgstr "\"overskygget i indre blok: {a}\"" +#: src/references/shared.md:19 +msgid "" +"A shared reference to a type `T` has type `&T`. A reference value is made " +"with the `&` operator. The `*` operator \"dereferences\" a reference, " +"yielding its value." +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:19 -msgid "\"after: {a}\"" -msgstr "\"efter: {a}\"" +#: src/references/shared.md:22 +msgid "Rust will statically forbid dangling references:" +msgstr "" -#: src/basic-syntax/scopes-shadowing.md:25 +#: src/references/shared.md:35 msgid "" -"Definition: Shadowing is different from mutation, because after shadowing " -"both variable's memory locations exist at the same time. Both are available " -"under the same name, depending where you use it in the code. " +"A reference is said to \"borrow\" the value it refers to, and this is a good " +"model for students not familiar with pointers: code can use the reference to " +"access the value, but is still \"owned\" by the original variable. The " +"course will get into more detail on ownership in day 3." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:26 -msgid "A shadowing variable can have a different type. " +#: src/references/shared.md:40 +msgid "" +"References are implemented as pointers, and a key advantage is that they can " +"be much smaller than the thing they point to. Students familiar with C or C+" +"+ will recognize references as pointers. Later parts of the course will " +"cover how Rust prevents the memory-safety bugs that come from using raw " +"pointers." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:27 +#: src/references/shared.md:45 msgid "" -"Shadowing looks obscure at first, but is convenient for holding on to values " -"after `.unwrap()`." +"Rust does not automatically create references for you - the `&` is always " +"required." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:28 +#: src/references/shared.md:48 msgid "" -"The following code demonstrates why the compiler can't simply reuse memory " -"locations when shadowing an immutable variable in a scope, even if the type " -"does not change." +"Rust will auto-dereference in some cases, in particular when invoking " +"methods (try `r.count_ones()`). There is no need for an `->` operator like " +"in C++." msgstr "" -#: src/enums.md:3 +#: src/references/shared.md:52 msgid "" -"The `enum` keyword allows the creation of a type which has a few different " -"variants:" +"In this example, `r` is mutable so that it can be reassigned (`r = &b`). " +"Note that this re-binds `r`, so that it refers to something else. This is " +"different from C++, where assignment to a reference changes the referenced " +"value." msgstr "" -#: src/enums.md:8 -msgid "// Implementation based on https://xkcd.com/221/\n" +#: src/references/shared.md:57 +msgid "" +"A shared reference does not allow modifying the value it refers to, even if " +"that value was mutable. Try `*r = 'X'`." msgstr "" -#: src/enums.md:9 -msgid "// Chosen by fair dice roll. Guaranteed to be random.\n" +#: src/references/shared.md:60 +msgid "" +"Rust is tracking the lifetimes of all references to ensure they live long " +"enough. Dangling references cannot occur in safe Rust. `x_axis` would return " +"a reference to `point`, but `point` will be deallocated when the function " +"returns, so this will not compile." msgstr "" -#: src/enums.md:28 -msgid "\"You got: {:?}\"" +#: src/references/shared.md:65 +msgid "We will talk more about borrowing when we get to ownership." msgstr "" -#: src/enums.md:36 -msgid "Enumerations allow you to collect a set of values under one type" +#: src/references/exclusive.md:3 +msgid "" +"Exclusive references, also known as mutable references, allow changing the " +"value they refer to. They have type `&mut T`." msgstr "" -#: src/enums.md:37 +#: src/references/exclusive.md:21 msgid "" -"This page offers an enum type `CoinFlip` with two variants `Heads` and " -"`Tails`. You might note the namespace when using variants." +"\"Exclusive\" means that only this reference can be used to access the " +"value. No other references (shared or exclusive) can exist at the same time, " +"and the referenced value cannot be accessed while the exclusive reference " +"exists. Try making an `&point.0` or changing `point.0` while `x_coord` is " +"alive." msgstr "" -#: src/enums.md:38 -msgid "This might be a good time to compare Structs and Enums:" +#: src/references/exclusive.md:26 +msgid "" +"Be sure to note the difference between `let mut x_coord: &i32` and `let " +"x_coord: &mut i32`. The first one represents a shared reference which can be " +"bound to different values, while the second represents an exclusive " +"reference to a mutable value." msgstr "" -#: src/enums.md:39 +#: src/references/exercise.md:3 msgid "" -"In both, you can have a simple version without fields (unit struct) or one " -"with different types of fields (variant payloads). " +"We will create a few utility functions for 3-dimensional geometry, " +"representing a point as `[f64;3]`. It is up to you to determine the function " +"signatures." msgstr "" -#: src/enums.md:40 -msgid "In both, associated functions are defined within an `impl` block." +#: src/references/exercise.md:7 +msgid "" +"// Calculate the magnitude of a vector by summing the squares of its " +"coordinates\n" +"// and taking the square root. Use the `sqrt()` method to calculate the " +"square\n" +"// root, like `v.sqrt()`.\n" msgstr "" -#: src/enums.md:41 +#: src/references/exercise.md:15 msgid "" -"You could even implement the different variants of an enum with separate " -"structs but then they wouldn’t be the same type as they would if they were " -"all defined in an enum. " +"// Normalize a vector by calculating its magnitude and dividing all of its\n" +"// coordinates by that magnitude.\n" msgstr "" -#: src/enums/variant-payloads.md:3 -msgid "" -"You can define richer enums where the variants carry data. You can then use " -"the `match` statement to extract the data from each variant:" +#: src/references/exercise.md:23 +msgid "// Use the following `main` to test your work.\n" msgstr "" -#: src/enums/variant-payloads.md:8 -msgid "// Variant without payload\n" +#: src/references/exercise.md:28 src/references/solution.md:23 +msgid "\"Magnitude of a unit vector: {}\"" msgstr "" -#: src/enums/variant-payloads.md:9 -msgid "// Tuple struct variant\n" +#: src/references/exercise.md:33 src/references/solution.md:28 +msgid "\"Magnitude of {v:?}: {}\"" msgstr "" -#: src/enums/variant-payloads.md:10 -msgid "// Full struct variant\n" +#: src/references/exercise.md:35 src/references/solution.md:30 +msgid "\"Magnitude of {v:?} after normalization: {}\"" msgstr "" -#: src/enums/variant-payloads.md:16 -msgid "\"page loaded\"" +#: src/references/solution.md:4 +msgid "/// Calculate the magnitude of the given vector.\n" msgstr "" -#: src/enums/variant-payloads.md:17 -msgid "\"pressed '{c}'\"" +#: src/references/solution.md:12 +msgid "" +"/// Change the magnitude of the vector to 1.0 without changing its " +"direction.\n" msgstr "" -#: src/enums/variant-payloads.md:18 -msgid "\"clicked at x={x}, y={y}\"" +#: src/user-defined-types.md:4 +msgid "[Named Structs](./user-defined-types/named-structs.md) (10 minutes)" msgstr "" -#: src/enums/variant-payloads.md:24 src/pattern-matching.md:10 -msgid "'x'" -msgstr "'x'" +#: src/user-defined-types.md:5 +msgid "[Tuple Structs](./user-defined-types/tuple-structs.md) (10 minutes)" +msgstr "" -#: src/enums/variant-payloads.md:35 -msgid "" -"The values in the enum variants can only be accessed after being pattern " -"matched. The pattern binds references to the fields in the \"match arm\" " -"after the `=>`." +#: src/user-defined-types.md:6 +msgid "[Enums](./user-defined-types/enums.md) (5 minutes)" msgstr "" -#: src/enums/variant-payloads.md:36 +#: src/user-defined-types.md:7 msgid "" -"The expression is matched against the patterns from top to bottom. There is " -"no fall-through like in C or C++." +"[Static and Const](./user-defined-types/static-and-const.md) (5 minutes)" msgstr "" -#: src/enums/variant-payloads.md:37 -msgid "" -"The match expression has a value. The value is the last expression in the " -"match arm which was executed." +#: src/user-defined-types.md:8 +msgid "[Type Aliases](./user-defined-types/aliases.md) (2 minutes)" msgstr "" -#: src/enums/variant-payloads.md:38 +#: src/user-defined-types.md:9 msgid "" -"Starting from the top we look for what pattern matches the value then run " -"the code following the arrow. Once we find a match, we stop. " +"[Exercise: Elevator Events](./user-defined-types/exercise.md) (15 minutes)" msgstr "" -#: src/enums/variant-payloads.md:39 -msgid "" -"Demonstrate what happens when the search is inexhaustive. Note the advantage " -"the Rust compiler provides by confirming when all cases are handled. " +#: src/user-defined-types/named-structs.md:3 +msgid "Like C and C++, Rust has support for custom structs:" msgstr "" -#: src/enums/variant-payloads.md:40 -msgid "`match` inspects a hidden discriminant field in the `enum`." +#: src/user-defined-types/named-structs.md:12 +msgid "\"{} is {} years old\"" msgstr "" -#: src/enums/variant-payloads.md:41 -msgid "" -"It is possible to retrieve the discriminant by calling `std::mem::" -"discriminant()`" +#: src/user-defined-types/named-structs.md:17 +#: src/android/interoperability/with-c/bindgen.md:87 +msgid "\"Peter\"" +msgstr "\"Peter\"" + +#: src/user-defined-types/named-structs.md:25 +msgid "\"Avery\"" msgstr "" -#: src/enums/variant-payloads.md:42 -msgid "" -"This is useful, for example, if implementing `PartialEq` for structs where " -"comparing field values doesn't affect equality." +#: src/user-defined-types/named-structs.md:31 +msgid "\"Jackie\"" +msgstr "\"Jackie\"" + +#: src/user-defined-types/named-structs.md:43 +msgid "Structs work like in C or C++." msgstr "" -#: src/enums/variant-payloads.md:43 -msgid "" -"`WebEvent::Click { ... }` is not exactly the same as `WebEvent::" -"Click(Click)` with a top level `struct Click { ... }`. The inlined version " -"cannot implement traits, for example." +#: src/user-defined-types/named-structs.md:44 +msgid "Like in C++, and unlike in C, no typedef is needed to define a type." msgstr "" -#: src/enums/sizes.md:3 -msgid "" -"Rust enums are packed tightly, taking constraints due to alignment into " -"account:" +#: src/user-defined-types/named-structs.md:45 +msgid "Unlike in C++, there is no inheritance between structs." msgstr "" -#: src/enums/sizes.md:10 -msgid "\"{}: size {} bytes, align: {} bytes\"" +#: src/user-defined-types/named-structs.md:46 +msgid "" +"This may be a good time to let people know there are different types of " +"structs." msgstr "" -#: src/enums/sizes.md:24 +#: src/user-defined-types/named-structs.md:47 msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/type-layout." -"html)." +"Zero-sized structs (e.g. `struct Foo;`) might be used when implementing a " +"trait on some type but don’t have any data that you want to store in the " +"value itself." msgstr "" -#: src/enums/sizes.md:30 +#: src/user-defined-types/named-structs.md:48 msgid "" -"Internally Rust is using a field (discriminant) to keep track of the enum " -"variant." +"The next slide will introduce Tuple structs, used when the field names are " +"not important." msgstr "" -#: src/enums/sizes.md:32 +#: src/user-defined-types/named-structs.md:49 msgid "" -"You can control the discriminant if needed (e.g., for compatibility with C):" +"If you already have variables with the right names, then you can create the " +"struct using a shorthand." msgstr "" -#: src/enums/sizes.md:50 +#: src/user-defined-types/named-structs.md:51 msgid "" -"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " -"bytes." +"The syntax `..peter` allows us to copy the majority of the fields from the " +"old struct without having to explicitly type it all out. It must always be " +"the last element." +msgstr "" + +#: src/user-defined-types/tuple-structs.md:6 +msgid "If the field names are unimportant, you can use a tuple struct:" msgstr "" -#: src/enums/sizes.md:54 -msgid "Try out other types such as" +#: src/user-defined-types/tuple-structs.md:13 +msgid "\"({}, {})\"" +msgstr "\"({}, {})\"" + +#: src/user-defined-types/tuple-structs.md:17 +msgid "This is often used for single-field wrappers (called newtypes):" msgstr "" -#: src/enums/sizes.md:56 -msgid "`dbg_size!(bool)`: size 1 bytes, align: 1 bytes," +#: src/user-defined-types/tuple-structs.md:24 +msgid "\"Ask a rocket scientist at NASA\"" msgstr "" -#: src/enums/sizes.md:57 +#: src/user-defined-types/tuple-structs.md:28 +#: src/android/interoperability/cpp/cpp-bridge.md:50 +#: src/bare-metal/microcontrollers/type-state.md:14 +#: src/async/pitfalls/cancellation.md:96 src/async/pitfalls/cancellation.md:99 +msgid "// ...\n" +msgstr "// ...\n" + +#: src/user-defined-types/tuple-structs.md:41 msgid "" -"`dbg_size!(Option)`: size 1 bytes, align: 1 bytes (niche optimization, " -"see below)," +"Newtypes are a great way to encode additional information about the value in " +"a primitive type, for example:" msgstr "" -#: src/enums/sizes.md:58 -msgid "`dbg_size!(&i32)`: size 8 bytes, align: 8 bytes (on a 64-bit machine)," +#: src/user-defined-types/tuple-structs.md:42 +msgid "The number is measured in some units: `Newtons` in the example above." msgstr "" -#: src/enums/sizes.md:59 +#: src/user-defined-types/tuple-structs.md:43 msgid "" -"`dbg_size!(Option<&i32>)`: size 8 bytes, align: 8 bytes (null pointer " -"optimization, see below)." +"The value passed some validation when it was created, so you no longer have " +"to validate it again at every use: `PhoneNumber(String)` or `OddNumber(u32)`." msgstr "" -#: src/enums/sizes.md:61 +#: src/user-defined-types/tuple-structs.md:44 msgid "" -"Niche optimization: Rust will merge unused bit patterns for the enum " -"discriminant." +"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " +"single field in the newtype." msgstr "" -#: src/enums/sizes.md:64 +#: src/user-defined-types/tuple-structs.md:45 msgid "" -"Null pointer optimization: For [some types](https://doc.rust-lang.org/std/" -"option/#representation), Rust guarantees that `size_of::()` equals " -"`size_of::>()`." +"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " +"for instance using booleans as integers." msgstr "" -#: src/enums/sizes.md:68 -msgid "" -"Example code if you want to show how the bitwise representation _may_ look " -"like in practice. It's important to note that the compiler provides no " -"guarantees regarding this representation, therefore this is totally unsafe." +#: src/user-defined-types/tuple-structs.md:46 +msgid "Operator overloading is discussed on Day 3 (generics)." msgstr "" -#: src/enums/sizes.md:105 +#: src/user-defined-types/tuple-structs.md:47 msgid "" -"More complex example if you want to discuss what happens when we chain more " -"than 256 `Option`s together." +"The example is a subtle reference to the [Mars Climate Orbiter](https://en." +"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." msgstr "" -#: src/control-flow/novel.md:3 +#: src/user-defined-types/enums.md:3 msgid "" -"Rust has a few control flow constructs which differ from other languages. " -"They are used for pattern matching:" +"The `enum` keyword allows the creation of a type which has a few different " +"variants:" msgstr "" -#: src/control-flow/novel.md:6 src/control-flow/if-let-expressions.md:1 -msgid "`if let` expressions" -msgstr "`if let`-udtryk" - -#: src/control-flow/novel.md:7 -msgid "`while let` expressions" -msgstr "`while let`-udtryk" +#: src/user-defined-types/enums.md:15 +msgid "// Simple variant\n" +msgstr "" -#: src/control-flow/novel.md:8 src/control-flow/match-expressions.md:1 -msgid "`match` expressions" -msgstr "`match`-udtryk" +#: src/user-defined-types/enums.md:16 +msgid "// Tuple variant\n" +msgstr "" -#: src/control-flow/if-let-expressions.md:3 -msgid "" -"The [`if let` expression](https://doc.rust-lang.org/reference/expressions/if-" -"expr.html#if-let-expressions) lets you execute different code depending on " -"whether a value matches a pattern:" +#: src/user-defined-types/enums.md:17 +msgid "// Struct variant\n" msgstr "" -#: src/control-flow/if-let-expressions.md:11 -msgid "\"Program name: {value}\"" +#: src/user-defined-types/enums.md:22 +msgid "\"On this turn: {:?}\"" msgstr "" -#: src/control-flow/if-let-expressions.md:13 -msgid "\"Missing name?\"" +#: src/user-defined-types/enums.md:31 +msgid "Enumerations allow you to collect a set of values under one type" msgstr "" -#: src/control-flow/if-let-expressions.md:18 -#: src/control-flow/while-let-expressions.md:22 -#: src/control-flow/match-expressions.md:23 +#: src/user-defined-types/enums.md:32 msgid "" -"See [pattern matching](../pattern-matching.md) for more details on patterns " -"in Rust." +"Direction has two variants, `Left` and `Right`. These are referred to with " +"the `Direction::..` namespace." msgstr "" -#: src/control-flow/if-let-expressions.md:23 +#: src/user-defined-types/enums.md:33 msgid "" -"Unlike `match`, `if let` does not have to cover all branches. This can make " -"it more concise than `match`." +"PlayerMove shows the three types of variants. Rust will also store a " +"discriminant so that it can determine at runtime which variant is in a value." msgstr "" -#: src/control-flow/if-let-expressions.md:24 -msgid "A common usage is handling `Some` values when working with `Option`." +#: src/user-defined-types/enums.md:34 +msgid "This might be a good time to compare Structs and Enums:" msgstr "" -#: src/control-flow/if-let-expressions.md:25 +#: src/user-defined-types/enums.md:35 msgid "" -"Unlike `match`, `if let` does not support guard clauses for pattern matching." +"In both, you can have a simple version without fields (unit struct) or one " +"with different types of fields (variant payloads)." msgstr "" -#: src/control-flow/if-let-expressions.md:26 +#: src/user-defined-types/enums.md:36 msgid "" -"Since 1.65, a similar [let-else](https://doc.rust-lang.org/rust-by-example/" -"flow_control/let_else.html) construct allows to do a destructuring " -"assignment, or if it fails, execute a block which is required to abort " -"normal control flow (with `panic`/`return`/`break`/`continue`):" +"You could even implement the different variants of an enum with separate " +"structs but then they wouldn’t be the same type as they would if they were " +"all defined in an enum." msgstr "" -#: src/control-flow/while-let-expressions.md:1 -msgid "`while let` loops" -msgstr "`while let`-lykker" - -#: src/control-flow/while-let-expressions.md:3 -msgid "" -"Like with `if let`, there is a [`while let`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#predicate-pattern-loops) variant which " -"repeatedly tests a value against a pattern:" +#: src/user-defined-types/enums.md:37 +msgid "Rust uses minimal space to store the discriminant." msgstr "" -#: src/control-flow/while-let-expressions.md:18 -msgid "" -"Here the iterator returned by `v.into_iter()` will return a `Option` on " -"every call to `next()`. It returns `Some(x)` until it is done, after which " -"it will return `None`. The `while let` lets us keep iterating through all " -"items." +#: src/user-defined-types/enums.md:38 +msgid "If necessary, it stores an integer of the smallest required size" msgstr "" -#: src/control-flow/while-let-expressions.md:27 +#: src/user-defined-types/enums.md:39 msgid "" -"Point out that the `while let` loop will keep going as long as the value " -"matches the pattern." +"If the allowed variant values do not cover all bit patterns, it will use " +"invalid bit patterns to encode the discriminant (the \"niche " +"optimization\"). For example, `Option<&u8>` stores either a pointer to an " +"integer or `NULL` for the `None` variant." msgstr "" -#: src/control-flow/while-let-expressions.md:28 +#: src/user-defined-types/enums.md:43 msgid "" -"You could rewrite the `while let` loop as an infinite loop with an if " -"statement that breaks when there is no value to unwrap for `iter.next()`. " -"The `while let` provides syntactic sugar for the above scenario." +"You can control the discriminant if needed (e.g., for compatibility with C):" msgstr "" -#: src/control-flow/match-expressions.md:3 +#: src/user-defined-types/enums.md:61 msgid "" -"The [`match` keyword](https://doc.rust-lang.org/reference/expressions/match-" -"expr.html) is used to match a value against one or more patterns. In that " -"sense, it works like a series of `if let` expressions:" +"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " +"bytes." msgstr "" -#: src/control-flow/match-expressions.md:10 -msgid "\"cat\"" -msgstr "\"cat\"" - -#: src/control-flow/match-expressions.md:10 -msgid "\"Will do cat things\"" +#: src/user-defined-types/enums.md:64 +#: src/user-defined-types/static-and-const.md:68 +#: src/memory-management/review.md:48 src/memory-management/move.md:92 +#: src/smart-pointers/box.md:73 src/borrowing/shared.md:32 +msgid "More to Explore" msgstr "" -#: src/control-flow/match-expressions.md:11 -msgid "\"ls\"" -msgstr "\"ls\"" +#: src/user-defined-types/enums.md:66 +msgid "" +"Rust has several optimizations it can employ to make enums take up less " +"space." +msgstr "" -#: src/control-flow/match-expressions.md:11 -msgid "\"Will ls some files\"" +#: src/user-defined-types/enums.md:68 +msgid "" +"Niche optimization: Rust will merge unused bit patterns for the enum " +"discriminant." msgstr "" -#: src/control-flow/match-expressions.md:12 -msgid "\"mv\"" -msgstr "\"mv\"" +#: src/user-defined-types/enums.md:71 +msgid "" +"Null pointer optimization: For [some types](https://doc.rust-lang.org/std/" +"option/#representation), Rust guarantees that `size_of::()` equals " +"`size_of::>()`." +msgstr "" -#: src/control-flow/match-expressions.md:12 -msgid "\"Let's move some files\"" +#: src/user-defined-types/enums.md:75 +msgid "" +"Example code if you want to show how the bitwise representation _may_ look " +"like in practice. It's important to note that the compiler provides no " +"guarantees regarding this representation, therefore this is totally unsafe." msgstr "" -#: src/control-flow/match-expressions.md:13 -msgid "\"rm\"" -msgstr "\"rm\"" +#: src/user-defined-types/enums.md:112 +msgid "" +"More complex example if you want to discuss what happens when we chain more " +"than 256 `Option`s together." +msgstr "" -#: src/control-flow/match-expressions.md:13 -msgid "\"Uh, dangerous!\"" +#: src/user-defined-types/static-and-const.md:3 +msgid "" +"Static and constant variables are two different ways to create globally-" +"scoped values that cannot be moved or reallocated during the execution of " +"the program." msgstr "" -#: src/control-flow/match-expressions.md:14 -msgid "\"Hmm, no program name?\"" +#: src/user-defined-types/static-and-const.md:6 +msgid "`const`" msgstr "" -#: src/control-flow/match-expressions.md:15 -msgid "\"Unknown program name!\"" +#: src/user-defined-types/static-and-const.md:8 +msgid "" +"Constant variables are evaluated at compile time and their values are " +"inlined wherever they are used:" msgstr "" -#: src/control-flow/match-expressions.md:20 +#: src/user-defined-types/static-and-const.md:30 msgid "" -"Like `if let`, each match arm must have the same type. The type is the last " -"expression of the block, if any. In the example above, the type is `()`." +"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html) these are inlined upon use." msgstr "" -#: src/control-flow/match-expressions.md:28 -msgid "Save the match expression to a variable and print it out." +#: src/user-defined-types/static-and-const.md:32 +msgid "" +"Only functions marked `const` can be called at compile time to generate " +"`const` values. `const` functions can however be called at runtime." msgstr "" -#: src/control-flow/match-expressions.md:29 -msgid "Remove `.as_deref()` and explain the error." +#: src/user-defined-types/static-and-const.md:34 +msgid "`static`" msgstr "" -#: src/control-flow/match-expressions.md:30 +#: src/user-defined-types/static-and-const.md:36 msgid "" -"`std::env::args().next()` returns an `Option`, but we cannot match " -"against `String`." +"Static variables will live during the whole execution of the program, and " +"therefore will not move:" msgstr "" -#: src/control-flow/match-expressions.md:31 +#: src/user-defined-types/static-and-const.md:39 +msgid "\"Welcome to RustOS 3.14\"" +msgstr "\"Velkommen til RustOS 3.14\"" + +#: src/user-defined-types/static-and-const.md:42 +msgid "\"{BANNER}\"" +msgstr "\"{BANNER}\"" + +#: src/user-defined-types/static-and-const.md:46 msgid "" -"`as_deref()` transforms an `Option` to `Option<&T::Target>`. In our case, " -"this turns `Option` into `Option<&str>`." +"As noted in the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html), these are not inlined upon use and have an actual " +"associated memory location. This is useful for unsafe and embedded code, " +"and the variable lives through the entirety of the program execution. When a " +"globally-scoped value does not have a reason to need object identity, " +"`const` is generally preferred." msgstr "" -#: src/control-flow/match-expressions.md:32 -msgid "" -"We can now use pattern matching to match against the `&str` inside `Option`." +#: src/user-defined-types/static-and-const.md:53 +msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." msgstr "" -#: src/pattern-matching.md:3 +#: src/user-defined-types/static-and-const.md:54 msgid "" -"The `match` keyword let you match a value against one or more _patterns_. " -"The comparisons are done from top to bottom and the first match wins." +"`static`, on the other hand, is much more similar to a `const` or mutable " +"global variable in C++." msgstr "" -#: src/pattern-matching.md:6 -msgid "The patterns can be simple values, similarly to `switch` in C and C++:" +#: src/user-defined-types/static-and-const.md:55 +msgid "" +"`static` provides object identity: an address in memory and state as " +"required by types with interior mutability such as `Mutex`." msgstr "" -#: src/pattern-matching.md:13 -msgid "'q'" -msgstr "'q'" +#: src/user-defined-types/static-and-const.md:56 +msgid "" +"It isn't super common that one would need a runtime evaluated constant, but " +"it is helpful and safer than using a static." +msgstr "" -#: src/pattern-matching.md:13 -msgid "\"Quitting\"" +#: src/user-defined-types/static-and-const.md:58 +msgid "Properties table:" msgstr "" -#: src/pattern-matching.md:14 -msgid "'a'" -msgstr "'a'" +#: src/user-defined-types/static-and-const.md:60 +#: src/chromium/adding-third-party-crates.md:6 +msgid "Property" +msgstr "Egenskab" -#: src/pattern-matching.md:14 -msgid "'s'" -msgstr "'s'" - -#: src/pattern-matching.md:14 -msgid "'w'" -msgstr "'w'" +#: src/user-defined-types/static-and-const.md:60 +msgid "Static" +msgstr "Statisk" -#: src/pattern-matching.md:14 -msgid "'d'" -msgstr "'d'" +#: src/user-defined-types/static-and-const.md:60 +msgid "Constant" +msgstr "Konstant" -#: src/pattern-matching.md:14 -msgid "\"Moving around\"" -msgstr "" +#: src/user-defined-types/static-and-const.md:62 +msgid "Has an address in memory" +msgstr "Har en adresse i hukommelsen" -#: src/pattern-matching.md:15 -msgid "'0'" -msgstr "'0'" +#: src/user-defined-types/static-and-const.md:62 +#: src/user-defined-types/static-and-const.md:63 +#: src/user-defined-types/static-and-const.md:65 +#: src/user-defined-types/static-and-const.md:66 +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +msgid "Yes" +msgstr "Ja" -#: src/pattern-matching.md:15 -msgid "'9'" -msgstr "'9'" +#: src/user-defined-types/static-and-const.md:62 +msgid "No (inlined)" +msgstr "Nej (inlinet)" -#: src/pattern-matching.md:15 -msgid "\"Number input\"" +#: src/user-defined-types/static-and-const.md:63 +msgid "Lives for the entire duration of the program" msgstr "" -#: src/pattern-matching.md:16 -msgid "\"Something else\"" +#: src/user-defined-types/static-and-const.md:63 +#: src/user-defined-types/static-and-const.md:64 +#: src/user-defined-types/static-and-const.md:66 +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "No" +msgstr "Nej" + +#: src/user-defined-types/static-and-const.md:64 +msgid "Can be mutable" msgstr "" -#: src/pattern-matching.md:21 -msgid "The `_` pattern is a wildcard pattern which matches any value." +#: src/user-defined-types/static-and-const.md:64 +msgid "Yes (unsafe)" +msgstr "Ja (_unsafe_)" + +#: src/user-defined-types/static-and-const.md:65 +msgid "Evaluated at compile time" +msgstr "Evalueret ved kompileringstid" + +#: src/user-defined-types/static-and-const.md:65 +msgid "Yes (initialised at compile time)" +msgstr "Ja (initialiseret ved kompileringstid)" + +#: src/user-defined-types/static-and-const.md:66 +msgid "Inlined wherever it is used" msgstr "" -#: src/pattern-matching.md:26 +#: src/user-defined-types/static-and-const.md:70 msgid "" -"You might point out how some specific characters are being used when in a " -"pattern" +"Because `static` variables are accessible from any thread, they must be " +"`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" +"lang.org/std/sync/struct.Mutex.html), atomic or similar." msgstr "" -#: src/pattern-matching.md:27 -msgid "`|` as an `or`" +#: src/user-defined-types/static-and-const.md:74 +msgid "Thread-local data can be created with the macro `std::thread_local`." msgstr "" -#: src/pattern-matching.md:28 -msgid "`..` can expand as much as it needs to be" +#: src/user-defined-types/aliases.md:3 +msgid "" +"A type alias creates a name for another type. The two types can be used " +"interchangeably." msgstr "" -#: src/pattern-matching.md:29 -msgid "`1..=5` represents an inclusive range" +#: src/user-defined-types/aliases.md:12 +msgid "// Aliases are more useful with long, complex types:\n" msgstr "" -#: src/pattern-matching.md:30 -msgid "`_` is a wild card" +#: src/user-defined-types/aliases.md:21 +msgid "C programmers will recognize this as similar to a `typedef`." msgstr "" -#: src/pattern-matching.md:31 +#: src/user-defined-types/exercise.md:3 msgid "" -"It can be useful to show how binding works, by for instance replacing a " -"wildcard character with a variable, or removing the quotes around `q`." +"We will create a data structure to represent an event in an elevator control " +"system. It is up to you to define the types and functions to construct " +"various events. Use `#[derive(Debug)]` to allow the types to be formatted " +"with `{:?}`." msgstr "" -#: src/pattern-matching.md:32 -msgid "You can demonstrate matching on a reference." +#: src/user-defined-types/exercise.md:8 src/user-defined-types/solution.md:39 +msgid "/// The car has arrived on the given floor.\n" msgstr "" -#: src/pattern-matching.md:33 +#: src/user-defined-types/exercise.md:12 src/user-defined-types/solution.md:44 +#, fuzzy +msgid "/// The car doors have opened.\n" +msgstr "/// Clear to send.\n" + +#: src/user-defined-types/exercise.md:17 src/user-defined-types/solution.md:49 +#, fuzzy +msgid "/// The car doors have closed.\n" +msgstr "/// Clear to send.\n" + +#: src/user-defined-types/exercise.md:22 src/user-defined-types/solution.md:54 msgid "" -"This might be a good time to bring up the concept of irrefutable patterns, " -"as the term can show up in error messages." +"/// A directional button was pressed in an elevator lobby on the given " +"floor.\n" msgstr "" -#: src/pattern-matching/destructuring-enums.md:3 -msgid "" -"Patterns can also be used to bind variables to parts of your values. This is " -"how you inspect the structure of your types. Let us start with a simple " -"`enum` type:" +#: src/user-defined-types/exercise.md:27 src/user-defined-types/solution.md:59 +msgid "/// A floor button was pressed in the elevator car.\n" msgstr "" -#: src/pattern-matching/destructuring-enums.md:16 -msgid "\"cannot divide {n} into two equal parts\"" +#: src/user-defined-types/exercise.md:35 src/user-defined-types/solution.md:67 +msgid "\"A ground floor passenger has pressed the up button: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-enums.md:23 -msgid "\"{n} divided in two is {half}\"" +#: src/user-defined-types/exercise.md:39 src/user-defined-types/solution.md:71 +msgid "\"The car has arrived on the ground floor: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-enums.md:24 -msgid "\"sorry, an error happened: {msg}\"" +#: src/user-defined-types/exercise.md:42 src/user-defined-types/solution.md:74 +#, fuzzy +msgid "\"The car door opened: {:?}\"" +msgstr "\"Modtaget: {:?}\"" + +#: src/user-defined-types/exercise.md:44 src/user-defined-types/solution.md:76 +msgid "\"A passenger has pressed the 3rd floor button: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-enums.md:29 -msgid "" -"Here we have used the arms to _destructure_ the `Result` value. In the first " -"arm, `half` is bound to the value inside the `Ok` variant. In the second " -"arm, `msg` is bound to the error message." +#: src/user-defined-types/exercise.md:47 src/user-defined-types/solution.md:79 +msgid "\"The car door closed: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-enums.md:36 -msgid "" -"The `if`/`else` expression is returning an enum that is later unpacked with " -"a `match`." +#: src/user-defined-types/exercise.md:48 src/user-defined-types/solution.md:80 +msgid "\"The car has arrived on the 3rd floor: {:?}\"" msgstr "" -#: src/pattern-matching/destructuring-enums.md:37 +#: src/user-defined-types/exercise.md:52 msgid "" -"You can try adding a third variant to the enum definition and displaying the " -"errors when running the code. Point out the places where your code is now " -"inexhaustive and how the compiler tries to give you hints." +"This exercise only requires creating data structures. The next part of the " +"course will cover getting data out of these structures." msgstr "" -#: src/pattern-matching/destructuring-structs.md:3 -msgid "You can also destructure `structs`:" +#: src/user-defined-types/solution.md:4 +msgid "" +"/// An event in the elevator system that the controller must react to.\n" msgstr "" -#: src/pattern-matching/destructuring-structs.md:15 -msgid "\"x.0 = 1, b = {b}, y = {y}\"" -msgstr "\"x.0 = 1, b = {b}, y = {y}\"" - -#: src/pattern-matching/destructuring-structs.md:16 -msgid "\"y = 2, x = {i:?}\"" -msgstr "\"y = 2, x = {i:?}\"" - -#: src/pattern-matching/destructuring-structs.md:17 -msgid "\"y = {y}, other fields were ignored\"" -msgstr "\"y = {y}, andre felter blev ignoreret\"" +#: src/user-defined-types/solution.md:7 +msgid "/// A button was pressed.\n" +msgstr "" -#: src/pattern-matching/destructuring-structs.md:23 -msgid "Change the literal values in `foo` to match with the other patterns." +#: src/user-defined-types/solution.md:10 +msgid "/// The car has arrived at the given floor.\n" msgstr "" -#: src/pattern-matching/destructuring-structs.md:24 -msgid "Add a new field to `Foo` and make changes to the pattern as needed." +#: src/user-defined-types/solution.md:13 +msgid "/// The car's doors have opened.\n" msgstr "" -#: src/pattern-matching/destructuring-structs.md:25 -msgid "" -"The distinction between a capture and a constant expression can be hard to " -"spot. Try changing the `2` in the second arm to a variable, and see that it " -"subtly doesn't work. Change it to a `const` and see it working again." +#: src/user-defined-types/solution.md:16 +msgid "/// The car's doors have closed.\n" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:3 -msgid "" -"You can destructure arrays, tuples, and slices by matching on their elements:" +#: src/user-defined-types/solution.md:19 +msgid "/// A floor is represented as an integer.\n" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:9 -msgid "\"Tell me about {triple:?}\"" -msgstr "\"Fortæl mig om {triple:?}\"" +#: src/user-defined-types/solution.md:22 +msgid "/// A direction of travel.\n" +msgstr "" -#: src/pattern-matching/destructuring-arrays.md:11 -#: src/pattern-matching/destructuring-arrays.md:34 -msgid "\"First is 0, y = {y}, and z = {z}\"" +#: src/user-defined-types/solution.md:29 +msgid "/// A user-accessible button.\n" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:12 -#: src/pattern-matching/destructuring-arrays.md:35 -msgid "\"First is 1 and the rest were ignored\"" +#: src/user-defined-types/solution.md:33 +msgid "/// A button in the elevator lobby on the given floor.\n" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:13 -#: src/pattern-matching/destructuring-arrays.md:36 -msgid "\"All elements were ignored\"" +#: src/user-defined-types/solution.md:36 +msgid "/// A floor button within the car.\n" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:21 +#: src/welcome-day-2.md:1 +msgid "Welcome to Day 2" +msgstr "Velkommen til Dag 2" + +#: src/welcome-day-2.md:3 msgid "" -"Destructuring of slices of unknown length also works with patterns of fixed " -"length." +"Now that we have seen a fair amount of Rust, today will focus on Rust's type " +"system:" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:32 -msgid "\"Tell me about {slice:?}\"" -msgstr "\"Fortæl mig om {slice:?}\"" - -#: src/pattern-matching/destructuring-arrays.md:41 -msgid "Create a new pattern using `_` to represent an element. " +#: src/welcome-day-2.md:6 +msgid "Pattern matching: extracting data from structures." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:42 -msgid "Add more values to the array." +#: src/welcome-day-2.md:7 +msgid "Methods: associating functions with types." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:43 -msgid "" -"Point out that how `..` will expand to account for different number of " -"elements." +#: src/welcome-day-2.md:8 +msgid "Traits: behaviors shared by multiple types." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:44 -msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" +#: src/welcome-day-2.md:9 +msgid "Generics: parameterizing types on other types." msgstr "" -#: src/pattern-matching/match-guards.md:3 +#: src/welcome-day-2.md:10 msgid "" -"When matching, you can add a _guard_ to a pattern. This is an arbitrary " -"Boolean expression which will be executed if the pattern matches:" +"Standard library types and traits: a tour of Rust's rich standard library." msgstr "" -#: src/pattern-matching/match-guards.md:10 -msgid "\"Tell me about {pair:?}\"" +#: src/welcome-day-2.md:15 +msgid "[Welcome](./welcome-day-2.md) (3 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:12 -msgid "\"These are twins\"" -msgstr "\"Disse er tvillinger\"" - -#: src/pattern-matching/match-guards.md:13 -msgid "\"Antimatter, kaboom!\"" +#: src/welcome-day-2.md:16 +msgid "[Pattern Matching](./pattern-matching.md) (50 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:14 -msgid "\"The first one is odd\"" +#: src/welcome-day-2.md:17 +msgid "[Methods and Traits](./methods-and-traits.md) (1 hour and 5 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:15 -msgid "\"No correlation...\"" +#: src/welcome-day-2.md:18 +msgid "[Generics](./generics.md) (45 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:23 +#: src/welcome-day-2.md:20 msgid "" -"Match guards as a separate syntax feature are important and necessary when " -"we wish to concisely express more complex ideas than patterns alone would " -"allow." +"Including 10 minute breaks, this session should take about 3 hours and 15 " +"minutes" msgstr "" -#: src/pattern-matching/match-guards.md:24 -msgid "" -"They are not the same as separate `if` expression inside of the match arm. " -"An `if` expression inside of the branch block (after `=>`) happens after the " -"match arm is selected. Failing the `if` condition inside of that block won't " -"result in other arms of the original `match` expression being considered." +#: src/pattern-matching.md:4 +msgid "[Destructuring](./pattern-matching/destructuring.md) (10 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:26 -msgid "You can use the variables defined in the pattern in your if expression." +#: src/pattern-matching.md:5 +msgid "[Let Control Flow](./pattern-matching/let-control-flow.md) (10 minutes)" msgstr "" -#: src/pattern-matching/match-guards.md:27 +#: src/pattern-matching.md:6 msgid "" -"The condition defined in the guard applies to every expression in a pattern " -"with an `|`." +"[Exercise: Expression Evaluation](./pattern-matching/exercise.md) (30 " +"minutes)" msgstr "" -#: src/exercises/day-1/afternoon.md:1 -msgid "Day 1: Afternoon Exercises" +#: src/pattern-matching/destructuring.md:3 +msgid "Like tuples, structs and enums can also be destructured by matching:" msgstr "" -#: src/exercises/day-1/afternoon.md:3 -msgid "We will look at two things:" -msgstr "" +#: src/pattern-matching/destructuring.md:5 +#: src/pattern-matching/destructuring.md:58 +msgid "Structs" +msgstr "Strukturer" -#: src/exercises/day-1/afternoon.md:5 -msgid "The Luhn algorithm," -msgstr "Luhn-algorithmen," +#: src/pattern-matching/destructuring.md:17 +msgid "\"x.0 = 1, b = {b}, y = {y}\"" +msgstr "\"x.0 = 1, b = {b}, y = {y}\"" -#: src/exercises/day-1/afternoon.md:7 -msgid "An exercise on pattern matching." -msgstr "" +#: src/pattern-matching/destructuring.md:18 +msgid "\"y = 2, x = {i:?}\"" +msgstr "\"y = 2, x = {i:?}\"" -#: src/exercises/day-1/afternoon.md:11 src/exercises/day-2/afternoon.md:7 -#: src/exercises/bare-metal/afternoon.md:7 -#: src/exercises/concurrency/afternoon.md:13 +#: src/pattern-matching/destructuring.md:19 +msgid "\"y = {y}, other fields were ignored\"" +msgstr "\"y = {y}, andre felter blev ignoreret\"" + +#: src/pattern-matching/destructuring.md:25 msgid "" -"After looking at the exercises, you can look at the [solutions](solutions-" -"afternoon.md) provided." +"Patterns can also be used to bind variables to parts of your values. This is " +"how you inspect the structure of your types. Let us start with a simple " +"`enum` type:" msgstr "" -#: src/exercises/day-1/luhn.md:3 -msgid "" -"The [Luhn algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is used " -"to validate credit card numbers. The algorithm takes a string as input and " -"does the following to validate the credit card number:" +#: src/pattern-matching/destructuring.md:38 +msgid "\"cannot divide {n} into two equal parts\"" msgstr "" -#: src/exercises/day-1/luhn.md:7 -msgid "Ignore all spaces. Reject number with less than two digits." +#: src/pattern-matching/destructuring.md:45 +msgid "\"{n} divided in two is {half}\"" msgstr "" -#: src/exercises/day-1/luhn.md:9 -msgid "" -"Moving from **right to left**, double every second digit: for the number " -"`1234`, we double `3` and `1`. For the number `98765`, we double `6` and `8`." +#: src/pattern-matching/destructuring.md:46 +msgid "\"sorry, an error happened: {msg}\"" msgstr "" -#: src/exercises/day-1/luhn.md:12 +#: src/pattern-matching/destructuring.md:51 msgid "" -"After doubling a digit, sum the digits if the result is greater than 9. So " -"doubling `7` becomes `14` which becomes `1 + 4 = 5`." +"Here we have used the arms to _destructure_ the `Result` value. In the first " +"arm, `half` is bound to the value inside the `Ok` variant. In the second " +"arm, `msg` is bound to the error message." msgstr "" -#: src/exercises/day-1/luhn.md:15 -msgid "Sum all the undoubled and doubled digits." +#: src/pattern-matching/destructuring.md:60 +msgid "Change the literal values in `foo` to match with the other patterns." msgstr "" -#: src/exercises/day-1/luhn.md:17 -msgid "The credit card number is valid if the sum ends with `0`." +#: src/pattern-matching/destructuring.md:61 +msgid "Add a new field to `Foo` and make changes to the pattern as needed." msgstr "" -#: src/exercises/day-1/luhn.md:19 +#: src/pattern-matching/destructuring.md:62 msgid "" -"Copy the code below to and implement the " -"function." +"The distinction between a capture and a constant expression can be hard to " +"spot. Try changing the `2` in the second arm to a variable, and see that it " +"subtly doesn't work. Change it to a `const` and see it working again." msgstr "" -#: src/exercises/day-1/luhn.md:21 +#: src/pattern-matching/destructuring.md:69 msgid "" -"Try to solve the problem the \"simple\" way first, using `for` loops and " -"integers. Then, revisit the solution and try to implement it with iterators." +"The `if`/`else` expression is returning an enum that is later unpacked with " +"a `match`." msgstr "" -#: src/exercises/day-1/luhn.md:35 -#: src/exercises/day-2/iterators-and-ownership.md:75 -#: src/exercises/day-2/iterators-and-ownership.md:91 -#: src/traits/trait-bounds.md:22 src/traits/impl-trait.md:14 -#: src/exercises/day-3/simple-gui.md:150 src/exercises/day-3/simple-gui.md:151 -#: src/exercises/day-3/simple-gui.md:152 src/testing/test-modules.md:21 -#: src/exercises/day-1/solutions-afternoon.md:43 -msgid "\"foo\"" -msgstr "\"foo\"" +#: src/pattern-matching/destructuring.md:70 +msgid "" +"You can try adding a third variant to the enum definition and displaying the " +"errors when running the code. Point out the places where your code is now " +"inexhaustive and how the compiler tries to give you hints." +msgstr "" -#: src/exercises/day-1/luhn.md:36 src/exercises/day-1/solutions-afternoon.md:44 -msgid "\"foo 0 0\"" -msgstr "\"foo 0 0\"" +#: src/pattern-matching/destructuring.md:71 +msgid "" +"The values in the enum variants can only be accessed after being pattern " +"matched. The pattern binds references to the fields in the \"match arm\" " +"after the `=>`." +msgstr "" -#: src/exercises/day-1/luhn.md:41 src/testing/unit-tests.md:15 -#: src/exercises/day-1/solutions-afternoon.md:49 -#: src/exercises/day-3/solutions-morning.md:92 -#: src/exercises/day-3/solutions-morning.md:94 -#: src/exercises/day-3/solutions-morning.md:98 -#: src/exercises/day-3/solutions-morning.md:112 -#: src/exercises/day-3/solutions-morning.md:116 -msgid "\"\"" -msgstr "\"\"" +#: src/pattern-matching/destructuring.md:72 +msgid "" +"Demonstrate what happens when the search is inexhaustive. Note the advantage " +"the Rust compiler provides by confirming when all cases are handled." +msgstr "" -#: src/exercises/day-1/luhn.md:42 src/exercises/day-1/solutions-afternoon.md:50 -msgid "\" \"" -msgstr "\" \"" +#: src/pattern-matching/let-control-flow.md:3 +msgid "" +"Rust has a few control flow constructs which differ from other languages. " +"They are used for pattern matching:" +msgstr "" -#: src/exercises/day-1/luhn.md:43 src/exercises/day-1/solutions-afternoon.md:51 -msgid "\" \"" -msgstr "\" \"" +#: src/pattern-matching/let-control-flow.md:6 +#: src/pattern-matching/let-control-flow.md:9 +msgid "`if let` expressions" +msgstr "`if let`-udtryk" -#: src/exercises/day-1/luhn.md:44 src/exercises/day-1/solutions-afternoon.md:52 -msgid "\" \"" -msgstr "\" \"" +#: src/pattern-matching/let-control-flow.md:7 +msgid "`while let` expressions" +msgstr "`while let`-udtryk" -#: src/exercises/day-1/luhn.md:49 src/exercises/day-1/solutions-afternoon.md:57 -msgid "\"0\"" -msgstr "\"0\"" +#: src/pattern-matching/let-control-flow.md:8 +msgid "`match` expressions" +msgstr "`match`-udtryk" -#: src/exercises/day-1/luhn.md:54 src/exercises/day-1/solutions-afternoon.md:62 -msgid "\" 0 0 \"" -msgstr "\" 0 0 \"" +#: src/pattern-matching/let-control-flow.md:11 +msgid "" +"The [`if let` expression](https://doc.rust-lang.org/reference/expressions/if-" +"expr.html#if-let-expressions) lets you execute different code depending on " +"whether a value matches a pattern:" +msgstr "" -#: src/exercises/day-1/luhn.md:59 src/exercises/day-1/solutions-afternoon.md:67 -msgid "\"4263 9826 4026 9299\"" -msgstr "\"4263 9826 4026 9299\"" +#: src/pattern-matching/let-control-flow.md:23 +#, fuzzy +msgid "\"slept for {:?}\"" +msgstr "\"expr: {:?}\"" -#: src/exercises/day-1/luhn.md:60 src/exercises/day-1/solutions-afternoon.md:68 -msgid "\"4539 3195 0343 6467\"" -msgstr "\"4539 3195 0343 6467\"" +#: src/pattern-matching/let-control-flow.md:32 +msgid "" +"For the common case of matching a pattern and returning from the function, " +"use [`let else`](https://doc.rust-lang.org/rust-by-example/flow_control/" +"let_else.html). The \"else\" case must diverge (`return`, `break`, or panic " +"- anything but falling off the end of the block)." +msgstr "" -#: src/exercises/day-1/luhn.md:61 src/exercises/day-1/solutions-afternoon.md:69 -msgid "\"7992 7398 713\"" -msgstr "\"7992 7398 713\"" +#: src/pattern-matching/let-control-flow.md:43 +#: src/pattern-matching/let-control-flow.md:101 +#, fuzzy +msgid "\"got None\"" +msgstr "\"none\"" -#: src/exercises/day-1/luhn.md:66 src/exercises/day-1/solutions-afternoon.md:74 -msgid "\"4223 9826 4026 9299\"" -msgstr "\"4223 9826 4026 9299\"" +#: src/pattern-matching/let-control-flow.md:49 +#: src/pattern-matching/let-control-flow.md:105 +#, fuzzy +msgid "\"got empty string\"" +msgstr "\"En streng\"" -#: src/exercises/day-1/luhn.md:67 src/exercises/day-1/solutions-afternoon.md:75 -msgid "\"4539 3195 0343 6476\"" -msgstr "\"4539 3195 0343 6476\"" +#: src/pattern-matching/let-control-flow.md:55 +#: src/pattern-matching/let-control-flow.md:109 +msgid "\"not a hex digit\"" +msgstr "" -#: src/exercises/day-1/luhn.md:68 src/exercises/day-1/solutions-afternoon.md:76 -msgid "\"8273 1232 7352 0569\"" -msgstr "\"8273 1232 7352 0569\"" +#: src/pattern-matching/let-control-flow.md:60 +#: src/pattern-matching/solution.md:128 +msgid "\"result: {:?}\"" +msgstr "\"result: {:?}\"" -#: src/exercises/day-1/pattern-matching.md:1 -msgid "Exercise: Expression Evaluation" -msgstr "" +#: src/pattern-matching/let-control-flow.md:60 +#: src/methods-and-traits/exercise.md:121 +#: src/methods-and-traits/exercise.md:122 +#: src/methods-and-traits/exercise.md:123 src/generics/trait-bounds.md:16 +#: src/smart-pointers/solution.md:66 src/smart-pointers/solution.md:69 +#: src/testing/googletest.md:11 src/testing/googletest.md:12 +#: src/testing/solution.md:89 +msgid "\"foo\"" +msgstr "\"foo\"" -#: src/exercises/day-1/pattern-matching.md:3 -msgid "Let's write a simple recursive evaluator for arithmetic expressions. " +#: src/pattern-matching/let-control-flow.md:64 +msgid "" +"Like with `if let`, there is a [`while let`](https://doc.rust-lang.org/" +"reference/expressions/loop-expr.html#predicate-pattern-loops) variant which " +"repeatedly tests a value against a pattern:" msgstr "" -#: src/exercises/day-1/pattern-matching.md:6 -#: src/exercises/day-1/solutions-afternoon.md:83 -msgid "/// An operation to perform on two subexpressions.\n" +#: src/pattern-matching/let-control-flow.md:78 +msgid "" +"Here [`String::pop`](https://doc.rust-lang.org/stable/std/string/struct." +"String.html#method.pop) returns `Some(c)` until the string is empty, after " +"which it will return `None`. The `while let` lets us keep iterating through " +"all items." msgstr "" -#: src/exercises/day-1/pattern-matching.md:14 -#: src/exercises/day-1/solutions-afternoon.md:91 -msgid "/// An expression, in tree form.\n" +#: src/pattern-matching/let-control-flow.md:86 +msgid "if-let" msgstr "" -#: src/exercises/day-1/pattern-matching.md:18 -#: src/exercises/day-1/solutions-afternoon.md:95 -msgid "/// An operation on two subexpressions.\n" +#: src/pattern-matching/let-control-flow.md:88 +msgid "" +"Unlike `match`, `if let` does not have to cover all branches. This can make " +"it more concise than `match`." msgstr "" -#: src/exercises/day-1/pattern-matching.md:25 -#: src/exercises/day-1/solutions-afternoon.md:102 -msgid "/// A literal value\n" +#: src/pattern-matching/let-control-flow.md:89 +msgid "A common usage is handling `Some` values when working with `Option`." msgstr "" -#: src/exercises/day-1/pattern-matching.md:28 -#: src/exercises/day-1/solutions-afternoon.md:105 -msgid "/// The result of evaluating an expression.\n" +#: src/pattern-matching/let-control-flow.md:90 +msgid "" +"Unlike `match`, `if let` does not support guard clauses for pattern matching." msgstr "" -#: src/exercises/day-1/pattern-matching.md:32 -#: src/exercises/day-1/solutions-afternoon.md:109 -msgid "/// Evaluation was successful, with the given result.\n" +#: src/pattern-matching/let-control-flow.md:92 +msgid "let-else" msgstr "" -#: src/exercises/day-1/pattern-matching.md:34 -#: src/exercises/day-1/solutions-afternoon.md:111 -msgid "/// Evaluation failed, with the given error message.\n" +#: src/pattern-matching/let-control-flow.md:94 +msgid "" +"`if-let`s can pile up, as shown. The `let-else` construct supports " +"flattening this nested code. Rewrite the awkward version for students, so " +"they can see the transformation." msgstr "" -#: src/exercises/day-1/pattern-matching.md:36 -#: src/exercises/day-1/solutions-afternoon.md:113 -msgid "// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" +#: src/pattern-matching/let-control-flow.md:97 +msgid "The rewritten version is:" msgstr "" -#: src/exercises/day-1/pattern-matching.md:95 -#: src/exercises/day-1/solutions-afternoon.md:134 -#: src/exercises/day-1/solutions-afternoon.md:196 -msgid "\"division by zero\"" -msgstr "" +#: src/pattern-matching/let-control-flow.md:116 +#, fuzzy +msgid "while-let" +msgstr "`while let`-lykker" -#: src/exercises/day-1/pattern-matching.md:100 +#: src/pattern-matching/let-control-flow.md:118 msgid "" -"The `Box` type here is a smart pointer, and will be covered in detail later " -"in the course. An expression can be \"boxed\" with `Box::new` as seen in the " -"tests. To evaluate a boxed expression, use the deref operator to \"unbox\" " -"it: `eval(*boxed_expr)`." +"Point out that the `while let` loop will keep going as long as the value " +"matches the pattern." msgstr "" -#: src/exercises/day-1/pattern-matching.md:105 +#: src/pattern-matching/let-control-flow.md:119 msgid "" -"Some expressions cannot be evaluated and will return an error. The `Res` " -"type represents either a successful value or an error with a message. This " -"is very similar to the standard-library `Result` which we will see later." +"You could rewrite the `while let` loop as an infinite loop with an if " +"statement that breaks when there is no value to unwrap for `name.pop()`. The " +"`while let` provides syntactic sugar for the above scenario." msgstr "" -#: src/exercises/day-1/pattern-matching.md:109 +#: src/pattern-matching/exercise.md:3 msgid "" -"Copy and paste the code into the Rust playground, and begin implementing " -"`eval`. The final product should pass the tests. It may be helpful to use " -"`todo!()` and get the tests to pass one-by-one." +"Let's write a simple recursive evaluator for arithmetic expressions. Start " +"with an enum defining the binary operations:" msgstr "" -#: src/exercises/day-1/pattern-matching.md:113 -msgid "" -"If you finish early, try writing a test that results in an integer overflow. " -"How could you handle this with `Res::Err` instead of a panic?" +#: src/pattern-matching/exercise.md:7 src/pattern-matching/solution.md:4 +msgid "/// An operation to perform on two subexpressions.\n" msgstr "" -#: src/welcome-day-2.md:1 -msgid "Welcome to Day 2" -msgstr "Velkommen til Dag 2" - -#: src/welcome-day-2.md:3 -msgid "Now that we have seen a fair amount of Rust, we will continue with:" +#: src/pattern-matching/exercise.md:15 src/pattern-matching/solution.md:12 +msgid "/// An expression, in tree form.\n" msgstr "" -#: src/welcome-day-2.md:5 -msgid "" -"Memory management: stack vs heap, manual memory management, scope-based " -"memory management, and garbage collection." +#: src/pattern-matching/exercise.md:19 src/pattern-matching/solution.md:16 +msgid "/// An operation on two subexpressions.\n" msgstr "" -#: src/welcome-day-2.md:8 -msgid "" -"Ownership: move semantics, copying and cloning, borrowing, and lifetimes." +#: src/pattern-matching/exercise.md:26 src/pattern-matching/solution.md:23 +msgid "/// A literal value\n" msgstr "" -#: src/welcome-day-2.md:10 -msgid "Structs and methods." -msgstr "Strenge og iteratorer." +#: src/pattern-matching/exercise.md:29 src/pattern-matching/solution.md:26 +msgid "/// The result of evaluating an expression.\n" +msgstr "" -#: src/welcome-day-2.md:12 -msgid "" -"The Standard Library: `String`, `Option` and `Result`, `Vec`, `HashMap`, " -"`Rc` and `Arc`." +#: src/pattern-matching/exercise.md:33 src/pattern-matching/solution.md:30 +msgid "/// Evaluation was successful, with the given result.\n" msgstr "" -#: src/welcome-day-2.md:15 -msgid "Modules: visibility, paths, and filesystem hierarchy." +#: src/pattern-matching/exercise.md:35 src/pattern-matching/solution.md:32 +msgid "/// Evaluation failed, with the given error message.\n" msgstr "" -#: src/memory-management.md:3 -msgid "Traditionally, languages have fallen into two broad categories:" +#: src/pattern-matching/exercise.md:37 src/pattern-matching/solution.md:34 +msgid "// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" msgstr "" -#: src/memory-management.md:5 -msgid "Full control via manual memory management: C, C++, Pascal, ..." +#: src/pattern-matching/exercise.md:96 src/pattern-matching/solution.md:55 +#: src/pattern-matching/solution.md:117 +msgid "\"division by zero\"" msgstr "" -#: src/memory-management.md:6 +#: src/pattern-matching/exercise.md:101 msgid "" -"Full safety via automatic memory management at runtime: Java, Python, Go, " -"Haskell, ..." +"The `Box` type here is a smart pointer, and will be covered in detail later " +"in the course. An expression can be \"boxed\" with `Box::new` as seen in the " +"tests. To evaluate a boxed expression, use the deref operator to \"unbox\" " +"it: `eval(*boxed_expr)`." msgstr "" -#: src/memory-management.md:8 -msgid "Rust offers a new mix:" +#: src/pattern-matching/exercise.md:106 +msgid "" +"Some expressions cannot be evaluated and will return an error. The `Res` " +"type represents either a successful value or an error with a message. This " +"is very similar to the standard-library `Result` which we will see later." msgstr "" -#: src/memory-management.md:10 +#: src/pattern-matching/exercise.md:110 msgid "" -"Full control _and_ safety via compile time enforcement of correct memory " -"management." +"Copy and paste the code into the Rust playground, and begin implementing " +"`eval`. The final product should pass the tests. It may be helpful to use " +"`todo!()` and get the tests to pass one-by-one. You can also skip a test " +"temporarily with `#[ignore]`:" msgstr "" -#: src/memory-management.md:13 -msgid "It does this with an explicit ownership concept." +#: src/pattern-matching/exercise.md:122 +msgid "" +"If you finish early, try writing a test that results in an integer overflow. " +"How could you handle this with `Res::Err` instead of a panic?" msgstr "" -#: src/memory-management.md:15 -msgid "First, let's refresh how memory management works." +#: src/pattern-matching/solution.md:127 +msgid "\"expr: {:?}\"" +msgstr "\"expr: {:?}\"" + +#: src/methods-and-traits.md:4 +msgid "[Methods](./methods-and-traits/methods.md) (10 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:1 -msgid "The Stack vs The Heap" +#: src/methods-and-traits.md:5 +msgid "[Traits](./methods-and-traits/traits.md) (10 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:3 -msgid "Stack: Continuous area of memory for local variables." +#: src/methods-and-traits.md:6 +msgid "[Deriving](./methods-and-traits/deriving.md) (5 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:4 -msgid "Values have fixed sizes known at compile time." +#: src/methods-and-traits.md:7 +msgid "[Trait Objects](./methods-and-traits/trait-objects.md) (10 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:5 -msgid "Extremely fast: just move a stack pointer." +#: src/methods-and-traits.md:8 +msgid "[Exercise: GUI Library](./methods-and-traits/exercise.md) (30 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:6 -msgid "Easy to manage: follows function calls." +#: src/methods-and-traits/methods.md:3 +msgid "" +"Rust allows you to associate functions with your new types. You do this with " +"an `impl` block:" msgstr "" -#: src/memory-management/stack-vs-heap.md:7 -msgid "Great memory locality." +#: src/methods-and-traits/methods.md:14 +msgid "// No receiver, a static method\n" msgstr "" -#: src/memory-management/stack-vs-heap.md:9 -msgid "Heap: Storage of values outside of function calls." +#: src/methods-and-traits/methods.md:18 +msgid "// Exclusive borrowed read-write access to self\n" msgstr "" -#: src/memory-management/stack-vs-heap.md:10 -msgid "Values have dynamic sizes determined at runtime." +#: src/methods-and-traits/methods.md:22 +msgid "// Shared and read-only borrowed access to self\n" msgstr "" -#: src/memory-management/stack-vs-heap.md:11 -msgid "Slightly slower than the stack: some book-keeping needed." +#: src/methods-and-traits/methods.md:23 +msgid "\"Recorded {} laps for {}:\"" msgstr "" -#: src/memory-management/stack-vs-heap.md:12 -msgid "No guarantee of memory locality." +#: src/methods-and-traits/methods.md:25 +msgid "\"Lap {idx}: {lap} sec\"" msgstr "" -#: src/memory-management/stack.md:1 -msgid "Stack and Heap Example" -msgstr "Eksempel på stak og heap" +#: src/methods-and-traits/methods.md:29 +msgid "// Exclusive ownership of self\n" +msgstr "" -#: src/memory-management/stack.md:3 -msgid "" -"Creating a `String` puts fixed-sized metadata on the stack and dynamically " -"sized data, the actual string, on the heap:" +#: src/methods-and-traits/methods.md:31 +msgid "\"Race {} is finished, total lap time: {}\"" msgstr "" -#: src/memory-management/stack.md:8 src/memory-management/stack.md:36 -#: src/std/string.md:8 src/traits/read-write.md:35 src/testing/unit-tests.md:20 -#: src/testing/unit-tests.md:25 src/testing/test-modules.md:12 -#: src/concurrency/scoped-threads.md:9 src/concurrency/scoped-threads.md:26 -msgid "\"Hello\"" -msgstr "\"Hello\"" +#: src/methods-and-traits/methods.md:36 +msgid "\"Monaco Grand Prix\"" +msgstr "\"Monacos Grand Prix\"" + +#: src/methods-and-traits/methods.md:43 +msgid "// race.add_lap(42);\n" +msgstr "// race.add_lap(42);\n" -#: src/memory-management/stack.md:28 +#: src/methods-and-traits/methods.md:47 msgid "" -"Mention that a `String` is backed by a `Vec`, so it has a capacity and " -"length and can grow if mutable via reallocation on the heap." +"The `self` arguments specify the \"receiver\" - the object the method acts " +"on. There are several common receivers for a method:" msgstr "" -#: src/memory-management/stack.md:30 +#: src/methods-and-traits/methods.md:50 msgid "" -"If students ask about it, you can mention that the underlying memory is heap " -"allocated using the [System Allocator](https://doc.rust-lang.org/std/alloc/" -"struct.System.html) and custom allocators can be implemented using the " -"[Allocator API](https://doc.rust-lang.org/std/alloc/index.html)" +"`&self`: borrows the object from the caller using a shared and immutable " +"reference. The object can be used again afterwards." msgstr "" -#: src/memory-management/stack.md:32 +#: src/methods-and-traits/methods.md:52 msgid "" -"We can inspect the memory layout with `unsafe` code. However, you should " -"point out that this is rightfully unsafe!" +"`&mut self`: borrows the object from the caller using a unique and mutable " +"reference. The object can be used again afterwards." msgstr "" -#: src/memory-management/stack.md:37 src/testing/unit-tests.md:7 -#: src/exercises/day-1/solutions-afternoon.md:11 -msgid "' '" -msgstr "' '" +#: src/methods-and-traits/methods.md:54 +msgid "" +"`self`: takes ownership of the object and moves it away from the caller. The " +"method becomes the owner of the object. The object will be dropped " +"(deallocated) when the method returns, unless its ownership is explicitly " +"transmitted. Complete ownership does not automatically mean mutability." +msgstr "" -#: src/memory-management/stack.md:38 -msgid "\"world\"" +#: src/methods-and-traits/methods.md:58 +msgid "`mut self`: same as above, but the method can mutate the object." msgstr "" -#: src/memory-management/stack.md:39 +#: src/methods-and-traits/methods.md:59 msgid "" -"// DON'T DO THIS AT HOME! For educational purposes only.\n" -" // String provides no guarantees about its layout, so this could lead " -"to\n" -" // undefined behavior.\n" +"No receiver: this becomes a static method on the struct. Typically used to " +"create constructors which are called `new` by convention." msgstr "" -#: src/memory-management/stack.md:44 -msgid "\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\"" +#: src/methods-and-traits/methods.md:66 +msgid "It can be helpful to introduce methods by comparing them to functions." msgstr "" -#: src/memory-management/manual.md:3 -msgid "You allocate and deallocate heap memory yourself." -msgstr "Du allokerer og deallokerer din heap-memory." - -#: src/memory-management/manual.md:5 +#: src/methods-and-traits/methods.md:67 msgid "" -"If not done with care, this can lead to crashes, bugs, security " -"vulnerabilities, and memory leaks." +"Methods are called on an instance of a type (such as a struct or enum), the " +"first parameter represents the instance as `self`." msgstr "" -#: src/memory-management/manual.md:7 -msgid "C Example" -msgstr "C-eksempel" +#: src/methods-and-traits/methods.md:68 +msgid "" +"Developers may choose to use methods to take advantage of method receiver " +"syntax and to help keep them more organized. By using methods we can keep " +"all the implementation code in one predictable place." +msgstr "" -#: src/memory-management/manual.md:9 -msgid "You must call `free` on every pointer you allocate with `malloc`:" +#: src/methods-and-traits/methods.md:69 +msgid "Point out the use of the keyword `self`, a method receiver." msgstr "" -#: src/memory-management/manual.md:14 +#: src/methods-and-traits/methods.md:70 msgid "" -"//\n" -" // ... lots of code\n" -" //\n" +"Show that it is an abbreviated term for `self: Self` and perhaps show how " +"the struct name could also be used." msgstr "" -#: src/memory-management/manual.md:21 +#: src/methods-and-traits/methods.md:71 msgid "" -"Memory is leaked if the function returns early between `malloc` and `free`: " -"the pointer is lost and we cannot deallocate the memory. Worse, freeing the " -"pointer twice, or accessing a freed pointer can lead to exploitable security " -"vulnerabilities." +"Explain that `Self` is a type alias for the type the `impl` block is in and " +"can be used elsewhere in the block." msgstr "" -#: src/memory-management/scope-based.md:3 +#: src/methods-and-traits/methods.md:72 msgid "" -"Constructors and destructors let you hook into the lifetime of an object." +"Note how `self` is used like other structs and dot notation can be used to " +"refer to individual fields." msgstr "" -#: src/memory-management/scope-based.md:5 +#: src/methods-and-traits/methods.md:73 msgid "" -"By wrapping a pointer in an object, you can free memory when the object is " -"destroyed. The compiler guarantees that this happens, even if an exception " -"is raised." +"This might be a good time to demonstrate how the `&self` differs from `self` " +"by trying to run `finish` twice." msgstr "" -#: src/memory-management/scope-based.md:9 +#: src/methods-and-traits/methods.md:74 msgid "" -"This is often called _resource acquisition is initialization_ (RAII) and " -"gives you smart pointers." +"Beyond variants on `self`, there are also [special wrapper types](https://" +"doc.rust-lang.org/reference/special-types-and-traits.html) allowed to be " +"receiver types, such as `Box`." msgstr "" -#: src/memory-management/scope-based.md:12 -msgid "C++ Example" +#: src/methods-and-traits/methods.md:75 +msgid "" +"Note that references have not been covered yet. References in method " +"receivers are a particularly \"natural\" form of reference, so there is no " +"need to go into a great level of detail." msgstr "" -#: src/memory-management/scope-based.md:20 +#: src/methods-and-traits/traits.md:3 msgid "" -"The `std::unique_ptr` object is allocated on the stack, and points to memory " -"allocated on the heap." +"Rust lets you abstract over types with traits. They're similar to interfaces:" msgstr "" -#: src/memory-management/scope-based.md:22 -msgid "At the end of `say_hello`, the `std::unique_ptr` destructor will run." +#: src/methods-and-traits/traits.md:7 src/methods-and-traits/trait-objects.md:7 +msgid "// No name needed, cats won't respond anyway.\n" msgstr "" -#: src/memory-management/scope-based.md:23 -msgid "The destructor frees the `Person` object it points to." +#: src/methods-and-traits/traits.md:13 +msgid "\"Oh you're a cutie! What's your name? {}\"" msgstr "" -#: src/memory-management/scope-based.md:25 -msgid "" -"Special move constructors are used when passing ownership to a function:" -msgstr "" +#: src/methods-and-traits/traits.md:18 +#: src/methods-and-traits/trait-objects.md:14 +#, fuzzy +msgid "\"Woof, my name is {}!\"" +msgstr "\"Hej, mit navn er {}\"" -#: src/memory-management/garbage-collection.md:1 -msgid "Automatic Memory Management" +#: src/methods-and-traits/traits.md:22 +#: src/methods-and-traits/trait-objects.md:18 +msgid "\"Miau!\"" msgstr "" -#: src/memory-management/garbage-collection.md:3 +#: src/methods-and-traits/traits.md:27 +#: src/methods-and-traits/trait-objects.md:24 +msgid "\"Fido\"" +msgstr "\"Fido\"" + +#: src/methods-and-traits/traits.md:37 msgid "" -"An alternative to manual and scope-based memory management is automatic " -"memory management:" +"A trait defines a number of methods that types must have in order to " +"implement the trait." msgstr "" -#: src/memory-management/garbage-collection.md:6 -msgid "The programmer never allocates or deallocates memory explicitly." +#: src/methods-and-traits/traits.md:40 +msgid "Traits are implemented in an `impl for { .. }` block." msgstr "" -#: src/memory-management/garbage-collection.md:7 +#: src/methods-and-traits/traits.md:42 msgid "" -"A garbage collector finds unused memory and deallocates it for the " -"programmer." +"Traits may specify pre-implemented (provided) methods and methods that users " +"are required to implement themselves. Provided methods can rely on required " +"methods. In this case, `greet` is provided, and relies on `talk`." msgstr "" -#: src/memory-management/garbage-collection.md:9 -msgid "Java Example" +#: src/methods-and-traits/deriving.md:3 +msgid "" +"Supported traits can be automatically implemented for your custom types, as " +"follows:" msgstr "" -#: src/memory-management/garbage-collection.md:11 -msgid "The `person` object is not deallocated after `sayHello` returns:" +#: src/methods-and-traits/deriving.md:15 +msgid "// Default trait adds `default` constructor.\n" msgstr "" -#: src/memory-management/rust.md:1 -msgid "Memory Management in Rust" +#: src/methods-and-traits/deriving.md:16 +msgid "// Clone trait adds `clone` method.\n" msgstr "" -#: src/memory-management/rust.md:3 -msgid "Memory management in Rust is a mix:" +#: src/methods-and-traits/deriving.md:17 +msgid "\"EldurScrollz\"" msgstr "" -#: src/memory-management/rust.md:5 -msgid "Safe and correct like Java, but without a garbage collector." +#: src/methods-and-traits/deriving.md:18 +msgid "// Debug trait adds support for printing with `{:?}`.\n" msgstr "" -#: src/memory-management/rust.md:6 -msgid "Scope-based like C++, but the compiler enforces full adherence." +#: src/methods-and-traits/deriving.md:19 +#, fuzzy +msgid "\"{:?} vs. {:?}\"" +msgstr "\"{:?} + {:?} = {:?}\"" + +#: src/methods-and-traits/deriving.md:26 +msgid "" +"Derivation is implemented with macros, and many crates provide useful derive " +"macros to add useful functionality. For example, `serde` can derive " +"serialization support for a struct using `#[derive(Serialize)]`." msgstr "" -#: src/memory-management/rust.md:7 +#: src/methods-and-traits/trait-objects.md:3 msgid "" -"A Rust user can choose the right abstraction for the situation, some even " -"have no cost at runtime like C." +"Trait objects allow for values of different types, for instance in a " +"collection:" msgstr "" -#: src/memory-management/rust.md:9 -msgid "Rust achieves this by modeling _ownership_ explicitly." +#: src/methods-and-traits/trait-objects.md:27 +#, fuzzy +msgid "\"Hello, who are you? {}\"" +msgstr "\"Hej, mit navn er {}\"" + +#: src/methods-and-traits/trait-objects.md:32 +msgid "Memory layout after allocating `pets`:" msgstr "" -#: src/memory-management/rust.md:13 +#: src/methods-and-traits/trait-objects.md:34 +#, fuzzy msgid "" -"If asked how at this point, you can mention that in Rust this is usually " -"handled by RAII wrapper types such as [Box](https://doc.rust-lang.org/std/" -"boxed/struct.Box.html), [Vec](https://doc.rust-lang.org/std/vec/struct.Vec." -"html), [Rc](https://doc.rust-lang.org/std/rc/struct.Rc.html), or [Arc]" -"(https://doc.rust-lang.org/std/sync/struct.Arc.html). These encapsulate " -"ownership and memory allocation via various means, and prevent the potential " -"errors in C." +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": pets : : +----+----+----+----" +"+ :\n" +": +-----------+-------+ : : +-----+-----+ .->| F | i | d | o " +"| :\n" +": | ptr | o---+---+-----+-->| o o | o o | | +----+----+----+----" +"+ :\n" +": | len | 2 | : : +-|-|-+-|-|-+ " +"`---------. :\n" +": | capacity | 2 | : : | | | | data " +"| :\n" +": +-----------+-------+ : : | | | | +-------+--|-------" +"+ :\n" +": : : | | | '-->| name | o, 4, 4 " +"| :\n" +": : : | | | | age | 5 " +"| :\n" +"`- - - - - - - - - - - - - -' : | | | +-------+----------" +"+ :\n" +" : | | " +"| :\n" +" : | | | " +"vtable :\n" +" : | | | +----------------------" +"+ :\n" +" : | | '---->| \"::talk\" " +"| :\n" +" : | | +----------------------" +"+ :\n" +" : | " +"| :\n" +" : | | " +"data :\n" +" : | | +-------+-------" +"+ :\n" +" : | '-->| lives | 9 " +"| :\n" +" : | +-------+-------" +"+ :\n" +" : " +"| :\n" +" : | " +"vtable :\n" +" : | +----------------------" +"+ :\n" +" : '---->| \"::talk\" " +"| :\n" +" : +----------------------" +"+ :\n" +" : :\n" +" '- - - - - - - - - - - - - - - - - - - - - " +"- -'\n" +"```" msgstr "" +"```bob\n" +" Stak Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": " +"pets : : :\n" +": +-----------+-------+ : : +-----+-----" +"+ :\n" +": | ptr | o---+---+-----+-->| o o | o o " +"| :\n" +": | len | 2 | : : +-|-|-+-|-|-" +"+ :\n" +": | capacity | 2 | : : | | | | +---------------" +"+ :\n" +": +-----------+-------+ : : | | | '-->| name: \"Fido\" " +"| :\n" +": : : | | | +---------------" +"+ :\n" +"`- - - - - - - - - - - - - -' : | | " +"| :\n" +" : | | | +----------------------" +"+ :\n" +" : | | '---->| \"::name\" " +"| :\n" +" : | | +----------------------" +"+ :\n" +" : | " +"| :\n" +" : | | +-" +"+ :\n" +" : | '-->|" +"\\| :\n" +" : | +-" +"+ :\n" +" : " +"| :\n" +" : | +----------------------" +"+ :\n" +" : '---->| \"::name\" " +"| :\n" +" : +----------------------" +"+ :\n" +" : :\n" +" '- - - - - - - - - - - - - - - - - - - - - " +"- -'\n" +"\n" +"```" -#: src/memory-management/rust.md:15 +#: src/methods-and-traits/trait-objects.md:69 msgid "" -"You may be asked about destructors here, the [Drop](https://doc.rust-lang." -"org/std/ops/trait.Drop.html) trait is the Rust equivalent." +"Types that implement a given trait may be of different sizes. This makes it " +"impossible to have things like `Vec` in the example above." msgstr "" -#: src/ownership.md:3 +#: src/methods-and-traits/trait-objects.md:71 msgid "" -"All variable bindings have a _scope_ where they are valid and it is an error " -"to use a variable outside its scope:" +"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " +"implements `Pet`." msgstr "" -#: src/ownership.md:19 +#: src/methods-and-traits/trait-objects.md:73 msgid "" -"At the end of the scope, the variable is _dropped_ and the data is freed." +"In the example, `pets` is allocated on the stack and the vector data is on " +"the heap. The two vector elements are _fat pointers_:" msgstr "" -#: src/ownership.md:20 -msgid "A destructor can run here to free up resources." +#: src/methods-and-traits/trait-objects.md:75 +msgid "" +"A fat pointer is a double-width pointer. It has two components: a pointer to " +"the actual object and a pointer to the [virtual method table](https://en." +"wikipedia.org/wiki/Virtual_method_table) (vtable) for the `Pet` " +"implementation of that particular object." msgstr "" -#: src/ownership.md:21 -msgid "We say that the variable _owns_ the value." +#: src/methods-and-traits/trait-objects.md:78 +msgid "" +"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " +"has a `lives` field." msgstr "" -#: src/ownership/move-semantics.md:3 -msgid "An assignment will transfer _ownership_ between variables:" +#: src/methods-and-traits/trait-objects.md:80 +msgid "Compare these outputs in the above example:" msgstr "" -#: src/ownership/move-semantics.md:7 -msgid "\"Hello!\"" -msgstr "" +#: src/methods-and-traits/trait-objects.md:82 +#: src/methods-and-traits/trait-objects.md:83 src/std-traits/closures.md:55 +msgid "\"{} {}\"" +msgstr "\"{} {}\"" -#: src/ownership/move-semantics.md:10 -msgid "// println!(\"s1: {s1}\");\n" -msgstr "" +#: src/methods-and-traits/trait-objects.md:84 +#: src/methods-and-traits/trait-objects.md:85 +#: src/methods-and-traits/solution.md:123 src/std-traits/exercise.md:25 +#: src/std-traits/solution.md:31 src/modules/solution.md:70 +#: src/android/build-rules/library.md:43 +#: src/android/interoperability/cpp/rust-bridge.md:17 +#: src/async/pitfalls/cancellation.md:59 +msgid "\"{}\"" +msgstr "\"{}\"" -#: src/ownership/move-semantics.md:14 -msgid "The assignment of `s1` to `s2` transfers ownership." +#: src/methods-and-traits/exercise.md:3 +msgid "" +"Let us design a classical GUI library using our new knowledge of traits and " +"trait objects. We'll only implement the drawing of it (as text) for " +"simplicity." msgstr "" -#: src/ownership/move-semantics.md:15 -msgid "When `s1` goes out of scope, nothing happens: it does not own anything." +#: src/methods-and-traits/exercise.md:6 +msgid "We will have a number of widgets in our library:" msgstr "" -#: src/ownership/move-semantics.md:16 -msgid "When `s2` goes out of scope, the string data is freed." +#: src/methods-and-traits/exercise.md:8 +msgid "`Window`: has a `title` and contains other widgets." msgstr "" -#: src/ownership/move-semantics.md:17 -msgid "There is always _exactly_ one variable binding which owns a value." +#: src/methods-and-traits/exercise.md:9 +msgid "" +"`Button`: has a `label`. In reality, it would also take a callback function " +"to allow the program to do something when the button is clicked but we won't " +"include that since we're only drawing the GUI." msgstr "" -#: src/ownership/move-semantics.md:21 -msgid "" -"Mention that this is the opposite of the defaults in C++, which copies by " -"value unless you use `std::move` (and the move constructor is defined!)." +#: src/methods-and-traits/exercise.md:12 +msgid "`Label`: has a `label`." msgstr "" -#: src/ownership/move-semantics.md:23 -msgid "" -"It is only the ownership that moves. Whether any machine code is generated " -"to manipulate the data itself is a matter of optimization, and such copies " -"are aggressively optimized away." +#: src/methods-and-traits/exercise.md:14 +msgid "The widgets will implement a `Widget` trait, see below." msgstr "" -#: src/ownership/move-semantics.md:25 +#: src/methods-and-traits/exercise.md:16 msgid "" -"Simple values (such as integers) can be marked `Copy` (see later slides)." +"Copy the code below to , fill in the missing " +"`draw_into` methods so that you implement the `Widget` trait:" msgstr "" -#: src/ownership/move-semantics.md:27 -msgid "In Rust, clones are explicit (by using `clone`)." +#: src/methods-and-traits/exercise.md:24 src/methods-and-traits/solution.md:5 +#: src/modules/solution.md:22 +msgid "/// Natural width of `self`.\n" msgstr "" -#: src/ownership/moved-strings-rust.md:11 -msgid "The heap data from `s1` is reused for `s2`." +#: src/methods-and-traits/exercise.md:27 src/methods-and-traits/solution.md:8 +#: src/modules/solution.md:25 +msgid "/// Draw the widget into a buffer.\n" msgstr "" -#: src/ownership/moved-strings-rust.md:12 -msgid "When `s1` goes out of scope, nothing happens (it has been moved from)." +#: src/methods-and-traits/exercise.md:30 src/methods-and-traits/solution.md:11 +#: src/modules/solution.md:28 +msgid "/// Draw the widget on standard output.\n" msgstr "" -#: src/ownership/moved-strings-rust.md:14 -msgid "Before move to `s2`:" +#: src/methods-and-traits/exercise.md:34 src/methods-and-traits/solution.md:15 +#: src/modules/solution.md:32 +msgid "\"{buffer}\"" +msgstr "\"{buffer}\"" + +#: src/methods-and-traits/exercise.md:86 +msgid "// TODO: Implement `Widget` for `Label`.\n" msgstr "" -#: src/ownership/moved-strings-rust.md:31 -msgid "After move to `s2`:" +#: src/methods-and-traits/exercise.md:88 +msgid "// TODO: Implement `Widget` for `Button`.\n" msgstr "" -#: src/ownership/moved-strings-rust.md:33 -msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" -": : : :\n" -": s1 \"(inaccessible)\" : : :\n" -": +-----------+-------+ : : +----+----+----+----+ :\n" -": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" -": | len | 4 | : | : +----+----+----+----+ :\n" -": | capacity | 4 | : | : :\n" -": +-----------+-------+ : | : :\n" -": : | `- - - - - - - - - - - - - -'\n" -": s2 : |\n" -": +-----------+-------+ : |\n" -": | ptr | o---+---+--'\n" -": | len | 4 | :\n" -": | capacity | 4 | :\n" -": +-----------+-------+ :\n" -": :\n" -"`- - - - - - - - - - - - - -'\n" -"```" +#: src/methods-and-traits/exercise.md:90 +msgid "// TODO: Implement `Widget` for `Window`.\n" msgstr "" -"```bob\n" -" Stak Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" -": : : :\n" -": s1 \"(utilgængelig)\" : : :\n" -": +-----------+-------+ : : +----+----+----+----+ :\n" -": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" -": | len | 4 | : | : +----+----+----+----+ :\n" -": | capacity | 4 | : | : :\n" -": +-----------+-------+ : | : :\n" -": : | `- - - - - - - - - - - - - -'\n" -": s2 : |\n" -": +-----------+-------+ : |\n" -": | ptr | o---+---+--'\n" -": | len | 4 | :\n" -": | capacity | 4 | :\n" -": +-----------+-------+ :\n" -": :\n" -"`- - - - - - - - - - - - - -'\n" -"```" -#: src/ownership/double-free-modern-cpp.md:1 -msgid "Defensive Copies in Modern C++" -msgstr "Defensive kopier i moderne C++" +#: src/methods-and-traits/exercise.md:94 src/methods-and-traits/solution.md:128 +#: src/modules/solution.md:178 +msgid "\"Rust GUI Demo 1.23\"" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:3 -msgid "Modern C++ solves this differently:" +#: src/methods-and-traits/exercise.md:95 src/methods-and-traits/solution.md:129 +#: src/modules/solution.md:180 +msgid "\"This is a small text GUI demo.\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:6 -msgid "\"Cpp\"" -msgstr "\"Cpp\"" +#: src/methods-and-traits/exercise.md:96 src/methods-and-traits/solution.md:130 +#: src/modules/solution.md:182 +msgid "\"Click me!\"" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:7 -msgid "// Duplicate the data in s1.\n" +#: src/methods-and-traits/exercise.md:101 +msgid "The output of the above program can be something simple like this:" msgstr "" -#: src/ownership/double-free-modern-cpp.md:10 +#: src/methods-and-traits/exercise.md:113 msgid "" -"The heap data from `s1` is duplicated and `s2` gets its own independent copy." +"If you want to draw aligned text, you can use the [fill/alignment](https://" +"doc.rust-lang.org/std/fmt/index.html#fillalignment) formatting operators. In " +"particular, notice how you can pad with different characters (here a `'/'`) " +"and how you can control alignment:" msgstr "" -#: src/ownership/double-free-modern-cpp.md:11 -msgid "When `s1` and `s2` go out of scope, they each free their own memory." +#: src/methods-and-traits/exercise.md:121 +msgid "\"left aligned: |{:/width$}|\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:57 +#: src/methods-and-traits/exercise.md:127 msgid "" -"C++ has made a slightly different choice than Rust. Because `=` copies data, " -"the string data has to be cloned. Otherwise we would get a double-free when " -"either string goes out of scope." +"Using such alignment tricks, you can for example produce output like this:" msgstr "" -#: src/ownership/double-free-modern-cpp.md:61 -msgid "" -"C++ also has [`std::move`](https://en.cppreference.com/w/cpp/utility/move), " -"which is used to indicate when a value may be moved from. If the example had " -"been `s2 = std::move(s1)`, no heap allocation would take place. After the " -"move, `s1` would be in a valid but unspecified state. Unlike Rust, the " -"programmer is allowed to keep using `s1`." +#: src/methods-and-traits/solution.md:70 +msgid "// Add 4 paddings for borders\n" msgstr "" -#: src/ownership/double-free-modern-cpp.md:66 +#: src/methods-and-traits/solution.md:82 src/modules/solution.md:159 msgid "" -"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " -"which is being copied or moved." +"// TODO: after learning about error handling, you can change\n" +" // draw_into to return Result<(), std::fmt::Error>. Then use\n" +" // the ?-operator here instead of .unwrap().\n" msgstr "" -#: src/ownership/moves-function-calls.md:3 -msgid "" -"When you pass a value to a function, the value is assigned to the function " -"parameter. This transfers ownership:" -msgstr "" +#: src/methods-and-traits/solution.md:85 src/methods-and-traits/solution.md:91 +#: src/modules/solution.md:162 src/modules/solution.md:168 +msgid "\"+-{:- Point {}`? Isn't that " +"redundant?" msgstr "" -#: src/ownership/borrowing.md:3 +#: src/generics/generic-data.md:32 msgid "" -"Instead of transferring ownership when calling a function, you can let a " -"function _borrow_ the value:" -msgstr "" - -#: src/ownership/borrowing.md:23 -msgid "The `add` function _borrows_ two points and returns a new point." +"This is because it is a generic implementation section for generic type. " +"They are independently generic." msgstr "" -#: src/ownership/borrowing.md:24 -msgid "The caller retains ownership of the inputs." +#: src/generics/generic-data.md:33 +msgid "It means these methods are defined for any `T`." msgstr "" -#: src/ownership/borrowing.md:28 -msgid "Notes on stack returns:" +#: src/generics/generic-data.md:34 +msgid "It is possible to write `impl Point { .. }`." msgstr "" -#: src/ownership/borrowing.md:29 +#: src/generics/generic-data.md:35 msgid "" -"Demonstrate that the return from `add` is cheap because the compiler can " -"eliminate the copy operation. Change the above code to print stack addresses " -"and run it on the [Playground](https://play.rust-lang.org/) or look at the " -"assembly in [Godbolt](https://rust.godbolt.org/). In the \"DEBUG\" " -"optimization level, the addresses should change, while they stay the same " -"when changing to the \"RELEASE\" setting:" -msgstr "" - -#: src/ownership/borrowing.md:50 -msgid "The Rust compiler can do return value optimization (RVO)." +"`Point` is still generic and you can use `Point`, but methods in this " +"block will only be available for `Point`." msgstr "" -#: src/ownership/borrowing.md:51 +#: src/generics/generic-data.md:37 msgid "" -"In C++, copy elision has to be defined in the language specification because " -"constructors can have side effects. In Rust, this is not an issue at all. If " -"RVO did not happen, Rust will always perform a simple and efficient `memcpy` " -"copy." +"Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`. Update the " +"code to allow points that have elements of different types, by using two " +"type variables, e.g., `T` and `U`." msgstr "" -#: src/ownership/shared-unique-borrows.md:3 -msgid "Rust puts constraints on the ways you can borrow values:" +#: src/generics/trait-bounds.md:3 +msgid "" +"When working with generics, you often want to require the types to implement " +"some trait, so that you can call this trait's methods." msgstr "" -#: src/ownership/shared-unique-borrows.md:5 -msgid "You can have one or more `&T` values at any given time, _or_" +#: src/generics/trait-bounds.md:6 +msgid "You can do this with `T: Trait` or `impl Trait`:" msgstr "" -#: src/ownership/shared-unique-borrows.md:6 -msgid "You can have exactly one `&mut T` value." -msgstr "" +#: src/generics/trait-bounds.md:12 +msgid "// struct NotClonable;\n" +msgstr "// struct NotClonable;\n" -#: src/ownership/shared-unique-borrows.md:26 -msgid "" -"The above code does not compile because `a` is borrowed as mutable (through " -"`c`) and as immutable (through `b`) at the same time." -msgstr "" +#: src/generics/trait-bounds.md:18 +msgid "\"{pair:?}\"" +msgstr "\"{pair:?}\"" -#: src/ownership/shared-unique-borrows.md:27 -msgid "" -"Move the `println!` statement for `b` before the scope that introduces `c` " -"to make the code compile." +#: src/generics/trait-bounds.md:25 +msgid "Try making a `NonClonable` and passing it to `duplicate`." msgstr "" -#: src/ownership/shared-unique-borrows.md:28 -msgid "" -"After that change, the compiler realizes that `b` is only ever used before " -"the new mutable borrow of `a` through `c`. This is a feature of the borrow " -"checker called \"non-lexical lifetimes\"." +#: src/generics/trait-bounds.md:27 +msgid "When multiple traits are necessary, use `+` to join them." msgstr "" -#: src/ownership/lifetimes.md:3 -msgid "A borrowed value has a _lifetime_:" +#: src/generics/trait-bounds.md:29 +msgid "Show a `where` clause, students will encounter it when reading code." msgstr "" -#: src/ownership/lifetimes.md:5 -msgid "The lifetime can be implicit: `add(p1: &Point, p2: &Point) -> Point`." +#: src/generics/trait-bounds.md:40 +msgid "It declutters the function signature if you have many parameters." msgstr "" -#: src/ownership/lifetimes.md:6 -msgid "Lifetimes can also be explicit: `&'a Point`, `&'document str`." +#: src/generics/trait-bounds.md:41 +msgid "It has additional features making it more powerful." msgstr "" -#: src/ownership/lifetimes.md:7 src/ownership/lifetimes-function-calls.md:24 +#: src/generics/trait-bounds.md:42 msgid "" -"Read `&'a Point` as \"a borrowed `Point` which is valid for at least the " -"lifetime `a`\"." +"If someone asks, the extra feature is that the type on the left of \":\" can " +"be arbitrary, like `Option`." msgstr "" -#: src/ownership/lifetimes.md:9 +#: src/generics/trait-bounds.md:44 msgid "" -"Lifetimes are always inferred by the compiler: you cannot assign a lifetime " -"yourself." +"Note that Rust does not (yet) support specialization. For example, given the " +"original `duplicate`, it is invalid to add a specialized `duplicate(a: u32)`." msgstr "" -#: src/ownership/lifetimes.md:11 -msgid "" -"Lifetime annotations create constraints; the compiler verifies that there is " -"a valid solution." -msgstr "" +#: src/generics/impl-trait.md:1 +msgid "`impl Trait`" +msgstr "`impl Trait`" -#: src/ownership/lifetimes.md:13 +#: src/generics/impl-trait.md:3 msgid "" -"Lifetimes for function arguments and return values must be fully specified, " -"but Rust allows lifetimes to be elided in most cases with [a few simple " -"rules](https://doc.rust-lang.org/nomicon/lifetime-elision.html)." +"Similar to trait bounds, an `impl Trait` syntax can be used in function " +"arguments and return values:" msgstr "" -#: src/ownership/lifetimes-function-calls.md:3 +#: src/generics/impl-trait.md:7 msgid "" -"In addition to borrowing its arguments, a function can return a borrowed " -"value:" +"// Syntactic sugar for:\n" +"// fn add_42_millions>(x: T) -> i32 {\n" msgstr "" -#: src/ownership/lifetimes-function-calls.md:22 -msgid "`'a` is a generic parameter, it is inferred by the compiler." -msgstr "" +#: src/generics/impl-trait.md:19 +msgid "\"{many}\"" +msgstr "\"{many}\"" + +#: src/generics/impl-trait.md:21 +msgid "\"{many_more}\"" +msgstr "\"{many_more}\"" -#: src/ownership/lifetimes-function-calls.md:23 -msgid "Lifetimes start with `'` and `'a` is a typical default name." +#: src/generics/impl-trait.md:23 +msgid "\"debuggable: {debuggable:?}\"" msgstr "" -#: src/ownership/lifetimes-function-calls.md:26 +#: src/generics/impl-trait.md:30 msgid "" -"The _at least_ part is important when parameters are in different scopes." +"`impl Trait` allows you to work with types which you cannot name. The " +"meaning of `impl Trait` is a bit different in the different positions." msgstr "" -#: src/ownership/lifetimes-function-calls.md:32 +#: src/generics/impl-trait.md:33 msgid "" -"Move the declaration of `p2` and `p3` into a new scope (`{ ... }`), " -"resulting in the following code:" +"For a parameter, `impl Trait` is like an anonymous generic parameter with a " +"trait bound." msgstr "" -#: src/ownership/lifetimes-function-calls.md:52 -msgid "Note how this does not compile since `p3` outlives `p2`." -msgstr "" - -#: src/ownership/lifetimes-function-calls.md:54 +#: src/generics/impl-trait.md:35 msgid "" -"Reset the workspace and change the function signature to `fn left_most<'a, " -"'b>(p1: &'a Point, p2: &'a Point) -> &'b Point`. This will not compile " -"because the relationship between the lifetimes `'a` and `'b` is unclear." -msgstr "" - -#: src/ownership/lifetimes-function-calls.md:55 -msgid "Another way to explain it:" +"For a return type, it means that the return type is some concrete type that " +"implements the trait, without naming the type. This can be useful when you " +"don't want to expose the concrete type in a public API." msgstr "" -#: src/ownership/lifetimes-function-calls.md:56 +#: src/generics/impl-trait.md:39 msgid "" -"Two references to two values are borrowed by a function and the function " -"returns another reference." +"Inference is hard in return position. A function returning `impl Foo` picks " +"the concrete type it returns, without writing it out in the source. A " +"function returning a generic type like `collect() -> B` can return any " +"type satisfying `B`, and the caller may need to choose one, such as with " +"`let x: Vec<_> = foo.collect()` or with the turbofish, `foo.collect::" +">()`." msgstr "" -#: src/ownership/lifetimes-function-calls.md:58 +#: src/generics/impl-trait.md:45 msgid "" -"It must have come from one of those two inputs (or from a global variable)." +"What is the type of `debuggable`? Try `let debuggable: () = ..` to see what " +"the error message shows." msgstr "" -#: src/ownership/lifetimes-function-calls.md:59 +#: src/generics/exercise.md:3 msgid "" -"Which one is it? The compiler needs to know, so at the call site the " -"returned reference is not used for longer than a variable from where the " -"reference came from." +"In this short exercise, you will implement a generic `min` function that " +"determines the minimum of two values, using a `LessThan` trait." msgstr "" -#: src/ownership/lifetimes-data-structures.md:3 -msgid "" -"If a data type stores borrowed data, it must be annotated with a lifetime:" +#: src/generics/exercise.md:8 src/generics/solution.md:5 +msgid "/// Return true if self is less than other.\n" msgstr "" -#: src/ownership/lifetimes-data-structures.md:10 -msgid "\"Bye {text}!\"" -msgstr "\"Farvel {text}!\"" - -#: src/ownership/lifetimes-data-structures.md:14 -msgid "\"The quick brown fox jumps over the lazy dog.\"" +#: src/generics/exercise.md:29 +msgid "// TODO: implement the `min` function used in `main`.\n" msgstr "" -#: src/ownership/lifetimes-data-structures.md:17 -msgid "// erase(text);\n" -msgstr "// erase(text);\n" - -#: src/ownership/lifetimes-data-structures.md:18 -msgid "\"{fox:?}\"" -msgstr "\"{fox:?}\"" +#: src/generics/exercise.md:34 src/generics/solution.md:37 +msgid "\"Shapiro\"" +msgstr "" -#: src/ownership/lifetimes-data-structures.md:19 -msgid "\"{dog:?}\"" -msgstr "\"{dog:?}\"" +#: src/generics/exercise.md:38 src/generics/exercise.md:42 +#: src/generics/solution.md:41 src/generics/solution.md:45 +msgid "\"Baumann\"" +msgstr "" -#: src/ownership/lifetimes-data-structures.md:25 -msgid "" -"In the above example, the annotation on `Highlight` enforces that the data " -"underlying the contained `&str` lives at least as long as any instance of " -"`Highlight` that uses that data." +#: src/welcome-day-2-afternoon.md:4 +msgid "[Standard Library Types](./std-types.md) (1 hour and 10 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:26 -msgid "" -"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " -"the borrow checker throws an error." +#: src/welcome-day-2-afternoon.md:5 +msgid "[Standard Library Traits](./std-traits.md) (1 hour and 40 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:27 -msgid "" -"Types with borrowed data force users to hold on to the original data. This " -"can be useful for creating lightweight views, but it generally makes them " -"somewhat harder to use." +#: src/std-types.md:4 +msgid "[Standard Library](./std-types/std.md) (3 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:28 -msgid "When possible, make data structures own their data directly." +#: src/std-types.md:5 +msgid "[Language Docs](./std-types/docs.md) (5 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:29 -msgid "" -"Some structs with multiple references inside can have more than one lifetime " -"annotation. This can be necessary if there is a need to describe lifetime " -"relationships between the references themselves, in addition to the lifetime " -"of the struct itself. Those are very advanced use cases." +#: src/std-types.md:6 +msgid "[Option](./std-types/option.md) (10 minutes)" msgstr "" -#: src/structs.md:3 -msgid "Like C and C++, Rust has support for custom structs:" +#: src/std-types.md:7 +msgid "[Result](./std-types/result.md) (10 minutes)" msgstr "" -#: src/structs.md:13 src/structs/field-shorthand.md:20 src/methods.md:21 -#: src/android/interoperability/with-c/bindgen.md:87 -msgid "\"Peter\"" -msgstr "\"Peter\"" +#: src/std-types.md:8 +msgid "[String](./std-types/string.md) (10 minutes)" +msgstr "" -#: src/structs.md:16 src/structs.md:19 src/structs.md:25 -msgid "\"{} is {} years old\"" +#: src/std-types.md:9 +msgid "[Vec](./std-types/vec.md) (10 minutes)" msgstr "" -#: src/structs.md:22 -msgid "\"Jackie\"" -msgstr "\"Jackie\"" +#: src/std-types.md:10 +msgid "[HashMap](./std-types/hashmap.md) (10 minutes)" +msgstr "" -#: src/structs.md:33 -msgid "Structs work like in C or C++." +#: src/std-types.md:11 +msgid "[Exercise: Counter](./std-types/exercise.md) (10 minutes)" msgstr "" -#: src/structs.md:34 -msgid "Like in C++, and unlike in C, no typedef is needed to define a type." +#: src/std-types.md:13 src/memory-management.md:13 +#: src/slices-and-lifetimes.md:11 +msgid "This segment should take about 1 hour and 10 minutes" msgstr "" -#: src/structs.md:35 -msgid "Unlike in C++, there is no inheritance between structs." +#: src/std-types.md:18 +msgid "" +"For each of the slides in this section, spend some time reviewing the " +"documentation pages, highlighting some of the more common methods." msgstr "" -#: src/structs.md:36 +#: src/std-types/std.md:3 msgid "" -"Methods are defined in an `impl` block, which we will see in following " -"slides." +"Rust comes with a standard library which helps establish a set of common " +"types used by Rust libraries and programs. This way, two libraries can work " +"together smoothly because they both use the same `String` type." msgstr "" -#: src/structs.md:37 +#: src/std-types/std.md:7 msgid "" -"This may be a good time to let people know there are different types of " -"structs. " +"In fact, Rust contains several layers of the Standard Library: `core`, " +"`alloc` and `std`." msgstr "" -#: src/structs.md:38 +#: src/std-types/std.md:8 msgid "" -"Zero-sized structs `e.g., struct Foo;` might be used when implementing a " -"trait on some type but don’t have any data that you want to store in the " -"value itself. " +"`core` includes the most basic types and functions that don't depend on " +"`libc`, allocator or even the presence of an operating system." msgstr "" -#: src/structs.md:39 +#: src/std-types/std.md:10 msgid "" -"The next slide will introduce Tuple structs, used when the field names are " -"not important." +"`alloc` includes types which require a global heap allocator, such as `Vec`, " +"`Box` and `Arc`." msgstr "" -#: src/structs.md:40 +#: src/std-types/std.md:11 msgid "" -"The syntax `..peter` allows us to copy the majority of the fields from the " -"old struct without having to explicitly type it all out. It must always be " -"the last element." +"Embedded Rust applications often only use `core`, and sometimes `alloc`." msgstr "" -#: src/structs/tuple-structs.md:3 -msgid "If the field names are unimportant, you can use a tuple struct:" +#: src/std-types/docs.md:3 +msgid "" +"Rust comes with extensive documentation of the language and the standard " +"library." msgstr "" -#: src/structs/tuple-structs.md:10 -msgid "\"({}, {})\"" -msgstr "\"({}, {})\"" +#: src/std-types/docs.md:5 +#, fuzzy +msgid "For example:" +msgstr "C-eksempel" -#: src/structs/tuple-structs.md:14 -msgid "This is often used for single-field wrappers (called newtypes):" +#: src/std-types/docs.md:6 +msgid "" +"All of the details about [loops](https://doc.rust-lang.org/stable/reference/" +"expressions/loop-expr.html)." msgstr "" -#: src/structs/tuple-structs.md:21 -msgid "\"Ask a rocket scientist at NASA\"" +#: src/std-types/docs.md:7 +msgid "" +"Primitive types like [`u8`](https://doc.rust-lang.org/stable/std/primitive." +"u8.html)." msgstr "" -#: src/structs/tuple-structs.md:25 -#: src/bare-metal/microcontrollers/type-state.md:14 -#: src/async/pitfalls/cancellation.md:99 -msgid "// ...\n" -msgstr "// ...\n" - -#: src/structs/tuple-structs.md:37 +#: src/std-types/docs.md:8 msgid "" -"Newtypes are a great way to encode additional information about the value in " -"a primitive type, for example:" +"Standard-library items like [`Option`](https://doc.rust-lang.org/stable/std/" +"option/enum.Option.html) or [`BinaryHeap`](https://doc.rust-lang.org/stable/" +"std/collections/struct.BinaryHeap.html)." msgstr "" -#: src/structs/tuple-structs.md:38 -msgid "The number is measured in some units: `Newtons` in the example above." +#: src/std-types/docs.md:10 +msgid "In fact, you can document your own code:" msgstr "" -#: src/structs/tuple-structs.md:39 +#: src/std-types/docs.md:13 msgid "" -"The value passed some validation when it was created, so you no longer have " -"to validate it again at every use: 'PhoneNumber(String)`or`OddNumber(u32)\\`." +"/// Determine whether the first argument is divisible by the second " +"argument.\n" +"///\n" +"/// If the second argument is zero, the result is false.\n" msgstr "" -#: src/structs/tuple-structs.md:40 +#: src/std-types/docs.md:24 msgid "" -"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " -"single field in the newtype." +"The contents are treated as Markdown. All published Rust library crates are " +"automatically documented at [`docs.rs`](https://docs.rs) using the [rustdoc]" +"(https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is " +"idiomatic to document all public items in an API using this pattern." msgstr "" -#: src/structs/tuple-structs.md:41 +#: src/std-types/docs.md:29 msgid "" -"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " -"for instance using booleans as integers." +"To document an item from inside the item (such as inside a module), use `//!" +"` or `/*! .. */`, called \"inner doc comments\":" msgstr "" -#: src/structs/tuple-structs.md:42 -msgid "Operator overloading is discussed on Day 3 (generics)." +#: src/std-types/docs.md:33 +msgid "" +"//! This module contains functionality relating to divisibility of " +"integers.\n" msgstr "" -#: src/structs/tuple-structs.md:43 +#: src/std-types/docs.md:39 msgid "" -"The example is a subtle reference to the [Mars Climate Orbiter](https://en." -"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." +"Show students the generated docs for the `rand` crate at [`docs.rs/rand`]" +"(https://docs.rs/rand)." msgstr "" -#: src/structs/field-shorthand.md:3 +#: src/std-types/option.md:3 msgid "" -"If you already have variables with the right names, then you can create the " -"struct using a shorthand:" +"We have already seen some use of `Option`. It stores either a value of " +"type `T` or nothing. For example, [`String::find`](https://doc.rust-lang.org/" +"stable/std/string/struct.String.html#method.find) returns an `Option`." msgstr "" -#: src/structs/field-shorthand.md:21 -msgid "\"{peter:?}\"" -msgstr "\"{peter:?}\"" +#: src/std-types/option.md:10 +msgid "\"Löwe 老虎 Léopard Gepardi\"" +msgstr "" -#: src/structs/field-shorthand.md:27 -msgid "" -"The `new` function could be written using `Self` as a type, as it is " -"interchangeable with the struct type name" +#: src/std-types/option.md:11 +msgid "'é'" msgstr "" -#: src/structs/field-shorthand.md:41 -msgid "" -"Implement the `Default` trait for the struct. Define some fields and use the " -"default values for the other fields." +#: src/std-types/option.md:12 src/std-types/option.md:15 +msgid "\"find returned {position:?}\"" msgstr "" -#: src/structs/field-shorthand.md:52 -msgid "\"Bot\"" -msgstr "\"Bot\"" +#: src/std-types/option.md:14 +#, fuzzy +msgid "'Z'" +msgstr "'x'" -#: src/structs/field-shorthand.md:62 -msgid "\"Sam\"" -msgstr "\"Sam\"" +#: src/std-types/option.md:16 +msgid "\"Character not found\"" +msgstr "" -#: src/structs/field-shorthand.md:68 -msgid "Methods are defined in the `impl` block." +#: src/std-types/option.md:23 +msgid "`Option` is widely used, not just in the standard library." msgstr "" -#: src/structs/field-shorthand.md:69 +#: src/std-types/option.md:24 msgid "" -"Use struct update syntax to define a new structure using `peter`. Note that " -"the variable `peter` will no longer be accessible afterwards." +"`unwrap` will return the value in an `Option`, or panic. `expect` is similar " +"but takes an error message." msgstr "" -#: src/structs/field-shorthand.md:70 +#: src/std-types/option.md:25 msgid "" -"Use `{:#?}` when printing structs to request the `Debug` representation." +"You can panic on None, but you can't \"accidentally\" forget to check for " +"None." msgstr "" -#: src/methods.md:3 +#: src/std-types/option.md:26 msgid "" -"Rust allows you to associate functions with your new types. You do this with " -"an `impl` block:" +"It's common to `unwrap`/`expect` all over the place when hacking something " +"together, but production code typically handles `None` in a nicer fashion." msgstr "" -#: src/methods.md:15 -msgid "\"Hello, my name is {}\"" -msgstr "\"Hej, mit navn er {}\"" - -#: src/methods.md:31 -msgid "It can be helpful to introduce methods by comparing them to functions." +#: src/std-types/option.md:27 +msgid "" +"The niche optimization means that `Option` often has the same size in " +"memory as `T`." msgstr "" -#: src/methods.md:32 +#: src/std-types/result.md:3 msgid "" -"Methods are called on an instance of a type (such as a struct or enum), the " -"first parameter represents the instance as `self`." +"`Result` is similar to `Option`, but indicates the success or failure of an " +"operation, each with a different type. This is similar to the `Res` defined " +"in the expression exercise, but generic: `Result` where `T` is used in " +"the `Ok` variant and `E` appears in the `Err` variant." msgstr "" -#: src/methods.md:33 -msgid "" -"Developers may choose to use methods to take advantage of method receiver " -"syntax and to help keep them more organized. By using methods we can keep " -"all the implementation code in one predictable place." +#: src/std-types/result.md:13 +msgid "\"diary.txt\"" +msgstr "\"dagbog.txt\"" + +#: src/std-types/result.md:18 +#, fuzzy +msgid "\"Dear diary: {contents} ({bytes} bytes)\"" +msgstr "\"Kære dagbog: {contents}\"" + +#: src/std-types/result.md:20 +msgid "\"Could not read file content\"" msgstr "" -#: src/methods.md:34 -msgid "Point out the use of the keyword `self`, a method receiver." +#: src/std-types/result.md:24 +msgid "\"The diary could not be opened: {err}\"" msgstr "" -#: src/methods.md:35 +#: src/std-types/result.md:33 msgid "" -"Show that it is an abbreviated term for `self: Self` and perhaps show how " -"the struct name could also be used." +"As with `Option`, the successful value sits inside of `Result`, forcing the " +"developer to explicitly extract it. This encourages error checking. In the " +"case where an error should never happen, `unwrap()` or `expect()` can be " +"called, and this is a signal of the developer intent too." msgstr "" -#: src/methods.md:36 +#: src/std-types/result.md:36 msgid "" -"Explain that `Self` is a type alias for the type the `impl` block is in and " -"can be used elsewhere in the block." +"`Result` documentation is a recommended read. Not during the course, but it " +"is worth mentioning. It contains a lot of convenience methods and functions " +"that help functional-style programming." msgstr "" -#: src/methods.md:37 +#: src/std-types/result.md:38 msgid "" -"Note how `self` is used like other structs and dot notation can be used to " -"refer to individual fields." +"`Result` is the standard type to implement error handling as we will see on " +"Day 3." msgstr "" -#: src/methods.md:38 +#: src/std-types/string.md:3 msgid "" -"This might be a good time to demonstrate how the `&self` differs from `self` " -"by modifying the code and trying to run say_hello twice." +"[`String`](https://doc.rust-lang.org/std/string/struct.String.html) is the " +"standard heap-allocated growable UTF-8 string buffer:" msgstr "" -#: src/methods.md:39 -msgid "We describe the distinction between method receivers next." -msgstr "" +#: src/std-types/string.md:8 src/std-traits/read-and-write.md:35 +#: src/memory-management/review.md:23 src/memory-management/review.md:55 +#: src/testing/unit-tests.md:32 src/testing/unit-tests.md:37 +#: src/concurrency/scoped-threads.md:9 src/concurrency/scoped-threads.md:26 +msgid "\"Hello\"" +msgstr "\"Hello\"" + +#: src/std-types/string.md:9 +msgid "\"s1: len = {}, capacity = {}\"" +msgstr "\"s1: len = {}, capacity = {}\"" + +#: src/std-types/string.md:13 +msgid "'!'" +msgstr "'!'" + +#: src/std-types/string.md:14 +msgid "\"s2: len = {}, capacity = {}\"" +msgstr "\"s2: len = {}, capacity = {}\"" + +#: src/std-types/string.md:16 +msgid "\"🇨🇭\"" +msgstr "\"🇨🇭\"" + +#: src/std-types/string.md:17 +msgid "\"s3: len = {}, number of chars = {}\"" +msgstr "\"s3: len = {}, antal tegn = {}\"" -#: src/methods/receiver.md:3 +#: src/std-types/string.md:22 msgid "" -"The `&self` above indicates that the method borrows the object immutably. " -"There are other possible receivers for a method:" +"`String` implements [`Deref`](https://doc.rust-lang.org/std/" +"string/struct.String.html#deref-methods-str), which means that you can call " +"all `str` methods on a `String`." msgstr "" -#: src/methods/receiver.md:6 +#: src/std-types/string.md:31 msgid "" -"`&self`: borrows the object from the caller using a shared and immutable " -"reference. The object can be used again afterwards." +"`String::new` returns a new empty string, use `String::with_capacity` when " +"you know how much data you want to push to the string." msgstr "" -#: src/methods/receiver.md:8 +#: src/std-types/string.md:32 msgid "" -"`&mut self`: borrows the object from the caller using a unique and mutable " -"reference. The object can be used again afterwards." +"`String::len` returns the size of the `String` in bytes (which can be " +"different from its length in characters)." msgstr "" -#: src/methods/receiver.md:10 +#: src/std-types/string.md:33 msgid "" -"`self`: takes ownership of the object and moves it away from the caller. The " -"method becomes the owner of the object. The object will be dropped " -"(deallocated) when the method returns, unless its ownership is explicitly " -"transmitted. Complete ownership does not automatically mean mutability." +"`String::chars` returns an iterator over the actual characters. Note that a " +"`char` can be different from what a human will consider a \"character\" due " +"to [grapheme clusters](https://docs.rs/unicode-segmentation/latest/" +"unicode_segmentation/struct.Graphemes.html)." msgstr "" -#: src/methods/receiver.md:14 -msgid "`mut self`: same as above, but the method can mutate the object. " +#: src/std-types/string.md:34 +msgid "" +"When people refer to strings they could either be talking about `&str` or " +"`String`." msgstr "" -#: src/methods/receiver.md:15 +#: src/std-types/string.md:35 msgid "" -"No receiver: this becomes a static method on the struct. Typically used to " -"create constructors which are called `new` by convention." +"When a type implements `Deref`, the compiler will let you " +"transparently call methods from `T`." msgstr "" -#: src/methods/receiver.md:18 +#: src/std-types/string.md:36 msgid "" -"Beyond variants on `self`, there are also [special wrapper types](https://" -"doc.rust-lang.org/reference/special-types-and-traits.html) allowed to be " -"receiver types, such as `Box`." +"We haven't discussed the `Deref` trait yet, so at this point this mostly " +"explains the structure of the sidebar in the documentation." msgstr "" -#: src/methods/receiver.md:24 +#: src/std-types/string.md:37 msgid "" -"Consider emphasizing \"shared and immutable\" and \"unique and mutable\". " -"These constraints always come together in Rust due to borrow checker rules, " -"and `self` is no exception. It isn't possible to reference a struct from " -"multiple locations and call a mutating (`&mut self`) method on it." +"`String` implements `Deref` which transparently gives it " +"access to `str`'s methods." msgstr "" -#: src/methods/example.md:11 -msgid "// No receiver, a static method\n" +#: src/std-types/string.md:38 +msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1;`." msgstr "" -#: src/methods/example.md:15 -msgid "// Exclusive borrowed read-write access to self\n" +#: src/std-types/string.md:39 +msgid "" +"`String` is implemented as a wrapper around a vector of bytes, many of the " +"operations you see supported on vectors are also supported on `String`, but " +"with some extra guarantees." msgstr "" -#: src/methods/example.md:19 -msgid "// Shared and read-only borrowed access to self\n" +#: src/std-types/string.md:40 +msgid "Compare the different ways to index a `String`:" msgstr "" -#: src/methods/example.md:20 -msgid "\"Recorded {} laps for {}:\"" +#: src/std-types/string.md:41 +msgid "" +"To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, " +"out-of-bounds." msgstr "" -#: src/methods/example.md:22 -msgid "\"Lap {idx}: {lap} sec\"" +#: src/std-types/string.md:42 +msgid "" +"To a substring by using `s3[0..4]`, where that slice is on character " +"boundaries or not." msgstr "" -#: src/methods/example.md:26 -msgid "// Exclusive ownership of self\n" +#: src/std-types/vec.md:1 +msgid "`Vec`" +msgstr "`Vec`" + +#: src/std-types/vec.md:3 +msgid "" +"[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " +"resizable heap-allocated buffer:" msgstr "" -#: src/methods/example.md:28 -msgid "\"Race {} is finished, total lap time: {}\"" +#: src/std-types/vec.md:9 +msgid "\"v1: len = {}, capacity = {}\"" +msgstr "\"v1: len = {}, capacity = {}\"" + +#: src/std-types/vec.md:14 +msgid "\"v2: len = {}, capacity = {}\"" +msgstr "\"v2: len = {}, capacity = {}\"" + +#: src/std-types/vec.md:16 +msgid "// Canonical macro to initialize a vector with elements.\n" msgstr "" -#: src/methods/example.md:33 -msgid "\"Monaco Grand Prix\"" -msgstr "\"Monacos Grand Prix\"" +#: src/std-types/vec.md:19 +msgid "// Retain only the even elements.\n" +msgstr "" -#: src/methods/example.md:40 -msgid "// race.add_lap(42);\n" -msgstr "// race.add_lap(42);\n" +#: src/std-types/vec.md:21 src/std-types/vec.md:25 +msgid "\"{v3:?}\"" +msgstr "\"{v3:?}\"" -#: src/methods/example.md:47 -msgid "All four methods here use a different method receiver." +#: src/std-types/vec.md:23 +msgid "// Remove consecutive duplicates.\n" msgstr "" -#: src/methods/example.md:48 +#: src/std-types/vec.md:29 msgid "" -"You can point out how that changes what the function can do with the " -"variable values and if/how it can be used again in `main`." +"`Vec` implements [`Deref`](https://doc.rust-lang.org/std/vec/" +"struct.Vec.html#deref-methods-%5BT%5D), which means that you can call slice " +"methods on a `Vec`." msgstr "" -#: src/methods/example.md:49 +#: src/std-types/vec.md:38 msgid "" -"You can showcase the error that appears when trying to call `finish` twice." +"`Vec` is a type of collection, along with `String` and `HashMap`. The data " +"it contains is stored on the heap. This means the amount of data doesn't " +"need to be known at compile time. It can grow or shrink at runtime." msgstr "" -#: src/methods/example.md:50 +#: src/std-types/vec.md:41 msgid "" -"Note that although the method receivers are different, the non-static " -"functions are called the same way in the main body. Rust enables automatic " -"referencing and dereferencing when calling methods. Rust automatically adds " -"in the `&`, `*`, `muts` so that that object matches the method signature." +"Notice how `Vec` is a generic type too, but you don't have to specify `T` " +"explicitly. As always with Rust type inference, the `T` was established " +"during the first `push` call." msgstr "" -#: src/methods/example.md:51 +#: src/std-types/vec.md:43 msgid "" -"You might point out that `print_laps` is using a vector that is iterated " -"over. We describe vectors in more detail in the afternoon. " +"`vec![...]` is a canonical macro to use instead of `Vec::new()` and it " +"supports adding initial elements to the vector." msgstr "" -#: src/exercises/day-2/morning.md:1 -msgid "Day 2: Morning Exercises" -msgstr "Dag 2: formiddagsøvelser" - -#: src/exercises/day-2/morning.md:3 -msgid "We will look at implementing methods in two contexts:" +#: src/std-types/vec.md:45 +msgid "" +"To index the vector you use `[` `]`, but they will panic if out of bounds. " +"Alternatively, using `get` will return an `Option`. The `pop` function will " +"remove the last element." msgstr "" -#: src/exercises/day-2/morning.md:5 -msgid "Storing books and querying the collection" +#: src/std-types/vec.md:47 +msgid "" +"Slices are covered on day 3. For now, students only need to know that a " +"value of type `Vec` gives access to all of the documented read-only slice " +"methods, too." msgstr "" -#: src/exercises/day-2/morning.md:7 -msgid "Keeping track of health statistics for patients" -msgstr "" +#: src/std-types/hashmap.md:1 src/bare-metal/no_std.md:46 +msgid "`HashMap`" +msgstr "`HashMap`" -#: src/exercises/day-2/book-library.md:3 -msgid "" -"We will learn much more about structs and the `Vec` type tomorrow. For " -"now, you just need to know part of its API:" +#: src/std-types/hashmap.md:3 +msgid "Standard hash map with protection against HashDoS attacks:" msgstr "" -#: src/exercises/day-2/book-library.md:11 -msgid "\"middle value: {}\"" -msgstr "\"midterste værdi: {}\"" +#: src/std-types/hashmap.md:10 +msgid "\"Adventures of Huckleberry Finn\"" +msgstr "\"Huckleberry Finn\"" -#: src/exercises/day-2/book-library.md:13 -msgid "\"item: {item}\"" -msgstr "\"item: {item}\"" +#: src/std-types/hashmap.md:11 +msgid "\"Grimms' Fairy Tales\"" +msgstr "\"Grimms eventyr\"" -#: src/exercises/day-2/book-library.md:18 -msgid "" -"Use this to model a library's book collection. Copy the code below to " -" and update the types to make it compile:" -msgstr "" +#: src/std-types/hashmap.md:12 src/std-types/hashmap.md:19 +#: src/std-types/hashmap.md:27 +msgid "\"Pride and Prejudice\"" +msgstr "\"Stolthed og fordom\"" -#: src/exercises/day-2/book-library.md:32 -#: src/exercises/day-2/solutions-morning.md:18 -msgid "// This is a constructor, used below.\n" -msgstr "" +#: src/std-types/hashmap.md:14 +msgid "\"Les Misérables\"" +msgstr "\"De Elendige\"" -#: src/exercises/day-2/book-library.md:40 -#: src/exercises/day-2/solutions-morning.md:26 -msgid "" -"// Implement the methods below. Notice how the `self` parameter\n" -"// changes type to indicate the method's required level of ownership\n" -"// over the object:\n" -"//\n" -"// - `&self` for shared read-only access,\n" -"// - `&mut self` for unique and mutable access,\n" -"// - `self` for unique access by value.\n" +#: src/std-types/hashmap.md:15 +msgid "\"We know about {} books, but not Les Misérables.\"" msgstr "" -#: src/exercises/day-2/book-library.md:50 -msgid "\"Initialize and return a `Library` value\"" -msgstr "" +#: src/std-types/hashmap.md:19 src/std-types/hashmap.md:27 +msgid "\"Alice's Adventure in Wonderland\"" +msgstr "\"Alice i Eventyrland\"" -#: src/exercises/day-2/book-library.md:54 -msgid "\"Return the length of `self.books`\"" -msgstr "" +#: src/std-types/hashmap.md:21 +msgid "\"{book}: {count} pages\"" +msgstr "\"{book}: {count} sider\"" -#: src/exercises/day-2/book-library.md:58 -msgid "\"Return `true` if `self.books` is empty\"" -msgstr "" +#: src/std-types/hashmap.md:22 +msgid "\"{book} is unknown.\"" +msgstr "\"{book} er ukendt.\"" -#: src/exercises/day-2/book-library.md:62 -msgid "\"Add a new book to `self.books`\"" +#: src/std-types/hashmap.md:26 +msgid "// Use the .entry() method to insert a value if nothing is found.\n" msgstr "" -#: src/exercises/day-2/book-library.md:66 -msgid "\"Iterate over `self.books` and print each book's title and year\"" +#: src/std-types/hashmap.md:32 +msgid "\"{page_counts:#?}\"" +msgstr "\"{page_counts:#?}\"" + +#: src/std-types/hashmap.md:39 +msgid "" +"`HashMap` is not defined in the prelude and needs to be brought into scope." msgstr "" -#: src/exercises/day-2/book-library.md:70 -msgid "\"Return a reference to the oldest book (if any)\"" +#: src/std-types/hashmap.md:40 +msgid "" +"Try the following lines of code. The first line will see if a book is in the " +"hashmap and if not return an alternative value. The second line will insert " +"the alternative value in the hashmap if the book is not found." msgstr "" -#: src/exercises/day-2/book-library.md:78 -#: src/exercises/day-2/solutions-morning.md:78 -msgid "\"The library is empty: library.is_empty() -> {}\"" +#: src/std-types/hashmap.md:44 src/std-types/hashmap.md:55 +msgid "\"Harry Potter and the Sorcerer's Stone\"" msgstr "" -#: src/exercises/day-2/book-library.md:82 -#: src/exercises/day-2/solutions-morning.md:82 -#: src/exercises/day-2/solutions-morning.md:107 -#: src/exercises/day-2/solutions-morning.md:118 -#: src/exercises/day-2/solutions-morning.md:125 -#: src/exercises/day-2/solutions-morning.md:137 -#: src/exercises/day-2/solutions-morning.md:140 -msgid "\"Lord of the Rings\"" -msgstr "\"Ringenes Herre\"" +#: src/std-types/hashmap.md:47 src/std-types/hashmap.md:56 +msgid "\"The Hunger Games\"" +msgstr "\"Dødsspillet\"" -#: src/exercises/day-2/book-library.md:83 -#: src/exercises/day-2/solutions-morning.md:83 -#: src/exercises/day-2/solutions-morning.md:108 -#: src/exercises/day-2/solutions-morning.md:126 -#: src/exercises/day-2/solutions-morning.md:143 -#: src/exercises/day-2/solutions-morning.md:146 -msgid "\"Alice's Adventures in Wonderland\"" -msgstr "\"Alice i Eventyrland\"" +#: src/std-types/hashmap.md:50 +msgid "Unlike `vec!`, there is unfortunately no standard `hashmap!` macro." +msgstr "" -#: src/exercises/day-2/book-library.md:86 -#: src/exercises/day-2/solutions-morning.md:86 -msgid "\"The library is no longer empty: library.is_empty() -> {}\"" +#: src/std-types/hashmap.md:51 +msgid "" +"Although, since Rust 1.56, HashMap implements [`From<[(K, V); N]>`](https://" +"doc.rust-lang.org/std/collections/hash_map/struct.HashMap.html#impl-" +"From%3C%5B(K,+V);+N%5D%3E-for-HashMap%3CK,+V,+RandomState%3E), which allows " +"us to easily initialize a hash map from a literal array:" msgstr "" -#: src/exercises/day-2/book-library.md:93 -#: src/exercises/day-2/solutions-morning.md:93 -msgid "\"The oldest book is {}\"" +#: src/std-types/hashmap.md:60 +msgid "" +"Alternatively HashMap can be built from any `Iterator` which yields key-" +"value tuples." msgstr "" -#: src/exercises/day-2/book-library.md:94 -#: src/exercises/day-2/solutions-morning.md:94 -msgid "\"The library is empty!\"" +#: src/std-types/hashmap.md:61 +msgid "" +"We are showing `HashMap`, and avoid using `&str` as key to make " +"examples easier. Using references in collections can, of course, be done, " +"but it can lead into complications with the borrow checker." msgstr "" -#: src/exercises/day-2/book-library.md:97 -#: src/exercises/day-2/solutions-morning.md:97 -msgid "\"The library has {} books\"" +#: src/std-types/hashmap.md:63 +msgid "" +"Try removing `to_string()` from the example above and see if it still " +"compiles. Where do you think we might run into issues?" msgstr "" -#: src/exercises/day-2/health-statistics.md:3 +#: src/std-types/hashmap.md:65 msgid "" -"You're working on implementing a health-monitoring system. As part of that, " -"you need to keep track of users' health statistics." +"This type has several \"method-specific\" return types, such as `std::" +"collections::hash_map::Keys`. These types often appear in searches of the " +"Rust docs. Show students the docs for this type, and the helpful link back " +"to the `keys` method." msgstr "" -#: src/exercises/day-2/health-statistics.md:6 +#: src/std-types/exercise.md:3 msgid "" -"You'll start with some stubbed functions in an `impl` block as well as a " -"`User` struct definition. Your goal is to implement the stubbed out methods " -"on the `User` `struct` defined in the `impl` block." +"In this exercise you will take a very simple data structure and make it " +"generic. It uses a [`std::collections::HashMap`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html) to keep track of which values " +"have been seen and how many times each one has appeared." msgstr "" -#: src/exercises/day-2/health-statistics.md:10 +#: src/std-types/exercise.md:9 msgid "" -"Copy the code below to and fill in the missing " -"methods:" +"The initial version of `Counter` is hard coded to only work for `u32` " +"values. Make the struct and its methods generic over the type of value being " +"tracked, that way `Counter` can track any type of value." msgstr "" -#: src/exercises/day-2/health-statistics.md:39 -msgid "\"Create a new User instance\"" +#: src/std-types/exercise.md:13 +msgid "" +"If you finish early, try using the [`entry`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html#method.entry) method to halve the " +"number of hash lookups required to implement the `count` method." msgstr "" -#: src/exercises/day-2/health-statistics.md:43 -msgid "\"Return the user's name\"" +#: src/std-types/exercise.md:20 src/std-types/solution.md:6 +msgid "" +"/// Counter counts the number of times each value of type T has been seen.\n" msgstr "" -#: src/exercises/day-2/health-statistics.md:47 -msgid "\"Return the user's age\"" +#: src/std-types/exercise.md:27 src/std-types/solution.md:13 +#, fuzzy +msgid "/// Create a new Counter.\n" +msgstr "/// Break error.\n" + +#: src/std-types/exercise.md:34 src/std-types/solution.md:20 +msgid "/// Count an occurrence of the given value.\n" msgstr "" -#: src/exercises/day-2/health-statistics.md:51 -msgid "\"Return the user's height\"" +#: src/std-types/exercise.md:43 src/std-types/solution.md:25 +msgid "/// Return the number of times the given value has been seen.\n" msgstr "" -#: src/exercises/day-2/health-statistics.md:55 -msgid "\"Return the number of time the user has visited the doctor\"" +#: src/std-types/exercise.md:59 src/std-types/solution.md:41 +msgid "\"saw {} values equal to {}\"" msgstr "" -#: src/exercises/day-2/health-statistics.md:59 -msgid "\"Set the user's age\"" +#: src/std-types/exercise.md:63 src/std-types/exercise.md:65 +#: src/std-types/exercise.md:66 src/std-types/solution.md:45 +#: src/std-types/solution.md:47 src/std-types/solution.md:48 +msgid "\"apple\"" msgstr "" -#: src/exercises/day-2/health-statistics.md:63 -msgid "\"Set the user's height\"" +#: src/std-types/exercise.md:64 src/std-types/solution.md:46 +msgid "\"orange\"" msgstr "" -#: src/exercises/day-2/health-statistics.md:67 -msgid "" -"\"Update a user's statistics based on measurements from a visit to the " -"doctor\"" +#: src/std-types/exercise.md:66 src/std-types/solution.md:48 +msgid "\"got {} apples\"" msgstr "" -#: src/exercises/day-2/health-statistics.md:72 -#: src/exercises/day-2/health-statistics.md:78 -#: src/exercises/day-2/health-statistics.md:84 -#: src/exercises/day-2/health-statistics.md:92 -#: src/exercises/day-2/health-statistics.md:98 -#: src/android/build-rules/library.md:44 src/android/aidl/client.md:23 -#: src/exercises/day-2/solutions-morning.md:233 -#: src/exercises/day-2/solutions-morning.md:239 -#: src/exercises/day-2/solutions-morning.md:245 -#: src/exercises/day-2/solutions-morning.md:253 -#: src/exercises/day-2/solutions-morning.md:259 -msgid "\"Bob\"" -msgstr "\"Bob\"" +#: src/std-traits.md:4 +msgid "[Comparisons](./std-traits/comparisons.md) (10 minutes)" +msgstr "" -#: src/exercises/day-2/health-statistics.md:73 -#: src/exercises/day-2/solutions-morning.md:234 -msgid "\"I'm {} and my age is {}\"" +#: src/std-traits.md:5 +msgid "[Operators](./std-traits/operators.md) (10 minutes)" msgstr "" -#: src/std.md:3 -msgid "" -"Rust comes with a standard library which helps establish a set of common " -"types used by Rust library and programs. This way, two libraries can work " -"together smoothly because they both use the same `String` type." +#: src/std-traits.md:6 +msgid "[From and Into](./std-traits/from-and-into.md) (10 minutes)" msgstr "" -#: src/std.md:7 -msgid "The common vocabulary types include:" +#: src/std-traits.md:7 +msgid "[Casting](./std-traits/casting.md) (5 minutes)" msgstr "" -#: src/std.md:9 -msgid "" -"[`Option` and `Result`](std/option-result.md) types: used for optional " -"values and [error handling](error-handling.md)." +#: src/std-traits.md:8 +msgid "[Read and Write](./std-traits/read-and-write.md) (10 minutes)" msgstr "" -#: src/std.md:12 -msgid "[`String`](std/string.md): the default string type used for owned data." +#: src/std-traits.md:9 +msgid "[Default, struct update syntax](./std-traits/default.md) (5 minutes)" msgstr "" -#: src/std.md:14 -msgid "[`Vec`](std/vec.md): a standard extensible vector." +#: src/std-traits.md:10 +msgid "[Closures](./std-traits/closures.md) (20 minutes)" msgstr "" -#: src/std.md:16 -msgid "" -"[`HashMap`](std/hashmap.md): a hash map type with a configurable hashing " -"algorithm." +#: src/std-traits.md:11 +msgid "[Exercise: ROT13](./std-traits/exercise.md) (30 minutes)" msgstr "" -#: src/std.md:19 -msgid "[`Box`](std/box.md): an owned pointer for heap-allocated data." +#: src/std-traits.md:13 +msgid "This segment should take about 1 hour and 40 minutes" msgstr "" -#: src/std.md:21 +#: src/std-traits.md:18 msgid "" -"[`Rc`](std/rc.md): a shared reference-counted pointer for heap-allocated " -"data." +"As with the standard-library types, spend time reviewing the documentation " +"for each trait." msgstr "" -#: src/std.md:25 -msgid "" -"In fact, Rust contains several layers of the Standard Library: `core`, " -"`alloc` and `std`. " +#: src/std-traits.md:21 +msgid "This section is long. Take a break midway through." msgstr "" -#: src/std.md:26 +#: src/std-traits/comparisons.md:3 msgid "" -"`core` includes the most basic types and functions that don't depend on " -"`libc`, allocator or even the presence of an operating system. " +"These traits support comparisons between values. All traits can be derived " +"for types containing fields that implement these traits." msgstr "" -#: src/std.md:28 -msgid "" -"`alloc` includes types which require a global heap allocator, such as `Vec`, " -"`Box` and `Arc`." +#: src/std-traits/comparisons.md:6 +msgid "`PartialEq` and `Eq`" msgstr "" -#: src/std.md:29 +#: src/std-traits/comparisons.md:8 msgid "" -"Embedded Rust applications often only use `core`, and sometimes `alloc`." +"`PartialEq` is a partial equivalence relation, with required method `eq` and " +"provided method `ne`. The `==` and `!=` operators will call these methods." msgstr "" -#: src/std/option-result.md:1 -msgid "`Option` and `Result`" -msgstr "`Option` og `Result`" - -#: src/std/option-result.md:3 -msgid "The types represent optional data:" +#: src/std-traits/comparisons.md:20 +msgid "" +"`Eq` is a full equivalence relation (reflexive, symmetric, and transitive) " +"and implies `PartialEq`. Functions that require full equivalence will use " +"`Eq` as a trait bound." msgstr "" -#: src/std/option-result.md:9 -msgid "\"first: {first:?}\"" -msgstr "\"first: {first:?}\"" - -#: src/std/option-result.md:12 -msgid "\"arr: {arr:?}\"" -msgstr "\"arr: {arr:?}\"" +#: src/std-traits/comparisons.md:24 +#, fuzzy +msgid "`PartialOrd` and `Ord`" +msgstr "`Read` og `Write`" -#: src/std/option-result.md:18 -msgid "`Option` and `Result` are widely used not just in the standard library." +#: src/std-traits/comparisons.md:26 +msgid "" +"`PartialOrd` defines a partial ordering, with a `partial_cmp` method. It is " +"used to implement the `<`, `<=`, `>=`, and `>` operators." msgstr "" -#: src/std/option-result.md:19 -msgid "`Option<&T>` has zero space overhead compared to `&T`." +#: src/std-traits/comparisons.md:43 +msgid "`Ord` is a total ordering, with `cmp` returning `Ordering`." msgstr "" -#: src/std/option-result.md:20 +#: src/std-traits/comparisons.md:48 msgid "" -"`Result` is the standard type to implement error handling as we will see on " -"Day 3." +"`PartialEq` can be implemented between different types, but `Eq` cannot, " +"because it is reflexive:" msgstr "" -#: src/std/option-result.md:21 +#: src/std-traits/comparisons.md:59 msgid "" -"`try_into` attempts to convert the vector into a fixed-sized array. This can " -"fail:" +"In practice, it's common to derive these traits, but uncommon to implement " +"them." msgstr "" -#: src/std/option-result.md:22 +#: src/std-traits/operators.md:3 msgid "" -"If the vector has the right size, `Result::Ok` is returned with the array." +"Operator overloading is implemented via traits in [`std::ops`](https://doc." +"rust-lang.org/std/ops/index.html):" msgstr "" -#: src/std/option-result.md:23 -msgid "Otherwise, `Result::Err` is returned with the original vector." +#: src/std-traits/operators.md:20 +msgid "\"{:?} + {:?} = {:?}\"" +msgstr "\"{:?} + {:?} = {:?}\"" + +#: src/std-traits/operators.md:27 src/memory-management/drop.md:46 +msgid "Discussion points:" msgstr "" -#: src/std/string.md:3 +#: src/std-traits/operators.md:29 msgid "" -"[`String`](https://doc.rust-lang.org/std/string/struct.String.html) is the " -"standard heap-allocated growable UTF-8 string buffer:" +"You could implement `Add` for `&Point`. In which situations is that useful?" msgstr "" -#: src/std/string.md:9 -msgid "\"s1: len = {}, capacity = {}\"" -msgstr "\"s1: len = {}, capacity = {}\"" - -#: src/std/string.md:13 -msgid "'!'" -msgstr "'!'" - -#: src/std/string.md:14 -msgid "\"s2: len = {}, capacity = {}\"" -msgstr "\"s2: len = {}, capacity = {}\"" - -#: src/std/string.md:16 -msgid "\"🇨🇭\"" -msgstr "\"🇨🇭\"" - -#: src/std/string.md:17 -msgid "\"s3: len = {}, number of chars = {}\"" -msgstr "\"s3: len = {}, antal tegn = {}\"" +#: src/std-traits/operators.md:30 +msgid "" +"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " +"the operator is not `Copy`, you should consider overloading the operator for " +"`&T` as well. This avoids unnecessary cloning on the call site." +msgstr "" -#: src/std/string.md:22 +#: src/std-traits/operators.md:34 msgid "" -"`String` implements [`Deref`](https://doc.rust-lang.org/std/" -"string/struct.String.html#deref-methods-str), which means that you can call " -"all `str` methods on a `String`." +"Why is `Output` an associated type? Could it be made a type parameter of the " +"method?" msgstr "" -#: src/std/string.md:30 +#: src/std-traits/operators.md:35 msgid "" -"`String::new` returns a new empty string, use `String::with_capacity` when " -"you know how much data you want to push to the string." +"Short answer: Function type parameters are controlled by the caller, but " +"associated types (like `Output`) are controlled by the implementor of a " +"trait." msgstr "" -#: src/std/string.md:31 +#: src/std-traits/operators.md:38 msgid "" -"`String::len` returns the size of the `String` in bytes (which can be " -"different from its length in characters)." +"You could implement `Add` for two different types, e.g. `impl Add<(i32, " +"i32)> for Point` would add a tuple to a `Point`." msgstr "" -#: src/std/string.md:32 +#: src/std-traits/from-and-into.md:1 +msgid "`From` and `Into`" +msgstr "`From` og `Into`" + +#: src/std-traits/from-and-into.md:3 msgid "" -"`String::chars` returns an iterator over the actual characters. Note that a " -"`char` can be different from what a human will consider a \"character\" due " -"to [grapheme clusters](https://docs.rs/unicode-segmentation/latest/" -"unicode_segmentation/struct.Graphemes.html)." +"Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." +"html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " +"facilitate type conversions:" msgstr "" -#: src/std/string.md:33 +#: src/std-traits/from-and-into.md:11 src/std-traits/from-and-into.md:23 +msgid "\"{s}, {addr}, {one}, {bigger}\"" +msgstr "\"{s}, {addr}, {one}, {bigger}\"" + +#: src/std-traits/from-and-into.md:15 msgid "" -"When people refer to strings they could either be talking about `&str` or " -"`String`." +"[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) is " +"automatically implemented when [`From`](https://doc.rust-lang.org/std/" +"convert/trait.From.html) is implemented:" msgstr "" -#: src/std/string.md:34 +#: src/std-traits/from-and-into.md:30 msgid "" -"When a type implements `Deref`, the compiler will let you " -"transparently call methods from `T`." +"That's why it is common to only implement `From`, as your type will get " +"`Into` implementation too." msgstr "" -#: src/std/string.md:35 +#: src/std-traits/from-and-into.md:31 msgid "" -"`String` implements `Deref` which transparently gives it " -"access to `str`'s methods." +"When declaring a function argument input type like \"anything that can be " +"converted into a `String`\", the rule is opposite, you should use `Into`. " +"Your function will accept types that implement `From` and those that _only_ " +"implement `Into`." msgstr "" -#: src/std/string.md:36 -msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1`;." +#: src/std-traits/casting.md:3 +msgid "" +"Rust has no _implicit_ type conversions, but does support explicit casts " +"with `as`. These generally follow C semantics where those are defined." msgstr "" -#: src/std/string.md:37 +#: src/std-traits/casting.md:9 +#, fuzzy +msgid "\"as u16: {}\"" +msgstr "\"pengepremie: {}\"" + +#: src/std-traits/casting.md:10 +#, fuzzy +msgid "\"as i16: {}\"" +msgstr "\"pengepremie: {}\"" + +#: src/std-traits/casting.md:11 +#, fuzzy +msgid "\"as u8: {}\"" +msgstr "\"pengepremie: {}\"" + +#: src/std-traits/casting.md:15 msgid "" -"`String` is implemented as a wrapper around a vector of bytes, many of the " -"operations you see supported on vectors are also supported on `String`, but " -"with some extra guarantees." +"The results of `as` are _always_ defined in Rust and consistent across " +"platforms. This might not match your intuition for changing sign or casting " +"to a smaller type -- check the docs, and comment for clarity." msgstr "" -#: src/std/string.md:38 -msgid "Compare the different ways to index a `String`:" +#: src/std-traits/casting.md:22 +msgid "Consider taking a break after this slide." msgstr "" -#: src/std/string.md:39 +#: src/std-traits/casting.md:24 msgid "" -"To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, " -"out-of-bounds." +"`as` is similar to a C++ static cast. Use of `as` in cases where data might " +"be lost is generally discouraged, or at least deserves an explanatory " +"comment." msgstr "" -#: src/std/string.md:40 -msgid "" -"To a substring by using `s3[0..4]`, where that slice is on character " -"boundaries or not." +#: src/std-traits/casting.md:27 +msgid "This is common in casting integers to `usize` for use as an index." msgstr "" -#: src/std/vec.md:1 -msgid "`Vec`" -msgstr "`Vec`" +#: src/std-traits/read-and-write.md:1 +msgid "`Read` and `Write`" +msgstr "`Read` og `Write`" -#: src/std/vec.md:3 +#: src/std-traits/read-and-write.md:3 msgid "" -"[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " -"resizable heap-allocated buffer:" +"Using [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and " +"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html), you can " +"abstract over `u8` sources:" msgstr "" -#: src/std/vec.md:9 -msgid "\"v1: len = {}, capacity = {}\"" -msgstr "\"v1: len = {}, capacity = {}\"" +#: src/std-traits/read-and-write.md:14 +msgid "b\"foo\\nbar\\nbaz\\n\"" +msgstr "b\"foo\\nbar\\nbaz\\n\"" -#: src/std/vec.md:14 -msgid "\"v2: len = {}, capacity = {}\"" -msgstr "\"v2: len = {}, capacity = {}\"" +#: src/std-traits/read-and-write.md:15 +msgid "\"lines in slice: {}\"" +msgstr "\"linjer i slice: {}\"" -#: src/std/vec.md:16 -msgid "// Canonical macro to initialize a vector with elements.\n" -msgstr "" +#: src/std-traits/read-and-write.md:18 +msgid "\"lines in file: {}\"" +msgstr "\"linjer i file: {}\"" -#: src/std/vec.md:19 -msgid "// Retain only the even elements.\n" +#: src/std-traits/read-and-write.md:23 +msgid "" +"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " +"you abstract over `u8` sinks:" msgstr "" -#: src/std/vec.md:21 src/std/vec.md:25 -msgid "\"{v3:?}\"" -msgstr "\"{v3:?}\"" +#: src/std-traits/read-and-write.md:30 +msgid "\"\\n\"" +msgstr "\"\\n\"" -#: src/std/vec.md:23 -msgid "// Remove consecutive duplicates.\n" -msgstr "" +#: src/std-traits/read-and-write.md:36 src/slices-and-lifetimes/str.md:11 +msgid "\"World\"" +msgstr "\"Verden\"" -#: src/std/vec.md:29 -msgid "" -"`Vec` implements [`Deref`](https://doc.rust-lang.org/std/vec/" -"struct.Vec.html#deref-methods-%5BT%5D), which means that you can call slice " -"methods on a `Vec`." +#: src/std-traits/read-and-write.md:37 +msgid "\"Logged: {:?}\"" msgstr "" -#: src/std/vec.md:37 -msgid "" -"`Vec` is a type of collection, along with `String` and `HashMap`. The data " -"it contains is stored on the heap. This means the amount of data doesn't " -"need to be known at compile time. It can grow or shrink at runtime." +#: src/std-traits/default.md:1 +msgid "The `Default` Trait" msgstr "" -#: src/std/vec.md:40 +#: src/std-traits/default.md:3 msgid "" -"Notice how `Vec` is a generic type too, but you don't have to specify `T` " -"explicitly. As always with Rust type inference, the `T` was established " -"during the first `push` call." +"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " +"produces a default value for a type." msgstr "" -#: src/std/vec.md:42 -msgid "" -"`vec![...]` is a canonical macro to use instead of `Vec::new()` and it " -"supports adding initial elements to the vector." +#: src/std-traits/default.md:18 +msgid "\"John Smith\"" +msgstr "\"John Smith\"" + +#: src/std-traits/default.md:24 +msgid "\"{default_struct:#?}\"" +msgstr "\"{default_struct:#?}\"" + +#: src/std-traits/default.md:27 +msgid "\"Y is set!\"" +msgstr "\"Y er sat!\"" + +#: src/std-traits/default.md:30 +msgid "\"{almost_default_struct:#?}\"" msgstr "" -#: src/std/vec.md:44 +#: src/std-traits/default.md:33 +msgid "\"{:#?}\"" +msgstr "\"{:#?}\"" + +#: src/std-traits/default.md:41 msgid "" -"To index the vector you use `[` `]`, but they will panic if out of bounds. " -"Alternatively, using `get` will return an `Option`. The `pop` function will " -"remove the last element." +"It can be implemented directly or it can be derived via `#[derive(Default)]`." msgstr "" -#: src/std/vec.md:46 +#: src/std-traits/default.md:42 msgid "" -"Show iterating over a vector and mutating the value: `for e in &mut v { *e " -"+= 50; }`" +"A derived implementation will produce a value where all fields are set to " +"their default values." msgstr "" -#: src/std/hashmap.md:1 src/bare-metal/no_std.md:46 -msgid "`HashMap`" -msgstr "`HashMap`" - -#: src/std/hashmap.md:3 -msgid "Standard hash map with protection against HashDoS attacks:" +#: src/std-traits/default.md:43 +msgid "This means all types in the struct must implement `Default` too." msgstr "" -#: src/std/hashmap.md:10 -msgid "\"Adventures of Huckleberry Finn\"" -msgstr "\"Huckleberry Finn\"" - -#: src/std/hashmap.md:11 -msgid "\"Grimms' Fairy Tales\"" -msgstr "\"Grimms eventyr\"" - -#: src/std/hashmap.md:12 src/std/hashmap.md:19 src/std/hashmap.md:27 -msgid "\"Pride and Prejudice\"" -msgstr "\"Stolthed og fordom\"" - -#: src/std/hashmap.md:14 -msgid "\"Les Misérables\"" -msgstr "\"De Elendige\"" - -#: src/std/hashmap.md:15 -msgid "\"We know about {} books, but not Les Misérables.\"" +#: src/std-traits/default.md:44 +msgid "" +"Standard Rust types often implement `Default` with reasonable values (e.g. " +"`0`, `\"\"`, etc)." msgstr "" -#: src/std/hashmap.md:19 src/std/hashmap.md:27 -msgid "\"Alice's Adventure in Wonderland\"" -msgstr "\"Alice i Eventyrland\"" - -#: src/std/hashmap.md:21 -msgid "\"{book}: {count} pages\"" -msgstr "\"{book}: {count} sider\"" - -#: src/std/hashmap.md:22 -msgid "\"{book} is unknown.\"" -msgstr "\"{book} er ukendt.\"" - -#: src/std/hashmap.md:26 -msgid "// Use the .entry() method to insert a value if nothing is found.\n" +#: src/std-traits/default.md:45 +msgid "The partial struct copy works nicely with default." msgstr "" -#: src/std/hashmap.md:32 -msgid "\"{page_counts:#?}\"" -msgstr "\"{page_counts:#?}\"" +#: src/std-traits/default.md:46 +msgid "" +"Rust standard library is aware that types can implement `Default` and " +"provides convenience methods that use it." +msgstr "" -#: src/std/hashmap.md:38 +#: src/std-traits/default.md:47 msgid "" -"`HashMap` is not defined in the prelude and needs to be brought into scope." +"the `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" +"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" +"with-struct-update-syntax)" msgstr "" -#: src/std/hashmap.md:39 +#: src/std-traits/closures.md:3 msgid "" -"Try the following lines of code. The first line will see if a book is in the " -"hashmap and if not return an alternative value. The second line will insert " -"the alternative value in the hashmap if the book is not found." +"Closures or lambda expressions have types which cannot be named. However, " +"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." +"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " +"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" msgstr "" -#: src/std/hashmap.md:43 -msgid "\"Harry Potter and the Sorcerer's Stone \"" -msgstr "\"Harry Potter og De Vises Sten\"" +#: src/std-traits/closures.md:10 +msgid "\"Calling function on {input}\"" +msgstr "" -#: src/std/hashmap.md:46 src/std/hashmap.md:55 -msgid "\"The Hunger Games\"" -msgstr "\"Dødsspillet\"" +#: src/std-traits/closures.md:16 src/std-traits/closures.md:17 +msgid "\"add_3: {}\"" +msgstr "\"add_3: {}\"" -#: src/std/hashmap.md:49 -msgid "Unlike `vec!`, there is unfortunately no standard `hashmap!` macro." -msgstr "" +#: src/std-traits/closures.md:24 src/std-traits/closures.md:25 +msgid "\"accumulate: {}\"" +msgstr "\"accumulate: {}\"" + +#: src/std-traits/closures.md:28 +msgid "\"multiply_sum: {}\"" +msgstr "\"multiply_sum: {}\"" -#: src/std/hashmap.md:50 +#: src/std-traits/closures.md:35 msgid "" -"Although, since Rust 1.56, HashMap implements [`From<[(K, V); N]>`](https://" -"doc.rust-lang.org/std/collections/hash_map/struct.HashMap.html#impl-" -"From%3C%5B(K,+V);+N%5D%3E-for-HashMap%3CK,+V,+RandomState%3E), which allows " -"us to easily initialize a hash map from a literal array:" +"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " +"perhaps captures nothing at all. It can be called multiple times " +"concurrently." msgstr "" -#: src/std/hashmap.md:54 -msgid "\"Harry Potter and the Sorcerer's Stone\"" +#: src/std-traits/closures.md:38 +msgid "" +"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " +"multiple times, but not concurrently." msgstr "" -#: src/std/hashmap.md:59 +#: src/std-traits/closures.md:41 msgid "" -"Alternatively HashMap can be built from any `Iterator` which yields key-" -"value tuples." +"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " +"might consume captured values." msgstr "" -#: src/std/hashmap.md:60 +#: src/std-traits/closures.md:44 msgid "" -"We are showing `HashMap`, and avoid using `&str` as key to make " -"examples easier. Using references in collections can, of course, be done, " -"but it can lead into complications with the borrow checker." +"`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " +"I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " +"use an `Fn` wherever an `FnMut` or `FnOnce` is called for." msgstr "" -#: src/std/hashmap.md:62 +#: src/std-traits/closures.md:48 msgid "" -"Try removing `to_string()` from the example above and see if it still " -"compiles. Where do you think we might run into issues?" +"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " +"`multiply_sum`), depending on what the closure captures." msgstr "" -#: src/std/hashmap.md:64 +#: src/std-traits/closures.md:51 msgid "" -"This type has several \"method-specific\" return types, such as `std::" -"collections::hash_map::Keys`. These types often appear in searches of the " -"Rust docs. Show students the docs for this type, and the helpful link back " -"to the `keys` method." +"By default, closures will capture by reference if they can. The `move` " +"keyword makes them capture by value." msgstr "" -#: src/std/box.md:1 -msgid "`Box`" -msgstr "`Box`" +#: src/std-traits/closures.md:59 +msgid "\"Hi\"" +msgstr "\"Hej\"" -#: src/std/box.md:3 +#: src/std-traits/closures.md:60 +msgid "\"there\"" +msgstr "\"der\"" + +#: src/std-traits/exercise.md:3 msgid "" -"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " -"pointer to data on the heap:" +"In this example, you will implement the classic [\"ROT13\" cipher](https://" +"en.wikipedia.org/wiki/ROT13). Copy this code to the playground, and " +"implement the missing bits. Only rotate ASCII alphabetic characters, to " +"ensure the result is still valid UTF-8." msgstr "" -#: src/std/box.md:8 -msgid "\"five: {}\"" -msgstr "\"five: {}\"" +#: src/std-traits/exercise.md:15 +msgid "// Implement the `Read` trait for `RotDecoder`.\n" +msgstr "" -#: src/std/box.md:26 -msgid "" -"`Box` implements `Deref`, which means that you can [call " -"methods from `T` directly on a `Box`](https://doc.rust-lang.org/std/ops/" -"trait.Deref.html#more-on-deref-coercion)." +#: src/std-traits/exercise.md:20 src/std-traits/exercise.md:35 +#: src/std-traits/solution.md:26 src/std-traits/solution.md:41 +msgid "\"Gb trg gb gur bgure fvqr!\"" msgstr "" -#: src/std/box.md:34 -msgid "" -"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " -"not null. " +#: src/std-traits/exercise.md:40 src/std-traits/solution.md:46 +msgid "\"To get to the other side!\"" msgstr "" -#: src/std/box.md:35 +#: src/std-traits/exercise.md:62 msgid "" -"In the above example, you can even leave out the `*` in the `println!` " -"statement thanks to `Deref`. " +"What happens if you chain two `RotDecoder` instances together, each rotating " +"by 13 characters?" msgstr "" -#: src/std/box.md:36 -msgid "A `Box` can be useful when you:" -msgstr "" +#: src/std-traits/solution.md:16 +#, fuzzy +msgid "'A'" +msgstr "'x'" -#: src/std/box.md:37 -msgid "" -"have a type whose size that can't be known at compile time, but the Rust " -"compiler wants to know an exact size." +#: src/welcome-day-3.md:1 +msgid "Welcome to Day 3" +msgstr "Velkommen til Dag 3" + +#: src/welcome-day-3.md:3 +msgid "Today, we will cover:" msgstr "" -#: src/std/box.md:38 +#: src/welcome-day-3.md:5 msgid "" -"want to transfer ownership of a large amount of data. To avoid copying large " -"amounts of data on the stack, instead store the data on the heap in a `Box` " -"so only the pointer is moved." +"Memory management, lifetimes, and the borrow checker: how Rust ensures " +"memory safety." msgstr "" -#: src/std/box-recursive.md:1 -msgid "Box with Recursive Data Structures" +#: src/welcome-day-3.md:6 +msgid "Smart pointers: standard library pointer types." msgstr "" -#: src/std/box-recursive.md:3 -msgid "" -"Recursive data types or data types with dynamic sizes need to use a `Box`:" +#: src/welcome-day-3.md:11 +msgid "[Welcome](./welcome-day-3.md) (3 minutes)" msgstr "" -#: src/std/box-recursive.md:14 src/std/box-niche.md:12 -msgid "\"{list:?}\"" -msgstr "\"{list:?}\"" +#: src/welcome-day-3.md:12 +msgid "[Memory Management](./memory-management.md) (1 hour and 10 minutes)" +msgstr "" -#: src/std/box-recursive.md:18 -msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"list : : :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " -"| :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": : : :\n" -": : : :\n" -"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"```" +#: src/welcome-day-3.md:13 +msgid "[Smart Pointers](./smart-pointers.md) (45 minutes)" msgstr "" -"```bob\n" -" Stak Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"list : : :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " -"| :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": : : :\n" -": : : :\n" -"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"```" -#: src/std/box-recursive.md:33 +#: src/welcome-day-3.md:15 msgid "" -"If `Box` was not used and we attempted to embed a `List` directly into the " -"`List`, the compiler would not compute a fixed size of the struct in memory " -"(`List` would be of infinite size)." +"Including 10 minute breaks, this session should take about 2 hours and 15 " +"minutes" msgstr "" -#: src/std/box-recursive.md:36 -msgid "" -"`Box` solves this problem as it has the same size as a regular pointer and " -"just points at the next element of the `List` in the heap." +#: src/memory-management.md:4 +msgid "[Review of Program Memory](./memory-management/review.md) (5 minutes)" msgstr "" -#: src/std/box-recursive.md:39 +#: src/memory-management.md:5 msgid "" -"Remove the `Box` in the List definition and show the compiler error. " -"\"Recursive with indirection\" is a hint you might want to use a Box or " -"reference of some kind, instead of storing a value directly." +"[Approaches to Memory Management](./memory-management/approaches.md) (10 " +"minutes)" msgstr "" -#: src/std/box-niche.md:16 -msgid "" -"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This " -"allows the compiler to optimize the memory layout:" +#: src/memory-management.md:6 +msgid "[Ownership](./memory-management/ownership.md) (5 minutes)" msgstr "" -#: src/std/box-niche.md:19 -msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"-.\n" -": : : :\n" -": " -"list : : :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " -"| :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": : : :\n" -": : : :\n" -"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"-'\n" -"```" +#: src/memory-management.md:7 +msgid "[Move semantics](./memory-management/move.md) (10 minutes)" msgstr "" -"```bob\n" -" Stak Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"-.\n" -": : : :\n" -": " -"list : : :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " -"| :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": : : :\n" -": : : :\n" -"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"-'\n" -"```" -#: src/std/rc.md:1 -msgid "`Rc`" -msgstr "`Rc`" +#: src/memory-management.md:8 +msgid "[Clone](./memory-management/clone.md) (2 minutes)" +msgstr "" -#: src/std/rc.md:3 -msgid "" -"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) is a reference-" -"counted shared pointer. Use this when you need to refer to the same data " -"from multiple places:" +#: src/memory-management.md:9 +msgid "[Copy Types](./memory-management/copy-types.md) (5 minutes)" msgstr "" -#: src/std/rc.md:13 -msgid "\"a: {a}\"" -msgstr "\"a: {a}\"" +#: src/memory-management.md:10 +msgid "[Drop](./memory-management/drop.md) (10 minutes)" +msgstr "" -#: src/std/rc.md:14 -msgid "\"b: {b}\"" -msgstr "\"b: {b}\"" +#: src/memory-management.md:11 +msgid "[Exercise: Builder Type](./memory-management/exercise.md) (20 minutes)" +msgstr "" -#: src/std/rc.md:18 -msgid "" -"See [`Arc`](../concurrency/shared_state/arc.md) and [`Mutex`](https://doc." -"rust-lang.org/std/sync/struct.Mutex.html) if you are in a multi-threaded " -"context." +#: src/memory-management/review.md:3 +msgid "Programs allocate memory in two ways:" msgstr "" -#: src/std/rc.md:19 -msgid "" -"You can _downgrade_ a shared pointer into a [`Weak`](https://doc.rust-lang." -"org/std/rc/struct.Weak.html) pointer to create cycles that will get dropped." +#: src/memory-management/review.md:5 +msgid "Stack: Continuous area of memory for local variables." msgstr "" -#: src/std/rc.md:29 -msgid "" -"`Rc`'s count ensures that its contained value is valid for as long as there " -"are references." +#: src/memory-management/review.md:6 +msgid "Values have fixed sizes known at compile time." msgstr "" -#: src/std/rc.md:30 -msgid "`Rc` in Rust is like `std::shared_ptr` in C++." +#: src/memory-management/review.md:7 +msgid "Extremely fast: just move a stack pointer." msgstr "" -#: src/std/rc.md:31 -msgid "" -"`Rc::clone` is cheap: it creates a pointer to the same allocation and " -"increases the reference count. Does not make a deep clone and can generally " -"be ignored when looking for performance issues in code." +#: src/memory-management/review.md:8 +msgid "Easy to manage: follows function calls." msgstr "" -#: src/std/rc.md:32 -msgid "" -"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " -"and returns a mutable reference." +#: src/memory-management/review.md:9 +msgid "Great memory locality." msgstr "" -#: src/std/rc.md:33 -msgid "Use `Rc::strong_count` to check the reference count." +#: src/memory-management/review.md:11 +msgid "Heap: Storage of values outside of function calls." msgstr "" -#: src/std/rc.md:34 -msgid "" -"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " -"cycles that will be dropped properly (likely in combination with `RefCell`, " -"on the next slide)." +#: src/memory-management/review.md:12 +msgid "Values have dynamic sizes determined at runtime." msgstr "" -#: src/std/cell.md:1 -msgid "`Cell` and `RefCell`" -msgstr "`Cell` og `RefCell`" - -#: src/std/cell.md:3 -msgid "" -"[`Cell`](https://doc.rust-lang.org/std/cell/struct.Cell.html) and [`RefCell`]" -"(https://doc.rust-lang.org/std/cell/struct.RefCell.html) implement what Rust " -"calls _interior mutability:_ mutation of values in an immutable context." +#: src/memory-management/review.md:13 +msgid "Slightly slower than the stack: some book-keeping needed." msgstr "" -#: src/std/cell.md:8 -msgid "" -"`Cell` is typically used for simple types, as it requires copying or moving " -"values. More complex interior types typically use `RefCell`, which tracks " -"shared and exclusive references at runtime and panics if they are misused." +#: src/memory-management/review.md:14 +msgid "No guarantee of memory locality." msgstr "" -#: src/std/cell.md:40 -msgid "\"graph: {root:#?}\"" +#: src/memory-management/review.md:18 +msgid "" +"Creating a `String` puts fixed-sized metadata on the stack and dynamically " +"sized data, the actual string, on the heap:" msgstr "" -#: src/std/cell.md:41 -msgid "\"graph sum: {}\"" +#: src/memory-management/review.md:44 +msgid "" +"Mention that a `String` is backed by a `Vec`, so it has a capacity and " +"length and can grow if mutable via reallocation on the heap." msgstr "" -#: src/std/cell.md:47 +#: src/memory-management/review.md:46 msgid "" -"If we were using `Cell` instead of `RefCell` in this example, we would have " -"to move the `Node` out of the `Rc` to push children, then move it back in. " -"This is safe because there's always one, un-referenced value in the cell, " -"but it's not ergonomic." +"If students ask about it, you can mention that the underlying memory is heap " +"allocated using the [System Allocator](https://doc.rust-lang.org/std/alloc/" +"struct.System.html) and custom allocators can be implemented using the " +"[Allocator API](https://doc.rust-lang.org/std/alloc/index.html)" msgstr "" -#: src/std/cell.md:48 +#: src/memory-management/review.md:50 msgid "" -"To do anything with a Node, you must call a `RefCell` method, usually " -"`borrow` or `borrow_mut`." +"We can inspect the memory layout with `unsafe` Rust. However, you should " +"point out that this is rightfully unsafe!" msgstr "" -#: src/std/cell.md:49 -msgid "" -"Demonstrate that reference loops can be created by adding `root` to `subtree." -"children` (don't try to print it!)." +#: src/memory-management/review.md:56 src/testing/unit-tests.md:15 +msgid "' '" +msgstr "' '" + +#: src/memory-management/review.md:57 +msgid "\"world\"" msgstr "" -#: src/std/cell.md:50 +#: src/memory-management/review.md:58 msgid "" -"To demonstrate a runtime panic, add a `fn inc(&mut self)` that increments " -"`self.value` and calls the same method on its children. This will panic in " -"the presence of the reference loop, with `thread 'main' panicked at 'already " -"borrowed: BorrowMutError'`." +"// DON'T DO THIS AT HOME! For educational purposes only.\n" +" // String provides no guarantees about its layout, so this could lead " +"to\n" +" // undefined behavior.\n" msgstr "" -#: src/modules.md:3 -msgid "We have seen how `impl` blocks let us namespace functions to a type." +#: src/memory-management/review.md:63 +msgid "\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\"" msgstr "" -#: src/modules.md:5 -msgid "Similarly, `mod` lets us namespace types and functions:" +#: src/memory-management/approaches.md:3 +msgid "Traditionally, languages have fallen into two broad categories:" msgstr "" -#: src/modules.md:10 -msgid "\"In the foo module\"" +#: src/memory-management/approaches.md:5 +msgid "Full control via manual memory management: C, C++, Pascal, ..." msgstr "" -#: src/modules.md:16 -msgid "\"In the bar module\"" +#: src/memory-management/approaches.md:6 +msgid "Programmer decides when to allocate or free heap memory." msgstr "" -#: src/modules.md:28 +#: src/memory-management/approaches.md:7 msgid "" -"Packages provide functionality and include a `Cargo.toml` file that " -"describes how to build a bundle of 1+ crates." +"Programmer must determine whether a pointer still points to valid memory." msgstr "" -#: src/modules.md:29 -msgid "" -"Crates are a tree of modules, where a binary crate creates an executable and " -"a library crate compiles to a library." +#: src/memory-management/approaches.md:8 +msgid "Studies show, programmers make mistakes." msgstr "" -#: src/modules.md:30 -msgid "Modules define organization, scope, and are the focus of this section." +#: src/memory-management/approaches.md:9 +msgid "" +"Full safety via automatic memory management at runtime: Java, Python, Go, " +"Haskell, ..." msgstr "" -#: src/modules/visibility.md:3 -msgid "Modules are a privacy boundary:" +#: src/memory-management/approaches.md:10 +msgid "" +"A runtime system ensures that memory is not freed until it can no longer be " +"referenced." msgstr "" -#: src/modules/visibility.md:5 -msgid "Module items are private by default (hides implementation details)." +#: src/memory-management/approaches.md:11 +msgid "" +"Typically implemented with reference counting, garbage collection, or RAII." msgstr "" -#: src/modules/visibility.md:6 -msgid "Parent and sibling items are always visible." +#: src/memory-management/approaches.md:13 +msgid "Rust offers a new mix:" msgstr "" -#: src/modules/visibility.md:7 +#: src/memory-management/approaches.md:15 msgid "" -"In other words, if an item is visible in module `foo`, it's visible in all " -"the descendants of `foo`." +"Full control _and_ safety via compile time enforcement of correct memory " +"management." msgstr "" -#: src/modules/visibility.md:13 -msgid "\"outer::private\"" +#: src/memory-management/approaches.md:18 +msgid "It does this with an explicit ownership concept." msgstr "" -#: src/modules/visibility.md:17 -msgid "\"outer::public\"" +#: src/memory-management/approaches.md:23 +msgid "" +"This slide is intended to help students coming from other languages to put " +"Rust in context." msgstr "" -#: src/modules/visibility.md:22 -msgid "\"outer::inner::private\"" +#: src/memory-management/approaches.md:26 +msgid "" +"C must manage heap manually with `malloc` and `free`. Common errors include " +"forgetting to call `free`, calling it multiple times for the same pointer, " +"or dereferencing a pointer after the memory it points to has been freed." msgstr "" -#: src/modules/visibility.md:26 -msgid "\"outer::inner::public\"" +#: src/memory-management/approaches.md:31 +msgid "" +"C++ has tools like smart pointers (`unique_ptr`, `shared_ptr`) that take " +"advantage of language guarantees about calling destructors to ensure memory " +"is freed when a function returns. It is still quite easy to mis-use these " +"tools and create similar bugs to C." msgstr "" -#: src/modules/visibility.md:39 -msgid "Use the `pub` keyword to make modules public." +#: src/memory-management/approaches.md:36 +msgid "" +"Java, Go, and Python rely on the garbage collector to identify memory that " +"is no longer reachable and discard it. This guarantees that any pointer can " +"be dereferenced, eliminating use-after-free and other classes of bugs. But, " +"GC has a runtime cost and is difficult to tune properly." msgstr "" -#: src/modules/visibility.md:41 +#: src/memory-management/approaches.md:41 msgid "" -"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " -"of public visibility." +"Rust's ownership and borrowing model can, in many cases, get the performance " +"of C, with alloc and free operations precisely where they are required -- " +"zero cost. It also provides tools similar to C++'s smart pointers. When " +"required, other options such as reference counting are available, and there " +"are even third-party crates available to support runtime garbage collection " +"(not covered in this class)." msgstr "" -#: src/modules/visibility.md:43 +#: src/memory-management/ownership.md:3 msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" -"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." +"All variable bindings have a _scope_ where they are valid and it is an error " +"to use a variable outside its scope:" msgstr "" -#: src/modules/visibility.md:44 -msgid "Configuring `pub(crate)` visibility is a common pattern." +#: src/memory-management/ownership.md:19 +msgid "" +"We say that the variable _owns_ the value. Every Rust value has precisely " +"one owner at all times." msgstr "" -#: src/modules/visibility.md:45 -msgid "Less commonly, you can give visibility to a specific path." +#: src/memory-management/ownership.md:22 +msgid "" +"At the end of the scope, the variable is _dropped_ and the data is freed. A " +"destructor can run here to free up resources." msgstr "" -#: src/modules/visibility.md:46 +#: src/memory-management/ownership.md:28 msgid "" -"In any case, visibility must be granted to an ancestor module (and all of " -"its descendants)." +"Students familiar with garbage-collection implementations will know that a " +"garbage collector starts with a set of \"roots\" to find all reachable " +"memory. Rust's \"single owner\" principle is a similar idea." msgstr "" -#: src/modules/paths.md:3 -msgid "Paths are resolved as follows:" +#: src/memory-management/move.md:1 +msgid "Move Semantics" +msgstr "Overførselssemantik" + +#: src/memory-management/move.md:3 +msgid "An assignment will transfer _ownership_ between variables:" msgstr "" -#: src/modules/paths.md:5 -msgid "As a relative path:" +#: src/memory-management/move.md:7 +msgid "\"Hello!\"" msgstr "" -#: src/modules/paths.md:6 -msgid "`foo` or `self::foo` refers to `foo` in the current module," +#: src/memory-management/move.md:9 src/slices-and-lifetimes/str.md:15 +#: src/slices-and-lifetimes/str.md:17 +msgid "\"s2: {s2}\"" +msgstr "\"s2: {s2}\"" + +#: src/memory-management/move.md:10 +msgid "// println!(\"s1: {s1}\");\n" msgstr "" -#: src/modules/paths.md:7 -msgid "`super::foo` refers to `foo` in the parent module." +#: src/memory-management/move.md:14 +msgid "The assignment of `s1` to `s2` transfers ownership." msgstr "" -#: src/modules/paths.md:9 -msgid "As an absolute path:" +#: src/memory-management/move.md:15 +msgid "When `s1` goes out of scope, nothing happens: it does not own anything." msgstr "" -#: src/modules/paths.md:10 -msgid "`crate::foo` refers to `foo` in the root of the current crate," +#: src/memory-management/move.md:16 +msgid "When `s2` goes out of scope, the string data is freed." msgstr "" -#: src/modules/paths.md:11 -msgid "`bar::foo` refers to `foo` in the `bar` crate." +#: src/memory-management/move.md:18 +msgid "Before move to `s2`:" msgstr "" -#: src/modules/paths.md:13 -msgid "" -"A module can bring symbols from another module into scope with `use`. You " -"will typically see something like this at the top of each module:" +#: src/memory-management/move.md:35 +msgid "After move to `s2`:" msgstr "" -#: src/modules/filesystem.md:3 +#: src/memory-management/move.md:37 msgid "" -"Omitting the module content will tell Rust to look for it in another file:" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"(inaccessible)\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" msgstr "" +"```bob\n" +" Stak Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - -.\n" +": : : :\n" +": s1 \"(utilgængelig)\" : : :\n" +": +-----------+-------+ : : +----+----+----+----+ :\n" +": | ptr | o---+---+--+--+-->| R | u | s | t | :\n" +": | len | 4 | : | : +----+----+----+----+ :\n" +": | capacity | 4 | : | : :\n" +": +-----------+-------+ : | : :\n" +": : | `- - - - - - - - - - - - - -'\n" +": s2 : |\n" +": +-----------+-------+ : |\n" +": | ptr | o---+---+--'\n" +": | len | 4 | :\n" +": | capacity | 4 | :\n" +": +-----------+-------+ :\n" +": :\n" +"`- - - - - - - - - - - - - -'\n" +"```" -#: src/modules/filesystem.md:9 +#: src/memory-management/move.md:58 msgid "" -"This tells rust that the `garden` module content is found at `src/garden." -"rs`. Similarly, a `garden::vegetables` module can be found at `src/garden/" -"vegetables.rs`." +"When you pass a value to a function, the value is assigned to the function " +"parameter. This transfers ownership:" msgstr "" -#: src/modules/filesystem.md:12 -msgid "The `crate` root is in:" +#: src/memory-management/move.md:63 +msgid "\"Hello {name}\"" msgstr "" -#: src/modules/filesystem.md:14 -msgid "`src/lib.rs` (for a library crate)" +#: src/memory-management/move.md:67 src/android/interoperability/java.md:56 +msgid "\"Alice\"" msgstr "" -#: src/modules/filesystem.md:15 -msgid "`src/main.rs` (for a binary crate)" +#: src/memory-management/move.md:69 +msgid "// say_hello(name);\n" msgstr "" -#: src/modules/filesystem.md:17 +#: src/memory-management/move.md:76 msgid "" -"Modules defined in files can be documented, too, using \"inner doc " -"comments\". These document the item that contains them -- in this case, a " -"module." +"Mention that this is the opposite of the defaults in C++, which copies by " +"value unless you use `std::move` (and the move constructor is defined!)." msgstr "" -#: src/modules/filesystem.md:21 +#: src/memory-management/move.md:78 msgid "" -"//! This module implements the garden, including a highly performant " -"germination\n" -"//! implementation.\n" +"It is only the ownership that moves. Whether any machine code is generated " +"to manipulate the data itself is a matter of optimization, and such copies " +"are aggressively optimized away." msgstr "" -#: src/modules/filesystem.md:23 -msgid "// Re-export types from this module.\n" +#: src/memory-management/move.md:80 +msgid "" +"Simple values (such as integers) can be marked `Copy` (see later slides)." msgstr "" -#: src/modules/filesystem.md:27 -msgid "/// Sow the given seed packets.\n" +#: src/memory-management/move.md:82 +msgid "In Rust, clones are explicit (by using `clone`)." msgstr "" -#: src/modules/filesystem.md:30 -msgid "/// Harvest the produce in the garden that is ready.\n" +#: src/memory-management/move.md:84 +msgid "In the `say_hello` example:" msgstr "" -#: src/modules/filesystem.md:37 +#: src/memory-management/move.md:86 msgid "" -"Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " -"`module.rs`, and this is still a working alternative for editions after 2018." +"With the first call to `say_hello`, `main` gives up ownership of `name`. " +"Afterwards, `name` cannot be used anymore within `main`." msgstr "" -#: src/modules/filesystem.md:39 +#: src/memory-management/move.md:87 msgid "" -"The main reason to introduce `filename.rs` as alternative to `filename/mod." -"rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." -msgstr "" - -#: src/modules/filesystem.md:42 -msgid "Deeper nesting can use folders, even if the main module is a file:" +"The heap memory allocated for `name` will be freed at the end of the " +"`say_hello` function." msgstr "" -#: src/modules/filesystem.md:52 +#: src/memory-management/move.md:88 msgid "" -"The place rust will look for modules can be changed with a compiler " -"directive:" +"`main` can retain ownership if it passes `name` as a reference (`&name`) and " +"if `say_hello` accepts a reference as a parameter." msgstr "" -#: src/modules/filesystem.md:55 -msgid "\"some/path.rs\"" +#: src/memory-management/move.md:89 +msgid "" +"Alternatively, `main` can pass a clone of `name` in the first call (`name." +"clone()`)." msgstr "" -#: src/modules/filesystem.md:59 +#: src/memory-management/move.md:90 msgid "" -"This is useful, for example, if you would like to place tests for a module " -"in a file named `some_module_test.rs`, similar to the convention in Go." +"Rust makes it harder than C++ to inadvertently create copies by making move " +"semantics the default, and by forcing programmers to make clones explicit." msgstr "" -#: src/exercises/day-2/afternoon.md:1 -msgid "Day 2: Afternoon Exercises" +#: src/memory-management/move.md:94 +msgid "Defensive Copies in Modern C++" +msgstr "Defensive kopier i moderne C++" + +#: src/memory-management/move.md:96 +msgid "Modern C++ solves this differently:" msgstr "" -#: src/exercises/day-2/afternoon.md:3 -msgid "The exercises for this afternoon will focus on strings and iterators." +#: src/memory-management/move.md:99 +msgid "\"Cpp\"" +msgstr "\"Cpp\"" + +#: src/memory-management/move.md:100 +msgid "// Duplicate the data in s1.\n" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:3 +#: src/memory-management/move.md:103 msgid "" -"The ownership model of Rust affects many APIs. An example of this is the " -"[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " -"[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " -"traits." +"The heap data from `s1` is duplicated and `s2` gets its own independent copy." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:8 src/bare-metal/no_std.md:28 -msgid "`Iterator`" -msgstr "`Iterator`" - -#: src/exercises/day-2/iterators-and-ownership.md:10 -msgid "" -"Traits are like interfaces: they describe behavior (methods) for a type. The " -"`Iterator` trait simply says that you can call `next` until you get `None` " -"back:" +#: src/memory-management/move.md:104 +msgid "When `s1` and `s2` go out of scope, they each free their own memory." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:20 -msgid "You use this trait like this:" +#: src/memory-management/move.md:106 +msgid "Before copy-assignment:" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:27 -msgid "\"v[0]: {:?}\"" -msgstr "\"v[0]: {:?}\"" - -#: src/exercises/day-2/iterators-and-ownership.md:28 -msgid "\"v[1]: {:?}\"" -msgstr "\"v[1]: {:?}\"" - -#: src/exercises/day-2/iterators-and-ownership.md:29 -msgid "\"v[2]: {:?}\"" -msgstr "\"v[2]: {:?}\"" - -#: src/exercises/day-2/iterators-and-ownership.md:30 -msgid "\"No more items: {:?}\"" +#: src/memory-management/move.md:123 +msgid "After copy-assignment:" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:34 -msgid "What is the type returned by the iterator? Test your answer here:" +#: src/memory-management/move.md:149 +msgid "" +"C++ has made a slightly different choice than Rust. Because `=` copies data, " +"the string data has to be cloned. Otherwise we would get a double-free when " +"either string goes out of scope." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:42 -#: src/exercises/day-2/iterators-and-ownership.md:79 -msgid "\"v0: {v0:?}\"" -msgstr "\"v0: {v0:?}\"" - -#: src/exercises/day-2/iterators-and-ownership.md:46 -msgid "Why is this type used?" +#: src/memory-management/move.md:153 +msgid "" +"C++ also has [`std::move`](https://en.cppreference.com/w/cpp/utility/move), " +"which is used to indicate when a value may be moved from. If the example had " +"been `s2 = std::move(s1)`, no heap allocation would take place. After the " +"move, `s1` would be in a valid but unspecified state. Unlike Rust, the " +"programmer is allowed to keep using `s1`." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:48 -msgid "`IntoIterator`" -msgstr "`IntoIterator`" - -#: src/exercises/day-2/iterators-and-ownership.md:50 +#: src/memory-management/move.md:158 msgid "" -"The `Iterator` trait tells you how to _iterate_ once you have created an " -"iterator. The related trait `IntoIterator` tells you how to create the " -"iterator:" +"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " +"which is being copied or moved." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:62 +#: src/memory-management/clone.md:3 msgid "" -"The syntax here means that every implementation of `IntoIterator` must " -"declare two types:" +"Sometimes you _want_ to make a copy of a value. The `Clone` trait " +"accomplishes this." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:65 -msgid "`Item`: the type we iterate over, such as `i8`," +#: src/memory-management/clone.md:23 +msgid "" +"The idea of `Clone` is to make it easy to spot where heap allocations are " +"occurring. Look for `.clone()` and a few others like `Vec::new` or `Box::" +"new`." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:66 -msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." +#: src/memory-management/clone.md:26 +msgid "" +"It's common to \"clone your way out\" of problems with the borrow checker, " +"and return later to try to optimize those clones away." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:68 +#: src/memory-management/copy-types.md:6 msgid "" -"Note that `IntoIter` and `Item` are linked: the iterator must have the same " -"`Item` type, which means that it returns `Option`" +"While move semantics are the default, certain types are copied by default:" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:71 -msgid "Like before, what is the type returned by the iterator?" +#: src/memory-management/copy-types.md:18 +msgid "These types implement the `Copy` trait." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:75 -#: src/exercises/day-2/iterators-and-ownership.md:91 -#: src/testing/test-modules.md:21 -msgid "\"bar\"" -msgstr "\"bar\"" - -#: src/exercises/day-2/iterators-and-ownership.md:83 -msgid "`for` Loops" -msgstr "`for`\\-løkker" - -#: src/exercises/day-2/iterators-and-ownership.md:85 -msgid "" -"Now that we know both `Iterator` and `IntoIterator`, we can build `for` " -"loops. They call `into_iter()` on an expression and iterates over the " -"resulting iterator:" +#: src/memory-management/copy-types.md:20 +msgid "You can opt-in your own types to use copy semantics:" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:94 -#: src/exercises/day-2/iterators-and-ownership.md:98 -msgid "\"word: {word}\"" -msgstr "\"word: {word}\"" - -#: src/exercises/day-2/iterators-and-ownership.md:103 -msgid "What is the type of `word` in each loop?" +#: src/memory-management/copy-types.md:35 +msgid "After the assignment, both `p1` and `p2` own their own data." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:105 -msgid "" -"Experiment with the code above and then consult the documentation for [`impl " -"IntoIterator for &Vec`](https://doc.rust-lang.org/std/vec/struct.Vec." -"html#impl-IntoIterator-for-%26'a+Vec%3CT,+A%3E) and [`impl IntoIterator for " -"Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-" -"for-Vec%3CT,+A%3E) to check your answers." +#: src/memory-management/copy-types.md:36 +msgid "We can also use `p1.clone()` to explicitly copy the data." msgstr "" -#: src/exercises/day-2/strings-iterators.md:3 -msgid "" -"In this exercise, you are implementing a routing component of a web server. " -"The server is configured with a number of _path prefixes_ which are matched " -"against _request paths_. The path prefixes can contain a wildcard character " -"which matches a full segment. See the unit tests below." +#: src/memory-management/copy-types.md:41 +msgid "Copying and cloning are not the same thing:" msgstr "" -#: src/exercises/day-2/strings-iterators.md:8 +#: src/memory-management/copy-types.md:43 msgid "" -"Copy the following code to and make the tests " -"pass. Try avoiding allocating a `Vec` for your intermediate results:" -msgstr "" - -#: src/exercises/day-2/strings-iterators.md:22 -#: src/exercises/day-2/strings-iterators.md:23 -#: src/exercises/day-2/strings-iterators.md:24 -#: src/exercises/day-2/strings-iterators.md:26 -#: src/exercises/day-2/strings-iterators.md:27 -#: src/exercises/day-2/strings-iterators.md:28 -#: src/exercises/day-2/strings-iterators.md:46 -#: src/exercises/day-2/solutions-afternoon.md:32 -#: src/exercises/day-2/solutions-afternoon.md:33 -#: src/exercises/day-2/solutions-afternoon.md:34 -#: src/exercises/day-2/solutions-afternoon.md:36 -#: src/exercises/day-2/solutions-afternoon.md:37 -#: src/exercises/day-2/solutions-afternoon.md:38 -#: src/exercises/day-2/solutions-afternoon.md:56 -msgid "\"/v1/publishers\"" -msgstr "\"/v1/publishers\"" - -#: src/exercises/day-2/strings-iterators.md:23 -#: src/exercises/day-2/solutions-afternoon.md:33 -msgid "\"/v1/publishers/abc-123\"" -msgstr "\"/v1/publishers/abc-123\"" - -#: src/exercises/day-2/strings-iterators.md:24 -#: src/exercises/day-2/solutions-afternoon.md:34 -msgid "\"/v1/publishers/abc/books\"" -msgstr "\"/v1/publishers/abc/books\"" - -#: src/exercises/day-2/strings-iterators.md:26 -#: src/exercises/day-2/solutions-afternoon.md:36 -msgid "\"/v1\"" -msgstr "\"/v1\"" - -#: src/exercises/day-2/strings-iterators.md:27 -#: src/exercises/day-2/solutions-afternoon.md:37 -msgid "\"/v1/publishersBooks\"" -msgstr "\"/v1/publishersBooks\"" - -#: src/exercises/day-2/strings-iterators.md:28 -#: src/exercises/day-2/solutions-afternoon.md:38 -msgid "\"/v1/parent/publishers\"" -msgstr "\"/v1/parent/publishers\"" - -#: src/exercises/day-2/strings-iterators.md:34 -#: src/exercises/day-2/strings-iterators.md:38 -#: src/exercises/day-2/strings-iterators.md:42 -#: src/exercises/day-2/strings-iterators.md:46 -#: src/exercises/day-2/strings-iterators.md:48 -#: src/exercises/day-2/solutions-afternoon.md:44 -#: src/exercises/day-2/solutions-afternoon.md:48 -#: src/exercises/day-2/solutions-afternoon.md:52 -#: src/exercises/day-2/solutions-afternoon.md:56 -#: src/exercises/day-2/solutions-afternoon.md:58 -msgid "\"/v1/publishers/*/books\"" -msgstr "\"/v1/publishers/*/books\"" - -#: src/exercises/day-2/strings-iterators.md:35 -#: src/exercises/day-2/solutions-afternoon.md:45 -msgid "\"/v1/publishers/foo/books\"" -msgstr "\"/v1/publishers/foo/books\"" - -#: src/exercises/day-2/strings-iterators.md:39 -#: src/exercises/day-2/solutions-afternoon.md:49 -msgid "\"/v1/publishers/bar/books\"" -msgstr "\"/v1/publishers/bar/books\"" - -#: src/exercises/day-2/strings-iterators.md:43 -#: src/exercises/day-2/solutions-afternoon.md:53 -msgid "\"/v1/publishers/foo/books/book1\"" -msgstr "\"/v1/publishers/foo/books/book1\"" - -#: src/exercises/day-2/strings-iterators.md:49 -#: src/exercises/day-2/solutions-afternoon.md:59 -msgid "\"/v1/publishers/foo/booksByAuthor\"" -msgstr "\"/v1/publishers/foo/booksByAuthor\"" - -#: src/welcome-day-3.md:1 -msgid "Welcome to Day 3" -msgstr "Velkommen til Dag 3" - -#: src/welcome-day-3.md:3 -msgid "Today, we will cover some more advanced topics of Rust:" +"Copying refers to bitwise copies of memory regions and does not work on " +"arbitrary objects." msgstr "" -#: src/welcome-day-3.md:5 +#: src/memory-management/copy-types.md:44 msgid "" -"Traits: deriving traits, default methods, and important standard library " -"traits." +"Copying does not allow for custom logic (unlike copy constructors in C++)." msgstr "" -#: src/welcome-day-3.md:8 +#: src/memory-management/copy-types.md:45 msgid "" -"Generics: generic data types, generic methods, monomorphization, and trait " -"objects." +"Cloning is a more general operation and also allows for custom behavior by " +"implementing the `Clone` trait." msgstr "" -#: src/welcome-day-3.md:11 -msgid "Error handling: panics, `Result`, and the try operator `?`." +#: src/memory-management/copy-types.md:46 +msgid "Copying does not work on types that implement the `Drop` trait." msgstr "" -#: src/welcome-day-3.md:13 -msgid "Testing: unit tests, documentation tests, and integration tests." +#: src/memory-management/copy-types.md:48 +msgid "In the above example, try the following:" msgstr "" -#: src/welcome-day-3.md:15 +#: src/memory-management/copy-types.md:50 msgid "" -"Unsafe Rust: raw pointers, static variables, unsafe functions, and extern " -"functions." +"Add a `String` field to `struct Point`. It will not compile because `String` " +"is not a `Copy` type." msgstr "" -#: src/generics.md:3 +#: src/memory-management/copy-types.md:51 msgid "" -"Rust support generics, which lets you abstract algorithms or data structures " -"(such as sorting or a binary tree) over the types used or stored." +"Remove `Copy` from the `derive` attribute. The compiler error is now in the " +"`println!` for `p1`." msgstr "" -#: src/generics/data-types.md:3 -msgid "You can use generics to abstract over the concrete field type:" +#: src/memory-management/copy-types.md:52 +msgid "Show that it works if you clone `p1` instead." msgstr "" -#: src/generics/data-types.md:15 -msgid "\"{integer:?} and {float:?}\"" -msgstr "\"{integer:?} og {float:?}\"" - -#: src/generics/data-types.md:21 -msgid "Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`." +#: src/memory-management/drop.md:1 +msgid "The `Drop` Trait" msgstr "" -#: src/generics/data-types.md:23 -msgid "Fix the code to allow points that have elements of different types." +#: src/memory-management/drop.md:3 +msgid "" +"Values which implement [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop." +"html) can specify code to run when they go out of scope:" msgstr "" -#: src/generics/methods.md:3 -msgid "You can declare a generic type on your `impl` block:" -msgstr "" +#: src/memory-management/drop.md:12 +msgid "\"Dropping {}\"" +msgstr "\"Dropper {}\"" -#: src/generics/methods.md:11 -msgid "// + 10\n" -msgstr "// + 10\n" +#: src/memory-management/drop.md:17 +#: src/exercises/concurrency/link-checker.md:92 +#: src/exercises/concurrency/solutions-morning.md:123 +msgid "\"a\"" +msgstr "\"a\"" -#: src/generics/methods.md:14 -msgid "// fn set_x(&mut self, x: T)\n" -msgstr "// fn set_x(&mut self, x: T)\n" +#: src/memory-management/drop.md:19 src/testing/googletest.md:12 +msgid "\"b\"" +msgstr "\"b\"" -#: src/generics/methods.md:19 -msgid "\"p.x = {}\"" -msgstr "\"p.x = {}\"" +#: src/memory-management/drop.md:21 +msgid "\"c\"" +msgstr "\"c\"" -#: src/generics/methods.md:25 -msgid "" -"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " -"redundant?" -msgstr "" +#: src/memory-management/drop.md:22 +msgid "\"d\"" +msgstr "\"d\"" -#: src/generics/methods.md:26 -msgid "" -"This is because it is a generic implementation section for generic type. " -"They are independently generic." +#: src/memory-management/drop.md:23 +msgid "\"Exiting block B\"" msgstr "" -#: src/generics/methods.md:27 -msgid "It means these methods are defined for any `T`." +#: src/memory-management/drop.md:25 +msgid "\"Exiting block A\"" msgstr "" -#: src/generics/methods.md:28 -msgid "It is possible to write `impl Point { .. }`. " +#: src/memory-management/drop.md:28 +msgid "\"Exiting main\"" msgstr "" -#: src/generics/methods.md:29 -msgid "" -"`Point` is still generic and you can use `Point`, but methods in this " -"block will only be available for `Point`." +#: src/memory-management/drop.md:35 +msgid "Note that `std::mem::drop` is not the same as `std::ops::Drop::drop`." msgstr "" -#: src/generics/monomorphization.md:3 -msgid "Generic code is turned into non-generic code based on the call sites:" +#: src/memory-management/drop.md:36 +msgid "Values are automatically dropped when they go out of scope." msgstr "" -#: src/generics/monomorphization.md:12 -msgid "behaves as if you wrote" +#: src/memory-management/drop.md:37 +msgid "" +"When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" +"drop` implementation will be called." msgstr "" -#: src/generics/monomorphization.md:31 +#: src/memory-management/drop.md:39 msgid "" -"This is a zero-cost abstraction: you get exactly the same result as if you " -"had hand-coded the data structures without the abstraction." +"All its fields will then be dropped too, whether or not it implements `Drop`." msgstr "" -#: src/traits.md:3 +#: src/memory-management/drop.md:40 msgid "" -"Rust lets you abstract over types with traits. They're similar to interfaces:" +"`std::mem::drop` is just an empty function that takes any value. The " +"significance is that it takes ownership of the value, so at the end of its " +"scope it gets dropped. This makes it a convenient way to explicitly drop " +"values earlier than they would otherwise go out of scope." msgstr "" -#: src/traits.md:24 src/traits/trait-objects.md:24 -msgid "\"The cat\"" +#: src/memory-management/drop.md:43 +msgid "" +"This can be useful for objects that do some work on `drop`: releasing locks, " +"closing files, etc." msgstr "" -#: src/traits.md:24 src/traits/trait-objects.md:24 -msgid "// No name, cats won't respond to it anyway.\n" +#: src/memory-management/drop.md:48 +msgid "Why doesn't `Drop::drop` take `self`?" msgstr "" -#: src/traits.md:29 -msgid "\"Who's a cutie? {} is!\"" +#: src/memory-management/drop.md:49 +msgid "" +"Short-answer: If it did, `std::mem::drop` would be called at the end of the " +"block, resulting in another call to `Drop::drop`, and a stack overflow!" msgstr "" -#: src/traits.md:33 src/traits/trait-objects.md:31 -msgid "\"Fido\"" -msgstr "\"Fido\"" +#: src/memory-management/drop.md:52 +msgid "Try replacing `drop(a)` with `a.drop()`." +msgstr "" -#: src/traits/trait-objects.md:3 +#: src/memory-management/exercise.md:3 msgid "" -"Trait objects allow for values of different types, for instance in a " -"collection:" +"In this example, we will implement a complex data type that owns all of its " +"data. We will use the \"builder pattern\" to support building a new value " +"piece-by-piece, using convenience functions." msgstr "" -#: src/traits/trait-objects.md:34 -msgid "\"Hello {}!\"" -msgstr "\"Hallo {}!\"" +#: src/memory-management/exercise.md:7 +msgid "Fill in the missing pieces." +msgstr "" -#: src/traits/trait-objects.md:40 -msgid "Memory layout after allocating `pets`:" +#: src/memory-management/exercise.md:22 src/memory-management/solution.md:16 +msgid "/// A representation of a software package.\n" msgstr "" -#: src/traits/trait-objects.md:42 +#: src/memory-management/exercise.md:35 +#, fuzzy +msgid "\"1\"" +msgstr "\"\"" + +#: src/memory-management/exercise.md:38 src/memory-management/solution.md:35 msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"pets : : :\n" -": +-----------+-------+ : : +-----+-----" -"+ :\n" -": | ptr | o---+---+-----+-->| o o | o o " -"| :\n" -": | len | 2 | : : +-|-|-+-|-|-" -"+ :\n" -": | capacity | 2 | : : | | | | +---------------" -"+ :\n" -": +-----------+-------+ : : | | | '-->| name: \"Fido\" " -"| :\n" -": : : | | | +---------------" -"+ :\n" -"`- - - - - - - - - - - - - -' : | | " -"| :\n" -" : | | | +----------------------" -"+ : \n" -" : | | '---->| \"::name\" " -"| :\n" -" : | | +----------------------" -"+ : \n" -" : | " -"| : \n" -" : | | +-" -"+ : \n" -" : | '-->|" -"\\| : \n" -" : | +-" -"+ : \n" -" : " -"| : \n" -" : | +----------------------" -"+ : \n" -" : '---->| \"::name\" " -"| : \n" -" : +----------------------" -"+ :\n" -" : :\n" -" '- - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"\n" -"```" +"/// A builder for a Package. Use `build()` to create the `Package` itself.\n" msgstr "" -"```bob\n" -" Stak Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"pets : : :\n" -": +-----------+-------+ : : +-----+-----" -"+ :\n" -": | ptr | o---+---+-----+-->| o o | o o " -"| :\n" -": | len | 2 | : : +-|-|-+-|-|-" -"+ :\n" -": | capacity | 2 | : : | | | | +---------------" -"+ :\n" -": +-----------+-------+ : : | | | '-->| name: \"Fido\" " -"| :\n" -": : : | | | +---------------" -"+ :\n" -"`- - - - - - - - - - - - - -' : | | " -"| :\n" -" : | | | +----------------------" -"+ :\n" -" : | | '---->| \"::name\" " -"| :\n" -" : | | +----------------------" -"+ :\n" -" : | " -"| :\n" -" : | | +-" -"+ :\n" -" : | '-->|" -"\\| :\n" -" : | +-" -"+ :\n" -" : " -"| :\n" -" : | +----------------------" -"+ :\n" -" : '---->| \"::name\" " -"| :\n" -" : +----------------------" -"+ :\n" -" : :\n" -" '- - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"\n" -"```" -#: src/traits/trait-objects.md:72 -msgid "" -"Types that implement a given trait may be of different sizes. This makes it " -"impossible to have things like `Vec` in the example above." +#: src/memory-management/exercise.md:44 +#, fuzzy +msgid "\"2\"" +msgstr "\"\"" + +#: src/memory-management/exercise.md:47 src/memory-management/solution.md:50 +msgid "/// Set the package version.\n" msgstr "" -#: src/traits/trait-objects.md:73 -msgid "" -"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " -"implements `Pet`." +#: src/memory-management/exercise.md:53 src/memory-management/solution.md:56 +msgid "/// Set the package authors.\n" msgstr "" -#: src/traits/trait-objects.md:74 -msgid "" -"In the example, `pets` holds _fat pointers_ to objects that implement `Pet`. " -"The fat pointer consists of two components, a pointer to the actual object " -"and a pointer to the virtual method table for the `Pet` implementation of " -"that particular object." +#: src/memory-management/exercise.md:55 +#, fuzzy +msgid "\"3\"" +msgstr "\"\"" + +#: src/memory-management/exercise.md:58 src/memory-management/solution.md:62 +msgid "/// Add an additional dependency.\n" msgstr "" -#: src/traits/trait-objects.md:75 -msgid "Compare these outputs in the above example:" +#: src/memory-management/exercise.md:60 +#, fuzzy +msgid "\"4\"" +msgstr "\"\"" + +#: src/memory-management/exercise.md:63 src/memory-management/solution.md:68 +msgid "/// Set the language. If not set, language defaults to None.\n" msgstr "" -#: src/traits/trait-objects.md:77 src/traits/trait-objects.md:78 -#: src/traits/closures.md:54 -msgid "\"{} {}\"" -msgstr "\"{} {}\"" +#: src/memory-management/exercise.md:65 +#, fuzzy +msgid "\"5\"" +msgstr "\"\"" -#: src/traits/trait-objects.md:79 src/traits/trait-objects.md:80 -#: src/testing/test-modules.md:12 src/android/build-rules/library.md:44 -#: src/async/pitfalls/cancellation.md:59 -#: src/exercises/day-3/solutions-morning.md:130 -msgid "\"{}\"" -msgstr "\"{}\"" +#: src/memory-management/exercise.md:74 src/memory-management/exercise.md:76 +#: src/memory-management/solution.md:80 src/memory-management/solution.md:82 +msgid "\"base64\"" +msgstr "" -#: src/traits/deriving-traits.md:3 -msgid "" -"Rust derive macros work by automatically generating code that implements the " -"specified traits for a data structure." +#: src/memory-management/exercise.md:74 src/memory-management/solution.md:80 +msgid "\"0.13\"" msgstr "" -#: src/traits/deriving-traits.md:5 -msgid "You can let the compiler derive a number of traits as follows:" +#: src/memory-management/exercise.md:75 src/memory-management/solution.md:81 +msgid "\"base64: {base64:?}\"" msgstr "" -#: src/traits/deriving-traits.md:18 -msgid "\"Is {:?}\\nequal to {:?}?\\nThe answer is {}!\"" +#: src/memory-management/exercise.md:77 src/memory-management/solution.md:83 +msgid "\"0.4\"" msgstr "" -#: src/traits/deriving-traits.md:19 -#: src/exercises/day-1/solutions-afternoon.md:37 -msgid "\"yes\"" -msgstr "\"ja\"" +#: src/memory-management/exercise.md:80 src/memory-management/solution.md:86 +#, fuzzy +msgid "\"log: {log:?}\"" +msgstr "\"{dog:?}\"" -#: src/traits/deriving-traits.md:19 -#: src/exercises/day-1/solutions-afternoon.md:37 -msgid "\"no\"" -msgstr "\"nej\"" +#: src/memory-management/exercise.md:81 src/memory-management/solution.md:87 +msgid "\"hawk\"" +msgstr "" -#: src/traits/default-methods.md:3 -msgid "Traits can implement behavior in terms of other trait methods:" +#: src/memory-management/exercise.md:82 src/memory-management/solution.md:88 +msgid "\"djmitche\"" msgstr "" -#: src/traits/default-methods.md:25 -msgid "\"{a:?} equals {b:?}: {}\"" -msgstr "\"{a:?} er lig {b:?}: {}\"" +#: src/memory-management/exercise.md:83 src/memory-management/solution.md:89 +msgid "\"4.0\"" +msgstr "" -#: src/traits/default-methods.md:26 -msgid "\"{a:?} not_equals {b:?}: {}\"" -msgstr "\"{a:?} er ikke lig {b:?}: {}\"" +#: src/memory-management/exercise.md:87 src/memory-management/solution.md:93 +#, fuzzy +msgid "\"serde: {serde:?}\"" +msgstr "\"expr: {:?}\"" -#: src/traits/default-methods.md:32 -msgid "" -"Traits may specify pre-implemented (default) methods and methods that users " -"are required to implement themselves. Methods with default implementations " -"can rely on required methods." +#: src/memory-management/solution.md:43 +msgid "\"0.1\"" msgstr "" -#: src/traits/default-methods.md:35 -msgid "Move method `not_equals` to a new trait `NotEquals`." +#: src/smart-pointers.md:4 +msgid "[Box](./smart-pointers/box.md) (10 minutes)" msgstr "" -#: src/traits/default-methods.md:37 -msgid "Make `Equals` a super trait for `NotEquals`." +#: src/smart-pointers.md:5 +msgid "[Rc](./smart-pointers/rc.md) (5 minutes)" msgstr "" -#: src/traits/default-methods.md:46 -msgid "Provide a blanket implementation of `NotEquals` for `Equals`." +#: src/smart-pointers.md:6 +msgid "[Exercise: Binary Tree](./smart-pointers/exercise.md) (30 minutes)" msgstr "" -#: src/traits/default-methods.md:58 -msgid "" -"With the blanket implementation, you no longer need `Equals` as a super " -"trait for `NotEqual`." -msgstr "" +#: src/smart-pointers/box.md:1 +#: src/android/interoperability/cpp/type-mapping.md:9 +#, fuzzy +msgid "`Box`" +msgstr "`Box`" -#: src/traits/trait-bounds.md:3 +#: src/smart-pointers/box.md:3 msgid "" -"When working with generics, you often want to require the types to implement " -"some trait, so that you can call this trait's methods." +"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " +"pointer to data on the heap:" msgstr "" -#: src/traits/trait-bounds.md:6 -msgid "You can do this with `T: Trait` or `impl Trait`:" -msgstr "" +#: src/smart-pointers/box.md:8 +msgid "\"five: {}\"" +msgstr "\"five: {}\"" -#: src/traits/trait-bounds.md:12 +#: src/smart-pointers/box.md:26 msgid "" -"// Syntactic sugar for:\n" -"// fn add_42_millions>(x: T) -> i32 {\n" +"`Box` implements `Deref`, which means that you can [call " +"methods from `T` directly on a `Box`](https://doc.rust-lang.org/std/ops/" +"trait.Deref.html#more-on-deref-coercion)." msgstr "" -#: src/traits/trait-bounds.md:18 -msgid "// struct NotClonable;\n" -msgstr "// struct NotClonable;\n" - -#: src/traits/trait-bounds.md:24 -msgid "\"{pair:?}\"" -msgstr "\"{pair:?}\"" - -#: src/traits/trait-bounds.md:27 -msgid "\"{many}\"" -msgstr "\"{many}\"" - -#: src/traits/trait-bounds.md:29 -msgid "\"{many_more}\"" -msgstr "\"{many_more}\"" - -#: src/traits/trait-bounds.md:35 -msgid "Show a `where` clause, students will encounter it when reading code." +#: src/smart-pointers/box.md:29 +msgid "" +"Recursive data types or data types with dynamic sizes need to use a `Box`:" msgstr "" -#: src/traits/trait-bounds.md:46 -msgid "It declutters the function signature if you have many parameters." -msgstr "" +#: src/smart-pointers/box.md:40 src/smart-pointers/box.md:86 +msgid "\"{list:?}\"" +msgstr "\"{list:?}\"" -#: src/traits/trait-bounds.md:47 -msgid "It has additional features making it more powerful." +#: src/smart-pointers/box.md:44 +msgid "" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": " +"list : : :\n" +": +------+----+----+ : : +------+----+----+ +------+----+----" +"+ :\n" +": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " +"| :\n" +": +------+----+----+ : : +------+----+----+ +------+----+----" +"+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " +"- -'\n" +"```" msgstr "" +"```bob\n" +" Stak Heap\n" +".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": " +"list : : :\n" +": +------+----+----+ : : +------+----+----+ +------+----+----" +"+ :\n" +": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " +"| :\n" +": +------+----+----+ : : +------+----+----+ +------+----+----" +"+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " +"- -'\n" +"```" -#: src/traits/trait-bounds.md:48 +#: src/smart-pointers/box.md:59 msgid "" -"If someone asks, the extra feature is that the type on the left of \":\" can " -"be arbitrary, like `Option`." +"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " +"not null." msgstr "" -#: src/traits/impl-trait.md:1 -msgid "`impl Trait`" -msgstr "`impl Trait`" - -#: src/traits/impl-trait.md:3 +#: src/smart-pointers/box.md:60 msgid "" -"Similar to trait bounds, an `impl Trait` syntax can be used in function " -"arguments and return values:" +"In the above example, you can even leave out the `*` in the `println!` " +"statement thanks to `Deref`." msgstr "" -#: src/traits/impl-trait.md:19 -msgid "`impl Trait` allows you to work with types which you cannot name." +#: src/smart-pointers/box.md:61 +msgid "A `Box` can be useful when you:" msgstr "" -#: src/traits/impl-trait.md:23 +#: src/smart-pointers/box.md:62 msgid "" -"The meaning of `impl Trait` is a bit different in the different positions." +"have a type whose size that can't be known at compile time, but the Rust " +"compiler wants to know an exact size." msgstr "" -#: src/traits/impl-trait.md:25 +#: src/smart-pointers/box.md:63 msgid "" -"For a parameter, `impl Trait` is like an anonymous generic parameter with a " -"trait bound." +"want to transfer ownership of a large amount of data. To avoid copying large " +"amounts of data on the stack, instead store the data on the heap in a `Box` " +"so only the pointer is moved." msgstr "" -#: src/traits/impl-trait.md:27 +#: src/smart-pointers/box.md:65 msgid "" -"For a return type, it means that the return type is some concrete type that " -"implements the trait, without naming the type. This can be useful when you " -"don't want to expose the concrete type in a public API." +"If `Box` was not used and we attempted to embed a `List` directly into the " +"`List`, the compiler would not compute a fixed size of the struct in memory " +"(`List` would be of infinite size)." msgstr "" -#: src/traits/impl-trait.md:31 +#: src/smart-pointers/box.md:68 msgid "" -"Inference is hard in return position. A function returning `impl Foo` picks " -"the concrete type it returns, without writing it out in the source. A " -"function returning a generic type like `collect() -> B` can return any " -"type satisfying `B`, and the caller may need to choose one, such as with " -"`let x: Vec<_> = foo.collect()` or with the turbofish, `foo.collect::" -">()`." +"`Box` solves this problem as it has the same size as a regular pointer and " +"just points at the next element of the `List` in the heap." msgstr "" -#: src/traits/impl-trait.md:37 +#: src/smart-pointers/box.md:71 msgid "" -"This example is great, because it uses `impl Display` twice. It helps to " -"explain that nothing here enforces that it is _the same_ `impl Display` " -"type. If we used a single `T: Display`, it would enforce the constraint " -"that input `T` and return `T` type are the same type. It would not work for " -"this particular function, as the type we expect as input is likely not what " -"`format!` returns. If we wanted to do the same via `: Display` syntax, we'd " -"need two independent generic parameters." +"Remove the `Box` in the List definition and show the compiler error. " +"\"Recursive with indirection\" is a hint you might want to use a Box or " +"reference of some kind, instead of storing a value directly." msgstr "" -#: src/traits/important-traits.md:3 -msgid "" -"We will now look at some of the most common traits of the Rust standard " -"library:" +#: src/smart-pointers/box.md:75 +msgid "Niche Optimization" msgstr "" -#: src/traits/important-traits.md:5 +#: src/smart-pointers/box.md:90 msgid "" -"[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " -"[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " -"used in `for` loops," +"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This " +"allows the compiler to optimize the memory layout:" msgstr "" -#: src/traits/important-traits.md:6 +#: src/smart-pointers/box.md:93 msgid "" -"[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) and [`Into`]" -"(https://doc.rust-lang.org/std/convert/trait.Into.html) used to convert " -"values," +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": " +"list : : :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " +"| :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": : : :\n" +": : : :\n" +"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" msgstr "" +"```bob\n" +" Stak Heap\n" +".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": " +"list : : :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " +"| :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": : : :\n" +": : : :\n" +"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" -#: src/traits/important-traits.md:7 +#: src/smart-pointers/rc.md:1 +msgid "`Rc`" +msgstr "`Rc`" + +#: src/smart-pointers/rc.md:3 msgid "" -"[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and [`Write`]" -"(https://doc.rust-lang.org/std/io/trait.Write.html) used for IO," +"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) is a reference-" +"counted shared pointer. Use this when you need to refer to the same data " +"from multiple places:" msgstr "" -#: src/traits/important-traits.md:8 +#: src/smart-pointers/rc.md:13 +msgid "\"a: {a}\"" +msgstr "\"a: {a}\"" + +#: src/smart-pointers/rc.md:14 +msgid "\"b: {b}\"" +msgstr "\"b: {b}\"" + +#: src/smart-pointers/rc.md:18 msgid "" -"[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html), [`Mul`](https://" -"doc.rust-lang.org/std/ops/trait.Mul.html), ... used for operator " -"overloading, and" +"See [`Arc`](../concurrency/shared_state/arc.md) and [`Mutex`](https://doc." +"rust-lang.org/std/sync/struct.Mutex.html) if you are in a multi-threaded " +"context." msgstr "" -#: src/traits/important-traits.md:9 +#: src/smart-pointers/rc.md:19 msgid "" -"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) used for " -"defining destructors." +"You can _downgrade_ a shared pointer into a [`Weak`](https://doc.rust-lang." +"org/std/rc/struct.Weak.html) pointer to create cycles that will get dropped." msgstr "" -#: src/traits/important-traits.md:10 +#: src/smart-pointers/rc.md:30 msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) used " -"to construct a default instance of a type." +"`Rc`'s count ensures that its contained value is valid for as long as there " +"are references." msgstr "" -#: src/traits/iterator.md:1 -msgid "Iterators" -msgstr "Iteratorer" +#: src/smart-pointers/rc.md:31 +msgid "`Rc` in Rust is like `std::shared_ptr` in C++." +msgstr "" -#: src/traits/iterator.md:3 +#: src/smart-pointers/rc.md:32 msgid "" -"You can implement the [`Iterator`](https://doc.rust-lang.org/std/iter/trait." -"Iterator.html) trait on your own types:" +"`Rc::clone` is cheap: it creates a pointer to the same allocation and " +"increases the reference count. Does not make a deep clone and can generally " +"be ignored when looking for performance issues in code." msgstr "" -#: src/traits/iterator.md:25 -msgid "\"fib({i}): {n}\"" -msgstr "\"fib({i}): {n}\"" - -#: src/traits/iterator.md:32 +#: src/smart-pointers/rc.md:33 msgid "" -"The `Iterator` trait implements many common functional programming " -"operations over collections (e.g. `map`, `filter`, `reduce`, etc). This is " -"the trait where you can find all the documentation about them. In Rust these " -"functions should produce the code as efficient as equivalent imperative " -"implementations." +"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " +"and returns a mutable reference." msgstr "" -#: src/traits/iterator.md:37 -msgid "" -"`IntoIterator` is the trait that makes for loops work. It is implemented by " -"collection types such as `Vec` and references to them such as `&Vec` " -"and `&[T]`. Ranges also implement it. This is why you can iterate over a " -"vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." +#: src/smart-pointers/rc.md:34 +msgid "Use `Rc::strong_count` to check the reference count." msgstr "" -#: src/traits/from-iterator.md:3 +#: src/smart-pointers/rc.md:35 msgid "" -"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " -"lets you build a collection from an [`Iterator`](https://doc.rust-lang.org/" -"std/iter/trait.Iterator.html)." +"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " +"cycles that will be dropped properly (likely in combination with `RefCell`, " +"on the next slide)." msgstr "" -#: src/traits/from-iterator.md:17 +#: src/smart-pointers/exercise.md:3 msgid "" -"`Iterator` implements `fn collect(self) -> B where B: FromIterator, Self: Sized`" +"A binary tree is a tree-type data structure where every node has two " +"children (left and right). We will create a tree where each node stores a " +"value. For a given node N, all nodes in a N's left subtree contain smaller " +"values, and all nodes in N's right subtree will contain larger values." +msgstr "" + +#: src/smart-pointers/exercise.md:8 +msgid "Implement the following types, so that the given tests pass." msgstr "" -#: src/traits/from-iterator.md:23 +#: src/smart-pointers/exercise.md:17 src/smart-pointers/solution.md:10 msgid "" -"There are also implementations which let you do cool things like convert an " -"`Iterator>` into a `Result, E>`." +"/// A container storing a set of values, using a binary tree.\n" +"///\n" +"/// If the same value is added multiple times, it is only stored once.\n" msgstr "" -#: src/traits/from-into.md:1 -msgid "`From` and `Into`" -msgstr "`From` og `Into`" +#: src/smart-pointers/exercise.md:23 +msgid "// Implement `new`, `insert`, and `has`.\n" +msgstr "" + +#: src/smart-pointers/exercise.md:38 src/smart-pointers/solution.md:84 +msgid "// not a unique item\n" +msgstr "" -#: src/traits/from-into.md:3 +#: src/smart-pointers/exercise.md:73 msgid "" -"Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." -"html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " -"facilitate type conversions:" +"Extra Credit: implement an iterator over a binary tree that returns the " +"values in order." msgstr "" -#: src/traits/from-into.md:11 src/traits/from-into.md:23 -msgid "\"{s}, {addr}, {one}, {bigger}\"" -msgstr "\"{s}, {addr}, {one}, {bigger}\"" +#: src/smart-pointers/solution.md:68 src/testing/googletest.md:11 +msgid "\"bar\"" +msgstr "\"bar\"" -#: src/traits/from-into.md:15 -msgid "" -"[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) is " -"automatically implemented when [`From`](https://doc.rust-lang.org/std/" -"convert/trait.From.html) is implemented:" +#: src/welcome-day-3-afternoon.md:4 +msgid "[Borrowing](./borrowing.md) (1 hour)" msgstr "" -#: src/traits/from-into.md:29 +#: src/welcome-day-3-afternoon.md:5 msgid "" -"That's why it is common to only implement `From`, as your type will get " -"`Into` implementation too." +"[Slices and Lifetimes](./slices-and-lifetimes.md) (1 hour and 10 minutes)" msgstr "" -#: src/traits/from-into.md:30 +#: src/welcome-day-3-afternoon.md:7 msgid "" -"When declaring a function argument input type like \"anything that can be " -"converted into a `String`\", the rule is opposite, you should use `Into`. " -"Your function will accept types that implement `From` and those that _only_ " -"implement `Into`." +"Including 10 minute breaks, this session should take about 2 hours and 20 " +"minutes" msgstr "" -#: src/traits/read-write.md:1 -msgid "`Read` and `Write`" -msgstr "`Read` og `Write`" - -#: src/traits/read-write.md:3 -msgid "" -"Using [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and " -"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html), you can " -"abstract over `u8` sources:" +#: src/borrowing.md:4 +msgid "[Borrowing a Value](./borrowing/shared.md) (10 minutes)" msgstr "" -#: src/traits/read-write.md:14 -msgid "b\"foo\\nbar\\nbaz\\n\"" -msgstr "b\"foo\\nbar\\nbaz\\n\"" +#: src/borrowing.md:5 +msgid "[Borrow Checking](./borrowing/borrowck.md) (10 minutes)" +msgstr "" -#: src/traits/read-write.md:15 -msgid "\"lines in slice: {}\"" -msgstr "\"linjer i slice: {}\"" +#: src/borrowing.md:6 +msgid "[Interior Mutability](./borrowing/interior-mutability.md) (10 minutes)" +msgstr "" -#: src/traits/read-write.md:18 -msgid "\"lines in file: {}\"" -msgstr "\"linjer i file: {}\"" +#: src/borrowing.md:7 +msgid "[Exercise: Health Statistics](./borrowing/exercise.md) (30 minutes)" +msgstr "" -#: src/traits/read-write.md:23 +#: src/borrowing/shared.md:3 msgid "" -"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " -"you abstract over `u8` sinks:" +"As we saw before, instead of transferring ownership when calling a function, " +"you can let a function _borrow_ the value:" msgstr "" -#: src/traits/read-write.md:30 -msgid "\"\\n\"" -msgstr "\"\\n\"" - -#: src/traits/read-write.md:37 -msgid "\"Logged: {:?}\"" +#: src/borrowing/shared.md:23 +msgid "The `add` function _borrows_ two points and returns a new point." msgstr "" -#: src/traits/drop.md:1 -msgid "The `Drop` Trait" +#: src/borrowing/shared.md:24 +msgid "The caller retains ownership of the inputs." msgstr "" -#: src/traits/drop.md:3 +#: src/borrowing/shared.md:29 msgid "" -"Values which implement [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop." -"html) can specify code to run when they go out of scope:" +"This slide is a review of the material on references from day 1, expanding " +"slightly to include function arguments and return values." msgstr "" -#: src/traits/drop.md:12 -msgid "\"Dropping {}\"" -msgstr "\"Dropper {}\"" - -#: src/traits/drop.md:17 src/exercises/concurrency/link-checker.md:92 -#: src/exercises/day-1/solutions-morning.md:86 -#: src/exercises/concurrency/solutions-morning.md:123 -msgid "\"a\"" -msgstr "\"a\"" - -#: src/traits/drop.md:19 src/exercises/day-1/solutions-morning.md:86 -msgid "\"b\"" -msgstr "\"b\"" +#: src/borrowing/shared.md:34 +msgid "Notes on stack returns:" +msgstr "" -#: src/traits/drop.md:21 src/exercises/day-1/solutions-morning.md:86 -msgid "\"c\"" -msgstr "\"c\"" - -#: src/traits/drop.md:22 src/exercises/day-1/solutions-morning.md:86 -msgid "\"d\"" -msgstr "\"d\"" +#: src/borrowing/shared.md:36 +msgid "" +"Demonstrate that the return from `add` is cheap because the compiler can " +"eliminate the copy operation. Change the above code to print stack addresses " +"and run it on the [Playground](https://play.rust-lang.org/) or look at the " +"assembly in [Godbolt](https://rust.godbolt.org/). In the \"DEBUG\" " +"optimization level, the addresses should change, while they stay the same " +"when changing to the \"RELEASE\" setting:" +msgstr "" -#: src/traits/drop.md:23 -msgid "\"Exiting block B\"" +#: src/borrowing/shared.md:57 +msgid "The Rust compiler can do return value optimization (RVO)." msgstr "" -#: src/traits/drop.md:25 -msgid "\"Exiting block A\"" +#: src/borrowing/shared.md:58 +msgid "" +"In C++, copy elision has to be defined in the language specification because " +"constructors can have side effects. In Rust, this is not an issue at all. If " +"RVO did not happen, Rust will always perform a simple and efficient `memcpy` " +"copy." msgstr "" -#: src/traits/drop.md:28 -msgid "\"Exiting main\"" +#: src/borrowing/borrowck.md:3 +msgid "" +"Rust's _borrow checker_ puts constraints on the ways you can borrow values. " +"For a given value, at any time:" msgstr "" -#: src/traits/drop.md:34 -msgid "Note that `std::mem::drop` is not the same as `std::ops::Drop::drop`." +#: src/borrowing/borrowck.md:5 +msgid "You can have one or more shared references to the value, _or_" msgstr "" -#: src/traits/drop.md:35 -msgid "Values are automatically dropped when they go out of scope." +#: src/borrowing/borrowck.md:6 +msgid "You can have exactly one exclusive reference to the value." msgstr "" -#: src/traits/drop.md:36 +#: src/borrowing/borrowck.md:27 msgid "" -"When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" -"drop` implementation will be called." +"Note that the requirement is that conflicting references not _exist_ at the " +"same point. It does not matter where the reference is dereferenced." msgstr "" -#: src/traits/drop.md:38 +#: src/borrowing/borrowck.md:28 msgid "" -"All its fields will then be dropped too, whether or not it implements `Drop`." +"The above code does not compile because `a` is borrowed as mutable (through " +"`c`) and as immutable (through `b`) at the same time." msgstr "" -#: src/traits/drop.md:39 +#: src/borrowing/borrowck.md:29 msgid "" -"`std::mem::drop` is just an empty function that takes any value. The " -"significance is that it takes ownership of the value, so at the end of its " -"scope it gets dropped. This makes it a convenient way to explicitly drop " -"values earlier than they would otherwise go out of scope." +"Move the `println!` statement for `b` before the scope that introduces `c` " +"to make the code compile." msgstr "" -#: src/traits/drop.md:42 +#: src/borrowing/borrowck.md:30 msgid "" -"This can be useful for objects that do some work on `drop`: releasing locks, " -"closing files, etc." +"After that change, the compiler realizes that `b` is only ever used before " +"the new mutable borrow of `a` through `c`. This is a feature of the borrow " +"checker called \"non-lexical lifetimes\"." msgstr "" -#: src/traits/drop.md:45 src/traits/operators.md:26 -msgid "Discussion points:" +#: src/borrowing/borrowck.md:31 +msgid "" +"The exclusive reference constraint is quite strong. Rust uses it to ensure " +"that data races do not occur. Rust also _relies_ on this constraint to " +"optimize codes. For example, a value behind a shared reference can be safely " +"cached in a register for the lifetime of that reference." msgstr "" -#: src/traits/drop.md:47 -msgid "Why doesn't `Drop::drop` take `self`?" +#: src/borrowing/borrowck.md:32 +msgid "" +"The borrow checker is designed to accommodate many common patterns, such as " +"taking exclusive references to different fields in a struct at the same " +"time. But, there are some situations where it doesn't quite \"get it\" and " +"this often results in \"fighting with the borrow checker.\"" msgstr "" -#: src/traits/drop.md:48 +#: src/borrowing/interior-mutability.md:6 msgid "" -"Short-answer: If it did, `std::mem::drop` would be called at the end of the " -"block, resulting in another call to `Drop::drop`, and a stack overflow!" +"Rust provides a few safe means of modifying a value given only a shared " +"reference to that value. All of these replace copmile-time checks with " +"runtime checks." msgstr "" -#: src/traits/drop.md:51 -msgid "Try replacing `drop(a)` with `a.drop()`." -msgstr "" +#: src/borrowing/interior-mutability.md:10 +msgid "`Cell` and `RefCell`" +msgstr "`Cell` og `RefCell`" -#: src/traits/default.md:1 -msgid "The `Default` Trait" +#: src/borrowing/interior-mutability.md:12 +msgid "" +"[`Cell`](https://doc.rust-lang.org/std/cell/struct.Cell.html) and [`RefCell`]" +"(https://doc.rust-lang.org/std/cell/struct.RefCell.html) implement what Rust " +"calls _interior mutability:_ mutation of values in an immutable context." msgstr "" -#: src/traits/default.md:3 +#: src/borrowing/interior-mutability.md:17 msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " -"produces a default value for a type." +"`Cell` is typically used for simple types, as it requires copying or moving " +"values. More complex interior types typically use `RefCell`, which tracks " +"shared and exclusive references at runtime and panics if they are misused." msgstr "" -#: src/traits/default.md:18 -msgid "\"John Smith\"" -msgstr "\"John Smith\"" - -#: src/traits/default.md:24 -msgid "\"{default_struct:#?}\"" -msgstr "\"{default_struct:#?}\"" - -#: src/traits/default.md:27 -msgid "\"Y is set!\"" -msgstr "\"Y er sat!\"" - -#: src/traits/default.md:30 -msgid "\"{almost_default_struct:#?}\"" +#: src/borrowing/interior-mutability.md:49 +msgid "\"graph: {root:#?}\"" msgstr "" -#: src/traits/default.md:33 -msgid "\"{:#?}\"" -msgstr "\"{:#?}\"" +#: src/borrowing/interior-mutability.md:50 +msgid "\"graph sum: {}\"" +msgstr "" -#: src/traits/default.md:40 +#: src/borrowing/interior-mutability.md:57 msgid "" -"It can be implemented directly or it can be derived via `#[derive(Default)]`." +"If we were using `Cell` instead of `RefCell` in this example, we would have " +"to move the `Node` out of the `Rc` to push children, then move it back in. " +"This is safe because there's always one, un-referenced value in the cell, " +"but it's not ergonomic." msgstr "" -#: src/traits/default.md:41 +#: src/borrowing/interior-mutability.md:58 msgid "" -"A derived implementation will produce a value where all fields are set to " -"their default values." +"To do anything with a Node, you must call a `RefCell` method, usually " +"`borrow` or `borrow_mut`." msgstr "" -#: src/traits/default.md:42 -msgid "This means all types in the struct must implement `Default` too." +#: src/borrowing/interior-mutability.md:59 +msgid "" +"Demonstrate that reference loops can be created by adding `root` to `subtree." +"children` (don't try to print it!)." msgstr "" -#: src/traits/default.md:43 +#: src/borrowing/interior-mutability.md:60 msgid "" -"Standard Rust types often implement `Default` with reasonable values (e.g. " -"`0`, `\"\"`, etc)." +"To demonstrate a runtime panic, add a `fn inc(&mut self)` that increments " +"`self.value` and calls the same method on its children. This will panic in " +"the presence of the reference loop, with `thread 'main' panicked at 'already " +"borrowed: BorrowMutError'`." msgstr "" -#: src/traits/default.md:44 -msgid "The partial struct copy works nicely with default." +#: src/borrowing/exercise.md:3 +msgid "" +"You're working on implementing a health-monitoring system. As part of that, " +"you need to keep track of users' health statistics." msgstr "" -#: src/traits/default.md:45 +#: src/borrowing/exercise.md:6 msgid "" -"Rust standard library is aware that types can implement `Default` and " -"provides convenience methods that use it." +"You'll start with some stubbed functions in an `impl` block as well as a " +"`User` struct definition. Your goal is to implement the stubbed out methods " +"on the `User` `struct` defined in the `impl` block." msgstr "" -#: src/traits/default.md:46 +#: src/borrowing/exercise.md:10 msgid "" -"the `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" -"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" -"with-struct-update-syntax)" +"Copy the code below to and fill in the missing " +"methods:" msgstr "" -#: src/traits/operators.md:1 -msgid "`Add`, `Mul`, ..." -msgstr "`Add`, `Mul`, ..." - -#: src/traits/operators.md:3 +#: src/borrowing/exercise.md:51 msgid "" -"Operator overloading is implemented via traits in [`std::ops`](https://doc." -"rust-lang.org/std/ops/index.html):" +"\"Update a user's statistics based on measurements from a visit to the " +"doctor\"" msgstr "" -#: src/traits/operators.md:20 -msgid "\"{:?} + {:?} = {:?}\"" -msgstr "\"{:?} + {:?} = {:?}\"" +#: src/borrowing/exercise.md:56 src/borrowing/exercise.md:62 +#: src/borrowing/exercise.md:68 src/borrowing/solution.md:58 +#: src/borrowing/solution.md:64 src/borrowing/solution.md:70 +#: src/android/build-rules/library.md:43 src/android/aidl/client.md:23 +msgid "\"Bob\"" +msgstr "\"Bob\"" -#: src/traits/operators.md:28 -msgid "" -"You could implement `Add` for `&Point`. In which situations is that useful? " +#: src/borrowing/exercise.md:57 src/borrowing/solution.md:59 +msgid "\"I'm {} and my age is {}\"" msgstr "" -#: src/traits/operators.md:29 -msgid "" -"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " -"the operator is not `Copy`, you should consider overloading the operator for " -"`&T` as well. This avoids unnecessary cloning on the call site." +#: src/slices-and-lifetimes.md:4 +msgid "[Slices: &\\[T\\]](./slices-and-lifetimes/slices.md) (10 minutes)" msgstr "" -#: src/traits/operators.md:33 -msgid "" -"Why is `Output` an associated type? Could it be made a type parameter of the " -"method?" +#: src/slices-and-lifetimes.md:5 +msgid "[String References](./slices-and-lifetimes/str.md) (10 minutes)" msgstr "" -#: src/traits/operators.md:34 +#: src/slices-and-lifetimes.md:6 msgid "" -"Short answer: Function type parameters are controlled by the caller, but " -"associated types (like `Output`) are controlled by the implementor of a " -"trait." +"[Lifetime Annotations](./slices-and-lifetimes/lifetime-annotations.md) (10 " +"minutes)" msgstr "" -#: src/traits/operators.md:37 +#: src/slices-and-lifetimes.md:7 msgid "" -"You could implement `Add` for two different types, e.g. `impl Add<(i32, " -"i32)> for Point` would add a tuple to a `Point`." -msgstr "" - -#: src/traits/closures.md:1 -msgid "Closures" +"[Lifetime Elision](./slices-and-lifetimes/lifetime-elision.md) (5 minutes)" msgstr "" -#: src/traits/closures.md:3 +#: src/slices-and-lifetimes.md:8 msgid "" -"Closures or lambda expressions have types which cannot be named. However, " -"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." -"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " -"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" +"[Struct Lifetimes](./slices-and-lifetimes/struct-lifetimes.md) (5 minutes)" msgstr "" -#: src/traits/closures.md:10 -msgid "\"Calling function on {input}\"" +#: src/slices-and-lifetimes.md:9 +msgid "" +"[Exercise: Protobuf Parsing](./slices-and-lifetimes/exercise.md) (30 minutes)" msgstr "" -#: src/traits/closures.md:16 src/traits/closures.md:17 -msgid "\"add_3: {}\"" -msgstr "\"add_3: {}\"" +#: src/slices-and-lifetimes/slices.md:1 +msgid "Slices" +msgstr "Arraysegmenter" -#: src/traits/closures.md:24 src/traits/closures.md:25 -msgid "\"accumulate: {}\"" -msgstr "\"accumulate: {}\"" +#: src/slices-and-lifetimes/slices.md:3 +msgid "A slice gives you a view into a larger collection:" +msgstr "" -#: src/traits/closures.md:28 -msgid "\"multiply_sum: {}\"" -msgstr "\"multiply_sum: {}\"" +#: src/slices-and-lifetimes/slices.md:17 +msgid "Slices borrow data from the sliced type." +msgstr "" -#: src/traits/closures.md:34 -msgid "" -"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " -"perhaps captures nothing at all. It can be called multiple times " -"concurrently." +#: src/slices-and-lifetimes/slices.md:18 +msgid "Question: What happens if you modify `a[3]` right before printing `s`?" msgstr "" -#: src/traits/closures.md:37 +#: src/slices-and-lifetimes/slices.md:23 msgid "" -"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " -"multiple times, but not concurrently." +"We create a slice by borrowing `a` and specifying the starting and ending " +"indexes in brackets." msgstr "" -#: src/traits/closures.md:40 +#: src/slices-and-lifetimes/slices.md:25 msgid "" -"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " -"might consume captured values." +"If the slice starts at index 0, Rust’s range syntax allows us to drop the " +"starting index, meaning that `&a[0..a.len()]` and `&a[..a.len()]` are " +"identical." msgstr "" -#: src/traits/closures.md:43 +#: src/slices-and-lifetimes/slices.md:27 msgid "" -"`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " -"I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " -"use an `Fn` wherever an `FnMut` or `FnOnce` is called for." +"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " +"identical." msgstr "" -#: src/traits/closures.md:47 +#: src/slices-and-lifetimes/slices.md:29 msgid "" -"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " -"`multiply_sum`), depending on what the closure captures." +"To easily create a slice of the full array, we can therefore use `&a[..]`." msgstr "" -#: src/traits/closures.md:50 +#: src/slices-and-lifetimes/slices.md:31 msgid "" -"By default, closures will capture by reference if they can. The `move` " -"keyword makes them capture by value." +"`s` is a reference to a slice of `i32`s. Notice that the type of `s` " +"(`&[i32]`) no longer mentions the array length. This allows us to perform " +"computation on slices of different sizes." msgstr "" -#: src/traits/closures.md:58 -msgid "\"Hi\"" -msgstr "\"Hej\"" - -#: src/traits/closures.md:59 -msgid "\"there\"" -msgstr "\"der\"" - -#: src/exercises/day-3/morning.md:1 -msgid "Day 3: Morning Exercises" -msgstr "Dag 3: Formiddagsøvelser" - -#: src/exercises/day-3/morning.md:3 -msgid "We will design a classical GUI library using traits and trait objects." +#: src/slices-and-lifetimes/slices.md:33 +msgid "" +"Slices always borrow from another object. In this example, `a` has to remain " +"'alive' (in scope) for at least as long as our slice." msgstr "" -#: src/exercises/day-3/morning.md:5 +#: src/slices-and-lifetimes/slices.md:35 msgid "" -"We will also look at enum dispatch with an exercise involving points and " -"polygons." +"The question about modifying `a[3]` can spark an interesting discussion, but " +"the answer is that for memory safety reasons you cannot do it through `a` at " +"this point in the execution, but you can read the data from both `a` and `s` " +"safely. It works before you created the slice, and again after the " +"`println`, when the slice is no longer used. More details will be explained " +"in the borrow checker section." msgstr "" -#: src/exercises/day-3/simple-gui.md:3 +#: src/slices-and-lifetimes/str.md:6 msgid "" -"Let us design a classical GUI library using our new knowledge of traits and " -"trait objects." +"We can now understand the two string types in Rust: `&str` is almost like " +"`&[char]`, but with its data stored in a variable-length encoding (UTF-8)." msgstr "" -#: src/exercises/day-3/simple-gui.md:6 -msgid "We will have a number of widgets in our library:" -msgstr "" +#: src/slices-and-lifetimes/str.md:12 +msgid "\"s1: {s1}\"" +msgstr "\"s1: {s1}\"" -#: src/exercises/day-3/simple-gui.md:8 -msgid "`Window`: has a `title` and contains other widgets." -msgstr "" +#: src/slices-and-lifetimes/str.md:14 +msgid "\"Hello \"" +msgstr "\"Hallo \"" -#: src/exercises/day-3/simple-gui.md:9 -msgid "" -"`Button`: has a `label` and a callback function which is invoked when the " -"button is pressed." +#: src/slices-and-lifetimes/str.md:20 +msgid "\"s3: {s3}\"" +msgstr "\"s3: {s3}\"" + +#: src/slices-and-lifetimes/str.md:24 +msgid "Rust terminology:" msgstr "" -#: src/exercises/day-3/simple-gui.md:11 -msgid "`Label`: has a `label`." +#: src/slices-and-lifetimes/str.md:26 +msgid "`&str` an immutable reference to a string slice." msgstr "" -#: src/exercises/day-3/simple-gui.md:13 -msgid "The widgets will implement a `Widget` trait, see below." +#: src/slices-and-lifetimes/str.md:27 +msgid "`String` a mutable string buffer." msgstr "" -#: src/exercises/day-3/simple-gui.md:15 +#: src/slices-and-lifetimes/str.md:32 msgid "" -"Copy the code below to , fill in the missing " -"`draw_into` methods so that you implement the `Widget` trait:" +"`&str` introduces a string slice, which is an immutable reference to UTF-8 " +"encoded string data stored in a block of memory. String literals " +"(`”Hello”`), are stored in the program’s binary." msgstr "" -#: src/exercises/day-3/simple-gui.md:23 -#: src/exercises/day-3/solutions-morning.md:9 -msgid "/// Natural width of `self`.\n" +#: src/slices-and-lifetimes/str.md:35 +msgid "" +"Rust’s `String` type is a wrapper around a vector of bytes. As with a " +"`Vec`, it is owned." msgstr "" -#: src/exercises/day-3/simple-gui.md:26 -#: src/exercises/day-3/solutions-morning.md:12 -msgid "/// Draw the widget into a buffer.\n" +#: src/slices-and-lifetimes/str.md:37 +msgid "" +"As with many other types `String::from()` creates a string from a string " +"literal; `String::new()` creates a new empty string, to which string data " +"can be added using the `push()` and `push_str()` methods." msgstr "" -#: src/exercises/day-3/simple-gui.md:29 -#: src/exercises/day-3/solutions-morning.md:15 -msgid "/// Draw the widget on standard output.\n" +#: src/slices-and-lifetimes/str.md:40 +msgid "" +"The `format!()` macro is a convenient way to generate an owned string from " +"dynamic values. It accepts the same format specification as `println!()`." msgstr "" -#: src/exercises/day-3/simple-gui.md:33 -#: src/exercises/day-3/solutions-morning.md:19 -msgid "\"{buffer}\"" -msgstr "\"{buffer}\"" - -#: src/exercises/day-3/simple-gui.md:120 -#: src/exercises/day-3/solutions-morning.md:135 -msgid "\"Rust GUI Demo 1.23\"" +#: src/slices-and-lifetimes/str.md:43 +msgid "" +"You can borrow `&str` slices from `String` via `&` and optionally range " +"selection. If you select a byte range that is not aligned to character " +"boundaries, the expression will panic. The `chars` iterator iterates over " +"characters and is preferred over trying to get character boundaries right." msgstr "" -#: src/exercises/day-3/simple-gui.md:121 -#: src/exercises/day-3/solutions-morning.md:136 -msgid "\"This is a small text GUI demo.\"" +#: src/slices-and-lifetimes/str.md:48 +msgid "" +"For C++ programmers: think of `&str` as `const char*` from C++, but the one " +"that always points to a valid string in memory. Rust `String` is a rough " +"equivalent of `std::string` from C++ (main difference: it can only contain " +"UTF-8 encoded bytes and will never use a small-string optimization)." msgstr "" -#: src/exercises/day-3/simple-gui.md:123 -#: src/exercises/day-3/solutions-morning.md:138 -msgid "\"Click me!\"" +#: src/slices-and-lifetimes/str.md:52 +msgid "Byte strings literals allow you to create a `&[u8]` value directly:" msgstr "" -#: src/exercises/day-3/simple-gui.md:124 -#: src/exercises/day-3/solutions-morning.md:139 -msgid "\"You clicked the button!\"" -msgstr "" +#: src/slices-and-lifetimes/lifetime-annotations.md:1 +msgid "Lifetimes" +msgstr "Livstider" -#: src/exercises/day-3/simple-gui.md:130 -msgid "The output of the above program can be something simple like this:" +#: src/slices-and-lifetimes/lifetime-annotations.md:3 +msgid "" +"A reference has a _lifetime_, which must \"outlive\" the value it refers to. " +"This is verified by the borrow checker." msgstr "" -#: src/exercises/day-3/simple-gui.md:142 +#: src/slices-and-lifetimes/lifetime-annotations.md:6 msgid "" -"If you want to draw aligned text, you can use the [fill/alignment](https://" -"doc.rust-lang.org/std/fmt/index.html#fillalignment) formatting operators. In " -"particular, notice how you can pad with different characters (here a `'/'`) " -"and how you can control alignment:" +"The lifetime can be implicit - this is what we have seen so far. Lifetimes " +"can also be explicit: `&'a Point`, `&'document str`. Lifetimes start with " +"`'` and `'a` is a typical default name. Read `&'a Point` as \"a borrowed " +"`Point` which is valid for at least the lifetime `a`\"." msgstr "" -#: src/exercises/day-3/simple-gui.md:150 -msgid "\"left aligned: |{:/width$}|\"" +#: src/slices-and-lifetimes/lifetime-annotations.md:29 +msgid "// What is the lifetime of p3?\n" msgstr "" -#: src/exercises/day-3/simple-gui.md:156 +#: src/slices-and-lifetimes/lifetime-annotations.md:30 +#, fuzzy +msgid "\"p3: {p3:?}\"" +msgstr "\"v: {:?}\"" + +#: src/slices-and-lifetimes/lifetime-annotations.md:37 msgid "" -"Using such alignment tricks, you can for example produce output like this:" +"In this example, the the compiler does not know what lifetime to infer for " +"`p3`. Looking inside the function body shows that it can only safely assume " +"that `p3`'s lifetime is the shorter of `p1` and `p2`. But just like types, " +"Rust requires explicit annotations of lifetimes on function arguments and " +"return values." msgstr "" -#: src/exercises/day-3/points-polygons.md:1 -msgid "Polygon Struct" +#: src/slices-and-lifetimes/lifetime-annotations.md:43 +msgid "Add `'a` appropriately to `left_most`:" msgstr "" -#: src/exercises/day-3/points-polygons.md:3 +#: src/slices-and-lifetimes/lifetime-annotations.md:49 msgid "" -"We will create a `Polygon` struct which contain some points. Copy the code " -"below to and fill in the missing methods to " -"make the tests pass:" +"This says, \"given p1 and p2 which both outlive `'a`, the return value lives " +"for at least `'a`." msgstr "" -#: src/exercises/day-3/points-polygons.md:12 -#: src/exercises/day-3/points-polygons.md:20 -#: src/exercises/day-3/points-polygons.md:28 -msgid "// add fields\n" +#: src/slices-and-lifetimes/lifetime-annotations.md:51 +msgid "" +"In common cases, lifetimes can be elided, as described on the next slide." msgstr "" -#: src/exercises/day-3/points-polygons.md:16 -#: src/exercises/day-3/points-polygons.md:24 -#: src/exercises/day-3/points-polygons.md:32 -msgid "// add methods\n" -msgstr "" +#: src/slices-and-lifetimes/lifetime-elision.md:1 +msgid "Lifetimes in Function Calls" +msgstr "Livstider i funktionskald" -#: src/exercises/day-3/points-polygons.md:117 +#: src/slices-and-lifetimes/lifetime-elision.md:3 msgid "" -"Since the method signatures are missing from the problem statements, the key " -"part of the exercise is to specify those correctly. You don't have to modify " -"the tests." +"Lifetimes for function arguments and return values must be fully specified, " +"but Rust allows lifetimes to be elided in most cases with [a few simple " +"rules](https://doc.rust-lang.org/nomicon/lifetime-elision.html). This is not " +"inference -- it is just a syntactic shorthand." msgstr "" -#: src/exercises/day-3/points-polygons.md:120 -msgid "Other interesting parts of the exercise:" +#: src/slices-and-lifetimes/lifetime-elision.md:8 +msgid "Each argument which does not have a lifetime annotation is given one." msgstr "" -#: src/exercises/day-3/points-polygons.md:122 +#: src/slices-and-lifetimes/lifetime-elision.md:9 msgid "" -"Derive a `Copy` trait for some structs, as in tests the methods sometimes " -"don't borrow their arguments." +"If there is only one argument lifetime, it is given to all un-annotated " +"return values." msgstr "" -#: src/exercises/day-3/points-polygons.md:123 +#: src/slices-and-lifetimes/lifetime-elision.md:10 msgid "" -"Discover that `Add` trait must be implemented for two objects to be addable " -"via \"+\". Note that we do not discuss generics until Day 3." +"If there are multiple argument lifetimes, but the first one is for `self`, " +"that lifetime is given to all un-annotated return values." msgstr "" -#: src/error-handling.md:3 -msgid "Error handling in Rust is done using explicit control flow:" +#: src/slices-and-lifetimes/lifetime-elision.md:50 +msgid "In this example, `cab_distance` is trivially elided." msgstr "" -#: src/error-handling.md:5 -msgid "Functions that can have errors list this in their return type," +#: src/slices-and-lifetimes/lifetime-elision.md:52 +msgid "" +"The `nearest` function provides another example of a function with multiple " +"references in its arguments that requires explicit annotation." msgstr "" -#: src/error-handling.md:6 -msgid "There are no exceptions." +#: src/slices-and-lifetimes/lifetime-elision.md:54 +msgid "Try adjusting the signature to \"lie\" about the lifetimes returned:" msgstr "" -#: src/error-handling/panics.md:3 -msgid "Rust will trigger a panic if a fatal error happens at runtime:" +#: src/slices-and-lifetimes/lifetime-elision.md:60 +msgid "" +"This won't compile, demonstrating that the annotations are checked for " +"validity by the compiler. Note that this is not the case for raw pointers " +"(unsafe), and this is a common source of errors with unsafe Rust." msgstr "" -#: src/error-handling/panics.md:8 -msgid "\"v[100]: {}\"" -msgstr "\"v[100]: {}\"" +#: src/slices-and-lifetimes/struct-lifetimes.md:1 +msgid "Lifetimes in Data Structures" +msgstr "Livstider i datastrukturer" -#: src/error-handling/panics.md:12 -msgid "Panics are for unrecoverable and unexpected errors." +#: src/slices-and-lifetimes/struct-lifetimes.md:3 +msgid "" +"If a data type stores borrowed data, it must be annotated with a lifetime:" msgstr "" -#: src/error-handling/panics.md:13 -msgid "Panics are symptoms of bugs in the program." +#: src/slices-and-lifetimes/struct-lifetimes.md:10 +msgid "\"Bye {text}!\"" +msgstr "\"Farvel {text}!\"" + +#: src/slices-and-lifetimes/struct-lifetimes.md:14 +msgid "\"The quick brown fox jumps over the lazy dog.\"" msgstr "" -#: src/error-handling/panics.md:14 +#: src/slices-and-lifetimes/struct-lifetimes.md:17 +msgid "// erase(text);\n" +msgstr "// erase(text);\n" + +#: src/slices-and-lifetimes/struct-lifetimes.md:18 +msgid "\"{fox:?}\"" +msgstr "\"{fox:?}\"" + +#: src/slices-and-lifetimes/struct-lifetimes.md:19 +msgid "\"{dog:?}\"" +msgstr "\"{dog:?}\"" + +#: src/slices-and-lifetimes/struct-lifetimes.md:26 msgid "" -"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." +"In the above example, the annotation on `Highlight` enforces that the data " +"underlying the contained `&str` lives at least as long as any instance of " +"`Highlight` that uses that data." msgstr "" -#: src/error-handling/panic-unwind.md:1 -msgid "Catching the Stack Unwinding" +#: src/slices-and-lifetimes/struct-lifetimes.md:27 +msgid "" +"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " +"the borrow checker throws an error." msgstr "" -#: src/error-handling/panic-unwind.md:3 +#: src/slices-and-lifetimes/struct-lifetimes.md:28 msgid "" -"By default, a panic will cause the stack to unwind. The unwinding can be " -"caught:" +"Types with borrowed data force users to hold on to the original data. This " +"can be useful for creating lightweight views, but it generally makes them " +"somewhat harder to use." msgstr "" -#: src/error-handling/panic-unwind.md:10 -msgid "\"hello!\"" -msgstr "\"hallo!\"" +#: src/slices-and-lifetimes/struct-lifetimes.md:29 +msgid "When possible, make data structures own their data directly." +msgstr "" -#: src/error-handling/panic-unwind.md:15 -msgid "\"oh no!\"" -msgstr "\"åh nej!\"" +#: src/slices-and-lifetimes/struct-lifetimes.md:30 +msgid "" +"Some structs with multiple references inside can have more than one lifetime " +"annotation. This can be necessary if there is a need to describe lifetime " +"relationships between the references themselves, in addition to the lifetime " +"of the struct itself. Those are very advanced use cases." +msgstr "" -#: src/error-handling/panic-unwind.md:21 +#: src/slices-and-lifetimes/exercise.md:3 msgid "" -"This can be useful in servers which should keep running even if a single " -"request crashes." +"In this exercise, you will build a parser for the [protobuf binary encoding]" +"(https://protobuf.dev/programming-guides/encoding/). Don't worry, it's " +"simpler than it seems! This illustrates a common parsing pattern, passing " +"slices of data. The underlying data itself is never copied." msgstr "" -#: src/error-handling/panic-unwind.md:23 -msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." +#: src/slices-and-lifetimes/exercise.md:8 +msgid "" +"Fully parsing a protobuf message requires knowing the types of the fields, " +"indexed by their field numbers. That is typically provided in a `proto` " +"file. In this exercise, we'll encode that information into `match` " +"statements in functions that get called for each field." msgstr "" -#: src/error-handling/result.md:1 -msgid "Structured Error Handling with `Result`" +#: src/slices-and-lifetimes/exercise.md:13 +msgid "We'll use the following proto:" msgstr "" -#: src/error-handling/result.md:3 +#: src/slices-and-lifetimes/exercise.md:28 msgid "" -"We have already seen the `Result` enum. This is used pervasively when errors " -"are expected as part of normal operation:" +"A proto message is encoded as a series of fields, one after the next. Each " +"is implemented as a \"tag\" followed by the value. The tag contains a field " +"number (e.g., `2` for the `id` field of a `Person` message) and a wire type " +"defining how the payload should be determined from the byte stream." msgstr "" -#: src/error-handling/result.md:11 -msgid "\"diary.txt\"" -msgstr "\"dagbog.txt\"" +#: src/slices-and-lifetimes/exercise.md:33 +msgid "" +"Integers, including the tag, are represented with a variable-length encoding " +"called VARINT. Luckily, `parse_varint` is defined for you below. The given " +"code also defines callbacks to handle `Person` and `PhoneNumber` fields, and " +"to parse a message into a series of calls to those callbacks." +msgstr "" -#: src/error-handling/result.md:16 -msgid "\"Dear diary: {contents}\"" -msgstr "\"Kære dagbog: {contents}\"" +#: src/slices-and-lifetimes/exercise.md:38 +msgid "What remains for you is to implement the `parse_field` function." +msgstr "" -#: src/error-handling/result.md:19 -msgid "\"The diary could not be opened: {err}\"" +#: src/slices-and-lifetimes/exercise.md:47 +#: src/slices-and-lifetimes/solution.md:10 +msgid "\"Invalid varint\"" msgstr "" -#: src/error-handling/result.md:27 -msgid "" -"As with `Option`, the successful value sits inside of `Result`, forcing the " -"developer to explicitly extract it. This encourages error checking. In the " -"case where an error should never happen, `unwrap()` or `expect()` can be " -"called, and this is a signal of the developer intent too." +#: src/slices-and-lifetimes/exercise.md:49 +#: src/slices-and-lifetimes/solution.md:12 +msgid "\"Invalid wire-type\"" msgstr "" -#: src/error-handling/result.md:30 -msgid "" -"`Result` documentation is a recommended read. Not during the course, but it " -"is worth mentioning. It contains a lot of convenience methods and functions " -"that help functional-style programming. " +#: src/slices-and-lifetimes/exercise.md:51 +#: src/slices-and-lifetimes/solution.md:14 +msgid "\"Unexpected EOF\"" msgstr "" -#: src/error-handling/try-operator.md:1 -msgid "Propagating Errors with `?`" +#: src/slices-and-lifetimes/exercise.md:53 +#: src/slices-and-lifetimes/solution.md:16 +msgid "\"Invalid length\"" msgstr "" -#: src/error-handling/try-operator.md:3 -msgid "" -"The try-operator `?` is used to return errors to the caller. It lets you " -"turn the common" +#: src/slices-and-lifetimes/exercise.md:55 +#: src/slices-and-lifetimes/solution.md:18 +msgid "\"Unexpected wire-type)\"" msgstr "" -#: src/error-handling/try-operator.md:13 -msgid "into the much simpler" +#: src/slices-and-lifetimes/exercise.md:57 +#: src/slices-and-lifetimes/solution.md:20 +msgid "\"Invalid string (not UTF-8)\"" msgstr "" -#: src/error-handling/try-operator.md:19 -msgid "We can use this to simplify our error handling code:" +#: src/slices-and-lifetimes/exercise.md:60 +#: src/slices-and-lifetimes/solution.md:23 +msgid "/// A wire type as seen on the wire.\n" msgstr "" -#: src/error-handling/try-operator.md:40 -msgid "//fs::write(\"config.dat\", \"alice\").unwrap();\n" -msgstr "//fs::write(\"config.dat\", \"alice\").unwrap();\n" +#: src/slices-and-lifetimes/exercise.md:63 +#: src/slices-and-lifetimes/solution.md:26 +msgid "/// The Varint WireType indicates the value is a single VARINT.\n" +msgstr "" -#: src/error-handling/try-operator.md:41 -#: src/error-handling/converting-error-types-example.md:43 -#: src/error-handling/deriving-error-enums.md:30 -#: src/error-handling/dynamic-errors.md:27 -#: src/error-handling/error-contexts.md:26 -msgid "\"config.dat\"" -msgstr "\"config.dat\"" +#: src/slices-and-lifetimes/exercise.md:65 +#: src/slices-and-lifetimes/solution.md:28 +msgid "" +"//I64, -- not needed for this exercise\n" +" /// The Len WireType indicates that the value is a length represented as " +"a VARINT\n" +" /// followed by exactly that number of bytes.\n" +msgstr "" -#: src/error-handling/try-operator.md:42 -#: src/error-handling/converting-error-types-example.md:44 -msgid "\"username or error: {username:?}\"" +#: src/slices-and-lifetimes/exercise.md:69 +#: src/slices-and-lifetimes/solution.md:32 +msgid "" +"/// The I32 WireType indicates that the value is precisely 4 bytes in little-" +"endian order\n" +" /// containing a 32-bit signed integer.\n" msgstr "" -#: src/error-handling/try-operator.md:50 -#: src/error-handling/converting-error-types-example.md:52 -msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." +#: src/slices-and-lifetimes/exercise.md:74 +#: src/slices-and-lifetimes/solution.md:37 +msgid "/// A field's value, typed based on the wire type.\n" msgstr "" -#: src/error-handling/try-operator.md:51 -#: src/error-handling/converting-error-types-example.md:53 -msgid "" -"Use the `fs::write` call to test out the different scenarios: no file, empty " -"file, file with username." +#: src/slices-and-lifetimes/exercise.md:78 +#: src/slices-and-lifetimes/solution.md:41 +msgid "//I64(i64), -- not needed for this exercise\n" msgstr "" -#: src/error-handling/try-operator.md:52 -msgid "" -"The return type of the function has to be compatible with the nested " -"functions it calls. For instance, a function returning a `Result` " -"can only apply the `?` operator on a function returning a `Result`. It cannot apply the `?` operator on a function returning an " -"`Option` or `Result` unless `OtherErr` implements " -"`From`. Reciprocally, a function returning an `Option` can only " -"apply the `?` operator on a function returning an `Option`." +#: src/slices-and-lifetimes/exercise.md:83 +#: src/slices-and-lifetimes/solution.md:46 +msgid "/// A field, containing the field number and its value.\n" +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:96 +#: src/slices-and-lifetimes/solution.md:59 +msgid "//1 => WireType::I64, -- not needed for this exercise\n" msgstr "" -#: src/error-handling/try-operator.md:57 +#: src/slices-and-lifetimes/exercise.md:126 +#: src/slices-and-lifetimes/solution.md:89 msgid "" -"You can convert incompatible types into one another with the different " -"`Option` and `Result` methods such as `Option::ok_or`, `Result::ok`, " -"`Result::err`." +"/// Parse a VARINT, returning the parsed value and the remaining bytes.\n" msgstr "" -#: src/error-handling/converting-error-types.md:3 +#: src/slices-and-lifetimes/exercise.md:134 +#: src/slices-and-lifetimes/solution.md:97 msgid "" -"The effective expansion of `?` is a little more complicated than previously " -"indicated:" +"// This is the last byte of the VARINT, so convert it to\n" +" // a u64 and return it.\n" msgstr "" -#: src/error-handling/converting-error-types.md:9 -msgid "works the same as" +#: src/slices-and-lifetimes/exercise.md:144 +#: src/slices-and-lifetimes/solution.md:107 +msgid "// More than 7 bytes is invalid.\n" msgstr "" -#: src/error-handling/converting-error-types.md:18 +#: src/slices-and-lifetimes/exercise.md:147 +#: src/slices-and-lifetimes/solution.md:110 +msgid "/// Convert a tag into a field number and a WireType.\n" +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:155 +#: src/slices-and-lifetimes/solution.md:117 +msgid "/// Parse a field, returning the remaining bytes\n" +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:158 msgid "" -"The `From::from` call here means we attempt to convert the error type to the " -"type returned by the function:" +"// 1. Read and unpack the tag.\n" +" // 2. Based on the wire type, build a Field, consuming as many bytes as\n" +" // necessary.\n" +" // 3. Return the field, and any un-consumed bytes.\n" msgstr "" -#: src/error-handling/converting-error-types-example.md:20 -msgid "\"IO error: {e}\"" -msgstr "\"IO-fejl: {e}\"" +#: src/slices-and-lifetimes/exercise.md:164 +#: src/slices-and-lifetimes/solution.md:154 +msgid "" +"/// Parse a message in the given data, calling `field_callback` for each " +"field in the message.\n" +"///\n" +"/// The entire input is consumed.\n" +msgstr "" -#: src/error-handling/converting-error-types-example.md:21 -msgid "\"Found no username in {filename}\"" +#: src/slices-and-lifetimes/exercise.md:181 +#: src/slices-and-lifetimes/solution.md:171 +msgid "/// Handle a field in a Person message.\n" msgstr "" -#: src/error-handling/converting-error-types-example.md:42 -#: src/error-handling/deriving-error-enums.md:29 -#: src/error-handling/dynamic-errors.md:26 -#: src/error-handling/error-contexts.md:25 -msgid "//fs::write(\"config.dat\", \"\").unwrap();\n" -msgstr "//fs::write(\"config.dat\", \"\").unwrap();\n" +#: src/slices-and-lifetimes/exercise.md:184 +#: src/slices-and-lifetimes/solution.md:174 +#, fuzzy +msgid "\"name: {}\"" +msgstr "\"nyt areal: {}\"" -#: src/error-handling/converting-error-types-example.md:55 -msgid "" -"It is good practice for all error types that don't need to be `no_std` to " -"implement `std::error::Error`, which requires `Debug` and `Display`. The " -"`Error` crate for `core` is only available in [nightly](https://github.com/" -"rust-lang/rust/issues/103765), so not fully `no_std` compatible yet." +#: src/slices-and-lifetimes/exercise.md:185 +#: src/slices-and-lifetimes/solution.md:175 +#, fuzzy +msgid "\"id: {}\"" +msgstr "\"int: {}\"" + +#: src/slices-and-lifetimes/exercise.md:187 +#: src/slices-and-lifetimes/solution.md:177 +msgid "\"phone:\"" msgstr "" -#: src/error-handling/converting-error-types-example.md:57 -msgid "" -"It's generally helpful for them to implement `Clone` and `Eq` too where " -"possible, to make life easier for tests and consumers of your library. In " -"this case we can't easily do so, because `io::Error` doesn't implement them." +#: src/slices-and-lifetimes/exercise.md:190 +#: src/slices-and-lifetimes/exercise.md:200 +#: src/slices-and-lifetimes/solution.md:180 +#: src/slices-and-lifetimes/solution.md:190 +msgid "// skip everything else\n" +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:195 +#: src/slices-and-lifetimes/solution.md:185 +msgid "/// Handle a field in a PhoneNumber message.\n" +msgstr "" + +#: src/slices-and-lifetimes/exercise.md:198 +#: src/slices-and-lifetimes/solution.md:188 +#, fuzzy +msgid "\" number: {}\"" +msgstr "\"{numbers:?}\"" + +#: src/slices-and-lifetimes/exercise.md:199 +#: src/slices-and-lifetimes/solution.md:189 +#, fuzzy +msgid "\" type: {}\"" +msgstr "\"int: {}\"" + +#: src/slices-and-lifetimes/solution.md:141 +msgid "// Unwrap error because `value` is definitely 4 bytes long.\n" msgstr "" -#: src/error-handling/deriving-error-enums.md:3 +#: src/slices-and-lifetimes/solution.md:216 +#: src/slices-and-lifetimes/solution.md:223 +#: src/slices-and-lifetimes/solution.md:230 +#, fuzzy +msgid "b\"hello\"" +msgstr "\"hallo\"" + +#: src/welcome-day-4.md:1 +#, fuzzy +msgid "Welcome to Day 4" +msgstr "Velkommen til Dag 1" + +#: src/welcome-day-4.md:3 msgid "" -"The [thiserror](https://docs.rs/thiserror/) crate is a popular way to create " -"an error enum like we did on the previous page:" +"Today we will cover topics relating to building large-scale software in Rust:" msgstr "" -#: src/error-handling/deriving-error-enums.md:13 -msgid "\"Could not read: {0}\"" +#: src/welcome-day-4.md:5 +msgid "Iterators: a deep dive on the `Iterator` trait." msgstr "" -#: src/error-handling/deriving-error-enums.md:15 -#: src/error-handling/dynamic-errors.md:13 -msgid "\"Found no username in {0}\"" +#: src/welcome-day-4.md:6 +msgid "Modules and visibility." msgstr "" -#: src/error-handling/deriving-error-enums.md:31 -#: src/error-handling/dynamic-errors.md:28 -#: src/error-handling/error-contexts.md:27 -msgid "\"Username: {username}\"" +#: src/welcome-day-4.md:7 +msgid "Testing." msgstr "" -#: src/error-handling/deriving-error-enums.md:32 -#: src/error-handling/dynamic-errors.md:29 -msgid "\"Error: {err}\"" -msgstr "\"Fejl: {err}\"" +#: src/welcome-day-4.md:8 +msgid "Error handling: panics, `Result`, and the try operator `?`." +msgstr "" -#: src/error-handling/deriving-error-enums.md:39 +#: src/welcome-day-4.md:9 msgid "" -"`thiserror`'s derive macro automatically implements `std::error::Error`, and " -"optionally `Display` (if the `#[error(...)]` attributes are provided) and " -"`From` (if the `#[from]` attribute is added). It also works for structs." +"Unsafe Rust: the escape hatch when you can't express yourself in safe Rust." msgstr "" -#: src/error-handling/deriving-error-enums.md:43 -msgid "It doesn't affect your public API, which makes it good for libraries." +#: src/welcome-day-4.md:14 +msgid "[Welcome](./welcome-day-4.md) (3 minutes)" msgstr "" -#: src/error-handling/dynamic-errors.md:3 -msgid "" -"Sometimes we want to allow any type of error to be returned without writing " -"our own enum covering all the different possibilities. `std::error::Error` " -"makes this easy." +#: src/welcome-day-4.md:15 +msgid "[Iterators](./iterators.md) (45 minutes)" msgstr "" -#: src/error-handling/dynamic-errors.md:36 -msgid "" -"This saves on code, but gives up the ability to cleanly handle different " -"error cases differently in the program. As such it's generally not a good " -"idea to use `Box` in the public API of a library, but it can be a " -"good option in a program where you just want to display the error message " -"somewhere." +#: src/welcome-day-4.md:16 +msgid "[Modules](./modules.md) (45 minutes)" +msgstr "" + +#: src/welcome-day-4.md:17 +msgid "[Testing](./testing.md) (1 hour)" msgstr "" -#: src/error-handling/error-contexts.md:3 +#: src/welcome-day-4.md:19 msgid "" -"The widely used [anyhow](https://docs.rs/anyhow/) crate can help you add " -"contextual information to your errors and allows you to have fewer custom " -"error types:" +"Including 10 minute breaks, this session should take about 3 hours and 5 " +"minutes" msgstr "" -#: src/error-handling/error-contexts.md:15 -msgid "\"Failed to open {path}\"" +#: src/iterators.md:4 +msgid "[Iterators](./iterators/iterators.md) (5 minutes)" msgstr "" -#: src/error-handling/error-contexts.md:17 -msgid "\"Failed to read\"" +#: src/iterators.md:5 +msgid "[IntoIterator](./iterators/intoiterator.md) (5 minutes)" msgstr "" -#: src/error-handling/error-contexts.md:19 -msgid "\"Found no username in {path}\"" +#: src/iterators.md:6 +msgid "[FromIterator](./iterators/fromiterator.md) (5 minutes)" msgstr "" -#: src/error-handling/error-contexts.md:28 -msgid "\"Error: {err:?}\"" -msgstr "\"Fejl: {err:?}\"" +#: src/iterators.md:7 +msgid "" +"[Exercise: Iterator Method Chaining](./iterators/exercise.md) (30 minutes)" +msgstr "" -#: src/error-handling/error-contexts.md:35 -msgid "`anyhow::Result` is a type alias for `Result`." +#: src/iterators/iterators.md:6 +msgid "" +"The [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait supports iterating over values in a collection. It requires a `next` " +"method and provides lots of methods. Many standard library types implement " +"`Iterator`, and you can implement it yourself, too:" msgstr "" -#: src/error-handling/error-contexts.md:36 +#: src/iterators/iterators.md:30 +msgid "\"fib({i}): {n}\"" +msgstr "\"fib({i}): {n}\"" + +#: src/iterators/iterators.md:38 msgid "" -"`anyhow::Error` is essentially a wrapper around `Box`. As such " -"it's again generally not a good choice for the public API of a library, but " -"is widely used in applications." +"The `Iterator` trait implements many common functional programming " +"operations over collections (e.g. `map`, `filter`, `reduce`, etc). This is " +"the trait where you can find all the documentation about them. In Rust these " +"functions should produce the code as efficient as equivalent imperative " +"implementations." msgstr "" -#: src/error-handling/error-contexts.md:38 +#: src/iterators/iterators.md:43 msgid "" -"Actual error type inside of it can be extracted for examination if necessary." +"`IntoIterator` is the trait that makes for loops work. It is implemented by " +"collection types such as `Vec` and references to them such as `&Vec` " +"and `&[T]`. Ranges also implement it. This is why you can iterate over a " +"vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." msgstr "" -#: src/error-handling/error-contexts.md:39 +#: src/iterators/intoiterator.md:1 +msgid "`IntoIterator`" +msgstr "`IntoIterator`" + +#: src/iterators/intoiterator.md:3 msgid "" -"Functionality provided by `anyhow::Result` may be familiar to Go " -"developers, as it provides similar usage patterns and ergonomics to `(T, " -"error)` from Go." +"The `Iterator` trait tells you how to _iterate_ once you have created an " +"iterator. The related trait [`IntoIterator`](https://doc.rust-lang.org/std/" +"iter/trait.IntoIterator.html) defines how to create an iterator for a type. " +"It is used automatically by the `for` loop." msgstr "" -#: src/testing.md:3 -msgid "Rust and Cargo come with a simple unit test framework:" +#: src/iterators/intoiterator.md:51 +msgid "\"point = {x}, {y}\"" msgstr "" -#: src/testing.md:5 -msgid "Unit tests are supported throughout your code." +#: src/iterators/intoiterator.md:59 +msgid "" +"Click through to the docs for `IntoIterator`. Every implementation of " +"`IntoIterator` must declare two types:" msgstr "" -#: src/testing.md:7 -msgid "Integration tests are supported via the `tests/` directory." +#: src/iterators/intoiterator.md:62 +msgid "`Item`: the type to iterate over, such as `i8`," msgstr "" -#: src/testing/unit-tests.md:3 -msgid "Mark unit tests with `#[test]`:" +#: src/iterators/intoiterator.md:63 +msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." msgstr "" -#: src/testing/unit-tests.md:25 -msgid "\"Hello World\"" -msgstr "\"Hej verden\"" +#: src/iterators/intoiterator.md:65 +msgid "" +"Note that `IntoIter` and `Item` are linked: the iterator must have the same " +"`Item` type, which means that it returns `Option`" +msgstr "" -#: src/testing/unit-tests.md:29 -msgid "Use `cargo test` to find and run the unit tests." +#: src/iterators/intoiterator.md:68 +msgid "The example iterates over all combinations of x and y coordinates." msgstr "" -#: src/testing/test-modules.md:3 +#: src/iterators/intoiterator.md:70 msgid "" -"Unit tests are often put in a nested module (run tests on the [Playground]" -"(https://play.rust-lang.org/)):" +"Try iterating over the grid twice in `main`. Why does this fail? Note that " +"`IntoIterator::into_iter` takes ownership of `self`." msgstr "" -#: src/testing/test-modules.md:8 -msgid "\"{a} {b}\"" -msgstr "\"{a} {b}\"" +#: src/iterators/intoiterator.md:73 +msgid "" +"Fix this issue by implementing `IntoIterator` for `&Grid` and storing a " +"reference to the `Grid` in `GridIter`." +msgstr "" -#: src/testing/test-modules.md:21 -msgid "\"foo bar\"" -msgstr "\"foo bar\"" +#: src/iterators/intoiterator.md:76 +msgid "" +"The same problem can occur for standard library types: `for e in " +"some_vector` will take ownership of `some_vector` and iterate over owned " +"elements from that vector. Use `for e in &some_vector` instead, to iterate " +"over references to elements of `some_vector`." +msgstr "" -#: src/testing/test-modules.md:26 -msgid "This lets you unit test private helpers." +#: src/iterators/fromiterator.md:3 +msgid "" +"[`FromIterator`](https://doc.rust-lang.org/std/iter/trait.FromIterator.html) " +"lets you build a collection from an [`Iterator`](https://doc.rust-lang.org/" +"std/iter/trait.Iterator.html)." msgstr "" -#: src/testing/test-modules.md:27 -msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." +#: src/iterators/fromiterator.md:12 +msgid "\"prime_squares: {prime_squares:?}\"" msgstr "" -#: src/testing/doc-tests.md:3 -msgid "Rust has built-in support for documentation tests:" +#: src/iterators/fromiterator.md:19 +#, fuzzy +msgid "`Iterator` implements" +msgstr "`Iterator`" + +#: src/iterators/fromiterator.md:28 +msgid "There are two ways to specify `B` for this method:" msgstr "" -#: src/testing/doc-tests.md:6 +#: src/iterators/fromiterator.md:30 msgid "" -"/// Shortens a string to the given length.\n" -"///\n" -"/// ```\n" -"/// use playground::shorten_string;\n" -"/// assert_eq!(shorten_string(\"Hello World\", 5), \"Hello\");\n" -"/// assert_eq!(shorten_string(\"Hello World\", 20), \"Hello World\");\n" -"/// ```\n" +"With the \"turbofish\": `some_iterator.collect::()`, as " +"shown. The `_` shorthand used here lets Rust infer the type of the `Vec` " +"elements. " msgstr "" -#: src/testing/doc-tests.md:18 -msgid "Code blocks in `///` comments are automatically seen as Rust code." +#: src/iterators/fromiterator.md:33 +msgid "" +"With type inference: `let prime_squares: Vec<_> = some_iterator.collect()`. " +"Rewrite the example to use this form." msgstr "" -#: src/testing/doc-tests.md:19 -msgid "The code will be compiled and executed as part of `cargo test`." +#: src/iterators/fromiterator.md:36 +msgid "" +"There are basic implementations of `FromIterator` for `Vec`, `HashMap`, etc. " +"There are also more specialized implementations which let you do cool things " +"like convert an `Iterator>` into a `Result, E>`." msgstr "" -#: src/testing/doc-tests.md:20 +#: src/iterators/exercise.md:3 msgid "" -"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" -"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." +"In this exercise, you will need to find and use some of the provided methods " +"in the [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait to implement a complex calculation." msgstr "" -#: src/testing/integration-tests.md:3 -msgid "If you want to test your library as a client, use an integration test." +#: src/iterators/exercise.md:6 +msgid "" +"Copy the following code to and make the tests " +"pass. Use an iterator expression and `collect` the result to construct the " +"return value." msgstr "" -#: src/testing/integration-tests.md:5 -msgid "Create a `.rs` file under `tests/`:" +#: src/iterators/exercise.md:12 src/iterators/solution.md:4 +msgid "" +"/// Calculate the differences between elements of `values` offset by " +"`offset`, wrapping\n" +"/// around from the end of `values` to the beginning.\n" +"///\n" +"/// Element `n` of the result is `values[(n+offset)%len] - values[n]`.\n" msgstr "" -#: src/testing/integration-tests.md:16 -msgid "These tests only have access to the public API of your crate." +#: src/modules.md:4 +msgid "[Modules](./modules/modules.md) (5 minutes)" msgstr "" -#: src/testing/useful-crates.md:1 -msgid "Useful crates for writing tests" +#: src/modules.md:5 +msgid "[Filesystem Hierarchy](./modules/filesystem.md) (5 minutes)" msgstr "" -#: src/testing/useful-crates.md:3 -msgid "Rust comes with only basic support for writing tests." +#: src/modules.md:6 +msgid "[Visibility](./modules/visibility.md) (5 minutes)" msgstr "" -#: src/testing/useful-crates.md:5 -msgid "Here are some additional crates which we recommend for writing tests:" +#: src/modules.md:7 +msgid "[use, super, self](./modules/paths.md) (10 minutes)" msgstr "" -#: src/testing/useful-crates.md:7 +#: src/modules.md:8 msgid "" -"[googletest](https://docs.rs/googletest): Comprehensive test assertion " -"library in the tradition of GoogleTest for C++." +"[Exercise: Modules for the GUI Library](./modules/exercise.md) (20 minutes)" msgstr "" -#: src/testing/useful-crates.md:8 -msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." +#: src/modules/modules.md:3 +msgid "We have seen how `impl` blocks let us namespace functions to a type." msgstr "" -#: src/testing/useful-crates.md:9 -msgid "" -"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " -"tests." +#: src/modules/modules.md:5 +msgid "Similarly, `mod` lets us namespace types and functions:" msgstr "" -#: src/unsafe.md:3 -msgid "The Rust language has two parts:" +#: src/modules/modules.md:10 +msgid "\"In the foo module\"" msgstr "" -#: src/unsafe.md:5 -msgid "**Safe Rust:** memory safe, no undefined behavior possible." +#: src/modules/modules.md:16 +msgid "\"In the bar module\"" msgstr "" -#: src/unsafe.md:6 +#: src/modules/modules.md:29 msgid "" -"**Unsafe Rust:** can trigger undefined behavior if preconditions are " -"violated." +"Packages provide functionality and include a `Cargo.toml` file that " +"describes how to build a bundle of 1+ crates." +msgstr "" + +#: src/modules/modules.md:30 +msgid "" +"Crates are a tree of modules, where a binary crate creates an executable and " +"a library crate compiles to a library." +msgstr "" + +#: src/modules/modules.md:31 +msgid "Modules define organization, scope, and are the focus of this section." +msgstr "" + +#: src/modules/filesystem.md:3 +msgid "" +"Omitting the module content will tell Rust to look for it in another file:" +msgstr "" + +#: src/modules/filesystem.md:9 +msgid "" +"This tells rust that the `garden` module content is found at `src/garden." +"rs`. Similarly, a `garden::vegetables` module can be found at `src/garden/" +"vegetables.rs`." +msgstr "" + +#: src/modules/filesystem.md:12 +msgid "The `crate` root is in:" +msgstr "" + +#: src/modules/filesystem.md:14 +msgid "`src/lib.rs` (for a library crate)" +msgstr "" + +#: src/modules/filesystem.md:15 +msgid "`src/main.rs` (for a binary crate)" +msgstr "" + +#: src/modules/filesystem.md:17 +msgid "" +"Modules defined in files can be documented, too, using \"inner doc " +"comments\". These document the item that contains them -- in this case, a " +"module." +msgstr "" + +#: src/modules/filesystem.md:21 +msgid "" +"//! This module implements the garden, including a highly performant " +"germination\n" +"//! implementation.\n" +msgstr "" + +#: src/modules/filesystem.md:23 +msgid "// Re-export types from this module.\n" +msgstr "" + +#: src/modules/filesystem.md:27 +msgid "/// Sow the given seed packets.\n" +msgstr "" + +#: src/modules/filesystem.md:30 +msgid "/// Harvest the produce in the garden that is ready.\n" +msgstr "" + +#: src/modules/filesystem.md:38 +msgid "" +"Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " +"`module.rs`, and this is still a working alternative for editions after 2018." +msgstr "" + +#: src/modules/filesystem.md:40 +msgid "" +"The main reason to introduce `filename.rs` as alternative to `filename/mod." +"rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." +msgstr "" + +#: src/modules/filesystem.md:43 +msgid "Deeper nesting can use folders, even if the main module is a file:" +msgstr "" + +#: src/modules/filesystem.md:53 +msgid "" +"The place rust will look for modules can be changed with a compiler " +"directive:" +msgstr "" + +#: src/modules/filesystem.md:56 +msgid "\"some/path.rs\"" +msgstr "" + +#: src/modules/filesystem.md:60 +msgid "" +"This is useful, for example, if you would like to place tests for a module " +"in a file named `some_module_test.rs`, similar to the convention in Go." +msgstr "" + +#: src/modules/visibility.md:3 +msgid "Modules are a privacy boundary:" +msgstr "" + +#: src/modules/visibility.md:5 +msgid "Module items are private by default (hides implementation details)." +msgstr "" + +#: src/modules/visibility.md:6 +msgid "Parent and sibling items are always visible." +msgstr "" + +#: src/modules/visibility.md:7 +msgid "" +"In other words, if an item is visible in module `foo`, it's visible in all " +"the descendants of `foo`." +msgstr "" + +#: src/modules/visibility.md:13 +msgid "\"outer::private\"" +msgstr "" + +#: src/modules/visibility.md:17 +msgid "\"outer::public\"" +msgstr "" + +#: src/modules/visibility.md:22 +msgid "\"outer::inner::private\"" +msgstr "" + +#: src/modules/visibility.md:26 +msgid "\"outer::inner::public\"" +msgstr "" + +#: src/modules/visibility.md:40 +msgid "Use the `pub` keyword to make modules public." +msgstr "" + +#: src/modules/visibility.md:42 +msgid "" +"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " +"of public visibility." +msgstr "" + +#: src/modules/visibility.md:44 +msgid "" +"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" +"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." +msgstr "" + +#: src/modules/visibility.md:45 +msgid "Configuring `pub(crate)` visibility is a common pattern." +msgstr "" + +#: src/modules/visibility.md:46 +msgid "Less commonly, you can give visibility to a specific path." +msgstr "" + +#: src/modules/visibility.md:47 +msgid "" +"In any case, visibility must be granted to an ancestor module (and all of " +"its descendants)." +msgstr "" + +#: src/modules/paths.md:3 +msgid "" +"A module can bring symbols from another module into scope with `use`. You " +"will typically see something like this at the top of each module:" +msgstr "" + +#: src/modules/paths.md:11 +msgid "Paths" +msgstr "" + +#: src/modules/paths.md:13 +msgid "Paths are resolved as follows:" +msgstr "" + +#: src/modules/paths.md:15 +msgid "As a relative path:" +msgstr "" + +#: src/modules/paths.md:16 +msgid "`foo` or `self::foo` refers to `foo` in the current module," +msgstr "" + +#: src/modules/paths.md:17 +msgid "`super::foo` refers to `foo` in the parent module." +msgstr "" + +#: src/modules/paths.md:19 +msgid "As an absolute path:" +msgstr "" + +#: src/modules/paths.md:20 +msgid "`crate::foo` refers to `foo` in the root of the current crate," +msgstr "" + +#: src/modules/paths.md:21 +msgid "`bar::foo` refers to `foo` in the `bar` crate." +msgstr "" + +#: src/modules/paths.md:26 +msgid "" +"It is common to \"re-export\" symbols at a shorter path. For example, the " +"top-level `lib.rs` in a crate might have" +msgstr "" + +#: src/modules/paths.md:36 +msgid "" +"making `DiskStorage` and `NetworkStorage` available to other crates with a " +"convenient, short path." +msgstr "" + +#: src/modules/paths.md:39 +msgid "" +"For the most part, only items that appear in a module need to be `use`'d. " +"However, a trait must be in scope to call any methods on that trait, even if " +"a type implementing that trait is already in scope. For example, to use the " +"`read_to_string` method on a type implementing the `Read` trait, you need to " +"`use std::io::Read`." +msgstr "" + +#: src/modules/paths.md:45 +msgid "" +"The `use` statement can have a wildcard: `use std::io::*`. This is " +"discouraged because it is not clear which items are imported, and those " +"might change over time." +msgstr "" + +#: src/modules/exercise.md:3 +msgid "" +"In this exercise, you will reorganize the GUI Library exercise from the " +"\"Methods and Traits\" segment of the course into a collection of modules. " +"It is typical to put each type or set of closely-related types into its own " +"module, so each widget type should get its own module." +msgstr "" + +#: src/modules/exercise.md:8 +msgid "" +"If you no longer have your version, that's fine - refer back to the " +"[provided solution](../methods-and-traits/solution.html)." +msgstr "" + +#: src/modules/exercise.md:11 +msgid "Cargo Setup" +msgstr "" + +#: src/modules/exercise.md:13 +msgid "" +"The Rust playground only supports one file, so you will need to make a Cargo " +"project on your local filesystem:" +msgstr "" + +#: src/modules/exercise.md:22 +msgid "" +"Edit `src/main.rs` to add `mod` statements, and add additional files in the " +"`src` directory." +msgstr "" + +#: src/modules/exercise.md:28 +msgid "" +"Encourage students to divide the code in a way that feels natural for them, " +"and get accustomed to the required `mod`, `use`, and `pub` declarations. " +"Afterward, discuss what organizations are most idiomatic." +msgstr "" + +#: src/modules/solution.md:20 +msgid "// ---- src/widgets.rs ----\n" +msgstr "" + +#: src/modules/solution.md:42 +msgid "// ---- src/widgets/label.rs ----\n" +msgstr "" + +#: src/modules/solution.md:59 +#, fuzzy +msgid "// ANCHOR_END: Label-width\n" +msgstr "// ANCHOR_END: Uart\n" + +#: src/modules/solution.md:67 +#, fuzzy +msgid "// ANCHOR: Label-draw_into\n" +msgstr "// ANCHOR: main\n" + +#: src/modules/solution.md:69 +#, fuzzy +msgid "// ANCHOR_END: Label-draw_into\n" +msgstr "// ANCHOR_END: Uart\n" + +#: src/modules/solution.md:76 +msgid "// ---- src/widgets/button.rs ----\n" +msgstr "" + +#: src/modules/solution.md:93 +#, fuzzy +msgid "// ANCHOR_END: Button-width\n" +msgstr "// ANCHOR_END: Uart\n" + +#: src/modules/solution.md:97 +#, fuzzy +msgid "// ANCHOR: Button-draw_into\n" +msgstr "// ANCHOR: main\n" + +#: src/modules/solution.md:99 +#, fuzzy +msgid "// ANCHOR_END: Button-draw_into\n" +msgstr "// ANCHOR_END: Uart\n" + +#: src/modules/solution.md:114 +msgid "// ---- src/widgets/window.rs ----\n" +msgstr "" + +#: src/modules/solution.md:144 +msgid "" +"// ANCHOR_END: Window-width\n" +" // Add 4 paddings for borders\n" +msgstr "" + +#: src/modules/solution.md:149 +#, fuzzy +msgid "// ANCHOR: Window-draw_into\n" +msgstr "// ANCHOR: main\n" + +#: src/modules/solution.md:151 +#, fuzzy +msgid "// ANCHOR_END: Window-draw_into\n" +msgstr "// ANCHOR_END: Uart\n" + +#: src/modules/solution.md:174 +msgid "// ---- src/main.rs ----\n" +msgstr "" + +#: src/testing.md:4 +msgid "[Test Modules](./testing/unit-tests.md) (5 minutes)" +msgstr "" + +#: src/testing.md:5 +msgid "[Other Types of Tests](./testing/other.md) (10 minutes)" +msgstr "" + +#: src/testing.md:6 +msgid "[Useful Crates](./testing/useful-crates.md) (3 minutes)" +msgstr "" + +#: src/testing.md:7 +msgid "[GoogleTest](./testing/googletest.md) (5 minutes)" +msgstr "" + +#: src/testing.md:8 +msgid "[Compiler lints and Clippy](./testing/lints.md) (5 minutes)" +msgstr "" + +#: src/testing.md:9 +msgid "[Exercise: Luhn Algorithm](./testing/exercise.md) (30 minutes)" +msgstr "" + +#: src/testing/unit-tests.md:1 +msgid "Unit Tests" +msgstr "" + +#: src/testing/unit-tests.md:3 +msgid "Rust and Cargo come with a simple unit test framework:" +msgstr "" + +#: src/testing/unit-tests.md:5 +msgid "Unit tests are supported throughout your code." +msgstr "" + +#: src/testing/unit-tests.md:7 +msgid "Integration tests are supported via the `tests/` directory." +msgstr "" + +#: src/testing/unit-tests.md:9 +msgid "" +"Tests are marked with `#[test]`. Unit tests are often put in a nested " +"`tests` module, using `#[cfg(test)]` to conditionally compile them only when " +"building tests." +msgstr "" + +#: src/testing/unit-tests.md:37 +msgid "\"Hello World\"" +msgstr "\"Hej verden\"" + +#: src/testing/unit-tests.md:42 +msgid "This lets you unit test private helpers." +msgstr "" + +#: src/testing/unit-tests.md:43 +msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." +msgstr "" + +#: src/testing/unit-tests.md:48 +msgid "Run the tests in the playground in order to show their results." +msgstr "" + +#: src/testing/other.md:3 +msgid "Integration Tests" +msgstr "" + +#: src/testing/other.md:5 +msgid "If you want to test your library as a client, use an integration test." +msgstr "" + +#: src/testing/other.md:7 +msgid "Create a `.rs` file under `tests/`:" +msgstr "" + +#: src/testing/other.md:10 +msgid "// tests/my_library.rs\n" +msgstr "" + +#: src/testing/other.md:19 +msgid "These tests only have access to the public API of your crate." +msgstr "" + +#: src/testing/other.md:21 +msgid "Documentation Tests" +msgstr "" + +#: src/testing/other.md:23 +msgid "Rust has built-in support for documentation tests:" +msgstr "" + +#: src/testing/other.md:26 +msgid "" +"/// Shortens a string to the given length.\n" +"///\n" +"/// ```\n" +"/// # use playground::shorten_string;\n" +"/// assert_eq!(shorten_string(\"Hello World\", 5), \"Hello\");\n" +"/// assert_eq!(shorten_string(\"Hello World\", 20), \"Hello World\");\n" +"/// ```\n" +msgstr "" + +#: src/testing/other.md:38 +msgid "Code blocks in `///` comments are automatically seen as Rust code." +msgstr "" + +#: src/testing/other.md:39 +msgid "The code will be compiled and executed as part of `cargo test`." +msgstr "" + +#: src/testing/other.md:40 +msgid "" +"Adding `# ` in the code will hide it from the docs, but will still compile/" +"run it." +msgstr "" + +#: src/testing/other.md:41 +msgid "" +"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" +"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." +msgstr "" + +#: src/testing/useful-crates.md:3 +msgid "Rust comes with only basic support for writing tests." +msgstr "" + +#: src/testing/useful-crates.md:5 +msgid "Here are some additional crates which we recommend for writing tests:" +msgstr "" + +#: src/testing/useful-crates.md:7 +msgid "" +"[googletest](https://docs.rs/googletest): Comprehensive test assertion " +"library in the tradition of GoogleTest for C++." +msgstr "" + +#: src/testing/useful-crates.md:8 +msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." +msgstr "" + +#: src/testing/useful-crates.md:9 +msgid "" +"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " +"tests." +msgstr "" + +#: src/testing/googletest.md:3 +msgid "" +"The [GoogleTest](https://docs.rs/googletest/) crate allows for flexible test " +"assertions using _matchers_:" +msgstr "" + +#: src/testing/googletest.md:11 +msgid "\"baz\"" +msgstr "" + +#: src/testing/googletest.md:12 +msgid "\"xyz\"" +msgstr "" + +#: src/testing/googletest.md:16 +msgid "" +"If we change the last element to `\"!\"`, the test fails with a structured " +"error message pin-pointing the error:" +msgstr "" + +#: src/testing/googletest.md:37 +msgid "" +"GoogleTest is not part of the Rust Playground, so you need to run this " +"example in a local environment. Use `cargo add googletest` to quickly add it " +"to an existing Cargo project." +msgstr "" + +#: src/testing/googletest.md:41 +msgid "" +"The `use googletest::prelude::*;` line imports a number of [commonly used " +"macros and types](https://docs.rs/googletest/latest/googletest/prelude/index." +"html)." +msgstr "" + +#: src/testing/googletest.md:44 +msgid "This just scratches the surface, there are many builtin matchers." +msgstr "" + +#: src/testing/googletest.md:46 +msgid "" +"A particularly nice feature is that mismatches in multi-line strings strings " +"are shown as a diff:" +msgstr "" + +#: src/testing/googletest.md:52 +msgid "" +"\"Memory safety found,\\n\\\n" +" Rust's strong typing guides the way,\\n\\\n" +" Secure code you'll write.\"" +msgstr "" + +#: src/testing/googletest.md:57 +msgid "" +"\"Memory safety found,\\n\\\n" +" Rust's silly humor guides the way,\\n\\\n" +" Secure code you'll write.\"" +msgstr "" + +#: src/testing/googletest.md:64 +msgid "shows a color-coded diff (colors not shown here):" +msgstr "" + +#: src/testing/googletest.md:80 +msgid "" +"The crate is a Rust port of [GoogleTest for C++](https://google.github.io/" +"googletest/)." +msgstr "" + +#: src/testing/googletest.md:85 +msgid "GoogleTest is available for use in AOSP." +msgstr "" + +#: src/testing/lints.md:1 +msgid "Compiler Lints and Clippy" +msgstr "" + +#: src/testing/lints.md:3 +msgid "" +"The Rust compiler produces fantastic error messages, as well as helpful " +"built-in lints. [Clippy](https://doc.rust-lang.org/clippy/) provides even " +"more lints, organized into groups that can be enabled per-project." +msgstr "" + +#: src/testing/lints.md:14 +msgid "\"X probably fits in a u16, right? {}\"" +msgstr "" + +#: src/testing/lints.md:21 +msgid "" +"Run the code sample and examine the error message. There are also lints " +"visible here, but those will not be shown once the code compiles. Switch to " +"the Playground site to show those lints." +msgstr "" + +#: src/testing/lints.md:25 +msgid "" +"After resolving the lints, run `clippy` on the playground site to show " +"clippy warnings. Clippy has extensive documentation of its lints, and adds " +"new lints (including default-deny lints) all the time." +msgstr "" + +#: src/testing/lints.md:29 +msgid "" +"Note that errors or warnings with `help: ...` can be fixed with `cargo fix` " +"or via your editor." +msgstr "" + +#: src/testing/exercise.md:3 +msgid "Luhn Algorithm" +msgstr "Luhn-algorithmen" + +#: src/testing/exercise.md:5 +msgid "" +"The [Luhn algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is used " +"to validate credit card numbers. The algorithm takes a string as input and " +"does the following to validate the credit card number:" +msgstr "" + +#: src/testing/exercise.md:9 +msgid "Ignore all spaces. Reject number with less than two digits." +msgstr "" + +#: src/testing/exercise.md:11 +msgid "" +"Moving from **right to left**, double every second digit: for the number " +"`1234`, we double `3` and `1`. For the number `98765`, we double `6` and `8`." +msgstr "" + +#: src/testing/exercise.md:14 +msgid "" +"After doubling a digit, sum the digits if the result is greater than 9. So " +"doubling `7` becomes `14` which becomes `1 + 4 = 5`." +msgstr "" + +#: src/testing/exercise.md:17 +msgid "Sum all the undoubled and doubled digits." +msgstr "" + +#: src/testing/exercise.md:19 +msgid "The credit card number is valid if the sum ends with `0`." +msgstr "" + +#: src/testing/exercise.md:21 +msgid "" +"The provided code provides a buggy implementation of the luhn algorithm, " +"along with two basic unit tests that confirm that most the algorithm is " +"implemented correctly." +msgstr "" + +#: src/testing/exercise.md:25 +msgid "" +"Copy the code below to and write additional " +"tests to uncover bugs in the provided implementation, fixing any bugs you " +"find." +msgstr "" + +#: src/testing/exercise.md:60 src/testing/solution.md:75 +msgid "\"4263 9826 4026 9299\"" +msgstr "\"4263 9826 4026 9299\"" + +#: src/testing/exercise.md:61 src/testing/solution.md:76 +msgid "\"4539 3195 0343 6467\"" +msgstr "\"4539 3195 0343 6467\"" + +#: src/testing/exercise.md:62 src/testing/solution.md:77 +msgid "\"7992 7398 713\"" +msgstr "\"7992 7398 713\"" + +#: src/testing/exercise.md:67 src/testing/solution.md:82 +msgid "\"4223 9826 4026 9299\"" +msgstr "\"4223 9826 4026 9299\"" + +#: src/testing/exercise.md:68 src/testing/solution.md:83 +msgid "\"4539 3195 0343 6476\"" +msgstr "\"4539 3195 0343 6476\"" + +#: src/testing/exercise.md:69 src/testing/solution.md:84 +msgid "\"8273 1232 7352 0569\"" +msgstr "\"8273 1232 7352 0569\"" + +#: src/testing/solution.md:4 +msgid "// This is the buggy version that appears in the problem.\n" +msgstr "" + +#: src/testing/solution.md:30 +msgid "// This is the solution and passes all of the tests below.\n" +msgstr "" + +#: src/testing/solution.md:62 +msgid "\"1234 5678 1234 5670\"" +msgstr "\"1234 5678 1234 5670\"" + +#: src/testing/solution.md:64 +msgid "\"Is {cc_number} a valid credit card number? {}\"" +msgstr "\"Er {cc_number} et gyldigt kreditkortnummer? {}\"" + +#: src/testing/solution.md:65 +msgid "\"yes\"" +msgstr "\"ja\"" + +#: src/testing/solution.md:65 +msgid "\"no\"" +msgstr "\"nej\"" + +#: src/testing/solution.md:90 +msgid "\"foo 0 0\"" +msgstr "\"foo 0 0\"" + +#: src/testing/solution.md:96 +msgid "\" \"" +msgstr "\" \"" + +#: src/testing/solution.md:97 +msgid "\" \"" +msgstr "\" \"" + +#: src/testing/solution.md:98 +msgid "\" \"" +msgstr "\" \"" + +#: src/testing/solution.md:103 +msgid "\"0\"" +msgstr "\"0\"" + +#: src/testing/solution.md:108 +msgid "\" 0 0 \"" +msgstr "\" 0 0 \"" + +#: src/welcome-day-4-afternoon.md:4 +msgid "[Error Handling](./error-handling.md) (45 minutes)" +msgstr "" + +#: src/welcome-day-4-afternoon.md:5 +msgid "[Unsafe Rust](./unsafe-rust.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/welcome-day-4-afternoon.md:7 +msgid "Including 10 minute breaks, this session should take about 2 hours" +msgstr "" + +#: src/error-handling.md:4 +msgid "[Panics](./error-handling/panics.md) (3 minutes)" +msgstr "" + +#: src/error-handling.md:5 +msgid "[Try operator](./error-handling/try.md) (5 minutes)" +msgstr "" + +#: src/error-handling.md:6 +msgid "[Try Conversions](./error-handling/try-conversions.md) (5 minutes)" +msgstr "" + +#: src/error-handling.md:7 +msgid "[Error Trait](./error-handling/error.md) (5 minutes)" +msgstr "" + +#: src/error-handling.md:8 +msgid "" +"[thiserror and anyhow](./error-handling/thiserror-and-anyhow.md) (5 minutes)" +msgstr "" + +#: src/error-handling.md:9 +msgid "" +"[Exercise: Rewriting with Result](./error-handling/exercise.md) (20 minutes)" +msgstr "" + +#: src/error-handling/panics.md:3 +msgid "Rust handles fatal errors with a \"panic\"." +msgstr "" + +#: src/error-handling/panics.md:5 +msgid "Rust will trigger a panic if a fatal error happens at runtime:" +msgstr "" + +#: src/error-handling/panics.md:10 +msgid "\"v[100]: {}\"" +msgstr "\"v[100]: {}\"" + +#: src/error-handling/panics.md:14 +msgid "Panics are for unrecoverable and unexpected errors." +msgstr "" + +#: src/error-handling/panics.md:15 +msgid "Panics are symptoms of bugs in the program." +msgstr "" + +#: src/error-handling/panics.md:16 +msgid "Runtime failures like failed bounds checks can panic" +msgstr "" + +#: src/error-handling/panics.md:17 +msgid "Assertions (such as `assert!`) panic on failure" +msgstr "" + +#: src/error-handling/panics.md:18 +msgid "Purpose-specific panics can use the `panic!` macro." +msgstr "" + +#: src/error-handling/panics.md:19 +msgid "" +"A panic will \"unwind\" the stack, dropping values just as if the functions " +"had returned." +msgstr "" + +#: src/error-handling/panics.md:20 +msgid "" +"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." +msgstr "" + +#: src/error-handling/panics.md:25 +msgid "" +"By default, a panic will cause the stack to unwind. The unwinding can be " +"caught:" +msgstr "" + +#: src/error-handling/panics.md:32 +msgid "\"No problem here!\"" +msgstr "" + +#: src/error-handling/panics.md:34 src/error-handling/panics.md:39 +#, fuzzy +msgid "\"{result:?}\"" +msgstr "\"result: {:?}\"" + +#: src/error-handling/panics.md:37 +msgid "\"oh no!\"" +msgstr "\"åh nej!\"" + +#: src/error-handling/panics.md:43 +msgid "" +"Catching is unusual; do not attempt to implement exceptions with " +"`catch_unwind`!" +msgstr "" + +#: src/error-handling/panics.md:44 +msgid "" +"This can be useful in servers which should keep running even if a single " +"request crashes." +msgstr "" + +#: src/error-handling/panics.md:46 +msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." +msgstr "" + +#: src/error-handling/try.md:1 +msgid "Try Operator" +msgstr "" + +#: src/error-handling/try.md:3 +msgid "" +"Runtime errors like connection-refused or file-not-found are handled with " +"the `Result` type, but matching this type on every call can be cumbersome. " +"The try-operator `?` is used to return errors to the caller. It lets you " +"turn the common" +msgstr "" + +#: src/error-handling/try.md:15 +msgid "into the much simpler" +msgstr "" + +#: src/error-handling/try.md:21 +msgid "We can use this to simplify our error handling code:" +msgstr "" + +#: src/error-handling/try.md:42 +msgid "//fs::write(\"config.dat\", \"alice\").unwrap();\n" +msgstr "//fs::write(\"config.dat\", \"alice\").unwrap();\n" + +#: src/error-handling/try.md:43 src/error-handling/try-conversions.md:64 +#: src/error-handling/thiserror-and-anyhow.md:31 +msgid "\"config.dat\"" +msgstr "\"config.dat\"" + +#: src/error-handling/try.md:44 src/error-handling/try-conversions.md:65 +msgid "\"username or error: {username:?}\"" +msgstr "" + +#: src/error-handling/try.md:51 +msgid "Simplify the `read_username` function to use `?`." +msgstr "" + +#: src/error-handling/try.md:55 +msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." +msgstr "" + +#: src/error-handling/try.md:56 +msgid "" +"Use the `fs::write` call to test out the different scenarios: no file, empty " +"file, file with username." +msgstr "" + +#: src/error-handling/try.md:57 +msgid "" +"Note that `main` can return a `Result<(), E>` as long as it implements `std::" +"process:Termination`. In practice, this means that `E` implements `Debug`. " +"The executable will print the `Err` variant and return a nonzero exit status " +"on error." +msgstr "" + +#: src/error-handling/try-conversions.md:3 +msgid "" +"The effective expansion of `?` is a little more complicated than previously " +"indicated:" +msgstr "" + +#: src/error-handling/try-conversions.md:9 +msgid "works the same as" +msgstr "" + +#: src/error-handling/try-conversions.md:18 +msgid "" +"The `From::from` call here means we attempt to convert the error type to the " +"type returned by the function. This makes it easy to encapsulate errors into " +"higher-level errors." +msgstr "" + +#: src/error-handling/try-conversions.md:41 +msgid "\"IO error: {e}\"" +msgstr "\"IO-fejl: {e}\"" + +#: src/error-handling/try-conversions.md:42 +msgid "\"Found no username in {filename}\"" +msgstr "" + +#: src/error-handling/try-conversions.md:63 +#: src/error-handling/thiserror-and-anyhow.md:30 +msgid "//fs::write(\"config.dat\", \"\").unwrap();\n" +msgstr "//fs::write(\"config.dat\", \"\").unwrap();\n" + +#: src/error-handling/try-conversions.md:72 +msgid "" +"The return type of the function has to be compatible with the nested " +"functions it calls. For instance, a function returning a `Result` " +"can only apply the `?` operator on a function returning a `Result`. It cannot apply the `?` operator on a function returning an " +"`Option` or `Result` unless `OtherErr` implements " +"`From`. Reciprocally, a function returning an `Option` can only " +"apply the `?` operator on a function returning an `Option`." +msgstr "" + +#: src/error-handling/try-conversions.md:78 +msgid "" +"You can convert incompatible types into one another with the different " +"`Option` and `Result` methods such as `Option::ok_or`, `Result::ok`, " +"`Result::err`." +msgstr "" + +#: src/error-handling/try-conversions.md:82 +msgid "" +"It is good practice for all error types that don't need to be `no_std` to " +"implement `std::error::Error`, which requires `Debug` and `Display`. The " +"`Error` crate for `core` is only available in [nightly](https://github.com/" +"rust-lang/rust/issues/103765), so not fully `no_std` compatible yet." +msgstr "" + +#: src/error-handling/try-conversions.md:84 +msgid "" +"It's generally helpful for them to implement `Clone` and `Eq` too where " +"possible, to make life easier for tests and consumers of your library. In " +"this case we can't easily do so, because `io::Error` doesn't implement them." +msgstr "" + +#: src/error-handling/try-conversions.md:88 +msgid "" +"A common alternative to a `From` implementation is `Result::map_err`, " +"especially when the conversion only happens in one place." +msgstr "" + +#: src/error-handling/error.md:1 +msgid "Dynamic Error Types" +msgstr "" + +#: src/error-handling/error.md:3 +msgid "" +"Sometimes we want to allow any type of error to be returned without writing " +"our own enum covering all the different possibilities. The `std::error::" +"Error` trait makes it easy to create a trait object that can contain any " +"error." +msgstr "" + +#: src/error-handling/error.md:20 src/error-handling/error.md:21 +#, fuzzy +msgid "\"count.dat\"" +msgstr "\"config.dat\"" + +#: src/error-handling/error.md:20 +msgid "\"1i3\"" +msgstr "" + +#: src/error-handling/error.md:22 +#, fuzzy +msgid "\"Count: {count}\"" +msgstr "\"count: {}\"" + +#: src/error-handling/error.md:23 +msgid "\"Error: {err}\"" +msgstr "\"Fejl: {err}\"" + +#: src/error-handling/error.md:31 +msgid "" +"The `read_count` function can return `std::io::Error` (from file operations) " +"or `std::num::ParseIntError` (from `String::parse`)." +msgstr "" + +#: src/error-handling/error.md:34 +msgid "" +"Boxing errors saves on code, but gives up the ability to cleanly handle " +"different error cases differently in the program. As such it's generally not " +"a good idea to use `Box` in the public API of a library, but it " +"can be a good option in a program where you just want to display the error " +"message somewhere." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:1 +#, fuzzy +msgid "`thiserror` and `anyhow`" +msgstr "`From` og `Into`" + +#: src/error-handling/thiserror-and-anyhow.md:3 +msgid "" +"The [`thiserror`](https://docs.rs/thiserror/) and [`anyhow`](https://docs." +"rs/anyhow/) crates are widley used to simplify error handling. `thiserror` " +"helps create custom error types that implement `From`. `anyhow` helps " +"with error handling in functions, including adding contextual information to " +"your errors." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:14 +msgid "\"Found no username in {0}\"" +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:20 +msgid "\"Failed to open {path}\"" +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:22 +msgid "\"Failed to read\"" +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:32 +msgid "\"Username: {username}\"" +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:33 +msgid "\"Error: {err:?}\"" +msgstr "\"Fejl: {err:?}\"" + +#: src/error-handling/thiserror-and-anyhow.md:41 +msgid "" +"The `Error` derive macro is provided by `thiserror`, and has lots of useful " +"attributes like `#[error]` to help define a useful error type." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:43 +msgid "`anyhow::Result` is a type alias for `Result`." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:44 +msgid "" +"`anyhow::Error` is essentially a wrapper around `Box`. As such " +"it's again generally not a good choice for the public API of a library, but " +"is widely used in applications." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:46 +msgid "" +"Actual error type inside of it can be extracted for examination if necessary." +msgstr "" + +#: src/error-handling/thiserror-and-anyhow.md:47 +msgid "" +"Functionality provided by `anyhow::Result` may be familiar to Go " +"developers, as it provides similar usage patterns and ergonomics to `(T, " +"error)` from Go." +msgstr "" + +#: src/error-handling/exercise.md:3 +msgid "" +"The following implements a very simple parser for an expression language. " +"However, it handles errors by panicking. Rewrite it to instead use idiomatic " +"error handling and propagate errors to a return from `main`. Feel free to " +"use `thiserror` and `anyhow`." +msgstr "" + +#: src/error-handling/exercise.md:8 +msgid "" +"HINT: start by fixing error handling in the `parse` function. Once that is " +"working correctly, update `Tokenizer` to implement " +"`Iterator>` and handle that in the parser." +msgstr "" + +#: src/error-handling/exercise.md:15 src/error-handling/solution.md:8 +#, fuzzy +msgid "/// An arithmetic operator.\n" +msgstr "/// Parity error.\n" + +#: src/error-handling/exercise.md:22 src/error-handling/solution.md:15 +msgid "/// A token in the expression language.\n" +msgstr "" + +#: src/error-handling/exercise.md:30 src/error-handling/solution.md:23 +msgid "/// An expression in the expression language.\n" +msgstr "" + +#: src/error-handling/exercise.md:34 src/error-handling/solution.md:27 +msgid "/// A reference to a variable.\n" +msgstr "" + +#: src/error-handling/exercise.md:36 src/error-handling/solution.md:29 +#, fuzzy +msgid "/// A literal number.\n" +msgstr "/// Analyze the numbers.\n" + +#: src/error-handling/exercise.md:38 src/error-handling/solution.md:31 +#, fuzzy +msgid "/// A binary operation.\n" +msgstr "/// Parity error.\n" + +#: src/error-handling/exercise.md:64 src/error-handling/exercise.md:66 +#: src/error-handling/solution.md:63 src/error-handling/solution.md:65 +#, fuzzy +msgid "'z'" +msgstr "'x'" + +#: src/error-handling/exercise.md:66 src/error-handling/solution.md:65 +#, fuzzy +msgid "'_'" +msgstr "'x'" + +#: src/error-handling/exercise.md:72 src/error-handling/solution.md:71 +#, fuzzy +msgid "'+'" +msgstr "'x'" + +#: src/error-handling/exercise.md:73 src/error-handling/solution.md:72 +#, fuzzy +msgid "'-'" +msgstr "'x'" + +#: src/error-handling/exercise.md:74 +msgid "\"Unexpected character {c}\"" +msgstr "" + +#: src/error-handling/exercise.md:84 src/error-handling/solution.md:82 +msgid "\"Unexpected end of input\"" +msgstr "" + +#: src/error-handling/exercise.md:88 +msgid "\"Invalid 32-bit integer'\"" +msgstr "" + +#: src/error-handling/exercise.md:92 src/error-handling/exercise.md:100 +msgid "\"Unexpected token {tok:?}\"" +msgstr "" + +#: src/error-handling/exercise.md:94 src/error-handling/solution.md:105 +msgid "// Look ahead to parse a binary operation if present.\n" +msgstr "" + +#: src/error-handling/exercise.md:108 src/error-handling/solution.md:120 +msgid "\"10+foo+20-30\"" +msgstr "" + +#: src/error-handling/exercise.md:109 src/error-handling/solution.md:121 +#, fuzzy +msgid "\"{expr:?}\"" +msgstr "\"expr: {:?}\"" + +#: src/error-handling/solution.md:41 +msgid "\"Unexpected character '{0}' in input\"" +msgstr "" + +#: src/error-handling/solution.md:80 +#, fuzzy +msgid "\"Tokenizer error: {0}\"" +msgstr "\"IO-fejl: {e}\"" + +#: src/error-handling/solution.md:84 +msgid "\"Unexpected token {0:?}\"" +msgstr "" + +#: src/error-handling/solution.md:86 +#, fuzzy +msgid "\"Invalid number\"" +msgstr "\"analyze_numbers\"" + +#: src/unsafe-rust.md:4 +msgid "[Unsafe](./unsafe-rust/unsafe.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md:5 +msgid "" +"[Dereferencing Raw Pointers](./unsafe-rust/dereferencing.md) (10 minutes)" +msgstr "" + +#: src/unsafe-rust.md:6 +msgid "[Mutable Static Variables](./unsafe-rust/mutable-static.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md:7 +msgid "[Unions](./unsafe-rust/unions.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md:8 +msgid "[Unsafe Functions](./unsafe-rust/unsafe-functions.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md:9 +msgid "[Unsafe Traits](./unsafe-rust/unsafe-traits.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md:10 +msgid "[Exercise: FFI Wrapper](./unsafe-rust/exercise.md) (30 minutes)" +msgstr "" + +#: src/unsafe-rust/unsafe.md:3 +msgid "The Rust language has two parts:" +msgstr "" + +#: src/unsafe-rust/unsafe.md:5 +msgid "**Safe Rust:** memory safe, no undefined behavior possible." +msgstr "" + +#: src/unsafe-rust/unsafe.md:6 +msgid "" +"**Unsafe Rust:** can trigger undefined behavior if preconditions are " +"violated." +msgstr "" + +#: src/unsafe-rust/unsafe.md:8 +msgid "" +"We saw mostly safe Rust in this course, but it's important to know what " +"Unsafe Rust is." +msgstr "" + +#: src/unsafe-rust/unsafe.md:11 +msgid "" +"Unsafe code is usually small and isolated, and its correctness should be " +"carefully documented. It is usually wrapped in a safe abstraction layer." +msgstr "" + +#: src/unsafe-rust/unsafe.md:14 +msgid "Unsafe Rust gives you access to five new capabilities:" +msgstr "" + +#: src/unsafe-rust/unsafe.md:16 +msgid "Dereference raw pointers." +msgstr "" + +#: src/unsafe-rust/unsafe.md:17 +msgid "Access or modify mutable static variables." +msgstr "" + +#: src/unsafe-rust/unsafe.md:18 +msgid "Access `union` fields." +msgstr "" + +#: src/unsafe-rust/unsafe.md:19 +msgid "Call `unsafe` functions, including `extern` functions." +msgstr "" + +#: src/unsafe-rust/unsafe.md:20 +msgid "Implement `unsafe` traits." +msgstr "" + +#: src/unsafe-rust/unsafe.md:22 +msgid "" +"We will briefly cover unsafe capabilities next. For full details, please see " +"[Chapter 19.1 in the Rust Book](https://doc.rust-lang.org/book/ch19-01-" +"unsafe-rust.html) and the [Rustonomicon](https://doc.rust-lang.org/nomicon/)." +msgstr "" + +#: src/unsafe-rust/unsafe.md:29 +msgid "" +"Unsafe Rust does not mean the code is incorrect. It means that developers " +"have turned off some compiler safety features and have to write correct code " +"by themselves. It means the compiler no longer enforces Rust's memory-safety " +"rules." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:3 +msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:7 +msgid "\"careful!\"" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:12 +msgid "" +"// Safe because r1 and r2 were obtained from references and so are\n" +" // guaranteed to be non-null and properly aligned, the objects " +"underlying\n" +" // the references from which they were obtained are live throughout the\n" +" // whole unsafe block, and they are not accessed either through the\n" +" // references or concurrently through any other pointers.\n" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:18 +msgid "\"r1 is: {}\"" +msgstr "\"r1 er: {}\"" + +#: src/unsafe-rust/dereferencing.md:19 +msgid "\"uhoh\"" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:20 +msgid "\"r2 is: {}\"" +msgstr "\"r2 er: {}\"" + +#: src/unsafe-rust/dereferencing.md:23 +msgid "" +"// NOT SAFE. DO NOT DO THIS.\n" +" /*\n" +" let r3: &String = unsafe { &*r1 };\n" +" drop(s);\n" +" println!(\"r3 is: {}\", *r3);\n" +" */" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:35 +msgid "" +"It is good practice (and required by the Android Rust style guide) to write " +"a comment for each `unsafe` block explaining how the code inside it " +"satisfies the safety requirements of the unsafe operations it is doing." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:39 +msgid "" +"In the case of pointer dereferences, this means that the pointers must be " +"[_valid_](https://doc.rust-lang.org/std/ptr/index.html#safety), i.e.:" +msgstr "" + +#: src/unsafe-rust/dereferencing.md:42 +msgid "The pointer must be non-null." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:43 +msgid "" +"The pointer must be _dereferenceable_ (within the bounds of a single " +"allocated object)." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:44 +msgid "The object must not have been deallocated." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:45 +msgid "There must not be concurrent accesses to the same location." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:46 +msgid "" +"If the pointer was obtained by casting a reference, the underlying object " +"must be live and no reference may be used to access the memory." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:49 +msgid "In most cases the pointer must also be properly aligned." +msgstr "" + +#: src/unsafe-rust/dereferencing.md:51 +msgid "" +"The \"NOT SAFE\" sectoin gives an example of a common kind of UB bug: `*r1` " +"has the `'static` lifetime, so `r3` has type `&'static String`, and thus " +"outlives `s`. Creating a reference from a pointer requires _great care_." +msgstr "" + +#: src/unsafe-rust/mutable-static.md:3 +msgid "It is safe to read an immutable static variable:" +msgstr "" + +#: src/unsafe-rust/mutable-static.md:6 +msgid "\"Hello, world!\"" +msgstr "\"Hej verden!\"" + +#: src/unsafe-rust/mutable-static.md:9 +msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" +msgstr "\"HELLO_WORLD: {HELLO_WORLD}\"" + +#: src/unsafe-rust/mutable-static.md:13 +msgid "" +"However, since data races can occur, it is unsafe to read and write mutable " +"static variables:" +msgstr "" + +#: src/unsafe-rust/mutable-static.md:20 src/unsafe-rust/mutable-static.md:26 +msgid "// Potential data race!\n" +msgstr "" + +#: src/unsafe-rust/mutable-static.md:26 +msgid "\"COUNTER: {COUNTER}\"" +msgstr "\"COUNTER: {COUNTER}\"" + +#: src/unsafe-rust/mutable-static.md:33 +msgid "" +"The program here is safe because it is single-threaded. However, the Rust " +"compiler is conservative and will assume the worst. Try removing the " +"`unsafe` and see how the compiler explains that it is undefined behavior to " +"mutate a static from multiple threads." +msgstr "" + +#: src/unsafe-rust/mutable-static.md:37 +msgid "" +"Using a mutable static is generally a bad idea, but there are some cases " +"where it might make sense in low-level `no_std` code, such as implementing a " +"heap allocator or working with some C APIs." +msgstr "" + +#: src/unsafe-rust/unions.md:3 +msgid "Unions are like enums, but you need to track the active field yourself:" +msgstr "" + +#: src/unsafe-rust/unions.md:14 +msgid "\"int: {}\"" +msgstr "\"int: {}\"" + +#: src/unsafe-rust/unions.md:15 +msgid "\"bool: {}\"" +msgstr "\"bool: {}\"" + +#: src/unsafe-rust/unions.md:15 +msgid "// Undefined behavior!\n" +msgstr "" + +#: src/unsafe-rust/unions.md:22 +msgid "" +"Unions are very rarely needed in Rust as you can usually use an enum. They " +"are occasionally needed for interacting with C library APIs." +msgstr "" + +#: src/unsafe-rust/unions.md:25 +msgid "" +"If you just want to reinterpret bytes as a different type, you probably want " +"[`std::mem::transmute`](https://doc.rust-lang.org/stable/std/mem/fn." +"transmute.html) or a safe wrapper such as the [`zerocopy`](https://crates.io/" +"crates/zerocopy) crate." +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:3 src/unsafe-rust/unsafe-functions.md:74 +msgid "Calling Unsafe Functions" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:5 +msgid "" +"A function or method can be marked `unsafe` if it has extra preconditions " +"you must uphold to avoid undefined behaviour:" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:9 src/unsafe-rust/exercise.md:89 +#: src/unsafe-rust/solution.md:41 src/android/interoperability/with-c.md:9 +#: src/android/interoperability/with-c/rust.md:15 +#: src/android/interoperability/with-c/rust.md:30 +#: src/android/interoperability/cpp/cpp-bridge.md:29 +#: src/android/interoperability/cpp/cpp-bridge.md:38 +#: src/exercises/chromium/build-rules.md:7 +#: src/exercises/chromium/build-rules.md:19 +#: src/bare-metal/aps/inline-assembly.md:18 +#: src/bare-metal/aps/better-uart/using.md:24 +#: src/bare-metal/aps/logging/using.md:23 src/exercises/bare-metal/rtc.md:46 +#: src/exercises/bare-metal/rtc.md:100 src/exercises/bare-metal/rtc.md:106 +#: src/exercises/bare-metal/rtc.md:113 src/exercises/bare-metal/rtc.md:119 +#: src/exercises/bare-metal/rtc.md:125 src/exercises/bare-metal/rtc.md:131 +#: src/exercises/bare-metal/rtc.md:137 src/exercises/bare-metal/rtc.md:143 +#: src/exercises/bare-metal/solutions-afternoon.md:43 +msgid "\"C\"" +msgstr "\"C\"" + +#: src/unsafe-rust/unsafe-functions.md:14 +msgid "\"🗻∈🌏\"" +msgstr "\"🗻∈🌏\"" + +#: src/unsafe-rust/unsafe-functions.md:16 +msgid "" +"// Safe because the indices are in the correct order, within the bounds of\n" +" // the string slice, and lie on UTF-8 sequence boundaries.\n" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:19 +#: src/unsafe-rust/unsafe-functions.md:20 +#: src/unsafe-rust/unsafe-functions.md:21 +msgid "\"emoji: {}\"" +msgstr "\"emoji: {}\"" + +#: src/unsafe-rust/unsafe-functions.md:24 +msgid "\"char count: {}\"" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:27 +msgid "// Undefined behavior if abs misbehaves.\n" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:28 +msgid "\"Absolute value of -3 according to C: {}\"" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:31 +msgid "" +"// Not upholding the UTF-8 encoding requirement breaks memory safety!\n" +" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" +" // println!(\"char count: {}\", count_chars(unsafe { emojis." +"get_unchecked(0..3) }));\n" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:41 +#: src/unsafe-rust/unsafe-functions.md:86 +msgid "Writing Unsafe Functions" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:43 +msgid "" +"You can mark your own functions as `unsafe` if they require particular " +"conditions to avoid undefined behaviour." +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:47 +msgid "" +"/// Swaps the values pointed to by the given pointers.\n" +"///\n" +"/// # Safety\n" +"///\n" +"/// The pointers must be valid and properly aligned.\n" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:62 +msgid "// Safe because ...\n" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:67 +msgid "\"a = {}, b = {}\"" +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:76 +msgid "" +"`get_unchecked`, like most `_unchecked` functions, is unsafe, because it can " +"create UB if the range is incorrect. `abs` is incorrect for a different " +"reason: it is an external function (FFI). Calling external functions is " +"usually only a problem when those functions do things with pointers which " +"might violate Rust's memory model, but in general any C function might have " +"undefined behaviour under any arbitrary circumstances." +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:83 +msgid "" +"The `\"C\"` in this example is the ABI; [other ABIs are available too]" +"(https://doc.rust-lang.org/reference/items/external-blocks.html)." +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:88 +msgid "" +"We wouldn't actually use pointers for a `swap` function - it can be done " +"safely with references." +msgstr "" + +#: src/unsafe-rust/unsafe-functions.md:91 +msgid "" +"Note that unsafe code is allowed within an unsafe function without an " +"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " +"Try adding it and see what happens. This will likely change in a future Rust " +"edition." +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:1 +msgid "Implementing Unsafe Traits" +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:3 +msgid "" +"Like with functions, you can mark a trait as `unsafe` if the implementation " +"must guarantee particular conditions to avoid undefined behaviour." +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:6 +msgid "" +"For example, the `zerocopy` crate has an unsafe trait that looks [something " +"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:12 +msgid "" +"/// ...\n" +"/// # Safety\n" +"/// The type must have a defined representation and no padding.\n" +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:23 +msgid "// Safe because u32 has a defined representation and no padding.\n" +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:31 +msgid "" +"There should be a `# Safety` section on the Rustdoc for the trait explaining " +"the requirements for the trait to be safely implemented." +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:34 +msgid "" +"The actual safety section for `AsBytes` is rather longer and more " +"complicated." +msgstr "" + +#: src/unsafe-rust/unsafe-traits.md:36 +msgid "The built-in `Send` and `Sync` traits are unsafe." +msgstr "" + +#: src/unsafe-rust/exercise.md:1 +msgid "Safe FFI Wrapper" +msgstr "" + +#: src/unsafe-rust/exercise.md:3 +msgid "" +"Rust has great support for calling functions through a _foreign function " +"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " +"functions you would use from C to read the names of files in a directory." +msgstr "" + +#: src/unsafe-rust/exercise.md:7 +msgid "You will want to consult the manual pages:" +msgstr "" + +#: src/unsafe-rust/exercise.md:9 +msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:10 +msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:11 +msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:13 +msgid "" +"You will also want to browse the [`std::ffi`](https://doc.rust-lang.org/std/" +"ffi/) module. There you find a number of string types which you need for the " +"exercise:" +msgstr "" + +#: src/unsafe-rust/exercise.md:16 +msgid "Encoding" +msgstr "" + +#: src/unsafe-rust/exercise.md:16 +msgid "Use" +msgstr "" + +#: src/unsafe-rust/exercise.md:18 +msgid "" +"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" +"(https://doc.rust-lang.org/std/string/struct.String.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:18 +msgid "UTF-8" +msgstr "UTF-8" + +#: src/unsafe-rust/exercise.md:18 +msgid "Text processing in Rust" +msgstr "" + +#: src/unsafe-rust/exercise.md:19 +msgid "" +"[`CStr`](https://doc.rust-lang.org/std/ffi/struct.CStr.html) and [`CString`]" +"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:19 +msgid "NUL-terminated" +msgstr "" + +#: src/unsafe-rust/exercise.md:19 +msgid "Communicating with C functions" +msgstr "" + +#: src/unsafe-rust/exercise.md:20 +msgid "" +"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " +"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" +msgstr "" + +#: src/unsafe-rust/exercise.md:20 +msgid "OS-specific" +msgstr "" + +#: src/unsafe-rust/exercise.md:20 +msgid "Communicating with the OS" +msgstr "" + +#: src/unsafe-rust/exercise.md:22 +msgid "You will convert between all these types:" +msgstr "" + +#: src/unsafe-rust/exercise.md:24 +msgid "" +"`&str` to `CString`: you need to allocate space for a trailing `\\0` " +"character," +msgstr "" + +#: src/unsafe-rust/exercise.md:25 +msgid "`CString` to `*const i8`: you need a pointer to call C functions," +msgstr "" + +#: src/unsafe-rust/exercise.md:26 +msgid "" +"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " +"character," +msgstr "" + +#: src/unsafe-rust/exercise.md:27 +msgid "" +"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " +"unknown data\"," +msgstr "" + +#: src/unsafe-rust/exercise.md:28 +msgid "" +"`&[u8]` to `&OsStr`: `&OsStr` is a step towards `OsString`, use [`OsStrExt`]" +"(https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html) to create it," +msgstr "" + +#: src/unsafe-rust/exercise.md:31 +msgid "" +"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " +"return it and call `readdir` again." +msgstr "" + +#: src/unsafe-rust/exercise.md:34 +msgid "" +"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " +"useful chapter about FFI." +msgstr "" + +#: src/unsafe-rust/exercise.md:45 +msgid "" +"Copy the code below to and fill in the missing " +"functions and methods:" +msgstr "" + +#: src/unsafe-rust/exercise.md:54 src/unsafe-rust/exercise.md:67 +#: src/unsafe-rust/exercise.md:78 src/unsafe-rust/exercise.md:92 +#: src/unsafe-rust/exercise.md:100 src/unsafe-rust/solution.md:6 +#: src/unsafe-rust/solution.md:19 src/unsafe-rust/solution.md:30 +#: src/unsafe-rust/solution.md:44 src/unsafe-rust/solution.md:52 +msgid "\"macos\"" +msgstr "\"macos\"" + +#: src/unsafe-rust/exercise.md:57 src/unsafe-rust/solution.md:9 +msgid "// Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:64 src/unsafe-rust/solution.md:16 +msgid "" +"// Layout according to the Linux man page for readdir(3), where ino_t and\n" +" // off_t are resolved according to the definitions in\n" +" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:77 src/unsafe-rust/solution.md:29 +msgid "// Layout according to the macOS man page for dir(5).\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:92 src/unsafe-rust/exercise.md:100 +#: src/unsafe-rust/solution.md:44 src/unsafe-rust/solution.md:52 +msgid "\"x86_64\"" +msgstr "\"x86_64\"" + +#: src/unsafe-rust/exercise.md:95 src/unsafe-rust/solution.md:47 +msgid "" +"// See https://github.com/rust-lang/libc/issues/414 and the section on\n" +" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" +" //\n" +" // \"Platforms that existed before these updates were available\" " +"refers\n" +" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " +"PowerPC.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:101 src/unsafe-rust/solution.md:53 +msgid "\"readdir$INODE64\"" +msgstr "\"readdir$INODE64\"" + +#: src/unsafe-rust/exercise.md:119 src/unsafe-rust/solution.md:71 +msgid "" +"// Call opendir and return a Ok value if that worked,\n" +" // otherwise return Err with a message.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:128 +msgid "// Keep calling readdir until we get a NULL pointer back.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:135 src/unsafe-rust/solution.md:104 +msgid "// Call closedir as needed.\n" +msgstr "" + +#: src/unsafe-rust/exercise.md:141 src/unsafe-rust/solution.md:115 +#: src/unsafe-rust/solution.md:139 src/unsafe-rust/solution.md:154 +#: src/android/interoperability/with-c/rust.md:44 +msgid "\".\"" +msgstr "\".\"" + +#: src/unsafe-rust/exercise.md:142 src/unsafe-rust/solution.md:116 +msgid "\"files: {:#?}\"" +msgstr "" + +#: src/unsafe-rust/solution.md:73 +msgid "\"Invalid path: {err}\"" +msgstr "" + +#: src/unsafe-rust/solution.md:74 +msgid "// SAFETY: path.as_ptr() cannot be NULL.\n" +msgstr "" + +#: src/unsafe-rust/solution.md:77 +msgid "\"Could not open {:?}\"" +msgstr "" + +#: src/unsafe-rust/solution.md:87 +msgid "" +"// Keep calling readdir until we get a NULL pointer back.\n" +" // SAFETY: self.dir is never NULL.\n" +msgstr "" + +#: src/unsafe-rust/solution.md:91 +msgid "// We have reached the end of the directory.\n" +msgstr "" + +#: src/unsafe-rust/solution.md:94 +msgid "" +"// SAFETY: dirent is not NULL and dirent.d_name is NUL\n" +" // terminated.\n" +msgstr "" + +#: src/unsafe-rust/solution.md:106 +msgid "// SAFETY: self.dir is not NULL.\n" +msgstr "" + +#: src/unsafe-rust/solution.md:108 +msgid "\"Could not close {:?}\"" +msgstr "" + +#: src/unsafe-rust/solution.md:127 +msgid "\"no-such-directory\"" +msgstr "" + +#: src/unsafe-rust/solution.md:135 src/unsafe-rust/solution.md:150 +msgid "\"Non UTF-8 character in path\"" +msgstr "" + +#: src/unsafe-rust/solution.md:139 src/unsafe-rust/solution.md:154 +msgid "\"..\"" +msgstr "\"..\"" + +#: src/unsafe-rust/solution.md:146 src/unsafe-rust/solution.md:154 +msgid "\"foo.txt\"" +msgstr "\"foo.txt\"" + +#: src/unsafe-rust/solution.md:146 +msgid "\"The Foo Diaries\\n\"" +msgstr "" + +#: src/unsafe-rust/solution.md:147 src/unsafe-rust/solution.md:154 +msgid "\"bar.png\"" +msgstr "\"bar.png\"" + +#: src/unsafe-rust/solution.md:147 +msgid "\"\\n\"" +msgstr "\"\\n\"" + +#: src/unsafe-rust/solution.md:148 src/unsafe-rust/solution.md:154 +msgid "\"crab.rs\"" +msgstr "\"crab.rs\"" + +#: src/unsafe-rust/solution.md:148 +msgid "\"//! Crab\\n\"" +msgstr "" + +#: src/android.md:1 +msgid "Welcome to Rust in Android" +msgstr "" + +#: src/android.md:3 +msgid "" +"Rust is supported for system software on Android. This means that you can " +"write new services, libraries, drivers or even firmware in Rust (or improve " +"existing code as needed)." +msgstr "" + +#: src/android.md:7 +msgid "" +"We will attempt to call Rust from one of your own projects today. So try to " +"find a little corner of your code base where we can move some lines of code " +"to Rust. The fewer dependencies and \"exotic\" types the better. Something " +"that parses some raw bytes would be ideal." +msgstr "" + +#: src/android.md:14 +msgid "" +"The speaker may mention any of the following given the increased use of Rust " +"in Android:" +msgstr "" + +#: src/android.md:17 +msgid "" +"Service example: [DNS over HTTP](https://security.googleblog.com/2022/07/dns-" +"over-http3-in-android.html)" +msgstr "" + +#: src/android.md:19 +msgid "" +"Libraries: [Rutabaga Virtual Graphics Interface](https://crosvm.dev/book/" +"appendix/rutabaga_gfx.html)" +msgstr "" + +#: src/android.md:21 +msgid "" +"Kernel Drivers: [Binder](https://lore.kernel.org/rust-for-linux/20231101-" +"rust-binder-v1-0-08ba9197f637@google.com/)" +msgstr "" + +#: src/android.md:23 +msgid "" +"Firmware: [pKVM firmware](https://security.googleblog.com/2023/10/bare-metal-" +"rust-in-android.html)" +msgstr "" + +#: src/android/setup.md:3 +msgid "" +"We will be using a Cuttlefish Android Virtual Device to test our code. Make " +"sure you have access to one or create a new one with:" +msgstr "" + +#: src/android/setup.md:12 +msgid "" +"Please see the [Android Developer Codelab](https://source.android.com/docs/" +"setup/start) for details." +msgstr "" + +#: src/android/setup.md:19 +msgid "" +"Cuttlefish is a reference Android device designed to work on generic Linux " +"desktops. MacOS support is also planned." +msgstr "" + +#: src/android/setup.md:21 +msgid "" +"The Cuttlefish system image maintains high fidelity to real devices, and is " +"the ideal emulator to run many Rust use cases." +msgstr "" + +#: src/android/build-rules.md:3 +msgid "The Android build system (Soong) supports Rust via a number of modules:" +msgstr "" + +#: src/android/build-rules.md:5 +msgid "Module Type" +msgstr "" + +#: src/android/build-rules.md:5 +msgid "Description" +msgstr "" + +#: src/android/build-rules.md:7 +msgid "`rust_binary`" +msgstr "`rust_binary`" + +#: src/android/build-rules.md:7 +msgid "Produces a Rust binary." +msgstr "" + +#: src/android/build-rules.md:8 +msgid "`rust_library`" +msgstr "`rust_library`" + +#: src/android/build-rules.md:8 +msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." +msgstr "" + +#: src/android/build-rules.md:9 +msgid "`rust_ffi`" +msgstr "`rust_ffi`" + +#: src/android/build-rules.md:9 +msgid "" +"Produces a Rust C library usable by `cc` modules, and provides both static " +"and shared variants." +msgstr "" + +#: src/android/build-rules.md:10 +msgid "`rust_proc_macro`" +msgstr "`rust_proc_macro`" + +#: src/android/build-rules.md:10 +msgid "" +"Produces a `proc-macro` Rust library. These are analogous to compiler " +"plugins." +msgstr "" + +#: src/android/build-rules.md:11 +msgid "`rust_test`" +msgstr "`rust_test`" + +#: src/android/build-rules.md:11 +msgid "Produces a Rust test binary that uses the standard Rust test harness." +msgstr "" + +#: src/android/build-rules.md:12 +msgid "`rust_fuzz`" +msgstr "`rust_fuzz`" + +#: src/android/build-rules.md:12 +msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." +msgstr "" + +#: src/android/build-rules.md:13 +msgid "`rust_protobuf`" +msgstr "`rust_protobuf`" + +#: src/android/build-rules.md:13 +msgid "" +"Generates source and produces a Rust library that provides an interface for " +"a particular protobuf." +msgstr "" + +#: src/android/build-rules.md:14 +msgid "`rust_bindgen`" +msgstr "`rust_bindgen`" + +#: src/android/build-rules.md:14 +msgid "" +"Generates source and produces a Rust library containing Rust bindings to C " +"libraries." +msgstr "" + +#: src/android/build-rules.md:16 +msgid "We will look at `rust_binary` and `rust_library` next." +msgstr "" + +#: src/android/build-rules.md:20 +msgid "Additional items speaker may mention:" +msgstr "" + +#: src/android/build-rules.md:22 +msgid "" +"cargo is not optimized for multi-language repos, and also downloads packages " +"from the internet." +msgstr "" + +#: src/android/build-rules.md:24 +msgid "" +"For compliance and performance, Android must have crates in-tree. It must " +"also interop with C/C++/Java code. Soong fills that gap." +msgstr "" + +#: src/android/build-rules.md:26 +msgid "" +"Soong has many similarities to Bazel, which is the open-source variant of " +"Blaze (used in google3)." +msgstr "" + +#: src/android/build-rules.md:28 +msgid "" +"There is a plan to transition [Android](https://source.android.com/docs/" +"setup/build/bazel/introduction), [ChromeOS](https://chromium.googlesource." +"com/chromiumos/bazel/), and [Fuchsia](https://source.android.com/docs/setup/" +"build/bazel/introduction) to Bazel." +msgstr "" + +#: src/android/build-rules.md:30 +msgid "Learning Bazel-like build rules is useful for all Rust OS developers." +msgstr "" + +#: src/android/build-rules.md:32 +msgid "Fun fact: Data from Star Trek is a Soong-type Android." +msgstr "" + +#: src/android/build-rules/binary.md:1 +msgid "Rust Binaries" +msgstr "" + +#: src/android/build-rules/binary.md:3 +msgid "" +"Let us start with a simple application. At the root of an AOSP checkout, " +"create the following files:" +msgstr "" + +#: src/android/build-rules/binary.md:6 src/android/build-rules/library.md:13 +msgid "_hello_rust/Android.bp_:" +msgstr "_hello_rust/Android.bp_:" + +#: src/android/build-rules/binary.md:10 src/android/build-rules/binary.md:11 +msgid "\"hello_rust\"" +msgstr "\"hello_rust\"" + +#: src/android/build-rules/binary.md:12 src/android/build-rules/library.md:19 +#: src/android/logging.md:12 +msgid "\"src/main.rs\"" +msgstr "\"src/main.rs\"" + +#: src/android/build-rules/binary.md:16 src/android/build-rules/library.md:33 +msgid "_hello_rust/src/main.rs_:" +msgstr "_hello_rust/src/main.rs_:" + +#: src/android/build-rules/binary.md:19 src/android/build-rules/library.md:36 +msgid "//! Rust demo.\n" +msgstr "" + +#: src/android/build-rules/binary.md:20 src/android/build-rules/library.md:40 +msgid "/// Prints a greeting to standard output.\n" +msgstr "" + +#: src/android/build-rules/binary.md:23 src/exercises/chromium/build-rules.md:8 +msgid "\"Hello from Rust!\"" +msgstr "" + +#: src/android/build-rules/binary.md:27 +msgid "You can now build, push, and run the binary:" +msgstr "" + +#: src/android/build-rules/binary.md:29 +msgid "" +"```shell\n" +"m hello_rust\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust /data/local/tmp\"\n" +"adb shell /data/local/tmp/hello_rust\n" +"```" +msgstr "" +"```shell\n" +"m hello_rust\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust /data/local/tmp\"\n" +"adb shell /data/local/tmp/hello_rust\n" +"```" + +#: src/android/build-rules/library.md:1 +msgid "Rust Libraries" +msgstr "" + +#: src/android/build-rules/library.md:3 +msgid "You use `rust_library` to create a new Rust library for Android." +msgstr "" + +#: src/android/build-rules/library.md:5 +msgid "Here we declare a dependency on two libraries:" +msgstr "" + +#: src/android/build-rules/library.md:7 +msgid "`libgreeting`, which we define below," +msgstr "" + +#: src/android/build-rules/library.md:8 +msgid "" +"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" +"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" +"crates/)." +msgstr "" + +#: src/android/build-rules/library.md:17 src/android/build-rules/library.md:18 +msgid "\"hello_rust_with_dep\"" +msgstr "\"hello_rust_with_dep\"" + +#: src/android/build-rules/library.md:21 src/android/build-rules/library.md:27 +msgid "\"libgreetings\"" +msgstr "\"libgreetings\"" + +#: src/android/build-rules/library.md:22 +msgid "\"libtextwrap\"" +msgstr "\"libtextwrap\"" + +#: src/android/build-rules/library.md:28 +msgid "\"greetings\"" +msgstr "\"greetings\"" + +#: src/android/build-rules/library.md:29 src/android/aidl/implementation.md:31 +#: src/android/interoperability/java.md:38 +msgid "\"src/lib.rs\"" +msgstr "\"src/lib.rs\"" + +#: src/android/build-rules/library.md:47 +msgid "_hello_rust/src/lib.rs_:" +msgstr "_hello_rust/src/lib.rs_:" + +#: src/android/build-rules/library.md:50 +msgid "//! Greeting library.\n" +msgstr "" + +#: src/android/build-rules/library.md:51 +msgid "/// Greet `name`.\n" +msgstr "" + +#: src/android/build-rules/library.md:54 +msgid "\"Hello {name}, it is very nice to meet you!\"" +msgstr "" + +#: src/android/build-rules/library.md:58 +msgid "You build, push, and run the binary like before:" +msgstr "" + +#: src/android/build-rules/library.md:60 +msgid "" +"```shell\n" +"m hello_rust_with_dep\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/hello_rust_with_dep\n" +"```" +msgstr "" +"```shell\n" +"m hello_rust_with_dep\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/hello_rust_with_dep\n" +"```" + +#: src/android/aidl.md:3 +msgid "" +"The [Android Interface Definition Language (AIDL)](https://developer.android." +"com/guide/components/aidl) is supported in Rust:" +msgstr "" + +#: src/android/aidl.md:6 +msgid "Rust code can call existing AIDL servers," +msgstr "" + +#: src/android/aidl.md:7 +msgid "You can create new AIDL servers in Rust." +msgstr "" + +#: src/android/aidl/interface.md:1 +msgid "AIDL Interfaces" +msgstr "" + +#: src/android/aidl/interface.md:3 +msgid "You declare the API of your service using an AIDL interface:" +msgstr "" + +#: src/android/aidl/interface.md:5 +msgid "" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +msgstr "" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" + +#: src/android/aidl/interface.md:9 src/android/aidl/changing.md:8 +msgid "/** Birthday service interface. */" +msgstr "" + +#: src/android/aidl/interface.md:12 src/android/aidl/changing.md:11 +msgid "/** Generate a Happy Birthday message. */" +msgstr "" + +#: src/android/aidl/interface.md:17 +msgid "_birthday_service/aidl/Android.bp_:" +msgstr "_birthday_service/aidl/Android.bp_:" + +#: src/android/aidl/interface.md:21 +msgid "\"com.example.birthdayservice\"" +msgstr "\"com.example.birthdayservice\"" + +#: src/android/aidl/interface.md:22 +msgid "\"com/example/birthdayservice/*.aidl\"" +msgstr "\"com/example/birthdayservice/*.aidl\"" + +#: src/android/aidl/interface.md:25 +msgid "// Rust is not enabled by default\n" +msgstr "" + +#: src/android/aidl/interface.md:32 +msgid "" +"Add `vendor_available: true` if your AIDL file is used by a binary in the " +"vendor partition." +msgstr "" + +#: src/android/aidl/implementation.md:1 +msgid "Service Implementation" +msgstr "" + +#: src/android/aidl/implementation.md:3 +msgid "We can now implement the AIDL service:" +msgstr "" + +#: src/android/aidl/implementation.md:5 +msgid "_birthday_service/src/lib.rs_:" +msgstr "_birthday_service/src/lib.rs_:" + +#: src/android/aidl/implementation.md:8 +msgid "//! Implementation of the `IBirthdayService` AIDL interface.\n" +msgstr "" + +#: src/android/aidl/implementation.md:11 +msgid "/// The `IBirthdayService` implementation.\n" +msgstr "" + +#: src/android/aidl/implementation.md:20 +msgid "\"Happy Birthday {name}, congratulations with the {years} years!\"" +msgstr "" + +#: src/android/aidl/implementation.md:26 src/android/aidl/server.md:28 +#: src/android/aidl/client.md:37 +msgid "_birthday_service/Android.bp_:" +msgstr "_birthday_service/Android.bp_:" + +#: src/android/aidl/implementation.md:30 src/android/aidl/server.md:38 +msgid "\"libbirthdayservice\"" +msgstr "\"libbirthdayservice\"" + +#: src/android/aidl/implementation.md:32 src/android/aidl/server.md:13 +#: src/android/aidl/client.md:12 +msgid "\"birthdayservice\"" +msgstr "\"birthdayservice\"" + +#: src/android/aidl/implementation.md:34 src/android/aidl/server.md:36 +#: src/android/aidl/client.md:45 +msgid "\"com.example.birthdayservice-rust\"" +msgstr "\"com.example.birthdayservice-rust\"" + +#: src/android/aidl/implementation.md:35 src/android/aidl/server.md:37 +#: src/android/aidl/client.md:46 +msgid "\"libbinder_rs\"" +msgstr "\"libbinder_rs\"" + +#: src/android/aidl/server.md:1 +msgid "AIDL Server" +msgstr "" + +#: src/android/aidl/server.md:3 +msgid "Finally, we can create a server which exposes the service:" +msgstr "" + +#: src/android/aidl/server.md:5 +msgid "_birthday_service/src/server.rs_:" +msgstr "_birthday_service/src/server.rs_:" + +#: src/android/aidl/server.md:8 src/android/aidl/client.md:8 +msgid "//! Birthday service.\n" +msgstr "" + +#: src/android/aidl/server.md:14 +msgid "/// Entry point for birthday service.\n" +msgstr "" + +#: src/android/aidl/server.md:23 +msgid "\"Failed to register service\"" +msgstr "" + +#: src/android/aidl/server.md:32 src/android/aidl/server.md:33 +msgid "\"birthday_server\"" +msgstr "\"birthday_server\"" + +#: src/android/aidl/server.md:34 +msgid "\"src/server.rs\"" +msgstr "\"src/server.rs\"" + +#: src/android/aidl/deploy.md:3 +msgid "We can now build, push, and start the service:" +msgstr "" + +#: src/android/aidl/deploy.md:5 +msgid "" +"```shell\n" +"m birthday_server\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/birthday_server\n" +"```" +msgstr "" +"```shell\n" +"m birthday_server\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/birthday_server\n" +"```" + +#: src/android/aidl/deploy.md:11 +msgid "In another terminal, check that the service runs:" +msgstr "" + +#: src/android/aidl/deploy.md:21 +msgid "You can also call the service with `service call`:" +msgstr "" + +#: src/android/aidl/client.md:1 +msgid "AIDL Client" +msgstr "" + +#: src/android/aidl/client.md:3 +msgid "Finally, we can create a Rust client for our new service." +msgstr "" + +#: src/android/aidl/client.md:5 +msgid "_birthday_service/src/client.rs_:" +msgstr "_birthday_service/src/client.rs_:" + +#: src/android/aidl/client.md:13 +msgid "/// Connect to the BirthdayService.\n" +msgstr "" + +#: src/android/aidl/client.md:18 +msgid "/// Call the birthday service.\n" +msgstr "" + +#: src/android/aidl/client.md:30 +msgid "\"Failed to connect to BirthdayService\"" +msgstr "" + +#: src/android/aidl/client.md:32 +msgid "\"{msg}\"" +msgstr "\"{msg}\"" + +#: src/android/aidl/client.md:41 src/android/aidl/client.md:42 +msgid "\"birthday_client\"" +msgstr "\"birthday_client\"" + +#: src/android/aidl/client.md:43 +msgid "\"src/client.rs\"" +msgstr "\"src/client.rs\"" + +#: src/android/aidl/client.md:51 +msgid "Notice that the client does not depend on `libbirthdayservice`." +msgstr "" + +#: src/android/aidl/client.md:53 +msgid "Build, push, and run the client on your device:" +msgstr "" + +#: src/android/aidl/client.md:55 +msgid "" +"```shell\n" +"m birthday_client\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/birthday_client Charlie 60\n" +"```" +msgstr "" +"```shell\n" +"m birthday_client\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/birthday_client Charlie 60\n" +"```" + +#: src/android/aidl/changing.md:3 +msgid "" +"Let us extend the API with more functionality: we want to let clients " +"specify a list of lines for the birthday card:" +msgstr "" + +#: src/android/logging.md:3 +msgid "" +"You should use the `log` crate to automatically log to `logcat` (on-device) " +"or `stdout` (on-host):" +msgstr "" + +#: src/android/logging.md:6 +msgid "_hello_rust_logs/Android.bp_:" +msgstr "_hello_rust_logs/Android.bp_:" + +#: src/android/logging.md:10 src/android/logging.md:11 +msgid "\"hello_rust_logs\"" +msgstr "\"hello_rust_logs\"" + +#: src/android/logging.md:14 +msgid "\"liblog_rust\"" +msgstr "\"liblog_rust\"" + +#: src/android/logging.md:15 +msgid "\"liblogger\"" +msgstr "\"liblogger\"" + +#: src/android/logging.md:21 +msgid "_hello_rust_logs/src/main.rs_:" +msgstr "_hello_rust_logs/src/main.rs_:" + +#: src/android/logging.md:24 +msgid "//! Rust logging demo.\n" +msgstr "" + +#: src/android/logging.md:27 +msgid "/// Logs a greeting.\n" +msgstr "" + +#: src/android/logging.md:32 +msgid "\"rust\"" +msgstr "\"rust\"" + +#: src/android/logging.md:35 +msgid "\"Starting program.\"" +msgstr "" + +#: src/android/logging.md:36 +msgid "\"Things are going fine.\"" +msgstr "" + +#: src/android/logging.md:37 +msgid "\"Something went wrong!\"" +msgstr "" + +#: src/android/logging.md:41 src/android/interoperability/with-c/bindgen.md:98 +#: src/android/interoperability/with-c/rust.md:73 +msgid "Build, push, and run the binary on your device:" +msgstr "" + +#: src/android/logging.md:43 +msgid "" +"```shell\n" +"m hello_rust_logs\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/hello_rust_logs\n" +"```" +msgstr "" +"```shell\n" +"m hello_rust_logs\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/hello_rust_logs\n" +"```" + +#: src/android/logging.md:49 +msgid "The logs show up in `adb logcat`:" +msgstr "" + +#: src/android/interoperability.md:3 +msgid "" +"Rust has excellent support for interoperability with other languages. This " +"means that you can:" +msgstr "" + +#: src/android/interoperability.md:6 +msgid "Call Rust functions from other languages." +msgstr "" + +#: src/android/interoperability.md:7 +msgid "Call functions written in other languages from Rust." +msgstr "" + +#: src/android/interoperability.md:9 +msgid "" +"When you call functions in a foreign language we say that you're using a " +"_foreign function interface_, also known as FFI." +msgstr "" + +#: src/android/interoperability/with-c.md:1 +msgid "Interoperability with C" +msgstr "" + +#: src/android/interoperability/with-c.md:3 +msgid "" +"Rust has full support for linking object files with a C calling convention. " +"Similarly, you can export Rust functions and call them from C." +msgstr "" + +#: src/android/interoperability/with-c.md:6 +msgid "You can do it by hand if you want:" +msgstr "" + +#: src/android/interoperability/with-c.md:16 +msgid "\"{x}, {abs_x}\"" +msgstr "\"{x}, {abs_x}\"" + +#: src/android/interoperability/with-c.md:20 +msgid "" +"We already saw this in the [Safe FFI Wrapper exercise](../../exercises/day-3/" +"safe-ffi-wrapper.md)." +msgstr "" + +#: src/android/interoperability/with-c.md:23 +msgid "" +"This assumes full knowledge of the target platform. Not recommended for " +"production." +msgstr "" + +#: src/android/interoperability/with-c.md:26 +msgid "We will look at better options next." +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:1 +msgid "Using Bindgen" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:3 +msgid "" +"The [bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) " +"tool can auto-generate bindings from a C header file." +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:6 +msgid "First create a small C library:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:8 +msgid "_interoperability/bindgen/libbirthday.h_:" +msgstr "_interoperability/bindgen/libbirthday.h_:" + +#: src/android/interoperability/with-c/bindgen.md:19 +msgid "_interoperability/bindgen/libbirthday.c_:" +msgstr "_interoperability/bindgen/libbirthday.c_:" + +#: src/android/interoperability/with-c/bindgen.md:22 +msgid "" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:23 +#: src/android/interoperability/with-c/bindgen.md:50 +msgid "\"libbirthday.h\"" +msgstr "\"libbirthday.h\"" + +#: src/android/interoperability/with-c/bindgen.md:26 +#: src/android/interoperability/with-c/bindgen.md:29 +msgid "\"+--------------\\n\"" +msgstr "\"+--------------\\n\"" + +#: src/android/interoperability/with-c/bindgen.md:27 +msgid "\"| Happy Birthday %s!\\n\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:28 +msgid "\"| Congratulations with the %i years!\\n\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:33 +msgid "Add this to your `Android.bp` file:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:35 +#: src/android/interoperability/with-c/bindgen.md:55 +#: src/android/interoperability/with-c/bindgen.md:69 +#: src/android/interoperability/with-c/bindgen.md:108 +msgid "_interoperability/bindgen/Android.bp_:" +msgstr "_interoperability/bindgen/Android.bp_:" + +#: src/android/interoperability/with-c/bindgen.md:39 +#: src/android/interoperability/with-c/bindgen.md:63 +msgid "\"libbirthday\"" +msgstr "\"libbirthday\"" + +#: src/android/interoperability/with-c/bindgen.md:40 +msgid "\"libbirthday.c\"" +msgstr "\"libbirthday.c\"" + +#: src/android/interoperability/with-c/bindgen.md:44 +msgid "" +"Create a wrapper header file for the library (not strictly needed in this " +"example):" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:47 +msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" +msgstr "_interoperability/bindgen/libbirthday_wrapper.h_:" + +#: src/android/interoperability/with-c/bindgen.md:53 +msgid "You can now auto-generate the bindings:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:59 +#: src/android/interoperability/with-c/bindgen.md:75 +msgid "\"libbirthday_bindgen\"" +msgstr "\"libbirthday_bindgen\"" + +#: src/android/interoperability/with-c/bindgen.md:60 +msgid "\"birthday_bindgen\"" +msgstr "\"birthday_bindgen\"" + +#: src/android/interoperability/with-c/bindgen.md:61 +msgid "\"libbirthday_wrapper.h\"" +msgstr "\"libbirthday_wrapper.h\"" + +#: src/android/interoperability/with-c/bindgen.md:62 +msgid "\"bindings\"" +msgstr "\"bindings\"" + +#: src/android/interoperability/with-c/bindgen.md:67 +msgid "Finally, we can use the bindings in our Rust program:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:73 +msgid "\"print_birthday_card\"" +msgstr "\"print_birthday_card\"" + +#: src/android/interoperability/with-c/bindgen.md:74 +msgid "\"main.rs\"" +msgstr "\"main.rs\"" + +#: src/android/interoperability/with-c/bindgen.md:79 +msgid "_interoperability/bindgen/main.rs_:" +msgstr "_interoperability/bindgen/main.rs_:" + +#: src/android/interoperability/with-c/bindgen.md:82 +msgid "//! Bindgen demo.\n" +msgstr "//! Bindgen-demo.\n" + +#: src/android/interoperability/with-c/bindgen.md:100 +msgid "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" +msgstr "" +"```shell\n" +"m print_birthday_card\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/print_birthday_card\n" +"```" + +#: src/android/interoperability/with-c/bindgen.md:106 +msgid "Finally, we can run auto-generated tests to ensure the bindings work:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md:112 +#: src/android/interoperability/with-c/bindgen.md:114 +msgid "\"libbirthday_bindgen_test\"" +msgstr "\"libbirthday_bindgen_test\"" + +#: src/android/interoperability/with-c/bindgen.md:113 +msgid "\":libbirthday_bindgen\"" +msgstr "\":libbirthday_bindgen\"" + +#: src/android/interoperability/with-c/bindgen.md:115 +msgid "\"general-tests\"" +msgstr "\"general-tests\"" + +#: src/android/interoperability/with-c/bindgen.md:117 +#: src/android/interoperability/with-c/bindgen.md:118 +msgid "\"none\"" +msgstr "\"none\"" + +#: src/android/interoperability/with-c/bindgen.md:117 +msgid "// Generated file, skip linting\n" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:1 +msgid "Calling Rust" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:3 +msgid "Exporting Rust functions and types to C is easy:" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:5 +msgid "_interoperability/rust/libanalyze/analyze.rs_" +msgstr "_interoperability/rust/libanalyze/analyze.rs_" + +#: src/android/interoperability/with-c/rust.md:8 +msgid "//! Rust FFI demo.\n" +msgstr "//! Rust FFI-demo.\n" + +#: src/android/interoperability/with-c/rust.md:12 +msgid "/// Analyze the numbers.\n" +msgstr "/// Analyze the numbers.\n" + +#: src/android/interoperability/with-c/rust.md:17 +msgid "\"x ({x}) is smallest!\"" +msgstr "\"x ({x}) er mindst!\"" + +#: src/android/interoperability/with-c/rust.md:19 +msgid "\"y ({y}) is probably larger than x ({x})\"" +msgstr "\"y ({y}) er muligvis større end x ({x})\"" + +#: src/android/interoperability/with-c/rust.md:24 +msgid "_interoperability/rust/libanalyze/analyze.h_" +msgstr "_interoperability/rust/libanalyze/analyze.h_" + +#: src/android/interoperability/with-c/rust.md:37 +msgid "_interoperability/rust/libanalyze/Android.bp_" +msgstr "_interoperability/rust/libanalyze/Android.bp_" + +#: src/android/interoperability/with-c/rust.md:41 +#: src/android/interoperability/with-c/rust.md:68 +msgid "\"libanalyze_ffi\"" +msgstr "\"libanalyze_ffi\"" + +#: src/android/interoperability/with-c/rust.md:42 +msgid "\"analyze_ffi\"" +msgstr "\"analyze_ffi\"" + +#: src/android/interoperability/with-c/rust.md:43 +msgid "\"analyze.rs\"" +msgstr "\"analyze.rs\"" + +#: src/android/interoperability/with-c/rust.md:48 +msgid "We can now call this from a C binary:" +msgstr "" + +#: src/android/interoperability/with-c/rust.md:50 +msgid "_interoperability/rust/analyze/main.c_" +msgstr "_interoperability/rust/analyze/main.c_" + +#: src/android/interoperability/with-c/rust.md:53 +msgid "\"analyze.h\"" +msgstr "\"analyze.h\"" + +#: src/android/interoperability/with-c/rust.md:62 +msgid "_interoperability/rust/analyze/Android.bp_" +msgstr "_interoperability/rust/analyze/Android.bp_" + +#: src/android/interoperability/with-c/rust.md:66 +msgid "\"analyze_numbers\"" +msgstr "\"analyze_numbers\"" + +#: src/android/interoperability/with-c/rust.md:67 +msgid "\"main.c\"" +msgstr "\"main.c\"" + +#: src/android/interoperability/with-c/rust.md:75 +msgid "" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/analyze_numbers\n" +"```" +msgstr "" +"```shell\n" +"m analyze_numbers\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" +"tmp\"\n" +"adb shell /data/local/tmp/analyze_numbers\n" +"```" + +#: src/android/interoperability/with-c/rust.md:83 +msgid "" +"`#[no_mangle]` disables Rust's usual name mangling, so the exported symbol " +"will just be the name of the function. You can also use `#[export_name = " +"\"some_name\"]` to specify whatever name you want." +msgstr "" + +#: src/android/interoperability/cpp.md:1 +msgid "With C++" +msgstr "" + +#: src/android/interoperability/cpp.md:3 +msgid "" +"The [CXX crate](https://cxx.rs/) makes it possible to do safe " +"interoperability between Rust and C++." +msgstr "" + +#: src/android/interoperability/cpp.md:6 +msgid "The overall approach looks like this:" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:3 +msgid "" +"CXX relies on a description of the function signatures that will be exposed " +"from each language to the other. You provide this description using extern " +"blocks in a Rust module annotated with the `#[cxx::bridge]` attribute macro." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:9 +msgid "\"org::blobstore\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:11 +msgid "// Shared structs with fields visible to both languages.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:17 +#: src/android/interoperability/cpp/generated-cpp.md:6 +msgid "// Rust types and signatures exposed to C++.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:18 +#: src/android/interoperability/cpp/rust-bridge.md:6 +#: src/android/interoperability/cpp/generated-cpp.md:7 +#: src/android/interoperability/cpp/rust-result.md:6 +#: src/chromium/interoperability-with-cpp/example-bindings.md:9 +#: src/chromium/interoperability-with-cpp/error-handling.md:11 +#: src/chromium/interoperability-with-cpp/error-handling.md:26 +#, fuzzy +msgid "\"Rust\"" +msgstr "\"rust\"" + +#: src/android/interoperability/cpp/bridge.md:24 +#: src/android/interoperability/cpp/cpp-bridge.md:6 +msgid "// C++ types and signatures exposed to Rust.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:25 +#: src/android/interoperability/cpp/cpp-bridge.md:7 +#: src/android/interoperability/cpp/cpp-exception.md:6 +#: src/chromium/interoperability-with-cpp/example-bindings.md:15 +msgid "\"C++\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:26 +#: src/android/interoperability/cpp/cpp-bridge.md:8 +msgid "\"include/blobstore.h\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:40 +msgid "The bridge is generally declared in an `ffi` module within your crate." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:41 +msgid "" +"From the declarations made in the bridge module, CXX will generate matching " +"Rust and C++ type/function definitions in order to expose those items to " +"both languages." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:44 +msgid "" +"To view the generated Rust code, use [cargo-expand](https://github.com/" +"dtolnay/cargo-expand) to view the expanded proc macro. For most of the " +"examples you would use `cargo expand ::ffi` to expand just the `ffi` module " +"(though this doesn't apply for Android projects)." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md:47 +msgid "To view the generated C++ code, look in `target/cxxbridge`." +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md:1 +msgid "Rust Bridge Declarations" +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md:7 +msgid "// Opaque type\n" msgstr "" -#: src/unsafe.md:8 -msgid "" -"We will be seeing mostly safe Rust in this course, but it's important to " -"know what Unsafe Rust is." +#: src/android/interoperability/cpp/rust-bridge.md:8 +msgid "// Method on `MyType`\n" msgstr "" -#: src/unsafe.md:11 +#: src/android/interoperability/cpp/rust-bridge.md:9 +#, fuzzy +msgid "// Free function\n" +msgstr "Funktioner" + +#: src/android/interoperability/cpp/rust-bridge.md:28 msgid "" -"Unsafe code is usually small and isolated, and its correctness should be " -"carefully documented. It is usually wrapped in a safe abstraction layer." +"Items declared in the `extern \"Rust\"` reference items that are in scope in " +"the parent module." msgstr "" -#: src/unsafe.md:14 -msgid "Unsafe Rust gives you access to five new capabilities:" +#: src/android/interoperability/cpp/rust-bridge.md:30 +msgid "" +"The CXX code generator uses your `extern \"Rust\"` section(s) to produce a C+" +"+ header file containing the corresponding C++ declarations. The generated " +"header has the same path as the Rust source file containing the bridge, " +"except with a .rs.h file extension." msgstr "" -#: src/unsafe.md:16 -msgid "Dereference raw pointers." +#: src/android/interoperability/cpp/generated-cpp.md:15 +msgid "Results in (roughly) the following C++:" msgstr "" -#: src/unsafe.md:17 -msgid "Access or modify mutable static variables." +#: src/android/interoperability/cpp/cpp-bridge.md:1 +msgid "C++ Bridge Declarations" msgstr "" -#: src/unsafe.md:18 -msgid "Access `union` fields." +#: src/android/interoperability/cpp/cpp-bridge.md:20 +msgid "Results in (roughly) the following Rust:" msgstr "" -#: src/unsafe.md:19 -msgid "Call `unsafe` functions, including `extern` functions." +#: src/android/interoperability/cpp/cpp-bridge.md:30 +msgid "\"org$blobstore$cxxbridge1$new_blobstore_client\"" msgstr "" -#: src/unsafe.md:20 -msgid "Implement `unsafe` traits." +#: src/android/interoperability/cpp/cpp-bridge.md:39 +msgid "\"org$blobstore$cxxbridge1$BlobstoreClient$put\"" msgstr "" -#: src/unsafe.md:22 +#: src/android/interoperability/cpp/cpp-bridge.md:56 msgid "" -"We will briefly cover unsafe capabilities next. For full details, please see " -"[Chapter 19.1 in the Rust Book](https://doc.rust-lang.org/book/ch19-01-" -"unsafe-rust.html) and the [Rustonomicon](https://doc.rust-lang.org/nomicon/)." +"The programmer does not need to promise that the signatures they have typed " +"in are accurate. CXX performs static assertions that the signatures exactly " +"correspond with what is declared in C++." msgstr "" -#: src/unsafe.md:28 +#: src/android/interoperability/cpp/cpp-bridge.md:59 msgid "" -"Unsafe Rust does not mean the code is incorrect. It means that developers " -"have turned off the compiler safety features and have to write correct code " -"by themselves. It means the compiler no longer enforces Rust's memory-safety " -"rules." +"`unsafe extern` blocks allow you to declare C++ functions that are safe to " +"call from Rust." msgstr "" -#: src/unsafe/raw-pointers.md:3 -msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" +#: src/android/interoperability/cpp/shared-types.md:9 +msgid "// A=1, J=11, Q=12, K=13\n" +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md:23 +msgid "Only C-like (unit) enums are supported." msgstr "" -#: src/unsafe/raw-pointers.md:12 +#: src/android/interoperability/cpp/shared-types.md:24 msgid "" -"// Safe because r1 and r2 were obtained from references and so are\n" -" // guaranteed to be non-null and properly aligned, the objects " -"underlying\n" -" // the references from which they were obtained are live throughout the\n" -" // whole unsafe block, and they are not accessed either through the\n" -" // references or concurrently through any other pointers.\n" +"A limited number of traits are supported for `#[derive()]` on shared types. " +"Corresponding functionality is also generated for the C++ code, e.g. if you " +"derive `Hash` also generates an implementation of `std::hash` for the " +"corresponding C++ type." msgstr "" -#: src/unsafe/raw-pointers.md:18 -msgid "\"r1 is: {}\"" -msgstr "\"r1 er: {}\"" +#: src/android/interoperability/cpp/shared-enums.md:15 +#, fuzzy +msgid "Generated Rust:" +msgstr "\"general-tests\"" -#: src/unsafe/raw-pointers.md:20 -msgid "\"r2 is: {}\"" -msgstr "\"r2 er: {}\"" +#: src/android/interoperability/cpp/shared-enums.md:33 +msgid "Generated C++:" +msgstr "" -#: src/unsafe/raw-pointers.md:27 +#: src/android/interoperability/cpp/shared-enums.md:46 msgid "" -"It is good practice (and required by the Android Rust style guide) to write " -"a comment for each `unsafe` block explaining how the code inside it " -"satisfies the safety requirements of the unsafe operations it is doing." +"On the Rust side, the code generated for shared enums is actually a struct " +"wrapping a numeric value. This is because it is not UB in C++ for an enum " +"class to hold a value different from all of the listed variants, and our " +"Rust representation needs to have the same behavior." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:13 +msgid "\"fallible1 requires depth > 0\"" +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md:16 +msgid "\"Success!\"" msgstr "" -#: src/unsafe/raw-pointers.md:31 +#: src/android/interoperability/cpp/rust-result.md:22 msgid "" -"In the case of pointer dereferences, this means that the pointers must be " -"[_valid_](https://doc.rust-lang.org/std/ptr/index.html#safety), i.e.:" +"Rust functions that return `Result` are translated to exceptions on the C++ " +"side." msgstr "" -#: src/unsafe/raw-pointers.md:34 -msgid "The pointer must be non-null." +#: src/android/interoperability/cpp/rust-result.md:24 +msgid "" +"The exception thrown will always be of type `rust::Error`, which primarily " +"exposes a way to get the error message string. The error message will come " +"from the error type's `Display` impl." msgstr "" -#: src/unsafe/raw-pointers.md:35 +#: src/android/interoperability/cpp/rust-result.md:27 msgid "" -"The pointer must be _dereferenceable_ (within the bounds of a single " -"allocated object)." +"A panic unwinding from Rust to C++ will always cause the process to " +"immediately terminate." msgstr "" -#: src/unsafe/raw-pointers.md:36 -msgid "The object must not have been deallocated." +#: src/android/interoperability/cpp/cpp-exception.md:7 +msgid "\"example/include/example.h\"" msgstr "" -#: src/unsafe/raw-pointers.md:37 -msgid "There must not be concurrent accesses to the same location." +#: src/android/interoperability/cpp/cpp-exception.md:14 +#, fuzzy +msgid "\"Error: {}\"" +msgstr "\"Fejl: {err}\"" + +#: src/android/interoperability/cpp/cpp-exception.md:22 +msgid "" +"C++ functions declared to return a `Result` will catch any thrown exception " +"on the C++ side and return it as an `Err` value to the calling Rust function." msgstr "" -#: src/unsafe/raw-pointers.md:38 +#: src/android/interoperability/cpp/cpp-exception.md:24 msgid "" -"If the pointer was obtained by casting a reference, the underlying object " -"must be live and no reference may be used to access the memory." +"If an exception is thrown from an extern \"C++\" function that is not " +"declared by the CXX bridge to return `Result`, the program calls C++'s `std::" +"terminate`. The behavior is equivalent to the same exception being thrown " +"through a `noexcept` C++ function." msgstr "" -#: src/unsafe/raw-pointers.md:41 -msgid "In most cases the pointer must also be properly aligned." +#: src/android/interoperability/cpp/type-mapping.md:3 +#, fuzzy +msgid "Rust Type" +msgstr "Rust by Example" + +#: src/android/interoperability/cpp/type-mapping.md:3 +msgid "C++ Type" msgstr "" -#: src/unsafe/mutable-static-variables.md:3 -msgid "It is safe to read an immutable static variable:" +#: src/android/interoperability/cpp/type-mapping.md:5 +#, fuzzy +msgid "`String`" +msgstr "`Path`, `OsString`" + +#: src/android/interoperability/cpp/type-mapping.md:5 +#, fuzzy +msgid "`rust::String`" +msgstr "`rust_bindgen`" + +#: src/android/interoperability/cpp/type-mapping.md:6 +msgid "`&str`" msgstr "" -#: src/unsafe/mutable-static-variables.md:6 -msgid "\"Hello, world!\"" -msgstr "\"Hej verden!\"" +#: src/android/interoperability/cpp/type-mapping.md:6 +#, fuzzy +msgid "`rust::Str`" +msgstr "`rust_test`" -#: src/unsafe/mutable-static-variables.md:9 -msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" -msgstr "\"HELLO_WORLD: {HELLO_WORLD}\"" +#: src/android/interoperability/cpp/type-mapping.md:7 +msgid "`CxxString`" +msgstr "" -#: src/unsafe/mutable-static-variables.md:13 -msgid "" -"However, since data races can occur, it is unsafe to read and write mutable " -"static variables:" +#: src/android/interoperability/cpp/type-mapping.md:7 +msgid "`std::string`" msgstr "" -#: src/unsafe/mutable-static-variables.md:20 -#: src/unsafe/mutable-static-variables.md:26 -msgid "// Potential data race!\n" +#: src/android/interoperability/cpp/type-mapping.md:8 +msgid "`&[T]`/`&mut [T]`" msgstr "" -#: src/unsafe/mutable-static-variables.md:26 -msgid "\"COUNTER: {COUNTER}\"" -msgstr "\"COUNTER: {COUNTER}\"" +#: src/android/interoperability/cpp/type-mapping.md:8 +#, fuzzy +msgid "`rust::Slice`" +msgstr "`rust_ffi`" -#: src/unsafe/mutable-static-variables.md:32 -msgid "" -"Using a mutable static is generally a bad idea, but there are some cases " -"where it might make sense in low-level `no_std` code, such as implementing a " -"heap allocator or working with some C APIs." +#: src/android/interoperability/cpp/type-mapping.md:9 +msgid "`rust::Box`" msgstr "" -#: src/unsafe/unions.md:3 -msgid "Unions are like enums, but you need to track the active field yourself:" +#: src/android/interoperability/cpp/type-mapping.md:10 +msgid "`UniquePtr`" msgstr "" -#: src/unsafe/unions.md:14 -msgid "\"int: {}\"" -msgstr "\"int: {}\"" +#: src/android/interoperability/cpp/type-mapping.md:10 +msgid "`std::unique_ptr`" +msgstr "" -#: src/unsafe/unions.md:15 -msgid "\"bool: {}\"" -msgstr "\"bool: {}\"" +#: src/android/interoperability/cpp/type-mapping.md:11 +#, fuzzy +msgid "`Vec`" +msgstr "`Vec`" -#: src/unsafe/unions.md:15 -msgid "// Undefined behavior!\n" -msgstr "" +#: src/android/interoperability/cpp/type-mapping.md:11 +#, fuzzy +msgid "`rust::Vec`" +msgstr "`mpsc::Receiver`" + +#: src/android/interoperability/cpp/type-mapping.md:12 +#, fuzzy +msgid "`CxxVector`" +msgstr "`Cell`" + +#: src/android/interoperability/cpp/type-mapping.md:12 +#, fuzzy +msgid "`std::vector`" +msgstr "`mpsc::Receiver`" -#: src/unsafe/unions.md:21 +#: src/android/interoperability/cpp/type-mapping.md:16 msgid "" -"Unions are very rarely needed in Rust as you can usually use an enum. They " -"are occasionally needed for interacting with C library APIs." +"These types can be used in the fields of shared structs and the arguments " +"and returns of extern functions." msgstr "" -#: src/unsafe/unions.md:24 +#: src/android/interoperability/cpp/type-mapping.md:18 msgid "" -"If you just want to reinterpret bytes as a different type, you probably want " -"[`std::mem::transmute`](https://doc.rust-lang.org/stable/std/mem/fn." -"transmute.html) or a safe wrapper such as the [`zerocopy`](https://crates.io/" -"crates/zerocopy) crate." +"Note that Rust's `String` does not map directly to `std::string`. There are " +"a few reasons for this:" msgstr "" -#: src/unsafe/calling-unsafe-functions.md:3 +#: src/android/interoperability/cpp/type-mapping.md:20 msgid "" -"A function or method can be marked `unsafe` if it has extra preconditions " -"you must uphold to avoid undefined behaviour:" +"`std::string` does not uphold the UTF-8 invariant that `String` requires." msgstr "" -#: src/unsafe/calling-unsafe-functions.md:8 -msgid "\"🗻∈🌏\"" -msgstr "\"🗻∈🌏\"" +#: src/android/interoperability/cpp/type-mapping.md:21 +msgid "" +"The two types have different layouts in memory and so can't be passed " +"directly between languages." +msgstr "" -#: src/unsafe/calling-unsafe-functions.md:10 +#: src/android/interoperability/cpp/type-mapping.md:23 msgid "" -"// Safe because the indices are in the correct order, within the bounds of\n" -" // the string slice, and lie on UTF-8 sequence boundaries.\n" +"`std::string` requires move constructors that don't match Rust's move " +"semantics, so a `std::string` can't be passed by value to Rust." msgstr "" -#: src/unsafe/calling-unsafe-functions.md:13 -#: src/unsafe/calling-unsafe-functions.md:14 -#: src/unsafe/calling-unsafe-functions.md:15 -msgid "\"emoji: {}\"" -msgstr "\"emoji: {}\"" +#: src/android/interoperability/cpp/android-build-cpp.md:1 +#: src/android/interoperability/cpp/android-cpp-genrules.md:1 +#: src/android/interoperability/cpp/android-build-rust.md:1 +#, fuzzy +msgid "Building in Android" +msgstr "Rust i Android" -#: src/unsafe/calling-unsafe-functions.md:18 -msgid "\"char count: {}\"" +#: src/android/interoperability/cpp/android-build-cpp.md:3 +msgid "" +"Create a `cc_library_static` to build the C++ library, including the CXX " +"generated header and source file." msgstr "" -#: src/unsafe/calling-unsafe-functions.md:20 -msgid "" -"// Not upholding the UTF-8 encoding requirement breaks memory safety!\n" -" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" -" // println!(\"char count: {}\", count_chars(unsafe { emojis." -"get_unchecked(0..3) }));\n" +#: src/android/interoperability/cpp/android-build-cpp.md:8 +#: src/android/interoperability/cpp/android-build-rust.md:10 +#, fuzzy +msgid "\"libcxx_test_cpp\"" +msgstr "\"libtextwrap\"" + +#: src/android/interoperability/cpp/android-build-cpp.md:9 +msgid "\"cxx_test.cpp\"" msgstr "" -#: src/unsafe/writing-unsafe-functions.md:3 -msgid "" -"You can mark your own functions as `unsafe` if they require particular " -"conditions to avoid undefined behaviour." +#: src/android/interoperability/cpp/android-build-cpp.md:11 +msgid "\"cxx-bridge-header\"" msgstr "" -#: src/unsafe/writing-unsafe-functions.md:7 -msgid "" -"/// Swaps the values pointed to by the given pointers.\n" -"///\n" -"/// # Safety\n" -"///\n" -"/// The pointers must be valid and properly aligned.\n" +#: src/android/interoperability/cpp/android-build-cpp.md:12 +#: src/android/interoperability/cpp/android-cpp-genrules.md:10 +msgid "\"libcxx_test_bridge_header\"" msgstr "" -#: src/unsafe/writing-unsafe-functions.md:22 -msgid "// Safe because ...\n" +#: src/android/interoperability/cpp/android-build-cpp.md:14 +#: src/android/interoperability/cpp/android-cpp-genrules.md:19 +msgid "\"libcxx_test_bridge_code\"" msgstr "" -#: src/unsafe/writing-unsafe-functions.md:27 -msgid "\"a = {}, b = {}\"" +#: src/android/interoperability/cpp/android-build-cpp.md:20 +msgid "" +"Point out that `libcxx_test_bridge_header` and `libcxx_test_bridge_code` are " +"the dependencies for the CXX-generated C++ bindings. We'll show how these " +"are setup on the next slide." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:33 +#: src/android/interoperability/cpp/android-build-cpp.md:23 msgid "" -"We wouldn't actually use pointers for this because it can be done safely " -"with references." +"Note that you also need to depend on the `cxx-bridge-header` library in " +"order to pull in common CXX definitions." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:35 +#: src/android/interoperability/cpp/android-build-cpp.md:25 msgid "" -"Note that unsafe code is allowed within an unsafe function without an " -"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " -"Try adding it and see what happens." +"Full docs for using CXX in Android can be found in [the Android docs]" +"(https://source.android.com/docs/setup/build/rust/building-rust-modules/" +"android-rust-patterns#rust-cpp-interop-using-cxx). You may want to share " +"that link with the class so that students know where they can find these " +"instructions again in the future." msgstr "" -#: src/unsafe/extern-functions.md:1 -msgid "Calling External Code" +#: src/android/interoperability/cpp/android-cpp-genrules.md:3 +msgid "" +"Create two genrules: One to generate the CXX header, and one to generate the " +"CXX source file. These are then used as inputs to the `cc_library_static`." msgstr "" -#: src/unsafe/extern-functions.md:3 +#: src/android/interoperability/cpp/android-cpp-genrules.md:7 msgid "" -"Functions from other languages might violate the guarantees of Rust. Calling " -"them is thus unsafe:" +"// Generate a C++ header containing the C++ bindings\n" +"// to the Rust exported functions in lib.rs.\n" msgstr "" -#: src/unsafe/extern-functions.md:7 src/exercises/day-3/safe-ffi-wrapper.md:89 -#: src/android/interoperability/with-c.md:9 -#: src/android/interoperability/with-c/rust.md:15 -#: src/android/interoperability/with-c/rust.md:30 -#: src/bare-metal/aps/inline-assembly.md:18 -#: src/bare-metal/aps/better-uart/using.md:24 -#: src/bare-metal/aps/logging/using.md:23 src/bare-metal/aps/exceptions.md:14 -#: src/bare-metal/aps/exceptions.md:20 src/bare-metal/aps/exceptions.md:26 -#: src/bare-metal/aps/exceptions.md:32 src/bare-metal/aps/exceptions.md:38 -#: src/bare-metal/aps/exceptions.md:44 src/bare-metal/aps/exceptions.md:50 -#: src/bare-metal/aps/exceptions.md:56 src/exercises/bare-metal/rtc.md:46 -#: src/exercises/bare-metal/rtc.md:100 src/exercises/bare-metal/rtc.md:106 -#: src/exercises/bare-metal/rtc.md:113 src/exercises/bare-metal/rtc.md:119 -#: src/exercises/bare-metal/rtc.md:125 src/exercises/bare-metal/rtc.md:131 -#: src/exercises/bare-metal/rtc.md:137 src/exercises/bare-metal/rtc.md:143 -#: src/exercises/day-3/solutions-afternoon.md:45 -#: src/exercises/bare-metal/solutions-afternoon.md:43 -msgid "\"C\"" -msgstr "\"C\"" +#: src/android/interoperability/cpp/android-cpp-genrules.md:11 +#: src/android/interoperability/cpp/android-cpp-genrules.md:20 +msgid "\"cxxbridge\"" +msgstr "" -#: src/unsafe/extern-functions.md:13 -msgid "// Undefined behavior if abs misbehaves.\n" +#: src/android/interoperability/cpp/android-cpp-genrules.md:12 +msgid "\"$(location cxxbridge) $(in) --header > $(out)\"" msgstr "" -#: src/unsafe/extern-functions.md:14 -msgid "\"Absolute value of -3 according to C: {}\"" +#: src/android/interoperability/cpp/android-cpp-genrules.md:13 +#: src/android/interoperability/cpp/android-cpp-genrules.md:22 +#: src/android/interoperability/cpp/android-build-rust.md:8 +#, fuzzy +msgid "\"lib.rs\"" +msgstr "\"src/lib.rs\"" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:14 +#, fuzzy +msgid "\"lib.rs.h\"" +msgstr "\"src/lib.rs\"" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:16 +msgid "// Generate the C++ code that Rust calls into.\n" msgstr "" -#: src/unsafe/extern-functions.md:21 -msgid "" -"This is usually only a problem for extern functions which do things with " -"pointers which might violate Rust's memory model, but in general any C " -"function might have undefined behaviour under any arbitrary circumstances." +#: src/android/interoperability/cpp/android-cpp-genrules.md:21 +msgid "\"$(location cxxbridge) $(in) > $(out)\"" msgstr "" -#: src/unsafe/extern-functions.md:25 +#: src/android/interoperability/cpp/android-cpp-genrules.md:23 +#, fuzzy +msgid "\"lib.rs.cc\"" +msgstr "\"src/lib.rs\"" + +#: src/android/interoperability/cpp/android-cpp-genrules.md:29 msgid "" -"The `\"C\"` in this example is the ABI; [other ABIs are available too]" -"(https://doc.rust-lang.org/reference/items/external-blocks.html)." +"The `cxxbridge` tool is a standalone tool that generates the C++ side of the " +"bridge module. It is included in Android and available as a Soong tool." msgstr "" -#: src/unsafe/unsafe-traits.md:3 +#: src/android/interoperability/cpp/android-cpp-genrules.md:31 msgid "" -"Like with functions, you can mark a trait as `unsafe` if the implementation " -"must guarantee particular conditions to avoid undefined behaviour." +"By convention, if your Rust source file is `lib.rs` your header file will be " +"named `lib.rs.h` and your source file will be named `lib.rs.cc`. This naming " +"convention isn't enforced, though." msgstr "" -#: src/unsafe/unsafe-traits.md:6 +#: src/android/interoperability/cpp/android-build-rust.md:3 msgid "" -"For example, the `zerocopy` crate has an unsafe trait that looks [something " -"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" +"Create a `rust_binary` that depends on `libcxx` and your `cc_library_static`." msgstr "" -#: src/unsafe/unsafe-traits.md:12 -msgid "" -"/// ...\n" -"/// # Safety\n" -"/// The type must have a defined representation and no padding.\n" +#: src/android/interoperability/cpp/android-build-rust.md:7 +msgid "\"cxx_test\"" msgstr "" -#: src/unsafe/unsafe-traits.md:23 -msgid "// Safe because u32 has a defined representation and no padding.\n" +#: src/android/interoperability/cpp/android-build-rust.md:9 +#, fuzzy +msgid "\"libcxx\"" +msgstr "\"libjni\"" + +#: src/android/interoperability/java.md:1 +msgid "Interoperability with Java" msgstr "" -#: src/unsafe/unsafe-traits.md:30 +#: src/android/interoperability/java.md:3 msgid "" -"There should be a `# Safety` section on the Rustdoc for the trait explaining " -"the requirements for the trait to be safely implemented." +"Java can load shared objects via [Java Native Interface (JNI)](https://en." +"wikipedia.org/wiki/Java_Native_Interface). The [`jni` crate](https://docs.rs/" +"jni/) allows you to create a compatible library." msgstr "" -#: src/unsafe/unsafe-traits.md:33 -msgid "" -"The actual safety section for `AsBytes` is rather longer and more " -"complicated." +#: src/android/interoperability/java.md:7 +msgid "First, we create a Rust function to export to Java:" msgstr "" -#: src/unsafe/unsafe-traits.md:35 -msgid "The built-in `Send` and `Sync` traits are unsafe." +#: src/android/interoperability/java.md:9 +msgid "_interoperability/java/src/lib.rs_:" msgstr "" -#: src/exercises/day-3/afternoon.md:1 -msgid "Day 3: Afternoon Exercises" +#: src/android/interoperability/java.md:12 +msgid "//! Rust <-> Java FFI demo.\n" msgstr "" -#: src/exercises/day-3/afternoon.md:3 -msgid "Let us build a safe wrapper for reading directory content!" +#: src/android/interoperability/java.md:17 +msgid "/// HelloWorld::hello method implementation.\n" msgstr "" -#: src/exercises/day-3/afternoon.md:5 -msgid "" -"For this exercise, we suggest using a local dev environment instead of the " -"Playground. This will allow you to run your binary on your own machine." +#: src/android/interoperability/java.md:20 +msgid "\"system\"" +msgstr "\"system\"" + +#: src/android/interoperability/java.md:26 +msgid "\"Hello, {input}!\"" msgstr "" -#: src/exercises/day-3/afternoon.md:8 -msgid "" -"To get started, follow the [running locally](../../cargo/running-locally.md) " -"instructions." +#: src/android/interoperability/java.md:32 +#: src/android/interoperability/java.md:62 +msgid "_interoperability/java/Android.bp_:" +msgstr "_interoperability/java/Android.bp_:" + +#: src/android/interoperability/java.md:36 +#: src/android/interoperability/java.md:69 +msgid "\"libhello_jni\"" +msgstr "\"libhello_jni\"" + +#: src/android/interoperability/java.md:37 +#: src/android/interoperability/java.md:52 +msgid "\"hello_jni\"" +msgstr "\"hello_jni\"" + +#: src/android/interoperability/java.md:39 +msgid "\"libjni\"" +msgstr "\"libjni\"" + +#: src/android/interoperability/java.md:43 +msgid "Finally, we can call this function from Java:" msgstr "" -#: src/exercises/day-3/afternoon.md:14 -msgid "" -"After looking at the exercise, you can look at the [solution](solutions-" -"afternoon.md) provided." +#: src/android/interoperability/java.md:45 +msgid "_interoperability/java/HelloWorld.java_:" +msgstr "" + +#: src/android/interoperability/java.md:66 +msgid "\"helloworld_jni\"" +msgstr "\"helloworld_jni\"" + +#: src/android/interoperability/java.md:67 +msgid "\"HelloWorld.java\"" +msgstr "\"HelloWorld.java\"" + +#: src/android/interoperability/java.md:68 +msgid "\"HelloWorld\"" +msgstr "\"HelloWorld\"" + +#: src/android/interoperability/java.md:73 +msgid "Finally, you can build, sync, and run the binary:" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:3 +#: src/exercises/android/morning.md:3 msgid "" -"Rust has great support for calling functions through a _foreign function " -"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " -"functions you would use from C to read the filenames of a directory." +"This is a group exercise: We will look at one of the projects you work with " +"and try to integrate some Rust into it. Some suggestions:" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:7 -msgid "You will want to consult the manual pages:" +#: src/exercises/android/morning.md:6 +msgid "Call your AIDL service with a client written in Rust." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:9 -msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" +#: src/exercises/android/morning.md:8 +msgid "Move a function from your project to Rust and call it." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:10 -msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" +#: src/exercises/android/morning.md:12 +msgid "" +"No solution is provided here since this is open-ended: it relies on someone " +"in the class having a piece of code which you can turn in to Rust on the fly." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:11 -msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" +#: src/chromium.md:1 +#, fuzzy +msgid "Welcome to Rust in Chromium" +msgstr "\"Velkommen til RustOS 3.14\"" + +#: src/chromium.md:3 +msgid "" +"Rust is supported for third-party libraries in Chromium, with first-party " +"glue code to connect between Rust and existing Chromium C++ code." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:13 +#: src/chromium.md:6 msgid "" -"You will also want to browse the [`std::ffi`](https://doc.rust-lang.org/std/" -"ffi/) module. There you find a number of string types which you need for the " -"exercise:" +"Today, we'll call into Rust to do something silly with strings. If you've " +"got a corner of the code where you're displaying a UTF8 string to the user, " +"feel free to follow this recipe in your part of the codebase instead of the " +"exact part we talk about." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Encoding" +#: src/chromium/setup.md:3 +msgid "" +"Make sure you can build and run Chromium. Any platform and set of build " +"flags is OK, so long as your code is relatively recent (commit position " +"1223636 onwards, corresponding to November 2023):" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Use" +#: src/chromium/setup.md:13 +msgid "" +"(A component, debug build is recommended for quickest iteration time. This " +"is the default!)" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 +#: src/chromium/setup.md:16 msgid "" -"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" -"(https://doc.rust-lang.org/std/string/struct.String.html)" +"See [How to build Chromium](https://www.chromium.org/developers/how-tos/get-" +"the-code/) if you aren't already at that point. Be warned: setting up to " +"build Chromium takes time." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "UTF-8" -msgstr "UTF-8" +#: src/chromium/setup.md:20 +msgid "It's also recommended that you have Visual Studio code installed." +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "Text processing in Rust" +#: src/chromium/setup.md:22 +msgid "About the exercises" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 +#: src/chromium/setup.md:24 msgid "" -"[`CStr`](https://doc.rust-lang.org/std/ffi/struct.CStr.html) and [`CString`]" -"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" +"This part of the course has a series of exercises which build on each other. " +"We'll be doing them spread throughout the course instead of just at the end. " +"If you don't have time to complete a certain part, don't worry: you can " +"catch up in the next slot." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "NUL-terminated" +#: src/chromium/cargo.md:3 +msgid "Subjectively," msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "Communicating with C functions" +#: src/chromium/cargo.md:5 +msgid "" +"```bob\n" +"High ^\n" +" | x cargo\n" +" |\n" +"Development | x \"cargo --offline\"\n" +"speed |\n" +" | x \"gn/ninja\"\n" +" | \"rust_executable(...)\" \n" +"Low +---------------------------------------------------->\n" +" Low Determinism High\n" +"```" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 +#: src/chromium/cargo.md:17 msgid "" -"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " -"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" +"`cargo` works great for pure-Rust tools, but isn't optimized for large " +"multi- language projects like Chromium. Chromium uses `gn` and `ninja`." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "OS-specific" +#: src/chromium/cargo.md:20 +msgid "When writing a tool in Rust, your choices are:" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "Communicating with the OS" +#: src/chromium/cargo.md:22 +msgid "" +"Use `gn` and `ninja` (using the `rust_executable` template we'll meet later)" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:22 -msgid "You will convert between all these types:" +#: src/chromium/cargo.md:24 +msgid "" +"Use `cargo`, but [restrict yourself to Chromium's audited toolchain and " +"crates](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/" +"docs/rust.md#Using-cargo)" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:24 +#: src/chromium/cargo.md:25 msgid "" -"`&str` to `CString`: you need to allocate space for a trailing `\\0` " -"character," +"Use `cargo`, trusting a [toolchain](https://rustup.rs/) and [crates " +"downloaded from the internet](https://crates.io/)" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:25 -msgid "`CString` to `*const i8`: you need a pointer to call C functions," +#: src/chromium/cargo.md:27 +msgid "" +"Your organization's policy, and/or common sense, may prohibit you from doing " +"these things." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:26 -msgid "" -"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " -"character," +#: src/chromium/cargo.md:30 +msgid "From here on we'll be focusing on `gn` and `ninja`." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:27 +#: src/chromium/cargo.md:32 +#, fuzzy +msgid "Mini exercise" +msgstr "Øvelser" + +#: src/chromium/cargo.md:34 msgid "" -"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " -"unknow data\"," +"Discuss in small groups the policies within your own team and organization, " +"and come to a group agreement about what's an acceptable level of risk." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:28 +#: src/chromium/cargo.md:39 msgid "" -"`&[u8]` to `&OsStr`: `&OsStr` is a step towards `OsString`, use [`OsStrExt`]" -"(https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html) to create it," +"Talk about the cultural differences between the `cargo` world and the " +"Chromium world: for instance, that code reuse is cheap in `cargo` and that " +"it's encouraged to use (and create) lots of small single-purpose crates, " +"which is difficult in Chromium (for good reasons). The net effect is that " +"`cargo` ecosystem development feels more agile." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:31 +#: src/chromium/cargo.md:45 msgid "" -"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " -"return it and call `readdir` again." +"Explain that it might seem strange to write tools in Rust, but this is " +"increasingly popular across the industry --- Rust tools are quicker and work " +"more reliably." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:34 +#: src/chromium/cargo.md:49 msgid "" -"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " -"useful chapter about FFI." +"Assuming folks taking the course are physically together, ask them to " +"discuss in small groups of 3-4 people. Then, ask each table whether they've " +"come to a consensus on the level of risk." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:45 +#: src/chromium/cargo.md:53 msgid "" -"Copy the code below to and fill in the missing " -"functions and methods:" +"Later in the course, we'll be running an actual `cargo`\\-based tool, `gnrt`." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:54 -#: src/exercises/day-3/safe-ffi-wrapper.md:67 -#: src/exercises/day-3/safe-ffi-wrapper.md:78 -#: src/exercises/day-3/safe-ffi-wrapper.md:92 -#: src/exercises/day-3/safe-ffi-wrapper.md:100 -#: src/exercises/day-3/solutions-afternoon.md:10 -#: src/exercises/day-3/solutions-afternoon.md:23 -#: src/exercises/day-3/solutions-afternoon.md:34 -#: src/exercises/day-3/solutions-afternoon.md:48 -#: src/exercises/day-3/solutions-afternoon.md:56 -msgid "\"macos\"" -msgstr "\"macos\"" - -#: src/exercises/day-3/safe-ffi-wrapper.md:57 -#: src/exercises/day-3/solutions-afternoon.md:13 -msgid "// Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" +#: src/chromium/policy.md:1 +msgid "Chromium Rust policy" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:64 -#: src/exercises/day-3/solutions-afternoon.md:20 +#: src/chromium/policy.md:3 msgid "" -"// Layout according to the Linux man page for readdir(3), where ino_t and\n" -" // off_t are resolved according to the definitions in\n" -" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" +"Chromium does not yet allow first-party Rust except in rare cases as " +"approved by Chromium's [Area Tech Leads](https://source.chromium.org/" +"chromium/chromium/src/+/main:ATL_OWNERS)." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:77 -#: src/exercises/day-3/solutions-afternoon.md:33 -msgid "// Layout according to the macOS man page for dir(5).\n" +#: src/chromium/policy.md:6 +msgid "" +"Chromium's policy on third party libraries is outlined [here](https://" +"chromium.googlesource.com/chromium/src/+/main/docs/adding_to_third_party." +"md#rust) - Rust is allowed for third party libraries under various " +"circumstances, including if they're the best option for performance or for " +"security." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:92 -#: src/exercises/day-3/safe-ffi-wrapper.md:100 -#: src/exercises/day-3/solutions-afternoon.md:48 -#: src/exercises/day-3/solutions-afternoon.md:56 -msgid "\"x86_64\"" -msgstr "\"x86_64\"" - -#: src/exercises/day-3/safe-ffi-wrapper.md:95 -#: src/exercises/day-3/solutions-afternoon.md:51 +#: src/chromium/policy.md:10 msgid "" -"// See https://github.com/rust-lang/libc/issues/414 and the section on\n" -" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" -" //\n" -" // \"Platforms that existed before these updates were available\" " -"refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " -"PowerPC.\n" +"Very few Rust libraries directly expose a C/C++ API, so that means that " +"nearly all such libraries will require a small amount of first-party glue " +"code." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:101 -#: src/exercises/day-3/solutions-afternoon.md:57 -msgid "\"readdir$INODE64\"" -msgstr "\"readdir$INODE64\"" +#: src/chromium/policy.md:13 +#, fuzzy +msgid "" +"```bob\n" +"C++ Rust\n" +".- - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": Existing Chromium : : Chromium Rust Existing " +"Rust :\n" +": \"C++\" : : \"wrapper\" " +"crate :\n" +": +---------------+ : : +----------------+ +-------------" +"+ :\n" +": | | : : | | | " +"| :\n" +": | o-----+-+-----------+-+-> o-+----------+--> " +"| :\n" +": | | : Language : | | Crate | " +"| :\n" +": +---------------+ : boundary : +----------------+ API +-------------" +"+ :\n" +": : : :\n" +"`- - - - - - - - - -' `- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" +msgstr "" +"```bob\n" +" Stak Heap\n" +".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": " +"list : : :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " +"| :\n" +": +----+----+ : : +----+----+ +----+------" +"+ :\n" +": : : :\n" +": : : :\n" +"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" -#: src/exercises/day-3/safe-ffi-wrapper.md:119 -#: src/exercises/day-3/solutions-afternoon.md:75 +#: src/chromium/policy.md:28 msgid "" -"// Call opendir and return a Ok value if that worked,\n" -" // otherwise return Err with a message.\n" +"First-party Rust glue code for a particular third-party crate should " +"normally be kept in `third_party/rust///wrapper`." msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:128 -msgid "// Keep calling readdir until we get a NULL pointer back.\n" +#: src/chromium/policy.md:31 +msgid "Because of this, today's course will be heavily focused on:" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:135 -#: src/exercises/day-3/solutions-afternoon.md:108 -msgid "// Call closedir as needed.\n" +#: src/chromium/policy.md:33 +msgid "Bringing in third-party Rust libraries (\"crates\")" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:141 -#: src/android/interoperability/with-c/rust.md:44 -#: src/exercises/day-3/solutions-afternoon.md:119 -#: src/exercises/day-3/solutions-afternoon.md:143 -#: src/exercises/day-3/solutions-afternoon.md:158 -msgid "\".\"" -msgstr "\".\"" +#: src/chromium/policy.md:34 +msgid "Writing glue code to be able to use those crates from Chromium C++." +msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:142 -#: src/exercises/day-3/solutions-afternoon.md:120 -msgid "\"files: {:#?}\"" +#: src/chromium/policy.md:36 +msgid "If this policy changes over time, the course will evolve to keep up." msgstr "" -#: src/android.md:1 -msgid "Welcome to Rust in Android" +#: src/chromium/build-rules.md:1 +msgid "Build rules" msgstr "" -#: src/android.md:3 +#: src/chromium/build-rules.md:3 msgid "" -"Rust is supported for native platform development on Android. This means " -"that you can write new operating system services in Rust, as well as " -"extending existing services." +"Rust code is usually built using `cargo`. Chromium builds with `gn` and " +"`ninja` for efficiency --- its static rules allow maximum parallelism. Rust " +"is no exception." msgstr "" -#: src/android.md:7 -msgid "" -"We will attempt to call Rust from one of your own projects today. So try to " -"find a little corner of your code base where we can move some lines of code " -"to Rust. The fewer dependencies and \"exotic\" types the better. Something " -"that parses some raw bytes would be ideal." +#: src/chromium/build-rules.md:6 +msgid "Adding Rust code to Chromium" msgstr "" -#: src/android/setup.md:3 +#: src/chromium/build-rules.md:8 msgid "" -"We will be using an Android Virtual Device to test our code. Make sure you " -"have access to one or create a new one with:" +"In some existing Chromium `BUILD.gn` file, declare a `rust_static_library`:" msgstr "" -#: src/android/setup.md:12 +#: src/chromium/build-rules.md:10 msgid "" -"Please see the [Android Developer Codelab](https://source.android.com/docs/" -"setup/start) for details." +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"```" msgstr "" -#: src/android/build-rules.md:3 -msgid "The Android build system (Soong) supports Rust via a number of modules:" +#: src/chromium/build-rules.md:19 +msgid "" +"You can also add `deps` on other Rust targets. Later we'll use this to " +"depend upon third party code." msgstr "" -#: src/android/build-rules.md:5 -msgid "Module Type" +#: src/chromium/build-rules.md:24 +msgid "" +"You must specify _both_ the crate root, _and_ a full list of sources. The " +"`crate_root` is the file given to the Rust compiler representing the root " +"file of the compilation unit --- typically `lib.rs`. `sources` is a complete " +"list of all source files which `ninja` needs in order to determine when " +"rebuilds are necessary." msgstr "" -#: src/android/build-rules.md:5 -msgid "Description" +#: src/chromium/build-rules.md:30 +msgid "" +"(There's no such thing as a Rust `source_set`, because in Rust, an entire " +"crate is a compilation unit. A `static_library` is the smallest unit.)" msgstr "" -#: src/android/build-rules.md:7 -msgid "`rust_binary`" -msgstr "`rust_binary`" - -#: src/android/build-rules.md:7 -msgid "Produces a Rust binary." +#: src/chromium/build-rules.md:33 +msgid "" +"Students might be wondering why we need a gn template, rather than using " +"[gn's built-in support for Rust static libraries](https://gn.googlesource." +"com/gn/+/main/docs/reference.md#func_static_library). The answer is that " +"this template provides support for cxx interop, Rust features, and unit " +"tests, some of which we'll use later." msgstr "" -#: src/android/build-rules.md:8 -msgid "`rust_library`" -msgstr "`rust_library`" - -#: src/android/build-rules.md:8 -msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." +#: src/chromium/build-rules/unsafe.md:1 +msgid "Including `unsafe` Rust code" msgstr "" -#: src/android/build-rules.md:9 -msgid "`rust_ffi`" -msgstr "`rust_ffi`" +#: src/chromium/build-rules/unsafe.md:3 +msgid "" +"Unsafe Rust code is forbidden in `rust_static_library` by default --- it " +"won't compile. If you need unsafe Rust code, add `allow_unsafe = true` to " +"the gn target. (Later in the course we'll see circumstances where this is " +"necessary.)" +msgstr "" -#: src/android/build-rules.md:9 +#: src/chromium/build-rules/unsafe.md:7 msgid "" -"Produces a Rust C library usable by `cc` modules, and provides both static " -"and shared variants." +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [\n" +" \"lib.rs\",\n" +" \"hippopotamus.rs\"\n" +" ]\n" +" allow_unsafe = true\n" +"}\n" +"```" msgstr "" -#: src/android/build-rules.md:10 -msgid "`rust_proc_macro`" -msgstr "`rust_proc_macro`" +#: src/chromium/build-rules/depending.md:3 +msgid "Simply add the above target to the `deps` of some Chromium C++ target." +msgstr "" -#: src/android/build-rules.md:10 +#: src/chromium/build-rules/depending.md:5 msgid "" -"Produces a `proc-macro` Rust library. These are analogous to compiler " -"plugins." +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"\n" +"# or source_set, static_library etc.\n" +"component(\"preexisting_cpp\") {\n" +" deps = [ \":my_rust_lib\" ]\n" +"}\n" +"```" msgstr "" -#: src/android/build-rules.md:11 -msgid "`rust_test`" -msgstr "`rust_test`" +#: src/chromium/build-rules/vscode.md:3 +msgid "" +"Types are elided in Rust code, which makes a good IDE even more useful than " +"for C++. Visual Studio code works well for Rust in Chromium. To use it," +msgstr "" -#: src/android/build-rules.md:11 -msgid "Produces a Rust test binary that uses the standard Rust test harness." +#: src/chromium/build-rules/vscode.md:6 +msgid "" +"Ensure your VSCode has the `rust-analyzer` extension, not earlier forms of " +"Rust support" msgstr "" -#: src/android/build-rules.md:12 -msgid "`rust_fuzz`" -msgstr "`rust_fuzz`" +#: src/chromium/build-rules/vscode.md:8 +msgid "" +"`gn gen out/Debug --export-rust-project` (or equivalent for your output " +"directory)" +msgstr "" -#: src/android/build-rules.md:12 -msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." +#: src/chromium/build-rules/vscode.md:10 +msgid "`ln -s out/Debug/rust-project.json rust-project.json`" msgstr "" -#: src/android/build-rules.md:13 -msgid "`rust_protobuf`" -msgstr "`rust_protobuf`" +#: src/exercises/chromium/build-rules.md:1 +msgid "Build rules exercise" +msgstr "" -#: src/android/build-rules.md:13 +#: src/exercises/chromium/build-rules.md:3 msgid "" -"Generates source and produces a Rust library that provides an interface for " -"a particular protobuf." +"In your Chromium build, add a new Rust target to `//ui/base/BUILD.gn` " +"containing:" msgstr "" -#: src/android/build-rules.md:14 -msgid "`rust_bindgen`" -msgstr "`rust_bindgen`" - -#: src/android/build-rules.md:14 +#: src/exercises/chromium/build-rules.md:11 msgid "" -"Generates source and produces a Rust library containing Rust bindings to C " -"libraries." +"**Important**: note that `no_mangle` here is considered a type of unsafety " +"by the Rust compiler, so you'll need to to allow unsafe code in your `gn` " +"target." msgstr "" -#: src/android/build-rules.md:16 -msgid "We will look at `rust_binary` and `rust_library` next." +#: src/exercises/chromium/build-rules.md:15 +msgid "" +"Add this new Rust target as a dependency of `//ui/base:base`. Declare this " +"function at the top of `ui/base/resource/resource_bundle.cc` (later, we'll " +"see how this can be automated by bindings generation tools):" msgstr "" -#: src/android/build-rules/binary.md:1 -msgid "Rust Binaries" +#: src/exercises/chromium/build-rules.md:22 +msgid "" +"Call this function from somewhere in `ui/base/resource/resource_bundle.cc` - " +"we suggest the top of `ResourceBundle::MaybeMangleLocalizedString`. Build " +"and run Chromium, and ensure that \"Hello from Rust!\" is printed lots of " +"times." msgstr "" -#: src/android/build-rules/binary.md:3 +#: src/exercises/chromium/build-rules.md:26 msgid "" -"Let us start with a simple application. At the root of an AOSP checkout, " -"create the following files:" +"If you use VSCode, now set up Rust to work well in VSCode. It will be useful " +"in subsequent exercises. If you've succeeded, you will be able to use right-" +"click \"Go to definition\" on `println!`." msgstr "" -#: src/android/build-rules/binary.md:6 src/android/build-rules/library.md:13 -msgid "_hello_rust/Android.bp_:" -msgstr "_hello_rust/Android.bp_:" - -#: src/android/build-rules/binary.md:10 src/android/build-rules/binary.md:11 -msgid "\"hello_rust\"" -msgstr "\"hello_rust\"" - -#: src/android/build-rules/binary.md:12 src/android/build-rules/library.md:19 -#: src/android/logging.md:12 -msgid "\"src/main.rs\"" -msgstr "\"src/main.rs\"" - -#: src/android/build-rules/binary.md:16 src/android/build-rules/library.md:34 -msgid "_hello_rust/src/main.rs_:" -msgstr "_hello_rust/src/main.rs_:" +#: src/exercises/chromium/build-rules.md:30 +#: src/exercises/chromium/interoperability-with-cpp.md:47 +msgid "Where to find help" +msgstr "" -#: src/android/build-rules/binary.md:19 src/android/build-rules/library.md:37 -msgid "//! Rust demo.\n" +#: src/exercises/chromium/build-rules.md:32 +msgid "" +"The options available to the [`rust_static_library` gn template](https://" +"source.chromium.org/chromium/chromium/src/+/main:build/rust/" +"rust_static_library.gni;l=16)" msgstr "" -#: src/android/build-rules/binary.md:20 src/android/build-rules/library.md:41 -msgid "/// Prints a greeting to standard output.\n" +#: src/exercises/chromium/build-rules.md:33 +msgid "" +"Information about [`#[no_mangle]`](https://doc.rust-lang.org/beta/reference/" +"abi.html#the-no_mangle-attribute)" msgstr "" -#: src/android/build-rules/binary.md:23 -msgid "\"Hello from Rust!\"" +#: src/exercises/chromium/build-rules.md:34 +msgid "" +"Information about [`extern \"C\"`](https://doc.rust-lang.org/std/keyword." +"extern.html)" msgstr "" -#: src/android/build-rules/binary.md:27 -msgid "You can now build, push, and run the binary:" +#: src/exercises/chromium/build-rules.md:35 +msgid "" +"Information about gn's [`--export-rust-project`](https://gn.googlesource.com/" +"gn/+/main/docs/reference.md#compilation-database) switch" msgstr "" -#: src/android/build-rules/binary.md:29 +#: src/exercises/chromium/build-rules.md:36 msgid "" -"```shell\n" -"m hello_rust\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust /data/local/tmp\"\n" -"adb shell /data/local/tmp/hello_rust\n" -"```" +"[How to install rust-analyzer in VSCode](https://code.visualstudio.com/docs/" +"languages/rust)" msgstr "" -"```shell\n" -"m hello_rust\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust /data/local/tmp\"\n" -"adb shell /data/local/tmp/hello_rust\n" -"```" -#: src/android/build-rules/library.md:1 -msgid "Rust Libraries" +#: src/exercises/chromium/build-rules.md:42 +msgid "" +"This example is unusual because it boils down to the lowest-common-" +"denominator interop language, C. Both C++ and Rust can natively declare and " +"call C ABI functions. Later in the course, we'll connect C++ directly to " +"Rust." msgstr "" -#: src/android/build-rules/library.md:3 -msgid "You use `rust_library` to create a new Rust library for Android." +#: src/exercises/chromium/build-rules.md:46 +msgid "" +"`allow_unsafe = true` is required here because `#[no_mangle]` might allow " +"Rust to generate two functions with the same name, and Rust can no longer " +"guarantee that the right one is called." msgstr "" -#: src/android/build-rules/library.md:5 -msgid "Here we declare a dependency on two libraries:" +#: src/exercises/chromium/build-rules.md:50 +msgid "" +"If you need a pure Rust executable, you can also do that using the " +"`rust_executable` gn template." msgstr "" -#: src/android/build-rules/library.md:7 -msgid "`libgreeting`, which we define below," +#: src/chromium/interoperability-with-cpp.md:3 +msgid "" +"The Rust community offers multiple options for C++/Rust interop, with new " +"tools being developed all the time. At the moment, Chromium uses a tool " +"called \"cxx\"." msgstr "" -#: src/android/build-rules/library.md:8 +#: src/chromium/interoperability-with-cpp.md:6 msgid "" -"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" -"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" -"crates/)." +"You describe your whole language boundary in an interface definition " +"language (which looks a lot like Rust) and then cxx tools generate " +"declarations for functions and types in both Rust and C++." msgstr "" -#: src/android/build-rules/library.md:17 src/android/build-rules/library.md:18 -msgid "\"hello_rust_with_dep\"" -msgstr "\"hello_rust_with_dep\"" +#: src/chromium/interoperability-with-cpp.md:12 +msgid "" +"See the [CXX tutorial](https://cxx.rs/tutorial.html) for a full example of " +"using this." +msgstr "" -#: src/android/build-rules/library.md:21 src/android/build-rules/library.md:28 -msgid "\"libgreetings\"" -msgstr "\"libgreetings\"" +#: src/chromium/interoperability-with-cpp.md:21 +msgid "" +"Talk through the diagram. Explain that behind the scenes, this is doing just " +"the same as you previously did --- but by programmatically ensuring that the " +"C++ and Rust sides match, cxx can ensure there aren't obvious errors with " +"object lifetimes, string lengths, etc. It reduces lots of fiddly boilerplate " +"and the resulting code feels more \"natural\"." +msgstr "" -#: src/android/build-rules/library.md:22 -msgid "\"libtextwrap\"" -msgstr "\"libtextwrap\"" +#: src/chromium/interoperability-with-cpp/example-bindings.md:3 +msgid "" +"cxx requires you to declare the whole C++/Rust boundary in one of your `.rs` " +"files. For instance:" +msgstr "" -#: src/android/build-rules/library.md:29 -msgid "\"greetings\"" -msgstr "\"greetings\"" +#: src/chromium/interoperability-with-cpp/example-bindings.md:16 +msgid "\"example/include/blobstore.h\"" +msgstr "" -#: src/android/build-rules/library.md:30 src/android/aidl/implementation.md:31 -#: src/android/interoperability/java.md:38 -msgid "\"src/lib.rs\"" -msgstr "\"src/lib.rs\"" +#: src/chromium/interoperability-with-cpp/example-bindings.md:24 +msgid "// Definitions of Rust types and functions go here\n" +msgstr "" -#: src/android/build-rules/library.md:48 -msgid "_hello_rust/src/lib.rs_:" -msgstr "_hello_rust/src/lib.rs_:" +#: src/chromium/interoperability-with-cpp/example-bindings.md:31 +msgid "Native support for C++'s `std::unique_ptr` in Rust" +msgstr "" -#: src/android/build-rules/library.md:51 -msgid "//! Greeting library.\n" +#: src/chromium/interoperability-with-cpp/example-bindings.md:32 +msgid "Native support for Rust slices in C++" msgstr "" -#: src/android/build-rules/library.md:52 -msgid "/// Greet `name`.\n" +#: src/chromium/interoperability-with-cpp/example-bindings.md:33 +msgid "Calls from C++ to Rust, and Rust types (in the top part)" msgstr "" -#: src/android/build-rules/library.md:55 -msgid "\"Hello {name}, it is very nice to meet you!\"" +#: src/chromium/interoperability-with-cpp/example-bindings.md:34 +msgid "Calls from Rust to C++, and C++ types (in the bottom part)" msgstr "" -#: src/android/build-rules/library.md:59 -msgid "You build, push, and run the binary like before:" +#: src/chromium/interoperability-with-cpp/example-bindings.md:35 +msgid "" +"If the function definitions in C++ or Rust don't match the cxx::bridge, a " +"compilation failure results." msgstr "" -#: src/android/build-rules/library.md:61 +#: src/chromium/interoperability-with-cpp/example-bindings.md:38 msgid "" -"```shell\n" -"m hello_rust_with_dep\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_with_dep\n" -"```" +"**Common misconception**: It _looks_ like a C++ header is being parser by " +"Rust, but this is misleading. This header is never interpreted by Rust, but " +"simply `#include`d in the generated C++ code for the benefit of C++ " +"compilers." msgstr "" -"```shell\n" -"m hello_rust_with_dep\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_with_dep /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_with_dep\n" -"```" -#: src/android/aidl.md:3 +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:3 msgid "" -"The [Android Interface Definition Language (AIDL)](https://developer.android." -"com/guide/components/aidl) is supported in Rust:" +"By far the most useful page when using cxx is the [type reference](https://" +"cxx.rs/bindings.html)." msgstr "" -#: src/android/aidl.md:6 -msgid "Rust code can call existing AIDL servers," +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:5 +msgid "cxx fundamentally suits cases where:" msgstr "" -#: src/android/aidl.md:7 -msgid "You can create new AIDL servers in Rust." +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:7 +msgid "" +"Your Rust-C++ interface is sufficiently simple that you can declare all of " +"it." msgstr "" -#: src/android/aidl/interface.md:1 -msgid "AIDL Interfaces" +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:8 +msgid "" +"You're using only the types natively supported by cxx already, for example " +"`std::unique_ptr`, `std::string`, `&[u8]` etc." msgstr "" -#: src/android/aidl/interface.md:3 -msgid "You declare the API of your service using an AIDL interface:" +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:11 +msgid "" +"It has many limitations --- for example lack of support for Rust's `Option` " +"type." msgstr "" -#: src/android/aidl/interface.md:5 +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:13 msgid "" -"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +"These limitations constrain us to using Rust in Chromium only for well " +"isolated \"leaf nodes\" rather than for arbitrary Rust-C++ interop. When " +"considering a use-case for Rust in Chromium, a good starting point is to " +"draft the cxx bindings for the language boundary to see if it appears simple " +"enough." msgstr "" -"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" -#: src/android/aidl/interface.md:17 -msgid "_birthday_service/aidl/Android.bp_:" -msgstr "_birthday_service/aidl/Android.bp_:" +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:26 +msgid "" +"You should also discuss some of the other sticky points with cxx, for " +"example:" +msgstr "" -#: src/android/aidl/interface.md:21 -msgid "\"com.example.birthdayservice\"" -msgstr "\"com.example.birthdayservice\"" +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:28 +msgid "" +"Its error handling is based around C++ exceptions (given on the next slide)" +msgstr "" -#: src/android/aidl/interface.md:22 -msgid "\"com/example/birthdayservice/*.aidl\"" -msgstr "\"com/example/birthdayservice/*.aidl\"" +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md:29 +msgid "Function pointers are awkward to use." +msgstr "" -#: src/android/aidl/interface.md:25 -msgid "// Rust is not enabled by default\n" +#: src/chromium/interoperability-with-cpp/error-handling.md:3 +msgid "" +"cxx's support for `Result` relies on C++ exceptions, so we can't use " +"that in Chromium. Alternatives:" msgstr "" -#: src/android/aidl/interface.md:32 +#: src/chromium/interoperability-with-cpp/error-handling.md:6 msgid "" -"Add `vendor_available: true` if your AIDL file is used by a binary in the " -"vendor partition." +"Where success can be represented as a simple Boolean, as done in our [QR " +"code generator](https://source.chromium.org/chromium/chromium/src/+/main:" +"components/qr_code_generator/qr_code_generator_ffi_glue.rs;l=10): Return a " +"Boolean representing success, and record results using out-parameters:" msgstr "" -#: src/android/aidl/implementation.md:1 -msgid "Service Implementation" +#: src/chromium/interoperability-with-cpp/error-handling.md:9 +msgid "\"qr_code_generator\"" msgstr "" -#: src/android/aidl/implementation.md:3 -msgid "We can now implement the AIDL service:" +#: src/chromium/interoperability-with-cpp/error-handling.md:21 +msgid "" +"Where success is more complex, provide a Rust object which can be queried " +"for details of success or failure:" msgstr "" -#: src/android/aidl/implementation.md:5 -msgid "_birthday_service/src/lib.rs_:" -msgstr "_birthday_service/src/lib.rs_:" +#: src/chromium/interoperability-with-cpp/error-handling.md:29 +msgid "// whether successful\n" +msgstr "" -#: src/android/aidl/implementation.md:8 -msgid "//! Implementation of the `IBirthdayService` AIDL interface.\n" +#: src/chromium/interoperability-with-cpp/error-handling.md:30 +msgid "// or some more complex error type\n" msgstr "" -#: src/android/aidl/implementation.md:11 -msgid "/// The `IBirthdayService` implementation.\n" +#: src/chromium/interoperability-with-cpp/error-handling.md:32 +msgid "// or some more complex success type\n" msgstr "" -#: src/android/aidl/implementation.md:20 -msgid "\"Happy Birthday {name}, congratulations with the {years} years!\"" +#: src/chromium/interoperability-with-cpp/error-handling.md:38 +msgid "The best way to learn cxx is by doing, so, another exercise!" msgstr "" -#: src/android/aidl/implementation.md:26 src/android/aidl/server.md:28 -#: src/android/aidl/client.md:37 -msgid "_birthday_service/Android.bp_:" -msgstr "_birthday_service/Android.bp_:" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:3 +msgid "" +"In Chromium, we define an independent `#[cxx::bridge] mod` for each leaf-" +"node where we want to use Rust. You'd typically have one for each " +"`rust_static_library`. Just add" +msgstr "" -#: src/android/aidl/implementation.md:30 src/android/aidl/server.md:38 -msgid "\"libbirthdayservice\"" -msgstr "\"libbirthdayservice\"" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:7 +msgid "" +"```gn\n" +"cxx_bindings = [ \"my_rust_file.rs\" ]\n" +" # list of files containing #[cxx::bridge], not all source files\n" +"allow_unsafe = true\n" +"```" +msgstr "" -#: src/android/aidl/implementation.md:32 src/android/aidl/server.md:13 -#: src/android/aidl/client.md:12 -msgid "\"birthdayservice\"" -msgstr "\"birthdayservice\"" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:13 +msgid "" +"to your existing `rust_static_library` target alongside `crate_root` and " +"`sources`." +msgstr "" -#: src/android/aidl/implementation.md:34 src/android/aidl/server.md:36 -#: src/android/aidl/client.md:45 -msgid "\"com.example.birthdayservice-rust\"" -msgstr "\"com.example.birthdayservice-rust\"" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:16 +msgid "C++ headers will be generated at a sensible location, so you can just" +msgstr "" -#: src/android/aidl/implementation.md:35 src/android/aidl/server.md:37 -#: src/android/aidl/client.md:46 -msgid "\"libbinder_rs\"" -msgstr "\"libbinder_rs\"" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:19 +msgid "\"ui/base/my_rust_file.rs.h\"" +msgstr "" -#: src/android/aidl/server.md:1 -msgid "AIDL Server" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:22 +msgid "" +"You will find some utility functions in `//base` to convert to/from Chromium " +"C++ types to cxx Rust types --- for example [`SpanToRustSlice`](https://" +"source.chromium.org/chromium/chromium/src/+/main:base/containers/span_rust.h;" +"l=21)." msgstr "" -#: src/android/aidl/server.md:3 -msgid "Finally, we can create a server which exposes the service:" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:27 +msgid "Students may ask --- why do we still need `allow_unsafe = true`?" msgstr "" -#: src/android/aidl/server.md:5 -msgid "_birthday_service/src/server.rs_:" -msgstr "_birthday_service/src/server.rs_:" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:29 +msgid "" +"The broad answer is that no C/C++ code is \"safe\" by the normal Rust " +"standards. Calling back and forth to C/C++ from Rust may do arbitrary things " +"to memory, and compromise the safety of Rust's own data layouts. Presence of " +"_too many_ `unsafe` keywords in C/C++ interop can harm the signal-to-noise " +"ratio of such a keyword, and is [controversial](https://steveklabnik.com/" +"writing/the-cxx-debate), but strictly, bringing any foreign code into a Rust " +"binary can cause unexpected behavior from Rust's perspective." +msgstr "" -#: src/android/aidl/server.md:8 src/android/aidl/client.md:8 -msgid "//! Birthday service.\n" +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md:36 +msgid "" +"The narrow answer lies in the diagram at the top of this page --- behind the " +"scenes, cxx generates Rust `unsafe` and `extern \"C\"` functions just like " +"we did manually in the previous section." msgstr "" -#: src/android/aidl/server.md:14 -msgid "/// Entry point for birthday service.\n" +#: src/exercises/chromium/interoperability-with-cpp.md:1 +msgid "Exercise: Interoperability with C++" msgstr "" -#: src/android/aidl/server.md:23 -msgid "\"Failed to register service\"" +#: src/exercises/chromium/interoperability-with-cpp.md:3 +msgid "Part one" msgstr "" -#: src/android/aidl/server.md:32 src/android/aidl/server.md:33 -msgid "\"birthday_server\"" -msgstr "\"birthday_server\"" +#: src/exercises/chromium/interoperability-with-cpp.md:5 +msgid "" +"In the Rust file you previously created, add a `#[cxx::bridge]` which " +"specifies a single function, to be called from C++, called " +"`hello_from_rust`, taking no parameters and returning no value." +msgstr "" -#: src/android/aidl/server.md:34 -msgid "\"src/server.rs\"" -msgstr "\"src/server.rs\"" +#: src/exercises/chromium/interoperability-with-cpp.md:8 +msgid "" +"Modify your previous `hello_from_rust` function to remove `extern \"C\"` and " +"`#[no_mangle]`. This is now just a standard Rust function." +msgstr "" -#: src/android/aidl/deploy.md:3 -msgid "We can now build, push, and start the service:" +#: src/exercises/chromium/interoperability-with-cpp.md:10 +msgid "Modify your `gn` target to build these bindings." msgstr "" -#: src/android/aidl/deploy.md:5 +#: src/exercises/chromium/interoperability-with-cpp.md:11 msgid "" -"```shell\n" -"m birthday_server\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_server\n" -"```" +"In your C++ code, remove the forward-declaration of `hello_from_rust`. " +"Instead, include the generated header file." msgstr "" -"```shell\n" -"m birthday_server\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_server\n" -"```" -#: src/android/aidl/deploy.md:11 -msgid "In another terminal, check that the service runs:" +#: src/exercises/chromium/interoperability-with-cpp.md:13 +msgid "Build and run!" msgstr "" -#: src/android/aidl/deploy.md:21 -msgid "You can also call the service with `service call`:" +#: src/exercises/chromium/interoperability-with-cpp.md:15 +msgid "Part two" msgstr "" -#: src/android/aidl/client.md:1 -msgid "AIDL Client" +#: src/exercises/chromium/interoperability-with-cpp.md:17 +msgid "" +"It's a good idea to play with cxx a little. It helps you think about how " +"flexible Rust in Chromium actually is." msgstr "" -#: src/android/aidl/client.md:3 -msgid "Finally, we can create a Rust client for our new service." +#: src/exercises/chromium/interoperability-with-cpp.md:20 +msgid "Some things to try:" msgstr "" -#: src/android/aidl/client.md:5 -msgid "_birthday_service/src/client.rs_:" -msgstr "_birthday_service/src/client.rs_:" - -#: src/android/aidl/client.md:13 -msgid "/// Connect to the BirthdayService.\n" +#: src/exercises/chromium/interoperability-with-cpp.md:22 +msgid "Call back into C++ from Rust. You will need:" msgstr "" -#: src/android/aidl/client.md:18 -msgid "/// Call the birthday service.\n" +#: src/exercises/chromium/interoperability-with-cpp.md:23 +msgid "" +"An additional header file which you can `include!` from your `cxx::bridge`. " +"You'll need to declare your C++ function in that new header file." msgstr "" -#: src/android/aidl/client.md:30 -msgid "\"Failed to connect to BirthdayService\"" +#: src/exercises/chromium/interoperability-with-cpp.md:25 +msgid "" +"An `unsafe` block to call such a function, or alternatively specify the " +"`unsafe` keyword in your `#[cxx::bridge]` [as described here](https://cxx.rs/" +"extern-c++.html#functions-and-member-functions)." msgstr "" -#: src/android/aidl/client.md:32 -msgid "\"{msg}\"" -msgstr "\"{msg}\"" +#: src/exercises/chromium/interoperability-with-cpp.md:27 +msgid "" +"You may also need to `#include \"third_party/rust/cxx/v1/crate/include/cxx." +"h\"`" +msgstr "" -#: src/android/aidl/client.md:41 src/android/aidl/client.md:42 -msgid "\"birthday_client\"" -msgstr "\"birthday_client\"" +#: src/exercises/chromium/interoperability-with-cpp.md:28 +msgid "Pass a C++ string from C++ into Rust." +msgstr "" -#: src/android/aidl/client.md:43 -msgid "\"src/client.rs\"" -msgstr "\"src/client.rs\"" +#: src/exercises/chromium/interoperability-with-cpp.md:29 +msgid "Pass a reference to a C++ object into Rust." +msgstr "" -#: src/android/aidl/client.md:52 -msgid "Notice that the client does not depend on `libbirthdayservice`." +#: src/exercises/chromium/interoperability-with-cpp.md:30 +msgid "" +"Intentionally get the Rust function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." msgstr "" -#: src/android/aidl/client.md:54 -msgid "Build, push, and run the client on your device:" +#: src/exercises/chromium/interoperability-with-cpp.md:32 +msgid "" +"Intentionally get the C++ function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." msgstr "" -#: src/android/aidl/client.md:56 +#: src/exercises/chromium/interoperability-with-cpp.md:34 msgid "" -"```shell\n" -"m birthday_client\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_client Charlie 60\n" -"```" +"Pass a `std::unique_ptr` of some type from C++ into Rust, so that Rust can " +"own some C++ object." msgstr "" -"```shell\n" -"m birthday_client\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/birthday_client Charlie 60\n" -"```" -#: src/android/aidl/changing.md:3 +#: src/exercises/chromium/interoperability-with-cpp.md:36 msgid "" -"Let us extend the API with more functionality: we want to let clients " -"specify a list of lines for the birthday card:" +"Create a Rust object and pass it into C++, so that C++ owns it. (Hint: you " +"need a `Box`)." msgstr "" -#: src/android/logging.md:3 +#: src/exercises/chromium/interoperability-with-cpp.md:38 +msgid "Declare some methods on a C++ type. Call them from Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:39 +msgid "Declare some methods on a Rust type. Call them from C++." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:41 +msgid "Part three" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md:43 msgid "" -"You should use the `log` crate to automatically log to `logcat` (on-device) " -"or `stdout` (on-host):" +"Now you understand the strengths and limitations of cxx interop, think of a " +"couple of use-cases for Rust in Chromium where the interface would be " +"sufficiently simple. Sketch how you might define that interface." msgstr "" -#: src/android/logging.md:6 -msgid "_hello_rust_logs/Android.bp_:" -msgstr "_hello_rust_logs/Android.bp_:" +#: src/exercises/chromium/interoperability-with-cpp.md:49 +msgid "The [cxx binding reference](https://cxx.rs/bindings.html)" +msgstr "" -#: src/android/logging.md:10 src/android/logging.md:11 -msgid "\"hello_rust_logs\"" -msgstr "\"hello_rust_logs\"" +#: src/exercises/chromium/interoperability-with-cpp.md:50 +msgid "" +"The [`rust_static_library` gn template](https://source.chromium.org/chromium/" +"chromium/src/+/main:build/rust/rust_static_library.gni;l=16)" +msgstr "" -#: src/android/logging.md:14 -msgid "\"liblog_rust\"" -msgstr "\"liblog_rust\"" +#: src/exercises/chromium/interoperability-with-cpp.md:56 +msgid "Some of the questions you may encounter:" +msgstr "" -#: src/android/logging.md:15 -msgid "\"liblogger\"" -msgstr "\"liblogger\"" +#: src/exercises/chromium/interoperability-with-cpp.md:57 +msgid "" +"I'm seeing a problem initializing a variable of type X with type Y, where X " +"and Y are both function types. This is because your C++ function doesn't " +"quite match the declaration in your `cxx::bridge`." +msgstr "" -#: src/android/logging.md:22 -msgid "_hello_rust_logs/src/main.rs_:" -msgstr "_hello_rust_logs/src/main.rs_:" +#: src/exercises/chromium/interoperability-with-cpp.md:61 +msgid "" +"I seem to be able to freely convert C++ references into Rust references. " +"Doesn't that risk UB? For cxx's _opaque_ types, no, because they are zero-" +"sized. For cxx trivial types yes, it's _possible_ to cause UB, although " +"cxx's design makes it quite difficult to craft such an example." +msgstr "" -#: src/android/logging.md:25 -msgid "//! Rust logging demo.\n" +#: src/chromium/adding-third-party-crates.md:3 +msgid "" +"Rust libraries are called \"crates\" and are found at [crates.io](https://" +"crates.io). It's _very easy_ for Rust crates to depend upon one another. So " +"they do!" msgstr "" -#: src/android/logging.md:28 -msgid "/// Logs a greeting.\n" +#: src/chromium/adding-third-party-crates.md:6 +msgid "C++ library" msgstr "" -#: src/android/logging.md:33 -msgid "\"rust\"" -msgstr "\"rust\"" +#: src/chromium/adding-third-party-crates.md:6 +#, fuzzy +msgid "Rust crate" +msgstr "Rust's økosystem" -#: src/android/logging.md:36 -msgid "\"Starting program.\"" +#: src/chromium/adding-third-party-crates.md:8 +#, fuzzy +msgid "Build system" +msgstr "Rust's økosystem" + +#: src/chromium/adding-third-party-crates.md:8 +#: src/chromium/adding-third-party-crates.md:10 +msgid "Lots" msgstr "" -#: src/android/logging.md:37 -msgid "\"Things are going fine.\"" +#: src/chromium/adding-third-party-crates.md:8 +msgid "Consistent: `Cargo.toml`" msgstr "" -#: src/android/logging.md:38 -msgid "\"Something went wrong!\"" +#: src/chromium/adding-third-party-crates.md:9 +msgid "Typical library size" msgstr "" -#: src/android/logging.md:42 src/android/interoperability/with-c/bindgen.md:98 -#: src/android/interoperability/with-c/rust.md:73 -msgid "Build, push, and run the binary on your device:" +#: src/chromium/adding-third-party-crates.md:9 +msgid "Large-ish" msgstr "" -#: src/android/logging.md:44 -msgid "" -"```shell\n" -"m hello_rust_logs\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_logs\n" -"```" +#: src/chromium/adding-third-party-crates.md:9 +msgid "Small" msgstr "" -"```shell\n" -"m hello_rust_logs\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/hello_rust_logs\n" -"```" -#: src/android/logging.md:50 -msgid "The logs show up in `adb logcat`:" +#: src/chromium/adding-third-party-crates.md:10 +msgid "Transitive dependencies" msgstr "" -#: src/android/interoperability.md:3 -msgid "" -"Rust has excellent support for interoperability with other languages. This " -"means that you can:" +#: src/chromium/adding-third-party-crates.md:10 +msgid "Few" msgstr "" -#: src/android/interoperability.md:6 -msgid "Call Rust functions from other languages." +#: src/chromium/adding-third-party-crates.md:12 +msgid "For a Chromium engineer, this has pros and cons:" msgstr "" -#: src/android/interoperability.md:7 -msgid "Call functions written in other languages from Rust." +#: src/chromium/adding-third-party-crates.md:14 +msgid "" +"All crates use a common build system so we can automate their inclusion into " +"Chromium..." msgstr "" -#: src/android/interoperability.md:9 +#: src/chromium/adding-third-party-crates.md:16 msgid "" -"When you call functions in a foreign language we say that you're using a " -"_foreign function interface_, also known as FFI." +"... but, crates typically have transitive dependencies, so you will likely " +"have to bring in multiple libraries." msgstr "" -#: src/android/interoperability/with-c.md:1 -msgid "Interoperability with C" +#: src/chromium/adding-third-party-crates.md:19 +msgid "We'll discuss:" msgstr "" -#: src/android/interoperability/with-c.md:3 -msgid "" -"Rust has full support for linking object files with a C calling convention. " -"Similarly, you can export Rust functions and call them from C." +#: src/chromium/adding-third-party-crates.md:21 +msgid "How to put a crate in the Chromium source code tree" msgstr "" -#: src/android/interoperability/with-c.md:6 -msgid "You can do it by hand if you want:" +#: src/chromium/adding-third-party-crates.md:22 +msgid "How to make `gn` build rules for it" msgstr "" -#: src/android/interoperability/with-c.md:16 -msgid "\"{x}, {abs_x}\"" -msgstr "\"{x}, {abs_x}\"" +#: src/chromium/adding-third-party-crates.md:23 +msgid "How to audit its source code for sufficient safety." +msgstr "" -#: src/android/interoperability/with-c.md:20 -msgid "" -"We already saw this in the [Safe FFI Wrapper exercise](../../exercises/day-3/" -"safe-ffi-wrapper.md)." +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:1 +msgid "Configuring the `Cargo.toml` file to add crates" msgstr "" -#: src/android/interoperability/with-c.md:23 +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:3 msgid "" -"This assumes full knowledge of the target platform. Not recommended for " -"production." +"Chromium has a single set of centrally-managed direct crate dependencies. " +"These are managed through a single [`Cargo.toml`](https://source.chromium." +"org/chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/Cargo." +"toml):" msgstr "" -#: src/android/interoperability/with-c.md:26 -msgid "We will look at better options next." +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:6 +msgid "" +"```toml\n" +"[dependencies]\n" +"bitflags = \"1\"\n" +"cfg-if = \"1\"\n" +"cxx = \"1\"\n" +"# lots more...\n" +"```" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:1 -msgid "Using Bindgen" +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:14 +msgid "" +"As with any other `Cargo.toml`, you can specify [more details about the " +"dependencies](https://doc.rust-lang.org/cargo/reference/specifying-" +"dependencies.html) --- most commonly, you'll want to specify the `features` " +"that you wish to enable in the crate." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:3 +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md:18 msgid "" -"The [bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) " -"tool can auto-generate bindings from a C header file." +"When adding a crate to Chromium, you'll often need to provide some extra " +"information in an additional file, `gnrt_config.toml`, which we'll meet next." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:6 -msgid "First create a small C library:" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:1 +msgid "Configuring `gnrt_config.toml`" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:8 -msgid "_interoperability/bindgen/libbirthday.h_:" -msgstr "_interoperability/bindgen/libbirthday.h_:" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:3 +msgid "" +"Alongside `Cargo.toml` is [`gnrt_config.toml`](https://source.chromium.org/" +"chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/gnrt_config." +"toml). This contains Chromium-specific extensions to crate handling." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:19 -msgid "_interoperability/bindgen/libbirthday.c_:" -msgstr "_interoperability/bindgen/libbirthday.c_:" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:6 +msgid "" +"If you add a new crate, you should specify at least the `group`. This is one " +"of:" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:22 -msgid "" -msgstr "" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:16 +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:15 +msgid "For instance," +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:23 -#: src/android/interoperability/with-c/bindgen.md:50 -msgid "\"libbirthday.h\"" -msgstr "\"libbirthday.h\"" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:23 +msgid "" +"Depending on the crate source code layout, you may also need to use this " +"file to specify where its `LICENSE` file(s) can be found." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:26 -#: src/android/interoperability/with-c/bindgen.md:29 -msgid "\"+--------------\\n\"" -msgstr "\"+--------------\\n\"" +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md:26 +msgid "" +"Later, we'll see some other things you will need to configure in this file " +"to resolve problems." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:27 -msgid "\"| Happy Birthday %s!\\n\"" +#: src/chromium/adding-third-party-crates/downloading-crates.md:3 +msgid "" +"A tool called `gnrt` knows how to download crates and how to generate `BUILD." +"gn` rules." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:28 -msgid "\"| Congratulations with the %i years!\\n\"" +#: src/chromium/adding-third-party-crates/downloading-crates.md:6 +msgid "To start, download the crate you want like this:" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:33 -msgid "Add this to your `Android.bp` file:" +#: src/chromium/adding-third-party-crates/downloading-crates.md:13 +msgid "" +"Although the `gnrt` tool is part of the Chromium source code, by running " +"this command you will be downloading and running its dependencies from " +"`crates.io`. See [the earlier section](../cargo.md) discussing this security " +"decision." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:35 -#: src/android/interoperability/with-c/bindgen.md:55 -#: src/android/interoperability/with-c/bindgen.md:69 -#: src/android/interoperability/with-c/bindgen.md:108 -msgid "_interoperability/bindgen/Android.bp_:" -msgstr "_interoperability/bindgen/Android.bp_:" +#: src/chromium/adding-third-party-crates/downloading-crates.md:18 +msgid "This `vendor` command may download:" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:39 -#: src/android/interoperability/with-c/bindgen.md:63 -msgid "\"libbirthday\"" -msgstr "\"libbirthday\"" +#: src/chromium/adding-third-party-crates/downloading-crates.md:19 +#, fuzzy +msgid "Your crate" +msgstr "\"Sokrates\"" -#: src/android/interoperability/with-c/bindgen.md:40 -msgid "\"libbirthday.c\"" -msgstr "\"libbirthday.c\"" +#: src/chromium/adding-third-party-crates/downloading-crates.md:20 +msgid "Direct and transitive dependencies" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:44 +#: src/chromium/adding-third-party-crates/downloading-crates.md:21 msgid "" -"Create a wrapper header file for the library (not strictly needed in this " -"example):" +"New versions of other crates, as required by `cargo` to resolve the complete " +"set of crates required by Chromium." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:47 -msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" -msgstr "_interoperability/bindgen/libbirthday_wrapper.h_:" - -#: src/android/interoperability/with-c/bindgen.md:53 -msgid "You can now auto-generate the bindings:" +#: src/chromium/adding-third-party-crates/downloading-crates.md:24 +msgid "" +"Chromium maintains patches for some crates, kept in `//third_party/rust/" +"chromium_crates_io/patches`. These will be reapplied automatically, but if " +"patching fails you may need to take manual action." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:59 -#: src/android/interoperability/with-c/bindgen.md:75 -msgid "\"libbirthday_bindgen\"" -msgstr "\"libbirthday_bindgen\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:1 +msgid "Generating `gn` build rules" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:60 -msgid "\"birthday_bindgen\"" -msgstr "\"birthday_bindgen\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:3 +msgid "" +"Once you've downloaded the crate, generate the `BUILD.gn` files like this:" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:61 -msgid "\"libbirthday_wrapper.h\"" -msgstr "\"libbirthday_wrapper.h\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:9 +msgid "Now run `git status`. You should find:" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:62 -msgid "\"bindings\"" -msgstr "\"bindings\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:11 +msgid "" +"At least one new crate source code in `third_party/rust/chromium_crates_io/" +"vendor`" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:67 -msgid "Finally, we can use the bindings in our Rust program:" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:12 +msgid "" +"At least one new `BUILD.gn` in `third_party/rust//v`" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:73 -msgid "\"print_birthday_card\"" -msgstr "\"print_birthday_card\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:13 +msgid "An appropriate `README.chromium`" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:74 -msgid "\"main.rs\"" -msgstr "\"main.rs\"" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:15 +msgid "" +"The \"major semver version\" is a [Rust \"semver\" version number](https://" +"doc.rust-lang.org/cargo/reference/semver.html)." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:79 -msgid "_interoperability/bindgen/main.rs_:" -msgstr "_interoperability/bindgen/main.rs_:" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:17 +msgid "" +"Take a close look, especially at the things generated in `third_party/rust`." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:82 -msgid "//! Bindgen demo.\n" -msgstr "//! Bindgen-demo.\n" +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md:21 +msgid "" +"Talk a little about semver --- and specifically the way that in Chromium " +"it's to allow multiple incompatible versions of a crate, which is " +"discouraged but sometimes necessary in the cargo ecosystem." +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:100 +#: src/chromium/adding-third-party-crates/resolving-problems.md:3 msgid "" -"```shell\n" -"m print_birthday_card\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/print_birthday_card\n" -"```" +"If your build fails, it may be because of a `build.rs`: programs which do " +"arbitrary things at build time. This is fundamentally at odds with the " +"design of `gn` and `ninja` which aim for static, deterministic, build rules " +"to maximize parallelism and repeatability of builds." msgstr "" -"```shell\n" -"m print_birthday_card\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/print_birthday_card\n" -"```" -#: src/android/interoperability/with-c/bindgen.md:106 -msgid "Finally, we can run auto-generated tests to ensure the bindings work:" +#: src/chromium/adding-third-party-crates/resolving-problems.md:8 +msgid "" +"Some `build.rs` actions are automatically supported; others require action:" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:112 -#: src/android/interoperability/with-c/bindgen.md:114 -msgid "\"libbirthday_bindgen_test\"" -msgstr "\"libbirthday_bindgen_test\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "build script effect" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:113 -msgid "\":libbirthday_bindgen\"" -msgstr "\":libbirthday_bindgen\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "Supported by our gn templates" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:115 -msgid "\"general-tests\"" -msgstr "\"general-tests\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:10 +msgid "Work required by you" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:117 -#: src/android/interoperability/with-c/bindgen.md:118 -msgid "\"none\"" -msgstr "\"none\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +msgid "Checking rustc version to configure features on and off" +msgstr "" -#: src/android/interoperability/with-c/bindgen.md:117 -msgid "// Generated file, skip linting\n" +#: src/chromium/adding-third-party-crates/resolving-problems.md:12 +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +msgid "None" msgstr "" -#: src/android/interoperability/with-c/rust.md:1 -msgid "Calling Rust" +#: src/chromium/adding-third-party-crates/resolving-problems.md:13 +msgid "Checking platform or CPU to configure features on and off" msgstr "" -#: src/android/interoperability/with-c/rust.md:3 -msgid "Exporting Rust functions and types to C is easy:" +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +msgid "Generating code" msgstr "" -#: src/android/interoperability/with-c/rust.md:5 -msgid "_interoperability/rust/libanalyze/analyze.rs_" -msgstr "_interoperability/rust/libanalyze/analyze.rs_" +#: src/chromium/adding-third-party-crates/resolving-problems.md:14 +msgid "Yes - specify in `gnrt_config.toml`" +msgstr "" -#: src/android/interoperability/with-c/rust.md:8 -msgid "//! Rust FFI demo.\n" -msgstr "//! Rust FFI-demo.\n" +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +msgid "Building C/C++" +msgstr "" -#: src/android/interoperability/with-c/rust.md:12 -msgid "/// Analyze the numbers.\n" -msgstr "/// Analyze the numbers.\n" +#: src/chromium/adding-third-party-crates/resolving-problems.md:15 +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "Patch around it" +msgstr "" -#: src/android/interoperability/with-c/rust.md:17 -msgid "\"x ({x}) is smallest!\"" -msgstr "\"x ({x}) er mindst!\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:16 +msgid "Arbitrary other actions" +msgstr "" -#: src/android/interoperability/with-c/rust.md:19 -msgid "\"y ({y}) is probably larger than x ({x})\"" -msgstr "\"y ({y}) er muligvis større end x ({x})\"" +#: src/chromium/adding-third-party-crates/resolving-problems.md:18 +msgid "" +"Fortunately, most crates don't contain a build script, and fortunately, most " +"build scripts only do the top two actions." +msgstr "" -#: src/android/interoperability/with-c/rust.md:24 -msgid "_interoperability/rust/libanalyze/analyze.h_" -msgstr "_interoperability/rust/libanalyze/analyze.h_" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:3 +msgid "" +"If `ninja` complains about missing files, check the `build.rs` to see if it " +"writes source code files." +msgstr "" -#: src/android/interoperability/with-c/rust.md:37 -msgid "_interoperability/rust/libanalyze/Android.bp_" -msgstr "_interoperability/rust/libanalyze/Android.bp_" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:6 +msgid "" +"If so, modify [`gnrt_config.toml`](../configuring-gnrt-config-toml.md) to " +"add `build-script-outputs` to the crate. If this is a transitive dependency, " +"that is, one on which Chromium code should not directly depend, also add " +"`allow-first-party-usage=false`. There are several examples already in that " +"file:" +msgstr "" -#: src/android/interoperability/with-c/rust.md:41 -#: src/android/interoperability/with-c/rust.md:68 -msgid "\"libanalyze_ffi\"" -msgstr "\"libanalyze_ffi\"" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:11 +msgid "" +"```toml\n" +"[crate.unicode-linebreak]\n" +"allow-first-party-usage = false\n" +"build-script-outputs = [ \"tables.rs\" ]\n" +"```" +msgstr "" -#: src/android/interoperability/with-c/rust.md:42 -msgid "\"analyze_ffi\"" -msgstr "\"analyze_ffi\"" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md:17 +msgid "" +"Now rerun [`gnrt.py -- gen`](../generating-gn-build-rules.md) to regenerate " +"`BUILD.gn` files to inform ninja that this particular output file is input " +"to subsequent build steps." +msgstr "" -#: src/android/interoperability/with-c/rust.md:43 -msgid "\"analyze.rs\"" -msgstr "\"analyze.rs\"" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:3 +msgid "" +"Some crates use the [`cc`](https://crates.io/crates/cc) crate to build and " +"link C/C++ libraries. Other crates parse C/C++ using [`bindgen`](https://" +"crates.io/crates/bindgen) within their build scripts. These actions can't be " +"supported in a Chromium context --- our gn, ninja and LLVM build system is " +"very specific in expressing relationships between build actions." +msgstr "" -#: src/android/interoperability/with-c/rust.md:48 -msgid "We can now call this from a C binary:" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:9 +msgid "So, your options are:" msgstr "" -#: src/android/interoperability/with-c/rust.md:50 -msgid "_interoperability/rust/analyze/main.c_" -msgstr "_interoperability/rust/analyze/main.c_" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:11 +msgid "Avoid these crates" +msgstr "" -#: src/android/interoperability/with-c/rust.md:53 -msgid "\"analyze.h\"" -msgstr "\"analyze.h\"" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:12 +msgid "Apply a patch to the crate." +msgstr "" -#: src/android/interoperability/with-c/rust.md:62 -msgid "_interoperability/rust/analyze/Android.bp_" -msgstr "_interoperability/rust/analyze/Android.bp_" +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md:14 +msgid "" +"Patches should be kept in `third_party/rust/chromium_crates_io/patches/" +"` - see for example the [patches against the cxx crate](https://" +"source.chromium.org/chromium/chromium/src/+/main:third_party/rust/" +"chromium_crates_io/patches/cxx/) - and will be applied automatically by " +"`gnrt` each time it upgrades the crate." +msgstr "" -#: src/android/interoperability/with-c/rust.md:66 -msgid "\"analyze_numbers\"" -msgstr "\"analyze_numbers\"" +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:3 +msgid "" +"Once you've added a third-party crate and generated build rules, depending " +"on a crate is simple. Find your `rust_static_library` target, and add a " +"`dep` on the `:lib` target within your crate." +msgstr "" -#: src/android/interoperability/with-c/rust.md:67 -msgid "\"main.c\"" -msgstr "\"main.c\"" +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:7 +msgid "Specifically," +msgstr "" -#: src/android/interoperability/with-c/rust.md:75 +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:9 msgid "" -"```shell\n" -"m analyze_numbers\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/analyze_numbers\n" +"```bob\n" +" +------------+ +----------------------+\n" +"\"//third_party/rust\" | crate name | \"/v\" | major semver version | \"/:" +"lib\"\n" +" +------------+ +----------------------+\n" "```" msgstr "" -"```shell\n" -"m analyze_numbers\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers /data/local/" -"tmp\"\n" -"adb shell /data/local/tmp/analyze_numbers\n" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md:17 +msgid "" +"```gn\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +" deps = [ \"//third_party/rust/example_rust_crate/v1:lib\" ]\n" +"}\n" "```" +msgstr "" -#: src/android/interoperability/with-c/rust.md:83 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:1 +msgid "Auditing third party crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:3 msgid "" -"`#[no_mangle]` disables Rust's usual name mangling, so the exported symbol " -"will just be the name of the function. You can also use `#[export_name = " -"\"some_name\"]` to specify whatever name you want." +"Adding new libraries is subject to Chromium's standard [policies](https://" +"chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/rust." +"md#Third_party-review), but of course also subject to code review. As you " +"may be bringing in not just a single crate but also transitive dependencies, " +"there may be a lot of code to review. On the other hand, safe Rust code can " +"have limited negative side effects. How should you review it?" msgstr "" -#: src/android/interoperability/cpp.md:3 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:9 msgid "" -"The [CXX crate](https://cxx.rs/) makes it possible to do safe " -"interoperability between Rust and C++." +"Over time Chromium aims to move to a process based around [cargo vet]" +"(https://mozilla.github.io/cargo-vet/)." msgstr "" -#: src/android/interoperability/cpp.md:6 -msgid "The overall approach looks like this:" +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:11 +msgid "" +"Meanwhile, for each new crate addition, we are checking for the following:" msgstr "" -#: src/android/interoperability/cpp.md:10 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:13 msgid "" -"See the [CXX tutorial](https://cxx.rs/tutorial.html) for an full example of " -"using this." +"Understand why each crate is used. What's the relationship between crates? " +"If the build system for each crate contains a `build.rs` or procedural " +"macros, work out what they're for. Are they compatible with the way Chromium " +"is normally built?" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:17 +msgid "Check each crate seems to be reasonably well maintained" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:18 +msgid "" +"Use `cd third-party/rust/chromium_crates_io; cargo audit` to check for known " +"vulnerabilities (first you'll need to `cargo install cargo-audit`, which " +"ironically involves downloading lots of dependencies from the internet[2](../" +"cargo.md))" msgstr "" -#: src/android/interoperability/cpp.md:14 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:21 msgid "" -"At this point, the instructor should switch to the [CXX tutorial](https://" -"cxx.rs/tutorial.html)." +"Ensure any unsafe code is good enough for the [Rule of Two](https://chromium." +"googlesource.com/chromium/src/+/main/docs/security/rule-of-2.md#unsafe-code-" +"in-safe-languages)" msgstr "" -#: src/android/interoperability/cpp.md:16 -msgid "Walk the students through the tutorial step by step." +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:22 +msgid "Check for any use of `fs` or `net` APIs" msgstr "" -#: src/android/interoperability/cpp.md:18 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:23 msgid "" -"Highlight how CXX presents a clean interface without unsafe code in _both " -"languages_." +"Read all the code at a sufficient level to look for anything out of place " +"that might have been maliciously inserted. (You can't realistically aim for " +"100% perfection here: there's often just too much code.)" msgstr "" -#: src/android/interoperability/cpp.md:20 +#: src/chromium/adding-third-party-crates/reviews-and-audits.md:27 msgid "" -"Show the correspondence between [Rust and C++ types](https://cxx.rs/bindings." -"html):" +"These are just guidelines --- work with reviewers from `security@chromium." +"org` to work out the right way to become confident of the crate." msgstr "" -#: src/android/interoperability/cpp.md:22 +#: src/chromium/adding-third-party-crates/checking-in.md:1 +msgid "Checking crates into Chromium source code" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:3 +msgid "`git status` should reveal:" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:4 +msgid "Crate code in `//third_party/rust/chromium_crates_io`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:5 msgid "" -"Explain how a Rust `String` cannot map to a C++ `std::string` (the latter " -"does not uphold the UTF-8 invariant). Show that despite being different " -"types, `rust::String` in C++ can be easily constructed from a C++ `std::" -"string`, making it very ergonomic to use." +"Metadata (`BUILD.gn` and `README.chromium`) in `//third_party/rust//" +"`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md:7 +msgid "Please also add an `OWNERS` file in the latter location." msgstr "" -#: src/android/interoperability/cpp.md:28 +#: src/chromium/adding-third-party-crates/checking-in.md:9 msgid "" -"Explain that a Rust function returning `Result` becomes a function " -"which throws a `E` exception in C++ (and vice versa)." +"You should land all this, along with your `Cargo.toml` and `gnrt_config." +"toml` changes, into the Chromium repo." msgstr "" -#: src/android/interoperability/java.md:1 -msgid "Interoperability with Java" +#: src/chromium/adding-third-party-crates/checking-in.md:12 +msgid "" +"**Important**: you need to use `git add -f` because otherwise `.gitignore` " +"files may result in some files being skipped." msgstr "" -#: src/android/interoperability/java.md:3 +#: src/chromium/adding-third-party-crates/checking-in.md:15 msgid "" -"Java can load shared objects via [Java Native Interface (JNI)](https://en." -"wikipedia.org/wiki/Java_Native_Interface). The [`jni` crate](https://docs.rs/" -"jni/) allows you to create a compatible library." +"As you do so, you might find presubmit checks fail because of non-inclusive " +"language. This is because Rust crate data tends to include names of git " +"branches, and many projects still use non-inclusive terminology there. So " +"you may need to run:" msgstr "" -#: src/android/interoperability/java.md:7 -msgid "First, we create a Rust function to export to Java:" +#: src/chromium/adding-third-party-crates/keeping-up-to-date.md:3 +msgid "" +"As the OWNER of any third party Chromium dependency, you are [expected to " +"keep it up to date with any security fixes](https://chromium.googlesource." +"com/chromium/src/+/main/docs/adding_to_third_party.md#add-owners). It is " +"hoped that we will soon automate this for Rust crates, but for now, it's " +"still your responsibility just as it is for any other third party dependency." msgstr "" -#: src/android/interoperability/java.md:9 -msgid "_interoperability/java/src/lib.rs_:" +#: src/exercises/chromium/third-party.md:3 +msgid "" +"Add [uwuify](https://crates.io/crates/uwuify) to Chromium, turning off the " +"crate's [default features](https://doc.rust-lang.org/cargo/reference/" +"features.html#the-default-feature). Assume that the crate will be used in " +"shipping Chromium, but won't be used to handle untrustworthy input." msgstr "" -#: src/android/interoperability/java.md:12 -msgid "//! Rust <-> Java FFI demo.\n" +#: src/exercises/chromium/third-party.md:7 +msgid "" +"(In the next exercise we'll use uwuify from Chromium, but feel free to skip " +"ahead and do that now if you like. Or, you could create a new " +"[`rust_executable` target](https://source.chromium.org/chromium/chromium/src/" +"+/main:build/rust/rust_executable.gni) which uses `uwuify`)." msgstr "" -#: src/android/interoperability/java.md:17 -msgid "/// HelloWorld::hello method implementation.\n" +#: src/exercises/chromium/third-party.md:14 +msgid "" +"The total crates needed are: uwuify, smallvec, scopeguard, parking_lot, " +"parking_lot_core, lock_api and instant. If students are downloading even " +"more than that, they probably forgot to turn off the default features." msgstr "" -#: src/android/interoperability/java.md:20 -msgid "\"system\"" -msgstr "\"system\"" +#: src/exercises/chromium/third-party.md:18 +msgid "" +"Thanks to [Daniel Liu](https://github.com/Daniel-Liu-c0deb0t) for this " +"crate! " +msgstr "" -#: src/android/interoperability/java.md:26 -msgid "\"Hello, {input}!\"" +#: src/exercises/chromium/bringing-it-together.md:1 +msgid "Bringing it together --- Exercise" msgstr "" -#: src/android/interoperability/java.md:32 -#: src/android/interoperability/java.md:62 -msgid "_interoperability/java/Android.bp_:" -msgstr "_interoperability/java/Android.bp_:" +#: src/exercises/chromium/bringing-it-together.md:3 +msgid "" +"In this exercise, you're going to add a whole new Chromium feature, bringing " +"together everything you already learned." +msgstr "" -#: src/android/interoperability/java.md:36 -#: src/android/interoperability/java.md:69 -msgid "\"libhello_jni\"" -msgstr "\"libhello_jni\"" +#: src/exercises/chromium/bringing-it-together.md:6 +msgid "The brief from Product Management" +msgstr "" -#: src/android/interoperability/java.md:37 -#: src/android/interoperability/java.md:52 -msgid "\"hello_jni\"" -msgstr "\"hello_jni\"" +#: src/exercises/chromium/bringing-it-together.md:8 +msgid "" +"A community of pixies has been discovered living in a remote rainforest. " +"It's important that we get Chromium for Pixies delivered to them as soon as " +"possible." +msgstr "" -#: src/android/interoperability/java.md:39 -msgid "\"libjni\"" -msgstr "\"libjni\"" +#: src/exercises/chromium/bringing-it-together.md:12 +msgid "" +"The requirement is to translate all Chromium's UI strings into Pixie " +"language." +msgstr "" -#: src/android/interoperability/java.md:43 -msgid "Finally, we can call this function from Java:" +#: src/exercises/chromium/bringing-it-together.md:14 +msgid "" +"There's not time to wait for proper translations, but fortunately pixie " +"language is very close to English, and it turns out there's a Rust crate " +"which does the translation." msgstr "" -#: src/android/interoperability/java.md:45 -msgid "_interoperability/java/HelloWorld.java_:" +#: src/exercises/chromium/bringing-it-together.md:18 +msgid "" +"In fact, you already [imported that crate in the previous exercise](https://" +"crates.io/crates/uwuify)." msgstr "" -#: src/android/interoperability/java.md:66 -msgid "\"helloworld_jni\"" -msgstr "\"helloworld_jni\"" +#: src/exercises/chromium/bringing-it-together.md:20 +msgid "" +"(Obviously, real translations of Chrome require incredible care and " +"diligence. Don't ship this!)" +msgstr "" -#: src/android/interoperability/java.md:67 -msgid "\"HelloWorld.java\"" -msgstr "\"HelloWorld.java\"" +#: src/exercises/chromium/bringing-it-together.md:23 +msgid "Steps" +msgstr "" -#: src/android/interoperability/java.md:68 -msgid "\"HelloWorld\"" -msgstr "\"HelloWorld\"" +#: src/exercises/chromium/bringing-it-together.md:25 +msgid "" +"Modify `ResourceBundle::MaybeMangleLocalizedString` so that it uwuifies all " +"strings before display. In this special build of Chromium, it should always " +"do this irrespective of the setting of `mangle_localized_strings_`." +msgstr "" -#: src/android/interoperability/java.md:73 -msgid "Finally, you can build, sync, and run the binary:" +#: src/exercises/chromium/bringing-it-together.md:29 +msgid "" +"If you've done everything right across all these exercises, congratulations, " +"you should have created Chrome for pixies!" msgstr "" -#: src/exercises/android/morning.md:3 +#: src/exercises/chromium/bringing-it-together.md:37 msgid "" -"This is a group exercise: We will look at one of the projects you work with " -"and try to integrate some Rust into it. Some suggestions:" +"UTF16 vs UTF8. Students should be aware that Rust strings are always UTF8, " +"and will probably decide that it's better to do the conversion on the C++ " +"side using `base::UTF16ToUTF8` and back again." msgstr "" -#: src/exercises/android/morning.md:6 -msgid "Call your AIDL service with a client written in Rust." +#: src/exercises/chromium/bringing-it-together.md:40 +msgid "" +"If students decide to do the conversion on the Rust side, they'll need to " +"consider [`std::string::from_utf16`](https://doc.rust-lang.org/std/string/" +"struct.String.html#method.from_utf16), consider error handling, and consider " +"which [cxx supported types can transfer a lot of u16s](https://cxx.rs/" +"binding/slice.html)." msgstr "" -#: src/exercises/android/morning.md:8 -msgid "Move a function from your project to Rust and call it." +#: src/exercises/chromium/bringing-it-together.md:43 +msgid "" +"Students may design the C++/Rust boundary in several different ways, e.g. " +"taking and returning strings by value, or taking a mutable reference to a " +"string. If a mutable reference is used, cxx will likely tell the student " +"that they need to use [`Pin`](https://doc.rust-lang.org/std/pin/). You may " +"need to explain what `Pin` does, and then explain why `cxx` needs it for " +"mutable references to C++ data: the answer is that C++ data can't be moved " +"around like Rust data, because it may contain self-referential pointers." msgstr "" -#: src/exercises/android/morning.md:12 +#: src/exercises/chromium/bringing-it-together.md:50 msgid "" -"No solution is provided here since this is open-ended: it relies on someone " -"in the class having a piece of code which you can turn in to Rust on the fly." +"The C++ target containing `ResourceBundle::MaybeMangleLocalizedString` will " +"need to depend on a `rust_static_library` target. The student probably " +"already did this." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md:53 +msgid "" +"The `rust_static_library` target will need to depend on `//third_party/rust/" +"uwuify/v0_2:lib`." msgstr "" #: src/bare-metal.md:1 @@ -10146,15 +13916,7 @@ msgid "" "And give users in the `plugdev` group access to the micro:bit programmer:" msgstr "" -#: src/bare-metal.md:33 -msgid "" -"'SUBSYSTEM==\"usb\", ATTR{idVendor}==\"0d28\", MODE=\"0664\", " -"GROUP=\"plugdev\"'" -msgstr "" -"'SUBSYSTEM==\"usb\", ATTR{idVendor}==\"0d28\", MODE=\"0664\", " -"GROUP=\"plugdev\"'" - -#: src/bare-metal.md:38 +#: src/bare-metal.md:38 src/bare-metal/microcontrollers/debugging.md:27 msgid "On MacOS:" msgstr "På MacOS:" @@ -10190,6 +13952,10 @@ msgstr "`Option`, `Result`" msgid "`Display`, `Debug`, `write!`..." msgstr "`Display`, `Debug`, `write!`..." +#: src/bare-metal/no_std.md:28 +msgid "`Iterator`" +msgstr "`Iterator`" + #: src/bare-metal/no_std.md:29 msgid "`panic!`, `assert_eq!`..." msgstr "`panic!`, `assert_eq!`..." @@ -10623,41 +14389,23 @@ msgid "" msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:6 -msgid "SWD" -msgstr "SWD" - -#: src/bare-metal/microcontrollers/probe-rs.md:6 -msgid "and JTAG via CMSIS-DAP, ST-Link and J-Link probes" +msgid "" +"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:7 -msgid "GDB stub and Microsoft " +msgid "GDB stub and Microsoft DAP (Debug Adapter Protocol) server" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:7 -msgid "DAP" -msgstr "DAP" - -#: src/bare-metal/microcontrollers/probe-rs.md:7 -msgid "server" -msgstr "server" - #: src/bare-metal/microcontrollers/probe-rs.md:8 msgid "Cargo integration" msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:10 -msgid "`cargo-embed` is a cargo subcommand to build and flash binaries, log " -msgstr "" - -#: src/bare-metal/microcontrollers/probe-rs.md:11 -msgid "RTT" -msgstr "RTT" - -#: src/bare-metal/microcontrollers/probe-rs.md:11 msgid "" -"output and connect GDB. It's configured by an `Embed.toml` file in your " -"project directory." +"`cargo-embed` is a cargo subcommand to build and flash binaries, log RTT " +"(Real Time Transfers) output and connect GDB. It's configured by an `Embed." +"toml` file in your project directory." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:16 @@ -10704,27 +14452,10 @@ msgid "" msgstr "" #: src/bare-metal/microcontrollers/debugging.md:3 -msgid "Embed.toml:" +#, fuzzy +msgid "_Embed.toml_:" msgstr "Embed.toml:" -#: src/bare-metal/microcontrollers/debugging.md:5 -msgid "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"```" -msgstr "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"```" - #: src/bare-metal/microcontrollers/debugging.md:13 msgid "In one terminal under `src/bare-metal/microcontrollers/examples/`:" msgstr "" @@ -10733,11 +14464,11 @@ msgstr "" msgid "In another terminal in the same directory:" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:22 -msgid "\"target remote :1337\"" -msgstr "\"target remote :1337\"" +#: src/bare-metal/microcontrollers/debugging.md:21 +msgid "On gLinux or Debian:" +msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:27 +#: src/bare-metal/microcontrollers/debugging.md:34 msgid "In GDB, try running:" msgstr "" @@ -10832,6 +14563,13 @@ msgid "" "serial port." msgstr "" +#: src/exercises/bare-metal/morning.md:7 +#: src/exercises/concurrency/morning.md:12 +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"morning.md) provided." +msgstr "" + #: src/exercises/bare-metal/compass.md:3 msgid "" "We will read the direction from an I2C compass, and log the readings to a " @@ -10917,92 +14655,14 @@ msgstr "" msgid "_Cargo.toml_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/compass.md:68 -msgid "" -"```toml\n" -"[workspace]\n" -"\n" -"[package]\n" -"name = \"compass\"\n" -"version = \"0.1.0\"\n" -"edition = \"2021\"\n" -"publish = false\n" -"\n" -"[dependencies]\n" -"cortex-m-rt = \"0.7.3\"\n" -"embedded-hal = \"0.2.6\"\n" -"lsm303agr = \"0.2.2\"\n" -"microbit-v2 = \"0.13.0\"\n" -"panic-halt = \"0.2.0\"\n" -"```" -msgstr "" -"```toml\n" -"[workspace]\n" -"\n" -"[package]\n" -"name = \"compass\"\n" -"version = \"0.1.0\"\n" -"edition = \"2021\"\n" -"publish = false\n" -"\n" -"[dependencies]\n" -"cortex-m-rt = \"0.7.3\"\n" -"embedded-hal = \"0.2.6\"\n" -"lsm303agr = \"0.2.2\"\n" -"microbit-v2 = \"0.13.0\"\n" -"panic-halt = \"0.2.0\"\n" -"```" - #: src/exercises/bare-metal/compass.md:85 msgid "_Embed.toml_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/compass.md:89 -msgid "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"\n" -"[debug.reset]\n" -"halt_afterwards = true\n" -"```" -msgstr "" -"```toml\n" -"[default.general]\n" -"chip = \"nrf52833_xxAA\"\n" -"\n" -"[debug.gdb]\n" -"enabled = true\n" -"\n" -"[debug.reset]\n" -"halt_afterwards = true\n" -"```" - #: src/exercises/bare-metal/compass.md:100 src/exercises/bare-metal/rtc.md:985 msgid "_.cargo/config.toml_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/compass.md:104 -msgid "" -"```toml\n" -"[build]\n" -"target = \"thumbv7em-none-eabihf\" # Cortex-M4F\n" -"\n" -"[target.'cfg(all(target_arch = \"arm\", target_os = \"none\"))']\n" -"rustflags = [\"-C\", \"link-arg=-Tlink.x\"]\n" -"```" -msgstr "" -"```toml\n" -"[build]\n" -"target = \"thumbv7em-none-eabihf\" # Cortex-M4F\n" -"\n" -"[target.'cfg(all(target_arch = \"arm\", target_os = \"none\"))']\n" -"rustflags = [\"-C\", \"link-arg=-Tlink.x\"]\n" -"```" - #: src/exercises/bare-metal/compass.md:112 msgid "See the serial output on Linux with:" msgstr "" @@ -11016,6 +14676,40 @@ msgstr "" msgid "Use Ctrl+A Ctrl+Q to quit picocom." msgstr "" +#: src/exercises/bare-metal/solutions-morning.md:1 +msgid "Bare Metal Rust Morning Exercise" +msgstr "Bar metal formiddagsøvelser" + +#: src/exercises/bare-metal/solutions-morning.md:5 +msgid "([back to exercise](compass.md))" +msgstr "([tilbage til øvelsen](compass.md))" + +#: src/exercises/bare-metal/solutions-morning.md:40 +msgid "// Set up the I2C controller and Inertial Measurement Unit.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:41 +msgid "\"Setting up IMU...\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:49 +msgid "// Set up display and timer.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:59 +msgid "// Read compass data and log it to the serial port.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md:67 +msgid "\"{},{},{}\\t{},{},{}\"" +msgstr "\"{},{},{}\\t{},{},{}\"" + +#: src/exercises/bare-metal/solutions-morning.md:103 +msgid "" +"// If button A is pressed, switch to the next mode and briefly blink all " +"LEDs on.\n" +msgstr "" + #: src/bare-metal/aps.md:1 msgid "Application processors" msgstr "" @@ -11197,15 +14891,8 @@ msgstr "" #: src/bare-metal/aps/inline-assembly.md:3 msgid "" "Sometimes we need to use assembly to do things that aren't possible with " -"Rust code. For example, to make an " -msgstr "" - -#: src/bare-metal/aps/inline-assembly.md:4 -msgid "HVC" -msgstr "" - -#: src/bare-metal/aps/inline-assembly.md:4 -msgid "to tell the firmware to power off the system:" +"Rust code. For example, to make an HVC (hypervisor call) to tell the " +"firmware to power off the system:" msgstr "" #: src/bare-metal/aps/inline-assembly.md:19 @@ -11491,10 +15178,6 @@ msgstr "" msgid "RSR" msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "4" -msgstr "" - #: src/bare-metal/aps/better-uart.md:11 msgid "0x18" msgstr "" @@ -11515,10 +15198,6 @@ msgstr "" msgid "ILPR" msgstr "" -#: src/bare-metal/aps/better-uart.md:12 src/bare-metal/aps/better-uart.md:15 -msgid "8" -msgstr "" - #: src/bare-metal/aps/better-uart.md:13 msgid "0x24" msgstr "" @@ -11539,10 +15218,6 @@ msgstr "" msgid "FBRD" msgstr "" -#: src/bare-metal/aps/better-uart.md:14 src/bare-metal/aps/better-uart.md:17 -msgid "6" -msgstr "" - #: src/bare-metal/aps/better-uart.md:15 msgid "0x2c" msgstr "" @@ -11612,10 +15287,6 @@ msgstr "" msgid "DMACR" msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "3" -msgstr "" - #: src/bare-metal/aps/better-uart.md:26 msgid "There are also some ID registers which have been omitted for brevity." msgstr "" @@ -11846,38 +15517,6 @@ msgid "" "calling into Rust code:" msgstr "" -#: src/bare-metal/aps/exceptions.md:15 src/exercises/bare-metal/rtc.md:101 -msgid "\"sync_exception_current\"" -msgstr "\"sync_exception_current\"" - -#: src/bare-metal/aps/exceptions.md:21 src/exercises/bare-metal/rtc.md:107 -msgid "\"irq_current\"" -msgstr "\"irq_current\"" - -#: src/bare-metal/aps/exceptions.md:27 src/exercises/bare-metal/rtc.md:114 -msgid "\"fiq_current\"" -msgstr "\"fiq_current\"" - -#: src/bare-metal/aps/exceptions.md:33 src/exercises/bare-metal/rtc.md:120 -msgid "\"serr_current\"" -msgstr "\"serr_current\"" - -#: src/bare-metal/aps/exceptions.md:39 src/exercises/bare-metal/rtc.md:126 -msgid "\"sync_lower\"" -msgstr "\"sync_lower\"" - -#: src/bare-metal/aps/exceptions.md:45 src/exercises/bare-metal/rtc.md:132 -msgid "\"irq_lower\"" -msgstr "\"irq_lower\"" - -#: src/bare-metal/aps/exceptions.md:51 src/exercises/bare-metal/rtc.md:138 -msgid "\"fiq_lower\"" -msgstr "\"fiq_lower\"" - -#: src/bare-metal/aps/exceptions.md:57 src/exercises/bare-metal/rtc.md:144 -msgid "\"serr_lower\"" -msgstr "\"serr_lower\"" - #: src/bare-metal/aps/exceptions.md:64 msgid "EL is exception level; all our examples this afternoon run in EL1." msgstr "" @@ -11971,6 +15610,10 @@ msgid "" "hypervisor), but isn't a good pattern in general." msgstr "" +#: src/bare-metal/useful-crates.md:1 +msgid "Useful crates" +msgstr "" + #: src/bare-metal/useful-crates.md:3 msgid "" "We'll go over a few crates which solve some common problems in bare-metal " @@ -12078,14 +15721,6 @@ msgid "" "space for PCI BARs:" msgstr "" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:19 -msgid "\"Failed to allocate 0x100 byte MMIO region\"" -msgstr "" - -#: src/bare-metal/useful-crates/buddy_system_allocator.md:20 -msgid "\"Allocated 0x100 byte MMIO region at {:#x}\"" -msgstr "" - #: src/bare-metal/useful-crates/buddy_system_allocator.md:26 msgid "PCI BARs always have alignment equal to their size." msgstr "" @@ -12110,12 +15745,6 @@ msgid "" "and panics if you try to use more than are allocated." msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:13 -#: src/bare-metal/useful-crates/tinyvec.md:15 -#: src/bare-metal/useful-crates/tinyvec.md:17 -msgid "\"{numbers:?}\"" -msgstr "\"{numbers:?}\"" - #: src/bare-metal/useful-crates/tinyvec.md:23 msgid "" "`tinyvec` requires that the element type implement `Default` for " @@ -12144,11 +15773,6 @@ msgid "" "equivalents of many of these primitives." msgstr "" -#: src/bare-metal/useful-crates/spin.md:15 -#: src/bare-metal/useful-crates/spin.md:17 -msgid "\"count: {}\"" -msgstr "\"count: {}\"" - #: src/bare-metal/useful-crates/spin.md:23 msgid "Be careful to avoid deadlock if you take locks in interrupt handlers." msgstr "" @@ -12179,48 +15803,6 @@ msgid "" "to convert the ELF to a raw binary ready to be run." msgstr "" -#: src/bare-metal/android.md:7 -msgid "" -"```soong\n" -"rust_ffi_static {\n" -" name: \"libvmbase_example\",\n" -" defaults: [\"vmbase_ffi_defaults\"],\n" -" crate_name: \"vmbase_example\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"libvmbase\",\n" -" ],\n" -"}\n" -"\n" -"cc_binary {\n" -" name: \"vmbase_example\",\n" -" defaults: [\"vmbase_elf_defaults\"],\n" -" srcs: [\n" -" \"idmap.S\",\n" -" ],\n" -" static_libs: [\n" -" \"libvmbase_example\",\n" -" ],\n" -" linker_scripts: [\n" -" \"image.ld\",\n" -" \":vmbase_sections\",\n" -" ],\n" -"}\n" -"\n" -"raw_binary {\n" -" name: \"vmbase_example_bin\",\n" -" stem: \"vmbase_example.bin\",\n" -" src: \":vmbase_example\",\n" -" enabled: false,\n" -" target: {\n" -" android_arm64: {\n" -" enabled: true,\n" -" },\n" -" },\n" -"}\n" -"```" -msgstr "" - #: src/bare-metal/android/vmbase.md:3 msgid "" "For VMs running under crosvm on aarch64, the [vmbase](https://android." @@ -12229,10 +15811,6 @@ msgid "" "build rules, along with an entry point, UART console logging and more." msgstr "" -#: src/bare-metal/android/vmbase.md:15 -msgid "\"Hello world\"" -msgstr "\"Hej verden\"" - #: src/bare-metal/android/vmbase.md:21 msgid "" "The `main!` macro marks your main function, to be called from the `vmbase` " @@ -12249,6 +15827,13 @@ msgstr "" msgid "We will write a driver for the PL031 real-time clock device." msgstr "" +#: src/exercises/bare-metal/afternoon.md:7 +#: src/exercises/concurrency/afternoon.md:13 +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"afternoon.md) provided." +msgstr "" + #: src/exercises/bare-metal/rtc.md:1 #: src/exercises/bare-metal/solutions-afternoon.md:3 msgid "RTC driver" @@ -12360,6 +15945,14 @@ msgstr "" "// See the License for the specific language governing permissions and\n" "// limitations under the License.\n" +#: src/exercises/bare-metal/rtc.md:101 +msgid "\"sync_exception_current\"" +msgstr "\"sync_exception_current\"" + +#: src/exercises/bare-metal/rtc.md:107 +msgid "\"irq_current\"" +msgstr "\"irq_current\"" + #: src/exercises/bare-metal/rtc.md:108 msgid "\"No pending interrupt\"" msgstr "\"No pending interrupt\"" @@ -12368,6 +15961,30 @@ msgstr "\"No pending interrupt\"" msgid "\"IRQ {intid:?}\"" msgstr "\"IRQ {intid:?}\"" +#: src/exercises/bare-metal/rtc.md:114 +msgid "\"fiq_current\"" +msgstr "\"fiq_current\"" + +#: src/exercises/bare-metal/rtc.md:120 +msgid "\"serr_current\"" +msgstr "\"serr_current\"" + +#: src/exercises/bare-metal/rtc.md:126 +msgid "\"sync_lower\"" +msgstr "\"sync_lower\"" + +#: src/exercises/bare-metal/rtc.md:132 +msgid "\"irq_lower\"" +msgstr "\"irq_lower\"" + +#: src/exercises/bare-metal/rtc.md:138 +msgid "\"fiq_lower\"" +msgstr "\"fiq_lower\"" + +#: src/exercises/bare-metal/rtc.md:144 +msgid "\"serr_lower\"" +msgstr "\"serr_lower\"" + #: src/exercises/bare-metal/rtc.md:149 msgid "_src/logger.rs_ (you shouldn't need to change this):" msgstr "" @@ -12454,30 +16071,6 @@ msgstr "" msgid "// ANCHOR_END: Uart\n" msgstr "// ANCHOR_END: Uart\n" -#: src/exercises/bare-metal/rtc.md:389 -msgid "" -"```toml\n" -"[workspace]\n" -"\n" -"[package]\n" -"name = \"rtc\"\n" -"version = \"0.1.0\"\n" -"edition = \"2021\"\n" -"publish = false\n" -"\n" -"[dependencies]\n" -"arm-gic = \"0.1.0\"\n" -"bitflags = \"2.0.0\"\n" -"chrono = { version = \"0.4.24\", default-features = false }\n" -"log = \"0.4.17\"\n" -"smccc = \"0.1.1\"\n" -"spin = \"0.9.8\"\n" -"\n" -"[build-dependencies]\n" -"cc = \"1.0.73\"\n" -"```" -msgstr "" - #: src/exercises/bare-metal/rtc.md:410 msgid "_build.rs_ (you shouldn't need to change this):" msgstr "" @@ -13046,41 +16639,192 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:940 -msgid "_Makefile_ (you shouldn't need to change this):" +#: src/exercises/bare-metal/rtc.md:940 +msgid "_Makefile_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md:945 +msgid "# Copyright 2023 Google LLC" +msgstr "# Copyright 2023 Google LLC" + +#: src/exercises/bare-metal/rtc.md:959 +msgid "$(shell uname -s)" +msgstr "$(shell uname -s)" + +#: src/exercises/bare-metal/rtc.md:961 +msgid "aarch64-linux-gnu" +msgstr "aarch64-linux-gnu" + +#: src/exercises/bare-metal/rtc.md:978 +msgid "stdio -display none -kernel $< -s" +msgstr "stdio -display none -kernel $< -s" + +#: src/exercises/bare-metal/rtc.md:981 +msgid "cargo clean" +msgstr "cargo clean" + +#: src/exercises/bare-metal/rtc.md:995 +msgid "Run the code in QEMU with `make qemu`." +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:1 +msgid "Bare Metal Rust Afternoon" +msgstr "Rå jern Rust eftermiddag" + +#: src/exercises/bare-metal/solutions-afternoon.md:5 +msgid "([back to exercise](rtc.md))" +msgstr "([tilbage til øvelsen](rtc.md))" + +#: src/exercises/bare-metal/solutions-afternoon.md:7 +#, fuzzy +msgid "_main.rs_:" +msgstr "_src/main.rs_:" + +#: src/exercises/bare-metal/solutions-afternoon.md:36 +msgid "/// Base address of the PL031 RTC.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:38 +msgid "/// The IRQ used by the PL031 RTC.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:57 +msgid "" +"// Safe because `PL031_BASE_ADDRESS` is the base address of a PL031 device,\n" +" // and nothing else accesses that address range.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:62 +msgid "\"RTC: {time}\"" +msgstr "\"RTC: {time}\"" + +#: src/exercises/bare-metal/solutions-afternoon.md:70 +msgid "// Wait for 3 seconds, without interrupts.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:74 +#: src/exercises/bare-metal/solutions-afternoon.md:95 +msgid "\"Waiting for {}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:78 +#: src/exercises/bare-metal/solutions-afternoon.md:86 +#: src/exercises/bare-metal/solutions-afternoon.md:102 +#: src/exercises/bare-metal/solutions-afternoon.md:110 +msgid "\"matched={}, interrupt_pending={}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:90 +#: src/exercises/bare-metal/solutions-afternoon.md:114 +msgid "\"Finished waiting\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:92 +msgid "// Wait another 3 seconds for an interrupt.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:127 +#, fuzzy +msgid "_pl031.rs_:" +msgstr "`pl031.rs`:" + +#: src/exercises/bare-metal/solutions-afternoon.md:134 +msgid "/// Data register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:136 +msgid "/// Match register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:138 +msgid "/// Load register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:140 +msgid "/// Control register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:143 +msgid "/// Interrupt Mask Set or Clear register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:146 +msgid "/// Raw Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:149 +msgid "/// Masked Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:152 +msgid "/// Interrupt Clear Register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:156 +msgid "/// Driver for a PL031 real-time clock.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:164 +msgid "" +"/// Constructs a new instance of the RTC driver for a PL031 device at the\n" +" /// given base address.\n" +" ///\n" +" /// # Safety\n" +" ///\n" +" /// The given base address must point to the MMIO control registers of " +"a\n" +" /// PL031 device, which must be mapped into the address space of the " +"process\n" +" /// as device memory and not have any other aliases.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:178 +msgid "/// Reads the current RTC value.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:180 +#: src/exercises/bare-metal/solutions-afternoon.md:188 +#: src/exercises/bare-metal/solutions-afternoon.md:196 +#: src/exercises/bare-metal/solutions-afternoon.md:207 +#: src/exercises/bare-metal/solutions-afternoon.md:219 +#: src/exercises/bare-metal/solutions-afternoon.md:226 +msgid "" +"// Safe because we know that self.registers points to the control\n" +" // registers of a PL031 device which is appropriately mapped.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md:185 +msgid "" +"/// Writes a match value. When the RTC value matches this then an interrupt\n" +" /// will be generated (if it is enabled).\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:945 -msgid "# Copyright 2023 Google LLC" -msgstr "# Copyright 2023 Google LLC" - -#: src/exercises/bare-metal/rtc.md:959 -msgid "$(shell uname -s)" -msgstr "$(shell uname -s)" - -#: src/exercises/bare-metal/rtc.md:961 -msgid "aarch64-linux-gnu" -msgstr "aarch64-linux-gnu" - -#: src/exercises/bare-metal/rtc.md:978 -msgid "stdio -display none -kernel $< -s" -msgstr "stdio -display none -kernel $< -s" +#: src/exercises/bare-metal/solutions-afternoon.md:193 +msgid "" +"/// Returns whether the match register matches the RTC value, whether or " +"not\n" +" /// the interrupt is enabled.\n" +msgstr "" -#: src/exercises/bare-metal/rtc.md:981 -msgid "cargo clean" -msgstr "cargo clean" +#: src/exercises/bare-metal/solutions-afternoon.md:202 +msgid "" +"/// Returns whether there is currently an interrupt pending.\n" +" ///\n" +" /// This should be true if and only if `matched` returns true and the\n" +" /// interrupt is masked.\n" +msgstr "" -#: src/exercises/bare-metal/rtc.md:989 +#: src/exercises/bare-metal/solutions-afternoon.md:213 msgid "" -"```toml\n" -"[build]\n" -"target = \"aarch64-unknown-none\"\n" -"rustflags = [\"-C\", \"link-arg=-Timage.ld\"]\n" -"```" +"/// Sets or clears the interrupt mask.\n" +" ///\n" +" /// When the mask is true the interrupt is enabled; when it is false " +"the\n" +" /// interrupt is disabled.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:995 -msgid "Run the code in QEMU with `make qemu`." +#: src/exercises/bare-metal/solutions-afternoon.md:224 +msgid "/// Clears a pending interrupt, if any.\n" msgstr "" #: src/concurrency.md:1 @@ -13127,9 +16871,10 @@ msgid "Panics can carry a payload, which can be unpacked with `downcast_ref`." msgstr "En panik kan have en nyttelast som kan udpakkes med `downcast_ref`." #: src/concurrency/threads.md:32 +#, fuzzy msgid "" -"Notice that the thread is stopped before it reaches 10 — the main thread is " -"not waiting." +"Notice that the thread is stopped before it reaches 10 --- the main thread " +"is not waiting." msgstr "Bemærk at tråden stopper før den når 10 --- hovedtråden venter ikke." #: src/concurrency/threads.md:35 @@ -13158,10 +16903,6 @@ msgstr "" msgid "Normal threads cannot borrow from their environment:" msgstr "Normale tråde kan ikke låne fra deres omgivelser:" -#: src/concurrency/scoped-threads.md:11 src/concurrency/scoped-threads.md:30 -msgid "\"Length: {}\"" -msgstr "\"Længde: {}\"" - #: src/concurrency/scoped-threads.md:20 msgid "" "However, you can use a [scoped thread](https://doc.rust-lang.org/std/thread/" @@ -13194,19 +16935,19 @@ msgid "" "parts are connected via the channel, but you only see the end-points." msgstr "" -#: src/concurrency/channels.md:16 src/concurrency/channels.md:17 -#: src/concurrency/channels.md:21 +#: src/concurrency/channels.md:15 src/concurrency/channels.md:16 +#: src/concurrency/channels.md:20 msgid "\"Received: {:?}\"" msgstr "\"Modtaget: {:?}\"" -#: src/concurrency/channels.md:27 +#: src/concurrency/channels.md:26 msgid "" "`mpsc` stands for Multi-Producer, Single-Consumer. `Sender` and `SyncSender` " "implement `Clone` (so you can make multiple producers) but `Receiver` does " "not." msgstr "" -#: src/concurrency/channels.md:29 +#: src/concurrency/channels.md:28 msgid "" "`send()` and `recv()` return `Result`. If they return `Err`, it means the " "counterpart `Sender` or `Receiver` is dropped and the channel is closed." @@ -13266,7 +17007,7 @@ msgstr "`Send` og `Sync`" #: src/concurrency/send-sync.md:3 msgid "" -"How does Rust know to forbid shared access across thread? The answer is in " +"How does Rust know to forbid shared access across threads? The answer is in " "two traits:" msgstr "" @@ -13432,8 +17173,8 @@ msgstr "" #: src/concurrency/send-sync/examples.md:31 msgid "" -"`MutexGuard`: Uses OS level primitives which must be deallocated on the " -"thread which created them." +"`MutexGuard`: Uses OS level primitives which must be deallocated on " +"the thread which created them." msgstr "" #: src/concurrency/send-sync/examples.md:34 @@ -13548,7 +17289,7 @@ msgstr "" #: src/concurrency/shared_state/mutex.md:31 msgid "" -"`Mutex` in Rust looks like a collection with just one element - the " +"`Mutex` in Rust looks like a collection with just one element --- the " "protected data." msgstr "" @@ -13571,7 +17312,7 @@ msgid "" msgstr "" #: src/concurrency/shared_state/mutex.md:36 -msgid "A read-write lock counterpart - `RwLock`." +msgid "A read-write lock counterpart: `RwLock`." msgstr "" #: src/concurrency/shared_state/mutex.md:37 @@ -13673,8 +17414,8 @@ msgid "" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:36 -#: src/exercises/concurrency/dining-philosophers-async.md:31 #: src/exercises/concurrency/solutions-morning.md:24 +#: src/exercises/concurrency/dining-philosophers-async.md:31 #: src/exercises/concurrency/solutions-afternoon.md:25 msgid "\"Eureka! {} has a new idea!\"" msgstr "" @@ -13686,43 +17427,43 @@ msgid "// Pick up forks...\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:42 -#: src/exercises/concurrency/dining-philosophers-async.md:37 #: src/exercises/concurrency/solutions-morning.md:33 +#: src/exercises/concurrency/dining-philosophers-async.md:37 #: src/exercises/concurrency/solutions-afternoon.md:37 msgid "\"{} is eating...\"" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:48 -#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-afternoon.md:45 msgid "\"Socrates\"" msgstr "\"Sokrates\"" #: src/exercises/concurrency/dining-philosophers.md:48 +#: src/exercises/concurrency/solutions-morning.md:39 #: src/exercises/concurrency/dining-philosophers-async.md:43 +#: src/exercises/concurrency/solutions-afternoon.md:45 +msgid "\"Hypatia\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md:48 #: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-afternoon.md:45 msgid "\"Plato\"" msgstr "\"Plato\"" #: src/exercises/concurrency/dining-philosophers.md:48 -#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-morning.md:39 +#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-afternoon.md:45 msgid "\"Aristotle\"" msgstr "\"Aristoteles\"" #: src/exercises/concurrency/dining-philosophers.md:48 -#: src/exercises/concurrency/dining-philosophers-async.md:43 #: src/exercises/concurrency/solutions-morning.md:39 -#: src/exercises/concurrency/solutions-afternoon.md:45 -msgid "\"Thales\"" -msgstr "\"Thales\"" - -#: src/exercises/concurrency/dining-philosophers.md:48 #: src/exercises/concurrency/dining-philosophers-async.md:43 -#: src/exercises/concurrency/solutions-morning.md:39 #: src/exercises/concurrency/solutions-afternoon.md:45 msgid "\"Pythagoras\"" msgstr "\"Pythagoras\"" @@ -13872,7 +17613,7 @@ msgid "\"On {base_url:#}: ignored unparsable {href:?}: {err}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:111 -#: src/exercises/concurrency/solutions-morning.md:246 +#: src/exercises/concurrency/solutions-morning.md:249 msgid "\"https://www.google.org\"" msgstr "\"https://www.google.org\"" @@ -13901,6 +17642,60 @@ msgid "" "being blocked by the site." msgstr "" +#: src/exercises/concurrency/solutions-morning.md:1 +msgid "Concurrency Morning Exercise" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:5 +msgid "([back to exercise](dining-philosophers.md))" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:29 +msgid "\"{} is trying to eat\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:53 +msgid "" +"// To avoid a deadlock, we have to break the symmetry\n" +" // somewhere. This will swap the forks without deinitializing\n" +" // either of them.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:77 +msgid "\"{thought}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:82 +msgid "Link Checker" +msgstr "Linktjekker" + +#: src/exercises/concurrency/solutions-morning.md:84 +msgid "([back to exercise](link-checker.md))" +msgstr "([tilbage til øvelsen](link-checker.md))" + +#: src/exercises/concurrency/solutions-morning.md:155 +msgid "" +"/// Determine whether links within the given page should be extracted.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:163 +msgid "" +"/// Mark the given page as visited, returning false if it had already\n" +" /// been visited.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:189 +msgid "// The sender got dropped. No more commands coming in.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:233 +msgid "\"Got crawling error: {:#}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md:251 +msgid "\"Bad URLs: {:#?}\"" +msgstr "" + #: src/async.md:1 msgid "Async Rust" msgstr "" @@ -13928,10 +17723,6 @@ msgid "" "available." msgstr "" -#: src/async.md:17 -msgid "Comparisons" -msgstr "Sammenligninger" - #: src/async.md:19 msgid "" "Python has a similar model in its `asyncio`. However, its `Future` type is " @@ -14196,21 +17987,28 @@ msgstr "" #: src/async/tasks.md:54 msgid "" +"Try connecting to it with a TCP connection tool like [nc](https://www.unix." +"com/man-page/linux/1/nc/) or [telnet](https://www.unix.com/man-page/linux/1/" +"telnet/)." +msgstr "" + +#: src/async/tasks.md:56 +msgid "" "Ask students to visualize what the state of the example server would be with " "a few connected clients. What tasks exist? What are their Futures?" msgstr "" -#: src/async/tasks.md:57 +#: src/async/tasks.md:59 msgid "" "This is the first time we've seen an `async` block. This is similar to a " "closure, but does not take any arguments. Its return value is a Future, " "similar to an `async fn`. " msgstr "" -#: src/async/tasks.md:61 +#: src/async/tasks.md:63 msgid "" "Refactor the async block into a function, and improve the error handling " -"using `?`." +"using `?`. " msgstr "" #: src/async/channels.md:3 @@ -14308,11 +18106,6 @@ msgstr "\"https://play.rust-lang.org/\"" msgid "\"BAD_URL\"" msgstr "\"BAD_URL\"" -#: src/async/control-flow/join.md:30 -#: src/exercises/day-1/solutions-morning.md:78 -msgid "\"{:?}\"" -msgstr "\"{:?}\"" - #: src/async/control-flow/join.md:38 msgid "" "For multiple futures of disjoint types, you can use `std::future::join!` but " @@ -14690,9 +18483,7 @@ msgid "" msgstr "" #: src/async/pitfalls/cancellation.md:95 -msgid "" -"// prefix buf and bytes with self.\n" -" // ...\n" +msgid "// prefix buf and bytes with self.\n" msgstr "" #: src/async/pitfalls/cancellation.md:104 @@ -14735,8 +18526,9 @@ msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:1 #: src/exercises/concurrency/solutions-afternoon.md:3 -msgid "Dining Philosophers - Async" -msgstr "" +#, fuzzy +msgid "Dining Philosophers --- Async" +msgstr "Filosoffer omkring spisebordet" #: src/exercises/concurrency/dining-philosophers-async.md:3 msgid "" @@ -14890,6 +18682,7 @@ msgid "" msgstr "" #: src/exercises/concurrency/chat-app.md:59 +#: src/exercises/concurrency/solutions-afternoon.md:99 msgid "_src/bin/server.rs_:" msgstr "_src/bin/server.rs_:" @@ -14919,6 +18712,7 @@ msgid "// Wrap the raw TCP stream into a websocket.\n" msgstr "" #: src/exercises/concurrency/chat-app.md:103 +#: src/exercises/concurrency/solutions-afternoon.md:166 msgid "_src/bin/client.rs_:" msgstr "_src/bin/client.rs_:" @@ -14968,838 +18762,696 @@ msgid "" "clients, but the sender of the message." msgstr "" -#: src/thanks.md:3 -msgid "" -"_Thank you for taking Comprehensive Rust 🦀!_ We hope you enjoyed it and " -"that it was useful." -msgstr "" -"_Tak for at tage Comprehensive Rust 🦀!_ Vi håber du har nydt det og at det " -"har været hjælpsomt." - -#: src/thanks.md:6 -msgid "" -"We've had a lot of fun putting the course together. The course is not " -"perfect, so if you spotted any mistakes or have ideas for improvements, " -"please get in [contact with us on GitHub](https://github.com/google/" -"comprehensive-rust/discussions). We would love to hear from you." -msgstr "" - -#: src/other-resources.md:1 -msgid "Other Rust Resources" -msgstr "Andre Rust-resourcer" - -#: src/other-resources.md:3 -msgid "" -"The Rust community has created a wealth of high-quality and free resources " -"online." -msgstr "" - -#: src/other-resources.md:6 -msgid "Official Documentation" -msgstr "Officiel dokumentation" - -#: src/other-resources.md:8 -msgid "The Rust project hosts many resources. These cover Rust in general:" -msgstr "" - -#: src/other-resources.md:10 -msgid "" -"[The Rust Programming Language](https://doc.rust-lang.org/book/): the " -"canonical free book about Rust. Covers the language in detail and includes a " -"few projects for people to build." -msgstr "" - -#: src/other-resources.md:13 -msgid "" -"[Rust By Example](https://doc.rust-lang.org/rust-by-example/): covers the " -"Rust syntax via a series of examples which showcase different constructs. " -"Sometimes includes small exercises where you are asked to expand on the code " -"in the examples." -msgstr "" - -#: src/other-resources.md:17 -msgid "" -"[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation " -"of the standard library for Rust." -msgstr "" - -#: src/other-resources.md:19 -msgid "" -"[The Rust Reference](https://doc.rust-lang.org/reference/): an incomplete " -"book which describes the Rust grammar and memory model." +#: src/exercises/concurrency/solutions-afternoon.md:1 +msgid "Concurrency Afternoon Exercise" msgstr "" -#: src/other-resources.md:22 -msgid "More specialized guides hosted on the official Rust site:" +#: src/exercises/concurrency/solutions-afternoon.md:5 +msgid "([back to exercise](dining-philosophers-async.md))" msgstr "" -#: src/other-resources.md:24 +#: src/exercises/concurrency/solutions-afternoon.md:32 msgid "" -"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " -"including working with raw pointers and interfacing with other languages " -"(FFI)." +"// Add a delay before picking the second fork to allow the execution\n" +" // to transfer to another task\n" msgstr "" -#: src/other-resources.md:27 -msgid "" -"[Asynchronous Programming in Rust](https://rust-lang.github.io/async-book/): " -"covers the new asynchronous programming model which was introduced after the " -"Rust Book was written." +#: src/exercises/concurrency/solutions-afternoon.md:40 +msgid "// The locks are dropped here\n" msgstr "" -#: src/other-resources.md:30 +#: src/exercises/concurrency/solutions-afternoon.md:60 msgid "" -"[The Embedded Rust Book](https://doc.rust-lang.org/stable/embedded-book/): " -"an introduction to using Rust on embedded devices without an operating " -"system." +"// To avoid a deadlock, we have to break the symmetry\n" +" // somewhere. This will swap the forks without deinitializing\n" +" // either of them.\n" msgstr "" -#: src/other-resources.md:33 -msgid "Unofficial Learning Material" +#: src/exercises/concurrency/solutions-afternoon.md:74 +msgid "// tx is dropped here, so we don't need to explicitly drop it later\n" msgstr "" -#: src/other-resources.md:35 -msgid "A small selection of other guides and tutorial for Rust:" +#: src/exercises/concurrency/solutions-afternoon.md:90 +msgid "\"Here is a thought: {thought}\"" msgstr "" -#: src/other-resources.md:37 -msgid "" -"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust " -"from the perspective of low-level C programmers." -msgstr "" +#: src/exercises/concurrency/solutions-afternoon.md:97 +msgid "([back to exercise](chat-app.md))" +msgstr "([tilbage til øvelsen](chat-app.md))" -#: src/other-resources.md:39 -msgid "" -"[Rust for Embedded C Programmers](https://docs.opentitan.org/doc/ug/" -"rust_for_c/): covers Rust from the perspective of developers who write " -"firmware in C." +#: src/exercises/concurrency/solutions-afternoon.md:117 +msgid "\"Welcome to chat! Type a message\"" msgstr "" -#: src/other-resources.md:42 +#: src/exercises/concurrency/solutions-afternoon.md:121 msgid "" -"[Rust for professionals](https://overexact.com/rust-for-professionals/): " -"covers the syntax of Rust using side-by-side comparisons with other " -"languages such as C, C++, Java, JavaScript, and Python." +"// A continuous loop for concurrently performing two tasks: (1) receiving\n" +" // messages from `ws_stream` and broadcasting them, and (2) receiving\n" +" // messages on `bcast_rx` and sending them to the client.\n" msgstr "" -#: src/other-resources.md:45 -msgid "" -"[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " -"you learn Rust." +#: src/exercises/concurrency/solutions-afternoon.md:130 +msgid "\"From client {addr:?} {text:?}\"" msgstr "" -#: src/other-resources.md:47 -msgid "" -"[Ferrous Teaching Material](https://ferrous-systems.github.io/teaching-" -"material/index.html): a series of small presentations covering both basic " -"and advanced part of the Rust language. Other topics such as WebAssembly, " -"and async/await are also covered." +#: src/exercises/concurrency/solutions-afternoon.md:185 +msgid "// Continuous loop for concurrently sending and receiving messages.\n" msgstr "" -#: src/other-resources.md:52 -msgid "" -"[Beginner's Series to Rust](https://docs.microsoft.com/en-us/shows/beginners-" -"series-to-rust/) and [Take your first steps with Rust](https://docs." -"microsoft.com/en-us/learn/paths/rust-first-steps/): two Rust guides aimed at " -"new developers. The first is a set of 35 videos and the second is a set of " -"11 modules which covers Rust syntax and basic constructs." +#: src/exercises/concurrency/solutions-afternoon.md:192 +msgid "\"From server: {}\"" msgstr "" -#: src/other-resources.md:58 +#: src/thanks.md:3 msgid "" -"[Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial." -"github.io/too-many-lists/): in-depth exploration of Rust's memory management " -"rules, through implementing a few different types of list structures." +"_Thank you for taking Comprehensive Rust 🦀!_ We hope you enjoyed it and " +"that it was useful." msgstr "" +"_Tak for at tage Comprehensive Rust 🦀!_ Vi håber du har nydt det og at det " +"har været hjælpsomt." -#: src/other-resources.md:63 +#: src/thanks.md:6 msgid "" -"Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " -"for even more Rust books." +"We've had a lot of fun putting the course together. The course is not " +"perfect, so if you spotted any mistakes or have ideas for improvements, " +"please get in [contact with us on GitHub](https://github.com/google/" +"comprehensive-rust/discussions). We would love to hear from you." msgstr "" -#: src/credits.md:3 +#: src/glossary.md:3 msgid "" -"The material here builds on top of the many great sources of Rust " -"documentation. See the page on [other resources](other-resources.md) for a " -"full list of useful resources." +"The following is a glossary which aims to give a short definition of many " +"Rust terms. For translations, this also serves to connect the term back to " +"the English original." msgstr "" -#: src/credits.md:7 +#: src/glossary.md:30 msgid "" -"The material of Comprehensive Rust is licensed under the terms of the Apache " -"2.0 license, please see [`LICENSE`](https://github.com/google/comprehensive-" -"rust/blob/main/LICENSE) for details." +"allocate: \n" +"Dynamic memory allocation on [the heap](memory-management/stack-vs-heap.md)." msgstr "" -#: src/credits.md:12 -msgid "Rust by Example" -msgstr "Rust by Example" - -#: src/credits.md:14 +#: src/glossary.md:32 msgid "" -"Some examples and exercises have been copied and adapted from [Rust by " -"Example](https://doc.rust-lang.org/rust-by-example/). Please see the " -"`third_party/rust-by-example/` directory for details, including the license " -"terms." +"argument: \n" +"Information that is passed into a function or method." msgstr "" -#: src/credits.md:19 -msgid "Rust on Exercism" -msgstr "Rust på Exercism" - -#: src/credits.md:21 +#: src/glossary.md:34 msgid "" -"Some exercises have been copied and adapted from [Rust on Exercism](https://" -"exercism.org/tracks/rust). Please see the `third_party/rust-on-exercism/` " -"directory for details, including the license terms." +"Bare-metal Rust: \n" +"Low-level Rust development, often deployed to a system without an operating " +"system. See [Bare-metal Rust](bare-metal.md)." msgstr "" -#: src/credits.md:26 -msgid "CXX" -msgstr "CXX" - -#: src/credits.md:28 +#: src/glossary.md:37 msgid "" -"The [Interoperability with C++](android/interoperability/cpp.md) section " -"uses an image from [CXX](https://cxx.rs/). Please see the `third_party/cxx/` " -"directory for details, including the license terms." +"block: \n" +"See [Blocks](control-flow/blocks.md) and _scope_." msgstr "" -#: src/exercises/solutions.md:3 -msgid "You will find solutions to the exercises on the following pages." -msgstr "Du til finde løsningerne til opgaverne på de næste sider." - -#: src/exercises/solutions.md:5 +#: src/glossary.md:39 msgid "" -"Feel free to ask questions about the solutions [on GitHub](https://github." -"com/google/comprehensive-rust/discussions). Let us know if you have a " -"different or better solution than what is presented here." +"borrow: \n" +"See [Borrowing](ownership/borrowing.md)." msgstr "" -#: src/exercises/day-1/solutions-morning.md:1 -msgid "Day 1 Morning Exercises" -msgstr "Dag 1 formiddagsøvelser" - -#: src/exercises/day-1/solutions-morning.md:5 -msgid "([back to exercise](for-loops.md))" -msgstr "([tilbage til øvelsen](for-loops.md))" - -#: src/exercises/day-1/solutions-morning.md:20 -msgid "\"{row:?}\"" +#: src/glossary.md:41 +msgid "" +"borrow checker: \n" +"The part of the Rust compiler which checks that all borrows are valid." msgstr "" -#: src/exercises/day-1/solutions-morning.md:27 -#: src/exercises/day-1/solutions-morning.md:35 -msgid "//\n" +#: src/glossary.md:43 +msgid "" +"brace: \n" +"`{` and `}`. Also called _curly brace_, they delimit _blocks_." msgstr "" -#: src/exercises/day-1/solutions-morning.md:57 -msgid "Bonus question" -msgstr "Bonusspørgsmål" - -#: src/exercises/day-1/solutions-morning.md:59 +#: src/glossary.md:45 msgid "" -"It requires more advanced concepts. It might seem that we could use a slice-" -"of-slices (`&[&[i32]]`) as the input type to transpose and thus make our " -"function handle any size of matrix. However, this quickly breaks down: the " -"return type cannot be `&[&[i32]]` since it needs to own the data you return." +"build: \n" +"The process of converting source code into executable code or a usable " +"program." msgstr "" -#: src/exercises/day-1/solutions-morning.md:61 +#: src/glossary.md:47 msgid "" -"You can attempt to use something like `Vec>`, but this doesn't work " -"out-of-the-box either: it's hard to convert from `Vec>` to " -"`&[&[i32]]` so now you cannot easily use `pretty_print` either." +"call: \n" +"To invoke or execute a function or method." msgstr "" -#: src/exercises/day-1/solutions-morning.md:63 +#: src/glossary.md:49 msgid "" -"Once we get to traits and generics, we'll be able to use the [`std::convert::" -"AsRef`](https://doc.rust-lang.org/std/convert/trait.AsRef.html) trait to " -"abstract over anything that can be referenced as a slice." +"channel: \n" +"Used to safely pass messages [between threads](concurrency/channels.md)." msgstr "" -#: src/exercises/day-1/solutions-morning.md:72 -msgid "// A line references a slice of items\n" +#: src/glossary.md:51 +msgid "" +"Comprehensive Rust 🦀: \n" +"The courses here are jointly called Comprehensive Rust 🦀." msgstr "" -#: src/exercises/day-1/solutions-morning.md:74 -msgid "// A matrix references a slice of lines\n" +#: src/glossary.md:53 +msgid "" +"concurrency: \n" +"The execution of multiple tasks or processes at the same time." msgstr "" -#: src/exercises/day-1/solutions-morning.md:83 -msgid "// &[&[i32]]\n" -msgstr "// &[&[i32]]\n" - -#: src/exercises/day-1/solutions-morning.md:85 -msgid "// [[&str; 2]; 2]\n" -msgstr "// [[&str; 2]; 2]\n" - -#: src/exercises/day-1/solutions-morning.md:87 -msgid "// Vec>\n" -msgstr "// Vec>\n" - -#: src/exercises/day-1/solutions-morning.md:92 +#: src/glossary.md:55 msgid "" -"In addition, the type itself would not enforce that the child slices are of " -"the same length, so such variable could contain an invalid matrix." +"Concurrency in Rust: \n" +"See [Concurrency in Rust](concurrency.md)." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:1 -msgid "Day 1 Afternoon Exercises" +#: src/glossary.md:57 +msgid "" +"constant: \n" +"A value that does not change during the execution of a program." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:5 -msgid "([back to exercise](luhn.md))" -msgstr "([tilbage til øvelsen](luhn.md))" - -#: src/exercises/day-1/solutions-afternoon.md:34 -msgid "\"1234 5678 1234 5670\"" -msgstr "\"1234 5678 1234 5670\"" - -#: src/exercises/day-1/solutions-afternoon.md:36 -msgid "\"Is {cc_number} a valid credit card number? {}\"" -msgstr "\"Er {cc_number} et gyldigt kreditkortnummer? {}\"" - -#: src/exercises/day-1/solutions-afternoon.md:80 -msgid "Pattern matching" -msgstr "Mønstergenkendelse" - -#: src/exercises/day-1/solutions-afternoon.md:205 -msgid "\"expr: {:?}\"" -msgstr "\"expr: {:?}\"" - -#: src/exercises/day-1/solutions-afternoon.md:206 -msgid "\"result: {:?}\"" -msgstr "\"result: {:?}\"" - -#: src/exercises/day-2/solutions-morning.md:1 -msgid "Day 2 Morning Exercises" -msgstr "Dag 2 formiddagsøvelser" - -#: src/exercises/day-2/solutions-morning.md:3 -msgid "Designing a Library" -msgstr "Design af et bibliotek" - -#: src/exercises/day-2/solutions-morning.md:5 -msgid "([back to exercise](book-library.md))" -msgstr "([tilbage til øvelsen](book-library.md))" - -#: src/exercises/day-2/solutions-morning.md:54 -msgid "\"{}, published in {}\"" +#: src/glossary.md:59 +msgid "" +"control flow: \n" +"The order in which the individual statements or instructions are executed in " +"a program." msgstr "" -#: src/exercises/day-2/solutions-morning.md:59 +#: src/glossary.md:61 msgid "" -"// Using a closure and a built-in method:\n" -" // self.books.iter().min_by_key(|book| book.year)\n" +"crash: \n" +"An unexpected and unhandled failure or termination of a program." msgstr "" -#: src/exercises/day-2/solutions-morning.md:62 -msgid "// Longer hand-written solution:\n" +#: src/glossary.md:63 +msgid "" +"enumeration: \n" +"A data type that consists of named constant values." msgstr "" -#: src/exercises/day-2/solutions-morning.md:127 +#: src/glossary.md:65 msgid "" -"// We could try and capture stdout, but let us just call the\n" -" // method to start with.\n" +"error: \n" +"An unexpected condition or result that deviates from the expected behavior." msgstr "" -#: src/exercises/day-2/solutions-morning.md:153 -msgid "([back to exercise](health-statistics.md))" -msgstr "([tilbage til øvelsen](health-statistics.md))" - -#: src/exercises/day-2/solutions-afternoon.md:1 -msgid "Day 2 Afternoon Exercises" +#: src/glossary.md:67 +msgid "" +"error handling: \n" +"The process of managing and responding to errors that occur during program " +"execution." msgstr "" -#: src/exercises/day-2/solutions-afternoon.md:5 -msgid "([back to exercise](strings-iterators.md))" -msgstr "([tilbage til øvelsen](strings-iterators.md))" - -#: src/exercises/day-2/solutions-afternoon.md:10 -#: src/exercises/day-2/solutions-afternoon.md:12 -msgid "'/'" -msgstr "'/'" - -#: src/exercises/day-2/solutions-afternoon.md:16 -msgid "\"*\"" -msgstr "\"*\"" - -#: src/exercises/day-2/solutions-afternoon.md:22 +#: src/glossary.md:69 msgid "" -"// Alternatively, Iterator::zip() lets us iterate simultaneously over " -"prefix\n" -" // and request segments. The zip() iterator is finished as soon as one " -"of\n" -" // the source iterators is finished, but we need to iterate over all " -"request\n" -" // segments. A neat trick that makes zip() work is to use map() and " -"chain()\n" -" // to produce an iterator that returns Some(str) for each pattern " -"segments,\n" -" // and then returns None indefinitely.\n" +"exercise: \n" +"A task or problem designed to practice and test programming skills." msgstr "" -#: src/exercises/day-3/solutions-morning.md:1 -msgid "Day 3 Morning Exercise" -msgstr "Dag 3 formiddagsøvelser" - -#: src/exercises/day-3/solutions-morning.md:5 -msgid "([back to exercise](simple-gui.md))" -msgstr "([tilbage til øvelsen](simple-gui.md))" - -#: src/exercises/day-3/solutions-morning.md:77 -msgid "// Add 4 paddings for borders\n" +#: src/glossary.md:71 +msgid "" +"function: \n" +"A reusable block of code that performs a specific task." msgstr "" -#: src/exercises/day-3/solutions-morning.md:89 +#: src/glossary.md:73 msgid "" -"// TODO: after learning about error handling, you can change\n" -" // draw_into to return Result<(), std::fmt::Error>. Then use\n" -" // the ?-operator here instead of .unwrap().\n" +"garbage collector: \n" +"A mechanism that automatically frees up memory occupied by objects that are " +"no longer in use." msgstr "" -#: src/exercises/day-3/solutions-morning.md:92 -#: src/exercises/day-3/solutions-morning.md:98 -msgid "\"+-{:-\\n\"" -msgstr "\"\\n\"" - -#: src/exercises/day-3/solutions-afternoon.md:152 -#: src/exercises/day-3/solutions-afternoon.md:158 -msgid "\"crab.rs\"" -msgstr "\"crab.rs\"" - -#: src/exercises/day-3/solutions-afternoon.md:152 -msgid "\"//! Crab\\n\"" +#: src/glossary.md:106 +msgid "" +"panic: \n" +"An unrecoverable error condition in Rust that results in the termination of " +"the program." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:1 -msgid "Bare Metal Rust Morning Exercise" -msgstr "Bar metal formiddagsøvelser" - -#: src/exercises/bare-metal/solutions-morning.md:5 -msgid "([back to exercise](compass.md))" -msgstr "([tilbage til øvelsen](compass.md))" - -#: src/exercises/bare-metal/solutions-morning.md:40 -msgid "// Set up the I2C controller and Inertial Measurement Unit.\n" +#: src/glossary.md:108 +msgid "" +"parameter: \n" +"A value that is passed into a function or method when it is called." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:41 -msgid "\"Setting up IMU...\"" +#: src/glossary.md:110 +msgid "" +"pattern: \n" +"A combination of values, literals, or structures that can be matched against " +"an expression in Rust." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:49 -msgid "// Set up display and timer.\n" +#: src/glossary.md:112 +msgid "" +"payload: \n" +"The data or information carried by a message, event, or data structure." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:59 -msgid "// Read compass data and log it to the serial port.\n" +#: src/glossary.md:114 +msgid "" +"program: \n" +"A set of instructions that a computer can execute to perform a specific task " +"or solve a particular problem." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:67 -msgid "\"{},{},{}\\t{},{},{}\"" -msgstr "\"{},{},{}\\t{},{},{}\"" - -#: src/exercises/bare-metal/solutions-morning.md:103 +#: src/glossary.md:116 msgid "" -"// If button A is pressed, switch to the next mode and briefly blink all " -"LEDs on.\n" +"programming language: \n" +"A formal system used to communicate instructions to a computer, such as Rust." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:5 -msgid "([back to exercise](rtc.md))" -msgstr "([tilbage til øvelsen](rtc.md))" - -#: src/exercises/bare-metal/solutions-afternoon.md:7 -msgid "`main.rs`:" -msgstr "`main.rs`:" - -#: src/exercises/bare-metal/solutions-afternoon.md:36 -msgid "/// Base address of the PL031 RTC.\n" +#: src/glossary.md:118 +msgid "" +"receiver: \n" +"The first parameter in a Rust method that represents the instance on which " +"the method is called." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:38 -msgid "/// The IRQ used by the PL031 RTC.\n" +#: src/glossary.md:120 +msgid "" +"reference counting: \n" +"A memory management technique in which the number of references to an object " +"is tracked, and the object is deallocated when the count reaches zero." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:57 +#: src/glossary.md:122 msgid "" -"// Safe because `PL031_BASE_ADDRESS` is the base address of a PL031 device,\n" -" // and nothing else accesses that address range.\n" +"return: \n" +"A keyword in Rust used to indicate the value to be returned from a function." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:62 -msgid "\"RTC: {time}\"" -msgstr "\"RTC: {time}\"" - -#: src/exercises/bare-metal/solutions-afternoon.md:70 -msgid "// Wait for 3 seconds, without interrupts.\n" +#: src/glossary.md:124 +msgid "" +"Rust: \n" +"A systems programming language that focuses on safety, performance, and " +"concurrency." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:74 -#: src/exercises/bare-metal/solutions-afternoon.md:95 -msgid "\"Waiting for {}\"" +#: src/glossary.md:126 +msgid "" +"Rust Fundamentals: \n" +"Days 1 to 3 of this course." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:78 -#: src/exercises/bare-metal/solutions-afternoon.md:86 -#: src/exercises/bare-metal/solutions-afternoon.md:102 -#: src/exercises/bare-metal/solutions-afternoon.md:110 -msgid "\"matched={}, interrupt_pending={}\"" +#: src/glossary.md:128 +msgid "" +"Rust in Android: \n" +"See [Rust in Android](android.md)." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:90 -#: src/exercises/bare-metal/solutions-afternoon.md:114 -msgid "\"Finished waiting\"" +#: src/glossary.md:130 +msgid "" +"Rust in Chromium: \n" +"See [Rust in Chromium](chromium.md)." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:92 -msgid "// Wait another 3 seconds for an interrupt.\n" +#: src/glossary.md:132 +msgid "" +"safe: \n" +"Refers to code that adheres to Rust's ownership and borrowing rules, " +"preventing memory-related errors." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:127 -msgid "`pl031.rs`:" -msgstr "`pl031.rs`:" - -#: src/exercises/bare-metal/solutions-afternoon.md:134 -msgid "/// Data register\n" +#: src/glossary.md:134 +msgid "" +"scope: \n" +"The region of a program where a variable is valid and can be used." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:136 -msgid "/// Match register\n" +#: src/glossary.md:136 +msgid "" +"standard library: \n" +"A collection of modules providing essential functionality in Rust." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:138 -msgid "/// Load register\n" +#: src/glossary.md:138 +msgid "" +"static: \n" +"A keyword in Rust used to define static variables or items with a `'static` " +"lifetime." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:140 -msgid "/// Control register\n" +#: src/glossary.md:140 +msgid "" +"string: \n" +"A data type storing textual data. See [`String` vs `str`](basic-syntax/" +"string-slices.html) for more." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:143 -msgid "/// Interrupt Mask Set or Clear register\n" +#: src/glossary.md:142 +msgid "" +"struct: \n" +"A composite data type in Rust that groups together variables of different " +"types under a single name." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:146 -msgid "/// Raw Interrupt Status\n" +#: src/glossary.md:144 +msgid "" +"test: \n" +"A Rust module containing functions that test the correctness of other " +"functions." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:149 -msgid "/// Masked Interrupt Status\n" +#: src/glossary.md:146 +msgid "" +"thread: \n" +"A separate sequence of execution in a program, allowing concurrent execution." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:152 -msgid "/// Interrupt Clear Register\n" +#: src/glossary.md:148 +msgid "" +"thread safety: \n" +"The property of a program that ensures correct behavior in a multithreaded " +"environment." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:156 -msgid "/// Driver for a PL031 real-time clock.\n" +#: src/glossary.md:150 +msgid "" +"trait: \n" +"A collection of methods defined for an unknown type, providing a way to " +"achieve polymorphism in Rust." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:164 +#: src/glossary.md:152 msgid "" -"/// Constructs a new instance of the RTC driver for a PL031 device at the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the MMIO control registers of " -"a\n" -" /// PL031 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" +"type: \n" +"A classification that specifies which operations can be performed on values " +"of a particular kind in Rust." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:178 -msgid "/// Reads the current RTC value.\n" +#: src/glossary.md:154 +msgid "" +"type inference: \n" +"The ability of the Rust compiler to deduce the type of a variable or " +"expression." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:180 -#: src/exercises/bare-metal/solutions-afternoon.md:188 -#: src/exercises/bare-metal/solutions-afternoon.md:196 -#: src/exercises/bare-metal/solutions-afternoon.md:207 -#: src/exercises/bare-metal/solutions-afternoon.md:219 -#: src/exercises/bare-metal/solutions-afternoon.md:226 +#: src/glossary.md:156 msgid "" -"// Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" +"undefined behavior: \n" +"Actions or conditions in Rust that have no specified result, often leading " +"to unpredictable program behavior." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:185 +#: src/glossary.md:158 msgid "" -"/// Writes a match value. When the RTC value matches this then an interrupt\n" -" /// will be generated (if it is enabled).\n" +"union: \n" +"A data type that can hold values of different types but only one at a time." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:193 +#: src/glossary.md:160 msgid "" -"/// Returns whether the match register matches the RTC value, whether or " -"not\n" -" /// the interrupt is enabled.\n" +"unit test: \n" +"Rust comes with built-in support for running small unit tests and larger " +"integration tests. See [Unit Tests](testing/unit-tests.html)." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:202 +#: src/glossary.md:163 msgid "" -"/// Returns whether there is currently an interrupt pending.\n" -" ///\n" -" /// This should be true if and only if `matched` returns true and the\n" -" /// interrupt is masked.\n" +"unsafe: \n" +"The subset of Rust which allows you to trigger _undefined behavior_. See " +"[Unsafe Rust](unsafe.html)." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:213 +#: src/glossary.md:165 msgid "" -"/// Sets or clears the interrupt mask.\n" -" ///\n" -" /// When the mask is true the interrupt is enabled; when it is false " -"the\n" -" /// interrupt is disabled.\n" +"variable: \n" +"A memory location storing data. Variables are valid in a _scope_. " msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:224 -msgid "/// Clears a pending interrupt, if any.\n" -msgstr "" +#: src/other-resources.md:1 +msgid "Other Rust Resources" +msgstr "Andre Rust-resourcer" -#: src/exercises/concurrency/solutions-morning.md:1 -msgid "Concurrency Morning Exercise" +#: src/other-resources.md:3 +msgid "" +"The Rust community has created a wealth of high-quality and free resources " +"online." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:5 -msgid "([back to exercise](dining-philosophers.md))" +#: src/other-resources.md:6 +msgid "Official Documentation" +msgstr "Officiel dokumentation" + +#: src/other-resources.md:8 +msgid "The Rust project hosts many resources. These cover Rust in general:" msgstr "" -#: src/exercises/concurrency/solutions-morning.md:29 -msgid "\"{} is trying to eat\"" +#: src/other-resources.md:10 +msgid "" +"[The Rust Programming Language](https://doc.rust-lang.org/book/): the " +"canonical free book about Rust. Covers the language in detail and includes a " +"few projects for people to build." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:53 +#: src/other-resources.md:13 msgid "" -"// To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" +"[Rust By Example](https://doc.rust-lang.org/rust-by-example/): covers the " +"Rust syntax via a series of examples which showcase different constructs. " +"Sometimes includes small exercises where you are asked to expand on the code " +"in the examples." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:77 -msgid "\"{thought}\"" +#: src/other-resources.md:17 +msgid "" +"[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation " +"of the standard library for Rust." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:82 -msgid "Link Checker" -msgstr "Linktjekker" +#: src/other-resources.md:19 +msgid "" +"[The Rust Reference](https://doc.rust-lang.org/reference/): an incomplete " +"book which describes the Rust grammar and memory model." +msgstr "" -#: src/exercises/concurrency/solutions-morning.md:84 -msgid "([back to exercise](link-checker.md))" -msgstr "([tilbage til øvelsen](link-checker.md))" +#: src/other-resources.md:22 +msgid "More specialized guides hosted on the official Rust site:" +msgstr "" -#: src/exercises/concurrency/solutions-morning.md:155 +#: src/other-resources.md:24 msgid "" -"/// Determine whether links within the given page should be extracted.\n" +"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " +"including working with raw pointers and interfacing with other languages " +"(FFI)." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:163 +#: src/other-resources.md:27 msgid "" -"/// Mark the given page as visited, returning true if it had already\n" -" /// been visited.\n" +"[Asynchronous Programming in Rust](https://rust-lang.github.io/async-book/): " +"covers the new asynchronous programming model which was introduced after the " +"Rust Book was written." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:189 -msgid "// The sender got dropped. No more commands coming in.\n" +#: src/other-resources.md:30 +msgid "" +"[The Embedded Rust Book](https://doc.rust-lang.org/stable/embedded-book/): " +"an introduction to using Rust on embedded devices without an operating " +"system." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:230 -msgid "\"Got crawling error: {:#}\"" +#: src/other-resources.md:33 +msgid "Unofficial Learning Material" msgstr "" -#: src/exercises/concurrency/solutions-morning.md:248 -msgid "\"Bad URLs: {:#?}\"" +#: src/other-resources.md:35 +msgid "A small selection of other guides and tutorial for Rust:" msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:1 -msgid "Concurrency Afternoon Exercise" +#: src/other-resources.md:37 +msgid "" +"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust " +"from the perspective of low-level C programmers." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:5 -msgid "([back to exercise](dining-philosophers-async.md))" +#: src/other-resources.md:39 +msgid "" +"[Rust for Embedded C Programmers](https://docs.opentitan.org/doc/ug/" +"rust_for_c/): covers Rust from the perspective of developers who write " +"firmware in C." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:32 +#: src/other-resources.md:42 msgid "" -"// Add a delay before picking the second fork to allow the execution\n" -" // to transfer to another task\n" +"[Rust for professionals](https://overexact.com/rust-for-professionals/): " +"covers the syntax of Rust using side-by-side comparisons with other " +"languages such as C, C++, Java, JavaScript, and Python." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:40 -msgid "// The locks are dropped here\n" +#: src/other-resources.md:45 +msgid "" +"[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " +"you learn Rust." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:60 +#: src/other-resources.md:47 msgid "" -"// To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" +"[Ferrous Teaching Material](https://ferrous-systems.github.io/teaching-" +"material/index.html): a series of small presentations covering both basic " +"and advanced part of the Rust language. Other topics such as WebAssembly, " +"and async/await are also covered." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:74 -msgid "// tx is dropped here, so we don't need to explicitly drop it later\n" +#: src/other-resources.md:52 +msgid "" +"[Beginner's Series to Rust](https://docs.microsoft.com/en-us/shows/beginners-" +"series-to-rust/) and [Take your first steps with Rust](https://docs." +"microsoft.com/en-us/learn/paths/rust-first-steps/): two Rust guides aimed at " +"new developers. The first is a set of 35 videos and the second is a set of " +"11 modules which covers Rust syntax and basic constructs." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:90 -msgid "\"Here is a thought: {thought}\"" +#: src/other-resources.md:58 +msgid "" +"[Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial." +"github.io/too-many-lists/): in-depth exploration of Rust's memory management " +"rules, through implementing a few different types of list structures." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:97 -msgid "([back to exercise](chat-app.md))" -msgstr "([tilbage til øvelsen](chat-app.md))" - -#: src/exercises/concurrency/solutions-afternoon.md:99 -msgid "`src/bin/server.rs`:" -msgstr "`src/bin/server.rs`:" +#: src/other-resources.md:63 +msgid "" +"Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " +"for even more Rust books." +msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:117 -msgid "\"Welcome to chat! Type a message\"" +#: src/credits.md:3 +msgid "" +"The material here builds on top of the many great sources of Rust " +"documentation. See the page on [other resources](other-resources.md) for a " +"full list of useful resources." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:121 +#: src/credits.md:7 msgid "" -"// A continuous loop for concurrently performing two tasks: (1) receiving\n" -" // messages from `ws_stream` and broadcasting them, and (2) receiving\n" -" // messages on `bcast_rx` and sending them to the client.\n" +"The material of Comprehensive Rust is licensed under the terms of the Apache " +"2.0 license, please see [`LICENSE`](https://github.com/google/comprehensive-" +"rust/blob/main/LICENSE) for details." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:130 -msgid "\"From client {addr:?} {text:?}\"" +#: src/credits.md:12 +msgid "Rust by Example" +msgstr "Rust by Example" + +#: src/credits.md:14 +msgid "" +"Some examples and exercises have been copied and adapted from [Rust by " +"Example](https://doc.rust-lang.org/rust-by-example/). Please see the " +"`third_party/rust-by-example/` directory for details, including the license " +"terms." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:166 -msgid "`src/bin/client.rs`:" -msgstr "`src/bin/client.rs`:" +#: src/credits.md:19 +msgid "Rust on Exercism" +msgstr "Rust på Exercism" -#: src/exercises/concurrency/solutions-afternoon.md:185 -msgid "// Continuous loop for concurrently sending and receiving messages.\n" +#: src/credits.md:21 +msgid "" +"Some exercises have been copied and adapted from [Rust on Exercism](https://" +"exercism.org/tracks/rust). Please see the `third_party/rust-on-exercism/` " +"directory for details, including the license terms." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:192 -msgid "\"From server: {}\"" +#: src/credits.md:26 +msgid "CXX" +msgstr "CXX" + +#: src/credits.md:28 +msgid "" +"The [Interoperability with C++](android/interoperability/cpp.md) section " +"uses an image from [CXX](https://cxx.rs/). Please see the `third_party/cxx/` " +"directory for details, including the license terms." msgstr ""