msgid "" msgstr "" "Project-Id-Version: Comprehensive Rust 🦀\n" "POT-Creation-Date: 2023-09-27T15:38:22+02:00\n" "PO-Revision-Date: \n" "Last-Translator: \n" "Language-Team: \n" "Language: da\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: src/SUMMARY.md:4 src/index.md:1 msgid "Welcome to Comprehensive Rust 🦀" msgstr "Velkommen til Comprehensive Rust 🦀" #: src/SUMMARY.md:5 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 msgid "Course Structure" msgstr "Kursets struktur" #: src/SUMMARY.md:7 src/running-the-course/keyboard-shortcuts.md:1 msgid "Keyboard Shortcuts" msgstr "Genvejstaster" #: src/SUMMARY.md:8 src/running-the-course/translations.md:1 msgid "Translations" msgstr "Oversættelser" #: src/SUMMARY.md:9 src/cargo.md:1 msgid "Using Cargo" msgstr "Brug af Cargo" #: src/SUMMARY.md:10 msgid "Rust Ecosystem" msgstr "Rust's økosystem" #: src/SUMMARY.md:11 msgid "Code Samples" msgstr "Kodeeksempler" #: src/SUMMARY.md:12 msgid "Running Cargo Locally" msgstr "" #: src/SUMMARY.md:15 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 msgid "Welcome" msgstr "Velkommen" #: src/SUMMARY.md:20 src/welcome-day-1/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:22 src/hello-world/small-example.md:1 msgid "Small Example" msgstr "Et little eksempel" #: src/SUMMARY.md:23 src/why-rust.md:1 msgid "Why Rust?" msgstr "Hvorfor bruge Rust?" #: src/SUMMARY.md:24 src/why-rust/compile-time.md:1 msgid "Compile Time Guarantees" msgstr "Garantier før programudføring" #: src/SUMMARY.md:25 src/why-rust/runtime.md:1 msgid "Runtime Guarantees" msgstr "Garantier under programudføring" #: src/SUMMARY.md:26 src/why-rust/modern.md:1 msgid "Modern Features" msgstr "Moderne faciliteter" #: src/SUMMARY.md:27 src/basic-syntax.md:1 msgid "Basic Syntax" msgstr "Grundlæggende syntaks" #: src/SUMMARY.md:28 src/basic-syntax/scalar-types.md:1 msgid "Scalar Types" msgstr "Skalartyper" #: src/SUMMARY.md:29 src/basic-syntax/compound-types.md:1 msgid "Compound Types" msgstr "Sammensatte typer" #: src/SUMMARY.md:30 src/basic-syntax/references.md:1 msgid "References" msgstr "Referencer" #: src/SUMMARY.md:31 src/basic-syntax/references-dangling.md:1 msgid "Dangling References" msgstr "Hængende referencer" #: src/SUMMARY.md:32 src/basic-syntax/slices.md:1 msgid "Slices" msgstr "Arraysegmenter" #: src/SUMMARY.md:33 msgid "String vs str" msgstr "String og str" #: src/SUMMARY.md:34 src/basic-syntax/functions.md:1 msgid "Functions" msgstr "Funktioner" #: src/SUMMARY.md:35 src/basic-syntax/rustdoc.md:1 msgid "Rustdoc" 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:42 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:63 msgid "match expressions" msgstr "match udtryk" #: src/SUMMARY.md:65 src/SUMMARY.md:73 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" 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" 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:81 src/memory-management.md:1 msgid "Memory Management" msgstr "Håndtering af hukommelse" #: src/SUMMARY.md:82 msgid "Stack vs Heap" msgstr "Stak og heap" #: src/SUMMARY.md:83 msgid "Stack Memory" msgstr "Stakhukommelse" #: src/SUMMARY.md:84 src/memory-management/manual.md:1 msgid "Manual Memory Management" msgstr "Manuel hukommelseshåndtering" #: 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:86 msgid "Garbage Collection" msgstr "Automatisk hukommelseshåndtering" #: src/SUMMARY.md:87 msgid "Rust Memory Management" msgstr "Hukommelseshåndtering i Rust" #: src/SUMMARY.md:88 src/ownership.md:1 msgid "Ownership" msgstr "Ejerskab" #: src/SUMMARY.md:89 src/ownership/move-semantics.md:1 msgid "Move Semantics" msgstr "Overførselssemantik" #: 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:91 msgid "Double Frees in Modern C++" msgstr "Dobbeltfrigivelser i moderne C++" #: 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:93 src/ownership/copy-clone.md:1 msgid "Copying and Cloning" msgstr "Kopiering og kloning" #: src/SUMMARY.md:94 src/ownership/borrowing.md:1 msgid "Borrowing" msgstr "Lån af variabler" #: 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:96 src/ownership/lifetimes.md:1 msgid "Lifetimes" msgstr "Livstider" #: src/SUMMARY.md:97 src/ownership/lifetimes-function-calls.md:1 msgid "Lifetimes in Function Calls" msgstr "Livstider i funktionskald" #: src/SUMMARY.md:98 src/ownership/lifetimes-data-structures.md:1 msgid "Lifetimes in Data Structures" msgstr "Livstider i datastrukturer" #: src/SUMMARY.md:99 src/structs.md:1 msgid "Structs" msgstr "Strukturer" #: src/SUMMARY.md:100 src/structs/tuple-structs.md:1 msgid "Tuple Structs" msgstr "Tuple-strukturer" #: src/SUMMARY.md:101 src/structs/field-shorthand.md:1 msgid "Field Shorthand Syntax" msgstr "Forenklet strukturinitialisering" #: src/SUMMARY.md:103 src/methods/receiver.md:1 msgid "Method Receiver" msgstr "Modtager af funktionskald" #: 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:106 src/exercises/day-2/book-library.md:1 msgid "Storing Books" msgstr "Lagring af bøger" #: src/SUMMARY.md:107 src/exercises/day-2/health-statistics.md:1 #: src/exercises/day-2/solutions-morning.md:151 msgid "Health Statistics" msgstr "" #: src/SUMMARY.md:109 msgid "Day 2: Afternoon" msgstr "Dag 2: Eftermiddag" #: src/SUMMARY.md:111 src/std.md:1 msgid "Standard Library" msgstr "" #: src/SUMMARY.md:112 msgid "Option and Result" msgstr "" #: src/SUMMARY.md:113 src/std/string.md:1 msgid "String" msgstr "" #: src/SUMMARY.md:114 msgid "Vec" msgstr "" #: src/SUMMARY.md:115 msgid "HashMap" msgstr "" #: src/SUMMARY.md:116 msgid "Box" msgstr "" #: src/SUMMARY.md:117 msgid "Recursive Data Types" msgstr "" #: src/SUMMARY.md:118 src/std/box-niche.md:1 msgid "Niche Optimization" msgstr "" #: src/SUMMARY.md:119 msgid "Rc" msgstr "" #: src/SUMMARY.md:120 msgid "Cell/RefCell" msgstr "" #: src/SUMMARY.md:121 src/modules.md:1 msgid "Modules" msgstr "" #: src/SUMMARY.md:122 src/modules/visibility.md:1 msgid "Visibility" msgstr "" #: src/SUMMARY.md:123 src/modules/paths.md:1 msgid "Paths" msgstr "" #: src/SUMMARY.md:124 src/modules/filesystem.md:1 msgid "Filesystem Hierarchy" 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:130 msgid "Day 3: Morning" msgstr "" #: src/SUMMARY.md:135 src/generics.md:1 msgid "Generics" msgstr "" #: src/SUMMARY.md:136 src/generics/data-types.md:1 msgid "Generic Data Types" msgstr "" #: src/SUMMARY.md:137 src/generics/methods.md:1 msgid "Generic Methods" msgstr "" #: src/SUMMARY.md:138 src/generics/monomorphization.md:1 msgid "Monomorphization" msgstr "" #: src/SUMMARY.md:139 src/traits.md:1 msgid "Traits" msgstr "" #: src/SUMMARY.md:140 src/traits/trait-objects.md:1 msgid "Trait Objects" msgstr "" #: src/SUMMARY.md:141 src/traits/deriving-traits.md:1 msgid "Deriving Traits" msgstr "" #: src/SUMMARY.md:142 src/traits/default-methods.md:1 msgid "Default Methods" msgstr "" #: src/SUMMARY.md:143 src/traits/trait-bounds.md:1 msgid "Trait Bounds" msgstr "" #: src/SUMMARY.md:144 msgid "impl Trait" msgstr "" #: src/SUMMARY.md:145 src/traits/important-traits.md:1 msgid "Important Traits" msgstr "" #: src/SUMMARY.md:146 msgid "Iterator" msgstr "" #: src/SUMMARY.md:147 src/traits/from-iterator.md:1 msgid "FromIterator" msgstr "" #: src/SUMMARY.md:148 msgid "From and Into" msgstr "" #: src/SUMMARY.md:149 msgid "Read and Write" msgstr "" #: src/SUMMARY.md:150 msgid "Drop" msgstr "" #: src/SUMMARY.md:151 msgid "Default" msgstr "" #: src/SUMMARY.md:152 msgid "Operators: Add, Mul, ..." msgstr "" #: src/SUMMARY.md:153 msgid "Closures: Fn, FnMut, FnOnce" msgstr "" #: 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" 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" msgstr "" #: src/SUMMARY.md:160 src/error-handling.md:1 msgid "Error Handling" msgstr "" #: src/SUMMARY.md:161 src/error-handling/panics.md:1 msgid "Panics" msgstr "" #: src/SUMMARY.md:162 msgid "Catching Stack Unwinding" msgstr "" #: src/SUMMARY.md:163 msgid "Structured Error Handling" msgstr "" #: src/SUMMARY.md:164 msgid "Propagating Errors with ?" 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" msgstr "" #: src/SUMMARY.md:167 src/error-handling/deriving-error-enums.md:1 msgid "Deriving Error Enums" msgstr "" #: src/SUMMARY.md:168 src/error-handling/dynamic-errors.md:1 msgid "Dynamic Error Types" msgstr "" #: src/SUMMARY.md:169 src/error-handling/error-contexts.md:1 msgid "Adding Context to Errors" msgstr "" #: src/SUMMARY.md:170 src/testing.md:1 msgid "Testing" msgstr "" #: src/SUMMARY.md:171 src/testing/unit-tests.md:1 msgid "Unit Tests" msgstr "" #: src/SUMMARY.md:172 src/testing/test-modules.md:1 msgid "Test Modules" msgstr "" #: src/SUMMARY.md:173 src/testing/doc-tests.md:1 msgid "Documentation Tests" msgstr "" #: src/SUMMARY.md:174 src/testing/integration-tests.md:1 msgid "Integration Tests" msgstr "" #: src/SUMMARY.md:175 src/bare-metal/useful-crates.md:1 msgid "Useful crates" msgstr "" #: src/SUMMARY.md:176 src/unsafe.md:1 msgid "Unsafe Rust" msgstr "" #: src/SUMMARY.md:177 src/unsafe/raw-pointers.md:1 msgid "Dereferencing Raw Pointers" msgstr "" #: src/SUMMARY.md:178 src/unsafe/mutable-static-variables.md:1 msgid "Mutable Static Variables" msgstr "" #: src/SUMMARY.md:179 src/unsafe/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:183 src/unsafe/unsafe-traits.md:1 msgid "Implementing Unsafe Traits" msgstr "" #: 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" msgstr "" #: src/SUMMARY.md:188 src/SUMMARY.md:258 src/bare-metal/android.md:1 msgid "Android" msgstr "Android" #: src/SUMMARY.md:193 src/android/setup.md:1 msgid "Setup" msgstr "" #: src/SUMMARY.md:194 src/android/build-rules.md:1 msgid "Build Rules" msgstr "" #: src/SUMMARY.md:195 msgid "Binary" msgstr "" #: src/SUMMARY.md:196 msgid "Library" msgstr "" #: src/SUMMARY.md:197 src/android/aidl.md:1 msgid "AIDL" msgstr "" #: src/SUMMARY.md:198 msgid "Interface" msgstr "" #: src/SUMMARY.md:199 msgid "Implementation" msgstr "" #: src/SUMMARY.md:200 msgid "Server" msgstr "" #: src/SUMMARY.md:201 src/android/aidl/deploy.md:1 msgid "Deploy" msgstr "" #: src/SUMMARY.md:202 msgid "Client" msgstr "" #: src/SUMMARY.md:203 src/android/aidl/changing.md:1 msgid "Changing API" msgstr "" #: src/SUMMARY.md:204 src/SUMMARY.md:248 src/android/logging.md:1 #: src/bare-metal/aps/logging.md:1 msgid "Logging" msgstr "" #: src/SUMMARY.md:205 src/android/interoperability.md:1 msgid "Interoperability" msgstr "" #: src/SUMMARY.md:206 msgid "With C" msgstr "" #: src/SUMMARY.md:207 msgid "Calling C with Bindgen" msgstr "" #: src/SUMMARY.md:208 msgid "Calling Rust from C" msgstr "" #: src/SUMMARY.md:209 src/android/interoperability/cpp.md:1 msgid "With C++" msgstr "" #: src/SUMMARY.md:210 msgid "With Java" msgstr "" #: src/SUMMARY.md:214 msgid "Bare Metal: Morning" msgstr "Rå jern: Formiddag" #: src/SUMMARY.md:219 msgid "no_std" msgstr "no_std" #: src/SUMMARY.md:220 msgid "A Minimal Example" msgstr "Et minimalt eksempel" #: src/SUMMARY.md:221 msgid "alloc" msgstr "alloc" #: src/SUMMARY.md:222 src/bare-metal/microcontrollers.md:1 msgid "Microcontrollers" msgstr "" #: src/SUMMARY.md:223 src/bare-metal/microcontrollers/mmio.md:1 msgid "Raw MMIO" msgstr "Rå MMIO" #: src/SUMMARY.md:224 msgid "PACs" msgstr "PAC'er" #: src/SUMMARY.md:225 msgid "HAL Crates" msgstr "" #: src/SUMMARY.md:226 msgid "Board Support Crates" msgstr "" #: src/SUMMARY.md:227 msgid "The Type State Pattern" msgstr "" #: src/SUMMARY.md:228 msgid "embedded-hal" msgstr "embedded-hal" #: src/SUMMARY.md:229 msgid "probe-rs, cargo-embed" msgstr "probe-rs, cargo-embed" #: src/SUMMARY.md:230 src/bare-metal/microcontrollers/debugging.md:1 msgid "Debugging" msgstr "Fejlfinding" #: src/SUMMARY.md:231 src/SUMMARY.md:251 msgid "Other Projects" msgstr "Andre projekter" #: src/SUMMARY.md:233 src/exercises/bare-metal/compass.md:1 #: src/exercises/bare-metal/solutions-morning.md:3 msgid "Compass" msgstr "Kompas" #: src/SUMMARY.md:235 msgid "Bare Metal: Afternoon" msgstr "Rå jern: Eftermiddag" #: src/SUMMARY.md:237 msgid "Application Processors" msgstr "" #: src/SUMMARY.md:238 src/bare-metal/aps/entry-point.md:1 msgid "Getting Ready to Rust" msgstr "" #: src/SUMMARY.md:239 msgid "Inline Assembly" msgstr "" #: src/SUMMARY.md:240 msgid "MMIO" msgstr "MMIO" #: src/SUMMARY.md:241 msgid "Let's Write a UART Driver" msgstr "" #: src/SUMMARY.md:242 msgid "More Traits" msgstr "" #: src/SUMMARY.md:243 msgid "A Better UART Driver" msgstr "" #: src/SUMMARY.md:244 src/bare-metal/aps/better-uart/bitflags.md:1 msgid "Bitflags" msgstr "Bitflag" #: src/SUMMARY.md:245 msgid "Multiple Registers" msgstr "" #: src/SUMMARY.md:246 src/bare-metal/aps/better-uart/driver.md:1 msgid "Driver" msgstr "Driver" #: src/SUMMARY.md:247 src/SUMMARY.md:249 msgid "Using It" msgstr "Anvendelse" #: src/SUMMARY.md:250 src/bare-metal/aps/exceptions.md:1 msgid "Exceptions" msgstr "Undtagelser" #: src/SUMMARY.md:252 msgid "Useful Crates" msgstr "" #: src/SUMMARY.md:253 msgid "zerocopy" msgstr "zerocopy" #: src/SUMMARY.md:254 msgid "aarch64-paging" msgstr "aarch64-paging" #: src/SUMMARY.md:255 msgid "buddy_system_allocator" msgstr "buddy_system_allocator" #: src/SUMMARY.md:256 msgid "tinyvec" msgstr "tinyvec" #: src/SUMMARY.md:257 msgid "spin" msgstr "spin" #: src/SUMMARY.md:259 src/bare-metal/android/vmbase.md:1 msgid "vmbase" msgstr "vmbase" #: src/SUMMARY.md:261 msgid "RTC Driver" msgstr "" #: src/SUMMARY.md:264 msgid "Concurrency: Morning" msgstr "" #: src/SUMMARY.md:269 src/concurrency/threads.md:1 msgid "Threads" msgstr "Tråde" #: src/SUMMARY.md:270 src/concurrency/scoped-threads.md:1 msgid "Scoped Threads" msgstr "Tråde med virkefelt" #: src/SUMMARY.md:271 src/concurrency/channels.md:1 msgid "Channels" msgstr "Kanaler" #: src/SUMMARY.md:272 src/concurrency/channels/unbounded.md:1 msgid "Unbounded Channels" msgstr "Ubegrænsede kanaler" #: src/SUMMARY.md:273 src/concurrency/channels/bounded.md:1 msgid "Bounded Channels" msgstr "Begrænsede kanaler" #: src/SUMMARY.md:274 msgid "Send and Sync" msgstr "Send og Sync" #: src/SUMMARY.md:274 msgid "Send" msgstr "Send" #: src/SUMMARY.md:274 msgid "Sync" msgstr "Sync" #: src/SUMMARY.md:277 src/concurrency/send-sync/examples.md:1 msgid "Examples" msgstr "Eksempler" #: src/SUMMARY.md:278 src/concurrency/shared_state.md:1 msgid "Shared State" msgstr "Delt tilstand" #: src/SUMMARY.md:279 msgid "Arc" msgstr "Arc" #: src/SUMMARY.md:280 msgid "Mutex" msgstr "Mutex" #: src/SUMMARY.md:283 src/SUMMARY.md:304 #: 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 msgid "Multi-threaded Link Checker" msgstr "Flertrådet linktjekker" #: src/SUMMARY.md:286 msgid "Concurrency: Afternoon" msgstr "Concurrency: Eftermiddag" #: src/SUMMARY.md:288 msgid "Async Basics" msgstr "Grundlæggende Async" #: src/SUMMARY.md:289 msgid "async/await" msgstr "async/await" #: src/SUMMARY.md:290 src/async/futures.md:1 msgid "Futures" msgstr "Fremtidige resultater (eng. Futures)" #: src/SUMMARY.md:291 src/async/runtimes.md:1 msgid "Runtimes" msgstr "" #: src/SUMMARY.md:292 src/async/runtimes/tokio.md:1 msgid "Tokio" msgstr "Tokio" #: src/SUMMARY.md:293 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 msgid "Async Channels" msgstr "Asynkrone kanaler" #: src/SUMMARY.md:296 src/async/control-flow/join.md:1 msgid "Join" msgstr "Join" #: src/SUMMARY.md:297 src/async/control-flow/select.md:1 msgid "Select" msgstr "Select" #: src/SUMMARY.md:298 msgid "Pitfalls" msgstr "Faldgruber" #: src/SUMMARY.md:299 msgid "Blocking the Executor" msgstr "" #: src/SUMMARY.md:300 src/async/pitfalls/pin.md:1 msgid "Pin" msgstr "Pin" #: src/SUMMARY.md:301 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 msgid "Cancellation" msgstr "Annulering" #: src/SUMMARY.md:305 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 msgid "Final Words" msgstr "Afsluttende bemærkninger" #: src/SUMMARY.md:312 src/thanks.md:1 msgid "Thanks!" msgstr "Tak!" #: src/SUMMARY.md:313 msgid "Other Resources" msgstr "Andre resourcer" #: src/SUMMARY.md:314 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/" "google/comprehensive-rust/build.yml?style=flat-square)](https://github.com/" "google/comprehensive-rust/actions/workflows/build.yml?query=branch%3Amain) [!" "[GitHub contributors](https://img.shields.io/github/contributors/google/" "comprehensive-rust?style=flat-square)](https://github.com/google/" "comprehensive-rust/graphs/contributors) [![GitHub stars](https://img.shields." "io/github/stars/google/comprehensive-rust?style=flat-square)](https://github." "com/google/comprehensive-rust/stargazers)" msgstr "" "[![Bygge-arbejdsgang](https://img.shields.io/github/actions/workflow/status/" "google/comprehensive-rust/build.yml?style=flat-square)](https://github.com/" "google/comprehensive-rust/actions/workflows/build.yml?query=branch%3Amain) [!" "[GitHub-bidragsydere](https://img.shields.io/github/contributors/google/" "comprehensive-rust?style=flat-square)](https://github.com/google/" "comprehensive-rust/graphs/contributors) [![GitHub-stjerner](https://img." "shields.io/github/stars/google/comprehensive-rust?style=flat-square)]" "(https://github.com/google/comprehensive-rust/stargazers)" #: src/index.md:7 msgid "" "This is a free Rust course developed by the Android team at Google. The " "course covers the full spectrum of Rust, from basic syntax to advanced " "topics like generics and error handling." msgstr "" "Dette er et gratis Rust-kursus udviklet af Android-teamet. Kurset dækker " "hele spektret af Rust, fra grundlæggende syntaks til avancerede emner som " "generiske typer og fejlhåndtering." #: src/index.md:11 msgid "" "The latest version of the course can be found at . If you are reading somewhere else, please check there " "for updates." msgstr "" #: src/index.md:15 msgid "" "The goal of the course is to teach you Rust. We assume you don't know " "anything about Rust and hope to:" msgstr "" "Målet med kurset er at lære dig Rust. Vi antager, at du ikke ved noget om " "Rust og håber at:" #: src/index.md:18 msgid "Give you a comprehensive understanding of the Rust syntax and language." msgstr "Give dig en omfattende forståelse af Rust-syntaksen og sproget." #: src/index.md:19 msgid "Enable you to modify existing programs and write new programs in Rust." msgstr "" "Gøre det muligt for dig at ændre eksisterende programmer og skrive nye " "programmer i Rust." #: src/index.md:20 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." msgstr "" "Vi kalder de første tre kursusdage Grundlæggende Rust (_Rust Fundamentals_)." #: src/index.md:24 msgid "" "Building on this, you're invited to dive into one or more specialized topics:" msgstr "" "Efterfølgende er du inviteret til at dykke ned i et eller flere " "specialiserede emner:" #: src/index.md:26 msgid "" "[Android](android.md): a half-day course on using Rust for Android platform " "development (AOSP). This includes interoperability with C, C++, and Java." 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:28 msgid "" "[Bare-metal](bare-metal.md): a whole-day class on using Rust for bare-metal " "(embedded) development. Both microcontrollers and application processors are " "covered." msgstr "" "[Rå jern](bare-metal.md): en fuld kursusdag om at bruge Rust til udvikling " "på det rå jern og indlejrede (_bare metal and embedded_) systemer. Dækker " "både mikroprocessorer og applikationsprocessorer." #: src/index.md:31 msgid "" "[Concurrency](concurrency.md): a whole-day class on concurrency in Rust. We " "cover both classical concurrency (preemptively scheduling using threads and " "mutexes) and async/await concurrency (cooperative multitasking using " "futures)." msgstr "" "[Samtidighed](concurrency.md): en hel kursusdag om samtidighed " "(_concurrency_) i Rust. Vi dækker både klassisk samtidighed (tidsdelt " "multitasking ved hjælp af tråde og mutexes) og async/await samtidighed " "(kooperativ multitasking ved hjælp af _futures_)." #: src/index.md:37 msgid "Non-Goals" msgstr "Ting som ikke dækkes" #: src/index.md:39 msgid "" "Rust is a large language and we won't be able to cover all of it in a few " "days. Some non-goals of this course are:" msgstr "" "Rust 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 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]" "(https://doc.rust-lang.org/rust-by-example/macros.html) instead." msgstr "" "At lære hvordan man udvikler makroer: se venligst [Kapitel 19.5 i Rust-bogen]" "(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 msgid "Assumptions" msgstr "Antagelser" #: src/index.md:48 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 " "C++ to better explain or contrast the Rust approach." msgstr "" "Kurset antager at du allerede ved hvordan man programerer. Rust er et " "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 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." 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 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 " "should cover as well as answers to typical questions which come up in class." msgstr "" "Dette er et eksempel på en _note_. Vi vil bruge disse til at tilføje " "yderligere information til siderne. Dette kan være nøglepunkter som " "instruktøren skal dække såvel som svar på typiske spørgsmål som bliver " "stillet i klassen." #: src/running-the-course.md:3 src/running-the-course/course-structure.md:3 msgid "This page is for the course instructor." msgstr "Denne side er for kursuslederen." #: src/running-the-course.md:5 msgid "" "Here is a bit of background information about how we've been running the " "course internally at Google." 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." msgstr "" #: src/running-the-course.md:16 msgid "Before you run the course, you will want to:" msgstr "" #: src/running-the-course.md:18 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 " "speaker notes!). When presenting, you should make sure to open the speaker " "notes in a popup (click the link with a little arrow next to \"Speaker " "Notes\"). This way you have a clean screen to present to the class." msgstr "" #: src/running-the-course.md:24 msgid "" "Decide on the dates. Since the course takes at least three full days, we " "recommend that you schedule the days over two weeks. Course participants " "have said that they find it helpful to have a gap in the course since it " "helps them process all the information we give them." msgstr "" #: src/running-the-course.md:29 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 " "asking questions --- it's also small enough that one instructor will have " "time to answer the questions. Make sure the room has _desks_ for yourself " "and for the students: you will all need to be able to sit and work with your " "laptops. In particular, you will be doing a lot of live-coding as an " "instructor, so a lectern won't be very helpful for you." msgstr "" #: src/running-the-course.md:37 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 " "laptop (see the [installation instructions](https://github.com/google/" "comprehensive-rust#building)). This ensures optimal performance with no lag " "as you change pages. Using your laptop will also allow you to fix typos as " "you or the course participants spot them." msgstr "" #: src/running-the-course.md:43 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 " "afternoon (including time to review the solutions). Make sure to ask people " "if they're stuck or if there is anything you can help with. When you see " "that several people have the same problem, call it out to the class and " "offer a solution, e.g., by showing people where to find the relevant " "information in the standard library." msgstr "" #: src/running-the-course.md:51 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 msgid "" "Please [provide feedback](https://github.com/google/comprehensive-rust/" "discussions/86) afterwards so that we can keep improving the course. We " "would love to hear what worked well for you and what can be made better. " "Your students are also very welcome to [send us feedback](https://github.com/" "google/comprehensive-rust/discussions/100)!" msgstr "" #: src/running-the-course/course-structure.md:5 msgid "Rust Fundamentals" 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:" msgstr "" #: src/running-the-course/course-structure.md:10 msgid "Day 1: Basic Rust, syntax, control flow, creating and consuming values." msgstr "" #: src/running-the-course/course-structure.md:11 msgid "" "Day 2: Memory management, ownership, compound data types, and the standard " "library." msgstr "" #: src/running-the-course/course-structure.md:12 msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." msgstr "" #: src/running-the-course/course-structure.md:14 msgid "Deep Dives" 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:" 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: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." 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/`." 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." msgstr "" #: src/running-the-course/course-structure.md:37 msgid "Bare-Metal Rust" msgstr "Bare-Metal Rust" #: 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." 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)." msgstr "" #: src/running-the-course/course-structure.md:48 msgid "Concurrency in Rust" msgstr "Samtidighed i Rust" #: 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." 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:" msgstr "" #: src/running-the-course/course-structure.md:64 msgid "Format" 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!" 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" #: src/running-the-course/keyboard-shortcuts.md:7 msgid ": Execute the code sample that has focus." msgstr "" #: src/running-the-course/keyboard-shortcuts.md:8 msgid "s" msgstr "" #: src/running-the-course/keyboard-shortcuts.md:8 msgid ": Activate the search bar." msgstr "" #: src/running-the-course/translations.md:3 msgid "" "The course has been translated into other languages by a set of wonderful " "volunteers:" msgstr "" #: src/running-the-course/translations.md:6 msgid "" "[Brazilian Portuguese](https://google.github.io/comprehensive-rust/pt-BR/) " "by [@rastringer](https://github.com/rastringer), [@hugojacob](https://github." "com/hugojacob), [@joaovicmendes](https://github.com/joaovicmendes), and " "[@henrif75](https://github.com/henrif75)." msgstr "" #: src/running-the-course/translations.md:7 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 msgid "" "[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid]" "(https://github.com/deavid)." msgstr "" #: src/running-the-course/translations.md:10 msgid "" "Use the language picker in the top-right corner to switch between languages." msgstr "" #: src/running-the-course/translations.md:12 msgid "Incomplete Translations" msgstr "Ufuldstændige oversættelser" #: src/running-the-course/translations.md:14 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 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]" "(https://github.com/KookaS) and [@vcaen](https://github.com/vcaen)." msgstr "" #: src/running-the-course/translations.md:21 msgid "" "[German](https://google.github.io/comprehensive-rust/de/) by [@Throvn]" "(https://github.com/Throvn) and [@ronaldfw](https://github.com/ronaldfw)." msgstr "" #: src/running-the-course/translations.md:22 msgid "" "[Japanese](https://google.github.io/comprehensive-rust/ja/) by [@CoinEZ-JPN]" "(https://github.com/CoinEZ) and [@momotaro1105](https://github.com/" "momotaro1105)." msgstr "" #: src/running-the-course/translations.md:24 msgid "" "If you want to help with this effort, please see [our instructions](https://" "github.com/google/comprehensive-rust/blob/main/TRANSLATIONS.md) for how to " "get going. Translations are coordinated on the [issue tracker](https://" "github.com/google/comprehensive-rust/issues/282)." msgstr "" #: src/cargo.md:3 msgid "" "When you start reading about Rust, you will soon meet [Cargo](https://doc." "rust-lang.org/cargo/), the standard tool used in the Rust ecosystem to build " "and run Rust applications. Here we want to give a brief overview of what " "Cargo is and how it fits into the wider ecosystem and how it fits into this " "training." msgstr "" #: src/cargo.md:8 msgid "Installation" msgstr "Installation" #: src/cargo.md:10 msgid "**Please follow the instructions on .**" msgstr "" #: src/cargo.md:12 msgid "" "This will give you the Cargo build tool (`cargo`) and the Rust compiler " "(`rustc`). You will also get `rustup`, a command line utility that you can " "use to install to different compiler versions." msgstr "" #: src/cargo.md:14 msgid "" "After installing Rust, you should configure your editor or IDE to work with " "Rust. Most editors do this by talking to [rust-analyzer](https://rust-" "analyzer.github.io/), which provides auto-completion and jump-to-definition " "functionality for [VS Code](https://code.visualstudio.com/), [Emacs](https://" "rust-analyzer.github.io/manual.html#emacs), [Vim/Neovim](https://rust-" "analyzer.github.io/manual.html#vimneovim), and many others. There is also a " "different IDE available called [RustRover](https://www.jetbrains.com/rust/)." msgstr "" #: src/cargo.md:18 msgid "" "On Debian/Ubuntu, you can also install Cargo, the Rust source and the [Rust " "formatter](https://github.com/rust-lang/rustfmt) via `apt`. However, this " "gets you an outdated rust version and may lead to unexpected behavior. The " "command would be:" msgstr "" #: src/cargo/rust-ecosystem.md:1 msgid "The Rust Ecosystem" msgstr "" #: src/cargo/rust-ecosystem.md:3 msgid "" "The Rust ecosystem consists of a number of tools, of which the main ones are:" msgstr "" #: src/cargo/rust-ecosystem.md:5 msgid "" "`rustc`: the Rust compiler which turns `.rs` files into binaries and other " "intermediate formats." msgstr "" #: src/cargo/rust-ecosystem.md:8 msgid "" "`cargo`: the Rust dependency manager and build tool. Cargo knows how to " "download dependencies, usually hosted on , and it will " "pass them to `rustc` when building your project. Cargo also comes with a " "built-in test runner which is used to execute unit tests." 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 " "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/concurrency/threads.md:30 src/async/async-await.md:25 msgid "Key points:" msgstr "Nøglepunkter:" #: src/cargo/rust-ecosystem.md:23 msgid "" "Rust has a rapid release schedule with a new release coming out every six " "weeks. New releases maintain backwards compatibility with old releases --- " "plus they enable new functionality." msgstr "" #: src/cargo/rust-ecosystem.md:27 msgid "" "There are three release channels: \"stable\", \"beta\", and \"nightly\"." msgstr "" #: src/cargo/rust-ecosystem.md:29 msgid "" "New features are being tested on \"nightly\", \"beta\" is what becomes " "\"stable\" every six weeks." msgstr "" #: src/cargo/rust-ecosystem.md:32 msgid "" "Dependencies can also be resolved from alternative [registries](https://doc." "rust-lang.org/cargo/reference/registries.html), git, folders, and more." msgstr "" #: src/cargo/rust-ecosystem.md:34 msgid "" "Rust also has [editions](https://doc.rust-lang.org/edition-guide/): the " "current edition is Rust 2021. Previous editions were Rust 2015 and Rust 2018." msgstr "" #: src/cargo/rust-ecosystem.md:37 msgid "" "The editions are allowed to make backwards incompatible changes to the " "language." msgstr "" #: src/cargo/rust-ecosystem.md:40 msgid "" "To prevent breaking code, editions are opt-in: you select the edition for " "your crate via the `Cargo.toml` file." msgstr "" #: src/cargo/rust-ecosystem.md:43 msgid "" "To avoid splitting the ecosystem, Rust compilers can mix code written for " "different editions." msgstr "" #: src/cargo/rust-ecosystem.md:46 msgid "" "Mention that it is quite rare to ever use the compiler directly not through " "`cargo` (most users never do)." msgstr "" #: src/cargo/rust-ecosystem.md:48 msgid "" "It might be worth alluding that Cargo itself is an extremely powerful and " "comprehensive tool. It is capable of many advanced features including but " "not limited to: " msgstr "" #: src/cargo/rust-ecosystem.md:49 msgid "Project/package structure" msgstr "" #: src/cargo/rust-ecosystem.md:50 msgid "[workspaces](https://doc.rust-lang.org/cargo/reference/workspaces.html)" msgstr "" #: src/cargo/rust-ecosystem.md:51 msgid "Dev Dependencies and Runtime Dependency management/caching" msgstr "" #: src/cargo/rust-ecosystem.md:52 msgid "" "[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts." "html)" msgstr "" #: src/cargo/rust-ecosystem.md:53 msgid "" "[global installation](https://doc.rust-lang.org/cargo/commands/cargo-install." "html)" msgstr "" #: src/cargo/rust-ecosystem.md:54 msgid "" "It is also extensible with sub command plugins as well (such as [cargo " "clippy](https://github.com/rust-lang/rust-clippy))." msgstr "" #: src/cargo/rust-ecosystem.md:55 msgid "" "Read more from the [official Cargo Book](https://doc.rust-lang.org/cargo/)" msgstr "" #: src/cargo/code-samples.md:1 msgid "Code Samples in This Training" msgstr "" #: src/cargo/code-samples.md:3 msgid "" "For this training, we will mostly explore the Rust language through examples " "which can be executed through your browser. This makes the setup much easier " "and ensures a consistent experience for everyone." msgstr "" #: src/cargo/code-samples.md:7 msgid "" "Installing Cargo is still encouraged: it will make it easier for you to do " "the exercises. On the last day, we will do a larger exercise which shows you " "how to work with dependencies and for that you need Cargo." msgstr "" #: src/cargo/code-samples.md:11 msgid "The code blocks in this course are fully interactive:" msgstr "" #: src/cargo/code-samples.md:15 src/cargo/running-locally.md:45 msgid "\"Edit me!\"" msgstr "\"Rediger mig!\"" #: src/cargo/code-samples.md:19 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." msgstr "for at afvikle koden når tekstboksen er i fokus." #: src/cargo/code-samples.md:24 msgid "" "Most code samples are editable like shown above. A few code samples are not " "editable for various reasons:" msgstr "" #: src/cargo/code-samples.md:27 msgid "" "The embedded playgrounds cannot execute unit tests. Copy-paste the code and " "open it in the real Playground to demonstrate unit tests." msgstr "" #: src/cargo/code-samples.md:30 msgid "" "The embedded playgrounds lose their state the moment you navigate away from " "the page! This is the reason that the students should solve the exercises " "using a local Rust installation or via the Playground." msgstr "" #: src/cargo/running-locally.md:1 msgid "Running Code Locally with Cargo" msgstr "" #: src/cargo/running-locally.md:3 msgid "" "If you want to experiment with the code on your own system, then you will " "need to first install Rust. Do this by following the [instructions in the " "Rust Book](https://doc.rust-lang.org/book/ch01-01-installation.html). This " "should give you a working `rustc` and `cargo`. At the time of writing, the " "latest stable Rust release has these version numbers:" msgstr "" #: src/cargo/running-locally.md:15 msgid "" "You can use any later version too since Rust maintains backwards " "compatibility." msgstr "" #: src/cargo/running-locally.md:17 msgid "" "With this in place, follow these steps to build a Rust binary from one of " "the examples in this training:" msgstr "" #: src/cargo/running-locally.md:20 msgid "Click the \"Copy to clipboard\" button on the example you want to copy." msgstr "" #: src/cargo/running-locally.md:22 msgid "" "Use `cargo new exercise` to create a new `exercise/` directory for your code:" msgstr "" #: src/cargo/running-locally.md:29 msgid "" "Navigate into `exercise/` and use `cargo run` to build and run your binary:" msgstr "" #: src/cargo/running-locally.md:40 msgid "" "Replace the boiler-plate code in `src/main.rs` with your own code. For " "example, using the example on the previous page, make `src/main.rs` look like" msgstr "" #: src/cargo/running-locally.md:49 msgid "Use `cargo run` to build and run your updated binary:" msgstr "" #: src/cargo/running-locally.md:59 msgid "" "Use `cargo check` to quickly check your project for errors, use `cargo " "build` to compile it without running it. You will find the output in `target/" "debug/` for a normal debug build. Use `cargo build --release` to produce an " "optimized release build in `target/release/`." msgstr "" #: src/cargo/running-locally.md:64 msgid "" "You can add dependencies for your project by editing `Cargo.toml`. When you " "run `cargo` commands, it will automatically download and compile missing " "dependencies for you." msgstr "" #: src/cargo/running-locally.md:72 msgid "" "Try to encourage the class participants to install Cargo and use a local " "editor. It will make their life easier since they will have a normal " "development environment." msgstr "" #: src/welcome-day-1.md:1 msgid "Welcome to Day 1" msgstr "Velkommen til Dag 1" #: src/welcome-day-1.md:3 msgid "" "This is the first day of Rust Fundamentals. We will cover a lot of ground " "today:" msgstr "" "Dette er den første dag af Rust Fundamentals. Vi kommer til at dække en " "masse terræn i dag:" #: src/welcome-day-1.md:6 msgid "" "Basic Rust syntax: variables, scalar and compound types, enums, structs, " "references, functions, and methods." msgstr "" #: src/welcome-day-1.md:9 msgid "" "Control flow constructs: `if`, `if let`, `while`, `while let`, `break`, and " "`continue`." msgstr "" #: src/welcome-day-1.md:12 msgid "Pattern matching: destructuring enums, structs, and arrays." msgstr "" #: src/welcome-day-1.md:16 msgid "Please remind the students that:" msgstr "" #: src/welcome-day-1.md:18 msgid "" "They should ask questions when they get them, don't save them to the end." msgstr "" #: src/welcome-day-1.md:19 msgid "" "The class is meant to be interactive and discussions are very much " "encouraged!" msgstr "" #: src/welcome-day-1.md:20 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." msgstr "" #: src/welcome-day-1.md:24 msgid "" "The questions will likely mean that we talk about things ahead of the slides." msgstr "" #: src/welcome-day-1.md:25 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 msgid "" "The idea for the first day is to show _just enough_ of Rust to be able to " "speak about the famous borrow checker. The way Rust handles memory is a " "major feature and we should show students this right away." msgstr "" #: src/welcome-day-1.md:33 msgid "" "If you're teaching this in a classroom, this is a good place to go over the " "schedule. We suggest splitting the day into two parts (following the slides):" msgstr "" #: src/welcome-day-1.md:36 msgid "Morning: 9:00 to 12:00," msgstr "" #: src/welcome-day-1.md:37 msgid "Afternoon: 13:00 to 16:00." 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!" msgstr "" #: src/welcome-day-1/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 msgid "Rust is a statically compiled language in a similar role as C++" msgstr "" #: src/welcome-day-1/what-is-rust.md:6 msgid "`rustc` uses LLVM as its backend." msgstr "" #: src/welcome-day-1/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 msgid "x86, ARM, WebAssembly, ..." msgstr "" #: src/welcome-day-1/what-is-rust.md:10 msgid "Linux, Mac, Windows, ..." msgstr "" #: src/welcome-day-1/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 msgid "firmware and boot loaders," msgstr "" #: src/welcome-day-1/what-is-rust.md:13 msgid "smart displays," msgstr "" #: src/welcome-day-1/what-is-rust.md:14 msgid "mobile phones," msgstr "" #: src/welcome-day-1/what-is-rust.md:15 msgid "desktops," msgstr "" #: src/welcome-day-1/what-is-rust.md:16 msgid "servers." msgstr "" #: src/welcome-day-1/what-is-rust.md:21 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 msgid "High flexibility." msgstr "" #: src/welcome-day-1/what-is-rust.md:24 msgid "High level of control." msgstr "" #: src/welcome-day-1/what-is-rust.md:25 msgid "" "Can be scaled down to very constrained devices such as microcontrollers." msgstr "" #: src/welcome-day-1/what-is-rust.md:26 msgid "Has no runtime or garbage collection." msgstr "" #: src/welcome-day-1/what-is-rust.md:27 msgid "Focuses on reliability and safety without sacrificing performance." msgstr "" #: src/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 msgid "\"Hello 🌍!\"" msgstr "\"Hallo 🌍!\"" #: src/hello-world.md:12 msgid "What you see:" msgstr "Hvad du ser:" #: src/hello-world.md:14 msgid "Functions are introduced with `fn`." msgstr "" #: src/hello-world.md:15 msgid "Blocks are delimited by curly braces like in C and C++." msgstr "" #: src/hello-world.md:16 msgid "The `main` function is the entry point of the program." msgstr "" #: src/hello-world.md:17 msgid "Rust has hygienic macros, `println!` is an example of this." msgstr "" #: src/hello-world.md:18 msgid "Rust strings are UTF-8 encoded and can contain any Unicode character." msgstr "" #: src/hello-world.md:22 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 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 msgid "Rust is modern with full support for things like Unicode." msgstr "" #: src/hello-world.md:33 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 msgid "" "Macros being 'hygienic' means they don't accidentally capture identifiers " "from the scope they are used in. Rust macros are actually only [partially " "hygienic](https://veykril.github.io/tlborm/decl-macros/minutiae/hygiene." "html)." msgstr "" #: src/hello-world.md:40 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, " "while it is not a functional language, it includes a range of [functional " "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/small-example.md:6 msgid "// Program entry point\n" msgstr "" #: src/hello-world/small-example.md:7 msgid "// Mutable variable binding\n" msgstr "" #: src/hello-world/small-example.md:8 src/traits/impl-trait.md:15 msgid "\"{x}\"" msgstr "\"{x}\"" #: src/hello-world/small-example.md:8 msgid "// Macro for printing, like printf\n" msgstr "" #: src/hello-world/small-example.md:9 msgid "// No parenthesis around expression\n" msgstr "" #: src/hello-world/small-example.md:10 msgid "// Math like in other languages\n" msgstr "" #: src/hello-world/small-example.md:15 msgid "\" -> {x}\"" msgstr "\" -> {x}\"" #: src/hello-world/small-example.md:23 msgid "" "The code implements the Collatz conjecture: it is believed that the loop " "will always end, but this is not yet proved. Edit the code and play with " "different inputs." msgstr "" #: src/hello-world/small-example.md:29 msgid "" "Explain that all variables are statically typed. Try removing `i32` to " "trigger type inference. Try with `i8` instead and trigger a runtime integer " "overflow." msgstr "" #: src/hello-world/small-example.md:32 msgid "Change `let mut x` to `let x`, discuss the compiler error." msgstr "" #: src/hello-world/small-example.md:34 msgid "" "Show how `print!` gives a compilation error if the arguments don't match the " "format string." msgstr "" #: src/hello-world/small-example.md:37 msgid "" "Show how you need to use `{}` as a placeholder if you want to print an " "expression which is more complex than just a single variable." msgstr "" #: src/hello-world/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." 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" msgstr "" #: src/why-rust.md:3 msgid "Some unique selling points of Rust:" msgstr "" #: src/why-rust.md:5 msgid "Compile time memory safety." msgstr "" #: src/why-rust.md:6 msgid "Lack of undefined runtime behavior." msgstr "" #: src/why-rust.md:7 msgid "Modern language features." msgstr "" #: src/why-rust.md:11 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 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 " "have the memory unsafety issues. In addition, you get a modern language with " "constructs like pattern matching and built-in dependency management." msgstr "" #: src/why-rust.md:19 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 " "addition you get fast and predictable performance like C and C++ (no garbage " "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:" msgstr "" #: src/why-rust/compile-time.md:5 msgid "No uninitialized variables." msgstr "" #: src/why-rust/compile-time.md:6 msgid "No memory leaks (_mostly_, see notes)." msgstr "" #: src/why-rust/compile-time.md:7 msgid "No double-frees." msgstr "" #: src/why-rust/compile-time.md:8 msgid "No use-after-free." msgstr "" #: src/why-rust/compile-time.md:9 msgid "No `NULL` pointers." msgstr "" #: src/why-rust/compile-time.md:10 msgid "No forgotten locked mutexes." msgstr "" #: src/why-rust/compile-time.md:11 msgid "No data races between threads." msgstr "" #: src/why-rust/compile-time.md:12 msgid "No iterator invalidation." msgstr "" #: src/why-rust/compile-time.md:16 msgid "" "It is possible to produce memory leaks in (safe) Rust. Some examples are:" msgstr "" #: src/why-rust/compile-time.md:19 msgid "" "You can use [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." "html#method.leak) to leak a pointer. A use of this could be to get runtime-" "initialized and runtime-sized static variables" msgstr "" #: src/why-rust/compile-time.md:21 msgid "" "You can use [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." "html) to make the compiler \"forget\" about a value (meaning the destructor " "is never run)." msgstr "" #: src/why-rust/compile-time.md:23 msgid "" "You can also accidentally create a [reference cycle](https://doc.rust-lang." "org/book/ch15-06-reference-cycles.html) with `Rc` or `Arc`." msgstr "" #: src/why-rust/compile-time.md:25 msgid "" "In fact, some will consider infinitely populating a collection a memory leak " "and Rust does not protect from those." msgstr "" #: src/why-rust/compile-time.md:28 msgid "" "For the purpose of this course, \"No memory leaks\" should be understood as " "\"Pretty much no _accidental_ memory leaks\"." msgstr "" #: src/why-rust/runtime.md:3 msgid "No undefined behavior at runtime:" msgstr "" #: src/why-rust/runtime.md:5 msgid "Array access is bounds checked." msgstr "" #: src/why-rust/runtime.md:6 msgid "Integer overflow is defined (panic or wrap-around)." msgstr "" #: src/why-rust/runtime.md:12 msgid "" "Integer overflow is defined via the [`overflow-checks`](https://doc.rust-" "lang.org/rustc/codegen-options/index.html#overflow-checks) compile-time " "flag. If enabled, the program will panic (a controlled crash of the " "program), otherwise you get wrap-around semantics. By default, you get " "panics in debug mode (`cargo build`) and wrap-around in release mode (`cargo " "build --release`)." msgstr "" #: 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." msgstr "" #: src/why-rust/modern.md:3 msgid "Rust is built with all the experience gained in the last decades." msgstr "" #: src/why-rust/modern.md:5 msgid "Language Features" msgstr "" #: src/why-rust/modern.md:7 msgid "Enums and pattern matching." msgstr "" #: src/why-rust/modern.md:8 msgid "Generics." msgstr "" #: src/why-rust/modern.md:9 msgid "No overhead FFI." msgstr "" #: src/why-rust/modern.md:10 msgid "Zero-cost abstractions." msgstr "" #: src/why-rust/modern.md:12 msgid "Tooling" msgstr "" #: src/why-rust/modern.md:14 msgid "Great compiler errors." msgstr "" #: src/why-rust/modern.md:15 msgid "Built-in dependency manager." msgstr "" #: src/why-rust/modern.md:16 msgid "Built-in support for testing." msgstr "" #: src/why-rust/modern.md:17 msgid "Excellent Language Server Protocol support." msgstr "" #: 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." 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`." 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." 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:" msgstr "" #: src/why-rust/modern.md:41 msgid "a random number generator, but see [rand](https://docs.rs/rand/)." msgstr "" #: src/why-rust/modern.md:42 msgid "support for SSL or TLS, but see [rusttls](https://docs.rs/rustls/)." msgstr "" #: src/why-rust/modern.md:43 msgid "support for JSON, but see [serde_json](https://docs.rs/serde_json/)." 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." 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." msgstr "" #: src/why-rust/modern.md:54 msgid "" "Discovering good third-party crates can be a problem. Sites like help with this by letting you compare health metrics for crates to " "find a good and trusted one." msgstr "" #: 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/basic-syntax.md:3 msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" msgstr "" #: src/basic-syntax.md:5 msgid "Blocks and scopes are delimited by curly braces." msgstr "" #: src/basic-syntax.md:6 msgid "" "Line comments are started with `//`, block comments are delimited by `/* ... " "*/`." msgstr "" #: src/basic-syntax.md:8 msgid "Keywords like `if` and `while` work the same." msgstr "" #: src/basic-syntax.md:9 msgid "Variable assignment is done with `=`, comparison is done with `==`." msgstr "" #: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 #: src/exercises/day-3/safe-ffi-wrapper.md:16 msgid "Types" msgstr "" #: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 msgid "Literals" msgstr "" #: src/basic-syntax/scalar-types.md:5 msgid "Signed integers" msgstr "" #: src/basic-syntax/scalar-types.md:5 msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" msgstr "" #: src/basic-syntax/scalar-types.md:5 msgid "`-10`, `0`, `1_000`, `123_i64`" msgstr "" #: src/basic-syntax/scalar-types.md:6 msgid "Unsigned integers" msgstr "" #: src/basic-syntax/scalar-types.md:6 msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" msgstr "" #: src/basic-syntax/scalar-types.md:6 msgid "`0`, `123`, `10_u16`" msgstr "" #: src/basic-syntax/scalar-types.md:7 msgid "Floating point numbers" msgstr "" #: src/basic-syntax/scalar-types.md:7 msgid "`f32`, `f64`" msgstr "" #: src/basic-syntax/scalar-types.md:7 msgid "`3.14`, `-10.0e20`, `2_f32`" msgstr "" #: src/basic-syntax/scalar-types.md:8 msgid "Strings" msgstr "" #: src/basic-syntax/scalar-types.md:8 msgid "`&str`" msgstr "" #: src/basic-syntax/scalar-types.md:8 msgid "`\"foo\"`, `\"two\\nlines\"`" msgstr "" #: src/basic-syntax/scalar-types.md:9 msgid "Unicode scalar values" msgstr "" #: src/basic-syntax/scalar-types.md:9 msgid "`char`" msgstr "" #: src/basic-syntax/scalar-types.md:9 msgid "`'a'`, `'α'`, `'∞'`" msgstr "" #: src/basic-syntax/scalar-types.md:10 msgid "Booleans" msgstr "" #: src/basic-syntax/scalar-types.md:10 msgid "`bool`" msgstr "" #: src/basic-syntax/scalar-types.md:10 msgid "`true`, `false`" msgstr "" #: src/basic-syntax/scalar-types.md:12 msgid "The types have widths as follows:" msgstr "" #: src/basic-syntax/scalar-types.md:14 msgid "`iN`, `uN`, and `fN` are _N_ bits wide," msgstr "" #: src/basic-syntax/scalar-types.md:15 msgid "`isize` and `usize` are the width of a pointer," msgstr "" #: src/basic-syntax/scalar-types.md:16 msgid "`char` is 32 bits wide," msgstr "" #: src/basic-syntax/scalar-types.md:17 msgid "`bool` is 8 bits wide." msgstr "" #: src/basic-syntax/scalar-types.md:21 msgid "There are a few syntaxes which are not shown above:" msgstr "" #: src/basic-syntax/scalar-types.md:23 msgid "" "Raw strings allow you to create a `&str` value with escapes disabled: " "`r\"\\n\" == \"\\\\n\"`. You can embed double-quotes by using an equal " "amount of `#` on either side of the quotes:" msgstr "" #: src/basic-syntax/scalar-types.md:35 msgid "Byte strings allow you to create a `&[u8]` value directly:" msgstr "" #: src/basic-syntax/scalar-types.md:45 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`." msgstr "" #: src/basic-syntax/compound-types.md:5 msgid "Arrays" msgstr "" #: src/basic-syntax/compound-types.md:5 msgid "`[T; N]`" msgstr "" #: src/basic-syntax/compound-types.md:5 msgid "`[20, 30, 40]`, `[0; 3]`" msgstr "" #: src/basic-syntax/compound-types.md:6 msgid "Tuples" msgstr "" #: src/basic-syntax/compound-types.md:6 msgid "`()`, `(T,)`, `(T1, T2)`, ..." msgstr "" #: src/basic-syntax/compound-types.md:6 msgid "`()`, `('x',)`, `('x', 1.2)`, ..." msgstr "" #: src/basic-syntax/compound-types.md:8 msgid "Array assignment and access:" msgstr "" #: src/basic-syntax/compound-types.md:19 msgid "Tuple assignment and access:" msgstr "" #: src/basic-syntax/compound-types.md:34 msgid "Arrays:" 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." msgstr "" #: src/basic-syntax/compound-types.md:40 msgid "We can use literals to assign values to arrays." msgstr "" #: src/basic-syntax/compound-types.md:42 msgid "" "In the main function, the print statement asks for the debug implementation " "with the `?` format parameter: `{}` gives the default output, `{:?}` gives " "the debug output. We could also have used `{a}` and `{a:?}` without " "specifying the value after the format string." msgstr "" #: src/basic-syntax/compound-types.md:47 msgid "" "Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " "easier to read." msgstr "" #: src/basic-syntax/compound-types.md:49 msgid "Tuples:" msgstr "" #: src/basic-syntax/compound-types.md:51 msgid "Like arrays, tuples have a fixed length." msgstr "" #: src/basic-syntax/compound-types.md:53 msgid "Tuples group together values of different types into a compound type." msgstr "" #: src/basic-syntax/compound-types.md:55 msgid "" "Fields of a tuple can be accessed by the period and the index of the value, " "e.g. `t.0`, `t.1`." msgstr "" #: src/basic-syntax/compound-types.md:57 msgid "" "The empty tuple `()` is also known as the \"unit type\". It is both a type, " "and the only valid value of that type - that is to say both the type and its " "value are expressed as `()`. It is used to indicate, for example, that a " "function or expression has no return value, as we'll see in a future slide. " msgstr "" #: src/basic-syntax/compound-types.md:61 msgid "" "You can think of it as `void` that can be familiar to you from other " "programming languages." msgstr "" #: src/basic-syntax/references.md:3 msgid "Like C++, Rust has references:" msgstr "" #: src/basic-syntax/references.md:15 msgid "Some notes:" msgstr "" #: src/basic-syntax/references.md:17 msgid "" "We must dereference `ref_x` when assigning to it, similar to C and C++ " "pointers." 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/basic-syntax/references.md:20 msgid "" "References that are declared as `mut` can be bound to different values over " "their lifetime." msgstr "" #: src/basic-syntax/references.md:26 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:" msgstr "" #: src/basic-syntax/references-dangling.md:17 msgid "A reference is said to \"borrow\" the value it refers to." msgstr "" #: src/basic-syntax/references-dangling.md:18 msgid "" "Rust is tracking the lifetimes of all references to ensure they live long " "enough." msgstr "" #: src/basic-syntax/references-dangling.md:20 msgid "We will talk more about borrowing when we get to ownership." msgstr "" #: src/basic-syntax/slices.md:3 msgid "A slice gives you a view into a larger collection:" msgstr "" #: src/basic-syntax/slices.md:17 msgid "Slices borrow data from the sliced type." msgstr "" #: src/basic-syntax/slices.md:18 msgid "Question: What happens if you modify `a[3]` right before printing `s`?" msgstr "" #: src/basic-syntax/slices.md:22 msgid "" "We create a slice by borrowing `a` and specifying the starting and ending " "indexes in brackets." msgstr "" #: src/basic-syntax/slices.md:24 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." msgstr "" #: src/basic-syntax/slices.md:26 msgid "" "The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " "identical." msgstr "" #: src/basic-syntax/slices.md:28 msgid "" "To easily create a slice of the full array, we can therefore use `&a[..]`." msgstr "" #: src/basic-syntax/slices.md:30 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." 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. " msgstr "" #: src/basic-syntax/slices.md:34 msgid "" "The question about modifying `a[3]` can spark an interesting discussion, but " "the answer is that for memory safety reasons you cannot do it through `a` at " "this point in the execution, but you can read the data from both `a` and `s` " "safely. It works before you created the slice, and again after the " "`println`, when the slice is no longer used. More details will be explained " "in the borrow checker section." msgstr "" #: src/basic-syntax/string-slices.md:1 msgid "`String` vs `str`" msgstr "" #: src/basic-syntax/string-slices.md:3 msgid "We can now understand the two string types in Rust:" 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/basic-syntax/string-slices.md:8 msgid "\"s1: {s1}\"" msgstr "\"s1: {s1}\"" #: 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/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/basic-syntax/string-slices.md:16 msgid "\"s3: {s3}\"" msgstr "\"s3: {s3}\"" #: src/basic-syntax/string-slices.md:20 msgid "Rust terminology:" msgstr "" #: src/basic-syntax/string-slices.md:22 msgid "`&str` an immutable reference to a string slice." msgstr "" #: src/basic-syntax/string-slices.md:23 msgid "`String` a mutable string buffer." msgstr "" #: src/basic-syntax/string-slices.md:27 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." 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." msgstr "" #: src/basic-syntax/string-slices.md:32 msgid "" "As with many other types `String::from()` creates a string from a string " "literal; `String::new()` creates a new empty string, to which string data " "can be added using the `push()` and `push_str()` methods." msgstr "" #: src/basic-syntax/string-slices.md:35 msgid "" "The `format!()` macro is a convenient way to generate an owned string from " "dynamic values. It accepts the same format specification as `println!()`." msgstr "" #: src/basic-syntax/string-slices.md:38 msgid "" "You can borrow `&str` slices from `String` via `&` and optionally range " "selection." msgstr "" #: src/basic-syntax/string-slices.md:40 msgid "" "For C++ programmers: think of `&str` as `const char*` from C++, but the one " "that always points to a valid string in memory. Rust `String` is a rough " "equivalent of `std::string` from C++ (main difference: it can only contain " "UTF-8 encoded bytes and will never use a small-string optimization)." msgstr "" #: src/basic-syntax/functions.md:3 msgid "" "A Rust version of the famous [FizzBuzz](https://en.wikipedia.org/wiki/" "Fizz_buzz) interview question:" msgstr "" #: src/basic-syntax/functions.md:36 msgid "" "We refer in `main` to a function written below. Neither forward declarations " "nor headers are necessary. " msgstr "" #: src/basic-syntax/functions.md:37 msgid "" "Declaration parameters are followed by a type (the reverse of some " "programming languages), then a return type." msgstr "" #: src/basic-syntax/functions.md:38 msgid "" "The last expression in a function body (or any block) becomes the return " "value. Simply omit the `;` at the end of the expression." msgstr "" #: src/basic-syntax/functions.md:39 msgid "" "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:40 msgid "" "The range expression in the `for` loop in `print_fizzbuzz_to()` contains " "`=n`, which causes it to include the upper bound." msgstr "" #: src/basic-syntax/rustdoc.md:3 msgid "" "All language items in Rust can be documented using special `///` syntax." msgstr "" #: src/basic-syntax/rustdoc.md:6 msgid "" "/// Determine whether the first argument is divisible by the second " "argument.\n" "///\n" "/// If the second argument is zero, the result is false.\n" msgstr "" #: src/basic-syntax/rustdoc.md:11 msgid "// Corner case, early return\n" msgstr "" #: src/basic-syntax/rustdoc.md:13 msgid "// The last expression in a block is the return value\n" msgstr "" #: src/basic-syntax/rustdoc.md:17 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." msgstr "" #: src/basic-syntax/rustdoc.md:24 msgid "" "Show students the generated docs for the `rand` crate at [`docs.rs/rand`]" "(https://docs.rs/rand)." 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." msgstr "" #: src/basic-syntax/rustdoc.md:30 msgid "" "Inner doc comments are discussed later (in the page on modules) and need not " "be addressed here." 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)." 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:" msgstr "" #: src/basic-syntax/methods.md:24 msgid "\"old area: {}\"" msgstr "\"gammelt areal: {}\"" #: src/basic-syntax/methods.md:26 msgid "\"new area: {}\"" msgstr "\"nyt areal: {}\"" #: src/basic-syntax/methods.md:30 msgid "" "We will look much more at methods in today's exercise and in tomorrow's " "class." msgstr "" #: src/basic-syntax/methods.md:34 msgid "Add a static method called `Rectangle::new` and call this from `main`:" 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)." 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." msgstr "" #: src/basic-syntax/functions-interlude.md:1 msgid "Function Overloading" msgstr "" #: src/basic-syntax/functions-interlude.md:3 msgid "Overloading is not supported:" msgstr "" #: src/basic-syntax/functions-interlude.md:5 msgid "Each function has a single implementation:" msgstr "" #: src/basic-syntax/functions-interlude.md:6 msgid "Always takes a fixed number of parameters." msgstr "" #: src/basic-syntax/functions-interlude.md:7 msgid "Always takes a single set of parameter types." msgstr "" #: src/basic-syntax/functions-interlude.md:8 msgid "Default values are not supported:" msgstr "" #: src/basic-syntax/functions-interlude.md:9 msgid "All call sites have the same number of arguments." msgstr "" #: src/basic-syntax/functions-interlude.md:10 msgid "Macros are sometimes used as an alternative." msgstr "" #: src/basic-syntax/functions-interlude.md:12 msgid "However, function parameters can be generic:" msgstr "" #: src/basic-syntax/functions-interlude.md:20 msgid "\"coin toss: {}\"" msgstr "\"mønt kast: {}\"" #: src/basic-syntax/functions-interlude.md:20 msgid "\"heads\"" msgstr "\"plat\"" #: src/basic-syntax/functions-interlude.md:20 msgid "\"tails\"" msgstr "\"krone\"" #: src/basic-syntax/functions-interlude.md:21 msgid "\"cash prize: {}\"" msgstr "\"pengepremie: {}\"" #: 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." msgstr "" #: src/exercises/day-1/morning.md:1 msgid "Day 1: Morning Exercises" msgstr "Dag 1: formiddagsøvelser" #: src/exercises/day-1/morning.md:3 msgid "In these exercises, we will explore two parts of Rust:" msgstr "" #: src/exercises/day-1/morning.md:5 msgid "Implicit conversions between types." msgstr "" #: src/exercises/day-1/morning.md:7 msgid "Arrays and `for` loops." msgstr "" #: src/exercises/day-1/morning.md:11 msgid "A few things to consider while solving the exercises:" msgstr "" #: src/exercises/day-1/morning.md:13 msgid "" "Use a local Rust installation, if possible. This way you can get auto-" "completion in your editor. See the page about [Using Cargo](../../cargo.md) " "for details on installing Rust." msgstr "" #: src/exercises/day-1/morning.md:17 msgid "Alternatively, use the Rust Playground." 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." 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." 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:" 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." 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`." 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." msgstr "" #: src/exercises/day-1/implicit-conversions.md:34 msgid "Execute the above program and look at the compiler error." msgstr "" #: src/exercises/day-1/implicit-conversions.md:36 msgid "Update the code above to use `into()` to do the conversion." msgstr "" #: src/exercises/day-1/implicit-conversions.md:38 msgid "" "Change the types of `x` and `y` to other things (such as `f32`, `bool`, " "`i128`) to see which types you can convert to which other types. Try " "converting small types to big types and the other way around. Check the " "[standard library documentation](https://doc.rust-lang.org/std/convert/trait." "From.html) to see if `From` is implemented for the pairs you check." msgstr "" #: src/exercises/day-1/for-loops.md:1 #: src/exercises/day-1/solutions-morning.md:3 msgid "Arrays and `for` Loops" msgstr "" #: src/exercises/day-1/for-loops.md:3 msgid "We saw that an array can be declared like this:" msgstr "" #: src/exercises/day-1/for-loops.md:9 msgid "" "You can print such an array by asking for its debug representation with `{:?}" "`:" msgstr "" #: src/exercises/day-1/for-loops.md:19 msgid "" "Rust lets you iterate over things like arrays and ranges using the `for` " "keyword:" msgstr "" #: src/exercises/day-1/for-loops.md:25 msgid "\"Iterating over array:\"" msgstr "" #: src/exercises/day-1/for-loops.md:27 msgid "\" {n}\"" msgstr "\" {n}\"" #: src/exercises/day-1/for-loops.md:31 msgid "\"Iterating over range:\"" msgstr "" #: src/exercises/day-1/for-loops.md:33 msgid "\" {}\"" msgstr "\" {}\"" #: src/exercises/day-1/for-loops.md:39 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):" msgstr "" #: src/exercises/day-1/for-loops.md:49 msgid "Hard-code both functions to operate on 3 × 3 matrices." msgstr "" #: src/exercises/day-1/for-loops.md:51 msgid "" "Copy the code below to and implement the " "functions:" 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" 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" msgstr "" #: src/exercises/day-1/for-loops.md:73 #: src/exercises/day-1/solutions-morning.md:49 msgid "\"matrix:\"" msgstr "\"matrix:\"" #: src/exercises/day-1/for-loops.md:77 #: src/exercises/day-1/solutions-morning.md:53 msgid "\"transposed:\"" msgstr "\"transponeret:\"" #: src/exercises/day-1/for-loops.md:82 msgid "Bonus Question" 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?" msgstr "" #: src/exercises/day-1/for-loops.md:89 msgid "" "See the [`ndarray` crate](https://docs.rs/ndarray/) for a production quality " "implementation." msgstr "" #: src/exercises/day-1/for-loops.md:94 msgid "" "The solution and the answer to the bonus section are available in the " "[Solution](solutions-morning.md#arrays-and-for-loops) section." msgstr "" #: src/exercises/day-1/for-loops.md:97 msgid "" "The use of the reference `&array` within `for n in &array` is a subtle " "preview of issues of ownership that will come later in the afternoon." msgstr "" #: src/exercises/day-1/for-loops.md:100 msgid "Without the `&`..." msgstr "" #: src/exercises/day-1/for-loops.md:101 msgid "" "The loop would have been one that consumes the array. This is a change " "[introduced in the 2021 Edition](https://doc.rust-lang.org/edition-guide/" "rust-2021/IntoIterator-for-arrays.html)." msgstr "" #: src/exercises/day-1/for-loops.md:104 msgid "" "An implicit array copy would have occurred. Since `i32` is a copy type, " "then `[i32; 3]` is also a copy type." 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." 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:" msgstr "" #: src/control-flow/blocks.md:27 msgid "" "If the last expression ends with `;`, then the resulting value and type is " "`()`." msgstr "" #: src/control-flow/blocks.md:29 msgid "" "The same rule is used for functions: the value of the function body is the " "return value:" msgstr "" #: src/control-flow/blocks.md:45 src/enums.md:34 src/enums/sizes.md:28 #: src/pattern-matching.md:25 src/pattern-matching/match-guards.md:22 #: src/structs.md:31 src/methods.md:30 src/methods/example.md:46 msgid "Key Points:" msgstr "" #: src/control-flow/blocks.md:46 msgid "" "The point of this slide is to show that blocks have a type and value in " "Rust. " msgstr "" #: src/control-flow/blocks.md:47 msgid "" "You can show how the value of the block changes by changing the last line in " "the block. For instance, adding/removing a semicolon or using a `return`." msgstr "" #: src/control-flow/if-expressions.md:1 msgid "`if` expressions" msgstr "" #: src/control-flow/if-expressions.md:3 msgid "" "You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" "if-expr.html#if-expressions) exactly like `if` statements in other languages:" msgstr "" #: src/control-flow/if-expressions.md:18 msgid "" "In addition, you can use `if` as an expression. The last expression of each " "block becomes the value of the `if` expression:" msgstr "" #: src/control-flow/if-expressions.md:35 msgid "" "Because `if` is an expression and must have a particular type, both of its " "branch blocks must have the same type. Consider showing what happens if you " "add `;` after `x / 2` in the second example." msgstr "" #: src/control-flow/for-expressions.md:1 msgid "`for` loops" 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/control-flow/for-expressions.md:22 msgid "You can use `break` and `continue` here as usual." msgstr "" #: src/control-flow/for-expressions.md:26 msgid "Index iteration is not a special syntax in Rust for just that case." msgstr "" #: src/control-flow/for-expressions.md:27 msgid "`(0..10)` is a range that implements an `Iterator` trait. " msgstr "" #: src/control-flow/for-expressions.md:28 msgid "" "`step_by` is a method that returns another `Iterator` that skips every other " "element. " 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()`." msgstr "" #: src/control-flow/while-expressions.md:1 msgid "`while` loops" msgstr "" #: src/control-flow/while-expressions.md:3 msgid "" "The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" "expr.html#predicate-loops) works very similar to other languages:" msgstr "" #: src/control-flow/break-continue.md:1 msgid "`break` and `continue`" msgstr "" #: src/control-flow/break-continue.md:3 msgid "" "If you want to exit a loop early, use [`break`](https://doc.rust-lang.org/" "reference/expressions/loop-expr.html#break-expressions)," 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)." 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:" msgstr "" #: src/control-flow/break-continue.md:29 msgid "" "In this case we break the outer loop after 3 iterations of the inner loop." msgstr "" #: src/control-flow/loop-expressions.md:1 msgid "`loop` expressions" 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." msgstr "" #: src/control-flow/loop-expressions.md:6 msgid "Here you must either `break` or `return` to stop the loop:" msgstr "" #: src/control-flow/loop-expressions.md:28 msgid "Break the `loop` with a value (e.g. `break 8`) and print it out." msgstr "" #: src/control-flow/loop-expressions.md:29 msgid "" "Note that `loop` is the only looping construct which returns a non-trivial " "value. This is because it's guaranteed to be entered at least once (unlike " "`while` and `for` loops)." msgstr "" #: src/basic-syntax/variables.md:3 msgid "" "Rust provides type safety via static typing. Variable bindings are immutable " "by default:" msgstr "" #: src/basic-syntax/variables.md:18 msgid "" "Due to type inference the `i32` is optional. We will gradually show the " "types less and less as the course progresses." msgstr "" #: src/basic-syntax/type-inference.md:3 msgid "Rust will look at how the variable is _used_ to determine the type:" 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." 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." 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:" 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." msgstr "" #: src/basic-syntax/static-and-const.md:1 msgid "Static and Constant Variables" 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. " msgstr "" #: src/basic-syntax/static-and-const.md:6 msgid "`const`" 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:" 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." 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." msgstr "" #: src/basic-syntax/static-and-const.md:34 msgid "`static`" msgstr "" #: src/basic-syntax/static-and-const.md:36 msgid "" "Static variables will live during the whole execution of the program, and " "therefore will not move:" msgstr "" #: src/basic-syntax/static-and-const.md:39 msgid "\"Welcome to RustOS 3.14\"" msgstr "\"Velkommen til RustOS 3.14\"" #: src/basic-syntax/static-and-const.md:42 msgid "\"{BANNER}\"" msgstr "\"{BANNER}\"" #: 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." msgstr "" #: src/basic-syntax/static-and-const.md:50 msgid "" "Because `static` variables are accessible from any thread, they must be " "`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" "lang.org/std/sync/struct.Mutex.html), atomic or similar. It is also possible " "to have mutable statics, but they require manual synchronisation so any " "access to them requires `unsafe` code. We will look at [mutable statics](../" "unsafe/mutable-static-variables.md) in the chapter on Unsafe Rust." msgstr "" #: src/basic-syntax/static-and-const.md:58 msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." msgstr "" #: src/basic-syntax/static-and-const.md:59 msgid "" "`static`, on the other hand, is much more similar to a `const` or mutable " "global variable in C++." 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`." msgstr "" #: src/basic-syntax/static-and-const.md:61 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/basic-syntax/static-and-const.md:62 msgid "`thread_local` data can be created with the macro `std::thread_local`." msgstr "" #: src/basic-syntax/static-and-const.md:64 msgid "Properties table:" 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" 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" 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" msgstr "" #: src/basic-syntax/scopes-shadowing.md:3 msgid "" "You can shadow variables, both those from outer scopes and variables from " "the same scope:" msgstr "" #: src/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/basic-syntax/scopes-shadowing.md:19 msgid "\"after: {a}\"" msgstr "\"efter: {a}\"" #: src/basic-syntax/scopes-shadowing.md:25 msgid "" "Definition: Shadowing is different from mutation, because after shadowing " "both variable's memory locations exist at the same time. Both are available " "under the same name, depending where you use it in the code. " msgstr "" #: src/basic-syntax/scopes-shadowing.md:26 msgid "A shadowing variable can have a different type. " msgstr "" #: src/basic-syntax/scopes-shadowing.md:27 msgid "" "Shadowing looks obscure at first, but is convenient for holding on to values " "after `.unwrap()`." msgstr "" #: src/basic-syntax/scopes-shadowing.md:28 msgid "" "The following code demonstrates why the compiler can't simply reuse memory " "locations when shadowing an immutable variable in a scope, even if the type " "does not change." msgstr "" #: src/enums.md:3 msgid "" "The `enum` keyword allows the creation of a type which has a few different " "variants:" msgstr "" #: src/enums.md:8 msgid "// Implementation based on https://xkcd.com/221/\n" msgstr "" #: src/enums.md:9 msgid "// Chosen by fair dice roll. Guaranteed to be random.\n" msgstr "" #: src/enums.md:28 msgid "\"You got: {:?}\"" msgstr "" #: src/enums.md:36 msgid "Enumerations allow you to collect a set of values under one type" msgstr "" #: src/enums.md:37 msgid "" "This page offers an enum type `CoinFlip` with two variants `Heads` and " "`Tails`. You might note the namespace when using variants." msgstr "" #: src/enums.md:38 msgid "This might be a good time to compare Structs and Enums:" msgstr "" #: src/enums.md:39 msgid "" "In both, you can have a simple version without fields (unit struct) or one " "with different types of fields (variant payloads). " msgstr "" #: src/enums.md:40 msgid "In both, associated functions are defined within an `impl` block." msgstr "" #: src/enums.md:41 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. " 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:" msgstr "" #: src/enums/variant-payloads.md:8 msgid "// Variant without payload\n" msgstr "" #: src/enums/variant-payloads.md:9 msgid "// Tuple struct variant\n" msgstr "" #: src/enums/variant-payloads.md:10 msgid "// Full struct variant\n" msgstr "" #: src/enums/variant-payloads.md:16 msgid "\"page loaded\"" msgstr "" #: src/enums/variant-payloads.md:17 msgid "\"pressed '{c}'\"" msgstr "" #: src/enums/variant-payloads.md:18 msgid "\"clicked at x={x}, y={y}\"" msgstr "" #: src/enums/variant-payloads.md:24 src/pattern-matching.md:10 msgid "'x'" msgstr "'x'" #: 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 `=>`." msgstr "" #: src/enums/variant-payloads.md:36 msgid "" "The expression is matched against the patterns from top to bottom. There is " "no fall-through like in C or C++." msgstr "" #: src/enums/variant-payloads.md:37 msgid "" "The match expression has a value. The value is the last expression in the " "match arm which was executed." msgstr "" #: src/enums/variant-payloads.md:38 msgid "" "Starting from the top we look for what pattern matches the value then run " "the code following the arrow. Once we find a match, we stop. " 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. " msgstr "" #: src/enums/variant-payloads.md:40 msgid "`match` inspects a hidden discriminant field in the `enum`." msgstr "" #: src/enums/variant-payloads.md:41 msgid "" "It is possible to retrieve the discriminant by calling `std::mem::" "discriminant()`" msgstr "" #: src/enums/variant-payloads.md:42 msgid "" "This is useful, for example, if implementing `PartialEq` for structs where " "comparing field values doesn't affect equality." msgstr "" #: 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." msgstr "" #: src/enums/sizes.md:3 msgid "" "Rust enums are packed tightly, taking constraints due to alignment into " "account:" msgstr "" #: src/enums/sizes.md:10 msgid "\"{}: size {} bytes, align: {} bytes\"" msgstr "" #: src/enums/sizes.md:24 msgid "" "See the [Rust Reference](https://doc.rust-lang.org/reference/type-layout." "html)." msgstr "" #: src/enums/sizes.md:30 msgid "" "Internally Rust is using a field (discriminant) to keep track of the enum " "variant." msgstr "" #: src/enums/sizes.md:32 msgid "" "You can control the discriminant if needed (e.g., for compatibility with C):" msgstr "" #: src/enums/sizes.md:50 msgid "" "Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " "bytes." msgstr "" #: src/enums/sizes.md:54 msgid "Try out other types such as" msgstr "" #: src/enums/sizes.md:56 msgid "`dbg_size!(bool)`: size 1 bytes, align: 1 bytes," msgstr "" #: src/enums/sizes.md:57 msgid "" "`dbg_size!(Option)`: size 1 bytes, align: 1 bytes (niche optimization, " "see below)," msgstr "" #: src/enums/sizes.md:58 msgid "`dbg_size!(&i32)`: size 8 bytes, align: 8 bytes (on a 64-bit machine)," msgstr "" #: src/enums/sizes.md:59 msgid "" "`dbg_size!(Option<&i32>)`: size 8 bytes, align: 8 bytes (null pointer " "optimization, see below)." msgstr "" #: src/enums/sizes.md:61 msgid "" "Niche optimization: Rust will merge unused bit patterns for the enum " "discriminant." msgstr "" #: src/enums/sizes.md:64 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/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." msgstr "" #: src/enums/sizes.md:105 msgid "" "More complex example if you want to discuss what happens when we chain more " "than 256 `Option`s together." msgstr "" #: src/control-flow/novel.md:3 msgid "" "Rust has a few control flow constructs which differ from other languages. " "They are used for pattern matching:" 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/control-flow/novel.md:8 src/control-flow/match-expressions.md:1 msgid "`match` expressions" msgstr "`match`-udtryk" #: 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:" msgstr "" #: src/control-flow/if-let-expressions.md:11 msgid "\"Program name: {value}\"" msgstr "" #: src/control-flow/if-let-expressions.md:13 msgid "\"Missing name?\"" msgstr "" #: src/control-flow/if-let-expressions.md:18 #: src/control-flow/while-let-expressions.md:22 #: src/control-flow/match-expressions.md:23 msgid "" "See [pattern matching](../pattern-matching.md) for more details on patterns " "in Rust." msgstr "" #: src/control-flow/if-let-expressions.md:23 msgid "" "Unlike `match`, `if let` does not have to cover all branches. This can make " "it more concise than `match`." msgstr "" #: src/control-flow/if-let-expressions.md:24 msgid "A common usage is handling `Some` values when working with `Option`." msgstr "" #: src/control-flow/if-let-expressions.md:25 msgid "" "Unlike `match`, `if let` does not support guard clauses for pattern matching." msgstr "" #: src/control-flow/if-let-expressions.md:26 msgid "" "Since 1.65, a similar [let-else](https://doc.rust-lang.org/rust-by-example/" "flow_control/let_else.html) construct allows to do a destructuring " "assignment, or if it fails, execute a block which is required to abort " "normal control flow (with `panic`/`return`/`break`/`continue`):" msgstr "" #: 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:" 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." msgstr "" #: src/control-flow/while-let-expressions.md:27 msgid "" "Point out that the `while let` loop will keep going as long as the value " "matches the pattern." msgstr "" #: src/control-flow/while-let-expressions.md:28 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." msgstr "" #: src/control-flow/match-expressions.md:3 msgid "" "The [`match` keyword](https://doc.rust-lang.org/reference/expressions/match-" "expr.html) is used to match a value against one or more patterns. In that " "sense, it works like a series of `if let` expressions:" msgstr "" #: src/control-flow/match-expressions.md:10 msgid "\"cat\"" msgstr "\"cat\"" #: src/control-flow/match-expressions.md:10 msgid "\"Will do cat things\"" msgstr "" #: src/control-flow/match-expressions.md:11 msgid "\"ls\"" msgstr "\"ls\"" #: src/control-flow/match-expressions.md:11 msgid "\"Will ls some files\"" msgstr "" #: src/control-flow/match-expressions.md:12 msgid "\"mv\"" msgstr "\"mv\"" #: src/control-flow/match-expressions.md:12 msgid "\"Let's move some files\"" msgstr "" #: src/control-flow/match-expressions.md:13 msgid "\"rm\"" msgstr "\"rm\"" #: src/control-flow/match-expressions.md:13 msgid "\"Uh, dangerous!\"" msgstr "" #: src/control-flow/match-expressions.md:14 msgid "\"Hmm, no program name?\"" msgstr "" #: src/control-flow/match-expressions.md:15 msgid "\"Unknown program name!\"" msgstr "" #: src/control-flow/match-expressions.md:20 msgid "" "Like `if let`, each match arm must have the same type. The type is the last " "expression of the block, if any. In the example above, the type is `()`." msgstr "" #: src/control-flow/match-expressions.md:28 msgid "Save the match expression to a variable and print it out." msgstr "" #: src/control-flow/match-expressions.md:29 msgid "Remove `.as_deref()` and explain the error." msgstr "" #: src/control-flow/match-expressions.md:30 msgid "" "`std::env::args().next()` returns an `Option`, but we cannot match " "against `String`." msgstr "" #: src/control-flow/match-expressions.md:31 msgid "" "`as_deref()` transforms an `Option` to `Option<&T::Target>`. In our case, " "this turns `Option` into `Option<&str>`." msgstr "" #: src/control-flow/match-expressions.md:32 msgid "" "We can now use pattern matching to match against the `&str` inside `Option`." msgstr "" #: src/pattern-matching.md:3 msgid "" "The `match` keyword let you match a value against one or more _patterns_. " "The comparisons are done from top to bottom and the first match wins." msgstr "" #: src/pattern-matching.md:6 msgid "The patterns can be simple values, similarly to `switch` in C and C++:" msgstr "" #: src/pattern-matching.md:13 msgid "'q'" msgstr "'q'" #: src/pattern-matching.md:13 msgid "\"Quitting\"" msgstr "" #: src/pattern-matching.md:14 msgid "'a'" msgstr "'a'" #: src/pattern-matching.md:14 msgid "'s'" msgstr "'s'" #: src/pattern-matching.md:14 msgid "'w'" msgstr "'w'" #: src/pattern-matching.md:14 msgid "'d'" msgstr "'d'" #: src/pattern-matching.md:14 msgid "\"Moving around\"" msgstr "" #: src/pattern-matching.md:15 msgid "'0'" msgstr "'0'" #: src/pattern-matching.md:15 msgid "'9'" msgstr "'9'" #: src/pattern-matching.md:15 msgid "\"Number input\"" msgstr "" #: src/pattern-matching.md:16 msgid "\"Something else\"" msgstr "" #: src/pattern-matching.md:21 msgid "The `_` pattern is a wildcard pattern which matches any value." msgstr "" #: src/pattern-matching.md:26 msgid "" "You might point out how some specific characters are being used when in a " "pattern" msgstr "" #: src/pattern-matching.md:27 msgid "`|` as an `or`" msgstr "" #: src/pattern-matching.md:28 msgid "`..` can expand as much as it needs to be" msgstr "" #: src/pattern-matching.md:29 msgid "`1..=5` represents an inclusive range" msgstr "" #: src/pattern-matching.md:30 msgid "`_` is a wild card" msgstr "" #: src/pattern-matching.md:31 msgid "" "It can be useful to show how binding works, by for instance replacing a " "wildcard character with a variable, or removing the quotes around `q`." msgstr "" #: src/pattern-matching.md:32 msgid "You can demonstrate matching on a reference." msgstr "" #: src/pattern-matching.md:33 msgid "" "This might be a good time to bring up the concept of irrefutable patterns, " "as the term can show up in error messages." 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:" msgstr "" #: src/pattern-matching/destructuring-enums.md:16 msgid "\"cannot divide {n} into two equal parts\"" msgstr "" #: src/pattern-matching/destructuring-enums.md:23 msgid "\"{n} divided in two is {half}\"" msgstr "" #: src/pattern-matching/destructuring-enums.md:24 msgid "\"sorry, an error happened: {msg}\"" 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." msgstr "" #: src/pattern-matching/destructuring-enums.md:36 msgid "" "The `if`/`else` expression is returning an enum that is later unpacked with " "a `match`." msgstr "" #: src/pattern-matching/destructuring-enums.md:37 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/pattern-matching/destructuring-structs.md:3 msgid "You can also destructure `structs`:" 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/pattern-matching/destructuring-structs.md:23 msgid "Change the literal values in `foo` to match with the other patterns." msgstr "" #: src/pattern-matching/destructuring-structs.md:24 msgid "Add a new field to `Foo` and make changes to the pattern as needed." 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." msgstr "" #: src/pattern-matching/destructuring-arrays.md:3 msgid "" "You can destructure arrays, tuples, and slices by matching on their elements:" msgstr "" #: src/pattern-matching/destructuring-arrays.md:9 msgid "\"Tell me about {triple:?}\"" msgstr "\"Fortæl mig om {triple:?}\"" #: src/pattern-matching/destructuring-arrays.md:11 #: src/pattern-matching/destructuring-arrays.md:34 msgid "\"First is 0, y = {y}, and z = {z}\"" msgstr "" #: src/pattern-matching/destructuring-arrays.md:12 #: src/pattern-matching/destructuring-arrays.md:35 msgid "\"First is 1 and the rest were ignored\"" msgstr "" #: src/pattern-matching/destructuring-arrays.md:13 #: src/pattern-matching/destructuring-arrays.md:36 msgid "\"All elements were ignored\"" msgstr "" #: src/pattern-matching/destructuring-arrays.md:21 msgid "" "Destructuring of slices of unknown length also works with patterns of fixed " "length." 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. " msgstr "" #: src/pattern-matching/destructuring-arrays.md:42 msgid "Add more values to the array." msgstr "" #: src/pattern-matching/destructuring-arrays.md:43 msgid "" "Point out that how `..` will expand to account for different number of " "elements." msgstr "" #: src/pattern-matching/destructuring-arrays.md:44 msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" msgstr "" #: src/pattern-matching/match-guards.md:3 msgid "" "When matching, you can add a _guard_ to a pattern. This is an arbitrary " "Boolean expression which will be executed if the pattern matches:" msgstr "" #: src/pattern-matching/match-guards.md:10 msgid "\"Tell me about {pair:?}\"" 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!\"" msgstr "" #: src/pattern-matching/match-guards.md:14 msgid "\"The first one is odd\"" msgstr "" #: src/pattern-matching/match-guards.md:15 msgid "\"No correlation...\"" msgstr "" #: src/pattern-matching/match-guards.md:23 msgid "" "Match guards as a separate syntax feature are important and necessary when " "we wish to concisely express more complex ideas than patterns alone would " "allow." 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." msgstr "" #: src/pattern-matching/match-guards.md:26 msgid "You can use the variables defined in the pattern in your if expression." msgstr "" #: src/pattern-matching/match-guards.md:27 msgid "" "The condition defined in the guard applies to every expression in a pattern " "with an `|`." msgstr "" #: src/exercises/day-1/afternoon.md:1 msgid "Day 1: Afternoon Exercises" msgstr "" #: src/exercises/day-1/afternoon.md:3 msgid "We will look at two things:" msgstr "" #: src/exercises/day-1/afternoon.md:5 msgid "The Luhn algorithm," msgstr "Luhn-algorithmen," #: src/exercises/day-1/afternoon.md:7 msgid "An exercise on pattern matching." msgstr "" #: src/exercises/day-1/afternoon.md:11 src/exercises/day-2/afternoon.md:7 #: src/exercises/bare-metal/afternoon.md:7 #: src/exercises/concurrency/afternoon.md:13 msgid "" "After looking at the exercises, you can look at the [solutions](solutions-" "afternoon.md) provided." 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:" msgstr "" #: src/exercises/day-1/luhn.md:7 msgid "Ignore all spaces. Reject number with less than two digits." 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`." msgstr "" #: src/exercises/day-1/luhn.md:12 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/exercises/day-1/luhn.md:15 msgid "Sum all the undoubled and doubled digits." msgstr "" #: src/exercises/day-1/luhn.md:17 msgid "The credit card number is valid if the sum ends with `0`." msgstr "" #: src/exercises/day-1/luhn.md:19 msgid "" "Copy the code below to and implement the " "function." msgstr "" #: src/exercises/day-1/luhn.md:21 msgid "" "Try to solve the problem the \"simple\" way first, using `for` loops and " "integers. Then, revisit the solution and try to implement it with iterators." 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/exercises/day-1/luhn.md:36 src/exercises/day-1/solutions-afternoon.md:44 msgid "\"foo 0 0\"" msgstr "\"foo 0 0\"" #: 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/exercises/day-1/luhn.md:42 src/exercises/day-1/solutions-afternoon.md:50 msgid "\" \"" msgstr "\" \"" #: src/exercises/day-1/luhn.md:43 src/exercises/day-1/solutions-afternoon.md:51 msgid "\" \"" msgstr "\" \"" #: src/exercises/day-1/luhn.md:44 src/exercises/day-1/solutions-afternoon.md:52 msgid "\" \"" msgstr "\" \"" #: src/exercises/day-1/luhn.md:49 src/exercises/day-1/solutions-afternoon.md:57 msgid "\"0\"" msgstr "\"0\"" #: src/exercises/day-1/luhn.md:54 src/exercises/day-1/solutions-afternoon.md:62 msgid "\" 0 0 \"" msgstr "\" 0 0 \"" #: 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/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/exercises/day-1/luhn.md:61 src/exercises/day-1/solutions-afternoon.md:69 msgid "\"7992 7398 713\"" msgstr "\"7992 7398 713\"" #: 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/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/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/exercises/day-1/pattern-matching.md:1 msgid "Exercise: Expression Evaluation" msgstr "" #: src/exercises/day-1/pattern-matching.md:3 msgid "Let's write a simple recursive evaluator for arithmetic expressions. " 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" msgstr "" #: src/exercises/day-1/pattern-matching.md:14 #: src/exercises/day-1/solutions-afternoon.md:91 msgid "/// An expression, in tree form.\n" msgstr "" #: src/exercises/day-1/pattern-matching.md:18 #: src/exercises/day-1/solutions-afternoon.md:95 msgid "/// An operation on two subexpressions.\n" msgstr "" #: src/exercises/day-1/pattern-matching.md:25 #: src/exercises/day-1/solutions-afternoon.md:102 msgid "/// A literal value\n" 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" 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" 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" 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" 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/exercises/day-1/pattern-matching.md:100 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)`." msgstr "" #: src/exercises/day-1/pattern-matching.md:105 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/exercises/day-1/pattern-matching.md:109 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." 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?" 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:" msgstr "" #: src/welcome-day-2.md:5 msgid "" "Memory management: stack vs heap, manual memory management, scope-based " "memory management, and garbage collection." msgstr "" #: src/welcome-day-2.md:8 msgid "" "Ownership: move semantics, copying and cloning, borrowing, and lifetimes." msgstr "" #: src/welcome-day-2.md:10 msgid "Structs and methods." msgstr "Strenge og iteratorer." #: src/welcome-day-2.md:12 msgid "" "The Standard Library: `String`, `Option` and `Result`, `Vec`, `HashMap`, " "`Rc` and `Arc`." msgstr "" #: src/welcome-day-2.md:15 msgid "Modules: visibility, paths, and filesystem hierarchy." msgstr "" #: src/memory-management.md:3 msgid "Traditionally, languages have fallen into two broad categories:" msgstr "" #: src/memory-management.md:5 msgid "Full control via manual memory management: C, C++, Pascal, ..." msgstr "" #: src/memory-management.md:6 msgid "" "Full safety via automatic memory management at runtime: Java, Python, Go, " "Haskell, ..." msgstr "" #: src/memory-management.md:8 msgid "Rust offers a new mix:" msgstr "" #: src/memory-management.md:10 msgid "" "Full control _and_ safety via compile time enforcement of correct memory " "management." msgstr "" #: src/memory-management.md:13 msgid "It does this with an explicit ownership concept." msgstr "" #: src/memory-management.md:15 msgid "First, let's refresh how memory management works." msgstr "" #: src/memory-management/stack-vs-heap.md:1 msgid "The Stack vs The Heap" msgstr "" #: src/memory-management/stack-vs-heap.md:3 msgid "Stack: Continuous area of memory for local variables." msgstr "" #: src/memory-management/stack-vs-heap.md:4 msgid "Values have fixed sizes known at compile time." msgstr "" #: src/memory-management/stack-vs-heap.md:5 msgid "Extremely fast: just move a stack pointer." msgstr "" #: src/memory-management/stack-vs-heap.md:6 msgid "Easy to manage: follows function calls." msgstr "" #: src/memory-management/stack-vs-heap.md:7 msgid "Great memory locality." msgstr "" #: src/memory-management/stack-vs-heap.md:9 msgid "Heap: Storage of values outside of function calls." msgstr "" #: src/memory-management/stack-vs-heap.md:10 msgid "Values have dynamic sizes determined at runtime." msgstr "" #: src/memory-management/stack-vs-heap.md:11 msgid "Slightly slower than the stack: some book-keeping needed." msgstr "" #: src/memory-management/stack-vs-heap.md:12 msgid "No guarantee of memory locality." msgstr "" #: src/memory-management/stack.md:1 msgid "Stack and Heap Example" msgstr "Eksempel på stak og heap" #: 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:" 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/memory-management/stack.md:28 msgid "" "Mention that a `String` is backed by a `Vec`, so it has a capacity and " "length and can grow if mutable via reallocation on the heap." msgstr "" #: src/memory-management/stack.md:30 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)" msgstr "" #: src/memory-management/stack.md:32 msgid "" "We can inspect the memory layout with `unsafe` code. However, you should " "point out that this is rightfully unsafe!" msgstr "" #: src/memory-management/stack.md:37 src/testing/unit-tests.md:7 #: src/exercises/day-1/solutions-afternoon.md:11 msgid "' '" msgstr "' '" #: src/memory-management/stack.md:38 msgid "\"world\"" msgstr "" #: src/memory-management/stack.md:39 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" msgstr "" #: src/memory-management/stack.md:44 msgid "\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\"" 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 msgid "" "If not done with care, this can lead to crashes, bugs, security " "vulnerabilities, and memory leaks." msgstr "" #: src/memory-management/manual.md:7 msgid "C Example" msgstr "C-eksempel" #: src/memory-management/manual.md:9 msgid "You must call `free` on every pointer you allocate with `malloc`:" msgstr "" #: src/memory-management/manual.md:14 msgid "" "//\n" " // ... lots of code\n" " //\n" msgstr "" #: src/memory-management/manual.md:21 msgid "" "Memory is leaked if the function returns early between `malloc` and `free`: " "the pointer is lost and we cannot deallocate the memory. Worse, freeing the " "pointer twice, or accessing a freed pointer can lead to exploitable security " "vulnerabilities." msgstr "" #: src/memory-management/scope-based.md:3 msgid "" "Constructors and destructors let you hook into the lifetime of an object." msgstr "" #: src/memory-management/scope-based.md:5 msgid "" "By wrapping a pointer in an object, you can free memory when the object is " "destroyed. The compiler guarantees that this happens, even if an exception " "is raised." msgstr "" #: src/memory-management/scope-based.md:9 msgid "" "This is often called _resource acquisition is initialization_ (RAII) and " "gives you smart pointers." msgstr "" #: src/memory-management/scope-based.md:12 msgid "C++ Example" msgstr "" #: src/memory-management/scope-based.md:20 msgid "" "The `std::unique_ptr` object is allocated on the stack, and points to memory " "allocated on the heap." msgstr "" #: src/memory-management/scope-based.md:22 msgid "At the end of `say_hello`, the `std::unique_ptr` destructor will run." msgstr "" #: src/memory-management/scope-based.md:23 msgid "The destructor frees the `Person` object it points to." msgstr "" #: src/memory-management/scope-based.md:25 msgid "" "Special move constructors are used when passing ownership to a function:" msgstr "" #: src/memory-management/garbage-collection.md:1 msgid "Automatic Memory Management" msgstr "" #: src/memory-management/garbage-collection.md:3 msgid "" "An alternative to manual and scope-based memory management is automatic " "memory management:" msgstr "" #: src/memory-management/garbage-collection.md:6 msgid "The programmer never allocates or deallocates memory explicitly." msgstr "" #: src/memory-management/garbage-collection.md:7 msgid "" "A garbage collector finds unused memory and deallocates it for the " "programmer." msgstr "" #: src/memory-management/garbage-collection.md:9 msgid "Java Example" msgstr "" #: src/memory-management/garbage-collection.md:11 msgid "The `person` object is not deallocated after `sayHello` returns:" msgstr "" #: src/memory-management/rust.md:1 msgid "Memory Management in Rust" msgstr "" #: src/memory-management/rust.md:3 msgid "Memory management in Rust is a mix:" msgstr "" #: src/memory-management/rust.md:5 msgid "Safe and correct like Java, but without a garbage collector." msgstr "" #: src/memory-management/rust.md:6 msgid "Scope-based like C++, but the compiler enforces full adherence." msgstr "" #: src/memory-management/rust.md:7 msgid "" "A Rust user can choose the right abstraction for the situation, some even " "have no cost at runtime like C." msgstr "" #: src/memory-management/rust.md:9 msgid "Rust achieves this by modeling _ownership_ explicitly." msgstr "" #: src/memory-management/rust.md:13 msgid "" "If asked how at this point, you can mention that in Rust this is usually " "handled by RAII wrapper types such as [Box](https://doc.rust-lang.org/std/" "boxed/struct.Box.html), [Vec](https://doc.rust-lang.org/std/vec/struct.Vec." "html), [Rc](https://doc.rust-lang.org/std/rc/struct.Rc.html), or [Arc]" "(https://doc.rust-lang.org/std/sync/struct.Arc.html). These encapsulate " "ownership and memory allocation via various means, and prevent the potential " "errors in C." msgstr "" #: src/memory-management/rust.md:15 msgid "" "You may be asked about destructors here, the [Drop](https://doc.rust-lang." "org/std/ops/trait.Drop.html) trait is the Rust equivalent." msgstr "" #: src/ownership.md:3 msgid "" "All variable bindings have a _scope_ where they are valid and it is an error " "to use a variable outside its scope:" msgstr "" #: src/ownership.md:19 msgid "" "At the end of the scope, the variable is _dropped_ and the data is freed." msgstr "" #: src/ownership.md:20 msgid "A destructor can run here to free up resources." msgstr "" #: src/ownership.md:21 msgid "We say that the variable _owns_ the value." msgstr "" #: src/ownership/move-semantics.md:3 msgid "An assignment will transfer _ownership_ between variables:" msgstr "" #: src/ownership/move-semantics.md:7 msgid "\"Hello!\"" msgstr "" #: src/ownership/move-semantics.md:10 msgid "// println!(\"s1: {s1}\");\n" msgstr "" #: src/ownership/move-semantics.md:14 msgid "The assignment of `s1` to `s2` transfers ownership." msgstr "" #: src/ownership/move-semantics.md:15 msgid "When `s1` goes out of scope, nothing happens: it does not own anything." msgstr "" #: src/ownership/move-semantics.md:16 msgid "When `s2` goes out of scope, the string data is freed." msgstr "" #: src/ownership/move-semantics.md:17 msgid "There is always _exactly_ one variable binding which owns a value." 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!)." 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." msgstr "" #: src/ownership/move-semantics.md:25 msgid "" "Simple values (such as integers) can be marked `Copy` (see later slides)." msgstr "" #: src/ownership/move-semantics.md:27 msgid "In Rust, clones are explicit (by using `clone`)." msgstr "" #: src/ownership/moved-strings-rust.md:11 msgid "The heap data from `s1` is reused for `s2`." msgstr "" #: src/ownership/moved-strings-rust.md:12 msgid "When `s1` goes out of scope, nothing happens (it has been moved from)." msgstr "" #: src/ownership/moved-strings-rust.md:14 msgid "Before move to `s2`:" msgstr "" #: src/ownership/moved-strings-rust.md:31 msgid "After move to `s2`:" 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" "```" 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/ownership/double-free-modern-cpp.md:3 msgid "Modern C++ solves this differently:" msgstr "" #: src/ownership/double-free-modern-cpp.md:6 msgid "\"Cpp\"" msgstr "\"Cpp\"" #: src/ownership/double-free-modern-cpp.md:7 msgid "// Duplicate the data in s1.\n" msgstr "" #: src/ownership/double-free-modern-cpp.md:10 msgid "" "The heap data from `s1` is duplicated and `s2` gets its own independent copy." msgstr "" #: src/ownership/double-free-modern-cpp.md:11 msgid "When `s1` and `s2` go out of scope, they each free their own memory." msgstr "" #: src/ownership/double-free-modern-cpp.md:13 msgid "Before copy-assignment:" msgstr "" #: src/ownership/double-free-modern-cpp.md:30 msgid "After copy-assignment:" msgstr "" #: src/ownership/double-free-modern-cpp.md:57 msgid "" "C++ has made a slightly different choice than Rust. Because `=` copies data, " "the string data has to be cloned. Otherwise we would get a double-free when " "either string goes out of scope." 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`." msgstr "" #: src/ownership/double-free-modern-cpp.md:66 msgid "" "Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " "which is being copied or moved." 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/ownership/moves-function-calls.md:8 src/traits/impl-trait.md:10 msgid "\"Hello {name}\"" msgstr "" #: src/ownership/moves-function-calls.md:12 #: src/android/interoperability/java.md:56 msgid "\"Alice\"" msgstr "" #: src/ownership/moves-function-calls.md:14 msgid "// say_hello(name);\n" msgstr "" #: src/ownership/moves-function-calls.md:20 msgid "" "With the first call to `say_hello`, `main` gives up ownership of `name`. " "Afterwards, `name` cannot be used anymore within `main`." msgstr "" #: src/ownership/moves-function-calls.md:21 msgid "" "The heap memory allocated for `name` will be freed at the end of the " "`say_hello` function." msgstr "" #: src/ownership/moves-function-calls.md:22 msgid "" "`main` can retain ownership if it passes `name` as a reference (`&name`) and " "if `say_hello` accepts a reference as a parameter." msgstr "" #: src/ownership/moves-function-calls.md:23 msgid "" "Alternatively, `main` can pass a clone of `name` in the first call (`name." "clone()`)." msgstr "" #: src/ownership/moves-function-calls.md:24 msgid "" "Rust makes it harder than C++ to inadvertently create copies by making move " "semantics the default, and by forcing programmers to make clones explicit." msgstr "" #: src/ownership/copy-clone.md:3 msgid "" "While move semantics are the default, certain types are copied by default:" msgstr "" #: src/ownership/copy-clone.md:15 msgid "These types implement the `Copy` trait." msgstr "" #: src/ownership/copy-clone.md:17 msgid "You can opt-in your own types to use copy semantics:" msgstr "" #: src/ownership/copy-clone.md:32 msgid "After the assignment, both `p1` and `p2` own their own data." msgstr "" #: src/ownership/copy-clone.md:33 msgid "We can also use `p1.clone()` to explicitly copy the data." msgstr "" #: src/ownership/copy-clone.md:37 msgid "Copying and cloning are not the same thing:" msgstr "" #: src/ownership/copy-clone.md:39 msgid "" "Copying refers to bitwise copies of memory regions and does not work on " "arbitrary objects." msgstr "" #: src/ownership/copy-clone.md:40 msgid "" "Copying does not allow for custom logic (unlike copy constructors in C++)." msgstr "" #: src/ownership/copy-clone.md:41 msgid "" "Cloning is a more general operation and also allows for custom behavior by " "implementing the `Clone` trait." msgstr "" #: src/ownership/copy-clone.md:42 msgid "Copying does not work on types that implement the `Drop` trait." msgstr "" #: src/ownership/copy-clone.md:44 src/ownership/lifetimes-function-calls.md:30 msgid "In the above example, try the following:" msgstr "" #: src/ownership/copy-clone.md:46 msgid "" "Add a `String` field to `struct Point`. It will not compile because `String` " "is not a `Copy` type." msgstr "" #: src/ownership/copy-clone.md:47 msgid "" "Remove `Copy` from the `derive` attribute. The compiler error is now in the " "`println!` for `p1`." msgstr "" #: src/ownership/copy-clone.md:48 msgid "Show that it works if you clone `p1` instead." msgstr "" #: src/ownership/copy-clone.md:50 msgid "" "If students ask about `derive`, it is sufficient to say that this is a way " "to generate code in Rust at compile time. In this case the default " "implementations of `Copy` and `Clone` traits are generated." msgstr "" #: src/ownership/borrowing.md:3 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." msgstr "" #: src/ownership/borrowing.md:24 msgid "The caller retains ownership of the inputs." msgstr "" #: src/ownership/borrowing.md:28 msgid "Notes on stack returns:" msgstr "" #: src/ownership/borrowing.md:29 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)." msgstr "" #: src/ownership/borrowing.md:51 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/ownership/shared-unique-borrows.md:3 msgid "Rust puts constraints on the ways you can borrow values:" msgstr "" #: src/ownership/shared-unique-borrows.md:5 msgid "You can have one or more `&T` values at any given time, _or_" msgstr "" #: src/ownership/shared-unique-borrows.md:6 msgid "You can have exactly one `&mut T` value." msgstr "" #: src/ownership/shared-unique-borrows.md:26 msgid "" "The above code does not compile because `a` is borrowed as mutable (through " "`c`) and as immutable (through `b`) at the same time." msgstr "" #: 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." 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\"." msgstr "" #: src/ownership/lifetimes.md:3 msgid "A borrowed value has a _lifetime_:" msgstr "" #: src/ownership/lifetimes.md:5 msgid "The lifetime can be implicit: `add(p1: &Point, p2: &Point) -> Point`." msgstr "" #: src/ownership/lifetimes.md:6 msgid "Lifetimes can also be explicit: `&'a Point`, `&'document str`." msgstr "" #: src/ownership/lifetimes.md:7 src/ownership/lifetimes-function-calls.md:24 msgid "" "Read `&'a Point` as \"a borrowed `Point` which is valid for at least the " "lifetime `a`\"." msgstr "" #: src/ownership/lifetimes.md:9 msgid "" "Lifetimes are always inferred by the compiler: you cannot assign a lifetime " "yourself." msgstr "" #: src/ownership/lifetimes.md:11 msgid "" "Lifetime annotations create constraints; the compiler verifies that there is " "a valid solution." msgstr "" #: src/ownership/lifetimes.md:13 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)." msgstr "" #: src/ownership/lifetimes-function-calls.md:3 msgid "" "In addition to borrowing its arguments, a function can return a borrowed " "value:" msgstr "" #: src/ownership/lifetimes-function-calls.md:22 msgid "`'a` is a generic parameter, it is inferred by the compiler." msgstr "" #: src/ownership/lifetimes-function-calls.md:23 msgid "Lifetimes start with `'` and `'a` is a typical default name." msgstr "" #: src/ownership/lifetimes-function-calls.md:26 msgid "" "The _at least_ part is important when parameters are in different scopes." msgstr "" #: src/ownership/lifetimes-function-calls.md:32 msgid "" "Move the declaration of `p2` and `p3` into a new scope (`{ ... }`), " "resulting in the following code:" msgstr "" #: 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 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:" msgstr "" #: src/ownership/lifetimes-function-calls.md:56 msgid "" "Two references to two values are borrowed by a function and the function " "returns another reference." msgstr "" #: src/ownership/lifetimes-function-calls.md:58 msgid "" "It must have come from one of those two inputs (or from a global variable)." msgstr "" #: src/ownership/lifetimes-function-calls.md:59 msgid "" "Which one is it? The compiler needs to know, so at the call site the " "returned reference is not used for longer than a variable from where the " "reference came from." msgstr "" #: src/ownership/lifetimes-data-structures.md:3 msgid "" "If a data type stores borrowed data, it must be annotated with a lifetime:" 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.\"" 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/ownership/lifetimes-data-structures.md:19 msgid "\"{dog:?}\"" msgstr "\"{dog:?}\"" #: 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." 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." 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." msgstr "" #: src/ownership/lifetimes-data-structures.md:28 msgid "When possible, make data structures own their data directly." 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." msgstr "" #: src/structs.md:3 msgid "Like C and C++, Rust has support for custom structs:" 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/structs.md:16 src/structs.md:19 src/structs.md:25 msgid "\"{} is {} years old\"" msgstr "" #: src/structs.md:22 msgid "\"Jackie\"" msgstr "\"Jackie\"" #: src/structs.md:33 msgid "Structs work like in C or C++." msgstr "" #: src/structs.md:34 msgid "Like in C++, and unlike in C, no typedef is needed to define a type." msgstr "" #: src/structs.md:35 msgid "Unlike in C++, there is no inheritance between structs." msgstr "" #: src/structs.md:36 msgid "" "Methods are defined in an `impl` block, which we will see in following " "slides." msgstr "" #: src/structs.md:37 msgid "" "This may be a good time to let people know there are different types of " "structs. " msgstr "" #: src/structs.md:38 msgid "" "Zero-sized structs `e.g., struct Foo;` might be used when implementing a " "trait on some type but don’t have any data that you want to store in the " "value itself. " msgstr "" #: src/structs.md:39 msgid "" "The next slide will introduce Tuple structs, used when the field names are " "not important." msgstr "" #: src/structs.md:40 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." msgstr "" #: src/structs/tuple-structs.md:3 msgid "If the field names are unimportant, you can use a tuple struct:" msgstr "" #: src/structs/tuple-structs.md:10 msgid "\"({}, {})\"" msgstr "\"({}, {})\"" #: src/structs/tuple-structs.md:14 msgid "This is often used for single-field wrappers (called newtypes):" msgstr "" #: src/structs/tuple-structs.md:21 msgid "\"Ask a rocket scientist at NASA\"" 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 msgid "" "Newtypes are a great way to encode additional information about the value in " "a primitive type, for example:" msgstr "" #: src/structs/tuple-structs.md:38 msgid "The number is measured in some units: `Newtons` in the example above." msgstr "" #: src/structs/tuple-structs.md:39 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)\\`." msgstr "" #: src/structs/tuple-structs.md:40 msgid "" "Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " "single field in the newtype." msgstr "" #: src/structs/tuple-structs.md:41 msgid "" "Rust generally doesn’t like inexplicit things, like automatic unwrapping or " "for instance using booleans as integers." msgstr "" #: src/structs/tuple-structs.md:42 msgid "Operator overloading is discussed on Day 3 (generics)." msgstr "" #: src/structs/tuple-structs.md:43 msgid "" "The example is a subtle reference to the [Mars Climate Orbiter](https://en." "wikipedia.org/wiki/Mars_Climate_Orbiter) failure." msgstr "" #: src/structs/field-shorthand.md:3 msgid "" "If you already have variables with the right names, then you can create the " "struct using a shorthand:" msgstr "" #: src/structs/field-shorthand.md:21 msgid "\"{peter:?}\"" msgstr "\"{peter:?}\"" #: 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" 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." msgstr "" #: src/structs/field-shorthand.md:52 msgid "\"Bot\"" msgstr "\"Bot\"" #: src/structs/field-shorthand.md:62 msgid "\"Sam\"" msgstr "\"Sam\"" #: src/structs/field-shorthand.md:68 msgid "Methods are defined in the `impl` block." msgstr "" #: src/structs/field-shorthand.md:69 msgid "" "Use struct update syntax to define a new structure using `peter`. Note that " "the variable `peter` will no longer be accessible afterwards." msgstr "" #: src/structs/field-shorthand.md:70 msgid "" "Use `{:#?}` when printing structs to request the `Debug` representation." msgstr "" #: src/methods.md:3 msgid "" "Rust allows you to associate functions with your new types. You do this with " "an `impl` block:" 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." msgstr "" #: src/methods.md:32 msgid "" "Methods are called on an instance of a type (such as a struct or enum), the " "first parameter represents the instance as `self`." 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." msgstr "" #: src/methods.md:34 msgid "Point out the use of the keyword `self`, a method receiver." msgstr "" #: src/methods.md:35 msgid "" "Show that it is an abbreviated term for `self: Self` and perhaps show how " "the struct name could also be used." msgstr "" #: src/methods.md:36 msgid "" "Explain that `Self` is a type alias for the type the `impl` block is in and " "can be used elsewhere in the block." msgstr "" #: src/methods.md:37 msgid "" "Note how `self` is used like other structs and dot notation can be used to " "refer to individual fields." msgstr "" #: src/methods.md:38 msgid "" "This might be a good time to demonstrate how the `&self` differs from `self` " "by modifying the code and trying to run say_hello twice." msgstr "" #: src/methods.md:39 msgid "We describe the distinction between method receivers next." msgstr "" #: src/methods/receiver.md:3 msgid "" "The `&self` above indicates that the method borrows the object immutably. " "There are other possible receivers for a method:" msgstr "" #: src/methods/receiver.md:6 msgid "" "`&self`: borrows the object from the caller using a shared and immutable " "reference. The object can be used again afterwards." msgstr "" #: src/methods/receiver.md:8 msgid "" "`&mut self`: borrows the object from the caller using a unique and mutable " "reference. The object can be used again afterwards." msgstr "" #: src/methods/receiver.md:10 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/methods/receiver.md:14 msgid "`mut self`: same as above, but the method can mutate the object. " msgstr "" #: src/methods/receiver.md:15 msgid "" "No receiver: this becomes a static method on the struct. Typically used to " "create constructors which are called `new` by convention." msgstr "" #: src/methods/receiver.md:18 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`." msgstr "" #: src/methods/receiver.md:24 msgid "" "Consider emphasizing \"shared and immutable\" and \"unique and mutable\". " "These constraints always come together in Rust due to borrow checker rules, " "and `self` is no exception. It isn't possible to reference a struct from " "multiple locations and call a mutating (`&mut self`) method on it." msgstr "" #: src/methods/example.md:11 msgid "// No receiver, a static method\n" msgstr "" #: src/methods/example.md:15 msgid "// Exclusive borrowed read-write access to self\n" msgstr "" #: src/methods/example.md:19 msgid "// Shared and read-only borrowed access to self\n" msgstr "" #: src/methods/example.md:20 msgid "\"Recorded {} laps for {}:\"" msgstr "" #: src/methods/example.md:22 msgid "\"Lap {idx}: {lap} sec\"" msgstr "" #: src/methods/example.md:26 msgid "// Exclusive ownership of self\n" msgstr "" #: src/methods/example.md:28 msgid "\"Race {} is finished, total lap time: {}\"" msgstr "" #: src/methods/example.md:33 msgid "\"Monaco Grand Prix\"" msgstr "\"Monacos Grand Prix\"" #: src/methods/example.md:40 msgid "// race.add_lap(42);\n" msgstr "// race.add_lap(42);\n" #: src/methods/example.md:47 msgid "All four methods here use a different method receiver." msgstr "" #: src/methods/example.md:48 msgid "" "You can point out how that changes what the function can do with the " "variable values and if/how it can be used again in `main`." msgstr "" #: src/methods/example.md:49 msgid "" "You can showcase the error that appears when trying to call `finish` twice." msgstr "" #: src/methods/example.md:50 msgid "" "Note that although the method receivers are different, the non-static " "functions are called the same way in the main body. Rust enables automatic " "referencing and dereferencing when calling methods. Rust automatically adds " "in the `&`, `*`, `muts` so that that object matches the method signature." msgstr "" #: src/methods/example.md:51 msgid "" "You might point out that `print_laps` is using a vector that is iterated " "over. We describe vectors in more detail in the afternoon. " msgstr "" #: 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:" msgstr "" #: src/exercises/day-2/morning.md:5 msgid "Storing books and querying the collection" msgstr "" #: src/exercises/day-2/morning.md:7 msgid "Keeping track of health statistics for patients" msgstr "" #: 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:" msgstr "" #: src/exercises/day-2/book-library.md:11 msgid "\"middle value: {}\"" msgstr "\"midterste værdi: {}\"" #: src/exercises/day-2/book-library.md:13 msgid "\"item: {item}\"" msgstr "\"item: {item}\"" #: 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/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/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" msgstr "" #: src/exercises/day-2/book-library.md:50 msgid "\"Initialize and return a `Library` value\"" msgstr "" #: src/exercises/day-2/book-library.md:54 msgid "\"Return the length of `self.books`\"" msgstr "" #: src/exercises/day-2/book-library.md:58 msgid "\"Return `true` if `self.books` is empty\"" msgstr "" #: src/exercises/day-2/book-library.md:62 msgid "\"Add a new book to `self.books`\"" msgstr "" #: src/exercises/day-2/book-library.md:66 msgid "\"Iterate over `self.books` and print each book's title and year\"" msgstr "" #: src/exercises/day-2/book-library.md:70 msgid "\"Return a reference to the oldest book (if any)\"" 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() -> {}\"" 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/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/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() -> {}\"" msgstr "" #: src/exercises/day-2/book-library.md:93 #: src/exercises/day-2/solutions-morning.md:93 msgid "\"The oldest book is {}\"" msgstr "" #: src/exercises/day-2/book-library.md:94 #: src/exercises/day-2/solutions-morning.md:94 msgid "\"The library is empty!\"" msgstr "" #: src/exercises/day-2/book-library.md:97 #: src/exercises/day-2/solutions-morning.md:97 msgid "\"The library has {} books\"" msgstr "" #: src/exercises/day-2/health-statistics.md:3 msgid "" "You're working on implementing a health-monitoring system. As part of that, " "you need to keep track of users' health statistics." msgstr "" #: src/exercises/day-2/health-statistics.md:6 msgid "" "You'll start with some stubbed functions in an `impl` block as well as a " "`User` struct definition. Your goal is to implement the stubbed out methods " "on the `User` `struct` defined in the `impl` block." msgstr "" #: src/exercises/day-2/health-statistics.md:10 msgid "" "Copy the code below to and fill in the missing " "methods:" msgstr "" #: src/exercises/day-2/health-statistics.md:39 msgid "\"Create a new User instance\"" msgstr "" #: src/exercises/day-2/health-statistics.md:43 msgid "\"Return the user's name\"" msgstr "" #: src/exercises/day-2/health-statistics.md:47 msgid "\"Return the user's age\"" msgstr "" #: src/exercises/day-2/health-statistics.md:51 msgid "\"Return the user's height\"" msgstr "" #: src/exercises/day-2/health-statistics.md:55 msgid "\"Return the number of time the user has visited the doctor\"" msgstr "" #: src/exercises/day-2/health-statistics.md:59 msgid "\"Set the user's age\"" msgstr "" #: src/exercises/day-2/health-statistics.md:63 msgid "\"Set the user's height\"" msgstr "" #: src/exercises/day-2/health-statistics.md:67 msgid "" "\"Update a user's statistics based on measurements from a visit to the " "doctor\"" 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/exercises/day-2/health-statistics.md:73 #: src/exercises/day-2/solutions-morning.md:234 msgid "\"I'm {} and my age is {}\"" 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." msgstr "" #: src/std.md:7 msgid "The common vocabulary types include:" msgstr "" #: src/std.md:9 msgid "" "[`Option` and `Result`](std/option-result.md) types: used for optional " "values and [error handling](error-handling.md)." msgstr "" #: src/std.md:12 msgid "[`String`](std/string.md): the default string type used for owned data." msgstr "" #: src/std.md:14 msgid "[`Vec`](std/vec.md): a standard extensible vector." msgstr "" #: src/std.md:16 msgid "" "[`HashMap`](std/hashmap.md): a hash map type with a configurable hashing " "algorithm." msgstr "" #: src/std.md:19 msgid "[`Box`](std/box.md): an owned pointer for heap-allocated data." msgstr "" #: src/std.md:21 msgid "" "[`Rc`](std/rc.md): a shared reference-counted pointer for heap-allocated " "data." msgstr "" #: src/std.md:25 msgid "" "In fact, Rust contains several layers of the Standard Library: `core`, " "`alloc` and `std`. " msgstr "" #: src/std.md:26 msgid "" "`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/std.md:28 msgid "" "`alloc` includes types which require a global heap allocator, such as `Vec`, " "`Box` and `Arc`." msgstr "" #: src/std.md:29 msgid "" "Embedded Rust applications often only use `core`, and sometimes `alloc`." 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:" 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/option-result.md:18 msgid "`Option` and `Result` are widely used not just in the standard library." msgstr "" #: src/std/option-result.md:19 msgid "`Option<&T>` has zero space overhead compared to `&T`." msgstr "" #: src/std/option-result.md:20 msgid "" "`Result` is the standard type to implement error handling as we will see on " "Day 3." msgstr "" #: src/std/option-result.md:21 msgid "" "`try_into` attempts to convert the vector into a fixed-sized array. This can " "fail:" msgstr "" #: src/std/option-result.md:22 msgid "" "If the vector has the right size, `Result::Ok` is returned with the array." msgstr "" #: src/std/option-result.md:23 msgid "Otherwise, `Result::Err` is returned with the original vector." msgstr "" #: src/std/string.md:3 msgid "" "[`String`](https://doc.rust-lang.org/std/string/struct.String.html) is the " "standard heap-allocated growable UTF-8 string buffer:" 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/string.md:22 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`." msgstr "" #: src/std/string.md:30 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." msgstr "" #: src/std/string.md:31 msgid "" "`String::len` returns the size of the `String` in bytes (which can be " "different from its length in characters)." msgstr "" #: src/std/string.md:32 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)." msgstr "" #: src/std/string.md:33 msgid "" "When people refer to strings they could either be talking about `&str` or " "`String`." msgstr "" #: src/std/string.md:34 msgid "" "When a type implements `Deref`, the compiler will let you " "transparently call methods from `T`." msgstr "" #: src/std/string.md:35 msgid "" "`String` implements `Deref` which transparently gives it " "access to `str`'s methods." msgstr "" #: src/std/string.md:36 msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1`;." msgstr "" #: src/std/string.md:37 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/std/string.md:38 msgid "Compare the different ways to index a `String`:" msgstr "" #: src/std/string.md:39 msgid "" "To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, " "out-of-bounds." msgstr "" #: src/std/string.md:40 msgid "" "To a substring by using `s3[0..4]`, where that slice is on character " "boundaries or not." msgstr "" #: src/std/vec.md:1 msgid "`Vec`" msgstr "`Vec`" #: src/std/vec.md:3 msgid "" "[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " "resizable heap-allocated buffer:" msgstr "" #: src/std/vec.md:9 msgid "\"v1: len = {}, capacity = {}\"" msgstr "\"v1: len = {}, capacity = {}\"" #: src/std/vec.md:14 msgid "\"v2: len = {}, capacity = {}\"" msgstr "\"v2: len = {}, capacity = {}\"" #: src/std/vec.md:16 msgid "// Canonical macro to initialize a vector with elements.\n" msgstr "" #: src/std/vec.md:19 msgid "// Retain only the even elements.\n" msgstr "" #: src/std/vec.md:21 src/std/vec.md:25 msgid "\"{v3:?}\"" msgstr "\"{v3:?}\"" #: src/std/vec.md:23 msgid "// Remove consecutive duplicates.\n" msgstr "" #: 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`." 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." msgstr "" #: src/std/vec.md:40 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." 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." msgstr "" #: src/std/vec.md:44 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/std/vec.md:46 msgid "" "Show iterating over a vector and mutating the value: `for e in &mut v { *e " "+= 50; }`" 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:" 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.\"" 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" msgstr "" #: src/std/hashmap.md:32 msgid "\"{page_counts:#?}\"" msgstr "\"{page_counts:#?}\"" #: src/std/hashmap.md:38 msgid "" "`HashMap` is not defined in the prelude and needs to be brought into scope." msgstr "" #: src/std/hashmap.md:39 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/std/hashmap.md:43 msgid "\"Harry Potter and the Sorcerer's Stone \"" msgstr "\"Harry Potter og De Vises Sten\"" #: src/std/hashmap.md:46 src/std/hashmap.md:55 msgid "\"The Hunger Games\"" msgstr "\"Dødsspillet\"" #: src/std/hashmap.md:49 msgid "Unlike `vec!`, there is unfortunately no standard `hashmap!` macro." msgstr "" #: src/std/hashmap.md:50 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/std/hashmap.md:54 msgid "\"Harry Potter and the Sorcerer's Stone\"" msgstr "" #: src/std/hashmap.md:59 msgid "" "Alternatively HashMap can be built from any `Iterator` which yields key-" "value tuples." msgstr "" #: src/std/hashmap.md:60 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/std/hashmap.md:62 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/std/hashmap.md:64 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." msgstr "" #: src/std/box.md:1 msgid "`Box`" msgstr "`Box`" #: src/std/box.md:3 msgid "" "[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " "pointer to data on the heap:" msgstr "" #: src/std/box.md:8 msgid "\"five: {}\"" msgstr "\"five: {}\"" #: 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)." msgstr "" #: src/std/box.md:34 msgid "" "`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " "not null. " msgstr "" #: src/std/box.md:35 msgid "" "In the above example, you can even leave out the `*` in the `println!` " "statement thanks to `Deref`. " msgstr "" #: src/std/box.md:36 msgid "A `Box` can be useful when you:" msgstr "" #: src/std/box.md:37 msgid "" "have a type whose size that can't be known at compile time, but the Rust " "compiler wants to know an exact size." msgstr "" #: src/std/box.md:38 msgid "" "want to transfer ownership of a large amount of data. To avoid copying large " "amounts of data on the stack, instead store the data on the heap in a `Box` " "so only the pointer is moved." msgstr "" #: src/std/box-recursive.md:1 msgid "Box with Recursive Data Structures" msgstr "" #: src/std/box-recursive.md:3 msgid "" "Recursive data types or data types with dynamic sizes need to use a `Box`:" msgstr "" #: src/std/box-recursive.md:14 src/std/box-niche.md:12 msgid "\"{list:?}\"" msgstr "\"{list:?}\"" #: 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" "```" 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 msgid "" "If `Box` was not used and we attempted to embed a `List` directly into the " "`List`, the compiler would not compute a fixed size of the struct in memory " "(`List` would be of infinite size)." msgstr "" #: 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." msgstr "" #: src/std/box-recursive.md:39 msgid "" "Remove the `Box` in the List definition and show the compiler error. " "\"Recursive with indirection\" is a hint you might want to use a Box or " "reference of some kind, instead of storing a value directly." 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:" 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" "```" 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/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:" msgstr "" #: src/std/rc.md:13 msgid "\"a: {a}\"" msgstr "\"a: {a}\"" #: src/std/rc.md:14 msgid "\"b: {b}\"" msgstr "\"b: {b}\"" #: 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." 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." msgstr "" #: src/std/rc.md:29 msgid "" "`Rc`'s count ensures that its contained value is valid for as long as there " "are references." msgstr "" #: src/std/rc.md:30 msgid "`Rc` in Rust is like `std::shared_ptr` in C++." 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." msgstr "" #: src/std/rc.md:32 msgid "" "`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " "and returns a mutable reference." msgstr "" #: src/std/rc.md:33 msgid "Use `Rc::strong_count` to check the reference count." 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)." 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." 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." msgstr "" #: src/std/cell.md:40 msgid "\"graph: {root:#?}\"" msgstr "" #: src/std/cell.md:41 msgid "\"graph sum: {}\"" msgstr "" #: src/std/cell.md:47 msgid "" "If we were using `Cell` instead of `RefCell` in this example, we would have " "to move the `Node` out of the `Rc` to push children, then move it back in. " "This is safe because there's always one, un-referenced value in the cell, " "but it's not ergonomic." msgstr "" #: src/std/cell.md:48 msgid "" "To do anything with a Node, you must call a `RefCell` method, usually " "`borrow` or `borrow_mut`." 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!)." msgstr "" #: src/std/cell.md:50 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'`." msgstr "" #: src/modules.md:3 msgid "We have seen how `impl` blocks let us namespace functions to a type." msgstr "" #: src/modules.md:5 msgid "Similarly, `mod` lets us namespace types and functions:" msgstr "" #: src/modules.md:10 msgid "\"In the foo module\"" msgstr "" #: src/modules.md:16 msgid "\"In the bar module\"" msgstr "" #: src/modules.md:28 msgid "" "Packages provide functionality and include a `Cargo.toml` file that " "describes how to build a bundle of 1+ crates." 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." msgstr "" #: src/modules.md:30 msgid "Modules define organization, scope, and are the focus of this section." 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:39 msgid "Use the `pub` keyword to make modules public." msgstr "" #: src/modules/visibility.md:41 msgid "" "Additionally, there are advanced `pub(...)` specifiers to restrict the scope " "of public visibility." msgstr "" #: src/modules/visibility.md:43 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:44 msgid "Configuring `pub(crate)` visibility is a common pattern." msgstr "" #: src/modules/visibility.md:45 msgid "Less commonly, you can give visibility to a specific path." msgstr "" #: src/modules/visibility.md:46 msgid "" "In any case, visibility must be granted to an ancestor module (and all of " "its descendants)." msgstr "" #: src/modules/paths.md:3 msgid "Paths are resolved as follows:" msgstr "" #: src/modules/paths.md:5 msgid "As a relative path:" msgstr "" #: src/modules/paths.md:6 msgid "`foo` or `self::foo` refers to `foo` in the current module," msgstr "" #: src/modules/paths.md:7 msgid "`super::foo` refers to `foo` in the parent module." msgstr "" #: src/modules/paths.md:9 msgid "As an absolute path:" msgstr "" #: src/modules/paths.md:10 msgid "`crate::foo` refers to `foo` in the root of the current crate," msgstr "" #: src/modules/paths.md:11 msgid "`bar::foo` refers to `foo` in the `bar` crate." 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:" 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:37 msgid "" "Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " "`module.rs`, and this is still a working alternative for editions after 2018." msgstr "" #: src/modules/filesystem.md:39 msgid "" "The main reason to introduce `filename.rs` as alternative to `filename/mod." "rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." msgstr "" #: src/modules/filesystem.md:42 msgid "Deeper nesting can use folders, even if the main module is a file:" msgstr "" #: src/modules/filesystem.md:52 msgid "" "The place rust will look for modules can be changed with a compiler " "directive:" msgstr "" #: src/modules/filesystem.md:55 msgid "\"some/path.rs\"" msgstr "" #: src/modules/filesystem.md:59 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/exercises/day-2/afternoon.md:1 msgid "Day 2: Afternoon Exercises" msgstr "" #: src/exercises/day-2/afternoon.md:3 msgid "The exercises for this afternoon will focus on strings and iterators." msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:3 msgid "" "The ownership model of Rust affects many APIs. An example of this is the " "[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " "[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " "traits." msgstr "" #: 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:" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:20 msgid "You use this trait like this:" 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: {:?}\"" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:34 msgid "What is the type returned by the iterator? Test your answer here:" msgstr "" #: src/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?" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:48 msgid "`IntoIterator`" msgstr "`IntoIterator`" #: src/exercises/day-2/iterators-and-ownership.md:50 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:" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:62 msgid "" "The syntax here means that every implementation of `IntoIterator` must " "declare two types:" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:65 msgid "`Item`: the type we iterate over, such as `i8`," msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:66 msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:68 msgid "" "Note that `IntoIter` and `Item` are linked: the iterator must have the same " "`Item` type, which means that it returns `Option`" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md:71 msgid "Like before, what is the type returned by the iterator?" msgstr "" #: src/exercises/day-2/iterators-and-ownership.md: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:" 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?" 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." 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." msgstr "" #: src/exercises/day-2/strings-iterators.md:8 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:" msgstr "" #: src/welcome-day-3.md:5 msgid "" "Traits: deriving traits, default methods, and important standard library " "traits." msgstr "" #: src/welcome-day-3.md:8 msgid "" "Generics: generic data types, generic methods, monomorphization, and trait " "objects." msgstr "" #: src/welcome-day-3.md:11 msgid "Error handling: panics, `Result`, and the try operator `?`." msgstr "" #: src/welcome-day-3.md:13 msgid "Testing: unit tests, documentation tests, and integration tests." msgstr "" #: src/welcome-day-3.md:15 msgid "" "Unsafe Rust: raw pointers, static variables, unsafe functions, and extern " "functions." msgstr "" #: src/generics.md:3 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." msgstr "" #: src/generics/data-types.md:3 msgid "You can use generics to abstract over the concrete field type:" 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 };`." msgstr "" #: src/generics/data-types.md:23 msgid "Fix the code to allow points that have elements of different types." msgstr "" #: src/generics/methods.md:3 msgid "You can declare a generic type on your `impl` block:" msgstr "" #: src/generics/methods.md:11 msgid "// + 10\n" msgstr "// + 10\n" #: src/generics/methods.md:14 msgid "// fn set_x(&mut self, x: T)\n" msgstr "// fn set_x(&mut self, x: T)\n" #: src/generics/methods.md:19 msgid "\"p.x = {}\"" msgstr "\"p.x = {}\"" #: src/generics/methods.md:25 msgid "" "_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " "redundant?" msgstr "" #: src/generics/methods.md:26 msgid "" "This is because it is a generic implementation section for generic type. " "They are independently generic." msgstr "" #: src/generics/methods.md:27 msgid "It means these methods are defined for any `T`." msgstr "" #: src/generics/methods.md:28 msgid "It is possible to write `impl Point { .. }`. " 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`." msgstr "" #: src/generics/monomorphization.md:3 msgid "Generic code is turned into non-generic code based on the call sites:" msgstr "" #: src/generics/monomorphization.md:12 msgid "behaves as if you wrote" msgstr "" #: src/generics/monomorphization.md:31 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." msgstr "" #: src/traits.md:3 msgid "" "Rust lets you abstract over types with traits. They're similar to interfaces:" msgstr "" #: src/traits.md:24 src/traits/trait-objects.md:24 msgid "\"The cat\"" msgstr "" #: src/traits.md:24 src/traits/trait-objects.md:24 msgid "// No name, cats won't respond to it anyway.\n" msgstr "" #: src/traits.md:29 msgid "\"Who's a cutie? {} is!\"" msgstr "" #: src/traits.md:33 src/traits/trait-objects.md:31 msgid "\"Fido\"" msgstr "\"Fido\"" #: src/traits/trait-objects.md:3 msgid "" "Trait objects allow for values of different types, for instance in a " "collection:" msgstr "" #: src/traits/trait-objects.md:34 msgid "\"Hello {}!\"" msgstr "\"Hallo {}!\"" #: src/traits/trait-objects.md:40 msgid "Memory layout after allocating `pets`:" msgstr "" #: src/traits/trait-objects.md:42 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" "```" 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." 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`." 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." msgstr "" #: src/traits/trait-objects.md:75 msgid "Compare these outputs in the above example:" msgstr "" #: src/traits/trait-objects.md:77 src/traits/trait-objects.md:78 #: src/traits/closures.md:54 msgid "\"{} {}\"" 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/traits/deriving-traits.md:3 msgid "" "Rust derive macros work by automatically generating code that implements the " "specified traits for a data structure." msgstr "" #: src/traits/deriving-traits.md:5 msgid "You can let the compiler derive a number of traits as follows:" msgstr "" #: src/traits/deriving-traits.md:18 msgid "\"Is {:?}\\nequal to {:?}?\\nThe answer is {}!\"" msgstr "" #: src/traits/deriving-traits.md:19 #: src/exercises/day-1/solutions-afternoon.md:37 msgid "\"yes\"" msgstr "\"ja\"" #: src/traits/deriving-traits.md:19 #: src/exercises/day-1/solutions-afternoon.md:37 msgid "\"no\"" msgstr "\"nej\"" #: src/traits/default-methods.md:3 msgid "Traits can implement behavior in terms of other trait methods:" msgstr "" #: src/traits/default-methods.md:25 msgid "\"{a:?} equals {b:?}: {}\"" msgstr "\"{a:?} er lig {b:?}: {}\"" #: src/traits/default-methods.md:26 msgid "\"{a:?} not_equals {b:?}: {}\"" msgstr "\"{a:?} er ikke lig {b:?}: {}\"" #: 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." msgstr "" #: src/traits/default-methods.md:35 msgid "Move method `not_equals` to a new trait `NotEquals`." msgstr "" #: src/traits/default-methods.md:37 msgid "Make `Equals` a super trait for `NotEquals`." msgstr "" #: src/traits/default-methods.md:46 msgid "Provide a blanket implementation of `NotEquals` for `Equals`." 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/traits/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/traits/trait-bounds.md:6 msgid "You can do this with `T: Trait` or `impl Trait`:" msgstr "" #: src/traits/trait-bounds.md:12 msgid "" "// Syntactic sugar for:\n" "// fn add_42_millions>(x: T) -> i32 {\n" 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." msgstr "" #: src/traits/trait-bounds.md:46 msgid "It declutters the function signature if you have many parameters." msgstr "" #: src/traits/trait-bounds.md:47 msgid "It has additional features making it more powerful." msgstr "" #: src/traits/trait-bounds.md:48 msgid "" "If someone asks, the extra feature is that the type on the left of \":\" can " "be arbitrary, like `Option`." msgstr "" #: src/traits/impl-trait.md:1 msgid "`impl Trait`" msgstr "`impl Trait`" #: src/traits/impl-trait.md:3 msgid "" "Similar to trait bounds, an `impl Trait` syntax can be used in function " "arguments and return values:" msgstr "" #: src/traits/impl-trait.md:19 msgid "`impl Trait` allows you to work with types which you cannot name." msgstr "" #: src/traits/impl-trait.md:23 msgid "" "The meaning of `impl Trait` is a bit different in the different positions." msgstr "" #: src/traits/impl-trait.md:25 msgid "" "For a parameter, `impl Trait` is like an anonymous generic parameter with a " "trait bound." msgstr "" #: src/traits/impl-trait.md:27 msgid "" "For a return type, it means that the return type is some concrete type that " "implements the trait, without naming the type. This can be useful when you " "don't want to expose the concrete type in a public API." msgstr "" #: src/traits/impl-trait.md:31 msgid "" "Inference is hard in return position. A function returning `impl Foo` picks " "the concrete type it returns, without writing it out in the source. A " "function returning a generic type like `collect() -> B` can return any " "type satisfying `B`, and the caller may need to choose one, such as with " "`let x: Vec<_> = foo.collect()` or with the turbofish, `foo.collect::" ">()`." msgstr "" #: src/traits/impl-trait.md:37 msgid "" "This example is great, because it uses `impl Display` twice. It helps to " "explain that nothing here enforces that it is _the same_ `impl Display` " "type. If we used a single `T: Display`, it would enforce the constraint " "that input `T` and return `T` type are the same type. It would not work for " "this particular function, as the type we expect as input is likely not what " "`format!` returns. If we wanted to do the same via `: Display` syntax, we'd " "need two independent generic parameters." msgstr "" #: src/traits/important-traits.md:3 msgid "" "We will now look at some of the most common traits of the Rust standard " "library:" msgstr "" #: src/traits/important-traits.md:5 msgid "" "[`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) and " "[`IntoIterator`](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html) " "used in `for` loops," msgstr "" #: src/traits/important-traits.md:6 msgid "" "[`From`](https://doc.rust-lang.org/std/convert/trait.From.html) and [`Into`]" "(https://doc.rust-lang.org/std/convert/trait.Into.html) used to convert " "values," msgstr "" #: src/traits/important-traits.md:7 msgid "" "[`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and [`Write`]" "(https://doc.rust-lang.org/std/io/trait.Write.html) used for IO," msgstr "" #: src/traits/important-traits.md:8 msgid "" "[`Add`](https://doc.rust-lang.org/std/ops/trait.Add.html), [`Mul`](https://" "doc.rust-lang.org/std/ops/trait.Mul.html), ... used for operator " "overloading, and" msgstr "" #: src/traits/important-traits.md:9 msgid "" "[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) used for " "defining destructors." msgstr "" #: src/traits/important-traits.md:10 msgid "" "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) used " "to construct a default instance of a type." msgstr "" #: src/traits/iterator.md:1 msgid "Iterators" msgstr "Iteratorer" #: src/traits/iterator.md:3 msgid "" "You can implement the [`Iterator`](https://doc.rust-lang.org/std/iter/trait." "Iterator.html) trait on your own types:" msgstr "" #: src/traits/iterator.md:25 msgid "\"fib({i}): {n}\"" msgstr "\"fib({i}): {n}\"" #: src/traits/iterator.md:32 msgid "" "The `Iterator` trait implements many common functional programming " "operations over collections (e.g. `map`, `filter`, `reduce`, etc). This is " "the trait where you can find all the documentation about them. In Rust these " "functions should produce the code as efficient as equivalent imperative " "implementations." msgstr "" #: src/traits/iterator.md:37 msgid "" "`IntoIterator` is the trait that makes for loops work. It is implemented by " "collection types such as `Vec` and references to them such as `&Vec` " "and `&[T]`. Ranges also implement it. This is why you can iterate over a " "vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." msgstr "" #: src/traits/from-iterator.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/traits/from-iterator.md:17 msgid "" "`Iterator` implements `fn collect(self) -> B where B: FromIterator, Self: Sized`" msgstr "" #: src/traits/from-iterator.md:23 msgid "" "There are also implementations which let you do cool things like convert an " "`Iterator>` into a `Result, E>`." msgstr "" #: src/traits/from-into.md:1 msgid "`From` and `Into`" msgstr "`From` og `Into`" #: src/traits/from-into.md:3 msgid "" "Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." "html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " "facilitate type conversions:" msgstr "" #: src/traits/from-into.md:11 src/traits/from-into.md:23 msgid "\"{s}, {addr}, {one}, {bigger}\"" msgstr "\"{s}, {addr}, {one}, {bigger}\"" #: 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:" msgstr "" #: src/traits/from-into.md:29 msgid "" "That's why it is common to only implement `From`, as your type will get " "`Into` implementation too." msgstr "" #: src/traits/from-into.md:30 msgid "" "When declaring a function argument input type like \"anything that can be " "converted into a `String`\", the rule is opposite, you should use `Into`. " "Your function will accept types that implement `From` and those that _only_ " "implement `Into`." 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:" msgstr "" #: src/traits/read-write.md:14 msgid "b\"foo\\nbar\\nbaz\\n\"" msgstr "b\"foo\\nbar\\nbaz\\n\"" #: src/traits/read-write.md:15 msgid "\"lines in slice: {}\"" msgstr "\"linjer i slice: {}\"" #: src/traits/read-write.md:18 msgid "\"lines in file: {}\"" msgstr "\"linjer i file: {}\"" #: src/traits/read-write.md:23 msgid "" "Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " "you abstract over `u8` sinks:" msgstr "" #: src/traits/read-write.md:30 msgid "\"\\n\"" msgstr "\"\\n\"" #: src/traits/read-write.md:37 msgid "\"Logged: {:?}\"" msgstr "" #: src/traits/drop.md:1 msgid "The `Drop` Trait" msgstr "" #: src/traits/drop.md:3 msgid "" "Values which implement [`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop." "html) can specify code to run when they go out of scope:" 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/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/traits/drop.md:23 msgid "\"Exiting block B\"" msgstr "" #: src/traits/drop.md:25 msgid "\"Exiting block A\"" msgstr "" #: src/traits/drop.md:28 msgid "\"Exiting main\"" msgstr "" #: src/traits/drop.md:34 msgid "Note that `std::mem::drop` is not the same as `std::ops::Drop::drop`." msgstr "" #: src/traits/drop.md:35 msgid "Values are automatically dropped when they go out of scope." msgstr "" #: src/traits/drop.md:36 msgid "" "When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" "drop` implementation will be called." msgstr "" #: src/traits/drop.md:38 msgid "" "All its fields will then be dropped too, whether or not it implements `Drop`." msgstr "" #: src/traits/drop.md:39 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." msgstr "" #: src/traits/drop.md:42 msgid "" "This can be useful for objects that do some work on `drop`: releasing locks, " "closing files, etc." msgstr "" #: src/traits/drop.md:45 src/traits/operators.md:26 msgid "Discussion points:" msgstr "" #: src/traits/drop.md:47 msgid "Why doesn't `Drop::drop` take `self`?" msgstr "" #: src/traits/drop.md:48 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/drop.md:51 msgid "Try replacing `drop(a)` with `a.drop()`." msgstr "" #: src/traits/default.md:1 msgid "The `Default` Trait" msgstr "" #: src/traits/default.md:3 msgid "" "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " "produces a default value for a type." msgstr "" #: 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:#?}\"" msgstr "" #: src/traits/default.md:33 msgid "\"{:#?}\"" msgstr "\"{:#?}\"" #: src/traits/default.md:40 msgid "" "It can be implemented directly or it can be derived via `#[derive(Default)]`." msgstr "" #: src/traits/default.md:41 msgid "" "A derived implementation will produce a value where all fields are set to " "their default values." msgstr "" #: src/traits/default.md:42 msgid "This means all types in the struct must implement `Default` too." msgstr "" #: src/traits/default.md:43 msgid "" "Standard Rust types often implement `Default` with reasonable values (e.g. " "`0`, `\"\"`, etc)." msgstr "" #: src/traits/default.md:44 msgid "The partial struct copy works nicely with default." msgstr "" #: src/traits/default.md:45 msgid "" "Rust standard library is aware that types can implement `Default` and " "provides convenience methods that use it." msgstr "" #: src/traits/default.md:46 msgid "" "the `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" "book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" "with-struct-update-syntax)" msgstr "" #: src/traits/operators.md:1 msgid "`Add`, `Mul`, ..." msgstr "`Add`, `Mul`, ..." #: src/traits/operators.md:3 msgid "" "Operator overloading is implemented via traits in [`std::ops`](https://doc." "rust-lang.org/std/ops/index.html):" msgstr "" #: src/traits/operators.md:20 msgid "\"{:?} + {:?} = {:?}\"" msgstr "\"{:?} + {:?} = {:?}\"" #: src/traits/operators.md:28 msgid "" "You could implement `Add` for `&Point`. In which situations is that useful? " 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." msgstr "" #: src/traits/operators.md:33 msgid "" "Why is `Output` an associated type? Could it be made a type parameter of the " "method?" msgstr "" #: src/traits/operators.md:34 msgid "" "Short answer: Function type parameters are controlled by the caller, but " "associated types (like `Output`) are controlled by the implementor of a " "trait." msgstr "" #: src/traits/operators.md:37 msgid "" "You could implement `Add` for two different types, e.g. `impl Add<(i32, " "i32)> for Point` would add a tuple to a `Point`." msgstr "" #: src/traits/closures.md:1 msgid "Closures" msgstr "" #: src/traits/closures.md:3 msgid "" "Closures or lambda expressions have types which cannot be named. However, " "they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." "html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " "[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" msgstr "" #: src/traits/closures.md:10 msgid "\"Calling function on {input}\"" msgstr "" #: src/traits/closures.md:16 src/traits/closures.md:17 msgid "\"add_3: {}\"" msgstr "\"add_3: {}\"" #: src/traits/closures.md:24 src/traits/closures.md:25 msgid "\"accumulate: {}\"" msgstr "\"accumulate: {}\"" #: src/traits/closures.md:28 msgid "\"multiply_sum: {}\"" msgstr "\"multiply_sum: {}\"" #: 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." msgstr "" #: src/traits/closures.md:37 msgid "" "An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " "multiple times, but not concurrently." msgstr "" #: src/traits/closures.md:40 msgid "" "If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " "might consume captured values." msgstr "" #: src/traits/closures.md:43 msgid "" "`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " "I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " "use an `Fn` wherever an `FnMut` or `FnOnce` is called for." msgstr "" #: src/traits/closures.md:47 msgid "" "The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " "`multiply_sum`), depending on what the closure captures." msgstr "" #: src/traits/closures.md:50 msgid "" "By default, closures will capture by reference if they can. The `move` " "keyword makes them capture by value." 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." msgstr "" #: src/exercises/day-3/morning.md:5 msgid "" "We will also look at enum dispatch with an exercise involving points and " "polygons." msgstr "" #: src/exercises/day-3/simple-gui.md:3 msgid "" "Let us design a classical GUI library using our new knowledge of traits and " "trait objects." msgstr "" #: src/exercises/day-3/simple-gui.md:6 msgid "We will have a number of widgets in our library:" msgstr "" #: src/exercises/day-3/simple-gui.md:8 msgid "`Window`: has a `title` and contains other widgets." msgstr "" #: 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." msgstr "" #: src/exercises/day-3/simple-gui.md:11 msgid "`Label`: has a `label`." msgstr "" #: src/exercises/day-3/simple-gui.md:13 msgid "The widgets will implement a `Widget` trait, see below." msgstr "" #: src/exercises/day-3/simple-gui.md:15 msgid "" "Copy the code below to , fill in the missing " "`draw_into` methods so that you implement the `Widget` trait:" msgstr "" #: src/exercises/day-3/simple-gui.md:23 #: src/exercises/day-3/solutions-morning.md:9 msgid "/// Natural width of `self`.\n" 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" 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" 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\"" 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.\"" msgstr "" #: src/exercises/day-3/simple-gui.md:123 #: src/exercises/day-3/solutions-morning.md:138 msgid "\"Click me!\"" msgstr "" #: src/exercises/day-3/simple-gui.md:124 #: src/exercises/day-3/solutions-morning.md:139 msgid "\"You clicked the button!\"" msgstr "" #: src/exercises/day-3/simple-gui.md:130 msgid "The output of the above program can be something simple like this:" msgstr "" #: src/exercises/day-3/simple-gui.md:142 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:" msgstr "" #: src/exercises/day-3/simple-gui.md:150 msgid "\"left aligned: |{:/width$}|\"" msgstr "" #: src/exercises/day-3/simple-gui.md:156 msgid "" "Using such alignment tricks, you can for example produce output like this:" msgstr "" #: src/exercises/day-3/points-polygons.md:1 msgid "Polygon Struct" msgstr "" #: src/exercises/day-3/points-polygons.md:3 msgid "" "We will create a `Polygon` struct which contain some points. Copy the code " "below to and fill in the missing methods to " "make the tests pass:" msgstr "" #: 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" 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/exercises/day-3/points-polygons.md:117 msgid "" "Since the method signatures are missing from the problem statements, the key " "part of the exercise is to specify those correctly. You don't have to modify " "the tests." msgstr "" #: src/exercises/day-3/points-polygons.md:120 msgid "Other interesting parts of the exercise:" msgstr "" #: src/exercises/day-3/points-polygons.md:122 msgid "" "Derive a `Copy` trait for some structs, as in tests the methods sometimes " "don't borrow their arguments." msgstr "" #: src/exercises/day-3/points-polygons.md:123 msgid "" "Discover that `Add` trait must be implemented for two objects to be addable " "via \"+\". Note that we do not discuss generics until Day 3." msgstr "" #: src/error-handling.md:3 msgid "Error handling in Rust is done using explicit control flow:" msgstr "" #: src/error-handling.md:5 msgid "Functions that can have errors list this in their return type," msgstr "" #: src/error-handling.md:6 msgid "There are no exceptions." msgstr "" #: src/error-handling/panics.md:3 msgid "Rust will trigger a panic if a fatal error happens at runtime:" msgstr "" #: src/error-handling/panics.md:8 msgid "\"v[100]: {}\"" msgstr "\"v[100]: {}\"" #: src/error-handling/panics.md:12 msgid "Panics are for unrecoverable and unexpected errors." msgstr "" #: src/error-handling/panics.md:13 msgid "Panics are symptoms of bugs in the program." msgstr "" #: src/error-handling/panics.md:14 msgid "" "Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." msgstr "" #: src/error-handling/panic-unwind.md:1 msgid "Catching the Stack Unwinding" msgstr "" #: src/error-handling/panic-unwind.md:3 msgid "" "By default, a panic will cause the stack to unwind. The unwinding can be " "caught:" msgstr "" #: src/error-handling/panic-unwind.md:10 msgid "\"hello!\"" msgstr "\"hallo!\"" #: src/error-handling/panic-unwind.md:15 msgid "\"oh no!\"" msgstr "\"åh nej!\"" #: src/error-handling/panic-unwind.md:21 msgid "" "This can be useful in servers which should keep running even if a single " "request crashes." msgstr "" #: src/error-handling/panic-unwind.md:23 msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." msgstr "" #: src/error-handling/result.md:1 msgid "Structured Error Handling with `Result`" msgstr "" #: src/error-handling/result.md:3 msgid "" "We have already seen the `Result` enum. This is used pervasively when errors " "are expected as part of normal operation:" msgstr "" #: src/error-handling/result.md:11 msgid "\"diary.txt\"" msgstr "\"dagbog.txt\"" #: src/error-handling/result.md:16 msgid "\"Dear diary: {contents}\"" msgstr "\"Kære dagbog: {contents}\"" #: src/error-handling/result.md:19 msgid "\"The diary could not be opened: {err}\"" 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." 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. " msgstr "" #: src/error-handling/try-operator.md:1 msgid "Propagating Errors with `?`" 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" msgstr "" #: src/error-handling/try-operator.md:13 msgid "into the much simpler" msgstr "" #: src/error-handling/try-operator.md:19 msgid "We can use this to simplify our error handling code:" 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/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/error-handling/try-operator.md:42 #: src/error-handling/converting-error-types-example.md:44 msgid "\"username or error: {username:?}\"" msgstr "" #: src/error-handling/try-operator.md:50 #: src/error-handling/converting-error-types-example.md:52 msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." msgstr "" #: 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." 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`." msgstr "" #: src/error-handling/try-operator.md:57 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/converting-error-types.md:3 msgid "" "The effective expansion of `?` is a little more complicated than previously " "indicated:" msgstr "" #: src/error-handling/converting-error-types.md:9 msgid "works the same as" msgstr "" #: src/error-handling/converting-error-types.md:18 msgid "" "The `From::from` call here means we attempt to convert the error type to the " "type returned by the function:" msgstr "" #: src/error-handling/converting-error-types-example.md:20 msgid "\"IO error: {e}\"" msgstr "\"IO-fejl: {e}\"" #: src/error-handling/converting-error-types-example.md:21 msgid "\"Found no username in {filename}\"" 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/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." 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." msgstr "" #: src/error-handling/deriving-error-enums.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:" msgstr "" #: src/error-handling/deriving-error-enums.md:13 msgid "\"Could not read: {0}\"" msgstr "" #: src/error-handling/deriving-error-enums.md:15 #: src/error-handling/dynamic-errors.md:13 msgid "\"Found no username in {0}\"" 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}\"" msgstr "" #: src/error-handling/deriving-error-enums.md:32 #: src/error-handling/dynamic-errors.md:29 msgid "\"Error: {err}\"" msgstr "\"Fejl: {err}\"" #: src/error-handling/deriving-error-enums.md:39 msgid "" "`thiserror`'s derive macro automatically implements `std::error::Error`, and " "optionally `Display` (if the `#[error(...)]` attributes are provided) and " "`From` (if the `#[from]` attribute is added). It also works for structs." msgstr "" #: src/error-handling/deriving-error-enums.md:43 msgid "It doesn't affect your public API, which makes it good for libraries." 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." 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." msgstr "" #: src/error-handling/error-contexts.md:3 msgid "" "The widely used [anyhow](https://docs.rs/anyhow/) crate can help you add " "contextual information to your errors and allows you to have fewer custom " "error types:" msgstr "" #: src/error-handling/error-contexts.md:15 msgid "\"Failed to open {path}\"" msgstr "" #: src/error-handling/error-contexts.md:17 msgid "\"Failed to read\"" msgstr "" #: src/error-handling/error-contexts.md:19 msgid "\"Found no username in {path}\"" msgstr "" #: src/error-handling/error-contexts.md:28 msgid "\"Error: {err:?}\"" msgstr "\"Fejl: {err:?}\"" #: src/error-handling/error-contexts.md:35 msgid "`anyhow::Result` is a type alias for `Result`." msgstr "" #: src/error-handling/error-contexts.md:36 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/error-contexts.md:38 msgid "" "Actual error type inside of it can be extracted for examination if necessary." msgstr "" #: src/error-handling/error-contexts.md:39 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/testing.md:3 msgid "Rust and Cargo come with a simple unit test framework:" msgstr "" #: src/testing.md:5 msgid "Unit tests are supported throughout your code." msgstr "" #: src/testing.md:7 msgid "Integration tests are supported via the `tests/` directory." msgstr "" #: src/testing/unit-tests.md:3 msgid "Mark unit tests with `#[test]`:" msgstr "" #: src/testing/unit-tests.md:25 msgid "\"Hello World\"" msgstr "\"Hej verden\"" #: src/testing/unit-tests.md:29 msgid "Use `cargo test` to find and run the unit tests." msgstr "" #: src/testing/test-modules.md:3 msgid "" "Unit tests are often put in a nested module (run tests on the [Playground]" "(https://play.rust-lang.org/)):" msgstr "" #: src/testing/test-modules.md:8 msgid "\"{a} {b}\"" msgstr "\"{a} {b}\"" #: src/testing/test-modules.md:21 msgid "\"foo bar\"" msgstr "\"foo bar\"" #: src/testing/test-modules.md:26 msgid "This lets you unit test private helpers." msgstr "" #: src/testing/test-modules.md:27 msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." msgstr "" #: src/testing/doc-tests.md:3 msgid "Rust has built-in support for documentation tests:" msgstr "" #: src/testing/doc-tests.md:6 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/doc-tests.md:18 msgid "Code blocks in `///` comments are automatically seen as Rust code." msgstr "" #: src/testing/doc-tests.md:19 msgid "The code will be compiled and executed as part of `cargo test`." msgstr "" #: src/testing/doc-tests.md:20 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/integration-tests.md:3 msgid "If you want to test your library as a client, use an integration test." msgstr "" #: src/testing/integration-tests.md:5 msgid "Create a `.rs` file under `tests/`:" msgstr "" #: src/testing/integration-tests.md:16 msgid "These tests only have access to the public API of your crate." msgstr "" #: src/testing/useful-crates.md:1 msgid "Useful crates for writing tests" 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/unsafe.md:3 msgid "The Rust language has two parts:" msgstr "" #: src/unsafe.md:5 msgid "**Safe Rust:** memory safe, no undefined behavior possible." msgstr "" #: src/unsafe.md:6 msgid "" "**Unsafe Rust:** can trigger undefined behavior if preconditions are " "violated." 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." msgstr "" #: src/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.md:14 msgid "Unsafe Rust gives you access to five new capabilities:" msgstr "" #: src/unsafe.md:16 msgid "Dereference raw pointers." msgstr "" #: src/unsafe.md:17 msgid "Access or modify mutable static variables." msgstr "" #: src/unsafe.md:18 msgid "Access `union` fields." msgstr "" #: src/unsafe.md:19 msgid "Call `unsafe` functions, including `extern` functions." msgstr "" #: src/unsafe.md:20 msgid "Implement `unsafe` traits." msgstr "" #: src/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.md:28 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." msgstr "" #: src/unsafe/raw-pointers.md:3 msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" msgstr "" #: src/unsafe/raw-pointers.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/raw-pointers.md:18 msgid "\"r1 is: {}\"" msgstr "\"r1 er: {}\"" #: src/unsafe/raw-pointers.md:20 msgid "\"r2 is: {}\"" msgstr "\"r2 er: {}\"" #: src/unsafe/raw-pointers.md:27 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/raw-pointers.md:31 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/raw-pointers.md:34 msgid "The pointer must be non-null." msgstr "" #: src/unsafe/raw-pointers.md:35 msgid "" "The pointer must be _dereferenceable_ (within the bounds of a single " "allocated object)." msgstr "" #: src/unsafe/raw-pointers.md:36 msgid "The object must not have been deallocated." msgstr "" #: src/unsafe/raw-pointers.md:37 msgid "There must not be concurrent accesses to the same location." msgstr "" #: src/unsafe/raw-pointers.md:38 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/raw-pointers.md:41 msgid "In most cases the pointer must also be properly aligned." msgstr "" #: src/unsafe/mutable-static-variables.md:3 msgid "It is safe to read an immutable static variable:" msgstr "" #: src/unsafe/mutable-static-variables.md:6 msgid "\"Hello, world!\"" msgstr "\"Hej verden!\"" #: src/unsafe/mutable-static-variables.md:9 msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" msgstr "\"HELLO_WORLD: {HELLO_WORLD}\"" #: src/unsafe/mutable-static-variables.md:13 msgid "" "However, since data races can occur, it is unsafe to read and write mutable " "static variables:" msgstr "" #: src/unsafe/mutable-static-variables.md:20 #: src/unsafe/mutable-static-variables.md:26 msgid "// Potential data race!\n" msgstr "" #: src/unsafe/mutable-static-variables.md:26 msgid "\"COUNTER: {COUNTER}\"" msgstr "\"COUNTER: {COUNTER}\"" #: 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." msgstr "" #: src/unsafe/unions.md:3 msgid "Unions are like enums, but you need to track the active field yourself:" msgstr "" #: src/unsafe/unions.md:14 msgid "\"int: {}\"" msgstr "\"int: {}\"" #: src/unsafe/unions.md:15 msgid "\"bool: {}\"" msgstr "\"bool: {}\"" #: src/unsafe/unions.md:15 msgid "// Undefined behavior!\n" msgstr "" #: src/unsafe/unions.md:21 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/unions.md:24 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/calling-unsafe-functions.md:3 msgid "" "A function or method can be marked `unsafe` if it has extra preconditions " "you must uphold to avoid undefined behaviour:" msgstr "" #: src/unsafe/calling-unsafe-functions.md:8 msgid "\"🗻∈🌏\"" msgstr "\"🗻∈🌏\"" #: src/unsafe/calling-unsafe-functions.md:10 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/calling-unsafe-functions.md:13 #: src/unsafe/calling-unsafe-functions.md:14 #: src/unsafe/calling-unsafe-functions.md:15 msgid "\"emoji: {}\"" msgstr "\"emoji: {}\"" #: src/unsafe/calling-unsafe-functions.md:18 msgid "\"char count: {}\"" 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" 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." 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" msgstr "" #: src/unsafe/writing-unsafe-functions.md:22 msgid "// Safe because ...\n" msgstr "" #: src/unsafe/writing-unsafe-functions.md:27 msgid "\"a = {}, b = {}\"" msgstr "" #: src/unsafe/writing-unsafe-functions.md:33 msgid "" "We wouldn't actually use pointers for this because it can be done safely " "with references." msgstr "" #: src/unsafe/writing-unsafe-functions.md:35 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." msgstr "" #: src/unsafe/extern-functions.md:1 msgid "Calling External Code" msgstr "" #: src/unsafe/extern-functions.md:3 msgid "" "Functions from other languages might violate the guarantees of Rust. Calling " "them is thus unsafe:" 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/unsafe/extern-functions.md:13 msgid "// Undefined behavior if abs misbehaves.\n" msgstr "" #: src/unsafe/extern-functions.md:14 msgid "\"Absolute value of -3 according to C: {}\"" 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." msgstr "" #: src/unsafe/extern-functions.md:25 msgid "" "The `\"C\"` in this example is the ABI; [other ABIs are available too]" "(https://doc.rust-lang.org/reference/items/external-blocks.html)." msgstr "" #: src/unsafe/unsafe-traits.md:3 msgid "" "Like with functions, you can mark a trait as `unsafe` if the implementation " "must guarantee particular conditions to avoid undefined behaviour." msgstr "" #: src/unsafe/unsafe-traits.md:6 msgid "" "For example, the `zerocopy` crate has an unsafe trait that looks [something " "like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" msgstr "" #: src/unsafe/unsafe-traits.md:12 msgid "" "/// ...\n" "/// # Safety\n" "/// The type must have a defined representation and no padding.\n" msgstr "" #: src/unsafe/unsafe-traits.md:23 msgid "// Safe because u32 has a defined representation and no padding.\n" msgstr "" #: src/unsafe/unsafe-traits.md:30 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/unsafe-traits.md:33 msgid "" "The actual safety section for `AsBytes` is rather longer and more " "complicated." msgstr "" #: src/unsafe/unsafe-traits.md:35 msgid "The built-in `Send` and `Sync` traits are unsafe." msgstr "" #: src/exercises/day-3/afternoon.md:1 msgid "Day 3: Afternoon Exercises" msgstr "" #: src/exercises/day-3/afternoon.md:3 msgid "Let us build a safe wrapper for reading directory content!" 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." msgstr "" #: src/exercises/day-3/afternoon.md:8 msgid "" "To get started, follow the [running locally](../../cargo/running-locally.md) " "instructions." msgstr "" #: src/exercises/day-3/afternoon.md:14 msgid "" "After looking at the exercise, you can look at the [solution](solutions-" "afternoon.md) provided." msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:3 msgid "" "Rust has great support for calling functions through a _foreign function " "interface_ (FFI). We will use this to build a safe wrapper for the `libc` " "functions you would use from C to read the filenames of a directory." msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:7 msgid "You will want to consult the manual pages:" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:9 msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:10 msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:11 msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.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/exercises/day-3/safe-ffi-wrapper.md:16 msgid "Encoding" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:16 msgid "Use" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:18 msgid "" "[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" "(https://doc.rust-lang.org/std/string/struct.String.html)" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:18 msgid "UTF-8" msgstr "UTF-8" #: src/exercises/day-3/safe-ffi-wrapper.md:18 msgid "Text processing in Rust" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.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/exercises/day-3/safe-ffi-wrapper.md:19 msgid "NUL-terminated" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:19 msgid "Communicating with C functions" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:20 msgid "" "[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " "[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:20 msgid "OS-specific" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:20 msgid "Communicating with the OS" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:22 msgid "You will convert between all these types:" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:24 msgid "" "`&str` to `CString`: you need to allocate space for a trailing `\\0` " "character," msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:25 msgid "`CString` to `*const i8`: you need a pointer to call C functions," 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," msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:27 msgid "" "`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " "unknow data\"," msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.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/exercises/day-3/safe-ffi-wrapper.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/exercises/day-3/safe-ffi-wrapper.md:34 msgid "" "The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " "useful chapter about FFI." msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:45 msgid "" "Copy the code below to and fill in the missing " "functions and methods:" 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" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:64 #: src/exercises/day-3/solutions-afternoon.md:20 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/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" 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 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/exercises/day-3/safe-ffi-wrapper.md:101 #: src/exercises/day-3/solutions-afternoon.md:57 msgid "\"readdir$INODE64\"" msgstr "\"readdir$INODE64\"" #: src/exercises/day-3/safe-ffi-wrapper.md:119 #: src/exercises/day-3/solutions-afternoon.md:75 msgid "" "// Call opendir and return a Ok value if that worked,\n" " // otherwise return Err with a message.\n" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:128 msgid "// Keep calling readdir until we get a NULL pointer back.\n" msgstr "" #: src/exercises/day-3/safe-ffi-wrapper.md:135 #: src/exercises/day-3/solutions-afternoon.md:108 msgid "// Call closedir as needed.\n" 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/exercises/day-3/safe-ffi-wrapper.md:142 #: src/exercises/day-3/solutions-afternoon.md:120 msgid "\"files: {:#?}\"" msgstr "" #: src/android.md:1 msgid "Welcome to Rust in Android" msgstr "" #: src/android.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." 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/setup.md:3 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:" 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/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/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:34 msgid "_hello_rust/src/main.rs_:" msgstr "_hello_rust/src/main.rs_:" #: src/android/build-rules/binary.md:19 src/android/build-rules/library.md:37 msgid "//! Rust demo.\n" msgstr "" #: src/android/build-rules/binary.md:20 src/android/build-rules/library.md:41 msgid "/// Prints a greeting to standard output.\n" msgstr "" #: src/android/build-rules/binary.md:23 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:28 msgid "\"libgreetings\"" msgstr "\"libgreetings\"" #: src/android/build-rules/library.md:22 msgid "\"libtextwrap\"" msgstr "\"libtextwrap\"" #: src/android/build-rules/library.md:29 msgid "\"greetings\"" msgstr "\"greetings\"" #: 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/android/build-rules/library.md:48 msgid "_hello_rust/src/lib.rs_:" msgstr "_hello_rust/src/lib.rs_:" #: src/android/build-rules/library.md:51 msgid "//! Greeting library.\n" msgstr "" #: src/android/build-rules/library.md:52 msgid "/// Greet `name`.\n" msgstr "" #: src/android/build-rules/library.md:55 msgid "\"Hello {name}, it is very nice to meet you!\"" msgstr "" #: src/android/build-rules/library.md:59 msgid "You build, push, and run the binary like before:" msgstr "" #: src/android/build-rules/library.md:61 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: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:52 msgid "Notice that the client does not depend on `libbirthdayservice`." msgstr "" #: src/android/aidl/client.md:54 msgid "Build, push, and run the client on your device:" msgstr "" #: src/android/aidl/client.md:56 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:22 msgid "_hello_rust_logs/src/main.rs_:" msgstr "_hello_rust_logs/src/main.rs_:" #: src/android/logging.md:25 msgid "//! Rust logging demo.\n" msgstr "" #: src/android/logging.md:28 msgid "/// Logs a greeting.\n" msgstr "" #: src/android/logging.md:33 msgid "\"rust\"" msgstr "\"rust\"" #: src/android/logging.md:36 msgid "\"Starting program.\"" msgstr "" #: src/android/logging.md:37 msgid "\"Things are going fine.\"" msgstr "" #: src/android/logging.md:38 msgid "\"Something went wrong!\"" 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:" 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" "```" 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`:" 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: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.md:10 msgid "" "See the [CXX tutorial](https://cxx.rs/tutorial.html) for an full example of " "using this." msgstr "" #: src/android/interoperability/cpp.md:14 msgid "" "At this point, the instructor should switch to the [CXX tutorial](https://" "cxx.rs/tutorial.html)." msgstr "" #: src/android/interoperability/cpp.md:16 msgid "Walk the students through the tutorial step by step." msgstr "" #: src/android/interoperability/cpp.md:18 msgid "" "Highlight how CXX presents a clean interface without unsafe code in _both " "languages_." msgstr "" #: src/android/interoperability/cpp.md:20 msgid "" "Show the correspondence between [Rust and C++ types](https://cxx.rs/bindings." "html):" msgstr "" #: src/android/interoperability/cpp.md:22 msgid "" "Explain how a Rust `String` cannot map to a C++ `std::string` (the latter " "does not uphold the UTF-8 invariant). Show that despite being different " "types, `rust::String` in C++ can be easily constructed from a C++ `std::" "string`, making it very ergonomic to use." msgstr "" #: src/android/interoperability/cpp.md:28 msgid "" "Explain that a Rust function returning `Result` becomes a function " "which throws a `E` exception in C++ (and vice versa)." msgstr "" #: src/android/interoperability/java.md:1 msgid "Interoperability with Java" msgstr "" #: src/android/interoperability/java.md:3 msgid "" "Java can load shared objects via [Java Native Interface (JNI)](https://en." "wikipedia.org/wiki/Java_Native_Interface). The [`jni` crate](https://docs.rs/" "jni/) allows you to create a compatible library." msgstr "" #: src/android/interoperability/java.md:7 msgid "First, we create a Rust function to export to Java:" msgstr "" #: src/android/interoperability/java.md:9 msgid "_interoperability/java/src/lib.rs_:" msgstr "" #: src/android/interoperability/java.md:12 msgid "//! Rust <-> Java FFI demo.\n" msgstr "" #: src/android/interoperability/java.md:17 msgid "/// HelloWorld::hello method implementation.\n" msgstr "" #: src/android/interoperability/java.md:20 msgid "\"system\"" msgstr "\"system\"" #: src/android/interoperability/java.md:26 msgid "\"Hello, {input}!\"" msgstr "" #: 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/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/android/morning.md:3 msgid "" "This is a group exercise: We will look at one of the projects you work with " "and try to integrate some Rust into it. Some suggestions:" msgstr "" #: src/exercises/android/morning.md:6 msgid "Call your AIDL service with a client written in Rust." msgstr "" #: src/exercises/android/morning.md:8 msgid "Move a function from your project to Rust and call it." msgstr "" #: 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/bare-metal.md:1 msgid "Welcome to Bare Metal Rust" msgstr "Velkommen til Rust på det rå jern" #: src/bare-metal.md:3 msgid "" "This is a standalone one-day course about bare-metal Rust, aimed at people " "who are familiar with the basics of Rust (perhaps from completing the " "Comprehensive Rust course), and ideally also have some experience with bare-" "metal programming in some other language such as C." msgstr "" #: src/bare-metal.md:7 msgid "" "Today we will talk about 'bare-metal' Rust: running Rust code without an OS " "underneath us. This will be divided into several parts:" msgstr "" #: src/bare-metal.md:10 msgid "What is `no_std` Rust?" msgstr "" #: src/bare-metal.md:11 msgid "Writing firmware for microcontrollers." msgstr "" #: src/bare-metal.md:12 msgid "Writing bootloader / kernel code for application processors." msgstr "" #: src/bare-metal.md:13 msgid "Some useful crates for bare-metal Rust development." msgstr "" #: src/bare-metal.md:15 msgid "" "For the microcontroller part of the course we will use the [BBC micro:bit]" "(https://microbit.org/) v2 as an example. It's a [development board](https://" "tech.microbit.org/hardware/) based on the Nordic nRF51822 microcontroller " "with some LEDs and buttons, an I2C-connected accelerometer and compass, and " "an on-board SWD debugger." msgstr "" #: src/bare-metal.md:20 msgid "" "To get started, install some tools we'll need later. On gLinux or Debian:" msgstr "" #: src/bare-metal.md:30 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 msgid "On MacOS:" msgstr "På MacOS:" #: src/bare-metal/no_std.md:1 msgid "`no_std`" msgstr "`no_std`" #: src/bare-metal/no_std.md:7 msgid "`core`" msgstr "`core`" #: src/bare-metal/no_std.md:12 src/bare-metal/alloc.md:1 msgid "`alloc`" msgstr "`alloc`" #: src/bare-metal/no_std.md:17 msgid "`std`" msgstr "`std`" #: src/bare-metal/no_std.md:24 msgid "Slices, `&str`, `CStr`" msgstr "" #: src/bare-metal/no_std.md:25 msgid "`NonZeroU8`..." msgstr "`NonZeroU8`..." #: src/bare-metal/no_std.md:26 msgid "`Option`, `Result`" msgstr "`Option`, `Result`" #: src/bare-metal/no_std.md:27 msgid "`Display`, `Debug`, `write!`..." msgstr "`Display`, `Debug`, `write!`..." #: src/bare-metal/no_std.md:29 msgid "`panic!`, `assert_eq!`..." msgstr "`panic!`, `assert_eq!`..." #: src/bare-metal/no_std.md:30 msgid "`NonNull` and all the usual pointer-related functions" msgstr "" #: src/bare-metal/no_std.md:31 msgid "`Future` and `async`/`await`" msgstr "`Future` og `async`/`await`" #: src/bare-metal/no_std.md:32 msgid "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." msgstr "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." #: src/bare-metal/no_std.md:33 msgid "`Duration`" msgstr "`Duration`" #: src/bare-metal/no_std.md:38 msgid "`Box`, `Cow`, `Arc`, `Rc`" msgstr "`Box`, `Cow`, `Arc`, `Rc`" #: src/bare-metal/no_std.md:39 msgid "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" msgstr "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" #: src/bare-metal/no_std.md:40 msgid "`String`, `CString`, `format!`" msgstr "`String`, `CString`, `format!`" #: src/bare-metal/no_std.md:45 msgid "`Error`" msgstr "`Error`" #: src/bare-metal/no_std.md:47 msgid "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" msgstr "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" #: src/bare-metal/no_std.md:48 msgid "`File` and the rest of `fs`" msgstr "`File` og resten af `fs`" #: src/bare-metal/no_std.md:49 msgid "`println!`, `Read`, `Write`, `Stdin`, `Stdout` and the rest of `io`" msgstr "`println!`, `Read`, `Write`, `Stdin`, `Stdout` og resten af `io`" #: src/bare-metal/no_std.md:50 msgid "`Path`, `OsString`" msgstr "`Path`, `OsString`" #: src/bare-metal/no_std.md:51 msgid "`net`" msgstr "`net`" #: src/bare-metal/no_std.md:52 msgid "`Command`, `Child`, `ExitCode`" msgstr "`Command`, `Child`, `ExitCode`" #: src/bare-metal/no_std.md:53 msgid "`spawn`, `sleep` and the rest of `thread`" msgstr "`spawn`, `sleep` og resten af `thread`" #: src/bare-metal/no_std.md:54 msgid "`SystemTime`, `Instant`" msgstr "`SystemTime`, `Instant`" #: src/bare-metal/no_std.md:62 msgid "`HashMap` depends on RNG." msgstr "" #: src/bare-metal/no_std.md:63 msgid "`std` re-exports the contents of both `core` and `alloc`." msgstr "" #: src/bare-metal/minimal.md:1 msgid "A minimal `no_std` program" msgstr "" #: src/bare-metal/minimal.md:17 msgid "This will compile to an empty binary." msgstr "" #: src/bare-metal/minimal.md:18 msgid "`std` provides a panic handler; without it we must provide our own." msgstr "" #: src/bare-metal/minimal.md:19 msgid "It can also be provided by another crate, such as `panic-halt`." msgstr "" #: src/bare-metal/minimal.md:20 msgid "" "Depending on the target, you may need to compile with `panic = \"abort\"` to " "avoid an error about `eh_personality`." msgstr "" #: src/bare-metal/minimal.md:22 msgid "" "Note that there is no `main` or any other entry point; it's up to you to " "define your own entry point. This will typically involve a linker script and " "some assembly code to set things up ready for Rust code to run." msgstr "" #: src/bare-metal/alloc.md:3 msgid "" "To use `alloc` you must implement a [global (heap) allocator](https://doc." "rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html)." msgstr "" #: src/bare-metal/alloc.md:23 msgid "" "// Safe because `HEAP` is only used here and `entry` is only called once.\n" msgstr "" "// Safe because `HEAP` is only used here and `entry` is only called once.\n" #: src/bare-metal/alloc.md:25 msgid "// Give the allocator some memory to allocate.\n" msgstr "// Give the allocator some memory to allocate.\n" #: src/bare-metal/alloc.md:31 msgid "// Now we can do things that require heap allocation.\n" msgstr "// Now we can do things that require heap allocation.\n" #: src/bare-metal/alloc.md:33 msgid "\"A string\"" msgstr "\"En streng\"" #: src/bare-metal/alloc.md:39 msgid "" "`buddy_system_allocator` is a third-party crate implementing a basic buddy " "system allocator. Other crates are available, or you can write your own or " "hook into your existing allocator." msgstr "" #: src/bare-metal/alloc.md:41 msgid "" "The const parameter of `LockedHeap` is the max order of the allocator; i.e. " "in this case it can allocate regions of up to 2\\*\\*32 bytes." msgstr "" #: src/bare-metal/alloc.md:43 msgid "" "If any crate in your dependency tree depends on `alloc` then you must have " "exactly one global allocator defined in your binary. Usually this is done in " "the top-level binary crate." msgstr "" #: src/bare-metal/alloc.md:45 msgid "" "`extern crate panic_halt as _` is necessary to ensure that the `panic_halt` " "crate is linked in so we get its panic handler." msgstr "" #: src/bare-metal/alloc.md:47 msgid "This example will build but not run, as it doesn't have an entry point." msgstr "" #: src/bare-metal/microcontrollers.md:3 msgid "" "The `cortex_m_rt` crate provides (among other things) a reset handler for " "Cortex M microcontrollers." msgstr "" #: src/bare-metal/microcontrollers.md:21 msgid "" "Next we'll look at how to access peripherals, with increasing levels of " "abstraction." msgstr "" #: src/bare-metal/microcontrollers.md:25 msgid "" "The `cortex_m_rt::entry` macro requires that the function have type `fn() -" "> !`, because returning to the reset handler doesn't make sense." msgstr "" #: src/bare-metal/microcontrollers.md:27 msgid "Run the example with `cargo embed --bin minimal`" msgstr "" #: src/bare-metal/microcontrollers/mmio.md:3 msgid "" "Most microcontrollers access peripherals via memory-mapped IO. Let's try " "turning on an LED on our micro:bit:" msgstr "" #: src/bare-metal/microcontrollers/mmio.md:16 msgid "/// GPIO port 0 peripheral address\n" msgstr "/// GPIO port 0 peripheral address\n" #: src/bare-metal/microcontrollers/mmio.md:19 msgid "// GPIO peripheral offsets\n" msgstr "// GPIO peripheral offsets\n" #: src/bare-metal/microcontrollers/mmio.md:24 msgid "// PIN_CNF fields\n" msgstr "// PIN_CNF fields\n" #: src/bare-metal/microcontrollers/mmio.md:34 #: src/bare-metal/microcontrollers/pacs.md:21 #: src/bare-metal/microcontrollers/hals.md:25 msgid "// Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" msgstr "// Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" #: src/bare-metal/microcontrollers/mmio.md:37 #: src/bare-metal/microcontrollers/mmio.md:51 msgid "" "// Safe because the pointers are to valid peripheral control registers, and\n" " // no aliases exist.\n" msgstr "" "// Safe because the pointers are to valid peripheral control registers, and\n" " // no aliases exist.\n" #: src/bare-metal/microcontrollers/mmio.md:48 #: src/bare-metal/microcontrollers/pacs.md:39 #: src/bare-metal/microcontrollers/hals.md:29 msgid "// Set pin 28 low and pin 21 high to turn the LED on.\n" msgstr "// Set pin 28 low and pin 21 high to turn the LED on.\n" #: src/bare-metal/microcontrollers/mmio.md:64 msgid "" "GPIO 0 pin 21 is connected to the first column of the LED matrix, and pin 28 " "to the first row." msgstr "" #: src/bare-metal/microcontrollers/mmio.md:66 #: src/bare-metal/microcontrollers/pacs.md:59 #: src/bare-metal/microcontrollers/hals.md:43 #: src/bare-metal/microcontrollers/board-support.md:34 msgid "Run the example with:" msgstr "" #: src/bare-metal/microcontrollers/pacs.md:1 msgid "Peripheral Access Crates" msgstr "" #: src/bare-metal/microcontrollers/pacs.md:3 msgid "" "[`svd2rust`](https://crates.io/crates/svd2rust) generates mostly-safe Rust " "wrappers for memory-mapped peripherals from [CMSIS-SVD](https://www.keil.com/" "pack/doc/CMSIS/SVD/html/index.html) files." msgstr "" #: src/bare-metal/microcontrollers/pacs.md:49 msgid "" "SVD (System View Description) files are XML files typically provided by " "silicon vendors which describe the memory map of the device." msgstr "" #: src/bare-metal/microcontrollers/pacs.md:51 msgid "" "They are organised by peripheral, register, field and value, with names, " "descriptions, addresses and so on." msgstr "" #: src/bare-metal/microcontrollers/pacs.md:53 msgid "" "SVD files are often buggy and incomplete, so there are various projects " "which patch the mistakes, add missing details, and publish the generated " "crates." msgstr "" #: src/bare-metal/microcontrollers/pacs.md:55 msgid "`cortex-m-rt` provides the vector table, among other things." msgstr "" #: src/bare-metal/microcontrollers/pacs.md:56 msgid "" "If you `cargo install cargo-binutils` then you can run `cargo objdump --bin " "pac -- -d --no-show-raw-insn` to see the resulting binary." msgstr "" #: src/bare-metal/microcontrollers/hals.md:1 msgid "HAL crates" msgstr "" #: src/bare-metal/microcontrollers/hals.md:3 msgid "" "[HAL crates](https://github.com/rust-embedded/awesome-embedded-rust#hal-" "implementation-crates) for many microcontrollers provide wrappers around " "various peripherals. These generally implement traits from [`embedded-hal`]" "(https://crates.io/crates/embedded-hal)." msgstr "" #: src/bare-metal/microcontrollers/hals.md:22 msgid "// Create HAL wrapper for GPIO port 0.\n" msgstr "" #: src/bare-metal/microcontrollers/hals.md:39 msgid "" "`set_low` and `set_high` are methods on the `embedded_hal` `OutputPin` trait." msgstr "" #: src/bare-metal/microcontrollers/hals.md:40 msgid "" "HAL crates exist for many Cortex-M and RISC-V devices, including various " "STM32, GD32, nRF, NXP, MSP430, AVR and PIC microcontrollers." msgstr "" #: src/bare-metal/microcontrollers/board-support.md:1 msgid "Board support crates" msgstr "" #: src/bare-metal/microcontrollers/board-support.md:3 msgid "" "Board support crates provide a further level of wrapping for a specific " "board for convenience." msgstr "" #: src/bare-metal/microcontrollers/board-support.md:28 msgid "" "In this case the board support crate is just providing more useful names, " "and a bit of initialisation." msgstr "" #: src/bare-metal/microcontrollers/board-support.md:30 msgid "" "The crate may also include drivers for some on-board devices outside of the " "microcontroller itself." msgstr "" #: src/bare-metal/microcontrollers/board-support.md:32 msgid "`microbit-v2` includes a simple driver for the LED matrix." msgstr "" #: src/bare-metal/microcontrollers/type-state.md:1 msgid "The type state pattern" msgstr "" #: src/bare-metal/microcontrollers/type-state.md:11 msgid "// let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" msgstr "// let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" #: src/bare-metal/microcontrollers/type-state.md:19 msgid "// pin_input.is_high(); // Error, moved.\n" msgstr "// pin_input.is_high(); // Error, moved.\n" #: src/bare-metal/microcontrollers/type-state.md:32 msgid "" "Pins don't implement `Copy` or `Clone`, so only one instance of each can " "exist. Once a pin is moved out of the port struct nobody else can take it." msgstr "" #: src/bare-metal/microcontrollers/type-state.md:34 msgid "" "Changing the configuration of a pin consumes the old pin instance, so you " "can’t keep use the old instance afterwards." msgstr "" #: src/bare-metal/microcontrollers/type-state.md:36 msgid "" "The type of a value indicates the state that it is in: e.g. in this case, " "the configuration state of a GPIO pin. This encodes the state machine into " "the type system, and ensures that you don't try to use a pin in a certain " "way without properly configuring it first. Illegal state transitions are " "caught at compile time." msgstr "" #: src/bare-metal/microcontrollers/type-state.md:40 msgid "" "You can call `is_high` on an input pin and `set_high` on an output pin, but " "not vice-versa." msgstr "" #: src/bare-metal/microcontrollers/type-state.md:41 msgid "Many HAL crates follow this pattern." msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:1 msgid "`embedded-hal`" msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:3 msgid "" "The [`embedded-hal`](https://crates.io/crates/embedded-hal) crate provides a " "number of traits covering common microcontroller peripherals." msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:6 msgid "GPIO" msgstr "GPIO" #: src/bare-metal/microcontrollers/embedded-hal.md:7 msgid "ADC" msgstr "ADC" #: src/bare-metal/microcontrollers/embedded-hal.md:8 msgid "I2C, SPI, UART, CAN" msgstr "I2C, SPI, UART, CAN" #: src/bare-metal/microcontrollers/embedded-hal.md:9 msgid "RNG" msgstr "RNG" #: src/bare-metal/microcontrollers/embedded-hal.md:10 msgid "Timers" msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:11 msgid "Watchdogs" msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:13 msgid "" "Other crates then implement [drivers](https://github.com/rust-embedded/" "awesome-embedded-rust#driver-crates) in terms of these traits, e.g. an " "accelerometer driver might need an I2C or SPI bus implementation." msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:19 msgid "" "There are implementations for many microcontrollers, as well as other " "platforms such as Linux on Raspberry Pi." msgstr "" #: src/bare-metal/microcontrollers/embedded-hal.md:21 msgid "" "There is work in progress on an `async` version of `embedded-hal`, but it " "isn't stable yet." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:1 msgid "`probe-rs`, `cargo-embed`" msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:3 msgid "" "[probe-rs](https://probe.rs/) is a handy toolset for embedded debugging, " "like OpenOCD but better integrated." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:6 msgid "SWD" msgstr "SWD" #: src/bare-metal/microcontrollers/probe-rs.md:6 msgid "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 " 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." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:16 msgid "" "[CMSIS-DAP](https://arm-software.github.io/CMSIS_5/DAP/html/index.html) is " "an Arm standard protocol over USB for an in-circuit debugger to access the " "CoreSight Debug Access Port of various Arm Cortex processors. It's what the " "on-board debugger on the BBC micro:bit uses." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:19 msgid "" "ST-Link is a range of in-circuit debuggers from ST Microelectronics, J-Link " "is a range from SEGGER." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:21 msgid "" "The Debug Access Port is usually either a 5-pin JTAG interface or 2-pin " "Serial Wire Debug." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:22 msgid "" "probe-rs is a library which you can integrate into your own tools if you " "want to." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:23 msgid "" "The [Microsoft Debug Adapter Protocol](https://microsoft.github.io/debug-" "adapter-protocol/) lets VSCode and other IDEs debug code running on any " "supported microcontroller." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:25 msgid "cargo-embed is a binary built using the probe-rs library." msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md:26 msgid "" "RTT (Real Time Transfers) is a mechanism to transfer data between the debug " "host and the target through a number of ringbuffers." msgstr "" #: src/bare-metal/microcontrollers/debugging.md:3 msgid "Embed.toml:" msgstr "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 "" #: src/bare-metal/microcontrollers/debugging.md:19 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:27 msgid "In GDB, try running:" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:1 #: src/bare-metal/aps/other-projects.md:1 msgid "Other projects" msgstr "Andre projekter" #: src/bare-metal/microcontrollers/other-projects.md:3 msgid "[RTIC](https://rtic.rs/)" msgstr "[RTIC](https://rtic.rs/)" #: src/bare-metal/microcontrollers/other-projects.md:4 msgid "\"Real-Time Interrupt-driven Concurrency\"" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:5 msgid "" "Shared resource management, message passing, task scheduling, timer queue" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:6 msgid "[Embassy](https://embassy.dev/)" msgstr "[Embassy](https://embassy.dev/)" #: src/bare-metal/microcontrollers/other-projects.md:7 msgid "`async` executors with priorities, timers, networking, USB" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:8 msgid "[TockOS](https://www.tockos.org/documentation/getting-started)" msgstr "[TockOS](https://www.tockos.org/documentation/getting-started)" #: src/bare-metal/microcontrollers/other-projects.md:9 msgid "" "Security-focused RTOS with preemptive scheduling and Memory Protection Unit " "support" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:10 msgid "[Hubris](https://hubris.oxide.computer/)" msgstr "[Hubris](https://hubris.oxide.computer/)" #: src/bare-metal/microcontrollers/other-projects.md:11 msgid "" "Microkernel RTOS from Oxide Computer Company with memory protection, " "unprivileged drivers, IPC" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:12 msgid "[Bindings for FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" msgstr "[Bindinger til FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" #: src/bare-metal/microcontrollers/other-projects.md:13 msgid "" "Some platforms have `std` implementations, e.g. [esp-idf](https://esp-rs." "github.io/book/overview/using-the-standard-library.html)." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:18 msgid "RTIC can be considered either an RTOS or a concurrency framework." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:19 msgid "It doesn't include any HALs." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:20 msgid "" "It uses the Cortex-M NVIC (Nested Virtual Interrupt Controller) for " "scheduling rather than a proper kernel." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:22 msgid "Cortex-M only." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:23 msgid "" "Google uses TockOS on the Haven microcontroller for Titan security keys." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md:24 msgid "" "FreeRTOS is mostly written in C, but there are Rust bindings for writing " "applications." msgstr "" #: src/exercises/bare-metal/morning.md:3 msgid "" "We will read the direction from an I2C compass, and log the readings to a " "serial port." msgstr "" #: src/exercises/bare-metal/compass.md:3 msgid "" "We will read the direction from an I2C compass, and log the readings to a " "serial port. If you have time, try displaying it on the LEDs somehow too, or " "use the buttons somehow." msgstr "" #: src/exercises/bare-metal/compass.md:6 msgid "Hints:" msgstr "" #: src/exercises/bare-metal/compass.md:8 msgid "" "Check the documentation for the [`lsm303agr`](https://docs.rs/lsm303agr/" "latest/lsm303agr/) and [`microbit-v2`](https://docs.rs/microbit-v2/latest/" "microbit/) crates, as well as the [micro:bit hardware](https://tech.microbit." "org/hardware/)." msgstr "" #: src/exercises/bare-metal/compass.md:11 msgid "" "The LSM303AGR Inertial Measurement Unit is connected to the internal I2C bus." msgstr "" #: src/exercises/bare-metal/compass.md:12 msgid "" "TWI is another name for I2C, so the I2C master peripheral is called TWIM." msgstr "" #: src/exercises/bare-metal/compass.md:13 msgid "" "The LSM303AGR driver needs something implementing the `embedded_hal::" "blocking::i2c::WriteRead` trait. The [`microbit::hal::Twim`](https://docs.rs/" "microbit-v2/latest/microbit/hal/struct.Twim.html) struct implements this." msgstr "" #: src/exercises/bare-metal/compass.md:17 msgid "" "You have a [`microbit::Board`](https://docs.rs/microbit-v2/latest/microbit/" "struct.Board.html) struct with fields for the various pins and peripherals." msgstr "" #: src/exercises/bare-metal/compass.md:19 msgid "" "You can also look at the [nRF52833 datasheet](https://infocenter.nordicsemi." "com/pdf/nRF52833_PS_v1.5.pdf) if you want, but it shouldn't be necessary for " "this exercise." msgstr "" #: src/exercises/bare-metal/compass.md:23 msgid "" "Download the [exercise template](../../comprehensive-rust-exercises.zip) and " "look in the `compass` directory for the following files." msgstr "" #: src/exercises/bare-metal/compass.md:26 src/exercises/bare-metal/rtc.md:19 msgid "_src/main.rs_:" msgstr "_src/main.rs_:" #: src/exercises/bare-metal/compass.md:44 #: src/exercises/bare-metal/solutions-morning.md:32 msgid "// Configure serial port.\n" msgstr "" #: src/exercises/bare-metal/compass.md:52 msgid "" "// Set up the I2C controller and Inertial Measurement Unit.\n" " // TODO\n" msgstr "" #: src/exercises/bare-metal/compass.md:55 #: src/exercises/bare-metal/solutions-morning.md:56 msgid "\"Ready.\"" msgstr "" #: src/exercises/bare-metal/compass.md:58 msgid "" "// Read compass data and log it to the serial port.\n" " // TODO\n" msgstr "" #: src/exercises/bare-metal/compass.md:64 src/exercises/bare-metal/rtc.md:385 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 "" #: src/exercises/bare-metal/compass.md:118 msgid "" "Or on Mac OS something like (the device name may be slightly different):" msgstr "" #: src/exercises/bare-metal/compass.md:124 msgid "Use Ctrl+A Ctrl+Q to quit picocom." msgstr "" #: src/bare-metal/aps.md:1 msgid "Application processors" msgstr "" #: src/bare-metal/aps.md:3 msgid "" "So far we've talked about microcontrollers, such as the Arm Cortex-M series. " "Now let's try writing something for Cortex-A. For simplicity we'll just work " "with QEMU's aarch64 ['virt'](https://qemu-project.gitlab.io/qemu/system/arm/" "virt.html) board." msgstr "" #: src/bare-metal/aps.md:9 msgid "" "Broadly speaking, microcontrollers don't have an MMU or multiple levels of " "privilege (exception levels on Arm CPUs, rings on x86), while application " "processors do." msgstr "" #: src/bare-metal/aps.md:11 msgid "" "QEMU supports emulating various different machines or board models for each " "architecture. The 'virt' board doesn't correspond to any particular real " "hardware, but is designed purely for virtual machines." msgstr "" #: src/bare-metal/aps/entry-point.md:3 msgid "" "Before we can start running Rust code, we need to do some initialisation." msgstr "" #: src/bare-metal/aps/entry-point.md:5 msgid "" "```armasm\n" ".section .init.entry, \"ax\"\n" ".global entry\n" "entry:\n" " /*\n" " * Load and apply the memory management configuration, ready to enable " "MMU and\n" " * caches.\n" " */\n" " adrp x30, idmap\n" " msr ttbr0_el1, x30\n" "\n" " mov_i x30, .Lmairval\n" " msr mair_el1, x30\n" "\n" " mov_i x30, .Ltcrval\n" " /* Copy the supported PA range into TCR_EL1.IPS. */\n" " mrs x29, id_aa64mmfr0_el1\n" " bfi x30, x29, #32, #4\n" "\n" " msr tcr_el1, x30\n" "\n" " mov_i x30, .Lsctlrval\n" "\n" " /*\n" " * Ensure everything before this point has completed, then invalidate " "any\n" " * potentially stale local TLB entries before they start being used.\n" " */\n" " isb\n" " tlbi vmalle1\n" " ic iallu\n" " dsb nsh\n" " isb\n" "\n" " /*\n" " * Configure sctlr_el1 to enable MMU and cache and don't proceed until " "this\n" " * has completed.\n" " */\n" " msr sctlr_el1, x30\n" " isb\n" "\n" " /* Disable trapping floating point access in EL1. */\n" " mrs x30, cpacr_el1\n" " orr x30, x30, #(0x3 << 20)\n" " msr cpacr_el1, x30\n" " isb\n" "\n" " /* Zero out the bss section. */\n" " adr_l x29, bss_begin\n" " adr_l x30, bss_end\n" "0: cmp x29, x30\n" " b.hs 1f\n" " stp xzr, xzr, [x29], #16\n" " b 0b\n" "\n" "1: /* Prepare the stack. */\n" " adr_l x30, boot_stack_end\n" " mov sp, x30\n" "\n" " /* Set up exception vector. */\n" " adr x30, vector_table_el1\n" " msr vbar_el1, x30\n" "\n" " /* Call into Rust code. */\n" " bl main\n" "\n" " /* Loop forever waiting for interrupts. */\n" "2: wfi\n" " b 2b\n" "```" msgstr "" #: src/bare-metal/aps/entry-point.md:77 msgid "" "This is the same as it would be for C: initialising the processor state, " "zeroing the BSS, and setting up the stack pointer." msgstr "" #: src/bare-metal/aps/entry-point.md:79 msgid "" "The BSS (block starting symbol, for historical reasons) is the part of the " "object file which containing statically allocated variables which are " "initialised to zero. They are omitted from the image, to avoid wasting space " "on zeroes. The compiler assumes that the loader will take care of zeroing " "them." msgstr "" #: src/bare-metal/aps/entry-point.md:83 msgid "" "The BSS may already be zeroed, depending on how memory is initialised and " "the image is loaded, but we zero it to be sure." msgstr "" #: src/bare-metal/aps/entry-point.md:85 msgid "" "We need to enable the MMU and cache before reading or writing any memory. If " "we don't:" msgstr "" #: src/bare-metal/aps/entry-point.md:86 msgid "" "Unaligned accesses will fault. We build the Rust code for the `aarch64-" "unknown-none` target which sets `+strict-align` to prevent the compiler " "generating unaligned accesses, so it should be fine in this case, but this " "is not necessarily the case in general." msgstr "" #: src/bare-metal/aps/entry-point.md:89 msgid "" "If it were running in a VM, this can lead to cache coherency issues. The " "problem is that the VM is accessing memory directly with the cache disabled, " "while the host has cacheable aliases to the same memory. Even if the host " "doesn't explicitly access the memory, speculative accesses can lead to cache " "fills, and then changes from one or the other will get lost when the cache " "is cleaned or the VM enables the cache. (Cache is keyed by physical address, " "not VA or IPA.)" msgstr "" #: src/bare-metal/aps/entry-point.md:94 msgid "" "For simplicity, we just use a hardcoded pagetable (see `idmap.S`) which " "identity maps the first 1 GiB of address space for devices, the next 1 GiB " "for DRAM, and another 1 GiB higher up for more devices. This matches the " "memory layout that QEMU uses." msgstr "" #: src/bare-metal/aps/entry-point.md:97 msgid "" "We also set up the exception vector (`vbar_el1`), which we'll see more about " "later." msgstr "" #: src/bare-metal/aps/entry-point.md:98 msgid "" "All examples this afternoon assume we will be running at exception level 1 " "(EL1). If you need to run at a different exception level you'll need to " "modify `entry.S` accordingly." msgstr "" #: src/bare-metal/aps/inline-assembly.md:1 msgid "Inline assembly" msgstr "" #: src/bare-metal/aps/inline-assembly.md:3 msgid "" "Sometimes we need to use assembly to do things that aren't possible with " "Rust code. For example, to make an " 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:" msgstr "" #: src/bare-metal/aps/inline-assembly.md:19 msgid "" "// Safe because this only uses the declared registers and doesn't do\n" " // anything with memory.\n" msgstr "" #: src/bare-metal/aps/inline-assembly.md:22 msgid "\"hvc #0\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:23 msgid "\"w0\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:24 msgid "\"w1\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:25 msgid "\"w2\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:26 msgid "\"w3\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:27 msgid "\"w4\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:28 msgid "\"w5\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:29 msgid "\"w6\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:30 msgid "\"w7\"" msgstr "" #: src/bare-metal/aps/inline-assembly.md:39 msgid "" "(If you actually want to do this, use the [`smccc`](https://crates.io/crates/" "smccc) crate which has wrappers for all these functions.)" msgstr "" #: src/bare-metal/aps/inline-assembly.md:43 msgid "" "PSCI is the Arm Power State Coordination Interface, a standard set of " "functions to manage system and CPU power states, among other things. It is " "implemented by EL3 firmware and hypervisors on many systems." msgstr "" #: src/bare-metal/aps/inline-assembly.md:46 msgid "" "The `0 => _` syntax means initialise the register to 0 before running the " "inline assembly code, and ignore its contents afterwards. We need to use " "`inout` rather than `in` because the call could potentially clobber the " "contents of the registers." msgstr "" #: src/bare-metal/aps/inline-assembly.md:49 msgid "" "This `main` function needs to be `#[no_mangle]` and `extern \"C\"` because " "it is called from our entry point in `entry.S`." msgstr "" #: src/bare-metal/aps/inline-assembly.md:51 msgid "" "`_x0`–`_x3` are the values of registers `x0`–`x3`, which are conventionally " "used by the bootloader to pass things like a pointer to the device tree. " "According to the standard aarch64 calling convention (which is what `extern " "\"C\"` specifies to use), registers `x0`–`x7` are used for the first 8 " "arguments passed to a function, so `entry.S` doesn't need to do anything " "special except make sure it doesn't change these registers." msgstr "" #: src/bare-metal/aps/inline-assembly.md:56 msgid "" "Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" "examples`." msgstr "" #: src/bare-metal/aps/mmio.md:1 msgid "Volatile memory access for MMIO" msgstr "" #: src/bare-metal/aps/mmio.md:3 msgid "Use `pointer::read_volatile` and `pointer::write_volatile`." msgstr "" #: src/bare-metal/aps/mmio.md:4 msgid "Never hold a reference." msgstr "" #: src/bare-metal/aps/mmio.md:5 msgid "" "`addr_of!` lets you get fields of structs without creating an intermediate " "reference." msgstr "" #: src/bare-metal/aps/mmio.md:9 msgid "" "Volatile access: read or write operations may have side-effects, so prevent " "the compiler or hardware from reordering, duplicating or eliding them." msgstr "" #: src/bare-metal/aps/mmio.md:11 msgid "" "Usually if you write and then read, e.g. via a mutable reference, the " "compiler may assume that the value read is the same as the value just " "written, and not bother actually reading memory." msgstr "" #: src/bare-metal/aps/mmio.md:13 msgid "" "Some existing crates for volatile access to hardware do hold references, but " "this is unsound. Whenever a reference exist, the compiler may choose to " "dereference it." msgstr "" #: src/bare-metal/aps/mmio.md:15 msgid "" "Use the `addr_of!` macro to get struct field pointers from a pointer to the " "struct." msgstr "" #: src/bare-metal/aps/uart.md:1 msgid "Let's write a UART driver" msgstr "" #: src/bare-metal/aps/uart.md:3 msgid "" "The QEMU 'virt' machine has a [PL011](https://developer.arm.com/" "documentation/ddi0183/g) UART, so let's write a driver for that." msgstr "" #: src/bare-metal/aps/uart.md:9 msgid "/// Minimal driver for a PL011 UART.\n" msgstr "" #: src/bare-metal/aps/uart.md:17 src/bare-metal/aps/better-uart/driver.md:13 msgid "" "/// Constructs a new instance of the UART driver for a PL011 device at the\n" " /// given base address.\n" " ///\n" " /// # Safety\n" " ///\n" " /// The given base address must point to the 8 MMIO control registers of " "a\n" " /// PL011 device, which must be mapped into the address space of the " "process\n" " /// as device memory and not have any other aliases.\n" msgstr "" #: src/bare-metal/aps/uart.md:29 src/bare-metal/aps/better-uart/driver.md:27 #: src/exercises/bare-metal/rtc.md:336 msgid "/// Writes a single byte to the UART.\n" msgstr "/// Writes a single byte to the UART.\n" #: src/bare-metal/aps/uart.md:31 src/bare-metal/aps/better-uart/driver.md:29 #: src/exercises/bare-metal/rtc.md:338 msgid "// Wait until there is room in the TX buffer.\n" msgstr "// Wait until there is room in the TX buffer.\n" #: src/bare-metal/aps/uart.md:34 src/bare-metal/aps/uart.md:46 msgid "" "// Safe because we know that the base address points to the control\n" " // registers of a PL011 device which is appropriately mapped.\n" msgstr "" #: src/bare-metal/aps/uart.md:37 src/bare-metal/aps/better-uart/driver.md:35 #: src/exercises/bare-metal/rtc.md:344 msgid "// Write to the TX buffer.\n" msgstr "// Write to the TX buffer.\n" #: src/bare-metal/aps/uart.md:41 src/bare-metal/aps/better-uart/driver.md:39 #: src/exercises/bare-metal/rtc.md:348 msgid "// Wait until the UART is no longer busy.\n" msgstr "// Wait until the UART is no longer busy.\n" #: src/bare-metal/aps/uart.md:55 msgid "" "Note that `Uart::new` is unsafe while the other methods are safe. This is " "because as long as the caller of `Uart::new` guarantees that its safety " "requirements are met (i.e. that there is only ever one instance of the " "driver for a given UART, and nothing else aliasing its address space), then " "it is always safe to call `write_byte` later because we can assume the " "necessary preconditions." msgstr "" #: src/bare-metal/aps/uart.md:60 msgid "" "We could have done it the other way around (making `new` safe but " "`write_byte` unsafe), but that would be much less convenient to use as every " "place that calls `write_byte` would need to reason about the safety" msgstr "" #: src/bare-metal/aps/uart.md:63 msgid "" "This is a common pattern for writing safe wrappers of unsafe code: moving " "the burden of proof for soundness from a large number of places to a smaller " "number of places." msgstr "" #: src/bare-metal/aps/uart/traits.md:1 msgid "More traits" msgstr "" #: src/bare-metal/aps/uart/traits.md:3 msgid "" "We derived the `Debug` trait. It would be useful to implement a few more " "traits too." msgstr "" #: src/bare-metal/aps/uart/traits.md:16 src/exercises/bare-metal/rtc.md:379 #: src/exercises/bare-metal/solutions-afternoon.md:231 msgid "" "// Safe because it just contains a pointer to device memory, which can be\n" "// accessed from any context.\n" msgstr "" "// Safe because it just contains a pointer to device memory, which can be\n" "// accessed from any context.\n" #: src/bare-metal/aps/uart/traits.md:24 msgid "" "Implementing `Write` lets us use the `write!` and `writeln!` macros with our " "`Uart` type." msgstr "" #: src/bare-metal/aps/uart/traits.md:25 msgid "" "Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" "examples`." msgstr "" #: src/bare-metal/aps/better-uart.md:1 msgid "A better UART driver" msgstr "" #: src/bare-metal/aps/better-uart.md:3 msgid "" "The PL011 actually has [a bunch more registers](https://developer.arm.com/" "documentation/ddi0183/g/programmers-model/summary-of-registers), and adding " "offsets to construct pointers to access them is error-prone and hard to " "read. Plus, some of them are bit fields which would be nice to access in a " "structured way." msgstr "" #: src/bare-metal/aps/better-uart.md:7 msgid "Offset" msgstr "" #: src/bare-metal/aps/better-uart.md:7 msgid "Register name" msgstr "" #: src/bare-metal/aps/better-uart.md:7 msgid "Width" msgstr "" #: src/bare-metal/aps/better-uart.md:9 msgid "0x00" msgstr "" #: src/bare-metal/aps/better-uart.md:9 msgid "DR" msgstr "" #: src/bare-metal/aps/better-uart.md:9 msgid "12" msgstr "" #: src/bare-metal/aps/better-uart.md:10 msgid "0x04" msgstr "" #: src/bare-metal/aps/better-uart.md:10 msgid "RSR" msgstr "" #: src/bare-metal/aps/better-uart.md:10 msgid "4" msgstr "" #: src/bare-metal/aps/better-uart.md:11 msgid "0x18" msgstr "" #: src/bare-metal/aps/better-uart.md:11 msgid "FR" msgstr "" #: src/bare-metal/aps/better-uart.md:11 msgid "9" msgstr "" #: src/bare-metal/aps/better-uart.md:12 msgid "0x20" msgstr "" #: src/bare-metal/aps/better-uart.md:12 msgid "ILPR" msgstr "" #: src/bare-metal/aps/better-uart.md:12 src/bare-metal/aps/better-uart.md:15 msgid "8" msgstr "" #: src/bare-metal/aps/better-uart.md:13 msgid "0x24" msgstr "" #: src/bare-metal/aps/better-uart.md:13 msgid "IBRD" msgstr "" #: src/bare-metal/aps/better-uart.md:13 src/bare-metal/aps/better-uart.md:16 msgid "16" msgstr "" #: src/bare-metal/aps/better-uart.md:14 msgid "0x28" msgstr "" #: src/bare-metal/aps/better-uart.md:14 msgid "FBRD" msgstr "" #: src/bare-metal/aps/better-uart.md:14 src/bare-metal/aps/better-uart.md:17 msgid "6" msgstr "" #: src/bare-metal/aps/better-uart.md:15 msgid "0x2c" msgstr "" #: src/bare-metal/aps/better-uart.md:15 msgid "LCR_H" msgstr "" #: src/bare-metal/aps/better-uart.md:16 msgid "0x30" msgstr "" #: src/bare-metal/aps/better-uart.md:16 msgid "CR" msgstr "" #: src/bare-metal/aps/better-uart.md:17 msgid "0x34" msgstr "" #: src/bare-metal/aps/better-uart.md:17 msgid "IFLS" msgstr "" #: src/bare-metal/aps/better-uart.md:18 msgid "0x38" msgstr "" #: src/bare-metal/aps/better-uart.md:18 msgid "IMSC" msgstr "" #: src/bare-metal/aps/better-uart.md:18 src/bare-metal/aps/better-uart.md:19 #: src/bare-metal/aps/better-uart.md:20 src/bare-metal/aps/better-uart.md:21 msgid "11" msgstr "" #: src/bare-metal/aps/better-uart.md:19 msgid "0x3c" msgstr "" #: src/bare-metal/aps/better-uart.md:19 msgid "RIS" msgstr "" #: src/bare-metal/aps/better-uart.md:20 msgid "0x40" msgstr "" #: src/bare-metal/aps/better-uart.md:20 msgid "MIS" msgstr "" #: src/bare-metal/aps/better-uart.md:21 msgid "0x44" msgstr "" #: src/bare-metal/aps/better-uart.md:21 msgid "ICR" msgstr "" #: src/bare-metal/aps/better-uart.md:22 msgid "0x48" msgstr "" #: src/bare-metal/aps/better-uart.md:22 msgid "DMACR" msgstr "" #: src/bare-metal/aps/better-uart.md: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 "" #: src/bare-metal/aps/better-uart/bitflags.md:3 msgid "" "The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " "working with bitflags." msgstr "" #: src/bare-metal/aps/better-uart/bitflags.md:9 #: src/exercises/bare-metal/rtc.md:238 msgid "/// Flags from the UART flag register.\n" msgstr "/// Flags from the UART flag register.\n" #: src/bare-metal/aps/better-uart/bitflags.md:13 #: src/exercises/bare-metal/rtc.md:242 msgid "/// Clear to send.\n" msgstr "/// Clear to send.\n" #: src/bare-metal/aps/better-uart/bitflags.md:15 #: src/exercises/bare-metal/rtc.md:244 msgid "/// Data set ready.\n" msgstr "/// Data set ready.\n" #: src/bare-metal/aps/better-uart/bitflags.md:17 #: src/exercises/bare-metal/rtc.md:246 msgid "/// Data carrier detect.\n" msgstr "/// Data carrier detect.\n" #: src/bare-metal/aps/better-uart/bitflags.md:19 #: src/exercises/bare-metal/rtc.md:248 msgid "/// UART busy transmitting data.\n" msgstr "/// UART busy transmitting data.\n" #: src/bare-metal/aps/better-uart/bitflags.md:21 #: src/exercises/bare-metal/rtc.md:250 msgid "/// Receive FIFO is empty.\n" msgstr "/// Receive FIFO is empty.\n" #: src/bare-metal/aps/better-uart/bitflags.md:23 #: src/exercises/bare-metal/rtc.md:252 msgid "/// Transmit FIFO is full.\n" msgstr "/// Transmit FIFO is full.\n" #: src/bare-metal/aps/better-uart/bitflags.md:25 #: src/exercises/bare-metal/rtc.md:254 msgid "/// Receive FIFO is full.\n" msgstr "/// Receive FIFO is full.\n" #: src/bare-metal/aps/better-uart/bitflags.md:27 #: src/exercises/bare-metal/rtc.md:256 msgid "/// Transmit FIFO is empty.\n" msgstr "/// Transmit FIFO is empty.\n" #: src/bare-metal/aps/better-uart/bitflags.md:29 #: src/exercises/bare-metal/rtc.md:258 msgid "/// Ring indicator.\n" msgstr "/// Ring indicator.\n" #: src/bare-metal/aps/better-uart/bitflags.md:37 msgid "" "The `bitflags!` macro creates a newtype something like `Flags(u16)`, along " "with a bunch of method implementations to get and set flags." msgstr "" #: src/bare-metal/aps/better-uart/registers.md:1 msgid "Multiple registers" msgstr "" #: src/bare-metal/aps/better-uart/registers.md:3 msgid "" "We can use a struct to represent the memory layout of the UART's registers." msgstr "" #: src/bare-metal/aps/better-uart/registers.md:41 msgid "" "[`#[repr(C)]`](https://doc.rust-lang.org/reference/type-layout.html#the-c-" "representation) tells the compiler to lay the struct fields out in order, " "following the same rules as C. This is necessary for our struct to have a " "predictable layout, as default Rust representation allows the compiler to " "(among other things) reorder fields however it sees fit." msgstr "" #: src/bare-metal/aps/better-uart/driver.md:3 msgid "Now let's use the new `Registers` struct in our driver." msgstr "" #: src/bare-metal/aps/better-uart/driver.md:6 msgid "/// Driver for a PL011 UART.\n" msgstr "" #: src/bare-metal/aps/better-uart/driver.md:32 #: src/bare-metal/aps/better-uart/driver.md:55 #: src/exercises/bare-metal/rtc.md:341 src/exercises/bare-metal/rtc.md:364 msgid "" "// Safe because we know that self.registers points to the control\n" " // registers of a PL011 device which is appropriately mapped.\n" msgstr "" "// Safe because we know that self.registers points to the control\n" " // registers of a PL011 device which is appropriately mapped.\n" #: src/bare-metal/aps/better-uart/driver.md:43 #: src/exercises/bare-metal/rtc.md:352 msgid "" "/// Reads and returns a pending byte, or `None` if nothing has been " "received.\n" msgstr "" "/// Reads and returns a pending byte, or `None` if nothing has been " "received.\n" #: src/bare-metal/aps/better-uart/driver.md:49 #: src/exercises/bare-metal/rtc.md:358 msgid "// TODO: Check for error conditions in bits 8-11.\n" msgstr "// TODO: Check for error conditions in bits 8-11.\n" #: src/bare-metal/aps/better-uart/driver.md:64 msgid "" "Note the use of `addr_of!` / `addr_of_mut!` to get pointers to individual " "fields without creating an intermediate reference, which would be unsound." msgstr "" #: src/bare-metal/aps/better-uart/using.md:1 #: src/bare-metal/aps/logging/using.md:1 msgid "Using it" msgstr "" #: src/bare-metal/aps/better-uart/using.md:3 msgid "" "Let's write a small program using our driver to write to the serial console, " "and echo incoming bytes." msgstr "" #: src/bare-metal/aps/better-uart/using.md:19 #: src/bare-metal/aps/logging/using.md:18 src/exercises/bare-metal/rtc.md:41 #: src/exercises/bare-metal/solutions-afternoon.md:33 msgid "/// Base address of the primary PL011 UART.\n" msgstr "" #: src/bare-metal/aps/better-uart/using.md:25 #: src/bare-metal/aps/logging/using.md:24 src/exercises/bare-metal/rtc.md:47 #: src/exercises/bare-metal/solutions-afternoon.md:44 msgid "" "// Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 device,\n" " // and nothing else accesses that address range.\n" msgstr "" #: src/bare-metal/aps/better-uart/using.md:29 #: src/bare-metal/aps/logging/using.md:29 msgid "\"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\"" msgstr "" #: src/bare-metal/aps/better-uart/using.md:35 msgid "b'\\r'" msgstr "" #: src/bare-metal/aps/better-uart/using.md:36 #: src/async/pitfalls/cancellation.md:27 msgid "b'\\n'" msgstr "" #: src/bare-metal/aps/better-uart/using.md:38 msgid "b'q'" msgstr "" #: src/bare-metal/aps/better-uart/using.md:44 msgid "\"Bye!\"" msgstr "" #: src/bare-metal/aps/better-uart/using.md:51 msgid "" "As in the [inline assembly](../inline-assembly.md) example, this `main` " "function is called from our entry point code in `entry.S`. See the speaker " "notes there for details." msgstr "" #: src/bare-metal/aps/better-uart/using.md:53 msgid "" "Run the example in QEMU with `make qemu` under `src/bare-metal/aps/examples`." msgstr "" #: src/bare-metal/aps/logging.md:3 msgid "" "It would be nice to be able to use the logging macros from the [`log`]" "(https://crates.io/crates/log) crate. We can do this by implementing the " "`Log` trait." msgstr "" #: src/bare-metal/aps/logging.md:28 src/exercises/bare-metal/rtc.md:190 msgid "\"[{}] {}\"" msgstr "\"[{}] {}\"" #: src/bare-metal/aps/logging.md:37 src/exercises/bare-metal/rtc.md:199 msgid "/// Initialises UART logger.\n" msgstr "/// Initialises UART logger.\n" #: src/bare-metal/aps/logging.md:50 msgid "" "The unwrap in `log` is safe because we initialise `LOGGER` before calling " "`set_logger`." msgstr "" #: src/bare-metal/aps/logging/using.md:3 msgid "We need to initialise the logger before we use it." msgstr "" #: src/bare-metal/aps/logging/using.md:38 src/exercises/bare-metal/rtc.md:69 #: src/exercises/bare-metal/solutions-afternoon.md:121 msgid "\"{info}\"" msgstr "" #: src/bare-metal/aps/logging/using.md:46 msgid "Note that our panic handler can now log details of panics." msgstr "" #: src/bare-metal/aps/logging/using.md:47 msgid "" "Run the example in QEMU with `make qemu_logger` under `src/bare-metal/aps/" "examples`." msgstr "" #: src/bare-metal/aps/exceptions.md:3 msgid "" "AArch64 defines an exception vector table with 16 entries, for 4 types of " "exceptions (synchronous, IRQ, FIQ, SError) from 4 states (current EL with " "SP0, current EL with SPx, lower EL using AArch64, lower EL using AArch32). " "We implement this in assembly to save volatile registers to the stack before " "calling into Rust code:" msgstr "" #: src/bare-metal/aps/exceptions.md: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 "" #: src/bare-metal/aps/exceptions.md:65 msgid "" "For simplicity we aren't distinguishing between SP0 and SPx for the current " "EL exceptions, or between AArch32 and AArch64 for the lower EL exceptions." msgstr "" #: src/bare-metal/aps/exceptions.md:67 msgid "" "For this example we just log the exception and power down, as we don't " "expect any of them to actually happen." msgstr "" #: src/bare-metal/aps/exceptions.md:69 msgid "" "We can think of exception handlers and our main execution context more or " "less like different threads. [`Send` and `Sync`](../../concurrency/send-sync." "md) will control what we can share between them, just like with threads. For " "example, if we want to share some value between exception handlers and the " "rest of the program, and it's `Send` but not `Sync`, then we'll need to wrap " "it in something like a `Mutex` and put it in a static." msgstr "" #: src/bare-metal/aps/other-projects.md:3 msgid "[oreboot](https://github.com/oreboot/oreboot)" msgstr "" #: src/bare-metal/aps/other-projects.md:4 msgid "\"coreboot without the C\"" msgstr "" #: src/bare-metal/aps/other-projects.md:5 msgid "Supports x86, aarch64 and RISC-V." msgstr "" #: src/bare-metal/aps/other-projects.md:6 msgid "Relies on LinuxBoot rather than having many drivers itself." msgstr "" #: src/bare-metal/aps/other-projects.md:7 msgid "" "[Rust RaspberryPi OS tutorial](https://github.com/rust-embedded/rust-" "raspberrypi-OS-tutorials)" msgstr "" #: src/bare-metal/aps/other-projects.md:8 msgid "" "Initialisation, UART driver, simple bootloader, JTAG, exception levels, " "exception handling, page tables" msgstr "" #: src/bare-metal/aps/other-projects.md:10 msgid "" "Some dodginess around cache maintenance and initialisation in Rust, not " "necessarily a good example to copy for production code." msgstr "" #: src/bare-metal/aps/other-projects.md:12 msgid "[`cargo-call-stack`](https://crates.io/crates/cargo-call-stack)" msgstr "" #: src/bare-metal/aps/other-projects.md:13 msgid "Static analysis to determine maximum stack usage." msgstr "" #: src/bare-metal/aps/other-projects.md:17 msgid "" "The RaspberryPi OS tutorial runs Rust code before the MMU and caches are " "enabled. This will read and write memory (e.g. the stack). However:" msgstr "" #: src/bare-metal/aps/other-projects.md:19 msgid "" "Without the MMU and cache, unaligned accesses will fault. It builds with " "`aarch64-unknown-none` which sets `+strict-align` to prevent the compiler " "generating unaligned accesses so it should be alright, but this is not " "necessarily the case in general." msgstr "" #: src/bare-metal/aps/other-projects.md:22 msgid "" "If it were running in a VM, this can lead to cache coherency issues. The " "problem is that the VM is accessing memory directly with the cache disabled, " "while the host has cacheable aliases to the same memory. Even if the host " "doesn't explicitly access the memory, speculative accesses can lead to cache " "fills, and then changes from one or the other will get lost. Again this is " "alright in this particular case (running directly on the hardware with no " "hypervisor), but isn't a good pattern in general." msgstr "" #: src/bare-metal/useful-crates.md:3 msgid "" "We'll go over a few crates which solve some common problems in bare-metal " "programming." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:1 msgid "`zerocopy`" msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:3 msgid "" "The [`zerocopy`](https://docs.rs/zerocopy/) crate (from Fuchsia) provides " "traits and macros for safely converting between byte sequences and other " "types." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:40 msgid "" "This is not suitable for MMIO (as it doesn't use volatile reads and writes), " "but can be useful for working with structures shared with hardware e.g. by " "DMA, or sent over some external interface." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:45 msgid "" "`FromBytes` can be implemented for types for which any byte pattern is " "valid, and so can safely be converted from an untrusted sequence of bytes." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:47 msgid "" "Attempting to derive `FromBytes` for these types would fail, because " "`RequestType` doesn't use all possible u32 values as discriminants, so not " "all byte patterns are valid." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:49 msgid "" "`zerocopy::byteorder` has types for byte-order aware numeric primitives." msgstr "" #: src/bare-metal/useful-crates/zerocopy.md:50 msgid "" "Run the example with `cargo run` under `src/bare-metal/useful-crates/" "zerocopy-example/`. (It won't run in the Playground because of the crate " "dependency.)" msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:1 msgid "`aarch64-paging`" msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:3 msgid "" "The [`aarch64-paging`](https://crates.io/crates/aarch64-paging) crate lets " "you create page tables according to the AArch64 Virtual Memory System " "Architecture." msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:14 msgid "// Create a new page table with identity mapping.\n" msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:16 msgid "// Map a 2 MiB region of memory as read-only.\n" msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:21 msgid "// Set `TTBR0_EL1` to activate the page table.\n" msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:28 msgid "" "For now it only supports EL1, but support for other exception levels should " "be straightforward to add." msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:30 msgid "" "This is used in Android for the [Protected VM Firmware](https://cs.android." "com/android/platform/superproject/+/master:packages/modules/Virtualization/" "pvmfw/)." msgstr "" #: src/bare-metal/useful-crates/aarch64-paging.md:31 msgid "" "There's no easy way to run this example, as it needs to run on real hardware " "or under QEMU." msgstr "" #: src/bare-metal/useful-crates/buddy_system_allocator.md:1 msgid "`buddy_system_allocator`" msgstr "" #: src/bare-metal/useful-crates/buddy_system_allocator.md:3 msgid "" "[`buddy_system_allocator`](https://crates.io/crates/buddy_system_allocator) " "is a third-party crate implementing a basic buddy system allocator. It can " "be used both for [`LockedHeap`](https://docs.rs/buddy_system_allocator/0.9.0/" "buddy_system_allocator/struct.LockedHeap.html) implementing [`GlobalAlloc`]" "(https://doc.rust-lang.org/core/alloc/trait.GlobalAlloc.html) so you can use " "the standard `alloc` crate (as we saw [before](../alloc.md)), or for " "allocating other address space. For example, we might want to allocate MMIO " "space for PCI BARs:" msgstr "" #: src/bare-metal/useful-crates/buddy_system_allocator.md: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 "" #: src/bare-metal/useful-crates/buddy_system_allocator.md:27 msgid "" "Run the example with `cargo run` under `src/bare-metal/useful-crates/" "allocator-example/`. (It won't run in the Playground because of the crate " "dependency.)" msgstr "" #: src/bare-metal/useful-crates/tinyvec.md:1 msgid "`tinyvec`" msgstr "" #: src/bare-metal/useful-crates/tinyvec.md:3 msgid "" "Sometimes you want something which can be resized like a `Vec`, but without " "heap allocation. [`tinyvec`](https://crates.io/crates/tinyvec) provides " "this: a vector backed by an array or slice, which could be statically " "allocated or on the stack, which keeps track of how many elements are used " "and panics if you try to use more than are allocated." msgstr "" #: src/bare-metal/useful-crates/tinyvec.md: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 " "initialisation." msgstr "" #: src/bare-metal/useful-crates/tinyvec.md:24 msgid "" "The Rust Playground includes `tinyvec`, so this example will run fine inline." msgstr "" #: src/bare-metal/useful-crates/spin.md:1 msgid "`spin`" msgstr "" #: src/bare-metal/useful-crates/spin.md:3 msgid "" "`std::sync::Mutex` and the other synchronisation primitives from `std::sync` " "are not available in `core` or `alloc`. How can we manage synchronisation or " "interior mutability, such as for sharing state between different CPUs?" msgstr "" #: src/bare-metal/useful-crates/spin.md:7 msgid "" "The [`spin`](https://crates.io/crates/spin) crate provides spinlock-based " "equivalents of many of these primitives." msgstr "" #: src/bare-metal/useful-crates/spin.md: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 "" #: src/bare-metal/useful-crates/spin.md:24 msgid "" "`spin` also has a ticket lock mutex implementation; equivalents of `RwLock`, " "`Barrier` and `Once` from `std::sync`; and `Lazy` for lazy initialisation." msgstr "" #: src/bare-metal/useful-crates/spin.md:26 msgid "" "The [`once_cell`](https://crates.io/crates/once_cell) crate also has some " "useful types for late initialisation with a slightly different approach to " "`spin::once::Once`." msgstr "" #: src/bare-metal/useful-crates/spin.md:28 msgid "" "The Rust Playground includes `spin`, so this example will run fine inline." msgstr "" #: src/bare-metal/android.md:3 msgid "" "To build a bare-metal Rust binary in AOSP, you need to use a " "`rust_ffi_static` Soong rule to build your Rust code, then a `cc_binary` " "with a linker script to produce the binary itself, and then a `raw_binary` " "to convert the ELF to a raw binary ready to be run." msgstr "" #: src/bare-metal/android.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." "googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/" "master/vmbase/) library provides a linker script and useful defaults for the " "build rules, along with an entry point, UART console logging and more." msgstr "" #: src/bare-metal/android/vmbase.md: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` " "entry point." msgstr "" #: src/bare-metal/android/vmbase.md:22 msgid "" "The `vmbase` entry point handles console initialisation, and issues a " "PSCI_SYSTEM_OFF to shutdown the VM if your main function returns." msgstr "" #: src/exercises/bare-metal/afternoon.md:3 msgid "We will write a driver for the PL031 real-time clock device." msgstr "" #: src/exercises/bare-metal/rtc.md:1 #: src/exercises/bare-metal/solutions-afternoon.md:3 msgid "RTC driver" msgstr "" #: src/exercises/bare-metal/rtc.md:3 msgid "" "The QEMU aarch64 virt machine has a [PL031](https://developer.arm.com/" "documentation/ddi0224/c) real-time clock at 0x9010000. For this exercise, " "you should write a driver for it." msgstr "" #: src/exercises/bare-metal/rtc.md:6 msgid "" "Use it to print the current time to the serial console. You can use the " "[`chrono`](https://crates.io/crates/chrono) crate for date/time formatting." msgstr "" #: src/exercises/bare-metal/rtc.md:8 msgid "" "Use the match register and raw interrupt status to busy-wait until a given " "time, e.g. 3 seconds in the future. (Call [`core::hint::spin_loop`](https://" "doc.rust-lang.org/core/hint/fn.spin_loop.html) inside the loop.)" msgstr "" #: src/exercises/bare-metal/rtc.md:10 msgid "" "_Extension if you have time:_ Enable and handle the interrupt generated by " "the RTC match. You can use the driver provided in the [`arm-gic`](https://" "docs.rs/arm-gic/) crate to configure the Arm Generic Interrupt Controller." msgstr "" #: src/exercises/bare-metal/rtc.md:12 msgid "Use the RTC interrupt, which is wired to the GIC as `IntId::spi(2)`." msgstr "" #: src/exercises/bare-metal/rtc.md:13 msgid "" "Once the interrupt is enabled, you can put the core to sleep via `arm_gic::" "wfi()`, which will cause the core to sleep until it receives an interrupt." msgstr "" #: src/exercises/bare-metal/rtc.md:16 msgid "" "Download the [exercise template](../../comprehensive-rust-exercises.zip) and " "look in the `rtc` directory for the following files." msgstr "" #: src/exercises/bare-metal/rtc.md:37 #: src/exercises/bare-metal/solutions-afternoon.md:29 msgid "/// Base addresses of the GICv3.\n" msgstr "" #: src/exercises/bare-metal/rtc.md:52 #: src/exercises/bare-metal/solutions-afternoon.md:49 msgid "\"main({:#x}, {:#x}, {:#x}, {:#x})\"" msgstr "" #: src/exercises/bare-metal/rtc.md:54 #: src/exercises/bare-metal/solutions-afternoon.md:51 msgid "" "// Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the base\n" " // addresses of a GICv3 distributor and redistributor respectively, and\n" " // nothing else accesses those address ranges.\n" msgstr "" #: src/exercises/bare-metal/rtc.md:60 msgid "// TODO: Create instance of RTC driver and print current time.\n" msgstr "" #: src/exercises/bare-metal/rtc.md:62 msgid "// TODO: Wait for 3 seconds.\n" msgstr "" #: src/exercises/bare-metal/rtc.md:75 msgid "" "_src/exceptions.rs_ (you should only need to change this for the 3rd part of " "the exercise):" msgstr "" #: src/exercises/bare-metal/rtc.md:80 src/exercises/bare-metal/rtc.md:154 #: src/exercises/bare-metal/rtc.md:215 src/exercises/bare-metal/rtc.md:415 msgid "" "// Copyright 2023 Google LLC\n" "//\n" "// Licensed under the Apache License, Version 2.0 (the \"License\");\n" "// you may not use this file except in compliance with the License.\n" "// You may obtain a copy of the License at\n" "//\n" "// http://www.apache.org/licenses/LICENSE-2.0\n" "//\n" "// Unless required by applicable law or agreed to in writing, software\n" "// distributed under the License is distributed on an \"AS IS\" BASIS,\n" "// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" "// See the License for the specific language governing permissions and\n" "// limitations under the License.\n" msgstr "" "// Copyright 2023 Google LLC\n" "//\n" "// Licensed under the Apache License, Version 2.0 (the \"License\");\n" "// you may not use this file except in compliance with the License.\n" "// You may obtain a copy of the License at\n" "//\n" "// http://www.apache.org/licenses/LICENSE-2.0\n" "//\n" "// Unless required by applicable law or agreed to in writing, software\n" "// distributed under the License is distributed on an \"AS IS\" BASIS,\n" "// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" "// See the License for the specific language governing permissions and\n" "// limitations under the License.\n" #: src/exercises/bare-metal/rtc.md:108 msgid "\"No pending interrupt\"" msgstr "\"No pending interrupt\"" #: src/exercises/bare-metal/rtc.md:109 msgid "\"IRQ {intid:?}\"" msgstr "\"IRQ {intid:?}\"" #: src/exercises/bare-metal/rtc.md:149 msgid "_src/logger.rs_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:167 msgid "// ANCHOR: main\n" msgstr "// ANCHOR: main\n" #: src/exercises/bare-metal/rtc.md:210 msgid "_src/pl011.rs_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:233 msgid "// ANCHOR: Flags\n" msgstr "// ANCHOR: Flags\n" #: src/exercises/bare-metal/rtc.md:261 msgid "// ANCHOR_END: Flags\n" msgstr "// ANCHOR_END: Flags\n" #: src/exercises/bare-metal/rtc.md:265 msgid "" "/// Flags from the UART Receive Status Register / Error Clear Register.\n" msgstr "" "/// Flags from the UART Receive Status Register / Error Clear Register.\n" #: src/exercises/bare-metal/rtc.md:269 msgid "/// Framing error.\n" msgstr "/// Framing error.\n" #: src/exercises/bare-metal/rtc.md:271 msgid "/// Parity error.\n" msgstr "/// Parity error.\n" #: src/exercises/bare-metal/rtc.md:273 msgid "/// Break error.\n" msgstr "/// Break error.\n" #: src/exercises/bare-metal/rtc.md:275 msgid "/// Overrun error.\n" msgstr "/// Overrun error.\n" #: src/exercises/bare-metal/rtc.md:279 msgid "// ANCHOR: Registers\n" msgstr "// ANCHOR: Registers\n" #: src/exercises/bare-metal/rtc.md:311 msgid "// ANCHOR_END: Registers\n" msgstr "// ANCHOR_END: Registers\n" #: src/exercises/bare-metal/rtc.md:313 msgid "" "// ANCHOR: Uart\n" "/// Driver for a PL011 UART.\n" msgstr "" "// ANCHOR: Uart\n" "/// Driver for a PL011 UART.\n" #: src/exercises/bare-metal/rtc.md:322 msgid "" "/// Constructs a new instance of the UART driver for a PL011 device at the\n" " /// given base address.\n" " ///\n" " /// # Safety\n" " ///\n" " /// The given base address must point to the MMIO control registers of " "a\n" " /// PL011 device, which must be mapped into the address space of the " "process\n" " /// as device memory and not have any other aliases.\n" msgstr "" "/// Constructs a new instance of the UART driver for a PL011 device at the\n" " /// given base address.\n" " ///\n" " /// # Safety\n" " ///\n" " /// The given base address must point to the MMIO control registers of " "a\n" " /// PL011 device, which must be mapped into the address space of the " "process\n" " /// as device memory and not have any other aliases.\n" #: src/exercises/bare-metal/rtc.md:368 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 "" #: src/exercises/bare-metal/rtc.md:433 src/exercises/bare-metal/rtc.md:435 msgid "\"linux\"" msgstr "\"linux\"" #: src/exercises/bare-metal/rtc.md:434 src/exercises/bare-metal/rtc.md:436 msgid "\"CROSS_COMPILE\"" msgstr "\"CROSS_COMPILE\"" #: src/exercises/bare-metal/rtc.md:434 msgid "\"aarch64-linux-gnu\"" msgstr "\"aarch64-linux-gnu\"" #: src/exercises/bare-metal/rtc.md:436 msgid "\"aarch64-none-elf\"" msgstr "\"aarch64-none-elf\"" #: src/exercises/bare-metal/rtc.md:439 msgid "\"entry.S\"" msgstr "\"entry.S\"" #: src/exercises/bare-metal/rtc.md:440 msgid "\"exceptions.S\"" msgstr "\"exceptions.S\"" #: src/exercises/bare-metal/rtc.md:441 msgid "\"idmap.S\"" msgstr "\"idmap.S\"" #: src/exercises/bare-metal/rtc.md:442 msgid "\"empty\"" msgstr "\"empty\"" #: src/exercises/bare-metal/rtc.md:446 msgid "_entry.S_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:450 msgid "" "```armasm\n" "/*\n" " * Copyright 2023 Google LLC\n" " *\n" " * Licensed under the Apache License, Version 2.0 (the \"License\");\n" " * you may not use this file except in compliance with the License.\n" " * You may obtain a copy of the License at\n" " *\n" " * https://www.apache.org/licenses/LICENSE-2.0\n" " *\n" " * Unless required by applicable law or agreed to in writing, software\n" " * distributed under the License is distributed on an \"AS IS\" BASIS,\n" " * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" " * See the License for the specific language governing permissions and\n" " * limitations under the License.\n" " */\n" "\n" ".macro adr_l, reg:req, sym:req\n" "\tadrp \\reg, \\sym\n" "\tadd \\reg, \\reg, :lo12:\\sym\n" ".endm\n" "\n" ".macro mov_i, reg:req, imm:req\n" "\tmovz \\reg, :abs_g3:\\imm\n" "\tmovk \\reg, :abs_g2_nc:\\imm\n" "\tmovk \\reg, :abs_g1_nc:\\imm\n" "\tmovk \\reg, :abs_g0_nc:\\imm\n" ".endm\n" "\n" ".set .L_MAIR_DEV_nGnRE,\t0x04\n" ".set .L_MAIR_MEM_WBWA,\t0xff\n" ".set .Lmairval, .L_MAIR_DEV_nGnRE | (.L_MAIR_MEM_WBWA << 8)\n" "\n" "/* 4 KiB granule size for TTBR0_EL1. */\n" ".set .L_TCR_TG0_4KB, 0x0 << 14\n" "/* 4 KiB granule size for TTBR1_EL1. */\n" ".set .L_TCR_TG1_4KB, 0x2 << 30\n" "/* Disable translation table walk for TTBR1_EL1, generating a translation " "fault instead. */\n" ".set .L_TCR_EPD1, 0x1 << 23\n" "/* Translation table walks for TTBR0_EL1 are inner sharable. */\n" ".set .L_TCR_SH_INNER, 0x3 << 12\n" "/*\n" " * Translation table walks for TTBR0_EL1 are outer write-back read-allocate " "write-allocate\n" " * cacheable.\n" " */\n" ".set .L_TCR_RGN_OWB, 0x1 << 10\n" "/*\n" " * Translation table walks for TTBR0_EL1 are inner write-back read-allocate " "write-allocate\n" " * cacheable.\n" " */\n" ".set .L_TCR_RGN_IWB, 0x1 << 8\n" "/* Size offset for TTBR0_EL1 is 2**39 bytes (512 GiB). */\n" ".set .L_TCR_T0SZ_512, 64 - 39\n" ".set .Ltcrval, .L_TCR_TG0_4KB | .L_TCR_TG1_4KB | .L_TCR_EPD1 | ." "L_TCR_RGN_OWB\n" ".set .Ltcrval, .Ltcrval | .L_TCR_RGN_IWB | .L_TCR_SH_INNER | ." "L_TCR_T0SZ_512\n" "\n" "/* Stage 1 instruction access cacheability is unaffected. */\n" ".set .L_SCTLR_ELx_I, 0x1 << 12\n" "/* SP alignment fault if SP is not aligned to a 16 byte boundary. */\n" ".set .L_SCTLR_ELx_SA, 0x1 << 3\n" "/* Stage 1 data access cacheability is unaffected. */\n" ".set .L_SCTLR_ELx_C, 0x1 << 2\n" "/* EL0 and EL1 stage 1 MMU enabled. */\n" ".set .L_SCTLR_ELx_M, 0x1 << 0\n" "/* Privileged Access Never is unchanged on taking an exception to EL1. */\n" ".set .L_SCTLR_EL1_SPAN, 0x1 << 23\n" "/* SETEND instruction disabled at EL0 in aarch32 mode. */\n" ".set .L_SCTLR_EL1_SED, 0x1 << 8\n" "/* Various IT instructions are disabled at EL0 in aarch32 mode. */\n" ".set .L_SCTLR_EL1_ITD, 0x1 << 7\n" ".set .L_SCTLR_EL1_RES1, (0x1 << 11) | (0x1 << 20) | (0x1 << 22) | (0x1 << " "28) | (0x1 << 29)\n" ".set .Lsctlrval, .L_SCTLR_ELx_M | .L_SCTLR_ELx_C | .L_SCTLR_ELx_SA | ." "L_SCTLR_EL1_ITD | .L_SCTLR_EL1_SED\n" ".set .Lsctlrval, .Lsctlrval | .L_SCTLR_ELx_I | .L_SCTLR_EL1_SPAN | ." "L_SCTLR_EL1_RES1\n" "\n" "/**\n" " * This is a generic entry point for an image. It carries out the operations " "required to prepare the\n" " * loaded image to be run. Specifically, it zeroes the bss section using " "registers x25 and above,\n" " * prepares the stack, enables floating point, and sets up the exception " "vector. It preserves x0-x3\n" " * for the Rust entry point, as these may contain boot parameters.\n" " */\n" ".section .init.entry, \"ax\"\n" ".global entry\n" "entry:\n" "\t/* Load and apply the memory management configuration, ready to enable MMU " "and caches. */\n" "\tadrp x30, idmap\n" "\tmsr ttbr0_el1, x30\n" "\n" "\tmov_i x30, .Lmairval\n" "\tmsr mair_el1, x30\n" "\n" "\tmov_i x30, .Ltcrval\n" "\t/* Copy the supported PA range into TCR_EL1.IPS. */\n" "\tmrs x29, id_aa64mmfr0_el1\n" "\tbfi x30, x29, #32, #4\n" "\n" "\tmsr tcr_el1, x30\n" "\n" "\tmov_i x30, .Lsctlrval\n" "\n" "\t/*\n" "\t * Ensure everything before this point has completed, then invalidate any " "potentially stale\n" "\t * local TLB entries before they start being used.\n" "\t */\n" "\tisb\n" "\ttlbi vmalle1\n" "\tic iallu\n" "\tdsb nsh\n" "\tisb\n" "\n" "\t/*\n" "\t * Configure sctlr_el1 to enable MMU and cache and don't proceed until " "this has completed.\n" "\t */\n" "\tmsr sctlr_el1, x30\n" "\tisb\n" "\n" "\t/* Disable trapping floating point access in EL1. */\n" "\tmrs x30, cpacr_el1\n" "\torr x30, x30, #(0x3 << 20)\n" "\tmsr cpacr_el1, x30\n" "\tisb\n" "\n" "\t/* Zero out the bss section. */\n" "\tadr_l x29, bss_begin\n" "\tadr_l x30, bss_end\n" "0:\tcmp x29, x30\n" "\tb.hs 1f\n" "\tstp xzr, xzr, [x29], #16\n" "\tb 0b\n" "\n" "1:\t/* Prepare the stack. */\n" "\tadr_l x30, boot_stack_end\n" "\tmov sp, x30\n" "\n" "\t/* Set up exception vector. */\n" "\tadr x30, vector_table_el1\n" "\tmsr vbar_el1, x30\n" "\n" "\t/* Call into Rust code. */\n" "\tbl main\n" "\n" "\t/* Loop forever waiting for interrupts. */\n" "2:\twfi\n" "\tb 2b\n" "```" msgstr "" #: src/exercises/bare-metal/rtc.md:595 msgid "_exceptions.S_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:599 msgid "" "```armasm\n" "/*\n" " * Copyright 2023 Google LLC\n" " *\n" " * Licensed under the Apache License, Version 2.0 (the \"License\");\n" " * you may not use this file except in compliance with the License.\n" " * You may obtain a copy of the License at\n" " *\n" " * https://www.apache.org/licenses/LICENSE-2.0\n" " *\n" " * Unless required by applicable law or agreed to in writing, software\n" " * distributed under the License is distributed on an \"AS IS\" BASIS,\n" " * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" " * See the License for the specific language governing permissions and\n" " * limitations under the License.\n" " */\n" "\n" "/**\n" " * Saves the volatile registers onto the stack. This currently takes 14\n" " * instructions, so it can be used in exception handlers with 18 " "instructions\n" " * left.\n" " *\n" " * On return, x0 and x1 are initialised to elr_el2 and spsr_el2 " "respectively,\n" " * which can be used as the first and second arguments of a subsequent " "call.\n" " */\n" ".macro save_volatile_to_stack\n" "\t/* Reserve stack space and save registers x0-x18, x29 & x30. */\n" "\tstp x0, x1, [sp, #-(8 * 24)]!\n" "\tstp x2, x3, [sp, #8 * 2]\n" "\tstp x4, x5, [sp, #8 * 4]\n" "\tstp x6, x7, [sp, #8 * 6]\n" "\tstp x8, x9, [sp, #8 * 8]\n" "\tstp x10, x11, [sp, #8 * 10]\n" "\tstp x12, x13, [sp, #8 * 12]\n" "\tstp x14, x15, [sp, #8 * 14]\n" "\tstp x16, x17, [sp, #8 * 16]\n" "\tstr x18, [sp, #8 * 18]\n" "\tstp x29, x30, [sp, #8 * 20]\n" "\n" "\t/*\n" "\t * Save elr_el1 & spsr_el1. This such that we can take nested exception\n" "\t * and still be able to unwind.\n" "\t */\n" "\tmrs x0, elr_el1\n" "\tmrs x1, spsr_el1\n" "\tstp x0, x1, [sp, #8 * 22]\n" ".endm\n" "\n" "/**\n" " * Restores the volatile registers from the stack. This currently takes 14\n" " * instructions, so it can be used in exception handlers while still leaving " "18\n" " * instructions left; if paired with save_volatile_to_stack, there are 4\n" " * instructions to spare.\n" " */\n" ".macro restore_volatile_from_stack\n" "\t/* Restore registers x2-x18, x29 & x30. */\n" "\tldp x2, x3, [sp, #8 * 2]\n" "\tldp x4, x5, [sp, #8 * 4]\n" "\tldp x6, x7, [sp, #8 * 6]\n" "\tldp x8, x9, [sp, #8 * 8]\n" "\tldp x10, x11, [sp, #8 * 10]\n" "\tldp x12, x13, [sp, #8 * 12]\n" "\tldp x14, x15, [sp, #8 * 14]\n" "\tldp x16, x17, [sp, #8 * 16]\n" "\tldr x18, [sp, #8 * 18]\n" "\tldp x29, x30, [sp, #8 * 20]\n" "\n" "\t/* Restore registers elr_el1 & spsr_el1, using x0 & x1 as scratch. */\n" "\tldp x0, x1, [sp, #8 * 22]\n" "\tmsr elr_el1, x0\n" "\tmsr spsr_el1, x1\n" "\n" "\t/* Restore x0 & x1, and release stack space. */\n" "\tldp x0, x1, [sp], #8 * 24\n" ".endm\n" "\n" "/**\n" " * This is a generic handler for exceptions taken at the current EL while " "using\n" " * SP0. It behaves similarly to the SPx case by first switching to SPx, " "doing\n" " * the work, then switching back to SP0 before returning.\n" " *\n" " * Switching to SPx and calling the Rust handler takes 16 instructions. To\n" " * restore and return we need an additional 16 instructions, so we can " "implement\n" " * the whole handler within the allotted 32 instructions.\n" " */\n" ".macro current_exception_sp0 handler:req\n" "\tmsr spsel, #1\n" "\tsave_volatile_to_stack\n" "\tbl \\handler\n" "\trestore_volatile_from_stack\n" "\tmsr spsel, #0\n" "\teret\n" ".endm\n" "\n" "/**\n" " * This is a generic handler for exceptions taken at the current EL while " "using\n" " * SPx. It saves volatile registers, calls the Rust handler, restores " "volatile\n" " * registers, then returns.\n" " *\n" " * This also works for exceptions taken from EL0, if we don't care about\n" " * non-volatile registers.\n" " *\n" " * Saving state and jumping to the Rust handler takes 15 instructions, and\n" " * restoring and returning also takes 15 instructions, so we can fit the " "whole\n" " * handler in 30 instructions, under the limit of 32.\n" " */\n" ".macro current_exception_spx handler:req\n" "\tsave_volatile_to_stack\n" "\tbl \\handler\n" "\trestore_volatile_from_stack\n" "\teret\n" ".endm\n" "\n" ".section .text.vector_table_el1, \"ax\"\n" ".global vector_table_el1\n" ".balign 0x800\n" "vector_table_el1:\n" "sync_cur_sp0:\n" "\tcurrent_exception_sp0 sync_exception_current\n" "\n" ".balign 0x80\n" "irq_cur_sp0:\n" "\tcurrent_exception_sp0 irq_current\n" "\n" ".balign 0x80\n" "fiq_cur_sp0:\n" "\tcurrent_exception_sp0 fiq_current\n" "\n" ".balign 0x80\n" "serr_cur_sp0:\n" "\tcurrent_exception_sp0 serr_current\n" "\n" ".balign 0x80\n" "sync_cur_spx:\n" "\tcurrent_exception_spx sync_exception_current\n" "\n" ".balign 0x80\n" "irq_cur_spx:\n" "\tcurrent_exception_spx irq_current\n" "\n" ".balign 0x80\n" "fiq_cur_spx:\n" "\tcurrent_exception_spx fiq_current\n" "\n" ".balign 0x80\n" "serr_cur_spx:\n" "\tcurrent_exception_spx serr_current\n" "\n" ".balign 0x80\n" "sync_lower_64:\n" "\tcurrent_exception_spx sync_lower\n" "\n" ".balign 0x80\n" "irq_lower_64:\n" "\tcurrent_exception_spx irq_lower\n" "\n" ".balign 0x80\n" "fiq_lower_64:\n" "\tcurrent_exception_spx fiq_lower\n" "\n" ".balign 0x80\n" "serr_lower_64:\n" "\tcurrent_exception_spx serr_lower\n" "\n" ".balign 0x80\n" "sync_lower_32:\n" "\tcurrent_exception_spx sync_lower\n" "\n" ".balign 0x80\n" "irq_lower_32:\n" "\tcurrent_exception_spx irq_lower\n" "\n" ".balign 0x80\n" "fiq_lower_32:\n" "\tcurrent_exception_spx fiq_lower\n" "\n" ".balign 0x80\n" "serr_lower_32:\n" "\tcurrent_exception_spx serr_lower\n" "```" msgstr "" #: src/exercises/bare-metal/rtc.md:780 msgid "_idmap.S_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:784 msgid "" "```armasm\n" "/*\n" " * Copyright 2023 Google LLC\n" " *\n" " * Licensed under the Apache License, Version 2.0 (the \"License\");\n" " * you may not use this file except in compliance with the License.\n" " * You may obtain a copy of the License at\n" " *\n" " * https://www.apache.org/licenses/LICENSE-2.0\n" " *\n" " * Unless required by applicable law or agreed to in writing, software\n" " * distributed under the License is distributed on an \"AS IS\" BASIS,\n" " * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" " * See the License for the specific language governing permissions and\n" " * limitations under the License.\n" " */\n" "\n" ".set .L_TT_TYPE_BLOCK, 0x1\n" ".set .L_TT_TYPE_PAGE, 0x3\n" ".set .L_TT_TYPE_TABLE, 0x3\n" "\n" "/* Access flag. */\n" ".set .L_TT_AF, 0x1 << 10\n" "/* Not global. */\n" ".set .L_TT_NG, 0x1 << 11\n" ".set .L_TT_XN, 0x3 << 53\n" "\n" ".set .L_TT_MT_DEV, 0x0 << 2\t\t\t// MAIR #0 (DEV_nGnRE)\n" ".set .L_TT_MT_MEM, (0x1 << 2) | (0x3 << 8)\t// MAIR #1 (MEM_WBWA), inner " "shareable\n" "\n" ".set .L_BLOCK_DEV, .L_TT_TYPE_BLOCK | .L_TT_MT_DEV | .L_TT_AF | .L_TT_XN\n" ".set .L_BLOCK_MEM, .L_TT_TYPE_BLOCK | .L_TT_MT_MEM | .L_TT_AF | .L_TT_NG\n" "\n" ".section \".rodata.idmap\", \"a\", %progbits\n" ".global idmap\n" ".align 12\n" "idmap:\n" "\t/* level 1 */\n" "\t.quad\t\t.L_BLOCK_DEV | 0x0\t\t // 1 GiB of device mappings\n" "\t.quad\t\t.L_BLOCK_MEM | 0x40000000\t// 1 GiB of DRAM\n" "\t.fill\t\t254, 8, 0x0\t\t\t// 254 GiB of unmapped VA space\n" "\t.quad\t\t.L_BLOCK_DEV | 0x4000000000 // 1 GiB of device mappings\n" "\t.fill\t\t255, 8, 0x0\t\t\t// 255 GiB of remaining VA space\n" "```" msgstr "" #: src/exercises/bare-metal/rtc.md:829 msgid "_image.ld_ (you shouldn't need to change this):" msgstr "" #: src/exercises/bare-metal/rtc.md:833 msgid "" "```ld\n" "/*\n" " * Copyright 2023 Google LLC\n" " *\n" " * Licensed under the Apache License, Version 2.0 (the \"License\");\n" " * you may not use this file except in compliance with the License.\n" " * You may obtain a copy of the License at\n" " *\n" " * https://www.apache.org/licenses/LICENSE-2.0\n" " *\n" " * Unless required by applicable law or agreed to in writing, software\n" " * distributed under the License is distributed on an \"AS IS\" BASIS,\n" " * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" " * See the License for the specific language governing permissions and\n" " * limitations under the License.\n" " */\n" "\n" "/*\n" " * Code will start running at this symbol which is placed at the start of " "the\n" " * image.\n" " */\n" "ENTRY(entry)\n" "\n" "MEMORY\n" "{\n" "\timage : ORIGIN = 0x40080000, LENGTH = 2M\n" "}\n" "\n" "SECTIONS\n" "{\n" "\t/*\n" "\t * Collect together the code.\n" "\t */\n" "\t.init : ALIGN(4096) {\n" "\t\ttext_begin = .;\n" "\t\t*(.init.entry)\n" "\t\t*(.init.*)\n" "\t} >image\n" "\t.text : {\n" "\t\t*(.text.*)\n" "\t} >image\n" "\ttext_end = .;\n" "\n" "\t/*\n" "\t * Collect together read-only data.\n" "\t */\n" "\t.rodata : ALIGN(4096) {\n" "\t\trodata_begin = .;\n" "\t\t*(.rodata.*)\n" "\t} >image\n" "\t.got : {\n" "\t\t*(.got)\n" "\t} >image\n" "\trodata_end = .;\n" "\n" "\t/*\n" "\t * Collect together the read-write data including .bss at the end which\n" "\t * will be zero'd by the entry code.\n" "\t */\n" "\t.data : ALIGN(4096) {\n" "\t\tdata_begin = .;\n" "\t\t*(.data.*)\n" "\t\t/*\n" "\t\t * The entry point code assumes that .data is a multiple of 32\n" "\t\t * bytes long.\n" "\t\t */\n" "\t\t. = ALIGN(32);\n" "\t\tdata_end = .;\n" "\t} >image\n" "\n" "\t/* Everything beyond this point will not be included in the binary. */\n" "\tbin_end = .;\n" "\n" "\t/* The entry point code assumes that .bss is 16-byte aligned. */\n" "\t.bss : ALIGN(16) {\n" "\t\tbss_begin = .;\n" "\t\t*(.bss.*)\n" "\t\t*(COMMON)\n" "\t\t. = ALIGN(16);\n" "\t\tbss_end = .;\n" "\t} >image\n" "\n" "\t.stack (NOLOAD) : ALIGN(4096) {\n" "\t\tboot_stack_begin = .;\n" "\t\t. += 40 * 4096;\n" "\t\t. = ALIGN(4096);\n" "\t\tboot_stack_end = .;\n" "\t} >image\n" "\n" "\t. = ALIGN(4K);\n" "\tPROVIDE(dma_region = .);\n" "\n" "\t/*\n" "\t * Remove unused sections from the image.\n" "\t */\n" "\t/DISCARD/ : {\n" "\t\t/* The image loads itself so doesn't need these sections. */\n" "\t\t*(.gnu.hash)\n" "\t\t*(.hash)\n" "\t\t*(.interp)\n" "\t\t*(.eh_frame_hdr)\n" "\t\t*(.eh_frame)\n" "\t\t*(.note.gnu.build-id)\n" "\t}\n" "}\n" "```" msgstr "" #: 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:989 msgid "" "```toml\n" "[build]\n" "target = \"aarch64-unknown-none\"\n" "rustflags = [\"-C\", \"link-arg=-Timage.ld\"]\n" "```" msgstr "" #: src/exercises/bare-metal/rtc.md:995 msgid "Run the code in QEMU with `make qemu`." msgstr "" #: src/concurrency.md:1 msgid "Welcome to Concurrency in Rust" msgstr "Velkommen til Concurrency i Rust" #: src/concurrency.md:3 msgid "" "Rust has full support for concurrency using OS threads with mutexes and " "channels." msgstr "" #: src/concurrency.md:6 msgid "" "The Rust type system plays an important role in making many concurrency bugs " "compile time bugs. This is often referred to as _fearless concurrency_ since " "you can rely on the compiler to ensure correctness at runtime." msgstr "" #: src/concurrency/threads.md:3 msgid "Rust threads work similarly to threads in other languages:" msgstr "Tråde (eng: _threads_) i Rust virker på samme måde som i andre sprog:" #: src/concurrency/threads.md:12 msgid "\"Count in thread: {i}!\"" msgstr "\"Tæller i tråden: {i}!\"" #: src/concurrency/threads.md:18 msgid "\"Main thread: {i}\"" msgstr "\"Hovedtråden: {i}\"" #: src/concurrency/threads.md:24 msgid "Threads are all daemon threads, the main thread does not wait for them." msgstr "" "Tråde er alle dæmontråde (eng: _daemon threads_), hvilket vil sige at " "hovedtråden ikke venter på dem." #: src/concurrency/threads.md:25 msgid "Thread panics are independent of each other." msgstr "Hver tråd kan gå i panik uafhængigt af andre tråde." #: src/concurrency/threads.md:26 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 msgid "" "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 msgid "" "Use `let handle = thread::spawn(...)` and later `handle.join()` to wait for " "the thread to finish." msgstr "" "Brug `let handle = thread::spawn(...)` og senere `handle.join()` for at " "vente på at tråden afsluttes." #: src/concurrency/threads.md:38 msgid "Trigger a panic in the thread, notice how this doesn't affect `main`." msgstr "Skab en panik i tråden, bemærk hvordan dette ikke påvirker `main`." #: src/concurrency/threads.md:40 msgid "" "Use the `Result` return value from `handle.join()` to get access to the " "panic payload. This is a good time to talk about [`Any`](https://doc.rust-" "lang.org/std/any/index.html)." msgstr "" "Bruge `Result`\\-returværdien fra `handle.join()` til at få adgang til " "panikkens nyttelast. Dette er et godt tidspunkt til at snakke om [`Any`]" "(https://doc.rust-lang.org/std/any/index.html)." #: src/concurrency/scoped-threads.md:3 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/" "fn.scope.html) for this:" msgstr "" "Du kan dog bruge en [tråd med virkefelt (eng: _scoped thread_)](https://doc." "rust-lang.org/std/thread/fn.scope.html) for at opnå dette:" #: src/concurrency/scoped-threads.md:40 msgid "" "The reason for that is that when the `thread::scope` function completes, all " "the threads are guaranteed to be joined, so they can return borrowed data." msgstr "" "Grunden er, at `thread::scope`\\-funktionen garanterer at alle trådene er " "blevet forenet med hovedtråden når kaldet afsluttet. De vil således " "returnere det lånte data." #: src/concurrency/scoped-threads.md:41 msgid "" "Normal Rust borrowing rules apply: you can either borrow mutably by one " "thread, or immutably by any number of threads." msgstr "" "De normale låneregler for Rust gælder: du kan enten lade én tråd låne data " "for at ændre på det, eller du kan lade flere tråde låne data uden at ændre " "på det." #: src/concurrency/channels.md:3 msgid "" "Rust channels have two parts: a `Sender` and a `Receiver`. The two " "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 msgid "\"Received: {:?}\"" msgstr "\"Modtaget: {:?}\"" #: src/concurrency/channels.md:27 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 msgid "" "`send()` and `recv()` return `Result`. If they return `Err`, it means the " "counterpart `Sender` or `Receiver` is dropped and the channel is closed." msgstr "" #: src/concurrency/channels/unbounded.md:3 msgid "You get an unbounded and asynchronous channel with `mpsc::channel()`:" msgstr "" #: src/concurrency/channels/unbounded.md:16 #: src/concurrency/channels/bounded.md:16 msgid "\"Message {i}\"" msgstr "\"Besked {i}\"" #: src/concurrency/channels/unbounded.md:17 #: src/concurrency/channels/bounded.md:17 msgid "\"{thread_id:?}: sent Message {i}\"" msgstr "\"{thread_id:?}: sendte Besked {i}\"" #: src/concurrency/channels/unbounded.md:19 #: src/concurrency/channels/bounded.md:19 msgid "\"{thread_id:?}: done\"" msgstr "\"{thread_id:?}: færdig\"" #: src/concurrency/channels/unbounded.md:24 #: src/concurrency/channels/bounded.md:24 msgid "\"Main: got {msg}\"" msgstr "\"Hovedtråden: modtog {msg}\"" #: src/concurrency/channels/bounded.md:3 msgid "" "With bounded (synchronous) channels, `send` can block the current thread:" msgstr "" #: src/concurrency/channels/bounded.md:31 msgid "" "Calling `send` will block the current thread until there is space in the " "channel for the new message. The thread can be blocked indefinitely if there " "is nobody who reads from the channel." msgstr "" #: src/concurrency/channels/bounded.md:32 msgid "" "A call to `send` will abort with an error (that is why it returns `Result`) " "if the channel is closed. A channel is closed when the receiver is dropped." msgstr "" #: src/concurrency/channels/bounded.md:33 msgid "" "A bounded channel with a size of zero is called a \"rendezvous channel\". " "Every send will block the current thread until another thread calls `read`." msgstr "" #: src/concurrency/send-sync.md:1 msgid "`Send` and `Sync`" msgstr "`Send` og `Sync`" #: src/concurrency/send-sync.md:3 msgid "" "How does Rust know to forbid shared access across thread? The answer is in " "two traits:" msgstr "" #: src/concurrency/send-sync.md:5 msgid "" "[`Send`](https://doc.rust-lang.org/std/marker/trait.Send.html): a type `T` " "is `Send` if it is safe to move a `T` across a thread boundary." msgstr "" #: src/concurrency/send-sync.md:7 msgid "" "[`Sync`](https://doc.rust-lang.org/std/marker/trait.Sync.html): a type `T` " "is `Sync` if it is safe to move a `&T` across a thread boundary." msgstr "" #: src/concurrency/send-sync.md:10 msgid "" "`Send` and `Sync` are [unsafe traits](../unsafe/unsafe-traits.md). The " "compiler will automatically derive them for your types as long as they only " "contain `Send` and `Sync` types. You can also implement them manually when " "you know it is valid." msgstr "" #: src/concurrency/send-sync.md:20 msgid "" "One can think of these traits as markers that the type has certain thread-" "safety properties." msgstr "" #: src/concurrency/send-sync.md:21 msgid "They can be used in the generic constraints as normal traits." msgstr "" #: src/concurrency/send-sync/send.md:1 msgid "`Send`" msgstr "`Send`" #: src/concurrency/send-sync/send.md:3 msgid "" "A type `T` is [`Send`](https://doc.rust-lang.org/std/marker/trait.Send.html) " "if it is safe to move a `T` value to another thread." msgstr "" #: src/concurrency/send-sync/send.md:5 msgid "" "The effect of moving ownership to another thread is that _destructors_ will " "run in that thread. So the question is when you can allocate a value in one " "thread and deallocate it in another." msgstr "" #: src/concurrency/send-sync/send.md:13 msgid "" "As an example, a connection to the SQLite library must only be accessed from " "a single thread." msgstr "" #: src/concurrency/send-sync/sync.md:1 msgid "`Sync`" msgstr "`Sync`" #: src/concurrency/send-sync/sync.md:3 msgid "" "A type `T` is [`Sync`](https://doc.rust-lang.org/std/marker/trait.Sync.html) " "if it is safe to access a `T` value from multiple threads at the same time." msgstr "" #: src/concurrency/send-sync/sync.md:6 msgid "More precisely, the definition is:" msgstr "" #: src/concurrency/send-sync/sync.md:8 msgid "`T` is `Sync` if and only if `&T` is `Send`" msgstr "" #: src/concurrency/send-sync/sync.md:14 msgid "" "This statement is essentially a shorthand way of saying that if a type is " "thread-safe for shared use, it is also thread-safe to pass references of it " "across threads." msgstr "" #: src/concurrency/send-sync/sync.md:16 msgid "" "This is because if a type is Sync it means that it can be shared across " "multiple threads without the risk of data races or other synchronization " "issues, so it is safe to move it to another thread. A reference to the type " "is also safe to move to another thread, because the data it references can " "be accessed from any thread safely." msgstr "" #: src/concurrency/send-sync/examples.md:3 msgid "`Send + Sync`" msgstr "`Send + Sync`" #: src/concurrency/send-sync/examples.md:5 msgid "Most types you come across are `Send + Sync`:" msgstr "" #: src/concurrency/send-sync/examples.md:7 msgid "`i8`, `f32`, `bool`, `char`, `&str`, ..." msgstr "`i8`, `f32`, `bool`, `char`, `&str`, ..." #: src/concurrency/send-sync/examples.md:8 msgid "`(T1, T2)`, `[T; N]`, `&[T]`, `struct { x: T }`, ..." msgstr "`(T1, T2)`, `[T; N]`, `&[T]`, `struct { x: T }`, ..." #: src/concurrency/send-sync/examples.md:9 msgid "`String`, `Option`, `Vec`, `Box`, ..." msgstr "`String`, `Option`, `Vec`, `Box`, ..." #: src/concurrency/send-sync/examples.md:10 msgid "`Arc`: Explicitly thread-safe via atomic reference count." msgstr "" #: src/concurrency/send-sync/examples.md:11 msgid "`Mutex`: Explicitly thread-safe via internal locking." msgstr "" #: src/concurrency/send-sync/examples.md:12 msgid "`AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions." msgstr "" #: src/concurrency/send-sync/examples.md:14 msgid "" "The generic types are typically `Send + Sync` when the type parameters are " "`Send + Sync`." msgstr "" #: src/concurrency/send-sync/examples.md:17 msgid "`Send + !Sync`" msgstr "`Send + !Sync`" #: src/concurrency/send-sync/examples.md:19 msgid "" "These types can be moved to other threads, but they're not thread-safe. " "Typically because of interior mutability:" msgstr "" #: src/concurrency/send-sync/examples.md:22 msgid "`mpsc::Sender`" msgstr "`mpsc::Sender`" #: src/concurrency/send-sync/examples.md:23 msgid "`mpsc::Receiver`" msgstr "`mpsc::Receiver`" #: src/concurrency/send-sync/examples.md:24 msgid "`Cell`" msgstr "`Cell`" #: src/concurrency/send-sync/examples.md:25 msgid "`RefCell`" msgstr "`RefCell`" #: src/concurrency/send-sync/examples.md:27 msgid "`!Send + Sync`" msgstr "`!Send + Sync`" #: src/concurrency/send-sync/examples.md:29 msgid "" "These types are thread-safe, but they cannot be moved to another thread:" msgstr "" #: src/concurrency/send-sync/examples.md:31 msgid "" "`MutexGuard`: Uses OS level primitives which must be deallocated on the " "thread which created them." msgstr "" #: src/concurrency/send-sync/examples.md:34 msgid "`!Send + !Sync`" msgstr "`!Send + !Sync`" #: src/concurrency/send-sync/examples.md:36 msgid "These types are not thread-safe and cannot be moved to other threads:" msgstr "" #: src/concurrency/send-sync/examples.md:38 msgid "" "`Rc`: each `Rc` has a reference to an `RcBox`, which contains a non-" "atomic reference count." msgstr "" #: src/concurrency/send-sync/examples.md:40 msgid "" "`*const T`, `*mut T`: Rust assumes raw pointers may have special concurrency " "considerations." msgstr "" #: src/concurrency/shared_state.md:3 msgid "" "Rust uses the type system to enforce synchronization of shared data. This is " "primarily done via two types:" msgstr "" #: src/concurrency/shared_state.md:6 msgid "" "[`Arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html), atomic " "reference counted `T`: handles sharing between threads and takes care to " "deallocate `T` when the last reference is dropped," msgstr "" #: src/concurrency/shared_state.md:8 msgid "" "[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html): ensures " "mutually exclusive access to the `T` value." msgstr "" #: src/concurrency/shared_state/arc.md:1 msgid "`Arc`" msgstr "`Arc`" #: src/concurrency/shared_state/arc.md:3 msgid "" "[`Arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html) allows shared " "read-only access via `Arc::clone`:" msgstr "" #: src/concurrency/shared_state/arc.md:16 msgid "\"{thread_id:?}: {v:?}\"" msgstr "" #: src/concurrency/shared_state/arc.md:21 #: src/concurrency/shared_state/example.md:17 #: src/concurrency/shared_state/example.md:45 msgid "\"v: {v:?}\"" msgstr "" #: src/concurrency/shared_state/arc.md:29 msgid "" "`Arc` stands for \"Atomic Reference Counted\", a thread safe version of `Rc` " "that uses atomic operations." msgstr "" #: src/concurrency/shared_state/arc.md:31 msgid "" "`Arc` implements `Clone` whether or not `T` does. It implements `Send` " "and `Sync` if and only if `T` implements them both." msgstr "" #: src/concurrency/shared_state/arc.md:33 msgid "" "`Arc::clone()` has the cost of atomic operations that get executed, but " "after that the use of the `T` is free." msgstr "" #: src/concurrency/shared_state/arc.md:35 msgid "" "Beware of reference cycles, `Arc` does not use a garbage collector to detect " "them." msgstr "" #: src/concurrency/shared_state/arc.md:36 msgid "`std::sync::Weak` can help." msgstr "`std::sync::Weak` kan hjælpe." #: src/concurrency/shared_state/mutex.md:1 msgid "`Mutex`" msgstr "`Mutex`" #: src/concurrency/shared_state/mutex.md:3 msgid "" "[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html) ensures " "mutual exclusion _and_ allows mutable access to `T` behind a read-only " "interface:" msgstr "" #: src/concurrency/shared_state/mutex.md:11 #: src/concurrency/shared_state/mutex.md:18 msgid "\"v: {:?}\"" msgstr "\"v: {:?}\"" #: src/concurrency/shared_state/mutex.md:22 msgid "" "Notice how we have a [`impl Sync for Mutex`](https://doc.rust-" "lang.org/std/sync/struct.Mutex.html#impl-Sync-for-Mutex%3CT%3E) blanket " "implementation." msgstr "" #: src/concurrency/shared_state/mutex.md:31 msgid "" "`Mutex` in Rust looks like a collection with just one element - the " "protected data." msgstr "" #: src/concurrency/shared_state/mutex.md:32 msgid "" "It is not possible to forget to acquire the mutex before accessing the " "protected data." msgstr "" #: src/concurrency/shared_state/mutex.md:33 msgid "" "You can get an `&mut T` from an `&Mutex` by taking the lock. The " "`MutexGuard` ensures that the `&mut T` doesn't outlive the lock being held." msgstr "" #: src/concurrency/shared_state/mutex.md:35 msgid "" "`Mutex` implements both `Send` and `Sync` iff (if and only if) `T` " "implements `Send`." msgstr "" #: src/concurrency/shared_state/mutex.md:36 msgid "A read-write lock counterpart - `RwLock`." msgstr "" #: src/concurrency/shared_state/mutex.md:37 msgid "Why does `lock()` return a `Result`? " msgstr "" #: src/concurrency/shared_state/mutex.md:38 msgid "" "If the thread that held the `Mutex` panicked, the `Mutex` becomes " "\"poisoned\" to signal that the data it protected might be in an " "inconsistent state. Calling `lock()` on a poisoned mutex fails with a " "[`PoisonError`](https://doc.rust-lang.org/std/sync/struct.PoisonError.html). " "You can call `into_inner()` on the error to recover the data regardless." msgstr "" #: src/concurrency/shared_state/example.md:3 msgid "Let us see `Arc` and `Mutex` in action:" msgstr "" #: src/concurrency/shared_state/example.md:6 msgid "// use std::sync::{Arc, Mutex};\n" msgstr "// use std::sync::{Arc, Mutex};\n" #: src/concurrency/shared_state/example.md:23 msgid "Possible solution:" msgstr "" #: src/concurrency/shared_state/example.md:49 msgid "Notable parts:" msgstr "" #: src/concurrency/shared_state/example.md:51 msgid "" "`v` is wrapped in both `Arc` and `Mutex`, because their concerns are " "orthogonal." msgstr "" #: src/concurrency/shared_state/example.md:52 msgid "" "Wrapping a `Mutex` in an `Arc` is a common pattern to share mutable state " "between threads." msgstr "" #: src/concurrency/shared_state/example.md:53 msgid "" "`v: Arc<_>` needs to be cloned as `v2` before it can be moved into another " "thread. Note `move` was added to the lambda signature." msgstr "" #: src/concurrency/shared_state/example.md:54 msgid "" "Blocks are introduced to narrow the scope of the `LockGuard` as much as " "possible." msgstr "" #: src/exercises/concurrency/morning.md:3 msgid "Let us practice our new concurrency skills with" msgstr "" #: src/exercises/concurrency/morning.md:5 msgid "Dining philosophers: a classic problem in concurrency." msgstr "" #: src/exercises/concurrency/morning.md:7 msgid "" "Multi-threaded link checker: a larger project where you'll use Cargo to " "download dependencies and then check links in parallel." msgstr "" #: src/exercises/concurrency/dining-philosophers.md:3 msgid "The dining philosophers problem is a classic problem in concurrency:" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:5 msgid "" "Five philosophers dine together at the same table. Each philosopher has " "their own place at the table. There is a fork between each plate. The dish " "served is a kind of spaghetti which has to be eaten with two forks. Each " "philosopher can only alternately think and eat. Moreover, a philosopher can " "only eat their spaghetti when they have both a left and right fork. Thus two " "forks will only be available when their two nearest neighbors are thinking, " "not eating. After an individual philosopher finishes eating, they will put " "down both forks." msgstr "" #: src/exercises/concurrency/dining-philosophers.md:13 msgid "" "You will need a local [Cargo installation](../../cargo/running-locally.md) " "for this exercise. Copy the code below to a file called `src/main.rs`, fill " "out the blanks, and test that `cargo run` does not deadlock:" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:28 #: src/exercises/concurrency/dining-philosophers-async.md:23 msgid "" "// left_fork: ...\n" " // right_fork: ...\n" " // thoughts: ...\n" 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/solutions-afternoon.md:25 msgid "\"Eureka! {} has a new idea!\"" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:41 #: src/exercises/concurrency/dining-philosophers-async.md:36 #: src/exercises/concurrency/solutions-afternoon.md:30 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/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/solutions-afternoon.md:45 msgid "\"Socrates\"" msgstr "\"Sokrates\"" #: 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 "\"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/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\"" #: src/exercises/concurrency/dining-philosophers.md:51 #: src/exercises/concurrency/dining-philosophers-async.md:47 #: src/exercises/concurrency/solutions-afternoon.md:49 msgid "// Create forks\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:53 #: src/exercises/concurrency/dining-philosophers-async.md:49 #: src/exercises/concurrency/solutions-afternoon.md:53 msgid "// Create philosophers\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:55 msgid "// Make each of them think and eat 100 times\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:57 #: src/exercises/concurrency/dining-philosophers-async.md:53 #: src/exercises/concurrency/solutions-afternoon.md:88 msgid "// Output their thoughts\n" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:61 msgid "You can use the following `Cargo.toml`:" msgstr "" #: src/exercises/concurrency/dining-philosophers.md:65 msgid "" "```toml\n" "[package]\n" "name = \"dining-philosophers\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "```" msgstr "" "```toml\n" "[package]\n" "name = \"dining-philosophers\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "```" #: src/exercises/concurrency/link-checker.md:3 msgid "" "Let us use our new knowledge to create a multi-threaded link checker. It " "should start at a webpage and check that links on the page are valid. It " "should recursively check other pages on the same domain and keep doing this " "until all pages have been validated." msgstr "" #: src/exercises/concurrency/link-checker.md:8 msgid "" "For this, you will need an HTTP client such as [`reqwest`](https://docs.rs/" "reqwest/). Create a new Cargo project and `reqwest` it as a dependency with:" msgstr "" #: src/exercises/concurrency/link-checker.md:17 msgid "" "If `cargo add` fails with `error: no such subcommand`, then please edit the " "`Cargo.toml` file by hand. Add the dependencies listed below." msgstr "" #: src/exercises/concurrency/link-checker.md:20 msgid "" "You will also need a way to find links. We can use [`scraper`](https://docs." "rs/scraper/) for that:" msgstr "" #: src/exercises/concurrency/link-checker.md:26 msgid "" "Finally, we'll need some way of handling errors. We use [`thiserror`]" "(https://docs.rs/thiserror/) for that:" msgstr "" #: src/exercises/concurrency/link-checker.md:33 msgid "" "The `cargo add` calls will update the `Cargo.toml` file to look like this:" msgstr "" #: src/exercises/concurrency/link-checker.md:37 msgid "" "```toml\n" "[package]\n" "name = \"link-checker\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "publish = false\n" "\n" "[dependencies]\n" "reqwest = { version = \"0.11.12\", features = [\"blocking\", \"rustls-" "tls\"] }\n" "scraper = \"0.13.0\"\n" "thiserror = \"1.0.37\"\n" "```" msgstr "" "```toml\n" "[package]\n" "name = \"link-checker\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "publish = false\n" "\n" "[dependencies]\n" "reqwest = { version = \"0.11.12\", features = [\"blocking\", \"rustls-" "tls\"] }\n" "scraper = \"0.13.0\"\n" "thiserror = \"1.0.37\"\n" "```" #: src/exercises/concurrency/link-checker.md:50 msgid "" "You can now download the start page. Try with a small site such as `https://" "www.google.org/`." msgstr "" #: src/exercises/concurrency/link-checker.md:53 msgid "Your `src/main.rs` file should look something like this:" msgstr "" #: src/exercises/concurrency/link-checker.md:64 #: src/exercises/concurrency/solutions-morning.md:95 msgid "\"request error: {0}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:66 #: src/exercises/concurrency/solutions-morning.md:97 msgid "\"bad http response: {0}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:77 #: src/exercises/concurrency/solutions-morning.md:108 msgid "\"Checking {:#}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:95 #: src/exercises/concurrency/solutions-morning.md:126 msgid "\"href\"" msgstr "\"href\"" #: src/exercises/concurrency/link-checker.md:102 #: src/exercises/concurrency/solutions-morning.md:133 msgid "\"On {base_url:#}: ignored unparsable {href:?}: {err}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:111 #: src/exercises/concurrency/solutions-morning.md:246 msgid "\"https://www.google.org\"" msgstr "\"https://www.google.org\"" #: src/exercises/concurrency/link-checker.md:114 msgid "\"Links: {links:#?}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:115 msgid "\"Could not extract links: {err:#}\"" msgstr "" #: src/exercises/concurrency/link-checker.md:120 msgid "Run the code in `src/main.rs` with" msgstr "" #: src/exercises/concurrency/link-checker.md:128 msgid "" "Use threads to check the links in parallel: send the URLs to be checked to a " "channel and let a few threads check the URLs in parallel." msgstr "" #: src/exercises/concurrency/link-checker.md:130 msgid "" "Extend this to recursively extract links from all pages on the `www.google." "org` domain. Put an upper limit of 100 pages or so so that you don't end up " "being blocked by the site." msgstr "" #: src/async.md:1 msgid "Async Rust" msgstr "" #: src/async.md:3 msgid "" "\"Async\" is a concurrency model where multiple tasks are executed " "concurrently by executing each task until it would block, then switching to " "another task that is ready to make progress. The model allows running a " "larger number of tasks on a limited number of threads. This is because the " "per-task overhead is typically very low and operating systems provide " "primitives for efficiently identifying I/O that is able to proceed." msgstr "" #: src/async.md:10 msgid "" "Rust's asynchronous operation is based on \"futures\", which represent work " "that may be completed in the future. Futures are \"polled\" until they " "signal that they are complete." msgstr "" #: src/async.md:14 msgid "" "Futures are polled by an async runtime, and several different runtimes are " "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 " "callback-based, and not polled. Async Python programs require a \"loop\", " "similar to a runtime in Rust." msgstr "" #: src/async.md:23 msgid "" "JavaScript's `Promise` is similar, but again callback-based. The language " "runtime implements the event loop, so many of the details of Promise " "resolution are hidden." msgstr "" #: src/async/async-await.md:1 msgid "`async`/`await`" msgstr "`async`/`await`" #: src/async/async-await.md:3 msgid "" "At a high level, async Rust code looks very much like \"normal\" sequential " "code:" msgstr "" #: src/async/async-await.md:10 msgid "\"Count is: {i}!\"" msgstr "" #: src/async/async-await.md:27 msgid "" "Note that this is a simplified example to show the syntax. There is no long " "running operation or any real concurrency in it!" msgstr "" #: src/async/async-await.md:30 msgid "What is the return type of an async call?" msgstr "" #: src/async/async-await.md:31 msgid "Use `let future: () = async_main(10);` in `main` to see the type." msgstr "" #: src/async/async-await.md:33 msgid "" "The \"async\" keyword is syntactic sugar. The compiler replaces the return " "type with a future. " msgstr "" #: src/async/async-await.md:36 msgid "" "You cannot make `main` async, without additional instructions to the " "compiler on how to use the returned future." msgstr "" #: src/async/async-await.md:39 msgid "" "You need an executor to run async code. `block_on` blocks the current thread " "until the provided future has run to completion. " msgstr "" #: src/async/async-await.md:42 msgid "" "`.await` asynchronously waits for the completion of another operation. " "Unlike `block_on`, `.await` doesn't block the current thread." msgstr "" #: src/async/async-await.md:45 msgid "" "`.await` can only be used inside an `async` function (or block; these are " "introduced later). " msgstr "" #: src/async/futures.md:3 msgid "" "[`Future`](https://doc.rust-lang.org/std/future/trait.Future.html) is a " "trait, implemented by objects that represent an operation that may not be " "complete yet. A future can be polled, and `poll` returns a [`Poll`](https://" "doc.rust-lang.org/std/task/enum.Poll.html)." msgstr "" #: src/async/futures.md:23 msgid "" "An async function returns an `impl Future`. It's also possible (but " "uncommon) to implement `Future` for your own types. For example, the " "`JoinHandle` returned from `tokio::spawn` implements `Future` to allow " "joining to it." msgstr "" #: src/async/futures.md:27 msgid "" "The `.await` keyword, applied to a Future, causes the current async function " "to pause until that Future is ready, and then evaluates to its output." msgstr "" #: src/async/futures.md:32 msgid "" "The `Future` and `Poll` types are implemented exactly as shown; click the " "links to show the implementations in the docs." msgstr "" #: src/async/futures.md:35 msgid "" "We will not get to `Pin` and `Context`, as we will focus on writing async " "code, rather than building new async primitives. Briefly:" msgstr "" #: src/async/futures.md:38 msgid "" "`Context` allows a Future to schedule itself to be polled again when an " "event occurs." msgstr "" #: src/async/futures.md:41 msgid "" "`Pin` ensures that the Future isn't moved in memory, so that pointers into " "that future remain valid. This is required to allow references to remain " "valid after an `.await`." msgstr "" #: src/async/runtimes.md:3 msgid "" "A _runtime_ provides support for performing operations asynchronously (a " "_reactor_) and is responsible for executing futures (an _executor_). Rust " "does not have a \"built-in\" runtime, but several options are available:" msgstr "" #: src/async/runtimes.md:7 msgid "" "[Tokio](https://tokio.rs/): performant, with a well-developed ecosystem of " "functionality like [Hyper](https://hyper.rs/) for HTTP or [Tonic](https://" "github.com/hyperium/tonic) for gRPC." msgstr "" #: src/async/runtimes.md:10 msgid "" "[async-std](https://async.rs/): aims to be a \"std for async\", and includes " "a basic runtime in `async::task`." msgstr "" #: src/async/runtimes.md:12 msgid "[smol](https://docs.rs/smol/latest/smol/): simple and lightweight" msgstr "" #: src/async/runtimes.md:14 msgid "" "Several larger applications have their own runtimes. For example, [Fuchsia]" "(https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/src/lib/fuchsia-" "async/src/lib.rs) already has one." msgstr "" #: src/async/runtimes.md:20 msgid "" "Note that of the listed runtimes, only Tokio is supported in the Rust " "playground. The playground also does not permit any I/O, so most interesting " "async things can't run in the playground." msgstr "" #: src/async/runtimes.md:24 msgid "" "Futures are \"inert\" in that they do not do anything (not even start an I/O " "operation) unless there is an executor polling them. This differs from JS " "Promises, for example, which will run to completion even if they are never " "used." msgstr "" #: src/async/runtimes/tokio.md:4 msgid "Tokio provides: " msgstr "" #: src/async/runtimes/tokio.md:6 msgid "A multi-threaded runtime for executing asynchronous code." msgstr "" #: src/async/runtimes/tokio.md:7 msgid "An asynchronous version of the standard library." msgstr "" #: src/async/runtimes/tokio.md:8 msgid "A large ecosystem of libraries." msgstr "" #: src/async/runtimes/tokio.md:15 msgid "\"Count in task: {i}!\"" msgstr "" #: src/async/runtimes/tokio.md:25 msgid "\"Main task: {i}\"" msgstr "" #: src/async/runtimes/tokio.md:33 msgid "With the `tokio::main` macro we can now make `main` async." msgstr "" #: src/async/runtimes/tokio.md:35 msgid "The `spawn` function creates a new, concurrent \"task\"." msgstr "" #: src/async/runtimes/tokio.md:37 msgid "Note: `spawn` takes a `Future`, you don't call `.await` on `count_to`." msgstr "" #: src/async/runtimes/tokio.md:39 msgid "**Further exploration:**" msgstr "" #: src/async/runtimes/tokio.md:41 msgid "" "Why does `count_to` not (usually) get to 10? This is an example of async " "cancellation. `tokio::spawn` returns a handle which can be awaited to wait " "until it finishes." msgstr "" #: src/async/runtimes/tokio.md:45 msgid "Try `count_to(10).await` instead of spawning." msgstr "" #: src/async/runtimes/tokio.md:47 msgid "Try awaiting the task returned from `tokio::spawn`." msgstr "" #: src/async/tasks.md:3 msgid "Rust has a task system, which is a form of lightweight threading." msgstr "" #: src/async/tasks.md:5 msgid "" "A task has a single top-level future which the executor polls to make " "progress. That future may have one or more nested futures that its `poll` " "method polls, corresponding loosely to a call stack. Concurrency within a " "task is possible by polling multiple child futures, such as racing a timer " "and an I/O operation." msgstr "" #: src/async/tasks.md:16 msgid "\"127.0.0.1:6142\"" msgstr "\"127.0.0.1:6142\"" #: src/async/tasks.md:17 msgid "\"listening on port 6142\"" msgstr "" #: src/async/tasks.md:22 msgid "\"connection from {addr:?}\"" msgstr "" #: src/async/tasks.md:25 msgid "b\"Who are you?\\n\"" msgstr "" #: src/async/tasks.md:26 src/async/tasks.md:37 src/async/tasks.md:43 msgid "\"socket error: {e:?}\"" msgstr "" #: src/async/tasks.md:34 msgid "\"Thanks for dialing in, {name}!\\n\"" msgstr "" #: src/async/tasks.md:52 src/async/control-flow/join.md:36 msgid "" "Copy this example into your prepared `src/main.rs` and run it from there." msgstr "" #: src/async/tasks.md:54 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 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 msgid "" "Refactor the async block into a function, and improve the error handling " "using `?`." msgstr "" #: src/async/channels.md:3 msgid "" "Several crates have support for asynchronous channels. For instance `tokio`:" msgstr "" #: src/async/channels.md:13 msgid "\"Received {count} pings so far.\"" msgstr "" #: src/async/channels.md:16 msgid "\"ping_handler complete\"" msgstr "" #: src/async/channels.md:24 msgid "\"Failed to send ping.\"" msgstr "" #: src/async/channels.md:25 msgid "\"Sent {} pings so far.\"" msgstr "" #: src/async/channels.md:29 msgid "\"Something went wrong in ping handler task.\"" msgstr "" #: src/async/channels.md:35 msgid "Change the channel size to `3` and see how it affects the execution." msgstr "" #: src/async/channels.md:37 msgid "" "Overall, the interface is similar to the `sync` channels as seen in the " "[morning class](concurrency/channels.md)." msgstr "" #: src/async/channels.md:40 msgid "Try removing the `std::mem::drop` call. What happens? Why?" msgstr "" #: src/async/channels.md:42 msgid "" "The [Flume](https://docs.rs/flume/latest/flume/) crate has channels that " "implement both `sync` and `async` `send` and `recv`. This can be convenient " "for complex applications with both IO and heavy CPU processing tasks." msgstr "" #: src/async/channels.md:46 msgid "" "What makes working with `async` channels preferable is the ability to " "combine them with other `future`s to combine them and create complex control " "flow." msgstr "" #: src/async/control-flow.md:1 msgid "Futures Control Flow" msgstr "" #: src/async/control-flow.md:3 msgid "" "Futures can be combined together to produce concurrent compute flow graphs. " "We have already seen tasks, that function as independent threads of " "execution." msgstr "" #: src/async/control-flow.md:6 msgid "[Join](control-flow/join.md)" msgstr "[Join](control-flow/join.md)" #: src/async/control-flow.md:7 msgid "[Select](control-flow/select.md)" msgstr "[Select](control-flow/select.md)" #: src/async/control-flow/join.md:3 msgid "" "A join operation waits until all of a set of futures are ready, and returns " "a collection of their results. This is similar to `Promise.all` in " "JavaScript or `asyncio.gather` in Python." msgstr "" #: src/async/control-flow/join.md:21 msgid "\"https://google.com\"" msgstr "\"https://google.com\"" #: src/async/control-flow/join.md:22 msgid "\"https://httpbin.org/ip\"" msgstr "\"https://httpbin.org/ip\"" #: src/async/control-flow/join.md:23 msgid "\"https://play.rust-lang.org/\"" msgstr "\"https://play.rust-lang.org/\"" #: src/async/control-flow/join.md:24 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 " "you must know how many futures you will have at compile time. This is " "currently in the `futures` crate, soon to be stabilised in `std::future`." msgstr "" #: src/async/control-flow/join.md:42 msgid "" "The risk of `join` is that one of the futures may never resolve, this would " "cause your program to stall. " msgstr "" #: src/async/control-flow/join.md:45 msgid "" "You can also combine `join_all` with `join!` for instance to join all " "requests to an http service as well as a database query. Try adding a " "`tokio::time::sleep` to the future, using `futures::join!`. This is not a " "timeout (that requires `select!`, explained in the next chapter), but " "demonstrates `join!`." msgstr "" #: src/async/control-flow/select.md:3 msgid "" "A select operation waits until any of a set of futures is ready, and " "responds to that future's result. In JavaScript, this is similar to `Promise." "race`. In Python, it compares to `asyncio.wait(task_set, return_when=asyncio." "FIRST_COMPLETED)`." msgstr "" #: src/async/control-flow/select.md:8 msgid "" "Similar to a match statement, the body of `select!` has a number of arms, " "each of the form `pattern = future => statement`. When the `future` is " "ready, the `statement` is executed with the variables in `pattern` bound to " "the `future`'s result." msgstr "" #: src/async/control-flow/select.md:40 msgid "\"Felix\"" msgstr "\"Felix\"" #: src/async/control-flow/select.md:42 msgid "\"Failed to send cat.\"" msgstr "\"Kunne ikke sende katten.\"" #: src/async/control-flow/select.md:47 msgid "\"Rex\"" msgstr "\"Rex\"" #: src/async/control-flow/select.md:49 msgid "\"Failed to send dog.\"" msgstr "\"Kunne ikke sende hunden.\"" #: src/async/control-flow/select.md:54 msgid "\"Failed to receive winner\"" msgstr "\"Kunne ikke modtage vinderen\"" #: src/async/control-flow/select.md:56 msgid "\"Winner is {winner:?}\"" msgstr "\"Vinderen er {winner:?}\"" #: src/async/control-flow/select.md:62 msgid "" "In this example, we have a race between a cat and a dog. " "`first_animal_to_finish_race` listens to both channels and will pick " "whichever arrives first. Since the dog takes 50ms, it wins against the cat " "that take 500ms." msgstr "" #: src/async/control-flow/select.md:67 msgid "" "You can use `oneshot` channels in this example as the channels are supposed " "to receive only one `send`." msgstr "" #: src/async/control-flow/select.md:70 msgid "" "Try adding a deadline to the race, demonstrating selecting different sorts " "of futures." msgstr "" #: src/async/control-flow/select.md:73 msgid "" "Note that `select!` drops unmatched branches, which cancels their futures. " "It is easiest to use when every execution of `select!` creates new futures." msgstr "" #: src/async/control-flow/select.md:76 msgid "" "An alternative is to pass `&mut future` instead of the future itself, but " "this can lead to issues, further discussed in the pinning slide." msgstr "" #: src/async/pitfalls.md:1 msgid "Pitfalls of async/await" msgstr "Faldgruber ved async/await" #: src/async/pitfalls.md:3 msgid "" "Async / await provides convenient and efficient abstraction for concurrent " "asynchronous programming. However, the async/await model in Rust also comes " "with its share of pitfalls and footguns. We illustrate some of them in this " "chapter:" msgstr "" #: src/async/pitfalls.md:5 msgid "[Blocking the Executor](pitfalls/blocking-executor.md)" msgstr "" #: src/async/pitfalls.md:6 msgid "[Pin](pitfalls/pin.md)" msgstr "[Pin](pitfalls/pin.md)" #: src/async/pitfalls.md:7 msgid "[Async Traits](pitfalls/async-traits.md)" msgstr "" #: src/async/pitfalls.md:8 msgid "[Cancellation](pitfalls/cancellation.md)" msgstr "" #: src/async/pitfalls/blocking-executor.md:1 msgid "Blocking the executor" msgstr "" #: src/async/pitfalls/blocking-executor.md:3 msgid "" "Most async runtimes only allow IO tasks to run concurrently. This means that " "CPU blocking tasks will block the executor and prevent other tasks from " "being executed. An easy workaround is to use async equivalent methods where " "possible." msgstr "" #: src/async/pitfalls/blocking-executor.md:14 msgid "\"future {id} slept for {duration_ms}ms, finished after {}ms\"" msgstr "" #: src/async/pitfalls/blocking-executor.md:19 msgid "\"current_thread\"" msgstr "" #: src/async/pitfalls/blocking-executor.md:29 msgid "" "Run the code and see that the sleeps happen consecutively rather than " "concurrently." msgstr "" #: src/async/pitfalls/blocking-executor.md:32 msgid "" "The `\"current_thread\"` flavor puts all tasks on a single thread. This " "makes the effect more obvious, but the bug is still present in the multi-" "threaded flavor." msgstr "" #: src/async/pitfalls/blocking-executor.md:36 msgid "" "Switch the `std::thread::sleep` to `tokio::time::sleep` and await its result." msgstr "" #: src/async/pitfalls/blocking-executor.md:38 msgid "" "Another fix would be to `tokio::task::spawn_blocking` which spawns an actual " "thread and transforms its handle into a future without blocking the executor." msgstr "" #: src/async/pitfalls/blocking-executor.md:41 msgid "" "You should not think of tasks as OS threads. They do not map 1 to 1 and most " "executors will allow many tasks to run on a single OS thread. This is " "particularly problematic when interacting with other libraries via FFI, " "where that library might depend on thread-local storage or map to specific " "OS threads (e.g., CUDA). Prefer `tokio::task::spawn_blocking` in such " "situations." msgstr "" #: src/async/pitfalls/blocking-executor.md:47 msgid "" "Use sync mutexes with care. Holding a mutex over an `.await` may cause " "another task to block, and that task may be running on the same thread." msgstr "" #: src/async/pitfalls/pin.md:3 msgid "" "When you await a future, all local variables (that would ordinarily be " "stored on a stack frame) are instead stored in the Future for the current " "async block. If your future has pointers to data on the stack, those " "pointers might get invalidated. This is unsafe." msgstr "" #: src/async/pitfalls/pin.md:8 msgid "" "Therefore, you must guarantee that the addresses your future points to don't " "change. That is why we need to `pin` futures. Using the same future " "repeatedly in a `select!` often leads to issues with pinned values." msgstr "" #: src/async/pitfalls/pin.md:16 msgid "" "// A work item. In this case, just sleep for the given time and respond\n" "// with a message on the `respond_on` channel.\n" msgstr "" #: src/async/pitfalls/pin.md:24 msgid "// A worker which listens for work on a queue and performs it.\n" msgstr "" #: src/async/pitfalls/pin.md:31 msgid "// Pretend to work.\n" msgstr "" #: src/async/pitfalls/pin.md:34 msgid "\"failed to send response\"" msgstr "" #: src/async/pitfalls/pin.md:37 msgid "// TODO: report number of iterations every 100ms\n" msgstr "" #: src/async/pitfalls/pin.md:41 msgid "// A requester which requests work and waits for it to complete.\n" msgstr "" #: src/async/pitfalls/pin.md:51 msgid "\"failed to send on work queue\"" msgstr "" #: src/async/pitfalls/pin.md:52 msgid "\"failed waiting for response\"" msgstr "" #: src/async/pitfalls/pin.md:61 msgid "\"work result for iteration {i}: {resp}\"" msgstr "" #: src/async/pitfalls/pin.md:68 msgid "" "You may recognize this as an example of the actor pattern. Actors typically " "call `select!` in a loop." msgstr "" #: src/async/pitfalls/pin.md:71 msgid "" "This serves as a summation of a few of the previous lessons, so take your " "time with it." msgstr "" #: src/async/pitfalls/pin.md:74 msgid "" "Naively add a `_ = sleep(Duration::from_millis(100)) => { println!(..) }` to " "the `select!`. This will never execute. Why?" msgstr "" #: src/async/pitfalls/pin.md:77 msgid "" "Instead, add a `timeout_fut` containing that future outside of the `loop`:" msgstr "" #: src/async/pitfalls/pin.md:88 msgid "" "This still doesn't work. Follow the compiler errors, adding `&mut` to the " "`timeout_fut` in the `select!` to work around the move, then using `Box::" "pin`:" msgstr "" #: src/async/pitfalls/pin.md:102 msgid "" "This compiles, but once the timeout expires it is `Poll::Ready` on every " "iteration (a fused future would help with this). Update to reset " "`timeout_fut` every time it expires." msgstr "" #: src/async/pitfalls/pin.md:106 msgid "" "Box allocates on the heap. In some cases, `std::pin::pin!` (only recently " "stabilized, with older code often using `tokio::pin!`) is also an option, " "but that is difficult to use for a future that is reassigned." msgstr "" #: src/async/pitfalls/pin.md:110 msgid "" "Another alternative is to not use `pin` at all but spawn another task that " "will send to a `oneshot` channel every 100ms." msgstr "" #: src/async/pitfalls/async-traits.md:3 msgid "" "Async methods in traits are not yet supported in the stable channel ([An " "experimental feature exists in nightly and should be stabilized in the mid " "term.](https://blog.rust-lang.org/inside-rust/2022/11/17/async-fn-in-trait-" "nightly.html))" msgstr "" #: src/async/pitfalls/async-traits.md:5 msgid "" "The crate [async_trait](https://docs.rs/async-trait/latest/async_trait/) " "provides a workaround through a macro:" msgstr "" #: src/async/pitfalls/async-traits.md:30 msgid "\"running all sleepers..\"" msgstr "" #: src/async/pitfalls/async-traits.md:34 msgid "\"slept for {}ms\"" msgstr "" #: src/async/pitfalls/async-traits.md:51 msgid "" "`async_trait` is easy to use, but note that it's using heap allocations to " "achieve this. This heap allocation has performance overhead." msgstr "" #: src/async/pitfalls/async-traits.md:54 msgid "" "The challenges in language support for `async trait` are deep Rust and " "probably not worth describing in-depth. Niko Matsakis did a good job of " "explaining them in [this post](https://smallcultfollowing.com/babysteps/" "blog/2019/10/26/async-fn-in-traits-are-hard/) if you are interested in " "digging deeper." msgstr "" #: src/async/pitfalls/async-traits.md:60 msgid "" "Try creating a new sleeper struct that will sleep for a random amount of " "time and adding it to the Vec." msgstr "" #: src/async/pitfalls/cancellation.md:3 msgid "" "Dropping a future implies it can never be polled again. This is called " "_cancellation_ and it can occur at any `await` point. Care is needed to " "ensure the system works correctly even when futures are cancelled. For " "example, it shouldn't deadlock or lose data." msgstr "" #: src/async/pitfalls/cancellation.md:35 msgid "\"not UTF-8\"" msgstr "" #: src/async/pitfalls/cancellation.md:51 msgid "\"hi\\nthere\\n\"" msgstr "" #: src/async/pitfalls/cancellation.md:57 msgid "\"tick!\"" msgstr "" #: src/async/pitfalls/cancellation.md:72 msgid "" "The compiler doesn't help with cancellation-safety. You need to read API " "documentation and consider what state your `async fn` holds." msgstr "" #: src/async/pitfalls/cancellation.md:75 msgid "" "Unlike `panic` and `?`, cancellation is part of normal control flow (vs " "error-handling)." msgstr "" #: src/async/pitfalls/cancellation.md:78 msgid "The example loses parts of the string." msgstr "" #: src/async/pitfalls/cancellation.md:80 msgid "" "Whenever the `tick()` branch finishes first, `next()` and its `buf` are " "dropped." msgstr "" #: src/async/pitfalls/cancellation.md:82 msgid "" "`LinesReader` can be made cancellation-safe by making `buf` part of the " "struct:" msgstr "" #: src/async/pitfalls/cancellation.md:95 msgid "" "// prefix buf and bytes with self.\n" " // ...\n" msgstr "" #: src/async/pitfalls/cancellation.md:104 msgid "" "[`Interval::tick`](https://docs.rs/tokio/latest/tokio/time/struct.Interval." "html#method.tick) is cancellation-safe because it keeps track of whether a " "tick has been 'delivered'." msgstr "" #: src/async/pitfalls/cancellation.md:107 msgid "" "[`AsyncReadExt::read`](https://docs.rs/tokio/latest/tokio/io/trait." "AsyncReadExt.html#method.read) is cancellation-safe because it either " "returns or doesn't read data." msgstr "" #: src/async/pitfalls/cancellation.md:110 msgid "" "[`AsyncBufReadExt::read_line`](https://docs.rs/tokio/latest/tokio/io/trait." "AsyncBufReadExt.html#method.read_line) is similar to the example and _isn't_ " "cancellation-safe. See its documentation for details and alternatives." msgstr "" #: src/exercises/concurrency/afternoon.md:3 msgid "" "To practice your Async Rust skills, we have again two exercises for you:" msgstr "" #: src/exercises/concurrency/afternoon.md:5 msgid "" "Dining philosophers: we already saw this problem in the morning. This time " "you are going to implement it with Async Rust." msgstr "" #: src/exercises/concurrency/afternoon.md:8 msgid "" "A Broadcast Chat Application: this is a larger project that allows you " "experiment with more advanced Async Rust features." msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:1 #: src/exercises/concurrency/solutions-afternoon.md:3 msgid "Dining Philosophers - Async" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:3 msgid "" "See [dining philosophers](dining-philosophers.md) for a description of the " "problem." msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:6 msgid "" "As before, you will need a local [Cargo installation](../../cargo/running-" "locally.md) for this exercise. Copy the code below to a file called `src/" "main.rs`, fill out the blanks, and test that `cargo run` does not deadlock:" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:51 #: src/exercises/concurrency/solutions-afternoon.md:77 msgid "// Make them think and eat\n" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:57 msgid "" "Since this time you are using Async Rust, you'll need a `tokio` dependency. " "You can use the following `Cargo.toml`:" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:62 msgid "" "```toml\n" "[package]\n" "name = \"dining-philosophers-async-dine\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "\n" "[dependencies]\n" "tokio = {version = \"1.26.0\", features = [\"sync\", \"time\", \"macros\", " "\"rt-multi-thread\"]}\n" "```" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:72 msgid "" "Also note that this time you have to use the `Mutex` and the `mpsc` module " "from the `tokio` crate." msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md:77 msgid "Can you make your implementation single-threaded? " msgstr "" #: src/exercises/concurrency/chat-app.md:3 msgid "" "In this exercise, we want to use our new knowledge to implement a broadcast " "chat application. We have a chat server that the clients connect to and " "publish their messages. The client reads user messages from the standard " "input, and sends them to the server. The chat server broadcasts each message " "that it receives to all the clients." msgstr "" #: src/exercises/concurrency/chat-app.md:9 msgid "" "For this, we use [a broadcast channel](https://docs.rs/tokio/latest/tokio/" "sync/broadcast/fn.channel.html) on the server, and [`tokio_websockets`]" "(https://docs.rs/tokio-websockets/0.4.0/tokio_websockets/) for the " "communication between the client and the server." msgstr "" #: src/exercises/concurrency/chat-app.md:13 msgid "Create a new Cargo project and add the following dependencies:" msgstr "" #: src/exercises/concurrency/chat-app.md:15 msgid "_Cargo.toml_:" msgstr "" #: src/exercises/concurrency/chat-app.md:19 msgid "" "```toml\n" "[package]\n" "name = \"chat-async\"\n" "version = \"0.1.0\"\n" "edition = \"2021\"\n" "\n" "[dependencies]\n" "futures-util = { version = \"0.3.28\", features = [\"sink\"] }\n" "http = \"0.2.9\"\n" "tokio = { version = \"1.28.1\", features = [\"full\"] }\n" "tokio-websockets = { version = \"0.4.0\", features = [\"client\", " "\"fastrand\", \"server\", \"sha1_smol\"] }\n" "```" msgstr "" #: src/exercises/concurrency/chat-app.md:32 msgid "The required APIs" msgstr "" #: src/exercises/concurrency/chat-app.md:33 msgid "" "You are going to need the following functions from `tokio` and " "[`tokio_websockets`](https://docs.rs/tokio-websockets/0.4.0/" "tokio_websockets/). Spend a few minutes to familiarize yourself with the " "API. " msgstr "" #: src/exercises/concurrency/chat-app.md:37 msgid "" "[StreamExt::next()](https://docs.rs/futures-util/0.3.28/futures_util/stream/" "trait.StreamExt.html#method.next) implemented by `WebsocketStream`: for " "asynchronously reading messages from a Websocket Stream." msgstr "" #: src/exercises/concurrency/chat-app.md:39 msgid "" "[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" "trait.SinkExt.html#method.send) implemented by `WebsocketStream`: for " "asynchronously sending messages on a Websocket Stream." msgstr "" #: src/exercises/concurrency/chat-app.md:41 msgid "" "[Lines::next_line()](https://docs.rs/tokio/latest/tokio/io/struct.Lines." "html#method.next_line): for asynchronously reading user messages from the " "standard input." msgstr "" #: src/exercises/concurrency/chat-app.md:43 msgid "" "[Sender::subscribe()](https://docs.rs/tokio/latest/tokio/sync/broadcast/" "struct.Sender.html#method.subscribe): for subscribing to a broadcast channel." msgstr "" #: src/exercises/concurrency/chat-app.md:46 msgid "Two binaries" msgstr "" #: src/exercises/concurrency/chat-app.md:48 msgid "" "Normally in a Cargo project, you can have only one binary, and one `src/main." "rs` file. In this project, we need two binaries. One for the client, and one " "for the server. You could potentially make them two separate Cargo projects, " "but we are going to put them in a single Cargo project with two binaries. " "For this to work, the client and the server code should go under `src/bin` " "(see the [documentation](https://doc.rust-lang.org/cargo/reference/cargo-" "targets.html#binaries)). " msgstr "" #: src/exercises/concurrency/chat-app.md:55 msgid "" "Copy the following server and client code into `src/bin/server.rs` and `src/" "bin/client.rs`, respectively. Your task is to complete these files as " "described below. " msgstr "" #: src/exercises/concurrency/chat-app.md:59 msgid "_src/bin/server.rs_:" msgstr "_src/bin/server.rs_:" #: src/exercises/concurrency/chat-app.md:78 #: src/exercises/concurrency/chat-app.md:125 msgid "// TODO: For a hint, see the description of the task below.\n" msgstr "" #: src/exercises/concurrency/chat-app.md:86 #: src/exercises/concurrency/solutions-afternoon.md:149 msgid "\"127.0.0.1:2000\"" msgstr "\"127.0.0.1:2000\"" #: src/exercises/concurrency/chat-app.md:87 #: src/exercises/concurrency/solutions-afternoon.md:150 msgid "\"listening on port 2000\"" msgstr "" #: src/exercises/concurrency/chat-app.md:91 #: src/exercises/concurrency/solutions-afternoon.md:154 msgid "\"New connection from {addr:?}\"" msgstr "" #: src/exercises/concurrency/chat-app.md:94 #: src/exercises/concurrency/solutions-afternoon.md:157 msgid "// Wrap the raw TCP stream into a websocket.\n" msgstr "" #: src/exercises/concurrency/chat-app.md:103 msgid "_src/bin/client.rs_:" msgstr "_src/bin/client.rs_:" #: src/exercises/concurrency/chat-app.md:117 #: src/exercises/concurrency/solutions-afternoon.md:178 msgid "\"ws://127.0.0.1:2000\"" msgstr "\"ws://127.0.0.1:2000\"" #: src/exercises/concurrency/chat-app.md:130 msgid "Running the binaries" msgstr "Afvikling af binære filer" #: src/exercises/concurrency/chat-app.md:131 msgid "Run the server with:" msgstr "" #: src/exercises/concurrency/chat-app.md:137 msgid "and the client with:" msgstr "" #: src/exercises/concurrency/chat-app.md:145 msgid "Implement the `handle_connection` function in `src/bin/server.rs`." msgstr "" #: src/exercises/concurrency/chat-app.md:146 msgid "" "Hint: Use `tokio::select!` for concurrently performing two tasks in a " "continuous loop. One task receives messages from the client and broadcasts " "them. The other sends messages received by the server to the client." msgstr "" #: src/exercises/concurrency/chat-app.md:149 msgid "Complete the main function in `src/bin/client.rs`." msgstr "" #: src/exercises/concurrency/chat-app.md:150 msgid "" "Hint: As before, use `tokio::select!` in a continuous loop for concurrently " "performing two tasks: (1) reading user messages from standard input and " "sending them to the server, and (2) receiving messages from the server, and " "displaying them for the user." msgstr "" #: src/exercises/concurrency/chat-app.md:154 msgid "" "Optional: Once you are done, change the code to broadcast messages to all " "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." msgstr "" #: src/other-resources.md:22 msgid "More specialized guides hosted on the official Rust site:" msgstr "" #: src/other-resources.md:24 msgid "" "[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " "including working with raw pointers and interfacing with other languages " "(FFI)." 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." msgstr "" #: 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/other-resources.md:33 msgid "Unofficial Learning Material" msgstr "" #: src/other-resources.md:35 msgid "A small selection of other guides and tutorial for Rust:" 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/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/other-resources.md:42 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." msgstr "" #: src/other-resources.md:45 msgid "" "[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " "you learn Rust." 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." 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." msgstr "" #: 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/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/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/credits.md:7 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." msgstr "" #: 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/credits.md:19 msgid "Rust on Exercism" msgstr "Rust på Exercism" #: 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/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 "" #: 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 msgid "" "Feel free to ask questions about the solutions [on GitHub](https://github." "com/google/comprehensive-rust/discussions). Let us know if you have a " "different or better solution than what is presented here." msgstr "" #: 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:?}\"" msgstr "" #: src/exercises/day-1/solutions-morning.md:27 #: src/exercises/day-1/solutions-morning.md:35 msgid "//\n" msgstr "" #: src/exercises/day-1/solutions-morning.md:57 msgid "Bonus question" msgstr "Bonusspørgsmål" #: src/exercises/day-1/solutions-morning.md:59 msgid "" "It requires more advanced concepts. It might seem that we could use a slice-" "of-slices (`&[&[i32]]`) as the input type to transpose and thus make our " "function handle any size of matrix. However, this quickly breaks down: the " "return type cannot be `&[&[i32]]` since it needs to own the data you return." msgstr "" #: src/exercises/day-1/solutions-morning.md:61 msgid "" "You can attempt to use something like `Vec>`, but this doesn't work " "out-of-the-box either: it's hard to convert from `Vec>` to " "`&[&[i32]]` so now you cannot easily use `pretty_print` either." msgstr "" #: src/exercises/day-1/solutions-morning.md:63 msgid "" "Once we get to traits and generics, we'll be able to use the [`std::convert::" "AsRef`](https://doc.rust-lang.org/std/convert/trait.AsRef.html) trait to " "abstract over anything that can be referenced as a slice." msgstr "" #: src/exercises/day-1/solutions-morning.md:72 msgid "// A line references a slice of items\n" msgstr "" #: src/exercises/day-1/solutions-morning.md:74 msgid "// A matrix references a slice of lines\n" 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 msgid "" "In addition, the type itself would not enforce that the child slices are of " "the same length, so such variable could contain an invalid matrix." msgstr "" #: src/exercises/day-1/solutions-afternoon.md:1 msgid "Day 1 Afternoon Exercises" 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 {}\"" msgstr "" #: src/exercises/day-2/solutions-morning.md:59 msgid "" "// Using a closure and a built-in method:\n" " // self.books.iter().min_by_key(|book| book.year)\n" msgstr "" #: src/exercises/day-2/solutions-morning.md:62 msgid "// Longer hand-written solution:\n" msgstr "" #: src/exercises/day-2/solutions-morning.md:127 msgid "" "// We could try and capture stdout, but let us just call the\n" " // method to start with.\n" 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" 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 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" 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" msgstr "" #: src/exercises/day-3/solutions-morning.md:89 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" 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\"" 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/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" 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 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/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/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/solutions-afternoon.md:213 msgid "" "/// Sets or clears the interrupt mask.\n" " ///\n" " /// When the mask is true the interrupt is enabled; when it is false " "the\n" " /// interrupt is disabled.\n" msgstr "" #: src/exercises/bare-metal/solutions-afternoon.md:224 msgid "/// Clears a pending interrupt, if any.\n" 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 true 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:230 msgid "\"Got crawling error: {:#}\"" msgstr "" #: src/exercises/concurrency/solutions-morning.md:248 msgid "\"Bad URLs: {:#?}\"" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:1 msgid "Concurrency Afternoon Exercise" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:5 msgid "([back to exercise](dining-philosophers-async.md))" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:32 msgid "" "// Add a delay before picking the second fork to allow the execution\n" " // to transfer to another task\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:40 msgid "// The locks are dropped here\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:60 msgid "" "// To avoid a deadlock, we have to break the symmetry\n" " // somewhere. This will swap the forks without deinitializing\n" " // either of them.\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:74 msgid "// tx is dropped here, so we don't need to explicitly drop it later\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:90 msgid "\"Here is a thought: {thought}\"" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:97 msgid "([back to exercise](chat-app.md))" msgstr "([tilbage til øvelsen](chat-app.md))" #: src/exercises/concurrency/solutions-afternoon.md:99 msgid "`src/bin/server.rs`:" msgstr "`src/bin/server.rs`:" #: src/exercises/concurrency/solutions-afternoon.md:117 msgid "\"Welcome to chat! Type a message\"" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:121 msgid "" "// A continuous loop for concurrently performing two tasks: (1) receiving\n" " // messages from `ws_stream` and broadcasting them, and (2) receiving\n" " // messages on `bcast_rx` and sending them to the client.\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:130 msgid "\"From client {addr:?} {text:?}\"" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:166 msgid "`src/bin/client.rs`:" msgstr "`src/bin/client.rs`:" #: src/exercises/concurrency/solutions-afternoon.md:185 msgid "// Continuous loop for concurrently sending and receiving messages.\n" msgstr "" #: src/exercises/concurrency/solutions-afternoon.md:192 msgid "\"From server: {}\"" msgstr ""