diff --git a/po/tr.po b/po/tr.po index 8236ef60d111..c58f8fa7ed68 100644 --- a/po/tr.po +++ b/po/tr.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: Comprehensive Rust 🦀\n" -"POT-Creation-Date: 2023-10-24T20:37:45+03:00\n" +"POT-Creation-Date: 2024-01-24T13:24:49+01:00\n" "PO-Revision-Date: 2023-10-27 14:20+0300\n" "Last-Translator: akerem@protonmail.com\n" "Language-Team: Turkish \n" @@ -12,1027 +12,1218 @@ msgstr "" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Poedit 3.4.1\n" -#: src/SUMMARY.md:4 src/index.md:1 +#: src/SUMMARY.md src/index.md msgid "Welcome to Comprehensive Rust 🦀" msgstr "Comprehensive Rust'a Hoşgeldiniz 🦀" -#: src/SUMMARY.md:5 src/running-the-course.md:1 +#: src/SUMMARY.md src/running-the-course.md msgid "Running the Course" msgstr "Kursun Çalıştırılması" -#: src/SUMMARY.md:6 src/running-the-course/course-structure.md:1 +#: src/SUMMARY.md src/running-the-course/course-structure.md msgid "Course Structure" msgstr "Kurs Yapısı" -#: src/SUMMARY.md:7 src/running-the-course/keyboard-shortcuts.md:1 +#: src/SUMMARY.md src/running-the-course/keyboard-shortcuts.md msgid "Keyboard Shortcuts" msgstr "Klavye Kısayolları" -#: src/SUMMARY.md:8 src/running-the-course/translations.md:1 +#: src/SUMMARY.md src/running-the-course/translations.md msgid "Translations" msgstr "Çeviriler" -#: src/SUMMARY.md:9 src/cargo.md:1 +#: src/SUMMARY.md src/cargo.md msgid "Using Cargo" msgstr "Cargo Kullanımı" -#: src/SUMMARY.md:10 +#: src/SUMMARY.md msgid "Rust Ecosystem" msgstr "Rust Ekosistemi" -#: src/SUMMARY.md:11 +#: src/SUMMARY.md msgid "Code Samples" msgstr "Kod Örnekleri" -#: src/SUMMARY.md:12 +#: src/SUMMARY.md msgid "Running Cargo Locally" msgstr "Cargo'nun Yerel (Local) Olarak Çalıştırılması" -#: src/SUMMARY.md:15 +#: src/SUMMARY.md msgid "Day 1: Morning" msgstr "Gün 1: Sabah" -#: src/SUMMARY.md:19 src/SUMMARY.md:80 src/SUMMARY.md:135 src/SUMMARY.md:193 -#: src/SUMMARY.md:219 src/SUMMARY.md:269 +#: src/SUMMARY.md msgid "Welcome" msgstr "Hoşgeldiniz" -#: src/SUMMARY.md:20 src/welcome-day-1/what-is-rust.md:1 +#: src/SUMMARY.md src/hello-world.md src/hello-world/hello-world.md +#, fuzzy +msgid "Hello, World" +msgstr "Merhaba Dünya!" + +#: src/SUMMARY.md src/hello-world/what-is-rust.md msgid "What is Rust?" msgstr "Rust Nedir?" -#: src/SUMMARY.md:21 src/hello-world.md:1 -msgid "Hello World!" -msgstr "Merhaba Dünya!" +#: src/SUMMARY.md src/hello-world/benefits.md +msgid "Benefits of Rust" +msgstr "" -#: src/SUMMARY.md:22 src/hello-world/small-example.md:1 -msgid "Small Example" -msgstr "Küçük Örnek" +#: src/SUMMARY.md src/hello-world/playground.md +msgid "Playground" +msgstr "" -#: src/SUMMARY.md:23 src/why-rust.md:1 -msgid "Why Rust?" -msgstr "Neden Rust?" +#: src/SUMMARY.md src/types-and-values.md +msgid "Types and Values" +msgstr "" -#: src/SUMMARY.md:24 src/why-rust/an-example-in-c.md:1 src/credits.md:32 -msgid "An Example in C" -msgstr "C Dilinde Bir Örnek" +#: src/SUMMARY.md src/types-and-values/variables.md +msgid "Variables" +msgstr "Değişkenler" -#: src/SUMMARY.md:25 src/why-rust/compile-time.md:1 -msgid "Compile Time Guarantees" -msgstr "Derleme Zamanı Garantileri" +#: src/SUMMARY.md src/types-and-values/values.md +msgid "Values" +msgstr "" -#: src/SUMMARY.md:26 src/why-rust/runtime.md:1 -msgid "Runtime Guarantees" -msgstr "Çalışma Zamanı Garantileri" +#: src/SUMMARY.md src/types-and-values/arithmetic.md +msgid "Arithmetic" +msgstr "" -#: src/SUMMARY.md:27 src/why-rust/modern.md:1 -msgid "Modern Features" -msgstr "Modern Özellikler" +#: src/SUMMARY.md src/types-and-values/strings.md +msgid "Strings" +msgstr "" -#: src/SUMMARY.md:28 src/basic-syntax.md:1 -msgid "Basic Syntax" -msgstr "Temel Sözdizimi" +#: src/SUMMARY.md src/types-and-values/inference.md +msgid "Type Inference" +msgstr "Tür Çıkarımı" -#: src/SUMMARY.md:29 src/basic-syntax/scalar-types.md:1 -msgid "Scalar Types" -msgstr "Skaler Türler" +#: src/SUMMARY.md src/types-and-values/exercise.md +msgid "Exercise: Fibonacci" +msgstr "" -#: src/SUMMARY.md:30 src/basic-syntax/compound-types.md:1 -msgid "Compound Types" -msgstr "Bileşik Türler" +#: src/SUMMARY.md src/types-and-values/solution.md +#: src/control-flow-basics/solution.md src/tuples-and-arrays/solution.md +#: src/references/solution.md src/user-defined-types/solution.md +#: src/pattern-matching/solution.md src/methods-and-traits/solution.md +#: src/generics/solution.md src/std-types/solution.md +#: src/std-traits/solution.md src/memory-management/solution.md +#: src/smart-pointers/solution.md src/borrowing/solution.md +#: src/slices-and-lifetimes/solution.md src/iterators/solution.md +#: src/modules/solution.md src/testing/solution.md +#: src/error-handling/solution.md src/unsafe-rust/solution.md +#, fuzzy +msgid "Solution" +msgstr "Çözümler" -#: src/SUMMARY.md:31 src/basic-syntax/references.md:1 -msgid "References" -msgstr "Referanslar" +#: src/SUMMARY.md src/control-flow-basics.md +#, fuzzy +msgid "Control Flow Basics" +msgstr "Kontrol Akışı" -#: src/SUMMARY.md:32 src/basic-syntax/references-dangling.md:1 -msgid "Dangling References" -msgstr "Geçersiz (Dangling) Referanslar" +#: src/SUMMARY.md src/control-flow-basics/conditionals.md +msgid "Conditionals" +msgstr "" -#: src/SUMMARY.md:33 src/basic-syntax/slices.md:1 -msgid "Slices" -msgstr "Dilimler (Slices)" +#: src/SUMMARY.md src/control-flow-basics/loops.md +msgid "Loops" +msgstr "" + +#: src/SUMMARY.md src/control-flow-basics/break-continue.md +msgid "`break` and `continue`" +msgstr "" -#: src/SUMMARY.md:34 -msgid "String vs str" -msgstr "String vs str" +#: src/SUMMARY.md src/control-flow-basics/blocks-and-scopes.md +msgid "Blocks and Scopes" +msgstr "" -#: src/SUMMARY.md:35 src/basic-syntax/functions.md:1 +#: src/SUMMARY.md src/control-flow-basics/functions.md msgid "Functions" msgstr "Fonksiyonlar" -#: src/SUMMARY.md:36 src/basic-syntax/rustdoc.md:1 -msgid "Rustdoc" -msgstr "Rustdoc" - -#: src/SUMMARY.md:37 src/SUMMARY.md:103 src/basic-syntax/methods.md:1 -#: src/methods.md:1 -msgid "Methods" -msgstr "Metotlar" - -#: src/SUMMARY.md:38 -msgid "Overloading" -msgstr "Yükleme (Overloading)" - -#: src/SUMMARY.md:39 src/SUMMARY.md:72 src/SUMMARY.md:106 src/SUMMARY.md:126 -#: src/SUMMARY.md:155 src/SUMMARY.md:185 src/SUMMARY.md:212 src/SUMMARY.md:233 -#: src/SUMMARY.md:261 src/SUMMARY.md:283 src/SUMMARY.md:304 -#: src/exercises/android/morning.md:1 src/exercises/bare-metal/morning.md:1 -#: src/exercises/bare-metal/afternoon.md:1 -#: src/exercises/concurrency/morning.md:1 -#: src/exercises/concurrency/afternoon.md:1 -msgid "Exercises" -msgstr "Egzersizler" - -#: src/SUMMARY.md:40 src/exercises/day-1/implicit-conversions.md:1 -msgid "Implicit Conversions" -msgstr "Örtülü Dönüşümler" +#: src/SUMMARY.md src/control-flow-basics/macros.md +msgid "Macros" +msgstr "" -#: src/SUMMARY.md:41 -msgid "Arrays and for Loops" -msgstr "Diziler ve for Döngüleri" +#: src/SUMMARY.md src/control-flow-basics/exercise.md +msgid "Exercise: Collatz Sequence" +msgstr "" -#: src/SUMMARY.md:43 +#: src/SUMMARY.md msgid "Day 1: Afternoon" msgstr "Gün 1: Öğleden Sonra" -#: src/SUMMARY.md:45 src/SUMMARY.md:296 src/control-flow.md:1 -msgid "Control Flow" -msgstr "Kontrol Akışı" - -#: src/SUMMARY.md:46 src/control-flow/blocks.md:1 -msgid "Blocks" -msgstr "Bloklar" - -#: src/SUMMARY.md:47 -msgid "if expressions" -msgstr "if İfadeleri" - -#: src/SUMMARY.md:48 -msgid "for expressions" -msgstr "for İfadeleri" - -#: src/SUMMARY.md:49 -msgid "while expressions" -msgstr "while İfadeleri" - -#: src/SUMMARY.md:50 -msgid "break & continue" -msgstr "break & continue" - -#: src/SUMMARY.md:51 -msgid "loop expressions" -msgstr "loop İfadeleri" - -#: src/SUMMARY.md:53 src/basic-syntax/variables.md:1 -msgid "Variables" -msgstr "Değişkenler" - -#: src/SUMMARY.md:54 src/basic-syntax/type-inference.md:1 -msgid "Type Inference" -msgstr "Tür Çıkarımı" - -#: src/SUMMARY.md:55 -msgid "static & const" -msgstr "static & const" - -#: src/SUMMARY.md:56 src/basic-syntax/scopes-shadowing.md:1 -msgid "Scopes and Shadowing" -msgstr "Kapsamlar (Scopes) ve Gölgeleme (Shadowing)" - -#: src/SUMMARY.md:57 src/enums.md:1 -msgid "Enums" -msgstr "Enumlar" - -#: src/SUMMARY.md:58 src/enums/variant-payloads.md:1 -msgid "Variant Payloads" -msgstr "Varyant Yükler" - -#: src/SUMMARY.md:59 src/enums/sizes.md:1 -msgid "Enum Sizes" -msgstr "Enum Boyutları" - -#: src/SUMMARY.md:61 src/control-flow/novel.md:1 -msgid "Novel Control Flow" -msgstr "Yeni Kontrol Akışları" - -#: src/SUMMARY.md:62 -msgid "if let expressions" -msgstr "if let İfadeleri" - -#: src/SUMMARY.md:63 -msgid "while let expressions" -msgstr "while let İfadeleri" +#: src/SUMMARY.md src/tuples-and-arrays.md +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Tuples and Arrays" +msgstr "" -#: src/SUMMARY.md:64 -msgid "match expressions" -msgstr "match ifadeleri" +#: src/SUMMARY.md src/tuples-and-arrays/iteration.md +#, fuzzy +msgid "Array Iteration" +msgstr "Iterator" -#: src/SUMMARY.md:66 src/SUMMARY.md:74 src/pattern-matching.md:1 +#: src/SUMMARY.md src/tuples-and-arrays/match.md src/pattern-matching.md msgid "Pattern Matching" msgstr "Desen Eşleştirme" -#: src/SUMMARY.md:67 src/pattern-matching/destructuring-enums.md:1 -msgid "Destructuring Enums" +#: src/SUMMARY.md src/tuples-and-arrays/destructuring.md +#: src/pattern-matching/destructuring.md +#, fuzzy +msgid "Destructuring" msgstr "Enumların Çözümlenmesi" -#: src/SUMMARY.md:68 src/pattern-matching/destructuring-structs.md:1 -msgid "Destructuring Structs" -msgstr "Yapıların (Struct) Çözümlenmesi" - -#: src/SUMMARY.md:69 src/pattern-matching/destructuring-arrays.md:1 -msgid "Destructuring Arrays" -msgstr "Dizilerin Çözümlenmesi" - -#: src/SUMMARY.md:70 src/pattern-matching/match-guards.md:1 -msgid "Match Guards" -msgstr "Eşleşme Koşulları/Filtreleri" - -#: src/SUMMARY.md:73 src/exercises/day-1/luhn.md:1 -#: src/exercises/day-1/solutions-afternoon.md:3 -msgid "Luhn Algorithm" -msgstr "Luhn Algrotiması" +#: src/SUMMARY.md src/tuples-and-arrays/exercise.md +msgid "Exercise: Nested Arrays" +msgstr "" -#: src/SUMMARY.md:76 -msgid "Day 2: Morning" -msgstr "Gün 2: Sabah" +#: src/SUMMARY.md src/references.md +msgid "References" +msgstr "Referanslar" -#: src/SUMMARY.md:82 src/memory-management.md:1 -msgid "Memory Management" -msgstr "Bellek Yönetimi" +#: src/SUMMARY.md src/references/shared.md +#, fuzzy +msgid "Shared References" +msgstr "Referanslar" -#: src/SUMMARY.md:83 -msgid "Stack vs Heap" -msgstr "Stack vs Heap" +#: src/SUMMARY.md src/references/exclusive.md +#, fuzzy +msgid "Exclusive References" +msgstr "Geçersiz (Dangling) Referanslar" -#: src/SUMMARY.md:84 -msgid "Stack Memory" -msgstr "Stack Belleği" +#: src/SUMMARY.md src/references/exercise.md +msgid "Exercise: Geometry" +msgstr "" -#: src/SUMMARY.md:85 src/memory-management/manual.md:1 -msgid "Manual Memory Management" -msgstr "Manuel Bellek Yönetimi" +#: src/SUMMARY.md src/user-defined-types.md +msgid "User-Defined Types" +msgstr "" -#: src/SUMMARY.md:86 src/memory-management/scope-based.md:1 -msgid "Scope-Based Memory Management" -msgstr "Kapsam Tabanlı Bellek Yönetimi" +#: src/SUMMARY.md src/user-defined-types/named-structs.md +#, fuzzy +msgid "Named Structs" +msgstr "Yapılar (Structs)" -#: src/SUMMARY.md:87 -msgid "Garbage Collection" -msgstr "Çöp Toplama" +#: src/SUMMARY.md src/user-defined-types/tuple-structs.md +msgid "Tuple Structs" +msgstr "Tuple Yapıları (Tuple Structs)" -#: src/SUMMARY.md:88 -msgid "Rust Memory Management" -msgstr "Rust Bellek Yönetimi" +#: src/SUMMARY.md src/user-defined-types/enums.md +#: src/pattern-matching/destructuring.md +msgid "Enums" +msgstr "Enumlar" -#: src/SUMMARY.md:89 src/ownership.md:1 -msgid "Ownership" -msgstr "Sahiplik" +#: src/SUMMARY.md src/user-defined-types/static-and-const.md +#, fuzzy +msgid "Static and Const" +msgstr "static & const" -#: src/SUMMARY.md:90 src/ownership/move-semantics.md:1 -msgid "Move Semantics" -msgstr "Taşıma Semantiği" +#: src/SUMMARY.md src/user-defined-types/aliases.md +msgid "Type Aliases" +msgstr "" -#: src/SUMMARY.md:91 src/ownership/moved-strings-rust.md:1 -msgid "Moved Strings in Rust" -msgstr "Rust'da Taşınmış Stringler" +#: src/SUMMARY.md src/user-defined-types/exercise.md +msgid "Exercise: Elevator Events" +msgstr "" -#: src/SUMMARY.md:92 -msgid "Double Frees in Modern C++" -msgstr "Modern C++'da Double Free'ler (Adresi iki kez serbest bırakma)" +#: src/SUMMARY.md +msgid "Day 2: Morning" +msgstr "Gün 2: Sabah" -#: src/SUMMARY.md:93 src/ownership/moves-function-calls.md:1 -msgid "Moves in Function Calls" -msgstr "Fonksiyon Çağrılarında Taşımalar" +#: src/SUMMARY.md src/pattern-matching/let-control-flow.md +#, fuzzy +msgid "Let Control Flow" +msgstr "Kontrol Akışı" -#: src/SUMMARY.md:94 src/ownership/copy-clone.md:1 -msgid "Copying and Cloning" -msgstr "Kopyalama ve Klonlama" +#: src/SUMMARY.md src/pattern-matching/exercise.md +msgid "Exercise: Expression Evaluation" +msgstr "" -#: src/SUMMARY.md:95 src/ownership/borrowing.md:1 -msgid "Borrowing" -msgstr "Ödünç Alma" +#: src/SUMMARY.md src/methods-and-traits.md +#, fuzzy +msgid "Methods and Traits" +msgstr "Read ve Write" -#: src/SUMMARY.md:96 src/ownership/shared-unique-borrows.md:1 -msgid "Shared and Unique Borrows" -msgstr "Paylaşımlı (Shared) ve Eşsiz (Unique) Ödünç Almalar" +#: src/SUMMARY.md src/methods-and-traits/methods.md +msgid "Methods" +msgstr "Metotlar" -#: src/SUMMARY.md:97 src/ownership/lifetimes.md:1 -msgid "Lifetimes" -msgstr "Ömürler" +#: src/SUMMARY.md src/methods-and-traits/traits.md +msgid "Traits" +msgstr "Özellikler (Traits)" -#: src/SUMMARY.md:98 src/ownership/lifetimes-function-calls.md:1 -msgid "Lifetimes in Function Calls" -msgstr "Fonksiyon Çağrılarında Ömürler" +#: src/SUMMARY.md src/methods-and-traits/deriving.md +#, fuzzy +msgid "Deriving" +msgstr "Türetilebilir Özellikler (Traits)" -#: src/SUMMARY.md:99 src/ownership/lifetimes-data-structures.md:1 -msgid "Lifetimes in Data Structures" -msgstr "Veri Yapılarında Ömürler" +#: src/SUMMARY.md src/methods-and-traits/trait-objects.md +msgid "Trait Objects" +msgstr "Özellik Nesneleri" -#: src/SUMMARY.md:100 src/structs.md:1 -msgid "Structs" -msgstr "Yapılar (Structs)" +#: src/SUMMARY.md src/methods-and-traits/exercise.md +msgid "Exercise: Generic Logger" +msgstr "" -#: src/SUMMARY.md:101 src/structs/tuple-structs.md:1 -msgid "Tuple Structs" -msgstr "Tuple Yapıları (Tuple Structs)" +#: src/SUMMARY.md src/generics.md +msgid "Generics" +msgstr "Jenerikler" -#: src/SUMMARY.md:102 src/structs/field-shorthand.md:1 -msgid "Field Shorthand Syntax" -msgstr "Alanlara İlk Değer Verme Kısaltması'nın Sözdizimi (Syntax)" +#: src/SUMMARY.md src/generics/generic-functions.md +#, fuzzy +msgid "Generic Functions" +msgstr "Dış Bağlantıya Sahip Fonksiyonlar" -#: src/SUMMARY.md:104 src/methods/receiver.md:1 -msgid "Method Receiver" -msgstr "Metot Alıcısı" +#: src/SUMMARY.md src/generics/generic-data.md +msgid "Generic Data Types" +msgstr "Jenerik Veri Türleri" -#: src/SUMMARY.md:105 src/SUMMARY.md:167 src/SUMMARY.md:282 -#: src/methods/example.md:1 src/concurrency/shared_state/example.md:1 -msgid "Example" -msgstr "Örnek" +#: src/SUMMARY.md src/generics/trait-bounds.md +msgid "Trait Bounds" +msgstr "Özellik (Trait) Sınırları" -#: src/SUMMARY.md:107 src/exercises/day-2/book-library.md:1 -msgid "Storing Books" -msgstr "Kitapların Saklanması" +#: src/SUMMARY.md src/generics/impl-trait.md +msgid "`impl Trait`" +msgstr "" -#: src/SUMMARY.md:108 src/exercises/day-2/health-statistics.md:1 -#: src/exercises/day-2/solutions-morning.md:151 -msgid "Health Statistics" -msgstr "Sağlık İstatistikleri" +#: src/SUMMARY.md src/generics/exercise.md +msgid "Exercise: Generic `min`" +msgstr "" -#: src/SUMMARY.md:110 +#: src/SUMMARY.md msgid "Day 2: Afternoon" msgstr "Gün 2: Öğleden Sonra" -#: src/SUMMARY.md:112 src/std.md:1 +#: src/SUMMARY.md src/std-types.md +#, fuzzy +msgid "Standard Library Types" +msgstr "Standart Kütüphane" + +#: src/SUMMARY.md src/std-types/std.md msgid "Standard Library" msgstr "Standart Kütüphane" -#: src/SUMMARY.md:113 -msgid "Option and Result" -msgstr "Option ve Result" +#: src/SUMMARY.md src/std-types/docs.md +#, fuzzy +msgid "Documentation" +msgstr "Dokümantasyon Testleri" -#: src/SUMMARY.md:114 src/std/string.md:1 -msgid "String" -msgstr "String" +#: src/SUMMARY.md +msgid "`Option`" +msgstr "" -#: src/SUMMARY.md:115 -msgid "Vec" -msgstr "Vec" +#: src/SUMMARY.md +msgid "`Result`" +msgstr "" -#: src/SUMMARY.md:116 -msgid "HashMap" -msgstr "HashMap" +#: src/SUMMARY.md src/android/interoperability/cpp/type-mapping.md +#, fuzzy +msgid "`String`" +msgstr "String" -#: src/SUMMARY.md:117 -msgid "Box" -msgstr "Box" +#: src/SUMMARY.md src/std-types/vec.md +msgid "`Vec`" +msgstr "" -#: src/SUMMARY.md:118 -msgid "Recursive Data Types" -msgstr "Özyinelemeli Veri Türleri" +#: src/SUMMARY.md src/std-types/hashmap.md src/bare-metal/no_std.md +msgid "`HashMap`" +msgstr "" -#: src/SUMMARY.md:119 src/std/box-niche.md:1 -msgid "Niche Optimization" -msgstr "Niche Optimizasyonu" +#: src/SUMMARY.md src/std-types/exercise.md +#, fuzzy +msgid "Exercise: Counter" +msgstr "Egzersizler" -#: src/SUMMARY.md:120 -msgid "Rc" -msgstr "Rc" +#: src/SUMMARY.md src/std-traits.md +#, fuzzy +msgid "Standard Library Traits" +msgstr "Standart Kütüphane" -#: src/SUMMARY.md:121 -msgid "Cell/RefCell" -msgstr "Cell/RefCell" +#: src/SUMMARY.md src/std-traits/comparisons.md src/async.md +msgid "Comparisons" +msgstr "" -#: src/SUMMARY.md:122 src/modules.md:1 -msgid "Modules" -msgstr "Modüller" +#: src/SUMMARY.md src/std-traits/operators.md +#, fuzzy +msgid "Operators" +msgstr "Iterator" -#: src/SUMMARY.md:123 src/modules/visibility.md:1 -msgid "Visibility" -msgstr "Görünürlük" +#: src/SUMMARY.md src/std-traits/from-and-into.md +msgid "`From` and `Into`" +msgstr "" -#: src/SUMMARY.md:124 src/modules/paths.md:1 -msgid "Paths" -msgstr "Yollar (Paths)" +#: src/SUMMARY.md src/std-traits/casting.md +#, fuzzy +msgid "Casting" +msgstr "Test Etme" -#: src/SUMMARY.md:125 src/modules/filesystem.md:1 -msgid "Filesystem Hierarchy" -msgstr "Dosya Sistemi Hiyerarşisi" +#: src/SUMMARY.md src/std-traits/read-and-write.md +msgid "`Read` and `Write`" +msgstr "" -#: src/SUMMARY.md:127 src/exercises/day-2/iterators-and-ownership.md:1 -msgid "Iterators and Ownership" -msgstr "Adımlayıcılar (Iterators) ve Sahiplik" +#: src/SUMMARY.md +msgid "`Default`, struct update syntax" +msgstr "" + +#: src/SUMMARY.md src/std-traits/closures.md +msgid "Closures" +msgstr "" -#: src/SUMMARY.md:128 src/exercises/day-2/strings-iterators.md:1 -#: src/exercises/day-2/solutions-afternoon.md:3 -msgid "Strings and Iterators" -msgstr "Dizeler (Stringler) ve Adımlayıcılar (Iterators)" +#: src/SUMMARY.md src/std-traits/exercise.md +#, fuzzy +msgid "Exercise: ROT13" +msgstr "Egzersizler" -#: src/SUMMARY.md:131 +#: src/SUMMARY.md msgid "Day 3: Morning" msgstr "Gün 3: Sabah" -#: src/SUMMARY.md:136 src/generics.md:1 -msgid "Generics" -msgstr "Jenerikler" - -#: src/SUMMARY.md:137 src/generics/data-types.md:1 -msgid "Generic Data Types" -msgstr "Jenerik Veri Türleri" - -#: src/SUMMARY.md:138 src/generics/methods.md:1 -msgid "Generic Methods" -msgstr "Jenerik Metotlar" - -#: src/SUMMARY.md:139 src/generics/monomorphization.md:1 -msgid "Monomorphization" -msgstr "Monomorfizasyon" - -#: src/SUMMARY.md:140 src/traits.md:1 -msgid "Traits" -msgstr "Özellikler (Traits)" - -#: src/SUMMARY.md:141 src/traits/trait-objects.md:1 -msgid "Trait Objects" -msgstr "Özellik Nesneleri" - -#: src/SUMMARY.md:142 src/traits/deriving-traits.md:1 -msgid "Deriving Traits" -msgstr "Türetilebilir Özellikler (Traits)" - -#: src/SUMMARY.md:143 src/traits/default-methods.md:1 -msgid "Default Methods" -msgstr "Varsayılan Metotlar" - -#: src/SUMMARY.md:144 src/traits/trait-bounds.md:1 -msgid "Trait Bounds" -msgstr "Özellik (Trait) Sınırları" +#: src/SUMMARY.md src/memory-management.md +msgid "Memory Management" +msgstr "Bellek Yönetimi" -#: src/SUMMARY.md:145 -msgid "impl Trait" -msgstr "impl Trait" +#: src/SUMMARY.md src/memory-management/review.md +msgid "Review of Program Memory" +msgstr "" -#: src/SUMMARY.md:146 src/traits/important-traits.md:1 -msgid "Important Traits" -msgstr "Önemli Özellikler (Traits)" +#: src/SUMMARY.md src/memory-management/approaches.md +#, fuzzy +msgid "Approaches to Memory Management" +msgstr "Rust Bellek Yönetimi" -#: src/SUMMARY.md:147 -msgid "Iterator" -msgstr "Iterator" +#: src/SUMMARY.md src/memory-management/ownership.md +msgid "Ownership" +msgstr "Sahiplik" -#: src/SUMMARY.md:148 src/traits/from-iterator.md:1 -msgid "FromIterator" -msgstr "FromIterator" +#: src/SUMMARY.md src/memory-management/move.md +msgid "Move Semantics" +msgstr "Taşıma Semantiği" -#: src/SUMMARY.md:149 -msgid "From and Into" -msgstr "From ve Into" +#: src/SUMMARY.md +msgid "`Clone`" +msgstr "" -#: src/SUMMARY.md:150 -msgid "Read and Write" -msgstr "Read ve Write" +#: src/SUMMARY.md src/memory-management/copy-types.md +#, fuzzy +msgid "Copy Types" +msgstr "Bileşik Türler" -#: src/SUMMARY.md:151 -msgid "Drop" +#: src/SUMMARY.md +#, fuzzy +msgid "`Drop`" msgstr "Drop" -#: src/SUMMARY.md:152 -msgid "Default" -msgstr "Default" +#: src/SUMMARY.md src/memory-management/exercise.md +msgid "Exercise: Builder Type" +msgstr "" -#: src/SUMMARY.md:153 -msgid "Operators: Add, Mul, ..." -msgstr "Operatörler: Add, Mul, ..." +#: src/SUMMARY.md src/smart-pointers.md +msgid "Smart Pointers" +msgstr "" -#: src/SUMMARY.md:154 -msgid "Closures: Fn, FnMut, FnOnce" -msgstr "Kapanışlar (Closures): Fn, FnMut, FnOnce" +#: src/SUMMARY.md src/smart-pointers/box.md +#: src/android/interoperability/cpp/type-mapping.md +msgid "`Box`" +msgstr "" -#: src/SUMMARY.md:156 -msgid "A Simple GUI Library" -msgstr "Basit bir GUI Kütüphanesi" +#: src/SUMMARY.md src/smart-pointers/rc.md +msgid "`Rc`" +msgstr "" -#: src/SUMMARY.md:157 src/exercises/day-3/solutions-morning.md:142 -msgid "Points and Polygons" -msgstr "Noktalar ve Çokgenler" +#: src/SUMMARY.md src/smart-pointers/exercise.md +msgid "Exercise: Binary Tree" +msgstr "" -#: src/SUMMARY.md:159 +#: src/SUMMARY.md msgid "Day 3: Afternoon" msgstr "Gün 3: Öğleden Sonra" -#: src/SUMMARY.md:161 src/error-handling.md:1 -msgid "Error Handling" -msgstr "Hata İşleme" +#: src/SUMMARY.md src/borrowing.md +msgid "Borrowing" +msgstr "Ödünç Alma" -#: src/SUMMARY.md:162 src/error-handling/panics.md:1 -msgid "Panics" -msgstr "Panikler" +#: src/SUMMARY.md src/borrowing/shared.md +#, fuzzy +msgid "Borrowing a Value" +msgstr "Ödünç Alma" -#: src/SUMMARY.md:163 -msgid "Catching Stack Unwinding" -msgstr "Yığın Geri Sarımınının Yakalanması" +#: src/SUMMARY.md src/borrowing/borrowck.md +#, fuzzy +msgid "Borrow Checking" +msgstr "Ödünç Alma" -#: src/SUMMARY.md:164 -msgid "Structured Error Handling" -msgstr "Yapılandırılmış Hata İşlemesi" +#: src/SUMMARY.md src/borrowing/interior-mutability.md +#, fuzzy +msgid "Interior Mutability" +msgstr "Birlikte Çalışabilirlik" -#: src/SUMMARY.md:165 -msgid "Propagating Errors with ?" -msgstr "? ile Hataların Yayılması" +#: src/SUMMARY.md src/borrowing/exercise.md +#, fuzzy +msgid "Exercise: Health Statistics" +msgstr "Sağlık İstatistikleri" -#: src/SUMMARY.md:166 src/error-handling/converting-error-types.md:1 -#: src/error-handling/converting-error-types-example.md:1 -msgid "Converting Error Types" -msgstr "Hata Türlerinin Dönüştürülmesi" +#: src/SUMMARY.md src/slices-and-lifetimes.md +#, fuzzy +msgid "Slices and Lifetimes" +msgstr "Ömürler" -#: src/SUMMARY.md:168 src/error-handling/deriving-error-enums.md:1 -msgid "Deriving Error Enums" -msgstr "Hata Enumlarının Türetilmesi" +#: src/SUMMARY.md +#, fuzzy +msgid "Slices: `&[T]`" +msgstr "Dilimler (Slices)" -#: src/SUMMARY.md:169 src/error-handling/dynamic-errors.md:1 -msgid "Dynamic Error Types" -msgstr "Dinamik Hata Türleri" +#: src/SUMMARY.md src/slices-and-lifetimes/str.md +#, fuzzy +msgid "String References" +msgstr "Geçersiz (Dangling) Referanslar" + +#: src/SUMMARY.md src/slices-and-lifetimes/lifetime-annotations.md +#, fuzzy +msgid "Lifetime Annotations" +msgstr "Fonksiyon Çağrılarında Ömürler" + +#: src/SUMMARY.md +#, fuzzy +msgid "Lifetime Elision" +msgstr "Ömürler" + +#: src/SUMMARY.md +#, fuzzy +msgid "Struct Lifetimes" +msgstr "Ömürler" + +#: src/SUMMARY.md src/slices-and-lifetimes/exercise.md +msgid "Exercise: Protobuf Parsing" +msgstr "" + +#: src/SUMMARY.md +#, fuzzy +msgid "Day 4: Morning" +msgstr "Gün 1: Sabah" + +#: src/SUMMARY.md src/iterators.md +msgid "Iterators" +msgstr "" + +#: src/SUMMARY.md src/iterators/iterator.md src/bare-metal/no_std.md +msgid "`Iterator`" +msgstr "" + +#: src/SUMMARY.md src/iterators/intoiterator.md +msgid "`IntoIterator`" +msgstr "" + +#: src/SUMMARY.md +#, fuzzy +msgid "`FromIterator`" +msgstr "FromIterator" -#: src/SUMMARY.md:170 src/error-handling/error-contexts.md:1 -msgid "Adding Context to Errors" -msgstr "Hatalara Bağlam (Context) Ekleme" +#: src/SUMMARY.md src/iterators/exercise.md +msgid "Exercise: Iterator Method Chaining" +msgstr "" + +#: src/SUMMARY.md src/modules.md src/modules/modules.md +msgid "Modules" +msgstr "Modüller" + +#: src/SUMMARY.md src/modules/filesystem.md +msgid "Filesystem Hierarchy" +msgstr "Dosya Sistemi Hiyerarşisi" + +#: src/SUMMARY.md src/modules/visibility.md +msgid "Visibility" +msgstr "Görünürlük" + +#: src/SUMMARY.md +msgid "`use`, `super`, `self`" +msgstr "" -#: src/SUMMARY.md:171 src/testing.md:1 +#: src/SUMMARY.md src/modules/exercise.md +msgid "Exercise: Modules for a GUI Library" +msgstr "" + +#: src/SUMMARY.md src/testing.md src/chromium/testing.md msgid "Testing" msgstr "Test Etme" -#: src/SUMMARY.md:172 src/testing/unit-tests.md:1 -msgid "Unit Tests" -msgstr "Birim Testleri" - -#: src/SUMMARY.md:173 src/testing/test-modules.md:1 +#: src/SUMMARY.md msgid "Test Modules" msgstr "Test Modülleri" -#: src/SUMMARY.md:174 src/testing/doc-tests.md:1 -msgid "Documentation Tests" -msgstr "Dokümantasyon Testleri" +#: src/SUMMARY.md src/testing/other.md +#, fuzzy +msgid "Other Types of Tests" +msgstr "Diğer Kaynaklar" -#: src/SUMMARY.md:175 src/testing/integration-tests.md:1 -msgid "Integration Tests" -msgstr "Entegrasyon Testleri" +#: src/SUMMARY.md src/testing/useful-crates.md +msgid "Useful Crates" +msgstr "Kullanışlı Sandıklar (Crates)" -#: src/SUMMARY.md:176 src/bare-metal/useful-crates.md:1 -msgid "Useful crates" -msgstr "Kullanışlı sandıklar (crates)" +#: src/SUMMARY.md src/testing/googletest.md +msgid "GoogleTest" +msgstr "" + +#: src/SUMMARY.md src/testing/mocking.md +msgid "Mocking" +msgstr "" + +#: src/SUMMARY.md src/testing/lints.md +msgid "Compiler Lints and Clippy" +msgstr "" -#: src/SUMMARY.md:177 src/unsafe.md:1 +#: src/SUMMARY.md src/testing/exercise.md +#, fuzzy +msgid "Exercise: Luhn Algorithm" +msgstr "Luhn Algrotiması" + +#: src/SUMMARY.md +#, fuzzy +msgid "Day 4: Afternoon" +msgstr "Gün 1: Öğleden Sonra" + +#: src/SUMMARY.md src/error-handling.md +msgid "Error Handling" +msgstr "Hata İşleme" + +#: src/SUMMARY.md src/error-handling/panics.md +msgid "Panics" +msgstr "Panikler" + +#: src/SUMMARY.md src/error-handling/try.md +#, fuzzy +msgid "Try Operator" +msgstr "Iterator" + +#: src/SUMMARY.md src/error-handling/try-conversions.md +#, fuzzy +msgid "Try Conversions" +msgstr "Örtülü Dönüşümler" + +#: src/SUMMARY.md +#, fuzzy +msgid "`Error` Trait" +msgstr "Daha Fazla Özellik (Trait)" + +#: src/SUMMARY.md src/error-handling/thiserror-and-anyhow.md +msgid "`thiserror` and `anyhow`" +msgstr "" + +#: src/SUMMARY.md +msgid "Exercise: Rewriting with `Result`" +msgstr "" + +#: src/SUMMARY.md src/unsafe-rust.md src/unsafe-rust/unsafe.md msgid "Unsafe Rust" msgstr "Güvensiz (Unsafe) Rust" -#: src/SUMMARY.md:178 src/unsafe/raw-pointers.md:1 +#: src/SUMMARY.md +#, fuzzy +msgid "Unsafe" +msgstr "Güvensiz (Unsafe) Rust" + +#: src/SUMMARY.md src/unsafe-rust/dereferencing.md msgid "Dereferencing Raw Pointers" msgstr "Ham Göstericilerinin İçeriği (Dereferencing)" -#: src/SUMMARY.md:179 src/unsafe/mutable-static-variables.md:1 +#: src/SUMMARY.md src/unsafe-rust/mutable-static.md msgid "Mutable Static Variables" msgstr "Değiştirilebilir Statik Değişkenler" -#: src/SUMMARY.md:180 src/unsafe/unions.md:1 +#: src/SUMMARY.md src/unsafe-rust/unions.md msgid "Unions" msgstr "Birlikler (Unions)" -#: src/SUMMARY.md:181 src/unsafe/calling-unsafe-functions.md:1 -msgid "Calling Unsafe Functions" +#: src/SUMMARY.md src/unsafe-rust/unsafe-functions.md +#, fuzzy +msgid "Unsafe Functions" msgstr "Güvensiz (Unsafe) Fonksiyonları Çağırma" -#: src/SUMMARY.md:182 src/unsafe/writing-unsafe-functions.md:1 -msgid "Writing Unsafe Functions" -msgstr "Güvensiz (Unsafe) Fonksiyonlar Yazma" - -#: src/SUMMARY.md:183 -msgid "Extern Functions" -msgstr "Dış Bağlantıya Sahip Fonksiyonlar" - -#: src/SUMMARY.md:184 src/unsafe/unsafe-traits.md:1 -msgid "Implementing Unsafe Traits" +#: src/SUMMARY.md +#, fuzzy +msgid "Unsafe Traits" msgstr "Güvensiz Özelliklerin (Unsafe Traits) Gerçekleştirilmesi" -#: src/SUMMARY.md:186 src/exercises/day-3/safe-ffi-wrapper.md:1 -#: src/exercises/day-3/solutions-afternoon.md:3 -msgid "Safe FFI Wrapper" +#: src/SUMMARY.md +#, fuzzy +msgid "Exercise: FFI Wrapper" msgstr "Güvenli FFI Sarıcı (Wrapper)" -#: src/SUMMARY.md:189 src/SUMMARY.md:259 src/bare-metal/android.md:1 +#: src/SUMMARY.md src/bare-metal/android.md msgid "Android" msgstr "Android" -#: src/SUMMARY.md:194 src/android/setup.md:1 +#: src/SUMMARY.md src/android/setup.md src/chromium/setup.md msgid "Setup" msgstr "Kurulum (Setup)" -#: src/SUMMARY.md:195 src/android/build-rules.md:1 +#: src/SUMMARY.md src/android/build-rules.md msgid "Build Rules" msgstr "İnşa (Build) Kuralları" -#: src/SUMMARY.md:196 +#: src/SUMMARY.md msgid "Binary" msgstr "İkili (Binary) Dosya" -#: src/SUMMARY.md:197 +#: src/SUMMARY.md msgid "Library" msgstr "Kütüphane" -#: src/SUMMARY.md:198 src/android/aidl.md:1 +#: src/SUMMARY.md src/android/aidl.md msgid "AIDL" msgstr "AIDL" -#: src/SUMMARY.md:199 +#: src/SUMMARY.md msgid "Interface" msgstr "Arayüz" -#: src/SUMMARY.md:200 +#: src/SUMMARY.md msgid "Implementation" msgstr "Gerçekleştirim" -#: src/SUMMARY.md:201 +#: src/SUMMARY.md msgid "Server" msgstr "Sunucu" -#: src/SUMMARY.md:202 src/android/aidl/deploy.md:1 +#: src/SUMMARY.md src/android/aidl/deploy.md msgid "Deploy" msgstr "Dağıtmak (Deploy)" -#: src/SUMMARY.md:203 +#: src/SUMMARY.md msgid "Client" msgstr "İstemci" -#: src/SUMMARY.md:204 src/android/aidl/changing.md:1 +#: src/SUMMARY.md src/android/aidl/changing.md msgid "Changing API" msgstr "API'yi Değiştirme" -#: src/SUMMARY.md:205 src/SUMMARY.md:249 src/android/logging.md:1 -#: src/bare-metal/aps/logging.md:1 +#: src/SUMMARY.md src/android/logging.md src/bare-metal/aps/logging.md msgid "Logging" msgstr "Kayıt Tutma (Logging)" -#: src/SUMMARY.md:206 src/android/interoperability.md:1 +#: src/SUMMARY.md src/android/interoperability.md msgid "Interoperability" msgstr "Birlikte Çalışabilirlik" -#: src/SUMMARY.md:207 +#: src/SUMMARY.md msgid "With C" msgstr "C ile" -#: src/SUMMARY.md:208 +#: src/SUMMARY.md msgid "Calling C with Bindgen" msgstr "Bindgen ile Rust Tarafından C'yi Kullanma" -#: src/SUMMARY.md:209 +#: src/SUMMARY.md msgid "Calling Rust from C" msgstr "C Tarafından Rust'ı Kullanma" -#: src/SUMMARY.md:210 src/android/interoperability/cpp.md:1 +#: src/SUMMARY.md src/android/interoperability/cpp.md msgid "With C++" msgstr "C++ ile" -#: src/SUMMARY.md:211 +#: src/SUMMARY.md src/android/interoperability/cpp/bridge.md +#, fuzzy +msgid "The Bridge Module" +msgstr "Test Modülleri" + +#: src/SUMMARY.md +#, fuzzy +msgid "Rust Bridge" +msgstr "Android'de Rust" + +#: src/SUMMARY.md src/android/interoperability/cpp/generated-cpp.md +msgid "Generated C++" +msgstr "" + +#: src/SUMMARY.md +msgid "C++ Bridge" +msgstr "" + +#: src/SUMMARY.md src/android/interoperability/cpp/shared-types.md +#, fuzzy +msgid "Shared Types" +msgstr "Skaler Türler" + +#: src/SUMMARY.md src/android/interoperability/cpp/shared-enums.md +msgid "Shared Enums" +msgstr "" + +#: src/SUMMARY.md src/android/interoperability/cpp/rust-result.md +#, fuzzy +msgid "Rust Error Handling" +msgstr "Hata İşleme" + +#: src/SUMMARY.md src/android/interoperability/cpp/cpp-exception.md +#, fuzzy +msgid "C++ Error Handling" +msgstr "Hata İşleme" + +#: src/SUMMARY.md src/android/interoperability/cpp/type-mapping.md +msgid "Additional Types" +msgstr "" + +#: src/SUMMARY.md +msgid "Building for Android: C++" +msgstr "" + +#: src/SUMMARY.md +msgid "Building for Android: Genrules" +msgstr "" + +#: src/SUMMARY.md +msgid "Building for Android: Rust" +msgstr "" + +#: src/SUMMARY.md msgid "With Java" msgstr "Java ile" -#: src/SUMMARY.md:215 +#: src/SUMMARY.md src/exercises/android/morning.md +#: src/exercises/bare-metal/morning.md src/exercises/bare-metal/afternoon.md +#: src/exercises/concurrency/morning.md src/exercises/concurrency/afternoon.md +msgid "Exercises" +msgstr "Egzersizler" + +#: src/SUMMARY.md +msgid "Chromium" +msgstr "" + +#: src/SUMMARY.md src/chromium/cargo.md +msgid "Comparing Chromium and Cargo Ecosystems" +msgstr "" + +#: src/SUMMARY.md +msgid "Policy" +msgstr "" + +#: src/SUMMARY.md +#, fuzzy +msgid "Unsafe Code" +msgstr "Güvensiz (Unsafe) Rust" + +#: src/SUMMARY.md src/chromium/build-rules/depending.md +msgid "Depending on Rust Code from Chromium C++" +msgstr "" + +#: src/SUMMARY.md src/chromium/build-rules/vscode.md +msgid "Visual Studio Code" +msgstr "" + +#: src/SUMMARY.md src/exercises/chromium/third-party.md +#, fuzzy +msgid "Exercise" +msgstr "Egzersizler" + +#: src/SUMMARY.md src/chromium/testing/rust-gtest-interop.md +msgid "`rust_gtest_interop` Library" +msgstr "" + +#: src/SUMMARY.md src/chromium/testing/build-gn.md +msgid "GN Rules for Rust Tests" +msgstr "" + +#: src/SUMMARY.md src/chromium/testing/chromium-import-macro.md +msgid "`chromium::import!` Macro" +msgstr "" + +#: src/SUMMARY.md src/chromium/interoperability-with-cpp.md +#, fuzzy +msgid "Interoperability with C++" +msgstr "Birlikte Çalışabilirlik" + +#: src/SUMMARY.md src/chromium/interoperability-with-cpp/example-bindings.md +#, fuzzy +msgid "Example Bindings" +msgstr "Örnekler" + +#: src/SUMMARY.md src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "Limitations of CXX" +msgstr "" + +#: src/SUMMARY.md src/chromium/interoperability-with-cpp/error-handling.md +#, fuzzy +msgid "CXX Error Handling" +msgstr "Hata İşleme" + +#: src/SUMMARY.md +#, fuzzy +msgid "Error Handling: QR Example" +msgstr "Hata İşleme" + +#: src/SUMMARY.md +#, fuzzy +msgid "Error Handling: PNG Example" +msgstr "Hata İşleme" + +#: src/SUMMARY.md +msgid "Using CXX in Chromium" +msgstr "" + +#: src/SUMMARY.md src/chromium/adding-third-party-crates.md +msgid "Adding Third Party Crates" +msgstr "" + +#: src/SUMMARY.md +msgid "Configuring Cargo.toml" +msgstr "" + +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +msgid "Configuring `gnrt_config.toml`" +msgstr "" + +#: src/SUMMARY.md src/chromium/adding-third-party-crates/downloading-crates.md +msgid "Downloading Crates" +msgstr "" + +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "Generating `gn` Build Rules" +msgstr "" + +#: src/SUMMARY.md src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Resolving Problems" +msgstr "" + +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +msgid "Build Scripts Which Generate Code" +msgstr "" + +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "Build Scripts Which Build C++ or Take Arbitrary Actions" +msgstr "" + +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "Depending on a Crate" +msgstr "" + +#: src/SUMMARY.md +msgid "Reviews and Audits" +msgstr "" + +#: src/SUMMARY.md +msgid "Checking into Chromium Source Code" +msgstr "" + +#: src/SUMMARY.md src/chromium/adding-third-party-crates/keeping-up-to-date.md +msgid "Keeping Crates Up to Date" +msgstr "" + +#: src/SUMMARY.md +msgid "Bringing It Together - Exercise" +msgstr "" + +#: src/SUMMARY.md src/exercises/chromium/solutions.md +#, fuzzy +msgid "Exercise Solutions" +msgstr "Çözümler" + +#: src/SUMMARY.md msgid "Bare Metal: Morning" msgstr "Yalın Metal (Bare Metal): Sabah" -#: src/SUMMARY.md:220 -msgid "no_std" -msgstr "no_std" +#: src/SUMMARY.md src/bare-metal/no_std.md +msgid "`no_std`" +msgstr "" -#: src/SUMMARY.md:221 +#: src/SUMMARY.md msgid "A Minimal Example" msgstr "Minimal Bir Örnek" -#: src/SUMMARY.md:222 -msgid "alloc" -msgstr "alloc" +#: src/SUMMARY.md src/bare-metal/no_std.md src/bare-metal/alloc.md +msgid "`alloc`" +msgstr "" -#: src/SUMMARY.md:223 src/bare-metal/microcontrollers.md:1 +#: src/SUMMARY.md src/bare-metal/microcontrollers.md msgid "Microcontrollers" msgstr "Mikrodenetleyiciler" -#: src/SUMMARY.md:224 src/bare-metal/microcontrollers/mmio.md:1 +#: src/SUMMARY.md src/bare-metal/microcontrollers/mmio.md msgid "Raw MMIO" msgstr "Ham MMIO" -#: src/SUMMARY.md:225 +#: src/SUMMARY.md msgid "PACs" msgstr "PAC'ler" -#: src/SUMMARY.md:226 +#: src/SUMMARY.md msgid "HAL Crates" msgstr "HAL Sandıkları (Crates)" -#: src/SUMMARY.md:227 +#: src/SUMMARY.md msgid "Board Support Crates" msgstr "Kart Destek Sandıkları (Board Support Crates)" -#: src/SUMMARY.md:228 +#: src/SUMMARY.md msgid "The Type State Pattern" msgstr "Tür Durum Deseni" -#: src/SUMMARY.md:229 -msgid "embedded-hal" -msgstr "embedded-hal" +#: src/SUMMARY.md src/bare-metal/microcontrollers/embedded-hal.md +msgid "`embedded-hal`" +msgstr "" -#: src/SUMMARY.md:230 -msgid "probe-rs, cargo-embed" +#: src/SUMMARY.md src/bare-metal/microcontrollers/probe-rs.md +#, fuzzy +msgid "`probe-rs` and `cargo-embed`" msgstr "probe-rs, cargo-embed" -#: src/SUMMARY.md:231 src/bare-metal/microcontrollers/debugging.md:1 +#: src/SUMMARY.md src/bare-metal/microcontrollers/debugging.md msgid "Debugging" msgstr "Hata Ayıklama" -#: src/SUMMARY.md:232 src/SUMMARY.md:252 +#: src/SUMMARY.md msgid "Other Projects" msgstr "Diğer Projeler" -#: src/SUMMARY.md:234 src/exercises/bare-metal/compass.md:1 -#: src/exercises/bare-metal/solutions-morning.md:3 +#: src/SUMMARY.md src/exercises/bare-metal/compass.md +#: src/exercises/bare-metal/solutions-morning.md msgid "Compass" msgstr "Pusula" -#: src/SUMMARY.md:236 +#: src/SUMMARY.md +msgid "Solutions" +msgstr "Çözümler" + +#: src/SUMMARY.md msgid "Bare Metal: Afternoon" msgstr "Yalın Metal (Bare Metal): Öğleden Sonra" -#: src/SUMMARY.md:238 +#: src/SUMMARY.md msgid "Application Processors" msgstr "Uygulama İşlemcileri" -#: src/SUMMARY.md:239 src/bare-metal/aps/entry-point.md:1 +#: src/SUMMARY.md src/bare-metal/aps/entry-point.md msgid "Getting Ready to Rust" msgstr "Rust'a Hazırlanmak" -#: src/SUMMARY.md:240 +#: src/SUMMARY.md msgid "Inline Assembly" msgstr "Satır İçi Assembly" -#: src/SUMMARY.md:241 +#: src/SUMMARY.md msgid "MMIO" msgstr "MMIO" -#: src/SUMMARY.md:242 +#: src/SUMMARY.md msgid "Let's Write a UART Driver" msgstr "Bir UART Sürücü Yazalım" -#: src/SUMMARY.md:243 +#: src/SUMMARY.md msgid "More Traits" msgstr "Daha Fazla Özellik (Trait)" -#: src/SUMMARY.md:244 +#: src/SUMMARY.md msgid "A Better UART Driver" msgstr "Daha İyi Bir UART Sürücüsü" -#: src/SUMMARY.md:245 src/bare-metal/aps/better-uart/bitflags.md:1 +#: src/SUMMARY.md src/bare-metal/aps/better-uart/bitflags.md msgid "Bitflags" msgstr "Bitflags Sandığı" -#: src/SUMMARY.md:246 +#: src/SUMMARY.md msgid "Multiple Registers" msgstr "Çoklu Yazmaçlar (Registers)" -#: src/SUMMARY.md:247 src/bare-metal/aps/better-uart/driver.md:1 +#: src/SUMMARY.md src/bare-metal/aps/better-uart/driver.md msgid "Driver" msgstr "Sürücü" -#: src/SUMMARY.md:248 src/SUMMARY.md:250 +#: src/SUMMARY.md msgid "Using It" msgstr "Onu Kullan" -#: src/SUMMARY.md:251 src/bare-metal/aps/exceptions.md:1 +#: src/SUMMARY.md src/bare-metal/aps/exceptions.md msgid "Exceptions" msgstr "İstisnalar" -#: src/SUMMARY.md:253 -msgid "Useful Crates" -msgstr "Kullanışlı Sandıklar (Crates)" - -#: src/SUMMARY.md:254 -msgid "zerocopy" -msgstr "zerocopy" +#: src/SUMMARY.md src/bare-metal/useful-crates/zerocopy.md +msgid "`zerocopy`" +msgstr "" -#: src/SUMMARY.md:255 -msgid "aarch64-paging" -msgstr "aarch64-paging" +#: src/SUMMARY.md src/bare-metal/useful-crates/aarch64-paging.md +msgid "`aarch64-paging`" +msgstr "" -#: src/SUMMARY.md:256 -msgid "buddy_system_allocator" -msgstr "buddy_system_allocator" +#: src/SUMMARY.md src/bare-metal/useful-crates/buddy_system_allocator.md +msgid "`buddy_system_allocator`" +msgstr "" -#: src/SUMMARY.md:257 -msgid "tinyvec" -msgstr "tinyvec" +#: src/SUMMARY.md src/bare-metal/useful-crates/tinyvec.md +msgid "`tinyvec`" +msgstr "" -#: src/SUMMARY.md:258 -msgid "spin" -msgstr "spin" +#: src/SUMMARY.md src/bare-metal/useful-crates/spin.md +msgid "`spin`" +msgstr "" -#: src/SUMMARY.md:260 src/bare-metal/android/vmbase.md:1 -msgid "vmbase" +#: src/SUMMARY.md +#, fuzzy +msgid "`vmbase`" msgstr "vmbase" -#: src/SUMMARY.md:262 +#: src/SUMMARY.md msgid "RTC Driver" msgstr "RTC Sürücüsü" -#: src/SUMMARY.md:265 +#: src/SUMMARY.md msgid "Concurrency: Morning" msgstr "Eşzamanlılık: Sabah" -#: src/SUMMARY.md:270 src/concurrency/threads.md:1 +#: src/SUMMARY.md src/concurrency/threads.md msgid "Threads" msgstr "İş Parçacıkları (Threads)" -#: src/SUMMARY.md:271 src/concurrency/scoped-threads.md:1 +#: src/SUMMARY.md src/concurrency/scoped-threads.md msgid "Scoped Threads" msgstr "Kapsamlı İş Parçacıkları (Threads)" -#: src/SUMMARY.md:272 src/concurrency/channels.md:1 +#: src/SUMMARY.md src/concurrency/channels.md msgid "Channels" msgstr "Kanallar" -#: src/SUMMARY.md:273 src/concurrency/channels/unbounded.md:1 +#: src/SUMMARY.md src/concurrency/channels/unbounded.md msgid "Unbounded Channels" msgstr "Sınırsız Kanallar" -#: src/SUMMARY.md:274 src/concurrency/channels/bounded.md:1 +#: src/SUMMARY.md src/concurrency/channels/bounded.md msgid "Bounded Channels" msgstr "Sınırlı Kanallar" -#: src/SUMMARY.md:275 -msgid "Send and Sync" -msgstr "Send ve Sync" +#: src/SUMMARY.md src/concurrency/send-sync.md +msgid "`Send` and `Sync`" +msgstr "" -#: src/SUMMARY.md:275 -msgid "Send" -msgstr "Send" +#: src/SUMMARY.md src/concurrency/send-sync/send.md +msgid "`Send`" +msgstr "" -#: src/SUMMARY.md:275 -msgid "Sync" -msgstr "Sync" +#: src/SUMMARY.md src/concurrency/send-sync/sync.md +msgid "`Sync`" +msgstr "" -#: src/SUMMARY.md:278 src/concurrency/send-sync/examples.md:1 +#: src/SUMMARY.md src/concurrency/send-sync/examples.md msgid "Examples" msgstr "Örnekler" -#: src/SUMMARY.md:279 src/concurrency/shared_state.md:1 +#: src/SUMMARY.md src/concurrency/shared_state.md msgid "Shared State" msgstr "Paylaşımlı Durum (State)" -#: src/SUMMARY.md:280 -msgid "Arc" -msgstr "Arc" +#: src/SUMMARY.md src/concurrency/shared_state/arc.md +msgid "`Arc`" +msgstr "" + +#: src/SUMMARY.md src/concurrency/shared_state/mutex.md +msgid "`Mutex`" +msgstr "" -#: src/SUMMARY.md:281 -msgid "Mutex" -msgstr "Mutex" +#: src/SUMMARY.md src/memory-management/review.md +#: src/error-handling/try-conversions.md +#: src/concurrency/shared_state/example.md +msgid "Example" +msgstr "Örnek" -#: src/SUMMARY.md:284 src/SUMMARY.md:305 -#: src/exercises/concurrency/dining-philosophers.md:1 -#: src/exercises/concurrency/solutions-morning.md:3 +#: src/SUMMARY.md src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md msgid "Dining Philosophers" msgstr "Filozofların Akşam Yemeği" -#: src/SUMMARY.md:285 src/exercises/concurrency/link-checker.md:1 +#: src/SUMMARY.md src/exercises/concurrency/link-checker.md msgid "Multi-threaded Link Checker" msgstr "Çok İş Parçacıklı Link Denetleyicisi" -#: src/SUMMARY.md:287 +#: src/SUMMARY.md msgid "Concurrency: Afternoon" msgstr "Eşzamanlılık: Öğleden Sonra" -#: src/SUMMARY.md:289 +#: src/SUMMARY.md msgid "Async Basics" msgstr "Async Temelleri" -#: src/SUMMARY.md:290 -msgid "async/await" -msgstr "async/await" +#: src/SUMMARY.md src/async/async-await.md +msgid "`async`/`await`" +msgstr "" -#: src/SUMMARY.md:291 src/async/futures.md:1 +#: src/SUMMARY.md src/async/futures.md msgid "Futures" msgstr "Future Özellikleri (Traits)" -#: src/SUMMARY.md:292 src/async/runtimes.md:1 +#: src/SUMMARY.md src/async/runtimes.md msgid "Runtimes" msgstr "Çalışma Zamanları" -#: src/SUMMARY.md:293 src/async/runtimes/tokio.md:1 +#: src/SUMMARY.md src/async/runtimes/tokio.md msgid "Tokio" msgstr "Tokio Sandığı" -#: src/SUMMARY.md:294 src/exercises/concurrency/link-checker.md:126 -#: src/async/tasks.md:1 src/exercises/concurrency/chat-app.md:143 +#: src/SUMMARY.md src/exercises/concurrency/link-checker.md src/async/tasks.md +#: src/exercises/concurrency/chat-app.md msgid "Tasks" msgstr "Görevler" -#: src/SUMMARY.md:295 src/async/channels.md:1 +#: src/SUMMARY.md src/async/channels.md msgid "Async Channels" msgstr "Async Kanalları" -#: src/SUMMARY.md:297 src/async/control-flow/join.md:1 +#: src/SUMMARY.md +msgid "Control Flow" +msgstr "Kontrol Akışı" + +#: src/SUMMARY.md src/async/control-flow/join.md msgid "Join" msgstr "Join" -#: src/SUMMARY.md:298 src/async/control-flow/select.md:1 +#: src/SUMMARY.md src/async/control-flow/select.md msgid "Select" msgstr "Select" -#: src/SUMMARY.md:299 +#: src/SUMMARY.md msgid "Pitfalls" msgstr "Tuzaklar" -#: src/SUMMARY.md:300 +#: src/SUMMARY.md msgid "Blocking the Executor" msgstr "Yürütücünün/Çalıştırıcının (Executor) Engellenmesi" -#: src/SUMMARY.md:301 src/async/pitfalls/pin.md:1 -msgid "Pin" -msgstr "Pin" +#: src/SUMMARY.md src/async/pitfalls/pin.md +msgid "`Pin`" +msgstr "" -#: src/SUMMARY.md:302 src/async/pitfalls/async-traits.md:1 +#: src/SUMMARY.md src/async/pitfalls/async-traits.md msgid "Async Traits" msgstr "Async Özellikleri (Traits)" -#: src/SUMMARY.md:303 src/async/pitfalls/cancellation.md:1 +#: src/SUMMARY.md src/async/pitfalls/cancellation.md msgid "Cancellation" msgstr "İptal (Cancellation)" -#: src/SUMMARY.md:306 src/exercises/concurrency/chat-app.md:1 -#: src/exercises/concurrency/solutions-afternoon.md:95 +#: src/SUMMARY.md src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "Broadcast Chat Application" msgstr "Yayımlamalı Sohbet Uygulaması" -#: src/SUMMARY.md:309 +#: src/SUMMARY.md msgid "Final Words" msgstr "Son sözler" -#: src/SUMMARY.md:313 src/thanks.md:1 +#: src/SUMMARY.md src/thanks.md msgid "Thanks!" msgstr "Teşekkürler!" -#: src/SUMMARY.md:314 src/glossary.md:1 +#: src/SUMMARY.md src/glossary.md msgid "Glossary" msgstr "Sözlük" -#: src/SUMMARY.md:315 +#: src/SUMMARY.md msgid "Other Resources" msgstr "Diğer Kaynaklar" -#: src/SUMMARY.md:316 src/credits.md:1 +#: src/SUMMARY.md src/credits.md msgid "Credits" msgstr "Emekler" -#: src/SUMMARY.md:319 src/exercises/solutions.md:1 -msgid "Solutions" -msgstr "Çözümler" - -#: src/SUMMARY.md:324 -msgid "Day 1 Morning" -msgstr "1. Gün Sabah" - -#: src/SUMMARY.md:325 -msgid "Day 1 Afternoon" -msgstr "1. Gün Öğleden Sonra" - -#: src/SUMMARY.md:326 -msgid "Day 2 Morning" -msgstr "2. Gün Sabah" - -#: src/SUMMARY.md:327 -msgid "Day 2 Afternoon" -msgstr "2. Gün Öüleden Sonra" - -#: src/SUMMARY.md:328 -msgid "Day 3 Morning" -msgstr "3. Gün Sabah" - -#: src/SUMMARY.md:329 -msgid "Day 3 Afternoon" -msgstr "3. Gün Öğleden Sonra" - -#: src/SUMMARY.md:330 -msgid "Bare Metal Rust Morning" -msgstr "Yalın (Bare) Metal Rust Sabah" - -#: src/SUMMARY.md:331 src/exercises/bare-metal/solutions-afternoon.md:1 -msgid "Bare Metal Rust Afternoon" -msgstr "Yalın (Bare) Metal Rust Öğleden Sonra" - -#: src/SUMMARY.md:332 -msgid "Concurrency Morning" -msgstr "Eşzamanlılık Sabah" - -#: src/SUMMARY.md:333 -msgid "Concurrency Afternoon" -msgstr "Eşzamanlılık Öğleden Sonra" - -#: src/index.md:3 +#: src/index.md msgid "" "[![Build workflow](https://img.shields.io/github/actions/workflow/status/" "google/comprehensive-rust/build.yml?style=flat-square)](https://github.com/" @@ -1052,7 +1243,7 @@ msgstr "" "io/github/stars/google/comprehensive-rust?style=flat-square)](https://github." "com/google/comprehensive-rust/stargazers)" -#: src/index.md:7 +#: src/index.md 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 " @@ -1062,7 +1253,7 @@ msgstr "" "kursudur. Kurs, temel sözdiziminden jenerikler ve hata işleme gibi ileri " "düzey konulara kadar Rust'ın tüm yelpazesini kapsar." -#: src/index.md:11 +#: src/index.md msgid "" "The latest version of the course can be found at . If you are reading somewhere else, please check there " @@ -1072,7 +1263,7 @@ msgstr "" "adresinden ulaşılabilir. Başka bir yerde okuyorsanız, lütfen güncellemeleri " "kontrol edin." -#: src/index.md:15 +#: src/index.md msgid "" "The goal of the course is to teach you Rust. We assume you don't know " "anything about Rust and hope to:" @@ -1080,31 +1271,32 @@ msgstr "" "Kursun amacı size Rust'ı öğretmektir. Rust hakkında hiçbir şey bilmediğinizi " "varsayıyoruz ve şunu umuyoruz:" -#: src/index.md:18 +#: src/index.md msgid "Give you a comprehensive understanding of the Rust syntax and language." msgstr "Rust sözdizimi ve dili hakkında kapsamlı bir anlayış sunmayı." -#: src/index.md:19 +#: src/index.md msgid "Enable you to modify existing programs and write new programs in Rust." msgstr "" "Rust'ta mevcut programları değiştirmenize ve yeni programlar yazmanıza " "olanak sağlamayı." -#: src/index.md:20 +#: src/index.md msgid "Show you common Rust idioms." msgstr "Yaygın Rust kod kaplarını göstermeyi." -#: src/index.md:22 -msgid "We call the first three course days Rust Fundamentals." +#: src/index.md +#, fuzzy +msgid "We call the first four course days Rust Fundamentals." msgstr "İlk üç kurs gününe Rust Esasları (Rust Fundamentals) adını veriyoruz." -#: src/index.md:24 +#: src/index.md msgid "" "Building on this, you're invited to dive into one or more specialized topics:" msgstr "" "Buna dayanarak, bir veya daha fazla uzmanlık konusuna dalmaya davetlisiniz:" -#: src/index.md:26 +#: src/index.md msgid "" "[Android](android.md): a half-day course on using Rust for Android platform " "development (AOSP). This includes interoperability with C, C++, and Java." @@ -1113,7 +1305,18 @@ msgstr "" "kullanımına ilişkin yarım günlük bir kurs. Buna C, C++ ve Java ile birlikte " "çalışabilirlik de dahildir." -#: src/index.md:28 +#: src/index.md +#, fuzzy +msgid "" +"[Chromium](chromium.md): a half-day course on using Rust within Chromium " +"based browsers. This includes interoperability with C++ and how to include " +"third-party crates in Chromium." +msgstr "" +"[Android](android.md): Android platformu geliştirme (AOSP) için Rust'ın " +"kullanımına ilişkin yarım günlük bir kurs. Buna C, C++ ve Java ile birlikte " +"çalışabilirlik de dahildir." + +#: src/index.md msgid "" "[Bare-metal](bare-metal.md): a whole-day class on using Rust for bare-metal " "(embedded) development. Both microcontrollers and application processors are " @@ -1123,7 +1326,7 @@ msgstr "" "kullanımına ilişkin tam günlük bir ders. Hem mikrodenetleyiciler hem de " "uygulama işlemcileri kapsanmaktadır." -#: src/index.md:31 +#: src/index.md msgid "" "[Concurrency](concurrency.md): a whole-day class on concurrency in Rust. We " "cover both classical concurrency (preemptively scheduling using threads and " @@ -1135,11 +1338,11 @@ msgstr "" "kesintili/geçişli zamanlama) hem de async/await eşzamanlılığını (future " "özelliklerini kullanarak işbirlikçi çoklu görev) ele alıyoruz." -#: src/index.md:37 +#: src/index.md msgid "Non-Goals" msgstr "Hedef Dışı" -#: src/index.md:39 +#: src/index.md 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:" @@ -1147,7 +1350,7 @@ msgstr "" "Rust geniş bir dil ve birkaç gün içinde tamamını ele almamız mümkün " "olmayacak. Aşağıdakiler bu kursun amaçları dışında kalır:" -#: src/index.md:42 +#: src/index.md 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]" @@ -1158,11 +1361,11 @@ msgstr "" "[Örneklerle Rust](https://doc.rust-lang.org/rust-by-example/macros.html) " "bakınız." -#: src/index.md:46 +#: src/index.md msgid "Assumptions" msgstr "Varsayımlar" -#: src/index.md:48 +#: src/index.md 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 " @@ -1172,7 +1375,7 @@ msgstr "" "olarak yazılmış bir dildir ve Rust yaklaşımını daha iyi açıklamak veya " "karşılaştırmak için bazen C ve C++ ile karşılaştırmalar yapacağız." -#: src/index.md:52 +#: src/index.md 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." @@ -1180,7 +1383,7 @@ msgstr "" "Python veya JavaScript gibi dinamik olarak yazılmış bir dilde nasıl " "programlanacağını biliyorsanız, o zaman da gayet iyi takip edebileceksiniz." -#: src/index.md:57 +#: src/index.md 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 " @@ -1190,11 +1393,11 @@ msgstr "" "kullanacağız. Bunlar, eğitmenin ele alması gereken önemli noktaların yanı " "sıra sınıfta ortaya çıkan tipik soruların yanıtları da olabilir." -#: src/running-the-course.md:3 src/running-the-course/course-structure.md:3 +#: src/running-the-course.md src/running-the-course/course-structure.md msgid "This page is for the course instructor." msgstr "Bu sayfa kurs eğitmenine yöneliktir." -#: src/running-the-course.md:5 +#: src/running-the-course.md msgid "" "Here is a bit of background information about how we've been running the " "course internally at Google." @@ -1202,14 +1405,13 @@ msgstr "" "Kursu Google'da dahili olarak nasıl kullandığımıza dair biraz arka plan " "bilgisini burada bulabilirsiniz." -#: src/running-the-course.md:8 +#: src/running-the-course.md +#, fuzzy msgid "" -"We typically run classes from 10:00 am to 4:00 pm, with a 1 hour lunch break " -"in the middle. This leaves 2.5 hours for the morning class and 2.5 hours for " -"the afternoon class. Note that this is just a recommendation: you can also " -"spend 3 hour on the morning session to give people more time for exercises. " -"The downside of longer session is that people can become very tired after 6 " -"full hours of class in the afternoon." +"We typically run classes from 9:00 am to 4:00 pm, with a 1 hour lunch break " +"in the middle. This leaves 3 hours for the morning class and 3 hours for the " +"afternoon class. Both sessions contain multiple breaks and time for students " +"to work on exercises." msgstr "" "Dersleri genellikle sabah 10:00'dan akşam 16:00'ya kadar yürütüyoruz ve " "ortasında 1 saatlik öğle yemeği molası veriyoruz. Geriye sabah dersi için " @@ -1219,11 +1421,11 @@ msgstr "" "dezavantajı, 16.00'dan sonra yani 6 saatlik dersten sonra insanların çok " "yorulabilmesidir." -#: src/running-the-course.md:16 +#: src/running-the-course.md msgid "Before you run the course, you will want to:" msgstr "Kursu çalıştırmadan önce şunları yapmak isteyeceksiniz:" -#: src/running-the-course.md:18 +#: src/running-the-course.md 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 " @@ -1238,19 +1440,20 @@ msgstr "" "küçük oklu bağlantıya tıklayın). Bu şekilde sınıfa sunacağınız temiz bir " "ekrana sahip olursunuz." -#: src/running-the-course.md:24 +#: src/running-the-course.md +#, fuzzy msgid "" -"Decide on the dates. Since the course takes at least three full days, we " -"recommend that you schedule the days over two weeks. Course participants " -"have said that they find it helpful to have a gap in the course since it " -"helps them process all the information we give them." +"Decide on the dates. Since the course takes four days, we recommend that you " +"schedule the days over two weeks. Course participants have said that they " +"find it helpful to have a gap in the course since it helps them process all " +"the information we give them." msgstr "" "Tarihlere karar verin. Kurs en az üç tam gün sürdüğünden, günleri iki " "haftaya yaymanızı öneririz. Kurs katılımcıları, kursta boşluk kalmasının, " "onlara verdiğimiz tüm bilgileri işlemelerine yardımcı olması açısından " "yararlı bulduklarını belirtmişlerdir." -#: src/running-the-course.md:29 +#: src/running-the-course.md 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 " @@ -1268,7 +1471,7 @@ msgstr "" "çalışabilmesi gerekir. Özellikle eğitmen olarak çok sayıda canlı kodlama " "yapacaksınız, bu nedenle kürsü size pek yardımcı olmayacaktır." -#: src/running-the-course.md:37 +#: src/running-the-course.md 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 " @@ -1285,7 +1488,7 @@ msgstr "" "veya kurs katılımcılarının tespit ettiği yazım hatalarını düzeltmenize de " "olanak tanır." -#: src/running-the-course.md:43 +#: src/running-the-course.md 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 " @@ -1303,7 +1506,7 @@ msgstr "" "gördüğünüzde bunu sınıfa söyleyin ve bir çözüm önerin; örneğin insanlara " "standart kütüphanede ilgili bilgiyi nerede bulabileceklerini gösterin." -#: src/running-the-course.md:51 +#: src/running-the-course.md 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!" @@ -1311,7 +1514,7 @@ msgstr "" "Hepsi bu kadar, kursta iyi şanslar! Umarız bizim için olduğu kadar sizin " "için de eğlenceli olur!" -#: src/running-the-course.md:54 +#: src/running-the-course.md msgid "" "Please [provide feedback](https://github.com/google/comprehensive-rust/" "discussions/86) afterwards so that we can keep improving the course. We " @@ -1325,53 +1528,171 @@ msgstr "" "isteriz. Öğrencileriniz de [bize geri bildirim gönderebilir](https://github." "com/google/comprehensive-rust/discussions/100)!" -#: src/running-the-course/course-structure.md:5 +#: src/running-the-course/course-structure.md msgid "Rust Fundamentals" msgstr "Rust Esasları" -#: src/running-the-course/course-structure.md:7 +#: src/running-the-course/course-structure.md +#, fuzzy msgid "" -"The first three days make up [Rust Fundaments](../welcome-day-1.md). The " -"days are fast paced and we cover a lot of ground:" +"The first four days make up [Rust Fundamentals](../welcome-day-1.md). The " +"days are fast paced and we cover a lot of ground!" msgstr "" "İlk üç gün [Rust Temelleri](../welcome-day-1.md)'ni oluşturur. Günler hızlı " "geçiyor ve çok fazla yol kat ediyoruz:" -#: src/running-the-course/course-structure.md:10 -msgid "Day 1: Basic Rust, syntax, control flow, creating and consuming values." +#: src/running-the-course/course-structure.md +#, fuzzy +msgid "Course schedule:" +msgstr "Kurs Yapısı" + +#: src/running-the-course/course-structure.md +msgid "Day 1 Morning (3 hours, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Welcome](../welcome-day-1.md) (5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Hello, World](../hello-world.md) (20 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Types and Values](../types-and-values.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Control Flow Basics](../control-flow-basics.md) (1 hour)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 1 Afternoon (2 hours and 55 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Tuples and Arrays](../tuples-and-arrays.md) (1 hour)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[References](../references.md) (50 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[User-Defined Types](../user-defined-types.md) (50 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 2 Morning (3 hours and 5 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Welcome](../welcome-day-2.md) (3 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Pattern Matching](../pattern-matching.md) (50 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Methods and Traits](../methods-and-traits.md) (55 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Generics](../generics.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 2 Afternoon (3 hours, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Standard Library Types](../std-types.md) (1 hour and 10 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Standard Library Traits](../std-traits.md) (1 hour and 40 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 3 Morning (2 hours and 15 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Welcome](../welcome-day-3.md) (3 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Memory Management](../memory-management.md) (1 hour and 10 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Smart Pointers](../smart-pointers.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 3 Afternoon (2 hours and 20 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Borrowing](../borrowing.md) (1 hour)" msgstr "" -"1. Gün: Temel Rust, sözdizimi, kontrol akışı, değer oluşturma ve tüketme." -#: src/running-the-course/course-structure.md:11 +#: src/running-the-course/course-structure.md msgid "" -"Day 2: Memory management, ownership, compound data types, and the standard " -"library." +"[Slices and Lifetimes](../slices-and-lifetimes.md) (1 hour and 10 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 4 Morning (3 hours and 5 minutes, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Welcome](../welcome-day-4.md) (3 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Iterators](../iterators.md) (45 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Modules](../modules.md) (40 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Testing](../testing.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "Day 4 Afternoon (2 hours, including breaks)" +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "[Error Handling](../error-handling.md) (45 minutes)" msgstr "" -"2. Gün: Bellek yönetimi, sahiplik, bileşik veri türleri ve standart kitaplık." -#: src/running-the-course/course-structure.md:12 -msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." +#: src/running-the-course/course-structure.md +msgid "[Unsafe Rust](../unsafe-rust.md) (1 hour and 5 minutes)" msgstr "" -"3. Gün: Jenerikler, özellikler (traits), hata işleme, testler ve güvenli " -"olmayan (unsafe) Rust." -#: src/running-the-course/course-structure.md:14 +#: src/running-the-course/course-structure.md msgid "Deep Dives" msgstr "Derin Dalışlar" -#: src/running-the-course/course-structure.md:16 +#: src/running-the-course/course-structure.md +#, fuzzy msgid "" -"In addition to the 3-day class on Rust Fundamentals, we cover some more " +"In addition to the 4-day class on Rust Fundamentals, we cover some more " "specialized topics:" msgstr "" "Rust'ın Esasları hakkındaki 3 günlük derse ek olarak, daha özel konuları da " "ele alıyoruz:" -#: src/running-the-course/course-structure.md:19 +#: src/running-the-course/course-structure.md msgid "Rust in Android" msgstr "Android'de Rust" -#: src/running-the-course/course-structure.md:21 +#: src/running-the-course/course-structure.md 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 " @@ -1381,7 +1702,7 @@ msgstr "" "geliştirme için Rust'ı kullanma konusunda yarım günlük bir kurstur. Buna C, " "C++ ve Java ile birlikte çalışabilirlik (interoperability) de dahildir." -#: src/running-the-course/course-structure.md:25 +#: src/running-the-course/course-structure.md msgid "" "You will need an [AOSP checkout](https://source.android.com/docs/setup/" "download/downloading). Make a checkout of the [course repository](https://" @@ -1396,7 +1717,7 @@ msgstr "" "sisteminin `src/android/` içindeki `Android.bp` dosyalarını görmesini " "sağlayacaktır." -#: src/running-the-course/course-structure.md:30 +#: src/running-the-course/course-structure.md 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 " @@ -1407,11 +1728,31 @@ msgstr "" "(build) edin. Çalıştırdığı komutları görmek için betiği okuyun ve bunları " "elle çalıştırdığınızda çalıştıklarından emin olun." -#: src/running-the-course/course-structure.md:37 +#: src/running-the-course/course-structure.md +#, fuzzy +msgid "Rust in Chromium" +msgstr "Android'de Rust" + +#: src/running-the-course/course-structure.md +msgid "" +"The [Rust in Chromium](../chromium.md) deep dive is a half-day course on " +"using Rust as part of the Chromium browser. It includes using Rust in " +"Chromium's `gn` build system, bringing in third-party libraries (\"crates\") " +"and C++ interoperability." +msgstr "" + +#: src/running-the-course/course-structure.md +msgid "" +"You will need to be able to build Chromium --- a debug, component build is " +"[recommended](../chromium/setup.md) for speed but any build will work. " +"Ensure that you can run the Chromium browser that you've built." +msgstr "" + +#: src/running-the-course/course-structure.md msgid "Bare-Metal Rust" msgstr "Yalın-Metal (Bare-metal) Rust" -#: src/running-the-course/course-structure.md:39 +#: src/running-the-course/course-structure.md 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 " @@ -1421,7 +1762,7 @@ msgstr "" "(gömülü) geliştirme için Rust kullanımına ilişkin tam günlük bir derstir. " "Hem mikrodenetleyiciler hem de uygulama işlemcileri kapsanmaktadır." -#: src/running-the-course/course-structure.md:43 +#: src/running-the-course/course-structure.md 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 " @@ -1433,11 +1774,11 @@ msgstr "" "sayfasında](../bare-metal.md) açıklandığı gibi bir dizi paketi yüklemesi " "gerekecektir." -#: src/running-the-course/course-structure.md:48 +#: src/running-the-course/course-structure.md msgid "Concurrency in Rust" msgstr "Rust'ta Eşzamanlılık" -#: src/running-the-course/course-structure.md:50 +#: src/running-the-course/course-structure.md msgid "" "The [Concurrency in Rust](../concurrency.md) deep dive is a full day class " "on classical as well as `async`/`await` concurrency." @@ -1445,7 +1786,7 @@ msgstr "" "[Rust'ta Eşzamanlılık](../concurrency.md) ayrıntılı incelemesi, klasik ve " "aynı zamanda `async`/`await` eşzamanlılığı üzerine tam günlük bir derstir." -#: src/running-the-course/course-structure.md:53 +#: src/running-the-course/course-structure.md 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 " @@ -1455,11 +1796,11 @@ msgstr "" "getirilmesine ihtiyacınız olacak. Daha sonra örnekleri denemek için " "kopyalayıp `src/main.rs` dosyasına yapıştırabilirsiniz:" -#: src/running-the-course/course-structure.md:64 +#: src/running-the-course/course-structure.md msgid "Format" msgstr "Format" -#: src/running-the-course/course-structure.md:66 +#: src/running-the-course/course-structure.md msgid "" "The course is meant to be very interactive and we recommend letting the " "questions drive the exploration of Rust!" @@ -1467,49 +1808,49 @@ msgstr "" "Kursun çok etkileşimli olması amaçlanıyor ve soruların Rust'ın keşfini " "yönlendirmesine izin vermenizi öneririz!" -#: src/running-the-course/keyboard-shortcuts.md:3 +#: src/running-the-course/keyboard-shortcuts.md msgid "There are several useful keyboard shortcuts in mdBook:" msgstr "mdBook'ta birkaç kullanışlı klavye kısayolu vardır:" -#: src/running-the-course/keyboard-shortcuts.md:5 +#: src/running-the-course/keyboard-shortcuts.md msgid "Arrow-Left" msgstr "Yön Oku-Sol" -#: src/running-the-course/keyboard-shortcuts.md:5 +#: src/running-the-course/keyboard-shortcuts.md msgid ": Navigate to the previous page." msgstr ": Önceki sayfaya gidin." -#: src/running-the-course/keyboard-shortcuts.md:6 +#: src/running-the-course/keyboard-shortcuts.md msgid "Arrow-Right" msgstr "Yön Oku-Sağ" -#: src/running-the-course/keyboard-shortcuts.md:6 +#: src/running-the-course/keyboard-shortcuts.md msgid ": Navigate to the next page." msgstr ": Sonraki sayfaya gidin." -#: src/running-the-course/keyboard-shortcuts.md:7 src/cargo/code-samples.md:19 +#: src/running-the-course/keyboard-shortcuts.md src/cargo/code-samples.md msgid "Ctrl + Enter" msgstr "Ctrl + Enter" -#: src/running-the-course/keyboard-shortcuts.md:7 +#: src/running-the-course/keyboard-shortcuts.md msgid ": Execute the code sample that has focus." msgstr ": Odaklı kod örneğini yürütün." -#: src/running-the-course/keyboard-shortcuts.md:8 +#: src/running-the-course/keyboard-shortcuts.md msgid "s" msgstr "s" -#: src/running-the-course/keyboard-shortcuts.md:8 +#: src/running-the-course/keyboard-shortcuts.md msgid ": Activate the search bar." msgstr ": Arama çubuğunu etkinleştirin." -#: src/running-the-course/translations.md:3 +#: src/running-the-course/translations.md msgid "" "The course has been translated into other languages by a set of wonderful " "volunteers:" msgstr "Kurs bir grup harika gönüllüler tarafından diğer dillere çevrildi:" -#: src/running-the-course/translations.md:6 +#: src/running-the-course/translations.md msgid "" "[Brazilian Portuguese](https://google.github.io/comprehensive-rust/pt-BR/) " "by [@rastringer](https://github.com/rastringer), [@hugojacob](https://github." @@ -1521,7 +1862,7 @@ msgstr "" "github.com/hugojacob), [@joaovicmendes](https://github.com/joaovicmendes) ve " "[@henrif75](https://github.com/henrif75)." -#: src/running-the-course/translations.md:7 +#: src/running-the-course/translations.md msgid "" "[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " "by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" @@ -1537,7 +1878,7 @@ msgstr "" "(https://github.com/superwhd), [@SketchK](https://github.com/SketchK) ve " "[@nodmp](https://github.com/nodmp)." -#: src/running-the-course/translations.md:8 +#: src/running-the-course/translations.md msgid "" "[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " "by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" @@ -1551,7 +1892,7 @@ msgstr "" "[@kuanhungchen](https://github.com/kuanhungchen) ve [@johnathan79717]" "(https://github.com/johnathan79717)." -#: src/running-the-course/translations.md:9 +#: src/running-the-course/translations.md msgid "" "[Korean](https://google.github.io/comprehensive-rust/ko/) by [@keispace]" "(https://github.com/keispace), [@jiyongp](https://github.com/jiyongp), and " @@ -1561,7 +1902,7 @@ msgstr "" "[@keispace](https://github.com/keispace), [@jiyongp](https://github.com) /" "jiyongp) ve [@jooyunghan](https://github.com/jooyunghan)." -#: src/running-the-course/translations.md:10 +#: src/running-the-course/translations.md msgid "" "[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid]" "(https://github.com/deavid)." @@ -1569,17 +1910,17 @@ msgstr "" "[Bengalce](https://google.github.io/comprehensive-rust/bn/) yazanlar: " "[@raselmandol](https://github.com/raselmandol)." -#: src/running-the-course/translations.md:12 +#: src/running-the-course/translations.md msgid "" "Use the language picker in the top-right corner to switch between languages." msgstr "" "Diller arasında geçiş yapmak için sağ üst köşedeki dil seçiciyi kullanın." -#: src/running-the-course/translations.md:14 +#: src/running-the-course/translations.md msgid "Incomplete Translations" msgstr "Tamamlanmamış Çeviriler" -#: src/running-the-course/translations.md:16 +#: src/running-the-course/translations.md msgid "" "There is a large number of in-progress translations. We link to the most " "recently updated translations:" @@ -1587,7 +1928,7 @@ msgstr "" "Devam eden çok sayıda çeviri var. En son güncellenen çevirilere bağlantı " "veriyoruz:" -#: src/running-the-course/translations.md:19 +#: src/running-the-course/translations.md msgid "" "[Bengali](https://google.github.io/comprehensive-rust/bn/) by [@raselmandol]" "(https://github.com/raselmandol)." @@ -1595,7 +1936,7 @@ msgstr "" "[Bengalce](https://google.github.io/comprehensive-rust/bn/) yazanlar: " "[@raselmandol](https://github.com/raselmandol)." -#: src/running-the-course/translations.md:20 +#: src/running-the-course/translations.md msgid "" "[French](https://google.github.io/comprehensive-rust/fr/) by [@KookaS]" "(https://github.com/KookaS) and [@vcaen](https://github.com/vcaen)." @@ -1603,7 +1944,7 @@ msgstr "" "[Fransızca](https://google.github.io/comprehensive-rust/fr/) yazanlar: " "[@KookaS](https://github.com/KookaS) ve [@vcaen](https://github.com) /vcaen)." -#: src/running-the-course/translations.md:21 +#: src/running-the-course/translations.md msgid "" "[German](https://google.github.io/comprehensive-rust/de/) by [@Throvn]" "(https://github.com/Throvn) and [@ronaldfw](https://github.com/ronaldfw)." @@ -1612,7 +1953,7 @@ msgstr "" "[@Throvn](https://github.com/Throvn) ve [@ronaldfw](https://github.com) /" "ronaldfw)." -#: src/running-the-course/translations.md:22 +#: src/running-the-course/translations.md msgid "" "[Japanese](https://google.github.io/comprehensive-rust/ja/) by [@CoinEZ-JPN]" "(https://github.com/CoinEZ) and [@momotaro1105](https://github.com/" @@ -1622,7 +1963,7 @@ msgstr "" "[@CoinEZ-JPN](https://github.com/CoinEZ) ve [@momotaro1105](https://github) ." "com/momotaro1105)." -#: src/running-the-course/translations.md:24 +#: src/running-the-course/translations.md 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 " @@ -1634,7 +1975,7 @@ msgstr "" "main/TRANSLATIONS.md) bakın. Çeviriler [sorun izleyicide](https://github.com/" "google/comprehensive-rust/issues/282) üzerinde koordine edilir." -#: src/cargo.md:3 +#: src/cargo.md 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 " @@ -1648,15 +1989,15 @@ msgstr "" "Cargo'nun ne olduğuna, daha geniş ekosisteme nasıl uyum sağladığına ve bu " "eğitime nasıl uyduğuna dair kısa bir genel bakış sunmak istiyoruz." -#: src/cargo.md:8 +#: src/cargo.md msgid "Installation" msgstr "Kurulum" -#: src/cargo.md:10 +#: src/cargo.md msgid "**Please follow the instructions on .**" msgstr "**Lütfen adresindeki talimatları izleyin.**" -#: src/cargo.md:12 +#: src/cargo.md 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 " @@ -1667,7 +2008,7 @@ msgstr "" "çapraz derlemeyi ayarlamak vb. için kullanabileceğiniz bir komut satırı " "yardımcı programı olan `rustup` a sahip olacaksınız." -#: src/cargo.md:14 +#: src/cargo.md 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-" @@ -1686,7 +2027,7 @@ msgstr "" "yapar. Ayrıca [RustRover](https://www.jetbrains.com/rust/) adında farklı bir " "IDE de mevcuttur." -#: src/cargo.md:18 +#: src/cargo.md 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 " @@ -1698,17 +2039,17 @@ msgstr "" "Ancak bu, eski bir Rust sürümüne sahip olmanızı sağlar ve beklenmeyen " "davranışlara yol açabilir. Komut şöyle olacaktır:" -#: src/cargo/rust-ecosystem.md:1 +#: src/cargo/rust-ecosystem.md msgid "The Rust Ecosystem" msgstr "Rust Ekosistemi" -#: src/cargo/rust-ecosystem.md:3 +#: src/cargo/rust-ecosystem.md msgid "" "The Rust ecosystem consists of a number of tools, of which the main ones are:" msgstr "" "Rust ekosistemi bir dizi araçtan oluşur; bunların başlıcaları şunlardır:" -#: src/cargo/rust-ecosystem.md:5 +#: src/cargo/rust-ecosystem.md msgid "" "`rustc`: the Rust compiler which turns `.rs` files into binaries and other " "intermediate formats." @@ -1716,7 +2057,7 @@ msgstr "" "`rustc`: `.rs` dosyalarını ikili (binary) dosyalara ve diğer ara formatlara " "dönüştüren Rust derleyicisi." -#: src/cargo/rust-ecosystem.md:8 +#: src/cargo/rust-ecosystem.md msgid "" "`cargo`: the Rust dependency manager and build tool. Cargo knows how to " "download dependencies, usually hosted on , and it will " @@ -1729,10 +2070,11 @@ msgstr "" "ayrıca birim testlerini yürütmek için kullanılan yerleşik bir test " "çalıştırıcısıyla birlikte gelir." -#: src/cargo/rust-ecosystem.md:13 +#: src/cargo/rust-ecosystem.md +#, fuzzy msgid "" "`rustup`: the Rust toolchain installer and updater. This tool is used to " -"install and update `rustc` and `cargo` when new versions of Rust is " +"install and update `rustc` and `cargo` when new versions of Rust are " "released. In addition, `rustup` can also download documentation for the " "standard library. You can have multiple versions of Rust installed at once " "and `rustup` will let you switch between them as needed." @@ -1744,19 +2086,15 @@ msgstr "" "Rust sürümünü yükleyebilirsiniz ve `rustup` gerektiğinde bunlar arasında " "geçiş yapmanıza olanak tanır." -#: 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 +#: src/cargo/rust-ecosystem.md src/hello-world/hello-world.md +#: src/tuples-and-arrays/tuples-and-arrays.md src/references/exclusive.md +#: src/pattern-matching/destructuring.md src/memory-management/move.md +#: src/error-handling/try.md src/android/setup.md src/concurrency/threads.md +#: src/async/async-await.md msgid "Key points:" msgstr "Anahtar noktalar:" -#: src/cargo/rust-ecosystem.md:23 +#: src/cargo/rust-ecosystem.md msgid "" "Rust has a rapid release schedule with a new release coming out every six " "weeks. New releases maintain backwards compatibility with old releases --- " @@ -1766,14 +2104,14 @@ msgstr "" "var. Yeni sürümler, eski sürümlerle geriye dönük uyumluluğu korur ve ayrıca " "yeni işlevsellik sağlar." -#: src/cargo/rust-ecosystem.md:27 +#: src/cargo/rust-ecosystem.md msgid "" "There are three release channels: \"stable\", \"beta\", and \"nightly\"." msgstr "" "Üç sürüm kanalı vardır: \"kararlı (stable)\", \"beta\" ve \"gecelik " "(nightly)\"." -#: src/cargo/rust-ecosystem.md:29 +#: src/cargo/rust-ecosystem.md msgid "" "New features are being tested on \"nightly\", \"beta\" is what becomes " "\"stable\" every six weeks." @@ -1781,7 +2119,7 @@ msgstr "" "Yeni özellikler \"gecelik (nightly)\" kanalında test ediliyor, \"beta\" her " "altı haftada bir \"kararlı (stable)\" hale geliyor." -#: src/cargo/rust-ecosystem.md:32 +#: src/cargo/rust-ecosystem.md msgid "" "Dependencies can also be resolved from alternative [registries](https://doc." "rust-lang.org/cargo/reference/registries.html), git, folders, and more." @@ -1790,7 +2128,7 @@ msgstr "" "org/cargo/reference/registries.html), git'ten, klasörlerden ve daha " "fazlasından çözülebilir." -#: src/cargo/rust-ecosystem.md:34 +#: src/cargo/rust-ecosystem.md 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." @@ -1799,7 +2137,7 @@ msgstr "" "(editions) vardır: mevcut yayın (edition) Rust 2021'dir. Önceki yayınlar " "Rust 2015 ve Rust 2018'di." -#: src/cargo/rust-ecosystem.md:37 +#: src/cargo/rust-ecosystem.md msgid "" "The editions are allowed to make backwards incompatible changes to the " "language." @@ -1807,7 +2145,7 @@ msgstr "" "Yayınların dilde geriye dönük olarak uyumsuz değişiklikler yapmasına izin " "verilir." -#: src/cargo/rust-ecosystem.md:40 +#: src/cargo/rust-ecosystem.md msgid "" "To prevent breaking code, editions are opt-in: you select the edition for " "your crate via the `Cargo.toml` file." @@ -1815,7 +2153,7 @@ msgstr "" "Kodun kırılmasını (breaking code) önlemek için yayınlar isteğe bağlıdır: " "`Cargo.toml` dosyası aracılığıyla kasanızın (crate) sürümünü seçersiniz." -#: src/cargo/rust-ecosystem.md:43 +#: src/cargo/rust-ecosystem.md msgid "" "To avoid splitting the ecosystem, Rust compilers can mix code written for " "different editions." @@ -1823,7 +2161,7 @@ msgstr "" "Ekosistemin bölünmesini önlemek için Rust derleyicileri farklı sürümler için " "yazılan kodları karıştırabilir." -#: src/cargo/rust-ecosystem.md:46 +#: src/cargo/rust-ecosystem.md msgid "" "Mention that it is quite rare to ever use the compiler directly not through " "`cargo` (most users never do)." @@ -1831,32 +2169,33 @@ msgstr "" "Derleyiciyi `cargo` yoluyla değil de doğrudan kullanmanın oldukça nadir " "olduğunu unutmayın (çoğu kullanıcı asla kullanmaz)." -#: src/cargo/rust-ecosystem.md:48 +#: src/cargo/rust-ecosystem.md +#, fuzzy msgid "" "It might be worth alluding that Cargo itself is an extremely powerful and " -"comprehensive tool. It is capable of many advanced features including but " -"not limited to: " +"comprehensive tool. It is capable of many advanced features including but " +"not limited to:" msgstr "" "Cargo'nun kendisinin son derece güçlü ve kapsamlı bir araç olduğunu " "belirtmekte fayda var. Aşağıdakiler dahil olmakla ve bunlarla sınırlı " "olmamak üzere birçok gelişmiş özelliğe sahiptir: " -#: src/cargo/rust-ecosystem.md:49 +#: src/cargo/rust-ecosystem.md msgid "Project/package structure" msgstr "Proje/paket yapısı" -#: src/cargo/rust-ecosystem.md:50 +#: src/cargo/rust-ecosystem.md msgid "[workspaces](https://doc.rust-lang.org/cargo/reference/workspaces.html)" msgstr "" "[çalışma alanları](https://doc.rust-lang.org/cargo/reference/workspaces.html)" -#: src/cargo/rust-ecosystem.md:51 +#: src/cargo/rust-ecosystem.md msgid "Dev Dependencies and Runtime Dependency management/caching" msgstr "" "Geliştirici Bağımlılıkları ve Çalışma Zamanı Bağımlılığı yönetimi/önbelleğe " "alma" -#: src/cargo/rust-ecosystem.md:52 +#: src/cargo/rust-ecosystem.md msgid "" "[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts." "html)" @@ -1864,14 +2203,14 @@ msgstr "" "[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts." "html)" -#: src/cargo/rust-ecosystem.md:53 +#: src/cargo/rust-ecosystem.md msgid "" "[global installation](https://doc.rust-lang.org/cargo/commands/cargo-install." "html)" msgstr "" "[genel kurulum](https://doc.rust-lang.org/cargo/commands/cargo-install.html)" -#: src/cargo/rust-ecosystem.md:54 +#: src/cargo/rust-ecosystem.md msgid "" "It is also extensible with sub command plugins as well (such as [cargo " "clippy](https://github.com/rust-lang/rust-clippy))." @@ -1879,18 +2218,18 @@ msgstr "" "Ayrıca alt komut eklentileriyle de genişletilebilir ([cargo Clippy](https://" "github.com/rust-lang/rust-clippy) gibi)." -#: src/cargo/rust-ecosystem.md:55 +#: src/cargo/rust-ecosystem.md msgid "" "Read more from the [official Cargo Book](https://doc.rust-lang.org/cargo/)" msgstr "" "[Resmi Cargo Kitabı'ndan](https://doc.rust-lang.org/cargo/) daha fazlasını " "okuyun" -#: src/cargo/code-samples.md:1 +#: src/cargo/code-samples.md msgid "Code Samples in This Training" msgstr "Bu Eğitimdeki Kod Örnekleri" -#: src/cargo/code-samples.md:3 +#: src/cargo/code-samples.md 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 " @@ -1900,7 +2239,7 @@ msgstr "" "çalıştırabileceğiniz örnekler üzerinden inceleyeceğiz. Bu, kurulumu çok daha " "kolay hale getirir ve herkes için tutarlı bir deneyim sağlar." -#: src/cargo/code-samples.md:7 +#: src/cargo/code-samples.md 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 " @@ -1911,33 +2250,23 @@ msgstr "" "için Cargo'ya ihtiyacınız olduğunu gösteren daha büyük bir alıştırma " "yapacağız." -#: src/cargo/code-samples.md:11 +#: src/cargo/code-samples.md msgid "The code blocks in this course are fully interactive:" msgstr "Bu kurstaki kod blokları tamamen etkileşimlidir:" -#: src/cargo/code-samples.md:13 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" +#: src/cargo/code-samples.md src/cargo/running-locally.md +msgid "\"Edit me!\"" msgstr "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" -#: src/cargo/code-samples.md:19 +#: src/cargo/code-samples.md msgid "You can use " msgstr "Odak metin kutusundayken kodu yürütmek için " -#: src/cargo/code-samples.md:19 +#: src/cargo/code-samples.md msgid " to execute the code when focus is in the text box." msgstr " kullanabilirsiniz.." -#: src/cargo/code-samples.md:24 +#: src/cargo/code-samples.md msgid "" "Most code samples are editable like shown above. A few code samples are not " "editable for various reasons:" @@ -1945,7 +2274,7 @@ msgstr "" "Çoğu kod örneği yukarıda gösterildiği gibi düzenlenebilir. Birkaç kod örneği " "çeşitli nedenlerden dolayı düzenlenemez:" -#: src/cargo/code-samples.md:27 +#: src/cargo/code-samples.md msgid "" "The embedded playgrounds cannot execute unit tests. Copy-paste the code and " "open it in the real Playground to demonstrate unit tests." @@ -1954,7 +2283,7 @@ msgstr "" "testlerini göstermek için kodu kopyalayıp yapıştırın ve gerçek Deneme " "Alanında (Playground) açın." -#: src/cargo/code-samples.md:30 +#: src/cargo/code-samples.md 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 " @@ -1964,11 +2293,11 @@ msgstr "" "Öğrencilerin alıştırmaları yerel bir Rust kurulumu kullanarak veya Deneme " "Alanı aracılığıyla çözmelerinin nedeni budur." -#: src/cargo/running-locally.md:1 +#: src/cargo/running-locally.md msgid "Running Code Locally with Cargo" msgstr "Cargo'nun Yerel (Local) Olarak Çalıştırılması" -#: src/cargo/running-locally.md:3 +#: src/cargo/running-locally.md 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 " @@ -1982,7 +2311,7 @@ msgstr "" "`rustc` ve `cargo`vermelidir. Bu yazının yazıldığı sırada en son kararlı " "Rust sürümü şu sürüm numaralarına sahiptir:" -#: src/cargo/running-locally.md:15 +#: src/cargo/running-locally.md msgid "" "You can use any later version too since Rust maintains backwards " "compatibility." @@ -1990,7 +2319,7 @@ msgstr "" "Rust geriye dönük uyumluluğu koruduğu için daha sonraki herhangi bir sürümü " "de kullanabilirsiniz." -#: src/cargo/running-locally.md:17 +#: src/cargo/running-locally.md msgid "" "With this in place, follow these steps to build a Rust binary from one of " "the examples in this training:" @@ -1998,27 +2327,27 @@ msgstr "" "Bunu yaptıktan sonra, bu eğitimdeki örneklerden birinden bir Rust ikili " "(binary) programı oluşturmak için şu adımları izleyin:" -#: src/cargo/running-locally.md:20 +#: src/cargo/running-locally.md msgid "Click the \"Copy to clipboard\" button on the example you want to copy." msgstr "" "Kopyalamak istediğiniz örneğin üzerindeki \"Panoya kopyala\" düğmesine " "tıklayın." -#: src/cargo/running-locally.md:22 +#: src/cargo/running-locally.md msgid "" "Use `cargo new exercise` to create a new `exercise/` directory for your code:" msgstr "" "Kodunuz için yeni bir `exercise/` dizini oluşturmak için `cargo new " "exercise` komutunu kullanın:" -#: src/cargo/running-locally.md:29 +#: src/cargo/running-locally.md msgid "" "Navigate into `exercise/` and use `cargo run` to build and run your binary:" msgstr "" "İkili (binary) dosyanızı inşa etmek (build) ve çalıştırmak için `exercise/` " "dizinine gidin ve `cargo run` komutunu kullanın:" -#: src/cargo/running-locally.md:40 +#: src/cargo/running-locally.md 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" @@ -2027,27 +2356,13 @@ msgstr "" "önceki sayfadaki örneği kullanarak `src/main.rs` dosyasının şu şekilde " "görünmesini sağlayın" -#: src/cargo/running-locally.md:43 -msgid "" -"```rust\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" -msgstr "" -"```rust\n" -"fn main() {\n" -" println!(\"Edit me!\");\n" -"}\n" -"```" - -#: src/cargo/running-locally.md:49 +#: src/cargo/running-locally.md msgid "Use `cargo run` to build and run your updated binary:" msgstr "" "Güncellenmiş ikili (binary) dosyanızı inşa etmek (build) ve çalıştırmak " "(run) için `cargo run` komutunu kullanın:" -#: src/cargo/running-locally.md:59 +#: src/cargo/running-locally.md 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/" @@ -2060,7 +2375,7 @@ msgstr "" "içinde bulacaksınız. `target/release/` içinde optimize edilmiş bir sürüm " "inşası oluşturmak için `cargo build --release` komutunu kullanın." -#: src/cargo/running-locally.md:64 +#: src/cargo/running-locally.md msgid "" "You can add dependencies for your project by editing `Cargo.toml`. When you " "run `cargo` commands, it will automatically download and compile missing " @@ -2070,7 +2385,7 @@ msgstr "" "ekleyebilirsiniz. `cargo` komutlarını çalıştırdığınızda, eksik " "bağımlılıkları sizin için otomatik olarak indirip derleyecektir." -#: src/cargo/running-locally.md:72 +#: src/cargo/running-locally.md 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 " @@ -2080,235 +2395,287 @@ msgstr "" "kullanmaya teşvik etmeye çalışın. Normal bir gelişim ortamına sahip " "olacakları için hayatları kolaylaşacaktır." -#: src/welcome-day-1.md:1 +#: src/welcome-day-1.md msgid "Welcome to Day 1" msgstr "" -#: src/welcome-day-1.md:3 +#: src/welcome-day-1.md msgid "" "This is the first day of Rust Fundamentals. We will cover a lot of ground " "today:" msgstr "" -#: src/welcome-day-1.md:6 +#: src/welcome-day-1.md 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`." +#: src/welcome-day-1.md +#, fuzzy +msgid "Types and type inference." +msgstr "tür çıkarımı:" + +#: src/welcome-day-1.md +msgid "Control flow constructs: loops, conditionals, and so on." +msgstr "" + +#: src/welcome-day-1.md +msgid "User-defined types: structs and enums." msgstr "" -#: src/welcome-day-1.md:12 +#: src/welcome-day-1.md msgid "Pattern matching: destructuring enums, structs, and arrays." msgstr "" -#: src/welcome-day-1.md:16 +#: src/welcome-day-1.md src/welcome-day-2.md src/welcome-day-3.md +#: src/welcome-day-4.md +msgid "Schedule" +msgstr "" + +#: src/welcome-day-1.md src/welcome-day-1-afternoon.md src/welcome-day-2.md +#: src/welcome-day-2-afternoon.md src/welcome-day-3.md +#: src/welcome-day-3-afternoon.md src/welcome-day-4.md +#: src/welcome-day-4-afternoon.md +msgid "In this session:" +msgstr "" + +#: src/welcome-day-1.md +msgid "[Welcome](./welcome-day-1.md) (5 minutes)" +msgstr "" + +#: src/welcome-day-1.md +msgid "[Hello, World](./hello-world.md) (20 minutes)" +msgstr "" + +#: src/welcome-day-1.md +msgid "[Types and Values](./types-and-values.md) (1 hour and 5 minutes)" +msgstr "" + +#: src/welcome-day-1.md +msgid "[Control Flow Basics](./control-flow-basics.md) (1 hour)" +msgstr "" + +#: src/welcome-day-1.md src/welcome-day-2-afternoon.md +msgid "Including 10 minute breaks, this session should take about 3 hours" +msgstr "" + +#: src/welcome-day-1.md msgid "Please remind the students that:" msgstr "" -#: src/welcome-day-1.md:18 +#: src/welcome-day-1.md msgid "" "They should ask questions when they get them, don't save them to the end." msgstr "" -#: src/welcome-day-1.md:19 +#: src/welcome-day-1.md msgid "" "The class is meant to be interactive and discussions are very much " "encouraged!" msgstr "" -#: src/welcome-day-1.md:20 +#: src/welcome-day-1.md msgid "" "As an instructor, you should try to keep the discussions relevant, i.e., " -"keep the discussions related to how Rust does things vs some other " -"language. It can be hard to find the right balance, but err on the side of " -"allowing discussions since they engage people much more than one-way " -"communication." +"keep the discussions related to how Rust does things vs some other language. " +"It can be hard to find the right balance, but err on the side of allowing " +"discussions since they engage people much more than one-way communication." msgstr "" -#: src/welcome-day-1.md:24 +#: src/welcome-day-1.md msgid "" "The questions will likely mean that we talk about things ahead of the slides." msgstr "" -#: src/welcome-day-1.md:25 +#: src/welcome-day-1.md msgid "" "This is perfectly okay! Repetition is an important part of learning. " "Remember that the slides are just a support and you are free to skip them as " "you like." msgstr "" -#: src/welcome-day-1.md:29 +#: src/welcome-day-1.md msgid "" -"The idea for the first day is to show _just enough_ of Rust to be able to " -"speak about the famous borrow checker. The way Rust handles memory is a " -"major feature and we should show students this right away." +"The idea for the first day is to show the \"basic\" things in Rust that " +"should have immediate parallels in other languages. The more advanced parts " +"of Rust come on the subsequent days." msgstr "" -#: src/welcome-day-1.md:33 +#: src/welcome-day-1.md msgid "" "If you're teaching this in a classroom, this is a good place to go over the " -"schedule. We suggest splitting the day into two parts (following the slides):" +"schedule. Note that there is an exercise at the end of each segment, " +"followed by a break. Plan to cover the exercise solution after the break. " +"The times listed here are a suggestion in order to keep the course on " +"schedule. Feel free to be flexible and adjust as necessary!" msgstr "" -#: src/welcome-day-1.md:36 -msgid "Morning: 9:00 to 12:00," +#: src/hello-world.md src/types-and-values.md src/control-flow-basics.md +#: src/tuples-and-arrays.md src/references.md src/user-defined-types.md +#: src/pattern-matching.md src/methods-and-traits.md src/generics.md +#: src/std-types.md src/std-traits.md src/memory-management.md +#: src/smart-pointers.md src/borrowing.md src/slices-and-lifetimes.md +#: src/iterators.md src/modules.md src/testing.md src/error-handling.md +#: src/unsafe-rust.md +msgid "In this segment:" msgstr "" -#: src/welcome-day-1.md:37 -msgid "Afternoon: 13:00 to 16:00." +#: src/hello-world.md +msgid "[What is Rust?](./hello-world/what-is-rust.md) (10 minutes)" msgstr "" -#: src/welcome-day-1.md:39 -msgid "" -"You can of course adjust this as necessary. Please make sure to include " -"breaks, we recommend a break every hour!" +#: src/hello-world.md +msgid "[Hello, World](./hello-world/hello-world.md) (5 minutes)" +msgstr "" + +#: src/hello-world.md +msgid "[Benefits of Rust](./hello-world/benefits.md) (3 minutes)" msgstr "" -#: src/welcome-day-1/what-is-rust.md:3 +#: src/hello-world.md +msgid "[Playground](./hello-world/playground.md) (2 minutes)" +msgstr "" + +#: src/hello-world.md +msgid "This segment should take about 20 minutes" +msgstr "" + +#: src/hello-world/what-is-rust.md msgid "" "Rust is a new programming language which had its [1.0 release in 2015]" "(https://blog.rust-lang.org/2015/05/15/Rust-1.0.html):" msgstr "" -#: src/welcome-day-1/what-is-rust.md:5 +#: src/hello-world/what-is-rust.md msgid "Rust is a statically compiled language in a similar role as C++" msgstr "" -#: src/welcome-day-1/what-is-rust.md:6 +#: src/hello-world/what-is-rust.md msgid "`rustc` uses LLVM as its backend." msgstr "" -#: src/welcome-day-1/what-is-rust.md:7 +#: src/hello-world/what-is-rust.md msgid "" "Rust supports many [platforms and architectures](https://doc.rust-lang.org/" "nightly/rustc/platform-support.html):" msgstr "" -#: src/welcome-day-1/what-is-rust.md:9 +#: src/hello-world/what-is-rust.md msgid "x86, ARM, WebAssembly, ..." msgstr "" -#: src/welcome-day-1/what-is-rust.md:10 +#: src/hello-world/what-is-rust.md msgid "Linux, Mac, Windows, ..." msgstr "" -#: src/welcome-day-1/what-is-rust.md:11 +#: src/hello-world/what-is-rust.md msgid "Rust is used for a wide range of devices:" msgstr "" -#: src/welcome-day-1/what-is-rust.md:12 +#: src/hello-world/what-is-rust.md msgid "firmware and boot loaders," msgstr "" -#: src/welcome-day-1/what-is-rust.md:13 +#: src/hello-world/what-is-rust.md msgid "smart displays," msgstr "" -#: src/welcome-day-1/what-is-rust.md:14 +#: src/hello-world/what-is-rust.md msgid "mobile phones," msgstr "" -#: src/welcome-day-1/what-is-rust.md:15 +#: src/hello-world/what-is-rust.md msgid "desktops," msgstr "" -#: src/welcome-day-1/what-is-rust.md:16 +#: src/hello-world/what-is-rust.md msgid "servers." msgstr "" -#: src/welcome-day-1/what-is-rust.md:21 +#: src/hello-world/what-is-rust.md msgid "Rust fits in the same area as C++:" msgstr "" -#: src/welcome-day-1/what-is-rust.md:23 +#: src/hello-world/what-is-rust.md msgid "High flexibility." msgstr "" -#: src/welcome-day-1/what-is-rust.md:24 +#: src/hello-world/what-is-rust.md msgid "High level of control." msgstr "" -#: src/welcome-day-1/what-is-rust.md:25 +#: src/hello-world/what-is-rust.md msgid "" "Can be scaled down to very constrained devices such as microcontrollers." msgstr "" -#: src/welcome-day-1/what-is-rust.md:26 +#: src/hello-world/what-is-rust.md msgid "Has no runtime or garbage collection." msgstr "" -#: src/welcome-day-1/what-is-rust.md:27 +#: src/hello-world/what-is-rust.md msgid "Focuses on reliability and safety without sacrificing performance." msgstr "" -#: src/hello-world.md:3 +#: src/hello-world/hello-world.md msgid "" "Let us jump into the simplest possible Rust program, a classic Hello World " "program:" msgstr "" -#: src/hello-world.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" println!(\"Hello 🌍!\");\n" -"}\n" -"```" +#: src/hello-world/hello-world.md +msgid "\"Hello 🌍!\"" msgstr "" -#: src/hello-world.md:12 +#: src/hello-world/hello-world.md msgid "What you see:" msgstr "" -#: src/hello-world.md:14 +#: src/hello-world/hello-world.md msgid "Functions are introduced with `fn`." msgstr "" -#: src/hello-world.md:15 +#: src/hello-world/hello-world.md msgid "Blocks are delimited by curly braces like in C and C++." msgstr "" -#: src/hello-world.md:16 +#: src/hello-world/hello-world.md msgid "The `main` function is the entry point of the program." msgstr "" -#: src/hello-world.md:17 +#: src/hello-world/hello-world.md msgid "Rust has hygienic macros, `println!` is an example of this." msgstr "" -#: src/hello-world.md:18 +#: src/hello-world/hello-world.md msgid "Rust strings are UTF-8 encoded and can contain any Unicode character." msgstr "" -#: src/hello-world.md:22 +#: src/hello-world/hello-world.md msgid "" "This slide tries to make the students comfortable with Rust code. They will " -"see a ton of it over the next three days so we start small with something " +"see a ton of it over the next four days so we start small with something " "familiar." msgstr "" -#: src/hello-world.md:27 +#: src/hello-world/hello-world.md msgid "" "Rust is very much like other languages in the C/C++/Java tradition. It is " "imperative and it doesn't try to reinvent things unless absolutely necessary." msgstr "" -#: src/hello-world.md:31 +#: src/hello-world/hello-world.md msgid "Rust is modern with full support for things like Unicode." msgstr "" -#: src/hello-world.md:33 +#: src/hello-world/hello-world.md msgid "" "Rust uses macros for situations where you want to have a variable number of " -"arguments (no function [overloading](basic-syntax/functions-interlude.md))." +"arguments (no function [overloading](../control-flow-basics/functions.md))." msgstr "" -#: src/hello-world.md:36 +#: src/hello-world/hello-world.md msgid "" "Macros being 'hygienic' means they don't accidentally capture identifiers " "from the scope they are used in. Rust macros are actually only [partially " @@ -2316,7 +2683,7 @@ msgid "" "html)." msgstr "" -#: src/hello-world.md:40 +#: src/hello-world/hello-world.md 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, " @@ -2324,95 +2691,109 @@ msgid "" "concepts](https://doc.rust-lang.org/book/ch13-00-functional-features.html)." msgstr "" -#: src/hello-world/small-example.md:3 -msgid "Here is a small example program in Rust:" +#: src/hello-world/benefits.md +msgid "Some unique selling points of Rust:" msgstr "" -#: src/hello-world/small-example.md:5 +#: src/hello-world/benefits.md msgid "" -"```rust,editable\n" -"fn main() { // Program entry point\n" -" let mut x: i32 = 6; // Mutable variable binding\n" -" print!(\"{x}\"); // Macro for printing, like printf\n" -" while x != 1 { // No parenthesis around expression\n" -" if x % 2 == 0 { // Math like in other languages\n" -" x = x / 2;\n" -" } else {\n" -" x = 3 * x + 1;\n" -" }\n" -" print!(\" -> {x}\");\n" -" }\n" -" println!();\n" -"}\n" -"```" +"_Compile time memory safety_ - whole classes of memory bugs are prevented at " +"compile time" msgstr "" -#: 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." +#: src/hello-world/benefits.md +msgid "No uninitialized variables." msgstr "" -#: src/hello-world/small-example.md:29 -msgid "" -"Explain that all variables are statically typed. Try removing `i32` to " -"trigger type inference. Try with `i8` instead and trigger a runtime integer " -"overflow." +#: src/hello-world/benefits.md +msgid "No double-frees." msgstr "" -#: src/hello-world/small-example.md:32 -msgid "Change `let mut x` to `let x`, discuss the compiler error." +#: src/hello-world/benefits.md +msgid "No use-after-free." 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." +#: src/hello-world/benefits.md +msgid "No `NULL` pointers." msgstr "" -#: src/hello-world/small-example.md:37 -msgid "" -"Show how you need to use `{}` as a placeholder if you want to print an " -"expression which is more complex than just a single variable." +#: src/hello-world/benefits.md +msgid "No forgotten locked mutexes." +msgstr "" + +#: src/hello-world/benefits.md +msgid "No data races between threads." +msgstr "" + +#: src/hello-world/benefits.md +msgid "No iterator invalidation." msgstr "" -#: src/hello-world/small-example.md:40 +#: src/hello-world/benefits.md msgid "" -"Show the students the standard library, show them how to search for `std::" -"fmt` which has the rules of the formatting mini-language. It's important " -"that the students become familiar with searching in the standard library." +"_No undefined runtime behavior_ - what a Rust statement does is never left " +"unspecified" +msgstr "" + +#: src/hello-world/benefits.md +msgid "Array access is bounds checked." msgstr "" -#: src/hello-world/small-example.md:44 +#: src/hello-world/benefits.md +msgid "Integer overflow is defined (panic or wrap-around)." +msgstr "" + +#: src/hello-world/benefits.md msgid "" -"In a shell `rustup doc std::fmt` will open a browser on the local std::fmt " -"documentation" +"_Modern language features_ - as expressive and ergonomic as higher-level " +"languages" msgstr "" -#: src/why-rust.md:3 -msgid "Some unique selling points of Rust:" +#: src/hello-world/benefits.md +msgid "Enums and pattern matching." +msgstr "" + +#: src/hello-world/benefits.md +msgid "Generics." +msgstr "" + +#: src/hello-world/benefits.md +msgid "No overhead FFI." +msgstr "" + +#: src/hello-world/benefits.md +msgid "Zero-cost abstractions." +msgstr "" + +#: src/hello-world/benefits.md +msgid "Great compiler errors." +msgstr "" + +#: src/hello-world/benefits.md +msgid "Built-in dependency manager." msgstr "" -#: src/why-rust.md:5 -msgid "Compile time memory safety." +#: src/hello-world/benefits.md +msgid "Built-in support for testing." msgstr "" -#: src/why-rust.md:6 -msgid "Lack of undefined runtime behavior." +#: src/hello-world/benefits.md +msgid "Excellent Language Server Protocol support." msgstr "" -#: src/why-rust.md:7 -msgid "Modern language features." +#: src/hello-world/benefits.md +msgid "" +"Do not spend much time here. All of these points will be covered in more " +"depth later." msgstr "" -#: src/why-rust.md:11 +#: src/hello-world/benefits.md msgid "" "Make sure to ask the class which languages they have experience with. " "Depending on the answer you can highlight different features of Rust:" msgstr "" -#: src/why-rust.md:14 +#: src/hello-world/benefits.md 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 " @@ -2420,7 +2801,7 @@ msgid "" "constructs like pattern matching and built-in dependency management." msgstr "" -#: src/why-rust.md:19 +#: src/hello-world/benefits.md 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 " @@ -2428,4364 +2809,3341 @@ msgid "" "collector) as well as access to low-level hardware (should you need it)" msgstr "" -#: src/why-rust/an-example-in-c.md:4 -msgid "Let's consider the following \"minimum wrong example\" program in C:" -msgstr "" - -#: src/why-rust/an-example-in-c.md:6 +#: src/hello-world/playground.md msgid "" -"```c,editable\n" -"#include \n" -"#include \n" -"#include \n" -"\n" -"int main(int argc, char* argv[]) {\n" -"\tchar *buf, *filename;\n" -"\tFILE *fp;\n" -"\tsize_t bytes, len;\n" -"\tstruct stat st;\n" -"\n" -"\tswitch (argc) {\n" -"\t\tcase 1:\n" -"\t\t\tprintf(\"Too few arguments!\\n\");\n" -"\t\t\treturn 1;\n" -"\n" -"\t\tcase 2:\n" -"\t\t\tfilename = argv[argc];\n" -"\t\t\tstat(filename, &st);\n" -"\t\t\tlen = st.st_size;\n" -"\t\t\t\n" -"\t\t\tbuf = (char*)malloc(len);\n" -"\t\t\tif (!buf)\n" -"\t\t\t\tprintf(\"malloc failed!\\n\", len);\n" -"\t\t\t\treturn 1;\n" -"\n" -"\t\t\tfp = fopen(filename, \"rb\");\n" -"\t\t\tbytes = fread(buf, 1, len, fp);\n" -"\t\t\tif (bytes = st.st_size)\n" -"\t\t\t\tprintf(\"%s\", buf);\n" -"\t\t\telse\n" -"\t\t\t\tprintf(\"fread failed!\\n\");\n" -"\n" -"\t\tcase 3:\n" -"\t\t\tprintf(\"Too many arguments!\\n\");\n" -"\t\t\treturn 1;\n" -"\t}\n" -"\n" -"\treturn 0;\n" -"}\n" -"```" -msgstr "" - -#: src/why-rust/an-example-in-c.md:48 -msgid "How many bugs do you spot?" +"The [Rust Playground](https://play.rust-lang.org/) provides an easy way to " +"run short Rust programs, and is the basis for the examples and exercises in " +"this course. Try running the \"hello-world\" program it starts with. It " +"comes with a few handy features:" msgstr "" -#: src/why-rust/an-example-in-c.md:52 +#: src/hello-world/playground.md msgid "" -"Despite just 29 lines of code, this C example contains serious bugs in at " -"least 11:" +"Under \"Tools\", use the `rustfmt` option to format your code in the " +"\"standard\" way." msgstr "" -#: src/why-rust/an-example-in-c.md:54 -msgid "Assignment `=` instead of equality comparison `==` (line 28)" +#: src/hello-world/playground.md +msgid "" +"Rust has two main \"profiles\" for generating code: Debug (extra runtime " +"checks, less optimization) and Release (fewer runtime checks, lots of " +"optimization). These are accessible under \"Debug\" at the top." msgstr "" -#: src/why-rust/an-example-in-c.md:55 -msgid "Excess argument to `printf` (line 23)" +#: src/hello-world/playground.md +msgid "" +"If you're interested, use \"ASM\" under \"...\" to see the generated " +"assembly code." msgstr "" -#: src/why-rust/an-example-in-c.md:56 -msgid "File descriptor leak (after line 26)" +#: src/hello-world/playground.md +msgid "" +"As students head into the break, encourage them to open up the playground " +"and experiment a little. Encourage them to keep the tab open and try things " +"out during the rest of the course. This is particularly helpful for advanced " +"students who want to know more about Rust's optimizations or generated " +"assembly." msgstr "" -#: src/why-rust/an-example-in-c.md:57 -msgid "Forgotten braces in multi-line `if` (line 22)" +#: src/types-and-values.md +msgid "[Variables](./types-and-values/variables.md) (5 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:58 -msgid "Forgotten `break` in a `switch` statement (line 32)" +#: src/types-and-values.md +msgid "[Values](./types-and-values/values.md) (10 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:59 -msgid "" -"Forgotten NUL-termination of the `buf` string, leading to a buffer overflow " -"(line 29)" +#: src/types-and-values.md +msgid "[Arithmetic](./types-and-values/arithmetic.md) (5 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:60 -msgid "Memory leak by not freeing the `malloc`\\-allocated buffer (line 21)" +#: src/types-and-values.md +msgid "[Strings](./types-and-values/strings.md) (10 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:61 -msgid "Out-of-bounds access (line 17)" +#: src/types-and-values.md +msgid "[Type Inference](./types-and-values/inference.md) (5 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:62 -msgid "Unchecked cases in the `switch` statement (line 11)" +#: src/types-and-values.md +msgid "[Exercise: Fibonacci](./types-and-values/exercise.md) (30 minutes)" msgstr "" -#: src/why-rust/an-example-in-c.md:63 -msgid "Unchecked return values of `stat` and `fopen` (lines 18 and 26)" +#: src/types-and-values.md src/testing.md src/unsafe-rust.md +msgid "This segment should take about 1 hour and 5 minutes" msgstr "" -#: src/why-rust/an-example-in-c.md:65 +#: src/types-and-values/variables.md msgid "" -"_Shouldn't these bugs be obvious even for a C compiler?_ \n" -"No, surprisingly this code compiles warning-free at the default warning " -"level, even in the latest GCC version (13.2 as of writing)." +"Rust provides type safety via static typing. Variable bindings are made with " +"`let`:" msgstr "" -#: src/why-rust/an-example-in-c.md:68 -msgid "" -"_Isn't this a highly unrealistic example?_ \n" -"Absolutely not, these kind of bugs have lead to serious security " -"vulnerabilities in the past. Some examples:" +#: src/types-and-values/variables.md src/control-flow-basics/loops.md +#: src/control-flow-basics/break-continue.md +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"x: {x}\"" msgstr "" -#: src/why-rust/an-example-in-c.md:71 +#: src/types-and-values/variables.md msgid "" -"Assignment `=` instead of equality comparison `==`: [The Linux Backdoor " -"Attempt of 2003](https://freedom-to-tinker.com/2013/10/09/the-linux-backdoor-" -"attempt-of-2003)" +"// x = 20;\n" +" // println!(\"x: {x}\");\n" msgstr "" -#: src/why-rust/an-example-in-c.md:72 +#: src/types-and-values/variables.md msgid "" -"Forgotten braces in multi-line `if`: [The Apple goto fail vulnerability]" -"(https://dwheeler.com/essays/apple-goto-fail.html)" +"Uncomment the `x = 20` to demonstrate that variables are immutable by " +"default. Add the `mut` keyword to allow changes." msgstr "" -#: src/why-rust/an-example-in-c.md:73 +#: src/types-and-values/variables.md msgid "" -"Forgotten `break` in a `switch` statement: [The break that broke sudo]" -"(https://nakedsecurity.sophos.com/2012/05/21/anatomy-of-a-security-hole-the-" -"break-that-broke-sudo)" +"The `i32` here is the type of the variable. This must be known at compile " +"time, but type inference (covered later) allows the programmer to omit it in " +"many cases." msgstr "" -#: src/why-rust/an-example-in-c.md:75 +#: src/types-and-values/values.md msgid "" -"_How is Rust any better here?_ \n" -"Safe Rust makes all of these bugs impossible:" +"Here are some basic built-in types, and the syntax for literal values of " +"each type." msgstr "" -#: src/why-rust/an-example-in-c.md:78 -msgid "Assignments inside an `if` clause are not supported." +#: src/types-and-values/values.md src/tuples-and-arrays/tuples-and-arrays.md +#: src/unsafe-rust/exercise.md +msgid "Types" msgstr "" -#: src/why-rust/an-example-in-c.md:79 -msgid "Format strings are checked at compile-time." +#: src/types-and-values/values.md src/tuples-and-arrays/tuples-and-arrays.md +msgid "Literals" msgstr "" -#: src/why-rust/an-example-in-c.md:80 -msgid "Resources are freed at the end of scope via the `Drop` trait." +#: src/types-and-values/values.md +msgid "Signed integers" msgstr "" -#: src/why-rust/an-example-in-c.md:81 -msgid "All `if` clauses require braces." +#: src/types-and-values/values.md +msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" msgstr "" -#: src/why-rust/an-example-in-c.md:82 -msgid "" -"`match` (as the Rust equivalent to `switch`) does not fall-through, hence " -"you can't accidentally forget a `break`." +#: src/types-and-values/values.md +msgid "`-10`, `0`, `1_000`, `123_i64`" msgstr "" -#: src/why-rust/an-example-in-c.md:83 -msgid "Buffer slices carry their size and don't rely on a NUL terminator." +#: src/types-and-values/values.md +msgid "Unsigned integers" msgstr "" -#: src/why-rust/an-example-in-c.md:84 -msgid "" -"Heap-allocated memory is freed via the `Drop` trait when the corresponding " -"`Box` leaves the scope." +#: src/types-and-values/values.md +msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" msgstr "" -#: src/why-rust/an-example-in-c.md:85 -msgid "" -"Out-of-bounds accesses cause a panic or can be checked via the `get` method " -"of a slice." +#: src/types-and-values/values.md +msgid "`0`, `123`, `10_u16`" msgstr "" -#: src/why-rust/an-example-in-c.md:86 -msgid "`match` mandates that all cases are handled." +#: src/types-and-values/values.md +msgid "Floating point numbers" msgstr "" -#: src/why-rust/an-example-in-c.md:87 -msgid "" -"Fallible Rust functions return `Result` values that need to be unwrapped and " -"thereby checked for success. Additionally, the compiler emits a warning if " -"you miss to check the return value of a function marked with `#[must_use]`." +#: src/types-and-values/values.md +msgid "`f32`, `f64`" msgstr "" -#: src/why-rust/compile-time.md:3 -msgid "Static memory management at compile time:" +#: src/types-and-values/values.md +msgid "`3.14`, `-10.0e20`, `2_f32`" msgstr "" -#: src/why-rust/compile-time.md:5 -msgid "No uninitialized variables." +#: src/types-and-values/values.md +msgid "Unicode scalar values" msgstr "" -#: src/why-rust/compile-time.md:6 -msgid "No memory leaks (_mostly_, see notes)." +#: src/types-and-values/values.md +msgid "`char`" msgstr "" -#: src/why-rust/compile-time.md:7 -msgid "No double-frees." +#: src/types-and-values/values.md +msgid "`'a'`, `'α'`, `'∞'`" msgstr "" -#: src/why-rust/compile-time.md:8 -msgid "No use-after-free." +#: src/types-and-values/values.md +msgid "Booleans" msgstr "" -#: src/why-rust/compile-time.md:9 -msgid "No `NULL` pointers." +#: src/types-and-values/values.md +msgid "`bool`" msgstr "" -#: src/why-rust/compile-time.md:10 -msgid "No forgotten locked mutexes." +#: src/types-and-values/values.md +msgid "`true`, `false`" msgstr "" -#: src/why-rust/compile-time.md:11 -msgid "No data races between threads." +#: src/types-and-values/values.md +msgid "The types have widths as follows:" msgstr "" -#: src/why-rust/compile-time.md:12 -msgid "No iterator invalidation." +#: src/types-and-values/values.md +msgid "`iN`, `uN`, and `fN` are _N_ bits wide," msgstr "" -#: src/why-rust/compile-time.md:16 -msgid "" -"It is possible to produce memory leaks in (safe) Rust. Some examples are:" +#: src/types-and-values/values.md +msgid "`isize` and `usize` are the width of a pointer," msgstr "" -#: src/why-rust/compile-time.md:19 -msgid "" -"You can use [`Box::leak`](https://doc.rust-lang.org/std/boxed/struct.Box." -"html#method.leak) to leak a pointer. A use of this could be to get runtime-" -"initialized and runtime-sized static variables" +#: src/types-and-values/values.md +msgid "`char` is 32 bits wide," msgstr "" -#: src/why-rust/compile-time.md:21 -msgid "" -"You can use [`std::mem::forget`](https://doc.rust-lang.org/std/mem/fn.forget." -"html) to make the compiler \"forget\" about a value (meaning the destructor " -"is never run)." +#: src/types-and-values/values.md +msgid "`bool` is 8 bits wide." 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`." +#: src/types-and-values/values.md +msgid "There are a few syntaxes which are not shown above:" msgstr "" -#: src/why-rust/compile-time.md:25 +#: src/types-and-values/values.md msgid "" -"In fact, some will consider infinitely populating a collection a memory leak " -"and Rust does not protect from those." +"All underscores in numbers can be left out, they are for legibility only. So " +"`1_000` can be written as `1000` (or `10_00`), and `123_i64` can be written " +"as `123i64`." msgstr "" -#: src/why-rust/compile-time.md:28 -msgid "" -"For the purpose of this course, \"No memory leaks\" should be understood as " -"\"Pretty much no _accidental_ memory leaks\"." +#: src/types-and-values/arithmetic.md +msgid "\"result: {}\"" msgstr "" -#: src/why-rust/runtime.md:3 -msgid "No undefined behavior at runtime:" +#: src/types-and-values/arithmetic.md +msgid "" +"This is the first time we've seen a function other than `main`, but the " +"meaning should be clear: it takes three integers, and returns an integer. " +"Functions will be covered in more detail later." msgstr "" -#: src/why-rust/runtime.md:5 -msgid "Array access is bounds checked." +#: src/types-and-values/arithmetic.md +msgid "Arithmetic is very similar to other languages, with similar precedence." msgstr "" -#: src/why-rust/runtime.md:6 -msgid "Integer overflow is defined (panic or wrap-around)." +#: src/types-and-values/arithmetic.md +msgid "" +"What about integer overflow? In C and C++ overflow of _signed_ integers is " +"actually undefined, and might do different things on different platforms or " +"compilers. In Rust, it's defined." msgstr "" -#: src/why-rust/runtime.md:12 +#: src/types-and-values/arithmetic.md 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`)." +"Change the `i32`'s to `i16` to see an integer overflow, which panics " +"(checked) in a debug build and wraps in a release build. There are other " +"options, such as overflowing, saturating, and carrying. These are accessed " +"with method syntax, e.g., `(a * b).saturating_add(b * c).saturating_add(c * " +"a)`." msgstr "" -#: src/why-rust/runtime.md:18 +#: src/types-and-values/arithmetic.md 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." +"In fact, the compiler will detect overflow of constant expressions, which is " +"why the example requires a separate function." msgstr "" -#: src/why-rust/modern.md:3 -msgid "Rust is built with all the experience gained in the last decades." +#: src/types-and-values/strings.md +msgid "" +"Rust has two types to represent strings, both of which will be covered in " +"more depth later. Both _always_ store UTF-8 encoded strings." msgstr "" -#: src/why-rust/modern.md:5 -msgid "Language Features" +#: src/types-and-values/strings.md +msgid "`String` - a modifiable, owned string." msgstr "" -#: src/why-rust/modern.md:7 -msgid "Enums and pattern matching." +#: src/types-and-values/strings.md +msgid "`&str` - a read-only string. String literals have this type." msgstr "" -#: src/why-rust/modern.md:8 -msgid "Generics." +#: src/types-and-values/strings.md +msgid "\"Greetings\"" msgstr "" -#: src/why-rust/modern.md:9 -msgid "No overhead FFI." +#: src/types-and-values/strings.md +msgid "\"🪐\"" msgstr "" -#: src/why-rust/modern.md:10 -msgid "Zero-cost abstractions." +#: src/types-and-values/strings.md +msgid "\", \"" msgstr "" -#: src/why-rust/modern.md:12 -msgid "Tooling" +#: src/types-and-values/strings.md +msgid "\"final sentence: {}\"" msgstr "" -#: src/why-rust/modern.md:14 -msgid "Great compiler errors." +#: src/types-and-values/strings.md src/async/control-flow/join.md +msgid "\"{:?}\"" msgstr "" -#: src/why-rust/modern.md:15 -msgid "Built-in dependency manager." +#: src/types-and-values/strings.md +msgid "//println!(\"{:?}\", &sentence[12..13]);\n" msgstr "" -#: src/why-rust/modern.md:16 -msgid "Built-in support for testing." +#: src/types-and-values/strings.md +msgid "" +"This slide introduces strings. Everything here will be covered in more depth " +"later, but this is enough for subsequent slides and exercises to use strings." msgstr "" -#: src/why-rust/modern.md:17 -msgid "Excellent Language Server Protocol support." +#: src/types-and-values/strings.md +msgid "Invalid UTF-8 in a string is UB, and this not allowed in safe Rust." msgstr "" -#: src/why-rust/modern.md:23 +#: src/types-and-values/strings.md 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." +"`String` is a user-defined type with a constructor (`::new()`) and methods " +"like `s.push_str(..)`." msgstr "" -#: src/why-rust/modern.md:28 +#: src/types-and-values/strings.md 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`." +"The `&` in `&str` indicates that this is a reference. We will cover " +"references later, so for now just think of `&str` as a unit meaning \"a read-" +"only string\"." msgstr "" -#: src/why-rust/modern.md:32 +#: src/types-and-values/strings.md 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." +"The commented-out line is indexing into the string by byte position. " +"`12..13` does not end on a character boundary, so the program panics. Adjust " +"it to a range that does, based on the error message." msgstr "" -#: src/why-rust/modern.md:37 +#: src/types-and-values/strings.md 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:" +"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/why-rust/modern.md:41 -msgid "a random number generator, but see [rand](https://docs.rs/rand/)." +#: src/types-and-values/inference.md +msgid "Rust will look at how the variable is _used_ to determine the type:" msgstr "" -#: src/why-rust/modern.md:42 -msgid "support for SSL or TLS, but see [rusttls](https://docs.rs/rustls/)." +#: src/types-and-values/inference.md +msgid "" +"This slide demonstrates how the Rust compiler infers types based on " +"constraints given by variable declarations and usages." msgstr "" -#: src/why-rust/modern.md:43 -msgid "support for JSON, but see [serde_json](https://docs.rs/serde_json/)." +#: src/types-and-values/inference.md +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/why-rust/modern.md:45 +#: src/types-and-values/inference.md 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." +"When nothing constrains the type of an integer literal, Rust defaults to " +"`i32`. This sometimes appears as `{integer}` in error messages. Similarly, " +"floating-point literals default to `f64`." msgstr "" -#: src/why-rust/modern.md:50 -msgid "" -"Rust comes with a built-in package manager in the form of Cargo and this " -"makes it trivial to download and compile third-party crates. A consequence " -"of this is that the standard library can be smaller." +#: src/types-and-values/inference.md +msgid "// ERROR: no implementation for `{float} == {integer}`\n" msgstr "" -#: src/why-rust/modern.md:54 +#: src/types-and-values/exercise.md msgid "" -"Discovering good third-party crates can be a problem. Sites like help with this by letting you compare health metrics for crates to " -"find a good and trusted one." +"The first and second Fibonacci numbers are both `1`. For n>2, the n'th " +"Fibonacci number is calculated recursively as the sum of the n-1'th and " +"n-2'th Fibonacci numbers." msgstr "" -#: src/why-rust/modern.md:58 +#: src/types-and-values/exercise.md msgid "" -"[rust-analyzer](https://rust-analyzer.github.io/) is a well supported LSP " -"implementation used in major IDEs and text editors." +"Write a function `fib(n)` that calculates the n'th Fibonacci number. When " +"will this function panic?" msgstr "" -#: src/basic-syntax.md:3 -msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" +#: src/types-and-values/exercise.md +msgid "// The base case.\n" msgstr "" -#: src/basic-syntax.md:5 -msgid "Blocks and scopes are delimited by curly braces." +#: src/types-and-values/exercise.md src/control-flow-basics/exercise.md +#, fuzzy +msgid "\"Implement this\"" +msgstr "Gerçekleştirim" + +#: src/types-and-values/exercise.md +msgid "// The recursive case.\n" msgstr "" -#: src/basic-syntax.md:6 -msgid "" -"Line comments are started with `//`, block comments are delimited by `/* ... " -"*/`." +#: src/types-and-values/exercise.md src/types-and-values/solution.md +msgid "\"fib(n) = {}\"" msgstr "" -#: src/basic-syntax.md:8 -msgid "Keywords like `if` and `while` work the same." +#: src/control-flow-basics.md +msgid "[Conditionals](./control-flow-basics/conditionals.md) (5 minutes)" msgstr "" -#: src/basic-syntax.md:9 -msgid "Variable assignment is done with `=`, comparison is done with `==`." +#: src/control-flow-basics.md +msgid "[Loops](./control-flow-basics/loops.md) (5 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Types" +#: src/control-flow-basics.md +msgid "" +"[break and continue](./control-flow-basics/break-continue.md) (5 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:3 src/basic-syntax/compound-types.md:3 -msgid "Literals" +#: src/control-flow-basics.md +msgid "" +"[Blocks and Scopes](./control-flow-basics/blocks-and-scopes.md) (10 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:5 -msgid "Signed integers" +#: src/control-flow-basics.md +msgid "[Functions](./control-flow-basics/functions.md) (3 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:5 -msgid "`i8`, `i16`, `i32`, `i64`, `i128`, `isize`" +#: src/control-flow-basics.md +msgid "[Macros](./control-flow-basics/macros.md) (2 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:5 -msgid "`-10`, `0`, `1_000`, `123_i64`" +#: src/control-flow-basics.md +msgid "" +"[Exercise: Collatz Sequence](./control-flow-basics/exercise.md) (30 minutes)" msgstr "" -#: src/basic-syntax/scalar-types.md:6 -msgid "Unsigned integers" +#: src/control-flow-basics.md src/tuples-and-arrays.md src/borrowing.md +msgid "This segment should take about 1 hour" msgstr "" -#: src/basic-syntax/scalar-types.md:6 -msgid "`u8`, `u16`, `u32`, `u64`, `u128`, `usize`" +#: src/control-flow-basics/conditionals.md +msgid "Much of the Rust syntax will be familiar to you from C, C++ or Java:" msgstr "" -#: src/basic-syntax/scalar-types.md:6 -msgid "`0`, `123`, `10_u16`" +#: src/control-flow-basics/conditionals.md +msgid "Blocks are delimited by curly braces." msgstr "" -#: src/basic-syntax/scalar-types.md:7 -msgid "Floating point numbers" +#: src/control-flow-basics/conditionals.md +msgid "" +"Line comments are started with `//`, block comments are delimited by `/* ... " +"*/`." msgstr "" -#: src/basic-syntax/scalar-types.md:7 -msgid "`f32`, `f64`" +#: src/control-flow-basics/conditionals.md +msgid "Keywords like `if` and `while` work the same." msgstr "" -#: src/basic-syntax/scalar-types.md:7 -msgid "`3.14`, `-10.0e20`, `2_f32`" +#: src/control-flow-basics/conditionals.md +msgid "Variable assignment is done with `=`, comparison is done with `==`." msgstr "" -#: src/basic-syntax/scalar-types.md:8 -msgid "Strings" +#: src/control-flow-basics/conditionals.md +msgid "`if` expressions" msgstr "" -#: src/basic-syntax/scalar-types.md:8 -msgid "`&str`" +#: src/control-flow-basics/conditionals.md +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/basic-syntax/scalar-types.md:8 -msgid "`\"foo\"`, `\"two\\nlines\"`" +#: src/control-flow-basics/conditionals.md +msgid "\"small\"" msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "Unicode scalar values" +#: src/control-flow-basics/conditionals.md +msgid "\"biggish\"" msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "`char`" +#: src/control-flow-basics/conditionals.md +msgid "\"huge\"" msgstr "" -#: src/basic-syntax/scalar-types.md:9 -msgid "`'a'`, `'α'`, `'∞'`" +#: src/control-flow-basics/conditionals.md +msgid "" +"In addition, you can use `if` as an expression. The last expression of each " +"block becomes the value of the `if` expression:" msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "Booleans" +#: src/control-flow-basics/conditionals.md +msgid "\"large\"" msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "`bool`" +#: src/control-flow-basics/conditionals.md +msgid "\"number size: {}\"" msgstr "" -#: src/basic-syntax/scalar-types.md:10 -msgid "`true`, `false`" +#: src/control-flow-basics/conditionals.md +msgid "" +"Because `if` is an expression and must have a particular type, both of its " +"branch blocks must have the same type. Show what happens if you add `;` " +"after `\"small\"` in the second example." msgstr "" -#: src/basic-syntax/scalar-types.md:12 -msgid "The types have widths as follows:" +#: src/control-flow-basics/conditionals.md +msgid "" +"When `if` is used in an expression, the expression must have a `;` to " +"separate it from the next statement. Remove the `;` before `println!` to see " +"the compiler error." msgstr "" -#: src/basic-syntax/scalar-types.md:14 -msgid "`iN`, `uN`, and `fN` are _N_ bits wide," +#: src/control-flow-basics/loops.md +msgid "There are three looping keywords in Rust: `while`, `loop`, and `for`:" msgstr "" -#: src/basic-syntax/scalar-types.md:15 -msgid "`isize` and `usize` are the width of a pointer," +#: src/control-flow-basics/loops.md +msgid "`while`" msgstr "" -#: src/basic-syntax/scalar-types.md:16 -msgid "`char` is 32 bits wide," +#: src/control-flow-basics/loops.md +msgid "" +"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" +"expr.html#predicate-loops) works much like in other languages, executing the " +"loop body as long as the condition is true." msgstr "" -#: src/basic-syntax/scalar-types.md:17 -msgid "`bool` is 8 bits wide." +#: src/control-flow-basics/loops.md +msgid "\"Final x: {x}\"" msgstr "" -#: src/basic-syntax/scalar-types.md:21 -msgid "There are a few syntaxes which are not shown above:" +#: src/control-flow-basics/loops.md +msgid "`for`" msgstr "" -#: src/basic-syntax/scalar-types.md:23 +#: src/control-flow-basics/loops.md 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:" +"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) iterates " +"over ranges of values:" msgstr "" -#: src/basic-syntax/scalar-types.md:35 -msgid "Byte strings allow you to create a `&[u8]` value directly:" +#: src/control-flow-basics/loops.md +msgid "`loop`" msgstr "" -#: src/basic-syntax/scalar-types.md:45 +#: src/control-flow-basics/loops.md 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`." +"The [`loop` statement](https://doc.rust-lang.org/std/keyword.loop.html) just " +"loops forever, until a `break`." msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "Arrays" +#: src/control-flow-basics/loops.md +msgid "\"{i}\"" msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "`[T; N]`" +#: src/control-flow-basics/loops.md +msgid "" +"We will discuss iteration later; for now, just stick to range expressions." msgstr "" -#: src/basic-syntax/compound-types.md:5 -msgid "`[20, 30, 40]`, `[0; 3]`" +#: src/control-flow-basics/loops.md +msgid "" +"Note that the `for` loop only iterates to `4`. Show the `1..=5` syntax for " +"an inclusive range." msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "Tuples" +#: src/control-flow-basics/break-continue.md +msgid "" +"If you want to exit any kind of loop early, use [`break`](https://doc.rust-" +"lang.org/reference/expressions/loop-expr.html#break-expressions). For " +"`loop`, this can take an optional expression that becomes the value of the " +"`loop` expression." msgstr "" -#: src/basic-syntax/compound-types.md:6 -msgid "`()`, `(T,)`, `(T1, T2)`, ..." +#: src/control-flow-basics/break-continue.md +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/basic-syntax/compound-types.md:6 -msgid "`()`, `('x',)`, `('x', 1.2)`, ..." +#: src/control-flow-basics/break-continue.md +msgid "\"{result}\"" msgstr "" -#: src/basic-syntax/compound-types.md:8 -msgid "Array assignment and access:" +#: src/control-flow-basics/break-continue.md +msgid "" +"Both `continue` and `break` can optionally take a label argument which is " +"used to break out of nested loops:" msgstr "" -#: src/basic-syntax/compound-types.md:19 -msgid "Tuple assignment and access:" +#: src/control-flow-basics/break-continue.md +msgid "\"x: {x}, i: {i}\"" msgstr "" -#: src/basic-syntax/compound-types.md:34 -msgid "Arrays:" +#: src/control-flow-basics/break-continue.md +msgid "" +"In this case we break the outer loop after 3 iterations of the inner loop." msgstr "" -#: src/basic-syntax/compound-types.md:36 +#: src/control-flow-basics/break-continue.md 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." +"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/compound-types.md:40 -msgid "We can use literals to assign values to arrays." -msgstr "" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "Blocks" +msgstr "Bloklar" -#: src/basic-syntax/compound-types.md:42 +#: src/control-flow-basics/blocks-and-scopes.md msgid "" -"The `println!` macro asks for the debug implementation with the `?` format " -"parameter: `{}` gives the default output, `{:?}` gives the debug output. " -"Types such as integers and strings implement the default output, but arrays " -"only implement the debug output. This means that we must use debug output " -"here." +"A block in Rust contains a sequence of expressions, enclosed by braces `{}`. " +"Each block has a value and a type, which are those of the last expression of " +"the block:" msgstr "" -#: src/basic-syntax/compound-types.md:47 -msgid "" -"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " -"easier to read." +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"y: {y}\"" msgstr "" -#: src/basic-syntax/compound-types.md:49 -msgid "Tuples:" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "" +"If the last expression ends with `;`, then the resulting value and type is " +"`()`." msgstr "" -#: src/basic-syntax/compound-types.md:51 -msgid "Like arrays, tuples have a fixed length." -msgstr "" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "Scopes and Shadowing" +msgstr "Kapsamlar (Scopes) ve Gölgeleme (Shadowing)" -#: src/basic-syntax/compound-types.md:53 -msgid "Tuples group together values of different types into a compound type." +#: src/control-flow-basics/blocks-and-scopes.md +msgid "A variable's scope is limited to the enclosing block." msgstr "" -#: src/basic-syntax/compound-types.md:55 +#: src/control-flow-basics/blocks-and-scopes.md msgid "" -"Fields of a tuple can be accessed by the period and the index of the value, " -"e.g. `t.0`, `t.1`." +"You can shadow variables, both those from outer scopes and variables from " +"the same scope:" msgstr "" -#: src/basic-syntax/compound-types.md:57 -msgid "" -"The empty tuple `()` is also known as the \"unit type\". It is both a type, " -"and the only valid value of that type - that is to say both the type and its " -"value are expressed as `()`. It is used to indicate, for example, that a " -"function or expression has no return value, as we'll see in a future slide. " +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"before: {a}\"" 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." +#: src/control-flow-basics/blocks-and-scopes.md src/std-traits/from-and-into.md +#: src/slices-and-lifetimes/solution.md +msgid "\"hello\"" msgstr "" -#: src/basic-syntax/references.md:3 -msgid "Like C++, Rust has references:" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"inner scope: {a}\"" msgstr "" -#: src/basic-syntax/references.md:15 -msgid "Some notes:" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"shadowed in inner scope: {a}\"" msgstr "" -#: src/basic-syntax/references.md:17 -msgid "" -"We must dereference `ref_x` when assigning to it, similar to C and C++ " -"pointers." +#: src/control-flow-basics/blocks-and-scopes.md +msgid "\"after: {a}\"" msgstr "" -#: src/basic-syntax/references.md:18 +#: src/control-flow-basics/blocks-and-scopes.md msgid "" -"Rust will auto-dereference in some cases, in particular when invoking " -"methods (try `ref_x.count_ones()`)." +"You can show how the value of the block changes by changing the last line in " +"the block. For instance, adding/removing a semicolon or using a `return`." msgstr "" -#: src/basic-syntax/references.md:20 +#: src/control-flow-basics/blocks-and-scopes.md msgid "" -"References that are declared as `mut` can be bound to different values over " -"their lifetime." +"Show that a variable's scope is limited by adding a `b` in the inner block " +"in the last example, and then trying to access it outside that block." msgstr "" -#: src/basic-syntax/references.md:26 +#: src/control-flow-basics/blocks-and-scopes.md 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." +"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/references-dangling.md:3 -msgid "Rust will statically forbid dangling references:" +#: src/control-flow-basics/blocks-and-scopes.md +msgid "A shadowing variable can have a different type." msgstr "" -#: src/basic-syntax/references-dangling.md:17 -msgid "A reference is said to \"borrow\" the value it refers to." +#: src/control-flow-basics/blocks-and-scopes.md +msgid "" +"Shadowing looks obscure at first, but is convenient for holding on to values " +"after `.unwrap()`." msgstr "" -#: src/basic-syntax/references-dangling.md:18 +#: src/control-flow-basics/functions.md msgid "" -"Rust is tracking the lifetimes of all references to ensure they live long " -"enough." +"Declaration parameters are followed by a type (the reverse of some " +"programming languages), then a return type." msgstr "" -#: src/basic-syntax/references-dangling.md:20 -msgid "We will talk more about borrowing when we get to ownership." +#: src/control-flow-basics/functions.md +msgid "" +"The last expression in a function body (or any block) becomes the return " +"value. Simply omit the `;` at the end of the expression. The `return` " +"keyword can be used for early return, but the \"bare value\" form is " +"idiomatic at the end of a function (refactor `gcd` to use a `return`)." msgstr "" -#: src/basic-syntax/slices.md:3 -msgid "A slice gives you a view into a larger collection:" +#: src/control-flow-basics/functions.md +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/slices.md:17 -msgid "Slices borrow data from the sliced type." +#: src/control-flow-basics/functions.md +msgid "" +"Overloading is not supported -- each function has a single implementation." msgstr "" -#: src/basic-syntax/slices.md:18 -msgid "Question: What happens if you modify `a[3]` right before printing `s`?" +#: src/control-flow-basics/functions.md +msgid "" +"Always takes a fixed number of parameters. Default arguments are not " +"supported. Macros can be used to support variadic functions." msgstr "" -#: src/basic-syntax/slices.md:22 +#: src/control-flow-basics/functions.md msgid "" -"We create a slice by borrowing `a` and specifying the starting and ending " -"indexes in brackets." +"Always takes a single set of parameter types. These types can be generic, " +"which will be covered later." msgstr "" -#: src/basic-syntax/slices.md:24 +#: src/control-flow-basics/macros.md 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." +"Macros are expanded into Rust code during compilation, and can take a " +"variable number of arguments. They are distinguished by a `!` at the end. " +"The Rust standard library includes an assortment of useful macros." msgstr "" -#: src/basic-syntax/slices.md:26 +#: src/control-flow-basics/macros.md msgid "" -"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " -"identical." +"`println!(format, ..)` prints a line to standard output, applying formatting " +"described in [`std::fmt`](https://doc.rust-lang.org/std/fmt/index.html)." msgstr "" -#: src/basic-syntax/slices.md:28 +#: src/control-flow-basics/macros.md msgid "" -"To easily create a slice of the full array, we can therefore use `&a[..]`." +"`format!(format, ..)` works just like `println!` but returns the result as a " +"string." 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." +#: src/control-flow-basics/macros.md +msgid "`dbg!(expression)` logs the value of the expression and returns it." msgstr "" -#: src/basic-syntax/slices.md:32 +#: src/control-flow-basics/macros.md 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. " +"`todo!()` marks a bit of code as not-yet-implemented. If executed, it will " +"panic." msgstr "" -#: src/basic-syntax/slices.md:34 +#: src/control-flow-basics/macros.md 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." +"`unreachable!()` marks a bit of code as unreachable. If executed, it will " +"panic." msgstr "" -#: src/basic-syntax/string-slices.md:1 -msgid "`String` vs `str`" +#: src/control-flow-basics/macros.md +msgid "\"{n}! = {}\"" msgstr "" -#: src/basic-syntax/string-slices.md:3 -msgid "We can now understand the two string types in Rust:" +#: src/control-flow-basics/macros.md +msgid "" +"The takeaway from this section is that these common conveniences exist, and " +"how to use them. Why they are defined as macros, and what they expand to, is " +"not especially critical." msgstr "" -#: src/basic-syntax/string-slices.md:5 +#: src/control-flow-basics/macros.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1: &str = \"World\";\n" -" println!(\"s1: {s1}\");\n" -"\n" -" let mut s2: String = String::from(\"Hello \");\n" -" println!(\"s2: {s2}\");\n" -" s2.push_str(s1);\n" -" println!(\"s2: {s2}\");\n" -" \n" -" let s3: &str = &s2[6..];\n" -" println!(\"s3: {s3}\");\n" -"}\n" -"```" +"The course does not cover defining macros, but a later section will describe " +"use of derive macros." msgstr "" -#: src/basic-syntax/string-slices.md:20 -msgid "Rust terminology:" +#: src/control-flow-basics/exercise.md +msgid "" +"The [Collatz Sequence](https://en.wikipedia.org/wiki/Collatz_conjecture) is " +"defined as follows, for an arbitrary n" msgstr "" -#: src/basic-syntax/string-slices.md:22 -msgid "`&str` an immutable reference to a string slice." +#: src/control-flow-basics/exercise.md +msgid "1" msgstr "" -#: src/basic-syntax/string-slices.md:23 -msgid "`String` a mutable string buffer." +#: src/control-flow-basics/exercise.md +msgid " greater than zero:" 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." +#: src/control-flow-basics/exercise.md +msgid "If _n" msgstr "" -#: src/basic-syntax/string-slices.md:30 -msgid "" -"Rust’s `String` type is a wrapper around a vector of bytes. As with a " -"`Vec`, it is owned." +#: src/control-flow-basics/exercise.md +msgid "i" 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." +#: src/control-flow-basics/exercise.md +msgid "_ is 1, then the sequence terminates at _n" 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!()`." +#: src/control-flow-basics/exercise.md +msgid "_." msgstr "" -#: src/basic-syntax/string-slices.md:38 -msgid "" -"You can borrow `&str` slices from `String` via `&` and optionally range " -"selection." +#: src/control-flow-basics/exercise.md +msgid "_ is even, then _n" 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)." +#: src/control-flow-basics/exercise.md +msgid "i+1" msgstr "" -#: src/basic-syntax/functions.md:3 -msgid "" -"A Rust version of the famous [FizzBuzz](https://en.wikipedia.org/wiki/" -"Fizz_buzz) interview question:" +#: src/control-flow-basics/exercise.md +msgid " = n" msgstr "" -#: src/basic-syntax/functions.md:36 -msgid "" -"We refer in `main` to a function written below. Neither forward declarations " -"nor headers are necessary. " +#: src/control-flow-basics/exercise.md +msgid " / 2_." 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." +#: src/control-flow-basics/exercise.md +msgid "_ is odd, then _n" msgstr "" -#: src/basic-syntax/functions.md:38 -msgid "" -"The last expression in a function body (or any block) becomes the return " -"value. Simply omit the `;` at the end of the expression." +#: src/control-flow-basics/exercise.md +msgid " = 3 * n" 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." +#: src/control-flow-basics/exercise.md +msgid " + 1_." 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." +#: src/control-flow-basics/exercise.md +msgid "For example, beginning with _n" msgstr "" -#: src/basic-syntax/rustdoc.md:3 -msgid "" -"All language items in Rust can be documented using special `///` syntax." +#: src/control-flow-basics/exercise.md +msgid "_ = 3:" msgstr "" -#: src/basic-syntax/rustdoc.md:5 -msgid "" -"```rust,editable\n" -"/// Determine whether the first argument is divisible by the second " -"argument.\n" -"///\n" -"/// If the second argument is zero, the result is false.\n" -"///\n" -"/// # Example\n" -"/// ```\n" -"/// assert!(is_divisible_by(42, 2));\n" -"/// ```\n" -"fn is_divisible_by(lhs: u32, rhs: u32) -> bool {\n" -" if rhs == 0 {\n" -" return false; // Corner case, early return\n" -" }\n" -" lhs % rhs == 0 // The last expression in a block is the return " -"value\n" -"}\n" -"```" +#: src/control-flow-basics/exercise.md +msgid "3 is odd, so _n" msgstr "" -#: src/basic-syntax/rustdoc.md:22 -msgid "" -"The contents are treated as Markdown. All published Rust library crates are " -"automatically documented at [`docs.rs`](https://docs.rs) using the [rustdoc]" -"(https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is " -"idiomatic to document all public items in an API using this pattern. Code " -"snippets can document usage and will be used as unit tests." +#: src/control-flow-basics/exercise.md +msgid "2" msgstr "" -#: src/basic-syntax/rustdoc.md:30 -msgid "" -"Show students the generated docs for the `rand` crate at [`docs.rs/rand`]" -"(https://docs.rs/rand)." +#: src/control-flow-basics/exercise.md +msgid "_ = 3 * 3 + 1 = 10;" msgstr "" -#: src/basic-syntax/rustdoc.md:33 -msgid "" -"This course does not include rustdoc on slides, just to save space, but in " -"real code they should be present." +#: src/control-flow-basics/exercise.md +msgid "10 is even, so _n" msgstr "" -#: src/basic-syntax/rustdoc.md:36 -msgid "" -"Inner doc comments are discussed later (in the page on modules) and need not " -"be addressed here." +#: src/control-flow-basics/exercise.md src/bare-metal/aps/better-uart.md +msgid "3" msgstr "" -#: src/basic-syntax/rustdoc.md:39 -msgid "" -"Rustdoc comments can contain code snippets that we can run and test using " -"`cargo test`. We will discuss these tests in the [Testing section](../" -"testing/doc-tests.html)." +#: src/control-flow-basics/exercise.md +msgid "_ = 10 / 2 = 5;" msgstr "" -#: src/basic-syntax/methods.md:3 -msgid "" -"Methods are functions associated with a type. The `self` argument of a " -"method is an instance of the type it is associated with:" +#: src/control-flow-basics/exercise.md +msgid "5 is odd, so _n" msgstr "" -#: src/basic-syntax/methods.md:6 -msgid "" -"```rust,editable\n" -"struct Rectangle {\n" -" width: u32,\n" -" height: u32,\n" -"}\n" -"\n" -"impl Rectangle {\n" -" fn area(&self) -> u32 {\n" -" self.width * self.height\n" -" }\n" -"\n" -" fn inc_width(&mut self, delta: u32) {\n" -" self.width += delta;\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut rect = Rectangle { width: 10, height: 5 };\n" -" println!(\"old area: {}\", rect.area());\n" -" rect.inc_width(5);\n" -" println!(\"new area: {}\", rect.area());\n" -"}\n" -"```" +#: src/control-flow-basics/exercise.md src/bare-metal/aps/better-uart.md +msgid "4" msgstr "" -#: src/basic-syntax/methods.md:30 -msgid "" -"We will look much more at methods in today's exercise and in tomorrow's " -"class." +#: src/control-flow-basics/exercise.md +msgid "_ = 3 * 5 + 1 = 16;" msgstr "" -#: src/basic-syntax/methods.md:34 -msgid "Add a static method called `Rectangle::new` and call this from `main`:" +#: src/control-flow-basics/exercise.md +msgid "16 is even, so _n" msgstr "" -#: src/basic-syntax/methods.md:42 -msgid "" -"While _technically_, Rust does not have custom constructors, static methods " -"are commonly used to initialize structs (but don't have to). The actual " -"constructor, `Rectangle { width, height }`, could be called directly. See " -"the [Rustnomicon](https://doc.rust-lang.org/nomicon/constructors.html)." +#: src/control-flow-basics/exercise.md +msgid "5" msgstr "" -#: src/basic-syntax/methods.md:45 -msgid "" -"Add a `Rectangle::square(width: u32)` constructor to illustrate that such " -"static methods can take arbitrary parameters." +#: src/control-flow-basics/exercise.md +msgid "_ = 16 / 2 = 8;" msgstr "" -#: src/basic-syntax/functions-interlude.md:1 -msgid "Function Overloading" +#: src/control-flow-basics/exercise.md +msgid "8 is even, so _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:3 -msgid "Overloading is not supported:" +#: src/control-flow-basics/exercise.md src/bare-metal/aps/better-uart.md +msgid "6" msgstr "" -#: src/basic-syntax/functions-interlude.md:5 -msgid "Each function has a single implementation:" +#: src/control-flow-basics/exercise.md +msgid "_ = 8 / 2 = 4;" msgstr "" -#: src/basic-syntax/functions-interlude.md:6 -msgid "Always takes a fixed number of parameters." +#: src/control-flow-basics/exercise.md +msgid "4 is even, so _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:7 -msgid "Always takes a single set of parameter types." +#: src/control-flow-basics/exercise.md +msgid "7" msgstr "" -#: src/basic-syntax/functions-interlude.md:8 -msgid "Default values are not supported:" +#: src/control-flow-basics/exercise.md +msgid "_ = 4 / 2 = 2;" msgstr "" -#: src/basic-syntax/functions-interlude.md:9 -msgid "All call sites have the same number of arguments." +#: src/control-flow-basics/exercise.md +msgid "2 is even, so _n" msgstr "" -#: src/basic-syntax/functions-interlude.md:10 -msgid "Macros are sometimes used as an alternative." +#: src/control-flow-basics/exercise.md src/bare-metal/aps/better-uart.md +msgid "8" msgstr "" -#: src/basic-syntax/functions-interlude.md:12 -msgid "However, function parameters can be generic:" +#: src/control-flow-basics/exercise.md +msgid "_ = 1; and" msgstr "" -#: src/basic-syntax/functions-interlude.md:14 -msgid "" -"```rust,editable\n" -"fn pick_one(a: T, b: T) -> T {\n" -" if std::process::id() % 2 == 0 { a } else { b }\n" -"}\n" -"\n" -"fn main() {\n" -" println!(\"coin toss: {}\", pick_one(\"heads\", \"tails\"));\n" -" println!(\"cash prize: {}\", pick_one(500, 1000));\n" -"}\n" -"```" +#: src/control-flow-basics/exercise.md +msgid "the sequence terminates." msgstr "" -#: src/basic-syntax/functions-interlude.md:27 +#: src/control-flow-basics/exercise.md 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." +"Write a function to calculate the length of the collatz sequence for a given " +"initial `n`." msgstr "" -#: src/exercises/day-1/morning.md:1 -msgid "Day 1: Morning Exercises" +#: src/control-flow-basics/exercise.md src/control-flow-basics/solution.md +msgid "/// Determine the length of the collatz sequence beginning at `n`.\n" msgstr "" -#: src/exercises/day-1/morning.md:3 -msgid "In these exercises, we will explore two parts of Rust:" +#: src/control-flow-basics/solution.md src/concurrency/scoped-threads.md +msgid "\"Length: {}\"" msgstr "" -#: src/exercises/day-1/morning.md:5 -msgid "Implicit conversions between types." -msgstr "" +#: src/welcome-day-1-afternoon.md src/welcome-day-2-afternoon.md +#: src/welcome-day-3-afternoon.md src/welcome-day-4-afternoon.md +#, fuzzy +msgid "Welcome Back" +msgstr "Hoşgeldiniz" -#: src/exercises/day-1/morning.md:7 -msgid "Arrays and `for` loops." +#: src/welcome-day-1-afternoon.md +msgid "[Tuples and Arrays](./tuples-and-arrays.md) (1 hour)" msgstr "" -#: src/exercises/day-1/morning.md:11 -msgid "A few things to consider while solving the exercises:" +#: src/welcome-day-1-afternoon.md +msgid "[References](./references.md) (50 minutes)" msgstr "" -#: src/exercises/day-1/morning.md:13 -msgid "" -"Use a local Rust installation, if possible. This way you can get auto-" -"completion in your editor. See the page about [Using Cargo](../../cargo.md) " -"for details on installing Rust." +#: src/welcome-day-1-afternoon.md +msgid "[User-Defined Types](./user-defined-types.md) (50 minutes)" msgstr "" -#: src/exercises/day-1/morning.md:17 -msgid "Alternatively, use the Rust Playground." +#: src/welcome-day-1-afternoon.md +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 55 " +"minutes" msgstr "" -#: src/exercises/day-1/morning.md:19 +#: src/tuples-and-arrays.md msgid "" -"The code snippets are not editable on purpose: the inline code snippets lose " -"their state if you navigate away from the page." +"[Tuples and Arrays](./tuples-and-arrays/tuples-and-arrays.md) (10 minutes)" msgstr "" -#: src/exercises/day-1/morning.md:22 src/exercises/day-2/morning.md:11 -#: src/exercises/day-3/morning.md:9 src/exercises/bare-metal/morning.md:7 -#: src/exercises/concurrency/morning.md:12 -msgid "" -"After looking at the exercises, you can look at the [solutions](solutions-" -"morning.md) provided." +#: src/tuples-and-arrays.md +msgid "[Array Iteration](./tuples-and-arrays/iteration.md) (3 minutes)" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:3 -msgid "" -"Rust will not automatically apply _implicit conversions_ between types " -"([unlike C++](https://en.cppreference.com/w/cpp/language/" -"implicit_conversion)). You can see this in a program like this:" +#: src/tuples-and-arrays.md +msgid "[Pattern Matching](./tuples-and-arrays/match.md) (10 minutes)" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:20 -msgid "" -"The Rust integer types all implement the [`From`](https://doc.rust-lang." -"org/std/convert/trait.From.html) and [`Into`](https://doc.rust-lang.org/" -"std/convert/trait.Into.html) traits to let us convert between them. The " -"`From` trait has a single `from()` method and similarly, the `Into` " -"trait has a single `into()` method. Implementing these traits is how a type " -"expresses that it can be converted into another type." +#: src/tuples-and-arrays.md +msgid "[Destructuring](./tuples-and-arrays/destructuring.md) (5 minutes)" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:26 -msgid "" -"The standard library has an implementation of `From for i16`, which " -"means that we can convert a variable `x` of type `i8` to an `i16` by " -"calling `i16::from(x)`. Or, simpler, with `x.into()`, because `From for " -"i16` implementation automatically create an implementation of `Into for " -"i8`." +#: src/tuples-and-arrays.md +msgid "[Exercise: Nested Arrays](./tuples-and-arrays/exercise.md) (30 minutes)" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:31 +#: src/tuples-and-arrays/tuples-and-arrays.md 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." +"Tuples and arrays are the first \"compound\" types we have seen. All " +"elements of an array have the same type, while tuples can accommodate " +"different types. Both types have a size fixed at compile time." msgstr "" -#: src/exercises/day-1/implicit-conversions.md:34 -msgid "Execute the above program and look at the compiler error." +#: src/tuples-and-arrays/tuples-and-arrays.md +#: src/tuples-and-arrays/destructuring.md +msgid "Arrays" msgstr "" -#: src/exercises/day-1/implicit-conversions.md:36 -msgid "Update the code above to use `into()` to do the conversion." +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "`[T; N]`" 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" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "`[20, 30, 40]`, `[0; 3]`" msgstr "" -#: src/exercises/day-1/for-loops.md:3 -msgid "We saw that an array can be declared like this:" +#: src/tuples-and-arrays/tuples-and-arrays.md +#: src/tuples-and-arrays/destructuring.md +msgid "Tuples" msgstr "" -#: src/exercises/day-1/for-loops.md:9 -msgid "" -"You can print such an array by asking for its debug representation with `{:?}" -"`:" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "`()`, `(T,)`, `(T1, T2)`, ..." msgstr "" -#: src/exercises/day-1/for-loops.md:19 -msgid "" -"Rust lets you iterate over things like arrays and ranges using the `for` " -"keyword:" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "`()`, `('x',)`, `('x', 1.2)`, ..." msgstr "" -#: src/exercises/day-1/for-loops.md:22 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let array = [10, 20, 30];\n" -" print!(\"Iterating over array:\");\n" -" for n in &array {\n" -" print!(\" {n}\");\n" -" }\n" -" println!();\n" -"\n" -" print!(\"Iterating over range:\");\n" -" for i in 0..3 {\n" -" print!(\" {}\", array[i]);\n" -" }\n" -" println!();\n" -"}\n" -"```" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Array assignment and access:" 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):" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Tuple assignment and access:" msgstr "" -#: src/exercises/day-1/for-loops.md:49 -msgid "Hard-code both functions to operate on 3 × 3 matrices." +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Arrays:" msgstr "" -#: src/exercises/day-1/for-loops.md:51 +#: src/tuples-and-arrays/tuples-and-arrays.md msgid "" -"Copy the code below to and implement the " -"functions:" +"A value of the array type `[T; N]` holds `N` (a compile-time constant) " +"elements of the same type `T`. Note that the length of the array is _part of " +"its type_, which means that `[u8; 3]` and `[u8; 4]` are considered two " +"different types. Slices, which have a size determined at runtime, are " +"covered later." msgstr "" -#: src/exercises/day-1/for-loops.md:54 +#: src/tuples-and-arrays/tuples-and-arrays.md msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" -" unimplemented!()\n" -"}\n" -"\n" -"fn main() {\n" -" let matrix = [\n" -" [101, 102, 103], // <-- the comment makes rustfmt add a newline\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -"\n" -" println!(\"matrix:\");\n" -" pretty_print(&matrix);\n" -"\n" -" let transposed = transpose(matrix);\n" -" println!(\"transposed:\");\n" -" pretty_print(&transposed);\n" -"}\n" -"```" +"Try accessing an out-of-bounds array element. Array accesses are checked at " +"runtime. Rust can usually optimize these checks away, and they can be " +"avoided using unsafe Rust." msgstr "" -#: src/exercises/day-1/for-loops.md: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?" +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "We can use literals to assign values to arrays." msgstr "" -#: src/exercises/day-1/for-loops.md:89 +#: src/tuples-and-arrays/tuples-and-arrays.md msgid "" -"See the [`ndarray` crate](https://docs.rs/ndarray/) for a production quality " -"implementation." +"The `println!` macro asks for the debug implementation with the `?` format " +"parameter: `{}` gives the default output, `{:?}` gives the debug output. " +"Types such as integers and strings implement the default output, but arrays " +"only implement the debug output. This means that we must use debug output " +"here." msgstr "" -#: src/exercises/day-1/for-loops.md:94 +#: src/tuples-and-arrays/tuples-and-arrays.md msgid "" -"The solution and the answer to the bonus section are available in the " -"[Solution](solutions-morning.md#arrays-and-for-loops) section." +"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " +"easier to read." 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." +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Tuples:" msgstr "" -#: src/exercises/day-1/for-loops.md:100 -msgid "Without the `&`..." +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Like arrays, tuples have a fixed length." msgstr "" -#: src/exercises/day-1/for-loops.md:101 -msgid "" -"The loop would have been one that consumes the array. This is a change " -"[introduced in the 2021 Edition](https://doc.rust-lang.org/edition-guide/" -"rust-2021/IntoIterator-for-arrays.html)." +#: src/tuples-and-arrays/tuples-and-arrays.md +msgid "Tuples group together values of different types into a compound type." msgstr "" -#: src/exercises/day-1/for-loops.md:104 +#: src/tuples-and-arrays/tuples-and-arrays.md msgid "" -"An implicit array copy would have occurred. Since `i32` is a copy type, " -"then `[i32; 3]` is also a copy type." +"Fields of a tuple can be accessed by the period and the index of the value, " +"e.g. `t.0`, `t.1`." msgstr "" -#: src/control-flow.md:3 +#: src/tuples-and-arrays/tuples-and-arrays.md 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." +"The empty tuple `()` is also known as the \"unit type\". It is both a type, " +"and the only valid value of that type --- that is to say both the type and " +"its value are expressed as `()`. It is used to indicate, for example, that a " +"function or expression has no return value, as we'll see in a future slide." msgstr "" -#: src/control-flow/blocks.md:3 +#: src/tuples-and-arrays/tuples-and-arrays.md 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:" +"You can think of it as `void` that can be familiar to you from other " +"programming languages." msgstr "" -#: src/control-flow/blocks.md:27 -msgid "" -"If the last expression ends with `;`, then the resulting value and type is " -"`()`." +#: src/tuples-and-arrays/iteration.md +msgid "The `for` statement supports iterating over arrays (but not tuples)." msgstr "" -#: src/control-flow/blocks.md:29 +#: src/tuples-and-arrays/iteration.md msgid "" -"The same rule is used for functions: the value of the function body is the " -"return value:" +"This functionality uses the `IntoIterator` trait, but we haven't covered " +"that yet." 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 +#: src/tuples-and-arrays/iteration.md msgid "" -"The point of this slide is to show that blocks have a type and value in " -"Rust. " +"The `assert_ne!` macro is new here. There are also `assert_eq!` and `assert!" +"` macros. These are always checked while, debug-only variants like " +"`debug_assert!` compile to nothing in release builds." msgstr "" -#: src/control-flow/blocks.md:47 +#: src/tuples-and-arrays/match.md 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`." +"The `match` keyword lets you match a value against one or more _patterns_. " +"The comparisons are done from top to bottom and the first match wins." msgstr "" -#: src/control-flow/if-expressions.md:1 -msgid "`if` expressions" +#: src/tuples-and-arrays/match.md +msgid "The patterns can be simple values, similarly to `switch` in C and C++:" msgstr "" -#: src/control-flow/if-expressions.md:3 -msgid "" -"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" -"if-expr.html#if-expressions) exactly like `if` statements in other languages:" +#: src/tuples-and-arrays/match.md +msgid "'x'" 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:" +#: src/tuples-and-arrays/match.md +msgid "'q'" 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." +#: src/tuples-and-arrays/match.md +msgid "\"Quitting\"" msgstr "" -#: src/control-flow/for-expressions.md:1 -msgid "`for` loops" +#: src/tuples-and-arrays/match.md src/std-traits/solution.md +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "'a'" 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:" +#: src/tuples-and-arrays/match.md +msgid "'s'" msgstr "" -#: src/control-flow/for-expressions.md:22 -msgid "You can use `break` and `continue` here as usual." +#: src/tuples-and-arrays/match.md +msgid "'w'" msgstr "" -#: src/control-flow/for-expressions.md:26 -msgid "Index iteration is not a special syntax in Rust for just that case." +#: src/tuples-and-arrays/match.md +msgid "'d'" msgstr "" -#: src/control-flow/for-expressions.md:27 -msgid "`(0..10)` is a range that implements an `Iterator` trait. " +#: src/tuples-and-arrays/match.md +msgid "\"Moving around\"" msgstr "" -#: src/control-flow/for-expressions.md:28 -msgid "" -"`step_by` is a method that returns another `Iterator` that skips every other " -"element. " +#: src/tuples-and-arrays/match.md src/error-handling/exercise.md +#: src/error-handling/solution.md +msgid "'0'" msgstr "" -#: src/control-flow/for-expressions.md:29 -msgid "" -"Modify the elements in the vector and explain the compiler errors. Change " -"vector `v` to be mutable and the for loop to `for x in v.iter_mut()`." +#: src/tuples-and-arrays/match.md src/error-handling/exercise.md +#: src/error-handling/solution.md +msgid "'9'" msgstr "" -#: src/control-flow/while-expressions.md:1 -msgid "`while` loops" +#: src/tuples-and-arrays/match.md +msgid "\"Number input\"" msgstr "" -#: src/control-flow/while-expressions.md:3 -msgid "" -"The [`while` keyword](https://doc.rust-lang.org/reference/expressions/loop-" -"expr.html#predicate-loops) works very similar to other languages:" +#: src/tuples-and-arrays/match.md +msgid "\"Lowercase: {key}\"" msgstr "" -#: src/control-flow/break-continue.md:1 -msgid "`break` and `continue`" +#: src/tuples-and-arrays/match.md +msgid "\"Something else\"" msgstr "" -#: src/control-flow/break-continue.md:3 +#: src/tuples-and-arrays/match.md msgid "" -"If you want to exit a loop early, use [`break`](https://doc.rust-lang.org/" -"reference/expressions/loop-expr.html#break-expressions)," +"The `_` pattern is a wildcard pattern which matches any value. The " +"expressions _must_ be irrefutable, meaning that it covers every possibility, " +"so `_` is often used as the final catch-all case." msgstr "" -#: src/control-flow/break-continue.md:4 +#: src/tuples-and-arrays/match.md msgid "" -"If you want to immediately start the next iteration use [`continue`](https://" -"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." +"Match can be used as an expression. Just like `if`, each match arm must have " +"the same type. The type is the last expression of the block, if any. In the " +"example above, the type is `()`." msgstr "" -#: src/control-flow/break-continue.md:7 +#: src/tuples-and-arrays/match.md msgid "" -"Both `continue` and `break` can optionally take a label argument which is " -"used to break out of nested loops:" +"A variable in the pattern (`key` in this example) will create a binding that " +"can be used within the match arm." msgstr "" -#: src/control-flow/break-continue.md:29 -msgid "" -"In this case we break the outer loop after 3 iterations of the inner loop." +#: src/tuples-and-arrays/match.md +msgid "A match guard causes the arm to match only if the condition is true." msgstr "" -#: src/control-flow/loop-expressions.md:1 -msgid "`loop` expressions" +#: src/tuples-and-arrays/match.md src/user-defined-types/named-structs.md +#: src/user-defined-types/enums.md src/methods-and-traits/methods.md +msgid "Key Points:" msgstr "" -#: src/control-flow/loop-expressions.md:3 +#: src/tuples-and-arrays/match.md msgid "" -"Finally, there is a [`loop` keyword](https://doc.rust-lang.org/reference/" -"expressions/loop-expr.html#infinite-loops) which creates an endless loop." +"You might point out how some specific characters are being used when in a " +"pattern" msgstr "" -#: src/control-flow/loop-expressions.md:6 -msgid "Here you must either `break` or `return` to stop the loop:" +#: src/tuples-and-arrays/match.md +msgid "`|` as an `or`" msgstr "" -#: src/control-flow/loop-expressions.md:28 -msgid "Break the `loop` with a value (e.g. `break 8`) and print it out." +#: src/tuples-and-arrays/match.md +msgid "`..` can expand as much as it needs to be" msgstr "" -#: src/control-flow/loop-expressions.md:29 -msgid "" -"Note that `loop` is the only looping construct which returns a non-trivial " -"value. This is because it's guaranteed to be entered at least once (unlike " -"`while` and `for` loops)." +#: src/tuples-and-arrays/match.md +msgid "`1..=5` represents an inclusive range" msgstr "" -#: src/basic-syntax/variables.md:3 -msgid "" -"Rust provides type safety via static typing. Variable bindings are immutable " -"by default:" +#: src/tuples-and-arrays/match.md +msgid "`_` is a wild card" msgstr "" -#: src/basic-syntax/variables.md:18 +#: src/tuples-and-arrays/match.md msgid "" -"Due to type inference the `i32` is optional. We will gradually show the " -"types less and less as the course progresses." +"Match guards as a separate syntax feature are important and necessary when " +"we wish to concisely express more complex ideas than patterns alone would " +"allow." msgstr "" -#: src/basic-syntax/type-inference.md:3 -msgid "Rust will look at how the variable is _used_ to determine the type:" +#: src/tuples-and-arrays/match.md +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/basic-syntax/type-inference.md:27 +#: src/tuples-and-arrays/match.md msgid "" -"This slide demonstrates how the Rust compiler infers types based on " -"constraints given by variable declarations and usages." +"The condition defined in the guard applies to every expression in a pattern " +"with an `|`." msgstr "" -#: src/basic-syntax/type-inference.md:29 +#: src/tuples-and-arrays/destructuring.md 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." +"Destructuring is a way of extracting data from a data structure by writing a " +"pattern that is matched up to the data structure, binding variables to " +"subcomponents of the data structure." msgstr "" -#: src/basic-syntax/type-inference.md:33 -msgid "" -"The following code tells the compiler to copy into a certain generic " -"container without the code ever explicitly specifying the contained type, " -"using `_` as a placeholder:" +#: src/tuples-and-arrays/destructuring.md +msgid "You can destructure tuples and arrays by matching on their elements:" msgstr "" -#: src/basic-syntax/type-inference.md:48 -msgid "" -"[`collect`](https://doc.rust-lang.org/stable/std/iter/trait.Iterator." -"html#method.collect) relies on [`FromIterator`](https://doc.rust-lang.org/" -"std/iter/trait.FromIterator.html), which [`HashSet`](https://doc.rust-lang." -"org/std/collections/struct.HashSet.html#impl-FromIterator%3CT%3E-for-" -"HashSet%3CT,+S%3E) implements." +#: src/tuples-and-arrays/destructuring.md +msgid "\"on Y axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:1 -msgid "Static and Constant Variables" +#: src/tuples-and-arrays/destructuring.md +msgid "\"on X axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:3 -msgid "" -"Static and constant variables are two different ways to create globally-" -"scoped values that cannot be moved or reallocated during the execution of " -"the program. " +#: src/tuples-and-arrays/destructuring.md +msgid "\"left of Y axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:6 -msgid "`const`" +#: src/tuples-and-arrays/destructuring.md +msgid "\"below X axis\"" msgstr "" -#: src/basic-syntax/static-and-const.md:8 -msgid "" -"Constant variables are evaluated at compile time and their values are " -"inlined wherever they are used:" +#: src/tuples-and-arrays/destructuring.md +msgid "\"first quadrant\"" msgstr "" -#: src/basic-syntax/static-and-const.md:30 -msgid "" -"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html) these are inlined upon use." +#: src/tuples-and-arrays/destructuring.md +msgid "\"Tell me about {triple:?}\"" msgstr "" -#: src/basic-syntax/static-and-const.md:32 -msgid "" -"Only functions marked `const` can be called at compile time to generate " -"`const` values. `const` functions can however be called at runtime." +#: src/tuples-and-arrays/destructuring.md +msgid "\"First is 0, y = {y}, and z = {z}\"" msgstr "" -#: src/basic-syntax/static-and-const.md:34 -msgid "`static`" +#: src/tuples-and-arrays/destructuring.md +msgid "\"First is 1 and the rest were ignored\"" 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:" +#: src/tuples-and-arrays/destructuring.md +msgid "\"All elements were ignored\"" msgstr "" -#: src/basic-syntax/static-and-const.md:38 -msgid "" -"```rust,editable\n" -"static BANNER: &str = \"Welcome to RustOS 3.14\";\n" -"\n" -"fn main() {\n" -" println!(\"{BANNER}\");\n" -"}\n" -"```" +#: src/tuples-and-arrays/destructuring.md +msgid "Create a new array pattern using `_` to represent an element." msgstr "" -#: src/basic-syntax/static-and-const.md:46 -msgid "" -"As noted in the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" -"vs-static.html), these are not inlined upon use and have an actual " -"associated memory location. This is useful for unsafe and embedded code, " -"and the variable lives through the entirety of the program execution. When a " -"globally-scoped value does not have a reason to need object identity, " -"`const` is generally preferred." +#: src/tuples-and-arrays/destructuring.md +msgid "Add more values to the array." msgstr "" -#: src/basic-syntax/static-and-const.md:50 +#: src/tuples-and-arrays/destructuring.md 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." +"Point out that how `..` will expand to account for different number of " +"elements." msgstr "" -#: src/basic-syntax/static-and-const.md:58 -msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." +#: src/tuples-and-arrays/destructuring.md +msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" 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++." +#: src/tuples-and-arrays/exercise.md +msgid "Arrays can contain other arrays:" msgstr "" -#: src/basic-syntax/static-and-const.md:60 -msgid "" -"`static` provides object identity: an address in memory and state as " -"required by types with interior mutability such as `Mutex`." +#: src/tuples-and-arrays/exercise.md +msgid "What is the type of this variable?" msgstr "" -#: src/basic-syntax/static-and-const.md:61 +#: src/tuples-and-arrays/exercise.md 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`." +"Use an array such as the above to write a function `transpose` which will " +"transpose a matrix (turn rows into columns):" msgstr "" -#: src/basic-syntax/static-and-const.md:64 -msgid "Properties table:" +#: src/tuples-and-arrays/exercise.md +msgid "Hard-code both functions to operate on 3 × 3 matrices." msgstr "" -#: src/basic-syntax/static-and-const.md:66 -msgid "Property" +#: src/tuples-and-arrays/exercise.md +msgid "" +"Copy the code below to and implement the " +"functions:" msgstr "" -#: src/basic-syntax/static-and-const.md:66 -msgid "Static" +#: src/tuples-and-arrays/exercise.md src/borrowing/exercise.md +#: src/unsafe-rust/exercise.md +msgid "// TODO: remove this when you're done with your implementation.\n" msgstr "" -#: src/basic-syntax/static-and-const.md:66 -msgid "Constant" +#: src/tuples-and-arrays/exercise.md src/tuples-and-arrays/solution.md +msgid "// <-- the comment makes rustfmt add a newline\n" msgstr "" -#: src/basic-syntax/static-and-const.md:68 -msgid "Has an address in memory" +#: src/tuples-and-arrays/exercise.md src/tuples-and-arrays/solution.md +msgid "\"matrix: {:#?}\"" msgstr "" -#: 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" +#: src/tuples-and-arrays/exercise.md src/tuples-and-arrays/solution.md +msgid "\"transposed: {:#?}\"" msgstr "" -#: src/basic-syntax/static-and-const.md:68 -msgid "No (inlined)" +#: src/tuples-and-arrays/solution.md +msgid "//\n" msgstr "" -#: src/basic-syntax/static-and-const.md:69 -msgid "Lives for the entire duration of the program" +#: src/references.md +msgid "[Shared References](./references/shared.md) (10 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:69 -#: src/basic-syntax/static-and-const.md:70 -#: src/basic-syntax/static-and-const.md:72 -msgid "No" +#: src/references.md +msgid "[Exclusive References](./references/exclusive.md) (10 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:70 -msgid "Can be mutable" +#: src/references.md +msgid "[Exercise: Geometry](./references/exercise.md) (30 minutes)" msgstr "" -#: src/basic-syntax/static-and-const.md:70 -msgid "Yes (unsafe)" +#: src/references.md src/user-defined-types.md src/pattern-matching.md +msgid "This segment should take about 50 minutes" msgstr "" -#: src/basic-syntax/static-and-const.md:71 -msgid "Evaluated at compile time" +#: src/references/shared.md +msgid "" +"A reference provides a way to access another value without taking " +"responsibility for the value, and is also called \"borrowing\". Shared " +"references are read-only, and the referenced data cannot change." msgstr "" -#: src/basic-syntax/static-and-const.md:71 -msgid "Yes (initialised at compile time)" +#: src/references/shared.md +msgid "" +"A shared reference to a type `T` has type `&T`. A reference value is made " +"with the `&` operator. The `*` operator \"dereferences\" a reference, " +"yielding its value." msgstr "" -#: src/basic-syntax/static-and-const.md:72 -msgid "Inlined wherever it is used" +#: src/references/shared.md +msgid "Rust will statically forbid dangling references:" msgstr "" -#: src/basic-syntax/scopes-shadowing.md:3 +#: src/references/shared.md msgid "" -"You can shadow variables, both those from outer scopes and variables from " -"the same scope:" +"A reference is said to \"borrow\" the value it refers to, and this is a good " +"model for students not familiar with pointers: code can use the reference to " +"access the value, but is still \"owned\" by the original variable. The " +"course will get into more detail on ownership in day 3." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:6 +#: src/references/shared.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let a = 10;\n" -" println!(\"before: {a}\");\n" -"\n" -" {\n" -" let a = \"hello\";\n" -" println!(\"inner scope: {a}\");\n" -"\n" -" let a = true;\n" -" println!(\"shadowed in inner scope: {a}\");\n" -" }\n" -"\n" -" println!(\"after: {a}\");\n" -"}\n" -"```" +"References are implemented as pointers, and a key advantage is that they can " +"be much smaller than the thing they point to. Students familiar with C or C+" +"+ will recognize references as pointers. Later parts of the course will " +"cover how Rust prevents the memory-safety bugs that come from using raw " +"pointers." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:25 +#: src/references/shared.md 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. " +"Rust does not automatically create references for you - the `&` is always " +"required." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:27 +#: src/references/shared.md msgid "" -"Shadowing looks obscure at first, but is convenient for holding on to values " -"after `.unwrap()`." +"Rust will auto-dereference in some cases, in particular when invoking " +"methods (try `r.count_ones()`). There is no need for an `->` operator like " +"in C++." msgstr "" -#: src/basic-syntax/scopes-shadowing.md:28 +#: src/references/shared.md 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." +"In this example, `r` is mutable so that it can be reassigned (`r = &b`). " +"Note that this re-binds `r`, so that it refers to something else. This is " +"different from C++, where assignment to a reference changes the referenced " +"value." msgstr "" -#: src/enums.md:3 +#: src/references/shared.md msgid "" -"The `enum` keyword allows the creation of a type which has a few different " -"variants:" +"A shared reference does not allow modifying the value it refers to, even if " +"that value was mutable. Try `*r = 'X'`." msgstr "" -#: src/enums.md:6 +#: src/references/shared.md msgid "" -"```rust,editable\n" -"fn generate_random_number() -> i32 {\n" -" // Implementation based on https://xkcd.com/221/\n" -" 4 // Chosen by fair dice roll. Guaranteed to be random.\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"enum CoinFlip {\n" -" Heads,\n" -" Tails,\n" -"}\n" -"\n" -"fn flip_coin() -> CoinFlip {\n" -" let random_number = generate_random_number();\n" -" if random_number % 2 == 0 {\n" -" return CoinFlip::Heads;\n" -" } else {\n" -" return CoinFlip::Tails;\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" println!(\"You got: {:?}\", flip_coin());\n" -"}\n" -"```" +"Rust is tracking the lifetimes of all references to ensure they live long " +"enough. Dangling references cannot occur in safe Rust. `x_axis` would return " +"a reference to `point`, but `point` will be deallocated when the function " +"returns, so this will not compile." msgstr "" -#: src/enums.md:36 -msgid "Enumerations allow you to collect a set of values under one type" +#: src/references/shared.md +msgid "We will talk more about borrowing when we get to ownership." msgstr "" -#: src/enums.md:37 +#: src/references/exclusive.md 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:" +"Exclusive references, also known as mutable references, allow changing the " +"value they refer to. They have type `&mut T`." msgstr "" -#: src/enums.md:39 +#: src/references/exclusive.md 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." +"\"Exclusive\" means that only this reference can be used to access the " +"value. No other references (shared or exclusive) can exist at the same time, " +"and the referenced value cannot be accessed while the exclusive reference " +"exists. Try making an `&point.0` or changing `point.0` while `x_coord` is " +"alive." msgstr "" -#: src/enums.md:41 +#: src/references/exclusive.md 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. " +"Be sure to note the difference between `let mut x_coord: &i32` and `let " +"x_coord: &mut i32`. The first one represents a shared reference which can be " +"bound to different values, while the second represents an exclusive " +"reference to a mutable value." msgstr "" -#: src/enums/variant-payloads.md:3 +#: src/references/exercise.md 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:" +"We will create a few utility functions for 3-dimensional geometry, " +"representing a point as `[f64;3]`. It is up to you to determine the function " +"signatures." msgstr "" -#: src/enums/variant-payloads.md:6 +#: src/references/exercise.md msgid "" -"```rust,editable\n" -"enum WebEvent {\n" -" PageLoad, // Variant without payload\n" -" KeyPress(char), // Tuple struct variant\n" -" Click { x: i64, y: i64 }, // Full struct variant\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(event: WebEvent) {\n" -" match event {\n" -" WebEvent::PageLoad => println!(\"page loaded\"),\n" -" WebEvent::KeyPress(c) => println!(\"pressed '{c}'\"),\n" -" WebEvent::Click { x, y } => println!(\"clicked at x={x}, y={y}\"),\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let load = WebEvent::PageLoad;\n" -" let press = WebEvent::KeyPress('x');\n" -" let click = WebEvent::Click { x: 20, y: 80 };\n" -"\n" -" inspect(load);\n" -" inspect(press);\n" -" inspect(click);\n" -"}\n" -"```" +"// Calculate the magnitude of a vector by summing the squares of its " +"coordinates\n" +"// and taking the square root. Use the `sqrt()` method to calculate the " +"square\n" +"// root, like `v.sqrt()`.\n" msgstr "" -#: src/enums/variant-payloads.md:35 +#: src/references/exercise.md 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 `=>`." +"// Normalize a vector by calculating its magnitude and dividing all of its\n" +"// coordinates by that magnitude.\n" 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++." +#: src/references/exercise.md +msgid "// Use the following `main` to test your work.\n" msgstr "" -#: src/enums/variant-payloads.md:37 -msgid "" -"The match expression has a value. The value is the last expression in the " -"match arm which was executed." +#: src/references/exercise.md src/references/solution.md +msgid "\"Magnitude of a unit vector: {}\"" msgstr "" -#: src/enums/variant-payloads.md:38 -msgid "" -"Starting from the top we look for what pattern matches the value then run " -"the code following the arrow. Once we find a match, we stop. " +#: src/references/exercise.md src/references/solution.md +msgid "\"Magnitude of {v:?}: {}\"" msgstr "" -#: src/enums/variant-payloads.md:39 -msgid "" -"Demonstrate what happens when the search is inexhaustive. Note the advantage " -"the Rust compiler provides by confirming when all cases are handled. " +#: src/references/exercise.md src/references/solution.md +msgid "\"Magnitude of {v:?} after normalization: {}\"" msgstr "" -#: src/enums/variant-payloads.md:40 -msgid "`match` inspects a hidden discriminant field in the `enum`." +#: src/references/solution.md +msgid "/// Calculate the magnitude of the given vector.\n" msgstr "" -#: src/enums/variant-payloads.md:41 +#: src/references/solution.md msgid "" -"It is possible to retrieve the discriminant by calling `std::mem::" -"discriminant()`" +"/// Change the magnitude of the vector to 1.0 without changing its " +"direction.\n" msgstr "" -#: src/enums/variant-payloads.md:42 -msgid "" -"This is useful, for example, if implementing `PartialEq` for structs where " -"comparing field values doesn't affect equality." +#: src/user-defined-types.md +msgid "[Named Structs](./user-defined-types/named-structs.md) (10 minutes)" msgstr "" -#: src/enums/variant-payloads.md:43 -msgid "" -"`WebEvent::Click { ... }` is not exactly the same as `WebEvent::" -"Click(Click)` with a top level `struct Click { ... }`. The inlined version " -"cannot implement traits, for example." +#: src/user-defined-types.md +msgid "[Tuple Structs](./user-defined-types/tuple-structs.md) (10 minutes)" msgstr "" -#: src/enums/sizes.md:3 -msgid "" -"Rust enums are packed tightly, taking constraints due to alignment into " -"account:" +#: src/user-defined-types.md +msgid "[Enums](./user-defined-types/enums.md) (5 minutes)" msgstr "" -#: src/enums/sizes.md:5 +#: src/user-defined-types.md msgid "" -"```rust,editable\n" -"use std::any::type_name;\n" -"use std::mem::{align_of, size_of};\n" -"\n" -"fn dbg_size() {\n" -" println!(\"{}: size {} bytes, align: {} bytes\",\n" -" type_name::(), size_of::(), align_of::());\n" -"}\n" -"\n" -"enum Foo {\n" -" A,\n" -" B,\n" -"}\n" -"\n" -"fn main() {\n" -" dbg_size::();\n" -"}\n" -"```" +"[Static and Const](./user-defined-types/static-and-const.md) (5 minutes)" msgstr "" -#: src/enums/sizes.md:24 -msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/type-layout." -"html)." +#: src/user-defined-types.md +msgid "[Type Aliases](./user-defined-types/aliases.md) (2 minutes)" msgstr "" -#: src/enums/sizes.md:30 +#: src/user-defined-types.md msgid "" -"Internally Rust is using a field (discriminant) to keep track of the enum " -"variant." +"[Exercise: Elevator Events](./user-defined-types/exercise.md) (15 minutes)" msgstr "" -#: src/enums/sizes.md:32 -msgid "" -"You can control the discriminant if needed (e.g., for compatibility with C):" +#: src/user-defined-types/named-structs.md +msgid "Like C and C++, Rust has support for custom structs:" msgstr "" -#: src/enums/sizes.md:50 -msgid "" -"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " -"bytes." +#: src/user-defined-types/named-structs.md +msgid "\"{} is {} years old\"" msgstr "" -#: src/enums/sizes.md:54 -msgid "Try out other types such as" +#: src/user-defined-types/named-structs.md +#: src/android/interoperability/with-c/bindgen.md +msgid "\"Peter\"" msgstr "" -#: src/enums/sizes.md:56 -msgid "`dbg_size!(bool)`: size 1 bytes, align: 1 bytes," +#: src/user-defined-types/named-structs.md +msgid "\"Avery\"" msgstr "" -#: src/enums/sizes.md:57 -msgid "" -"`dbg_size!(Option)`: size 1 bytes, align: 1 bytes (niche optimization, " -"see below)," +#: src/user-defined-types/named-structs.md +msgid "\"Jackie\"" msgstr "" -#: src/enums/sizes.md:58 -msgid "`dbg_size!(&i32)`: size 8 bytes, align: 8 bytes (on a 64-bit machine)," +#: src/user-defined-types/named-structs.md +msgid "Structs work like in C or C++." msgstr "" -#: src/enums/sizes.md:59 -msgid "" -"`dbg_size!(Option<&i32>)`: size 8 bytes, align: 8 bytes (null pointer " -"optimization, see below)." +#: src/user-defined-types/named-structs.md +msgid "Like in C++, and unlike in C, no typedef is needed to define a type." msgstr "" -#: src/enums/sizes.md:61 src/memory-management/stack.md:32 -msgid "More to Explore" +#: src/user-defined-types/named-structs.md +msgid "Unlike in C++, there is no inheritance between structs." msgstr "" -#: src/enums/sizes.md:63 +#: src/user-defined-types/named-structs.md msgid "" -"Rust has several optimizations it can employ to make enums take up less " -"space." +"This may be a good time to let people know there are different types of " +"structs." msgstr "" -#: src/enums/sizes.md:65 +#: src/user-defined-types/named-structs.md msgid "" -"Niche optimization: Rust will merge unused bit patterns for the enum " -"discriminant." +"Zero-sized structs (e.g. `struct Foo;`) might be used when implementing a " +"trait on some type but don’t have any data that you want to store in the " +"value itself." msgstr "" -#: src/enums/sizes.md:68 +#: src/user-defined-types/named-structs.md 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:72 -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." +"The next slide will introduce Tuple structs, used when the field names are " +"not important." msgstr "" -#: src/enums/sizes.md:109 +#: src/user-defined-types/named-structs.md msgid "" -"More complex example if you want to discuss what happens when we chain more " -"than 256 `Option`s together." +"If you already have variables with the right names, then you can create the " +"struct using a shorthand." msgstr "" -#: src/control-flow/novel.md:3 +#: src/user-defined-types/named-structs.md msgid "" -"Rust has a few control flow constructs which differ from other languages. " -"They are used for pattern matching:" +"The syntax `..avery` allows us to copy the majority of the fields from the " +"old struct without having to explicitly type it all out. It must always be " +"the last element." msgstr "" -#: src/control-flow/novel.md:6 src/control-flow/if-let-expressions.md:1 -msgid "`if let` expressions" +#: src/user-defined-types/tuple-structs.md +msgid "If the field names are unimportant, you can use a tuple struct:" msgstr "" -#: src/control-flow/novel.md:7 -msgid "`while let` expressions" -msgstr "`while let` ifadeleri" - -#: src/control-flow/novel.md:8 src/control-flow/match-expressions.md:1 -msgid "`match` expressions" +#: src/user-defined-types/tuple-structs.md +msgid "\"({}, {})\"" msgstr "" -#: src/control-flow/if-let-expressions.md:3 -msgid "" -"The [`if let` expression](https://doc.rust-lang.org/reference/expressions/if-" -"expr.html#if-let-expressions) lets you execute different code depending on " -"whether a value matches a pattern:" +#: src/user-defined-types/tuple-structs.md +msgid "This is often used for single-field wrappers (called newtypes):" msgstr "" -#: src/control-flow/if-let-expressions.md:7 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let arg = std::env::args().next();\n" -" if let Some(value) = arg {\n" -" println!(\"Program name: {value}\");\n" -" } else {\n" -" println!(\"Missing name?\");\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/tuple-structs.md +msgid "\"Ask a rocket scientist at NASA\"" 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." +#: src/user-defined-types/tuple-structs.md +#: src/android/interoperability/cpp/cpp-bridge.md +#: src/bare-metal/microcontrollers/type-state.md +#: src/async/pitfalls/cancellation.md +msgid "// ...\n" msgstr "" -#: src/control-flow/if-let-expressions.md:23 +#: src/user-defined-types/tuple-structs.md msgid "" -"Unlike `match`, `if let` does not have to cover all branches. This can make " -"it more concise than `match`." +"Newtypes are a great way to encode additional information about the value in " +"a primitive type, for example:" msgstr "" -#: src/control-flow/if-let-expressions.md:24 -msgid "A common usage is handling `Some` values when working with `Option`." +#: src/user-defined-types/tuple-structs.md +msgid "The number is measured in some units: `Newtons` in the example above." msgstr "" -#: src/control-flow/if-let-expressions.md:25 +#: src/user-defined-types/tuple-structs.md msgid "" -"Unlike `match`, `if let` does not support guard clauses for pattern matching." +"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/control-flow/if-let-expressions.md:26 +#: src/user-defined-types/tuple-structs.md 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" +"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " +"single field in the newtype." msgstr "" -#: src/control-flow/while-let-expressions.md:3 +#: src/user-defined-types/tuple-structs.md 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:" +"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " +"for instance using booleans as integers." msgstr "" -#: src/control-flow/while-let-expressions.md:18 -msgid "" -"Here the iterator returned by `v.into_iter()` will return a `Option` on " -"every call to `next()`. It returns `Some(x)` until it is done, after which " -"it will return `None`. The `while let` lets us keep iterating through all " -"items." +#: src/user-defined-types/tuple-structs.md +msgid "Operator overloading is discussed on Day 3 (generics)." msgstr "" -#: src/control-flow/while-let-expressions.md:27 +#: src/user-defined-types/tuple-structs.md msgid "" -"Point out that the `while let` loop will keep going as long as the value " -"matches the pattern." +"The example is a subtle reference to the [Mars Climate Orbiter](https://en." +"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." msgstr "" -#: src/control-flow/while-let-expressions.md:28 +#: src/user-defined-types/enums.md 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." +"The `enum` keyword allows the creation of a type which has a few different " +"variants:" 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:" +#: src/user-defined-types/enums.md +msgid "// Simple variant\n" msgstr "" -#: src/control-flow/match-expressions.md:7 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" match std::env::args().next().as_deref() {\n" -" Some(\"cat\") => println!(\"Will do cat things\"),\n" -" Some(\"ls\") => println!(\"Will ls some files\"),\n" -" Some(\"mv\") => println!(\"Let's move some files\"),\n" -" Some(\"rm\") => println!(\"Uh, dangerous!\"),\n" -" None => println!(\"Hmm, no program name?\"),\n" -" _ => println!(\"Unknown program name!\"),\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/enums.md +msgid "// Tuple variant\n" 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 `()`." +#: src/user-defined-types/enums.md +msgid "// Struct variant\n" msgstr "" -#: src/control-flow/match-expressions.md:28 -msgid "Save the match expression to a variable and print it out." +#: src/user-defined-types/enums.md +msgid "\"On this turn: {:?}\"" msgstr "" -#: src/control-flow/match-expressions.md:29 -msgid "Remove `.as_deref()` and explain the error." +#: src/user-defined-types/enums.md +msgid "Enumerations allow you to collect a set of values under one type." msgstr "" -#: src/control-flow/match-expressions.md:30 +#: src/user-defined-types/enums.md msgid "" -"`std::env::args().next()` returns an `Option`, but we cannot match " -"against `String`." +"`Direction` is a type with variants. There are two values of `Direction`: " +"`Direction::Left` and `Direction::Right`." msgstr "" -#: src/control-flow/match-expressions.md:31 +#: src/user-defined-types/enums.md msgid "" -"`as_deref()` transforms an `Option` to `Option<&T::Target>`. In our case, " -"this turns `Option` into `Option<&str>`." +"`PlayerMove` is a type with three variants. In addition to the payloads, " +"Rust will store a discriminant so that it knows at runtime which variant is " +"in a `PlayerMove` value." msgstr "" -#: src/control-flow/match-expressions.md:32 -msgid "" -"We can now use pattern matching to match against the `&str` inside `Option`." +#: src/user-defined-types/enums.md +msgid "This might be a good time to compare structs and enums:" msgstr "" -#: src/pattern-matching.md:3 +#: src/user-defined-types/enums.md msgid "" -"The `match` keyword lets you match a value against one or more _patterns_. " -"The comparisons are done from top to bottom and the first match wins." -msgstr "" - -#: src/pattern-matching.md:6 -msgid "The patterns can be simple values, similarly to `switch` in C and C++:" +"In both, you can have a simple version without fields (unit struct) or one " +"with different types of fields (variant payloads)." msgstr "" -#: src/pattern-matching.md:8 +#: src/user-defined-types/enums.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let input = 'x';\n" -"\n" -" match input {\n" -" 'q' => println!(\"Quitting\"),\n" -" 'a' | 's' | 'w' | 'd' => println!(\"Moving around\"),\n" -" '0'..='9' => println!(\"Number input\"),\n" -" _ => println!(\"Something else\"),\n" -" }\n" -"}\n" -"```" +"You could even implement the different variants of an enum with separate " +"structs but then they wouldn’t be the same type as they would if they were " +"all defined in an enum." msgstr "" -#: src/pattern-matching.md:21 -msgid "The `_` pattern is a wildcard pattern which matches any value." +#: src/user-defined-types/enums.md +msgid "Rust uses minimal space to store the discriminant." msgstr "" -#: src/pattern-matching.md:26 -msgid "" -"You might point out how some specific characters are being used when in a " -"pattern" +#: src/user-defined-types/enums.md +msgid "If necessary, it stores an integer of the smallest required size" msgstr "" -#: src/pattern-matching.md:27 -msgid "`|` as an `or`" +#: src/user-defined-types/enums.md +msgid "" +"If the allowed variant values do not cover all bit patterns, it will use " +"invalid bit patterns to encode the discriminant (the \"niche " +"optimization\"). For example, `Option<&u8>` stores either a pointer to an " +"integer or `NULL` for the `None` variant." msgstr "" -#: src/pattern-matching.md:28 -msgid "`..` can expand as much as it needs to be" +#: src/user-defined-types/enums.md +msgid "" +"You can control the discriminant if needed (e.g., for compatibility with C):" msgstr "" -#: src/pattern-matching.md:29 -msgid "`1..=5` represents an inclusive range" +#: src/user-defined-types/enums.md +msgid "" +"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " +"bytes." msgstr "" -#: src/pattern-matching.md:30 -msgid "`_` is a wild card" +#: src/user-defined-types/enums.md src/user-defined-types/static-and-const.md +#: src/memory-management/review.md src/memory-management/move.md +#: src/smart-pointers/box.md src/borrowing/shared.md +msgid "More to Explore" msgstr "" -#: src/pattern-matching.md:31 +#: src/user-defined-types/enums.md 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`." +"Rust has several optimizations it can employ to make enums take up less " +"space." msgstr "" -#: src/pattern-matching.md:32 -msgid "You can demonstrate matching on a reference." +#: src/user-defined-types/enums.md +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/pattern-matching.md:33 +#: src/user-defined-types/enums.md msgid "" -"This might be a good time to bring up the concept of irrefutable patterns, " -"as the term can show up in error messages." +"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/pattern-matching/destructuring-enums.md:3 +#: src/user-defined-types/static-and-const.md 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:" +"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/pattern-matching/destructuring-enums.md:6 -msgid "" -"```rust,editable\n" -"enum Result {\n" -" Ok(i32),\n" -" Err(String),\n" -"}\n" -"\n" -"fn divide_in_two(n: i32) -> Result {\n" -" if n % 2 == 0 {\n" -" Result::Ok(n / 2)\n" -" } else {\n" -" Result::Err(format!(\"cannot divide {n} into two equal parts\"))\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let n = 100;\n" -" match divide_in_two(n) {\n" -" Result::Ok(half) => println!(\"{n} divided in two is {half}\"),\n" -" Result::Err(msg) => println!(\"sorry, an error happened: {msg}\"),\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/static-and-const.md +msgid "`const`" msgstr "" -#: src/pattern-matching/destructuring-enums.md:29 +#: src/user-defined-types/static-and-const.md 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." +"Constant variables are evaluated at compile time and their values are " +"inlined wherever they are used:" msgstr "" -#: src/pattern-matching/destructuring-enums.md:36 +#: src/user-defined-types/static-and-const.md msgid "" -"The `if`/`else` expression is returning an enum that is later unpacked with " -"a `match`." +"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html) these are inlined upon use." msgstr "" -#: src/pattern-matching/destructuring-enums.md:37 +#: src/user-defined-types/static-and-const.md 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." +"Only functions marked `const` can be called at compile time to generate " +"`const` values. `const` functions can however be called at runtime." msgstr "" -#: src/pattern-matching/destructuring-structs.md:3 -msgid "You can also destructure `structs`:" +#: src/user-defined-types/static-and-const.md +msgid "`static`" msgstr "" -#: src/pattern-matching/destructuring-structs.md:5 +#: src/user-defined-types/static-and-const.md msgid "" -"```rust,editable\n" -"struct Foo {\n" -" x: (u32, u32),\n" -" y: u32,\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let foo = Foo { x: (1, 2), y: 3 };\n" -" match foo {\n" -" Foo { x: (1, b), y } => println!(\"x.0 = 1, b = {b}, y = {y}\"),\n" -" Foo { y: 2, x: i } => println!(\"y = 2, x = {i:?}\"),\n" -" Foo { y, .. } => println!(\"y = {y}, other fields were " -"ignored\"),\n" -" }\n" -"}\n" -"```" +"Static variables will live during the whole execution of the program, and " +"therefore will not move:" msgstr "" -#: src/pattern-matching/destructuring-structs.md:23 -msgid "Change the literal values in `foo` to match with the other patterns." +#: src/user-defined-types/static-and-const.md +msgid "\"Welcome to RustOS 3.14\"" msgstr "" -#: src/pattern-matching/destructuring-structs.md:24 -msgid "Add a new field to `Foo` and make changes to the pattern as needed." +#: src/user-defined-types/static-and-const.md +msgid "\"{BANNER}\"" msgstr "" -#: src/pattern-matching/destructuring-structs.md:25 +#: src/user-defined-types/static-and-const.md 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." +"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/pattern-matching/destructuring-arrays.md:3 -msgid "" -"You can destructure arrays, tuples, and slices by matching on their elements:" +#: src/user-defined-types/static-and-const.md +msgid "Mention that `const` behaves semantically similar to C++'s `constexpr`." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:5 +#: src/user-defined-types/static-and-const.md msgid "" -"```rust,editable\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let triple = [0, -2, 3];\n" -" println!(\"Tell me about {triple:?}\");\n" -" match triple {\n" -" [0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" -" [1, ..] => println!(\"First is 1 and the rest were ignored\"),\n" -" _ => println!(\"All elements were ignored\"),\n" -" }\n" -"}\n" -"```" +"`static`, on the other hand, is much more similar to a `const` or mutable " +"global variable in C++." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:21 +#: src/user-defined-types/static-and-const.md msgid "" -"Destructuring of slices of unknown length also works with patterns of fixed " -"length." +"`static` provides object identity: an address in memory and state as " +"required by types with interior mutability such as `Mutex`." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:24 +#: src/user-defined-types/static-and-const.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" inspect(&[0, -2, 3]);\n" -" inspect(&[0, -2, 3, 4]);\n" -"}\n" -"\n" -"#[rustfmt::skip]\n" -"fn inspect(slice: &[i32]) {\n" -" println!(\"Tell me about {slice:?}\");\n" -" match slice {\n" -" &[0, y, z] => println!(\"First is 0, y = {y}, and z = {z}\"),\n" -" &[1, ..] => println!(\"First is 1 and the rest were ignored\"),\n" -" _ => println!(\"All elements were ignored\"),\n" -" }\n" -"}\n" -"```" +"It isn't super common that one would need a runtime evaluated constant, but " +"it is helpful and safer than using a static." msgstr "" -#: src/pattern-matching/destructuring-arrays.md:41 -msgid "Create a new pattern using `_` to represent an element. " +#: src/user-defined-types/static-and-const.md +msgid "Properties table:" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:42 -msgid "Add more values to the array." +#: src/user-defined-types/static-and-const.md +#: src/chromium/adding-third-party-crates.md +msgid "Property" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:43 -msgid "" -"Point out that how `..` will expand to account for different number of " -"elements." +#: src/user-defined-types/static-and-const.md +msgid "Static" msgstr "" -#: src/pattern-matching/destructuring-arrays.md:44 -msgid "Show matching against the tail with patterns `[.., b]` and `[a@..,b]`" +#: src/user-defined-types/static-and-const.md +msgid "Constant" 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:" +#: src/user-defined-types/static-and-const.md +msgid "Has an address in memory" msgstr "" -#: src/pattern-matching/match-guards.md:6 -msgid "" -"```rust,editable\n" -"#[rustfmt::skip]\n" -"fn main() {\n" -" let pair = (2, -2);\n" -" println!(\"Tell me about {pair:?}\");\n" -" match pair {\n" -" (x, y) if x == y => println!(\"These are twins\"),\n" -" (x, y) if x + y == 0 => println!(\"Antimatter, kaboom!\"),\n" -" (x, _) if x % 2 == 1 => println!(\"The first one is odd\"),\n" -" _ => println!(\"No correlation...\"),\n" -" }\n" -"}\n" -"```" +#: src/user-defined-types/static-and-const.md +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Yes" msgstr "" -#: src/pattern-matching/match-guards.md:23 -msgid "" -"Match guards as a separate syntax feature are important and necessary when " -"we wish to concisely express more complex ideas than patterns alone would " -"allow." +#: src/user-defined-types/static-and-const.md +msgid "No (inlined)" msgstr "" -#: src/pattern-matching/match-guards.md:24 -msgid "" -"They are not the same as separate `if` expression inside of the match arm. " -"An `if` expression inside of the branch block (after `=>`) happens after the " -"match arm is selected. Failing the `if` condition inside of that block won't " -"result in other arms of the original `match` expression being considered." +#: src/user-defined-types/static-and-const.md +msgid "Lives for the entire duration of the program" msgstr "" -#: src/pattern-matching/match-guards.md:26 -msgid "You can use the variables defined in the pattern in your if expression." +#: src/user-defined-types/static-and-const.md +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "No" msgstr "" -#: src/pattern-matching/match-guards.md:27 -msgid "" -"The condition defined in the guard applies to every expression in a pattern " -"with an `|`." +#: src/user-defined-types/static-and-const.md +msgid "Can be mutable" msgstr "" -#: src/exercises/day-1/afternoon.md:1 -msgid "Day 1: Afternoon Exercises" +#: src/user-defined-types/static-and-const.md +msgid "Yes (unsafe)" msgstr "" -#: src/exercises/day-1/afternoon.md:3 -msgid "We will look at two things:" +#: src/user-defined-types/static-and-const.md +msgid "Evaluated at compile time" msgstr "" -#: src/exercises/day-1/afternoon.md:5 -msgid "The Luhn algorithm," -msgstr "Luhn Algortiması," - -#: src/exercises/day-1/afternoon.md:7 -msgid "An exercise on pattern matching." +#: src/user-defined-types/static-and-const.md +msgid "Yes (initialised at compile time)" 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." +#: src/user-defined-types/static-and-const.md +msgid "Inlined wherever it is used" msgstr "" -#: src/exercises/day-1/luhn.md:3 +#: src/user-defined-types/static-and-const.md 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:" +"Because `static` variables are accessible from any thread, they must be " +"`Sync`. Interior mutability is possible through a [`Mutex`](https://doc.rust-" +"lang.org/std/sync/struct.Mutex.html), atomic or similar." msgstr "" -#: src/exercises/day-1/luhn.md:7 -msgid "Ignore all spaces. Reject number with less than two digits." +#: src/user-defined-types/static-and-const.md +msgid "Thread-local data can be created with the macro `std::thread_local`." msgstr "" -#: src/exercises/day-1/luhn.md:9 +#: src/user-defined-types/aliases.md 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`." +"A type alias creates a name for another type. The two types can be used " +"interchangeably." 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`." +#: src/user-defined-types/aliases.md +msgid "// Aliases are more useful with long, complex types:\n" msgstr "" -#: src/exercises/day-1/luhn.md:15 -msgid "Sum all the undoubled and doubled digits." +#: src/user-defined-types/aliases.md +msgid "C programmers will recognize this as similar to a `typedef`." msgstr "" -#: src/exercises/day-1/luhn.md:17 -msgid "The credit card number is valid if the sum ends with `0`." +#: src/user-defined-types/exercise.md +msgid "" +"We will create a data structure to represent an event in an elevator control " +"system. It is up to you to define the types and functions to construct " +"various events. Use `#[derive(Debug)]` to allow the types to be formatted " +"with `{:?}`." msgstr "" -#: src/exercises/day-1/luhn.md:19 +#: src/user-defined-types/exercise.md msgid "" -"Copy the code below to and implement the " -"function." +"This exercise only requires creating and populating data structures so that " +"`main` runs without errors. The next part of the course will cover getting " +"data out of these structures." msgstr "" -#: src/exercises/day-1/luhn.md:21 +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md 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." +"/// An event in the elevator system that the controller must react to.\n" msgstr "" -#: src/exercises/day-1/luhn.md:25 -msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub fn luhn(cc_number: &str) -> bool {\n" -" unimplemented!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_non_digit_cc_number() {\n" -" assert!(!luhn(\"foo\"));\n" -" assert!(!luhn(\"foo 0 0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty_cc_number() {\n" -" assert!(!luhn(\"\"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_digit_cc_number() {\n" -" assert!(!luhn(\"0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_two_digit_cc_number() {\n" -" assert!(luhn(\" 0 0 \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_valid_cc_number() {\n" -" assert!(luhn(\"4263 9826 4026 9299\"));\n" -" assert!(luhn(\"4539 3195 0343 6467\"));\n" -" assert!(luhn(\"7992 7398 713\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_invalid_cc_number() {\n" -" assert!(!luhn(\"4223 9826 4026 9299\"));\n" -" assert!(!luhn(\"4539 3195 0343 6476\"));\n" -" assert!(!luhn(\"8273 1232 7352 0569\"));\n" -"}\n" -"\n" -"#[allow(dead_code)]\n" -"fn main() {}\n" -"```" +#: src/user-defined-types/exercise.md +msgid "// TODO: add required variants\n" msgstr "" -#: src/exercises/day-1/pattern-matching.md:1 -msgid "Exercise: Expression Evaluation" +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "/// A direction of travel.\n" msgstr "" -#: src/exercises/day-1/pattern-matching.md:3 -msgid "Let's write a simple recursive evaluator for arithmetic expressions. " +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "/// The car has arrived on the given floor.\n" msgstr "" -#: src/exercises/day-1/pattern-matching.md:5 -msgid "" -"```rust\n" -"/// An operation to perform on two subexpressions.\n" -"#[derive(Debug)]\n" -"enum Operation {\n" -" Add,\n" -" Sub,\n" -" Mul,\n" -" Div,\n" -"}\n" -"\n" -"/// An expression, in tree form.\n" -"#[derive(Debug)]\n" -"enum Expression {\n" -" /// An operation on two subexpressions.\n" -" Op {\n" -" op: Operation,\n" -" left: Box,\n" -" right: Box,\n" -" },\n" -"\n" -" /// A literal value\n" -" Value(i64),\n" -"}\n" -"\n" -"/// The result of evaluating an expression.\n" -"#[derive(Debug, PartialEq, Eq)]\n" -"enum Res {\n" -" /// Evaluation was successful, with the given result.\n" -" Ok(i64),\n" -" /// Evaluation failed, with the given error message.\n" -" Err(String),\n" -"}\n" -"// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" -"use Res::{Err, Ok};\n" -"\n" -"fn eval(e: Expression) -> Res {\n" -" todo!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_value() {\n" -" assert_eq!(eval(Expression::Value(19)), Ok(19));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_sum() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(20)),\n" -" }),\n" -" Ok(30)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_recursion() {\n" -" let term1 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(9)),\n" -" };\n" -" let term2 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(3)),\n" -" right: Box::new(Expression::Value(4)),\n" -" }),\n" -" right: Box::new(Expression::Value(5)),\n" -" };\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(term1),\n" -" right: Box::new(term2),\n" -" }),\n" -" Ok(85)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_error() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Div,\n" -" left: Box::new(Expression::Value(99)),\n" -" right: Box::new(Expression::Value(0)),\n" -" }),\n" -" Err(String::from(\"division by zero\"))\n" -" );\n" -"}\n" -"```" +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "/// The car doors have opened.\n" 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)`." +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "/// The car doors have closed.\n" msgstr "" -#: src/exercises/day-1/pattern-matching.md:105 +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md 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." +"/// A directional button was pressed in an elevator lobby on the given " +"floor.\n" 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." +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "/// A floor button was pressed in the elevator car.\n" msgstr "" -#: src/exercises/day-1/pattern-matching.md:113 -msgid "" -"If you finish early, try writing a test that results in an integer overflow. " -"How could you handle this with `Res::Err` instead of a panic?" +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"A ground floor passenger has pressed the up button: {:?}\"" msgstr "" -#: src/welcome-day-2.md:1 -msgid "Welcome to Day 2" +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"The car has arrived on the ground floor: {:?}\"" msgstr "" -#: src/welcome-day-2.md:3 -msgid "Now that we have seen a fair amount of Rust, we will continue with:" +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"The car door opened: {:?}\"" msgstr "" -#: src/welcome-day-2.md:5 -msgid "" -"Memory management: stack vs heap, manual memory management, scope-based " -"memory management, and garbage collection." +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"A passenger has pressed the 3rd floor button: {:?}\"" msgstr "" -#: src/welcome-day-2.md:8 -msgid "" -"Ownership: move semantics, copying and cloning, borrowing, and lifetimes." +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"The car door closed: {:?}\"" msgstr "" -#: src/welcome-day-2.md:10 -msgid "Structs and methods." -msgstr "Yapılar ve metotlar." +#: src/user-defined-types/exercise.md src/user-defined-types/solution.md +msgid "\"The car has arrived on the 3rd floor: {:?}\"" +msgstr "" -#: src/welcome-day-2.md:12 -msgid "" -"The Standard Library: `String`, `Option` and `Result`, `Vec`, `HashMap`, " -"`Rc` and `Arc`." +#: src/user-defined-types/solution.md +msgid "/// A button was pressed.\n" msgstr "" -#: src/welcome-day-2.md:15 -msgid "Modules: visibility, paths, and filesystem hierarchy." +#: src/user-defined-types/solution.md +msgid "/// The car has arrived at the given floor.\n" msgstr "" -#: src/memory-management.md:3 -msgid "Traditionally, languages have fallen into two broad categories:" +#: src/user-defined-types/solution.md +msgid "/// The car's doors have opened.\n" msgstr "" -#: src/memory-management.md:5 -msgid "Full control via manual memory management: C, C++, Pascal, ..." +#: src/user-defined-types/solution.md +msgid "/// The car's doors have closed.\n" msgstr "" -#: src/memory-management.md:6 -msgid "" -"Full safety via automatic memory management at runtime: Java, Python, Go, " -"Haskell, ..." +#: src/user-defined-types/solution.md +msgid "/// A floor is represented as an integer.\n" msgstr "" -#: src/memory-management.md:8 -msgid "Rust offers a new mix:" +#: src/user-defined-types/solution.md +msgid "/// A user-accessible button.\n" msgstr "" -#: src/memory-management.md:10 -msgid "" -"Full control _and_ safety via compile time enforcement of correct memory " -"management." +#: src/user-defined-types/solution.md +msgid "/// A button in the elevator lobby on the given floor.\n" msgstr "" -#: src/memory-management.md:13 -msgid "It does this with an explicit ownership concept." +#: src/user-defined-types/solution.md +msgid "/// A floor button within the car.\n" msgstr "" -#: src/memory-management.md:15 -msgid "First, let's refresh how memory management works." +#: src/welcome-day-2.md +msgid "Welcome to Day 2" msgstr "" -#: src/memory-management/stack-vs-heap.md:1 -msgid "The Stack vs The Heap" +#: src/welcome-day-2.md +msgid "" +"Now that we have seen a fair amount of Rust, today will focus on Rust's type " +"system:" msgstr "" -#: src/memory-management/stack-vs-heap.md:3 -msgid "Stack: Continuous area of memory for local variables." +#: src/welcome-day-2.md +msgid "Pattern matching: extracting data from structures." msgstr "" -#: src/memory-management/stack-vs-heap.md:4 -msgid "Values have fixed sizes known at compile time." +#: src/welcome-day-2.md +msgid "Methods: associating functions with types." msgstr "" -#: src/memory-management/stack-vs-heap.md:5 -msgid "Extremely fast: just move a stack pointer." +#: src/welcome-day-2.md +msgid "Traits: behaviors shared by multiple types." msgstr "" -#: src/memory-management/stack-vs-heap.md:6 -msgid "Easy to manage: follows function calls." +#: src/welcome-day-2.md +msgid "Generics: parameterizing types on other types." msgstr "" -#: src/memory-management/stack-vs-heap.md:7 -msgid "Great memory locality." +#: src/welcome-day-2.md +msgid "" +"Standard library types and traits: a tour of Rust's rich standard library." msgstr "" -#: src/memory-management/stack-vs-heap.md:9 -msgid "Heap: Storage of values outside of function calls." +#: src/welcome-day-2.md +msgid "[Welcome](./welcome-day-2.md) (3 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:10 -msgid "Values have dynamic sizes determined at runtime." +#: src/welcome-day-2.md +msgid "[Pattern Matching](./pattern-matching.md) (50 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:11 -msgid "Slightly slower than the stack: some book-keeping needed." +#: src/welcome-day-2.md +msgid "[Methods and Traits](./methods-and-traits.md) (55 minutes)" msgstr "" -#: src/memory-management/stack-vs-heap.md:12 -msgid "No guarantee of memory locality." +#: src/welcome-day-2.md +msgid "[Generics](./generics.md) (45 minutes)" msgstr "" -#: src/memory-management/stack.md:1 -msgid "Stack and Heap Example" -msgstr "Stack vs Heap Örneği" - -#: src/memory-management/stack.md:3 +#: src/welcome-day-2.md src/welcome-day-4.md msgid "" -"Creating a `String` puts fixed-sized metadata on the stack and dynamically " -"sized data, the actual string, on the heap:" +"Including 10 minute breaks, this session should take about 3 hours and 5 " +"minutes" msgstr "" -#: src/memory-management/stack.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1 = String::from(\"Hello\");\n" -"}\n" -"```" +#: src/pattern-matching.md +msgid "[Destructuring](./pattern-matching/destructuring.md) (10 minutes)" msgstr "" -#: src/memory-management/stack.md:28 -msgid "" -"Mention that a `String` is backed by a `Vec`, so it has a capacity and " -"length and can grow if mutable via reallocation on the heap." +#: src/pattern-matching.md +msgid "[Let Control Flow](./pattern-matching/let-control-flow.md) (10 minutes)" msgstr "" -#: src/memory-management/stack.md:30 +#: src/pattern-matching.md 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)" +"[Exercise: Expression Evaluation](./pattern-matching/exercise.md) (30 " +"minutes)" msgstr "" -#: src/memory-management/stack.md:34 -msgid "" -"We can inspect the memory layout with `unsafe` Rust. However, you should " -"point out that this is rightfully unsafe!" +#: src/pattern-matching/destructuring.md +msgid "Like tuples, structs and enums can also be destructured by matching:" msgstr "" -#: src/memory-management/stack.md:37 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut s1 = String::from(\"Hello\");\n" -" s1.push(' ');\n" -" s1.push_str(\"world\");\n" -" // DON'T DO THIS AT HOME! For educational purposes only.\n" -" // String provides no guarantees about its layout, so this could lead " -"to\n" -" // undefined behavior.\n" -" unsafe {\n" -" let (ptr, capacity, len): (usize, usize, usize) = std::mem::" -"transmute(s1);\n" -" println!(\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\");\n" -" }\n" -"}\n" -"```" +#: src/pattern-matching/destructuring.md +msgid "Structs" +msgstr "Yapılar (Structs)" + +#: src/pattern-matching/destructuring.md +msgid "\"x.0 = 1, b = {b}, y = {y}\"" msgstr "" -#: src/memory-management/manual.md:3 -msgid "You allocate and deallocate heap memory yourself." +#: src/pattern-matching/destructuring.md +msgid "\"y = 2, x = {i:?}\"" msgstr "" -#: src/memory-management/manual.md:5 +#: src/pattern-matching/destructuring.md +msgid "\"y = {y}, other fields were ignored\"" +msgstr "" + +#: src/pattern-matching/destructuring.md msgid "" -"If not done with care, this can lead to crashes, bugs, security " -"vulnerabilities, and memory leaks." +"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.md +msgid "\"cannot divide {n} into two equal parts\"" msgstr "" -#: src/memory-management/manual.md:7 -msgid "C Example" +#: src/pattern-matching/destructuring.md +msgid "\"{n} divided in two is {half}\"" msgstr "" -#: src/memory-management/manual.md:9 -msgid "You must call `free` on every pointer you allocate with `malloc`:" +#: src/pattern-matching/destructuring.md +msgid "\"sorry, an error happened: {msg}\"" msgstr "" -#: src/memory-management/manual.md:11 +#: src/pattern-matching/destructuring.md msgid "" -"```c\n" -"void foo(size_t n) {\n" -" int* int_array = malloc(n * sizeof(int));\n" -" //\n" -" // ... lots of code\n" -" //\n" -" free(int_array);\n" -"}\n" -"```" +"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.md +msgid "Change the literal values in `foo` to match with the other patterns." +msgstr "" + +#: src/pattern-matching/destructuring.md +msgid "Add a new field to `Foo` and make changes to the pattern as needed." msgstr "" -#: src/memory-management/manual.md:21 +#: src/pattern-matching/destructuring.md 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." +"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/memory-management/scope-based.md:3 +#: src/pattern-matching/destructuring.md msgid "" -"Constructors and destructors let you hook into the lifetime of an object." +"The `if`/`else` expression is returning an enum that is later unpacked with " +"a `match`." msgstr "" -#: src/memory-management/scope-based.md:5 +#: src/pattern-matching/destructuring.md 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." +"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/memory-management/scope-based.md:9 +#: src/pattern-matching/destructuring.md msgid "" -"This is often called _resource acquisition is initialization_ (RAII) and " -"gives you smart pointers." +"The values in the enum variants can only be accessed after being pattern " +"matched." msgstr "" -#: src/memory-management/scope-based.md:12 -msgid "C++ Example" +#: src/pattern-matching/destructuring.md +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/memory-management/scope-based.md:14 +#: src/pattern-matching/destructuring.md msgid "" -"```c++\n" -"void say_hello(std::unique_ptr person) {\n" -" std::cout << \"Hello \" << person->name << std::endl;\n" -"}\n" -"```" +"Save the result of `divide_in_two` in the `result` variable and `match` it " +"in a loop. That won't compile because `msg` is consumed when matched. To fix " +"it, match `&result` instead of `result`. That will make `msg` a reference so " +"it won't be consumed. This [\"match ergonomics\"](https://rust-lang.github." +"io/rfcs/2005-match-ergonomics.html) appeared in Rust 2018. If you want to " +"support older Rust, replace `msg` with `ref msg` in the pattern." msgstr "" -#: src/memory-management/scope-based.md:20 +#: src/pattern-matching/let-control-flow.md msgid "" -"The `std::unique_ptr` object is allocated on the stack, and points to memory " -"allocated on the heap." +"Rust has a few control flow constructs which differ from other languages. " +"They are used for pattern matching:" msgstr "" -#: src/memory-management/scope-based.md:22 -msgid "At the end of `say_hello`, the `std::unique_ptr` destructor will run." +#: src/pattern-matching/let-control-flow.md +msgid "`if let` expressions" msgstr "" -#: src/memory-management/scope-based.md:23 -msgid "The destructor frees the `Person` object it points to." +#: src/pattern-matching/let-control-flow.md +msgid "`while let` expressions" +msgstr "`while let` ifadeleri" + +#: src/pattern-matching/let-control-flow.md +msgid "`match` expressions" msgstr "" -#: src/memory-management/scope-based.md:25 +#: src/pattern-matching/let-control-flow.md msgid "" -"Special move constructors are used when passing ownership to a function:" +"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/memory-management/garbage-collection.md:1 -msgid "Automatic Memory Management" +#: src/pattern-matching/let-control-flow.md +msgid "\"slept for {:?}\"" msgstr "" -#: src/memory-management/garbage-collection.md:3 +#: src/pattern-matching/let-control-flow.md +#, fuzzy +msgid "`let else` expressions" +msgstr "`while let` ifadeleri" + +#: src/pattern-matching/let-control-flow.md msgid "" -"An alternative to manual and scope-based memory management is automatic " -"memory management:" +"For the common case of matching a pattern and returning from the function, " +"use [`let else`](https://doc.rust-lang.org/rust-by-example/flow_control/" +"let_else.html). The \"else\" case must diverge (`return`, `break`, or panic " +"- anything but falling off the end of the block)." msgstr "" -#: src/memory-management/garbage-collection.md:6 -msgid "The programmer never allocates or deallocates memory explicitly." +#: src/pattern-matching/let-control-flow.md +msgid "\"got None\"" msgstr "" -#: src/memory-management/garbage-collection.md:7 -msgid "" -"A garbage collector finds unused memory and deallocates it for the " -"programmer." +#: src/pattern-matching/let-control-flow.md +msgid "\"got empty string\"" +msgstr "" + +#: src/pattern-matching/let-control-flow.md +msgid "\"not a hex digit\"" msgstr "" -#: src/memory-management/garbage-collection.md:9 -msgid "Java Example" +#: src/pattern-matching/let-control-flow.md src/pattern-matching/solution.md +msgid "\"result: {:?}\"" msgstr "" -#: src/memory-management/garbage-collection.md:11 -msgid "The `person` object is not deallocated after `sayHello` returns:" +#: src/pattern-matching/let-control-flow.md src/generics/trait-bounds.md +#: src/smart-pointers/solution.md src/testing/googletest.md +#: src/testing/solution.md +msgid "\"foo\"" msgstr "" -#: src/memory-management/garbage-collection.md:13 +#: src/pattern-matching/let-control-flow.md msgid "" -"```java\n" -"void sayHello(Person person) {\n" -" System.out.println(\"Hello \" + person.getName());\n" -"}\n" -"```" +"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/memory-management/rust.md:1 -msgid "Memory Management in Rust" +#: src/pattern-matching/let-control-flow.md +msgid "" +"Here [`String::pop`](https://doc.rust-lang.org/stable/std/string/struct." +"String.html#method.pop) returns `Some(c)` until the string is empty, after " +"which it will return `None`. The `while let` lets us keep iterating through " +"all items." msgstr "" -#: src/memory-management/rust.md:3 -msgid "Memory management in Rust is a mix:" +#: src/pattern-matching/let-control-flow.md +msgid "if-let" msgstr "" -#: src/memory-management/rust.md:5 -msgid "Safe and correct like Java, but without a garbage collector." +#: src/pattern-matching/let-control-flow.md +msgid "" +"Unlike `match`, `if let` does not have to cover all branches. This can make " +"it more concise than `match`." msgstr "" -#: src/memory-management/rust.md:6 -msgid "Scope-based like C++, but the compiler enforces full adherence." +#: src/pattern-matching/let-control-flow.md +msgid "A common usage is handling `Some` values when working with `Option`." msgstr "" -#: src/memory-management/rust.md:7 +#: src/pattern-matching/let-control-flow.md msgid "" -"A Rust user can choose the right abstraction for the situation, some even " -"have no cost at runtime like C." +"Unlike `match`, `if let` does not support guard clauses for pattern matching." msgstr "" -#: src/memory-management/rust.md:9 -msgid "Rust achieves this by modeling _ownership_ explicitly." +#: src/pattern-matching/let-control-flow.md +msgid "let-else" msgstr "" -#: src/memory-management/rust.md:13 +#: src/pattern-matching/let-control-flow.md 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." +"`if-let`s can pile up, as shown. The `let-else` construct supports " +"flattening this nested code. Rewrite the awkward version for students, so " +"they can see the transformation." msgstr "" -#: src/memory-management/rust.md:15 -msgid "" -"You may be asked about destructors here, the [Drop](https://doc.rust-lang." -"org/std/ops/trait.Drop.html) trait is the Rust equivalent." +#: src/pattern-matching/let-control-flow.md +msgid "The rewritten version is:" +msgstr "" + +#: src/pattern-matching/let-control-flow.md +msgid "while-let" msgstr "" -#: src/ownership.md:3 +#: src/pattern-matching/let-control-flow.md msgid "" -"All variable bindings have a _scope_ where they are valid and it is an error " -"to use a variable outside its scope:" +"Point out that the `while let` loop will keep going as long as the value " +"matches the pattern." msgstr "" -#: src/ownership.md:19 +#: src/pattern-matching/let-control-flow.md msgid "" -"At the end of the scope, the variable is _dropped_ and the data is freed." +"You could rewrite the `while let` loop as an infinite loop with an if " +"statement that breaks when there is no value to unwrap for `name.pop()`. The " +"`while let` provides syntactic sugar for the above scenario." msgstr "" -#: src/ownership.md:20 -msgid "A destructor can run here to free up resources." +#: src/pattern-matching/exercise.md +msgid "Let's write a simple recursive evaluator for arithmetic expressions." msgstr "" -#: src/ownership.md:21 -msgid "We say that the variable _owns_ the value." +#: src/pattern-matching/exercise.md +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/ownership/move-semantics.md:3 -msgid "An assignment will transfer _ownership_ between variables:" +#: src/pattern-matching/exercise.md +msgid "" +"Some expressions cannot be evaluated and will return an error. The standard " +"[`Result`](https://doc.rust-lang.org/std/result/enum.Result." +"html) type is an enum that represents either a successful value " +"(`Ok(Value)`) or an error (`Err(String)`). We will cover this type in detail " +"later." msgstr "" -#: src/ownership/move-semantics.md:5 +#: src/pattern-matching/exercise.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s1: String = String::from(\"Hello!\");\n" -" let s2: String = s1;\n" -" println!(\"s2: {s2}\");\n" -" // println!(\"s1: {s1}\");\n" -"}\n" -"```" +"Copy and paste the code into the Rust playground, and begin implementing " +"`eval`. The final product should pass the tests. It may be helpful to use " +"`todo!()` and get the tests to pass one-by-one. You can also skip a test " +"temporarily with `#[ignore]`:" msgstr "" -#: src/ownership/move-semantics.md:14 -msgid "The assignment of `s1` to `s2` transfers ownership." +#: src/pattern-matching/exercise.md +msgid "" +"If you finish early, try writing a test that results in division by zero or " +"integer overflow. How could you handle this with `Result` instead of a panic?" msgstr "" -#: src/ownership/move-semantics.md:15 -msgid "When `s1` goes out of scope, nothing happens: it does not own anything." +#: src/pattern-matching/exercise.md src/pattern-matching/solution.md +msgid "/// An operation to perform on two subexpressions.\n" msgstr "" -#: src/ownership/move-semantics.md:16 -msgid "When `s2` goes out of scope, the string data is freed." +#: src/pattern-matching/exercise.md src/pattern-matching/solution.md +msgid "/// An expression, in tree form.\n" msgstr "" -#: src/ownership/move-semantics.md:17 -msgid "There is always _exactly_ one variable binding which owns a value." +#: src/pattern-matching/exercise.md src/pattern-matching/solution.md +msgid "/// An operation on two subexpressions.\n" msgstr "" -#: src/ownership/move-semantics.md:21 -msgid "" -"Mention that this is the opposite of the defaults in C++, which copies by " -"value unless you use `std::move` (and the move constructor is defined!)." +#: src/pattern-matching/exercise.md src/pattern-matching/solution.md +msgid "/// A literal value\n" msgstr "" -#: src/ownership/move-semantics.md:23 -msgid "" -"It is only the ownership that moves. Whether any machine code is generated " -"to manipulate the data itself is a matter of optimization, and such copies " -"are aggressively optimized away." +#: src/pattern-matching/exercise.md src/pattern-matching/solution.md +msgid "\"division by zero\"" msgstr "" -#: src/ownership/move-semantics.md:25 -msgid "" -"Simple values (such as integers) can be marked `Copy` (see later slides)." +#: src/pattern-matching/solution.md +msgid "\"expr: {:?}\"" msgstr "" -#: src/ownership/move-semantics.md:27 -msgid "In Rust, clones are explicit (by using `clone`)." +#: src/methods-and-traits.md +msgid "[Methods](./methods-and-traits/methods.md) (10 minutes)" msgstr "" -#: src/ownership/moved-strings-rust.md:11 -msgid "The heap data from `s1` is reused for `s2`." +#: src/methods-and-traits.md +msgid "[Traits](./methods-and-traits/traits.md) (10 minutes)" msgstr "" -#: src/ownership/moved-strings-rust.md:12 -msgid "When `s1` goes out of scope, nothing happens (it has been moved from)." +#: src/methods-and-traits.md +msgid "[Deriving](./methods-and-traits/deriving.md) (5 minutes)" msgstr "" -#: src/ownership/moved-strings-rust.md:14 -msgid "Before move to `s2`:" +#: src/methods-and-traits.md +msgid "[Trait Objects](./methods-and-traits/trait-objects.md) (10 minutes)" msgstr "" -#: src/ownership/moved-strings-rust.md:31 -msgid "After move to `s2`:" +#: src/methods-and-traits.md +msgid "" +"[Exercise: Generic Logger](./methods-and-traits/exercise.md) (20 minutes)" +msgstr "" + +#: src/methods-and-traits.md +msgid "This segment should take about 55 minutes" msgstr "" -#: src/ownership/moved-strings-rust.md:33 +#: src/methods-and-traits/methods.md 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" -"```" +"Rust allows you to associate functions with your new types. You do this with " +"an `impl` block:" msgstr "" -#: src/ownership/double-free-modern-cpp.md:1 -msgid "Defensive Copies in Modern C++" -msgstr "Modern C++'da Savunma Amaçlı Kopyalamalar" +#: src/methods-and-traits/methods.md +msgid "// No receiver, a static method\n" +msgstr "" -#: src/ownership/double-free-modern-cpp.md:3 -msgid "Modern C++ solves this differently:" +#: src/methods-and-traits/methods.md +msgid "// Exclusive borrowed read-write access to self\n" msgstr "" -#: src/ownership/double-free-modern-cpp.md:5 -msgid "" -"```c++\n" -"std::string s1 = \"Cpp\";\n" -"std::string s2 = s1; // Duplicate the data in s1.\n" -"```" +#: src/methods-and-traits/methods.md +msgid "// Shared and read-only borrowed access to self\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." +#: src/methods-and-traits/methods.md +msgid "\"Recorded {} laps for {}:\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:11 -msgid "When `s1` and `s2` go out of scope, they each free their own memory." +#: src/methods-and-traits/methods.md +msgid "\"Lap {idx}: {lap} sec\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:13 -msgid "Before copy-assignment:" +#: src/methods-and-traits/methods.md +msgid "// Exclusive ownership of self\n" msgstr "" -#: src/ownership/double-free-modern-cpp.md:30 -msgid "After copy-assignment:" +#: src/methods-and-traits/methods.md +msgid "\"Race {} is finished, total lap time: {}\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:57 -msgid "" -"C++ has made a slightly different choice than Rust. Because `=` copies data, " -"the string data has to be cloned. Otherwise we would get a double-free when " -"either string goes out of scope." +#: src/methods-and-traits/methods.md +msgid "\"Monaco Grand Prix\"" msgstr "" -#: src/ownership/double-free-modern-cpp.md:61 -msgid "" -"C++ also has [`std::move`](https://en.cppreference.com/w/cpp/utility/move), " -"which is used to indicate when a value may be moved from. If the example had " -"been `s2 = std::move(s1)`, no heap allocation would take place. After the " -"move, `s1` would be in a valid but unspecified state. Unlike Rust, the " -"programmer is allowed to keep using `s1`." +#: src/methods-and-traits/methods.md +msgid "// race.add_lap(42);\n" msgstr "" -#: src/ownership/double-free-modern-cpp.md:66 +#: src/methods-and-traits/methods.md msgid "" -"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " -"which is being copied or moved." +"The `self` arguments specify the \"receiver\" - the object the method acts " +"on. There are several common receivers for a method:" msgstr "" -#: src/ownership/moves-function-calls.md:3 +#: src/methods-and-traits/methods.md msgid "" -"When you pass a value to a function, the value is assigned to the function " -"parameter. This transfers ownership:" +"`&self`: borrows the object from the caller using a shared and immutable " +"reference. The object can be used again afterwards." msgstr "" -#: src/ownership/moves-function-calls.md:6 +#: src/methods-and-traits/methods.md msgid "" -"```rust,editable\n" -"fn say_hello(name: String) {\n" -" println!(\"Hello {name}\")\n" -"}\n" -"\n" -"fn main() {\n" -" let name = String::from(\"Alice\");\n" -" say_hello(name);\n" -" // say_hello(name);\n" -"}\n" -"```" +"`&mut self`: borrows the object from the caller using a unique and mutable " +"reference. The object can be used again afterwards." msgstr "" -#: src/ownership/moves-function-calls.md:20 +#: src/methods-and-traits/methods.md msgid "" -"With the first call to `say_hello`, `main` gives up ownership of `name`. " -"Afterwards, `name` cannot be used anymore within `main`." +"`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/ownership/moves-function-calls.md:21 -msgid "" -"The heap memory allocated for `name` will be freed at the end of the " -"`say_hello` function." +#: src/methods-and-traits/methods.md +msgid "`mut self`: same as above, but the method can mutate the object." msgstr "" -#: src/ownership/moves-function-calls.md:22 +#: src/methods-and-traits/methods.md msgid "" -"`main` can retain ownership if it passes `name` as a reference (`&name`) and " -"if `say_hello` accepts a reference as a parameter." +"No receiver: this becomes a static method on the struct. Typically used to " +"create constructors which are called `new` by convention." msgstr "" -#: src/ownership/moves-function-calls.md:23 -msgid "" -"Alternatively, `main` can pass a clone of `name` in the first call (`name." -"clone()`)." +#: src/methods-and-traits/methods.md +msgid "It can be helpful to introduce methods by comparing them to functions." msgstr "" -#: src/ownership/moves-function-calls.md:24 +#: src/methods-and-traits/methods.md 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." +"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/ownership/copy-clone.md:3 +#: src/methods-and-traits/methods.md msgid "" -"While move semantics are the default, certain types are copied by default:" +"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/ownership/copy-clone.md:15 -msgid "These types implement the `Copy` trait." +#: src/methods-and-traits/methods.md +msgid "Point out the use of the keyword `self`, a method receiver." msgstr "" -#: src/ownership/copy-clone.md:17 -msgid "You can opt-in your own types to use copy semantics:" +#: src/methods-and-traits/methods.md +msgid "" +"Show that it is an abbreviated term for `self: Self` and perhaps show how " +"the struct name could also be used." msgstr "" -#: src/ownership/copy-clone.md:32 -msgid "After the assignment, both `p1` and `p2` own their own data." +#: src/methods-and-traits/methods.md +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/ownership/copy-clone.md:33 -msgid "We can also use `p1.clone()` to explicitly copy the data." +#: src/methods-and-traits/methods.md +msgid "" +"Note how `self` is used like other structs and dot notation can be used to " +"refer to individual fields." msgstr "" -#: src/ownership/copy-clone.md:37 -msgid "Copying and cloning are not the same thing:" +#: src/methods-and-traits/methods.md +msgid "" +"This might be a good time to demonstrate how the `&self` differs from `self` " +"by trying to run `finish` twice." msgstr "" -#: src/ownership/copy-clone.md:39 +#: src/methods-and-traits/methods.md msgid "" -"Copying refers to bitwise copies of memory regions and does not work on " -"arbitrary objects." +"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/ownership/copy-clone.md:40 +#: src/methods-and-traits/traits.md msgid "" -"Copying does not allow for custom logic (unlike copy constructors in C++)." +"Rust lets you abstract over types with traits. They're similar to interfaces:" 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." +#: src/methods-and-traits/traits.md +msgid "\"Oh you're a cutie! What's your name? {}\"" msgstr "" -#: src/ownership/copy-clone.md:42 -msgid "Copying does not work on types that implement the `Drop` trait." +#: src/methods-and-traits/traits.md src/methods-and-traits/trait-objects.md +msgid "\"Woof, my name is {}!\"" msgstr "" -#: src/ownership/copy-clone.md:44 src/ownership/lifetimes-function-calls.md:30 -msgid "In the above example, try the following:" +#: src/methods-and-traits/traits.md src/methods-and-traits/trait-objects.md +msgid "\"Miau!\"" 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." +#: src/methods-and-traits/traits.md src/methods-and-traits/trait-objects.md +msgid "\"Fido\"" msgstr "" -#: src/ownership/copy-clone.md:47 +#: src/methods-and-traits/traits.md msgid "" -"Remove `Copy` from the `derive` attribute. The compiler error is now in the " -"`println!` for `p1`." +"A trait defines a number of methods that types must have in order to " +"implement the trait." msgstr "" -#: src/ownership/copy-clone.md:48 -msgid "Show that it works if you clone `p1` instead." +#: src/methods-and-traits/traits.md +msgid "Traits are implemented in an `impl for { .. }` block." msgstr "" -#: src/ownership/copy-clone.md:50 +#: src/methods-and-traits/traits.md 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." +"Traits may specify pre-implemented (provided) methods and methods that users " +"are required to implement themselves. Provided methods can rely on required " +"methods. In this case, `greet` is provided, and relies on `talk`." msgstr "" -#: src/ownership/borrowing.md:3 +#: src/methods-and-traits/deriving.md msgid "" -"Instead of transferring ownership when calling a function, you can let a " -"function _borrow_ the value:" +"Supported traits can be automatically implemented for your custom types, as " +"follows:" msgstr "" -#: src/ownership/borrowing.md:23 -msgid "The `add` function _borrows_ two points and returns a new point." +#: src/methods-and-traits/deriving.md +msgid "// Default trait adds `default` constructor.\n" msgstr "" -#: src/ownership/borrowing.md:24 -msgid "The caller retains ownership of the inputs." +#: src/methods-and-traits/deriving.md +msgid "// Clone trait adds `clone` method.\n" msgstr "" -#: src/ownership/borrowing.md:28 -msgid "Notes on stack returns:" +#: src/methods-and-traits/deriving.md +msgid "\"EldurScrollz\"" 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:" +#: src/methods-and-traits/deriving.md +msgid "// Debug trait adds support for printing with `{:?}`.\n" msgstr "" -#: src/ownership/borrowing.md:50 -msgid "The Rust compiler can do return value optimization (RVO)." +#: src/methods-and-traits/deriving.md +msgid "\"{:?} vs. {:?}\"" msgstr "" -#: src/ownership/borrowing.md:51 +#: src/methods-and-traits/deriving.md 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." +"Derivation is implemented with macros, and many crates provide useful derive " +"macros to add useful functionality. For example, `serde` can derive " +"serialization support for a struct using `#[derive(Serialize)]`." msgstr "" -#: src/ownership/shared-unique-borrows.md:3 -msgid "Rust puts constraints on the ways you can borrow values:" +#: src/methods-and-traits/trait-objects.md +msgid "" +"Trait objects allow for values of different types, for instance in a " +"collection:" msgstr "" -#: src/ownership/shared-unique-borrows.md:5 -msgid "You can have one or more `&T` values at any given time, _or_" +#: src/methods-and-traits/trait-objects.md +msgid "\"Hello, who are you? {}\"" msgstr "" -#: src/ownership/shared-unique-borrows.md:6 -msgid "You can have exactly one `&mut T` value." +#: src/methods-and-traits/trait-objects.md +msgid "Memory layout after allocating `pets`:" msgstr "" -#: src/ownership/shared-unique-borrows.md:26 +#: src/methods-and-traits/trait-objects.md msgid "" -"The above code does not compile because `a` is borrowed as mutable (through " -"`c`) and as immutable (through `b`) at the same time." +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " +"- -.\n" +": : : :\n" +": pets : : +----+----+----+----" +"+ :\n" +": +-----------+-------+ : : +-----+-----+ .->| F | i | d | o " +"| :\n" +": | ptr | o---+---+-----+-->| o o | o o | | +----+----+----+----" +"+ :\n" +": | len | 2 | : : +-|-|-+-|-|-+ " +"`---------. :\n" +": | capacity | 2 | : : | | | | data " +"| :\n" +": +-----------+-------+ : : | | | | +-------+--|-------" +"+ :\n" +": : : | | | '-->| name | o, 4, 4 " +"| :\n" +": : : | | | | age | 5 " +"| :\n" +"`- - - - - - - - - - - - - -' : | | | +-------+----------" +"+ :\n" +" : | | " +"| :\n" +" : | | | " +"vtable :\n" +" : | | | +----------------------" +"+ :\n" +" : | | '---->| \"::talk\" " +"| :\n" +" : | | +----------------------" +"+ :\n" +" : | " +"| :\n" +" : | | " +"data :\n" +" : | | +-------+-------" +"+ :\n" +" : | '-->| lives | 9 " +"| :\n" +" : | +-------+-------" +"+ :\n" +" : " +"| :\n" +" : | " +"vtable :\n" +" : | +----------------------" +"+ :\n" +" : '---->| \"::talk\" " +"| :\n" +" : +----------------------" +"+ :\n" +" : :\n" +" '- - - - - - - - - - - - - - - - - - - - - " +"- -'\n" +"```" msgstr "" -#: src/ownership/shared-unique-borrows.md:27 +#: src/methods-and-traits/trait-objects.md msgid "" -"Move the `println!` statement for `b` before the scope that introduces `c` " -"to make the code compile." +"Types that implement a given trait may be of different sizes. This makes it " +"impossible to have things like `Vec` in the example above." msgstr "" -#: src/ownership/shared-unique-borrows.md:28 +#: src/methods-and-traits/trait-objects.md 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`." +"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " +"implements `Pet`." msgstr "" -#: src/ownership/lifetimes.md:7 src/ownership/lifetimes-function-calls.md:24 +#: src/methods-and-traits/trait-objects.md msgid "" -"Read `&'a Point` as \"a borrowed `Point` which is valid for at least the " -"lifetime `a`\"." +"In the example, `pets` is allocated on the stack and the vector data is on " +"the heap. The two vector elements are _fat pointers_:" msgstr "" -#: src/ownership/lifetimes.md:9 +#: src/methods-and-traits/trait-objects.md msgid "" -"Lifetimes are always inferred by the compiler: you cannot assign a lifetime " -"yourself." +"A fat pointer is a double-width pointer. It has two components: a pointer to " +"the actual object and a pointer to the [virtual method table](https://en." +"wikipedia.org/wiki/Virtual_method_table) (vtable) for the `Pet` " +"implementation of that particular object." msgstr "" -#: src/ownership/lifetimes.md:11 +#: src/methods-and-traits/trait-objects.md msgid "" -"Lifetime annotations create constraints; the compiler verifies that there is " -"a valid solution." +"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " +"has a `lives` field." 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)." +#: src/methods-and-traits/trait-objects.md +msgid "Compare these outputs in the above example:" msgstr "" -#: src/ownership/lifetimes-function-calls.md:3 -msgid "" -"In addition to borrowing its arguments, a function can return a borrowed " -"value:" +#: src/methods-and-traits/trait-objects.md src/std-traits/closures.md +msgid "\"{} {}\"" msgstr "" -#: src/ownership/lifetimes-function-calls.md:22 -msgid "`'a` is a generic parameter, it is inferred by the compiler." +#: src/methods-and-traits/trait-objects.md src/std-traits/exercise.md +#: src/std-traits/solution.md src/modules/exercise.md src/modules/solution.md +#: src/android/build-rules/library.md +#: src/android/interoperability/cpp/rust-bridge.md +#: src/async/pitfalls/cancellation.md +msgid "\"{}\"" msgstr "" -#: src/ownership/lifetimes-function-calls.md:23 -msgid "Lifetimes start with `'` and `'a` is a typical default name." +#: src/methods-and-traits/exercise.md +msgid "" +"Let's design a simple logging utility, using a trait `Logger` with a `log` " +"method. Code which might log its progress can then take an `&impl Logger`. " +"In testing, this might put messages in the test logfile, while in a " +"production build it would send messages to a log server." msgstr "" -#: src/ownership/lifetimes-function-calls.md:26 +#: src/methods-and-traits/exercise.md msgid "" -"The _at least_ part is important when parameters are in different scopes." +"However, the `StderrLogger` given below logs all messages, regardless of " +"verbosity. Your task is to write a `VerbosityFilter` type that will ignore " +"messages above a maximum verbosity." msgstr "" -#: src/ownership/lifetimes-function-calls.md:32 +#: src/methods-and-traits/exercise.md msgid "" -"Move the declaration of `p2` and `p3` into a new scope (`{ ... }`), " -"resulting in the following code:" +"This is a common pattern: a struct wrapping a trait implementation and " +"implementing that same trait, adding behavior in the process. What other " +"kinds of wrappers might be useful in a logging utility?" msgstr "" -#: src/ownership/lifetimes-function-calls.md:52 -msgid "Note how this does not compile since `p3` outlives `p2`." +#: src/methods-and-traits/exercise.md src/methods-and-traits/solution.md +msgid "/// Log a message at the given verbosity level.\n" 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." +#: src/methods-and-traits/exercise.md src/methods-and-traits/solution.md +msgid "\"verbosity={verbosity}: {message}\"" msgstr "" -#: src/ownership/lifetimes-function-calls.md:55 -msgid "Another way to explain it:" +#: src/methods-and-traits/exercise.md src/methods-and-traits/solution.md +msgid "\"FYI\"" 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." +#: src/methods-and-traits/exercise.md src/methods-and-traits/solution.md +msgid "\"Uhoh\"" msgstr "" -#: src/ownership/lifetimes-function-calls.md:58 -msgid "" -"It must have come from one of those two inputs (or from a global variable)." +#: src/methods-and-traits/exercise.md +msgid "// TODO: Define and implement `VerbosityFilter`.\n" 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." +#: src/methods-and-traits/solution.md +msgid "/// Only log messages up to the given verbosity level.\n" msgstr "" -#: src/ownership/lifetimes-data-structures.md:3 -msgid "" -"If a data type stores borrowed data, it must be annotated with a lifetime:" +#: src/generics.md +msgid "[Generic Functions](./generics/generic-functions.md) (5 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Highlight<'doc>(&'doc str);\n" -"\n" -"fn erase(text: String) {\n" -" println!(\"Bye {text}!\");\n" -"}\n" -"\n" -"fn main() {\n" -" let text = String::from(\"The quick brown fox jumps over the lazy dog." -"\");\n" -" let fox = Highlight(&text[4..19]);\n" -" let dog = Highlight(&text[35..43]);\n" -" // erase(text);\n" -" println!(\"{fox:?}\");\n" -" println!(\"{dog:?}\");\n" -"}\n" -"```" +#: src/generics.md +msgid "[Generic Data Types](./generics/generic-data.md) (15 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:25 -msgid "" -"In the above example, the annotation on `Highlight` enforces that the data " -"underlying the contained `&str` lives at least as long as any instance of " -"`Highlight` that uses that data." +#: src/generics.md +msgid "[Trait Bounds](./generics/trait-bounds.md) (10 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:26 -msgid "" -"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " -"the borrow checker throws an error." +#: src/generics.md +msgid "[impl Trait](./generics/impl-trait.md) (5 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:27 -msgid "" -"Types with borrowed data force users to hold on to the original data. This " -"can be useful for creating lightweight views, but it generally makes them " -"somewhat harder to use." +#: src/generics.md +msgid "[Exercise: Generic min](./generics/exercise.md) (10 minutes)" msgstr "" -#: src/ownership/lifetimes-data-structures.md:28 -msgid "When possible, make data structures own their data directly." +#: src/generics.md src/smart-pointers.md src/iterators.md src/error-handling.md +msgid "This segment should take about 45 minutes" msgstr "" -#: src/ownership/lifetimes-data-structures.md:29 +#: src/generics/generic-functions.md 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." +"Rust supports generics, which lets you abstract algorithms or data " +"structures (such as sorting or a binary tree) over the types used or stored." msgstr "" -#: src/structs.md:3 -msgid "Like C and C++, Rust has support for custom structs:" +#: src/generics/generic-functions.md +msgid "/// Pick `even` or `odd` depending on the value of `n`.\n" msgstr "" -#: src/structs.md:5 -msgid "" -"```rust,editable\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"fn main() {\n" -" let mut peter = Person {\n" -" name: String::from(\"Peter\"),\n" -" age: 27,\n" -" };\n" -" println!(\"{} is {} years old\", peter.name, peter.age);\n" -" \n" -" peter.age = 28;\n" -" println!(\"{} is {} years old\", peter.name, peter.age);\n" -" \n" -" let jackie = Person {\n" -" name: String::from(\"Jackie\"),\n" -" ..peter\n" -" };\n" -" println!(\"{} is {} years old\", jackie.name, jackie.age);\n" -"}\n" -"```" +#: src/generics/generic-functions.md +msgid "\"picked a number: {:?}\"" msgstr "" -#: src/structs.md:33 -msgid "Structs work like in C or C++." +#: src/generics/generic-functions.md +msgid "\"picked a tuple: {:?}\"" msgstr "" -#: src/structs.md:34 -msgid "Like in C++, and unlike in C, no typedef is needed to define a type." +#: src/generics/generic-functions.md +msgid "\"dog\"" msgstr "" -#: src/structs.md:35 -msgid "Unlike in C++, there is no inheritance between structs." +#: src/generics/generic-functions.md +msgid "\"cat\"" msgstr "" -#: src/structs.md:36 +#: src/generics/generic-functions.md msgid "" -"Methods are defined in an `impl` block, which we will see in following " -"slides." +"Rust infers a type for T based on the types of the arguments and return " +"value." msgstr "" -#: src/structs.md:37 +#: src/generics/generic-functions.md msgid "" -"This may be a good time to let people know there are different types of " -"structs. " +"This is similar to C++ templates, but Rust partially compiles the generic " +"function immediately, so that function must be valid for all types matching " +"the constraints. For example, try modifying `pick` to return `even + odd` if " +"`n == 0`. Even if only the `pick` instantiation with integers is used, Rust " +"still considers it invalid. C++ would let you do this." msgstr "" -#: src/structs.md:38 +#: src/generics/generic-functions.md 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. " +"Generic code is turned into non-generic code based on the call sites. This " +"is a zero-cost abstraction: you get exactly the same result as if you had " +"hand-coded the data structures without the abstraction." msgstr "" -#: src/structs.md:39 -msgid "" -"The next slide will introduce Tuple structs, used when the field names are " -"not important." +#: src/generics/generic-data.md +msgid "You can use generics to abstract over the concrete field type:" 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." +#: src/generics/generic-data.md +msgid "// fn set_x(&mut self, x: T)\n" msgstr "" -#: src/structs/tuple-structs.md:3 -msgid "If the field names are unimportant, you can use a tuple struct:" +#: src/generics/generic-data.md +msgid "\"{integer:?} and {float:?}\"" msgstr "" -#: src/structs/tuple-structs.md:5 -msgid "" -"```rust,editable\n" -"struct Point(i32, i32);\n" -"\n" -"fn main() {\n" -" let p = Point(17, 23);\n" -" println!(\"({}, {})\", p.0, p.1);\n" -"}\n" -"```" +#: src/generics/generic-data.md +msgid "\"coords: {:?}\"" msgstr "" -#: src/structs/tuple-structs.md:14 -msgid "This is often used for single-field wrappers (called newtypes):" +#: src/generics/generic-data.md +msgid "" +"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " +"redundant?" msgstr "" -#: src/structs/tuple-structs.md:16 +#: src/generics/generic-data.md msgid "" -"```rust,editable,compile_fail\n" -"struct PoundsOfForce(f64);\n" -"struct Newtons(f64);\n" -"\n" -"fn compute_thruster_force() -> PoundsOfForce {\n" -" todo!(\"Ask a rocket scientist at NASA\")\n" -"}\n" -"\n" -"fn set_thruster_force(force: Newtons) {\n" -" // ...\n" -"}\n" -"\n" -"fn main() {\n" -" let force = compute_thruster_force();\n" -" set_thruster_force(force);\n" -"}\n" -"\n" -"```" +"This is because it is a generic implementation section for generic type. " +"They are independently generic." msgstr "" -#: 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:" +#: src/generics/generic-data.md +msgid "It means these methods are defined for any `T`." msgstr "" -#: src/structs/tuple-structs.md:38 -msgid "The number is measured in some units: `Newtons` in the example above." +#: src/generics/generic-data.md +msgid "It is possible to write `impl Point { .. }`." msgstr "" -#: src/structs/tuple-structs.md:39 +#: src/generics/generic-data.md 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)`." +"`Point` is still generic and you can use `Point`, but methods in this " +"block will only be available for `Point`." msgstr "" -#: src/structs/tuple-structs.md:40 +#: src/generics/generic-data.md msgid "" -"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " -"single field in the newtype." +"Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`. Update the " +"code to allow points that have elements of different types, by using two " +"type variables, e.g., `T` and `U`." msgstr "" -#: src/structs/tuple-structs.md:41 +#: src/generics/trait-bounds.md msgid "" -"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " -"for instance using booleans as integers." +"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/structs/tuple-structs.md:42 -msgid "Operator overloading is discussed on Day 3 (generics)." +#: src/generics/trait-bounds.md +msgid "You can do this with `T: Trait` or `impl Trait`:" msgstr "" -#: src/structs/tuple-structs.md:43 -msgid "" -"The example is a subtle reference to the [Mars Climate Orbiter](https://en." -"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." +#: src/generics/trait-bounds.md +msgid "// struct NotClonable;\n" 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:" +#: src/generics/trait-bounds.md +msgid "\"{pair:?}\"" msgstr "" -#: src/structs/field-shorthand.md:6 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"impl Person {\n" -" fn new(name: String, age: u8) -> Person {\n" -" Person { name, age }\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let peter = Person::new(String::from(\"Peter\"), 27);\n" -" println!(\"{peter:?}\");\n" -"}\n" -"```" +#: src/generics/trait-bounds.md +msgid "Try making a `NonClonable` and passing it to `duplicate`." msgstr "" -#: src/structs/field-shorthand.md:27 -msgid "" -"The `new` function could be written using `Self` as a type, as it is " -"interchangeable with the struct type name" +#: src/generics/trait-bounds.md +msgid "When multiple traits are necessary, use `+` to join them." msgstr "" -#: src/structs/field-shorthand.md:41 -msgid "" -"Implement the `Default` trait for the struct. Define some fields and use the " -"default values for the other fields." +#: src/generics/trait-bounds.md +msgid "Show a `where` clause, students will encounter it when reading code." msgstr "" -#: src/structs/field-shorthand.md:43 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"impl Default for Person {\n" -" fn default() -> Person {\n" -" Person {\n" -" name: \"Bot\".to_string(),\n" -" age: 0,\n" -" }\n" -" }\n" -"}\n" -"fn create_default() {\n" -" let tmp = Person {\n" -" ..Person::default()\n" -" };\n" -" let tmp = Person {\n" -" name: \"Sam\".to_string(),\n" -" ..Person::default()\n" -" };\n" -"}\n" -"```" +#: src/generics/trait-bounds.md +msgid "It declutters the function signature if you have many parameters." msgstr "" -#: src/structs/field-shorthand.md:68 -msgid "Methods are defined in the `impl` block." +#: src/generics/trait-bounds.md +msgid "It has additional features making it more powerful." msgstr "" -#: src/structs/field-shorthand.md:69 +#: src/generics/trait-bounds.md msgid "" -"Use struct update syntax to define a new structure using `peter`. Note that " -"the variable `peter` will no longer be accessible afterwards." +"If someone asks, the extra feature is that the type on the left of \":\" can " +"be arbitrary, like `Option`." msgstr "" -#: src/structs/field-shorthand.md:70 +#: src/generics/trait-bounds.md msgid "" -"Use `{:#?}` when printing structs to request the `Debug` representation." +"Note that Rust does not (yet) support specialization. For example, given the " +"original `duplicate`, it is invalid to add a specialized `duplicate(a: u32)`." msgstr "" -#: src/methods.md:3 +#: src/generics/impl-trait.md msgid "" -"Rust allows you to associate functions with your new types. You do this with " -"an `impl` block:" +"Similar to trait bounds, an `impl Trait` syntax can be used in function " +"arguments and return values:" msgstr "" -#: src/methods.md:6 +#: src/generics/impl-trait.md msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Person {\n" -" name: String,\n" -" age: u8,\n" -"}\n" -"\n" -"impl Person {\n" -" fn say_hello(&self) {\n" -" println!(\"Hello, my name is {}\", self.name);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let peter = Person {\n" -" name: String::from(\"Peter\"),\n" -" age: 27,\n" -" };\n" -" peter.say_hello();\n" -"}\n" -"```" +"// Syntactic sugar for:\n" +"// fn add_42_millions>(x: T) -> i32 {\n" msgstr "" -#: src/methods.md:31 -msgid "It can be helpful to introduce methods by comparing them to functions." +#: src/generics/impl-trait.md +msgid "\"{many}\"" msgstr "" -#: src/methods.md:32 -msgid "" -"Methods are called on an instance of a type (such as a struct or enum), the " -"first parameter represents the instance as `self`." +#: src/generics/impl-trait.md +msgid "\"{many_more}\"" +msgstr "" + +#: src/generics/impl-trait.md +msgid "\"debuggable: {debuggable:?}\"" msgstr "" -#: src/methods.md:33 +#: src/generics/impl-trait.md 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." +"`impl Trait` allows you to work with types which you cannot name. The " +"meaning of `impl Trait` is a bit different in the different positions." msgstr "" -#: src/methods.md:34 -msgid "Point out the use of the keyword `self`, a method receiver." +#: src/generics/impl-trait.md +msgid "" +"For a parameter, `impl Trait` is like an anonymous generic parameter with a " +"trait bound." msgstr "" -#: src/methods.md:35 +#: src/generics/impl-trait.md msgid "" -"Show that it is an abbreviated term for `self: Self` and perhaps show how " -"the struct name could also be used." +"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/methods.md:36 +#: src/generics/impl-trait.md msgid "" -"Explain that `Self` is a type alias for the type the `impl` block is in and " -"can be used elsewhere in the block." +"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/methods.md:37 +#: src/generics/impl-trait.md msgid "" -"Note how `self` is used like other structs and dot notation can be used to " -"refer to individual fields." +"What is the type of `debuggable`? Try `let debuggable: () = ..` to see what " +"the error message shows." msgstr "" -#: src/methods.md:38 +#: src/generics/exercise.md 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." +"In this short exercise, you will implement a generic `min` function that " +"determines the minimum of two values, using a `LessThan` trait." msgstr "" -#: src/methods.md:39 -msgid "We describe the distinction between method receivers next." +#: src/generics/exercise.md src/generics/solution.md +msgid "/// Return true if self is less than other.\n" msgstr "" -#: src/methods/receiver.md:3 -msgid "" -"The `&self` above indicates that the method borrows the object immutably. " -"There are other possible receivers for a method:" +#: src/generics/exercise.md +msgid "// TODO: implement the `min` function used in `main`.\n" 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." +#: src/generics/exercise.md src/generics/solution.md +msgid "\"Shapiro\"" 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." +#: src/generics/exercise.md src/generics/solution.md +msgid "\"Baumann\"" 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." +#: src/welcome-day-2-afternoon.md +msgid "[Standard Library Types](./std-types.md) (1 hour and 10 minutes)" msgstr "" -#: src/methods/receiver.md:14 -msgid "`mut self`: same as above, but the method can mutate the object. " +#: src/welcome-day-2-afternoon.md +msgid "[Standard Library Traits](./std-traits.md) (1 hour and 40 minutes)" 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." +#: src/std-types.md +msgid "[Standard Library](./std-types/std.md) (3 minutes)" 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`." +#: src/std-types.md +msgid "[Documentation](./std-types/docs.md) (5 minutes)" 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." +#: src/std-types.md +msgid "[Option](./std-types/option.md) (10 minutes)" msgstr "" -#: src/methods/example.md:3 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Race {\n" -" name: String,\n" -" laps: Vec,\n" -"}\n" -"\n" -"impl Race {\n" -" fn new(name: &str) -> Race { // No receiver, a static method\n" -" Race { name: String::from(name), laps: Vec::new() }\n" -" }\n" -"\n" -" fn add_lap(&mut self, lap: i32) { // Exclusive borrowed read-write " -"access to self\n" -" self.laps.push(lap);\n" -" }\n" -"\n" -" fn print_laps(&self) { // Shared and read-only borrowed access to self\n" -" println!(\"Recorded {} laps for {}:\", self.laps.len(), self.name);\n" -" for (idx, lap) in self.laps.iter().enumerate() {\n" -" println!(\"Lap {idx}: {lap} sec\");\n" -" }\n" -" }\n" -"\n" -" fn finish(self) { // Exclusive ownership of self\n" -" let total = self.laps.iter().sum::();\n" -" println!(\"Race {} is finished, total lap time: {}\", self.name, " -"total);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut race = Race::new(\"Monaco Grand Prix\");\n" -" race.add_lap(70);\n" -" race.add_lap(68);\n" -" race.print_laps();\n" -" race.add_lap(71);\n" -" race.print_laps();\n" -" race.finish();\n" -" // race.add_lap(42);\n" -"}\n" -"```" +#: src/std-types.md +msgid "[Result](./std-types/result.md) (10 minutes)" msgstr "" -#: src/methods/example.md:47 -msgid "All four methods here use a different method receiver." +#: src/std-types.md +msgid "[String](./std-types/string.md) (10 minutes)" msgstr "" -#: src/methods/example.md:48 -msgid "" -"You can point out how that changes what the function can do with the " -"variable values and if/how it can be used again in `main`." +#: src/std-types.md +msgid "[Vec](./std-types/vec.md) (10 minutes)" +msgstr "" + +#: src/std-types.md +msgid "[HashMap](./std-types/hashmap.md) (10 minutes)" +msgstr "" + +#: src/std-types.md +msgid "[Exercise: Counter](./std-types/exercise.md) (10 minutes)" +msgstr "" + +#: src/std-types.md src/memory-management.md src/slices-and-lifetimes.md +msgid "This segment should take about 1 hour and 10 minutes" msgstr "" -#: src/methods/example.md:49 +#: src/std-types.md msgid "" -"You can showcase the error that appears when trying to call `finish` twice." +"For each of the slides in this section, spend some time reviewing the " +"documentation pages, highlighting some of the more common methods." msgstr "" -#: src/methods/example.md:50 +#: src/std-types/std.md 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." +"Rust comes with a standard library which helps establish a set of common " +"types used by Rust libraries and programs. This way, two libraries can work " +"together smoothly because they both use the same `String` type." msgstr "" -#: src/methods/example.md:51 +#: src/std-types/std.md 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. " +"In fact, Rust contains several layers of the Standard Library: `core`, " +"`alloc` and `std`." msgstr "" -#: src/exercises/day-2/morning.md:1 -msgid "Day 2: Morning Exercises" +#: src/std-types/std.md +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/exercises/day-2/morning.md:3 -msgid "We will look at implementing methods in two contexts:" +#: src/std-types/std.md +msgid "" +"`alloc` includes types which require a global heap allocator, such as `Vec`, " +"`Box` and `Arc`." msgstr "" -#: src/exercises/day-2/morning.md:5 -msgid "Storing books and querying the collection" +#: src/std-types/std.md +msgid "" +"Embedded Rust applications often only use `core`, and sometimes `alloc`." msgstr "" -#: src/exercises/day-2/morning.md:7 -msgid "Keeping track of health statistics for patients" +#: src/std-types/docs.md +msgid "Rust comes with extensive documentation. For example:" msgstr "" -#: src/exercises/day-2/book-library.md:3 +#: src/std-types/docs.md +#, fuzzy msgid "" -"We will learn much more about structs and the `Vec` type tomorrow. For " -"now, you just need to know part of its API:" +"All of the details about [loops](https://doc.rust-lang.org/stable/reference/" +"expressions/loop-expr.html)." msgstr "" +"[çalışma alanları](https://doc.rust-lang.org/cargo/reference/workspaces.html)" -#: src/exercises/day-2/book-library.md:6 +#: src/std-types/docs.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut vec = vec![10, 20];\n" -" vec.push(30);\n" -" let midpoint = vec.len() / 2;\n" -" println!(\"middle value: {}\", vec[midpoint]);\n" -" for item in &vec {\n" -" println!(\"item: {item}\");\n" -" }\n" -"}\n" -"```" +"Primitive types like [`u8`](https://doc.rust-lang.org/stable/std/primitive." +"u8.html)." msgstr "" -#: src/exercises/day-2/book-library.md:18 +#: src/std-types/docs.md msgid "" -"Use this to model a library's book collection. Copy the code below to " -" and update the types to make it compile:" +"Standard library types like [`Option`](https://doc.rust-lang.org/stable/std/" +"option/enum.Option.html) or [`BinaryHeap`](https://doc.rust-lang.org/stable/" +"std/collections/struct.BinaryHeap.html)." +msgstr "" + +#: src/std-types/docs.md +msgid "In fact, you can document your own code:" msgstr "" -#: src/exercises/day-2/book-library.md:21 +#: src/std-types/docs.md msgid "" -"```rust,should_panic\n" -"struct Library {\n" -" books: Vec,\n" -"}\n" -"\n" -"struct Book {\n" -" title: String,\n" -" year: u16,\n" -"}\n" -"\n" -"impl Book {\n" -" // This is a constructor, used below.\n" -" fn new(title: &str, year: u16) -> Book {\n" -" Book {\n" -" title: String::from(title),\n" -" year,\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Implement the methods below. Notice how the `self` parameter\n" -"// changes type to indicate the method's required level of ownership\n" -"// over the object:\n" -"//\n" -"// - `&self` for shared read-only access,\n" -"// - `&mut self` for unique and mutable access,\n" -"// - `self` for unique access by value.\n" -"impl Library {\n" -" fn new() -> Library {\n" -" todo!(\"Initialize and return a `Library` value\")\n" -" }\n" -"\n" -" fn len(&self) -> usize {\n" -" todo!(\"Return the length of `self.books`\")\n" -" }\n" -"\n" -" fn is_empty(&self) -> bool {\n" -" todo!(\"Return `true` if `self.books` is empty\")\n" -" }\n" -"\n" -" fn add_book(&mut self, book: Book) {\n" -" todo!(\"Add a new book to `self.books`\")\n" -" }\n" -"\n" -" fn print_books(&self) {\n" -" todo!(\"Iterate over `self.books` and print each book's title and " -"year\")\n" -" }\n" -"\n" -" fn oldest_book(&self) -> Option<&Book> {\n" -" todo!(\"Return a reference to the oldest book (if any)\")\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut library = Library::new();\n" -"\n" -" println!(\n" -" \"The library is empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -"\n" -" println!(\n" -" \"The library is no longer empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.print_books();\n" -"\n" -" match library.oldest_book() {\n" -" Some(book) => println!(\"The oldest book is {}\", book.title),\n" -" None => println!(\"The library is empty!\"),\n" -" }\n" -"\n" -" println!(\"The library has {} books\", library.len());\n" -" library.print_books();\n" -"}\n" -"```" +"/// 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/exercises/day-2/health-statistics.md:3 +#: src/std-types/docs.md msgid "" -"You're working on implementing a health-monitoring system. As part of that, " -"you need to keep track of users' health statistics." +"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/exercises/day-2/health-statistics.md:6 +#: src/std-types/docs.md 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." +"To document an item from inside the item (such as inside a module), use `//!" +"` or `/*! .. */`, called \"inner doc comments\":" msgstr "" -#: src/exercises/day-2/health-statistics.md:10 +#: src/std-types/docs.md msgid "" -"Copy the code below to and fill in the missing " -"methods:" +"//! This module contains functionality relating to divisibility of " +"integers.\n" msgstr "" -#: src/exercises/day-2/health-statistics.md:13 +#: src/std-types/docs.md msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub struct User {\n" -" name: String,\n" -" age: u32,\n" -" height: f32,\n" -" visit_count: usize,\n" -" last_blood_pressure: Option<(u32, u32)>,\n" -"}\n" -"\n" -"pub struct Measurements {\n" -" height: f32,\n" -" blood_pressure: (u32, u32),\n" -"}\n" -"\n" -"pub struct HealthReport<'a> {\n" -" patient_name: &'a str,\n" -" visit_count: u32,\n" -" height_change: f32,\n" -" blood_pressure_change: Option<(i32, i32)>,\n" -"}\n" -"\n" -"impl User {\n" -" pub fn new(name: String, age: u32, height: f32) -> Self {\n" -" todo!(\"Create a new User instance\")\n" -" }\n" -"\n" -" pub fn name(&self) -> &str {\n" -" todo!(\"Return the user's name\")\n" -" }\n" -"\n" -" pub fn age(&self) -> u32 {\n" -" todo!(\"Return the user's age\")\n" -" }\n" -"\n" -" pub fn height(&self) -> f32 {\n" -" todo!(\"Return the user's height\")\n" -" }\n" -"\n" -" pub fn doctor_visits(&self) -> u32 {\n" -" todo!(\"Return the number of time the user has visited the " -"doctor\")\n" -" }\n" -"\n" -" pub fn set_age(&mut self, new_age: u32) {\n" -" todo!(\"Set the user's age\")\n" -" }\n" -"\n" -" pub fn set_height(&mut self, new_height: f32) {\n" -" todo!(\"Set the user's height\")\n" -" }\n" -"\n" -" pub fn visit_doctor(&mut self, measurements: Measurements) -> " -"HealthReport {\n" -" todo!(\"Update a user's statistics based on measurements from a " -"visit to the doctor\")\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" println!(\"I'm {} and my age is {}\", bob.name(), bob.age());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_height() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.height(), 155.2);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_set_age() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.age(), 32);\n" -" bob.set_age(33);\n" -" assert_eq!(bob.age(), 33);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_visit() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.doctor_visits(), 0);\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (120, 80),\n" -" });\n" -" assert_eq!(report.patient_name, \"Bob\");\n" -" assert_eq!(report.visit_count, 1);\n" -" assert_eq!(report.blood_pressure_change, None);\n" -"\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (115, 76),\n" -" });\n" -"\n" -" assert_eq!(report.visit_count, 2);\n" -" assert_eq!(report.blood_pressure_change, Some((-5, -4)));\n" -"}\n" -"```" +"Show students the generated docs for the `rand` crate at ." msgstr "" -#: src/std.md:3 +#: src/std-types/option.md +#, fuzzy +msgid "Option" +msgstr "İstisnalar" + +#: src/std-types/option.md msgid "" -"Rust comes with a standard library which helps establish a set of common " -"types used by Rust libraries and programs. This way, two libraries can work " -"together smoothly because they both use the same `String` type." +"We have already seen some use of `Option`. It stores either a value of " +"type `T` or nothing. For example, [`String::find`](https://doc.rust-lang.org/" +"stable/std/string/struct.String.html#method.find) returns an `Option`." msgstr "" -#: src/std.md:7 -msgid "The common vocabulary types include:" +#: src/std-types/option.md +msgid "\"Löwe 老虎 Léopard Gepardi\"" msgstr "" -#: src/std.md:9 -msgid "" -"[`Option` and `Result`](std/option-result.md) types: used for optional " -"values and [error handling](error-handling.md)." +#: src/std-types/option.md +msgid "'é'" msgstr "" -#: src/std.md:12 -msgid "[`String`](std/string.md): the default string type used for owned data." +#: src/std-types/option.md +msgid "\"find returned {position:?}\"" msgstr "" -#: src/std.md:14 -msgid "[`Vec`](std/vec.md): a standard extensible vector." +#: src/std-types/option.md +msgid "'Z'" msgstr "" -#: src/std.md:16 -msgid "" -"[`HashMap`](std/hashmap.md): a hash map type with a configurable hashing " -"algorithm." +#: src/std-types/option.md +msgid "\"Character not found\"" msgstr "" -#: src/std.md:19 -msgid "[`Box`](std/box.md): an owned pointer for heap-allocated data." +#: src/std-types/option.md +msgid "`Option` is widely used, not just in the standard library." msgstr "" -#: src/std.md:21 +#: src/std-types/option.md msgid "" -"[`Rc`](std/rc.md): a shared reference-counted pointer for heap-allocated " -"data." +"`unwrap` will return the value in an `Option`, or panic. `expect` is similar " +"but takes an error message." msgstr "" -#: src/std.md:25 +#: src/std-types/option.md msgid "" -"In fact, Rust contains several layers of the Standard Library: `core`, " -"`alloc` and `std`. " +"You can panic on None, but you can't \"accidentally\" forget to check for " +"None." msgstr "" -#: src/std.md:26 +#: src/std-types/option.md msgid "" -"`core` includes the most basic types and functions that don't depend on " -"`libc`, allocator or even the presence of an operating system. " +"It's common to `unwrap`/`expect` all over the place when hacking something " +"together, but production code typically handles `None` in a nicer fashion." msgstr "" -#: src/std.md:28 +#: src/std-types/option.md msgid "" -"`alloc` includes types which require a global heap allocator, such as `Vec`, " -"`Box` and `Arc`." +"The niche optimization means that `Option` often has the same size in " +"memory as `T`." msgstr "" -#: src/std.md:29 -msgid "" -"Embedded Rust applications often only use `core`, and sometimes `alloc`." +#: src/std-types/result.md +msgid "Result" msgstr "" -#: src/std/option-result.md:1 -msgid "`Option` and `Result`" +#: src/std-types/result.md +msgid "" +"`Result` is similar to `Option`, but indicates the success or failure of an " +"operation, each with a different type. This is similar to the `Res` defined " +"in the expression exercise, but generic: `Result` where `T` is used in " +"the `Ok` variant and `E` appears in the `Err` variant." msgstr "" -#: src/std/option-result.md:3 -msgid "The types represent optional data:" +#: src/std-types/result.md +msgid "\"diary.txt\"" msgstr "" -#: src/std/option-result.md:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let numbers = vec![10, 20, 30];\n" -" let first: Option<&i8> = numbers.first();\n" -" println!(\"first: {first:?}\");\n" -"\n" -" let arr: Result<[i8; 3], Vec> = numbers.try_into();\n" -" println!(\"arr: {arr:?}\");\n" -"}\n" -"```" +#: src/std-types/result.md +msgid "\"Dear diary: {contents} ({bytes} bytes)\"" msgstr "" -#: src/std/option-result.md:18 -msgid "`Option` and `Result` are widely used not just in the standard library." +#: src/std-types/result.md +msgid "\"Could not read file content\"" msgstr "" -#: src/std/option-result.md:19 -msgid "`Option<&T>` has zero space overhead compared to `&T`." +#: src/std-types/result.md +msgid "\"The diary could not be opened: {err}\"" msgstr "" -#: src/std/option-result.md:20 +#: src/std-types/result.md msgid "" -"`Result` is the standard type to implement error handling as we will see on " -"Day 3." +"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/std/option-result.md:21 +#: src/std-types/result.md msgid "" -"`try_into` attempts to convert the vector into a fixed-sized array. This can " -"fail:" +"`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/std/option-result.md:22 +#: src/std-types/result.md msgid "" -"If the vector has the right size, `Result::Ok` is returned with the array." +"`Result` is the standard type to implement error handling as we will see on " +"Day 3." msgstr "" -#: src/std/option-result.md:23 -msgid "Otherwise, `Result::Err` is returned with the original vector." -msgstr "" +#: src/std-types/string.md +msgid "String" +msgstr "String" -#: src/std/string.md:3 +#: src/std-types/string.md 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:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut s1 = String::new();\n" -" s1.push_str(\"Hello\");\n" -" println!(\"s1: len = {}, capacity = {}\", s1.len(), s1.capacity());\n" -"\n" -" let mut s2 = String::with_capacity(s1.len() + 1);\n" -" s2.push_str(&s1);\n" -" s2.push('!');\n" -" println!(\"s2: len = {}, capacity = {}\", s2.len(), s2.capacity());\n" -"\n" -" let s3 = String::from(\"🇨🇭\");\n" -" println!(\"s3: len = {}, number of chars = {}\", s3.len(),\n" -" s3.chars().count());\n" -"}\n" -"```" +#: src/std-types/string.md src/std-traits/read-and-write.md +#: src/memory-management/review.md src/testing/unit-tests.md +#: src/concurrency/scoped-threads.md +msgid "\"Hello\"" +msgstr "" + +#: src/std-types/string.md +msgid "\"s1: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/string.md +msgid "'!'" +msgstr "" + +#: src/std-types/string.md +msgid "\"s2: len = {}, capacity = {}\"" msgstr "" -#: src/std/string.md:22 +#: src/std-types/string.md +msgid "\"🇨🇭\"" +msgstr "" + +#: src/std-types/string.md +msgid "\"s3: len = {}, number of chars = {}\"" +msgstr "" + +#: src/std-types/string.md 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 +#: src/std-types/string.md 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 +#: src/std-types/string.md 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 +#: src/std-types/string.md 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 " @@ -6793,203 +6151,196 @@ msgid "" "unicode_segmentation/struct.Graphemes.html)." msgstr "" -#: src/std/string.md:33 +#: src/std-types/string.md msgid "" "When people refer to strings they could either be talking about `&str` or " "`String`." msgstr "" -#: src/std/string.md:34 +#: src/std-types/string.md msgid "" "When a type implements `Deref`, the compiler will let you " "transparently call methods from `T`." msgstr "" -#: src/std/string.md:35 +#: src/std-types/string.md +msgid "" +"We haven't discussed the `Deref` trait yet, so at this point this mostly " +"explains the structure of the sidebar in the documentation." +msgstr "" + +#: src/std-types/string.md 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;`." +#: src/std-types/string.md +msgid "Write and compare `let s3 = s1.deref();` and `let s3 = &*s1;`." msgstr "" -#: src/std/string.md:37 +#: src/std-types/string.md 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 +#: src/std-types/string.md msgid "Compare the different ways to index a `String`:" msgstr "" -#: src/std/string.md:39 +#: src/std-types/string.md 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 +#: src/std-types/string.md 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 "" - -#: src/std/vec.md:3 +#: src/std-types/vec.md msgid "" "[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " "resizable heap-allocated buffer:" msgstr "" -#: src/std/vec.md:5 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut v1 = Vec::new();\n" -" v1.push(42);\n" -" println!(\"v1: len = {}, capacity = {}\", v1.len(), v1.capacity());\n" -"\n" -" let mut v2 = Vec::with_capacity(v1.len() + 1);\n" -" v2.extend(v1.iter());\n" -" v2.push(9999);\n" -" println!(\"v2: len = {}, capacity = {}\", v2.len(), v2.capacity());\n" -"\n" -" // Canonical macro to initialize a vector with elements.\n" -" let mut v3 = vec![0, 0, 1, 2, 3, 4];\n" -"\n" -" // Retain only the even elements.\n" -" v3.retain(|x| x % 2 == 0);\n" -" println!(\"{v3:?}\");\n" -"\n" -" // Remove consecutive duplicates.\n" -" v3.dedup();\n" -" println!(\"{v3:?}\");\n" -"}\n" -"```" +#: src/std-types/vec.md +msgid "\"v1: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/vec.md +msgid "\"v2: len = {}, capacity = {}\"" +msgstr "" + +#: src/std-types/vec.md +msgid "// Canonical macro to initialize a vector with elements.\n" +msgstr "" + +#: src/std-types/vec.md +msgid "// Retain only the even elements.\n" +msgstr "" + +#: src/std-types/vec.md +msgid "\"{v3:?}\"" +msgstr "" + +#: src/std-types/vec.md +msgid "// Remove consecutive duplicates.\n" msgstr "" -#: src/std/vec.md:29 +#: src/std-types/vec.md 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 +#: src/std-types/vec.md msgid "" "`Vec` is a type of collection, along with `String` and `HashMap`. The data " "it contains is stored on the heap. This means the amount of data doesn't " -"need to be known at compile time. It can grow or shrink at runtime." +"need to be known at compile time. It can grow or shrink at runtime." msgstr "" -#: src/std/vec.md:40 +#: src/std-types/vec.md 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 +#: src/std-types/vec.md 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 +#: src/std-types/vec.md 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 +#: src/std-types/vec.md msgid "" -"Show iterating over a vector and mutating the value: `for e in &mut v { *e " -"+= 50; }`" +"Slices are covered on day 3. For now, students only need to know that a " +"value of type `Vec` gives access to all of the documented slice methods, too." msgstr "" -#: src/std/hashmap.md:1 src/bare-metal/no_std.md:46 -msgid "`HashMap`" +#: src/std-types/hashmap.md +msgid "Standard hash map with protection against HashDoS attacks:" msgstr "" -#: src/std/hashmap.md:3 -msgid "Standard hash map with protection against HashDoS attacks:" +#: src/std-types/hashmap.md +msgid "\"Adventures of Huckleberry Finn\"" msgstr "" -#: src/std/hashmap.md:5 -msgid "" -"```rust,editable\n" -"use std::collections::HashMap;\n" -"\n" -"fn main() {\n" -" let mut page_counts = HashMap::new();\n" -" page_counts.insert(\"Adventures of Huckleberry Finn\".to_string(), " -"207);\n" -" page_counts.insert(\"Grimms' Fairy Tales\".to_string(), 751);\n" -" page_counts.insert(\"Pride and Prejudice\".to_string(), 303);\n" -"\n" -" if !page_counts.contains_key(\"Les Misérables\") {\n" -" println!(\"We know about {} books, but not Les Misérables.\",\n" -" page_counts.len());\n" -" }\n" -"\n" -" for book in [\"Pride and Prejudice\", \"Alice's Adventure in " -"Wonderland\"] {\n" -" match page_counts.get(book) {\n" -" Some(count) => println!(\"{book}: {count} pages\"),\n" -" None => println!(\"{book} is unknown.\")\n" -" }\n" -" }\n" -"\n" -" // Use the .entry() method to insert a value if nothing is found.\n" -" for book in [\"Pride and Prejudice\", \"Alice's Adventure in " -"Wonderland\"] {\n" -" let page_count: &mut i32 = page_counts.entry(book.to_string())." -"or_insert(0);\n" -" *page_count += 1;\n" -" }\n" -"\n" -" println!(\"{page_counts:#?}\");\n" -"}\n" -"```" +#: src/std-types/hashmap.md +msgid "\"Grimms' Fairy Tales\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"Pride and Prejudice\"" msgstr "" -#: src/std/hashmap.md:38 +#: src/std-types/hashmap.md +msgid "\"Les Misérables\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"We know about {} books, but not Les Misérables.\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"Alice's Adventure in Wonderland\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"{book}: {count} pages\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"{book} is unknown.\"" +msgstr "" + +#: src/std-types/hashmap.md +msgid "// Use the .entry() method to insert a value if nothing is found.\n" +msgstr "" + +#: src/std-types/hashmap.md +msgid "\"{page_counts:#?}\"" +msgstr "" + +#: src/std-types/hashmap.md msgid "" "`HashMap` is not defined in the prelude and needs to be brought into scope." msgstr "" -#: src/std/hashmap.md:39 +#: src/std-types/hashmap.md 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:41 -msgid "" -"```rust,ignore\n" -" let pc1 = page_counts\n" -" .get(\"Harry Potter and the Sorcerer's Stone\")\n" -" .unwrap_or(&336);\n" -" let pc2 = page_counts\n" -" .entry(\"The Hunger Games\".to_string())\n" -" .or_insert(374);\n" -"```" +#: src/std-types/hashmap.md +msgid "\"Harry Potter and the Sorcerer's Stone\"" msgstr "" -#: src/std/hashmap.md:49 +#: src/std-types/hashmap.md +msgid "\"The Hunger Games\"" +msgstr "" + +#: src/std-types/hashmap.md msgid "Unlike `vec!`, there is unfortunately no standard `hashmap!` macro." msgstr "" -#: src/std/hashmap.md:50 +#: src/std-types/hashmap.md 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-" @@ -6997,36 +6348,26 @@ msgid "" "us to easily initialize a hash map from a literal array:" msgstr "" -#: src/std/hashmap.md:52 -msgid "" -"```rust,ignore\n" -" let page_counts = HashMap::from([\n" -" (\"Harry Potter and the Sorcerer's Stone\".to_string(), 336),\n" -" (\"The Hunger Games\".to_string(), 374),\n" -" ]);\n" -"```" -msgstr "" - -#: src/std/hashmap.md:59 +#: src/std-types/hashmap.md msgid "" "Alternatively HashMap can be built from any `Iterator` which yields key-" "value tuples." msgstr "" -#: src/std/hashmap.md:60 +#: src/std-types/hashmap.md 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 +#: src/std-types/hashmap.md 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 +#: src/std-types/hashmap.md msgid "" "This type has several \"method-specific\" return types, such as `std::" "collections::hash_map::Keys`. These types often appear in searches of the " @@ -7034,1621 +6375,1126 @@ msgid "" "to the `keys` method." msgstr "" -#: src/std/box.md:1 -msgid "`Box`" +#: src/std-types/exercise.md +msgid "" +"In this exercise you will take a very simple data structure and make it " +"generic. It uses a [`std::collections::HashMap`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html) to keep track of which values " +"have been seen and how many times each one has appeared." msgstr "" -#: src/std/box.md:3 +#: src/std-types/exercise.md msgid "" -"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " -"pointer to data on the heap:" +"The initial version of `Counter` is hard coded to only work for `u32` " +"values. Make the struct and its methods generic over the type of value being " +"tracked, that way `Counter` can track any type of value." msgstr "" -#: src/std/box.md:5 +#: src/std-types/exercise.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let five = Box::new(5);\n" -" println!(\"five: {}\", *five);\n" -"}\n" -"```" +"If you finish early, try using the [`entry`](https://doc.rust-lang.org/" +"stable/std/collections/struct.HashMap.html#method.entry) method to halve the " +"number of hash lookups required to implement the `count` method." msgstr "" -#: src/std/box.md:26 +#: src/std-types/exercise.md src/std-types/solution.md 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)." +"/// Counter counts the number of times each value of type T has been seen.\n" msgstr "" -#: src/std/box.md:34 -msgid "" -"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " -"not null. " +#: src/std-types/exercise.md src/std-types/solution.md +msgid "/// Create a new Counter.\n" msgstr "" -#: src/std/box.md:35 -msgid "" -"In the above example, you can even leave out the `*` in the `println!` " -"statement thanks to `Deref`. " +#: src/std-types/exercise.md src/std-types/solution.md +msgid "/// Count an occurrence of the given value.\n" msgstr "" -#: src/std/box.md:36 -msgid "A `Box` can be useful when you:" +#: src/std-types/exercise.md src/std-types/solution.md +msgid "/// Return the number of times the given value has been seen.\n" msgstr "" -#: src/std/box.md:37 -msgid "" -"have a type whose size that can't be known at compile time, but the Rust " -"compiler wants to know an exact size." +#: src/std-types/exercise.md src/std-types/solution.md +msgid "\"saw {} values equal to {}\"" msgstr "" -#: src/std/box.md:38 -msgid "" -"want to transfer ownership of a large amount of data. To avoid copying large " -"amounts of data on the stack, instead store the data on the heap in a `Box` " -"so only the pointer is moved." +#: src/std-types/exercise.md src/std-types/solution.md +msgid "\"apple\"" msgstr "" -#: src/std/box-recursive.md:1 -msgid "Box with Recursive Data Structures" +#: src/std-types/exercise.md src/std-types/solution.md +msgid "\"orange\"" msgstr "" -#: src/std/box-recursive.md:3 -msgid "" -"Recursive data types or data types with dynamic sizes need to use a `Box`:" +#: src/std-types/exercise.md src/std-types/solution.md +msgid "\"got {} apples\"" msgstr "" -#: src/std/box-recursive.md:5 src/std/box-niche.md:3 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"enum List {\n" -" Cons(T, Box>),\n" -" Nil,\n" -"}\n" -"\n" -"fn main() {\n" -" let list: List = List::Cons(1, Box::new(List::Cons(2, Box::" -"new(List::Nil))));\n" -" println!(\"{list:?}\");\n" -"}\n" -"```" +#: src/std-traits.md +msgid "[Comparisons](./std-traits/comparisons.md) (10 minutes)" msgstr "" -#: src/std/box-recursive.md:18 -msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": " -"list : : :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": | Cons | 1 | o--+----+-----+--->| Cons | 2 | o--+--->| Nil | // | // " -"| :\n" -": +------+----+----+ : : +------+----+----+ +------+----+----" -"+ :\n" -": : : :\n" -": : : :\n" -"'- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"```" +#: src/std-traits.md +msgid "[Operators](./std-traits/operators.md) (10 minutes)" msgstr "" -#: 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)." +#: src/std-traits.md +msgid "[From and Into](./std-traits/from-and-into.md) (10 minutes)" msgstr "" -#: src/std/box-recursive.md:36 -msgid "" -"`Box` solves this problem as it has the same size as a regular pointer and " -"just points at the next element of the `List` in the heap." +#: src/std-traits.md +msgid "[Casting](./std-traits/casting.md) (5 minutes)" 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." +#: src/std-traits.md +msgid "[Read and Write](./std-traits/read-and-write.md) (10 minutes)" msgstr "" -#: src/std/box-niche.md:16 -msgid "" -"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This " -"allows the compiler to optimize the memory layout:" +#: src/std-traits.md +msgid "[Default, struct update syntax](./std-traits/default.md) (5 minutes)" msgstr "" -#: src/std/box-niche.md:19 -msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " -"-.\n" -": : : :\n" -": " -"list : : :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": | 1 | o--+-----------+-----+--->| 2 | o--+--->| // | null " -"| :\n" -": +----+----+ : : +----+----+ +----+------" -"+ :\n" -": : : :\n" -": : : :\n" -"`- - - - - - - - - - - - -' '- - - - - - - - - - - - - - - - - - - - - - " -"-'\n" -"```" +#: src/std-traits.md +msgid "[Closures](./std-traits/closures.md) (20 minutes)" msgstr "" -#: src/std/rc.md:1 -msgid "`Rc`" +#: src/std-traits.md +msgid "[Exercise: ROT13](./std-traits/exercise.md) (30 minutes)" msgstr "" -#: src/std/rc.md:3 -msgid "" -"[`Rc`](https://doc.rust-lang.org/std/rc/struct.Rc.html) is a reference-" -"counted shared pointer. Use this when you need to refer to the same data " -"from multiple places:" +#: src/std-traits.md +msgid "This segment should take about 1 hour and 40 minutes" msgstr "" -#: src/std/rc.md:6 +#: src/std-traits.md msgid "" -"```rust,editable\n" -"use std::rc::Rc;\n" -"\n" -"fn main() {\n" -" let mut a = Rc::new(10);\n" -" let mut b = Rc::clone(&a);\n" -"\n" -" println!(\"a: {a}\");\n" -" println!(\"b: {b}\");\n" -"}\n" -"```" +"As with the standard-library types, spend time reviewing the documentation " +"for each trait." msgstr "" -#: src/std/rc.md:18 -msgid "" -"See [`Arc`](../concurrency/shared_state/arc.md) and [`Mutex`](https://doc." -"rust-lang.org/std/sync/struct.Mutex.html) if you are in a multi-threaded " -"context." +#: src/std-traits.md +msgid "This section is long. Take a break midway through." msgstr "" -#: src/std/rc.md:19 +#: src/std-traits/comparisons.md 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." +"These traits support comparisons between values. All traits can be derived " +"for types containing fields that implement these traits." msgstr "" -#: src/std/rc.md:29 -msgid "" -"`Rc`'s count ensures that its contained value is valid for as long as there " -"are references." +#: src/std-traits/comparisons.md +msgid "`PartialEq` and `Eq`" msgstr "" -#: src/std/rc.md:30 -msgid "`Rc` in Rust is like `std::shared_ptr` in C++." +#: src/std-traits/comparisons.md +msgid "" +"`PartialEq` is a partial equivalence relation, with required method `eq` and " +"provided method `ne`. The `==` and `!=` operators will call these methods." msgstr "" -#: src/std/rc.md:31 +#: src/std-traits/comparisons.md 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." +"`Eq` is a full equivalence relation (reflexive, symmetric, and transitive) " +"and implies `PartialEq`. Functions that require full equivalence will use " +"`Eq` as a trait bound." +msgstr "" + +#: src/std-traits/comparisons.md +msgid "`PartialOrd` and `Ord`" msgstr "" -#: src/std/rc.md:32 +#: src/std-traits/comparisons.md msgid "" -"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " -"and returns a mutable reference." +"`PartialOrd` defines a partial ordering, with a `partial_cmp` method. It is " +"used to implement the `<`, `<=`, `>=`, and `>` operators." msgstr "" -#: src/std/rc.md:33 -msgid "Use `Rc::strong_count` to check the reference count." +#: src/std-traits/comparisons.md +msgid "`Ord` is a total ordering, with `cmp` returning `Ordering`." msgstr "" -#: src/std/rc.md:34 +#: src/std-traits/comparisons.md 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)." +"`PartialEq` can be implemented between different types, but `Eq` cannot, " +"because it is reflexive:" msgstr "" -#: src/std/cell.md:1 -msgid "`Cell` and `RefCell`" +#: src/std-traits/comparisons.md +msgid "" +"In practice, it's common to derive these traits, but uncommon to implement " +"them." msgstr "" -#: src/std/cell.md:3 +#: src/std-traits/operators.md 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." +"Operator overloading is implemented via traits in [`std::ops`](https://doc." +"rust-lang.org/std/ops/index.html):" msgstr "" -#: src/std/cell.md:8 -msgid "" -"`Cell` is typically used for simple types, as it requires copying or moving " -"values. More complex interior types typically use `RefCell`, which tracks " -"shared and exclusive references at runtime and panics if they are misused." +#: src/std-traits/operators.md +msgid "\"{:?} + {:?} = {:?}\"" +msgstr "" + +#: src/std-traits/operators.md src/memory-management/drop.md +msgid "Discussion points:" msgstr "" -#: src/std/cell.md:12 +#: src/std-traits/operators.md msgid "" -"```rust,editable\n" -"use std::cell::RefCell;\n" -"use std::rc::Rc;\n" -"\n" -"#[derive(Debug, Default)]\n" -"struct Node {\n" -" value: i64,\n" -" children: Vec>>,\n" -"}\n" -"\n" -"impl Node {\n" -" fn new(value: i64) -> Rc> {\n" -" Rc::new(RefCell::new(Node { value, ..Node::default() }))\n" -" }\n" -"\n" -" fn sum(&self) -> i64 {\n" -" self.value + self.children.iter().map(|c| c.borrow().sum()).sum::" -"()\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let root = Node::new(1);\n" -" root.borrow_mut().children.push(Node::new(5));\n" -" let subtree = Node::new(10);\n" -" subtree.borrow_mut().children.push(Node::new(11));\n" -" subtree.borrow_mut().children.push(Node::new(12));\n" -" root.borrow_mut().children.push(subtree);\n" -"\n" -" println!(\"graph: {root:#?}\");\n" -" println!(\"graph sum: {}\", root.borrow().sum());\n" -"}\n" -"```" +"You could implement `Add` for `&Point`. In which situations is that useful?" msgstr "" -#: src/std/cell.md:47 +#: src/std-traits/operators.md 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." +"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " +"the operator is not `Copy`, you should consider overloading the operator for " +"`&T` as well. This avoids unnecessary cloning on the call site." msgstr "" -#: src/std/cell.md:48 +#: src/std-traits/operators.md msgid "" -"To do anything with a Node, you must call a `RefCell` method, usually " -"`borrow` or `borrow_mut`." +"Why is `Output` an associated type? Could it be made a type parameter of the " +"method?" msgstr "" -#: src/std/cell.md:49 +#: src/std-traits/operators.md msgid "" -"Demonstrate that reference loops can be created by adding `root` to `subtree." -"children` (don't try to print it!)." +"Short answer: Function type parameters are controlled by the caller, but " +"associated types (like `Output`) are controlled by the implementer of a " +"trait." msgstr "" -#: src/std/cell.md:50 +#: src/std-traits/operators.md 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'`." +"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/modules.md:3 -msgid "We have seen how `impl` blocks let us namespace functions to a type." +#: src/std-traits/from-and-into.md +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/modules.md:5 -msgid "Similarly, `mod` lets us namespace types and functions:" +#: src/std-traits/from-and-into.md +msgid "\"{s}, {addr}, {one}, {bigger}\"" msgstr "" -#: src/modules.md:7 +#: src/std-traits/from-and-into.md msgid "" -"```rust,editable\n" -"mod foo {\n" -" pub fn do_something() {\n" -" println!(\"In the foo module\");\n" -" }\n" -"}\n" -"\n" -"mod bar {\n" -" pub fn do_something() {\n" -" println!(\"In the bar module\");\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" foo::do_something();\n" -" bar::do_something();\n" -"}\n" -"```" +"[`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/modules.md:28 +#: src/std-traits/from-and-into.md msgid "" -"Packages provide functionality and include a `Cargo.toml` file that " -"describes how to build a bundle of 1+ crates." +"That's why it is common to only implement `From`, as your type will get " +"`Into` implementation too." msgstr "" -#: src/modules.md:29 +#: src/std-traits/from-and-into.md msgid "" -"Crates are a tree of modules, where a binary crate creates an executable and " -"a library crate compiles to a library." +"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/modules.md:30 -msgid "Modules define organization, scope, and are the focus of this section." +#: src/std-traits/casting.md +msgid "" +"Rust has no _implicit_ type conversions, but does support explicit casts " +"with `as`. These generally follow C semantics where those are defined." msgstr "" -#: src/modules/visibility.md:3 -msgid "Modules are a privacy boundary:" +#: src/std-traits/casting.md +msgid "\"as u16: {}\"" msgstr "" -#: src/modules/visibility.md:5 -msgid "Module items are private by default (hides implementation details)." +#: src/std-traits/casting.md +msgid "\"as i16: {}\"" msgstr "" -#: src/modules/visibility.md:6 -msgid "Parent and sibling items are always visible." +#: src/std-traits/casting.md +msgid "\"as u8: {}\"" msgstr "" -#: src/modules/visibility.md:7 +#: src/std-traits/casting.md msgid "" -"In other words, if an item is visible in module `foo`, it's visible in all " -"the descendants of `foo`." +"The results of `as` are _always_ defined in Rust and consistent across " +"platforms. This might not match your intuition for changing sign or casting " +"to a smaller type -- check the docs, and comment for clarity." msgstr "" -#: src/modules/visibility.md:10 +#: src/std-traits/casting.md msgid "" -"```rust,editable\n" -"mod outer {\n" -" fn private() {\n" -" println!(\"outer::private\");\n" -" }\n" -"\n" -" pub fn public() {\n" -" println!(\"outer::public\");\n" -" }\n" -"\n" -" mod inner {\n" -" fn private() {\n" -" println!(\"outer::inner::private\");\n" -" }\n" -"\n" -" pub fn public() {\n" -" println!(\"outer::inner::public\");\n" -" super::private();\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" outer::public();\n" -"}\n" -"```" +"Casting with `as` is a relatively sharp tool that is easy to use " +"incorrectly, and can be a source of subtle bugs as future maintenance work " +"changes the types that are used or the ranges of values in types. Casts are " +"best used only when the intent is to indicate unconditional truncation (e.g. " +"selecting the bottom 32 bits of a `u64` with `as u32`, regardless of what " +"was in the high bits)." msgstr "" -#: src/modules/visibility.md:39 -msgid "Use the `pub` keyword to make modules public." +#: src/std-traits/casting.md +msgid "" +"For infallible casts (e.g. `u32` to `u64`), prefer using `From` or `Into` " +"over `as` to confirm that the cast is in fact infallible. For fallible " +"casts, `TryFrom` and `TryInto` are available when you want to handle casts " +"that fit differently from those that don't." msgstr "" -#: src/modules/visibility.md:41 -msgid "" -"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " -"of public visibility." +#: src/std-traits/casting.md +msgid "Consider taking a break after this slide." msgstr "" -#: src/modules/visibility.md:43 +#: src/std-traits/casting.md msgid "" -"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" -"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." +"`as` is similar to a C++ static cast. Use of `as` in cases where data might " +"be lost is generally discouraged, or at least deserves an explanatory " +"comment." msgstr "" -#: src/modules/visibility.md:44 -msgid "Configuring `pub(crate)` visibility is a common pattern." +#: src/std-traits/casting.md +msgid "This is common in casting integers to `usize` for use as an index." msgstr "" -#: src/modules/visibility.md:45 -msgid "Less commonly, you can give visibility to a specific path." +#: src/std-traits/read-and-write.md +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/modules/visibility.md:46 -msgid "" -"In any case, visibility must be granted to an ancestor module (and all of " -"its descendants)." +#: src/std-traits/read-and-write.md +msgid "b\"foo\\nbar\\nbaz\\n\"" msgstr "" -#: src/modules/paths.md:3 -msgid "Paths are resolved as follows:" +#: src/std-traits/read-and-write.md +msgid "\"lines in slice: {}\"" msgstr "" -#: src/modules/paths.md:5 -msgid "As a relative path:" +#: src/std-traits/read-and-write.md +msgid "\"lines in file: {}\"" msgstr "" -#: src/modules/paths.md:6 -msgid "`foo` or `self::foo` refers to `foo` in the current module," +#: src/std-traits/read-and-write.md +msgid "" +"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " +"you abstract over `u8` sinks:" msgstr "" -#: src/modules/paths.md:7 -msgid "`super::foo` refers to `foo` in the parent module." +#: src/std-traits/read-and-write.md +msgid "\"\\n\"" msgstr "" -#: src/modules/paths.md:9 -msgid "As an absolute path:" +#: src/std-traits/read-and-write.md src/slices-and-lifetimes/str.md +msgid "\"World\"" msgstr "" -#: src/modules/paths.md:10 -msgid "`crate::foo` refers to `foo` in the root of the current crate," +#: src/std-traits/read-and-write.md +msgid "\"Logged: {:?}\"" msgstr "" -#: src/modules/paths.md:11 -msgid "`bar::foo` refers to `foo` in the `bar` crate." +#: src/std-traits/default.md +msgid "The `Default` Trait" msgstr "" -#: src/modules/paths.md:13 +#: src/std-traits/default.md 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:" +"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " +"produces a default value for a type." msgstr "" -#: src/modules/filesystem.md:3 -msgid "" -"Omitting the module content will tell Rust to look for it in another file:" +#: src/std-traits/default.md +msgid "\"John Smith\"" 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`." +#: src/std-traits/default.md +msgid "\"{default_struct:#?}\"" msgstr "" -#: src/modules/filesystem.md:12 -msgid "The `crate` root is in:" +#: src/std-traits/default.md +msgid "\"Y is set!\"" msgstr "" -#: src/modules/filesystem.md:14 -msgid "`src/lib.rs` (for a library crate)" +#: src/std-traits/default.md +msgid "\"{almost_default_struct:#?}\"" msgstr "" -#: src/modules/filesystem.md:15 -msgid "`src/main.rs` (for a binary crate)" +#: src/std-traits/default.md src/slices-and-lifetimes/exercise.md +#: src/slices-and-lifetimes/solution.md +msgid "\"{:#?}\"" msgstr "" -#: src/modules/filesystem.md:17 +#: src/std-traits/default.md 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." +"It can be implemented directly or it can be derived via `#[derive(Default)]`." msgstr "" -#: src/modules/filesystem.md:20 +#: src/std-traits/default.md msgid "" -"```rust,editable,compile_fail\n" -"//! This module implements the garden, including a highly performant " -"germination\n" -"//! implementation.\n" -"\n" -"// Re-export types from this module.\n" -"pub use seeds::SeedPacket;\n" -"pub use garden::Garden;\n" -"\n" -"/// Sow the given seed packets.\n" -"pub fn sow(seeds: Vec) { todo!() }\n" -"\n" -"/// Harvest the produce in the garden that is ready.\n" -"pub fn harvest(garden: &mut Garden) { todo!() }\n" -"```" +"A derived implementation will produce a value where all fields are set to " +"their default values." 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." +#: src/std-traits/default.md +msgid "This means all types in the struct must implement `Default` too." msgstr "" -#: src/modules/filesystem.md:39 +#: src/std-traits/default.md 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." +"Standard Rust types often implement `Default` with reasonable values (e.g. " +"`0`, `\"\"`, etc)." msgstr "" -#: src/modules/filesystem.md:42 -msgid "Deeper nesting can use folders, even if the main module is a file:" +#: src/std-traits/default.md +msgid "The partial struct initialization works nicely with default." msgstr "" -#: src/modules/filesystem.md:52 +#: src/std-traits/default.md msgid "" -"The place rust will look for modules can be changed with a compiler " -"directive:" +"The Rust standard library is aware that types can implement `Default` and " +"provides convenience methods that use it." msgstr "" -#: src/modules/filesystem.md:54 +#: src/std-traits/default.md msgid "" -"```rust,ignore\n" -"#[path = \"some/path.rs\"]\n" -"mod some_module;\n" -"```" +"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/modules/filesystem.md:59 +#: src/std-traits/closures.md 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." +"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/exercises/day-2/afternoon.md:1 -msgid "Day 2: Afternoon Exercises" -msgstr "" +#: src/std-traits/closures.md +#, fuzzy +msgid "\"Calling function on {input}\"" +msgstr "Güvensiz (Unsafe) Fonksiyonları Çağırma" -#: src/exercises/day-2/afternoon.md:3 -msgid "The exercises for this afternoon will focus on strings and iterators." +#: src/std-traits/closures.md +msgid "\"add_3: {}\"" 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." +#: src/std-traits/closures.md +msgid "\"accumulate: {}\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:8 src/bare-metal/no_std.md:28 -msgid "`Iterator`" +#: src/std-traits/closures.md +msgid "\"multiply_sum: {}\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:10 +#: src/std-traits/closures.md 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:" +"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/exercises/day-2/iterators-and-ownership.md:22 +#: src/std-traits/closures.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let v: Vec = vec![10, 20, 30];\n" -" let mut iter = v.iter();\n" -"\n" -" println!(\"v[0]: {:?}\", iter.next());\n" -" println!(\"v[1]: {:?}\", iter.next());\n" -" println!(\"v[2]: {:?}\", iter.next());\n" -" println!(\"No more items: {:?}\", iter.next());\n" -"}\n" -"```" +"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " +"multiple times, but not concurrently." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:34 -msgid "What is the type returned by the iterator? Test your answer here:" +#: src/std-traits/closures.md +msgid "" +"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " +"might consume captured values." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:36 +#: src/std-traits/closures.md msgid "" -"```rust,editable,compile_fail\n" -"fn main() {\n" -" let v: Vec = vec![10, 20, 30];\n" -" let mut iter = v.iter();\n" -"\n" -" let v0: Option<..> = iter.next();\n" -" println!(\"v0: {v0:?}\");\n" -"}\n" -"```" +"`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/exercises/day-2/iterators-and-ownership.md:46 -msgid "Why is this type used?" +#: src/std-traits/closures.md +msgid "" +"When you define a function that takes a closure, you should take `FnOnce` if " +"you can (i.e. you call it once), or `FnMut` else, and last `Fn`. This allows " +"the most flexibility for the caller." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:48 -msgid "`IntoIterator`" +#: src/std-traits/closures.md +msgid "" +"In contrast, when you have a closure, the most flexible you can have is `Fn` " +"(it can be passed everywhere), then `FnMut`, and lastly `FnOnce`." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:50 +#: src/std-traits/closures.md 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:" +"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " +"`multiply_sum`), depending on what the closure captures." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:62 +#: src/std-traits/closures.md msgid "" -"The syntax here means that every implementation of `IntoIterator` must " -"declare two types:" +"By default, closures will capture by reference if they can. The `move` " +"keyword makes them capture by value." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:65 -msgid "`Item`: the type we iterate over, such as `i8`," +#: src/std-traits/closures.md +msgid "\"Hi\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:66 -msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." +#: src/std-traits/closures.md +msgid "\"there\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:68 +#: src/std-traits/exercise.md msgid "" -"Note that `IntoIter` and `Item` are linked: the iterator must have the same " -"`Item` type, which means that it returns `Option`" +"In this example, you will implement the classic [\"ROT13\" cipher](https://" +"en.wikipedia.org/wiki/ROT13). Copy this code to the playground, and " +"implement the missing bits. Only rotate ASCII alphabetic characters, to " +"ensure the result is still valid UTF-8." msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:71 -msgid "Like before, what is the type returned by the iterator?" +#: src/std-traits/exercise.md +msgid "// Implement the `Read` trait for `RotDecoder`.\n" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:73 -msgid "" -"```rust,editable,compile_fail\n" -"fn main() {\n" -" let v: Vec = vec![String::from(\"foo\"), String::" -"from(\"bar\")];\n" -" let mut iter = v.into_iter();\n" -"\n" -" let v0: Option<..> = iter.next();\n" -" println!(\"v0: {v0:?}\");\n" -"}\n" -"```" +#: src/std-traits/exercise.md src/std-traits/solution.md +msgid "\"Gb trg gb gur bgure fvqr!\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:83 -msgid "`for` Loops" +#: src/std-traits/exercise.md src/std-traits/solution.md +msgid "\"To get to the other side!\"" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:85 +#: src/std-traits/exercise.md 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:" +"What happens if you chain two `RotDecoder` instances together, each rotating " +"by 13 characters?" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:89 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let v: Vec = vec![String::from(\"foo\"), String::" -"from(\"bar\")];\n" -"\n" -" for word in &v {\n" -" println!(\"word: {word}\");\n" -" }\n" -"\n" -" for word in v {\n" -" println!(\"word: {word}\");\n" -" }\n" -"}\n" -"```" +#: src/std-traits/solution.md +msgid "'A'" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:103 -msgid "What is the type of `word` in each loop?" +#: src/welcome-day-3.md +msgid "Welcome to Day 3" msgstr "" -#: src/exercises/day-2/iterators-and-ownership.md:105 -msgid "" -"Experiment with the code above and then consult the documentation for [`impl " -"IntoIterator for &Vec`](https://doc.rust-lang.org/std/vec/struct.Vec." -"html#impl-IntoIterator-for-%26'a+Vec%3CT,+A%3E) and [`impl IntoIterator for " -"Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html#impl-IntoIterator-" -"for-Vec%3CT,+A%3E) to check your answers." +#: src/welcome-day-3.md +msgid "Today, we will cover:" msgstr "" -#: src/exercises/day-2/strings-iterators.md:3 +#: src/welcome-day-3.md 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." +"Memory management, lifetimes, and the borrow checker: how Rust ensures " +"memory safety." 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:" +#: src/welcome-day-3.md +msgid "Smart pointers: standard library pointer types." msgstr "" -#: src/exercises/day-2/strings-iterators.md:12 -msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub fn prefix_matches(prefix: &str, request_path: &str) -> bool {\n" -" unimplemented!()\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_without_wildcard() {\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/" -"abc-123\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/abc/" -"books\"));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/publishersBooks\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/parent/" -"publishers\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_with_wildcard() {\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/bar/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books/book1\"\n" -" ));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers/*/books\", \"/v1/" -"publishers\"));\n" -" assert!(!prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/booksByAuthor\"\n" -" ));\n" -"}\n" -"```" +#: src/welcome-day-3.md +msgid "[Welcome](./welcome-day-3.md) (3 minutes)" msgstr "" -#: src/welcome-day-3.md:1 -msgid "Welcome to Day 3" +#: src/welcome-day-3.md +msgid "[Memory Management](./memory-management.md) (1 hour and 10 minutes)" msgstr "" -#: src/welcome-day-3.md:3 -msgid "Today, we will cover some more advanced topics of Rust:" +#: src/welcome-day-3.md +msgid "[Smart Pointers](./smart-pointers.md) (45 minutes)" msgstr "" -#: src/welcome-day-3.md:5 +#: src/welcome-day-3.md msgid "" -"Traits: deriving traits, default methods, and important standard library " -"traits." +"Including 10 minute breaks, this session should take about 2 hours and 15 " +"minutes" +msgstr "" + +#: src/memory-management.md +msgid "[Review of Program Memory](./memory-management/review.md) (5 minutes)" msgstr "" -#: src/welcome-day-3.md:8 +#: src/memory-management.md msgid "" -"Generics: generic data types, generic methods, monomorphization, and trait " -"objects." +"[Approaches to Memory Management](./memory-management/approaches.md) (10 " +"minutes)" msgstr "" -#: src/welcome-day-3.md:11 -msgid "Error handling: panics, `Result`, and the try operator `?`." +#: src/memory-management.md +msgid "[Ownership](./memory-management/ownership.md) (5 minutes)" msgstr "" -#: src/welcome-day-3.md:13 -msgid "Testing: unit tests, documentation tests, and integration tests." +#: src/memory-management.md +msgid "[Move Semantics](./memory-management/move.md) (10 minutes)" msgstr "" -#: src/welcome-day-3.md:15 -msgid "" -"Unsafe Rust: raw pointers, static variables, unsafe functions, and extern " -"functions." +#: src/memory-management.md +msgid "[Clone](./memory-management/clone.md) (2 minutes)" 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." +#: src/memory-management.md +msgid "[Copy Types](./memory-management/copy-types.md) (5 minutes)" msgstr "" -#: src/generics/data-types.md:3 -msgid "You can use generics to abstract over the concrete field type:" +#: src/memory-management.md +msgid "[Drop](./memory-management/drop.md) (10 minutes)" msgstr "" -#: src/generics/data-types.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Point {\n" -" x: T,\n" -" y: T,\n" -"}\n" -"\n" -"fn main() {\n" -" let integer = Point { x: 5, y: 10 };\n" -" let float = Point { x: 1.0, y: 4.0 };\n" -" println!(\"{integer:?} and {float:?}\");\n" -"}\n" -"```" -msgstr "" - -#: src/generics/data-types.md:21 -msgid "Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`." +#: src/memory-management.md +msgid "[Exercise: Builder Type](./memory-management/exercise.md) (20 minutes)" msgstr "" -#: src/generics/data-types.md:23 -msgid "Fix the code to allow points that have elements of different types." +#: src/memory-management/review.md +msgid "Programs allocate memory in two ways:" msgstr "" -#: src/generics/methods.md:3 -msgid "You can declare a generic type on your `impl` block:" +#: src/memory-management/review.md +msgid "Stack: Continuous area of memory for local variables." msgstr "" -#: src/generics/methods.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug)]\n" -"struct Point(T, T);\n" -"\n" -"impl Point {\n" -" fn x(&self) -> &T {\n" -" &self.0 // + 10\n" -" }\n" -"\n" -" // fn set_x(&mut self, x: T)\n" -"}\n" -"\n" -"fn main() {\n" -" let p = Point(5, 10);\n" -" println!(\"p.x = {}\", p.x());\n" -"}\n" -"```" +#: src/memory-management/review.md +msgid "Values have fixed sizes known at compile time." msgstr "" -#: src/generics/methods.md:25 -msgid "" -"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " -"redundant?" +#: src/memory-management/review.md +msgid "Extremely fast: just move a stack pointer." msgstr "" -#: src/generics/methods.md:26 -msgid "" -"This is because it is a generic implementation section for generic type. " -"They are independently generic." +#: src/memory-management/review.md +msgid "Easy to manage: follows function calls." msgstr "" -#: src/generics/methods.md:27 -msgid "It means these methods are defined for any `T`." +#: src/memory-management/review.md +msgid "Great memory locality." msgstr "" -#: src/generics/methods.md:28 -msgid "It is possible to write `impl Point { .. }`. " +#: src/memory-management/review.md +msgid "Heap: Storage of values outside of function calls." msgstr "" -#: src/generics/methods.md:29 -msgid "" -"`Point` is still generic and you can use `Point`, but methods in this " -"block will only be available for `Point`." +#: src/memory-management/review.md +msgid "Values have dynamic sizes determined at runtime." msgstr "" -#: src/generics/monomorphization.md:3 -msgid "Generic code is turned into non-generic code based on the call sites:" +#: src/memory-management/review.md +msgid "Slightly slower than the stack: some book-keeping needed." msgstr "" -#: src/generics/monomorphization.md:12 -msgid "behaves as if you wrote" +#: src/memory-management/review.md +msgid "No guarantee of memory locality." msgstr "" -#: src/generics/monomorphization.md:31 +#: src/memory-management/review.md 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." +"Creating a `String` puts fixed-sized metadata on the stack and dynamically " +"sized data, the actual string, on the heap:" msgstr "" -#: src/traits.md:3 +#: src/memory-management/review.md msgid "" -"Rust lets you abstract over types with traits. They're similar to interfaces:" +"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/traits.md:5 +#: src/memory-management/review.md msgid "" -"```rust,editable\n" -"struct Dog { name: String, age: i8 }\n" -"struct Cat { lives: i8 } // No name needed, cats won't respond anyway.\n" -"\n" -"trait Pet {\n" -" fn talk(&self) -> String;\n" -"}\n" -"\n" -"impl Pet for Dog {\n" -" fn talk(&self) -> String { format!(\"Woof, my name is {}!\", self." -"name) }\n" -"}\n" -"\n" -"impl Pet for Cat {\n" -" fn talk(&self) -> String { String::from(\"Miau!\") }\n" -"}\n" -"\n" -"fn greet(pet: &P) {\n" -" println!(\"Oh you're a cutie! What's your name? {}\", pet.talk());\n" -"}\n" -"\n" -"fn main() {\n" -" let captain_floof = Cat { lives: 9 };\n" -" let fido = Dog { name: String::from(\"Fido\"), age: 5 };\n" -"\n" -" greet(&captain_floof);\n" -" greet(&fido);\n" -"}\n" -"```" +"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/traits/trait-objects.md:3 +#: src/memory-management/review.md msgid "" -"Trait objects allow for values of different types, for instance in a " -"collection:" +"We can inspect the memory layout with `unsafe` Rust. However, you should " +"point out that this is rightfully unsafe!" msgstr "" -#: src/traits/trait-objects.md:5 -msgid "" -"```rust,editable\n" -"struct Dog { name: String, age: i8 }\n" -"struct Cat { lives: i8 } // No name needed, cats won't respond anyway.\n" -"\n" -"trait Pet {\n" -" fn talk(&self) -> String;\n" -"}\n" -"\n" -"impl Pet for Dog {\n" -" fn talk(&self) -> String { format!(\"Woof, my name is {}!\", self." -"name) }\n" -"}\n" -"\n" -"impl Pet for Cat {\n" -" fn talk(&self) -> String { String::from(\"Miau!\") }\n" -"}\n" -"\n" -"fn main() {\n" -" let pets: Vec> = vec![\n" -" Box::new(Cat { lives: 9 }),\n" -" Box::new(Dog { name: String::from(\"Fido\"), age: 5 }),\n" -" ];\n" -" for pet in pets {\n" -" println!(\"Hello, who are you? {}\", pet.talk());\n" -" }\n" -"}\n" -"```" +#: src/memory-management/review.md src/testing/unit-tests.md +msgid "' '" msgstr "" -#: src/traits/trait-objects.md:32 -msgid "Memory layout after allocating `pets`:" +#: src/memory-management/review.md +msgid "\"world\"" msgstr "" -#: src/traits/trait-objects.md:34 +#: src/memory-management/review.md msgid "" -"```bob\n" -" Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " -"- -.\n" -": : : :\n" -": pets : : +----+----+----+----" -"+ :\n" -": +-----------+-------+ : : +-----+-----+ .->| F | i | d | o " -"| :\n" -": | ptr | o---+---+-----+-->| o o | o o | | +----+----+----+----" -"+ :\n" -": | len | 2 | : : +-|-|-+-|-|-+ " -"`---------. :\n" -": | capacity | 2 | : : | | | | data " -"| :\n" -": +-----------+-------+ : : | | | | +-------+--|-------" -"+ :\n" -": : : | | | '-->| name | o, 4, 4 " -"| :\n" -": : : | | | | age | 5 " -"| :\n" -"`- - - - - - - - - - - - - -' : | | | +-------+----------" -"+ :\n" -" : | | " -"| :\n" -" : | | | " -"vtable :\n" -" : | | | +----------------------" -"+ :\n" -" : | | '---->| \"::talk\" " -"| :\n" -" : | | +----------------------" -"+ :\n" -" : | " -"| :\n" -" : | | " -"data :\n" -" : | | +-------+-------" -"+ :\n" -" : | '-->| lives | 9 " -"| :\n" -" : | +-------+-------" -"+ :\n" -" : " -"| :\n" -" : | " -"vtable :\n" -" : | +----------------------" -"+ :\n" -" : '---->| \"::talk\" " -"| :\n" -" : +----------------------" -"+ :\n" -" : :\n" -" '- - - - - - - - - - - - - - - - - - - - - " -"- -'\n" -"```" +"// 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/traits/trait-objects.md:68 -msgid "" -"Types that implement a given trait may be of different sizes. This makes it " -"impossible to have things like `Vec` in the example above." +#: src/memory-management/review.md +msgid "\"ptr = {ptr:#x}, len = {len}, capacity = {capacity}\"" msgstr "" -#: src/traits/trait-objects.md:70 -msgid "" -"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " -"implements `Pet`." +#: src/memory-management/approaches.md +msgid "Traditionally, languages have fallen into two broad categories:" msgstr "" -#: src/traits/trait-objects.md:72 -msgid "" -"In the example, `pets` is allocated on the stack and the vector data is on " -"the heap. The two vector elements are _fat pointers_:" +#: src/memory-management/approaches.md +msgid "Full control via manual memory management: C, C++, Pascal, ..." msgstr "" -#: src/traits/trait-objects.md:74 -msgid "" -"A fat pointer is a double-width pointer. It has two components: a pointer to " -"the actual object and a pointer to the [virtual method table](https://en." -"wikipedia.org/wiki/Virtual_method_table) (vtable) for the `Pet` " -"implementation of that particular object." +#: src/memory-management/approaches.md +msgid "Programmer decides when to allocate or free heap memory." msgstr "" -#: src/traits/trait-objects.md:77 +#: src/memory-management/approaches.md msgid "" -"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " -"has a `lives` field." +"Programmer must determine whether a pointer still points to valid memory." msgstr "" -#: src/traits/trait-objects.md:79 -msgid "Compare these outputs in the above example:" +#: src/memory-management/approaches.md +msgid "Studies show, programmers make mistakes." msgstr "" -#: src/traits/trait-objects.md:80 +#: src/memory-management/approaches.md msgid "" -"```rust,ignore\n" -" println!(\"{} {}\", std::mem::size_of::(), std::mem::size_of::" -"());\n" -" println!(\"{} {}\", std::mem::size_of::<&Dog>(), std::mem::size_of::" -"<&Cat>());\n" -" println!(\"{}\", std::mem::size_of::<&dyn Pet>());\n" -" println!(\"{}\", std::mem::size_of::>());\n" -"```" +"Full safety via automatic memory management at runtime: Java, Python, Go, " +"Haskell, ..." msgstr "" -#: src/traits/deriving-traits.md:3 +#: src/memory-management/approaches.md msgid "" -"Rust derive macros work by automatically generating code that implements the " -"specified traits for a data structure." +"A runtime system ensures that memory is not freed until it can no longer be " +"referenced." msgstr "" -#: src/traits/deriving-traits.md:5 -msgid "You can let the compiler derive a number of traits as follows:" +#: src/memory-management/approaches.md +msgid "" +"Typically implemented with reference counting, garbage collection, or RAII." +msgstr "" + +#: src/memory-management/approaches.md +msgid "Rust offers a new mix:" msgstr "" -#: src/traits/deriving-traits.md:7 +#: src/memory-management/approaches.md msgid "" -"```rust,editable\n" -"#[derive(Debug, Clone, PartialEq, Eq, Default)]\n" -"struct Player {\n" -" name: String,\n" -" strength: u8,\n" -" hit_points: u8,\n" -"}\n" -"\n" -"fn main() {\n" -" let p1 = Player::default();\n" -" let p2 = p1.clone();\n" -" println!(\"Is {:?}\\nequal to {:?}?\\nThe answer is {}!\", &p1, &p2,\n" -" if p1 == p2 { \"yes\" } else { \"no\" });\n" -"}\n" -"```" +"Full control _and_ safety via compile time enforcement of correct memory " +"management." msgstr "" -#: src/traits/default-methods.md:3 -msgid "Traits can implement behavior in terms of other trait methods:" +#: src/memory-management/approaches.md +msgid "It does this with an explicit ownership concept." msgstr "" -#: src/traits/default-methods.md:5 +#: src/memory-management/approaches.md msgid "" -"```rust,editable\n" -"trait Equals {\n" -" fn equals(&self, other: &Self) -> bool;\n" -" fn not_equals(&self, other: &Self) -> bool {\n" -" !self.equals(other)\n" -" }\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct Centimeter(i16);\n" -"\n" -"impl Equals for Centimeter {\n" -" fn equals(&self, other: &Centimeter) -> bool {\n" -" self.0 == other.0\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let a = Centimeter(10);\n" -" let b = Centimeter(20);\n" -" println!(\"{a:?} equals {b:?}: {}\", a.equals(&b));\n" -" println!(\"{a:?} not_equals {b:?}: {}\", a.not_equals(&b));\n" -"}\n" -"```" +"This slide is intended to help students coming from other languages to put " +"Rust in context." msgstr "" -#: src/traits/default-methods.md:32 +#: src/memory-management/approaches.md 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." +"C must manage heap manually with `malloc` and `free`. Common errors include " +"forgetting to call `free`, calling it multiple times for the same pointer, " +"or dereferencing a pointer after the memory it points to has been freed." msgstr "" -#: src/traits/default-methods.md:35 -msgid "Move method `not_equals` to a new trait `NotEquals`." +#: src/memory-management/approaches.md +msgid "" +"C++ has tools like smart pointers (`unique_ptr`, `shared_ptr`) that take " +"advantage of language guarantees about calling destructors to ensure memory " +"is freed when a function returns. It is still quite easy to mis-use these " +"tools and create similar bugs to C." msgstr "" -#: src/traits/default-methods.md:37 -msgid "Make `Equals` a super trait for `NotEquals`." +#: src/memory-management/approaches.md +msgid "" +"Java, Go, and Python rely on the garbage collector to identify memory that " +"is no longer reachable and discard it. This guarantees that any pointer can " +"be dereferenced, eliminating use-after-free and other classes of bugs. But, " +"GC has a runtime cost and is difficult to tune properly." msgstr "" -#: src/traits/default-methods.md:46 -msgid "Provide a blanket implementation of `NotEquals` for `Equals`." +#: src/memory-management/approaches.md +msgid "" +"Rust's ownership and borrowing model can, in many cases, get the performance " +"of C, with alloc and free operations precisely where they are required -- " +"zero cost. It also provides tools similar to C++'s smart pointers. When " +"required, other options such as reference counting are available, and there " +"are even third-party crates available to support runtime garbage collection " +"(not covered in this class)." msgstr "" -#: src/traits/default-methods.md:58 +#: src/memory-management/ownership.md msgid "" -"With the blanket implementation, you no longer need `Equals` as a super " -"trait for `NotEqual`." +"All variable bindings have a _scope_ where they are valid and it is an error " +"to use a variable outside its scope:" msgstr "" -#: src/traits/trait-bounds.md:3 +#: src/memory-management/ownership.md 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." +"We say that the variable _owns_ the value. Every Rust value has precisely " +"one owner at all times." msgstr "" -#: src/traits/trait-bounds.md:6 -msgid "You can do this with `T: Trait` or `impl Trait`:" +#: src/memory-management/ownership.md +msgid "" +"At the end of the scope, the variable is _dropped_ and the data is freed. A " +"destructor can run here to free up resources." msgstr "" -#: src/traits/trait-bounds.md:8 +#: src/memory-management/ownership.md msgid "" -"```rust,editable\n" -"fn duplicate(a: T) -> (T, T) {\n" -" (a.clone(), a.clone())\n" -"}\n" -"\n" -"// Syntactic sugar for:\n" -"// fn add_42_millions>(x: T) -> i32 {\n" -"fn add_42_millions(x: impl Into) -> i32 {\n" -" x.into() + 42_000_000\n" -"}\n" -"\n" -"// struct NotClonable;\n" -"\n" -"fn main() {\n" -" let foo = String::from(\"foo\");\n" -" let pair = duplicate(foo);\n" -" println!(\"{pair:?}\");\n" -"\n" -" let many = add_42_millions(42_i8);\n" -" println!(\"{many}\");\n" -" let many_more = add_42_millions(10_000_000);\n" -" println!(\"{many_more}\");\n" -"}\n" -"```" +"Students familiar with garbage-collection implementations will know that a " +"garbage collector starts with a set of \"roots\" to find all reachable " +"memory. Rust's \"single owner\" principle is a similar idea." msgstr "" -#: src/traits/trait-bounds.md:35 -msgid "Show a `where` clause, students will encounter it when reading code." +#: src/memory-management/move.md +msgid "An assignment will transfer _ownership_ between variables:" msgstr "" -#: src/traits/trait-bounds.md:46 -msgid "It declutters the function signature if you have many parameters." -msgstr "" +#: src/memory-management/move.md +#, fuzzy +msgid "\"Hello!\"" +msgstr "Merhaba Dünya!" -#: src/traits/trait-bounds.md:47 -msgid "It has additional features making it more powerful." +#: src/memory-management/move.md src/slices-and-lifetimes/str.md +msgid "\"s2: {s2}\"" 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`." +#: src/memory-management/move.md +msgid "// println!(\"s1: {s1}\");\n" msgstr "" -#: src/traits/impl-trait.md:1 -msgid "`impl Trait`" +#: src/memory-management/move.md +msgid "The assignment of `s1` to `s2` transfers ownership." msgstr "" -#: src/traits/impl-trait.md:3 -msgid "" -"Similar to trait bounds, an `impl Trait` syntax can be used in function " -"arguments and return values:" +#: src/memory-management/move.md +msgid "When `s1` goes out of scope, nothing happens: it does not own anything." msgstr "" -#: src/traits/impl-trait.md:6 -msgid "" -"```rust,editable\n" -"use std::fmt::Display;\n" -"\n" -"fn get_x(name: impl Display) -> impl Display {\n" -" format!(\"Hello {name}\")\n" -"}\n" -"\n" -"fn main() {\n" -" let x = get_x(\"foo\");\n" -" println!(\"{x}\");\n" -"}\n" -"```" +#: src/memory-management/move.md +msgid "When `s2` goes out of scope, the string data is freed." msgstr "" -#: src/traits/impl-trait.md:19 -msgid "`impl Trait` allows you to work with types which you cannot name." +#: src/memory-management/move.md +msgid "Before move to `s2`:" msgstr "" -#: src/traits/impl-trait.md:23 -msgid "" -"The meaning of `impl Trait` is a bit different in the different positions." +#: src/memory-management/move.md +msgid "After move to `s2`:" msgstr "" -#: src/traits/impl-trait.md:25 +#: src/memory-management/move.md msgid "" -"For a parameter, `impl Trait` is like an anonymous generic parameter with a " -"trait bound." +"```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 "" -#: src/traits/impl-trait.md:27 +#: src/memory-management/move.md 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." +"When you pass a value to a function, the value is assigned to the function " +"parameter. This transfers ownership:" 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::" -">()`." +#: src/memory-management/move.md +msgid "\"Hello {name}\"" 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/memory-management/move.md src/android/interoperability/java.md +#, fuzzy +msgid "\"Alice\"" +msgstr "Dilimler (Slices)" -#: src/traits/important-traits.md:3 -msgid "" -"We will now look at some of the most common traits of the Rust standard " -"library:" +#: src/memory-management/move.md +msgid "// say_hello(name);\n" msgstr "" -#: src/traits/important-traits.md:5 +#: src/memory-management/move.md 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," +"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/traits/important-traits.md:6 +#: src/memory-management/move.md 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," +"It is only the ownership that moves. Whether any machine code is generated " +"to manipulate the data itself is a matter of optimization, and such copies " +"are aggressively optimized away." msgstr "" -#: src/traits/important-traits.md:7 +#: src/memory-management/move.md 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," +"Simple values (such as integers) can be marked `Copy` (see later slides)." 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" +#: src/memory-management/move.md +msgid "In Rust, clones are explicit (by using `clone`)." msgstr "" -#: src/traits/important-traits.md:9 -msgid "" -"[`Drop`](https://doc.rust-lang.org/std/ops/trait.Drop.html) used for " -"defining destructors." +#: src/memory-management/move.md +msgid "In the `say_hello` example:" msgstr "" -#: src/traits/important-traits.md:10 +#: src/memory-management/move.md msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) used " -"to construct a default instance of a type." +"With the first call to `say_hello`, `main` gives up ownership of `name`. " +"Afterwards, `name` cannot be used anymore within `main`." msgstr "" -#: src/traits/iterator.md:1 -msgid "Iterators" +#: src/memory-management/move.md +msgid "" +"The heap memory allocated for `name` will be freed at the end of the " +"`say_hello` function." msgstr "" -#: src/traits/iterator.md:3 +#: src/memory-management/move.md msgid "" -"You can implement the [`Iterator`](https://doc.rust-lang.org/std/iter/trait." -"Iterator.html) trait on your own types:" +"`main` can retain ownership if it passes `name` as a reference (`&name`) and " +"if `say_hello` accepts a reference as a parameter." msgstr "" -#: src/traits/iterator.md:5 +#: src/memory-management/move.md msgid "" -"```rust,editable\n" -"struct Fibonacci {\n" -" curr: u32,\n" -" next: u32,\n" -"}\n" -"\n" -"impl Iterator for Fibonacci {\n" -" type Item = u32;\n" -"\n" -" fn next(&mut self) -> Option {\n" -" let new_next = self.curr + self.next;\n" -" self.curr = self.next;\n" -" self.next = new_next;\n" -" Some(self.curr)\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let fib = Fibonacci { curr: 0, next: 1 };\n" -" for (i, n) in fib.enumerate().take(5) {\n" -" println!(\"fib({i}): {n}\");\n" -" }\n" -"}\n" -"```" +"Alternatively, `main` can pass a clone of `name` in the first call (`name." +"clone()`)." msgstr "" -#: src/traits/iterator.md:32 +#: src/memory-management/move.md 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." +"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/traits/iterator.md:37 -msgid "" -"`IntoIterator` is the trait that makes for loops work. It is implemented by " -"collection types such as `Vec` and references to them such as `&Vec` " -"and `&[T]`. Ranges also implement it. This is why you can iterate over a " -"vector with `for i in some_vec { .. }` but `some_vec.next()` doesn't exist." +#: src/memory-management/move.md +msgid "Defensive Copies in Modern C++" +msgstr "Modern C++'da Savunma Amaçlı Kopyalamalar" + +#: src/memory-management/move.md +msgid "Modern C++ solves this differently:" +msgstr "" + +#: src/memory-management/move.md +msgid "\"Cpp\"" +msgstr "" + +#: src/memory-management/move.md +msgid "// Duplicate the data in s1.\n" msgstr "" -#: src/traits/from-iterator.md:3 +#: src/memory-management/move.md 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)." +"The heap data from `s1` is duplicated and `s2` gets its own independent copy." +msgstr "" + +#: src/memory-management/move.md +msgid "When `s1` and `s2` go out of scope, they each free their own memory." +msgstr "" + +#: src/memory-management/move.md +msgid "Before copy-assignment:" +msgstr "" + +#: src/memory-management/move.md +msgid "After copy-assignment:" msgstr "" -#: src/traits/from-iterator.md:5 +#: src/memory-management/move.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let primes = vec![2, 3, 5, 7];\n" -" let prime_squares = primes\n" -" .into_iter()\n" -" .map(|prime| prime * prime)\n" -" .collect::>();\n" -" println!(\"prime_squares: {prime_squares:?}\");\n" -"}\n" -"```" +"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/traits/from-iterator.md:18 +#: src/memory-management/move.md msgid "" -"`Iterator` implements `fn collect(self) -> B where B: FromIterator, Self: Sized`" +"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/traits/from-iterator.md:24 +#: src/memory-management/move.md msgid "" -"There are also implementations which let you do cool things like convert an " -"`Iterator>` into a `Result, E>`." +"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " +"which is being copied or moved." msgstr "" -#: src/traits/from-into.md:1 -msgid "`From` and `Into`" +#: src/memory-management/clone.md +msgid "Clone" msgstr "" -#: src/traits/from-into.md:3 +#: src/memory-management/clone.md 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:" +"Sometimes you _want_ to make a copy of a value. The `Clone` trait " +"accomplishes this." msgstr "" -#: src/traits/from-into.md:5 +#: src/memory-management/clone.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s = String::from(\"hello\");\n" -" let addr = std::net::Ipv4Addr::from([127, 0, 0, 1]);\n" -" let one = i16::from(true);\n" -" let bigger = i32::from(123i16);\n" -" println!(\"{s}, {addr}, {one}, {bigger}\");\n" -"}\n" -"```" +"The idea of `Clone` is to make it easy to spot where heap allocations are " +"occurring. Look for `.clone()` and a few others like `Vec::new` or `Box::" +"new`." msgstr "" -#: src/traits/from-into.md:15 +#: src/memory-management/clone.md 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:" +"It's common to \"clone your way out\" of problems with the borrow checker, " +"and return later to try to optimize those clones away." msgstr "" -#: src/traits/from-into.md:17 +#: src/memory-management/copy-types.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let s: String = \"hello\".into();\n" -" let addr: std::net::Ipv4Addr = [127, 0, 0, 1].into();\n" -" let one: i16 = true.into();\n" -" let bigger: i32 = 123i16.into();\n" -" println!(\"{s}, {addr}, {one}, {bigger}\");\n" -"}\n" -"```" +"While move semantics are the default, certain types are copied by default:" 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." +#: src/memory-management/copy-types.md +msgid "These types implement the `Copy` trait." 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`." +#: src/memory-management/copy-types.md +msgid "You can opt-in your own types to use copy semantics:" msgstr "" -#: src/traits/read-write.md:1 -msgid "`Read` and `Write`" +#: src/memory-management/copy-types.md +msgid "After the assignment, both `p1` and `p2` own their own data." msgstr "" -#: src/traits/read-write.md:3 +#: src/memory-management/copy-types.md +msgid "We can also use `p1.clone()` to explicitly copy the data." +msgstr "" + +#: src/memory-management/copy-types.md +msgid "Copying and cloning are not the same thing:" +msgstr "" + +#: src/memory-management/copy-types.md 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:" +"Copying refers to bitwise copies of memory regions and does not work on " +"arbitrary objects." msgstr "" -#: src/traits/read-write.md:5 +#: src/memory-management/copy-types.md msgid "" -"```rust,editable\n" -"use std::io::{BufRead, BufReader, Read, Result};\n" -"\n" -"fn count_lines(reader: R) -> usize {\n" -" let buf_reader = BufReader::new(reader);\n" -" buf_reader.lines().count()\n" -"}\n" -"\n" -"fn main() -> Result<()> {\n" -" let slice: &[u8] = b\"foo\\nbar\\nbaz\\n\";\n" -" println!(\"lines in slice: {}\", count_lines(slice));\n" -"\n" -" let file = std::fs::File::open(std::env::current_exe()?)?;\n" -" println!(\"lines in file: {}\", count_lines(file));\n" -" Ok(())\n" -"}\n" -"```" +"Copying does not allow for custom logic (unlike copy constructors in C++)." msgstr "" -#: src/traits/read-write.md:23 +#: src/memory-management/copy-types.md msgid "" -"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " -"you abstract over `u8` sinks:" +"Cloning is a more general operation and also allows for custom behavior by " +"implementing the `Clone` trait." +msgstr "" + +#: src/memory-management/copy-types.md +msgid "Copying does not work on types that implement the `Drop` trait." +msgstr "" + +#: src/memory-management/copy-types.md +msgid "In the above example, try the following:" msgstr "" -#: src/traits/read-write.md:25 +#: src/memory-management/copy-types.md msgid "" -"```rust,editable\n" -"use std::io::{Result, Write};\n" -"\n" -"fn log(writer: &mut W, msg: &str) -> Result<()> {\n" -" writer.write_all(msg.as_bytes())?;\n" -" writer.write_all(\"\\n\".as_bytes())\n" -"}\n" -"\n" -"fn main() -> Result<()> {\n" -" let mut buffer = Vec::new();\n" -" log(&mut buffer, \"Hello\")?;\n" -" log(&mut buffer, \"World\")?;\n" -" println!(\"Logged: {:?}\", buffer);\n" -" Ok(())\n" -"}\n" -"```" +"Add a `String` field to `struct Point`. It will not compile because `String` " +"is not a `Copy` type." +msgstr "" + +#: src/memory-management/copy-types.md +msgid "" +"Remove `Copy` from the `derive` attribute. The compiler error is now in the " +"`println!` for `p1`." +msgstr "" + +#: src/memory-management/copy-types.md +msgid "Show that it works if you clone `p1` instead." msgstr "" -#: src/traits/drop.md:1 +#: src/memory-management/drop.md msgid "The `Drop` Trait" msgstr "" -#: src/traits/drop.md:3 +#: src/memory-management/drop.md 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:5 -msgid "" -"```rust,editable\n" -"struct Droppable {\n" -" name: &'static str,\n" -"}\n" -"\n" -"impl Drop for Droppable {\n" -" fn drop(&mut self) {\n" -" println!(\"Dropping {}\", self.name);\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let a = Droppable { name: \"a\" };\n" -" {\n" -" let b = Droppable { name: \"b\" };\n" -" {\n" -" let c = Droppable { name: \"c\" };\n" -" let d = Droppable { name: \"d\" };\n" -" println!(\"Exiting block B\");\n" -" }\n" -" println!(\"Exiting block A\");\n" -" }\n" -" drop(a);\n" -" println!(\"Exiting main\");\n" -"}\n" -"```" +#: src/memory-management/drop.md +msgid "\"Dropping {}\"" +msgstr "" + +#: src/memory-management/drop.md src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"a\"" +msgstr "" + +#: src/memory-management/drop.md src/testing/googletest.md +msgid "\"b\"" +msgstr "" + +#: src/memory-management/drop.md +msgid "\"c\"" +msgstr "" + +#: src/memory-management/drop.md +msgid "\"d\"" +msgstr "" + +#: src/memory-management/drop.md +msgid "\"Exiting block B\"" +msgstr "" + +#: src/memory-management/drop.md +msgid "\"Exiting block A\"" +msgstr "" + +#: src/memory-management/drop.md +msgid "\"Exiting main\"" msgstr "" -#: src/traits/drop.md:34 +#: src/memory-management/drop.md msgid "Note that `std::mem::drop` is not the same as `std::ops::Drop::drop`." msgstr "" -#: src/traits/drop.md:35 +#: src/memory-management/drop.md msgid "Values are automatically dropped when they go out of scope." msgstr "" -#: src/traits/drop.md:36 +#: src/memory-management/drop.md msgid "" "When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" "drop` implementation will be called." msgstr "" -#: src/traits/drop.md:38 +#: src/memory-management/drop.md msgid "" "All its fields will then be dropped too, whether or not it implements `Drop`." msgstr "" -#: src/traits/drop.md:39 +#: src/memory-management/drop.md 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 " @@ -8656,5480 +7502,8882 @@ msgid "" "values earlier than they would otherwise go out of scope." msgstr "" -#: src/traits/drop.md:42 +#: src/memory-management/drop.md msgid "" "This can be useful for objects that do some work on `drop`: releasing locks, " "closing files, etc." msgstr "" -#: src/traits/drop.md:45 src/traits/operators.md:26 -msgid "Discussion points:" -msgstr "" - -#: src/traits/drop.md:47 +#: src/memory-management/drop.md msgid "Why doesn't `Drop::drop` take `self`?" msgstr "" -#: src/traits/drop.md:48 +#: src/memory-management/drop.md 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 +#: src/memory-management/drop.md msgid "Try replacing `drop(a)` with `a.drop()`." msgstr "" -#: src/traits/default.md:1 -msgid "The `Default` Trait" -msgstr "" - -#: src/traits/default.md:3 +#: src/memory-management/exercise.md msgid "" -"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " -"produces a default value for a type." +"In this example, we will implement a complex data type that owns all of its " +"data. We will use the \"builder pattern\" to support building a new value " +"piece-by-piece, using convenience functions." msgstr "" -#: src/traits/default.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug, Default)]\n" -"struct Derived {\n" -" x: u32,\n" -" y: String,\n" -" z: Implemented,\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct Implemented(String);\n" -"\n" -"impl Default for Implemented {\n" -" fn default() -> Self {\n" -" Self(\"John Smith\".into())\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let default_struct = Derived::default();\n" -" println!(\"{default_struct:#?}\");\n" -"\n" -" let almost_default_struct = Derived {\n" -" y: \"Y is set!\".into(),\n" -" ..Derived::default()\n" -" };\n" -" println!(\"{almost_default_struct:#?}\");\n" -"\n" -" let nothing: Option = None;\n" -" println!(\"{:#?}\", nothing.unwrap_or_default());\n" -"}\n" -"\n" -"```" +#: src/memory-management/exercise.md +msgid "Fill in the missing pieces." msgstr "" -#: src/traits/default.md:40 -msgid "" -"It can be implemented directly or it can be derived via `#[derive(Default)]`." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "/// A representation of a software package.\n" msgstr "" -#: src/traits/default.md:41 +#: src/memory-management/exercise.md src/memory-management/solution.md msgid "" -"A derived implementation will produce a value where all fields are set to " -"their default values." +"/// Return a representation of this package as a dependency, for use in\n" +" /// building other packages.\n" msgstr "" -#: src/traits/default.md:42 -msgid "This means all types in the struct must implement `Default` too." +#: src/memory-management/exercise.md +msgid "\"1\"" msgstr "" -#: src/traits/default.md:43 +#: src/memory-management/exercise.md src/memory-management/solution.md 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." +"/// A builder for a Package. Use `build()` to create the `Package` itself.\n" msgstr "" -#: src/traits/default.md:45 -msgid "" -"Rust standard library is aware that types can implement `Default` and " -"provides convenience methods that use it." +#: src/memory-management/exercise.md +msgid "\"2\"" msgstr "" -#: src/traits/default.md:46 -msgid "" -"the `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" -"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" -"with-struct-update-syntax)" +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "/// Set the package version.\n" msgstr "" -#: src/traits/operators.md:1 -msgid "`Add`, `Mul`, ..." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "/// Set the package authors.\n" msgstr "" -#: src/traits/operators.md:3 -msgid "" -"Operator overloading is implemented via traits in [`std::ops`](https://doc." -"rust-lang.org/std/ops/index.html):" +#: src/memory-management/exercise.md +msgid "\"3\"" msgstr "" -#: src/traits/operators.md:5 -msgid "" -"```rust,editable\n" -"#[derive(Debug, Copy, Clone)]\n" -"struct Point { x: i32, y: i32 }\n" -"\n" -"impl std::ops::Add for Point {\n" -" type Output = Self;\n" -"\n" -" fn add(self, other: Self) -> Self {\n" -" Self {x: self.x + other.x, y: self.y + other.y}\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let p1 = Point { x: 10, y: 20 };\n" -" let p2 = Point { x: 100, y: 200 };\n" -" println!(\"{:?} + {:?} = {:?}\", p1, p2, p1 + p2);\n" -"}\n" -"```" +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "/// Add an additional dependency.\n" msgstr "" -#: src/traits/operators.md:28 -msgid "" -"You could implement `Add` for `&Point`. In which situations is that useful? " +#: src/memory-management/exercise.md +msgid "\"4\"" msgstr "" -#: src/traits/operators.md:29 -msgid "" -"Answer: `Add:add` consumes `self`. If type `T` for which you are overloading " -"the operator is not `Copy`, you should consider overloading the operator for " -"`&T` as well. This avoids unnecessary cloning on the call site." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "/// Set the language. If not set, language defaults to None.\n" msgstr "" -#: src/traits/operators.md:33 -msgid "" -"Why is `Output` an associated type? Could it be made a type parameter of the " -"method?" +#: src/memory-management/exercise.md +msgid "\"5\"" msgstr "" -#: src/traits/operators.md:34 -msgid "" -"Short answer: Function type parameters are controlled by the caller, but " -"associated types (like `Output`) are controlled by the implementor of a " -"trait." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"base64\"" 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`." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"0.13\"" msgstr "" -#: src/traits/closures.md:1 -msgid "Closures" +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"base64: {base64:?}\"" msgstr "" -#: src/traits/closures.md:3 -msgid "" -"Closures or lambda expressions have types which cannot be named. However, " -"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." -"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " -"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"log\"" msgstr "" -#: src/traits/closures.md:8 -msgid "" -"```rust,editable\n" -"fn apply_with_log(func: impl FnOnce(i32) -> i32, input: i32) -> i32 {\n" -" println!(\"Calling function on {input}\");\n" -" func(input)\n" -"}\n" -"\n" -"fn main() {\n" -" let add_3 = |x| x + 3;\n" -" println!(\"add_3: {}\", apply_with_log(add_3, 10));\n" -" println!(\"add_3: {}\", apply_with_log(add_3, 20));\n" -"\n" -" let mut v = Vec::new();\n" -" let mut accumulate = |x: i32| {\n" -" v.push(x);\n" -" v.iter().sum::()\n" -" };\n" -" println!(\"accumulate: {}\", apply_with_log(&mut accumulate, 4));\n" -" println!(\"accumulate: {}\", apply_with_log(&mut accumulate, 5));\n" -"\n" -" let multiply_sum = |x| x * v.into_iter().sum::();\n" -" println!(\"multiply_sum: {}\", apply_with_log(multiply_sum, 3));\n" -"}\n" -"```" +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"0.4\"" msgstr "" -#: src/traits/closures.md:34 -msgid "" -"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " -"perhaps captures nothing at all. It can be called multiple times " -"concurrently." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"log: {log:?}\"" 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." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"serde\"" 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." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"djmitche\"" 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." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"4.0\"" 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." +#: src/memory-management/exercise.md src/memory-management/solution.md +msgid "\"serde: {serde:?}\"" 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." +#: src/memory-management/solution.md +msgid "\"0.1\"" msgstr "" -#: src/traits/closures.md:52 -msgid "" -"```rust,editable\n" -"fn make_greeter(prefix: String) -> impl Fn(&str) {\n" -" return move |name| println!(\"{} {}\", prefix, name)\n" -"}\n" -"\n" -"fn main() {\n" -" let hi = make_greeter(\"Hi\".to_string());\n" -" hi(\"there\");\n" -"}\n" -"```" +#: src/smart-pointers.md +msgid "[Box" msgstr "" -#: src/exercises/day-3/morning.md:1 -msgid "Day 3: Morning Exercises" +#: src/smart-pointers.md +msgid "](./smart-pointers/box.md) (10 minutes)" msgstr "" -#: src/exercises/day-3/morning.md:3 -msgid "We will design a classical GUI library using traits and trait objects." +#: src/smart-pointers.md +msgid "[Rc](./smart-pointers/rc.md) (5 minutes)" msgstr "" -#: src/exercises/day-3/morning.md:5 -msgid "" -"We will also look at enum dispatch with an exercise involving points and " -"polygons." +#: src/smart-pointers.md +msgid "[Exercise: Binary Tree](./smart-pointers/exercise.md) (30 minutes)" msgstr "" -#: src/exercises/day-3/simple-gui.md:1 -#: src/exercises/day-3/solutions-morning.md:3 -msgid "Drawing A Simple GUI" -msgstr "Basit Bir GUI Çizimi" - -#: src/exercises/day-3/simple-gui.md:3 +#: src/smart-pointers/box.md msgid "" -"Let us design a classical GUI library using our new knowledge of traits and " -"trait objects. We'll only implement the drawing of it (as text) for " -"simplicity." +"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " +"pointer to data on the heap:" msgstr "" -#: src/exercises/day-3/simple-gui.md:6 -msgid "We will have a number of widgets in our library:" +#: src/smart-pointers/box.md +msgid "\"five: {}\"" msgstr "" -#: src/exercises/day-3/simple-gui.md:8 -msgid "`Window`: has a `title` and contains other widgets." +#: src/smart-pointers/box.md +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/exercises/day-3/simple-gui.md:9 +#: src/smart-pointers/box.md msgid "" -"`Button`: has a `label`. In reality, it would also take a callback function " -"to allow the program to do something when the button is clicked but we won't " -"include that since we're only drawing the GUI." +"Recursive data types or data types with dynamic sizes need to use a `Box`:" msgstr "" -#: src/exercises/day-3/simple-gui.md:12 -msgid "`Label`: has a `label`." +#: src/smart-pointers/box.md +msgid "/// A non-empty list: first element and the rest of the list.\n" msgstr "" -#: src/exercises/day-3/simple-gui.md:14 -msgid "The widgets will implement a `Widget` trait, see below." +#: src/smart-pointers/box.md +msgid "/// An empty list.\n" msgstr "" -#: src/exercises/day-3/simple-gui.md:16 -msgid "" -"Copy the code below to , fill in the missing " -"`draw_into` methods so that you implement the `Widget` trait:" +#: src/smart-pointers/box.md +msgid "\"{list:?}\"" msgstr "" -#: src/exercises/day-3/simple-gui.md:19 +#: src/smart-pointers/box.md msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_imports, unused_variables, dead_code)]\n" -"\n" -"pub trait Widget {\n" -" /// Natural width of `self`.\n" -" fn width(&self) -> usize;\n" -"\n" -" /// Draw the widget into a buffer.\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write);\n" -"\n" -" /// Draw the widget on standard output.\n" -" fn draw(&self) {\n" -" let mut buffer = String::new();\n" -" self.draw_into(&mut buffer);\n" -" println!(\"{buffer}\");\n" -" }\n" -"}\n" -"\n" -"pub struct Label {\n" -" label: String,\n" -"}\n" -"\n" -"impl Label {\n" -" fn new(label: &str) -> Label {\n" -" Label {\n" -" label: label.to_owned(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Button {\n" -" label: Label,\n" -"}\n" -"\n" -"impl Button {\n" -" fn new(label: &str) -> Button {\n" -" Button {\n" -" label: Label::new(label),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Window {\n" -" title: String,\n" -" widgets: Vec>,\n" -"}\n" -"\n" -"impl Window {\n" -" fn new(title: &str) -> Window {\n" -" Window {\n" -" title: title.to_owned(),\n" -" widgets: Vec::new(),\n" -" }\n" -" }\n" -"\n" -" fn add_widget(&mut self, widget: Box) {\n" -" self.widgets.push(widget);\n" -" }\n" -"\n" -" fn inner_width(&self) -> usize {\n" -" std::cmp::max(\n" -" self.title.chars().count(),\n" -" self.widgets.iter().map(|w| w.width()).max().unwrap_or(0),\n" -" )\n" -" }\n" -"}\n" -"\n" -"\n" -"impl Widget for Label {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Widget for Button {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Widget for Window {\n" -" fn width(&self) -> usize {\n" -" unimplemented!()\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut window = Window::new(\"Rust GUI Demo 1.23\");\n" -" window.add_widget(Box::new(Label::new(\"This is a small text GUI demo." -"\")));\n" -" window.add_widget(Box::new(Button::new(\n" -" \"Click me!\"\n" -" )));\n" -" window.draw();\n" -"}\n" +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - - - - - - - - " +"- - - - -.\n" +": : : :\n" +": " +"list : : :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" +": | Element | 1 | o--+----+-----+--->| Element | 2 | o--+--->| Nil | // " +"| // | :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - - - - - - - - " +"- - - - -'\n" "```" msgstr "" -#: src/exercises/day-3/simple-gui.md:128 -msgid "The output of the above program can be something simple like this:" -msgstr "" - -#: src/exercises/day-3/simple-gui.md:140 +#: src/smart-pointers/box.md 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:" +"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " +"not null." msgstr "" -#: src/exercises/day-3/simple-gui.md:145 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let width = 10;\n" -" println!(\"left aligned: |{:/width$}|\", \"foo\");\n" -"}\n" -"```" +#: src/smart-pointers/box.md +msgid "A `Box` can be useful when you:" msgstr "" -#: src/exercises/day-3/simple-gui.md:154 +#: src/smart-pointers/box.md msgid "" -"Using such alignment tricks, you can for example produce output like this:" +"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/exercises/day-3/points-polygons.md:1 -msgid "Polygon Struct" +#: src/smart-pointers/box.md +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/exercises/day-3/points-polygons.md:3 +#: src/smart-pointers/box.md 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:" +"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/exercises/day-3/points-polygons.md:7 +#: src/smart-pointers/box.md msgid "" -"```rust\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_variables, dead_code)]\n" -"\n" -"pub struct Point {\n" -" // add fields\n" -"}\n" -"\n" -"impl Point {\n" -" // add methods\n" -"}\n" -"\n" -"pub struct Polygon {\n" -" // add fields\n" -"}\n" -"\n" -"impl Polygon {\n" -" // add methods\n" -"}\n" -"\n" -"pub struct Circle {\n" -" // add fields\n" -"}\n" -"\n" -"impl Circle {\n" -" // add methods\n" -"}\n" -"\n" -"pub enum Shape {\n" -" Polygon(Polygon),\n" -" Circle(Circle),\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" fn round_two_digits(x: f64) -> f64 {\n" -" (x * 100.0).round() / 100.0\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_magnitude() {\n" -" let p1 = Point::new(12, 13);\n" -" assert_eq!(round_two_digits(p1.magnitude()), 17.69);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_dist() {\n" -" let p1 = Point::new(10, 10);\n" -" let p2 = Point::new(14, 13);\n" -" assert_eq!(round_two_digits(p1.dist(p2)), 5.00);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_add() {\n" -" let p1 = Point::new(16, 16);\n" -" let p2 = p1 + Point::new(-4, 3);\n" -" assert_eq!(p2, Point::new(12, 19));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_left_most_point() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -" assert_eq!(poly.left_most_point(), Some(p1));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_iter() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -"\n" -" let points = poly.iter().cloned().collect::>();\n" -" assert_eq!(points, vec![Point::new(12, 13), Point::new(16, 16)]);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_shape_perimeters() {\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(Point::new(12, 13));\n" -" poly.add_point(Point::new(17, 11));\n" -" poly.add_point(Point::new(16, 16));\n" -" let shapes = vec![\n" -" Shape::from(poly),\n" -" Shape::from(Circle::new(Point::new(10, 20), 5)),\n" -" ];\n" -" let perimeters = shapes\n" -" .iter()\n" -" .map(Shape::perimeter)\n" -" .map(round_two_digits)\n" -" .collect::>();\n" -" assert_eq!(perimeters, vec![15.48, 31.42]);\n" -" }\n" -"}\n" -"\n" -"#[allow(dead_code)]\n" -"fn main() {}\n" -"```" +"`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/exercises/day-3/points-polygons.md:117 +#: src/smart-pointers/box.md 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." +"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/exercises/day-3/points-polygons.md:120 -msgid "Other interesting parts of the exercise:" -msgstr "" +#: src/smart-pointers/box.md +msgid "Niche Optimization" +msgstr "Niche Optimizasyonu" -#: src/exercises/day-3/points-polygons.md:122 +#: src/smart-pointers/box.md msgid "" -"Derive a `Copy` trait for some structs, as in tests the methods sometimes " -"don't borrow their arguments." +"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/exercises/day-3/points-polygons.md:123 +#: src/smart-pointers/box.md 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." +"```bob\n" +" Stack Heap\n" +".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - -.\n" +": : : :\n" +": list : : :\n" +": +---------+----+----+ : : +---------+----+----+ :\n" +": | Element | 1 | o--+----+-----+--->| Element | 2 | // | :\n" +": +---------+----+----+ : : +---------+----+----+ :\n" +": : : :\n" +": : : :\n" +"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - -'\n" +"```" msgstr "" -#: src/error-handling.md:3 -msgid "Error handling in Rust is done using explicit control flow:" +#: src/smart-pointers/rc.md +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/error-handling.md:5 -msgid "Functions that can have errors list this in their return type," +#: src/smart-pointers/rc.md +msgid "\"a: {a}\"" msgstr "" -#: src/error-handling.md:6 -msgid "There are no exceptions." +#: src/smart-pointers/rc.md +msgid "\"b: {b}\"" msgstr "" -#: src/error-handling/panics.md:3 -msgid "Rust will trigger a panic if a fatal error happens at runtime:" +#: src/smart-pointers/rc.md +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/error-handling/panics.md:5 +#: src/smart-pointers/rc.md msgid "" -"```rust,editable,should_panic\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" println!(\"v[100]: {}\", v[100]);\n" -"}\n" -"```" +"You can _downgrade_ a shared pointer into a [`Weak`](https://doc.rust-lang." +"org/std/rc/struct.Weak.html) pointer to create cycles that will get dropped." msgstr "" -#: src/error-handling/panics.md:12 -msgid "Panics are for unrecoverable and unexpected errors." +#: src/smart-pointers/rc.md +msgid "" +"`Rc`'s count ensures that its contained value is valid for as long as there " +"are references." msgstr "" -#: src/error-handling/panics.md:13 -msgid "Panics are symptoms of bugs in the program." +#: src/smart-pointers/rc.md +msgid "`Rc` in Rust is like `std::shared_ptr` in C++." msgstr "" -#: src/error-handling/panics.md:14 +#: src/smart-pointers/rc.md msgid "" -"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." +"`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/error-handling/panic-unwind.md:1 -msgid "Catching the Stack Unwinding" +#: src/smart-pointers/rc.md +msgid "" +"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " +"and returns a mutable reference." msgstr "" -#: src/error-handling/panic-unwind.md:3 -msgid "" -"By default, a panic will cause the stack to unwind. The unwinding can be " -"caught:" +#: src/smart-pointers/rc.md +msgid "Use `Rc::strong_count` to check the reference count." msgstr "" -#: src/error-handling/panic-unwind.md:5 +#: src/smart-pointers/rc.md msgid "" -"```rust,editable\n" -"use std::panic;\n" -"\n" -"fn main() {\n" -" let result = panic::catch_unwind(|| {\n" -" \"No problem here!\"\n" -" });\n" -" println!(\"{result:?}\");\n" -"\n" -" let result = panic::catch_unwind(|| {\n" -" panic!(\"oh no!\");\n" -" });\n" -" println!(\"{result:?}\");\n" -"}\n" -"```" +"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " +"cycles that will be dropped properly (likely in combination with `RefCell`)." msgstr "" -#: src/error-handling/panic-unwind.md:21 +#: src/smart-pointers/exercise.md msgid "" -"This can be useful in servers which should keep running even if a single " -"request crashes." +"A binary tree is a tree-type data structure where every node has two " +"children (left and right). We will create a tree where each node stores a " +"value. For a given node N, all nodes in a N's left subtree contain smaller " +"values, and all nodes in N's right subtree will contain larger values." msgstr "" -#: src/error-handling/panic-unwind.md:23 -msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." +#: src/smart-pointers/exercise.md +msgid "Implement the following types, so that the given tests pass." msgstr "" -#: src/error-handling/result.md:1 -msgid "Structured Error Handling with `Result`" +#: src/smart-pointers/exercise.md +msgid "" +"Extra Credit: implement an iterator over a binary tree that returns the " +"values in order." 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:" +#: src/smart-pointers/exercise.md src/smart-pointers/solution.md +msgid "/// A node in the binary tree.\n" msgstr "" -#: src/error-handling/result.md:6 -msgid "" -"```rust,editable\n" -"use std::fs;\n" -"use std::io::Read;\n" -"\n" -"fn main() {\n" -" let file = fs::File::open(\"diary.txt\");\n" -" match file {\n" -" Ok(mut file) => {\n" -" let mut contents = String::new();\n" -" file.read_to_string(&mut contents);\n" -" println!(\"Dear diary: {contents}\");\n" -" },\n" -" Err(err) => {\n" -" println!(\"The diary could not be opened: {err}\");\n" -" }\n" -" }\n" -"}\n" -"```" +#: src/smart-pointers/exercise.md src/smart-pointers/solution.md +msgid "/// A possibly-empty subtree.\n" msgstr "" -#: src/error-handling/result.md:27 +#: src/smart-pointers/exercise.md src/smart-pointers/solution.md 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." +"/// A container storing a set of values, using a binary tree.\n" +"///\n" +"/// If the same value is added multiple times, it is only stored once.\n" msgstr "" -#: src/error-handling/result.md:30 -msgid "" -"`Result` documentation is a recommended read. Not during the course, but it " -"is worth mentioning. It contains a lot of convenience methods and functions " -"that help functional-style programming. " +#: src/smart-pointers/exercise.md +msgid "// Implement `new`, `insert`, `len`, and `has`.\n" msgstr "" -#: src/error-handling/try-operator.md:1 -msgid "Propagating Errors with `?`" +#: src/smart-pointers/exercise.md src/smart-pointers/solution.md +msgid "// not a unique item\n" msgstr "" -#: src/error-handling/try-operator.md:3 -msgid "" -"The try-operator `?` is used to return errors to the caller. It lets you " -"turn the common" +#: src/smart-pointers/solution.md src/testing/googletest.md +msgid "\"bar\"" msgstr "" -#: src/error-handling/try-operator.md:13 -msgid "into the much simpler" +#: src/welcome-day-3-afternoon.md +msgid "[Borrowing](./borrowing.md) (1 hour)" msgstr "" -#: src/error-handling/try-operator.md:19 -msgid "We can use this to simplify our error handling code:" +#: src/welcome-day-3-afternoon.md +msgid "" +"[Slices and Lifetimes](./slices-and-lifetimes.md) (1 hour and 10 minutes)" msgstr "" -#: src/error-handling/try-operator.md:21 +#: src/welcome-day-3-afternoon.md msgid "" -"```rust,editable\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let username_file_result = fs::File::open(path);\n" -" let mut username_file = match username_file_result {\n" -" Ok(file) => file,\n" -" Err(err) => return Err(err),\n" -" };\n" -"\n" -" let mut username = String::new();\n" -" match username_file.read_to_string(&mut username) {\n" -" Ok(_) => Ok(username),\n" -" Err(err) => Err(err),\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"alice\").unwrap();\n" -" let username = read_username(\"config.dat\");\n" -" println!(\"username or error: {username:?}\");\n" -"}\n" -"```" +"Including 10 minute breaks, this session should take about 2 hours and 20 " +"minutes" msgstr "" -#: src/error-handling/try-operator.md:50 -#: src/error-handling/converting-error-types-example.md:52 -msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." +#: src/borrowing.md +msgid "[Borrowing a Value](./borrowing/shared.md) (10 minutes)" msgstr "" -#: src/error-handling/try-operator.md:51 -#: src/error-handling/converting-error-types-example.md:53 -msgid "" -"Use the `fs::write` call to test out the different scenarios: no file, empty " -"file, file with username." +#: src/borrowing.md +msgid "[Borrow Checking](./borrowing/borrowck.md) (10 minutes)" msgstr "" -#: src/error-handling/try-operator.md:52 -msgid "" -"The return type of the function has to be compatible with the nested " -"functions it calls. For instance, a function returning a `Result` " -"can only apply the `?` operator on a function returning a `Result`. It cannot apply the `?` operator on a function returning an " -"`Option` or `Result` unless `OtherErr` implements " -"`From`. Reciprocally, a function returning an `Option` can only " -"apply the `?` operator on a function returning an `Option`." +#: src/borrowing.md +msgid "[Interior Mutability](./borrowing/interior-mutability.md) (10 minutes)" 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`." +#: src/borrowing.md +msgid "[Exercise: Health Statistics](./borrowing/exercise.md) (30 minutes)" msgstr "" -#: src/error-handling/converting-error-types.md:3 +#: src/borrowing/shared.md msgid "" -"The effective expansion of `?` is a little more complicated than previously " -"indicated:" +"As we saw before, instead of transferring ownership when calling a function, " +"you can let a function _borrow_ the value:" msgstr "" -#: src/error-handling/converting-error-types.md:9 -msgid "works the same as" +#: src/borrowing/shared.md +msgid "The `add` function _borrows_ two points and returns a new point." 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:" +#: src/borrowing/shared.md +msgid "The caller retains ownership of the inputs." msgstr "" -#: src/error-handling/converting-error-types-example.md:3 +#: src/borrowing/shared.md msgid "" -"```rust,editable\n" -"use std::error::Error;\n" -"use std::fmt::{self, Display, Formatter};\n" -"use std::fs::{self, File};\n" -"use std::io::{self, Read};\n" -"\n" -"#[derive(Debug)]\n" -"enum ReadUsernameError {\n" -" IoError(io::Error),\n" -" EmptyUsername(String),\n" -"}\n" -"\n" -"impl Error for ReadUsernameError {}\n" -"\n" -"impl Display for ReadUsernameError {\n" -" fn fmt(&self, f: &mut Formatter) -> fmt::Result {\n" -" match self {\n" -" Self::IoError(e) => write!(f, \"IO error: {e}\"),\n" -" Self::EmptyUsername(filename) => write!(f, \"Found no username " -"in {filename}\"),\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl From for ReadUsernameError {\n" -" fn from(err: io::Error) -> ReadUsernameError {\n" -" ReadUsernameError::IoError(err)\n" -" }\n" -"}\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::with_capacity(100);\n" -" File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(ReadUsernameError::EmptyUsername(String::from(path)));\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" let username = read_username(\"config.dat\");\n" -" println!(\"username or error: {username:?}\");\n" -"}\n" -"```" +"This slide is a review of the material on references from day 1, expanding " +"slightly to include function arguments and return values." msgstr "" -#: src/error-handling/converting-error-types-example.md:55 -msgid "" -"It is good practice for all error types that don't need to be `no_std` to " -"implement `std::error::Error`, which requires `Debug` and `Display`. The " -"`Error` crate for `core` is only available in [nightly](https://github.com/" -"rust-lang/rust/issues/103765), so not fully `no_std` compatible yet." +#: src/borrowing/shared.md +msgid "Notes on stack returns:" msgstr "" -#: src/error-handling/converting-error-types-example.md:57 +#: src/borrowing/shared.md 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." +"Demonstrate that the return from `add` is cheap because the compiler can " +"eliminate the copy operation. Change the above code to print stack addresses " +"and run it on the [Playground](https://play.rust-lang.org/?" +"version=stable&mode=release&edition=2021&gist=0cb13be1c05d7e3446686ad9947c4671) " +"or look at the assembly in [Godbolt](https://rust.godbolt.org/). In the " +"\"DEBUG\" optimization level, the addresses should change, while they stay " +"the same when changing to the \"RELEASE\" setting:" msgstr "" -#: 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:" +#: src/borrowing/shared.md +msgid "The Rust compiler can do return value optimization (RVO)." msgstr "" -#: src/error-handling/deriving-error-enums.md:6 +#: src/borrowing/shared.md msgid "" -"```rust,editable,compile_fail\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Debug, Error)]\n" -"enum ReadUsernameError {\n" -" #[error(\"Could not read: {0}\")]\n" -" IoError(#[from] io::Error),\n" -" #[error(\"Found no username in {0}\")]\n" -" EmptyUsername(String),\n" -"}\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::new();\n" -" fs::File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(ReadUsernameError::EmptyUsername(String::from(path)));\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err}\"),\n" -" }\n" -"}\n" -"```" +"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/error-handling/deriving-error-enums.md:39 +#: src/borrowing/borrowck.md 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." +"Rust's _borrow checker_ puts constraints on the ways you can borrow values. " +"For a given value, at any time:" msgstr "" -#: src/error-handling/deriving-error-enums.md:43 -msgid "It doesn't affect your public API, which makes it good for libraries." +#: src/borrowing/borrowck.md +msgid "You can have one or more shared references to the value, _or_" msgstr "" -#: src/error-handling/dynamic-errors.md:3 -msgid "" -"Sometimes we want to allow any type of error to be returned without writing " -"our own enum covering all the different possibilities. `std::error::Error` " -"makes this easy." +#: src/borrowing/borrowck.md +msgid "You can have exactly one exclusive reference to the value." msgstr "" -#: src/error-handling/dynamic-errors.md:6 +#: src/borrowing/borrowck.md msgid "" -"```rust,editable,compile_fail\n" -"use std::fs;\n" -"use std::io::Read;\n" -"use thiserror::Error;\n" -"use std::error::Error;\n" -"\n" -"#[derive(Clone, Debug, Eq, Error, PartialEq)]\n" -"#[error(\"Found no username in {0}\")]\n" -"struct EmptyUsernameError(String);\n" -"\n" -"fn read_username(path: &str) -> Result> {\n" -" let mut username = String::new();\n" -" fs::File::open(path)?.read_to_string(&mut username)?;\n" -" if username.is_empty() {\n" -" return Err(EmptyUsernameError(String::from(path)).into());\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err}\"),\n" -" }\n" -"}\n" -"```" +"Note that the requirement is that conflicting references not _exist_ at the " +"same point. It does not matter where the reference is dereferenced." msgstr "" -#: src/error-handling/dynamic-errors.md:36 +#: src/borrowing/borrowck.md 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." +"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/error-handling/error-contexts.md:3 +#: src/borrowing/borrowck.md 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:" +"Move the `println!` statement for `b` before the scope that introduces `c` " +"to make the code compile." msgstr "" -#: src/error-handling/error-contexts.md:7 +#: src/borrowing/borrowck.md msgid "" -"```rust,editable,compile_fail\n" -"use std::{fs, io};\n" -"use std::io::Read;\n" -"use anyhow::{Context, Result, bail};\n" -"\n" -"fn read_username(path: &str) -> Result {\n" -" let mut username = String::with_capacity(100);\n" -" fs::File::open(path)\n" -" .with_context(|| format!(\"Failed to open {path}\"))?\n" -" .read_to_string(&mut username)\n" -" .context(\"Failed to read\")?;\n" -" if username.is_empty() {\n" -" bail!(\"Found no username in {path}\");\n" -" }\n" -" Ok(username)\n" -"}\n" -"\n" -"fn main() {\n" -" //fs::write(\"config.dat\", \"\").unwrap();\n" -" match read_username(\"config.dat\") {\n" -" Ok(username) => println!(\"Username: {username}\"),\n" -" Err(err) => println!(\"Error: {err:?}\"),\n" -" }\n" -"}\n" -"```" +"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/error-handling/error-contexts.md:35 -msgid "`anyhow::Result` is a type alias for `Result`." +#: src/borrowing/borrowck.md +msgid "" +"The exclusive reference constraint is quite strong. Rust uses it to ensure " +"that data races do not occur. Rust also _relies_ on this constraint to " +"optimize code. For example, a value behind a shared reference can be safely " +"cached in a register for the lifetime of that reference." msgstr "" -#: src/error-handling/error-contexts.md:36 +#: src/borrowing/borrowck.md msgid "" -"`anyhow::Error` is essentially a wrapper around `Box`. As such " -"it's again generally not a good choice for the public API of a library, but " -"is widely used in applications." +"The borrow checker is designed to accommodate many common patterns, such as " +"taking exclusive references to different fields in a struct at the same " +"time. But, there are some situations where it doesn't quite \"get it\" and " +"this often results in \"fighting with the borrow checker.\"" msgstr "" -#: src/error-handling/error-contexts.md:38 +#: src/borrowing/interior-mutability.md msgid "" -"Actual error type inside of it can be extracted for examination if necessary." +"In some situations, it's necessary to modify data behind a shared (read-" +"only) reference. For example, a shared data structure might have an internal " +"cache, and wish to update that cache from read-only methods." msgstr "" -#: src/error-handling/error-contexts.md:39 +#: src/borrowing/interior-mutability.md msgid "" -"Functionality provided by `anyhow::Result` may be familiar to Go " -"developers, as it provides similar usage patterns and ergonomics to `(T, " -"error)` from Go." +"The \"interior mutability\" pattern allows exclusive (mutable) access behind " +"a shared reference. The standard library provides several ways to do this, " +"all while still ensuring safety, typically by performing a runtime check." msgstr "" -#: src/testing.md:3 -msgid "Rust and Cargo come with a simple unit test framework:" -msgstr "" +#: src/borrowing/interior-mutability.md +#, fuzzy +msgid "`RefCell`" +msgstr "Cell/RefCell" -#: src/testing.md:5 -msgid "Unit tests are supported throughout your code." +#: src/borrowing/interior-mutability.md +msgid "\"graph: {root:#?}\"" msgstr "" -#: src/testing.md:7 -msgid "Integration tests are supported via the `tests/` directory." +#: src/borrowing/interior-mutability.md +msgid "\"graph sum: {}\"" msgstr "" -#: src/testing/unit-tests.md:3 -msgid "Mark unit tests with `#[test]`:" +#: src/borrowing/interior-mutability.md +msgid "`Cell`" msgstr "" -#: src/testing/unit-tests.md:5 +#: src/borrowing/interior-mutability.md msgid "" -"```rust,editable,ignore\n" -"fn first_word(text: &str) -> &str {\n" -" match text.find(' ') {\n" -" Some(idx) => &text[..idx],\n" -" None => &text,\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty() {\n" -" assert_eq!(first_word(\"\"), \"\");\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_word() {\n" -" assert_eq!(first_word(\"Hello\"), \"Hello\");\n" -"}\n" -"\n" -"#[test]\n" -"fn test_multiple_words() {\n" -" assert_eq!(first_word(\"Hello World\"), \"Hello\");\n" -"}\n" -"```" +"`Cell` wraps a value and allows getting or setting the value, even with a " +"shared reference to the `Cell`. However, it does not allow any references to " +"the value. Since there are no references, borrowing rules cannot be broken." msgstr "" -#: src/testing/unit-tests.md:29 -msgid "Use `cargo test` to find and run the unit tests." +#: src/borrowing/interior-mutability.md +msgid "" +"The main thing to take away from this slide is that Rust provides _safe_ " +"ways to modify data behind a shared reference. There are a variety of ways " +"to ensure that safety, and `RefCell` and `Cell` are two of them." msgstr "" -#: src/testing/test-modules.md:3 +#: src/borrowing/interior-mutability.md msgid "" -"Unit tests are often put in a nested module (run tests on the [Playground]" -"(https://play.rust-lang.org/)):" +"`RefCell` enforces Rust's usual borrowing rules (either multiple shared " +"references or a single exclusive reference) with a runtime check. In this " +"case, all borrows are very short and never overlap, so the checks always " +"succeed." msgstr "" -#: src/testing/test-modules.md:6 +#: src/borrowing/interior-mutability.md msgid "" -"```rust,editable\n" -"fn helper(a: &str, b: &str) -> String {\n" -" format!(\"{a} {b}\")\n" -"}\n" -"\n" -"pub fn main() {\n" -" println!(\"{}\", helper(\"Hello\", \"World\"));\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" #[test]\n" -" fn test_helper() {\n" -" assert_eq!(helper(\"foo\", \"bar\"), \"foo bar\");\n" -" }\n" -"}\n" -"```" +"`Rc` only allows shared (read-only) access to its contents, since its " +"purpose is to allow (and count) many references. But we want to modify the " +"value, so we need interior mutability." msgstr "" -#: src/testing/test-modules.md:26 -msgid "This lets you unit test private helpers." +#: src/borrowing/interior-mutability.md +msgid "" +"`Cell` is a simpler means to ensure safety: it has a `set` method that takes " +"`&self`. This needs no runtime check, but requires moving values, which can " +"have its own cost." msgstr "" -#: src/testing/test-modules.md:27 -msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." +#: src/borrowing/interior-mutability.md +msgid "" +"Demonstrate that reference loops can be created by adding `root` to `subtree." +"children`." msgstr "" -#: src/testing/doc-tests.md:3 -msgid "Rust has built-in support for documentation tests:" +#: src/borrowing/interior-mutability.md +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/testing/doc-tests.md:5 +#: src/borrowing/exercise.md msgid "" -"```rust\n" -"/// Shortens a string to the given length.\n" -"///\n" -"/// ```\n" -"/// # use playground::shorten_string;\n" -"/// assert_eq!(shorten_string(\"Hello World\", 5), \"Hello\");\n" -"/// assert_eq!(shorten_string(\"Hello World\", 20), \"Hello World\");\n" -"/// ```\n" -"pub fn shorten_string(s: &str, length: usize) -> &str {\n" -" &s[..std::cmp::min(length, s.len())]\n" -"}\n" -"```" +"You're working on implementing a health-monitoring system. As part of that, " +"you need to keep track of users' health statistics." msgstr "" -#: src/testing/doc-tests.md:18 -msgid "Code blocks in `///` comments are automatically seen as Rust code." +#: src/borrowing/exercise.md +msgid "" +"You'll start with a stubbed function in an `impl` block as well as a `User` " +"struct definition. Your goal is to implement the stubbed out method on the " +"`User` `struct` defined in the `impl` block." msgstr "" -#: src/testing/doc-tests.md:19 -msgid "The code will be compiled and executed as part of `cargo test`." +#: src/borrowing/exercise.md +msgid "" +"Copy the code below to and fill in the missing " +"method:" msgstr "" -#: src/testing/doc-tests.md:20 +#: src/borrowing/exercise.md msgid "" -"Adding `# ` in the code will hide it from the docs, but will still compile/" -"run it." +"\"Update a user's statistics based on measurements from a visit to the " +"doctor\"" msgstr "" -#: src/testing/doc-tests.md:21 -msgid "" -"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" -"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." +#: src/borrowing/exercise.md src/borrowing/solution.md +#: src/android/build-rules/library.md src/android/aidl/client.md +msgid "\"Bob\"" msgstr "" -#: src/testing/integration-tests.md:3 -msgid "If you want to test your library as a client, use an integration test." +#: src/borrowing/exercise.md src/borrowing/solution.md +msgid "\"I'm {} and my age is {}\"" msgstr "" -#: src/testing/integration-tests.md:5 -msgid "Create a `.rs` file under `tests/`:" +#: src/slices-and-lifetimes.md +msgid "[Slices: &\\[T\\]](./slices-and-lifetimes/slices.md) (10 minutes)" msgstr "" -#: src/testing/integration-tests.md:16 -msgid "These tests only have access to the public API of your crate." +#: src/slices-and-lifetimes.md +msgid "[String References](./slices-and-lifetimes/str.md) (10 minutes)" msgstr "" -#: src/testing/useful-crates.md:1 -msgid "Useful crates for writing tests" +#: src/slices-and-lifetimes.md +msgid "" +"[Lifetime Annotations](./slices-and-lifetimes/lifetime-annotations.md) (10 " +"minutes)" msgstr "" -#: src/testing/useful-crates.md:3 -msgid "Rust comes with only basic support for writing tests." +#: src/slices-and-lifetimes.md +msgid "" +"[Lifetime Elision](./slices-and-lifetimes/lifetime-elision.md) (5 minutes)" msgstr "" -#: src/testing/useful-crates.md:5 -msgid "Here are some additional crates which we recommend for writing tests:" +#: src/slices-and-lifetimes.md +msgid "" +"[Struct Lifetimes](./slices-and-lifetimes/struct-lifetimes.md) (5 minutes)" msgstr "" -#: src/testing/useful-crates.md:7 +#: src/slices-and-lifetimes.md msgid "" -"[googletest](https://docs.rs/googletest): Comprehensive test assertion " -"library in the tradition of GoogleTest for C++." +"[Exercise: Protobuf Parsing](./slices-and-lifetimes/exercise.md) (30 minutes)" msgstr "" -#: src/testing/useful-crates.md:8 -msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." +#: src/slices-and-lifetimes/slices.md +msgid "Slices" +msgstr "Dilimler (Slices)" + +#: src/slices-and-lifetimes/slices.md +msgid "A slice gives you a view into a larger collection:" +msgstr "" + +#: src/slices-and-lifetimes/slices.md +msgid "Slices borrow data from the sliced type." +msgstr "" + +#: src/slices-and-lifetimes/slices.md +msgid "Question: What happens if you modify `a[3]` right before printing `s`?" msgstr "" -#: src/testing/useful-crates.md:9 +#: src/slices-and-lifetimes/slices.md msgid "" -"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " -"tests." +"We create a slice by borrowing `a` and specifying the starting and ending " +"indexes in brackets." msgstr "" -#: src/unsafe.md:3 -msgid "The Rust language has two parts:" +#: src/slices-and-lifetimes/slices.md +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/unsafe.md:5 -msgid "**Safe Rust:** memory safe, no undefined behavior possible." +#: src/slices-and-lifetimes/slices.md +msgid "" +"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " +"identical." msgstr "" -#: src/unsafe.md:6 +#: src/slices-and-lifetimes/slices.md msgid "" -"**Unsafe Rust:** can trigger undefined behavior if preconditions are " -"violated." +"To easily create a slice of the full array, we can therefore use `&a[..]`." msgstr "" -#: src/unsafe.md:8 +#: src/slices-and-lifetimes/slices.md msgid "" -"We will be seeing mostly safe Rust in this course, but it's important to " -"know what Unsafe Rust is." +"`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/unsafe.md:11 +#: src/slices-and-lifetimes/slices.md msgid "" -"Unsafe code is usually small and isolated, and its correctness should be " -"carefully documented. It is usually wrapped in a safe abstraction layer." +"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/unsafe.md:14 -msgid "Unsafe Rust gives you access to five new capabilities:" +#: src/slices-and-lifetimes/slices.md +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." msgstr "" -#: src/unsafe.md:16 -msgid "Dereference raw pointers." +#: src/slices-and-lifetimes/str.md +msgid "" +"We can now understand the two string types in Rust: `&str` is almost like " +"`&[char]`, but with its data stored in a variable-length encoding (UTF-8)." msgstr "" -#: src/unsafe.md:17 -msgid "Access or modify mutable static variables." +#: src/slices-and-lifetimes/str.md +msgid "\"s1: {s1}\"" msgstr "" -#: src/unsafe.md:18 -msgid "Access `union` fields." +#: src/slices-and-lifetimes/str.md +#, fuzzy +msgid "\"Hello \"" +msgstr "Merhaba Dünya!" + +#: src/slices-and-lifetimes/str.md +msgid "\"s3: {s3}\"" msgstr "" -#: src/unsafe.md:19 -msgid "Call `unsafe` functions, including `extern` functions." +#: src/slices-and-lifetimes/str.md +msgid "Rust terminology:" msgstr "" -#: src/unsafe.md:20 -msgid "Implement `unsafe` traits." +#: src/slices-and-lifetimes/str.md +msgid "`&str` an immutable reference to a string slice." msgstr "" -#: src/unsafe.md:22 +#: src/slices-and-lifetimes/str.md +msgid "`String` a mutable string buffer." +msgstr "" + +#: src/slices-and-lifetimes/str.md 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/)." +"`&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/unsafe.md:28 +#: src/slices-and-lifetimes/str.md 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." +"Rust’s `String` type is a wrapper around a vector of bytes. As with a " +"`Vec`, it is owned." msgstr "" -#: src/unsafe/raw-pointers.md:3 -msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" +#: src/slices-and-lifetimes/str.md +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/unsafe/raw-pointers.md:5 +#: src/slices-and-lifetimes/str.md msgid "" -"```rust,editable\n" -"fn main() {\n" -" let mut num = 5;\n" -"\n" -" let r1 = &mut num as *mut i32;\n" -" let r2 = r1 as *const i32;\n" -"\n" -" // Safe because r1 and r2 were obtained from references and so are\n" -" // guaranteed to be non-null and properly aligned, the objects " -"underlying\n" -" // the references from which they were obtained are live throughout the\n" -" // whole unsafe block, and they are not accessed either through the\n" -" // references or concurrently through any other pointers.\n" -" unsafe {\n" -" println!(\"r1 is: {}\", *r1);\n" -" *r1 = 10;\n" -" println!(\"r2 is: {}\", *r2);\n" -" }\n" -"}\n" -"```" +"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/unsafe/raw-pointers.md:27 +#: src/slices-and-lifetimes/str.md 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." +"You can borrow `&str` slices from `String` via `&` and optionally range " +"selection. If you select a byte range that is not aligned to character " +"boundaries, the expression will panic. The `chars` iterator iterates over " +"characters and is preferred over trying to get character boundaries right." msgstr "" -#: src/unsafe/raw-pointers.md:31 +#: src/slices-and-lifetimes/str.md 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.:" +"For C++ programmers: think of `&str` as `std::string_view` from C++, but the " +"one that always points to a valid string in memory. Rust `String` is a rough " +"equivalent of `std::string` from C++ (main difference: it can only contain " +"UTF-8 encoded bytes and will never use a small-string optimization)." msgstr "" -#: src/unsafe/raw-pointers.md:34 -msgid "The pointer must be non-null." +#: src/slices-and-lifetimes/str.md +msgid "Byte strings literals allow you to create a `&[u8]` value directly:" msgstr "" -#: src/unsafe/raw-pointers.md:35 +#: src/slices-and-lifetimes/lifetime-annotations.md msgid "" -"The pointer must be _dereferenceable_ (within the bounds of a single " -"allocated object)." +"A reference has a _lifetime_, which must not \"outlive\" the value it refers " +"to. This is verified by the borrow checker." msgstr "" -#: src/unsafe/raw-pointers.md:36 -msgid "The object must not have been deallocated." +#: src/slices-and-lifetimes/lifetime-annotations.md +msgid "" +"The lifetime can be implicit - this is what we have seen so far. Lifetimes " +"can also be explicit: `&'a Point`, `&'document str`. Lifetimes start with " +"`'` and `'a` is a typical default name. Read `&'a Point` as \"a borrowed " +"`Point` which is valid for at least the lifetime `a`\"." msgstr "" -#: src/unsafe/raw-pointers.md:37 -msgid "There must not be concurrent accesses to the same location." +#: src/slices-and-lifetimes/lifetime-annotations.md +msgid "" +"Lifetimes are always inferred by the compiler: you cannot assign a lifetime " +"yourself. Explicit lifetime annotations create constraints where there is " +"ambiguity; the compiler verifies that there is a valid solution." msgstr "" -#: src/unsafe/raw-pointers.md:38 +#: src/slices-and-lifetimes/lifetime-annotations.md 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." +"Lifetimes become more complicated when considering passing values to and " +"returning values from functions." msgstr "" -#: src/unsafe/raw-pointers.md:41 -msgid "In most cases the pointer must also be properly aligned." +#: src/slices-and-lifetimes/lifetime-annotations.md +msgid "// What is the lifetime of p3?\n" msgstr "" -#: src/unsafe/mutable-static-variables.md:3 -msgid "It is safe to read an immutable static variable:" +#: src/slices-and-lifetimes/lifetime-annotations.md +msgid "\"p3: {p3:?}\"" msgstr "" -#: src/unsafe/mutable-static-variables.md:5 +#: src/slices-and-lifetimes/lifetime-annotations.md msgid "" -"```rust,editable\n" -"static HELLO_WORLD: &str = \"Hello, world!\";\n" -"\n" -"fn main() {\n" -" println!(\"HELLO_WORLD: {HELLO_WORLD}\");\n" -"}\n" -"```" +"In this example, the the compiler does not know what lifetime to infer for " +"`p3`. Looking inside the function body shows that it can only safely assume " +"that `p3`'s lifetime is the shorter of `p1` and `p2`. But just like types, " +"Rust requires explicit annotations of lifetimes on function arguments and " +"return values." msgstr "" -#: src/unsafe/mutable-static-variables.md:13 -msgid "" -"However, since data races can occur, it is unsafe to read and write mutable " -"static variables:" +#: src/slices-and-lifetimes/lifetime-annotations.md +msgid "Add `'a` appropriately to `left_most`:" msgstr "" -#: src/unsafe/mutable-static-variables.md:16 +#: src/slices-and-lifetimes/lifetime-annotations.md msgid "" -"```rust,editable\n" -"static mut COUNTER: u32 = 0;\n" -"\n" -"fn add_to_counter(inc: u32) {\n" -" unsafe { COUNTER += inc; } // Potential data race!\n" -"}\n" -"\n" -"fn main() {\n" -" add_to_counter(42);\n" -"\n" -" unsafe { println!(\"COUNTER: {COUNTER}\"); } // Potential data race!\n" -"}\n" -"```" +"This says, \"given p1 and p2 which both outlive `'a`, the return value lives " +"for at least `'a`." msgstr "" -#: src/unsafe/mutable-static-variables.md:32 +#: src/slices-and-lifetimes/lifetime-annotations.md msgid "" -"The program here is safe because it is single-threaded. However, the Rust " -"compiler is conservative and will assume the worst. Try removing the " -"`unsafe` and see how the compiler explains that it is undefined behavior to " -"mutate a static from multiple threads." +"In common cases, lifetimes can be elided, as described on the next slide." msgstr "" -#: src/unsafe/mutable-static-variables.md:36 +#: src/slices-and-lifetimes/lifetime-elision.md +msgid "Lifetimes in Function Calls" +msgstr "Fonksiyon Çağrılarında Ömürler" + +#: src/slices-and-lifetimes/lifetime-elision.md 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." +"Lifetimes for function arguments and return values must be fully specified, " +"but Rust allows lifetimes to be elided in most cases with [a few simple " +"rules](https://doc.rust-lang.org/nomicon/lifetime-elision.html). This is not " +"inference -- it is just a syntactic shorthand." msgstr "" -#: src/unsafe/unions.md:3 -msgid "Unions are like enums, but you need to track the active field yourself:" +#: src/slices-and-lifetimes/lifetime-elision.md +msgid "Each argument which does not have a lifetime annotation is given one." msgstr "" -#: src/unsafe/unions.md:5 +#: src/slices-and-lifetimes/lifetime-elision.md msgid "" -"```rust,editable\n" -"#[repr(C)]\n" -"union MyUnion {\n" -" i: u8,\n" -" b: bool,\n" -"}\n" -"\n" -"fn main() {\n" -" let u = MyUnion { i: 42 };\n" -" println!(\"int: {}\", unsafe { u.i });\n" -" println!(\"bool: {}\", unsafe { u.b }); // Undefined behavior!\n" -"}\n" -"```" +"If there is only one argument lifetime, it is given to all un-annotated " +"return values." msgstr "" -#: src/unsafe/unions.md:21 +#: src/slices-and-lifetimes/lifetime-elision.md msgid "" -"Unions are very rarely needed in Rust as you can usually use an enum. They " -"are occasionally needed for interacting with C library APIs." +"If there are multiple argument lifetimes, but the first one is for `self`, " +"that lifetime is given to all un-annotated return values." 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." +#: src/slices-and-lifetimes/lifetime-elision.md +msgid "In this example, `cab_distance` is trivially elided." msgstr "" -#: src/unsafe/calling-unsafe-functions.md:3 +#: src/slices-and-lifetimes/lifetime-elision.md msgid "" -"A function or method can be marked `unsafe` if it has extra preconditions " -"you must uphold to avoid undefined behaviour:" +"The `nearest` function provides another example of a function with multiple " +"references in its arguments that requires explicit annotation." msgstr "" -#: src/unsafe/calling-unsafe-functions.md:6 -msgid "" -"```rust,editable\n" -"fn main() {\n" -" let emojis = \"🗻∈🌏\";\n" -"\n" -" // Safe because the indices are in the correct order, within the bounds " -"of\n" -" // the string slice, and lie on UTF-8 sequence boundaries.\n" -" unsafe {\n" -" println!(\"emoji: {}\", emojis.get_unchecked(0..4));\n" -" println!(\"emoji: {}\", emojis.get_unchecked(4..7));\n" -" println!(\"emoji: {}\", emojis.get_unchecked(7..11));\n" -" }\n" -"\n" -" println!(\"char count: {}\", count_chars(unsafe { emojis." -"get_unchecked(0..7) }));\n" -"\n" -" // Not upholding the UTF-8 encoding requirement breaks memory safety!\n" -" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" -" // println!(\"char count: {}\", count_chars(unsafe { emojis." -"get_unchecked(0..3) }));\n" -"}\n" -"\n" -"fn count_chars(s: &str) -> usize {\n" -" s.chars().count()\n" -"}\n" -"```" +#: src/slices-and-lifetimes/lifetime-elision.md +msgid "Try adjusting the signature to \"lie\" about the lifetimes returned:" msgstr "" -#: src/unsafe/writing-unsafe-functions.md:3 +#: src/slices-and-lifetimes/lifetime-elision.md msgid "" -"You can mark your own functions as `unsafe` if they require particular " -"conditions to avoid undefined behaviour." +"This won't compile, demonstrating that the annotations are checked for " +"validity by the compiler. Note that this is not the case for raw pointers " +"(unsafe), and this is a common source of errors with unsafe Rust." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:6 +#: src/slices-and-lifetimes/lifetime-elision.md msgid "" -"```rust,editable\n" -"/// Swaps the values pointed to by the given pointers.\n" -"///\n" -"/// # Safety\n" -"///\n" -"/// The pointers must be valid and properly aligned.\n" -"unsafe fn swap(a: *mut u8, b: *mut u8) {\n" -" let temp = *a;\n" -" *a = *b;\n" -" *b = temp;\n" -"}\n" -"\n" -"fn main() {\n" -" let mut a = 42;\n" -" let mut b = 66;\n" -"\n" -" // Safe because ...\n" -" unsafe {\n" -" swap(&mut a, &mut b);\n" -" }\n" -"\n" -" println!(\"a = {}, b = {}\", a, b);\n" -"}\n" -"```" +"Students may ask when to use lifetimes. Rust borrows _always_ have " +"lifetimes. Most of the time, elision and type inference mean these don't " +"need to be written out. In more complicated cases, lifetime annotations can " +"help resolve ambiguity. Often, especially when prototyping, it's easier to " +"just work with owned data by cloning values where necessary." msgstr "" -#: src/unsafe/writing-unsafe-functions.md:33 +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "Lifetimes in Data Structures" +msgstr "Veri Yapılarında Ömürler" + +#: src/slices-and-lifetimes/struct-lifetimes.md msgid "" -"We wouldn't actually use pointers for this because it can be done safely " -"with references." +"If a data type stores borrowed data, it must be annotated with a lifetime:" 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." +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "\"Bye {text}!\"" msgstr "" -#: src/unsafe/extern-functions.md:1 -msgid "Calling External Code" +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "\"The quick brown fox jumps over the lazy dog.\"" msgstr "" -#: src/unsafe/extern-functions.md:3 -msgid "" -"Functions from other languages might violate the guarantees of Rust. Calling " -"them is thus unsafe:" +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "// erase(text);\n" msgstr "" -#: src/unsafe/extern-functions.md:6 -msgid "" -"```rust,editable\n" -"extern \"C\" {\n" -" fn abs(input: i32) -> i32;\n" -"}\n" -"\n" -"fn main() {\n" -" unsafe {\n" -" // Undefined behavior if abs misbehaves.\n" -" println!(\"Absolute value of -3 according to C: {}\", abs(-3));\n" -" }\n" -"}\n" -"```" +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "\"{fox:?}\"" msgstr "" -#: src/unsafe/extern-functions.md:21 -msgid "" -"This is usually only a problem for extern functions which do things with " -"pointers which might violate Rust's memory model, but in general any C " -"function might have undefined behaviour under any arbitrary circumstances." +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "\"{dog:?}\"" msgstr "" -#: src/unsafe/extern-functions.md:25 +#: src/slices-and-lifetimes/struct-lifetimes.md msgid "" -"The `\"C\"` in this example is the ABI; [other ABIs are available too]" -"(https://doc.rust-lang.org/reference/items/external-blocks.html)." +"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/unsafe/unsafe-traits.md:3 +#: src/slices-and-lifetimes/struct-lifetimes.md msgid "" -"Like with functions, you can mark a trait as `unsafe` if the implementation " -"must guarantee particular conditions to avoid undefined behaviour." +"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " +"the borrow checker throws an error." msgstr "" -#: src/unsafe/unsafe-traits.md:6 +#: src/slices-and-lifetimes/struct-lifetimes.md msgid "" -"For example, the `zerocopy` crate has an unsafe trait that looks [something " -"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" +"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/unsafe/unsafe-traits.md:9 -msgid "" -"```rust,editable\n" -"use std::mem::size_of_val;\n" -"use std::slice;\n" -"\n" -"/// ...\n" -"/// # Safety\n" -"/// The type must have a defined representation and no padding.\n" -"pub unsafe trait AsBytes {\n" -" fn as_bytes(&self) -> &[u8] {\n" -" unsafe {\n" -" slice::from_raw_parts(self as *const Self as *const u8, " -"size_of_val(self))\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Safe because u32 has a defined representation and no padding.\n" -"unsafe impl AsBytes for u32 {}\n" -"```" +#: src/slices-and-lifetimes/struct-lifetimes.md +msgid "When possible, make data structures own their data directly." msgstr "" -#: src/unsafe/unsafe-traits.md:30 +#: src/slices-and-lifetimes/struct-lifetimes.md msgid "" -"There should be a `# Safety` section on the Rustdoc for the trait explaining " -"the requirements for the trait to be safely implemented." +"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/unsafe/unsafe-traits.md:33 +#: src/slices-and-lifetimes/exercise.md msgid "" -"The actual safety section for `AsBytes` is rather longer and more " -"complicated." +"In this exercise, you will build a parser for the [protobuf binary encoding]" +"(https://protobuf.dev/programming-guides/encoding/). Don't worry, it's " +"simpler than it seems! This illustrates a common parsing pattern, passing " +"slices of data. The underlying data itself is never copied." msgstr "" -#: src/unsafe/unsafe-traits.md:35 -msgid "The built-in `Send` and `Sync` traits are unsafe." +#: src/slices-and-lifetimes/exercise.md +msgid "" +"Fully parsing a protobuf message requires knowing the types of the fields, " +"indexed by their field numbers. That is typically provided in a `proto` " +"file. In this exercise, we'll encode that information into `match` " +"statements in functions that get called for each field." msgstr "" -#: src/exercises/day-3/afternoon.md:1 -msgid "Day 3: Afternoon Exercises" +#: src/slices-and-lifetimes/exercise.md +msgid "We'll use the following proto:" msgstr "" -#: src/exercises/day-3/afternoon.md:3 -msgid "Let us build a safe wrapper for reading directory content!" +#: src/slices-and-lifetimes/exercise.md +msgid "" +"A proto message is encoded as a series of fields, one after the next. Each " +"is implemented as a \"tag\" followed by the value. The tag contains a field " +"number (e.g., `2` for the `id` field of a `Person` message) and a wire type " +"defining how the payload should be determined from the byte stream." msgstr "" -#: src/exercises/day-3/afternoon.md:5 +#: src/slices-and-lifetimes/exercise.md 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." +"Integers, including the tag, are represented with a variable-length encoding " +"called VARINT. Luckily, `parse_varint` is defined for you below. The given " +"code also defines callbacks to handle `Person` and `PhoneNumber` fields, and " +"to parse a message into a series of calls to those callbacks." msgstr "" -#: src/exercises/day-3/afternoon.md:8 +#: src/slices-and-lifetimes/exercise.md msgid "" -"To get started, follow the [running locally](../../cargo/running-locally.md) " -"instructions." +"What remains for you is to implement the `parse_field` function and the " +"`ProtoMessage` trait for `Person` and `PhoneNumber`." msgstr "" -#: src/exercises/day-3/afternoon.md:14 -msgid "" -"After looking at the exercise, you can look at the [solution](solutions-" -"afternoon.md) provided." +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Invalid varint\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:3 -msgid "" -"Rust has great support for calling functions through a _foreign function " -"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " -"functions you would use from C to read the names of files in a directory." +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Invalid wire-type\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:7 -msgid "You will want to consult the manual pages:" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Unexpected EOF\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:9 -msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Invalid length\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:10 -msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Unexpected wire-type)\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:11 -msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "\"Invalid string (not UTF-8)\"" 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:" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// A wire type as seen on the wire.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Encoding" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// The Varint WireType indicates the value is a single VARINT.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:16 -msgid "Use" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "" +"//I64, -- not needed for this exercise\n" +" /// The Len WireType indicates that the value is a length represented as " +"a\n" +" /// VARINT followed by exactly that number of bytes.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md msgid "" -"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" -"(https://doc.rust-lang.org/std/string/struct.String.html)" +"/// The I32 WireType indicates that the value is precisely 4 bytes in\n" +" /// little-endian order containing a 32-bit signed integer.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "UTF-8" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// A field's value, typed based on the wire type.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:18 -msgid "Text processing in Rust" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "//I64(i64), -- not needed for this exercise\n" 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)" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// A field, containing the field number and its value.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "NUL-terminated" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "//1 => WireType::I64, -- not needed for this exercise\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:19 -msgid "Communicating with C functions" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "" +"/// Parse a VARINT, returning the parsed value and the remaining bytes.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md msgid "" -"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " -"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" +"// This is the last byte of the VARINT, so convert it to\n" +" // a u64 and return it.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "OS-specific" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "// More than 7 bytes is invalid.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:20 -msgid "Communicating with the OS" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// Convert a tag into a field number and a WireType.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:22 -msgid "You will convert between all these types:" +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md +msgid "/// Parse a field, returning the remaining bytes\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:24 +#: src/slices-and-lifetimes/exercise.md msgid "" -"`&str` to `CString`: you need to allocate space for a trailing `\\0` " -"character," +"\"Based on the wire type, build a Field, consuming as many bytes as " +"necessary.\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:25 -msgid "`CString` to `*const i8`: you need a pointer to call C functions," +#: src/slices-and-lifetimes/exercise.md +msgid "\"Return the field, and any un-consumed bytes.\"" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:26 +#: src/slices-and-lifetimes/exercise.md src/slices-and-lifetimes/solution.md msgid "" -"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " -"character," +"/// Parse a message in the given data, calling `T::add_field` for each field " +"in\n" +"/// the message.\n" +"///\n" +"/// The entire input is consumed.\n" msgstr "" -#: src/exercises/day-3/safe-ffi-wrapper.md:27 -msgid "" -"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " -"unknown data\"," +#: src/slices-and-lifetimes/exercise.md +msgid "// TODO: Implement ProtoMessage for Person and PhoneNumber.\n" 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," +#: src/slices-and-lifetimes/solution.md +msgid "// Unwrap error because `value` is definitely 4 bytes long.\n" 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." +#: src/slices-and-lifetimes/solution.md +msgid "// skip everything else\n" 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." +#: src/slices-and-lifetimes/solution.md +msgid "b\"hello\"" 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/welcome-day-4.md +#, fuzzy +msgid "Welcome to Day 4" +msgstr "Hoşgeldiniz" -#: src/exercises/day-3/safe-ffi-wrapper.md:48 +#: src/welcome-day-4.md msgid "" -"```rust,should_panic\n" -"// TODO: remove this when you're done with your implementation.\n" -"#![allow(unused_imports, unused_variables, dead_code)]\n" -"\n" -"mod ffi {\n" -" use std::os::raw::{c_char, c_int};\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" use std::os::raw::{c_long, c_ulong, c_ushort, c_uchar};\n" -"\n" -" // Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" -" #[repr(C)]\n" -" pub struct DIR {\n" -" _data: [u8; 0],\n" -" _marker: core::marker::PhantomData<(*mut u8, core::marker::" -"PhantomPinned)>,\n" -" }\n" -"\n" -" // Layout according to the Linux man page for readdir(3), where ino_t " -"and\n" -" // off_t are resolved according to the definitions in\n" -" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_ino: c_ulong,\n" -" pub d_off: c_long,\n" -" pub d_reclen: c_ushort,\n" -" pub d_type: c_uchar,\n" -" pub d_name: [c_char; 256],\n" -" }\n" -"\n" -" // Layout according to the macOS man page for dir(5).\n" -" #[cfg(all(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_fileno: u64,\n" -" pub d_seekoff: u64,\n" -" pub d_reclen: u16,\n" -" pub d_namlen: u16,\n" -" pub d_type: u8,\n" -" pub d_name: [c_char; 1024],\n" -" }\n" -"\n" -" extern \"C\" {\n" -" pub fn opendir(s: *const c_char) -> *mut DIR;\n" -"\n" -" #[cfg(not(all(target_os = \"macos\", target_arch = \"x86_64\")))]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" // See https://github.com/rust-lang/libc/issues/414 and the section " -"on\n" -" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" -" //\n" -" // \"Platforms that existed before these updates were available\" " -"refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " -"PowerPC.\n" -" #[cfg(all(target_os = \"macos\", target_arch = \"x86_64\"))]\n" -" #[link_name = \"readdir$INODE64\"]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" pub fn closedir(s: *mut DIR) -> c_int;\n" -" }\n" -"}\n" -"\n" -"use std::ffi::{CStr, CString, OsStr, OsString};\n" -"use std::os::unix::ffi::OsStrExt;\n" -"\n" -"#[derive(Debug)]\n" -"struct DirectoryIterator {\n" -" path: CString,\n" -" dir: *mut ffi::DIR,\n" -"}\n" -"\n" -"impl DirectoryIterator {\n" -" fn new(path: &str) -> Result {\n" -" // Call opendir and return a Ok value if that worked,\n" -" // otherwise return Err with a message.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Iterator for DirectoryIterator {\n" -" type Item = OsString;\n" -" fn next(&mut self) -> Option {\n" -" // Keep calling readdir until we get a NULL pointer back.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"impl Drop for DirectoryIterator {\n" -" fn drop(&mut self) {\n" -" // Call closedir as needed.\n" -" unimplemented!()\n" -" }\n" -"}\n" -"\n" -"fn main() -> Result<(), String> {\n" -" let iter = DirectoryIterator::new(\".\")?;\n" -" println!(\"files: {:#?}\", iter.collect::>());\n" -" Ok(())\n" -"}\n" -"```" +"Today we will cover topics relating to building large-scale software in Rust:" msgstr "" -#: src/android.md:1 -msgid "Welcome to Rust in Android" +#: src/welcome-day-4.md +msgid "Iterators: a deep dive on the `Iterator` trait." 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." +#: src/welcome-day-4.md +msgid "Modules and visibility." 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/welcome-day-4.md +#, fuzzy +msgid "Testing." +msgstr "Test Etme" -#: 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:" +#: src/welcome-day-4.md +msgid "Error handling: panics, `Result`, and the try operator `?`." msgstr "" -#: src/android/setup.md:12 +#: src/welcome-day-4.md msgid "" -"Please see the [Android Developer Codelab](https://source.android.com/docs/" -"setup/start) for details." +"Unsafe Rust: the escape hatch when you can't express yourself in safe Rust." 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" +#: src/welcome-day-4.md +msgid "[Welcome](./welcome-day-4.md) (3 minutes)" msgstr "" -#: src/android/build-rules.md:5 -msgid "Description" +#: src/welcome-day-4.md +msgid "[Iterators](./iterators.md) (45 minutes)" msgstr "" -#: src/android/build-rules.md:7 -msgid "`rust_binary`" +#: src/welcome-day-4.md +msgid "[Modules](./modules.md) (40 minutes)" msgstr "" -#: src/android/build-rules.md:7 -msgid "Produces a Rust binary." +#: src/welcome-day-4.md +msgid "[Testing](./testing.md) (1 hour and 5 minutes)" msgstr "" -#: src/android/build-rules.md:8 -msgid "`rust_library`" +#: src/iterators.md +msgid "[Iterator](./iterators/iterator.md) (5 minutes)" msgstr "" -#: src/android/build-rules.md:8 -msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." +#: src/iterators.md +msgid "[IntoIterator](./iterators/intoiterator.md) (5 minutes)" msgstr "" -#: src/android/build-rules.md:9 -msgid "`rust_ffi`" +#: src/iterators.md +msgid "[FromIterator](./iterators/fromiterator.md) (5 minutes)" msgstr "" -#: src/android/build-rules.md:9 +#: src/iterators.md msgid "" -"Produces a Rust C library usable by `cc` modules, and provides both static " -"and shared variants." +"[Exercise: Iterator Method Chaining](./iterators/exercise.md) (30 minutes)" msgstr "" -#: src/android/build-rules.md:10 -msgid "`rust_proc_macro`" -msgstr "" - -#: src/android/build-rules.md:10 +#: src/iterators/iterator.md msgid "" -"Produces a `proc-macro` Rust library. These are analogous to compiler " -"plugins." +"The [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait supports iterating over values in a collection. It requires a `next` " +"method and provides lots of methods. Many standard library types implement " +"`Iterator`, and you can implement it yourself, too:" msgstr "" -#: src/android/build-rules.md:11 -msgid "`rust_test`" +#: src/iterators/iterator.md +msgid "\"fib({i}): {n}\"" msgstr "" -#: src/android/build-rules.md:11 -msgid "Produces a Rust test binary that uses the standard Rust test harness." +#: src/iterators/iterator.md +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/android/build-rules.md:12 -msgid "`rust_fuzz`" +#: src/iterators/iterator.md +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/android/build-rules.md:12 -msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." +#: src/iterators/intoiterator.md +msgid "" +"The `Iterator` trait tells you how to _iterate_ once you have created an " +"iterator. The related trait [`IntoIterator`](https://doc.rust-lang.org/std/" +"iter/trait.IntoIterator.html) defines how to create an iterator for a type. " +"It is used automatically by the `for` loop." msgstr "" -#: src/android/build-rules.md:13 -msgid "`rust_protobuf`" +#: src/iterators/intoiterator.md +msgid "\"point = {x}, {y}\"" msgstr "" -#: src/android/build-rules.md:13 +#: src/iterators/intoiterator.md msgid "" -"Generates source and produces a Rust library that provides an interface for " -"a particular protobuf." +"Click through to the docs for `IntoIterator`. Every implementation of " +"`IntoIterator` must declare two types:" msgstr "" -#: src/android/build-rules.md:14 -msgid "`rust_bindgen`" +#: src/iterators/intoiterator.md +msgid "`Item`: the type to iterate over, such as `i8`," msgstr "" -#: src/android/build-rules.md:14 -msgid "" -"Generates source and produces a Rust library containing Rust bindings to C " -"libraries." +#: src/iterators/intoiterator.md +msgid "`IntoIter`: the `Iterator` type returned by the `into_iter` method." msgstr "" -#: src/android/build-rules.md:16 -msgid "We will look at `rust_binary` and `rust_library` next." +#: src/iterators/intoiterator.md +msgid "" +"Note that `IntoIter` and `Item` are linked: the iterator must have the same " +"`Item` type, which means that it returns `Option`" msgstr "" -#: src/android/build-rules/binary.md:1 -msgid "Rust Binaries" +#: src/iterators/intoiterator.md +msgid "The example iterates over all combinations of x and y coordinates." msgstr "" -#: src/android/build-rules/binary.md:3 +#: src/iterators/intoiterator.md msgid "" -"Let us start with a simple application. At the root of an AOSP checkout, " -"create the following files:" +"Try iterating over the grid twice in `main`. Why does this fail? Note that " +"`IntoIterator::into_iter` takes ownership of `self`." msgstr "" -#: src/android/build-rules/binary.md:6 src/android/build-rules/library.md:13 -msgid "_hello_rust/Android.bp_:" +#: src/iterators/intoiterator.md +msgid "" +"Fix this issue by implementing `IntoIterator` for `&Grid` and storing a " +"reference to the `Grid` in `GridIter`." msgstr "" -#: src/android/build-rules/binary.md:8 +#: src/iterators/intoiterator.md msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust\",\n" -" crate_name: \"hello_rust\",\n" -" srcs: [\"src/main.rs\"],\n" -"}\n" -"```" +"The same problem can occur for standard library types: `for e in " +"some_vector` will take ownership of `some_vector` and iterate over owned " +"elements from that vector. Use `for e in &some_vector` instead, to iterate " +"over references to elements of `some_vector`." msgstr "" -#: src/android/build-rules/binary.md:16 src/android/build-rules/library.md:34 -msgid "_hello_rust/src/main.rs_:" -msgstr "" +#: src/iterators/fromiterator.md +msgid "FromIterator" +msgstr "FromIterator" -#: src/android/build-rules/binary.md:18 +#: src/iterators/fromiterator.md msgid "" -"```rust\n" -"//! Rust demo.\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"Hello from Rust!\");\n" -"}\n" -"```" +"[`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/android/build-rules/binary.md:27 -msgid "You can now build, push, and run the binary:" +#: src/iterators/fromiterator.md +msgid "\"prime_squares: {prime_squares:?}\"" 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" -"```" +#: src/iterators/fromiterator.md +msgid "`Iterator` implements" msgstr "" -#: src/android/build-rules/library.md:1 -msgid "Rust Libraries" +#: src/iterators/fromiterator.md +msgid "There are two ways to specify `B` for this method:" msgstr "" -#: src/android/build-rules/library.md:3 -msgid "You use `rust_library` to create a new Rust library for Android." +#: src/iterators/fromiterator.md +msgid "" +"With the \"turbofish\": `some_iterator.collect::()`, as " +"shown. The `_` shorthand used here lets Rust infer the type of the `Vec` " +"elements." msgstr "" -#: src/android/build-rules/library.md:5 -msgid "Here we declare a dependency on two libraries:" +#: src/iterators/fromiterator.md +msgid "" +"With type inference: `let prime_squares: Vec<_> = some_iterator.collect()`. " +"Rewrite the example to use this form." msgstr "" -#: src/android/build-rules/library.md:7 -msgid "`libgreeting`, which we define below," +#: src/iterators/fromiterator.md +msgid "" +"There are basic implementations of `FromIterator` for `Vec`, `HashMap`, etc. " +"There are also more specialized implementations which let you do cool things " +"like convert an `Iterator>` into a `Result, E>`." msgstr "" -#: src/android/build-rules/library.md:8 +#: src/iterators/exercise.md msgid "" -"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" -"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" -"crates/)." +"In this exercise, you will need to find and use some of the provided methods " +"in the [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) " +"trait to implement a complex calculation." msgstr "" -#: src/android/build-rules/library.md:15 +#: src/iterators/exercise.md msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_with_dep\",\n" -" crate_name: \"hello_rust_with_dep\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"libgreetings\",\n" -" \"libtextwrap\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"\n" -"rust_library {\n" -" name: \"libgreetings\",\n" -" crate_name: \"greetings\",\n" -" srcs: [\"src/lib.rs\"],\n" -"}\n" -"```" +"Copy the following code to and make the tests " +"pass. Use an iterator expression and `collect` the result to construct the " +"return value." msgstr "" -#: src/android/build-rules/library.md:36 +#: src/iterators/exercise.md src/iterators/solution.md msgid "" -"```rust,ignore\n" -"//! Rust demo.\n" -"\n" -"use greetings::greeting;\n" -"use textwrap::fill;\n" -"\n" -"/// Prints a greeting to standard output.\n" -"fn main() {\n" -" println!(\"{}\", fill(&greeting(\"Bob\"), 24));\n" -"}\n" -"```" +"/// Calculate the differences between elements of `values` offset by " +"`offset`,\n" +"/// wrapping around from the end of `values` to the beginning.\n" +"///\n" +"/// Element `n` of the result is `values[(n+offset)%len] - values[n]`.\n" msgstr "" -#: src/android/build-rules/library.md:48 -msgid "_hello_rust/src/lib.rs_:" +#: src/modules.md +msgid "[Modules](./modules/modules.md) (5 minutes)" msgstr "" -#: src/android/build-rules/library.md:50 -msgid "" -"```rust,ignore\n" -"//! Greeting library.\n" -"\n" -"/// Greet `name`.\n" -"pub fn greeting(name: &str) -> String {\n" -" format!(\"Hello {name}, it is very nice to meet you!\")\n" -"}\n" -"```" +#: src/modules.md +msgid "[Filesystem Hierarchy](./modules/filesystem.md) (5 minutes)" msgstr "" -#: src/android/build-rules/library.md:59 -msgid "You build, push, and run the binary like before:" +#: src/modules.md +msgid "[Visibility](./modules/visibility.md) (5 minutes)" 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" -"```" +#: src/modules.md +msgid "[use, super, self](./modules/paths.md) (10 minutes)" msgstr "" -#: src/android/aidl.md:3 +#: src/modules.md msgid "" -"The [Android Interface Definition Language (AIDL)](https://developer.android." -"com/guide/components/aidl) is supported in Rust:" +"[Exercise: Modules for a GUI Library](./modules/exercise.md) (15 minutes)" msgstr "" -#: src/android/aidl.md:6 -msgid "Rust code can call existing AIDL servers," +#: src/modules.md +msgid "This segment should take about 40 minutes" msgstr "" -#: src/android/aidl.md:7 -msgid "You can create new AIDL servers in Rust." +#: src/modules/modules.md +msgid "We have seen how `impl` blocks let us namespace functions to a type." msgstr "" -#: src/android/aidl/interface.md:1 -msgid "AIDL Interfaces" +#: src/modules/modules.md +msgid "Similarly, `mod` lets us namespace types and functions:" msgstr "" -#: src/android/aidl/interface.md:3 -msgid "You declare the API of your service using an AIDL interface:" +#: src/modules/modules.md +msgid "\"In the foo module\"" msgstr "" -#: src/android/aidl/interface.md:5 -msgid "" -"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +#: src/modules/modules.md +msgid "\"In the bar module\"" msgstr "" -#: src/android/aidl/interface.md:17 -msgid "_birthday_service/aidl/Android.bp_:" +#: src/modules/modules.md +msgid "" +"Packages provide functionality and include a `Cargo.toml` file that " +"describes how to build a bundle of 1+ crates." msgstr "" -#: src/android/aidl/interface.md:19 +#: src/modules/modules.md msgid "" -"```javascript\n" -"aidl_interface {\n" -" name: \"com.example.birthdayservice\",\n" -" srcs: [\"com/example/birthdayservice/*.aidl\"],\n" -" unstable: true,\n" -" backend: {\n" -" rust: { // Rust is not enabled by default\n" -" enabled: true,\n" -" },\n" -" },\n" -"}\n" -"```" +"Crates are a tree of modules, where a binary crate creates an executable and " +"a library crate compiles to a library." +msgstr "" + +#: src/modules/modules.md +msgid "Modules define organization, scope, and are the focus of this section." msgstr "" -#: src/android/aidl/interface.md:32 +#: src/modules/filesystem.md msgid "" -"Add `vendor_available: true` if your AIDL file is used by a binary in the " -"vendor partition." +"Omitting the module content will tell Rust to look for it in another file:" msgstr "" -#: src/android/aidl/implementation.md:1 -msgid "Service Implementation" +#: src/modules/filesystem.md +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/android/aidl/implementation.md:3 -msgid "We can now implement the AIDL service:" +#: src/modules/filesystem.md +msgid "The `crate` root is in:" msgstr "" -#: src/android/aidl/implementation.md:5 -msgid "_birthday_service/src/lib.rs_:" +#: src/modules/filesystem.md +msgid "`src/lib.rs` (for a library crate)" msgstr "" -#: src/android/aidl/implementation.md:7 -msgid "" -"```rust,ignore\n" -"//! Implementation of the `IBirthdayService` AIDL interface.\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"/// The `IBirthdayService` implementation.\n" -"pub struct BirthdayService;\n" -"\n" -"impl binder::Interface for BirthdayService {}\n" -"\n" -"impl IBirthdayService for BirthdayService {\n" -" fn wishHappyBirthday(&self, name: &str, years: i32) -> binder::" -"Result {\n" -" Ok(format!(\n" -" \"Happy Birthday {name}, congratulations with the {years} years!" -"\"\n" -" ))\n" -" }\n" -"}\n" -"```" +#: src/modules/filesystem.md +msgid "`src/main.rs` (for a binary crate)" msgstr "" -#: src/android/aidl/implementation.md:26 src/android/aidl/server.md:28 -#: src/android/aidl/client.md:37 -msgid "_birthday_service/Android.bp_:" +#: src/modules/filesystem.md +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/android/aidl/implementation.md:28 +#: src/modules/filesystem.md msgid "" -"```javascript\n" -"rust_library {\n" -" name: \"libbirthdayservice\",\n" -" srcs: [\"src/lib.rs\"],\n" -" crate_name: \"birthdayservice\",\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -"}\n" -"```" +"//! This module implements the garden, including a highly performant " +"germination\n" +"//! implementation.\n" msgstr "" -#: src/android/aidl/server.md:1 -msgid "AIDL Server" +#: src/modules/filesystem.md +msgid "// Re-export types from this module.\n" msgstr "" -#: src/android/aidl/server.md:3 -msgid "Finally, we can create a server which exposes the service:" +#: src/modules/filesystem.md +msgid "/// Sow the given seed packets.\n" msgstr "" -#: src/android/aidl/server.md:5 -msgid "_birthday_service/src/server.rs_:" +#: src/modules/filesystem.md +msgid "/// Harvest the produce in the garden that is ready.\n" msgstr "" -#: src/android/aidl/server.md:7 +#: src/modules/filesystem.md msgid "" -"```rust,ignore\n" -"//! Birthday service.\n" -"use birthdayservice::BirthdayService;\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::BnBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// Entry point for birthday service.\n" -"fn main() {\n" -" let birthday_service = BirthdayService;\n" -" let birthday_service_binder = BnBirthdayService::new_binder(\n" -" birthday_service,\n" -" binder::BinderFeatures::default(),\n" -" );\n" -" binder::add_service(SERVICE_IDENTIFIER, birthday_service_binder." -"as_binder())\n" -" .expect(\"Failed to register service\");\n" -" binder::ProcessState::join_thread_pool()\n" -"}\n" -"```" +"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/android/aidl/server.md:30 +#: src/modules/filesystem.md msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_server\",\n" -" crate_name: \"birthday_server\",\n" -" srcs: [\"src/server.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" \"libbirthdayservice\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" +"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/android/aidl/deploy.md:3 -msgid "We can now build, push, and start the service:" +#: src/modules/filesystem.md +msgid "Deeper nesting can use folders, even if the main module is a file:" msgstr "" -#: src/android/aidl/deploy.md:5 +#: src/modules/filesystem.md 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" -"```" +"The place rust will look for modules can be changed with a compiler " +"directive:" msgstr "" -#: src/android/aidl/deploy.md:11 -msgid "In another terminal, check that the service runs:" +#: src/modules/filesystem.md +msgid "\"some/path.rs\"" msgstr "" -#: src/android/aidl/deploy.md:21 -msgid "You can also call the service with `service call`:" +#: src/modules/filesystem.md +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/android/aidl/client.md:1 -msgid "AIDL Client" +#: src/modules/visibility.md +msgid "Modules are a privacy boundary:" msgstr "" -#: src/android/aidl/client.md:3 -msgid "Finally, we can create a Rust client for our new service." +#: src/modules/visibility.md +msgid "Module items are private by default (hides implementation details)." msgstr "" -#: src/android/aidl/client.md:5 -msgid "_birthday_service/src/client.rs_:" +#: src/modules/visibility.md +msgid "Parent and sibling items are always visible." msgstr "" -#: src/android/aidl/client.md:7 +#: src/modules/visibility.md msgid "" -"```rust,ignore\n" -"//! Birthday service.\n" -"use com_example_birthdayservice::aidl::com::example::birthdayservice::" -"IBirthdayService::IBirthdayService;\n" -"use com_example_birthdayservice::binder;\n" -"\n" -"const SERVICE_IDENTIFIER: &str = \"birthdayservice\";\n" -"\n" -"/// Connect to the BirthdayService.\n" -"pub fn connect() -> Result, binder::" -"StatusCode> {\n" -" binder::get_interface(SERVICE_IDENTIFIER)\n" -"}\n" -"\n" -"/// Call the birthday service.\n" -"fn main() -> Result<(), binder::Status> {\n" -" let name = std::env::args()\n" -" .nth(1)\n" -" .unwrap_or_else(|| String::from(\"Bob\"));\n" -" let years = std::env::args()\n" -" .nth(2)\n" -" .and_then(|arg| arg.parse::().ok())\n" -" .unwrap_or(42);\n" -"\n" -" binder::ProcessState::start_thread_pool();\n" -" let service = connect().expect(\"Failed to connect to " -"BirthdayService\");\n" -" let msg = service.wishHappyBirthday(&name, years)?;\n" -" println!(\"{msg}\");\n" -" Ok(())\n" -"}\n" -"```" +"In other words, if an item is visible in module `foo`, it's visible in all " +"the descendants of `foo`." msgstr "" -#: src/android/aidl/client.md:39 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"birthday_client\",\n" -" crate_name: \"birthday_client\",\n" -" srcs: [\"src/client.rs\"],\n" -" rustlibs: [\n" -" \"com.example.birthdayservice-rust\",\n" -" \"libbinder_rs\",\n" -" ],\n" -" prefer_rlib: true,\n" -"}\n" -"```" +#: src/modules/visibility.md +msgid "\"outer::private\"" msgstr "" -#: src/android/aidl/client.md:52 -msgid "Notice that the client does not depend on `libbirthdayservice`." +#: src/modules/visibility.md +msgid "\"outer::public\"" msgstr "" -#: src/android/aidl/client.md:54 -msgid "Build, push, and run the client on your device:" +#: src/modules/visibility.md +msgid "\"outer::inner::private\"" 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" -"```" +#: src/modules/visibility.md +msgid "\"outer::inner::public\"" msgstr "" -#: 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:" +#: src/modules/visibility.md +msgid "Use the `pub` keyword to make modules public." msgstr "" -#: src/android/logging.md:3 +#: src/modules/visibility.md msgid "" -"You should use the `log` crate to automatically log to `logcat` (on-device) " -"or `stdout` (on-host):" +"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " +"of public visibility." msgstr "" -#: src/android/logging.md:6 -msgid "_hello_rust_logs/Android.bp_:" +#: src/modules/visibility.md +msgid "" +"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" +"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." msgstr "" -#: src/android/logging.md:8 -msgid "" -"```javascript\n" -"rust_binary {\n" -" name: \"hello_rust_logs\",\n" -" crate_name: \"hello_rust_logs\",\n" -" srcs: [\"src/main.rs\"],\n" -" rustlibs: [\n" -" \"liblog_rust\",\n" -" \"liblogger\",\n" -" ],\n" -" prefer_rlib: true,\n" -" host_supported: true,\n" -"}\n" -"```" +#: src/modules/visibility.md +msgid "Configuring `pub(crate)` visibility is a common pattern." msgstr "" -#: src/android/logging.md:22 -msgid "_hello_rust_logs/src/main.rs_:" +#: src/modules/visibility.md +msgid "Less commonly, you can give visibility to a specific path." msgstr "" -#: src/android/logging.md:24 +#: src/modules/visibility.md msgid "" -"```rust,ignore\n" -"//! Rust logging demo.\n" -"\n" -"use log::{debug, error, info};\n" -"\n" -"/// Logs a greeting.\n" -"fn main() {\n" -" logger::init(\n" -" logger::Config::default()\n" -" .with_tag_on_device(\"rust\")\n" -" .with_min_level(log::Level::Trace),\n" -" );\n" -" debug!(\"Starting program.\");\n" -" info!(\"Things are going fine.\");\n" -" error!(\"Something went wrong!\");\n" -"}\n" -"```" +"In any case, visibility must be granted to an ancestor module (and all of " +"its descendants)." msgstr "" -#: src/android/logging.md:42 src/android/interoperability/with-c/bindgen.md:98 -#: src/android/interoperability/with-c/rust.md:73 -msgid "Build, push, and run the binary on your device:" +#: src/modules/paths.md +msgid "use, super, self" msgstr "" -#: src/android/logging.md:44 +#: src/modules/paths.md 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" -"```" +"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/android/logging.md:50 -msgid "The logs show up in `adb logcat`:" +#: src/modules/paths.md +msgid "Paths" +msgstr "Yollar (Paths)" + +#: src/modules/paths.md +msgid "Paths are resolved as follows:" msgstr "" -#: src/android/interoperability.md:3 -msgid "" -"Rust has excellent support for interoperability with other languages. This " -"means that you can:" +#: src/modules/paths.md +msgid "As a relative path:" msgstr "" -#: src/android/interoperability.md:6 -msgid "Call Rust functions from other languages." +#: src/modules/paths.md +msgid "`foo` or `self::foo` refers to `foo` in the current module," msgstr "" -#: src/android/interoperability.md:7 -msgid "Call functions written in other languages from Rust." +#: src/modules/paths.md +msgid "`super::foo` refers to `foo` in the parent module." msgstr "" -#: src/android/interoperability.md:9 -msgid "" -"When you call functions in a foreign language we say that you're using a " -"_foreign function interface_, also known as FFI." +#: src/modules/paths.md +msgid "As an absolute path:" msgstr "" -#: src/android/interoperability/with-c.md:1 -msgid "Interoperability with C" +#: src/modules/paths.md +msgid "`crate::foo` refers to `foo` in the root of the current crate," +msgstr "" + +#: src/modules/paths.md +msgid "`bar::foo` refers to `foo` in the `bar` crate." msgstr "" -#: src/android/interoperability/with-c.md:3 +#: src/modules/paths.md 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." +"It is common to \"re-export\" symbols at a shorter path. For example, the " +"top-level `lib.rs` in a crate might have" msgstr "" -#: src/android/interoperability/with-c.md:6 -msgid "You can do it by hand if you want:" +#: src/modules/paths.md +msgid "" +"making `DiskStorage` and `NetworkStorage` available to other crates with a " +"convenient, short path." msgstr "" -#: src/android/interoperability/with-c.md:8 +#: src/modules/paths.md msgid "" -"```rust\n" -"extern \"C\" {\n" -" fn abs(x: i32) -> i32;\n" -"}\n" -"\n" -"fn main() {\n" -" let x = -42;\n" -" let abs_x = unsafe { abs(x) };\n" -" println!(\"{x}, {abs_x}\");\n" -"}\n" -"```" +"For the most part, only items that appear in a module need to be `use`'d. " +"However, a trait must be in scope to call any methods on that trait, even if " +"a type implementing that trait is already in scope. For example, to use the " +"`read_to_string` method on a type implementing the `Read` trait, you need to " +"`use std::io::Read`." msgstr "" -#: src/android/interoperability/with-c.md:20 +#: src/modules/paths.md msgid "" -"We already saw this in the [Safe FFI Wrapper exercise](../../exercises/day-3/" -"safe-ffi-wrapper.md)." +"The `use` statement can have a wildcard: `use std::io::*`. This is " +"discouraged because it is not clear which items are imported, and those " +"might change over time." msgstr "" -#: src/android/interoperability/with-c.md:23 +#: src/modules/exercise.md msgid "" -"This assumes full knowledge of the target platform. Not recommended for " -"production." +"In this exercise, you will reorganize a small GUI Library implementation. " +"This library defines a `Widget` trait and a few implementations of that " +"trait, as well as a `main` function." msgstr "" -#: src/android/interoperability/with-c.md:26 -msgid "We will look at better options next." +#: src/modules/exercise.md +msgid "" +"It is typical to put each type or set of closely-related types into its own " +"module, so each widget type should get its own module." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:1 -msgid "Using Bindgen" +#: src/modules/exercise.md +#, fuzzy +msgid "Cargo Setup" +msgstr "Kurulum (Setup)" + +#: src/modules/exercise.md +msgid "" +"The Rust playground only supports one file, so you will need to make a Cargo " +"project on your local filesystem:" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:3 +#: src/modules/exercise.md msgid "" -"The [bindgen](https://rust-lang.github.io/rust-bindgen/introduction.html) " -"tool can auto-generate bindings from a C header file." +"Edit the resulting `src/main.rs` to add `mod` statements, and add additional " +"files in the `src` directory." msgstr "" -#: src/android/interoperability/with-c/bindgen.md:6 -msgid "First create a small C library:" +#: src/modules/exercise.md +msgid "Source" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:8 -msgid "_interoperability/bindgen/libbirthday.h_:" +#: src/modules/exercise.md +msgid "Here's the single-module implementation of the GUI library:" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:19 -msgid "_interoperability/bindgen/libbirthday.c_:" +#: src/modules/exercise.md src/modules/solution.md +msgid "/// Natural width of `self`.\n" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:21 -msgid "" -"```c\n" -"#include \n" -"#include \"libbirthday.h\"\n" -"\n" -"void print_card(const card* card) {\n" -" printf(\"+--------------\\n\");\n" -" printf(\"| Happy Birthday %s!\\n\", card->name);\n" -" printf(\"| Congratulations with the %i years!\\n\", card->years);\n" -" printf(\"+--------------\\n\");\n" -"}\n" -"```" +#: src/modules/exercise.md src/modules/solution.md +msgid "/// Draw the widget into a buffer.\n" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:33 -msgid "Add this to your `Android.bp` file:" +#: src/modules/exercise.md src/modules/solution.md +msgid "/// Draw the widget on standard output.\n" 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_:" +#: src/modules/exercise.md src/modules/solution.md +msgid "\"{buffer}\"" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:37 -msgid "" -"```javascript\n" -"cc_library {\n" -" name: \"libbirthday\",\n" -" srcs: [\"libbirthday.c\"],\n" -"}\n" -"```" +#: src/modules/exercise.md +msgid "// Add 4 paddings for borders\n" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:44 +#: src/modules/exercise.md msgid "" -"Create a wrapper header file for the library (not strictly needed in this " -"example):" +"// TODO: Change draw_into to return Result<(), std::fmt::Error>. Then use " +"the\n" +" // ?-operator here instead of .unwrap().\n" msgstr "" -#: src/android/interoperability/with-c/bindgen.md:47 -msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" +#: src/modules/exercise.md src/modules/solution.md +msgid "\"+-{:-. Then use\n" +" // the ?-operator here instead of .unwrap().\n" msgstr "" -#: 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." +#: src/modules/solution.md +msgid "// ---- src/main.rs ----\n" 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++." +#: src/testing.md +msgid "[Test Modules](./testing/unit-tests.md) (5 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:6 -msgid "The overall approach looks like this:" +#: src/testing.md +msgid "[Other Types of Tests](./testing/other.md) (10 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:10 -msgid "" -"See the [CXX tutorial](https://cxx.rs/tutorial.html) for an full example of " -"using this." +#: src/testing.md +msgid "[Useful Crates](./testing/useful-crates.md) (3 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:14 -msgid "" -"At this point, the instructor should switch to the [CXX tutorial](https://" -"cxx.rs/tutorial.html)." +#: src/testing.md +msgid "[GoogleTest](./testing/googletest.md) (5 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:16 -msgid "Walk the students through the tutorial step by step." +#: src/testing.md +msgid "[Mocking](./testing/mocking.md) (5 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:18 -msgid "" -"Highlight how CXX presents a clean interface without unsafe code in _both " -"languages_." +#: src/testing.md +msgid "[Compiler Lints and Clippy](./testing/lints.md) (5 minutes)" msgstr "" -#: src/android/interoperability/cpp.md:20 -msgid "" -"Show the correspondence between [Rust and C++ types](https://cxx.rs/bindings." -"html):" +#: src/testing.md +msgid "[Exercise: Luhn Algorithm](./testing/exercise.md) (30 minutes)" 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." +#: src/testing/unit-tests.md +msgid "Unit Tests" +msgstr "Birim Testleri" + +#: src/testing/unit-tests.md +msgid "Rust and Cargo come with a simple unit test framework:" 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)." +#: src/testing/unit-tests.md +msgid "Unit tests are supported throughout your code." msgstr "" -#: src/android/interoperability/java.md:1 -msgid "Interoperability with Java" +#: src/testing/unit-tests.md +msgid "Integration tests are supported via the `tests/` directory." msgstr "" -#: src/android/interoperability/java.md:3 +#: src/testing/unit-tests.md 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." +"Tests are marked with `#[test]`. Unit tests are often put in a nested " +"`tests` module, using `#[cfg(test)]` to conditionally compile them only when " +"building tests." msgstr "" -#: src/android/interoperability/java.md:7 -msgid "First, we create a Rust function to export to Java:" -msgstr "" +#: src/testing/unit-tests.md +#, fuzzy +msgid "\"Hello World\"" +msgstr "Merhaba Dünya!" -#: src/android/interoperability/java.md:9 -msgid "_interoperability/java/src/lib.rs_:" +#: src/testing/unit-tests.md +msgid "This lets you unit test private helpers." msgstr "" -#: src/android/interoperability/java.md:11 -msgid "" -"```rust,compile_fail\n" -"//! Rust <-> Java FFI demo.\n" -"\n" -"use jni::objects::{JClass, JString};\n" -"use jni::sys::jstring;\n" -"use jni::JNIEnv;\n" -"\n" -"/// HelloWorld::hello method implementation.\n" -"#[no_mangle]\n" -"pub extern \"system\" fn Java_HelloWorld_hello(\n" -" env: JNIEnv,\n" -" _class: JClass,\n" -" name: JString,\n" -") -> jstring {\n" -" let input: String = env.get_string(name).unwrap().into();\n" -" let greeting = format!(\"Hello, {input}!\");\n" -" let output = env.new_string(greeting).unwrap();\n" -" output.into_inner()\n" -"}\n" -"```" +#: src/testing/unit-tests.md +msgid "The `#[cfg(test)]` attribute is only active when you run `cargo test`." msgstr "" -#: src/android/interoperability/java.md:32 -#: src/android/interoperability/java.md:62 -msgid "_interoperability/java/Android.bp_:" +#: src/testing/unit-tests.md +msgid "Run the tests in the playground in order to show their results." msgstr "" -#: src/android/interoperability/java.md:34 -msgid "" -"```javascript\n" -"rust_ffi_shared {\n" -" name: \"libhello_jni\",\n" -" crate_name: \"hello_jni\",\n" -" srcs: [\"src/lib.rs\"],\n" -" rustlibs: [\"libjni\"],\n" -"}\n" -"```" -msgstr "" +#: src/testing/other.md +msgid "Integration Tests" +msgstr "Entegrasyon Testleri" -#: src/android/interoperability/java.md:43 -msgid "Finally, we can call this function from Java:" +#: src/testing/other.md +msgid "If you want to test your library as a client, use an integration test." msgstr "" -#: src/android/interoperability/java.md:45 -msgid "_interoperability/java/HelloWorld.java_:" +#: src/testing/other.md +msgid "Create a `.rs` file under `tests/`:" msgstr "" -#: src/android/interoperability/java.md:47 -msgid "" -"```java\n" -"class HelloWorld {\n" -" private static native String hello(String name);\n" -"\n" -" static {\n" -" System.loadLibrary(\"hello_jni\");\n" -" }\n" -"\n" -" public static void main(String[] args) {\n" -" String output = HelloWorld.hello(\"Alice\");\n" -" System.out.println(output);\n" -" }\n" -"}\n" -"```" +#: src/testing/other.md +msgid "// tests/my_library.rs\n" msgstr "" -#: src/android/interoperability/java.md:64 -msgid "" -"```javascript\n" -"java_binary {\n" -" name: \"helloworld_jni\",\n" -" srcs: [\"HelloWorld.java\"],\n" -" main_class: \"HelloWorld\",\n" -" required: [\"libhello_jni\"],\n" -"}\n" -"```" +#: src/testing/other.md +msgid "These tests only have access to the public API of your crate." msgstr "" -#: src/android/interoperability/java.md:73 -msgid "Finally, you can build, sync, and run the binary:" +#: src/testing/other.md +msgid "Documentation Tests" +msgstr "Dokümantasyon Testleri" + +#: src/testing/other.md +msgid "Rust has built-in support for documentation tests:" msgstr "" -#: src/exercises/android/morning.md:3 +#: src/testing/other.md 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:" +"/// 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/exercises/android/morning.md:6 -msgid "Call your AIDL service with a client written in Rust." +#: src/testing/other.md +msgid "Code blocks in `///` comments are automatically seen as Rust code." msgstr "" -#: src/exercises/android/morning.md:8 -msgid "Move a function from your project to Rust and call it." +#: src/testing/other.md +msgid "The code will be compiled and executed as part of `cargo test`." msgstr "" -#: src/exercises/android/morning.md:12 +#: src/testing/other.md 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." +"Adding `#` in the code will hide it from the docs, but will still compile/" +"run it." msgstr "" -#: src/bare-metal.md:1 -msgid "Welcome to Bare Metal Rust" +#: src/testing/other.md +msgid "" +"Test the above code on the [Rust Playground](https://play.rust-lang.org/?" +"version=stable&mode=debug&edition=2021&gist=3ce2ad13ea1302f6572cb15cd96becf0)." msgstr "" -#: src/bare-metal.md:3 -msgid "" -"This is a standalone one-day course about bare-metal Rust, aimed at people " -"who are familiar with the basics of Rust (perhaps from completing the " -"Comprehensive Rust course), and ideally also have some experience with bare-" -"metal programming in some other language such as C." +#: src/testing/useful-crates.md +msgid "Rust comes with only basic support for writing tests." +msgstr "" + +#: src/testing/useful-crates.md +msgid "Here are some additional crates which we recommend for writing tests:" msgstr "" -#: src/bare-metal.md:7 +#: src/testing/useful-crates.md msgid "" -"Today we will talk about 'bare-metal' Rust: running Rust code without an OS " -"underneath us. This will be divided into several parts:" +"[googletest](https://docs.rs/googletest): Comprehensive test assertion " +"library in the tradition of GoogleTest for C++." msgstr "" -#: src/bare-metal.md:10 -msgid "What is `no_std` Rust?" +#: src/testing/useful-crates.md +msgid "[proptest](https://docs.rs/proptest): Property-based testing for Rust." msgstr "" -#: src/bare-metal.md:11 -msgid "Writing firmware for microcontrollers." +#: src/testing/useful-crates.md +msgid "" +"[rstest](https://docs.rs/rstest): Support for fixtures and parameterised " +"tests." msgstr "" -#: src/bare-metal.md:12 -msgid "Writing bootloader / kernel code for application processors." +#: src/testing/googletest.md +msgid "" +"The [GoogleTest](https://docs.rs/googletest/) crate allows for flexible test " +"assertions using _matchers_:" msgstr "" -#: src/bare-metal.md:13 -msgid "Some useful crates for bare-metal Rust development." +#: src/testing/googletest.md +msgid "\"baz\"" +msgstr "" + +#: src/testing/googletest.md +msgid "\"xyz\"" msgstr "" -#: src/bare-metal.md:15 +#: src/testing/googletest.md 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." +"If we change the last element to `\"!\"`, the test fails with a structured " +"error message pin-pointing the error:" msgstr "" -#: src/bare-metal.md:20 +#: src/testing/googletest.md msgid "" -"To get started, install some tools we'll need later. On gLinux or Debian:" +"GoogleTest is not part of the Rust Playground, so you need to run this " +"example in a local environment. Use `cargo add googletest` to quickly add it " +"to an existing Cargo project." msgstr "" -#: src/bare-metal.md:30 +#: src/testing/googletest.md msgid "" -"And give users in the `plugdev` group access to the micro:bit programmer:" +"The `use googletest::prelude::*;` line imports a number of [commonly used " +"macros and types](https://docs.rs/googletest/latest/googletest/prelude/index." +"html)." msgstr "" -#: src/bare-metal.md:38 src/bare-metal/microcontrollers/debugging.md:27 -msgid "On MacOS:" +#: src/testing/googletest.md +msgid "This just scratches the surface, there are many builtin matchers." msgstr "" -#: src/bare-metal/no_std.md:1 -msgid "`no_std`" +#: src/testing/googletest.md +msgid "" +"A particularly nice feature is that mismatches in multi-line strings strings " +"are shown as a diff:" msgstr "" -#: src/bare-metal/no_std.md:7 -msgid "`core`" +#: src/testing/googletest.md +msgid "" +"\"Memory safety found,\\n\\\n" +" Rust's strong typing guides the way,\\n\\\n" +" Secure code you'll write.\"" msgstr "" -#: src/bare-metal/no_std.md:12 src/bare-metal/alloc.md:1 -msgid "`alloc`" +#: src/testing/googletest.md +msgid "" +"\"Memory safety found,\\n\\\n" +" Rust's silly humor guides the way,\\n\\\n" +" Secure code you'll write.\"" msgstr "" -#: src/bare-metal/no_std.md:17 -msgid "`std`" +#: src/testing/googletest.md +msgid "shows a color-coded diff (colors not shown here):" msgstr "" -#: src/bare-metal/no_std.md:24 -msgid "Slices, `&str`, `CStr`" +#: src/testing/googletest.md +msgid "" +"The crate is a Rust port of [GoogleTest for C++](https://google.github.io/" +"googletest/)." msgstr "" -#: src/bare-metal/no_std.md:25 -msgid "`NonZeroU8`..." +#: src/testing/googletest.md +msgid "GoogleTest is available for use in AOSP." msgstr "" -#: src/bare-metal/no_std.md:26 -msgid "`Option`, `Result`" +#: src/testing/mocking.md +msgid "" +"For mocking, [Mockall](https://docs.rs/mockall/) is a widely used library. " +"You need to refactor your code to use traits, which you can then quickly " +"mock:" msgstr "" -#: src/bare-metal/no_std.md:27 -msgid "`Display`, `Debug`, `write!`..." +#: src/testing/mocking.md +msgid "" +"The advice here is for Android (AOSP) where Mockall is the recommended " +"mocking library. There are other [mocking libraries available on crates.io]" +"(https://crates.io/keywords/mock), in particular in the area of mocking HTTP " +"services. The other mocking libraries work in a similar fashion as Mockall, " +"meaning that they make it easy to get a mock implementation of a given trait." msgstr "" -#: src/bare-metal/no_std.md:29 -msgid "`panic!`, `assert_eq!`..." +#: src/testing/mocking.md +msgid "" +"Note that mocking is somewhat _controversial_: mocks allow you to completely " +"isolate a test from its dependencies. The immediate result is faster and " +"more stable test execution. On the other hand, the mocks can be configured " +"wrongly and return output different from what the real dependencies would do." msgstr "" -#: src/bare-metal/no_std.md:30 -msgid "`NonNull` and all the usual pointer-related functions" +#: src/testing/mocking.md +msgid "" +"If at all possible, it is recommended that you use the real dependencies. As " +"an example, many databases allow you to configure an in-memory backend. This " +"means that you get the correct behavior in your tests, plus they are fast " +"and will automatically clean up after themselves." msgstr "" -#: src/bare-metal/no_std.md:31 -msgid "`Future` and `async`/`await`" +#: src/testing/mocking.md +msgid "" +"Similarly, many web frameworks allow you to start an in-process server which " +"binds to a random port on `localhost`. Always prefer this over mocking away " +"the framework since it helps you test your code in the real environment." msgstr "" -#: src/bare-metal/no_std.md:32 -msgid "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." +#: src/testing/mocking.md +msgid "" +"Mockall is not part of the Rust Playground, so you need to run this example " +"in a local environment. Use `cargo add mockall` to quickly add Mockall to an " +"existing Cargo project." msgstr "" -#: src/bare-metal/no_std.md:33 -msgid "`Duration`" +#: src/testing/mocking.md +msgid "" +"Mockall has a lot more functionality. In particular, you can set up " +"expectations which depend on the arguments passed. Here we use this to mock " +"a cat which becomes hungry 3 hours after the last time it was fed:" msgstr "" -#: src/bare-metal/no_std.md:38 -msgid "`Box`, `Cow`, `Arc`, `Rc`" +#: src/testing/mocking.md +msgid "" +"You can use `.times(n)` to limit the number of times a mock method can be " +"called to `n` --- the mock will automatically panic when dropped if this " +"isn't satisfied." msgstr "" -#: src/bare-metal/no_std.md:39 -msgid "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" +#: src/testing/lints.md +msgid "" +"The Rust compiler produces fantastic error messages, as well as helpful " +"built-in lints. [Clippy](https://doc.rust-lang.org/clippy/) provides even " +"more lints, organized into groups that can be enabled per-project." msgstr "" -#: src/bare-metal/no_std.md:40 -msgid "`String`, `CString`, `format!`" +#: src/testing/lints.md +msgid "\"X probably fits in a u16, right? {}\"" msgstr "" -#: src/bare-metal/no_std.md:45 -msgid "`Error`" +#: src/testing/lints.md +msgid "" +"Run the code sample and examine the error message. There are also lints " +"visible here, but those will not be shown once the code compiles. Switch to " +"the Playground site to show those lints." msgstr "" -#: src/bare-metal/no_std.md:47 -msgid "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" +#: src/testing/lints.md +msgid "" +"After resolving the lints, run `clippy` on the playground site to show " +"clippy warnings. Clippy has extensive documentation of its lints, and adds " +"new lints (including default-deny lints) all the time." msgstr "" -#: src/bare-metal/no_std.md:48 -msgid "`File` and the rest of `fs`" +#: src/testing/lints.md +msgid "" +"Note that errors or warnings with `help: ...` can be fixed with `cargo fix` " +"or via your editor." msgstr "" -#: src/bare-metal/no_std.md:49 -msgid "`println!`, `Read`, `Write`, `Stdin`, `Stdout` and the rest of `io`" +#: src/testing/exercise.md +msgid "Luhn Algorithm" +msgstr "Luhn Algrotiması" + +#: src/testing/exercise.md +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/bare-metal/no_std.md:50 -msgid "`Path`, `OsString`" +#: src/testing/exercise.md +msgid "Ignore all spaces. Reject number with less than two digits." msgstr "" -#: src/bare-metal/no_std.md:51 -msgid "`net`" +#: src/testing/exercise.md +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/bare-metal/no_std.md:52 -msgid "`Command`, `Child`, `ExitCode`" +#: src/testing/exercise.md +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/bare-metal/no_std.md:53 -msgid "`spawn`, `sleep` and the rest of `thread`" +#: src/testing/exercise.md +msgid "Sum all the undoubled and doubled digits." msgstr "" -#: src/bare-metal/no_std.md:54 -msgid "`SystemTime`, `Instant`" +#: src/testing/exercise.md +msgid "The credit card number is valid if the sum ends with `0`." msgstr "" -#: src/bare-metal/no_std.md:62 -msgid "`HashMap` depends on RNG." +#: src/testing/exercise.md +msgid "" +"The provided code provides a buggy implementation of the luhn algorithm, " +"along with two basic unit tests that confirm that most the algorithm is " +"implemented correctly." msgstr "" -#: src/bare-metal/no_std.md:63 -msgid "`std` re-exports the contents of both `core` and `alloc`." +#: src/testing/exercise.md +msgid "" +"Copy the code below to and write additional " +"tests to uncover bugs in the provided implementation, fixing any bugs you " +"find." msgstr "" -#: src/bare-metal/minimal.md:1 -msgid "A minimal `no_std` program" +#: src/testing/exercise.md src/testing/solution.md +msgid "\"4263 9826 4026 9299\"" msgstr "" -#: src/bare-metal/minimal.md:17 -msgid "This will compile to an empty binary." +#: src/testing/exercise.md src/testing/solution.md +msgid "\"4539 3195 0343 6467\"" msgstr "" -#: src/bare-metal/minimal.md:18 -msgid "`std` provides a panic handler; without it we must provide our own." +#: src/testing/exercise.md src/testing/solution.md +msgid "\"7992 7398 713\"" msgstr "" -#: src/bare-metal/minimal.md:19 -msgid "It can also be provided by another crate, such as `panic-halt`." +#: src/testing/exercise.md src/testing/solution.md +msgid "\"4223 9826 4026 9299\"" 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`." +#: src/testing/exercise.md src/testing/solution.md +msgid "\"4539 3195 0343 6476\"" 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." +#: src/testing/exercise.md src/testing/solution.md +msgid "\"8273 1232 7352 0569\"" 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)." +#: src/testing/solution.md +msgid "// This is the buggy version that appears in the problem.\n" msgstr "" -#: src/bare-metal/alloc.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate alloc;\n" -"extern crate panic_halt as _;\n" -"\n" -"use alloc::string::ToString;\n" -"use alloc::vec::Vec;\n" -"use buddy_system_allocator::LockedHeap;\n" -"\n" -"#[global_allocator]\n" -"static HEAP_ALLOCATOR: LockedHeap<32> = LockedHeap::<32>::new();\n" -"\n" -"static mut HEAP: [u8; 65536] = [0; 65536];\n" -"\n" -"pub fn entry() {\n" -" // Safe because `HEAP` is only used here and `entry` is only called " -"once.\n" -" unsafe {\n" -" // Give the allocator some memory to allocate.\n" -" HEAP_ALLOCATOR\n" -" .lock()\n" -" .init(HEAP.as_mut_ptr() as usize, HEAP.len());\n" -" }\n" -"\n" -" // Now we can do things that require heap allocation.\n" -" let mut v = Vec::new();\n" -" v.push(\"A string\".to_string());\n" -"}\n" -"```" +#: src/testing/solution.md +msgid "// This is the solution and passes all of the tests below.\n" msgstr "" -#: 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." +#: src/testing/solution.md +msgid "\"1234 5678 1234 5670\"" 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." +#: src/testing/solution.md +msgid "\"Is {cc_number} a valid credit card number? {}\"" msgstr "" -#: src/bare-metal/alloc.md:43 -msgid "" -"If any crate in your dependency tree depends on `alloc` then you must have " -"exactly one global allocator defined in your binary. Usually this is done in " -"the top-level binary crate." +#: src/testing/solution.md +msgid "\"yes\"" msgstr "" -#: src/bare-metal/alloc.md:45 -msgid "" -"`extern crate panic_halt as _` is necessary to ensure that the `panic_halt` " -"crate is linked in so we get its panic handler." +#: src/testing/solution.md +msgid "\"no\"" msgstr "" -#: src/bare-metal/alloc.md:47 -msgid "This example will build but not run, as it doesn't have an entry point." +#: src/testing/solution.md +msgid "\"foo 0 0\"" msgstr "" -#: src/bare-metal/microcontrollers.md:3 -msgid "" -"The `cortex_m_rt` crate provides (among other things) a reset handler for " -"Cortex M microcontrollers." +#: src/testing/solution.md +msgid "\" \"" msgstr "" -#: src/bare-metal/microcontrollers.md:21 -msgid "" -"Next we'll look at how to access peripherals, with increasing levels of " -"abstraction." +#: src/testing/solution.md +msgid "\" \"" 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." +#: src/testing/solution.md +msgid "\" \"" msgstr "" -#: src/bare-metal/microcontrollers.md:27 -msgid "Run the example with `cargo embed --bin minimal`" +#: src/testing/solution.md +msgid "\"0\"" 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:" +#: src/testing/solution.md +msgid "\" 0 0 \"" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"mod interrupts;\n" -"\n" -"use core::mem::size_of;\n" -"use cortex_m_rt::entry;\n" -"\n" -"/// GPIO port 0 peripheral address\n" -"const GPIO_P0: usize = 0x5000_0000;\n" -"\n" -"// GPIO peripheral offsets\n" -"const PIN_CNF: usize = 0x700;\n" -"const OUTSET: usize = 0x508;\n" -"const OUTCLR: usize = 0x50c;\n" -"\n" -"// PIN_CNF fields\n" -"const DIR_OUTPUT: u32 = 0x1;\n" -"const INPUT_DISCONNECT: u32 = 0x1 << 1;\n" -"const PULL_DISABLED: u32 = 0x0 << 2;\n" -"const DRIVE_S0S1: u32 = 0x0 << 8;\n" -"const SENSE_DISABLED: u32 = 0x0 << 16;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" let pin_cnf_21 = (GPIO_P0 + PIN_CNF + 21 * size_of::()) as *mut " -"u32;\n" -" let pin_cnf_28 = (GPIO_P0 + PIN_CNF + 28 * size_of::()) as *mut " -"u32;\n" -" // Safe because the pointers are to valid peripheral control registers, " -"and\n" -" // no aliases exist.\n" -" unsafe {\n" -" pin_cnf_21.write_volatile(\n" -" DIR_OUTPUT | INPUT_DISCONNECT | PULL_DISABLED | DRIVE_S0S1 | " -"SENSE_DISABLED,\n" -" );\n" -" pin_cnf_28.write_volatile(\n" -" DIR_OUTPUT | INPUT_DISCONNECT | PULL_DISABLED | DRIVE_S0S1 | " -"SENSE_DISABLED,\n" -" );\n" -" }\n" -"\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" let gpio0_outset = (GPIO_P0 + OUTSET) as *mut u32;\n" -" let gpio0_outclr = (GPIO_P0 + OUTCLR) as *mut u32;\n" -" // Safe because the pointers are to valid peripheral control registers, " -"and\n" -" // no aliases exist.\n" -" unsafe {\n" -" gpio0_outclr.write_volatile(1 << 28);\n" -" gpio0_outset.write_volatile(1 << 21);\n" -" }\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/welcome-day-4-afternoon.md +msgid "[Error Handling](./error-handling.md) (45 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:64 -msgid "" -"GPIO 0 pin 21 is connected to the first column of the LED matrix, and pin 28 " -"to the first row." +#: src/welcome-day-4-afternoon.md +msgid "[Unsafe Rust](./unsafe-rust.md) (1 hour and 5 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md:66 -#: src/bare-metal/microcontrollers/pacs.md:59 -#: src/bare-metal/microcontrollers/hals.md:43 -#: src/bare-metal/microcontrollers/board-support.md:34 -msgid "Run the example with:" +#: src/welcome-day-4-afternoon.md +msgid "Including 10 minute breaks, this session should take about 2 hours" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:1 -msgid "Peripheral Access Crates" +#: src/error-handling.md +msgid "[Panics](./error-handling/panics.md) (3 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:3 -msgid "" -"[`svd2rust`](https://crates.io/crates/svd2rust) generates mostly-safe Rust " -"wrappers for memory-mapped peripherals from [CMSIS-SVD](https://www.keil.com/" -"pack/doc/CMSIS/SVD/html/index.html) files." +#: src/error-handling.md +msgid "[Try Operator](./error-handling/try.md) (5 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use cortex_m_rt::entry;\n" -"use nrf52833_pac::Peripherals;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -" let gpio0 = p.P0;\n" -"\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" gpio0.pin_cnf[21].write(|w| {\n" -" w.dir().output();\n" -" w.input().disconnect();\n" -" w.pull().disabled();\n" -" w.drive().s0s1();\n" -" w.sense().disabled();\n" -" w\n" -" });\n" -" gpio0.pin_cnf[28].write(|w| {\n" -" w.dir().output();\n" -" w.input().disconnect();\n" -" w.pull().disabled();\n" -" w.drive().s0s1();\n" -" w.sense().disabled();\n" -" w\n" -" });\n" -"\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" gpio0.outclr.write(|w| w.pin28().clear());\n" -" gpio0.outset.write(|w| w.pin21().set());\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling.md +msgid "[Try Conversions](./error-handling/try-conversions.md) (5 minutes)" 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." +#: src/error-handling.md +msgid "[Error Trait](./error-handling/error.md) (5 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:51 +#: src/error-handling.md msgid "" -"They are organised by peripheral, register, field and value, with names, " -"descriptions, addresses and so on." +"[thiserror and anyhow](./error-handling/thiserror-and-anyhow.md) (5 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:53 +#: src/error-handling.md 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." +"[Exercise: Rewriting with Result](./error-handling/exercise.md) (20 minutes)" msgstr "" -#: src/bare-metal/microcontrollers/pacs.md:55 -msgid "`cortex-m-rt` provides the vector table, among other things." +#: src/error-handling/panics.md +msgid "Rust handles fatal errors with a \"panic\"." 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." +#: src/error-handling/panics.md +msgid "Rust will trigger a panic if a fatal error happens at runtime:" msgstr "" -#: src/bare-metal/microcontrollers/hals.md:1 -msgid "HAL crates" +#: src/error-handling/panics.md +msgid "\"v[100]: {}\"" 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)." +#: src/error-handling/panics.md +msgid "Panics are for unrecoverable and unexpected errors." msgstr "" -#: src/bare-metal/microcontrollers/hals.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use cortex_m_rt::entry;\n" -"use nrf52833_hal::gpio::{p0, Level};\n" -"use nrf52833_hal::pac::Peripherals;\n" -"use nrf52833_hal::prelude::*;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -"\n" -" // Create HAL wrapper for GPIO port 0.\n" -" let gpio0 = p0::Parts::new(p.P0);\n" -"\n" -" // Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" -" let mut col1 = gpio0.p0_28.into_push_pull_output(Level::High);\n" -" let mut row1 = gpio0.p0_21.into_push_pull_output(Level::Low);\n" -"\n" -" // Set pin 28 low and pin 21 high to turn the LED on.\n" -" col1.set_low().unwrap();\n" -" row1.set_high().unwrap();\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling/panics.md +msgid "Panics are symptoms of bugs in the program." msgstr "" -#: src/bare-metal/microcontrollers/hals.md:39 -msgid "" -"`set_low` and `set_high` are methods on the `embedded_hal` `OutputPin` trait." +#: src/error-handling/panics.md +msgid "Runtime failures like failed bounds checks can panic" 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." +#: src/error-handling/panics.md +msgid "Assertions (such as `assert!`) panic on failure" msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:1 -msgid "Board support crates" +#: src/error-handling/panics.md +msgid "Purpose-specific panics can use the `panic!` macro." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:3 +#: src/error-handling/panics.md msgid "" -"Board support crates provide a further level of wrapping for a specific " -"board for convenience." +"A panic will \"unwind\" the stack, dropping values just as if the functions " +"had returned." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:28 +#: src/error-handling/panics.md msgid "" -"In this case the board support crate is just providing more useful names, " -"and a bit of initialisation." +"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:30 +#: src/error-handling/panics.md msgid "" -"The crate may also include drivers for some on-board devices outside of the " -"microcontroller itself." +"By default, a panic will cause the stack to unwind. The unwinding can be " +"caught:" msgstr "" -#: src/bare-metal/microcontrollers/board-support.md:32 -msgid "`microbit-v2` includes a simple driver for the LED matrix." +#: src/error-handling/panics.md +msgid "\"No problem here!\"" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:1 -msgid "The type state pattern" +#: src/error-handling/panics.md +msgid "\"{result:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:3 -msgid "" -"```rust,editable,compile_fail\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let p = Peripherals::take().unwrap();\n" -" let gpio0 = p0::Parts::new(p.P0);\n" -"\n" -" let pin: P0_01 = gpio0.p0_01;\n" -"\n" -" // let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" -" let pin_input: P0_01> = pin.into_floating_input();\n" -" if pin_input.is_high().unwrap() {\n" -" // ...\n" -" }\n" -" let mut pin_output: P0_01> = pin_input\n" -" .into_open_drain_output(OpenDrainConfig::Disconnect0Standard1, " -"Level::Low);\n" -" pin_output.set_high().unwrap();\n" -" // pin_input.is_high(); // Error, moved.\n" -"\n" -" let _pin2: P0_02> = gpio0\n" -" .p0_02\n" -" .into_open_drain_output(OpenDrainConfig::Disconnect0Standard1, " -"Level::Low);\n" -" let _pin3: P0_03> = gpio0.p0_03." -"into_push_pull_output(Level::Low);\n" -"\n" -" loop {}\n" -"}\n" -"```" +#: src/error-handling/panics.md +msgid "\"oh no!\"" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:32 +#: src/error-handling/panics.md 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." +"Catching is unusual; do not attempt to implement exceptions with " +"`catch_unwind`!" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:34 +#: src/error-handling/panics.md msgid "" -"Changing the configuration of a pin consumes the old pin instance, so you " -"can’t keep use the old instance afterwards." +"This can be useful in servers which should keep running even if a single " +"request crashes." msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:36 -msgid "" -"The type of a value indicates the state that it is in: e.g. in this case, " -"the configuration state of a GPIO pin. This encodes the state machine into " -"the type system, and ensures that you don't try to use a pin in a certain " -"way without properly configuring it first. Illegal state transitions are " -"caught at compile time." +#: src/error-handling/panics.md +msgid "This does not work if `panic = 'abort'` is set in your `Cargo.toml`." msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:40 +#: src/error-handling/try.md msgid "" -"You can call `is_high` on an input pin and `set_high` on an output pin, but " -"not vice-versa." +"Runtime errors like connection-refused or file-not-found are handled with " +"the `Result` type, but matching this type on every call can be cumbersome. " +"The try-operator `?` is used to return errors to the caller. It lets you " +"turn the common" msgstr "" -#: src/bare-metal/microcontrollers/type-state.md:41 -msgid "Many HAL crates follow this pattern." +#: src/error-handling/try.md +msgid "into the much simpler" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:1 -msgid "`embedded-hal`" +#: src/error-handling/try.md +msgid "We can use this to simplify our error handling code:" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:3 -msgid "" -"The [`embedded-hal`](https://crates.io/crates/embedded-hal) crate provides a " -"number of traits covering common microcontroller peripherals." +#: src/error-handling/try.md +msgid "//fs::write(\"config.dat\", \"alice\").unwrap();\n" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:6 -msgid "GPIO" +#: src/error-handling/try.md src/error-handling/try-conversions.md +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"config.dat\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:7 -msgid "ADC" +#: src/error-handling/try.md src/error-handling/try-conversions.md +msgid "\"username or error: {username:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:8 -msgid "I2C, SPI, UART, CAN" +#: src/error-handling/try.md +msgid "Simplify the `read_username` function to use `?`." msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:9 -msgid "RNG" +#: src/error-handling/try.md +msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:10 -msgid "Timers" +#: src/error-handling/try.md +msgid "" +"Use the `fs::write` call to test out the different scenarios: no file, empty " +"file, file with username." msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:11 -msgid "Watchdogs" +#: src/error-handling/try.md +msgid "" +"Note that `main` can return a `Result<(), E>` as long as it implements `std::" +"process:Termination`. In practice, this means that `E` implements `Debug`. " +"The executable will print the `Err` variant and return a nonzero exit status " +"on error." msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:13 +#: src/error-handling/try-conversions.md 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." +"The effective expansion of `?` is a little more complicated than previously " +"indicated:" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:19 +#: src/error-handling/try-conversions.md +msgid "works the same as" +msgstr "" + +#: src/error-handling/try-conversions.md msgid "" -"There are implementations for many microcontrollers, as well as other " -"platforms such as Linux on Raspberry Pi." +"The `From::from` call here means we attempt to convert the error type to the " +"type returned by the function. This makes it easy to encapsulate errors into " +"higher-level errors." +msgstr "" + +#: src/error-handling/try-conversions.md +msgid "\"IO error: {e}\"" msgstr "" -#: src/bare-metal/microcontrollers/embedded-hal.md:21 +#: src/error-handling/try-conversions.md +msgid "\"Found no username in {path}\"" +msgstr "" + +#: src/error-handling/try-conversions.md +#: src/error-handling/thiserror-and-anyhow.md +msgid "//fs::write(\"config.dat\", \"\").unwrap();\n" +msgstr "" + +#: src/error-handling/try-conversions.md msgid "" -"There is work in progress on an `async` version of `embedded-hal`, but it " -"isn't stable yet." +"The `?` operator must return a value compatible with the return type of the " +"function. For `Result`, it means that the error types have to be compatible. " +"A function that returns `Result` can only use `?` on a value " +"of type `Result` if `ErrorOuter` and `ErrorInner` are the " +"same type or if `ErrorOuter` implements `From`." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:1 -msgid "`probe-rs`, `cargo-embed`" +#: src/error-handling/try-conversions.md +msgid "" +"A common alternative to a `From` implementation is `Result::map_err`, " +"especially when the conversion only happens in one place." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:3 +#: src/error-handling/try-conversions.md msgid "" -"[probe-rs](https://probe.rs/) is a handy toolset for embedded debugging, " -"like OpenOCD but better integrated." +"There is no compatibility requirement for `Option`. A function returning " +"`Option` can use the `?` operator on `Option` for arbitrary `T` and " +"`U` types." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:6 +#: src/error-handling/try-conversions.md msgid "" -"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" +"A function that returns `Result` cannot use `?` on `Option` and vice versa. " +"However, `Option::ok_or` converts `Option` to `Result` whereas `Result::ok` " +"turns `Result` into `Option`." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:7 -msgid "GDB stub and Microsoft DAP (Debug Adapter Protocol) server" +#: src/error-handling/error.md +msgid "Dynamic Error Types" +msgstr "Dinamik Hata Türleri" + +#: src/error-handling/error.md +msgid "" +"Sometimes we want to allow any type of error to be returned without writing " +"our own enum covering all the different possibilities. The `std::error::" +"Error` trait makes it easy to create a trait object that can contain any " +"error." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:8 -msgid "Cargo integration" +#: src/error-handling/error.md +msgid "\"count.dat\"" +msgstr "" + +#: src/error-handling/error.md +msgid "\"1i3\"" +msgstr "" + +#: src/error-handling/error.md +msgid "\"Count: {count}\"" +msgstr "" + +#: src/error-handling/error.md +msgid "\"Error: {err}\"" msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:10 +#: src/error-handling/error.md msgid "" -"`cargo-embed` is a cargo subcommand to build and flash binaries, log RTT " -"(Real Time Transfers) output and connect GDB. It's configured by an `Embed." -"toml` file in your project directory." +"The `read_count` function can return `std::io::Error` (from file operations) " +"or `std::num::ParseIntError` (from `String::parse`)." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:16 +#: src/error-handling/error.md 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." +"Boxing errors saves on code, but gives up the ability to cleanly handle " +"different error cases differently in the program. As such it's generally not " +"a good idea to use `Box` in the public API of a library, but it " +"can be a good option in a program where you just want to display the error " +"message somewhere." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:19 +#: src/error-handling/error.md msgid "" -"ST-Link is a range of in-circuit debuggers from ST Microelectronics, J-Link " -"is a range from SEGGER." +"Make sure to implement the `std::error::Error` trait when defining a custom " +"error type so it can be boxed. But if you need to support the `no_std` " +"attribute, keep in mind that the `std::error::Error` trait is currently " +"compatible with `no_std` in [nightly](https://github.com/rust-lang/rust/" +"issues/103765) only." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:21 +#: src/error-handling/thiserror-and-anyhow.md msgid "" -"The Debug Access Port is usually either a 5-pin JTAG interface or 2-pin " -"Serial Wire Debug." +"The [`thiserror`](https://docs.rs/thiserror/) and [`anyhow`](https://docs.rs/" +"anyhow/) crates are widely used to simplify error handling." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:22 +#: src/error-handling/thiserror-and-anyhow.md msgid "" -"probe-rs is a library which you can integrate into your own tools if you " -"want to." +"`thiserror` is often used in libraries to create custom error types that " +"implement `From`." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:23 +#: src/error-handling/thiserror-and-anyhow.md 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." +"`anyhow` is often used by applications to help with error handling in " +"functions, including adding contextual information to your errors." msgstr "" -#: src/bare-metal/microcontrollers/probe-rs.md:25 -msgid "cargo-embed is a binary built using the probe-rs library." +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"Found no username in {0}\"" 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." +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"Failed to open {path}\"" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:3 -msgid "_Embed.toml_:" +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"Failed to read\"" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:13 -msgid "In one terminal under `src/bare-metal/microcontrollers/examples/`:" +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"Username: {username}\"" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:19 -msgid "In another terminal in the same directory:" +#: src/error-handling/thiserror-and-anyhow.md +msgid "\"Error: {err:?}\"" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:21 -msgid "On gLinux or Debian:" +#: src/error-handling/thiserror-and-anyhow.md +msgid "`thiserror`" msgstr "" -#: src/bare-metal/microcontrollers/debugging.md:34 -msgid "In GDB, try running:" +#: src/error-handling/thiserror-and-anyhow.md +msgid "" +"The `Error` derive macro is provided by `thiserror`, and has lots of useful " +"attributes to help define error types in a compact way." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:1 -#: src/bare-metal/aps/other-projects.md:1 -msgid "Other projects" +#: src/error-handling/thiserror-and-anyhow.md +msgid "The `std::error::Error` trait is derived automatically." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:3 -msgid "[RTIC](https://rtic.rs/)" +#: src/error-handling/thiserror-and-anyhow.md +msgid "The message from `#[error]` is used to derive the `Display` trait." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:4 -msgid "\"Real-Time Interrupt-driven Concurrency\"" +#: src/error-handling/thiserror-and-anyhow.md +msgid "`anyhow`" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:5 +#: src/error-handling/thiserror-and-anyhow.md msgid "" -"Shared resource management, message passing, task scheduling, timer queue" +"`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/bare-metal/microcontrollers/other-projects.md:6 -msgid "[Embassy](https://embassy.dev/)" +#: src/error-handling/thiserror-and-anyhow.md +msgid "`anyhow::Result` is a type alias for `Result`." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:7 -msgid "`async` executors with priorities, timers, networking, USB" +#: src/error-handling/thiserror-and-anyhow.md +msgid "" +"Actual error type inside of it can be extracted for examination if necessary." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:8 -msgid "[TockOS](https://www.tockos.org/documentation/getting-started)" +#: src/error-handling/thiserror-and-anyhow.md +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/bare-metal/microcontrollers/other-projects.md:9 +#: src/error-handling/thiserror-and-anyhow.md msgid "" -"Security-focused RTOS with preemptive scheduling and Memory Protection Unit " -"support" +"`anyhow::Context` is a trait implemented for the standard `Result` and " +"`Option` types. `use anyhow::Context` is necessary to enable `.context()` " +"and `.with_context()` on those types." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:10 -msgid "[Hubris](https://hubris.oxide.computer/)" +#: src/error-handling/exercise.md +msgid "Exercise: Rewriting with Result" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:11 +#: src/error-handling/exercise.md msgid "" -"Microkernel RTOS from Oxide Computer Company with memory protection, " -"unprivileged drivers, IPC" +"The following implements a very simple parser for an expression language. " +"However, it handles errors by panicking. Rewrite it to instead use idiomatic " +"error handling and propagate errors to a return from `main`. Feel free to " +"use `thiserror` and `anyhow`." msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:12 -msgid "[Bindings for FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" +#: src/error-handling/exercise.md +msgid "" +"HINT: start by fixing error handling in the `parse` function. Once that is " +"working correctly, update `Tokenizer` to implement " +"`Iterator>` and handle that in the parser." msgstr "" -#: src/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)." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// An arithmetic operator.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:18 -msgid "RTIC can be considered either an RTOS or a concurrency framework." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// A token in the expression language.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:19 -msgid "It doesn't include any HALs." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// An expression in the expression language.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:20 -msgid "" -"It uses the Cortex-M NVIC (Nested Virtual Interrupt Controller) for " -"scheduling rather than a proper kernel." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// A reference to a variable.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:22 -msgid "Cortex-M only." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// A literal number.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:23 -msgid "" -"Google uses TockOS on the Haven microcontroller for Titan security keys." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "/// A binary operation.\n" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md:24 -msgid "" -"FreeRTOS is mostly written in C, but there are Rust bindings for writing " -"applications." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "'z'" 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." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "'_'" 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." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "'+'" msgstr "" -#: src/exercises/bare-metal/compass.md:6 -msgid "Hints:" +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "'-'" msgstr "" -#: src/exercises/bare-metal/compass.md:8 -msgid "" -"Check the documentation for the [`lsm303agr`](https://docs.rs/lsm303agr/" -"latest/lsm303agr/) and [`microbit-v2`](https://docs.rs/microbit-v2/latest/" -"microbit/) crates, as well as the [micro:bit hardware](https://tech.microbit." -"org/hardware/)." +#: src/error-handling/exercise.md +msgid "\"Unexpected character {c}\"" msgstr "" -#: src/exercises/bare-metal/compass.md:11 -msgid "" -"The LSM303AGR Inertial Measurement Unit is connected to the internal I2C bus." +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "\"Unexpected end of input\"" msgstr "" -#: src/exercises/bare-metal/compass.md:12 -msgid "" -"TWI is another name for I2C, so the I2C master peripheral is called TWIM." +#: src/error-handling/exercise.md +msgid "\"Invalid 32-bit integer'\"" msgstr "" -#: src/exercises/bare-metal/compass.md:13 +#: src/error-handling/exercise.md +msgid "\"Unexpected token {tok:?}\"" +msgstr "" + +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "// Look ahead to parse a binary operation if present.\n" +msgstr "" + +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "\"10+foo+20-30\"" +msgstr "" + +#: src/error-handling/exercise.md src/error-handling/solution.md +msgid "\"{expr:?}\"" +msgstr "" + +#: src/error-handling/solution.md +msgid "\"Unexpected character '{0}' in input\"" +msgstr "" + +#: src/error-handling/solution.md +msgid "\"Tokenizer error: {0}\"" +msgstr "" + +#: src/error-handling/solution.md +msgid "\"Unexpected token {0:?}\"" +msgstr "" + +#: src/error-handling/solution.md +msgid "\"Invalid number\"" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Unsafe](./unsafe-rust/unsafe.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md 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." +"[Dereferencing Raw Pointers](./unsafe-rust/dereferencing.md) (10 minutes)" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Mutable Static Variables](./unsafe-rust/mutable-static.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Unions](./unsafe-rust/unions.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Unsafe Functions](./unsafe-rust/unsafe-functions.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Unsafe Traits](./unsafe-rust/unsafe-traits.md) (5 minutes)" +msgstr "" + +#: src/unsafe-rust.md +msgid "[Exercise: FFI Wrapper](./unsafe-rust/exercise.md) (30 minutes)" +msgstr "" + +#: src/unsafe-rust/unsafe.md +msgid "The Rust language has two parts:" +msgstr "" + +#: src/unsafe-rust/unsafe.md +msgid "**Safe Rust:** memory safe, no undefined behavior possible." msgstr "" -#: src/exercises/bare-metal/compass.md:17 +#: src/unsafe-rust/unsafe.md 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." +"**Unsafe Rust:** can trigger undefined behavior if preconditions are " +"violated." msgstr "" -#: src/exercises/bare-metal/compass.md:19 +#: src/unsafe-rust/unsafe.md 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." +"We saw mostly safe Rust in this course, but it's important to know what " +"Unsafe Rust is." msgstr "" -#: src/exercises/bare-metal/compass.md:23 +#: src/unsafe-rust/unsafe.md msgid "" -"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " -"look in the `compass` directory for the following files." +"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/exercises/bare-metal/compass.md:26 src/exercises/bare-metal/rtc.md:19 -msgid "_src/main.rs_:" +#: src/unsafe-rust/unsafe.md +msgid "Unsafe Rust gives you access to five new capabilities:" msgstr "" -#: src/exercises/bare-metal/compass.md:30 -msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use core::fmt::Write;\n" -"use cortex_m_rt::entry;\n" -"use microbit::{hal::uarte::{Baudrate, Parity, Uarte}, Board};\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let board = Board::take().unwrap();\n" -"\n" -" // Configure serial port.\n" -" let mut serial = Uarte::new(\n" -" board.UARTE0,\n" -" board.uart.into(),\n" -" Parity::EXCLUDED,\n" -" Baudrate::BAUD115200,\n" -" );\n" -"\n" -" // Set up the I2C controller and Inertial Measurement Unit.\n" -" // TODO\n" -"\n" -" writeln!(serial, \"Ready.\").unwrap();\n" -"\n" -" loop {\n" -" // Read compass data and log it to the serial port.\n" -" // TODO\n" -" }\n" -"}\n" -"```" +#: src/unsafe-rust/unsafe.md +msgid "Dereference raw pointers." 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):" +#: src/unsafe-rust/unsafe.md +msgid "Access or modify mutable static variables." msgstr "" -#: src/exercises/bare-metal/compass.md:85 -msgid "_Embed.toml_ (you shouldn't need to change this):" +#: src/unsafe-rust/unsafe.md +msgid "Access `union` fields." msgstr "" -#: src/exercises/bare-metal/compass.md:100 src/exercises/bare-metal/rtc.md:985 -msgid "_.cargo/config.toml_ (you shouldn't need to change this):" +#: src/unsafe-rust/unsafe.md +msgid "Call `unsafe` functions, including `extern` functions." msgstr "" -#: src/exercises/bare-metal/compass.md:112 -msgid "See the serial output on Linux with:" +#: src/unsafe-rust/unsafe.md +msgid "Implement `unsafe` traits." msgstr "" -#: src/exercises/bare-metal/compass.md:118 +#: src/unsafe-rust/unsafe.md msgid "" -"Or on Mac OS something like (the device name may be slightly different):" +"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/exercises/bare-metal/compass.md:124 -msgid "Use Ctrl+A Ctrl+Q to quit picocom." +#: src/unsafe-rust/unsafe.md +msgid "" +"Unsafe Rust does not mean the code is incorrect. It means that developers " +"have turned off some compiler safety features and have to write correct code " +"by themselves. It means the compiler no longer enforces Rust's memory-safety " +"rules." msgstr "" -#: src/bare-metal/aps.md:1 -msgid "Application processors" +#: src/unsafe-rust/dereferencing.md +msgid "Creating pointers is safe, but dereferencing them requires `unsafe`:" +msgstr "" + +#: src/unsafe-rust/dereferencing.md +msgid "\"careful!\"" msgstr "" -#: src/bare-metal/aps.md:3 +#: src/unsafe-rust/dereferencing.md 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." +"// Safe because r1 and r2 were obtained from references and so are\n" +" // guaranteed to be non-null and properly aligned, the objects " +"underlying\n" +" // the references from which they were obtained are live throughout the\n" +" // whole unsafe block, and they are not accessed either through the\n" +" // references or concurrently through any other pointers.\n" +msgstr "" + +#: src/unsafe-rust/dereferencing.md +msgid "\"r1 is: {}\"" +msgstr "" + +#: src/unsafe-rust/dereferencing.md +msgid "\"uhoh\"" +msgstr "" + +#: src/unsafe-rust/dereferencing.md +msgid "\"r2 is: {}\"" msgstr "" -#: src/bare-metal/aps.md:9 +#: src/unsafe-rust/dereferencing.md 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." +"// NOT SAFE. DO NOT DO THIS.\n" +" /*\n" +" let r3: &String = unsafe { &*r1 };\n" +" drop(s);\n" +" println!(\"r3 is: {}\", *r3);\n" +" */" msgstr "" -#: src/bare-metal/aps.md:11 +#: src/unsafe-rust/dereferencing.md 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." +"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/bare-metal/aps/entry-point.md:3 +#: src/unsafe-rust/dereferencing.md msgid "" -"Before we can start running Rust code, we need to do some initialisation." +"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/bare-metal/aps/entry-point.md:5 +#: src/unsafe-rust/dereferencing.md +msgid "The pointer must be non-null." +msgstr "" + +#: src/unsafe-rust/dereferencing.md 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" -"```" +"The pointer must be _dereferenceable_ (within the bounds of a single " +"allocated object)." 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." +#: src/unsafe-rust/dereferencing.md +msgid "The object must not have been deallocated." 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." +#: src/unsafe-rust/dereferencing.md +msgid "There must not be concurrent accesses to the same location." msgstr "" -#: src/bare-metal/aps/entry-point.md:83 +#: src/unsafe-rust/dereferencing.md 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." +"If the pointer was obtained by casting a reference, the underlying object " +"must be live and no reference may be used to access the memory." msgstr "" -#: src/bare-metal/aps/entry-point.md:85 -msgid "" -"We need to enable the MMU and cache before reading or writing any memory. If " -"we don't:" +#: src/unsafe-rust/dereferencing.md +msgid "In most cases the pointer must also be properly aligned." msgstr "" -#: src/bare-metal/aps/entry-point.md:86 +#: src/unsafe-rust/dereferencing.md 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." +"The \"NOT SAFE\" section gives an example of a common kind of UB bug: `*r1` " +"has the `'static` lifetime, so `r3` has type `&'static String`, and thus " +"outlives `s`. Creating a reference from a pointer requires _great care_." msgstr "" -#: src/bare-metal/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.)" +#: src/unsafe-rust/mutable-static.md +msgid "It is safe to read an immutable static variable:" 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/unsafe-rust/mutable-static.md +#, fuzzy +msgid "\"Hello, world!\"" +msgstr "Merhaba Dünya!" -#: 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." +#: src/unsafe-rust/mutable-static.md +msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" msgstr "" -#: src/bare-metal/aps/entry-point.md:98 +#: src/unsafe-rust/mutable-static.md 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." +"However, since data races can occur, it is unsafe to read and write mutable " +"static variables:" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:1 -msgid "Inline assembly" +#: src/unsafe-rust/mutable-static.md +msgid "\"COUNTER: {COUNTER}\"" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:3 +#: src/unsafe-rust/mutable-static.md msgid "" -"Sometimes we need to use assembly to do things that aren't possible with " -"Rust code. For example, to make an HVC (hypervisor call) to tell the " -"firmware to power off the system:" +"The program here is safe because it is single-threaded. However, the Rust " +"compiler is conservative and will assume the worst. Try removing the " +"`unsafe` and see how the compiler explains that it is undefined behavior to " +"mutate a static from multiple threads." msgstr "" -#: src/bare-metal/aps/inline-assembly.md:6 +#: src/unsafe-rust/mutable-static.md msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"use core::arch::asm;\n" -"use core::panic::PanicInfo;\n" -"\n" -"mod exceptions;\n" -"\n" -"const PSCI_SYSTEM_OFF: u32 = 0x84000008;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(_x0: u64, _x1: u64, _x2: u64, _x3: u64) {\n" -" // Safe because this only uses the declared registers and doesn't do\n" -" // anything with memory.\n" -" unsafe {\n" -" asm!(\"hvc #0\",\n" -" inout(\"w0\") PSCI_SYSTEM_OFF => _,\n" -" inout(\"w1\") 0 => _,\n" -" inout(\"w2\") 0 => _,\n" -" inout(\"w3\") 0 => _,\n" -" inout(\"w4\") 0 => _,\n" -" inout(\"w5\") 0 => _,\n" -" inout(\"w6\") 0 => _,\n" -" inout(\"w7\") 0 => _,\n" -" options(nomem, nostack)\n" -" );\n" -" }\n" -"\n" -" loop {}\n" -"}\n" -"```" +"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/bare-metal/aps/inline-assembly.md:39 -msgid "" -"(If you actually want to do this, use the [`smccc`](https://crates.io/crates/" -"smccc) crate which has wrappers for all these functions.)" +#: src/unsafe-rust/unions.md +msgid "Unions are like enums, but you need to track the active field yourself:" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:43 -msgid "" -"PSCI is the Arm Power State Coordination Interface, a standard set of " -"functions to manage system and CPU power states, among other things. It is " -"implemented by EL3 firmware and hypervisors on many systems." +#: src/unsafe-rust/unions.md +msgid "\"int: {}\"" 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." +#: src/unsafe-rust/unions.md +msgid "\"bool: {}\"" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:49 -msgid "" -"This `main` function needs to be `#[no_mangle]` and `extern \"C\"` because " -"it is called from our entry point in `entry.S`." +#: src/unsafe-rust/unions.md +msgid "// Undefined behavior!\n" msgstr "" -#: src/bare-metal/aps/inline-assembly.md:51 +#: src/unsafe-rust/unions.md 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." +"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/bare-metal/aps/inline-assembly.md:56 +#: src/unsafe-rust/unions.md msgid "" -"Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" -"examples`." +"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/bare-metal/aps/mmio.md:1 -msgid "Volatile memory access for MMIO" -msgstr "" +#: src/unsafe-rust/unsafe-functions.md +msgid "Calling Unsafe Functions" +msgstr "Güvensiz (Unsafe) Fonksiyonları Çağırma" -#: src/bare-metal/aps/mmio.md:3 -msgid "Use `pointer::read_volatile` and `pointer::write_volatile`." +#: src/unsafe-rust/unsafe-functions.md +msgid "" +"A function or method can be marked `unsafe` if it has extra preconditions " +"you must uphold to avoid undefined behaviour:" msgstr "" -#: src/bare-metal/aps/mmio.md:4 -msgid "Never hold a reference." +#: src/unsafe-rust/unsafe-functions.md src/unsafe-rust/exercise.md +#: src/unsafe-rust/solution.md src/android/interoperability/with-c.md +#: src/android/interoperability/with-c/rust.md +#: src/android/interoperability/cpp/cpp-bridge.md +#: src/exercises/chromium/build-rules.md src/bare-metal/aps/inline-assembly.md +#: src/bare-metal/aps/better-uart/using.md src/bare-metal/aps/logging/using.md +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"C\"" msgstr "" -#: src/bare-metal/aps/mmio.md:5 -msgid "" -"`addr_of!` lets you get fields of structs without creating an intermediate " -"reference." +#: src/unsafe-rust/unsafe-functions.md +msgid "\"🗻∈🌏\"" msgstr "" -#: src/bare-metal/aps/mmio.md:9 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"Volatile access: read or write operations may have side-effects, so prevent " -"the compiler or hardware from reordering, duplicating or eliding them." +"// 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/bare-metal/aps/mmio.md:11 -msgid "" -"Usually if you write and then read, e.g. via a mutable reference, the " -"compiler may assume that the value read is the same as the value just " -"written, and not bother actually reading memory." +#: src/unsafe-rust/unsafe-functions.md +msgid "\"emoji: {}\"" msgstr "" -#: src/bare-metal/aps/mmio.md:13 -msgid "" -"Some existing crates for volatile access to hardware do hold references, but " -"this is unsound. Whenever a reference exist, the compiler may choose to " -"dereference it." +#: src/unsafe-rust/unsafe-functions.md +msgid "\"char count: {}\"" 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." +#: src/unsafe-rust/unsafe-functions.md +msgid "// Undefined behavior if abs misbehaves.\n" msgstr "" -#: src/bare-metal/aps/uart.md:1 -msgid "Let's write a UART driver" +#: src/unsafe-rust/unsafe-functions.md +msgid "\"Absolute value of -3 according to C: {}\"" msgstr "" -#: src/bare-metal/aps/uart.md:3 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"The QEMU 'virt' machine has a [PL011](https://developer.arm.com/" -"documentation/ddi0183/g) UART, so let's write a driver for that." +"// Not upholding the UTF-8 encoding requirement breaks memory safety!\n" +" // println!(\"emoji: {}\", unsafe { emojis.get_unchecked(0..3) });\n" +" // println!(\"char count: {}\", count_chars(unsafe {\n" +" // emojis.get_unchecked(0..3) }));\n" msgstr "" -#: src/bare-metal/aps/uart.md:5 -msgid "" -"```rust,editable\n" -"const FLAG_REGISTER_OFFSET: usize = 0x18;\n" -"const FR_BUSY: u8 = 1 << 3;\n" -"const FR_TXFF: u8 = 1 << 5;\n" -"\n" -"/// Minimal driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" base_address: *mut u8,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the 8 MMIO control registers of " -"a\n" -" /// PL011 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u8) -> Self {\n" -" Self { base_address }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register() & FR_TXFF != 0 {}\n" -"\n" -" // Safe because we know that the base address points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" self.base_address.write_volatile(byte);\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register() & FR_BUSY != 0 {}\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> u8 {\n" -" // Safe because we know that the base address points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { self.base_address.add(FLAG_REGISTER_OFFSET)." -"read_volatile() }\n" -" }\n" -"}\n" -"```" -msgstr "" +#: src/unsafe-rust/unsafe-functions.md +msgid "Writing Unsafe Functions" +msgstr "Güvensiz (Unsafe) Fonksiyonlar Yazma" -#: src/bare-metal/aps/uart.md:55 +#: src/unsafe-rust/unsafe-functions.md 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." +"You can mark your own functions as `unsafe` if they require particular " +"conditions to avoid undefined behaviour." msgstr "" -#: src/bare-metal/aps/uart.md:60 +#: src/unsafe-rust/unsafe-functions.md 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" +"/// 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/bare-metal/aps/uart.md:63 -msgid "" -"This is a common pattern for writing safe wrappers of unsafe code: moving " -"the burden of proof for soundness from a large number of places to a smaller " -"number of places." +#: src/unsafe-rust/unsafe-functions.md +msgid "// Safe because ...\n" msgstr "" -#: src/bare-metal/aps/uart/traits.md:1 -msgid "More traits" +#: src/unsafe-rust/unsafe-functions.md +msgid "\"a = {}, b = {}\"" msgstr "" -#: src/bare-metal/aps/uart/traits.md:3 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"We derived the `Debug` trait. It would be useful to implement a few more " -"traits too." +"`get_unchecked`, like most `_unchecked` functions, is unsafe, because it can " +"create UB if the range is incorrect. `abs` is incorrect for a different " +"reason: it is an external function (FFI). Calling external functions is " +"usually only a problem when those functions do things with pointers which " +"might violate Rust's memory model, but in general any C function might have " +"undefined behaviour under any arbitrary circumstances." msgstr "" -#: src/bare-metal/aps/uart/traits.md:5 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"```rust,editable,compile_fail\n" -"use core::fmt::{self, Write};\n" -"\n" -"impl Write for Uart {\n" -" fn write_str(&mut self, s: &str) -> fmt::Result {\n" -" for c in s.as_bytes() {\n" -" self.write_byte(*c);\n" -" }\n" -" Ok(())\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Uart {}\n" -"```" +"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/bare-metal/aps/uart/traits.md:24 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"Implementing `Write` lets us use the `write!` and `writeln!` macros with our " -"`Uart` type." +"We wouldn't actually use pointers for a `swap` function - it can be done " +"safely with references." msgstr "" -#: src/bare-metal/aps/uart/traits.md:25 +#: src/unsafe-rust/unsafe-functions.md msgid "" -"Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" -"examples`." +"Note that unsafe code is allowed within an unsafe function without an " +"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " +"Try adding it and see what happens. This will likely change in a future Rust " +"edition." msgstr "" -#: src/bare-metal/aps/better-uart.md:1 -msgid "A better UART driver" -msgstr "" +#: src/unsafe-rust/unsafe-traits.md +msgid "Implementing Unsafe Traits" +msgstr "Güvensiz Özelliklerin (Unsafe Traits) Gerçekleştirilmesi" -#: src/bare-metal/aps/better-uart.md:3 +#: src/unsafe-rust/unsafe-traits.md 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." +"Like with functions, you can mark a trait as `unsafe` if the implementation " +"must guarantee particular conditions to avoid undefined behaviour." msgstr "" -#: src/bare-metal/aps/better-uart.md:7 -msgid "Offset" +#: src/unsafe-rust/unsafe-traits.md +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/bare-metal/aps/better-uart.md:7 -msgid "Register name" +#: src/unsafe-rust/unsafe-traits.md +msgid "" +"/// ...\n" +"/// # Safety\n" +"/// The type must have a defined representation and no padding.\n" msgstr "" -#: src/bare-metal/aps/better-uart.md:7 -msgid "Width" +#: src/unsafe-rust/unsafe-traits.md +msgid "// Safe because u32 has a defined representation and no padding.\n" msgstr "" -#: src/bare-metal/aps/better-uart.md:9 -msgid "0x00" +#: src/unsafe-rust/unsafe-traits.md +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/bare-metal/aps/better-uart.md:9 -msgid "DR" +#: src/unsafe-rust/unsafe-traits.md +msgid "" +"The actual safety section for `AsBytes` is rather longer and more " +"complicated." msgstr "" -#: src/bare-metal/aps/better-uart.md:9 -msgid "12" +#: src/unsafe-rust/unsafe-traits.md +msgid "The built-in `Send` and `Sync` traits are unsafe." msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "0x04" -msgstr "" +#: src/unsafe-rust/exercise.md +msgid "Safe FFI Wrapper" +msgstr "Güvenli FFI Sarıcı (Wrapper)" -#: src/bare-metal/aps/better-uart.md:10 -msgid "RSR" +#: src/unsafe-rust/exercise.md +msgid "" +"Rust has great support for calling functions through a _foreign function " +"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " +"functions you would use from C to read the names of files in a directory." msgstr "" -#: src/bare-metal/aps/better-uart.md:10 -msgid "4" +#: src/unsafe-rust/exercise.md +msgid "You will want to consult the manual pages:" msgstr "" -#: src/bare-metal/aps/better-uart.md:11 -msgid "0x18" +#: src/unsafe-rust/exercise.md +msgid "[`opendir(3)`](https://man7.org/linux/man-pages/man3/opendir.3.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:11 -msgid "FR" +#: src/unsafe-rust/exercise.md +msgid "[`readdir(3)`](https://man7.org/linux/man-pages/man3/readdir.3.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:11 -msgid "9" +#: src/unsafe-rust/exercise.md +msgid "[`closedir(3)`](https://man7.org/linux/man-pages/man3/closedir.3.html)" msgstr "" -#: src/bare-metal/aps/better-uart.md:12 -msgid "0x20" +#: src/unsafe-rust/exercise.md +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/bare-metal/aps/better-uart.md:12 -msgid "ILPR" +#: src/unsafe-rust/exercise.md +msgid "Encoding" msgstr "" -#: src/bare-metal/aps/better-uart.md:12 src/bare-metal/aps/better-uart.md:15 -msgid "8" +#: src/unsafe-rust/exercise.md +msgid "Use" msgstr "" -#: src/bare-metal/aps/better-uart.md:13 -msgid "0x24" +#: src/unsafe-rust/exercise.md +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/bare-metal/aps/better-uart.md:13 -msgid "IBRD" +#: src/unsafe-rust/exercise.md +msgid "UTF-8" msgstr "" -#: src/bare-metal/aps/better-uart.md:13 src/bare-metal/aps/better-uart.md:16 -msgid "16" +#: src/unsafe-rust/exercise.md +msgid "Text processing in Rust" msgstr "" -#: src/bare-metal/aps/better-uart.md:14 -msgid "0x28" +#: src/unsafe-rust/exercise.md +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/bare-metal/aps/better-uart.md:14 -msgid "FBRD" +#: src/unsafe-rust/exercise.md +msgid "NUL-terminated" msgstr "" -#: src/bare-metal/aps/better-uart.md:14 src/bare-metal/aps/better-uart.md:17 -msgid "6" +#: src/unsafe-rust/exercise.md +msgid "Communicating with C functions" msgstr "" -#: src/bare-metal/aps/better-uart.md:15 -msgid "0x2c" +#: src/unsafe-rust/exercise.md +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/bare-metal/aps/better-uart.md:15 -msgid "LCR_H" +#: src/unsafe-rust/exercise.md +msgid "OS-specific" msgstr "" -#: src/bare-metal/aps/better-uart.md:16 -msgid "0x30" +#: src/unsafe-rust/exercise.md +msgid "Communicating with the OS" msgstr "" -#: src/bare-metal/aps/better-uart.md:16 -msgid "CR" +#: src/unsafe-rust/exercise.md +msgid "You will convert between all these types:" msgstr "" -#: src/bare-metal/aps/better-uart.md:17 -msgid "0x34" +#: src/unsafe-rust/exercise.md +msgid "" +"`&str` to `CString`: you need to allocate space for a trailing `\\0` " +"character," msgstr "" -#: src/bare-metal/aps/better-uart.md:17 -msgid "IFLS" +#: src/unsafe-rust/exercise.md +msgid "`CString` to `*const i8`: you need a pointer to call C functions," msgstr "" -#: src/bare-metal/aps/better-uart.md:18 -msgid "0x38" +#: src/unsafe-rust/exercise.md +msgid "" +"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " +"character," msgstr "" -#: src/bare-metal/aps/better-uart.md:18 -msgid "IMSC" +#: src/unsafe-rust/exercise.md +msgid "" +"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " +"unknown data\"," 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" +#: src/unsafe-rust/exercise.md +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/bare-metal/aps/better-uart.md:19 -msgid "0x3c" +#: src/unsafe-rust/exercise.md +msgid "" +"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " +"return it and call `readdir` again." msgstr "" -#: src/bare-metal/aps/better-uart.md:19 -msgid "RIS" +#: src/unsafe-rust/exercise.md +msgid "" +"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " +"useful chapter about FFI." msgstr "" -#: src/bare-metal/aps/better-uart.md:20 -msgid "0x40" +#: src/unsafe-rust/exercise.md +msgid "" +"Copy the code below to and fill in the missing " +"functions and methods:" msgstr "" -#: src/bare-metal/aps/better-uart.md:20 -msgid "MIS" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "\"macos\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:21 -msgid "0x44" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "// Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" msgstr "" -#: src/bare-metal/aps/better-uart.md:21 -msgid "ICR" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +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/bare-metal/aps/better-uart.md:22 -msgid "0x48" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "// Layout according to the macOS man page for dir(5).\n" msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "DMACR" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "\"x86_64\"" msgstr "" -#: src/bare-metal/aps/better-uart.md:22 -msgid "3" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +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/bare-metal/aps/better-uart.md:26 -msgid "There are also some ID registers which have been omitted for brevity." +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "\"readdir$INODE64\"" msgstr "" -#: src/bare-metal/aps/better-uart/bitflags.md:3 +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md msgid "" -"The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " -"working with bitflags." +"// Call opendir and return a Ok value if that worked,\n" +" // otherwise return Err with a message.\n" msgstr "" -#: src/bare-metal/aps/better-uart/bitflags.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use bitflags::bitflags;\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART flag register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct Flags: u16 {\n" -" /// Clear to send.\n" -" const CTS = 1 << 0;\n" -" /// Data set ready.\n" -" const DSR = 1 << 1;\n" -" /// Data carrier detect.\n" -" const DCD = 1 << 2;\n" -" /// UART busy transmitting data.\n" -" const BUSY = 1 << 3;\n" -" /// Receive FIFO is empty.\n" -" const RXFE = 1 << 4;\n" -" /// Transmit FIFO is full.\n" -" const TXFF = 1 << 5;\n" -" /// Receive FIFO is full.\n" -" const RXFF = 1 << 6;\n" -" /// Transmit FIFO is empty.\n" -" const TXFE = 1 << 7;\n" -" /// Ring indicator.\n" -" const RI = 1 << 8;\n" -" }\n" -"}\n" -"```" +#: src/unsafe-rust/exercise.md +msgid "// Keep calling readdir until we get a NULL pointer back.\n" msgstr "" -#: 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." +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "// Call closedir as needed.\n" msgstr "" -#: src/bare-metal/aps/better-uart/registers.md:1 -msgid "Multiple registers" +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +#: src/android/interoperability/with-c/rust.md +msgid "\".\"" msgstr "" -#: src/bare-metal/aps/better-uart/registers.md:3 -msgid "" -"We can use a struct to represent the memory layout of the UART's registers." +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +msgid "\"files: {:#?}\"" msgstr "" -#: src/bare-metal/aps/better-uart/registers.md:41 -msgid "" -"[`#[repr(C)]`](https://doc.rust-lang.org/reference/type-layout.html#the-c-" -"representation) tells the compiler to lay the struct fields out in order, " -"following the same rules as C. This is necessary for our struct to have a " -"predictable layout, as default Rust representation allows the compiler to " -"(among other things) reorder fields however it sees fit." +#: src/unsafe-rust/solution.md +msgid "\"Invalid path: {err}\"" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:3 -msgid "Now let's use the new `Registers` struct in our driver." +#: src/unsafe-rust/solution.md +msgid "// SAFETY: path.as_ptr() cannot be NULL.\n" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"/// Driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the 8 MMIO control registers of " -"a\n" -" /// PL011 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register().contains(Flags::TXFF) {}\n" -"\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" addr_of_mut!((*self.registers).dr).write_volatile(byte.into());\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register().contains(Flags::BUSY) {}\n" -" }\n" -"\n" -" /// Reads and returns a pending byte, or `None` if nothing has been " -"received.\n" -" pub fn read_byte(&self) -> Option {\n" -" if self.read_flag_register().contains(Flags::RXFE) {\n" -" None\n" -" } else {\n" -" let data = unsafe { addr_of!((*self.registers).dr)." -"read_volatile() };\n" -" // TODO: Check for error conditions in bits 8-11.\n" -" Some(data as u8)\n" -" }\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> Flags {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).fr).read_volatile() }\n" -" }\n" -"}\n" -"```" +#: src/unsafe-rust/solution.md +msgid "\"Could not open {:?}\"" msgstr "" -#: src/bare-metal/aps/better-uart/driver.md:64 +#: src/unsafe-rust/solution.md 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." +"// Keep calling readdir until we get a NULL pointer back.\n" +" // SAFETY: self.dir is never NULL.\n" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:1 -#: src/bare-metal/aps/logging/using.md:1 -msgid "Using it" +#: src/unsafe-rust/solution.md +msgid "// We have reached the end of the directory.\n" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:3 +#: src/unsafe-rust/solution.md msgid "" -"Let's write a small program using our driver to write to the serial console, " -"and echo incoming bytes." +"// SAFETY: dirent is not NULL and dirent.d_name is NUL\n" +" // terminated.\n" msgstr "" -#: src/bare-metal/aps/better-uart/using.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use core::panic::PanicInfo;\n" -"use log::error;\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let mut uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -"\n" -" writeln!(uart, \"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\").unwrap();\n" -"\n" -" loop {\n" -" if let Some(byte) = uart.read_byte() {\n" -" uart.write_byte(byte);\n" -" match byte {\n" -" b'\\r' => {\n" -" uart.write_byte(b'\\n');\n" -" }\n" -" b'q' => break,\n" -" _ => {}\n" -" }\n" -" }\n" -" }\n" -"\n" -" writeln!(uart, \"Bye!\").unwrap();\n" -" system_off::().unwrap();\n" -"}\n" -"```" +#: src/unsafe-rust/solution.md +msgid "// SAFETY: self.dir is not NULL.\n" 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." +#: src/unsafe-rust/solution.md +msgid "\"Could not close {:?}\"" 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`." +#: src/unsafe-rust/solution.md +msgid "\"no-such-directory\"" 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." +#: src/unsafe-rust/solution.md +msgid "\"Non UTF-8 character in path\"" msgstr "" -#: src/bare-metal/aps/logging.md:6 -msgid "" -"```rust,editable,compile_fail\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use log::{LevelFilter, Log, Metadata, Record, SetLoggerError};\n" -"use spin::mutex::SpinMutex;\n" -"\n" -"static LOGGER: Logger = Logger {\n" -" uart: SpinMutex::new(None),\n" -"};\n" -"\n" -"struct Logger {\n" -" uart: SpinMutex>,\n" -"}\n" -"\n" -"impl Log for Logger {\n" -" fn enabled(&self, _metadata: &Metadata) -> bool {\n" -" true\n" -" }\n" -"\n" -" fn log(&self, record: &Record) {\n" -" writeln!(\n" -" self.uart.lock().as_mut().unwrap(),\n" -" \"[{}] {}\",\n" -" record.level(),\n" -" record.args()\n" -" )\n" -" .unwrap();\n" -" }\n" -"\n" -" fn flush(&self) {}\n" -"}\n" -"\n" -"/// Initialises UART logger.\n" -"pub fn init(uart: Uart, max_level: LevelFilter) -> Result<(), " -"SetLoggerError> {\n" -" LOGGER.uart.lock().replace(uart);\n" -"\n" -" log::set_logger(&LOGGER)?;\n" -" log::set_max_level(max_level);\n" -" Ok(())\n" -"}\n" -"```" +#: src/unsafe-rust/solution.md +msgid "\"..\"" msgstr "" -#: src/bare-metal/aps/logging.md:50 -msgid "" -"The unwrap in `log` is safe because we initialise `LOGGER` before calling " -"`set_logger`." +#: src/unsafe-rust/solution.md +msgid "\"foo.txt\"" msgstr "" -#: src/bare-metal/aps/logging/using.md:3 -msgid "We need to initialise the logger before we use it." +#: src/unsafe-rust/solution.md +msgid "\"The Foo Diaries\\n\"" msgstr "" -#: src/bare-metal/aps/logging/using.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\");\n" -"\n" -" assert_eq!(x1, 42);\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" -"```" +#: src/unsafe-rust/solution.md +msgid "\"bar.png\"" msgstr "" -#: src/bare-metal/aps/logging/using.md:46 -msgid "Note that our panic handler can now log details of panics." +#: src/unsafe-rust/solution.md +msgid "\"\\n\"" msgstr "" -#: src/bare-metal/aps/logging/using.md:47 -msgid "" -"Run the example in QEMU with `make qemu_logger` under `src/bare-metal/aps/" -"examples`." +#: src/unsafe-rust/solution.md +msgid "\"crab.rs\"" 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:" +#: src/unsafe-rust/solution.md +msgid "\"//! Crab\\n\"" msgstr "" -#: src/bare-metal/aps/exceptions.md:64 -msgid "EL is exception level; all our examples this afternoon run in EL1." +#: src/android.md +msgid "Welcome to Rust in Android" msgstr "" -#: src/bare-metal/aps/exceptions.md:65 +#: src/android.md 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." +"Rust is supported for system software on Android. This means that you can " +"write new services, libraries, drivers or even firmware in Rust (or improve " +"existing code as needed)." msgstr "" -#: src/bare-metal/aps/exceptions.md:67 +#: src/android.md msgid "" -"For this example we just log the exception and power down, as we don't " -"expect any of them to actually happen." +"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/bare-metal/aps/exceptions.md:69 +#: src/android.md 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." +"The speaker may mention any of the following given the increased use of Rust " +"in Android:" msgstr "" -#: src/bare-metal/aps/other-projects.md:3 -msgid "[oreboot](https://github.com/oreboot/oreboot)" +#: src/android.md +msgid "" +"Service example: [DNS over HTTP](https://security.googleblog.com/2022/07/dns-" +"over-http3-in-android.html)" msgstr "" -#: src/bare-metal/aps/other-projects.md:4 -msgid "\"coreboot without the C\"" +#: src/android.md +msgid "" +"Libraries: [Rutabaga Virtual Graphics Interface](https://crosvm.dev/book/" +"appendix/rutabaga_gfx.html)" msgstr "" -#: src/bare-metal/aps/other-projects.md:5 -msgid "Supports x86, aarch64 and RISC-V." +#: src/android.md +msgid "" +"Kernel Drivers: [Binder](https://lore.kernel.org/rust-for-linux/20231101-" +"rust-binder-v1-0-08ba9197f637@google.com/)" msgstr "" -#: src/bare-metal/aps/other-projects.md:6 -msgid "Relies on LinuxBoot rather than having many drivers itself." +#: src/android.md +msgid "" +"Firmware: [pKVM firmware](https://security.googleblog.com/2023/10/bare-metal-" +"rust-in-android.html)" msgstr "" -#: src/bare-metal/aps/other-projects.md:7 +#: src/android/setup.md msgid "" -"[Rust RaspberryPi OS tutorial](https://github.com/rust-embedded/rust-" -"raspberrypi-OS-tutorials)" +"We will be using a Cuttlefish Android Virtual Device to test our code. Make " +"sure you have access to one or create a new one with:" msgstr "" -#: src/bare-metal/aps/other-projects.md:8 +#: src/android/setup.md msgid "" -"Initialisation, UART driver, simple bootloader, JTAG, exception levels, " -"exception handling, page tables" +"Please see the [Android Developer Codelab](https://source.android.com/docs/" +"setup/start) for details." msgstr "" -#: src/bare-metal/aps/other-projects.md:10 +#: src/android/setup.md msgid "" -"Some dodginess around cache maintenance and initialisation in Rust, not " -"necessarily a good example to copy for production code." +"Cuttlefish is a reference Android device designed to work on generic Linux " +"desktops. MacOS support is also planned." msgstr "" -#: src/bare-metal/aps/other-projects.md:12 -msgid "[`cargo-call-stack`](https://crates.io/crates/cargo-call-stack)" +#: src/android/setup.md +msgid "" +"The Cuttlefish system image maintains high fidelity to real devices, and is " +"the ideal emulator to run many Rust use cases." msgstr "" -#: src/bare-metal/aps/other-projects.md:13 -msgid "Static analysis to determine maximum stack usage." +#: src/android/build-rules.md +msgid "The Android build system (Soong) supports Rust via a number of modules:" msgstr "" -#: src/bare-metal/aps/other-projects.md:17 -msgid "" -"The RaspberryPi OS tutorial runs Rust code before the MMU and caches are " -"enabled. This will read and write memory (e.g. the stack). However:" +#: src/android/build-rules.md +msgid "Module Type" 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." +#: src/android/build-rules.md +msgid "Description" 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." +#: src/android/build-rules.md +msgid "`rust_binary`" 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." +#: src/android/build-rules.md +msgid "Produces a Rust binary." msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:1 -msgid "`zerocopy`" +#: src/android/build-rules.md +msgid "`rust_library`" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:3 -msgid "" -"The [`zerocopy`](https://docs.rs/zerocopy/) crate (from Fuchsia) provides " -"traits and macros for safely converting between byte sequences and other " -"types." +#: src/android/build-rules.md +msgid "Produces a Rust library, and provides both `rlib` and `dylib` variants." msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:40 -msgid "" -"This is not suitable for MMIO (as it doesn't use volatile reads and writes), " -"but can be useful for working with structures shared with hardware e.g. by " -"DMA, or sent over some external interface." +#: src/android/build-rules.md +msgid "`rust_ffi`" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:45 +#: src/android/build-rules.md 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." +"Produces a Rust C library usable by `cc` modules, and provides both static " +"and shared variants." msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:47 -msgid "" -"Attempting to derive `FromBytes` for these types would fail, because " -"`RequestType` doesn't use all possible u32 values as discriminants, so not " -"all byte patterns are valid." +#: src/android/build-rules.md +msgid "`rust_proc_macro`" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:49 +#: src/android/build-rules.md msgid "" -"`zerocopy::byteorder` has types for byte-order aware numeric primitives." +"Produces a `proc-macro` Rust library. These are analogous to compiler " +"plugins." +msgstr "" + +#: src/android/build-rules.md +msgid "`rust_test`" msgstr "" -#: src/bare-metal/useful-crates/zerocopy.md:50 +#: src/android/build-rules.md +msgid "Produces a Rust test binary that uses the standard Rust test harness." +msgstr "" + +#: src/android/build-rules.md +msgid "`rust_fuzz`" +msgstr "" + +#: src/android/build-rules.md +msgid "Produces a Rust fuzz binary leveraging `libfuzzer`." +msgstr "" + +#: src/android/build-rules.md +msgid "`rust_protobuf`" +msgstr "" + +#: src/android/build-rules.md 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.)" +"Generates source and produces a Rust library that provides an interface for " +"a particular protobuf." msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:1 -msgid "`aarch64-paging`" +#: src/android/build-rules.md +msgid "`rust_bindgen`" msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:3 +#: src/android/build-rules.md msgid "" -"The [`aarch64-paging`](https://crates.io/crates/aarch64-paging) crate lets " -"you create page tables according to the AArch64 Virtual Memory System " -"Architecture." +"Generates source and produces a Rust library containing Rust bindings to C " +"libraries." msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:6 +#: src/android/build-rules.md +msgid "We will look at `rust_binary` and `rust_library` next." +msgstr "" + +#: src/android/build-rules.md +msgid "Additional items speaker may mention:" +msgstr "" + +#: src/android/build-rules.md msgid "" -"```rust,editable,compile_fail\n" -"use aarch64_paging::{\n" -" idmap::IdMap,\n" -" paging::{Attributes, MemoryRegion},\n" -"};\n" -"\n" -"const ASID: usize = 1;\n" -"const ROOT_LEVEL: usize = 1;\n" -"\n" -"// Create a new page table with identity mapping.\n" -"let mut idmap = IdMap::new(ASID, ROOT_LEVEL);\n" -"// Map a 2 MiB region of memory as read-only.\n" -"idmap.map_range(\n" -" &MemoryRegion::new(0x80200000, 0x80400000),\n" -" Attributes::NORMAL | Attributes::NON_GLOBAL | Attributes::READ_ONLY,\n" -").unwrap();\n" -"// Set `TTBR0_EL1` to activate the page table.\n" -"idmap.activate();\n" -"```" +"Cargo is not optimized for multi-language repos, and also downloads packages " +"from the internet." msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:28 +#: src/android/build-rules.md msgid "" -"For now it only supports EL1, but support for other exception levels should " -"be straightforward to add." +"For compliance and performance, Android must have crates in-tree. It must " +"also interop with C/C++/Java code. Soong fills that gap." msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:30 +#: src/android/build-rules.md msgid "" -"This is used in Android for the [Protected VM Firmware](https://cs.android." -"com/android/platform/superproject/+/master:packages/modules/Virtualization/" -"pvmfw/)." +"Soong has many similarities to Bazel, which is the open-source variant of " +"Blaze (used in google3)." msgstr "" -#: src/bare-metal/useful-crates/aarch64-paging.md:31 +#: src/android/build-rules.md msgid "" -"There's no easy way to run this example, as it needs to run on real hardware " -"or under QEMU." +"There is a plan to transition [Android](https://source.android.com/docs/" +"setup/build/bazel/introduction), [ChromeOS](https://chromium.googlesource." +"com/chromiumos/bazel/), and [Fuchsia](https://source.android.com/docs/setup/" +"build/bazel/introduction) to Bazel." msgstr "" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:1 -msgid "`buddy_system_allocator`" +#: src/android/build-rules.md +msgid "Learning Bazel-like build rules is useful for all Rust OS developers." 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:" +#: src/android/build-rules.md +msgid "Fun fact: Data from Star Trek is a Soong-type Android." msgstr "" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:26 -msgid "PCI BARs always have alignment equal to their size." +#: src/android/build-rules/binary.md +msgid "Rust Binaries" msgstr "" -#: src/bare-metal/useful-crates/buddy_system_allocator.md:27 +#: src/android/build-rules/binary.md 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.)" +"Let us start with a simple application. At the root of an AOSP checkout, " +"create the following files:" msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:1 -msgid "`tinyvec`" +#: src/android/build-rules/binary.md src/android/build-rules/library.md +msgid "_hello_rust/Android.bp_:" 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." +#: src/android/build-rules/binary.md +msgid "\"hello_rust\"" msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:23 -msgid "" -"`tinyvec` requires that the element type implement `Default` for " -"initialisation." +#: src/android/build-rules/binary.md src/android/build-rules/library.md +#: src/android/logging.md +msgid "\"src/main.rs\"" msgstr "" -#: src/bare-metal/useful-crates/tinyvec.md:24 -msgid "" -"The Rust Playground includes `tinyvec`, so this example will run fine inline." +#: src/android/build-rules/binary.md src/android/build-rules/library.md +msgid "_hello_rust/src/main.rs_:" msgstr "" -#: src/bare-metal/useful-crates/spin.md:1 -msgid "`spin`" +#: src/android/build-rules/binary.md src/android/build-rules/library.md +msgid "//! Rust demo.\n" msgstr "" -#: src/bare-metal/useful-crates/spin.md:3 -msgid "" -"`std::sync::Mutex` and the other synchronisation primitives from `std::sync` " -"are not available in `core` or `alloc`. How can we manage synchronisation or " -"interior mutability, such as for sharing state between different CPUs?" +#: src/android/build-rules/binary.md src/android/build-rules/library.md +msgid "/// Prints a greeting to standard output.\n" msgstr "" -#: src/bare-metal/useful-crates/spin.md:7 -msgid "" -"The [`spin`](https://crates.io/crates/spin) crate provides spinlock-based " -"equivalents of many of these primitives." +#: src/android/build-rules/binary.md src/exercises/chromium/build-rules.md +msgid "\"Hello from Rust!\"" msgstr "" -#: src/bare-metal/useful-crates/spin.md:23 -msgid "Be careful to avoid deadlock if you take locks in interrupt handlers." +#: src/android/build-rules/binary.md +msgid "You can now build, push, and run the binary:" msgstr "" -#: src/bare-metal/useful-crates/spin.md:24 +#: src/android/build-rules/binary.md msgid "" -"`spin` also has a ticket lock mutex implementation; equivalents of `RwLock`, " -"`Barrier` and `Once` from `std::sync`; and `Lazy` for lazy initialisation." +"```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 "" -#: src/bare-metal/useful-crates/spin.md:26 -msgid "" -"The [`once_cell`](https://crates.io/crates/once_cell) crate also has some " -"useful types for late initialisation with a slightly different approach to " -"`spin::once::Once`." +#: src/android/build-rules/library.md +msgid "Rust Libraries" msgstr "" -#: src/bare-metal/useful-crates/spin.md:28 -msgid "" -"The Rust Playground includes `spin`, so this example will run fine inline." +#: src/android/build-rules/library.md +msgid "You use `rust_library` to create a new Rust library for Android." msgstr "" -#: src/bare-metal/android.md:3 -msgid "" -"To build a bare-metal Rust binary in AOSP, you need to use a " -"`rust_ffi_static` Soong rule to build your Rust code, then a `cc_binary` " -"with a linker script to produce the binary itself, and then a `raw_binary` " -"to convert the ELF to a raw binary ready to be run." +#: src/android/build-rules/library.md +msgid "Here we declare a dependency on two libraries:" msgstr "" -#: src/bare-metal/android/vmbase.md:3 -msgid "" -"For VMs running under crosvm on aarch64, the [vmbase](https://android." -"googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/" -"master/vmbase/) library provides a linker script and useful defaults for the " -"build rules, along with an entry point, UART console logging and more." +#: src/android/build-rules/library.md +msgid "`libgreeting`, which we define below," msgstr "" -#: src/bare-metal/android/vmbase.md:21 +#: src/android/build-rules/library.md msgid "" -"The `main!` macro marks your main function, to be called from the `vmbase` " -"entry point." +"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" +"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" +"crates/)." msgstr "" -#: src/bare-metal/android/vmbase.md:22 -msgid "" -"The `vmbase` entry point handles console initialisation, and issues a " -"PSCI_SYSTEM_OFF to shutdown the VM if your main function returns." +#: src/android/build-rules/library.md +msgid "\"hello_rust_with_dep\"" msgstr "" -#: src/exercises/bare-metal/afternoon.md:3 -msgid "We will write a driver for the PL031 real-time clock device." +#: src/android/build-rules/library.md +msgid "\"libgreetings\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:1 -#: src/exercises/bare-metal/solutions-afternoon.md:3 -msgid "RTC driver" +#: src/android/build-rules/library.md +msgid "\"libtextwrap\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:3 -msgid "" -"The QEMU aarch64 virt machine has a [PL031](https://developer.arm.com/" -"documentation/ddi0224/c) real-time clock at 0x9010000. For this exercise, " -"you should write a driver for it." +#: src/android/build-rules/library.md +msgid "// Need this to avoid dynamic link error.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:6 -msgid "" -"Use it to print the current time to the serial console. You can use the " -"[`chrono`](https://crates.io/crates/chrono) crate for date/time formatting." +#: src/android/build-rules/library.md +msgid "\"greetings\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:8 -msgid "" -"Use the match register and raw interrupt status to busy-wait until a given " -"time, e.g. 3 seconds in the future. (Call [`core::hint::spin_loop`](https://" -"doc.rust-lang.org/core/hint/fn.spin_loop.html) inside the loop.)" +#: src/android/build-rules/library.md src/android/aidl/implementation.md +#: src/android/interoperability/java.md +msgid "\"src/lib.rs\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:10 -msgid "" -"_Extension if you have time:_ Enable and handle the interrupt generated by " -"the RTC match. You can use the driver provided in the [`arm-gic`](https://" -"docs.rs/arm-gic/) crate to configure the Arm Generic Interrupt Controller." +#: src/android/build-rules/library.md +msgid "_hello_rust/src/lib.rs_:" msgstr "" -#: src/exercises/bare-metal/rtc.md:12 -msgid "Use the RTC interrupt, which is wired to the GIC as `IntId::spi(2)`." +#: src/android/build-rules/library.md +msgid "//! Greeting library.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:13 -msgid "" -"Once the interrupt is enabled, you can put the core to sleep via `arm_gic::" -"wfi()`, which will cause the core to sleep until it receives an interrupt." +#: src/android/build-rules/library.md +msgid "/// Greet `name`.\n" msgstr "" -#: src/exercises/bare-metal/rtc.md:16 -msgid "" -"Download the [exercise template](../../comprehensive-rust-exercises.zip) and " -"look in the `rtc` directory for the following files." +#: src/android/build-rules/library.md +msgid "\"Hello {name}, it is very nice to meet you!\"" +msgstr "" + +#: src/android/build-rules/library.md +msgid "You build, push, and run the binary like before:" msgstr "" -#: src/exercises/bare-metal/rtc.md:23 +#: src/android/build-rules/library.md msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"\n" -"use crate::pl011::Uart;\n" -"use arm_gic::gicv3::GicV3;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, trace, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base addresses of the GICv3.\n" -"const GICD_BASE_ADDRESS: *mut u64 = 0x800_0000 as _;\n" -"const GICR_BASE_ADDRESS: *mut u64 = 0x80A_0000 as _;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({:#x}, {:#x}, {:#x}, {:#x})\", x0, x1, x2, x3);\n" -"\n" -" // Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the " -"base\n" -" // addresses of a GICv3 distributor and redistributor respectively, and\n" -" // nothing else accesses those address ranges.\n" -" let mut gic = unsafe { GicV3::new(GICD_BASE_ADDRESS, " -"GICR_BASE_ADDRESS) };\n" -" gic.setup();\n" -"\n" -" // TODO: Create instance of RTC driver and print current time.\n" -"\n" -" // TODO: Wait for 3 seconds.\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" +"```shell\n" +"m 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 "" -#: src/exercises/bare-metal/rtc.md:75 +#: src/android/aidl.md msgid "" -"_src/exceptions.rs_ (you should only need to change this for the 3rd part of " -"the exercise):" +"The [Android Interface Definition Language (AIDL)](https://developer.android." +"com/guide/components/aidl) is supported in Rust:" +msgstr "" + +#: src/android/aidl.md +msgid "Rust code can call existing AIDL servers," +msgstr "" + +#: src/android/aidl.md +msgid "You can create new AIDL servers in Rust." +msgstr "" + +#: src/android/aidl/interface.md +msgid "AIDL Interfaces" +msgstr "" + +#: src/android/aidl/interface.md +msgid "You declare the API of your service using an AIDL interface:" msgstr "" -#: src/exercises/bare-metal/rtc.md:79 +#: src/android/aidl/interface.md msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"use arm_gic::gicv3::GicV3;\n" -"use log::{error, info, trace};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_exception_current(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_exception_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_current(_elr: u64, _spsr: u64) {\n" -" trace!(\"irq_current\");\n" -" let intid = GicV3::get_and_acknowledge_interrupt().expect(\"No pending " -"interrupt\");\n" -" info!(\"IRQ {intid:?}\");\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_current(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_current(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_current\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn sync_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"sync_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn irq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"irq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn fiq_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"fiq_lower\");\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn serr_lower(_elr: u64, _spsr: u64) {\n" -" error!(\"serr_lower\");\n" -" system_off::().unwrap();\n" -"}\n" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +msgstr "" + +#: src/android/aidl/interface.md src/android/aidl/changing.md +msgid "/** Birthday service interface. */" +msgstr "" + +#: src/android/aidl/interface.md src/android/aidl/changing.md +msgid "/** Generate a Happy Birthday message. */" +msgstr "" + +#: src/android/aidl/interface.md +msgid "_birthday_service/aidl/Android.bp_:" +msgstr "" + +#: src/android/aidl/interface.md +msgid "\"com.example.birthdayservice\"" +msgstr "" + +#: src/android/aidl/interface.md +msgid "\"com/example/birthdayservice/*.aidl\"" +msgstr "" + +#: src/android/aidl/interface.md +msgid "// Rust is not enabled by default\n" +msgstr "" + +#: src/android/aidl/interface.md +msgid "" +"Add `vendor_available: true` if your AIDL file is used by a binary in the " +"vendor partition." +msgstr "" + +#: src/android/aidl/implementation.md +msgid "Service Implementation" +msgstr "" + +#: src/android/aidl/implementation.md +msgid "We can now implement the AIDL service:" +msgstr "" + +#: src/android/aidl/implementation.md +msgid "_birthday_service/src/lib.rs_:" +msgstr "" + +#: src/android/aidl/implementation.md +msgid "//! Implementation of the `IBirthdayService` AIDL interface.\n" +msgstr "" + +#: src/android/aidl/implementation.md +msgid "/// The `IBirthdayService` implementation.\n" +msgstr "" + +#: src/android/aidl/implementation.md +msgid "\"Happy Birthday {name}, congratulations with the {years} years!\"" +msgstr "" + +#: src/android/aidl/implementation.md src/android/aidl/server.md +#: src/android/aidl/client.md +msgid "_birthday_service/Android.bp_:" +msgstr "" + +#: src/android/aidl/implementation.md src/android/aidl/server.md +msgid "\"libbirthdayservice\"" +msgstr "" + +#: src/android/aidl/implementation.md src/android/aidl/server.md +#: src/android/aidl/client.md +msgid "\"birthdayservice\"" +msgstr "" + +#: src/android/aidl/implementation.md src/android/aidl/server.md +#: src/android/aidl/client.md +msgid "\"com.example.birthdayservice-rust\"" +msgstr "" + +#: src/android/aidl/implementation.md src/android/aidl/server.md +#: src/android/aidl/client.md +msgid "\"libbinder_rs\"" +msgstr "" + +#: src/android/aidl/server.md +msgid "AIDL Server" +msgstr "" + +#: src/android/aidl/server.md +msgid "Finally, we can create a server which exposes the service:" +msgstr "" + +#: src/android/aidl/server.md +msgid "_birthday_service/src/server.rs_:" +msgstr "" + +#: src/android/aidl/server.md src/android/aidl/client.md +msgid "//! Birthday service.\n" +msgstr "" + +#: src/android/aidl/server.md +msgid "/// Entry point for birthday service.\n" +msgstr "" + +#: src/android/aidl/server.md +msgid "\"Failed to register service\"" +msgstr "" + +#: src/android/aidl/server.md +msgid "\"birthday_server\"" +msgstr "" + +#: src/android/aidl/server.md +msgid "\"src/server.rs\"" +msgstr "" + +#: src/android/aidl/server.md src/android/aidl/client.md +msgid "// To avoid dynamic link error.\n" +msgstr "" + +#: src/android/aidl/deploy.md +msgid "We can now build, push, and start the service:" +msgstr "" + +#: src/android/aidl/deploy.md +msgid "" +"```shell\n" +"m birthday_server\n" +"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server\" /data/local/" +"tmp\n" +"adb root\n" +"adb shell /data/local/tmp/birthday_server\n" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:149 -msgid "_src/logger.rs_ (you shouldn't need to change this):" +#: src/android/aidl/deploy.md +msgid "In another terminal, check that the service runs:" +msgstr "" + +#: src/android/aidl/deploy.md +msgid "You can also call the service with `service call`:" +msgstr "" + +#: src/android/aidl/client.md +msgid "AIDL Client" +msgstr "" + +#: src/android/aidl/client.md +msgid "Finally, we can create a Rust client for our new service." +msgstr "" + +#: src/android/aidl/client.md +msgid "_birthday_service/src/client.rs_:" +msgstr "" + +#: src/android/aidl/client.md +msgid "/// Connect to the BirthdayService.\n" +msgstr "" + +#: src/android/aidl/client.md +msgid "/// Call the birthday service.\n" +msgstr "" + +#: src/android/aidl/client.md +msgid "\"Failed to connect to BirthdayService\"" +msgstr "" + +#: src/android/aidl/client.md +msgid "\"{msg}\"" +msgstr "" + +#: src/android/aidl/client.md +msgid "\"birthday_client\"" +msgstr "" + +#: src/android/aidl/client.md +msgid "\"src/client.rs\"" +msgstr "" + +#: src/android/aidl/client.md +msgid "Notice that the client does not depend on `libbirthdayservice`." +msgstr "" + +#: src/android/aidl/client.md +msgid "Build, push, and run the client on your device:" msgstr "" -#: src/exercises/bare-metal/rtc.md:153 +#: src/android/aidl/client.md msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"// ANCHOR: main\n" -"use crate::pl011::Uart;\n" -"use core::fmt::Write;\n" -"use log::{LevelFilter, Log, Metadata, Record, SetLoggerError};\n" -"use spin::mutex::SpinMutex;\n" -"\n" -"static LOGGER: Logger = Logger {\n" -" uart: SpinMutex::new(None),\n" -"};\n" -"\n" -"struct Logger {\n" -" uart: SpinMutex>,\n" -"}\n" -"\n" -"impl Log for Logger {\n" -" fn enabled(&self, _metadata: &Metadata) -> bool {\n" -" true\n" -" }\n" -"\n" -" fn log(&self, record: &Record) {\n" -" writeln!(\n" -" self.uart.lock().as_mut().unwrap(),\n" -" \"[{}] {}\",\n" -" record.level(),\n" -" record.args()\n" -" )\n" -" .unwrap();\n" -" }\n" -"\n" -" fn flush(&self) {}\n" -"}\n" -"\n" -"/// Initialises UART logger.\n" -"pub fn init(uart: Uart, max_level: LevelFilter) -> Result<(), " -"SetLoggerError> {\n" -" LOGGER.uart.lock().replace(uart);\n" -"\n" -" log::set_logger(&LOGGER)?;\n" -" log::set_max_level(max_level);\n" -" Ok(())\n" -"}\n" +"```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 "" + +#: src/android/aidl/changing.md +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 +msgid "" +"You should use the `log` crate to automatically log to `logcat` (on-device) " +"or `stdout` (on-host):" +msgstr "" + +#: src/android/logging.md +msgid "_hello_rust_logs/Android.bp_:" +msgstr "" + +#: src/android/logging.md +msgid "\"hello_rust_logs\"" +msgstr "" + +#: src/android/logging.md +msgid "\"liblog_rust\"" +msgstr "" + +#: src/android/logging.md +msgid "\"liblogger\"" +msgstr "" + +#: src/android/logging.md +msgid "_hello_rust_logs/src/main.rs_:" +msgstr "" + +#: src/android/logging.md +msgid "//! Rust logging demo.\n" +msgstr "" + +#: src/android/logging.md +msgid "/// Logs a greeting.\n" +msgstr "" + +#: src/android/logging.md +msgid "\"rust\"" +msgstr "" + +#: src/android/logging.md +msgid "\"Starting program.\"" +msgstr "" + +#: src/android/logging.md +msgid "\"Things are going fine.\"" +msgstr "" + +#: src/android/logging.md +msgid "\"Something went wrong!\"" +msgstr "" + +#: src/android/logging.md src/android/interoperability/with-c/bindgen.md +#: src/android/interoperability/with-c/rust.md +msgid "Build, push, and run the binary on your device:" +msgstr "" + +#: src/android/logging.md +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 "" -#: src/exercises/bare-metal/rtc.md:210 -msgid "_src/pl011.rs_ (you shouldn't need to change this):" +#: src/android/logging.md +msgid "The logs show up in `adb logcat`:" +msgstr "" + +#: src/android/interoperability.md +msgid "" +"Rust has excellent support for interoperability with other languages. This " +"means that you can:" +msgstr "" + +#: src/android/interoperability.md +msgid "Call Rust functions from other languages." +msgstr "" + +#: src/android/interoperability.md +msgid "Call functions written in other languages from Rust." +msgstr "" + +#: src/android/interoperability.md +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 +msgid "Interoperability with C" +msgstr "" + +#: src/android/interoperability/with-c.md +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 +msgid "You can do it by hand if you want:" +msgstr "" + +#: src/android/interoperability/with-c.md +msgid "\"{x}, {abs_x}\"" +msgstr "" + +#: src/android/interoperability/with-c.md +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 +msgid "" +"This assumes full knowledge of the target platform. Not recommended for " +"production." +msgstr "" + +#: src/android/interoperability/with-c.md +msgid "We will look at better options next." +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "Using Bindgen" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +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 +msgid "First create a small C library:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "_interoperability/bindgen/libbirthday.h_:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "_interoperability/bindgen/libbirthday.c_:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday.h\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"+--------------\\n\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"| Happy Birthday %s!\\n\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"| Congratulations with the %i years!\\n\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "Add this to your `Android.bp` file:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "_interoperability/bindgen/Android.bp_:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday.c\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "" +"Create a wrapper header file for the library (not strictly needed in this " +"example):" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "_interoperability/bindgen/libbirthday_wrapper.h_:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "You can now auto-generate the bindings:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday_bindgen\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"birthday_bindgen\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday_wrapper.h\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"bindings\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "Finally, we can use the bindings in our Rust program:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"print_birthday_card\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"main.rs\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "_interoperability/bindgen/main.rs_:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "//! Bindgen demo.\n" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "// SAFETY: `print_card` is safe to call with a valid `card` pointer.\n" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +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 "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "Finally, we can run auto-generated tests to ensure the bindings work:" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"libbirthday_bindgen_test\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\":libbirthday_bindgen\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"general-tests\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "\"none\"" +msgstr "" + +#: src/android/interoperability/with-c/bindgen.md +msgid "// Generated file, skip linting\n" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "Calling Rust" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "Exporting Rust functions and types to C is easy:" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "_interoperability/rust/libanalyze/analyze.rs_" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "//! Rust FFI demo.\n" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "/// Analyze the numbers.\n" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"x ({x}) is smallest!\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"y ({y}) is probably larger than x ({x})\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "_interoperability/rust/libanalyze/analyze.h_" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "_interoperability/rust/libanalyze/Android.bp_" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"libanalyze_ffi\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"analyze_ffi\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"analyze.rs\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "We can now call this from a C binary:" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "_interoperability/rust/analyze/main.c_" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"analyze.h\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "_interoperability/rust/analyze/Android.bp_" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"analyze_numbers\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +msgid "\"main.c\"" +msgstr "" + +#: src/android/interoperability/with-c/rust.md +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 "" + +#: src/android/interoperability/with-c/rust.md +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 +msgid "" +"The [CXX crate](https://cxx.rs/) makes it possible to do safe " +"interoperability between Rust and C++." +msgstr "" + +#: src/android/interoperability/cpp.md +msgid "The overall approach looks like this:" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "" +"CXX relies on a description of the function signatures that will be exposed " +"from each language to the other. You provide this description using extern " +"blocks in a Rust module annotated with the `#[cxx::bridge]` attribute macro." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "\"org::blobstore\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "// Shared structs with fields visible to both languages.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/generated-cpp.md +msgid "// Rust types and signatures exposed to C++.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/rust-bridge.md +#: src/android/interoperability/cpp/generated-cpp.md +#: src/android/interoperability/cpp/rust-result.md +#: src/chromium/interoperability-with-cpp/example-bindings.md +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +#: src/chromium/interoperability-with-cpp/error-handling-png.md +#, fuzzy +msgid "\"Rust\"" +msgstr "Rust:" + +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "// C++ types and signatures exposed to Rust.\n" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/cpp-bridge.md +#: src/android/interoperability/cpp/cpp-exception.md +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "\"C++\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "\"include/blobstore.h\"" +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "The bridge is generally declared in an `ffi` module within your crate." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "" +"From the declarations made in the bridge module, CXX will generate matching " +"Rust and C++ type/function definitions in order to expose those items to " +"both languages." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "" +"To view the generated Rust code, use [cargo-expand](https://github.com/" +"dtolnay/cargo-expand) to view the expanded proc macro. For most of the " +"examples you would use `cargo expand ::ffi` to expand just the `ffi` module " +"(though this doesn't apply for Android projects)." +msgstr "" + +#: src/android/interoperability/cpp/bridge.md +msgid "To view the generated C++ code, look in `target/cxxbridge`." +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md +msgid "Rust Bridge Declarations" +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md +msgid "// Opaque type\n" +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md +msgid "// Method on `MyType`\n" +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md +#, fuzzy +msgid "// Free function\n" +msgstr "fonksiyon:" + +#: src/android/interoperability/cpp/rust-bridge.md +msgid "" +"Items declared in the `extern \"Rust\"` reference items that are in scope in " +"the parent module." +msgstr "" + +#: src/android/interoperability/cpp/rust-bridge.md +msgid "" +"The CXX code generator uses your `extern \"Rust\"` section(s) to produce a C+" +"+ header file containing the corresponding C++ declarations. The generated " +"header has the same path as the Rust source file containing the bridge, " +"except with a .rs.h file extension." +msgstr "" + +#: src/android/interoperability/cpp/generated-cpp.md +msgid "Results in (roughly) the following C++:" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "C++ Bridge Declarations" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "Results in (roughly) the following Rust:" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "\"org$blobstore$cxxbridge1$new_blobstore_client\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "\"org$blobstore$cxxbridge1$BlobstoreClient$put\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "" +"The programmer does not need to promise that the signatures they have typed " +"in are accurate. CXX performs static assertions that the signatures exactly " +"correspond with what is declared in C++." +msgstr "" + +#: src/android/interoperability/cpp/cpp-bridge.md +msgid "" +"`unsafe extern` blocks allow you to declare C++ functions that are safe to " +"call from Rust." +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md +msgid "// A=1, J=11, Q=12, K=13\n" +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md +msgid "Only C-like (unit) enums are supported." +msgstr "" + +#: src/android/interoperability/cpp/shared-types.md +msgid "" +"A limited number of traits are supported for `#[derive()]` on shared types. " +"Corresponding functionality is also generated for the C++ code, e.g. if you " +"derive `Hash` also generates an implementation of `std::hash` for the " +"corresponding C++ type." +msgstr "" + +#: src/android/interoperability/cpp/shared-enums.md +#, fuzzy +msgid "Generated Rust:" +msgstr "Güvensiz (Unsafe) Rust" + +#: src/android/interoperability/cpp/shared-enums.md +msgid "Generated C++:" +msgstr "" + +#: src/android/interoperability/cpp/shared-enums.md +msgid "" +"On the Rust side, the code generated for shared enums is actually a struct " +"wrapping a numeric value. This is because it is not UB in C++ for an enum " +"class to hold a value different from all of the listed variants, and our " +"Rust representation needs to have the same behavior." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md +msgid "\"fallible1 requires depth > 0\"" +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md +msgid "\"Success!\"" +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md +msgid "" +"Rust functions that return `Result` are translated to exceptions on the C++ " +"side." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md +msgid "" +"The exception thrown will always be of type `rust::Error`, which primarily " +"exposes a way to get the error message string. The error message will come " +"from the error type's `Display` impl." +msgstr "" + +#: src/android/interoperability/cpp/rust-result.md +msgid "" +"A panic unwinding from Rust to C++ will always cause the process to " +"immediately terminate." +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md +msgid "\"example/include/example.h\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md +msgid "\"Error: {}\"" +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md +msgid "" +"C++ functions declared to return a `Result` will catch any thrown exception " +"on the C++ side and return it as an `Err` value to the calling Rust function." +msgstr "" + +#: src/android/interoperability/cpp/cpp-exception.md +msgid "" +"If an exception is thrown from an extern \"C++\" function that is not " +"declared by the CXX bridge to return `Result`, the program calls C++'s `std::" +"terminate`. The behavior is equivalent to the same exception being thrown " +"through a `noexcept` C++ function." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +#, fuzzy +msgid "Rust Type" +msgstr "Özyinelemeli Veri Türleri" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "C++ Type" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +#, fuzzy +msgid "`rust::String`" +msgstr "String" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`&str`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`rust::Str`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +#, fuzzy +msgid "`CxxString`" +msgstr "String" + +#: src/android/interoperability/cpp/type-mapping.md +#, fuzzy +msgid "`std::string`" +msgstr "string:" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`&[T]`/`&mut [T]`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`rust::Slice`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`rust::Box`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`UniquePtr`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`std::unique_ptr`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`Vec`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`rust::Vec`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`CxxVector`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "`std::vector`" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "" +"These types can be used in the fields of shared structs and the arguments " +"and returns of extern functions." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "" +"Note that Rust's `String` does not map directly to `std::string`. There are " +"a few reasons for this:" +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "" +"`std::string` does not uphold the UTF-8 invariant that `String` requires." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "" +"The two types have different layouts in memory and so can't be passed " +"directly between languages." +msgstr "" + +#: src/android/interoperability/cpp/type-mapping.md +msgid "" +"`std::string` requires move constructors that don't match Rust's move " +"semantics, so a `std::string` can't be passed by value to Rust." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +#: src/android/interoperability/cpp/android-cpp-genrules.md +#: src/android/interoperability/cpp/android-build-rust.md +#, fuzzy +msgid "Building in Android" +msgstr "Android'de Rust" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "" +"Create a `cc_library_static` to build the C++ library, including the CXX " +"generated header and source file." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +#: src/android/interoperability/cpp/android-build-rust.md +msgid "\"libcxx_test_cpp\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "\"cxx_test.cpp\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "\"cxx-bridge-header\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"libcxx_test_bridge_header\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"libcxx_test_bridge_code\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "" +"Point out that `libcxx_test_bridge_header` and `libcxx_test_bridge_code` are " +"the dependencies for the CXX-generated C++ bindings. We'll show how these " +"are setup on the next slide." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "" +"Note that you also need to depend on the `cxx-bridge-header` library in " +"order to pull in common CXX definitions." +msgstr "" + +#: src/android/interoperability/cpp/android-build-cpp.md +msgid "" +"Full docs for using CXX in Android can be found in [the Android docs]" +"(https://source.android.com/docs/setup/build/rust/building-rust-modules/" +"android-rust-patterns#rust-cpp-interop-using-cxx). You may want to share " +"that link with the class so that students know where they can find these " +"instructions again in the future." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "" +"Create two genrules: One to generate the CXX header, and one to generate the " +"CXX source file. These are then used as inputs to the `cc_library_static`." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "" +"// Generate a C++ header containing the C++ bindings\n" +"// to the Rust exported functions in lib.rs.\n" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"cxxbridge\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"$(location cxxbridge) $(in) --header > $(out)\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +#: src/android/interoperability/cpp/android-build-rust.md +msgid "\"lib.rs\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"lib.rs.h\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "// Generate the C++ code that Rust calls into.\n" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"$(location cxxbridge) $(in) > $(out)\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "\"lib.rs.cc\"" +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "" +"The `cxxbridge` tool is a standalone tool that generates the C++ side of the " +"bridge module. It is included in Android and available as a Soong tool." +msgstr "" + +#: src/android/interoperability/cpp/android-cpp-genrules.md +msgid "" +"By convention, if your Rust source file is `lib.rs` your header file will be " +"named `lib.rs.h` and your source file will be named `lib.rs.cc`. This naming " +"convention isn't enforced, though." +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md +msgid "" +"Create a `rust_binary` that depends on `libcxx` and your `cc_library_static`." +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md +msgid "\"cxx_test\"" +msgstr "" + +#: src/android/interoperability/cpp/android-build-rust.md +msgid "\"libcxx\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "Interoperability with Java" +msgstr "" + +#: src/android/interoperability/java.md +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 +msgid "First, we create a Rust function to export to Java:" +msgstr "" + +#: src/android/interoperability/java.md +msgid "_interoperability/java/src/lib.rs_:" +msgstr "" + +#: src/android/interoperability/java.md +msgid "//! Rust <-> Java FFI demo.\n" +msgstr "" + +#: src/android/interoperability/java.md +msgid "/// HelloWorld::hello method implementation.\n" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"system\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"Hello, {input}!\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "_interoperability/java/Android.bp_:" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"libhello_jni\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"hello_jni\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"libjni\"" +msgstr "" + +#: src/android/interoperability/java.md +msgid "We then call this function from Java:" +msgstr "" + +#: src/android/interoperability/java.md +msgid "_interoperability/java/HelloWorld.java_:" +msgstr "" + +#: src/android/interoperability/java.md +msgid "\"helloworld_jni\"" +msgstr "" + +#: src/android/interoperability/java.md +#, fuzzy +msgid "\"HelloWorld.java\"" +msgstr "Merhaba Dünya!" + +#: src/android/interoperability/java.md +#, fuzzy +msgid "\"HelloWorld\"" +msgstr "Merhaba Dünya!" + +#: src/android/interoperability/java.md +msgid "Finally, you can build, sync, and run the binary:" +msgstr "" + +#: src/exercises/android/morning.md +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 +msgid "Call your AIDL service with a client written in Rust." +msgstr "" + +#: src/exercises/android/morning.md +msgid "Move a function from your project to Rust and call it." +msgstr "" + +#: src/exercises/android/morning.md +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/chromium.md +msgid "Welcome to Rust in Chromium" +msgstr "" + +#: src/chromium.md +msgid "" +"Rust is supported for third-party libraries in Chromium, with first-party " +"glue code to connect between Rust and existing Chromium C++ code." +msgstr "" + +#: src/chromium.md +msgid "" +"Today, we'll call into Rust to do something silly with strings. If you've " +"got a corner of the code where you're displaying a UTF8 string to the user, " +"feel free to follow this recipe in your part of the codebase instead of the " +"exact part we talk about." +msgstr "" + +#: src/chromium/setup.md +msgid "" +"Make sure you can build and run Chromium. Any platform and set of build " +"flags is OK, so long as your code is relatively recent (commit position " +"1223636 onwards, corresponding to November 2023):" +msgstr "" + +#: src/chromium/setup.md +msgid "" +"(A component, debug build is recommended for quickest iteration time. This " +"is the default!)" +msgstr "" + +#: src/chromium/setup.md +msgid "" +"See [How to build Chromium](https://www.chromium.org/developers/how-tos/get-" +"the-code/) if you aren't already at that point. Be warned: setting up to " +"build Chromium takes time." +msgstr "" + +#: src/chromium/setup.md +msgid "It's also recommended that you have Visual Studio code installed." +msgstr "" + +#: src/chromium/setup.md +msgid "About the exercises" +msgstr "" + +#: src/chromium/setup.md +msgid "" +"This part of the course has a series of exercises which build on each other. " +"We'll be doing them spread throughout the course instead of just at the end. " +"If you don't have time to complete a certain part, don't worry: you can " +"catch up in the next slot." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Rust community typically uses `cargo` and libraries from [crates.io](https://" +"crates.io/). Chromium is built using `gn` and `ninja` and a curated set of " +"dependencies." +msgstr "" + +#: src/chromium/cargo.md +msgid "When writing code in Rust, your choices are:" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Use `gn` and `ninja` with the help of the templates from `//build/rust/*." +"gni` (e.g. `rust_static_library` that we'll meet later). This uses " +"Chromium's audited toolchain and crates." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Use `cargo`, but [restrict yourself to Chromium's audited toolchain and " +"crates](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/" +"docs/rust.md#Using-cargo)" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Use `cargo`, trusting a [toolchain](https://rustup.rs/) and/or [crates " +"downloaded from the internet](https://crates.io/)" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"From here on we'll be focusing on `gn` and `ninja`, because this is how Rust " +"code can be built into the Chromium browser. At the same time, Cargo is an " +"important part of the Rust ecosystem and you should keep it in your toolbox." +msgstr "" + +#: src/chromium/cargo.md +#, fuzzy +msgid "Mini exercise" +msgstr "egzersiz:" + +#: src/chromium/cargo.md +msgid "Split into small groups and:" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Brainstorm scenarios where `cargo` may offer an advantage and assess the " +"risk profile of these scenarios." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Discuss which tools, libraries, and groups of people need to be trusted when " +"using `gn` and `ninja`, offline `cargo`, etc." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Ask students to avoid peeking at the speaker notes before completing the " +"exercise. Assuming folks taking the course are physically together, ask them " +"to discuss in small groups of 3-4 people." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Notes/hints related to the first part of the exercise (\"scenarios where " +"Cargo may offer an advantage\"):" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"It's fantastic that when writing a tool, or prototyping a part of Chromium, " +"one has access to the rich ecosystem of crates.io libraries. There is a " +"crate for almost anything and they are usually quite pleasant to use. " +"(`clap` for command-line parsing, `serde` for serializing/deserializing to/" +"from various formats, `itertools` for working with iterators, etc.)." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`cargo` makes it easy to try a library (just add a single line to `Cargo." +"toml` and start writing code)" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"It may be worth comparing how CPAN helped make `perl` a popular choice. Or " +"comparing with `python` + `pip`." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Development experience is made really nice not only by core Rust tools (e.g. " +"using `rustup` to switch to a different `rustc` version when testing a crate " +"that needs to work on nightly, current stable, and older stable) but also by " +"an ecosystem of third-party tools (e.g. Mozilla provides `cargo vet` for " +"streamlining and sharing security audits; `criterion` crate gives a " +"streamlined way to run benchmarks)." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`cargo` makes it easy to add a tool via `cargo install --locked cargo-vet`." +msgstr "" + +#: src/chromium/cargo.md +msgid "It may be worth comparing with Chrome Extensions or VScode extensions." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Broad, generic examples of projects where `cargo` may be the right choice:" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Perhaps surprisingly, Rust is becoming increasingly popular in the industry " +"for writing command line tools. The breadth and ergonomics of libraries is " +"comparable to Python, while being more robust (thanks to the rich " +"typesystem) and running faster (as a compiled, rather than interpreted " +"language)." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Participating in the Rust ecosystem requires using standard Rust tools like " +"Cargo. Libraries that want to get external contributions, and want to be " +"used outside of Chromium (e.g. in Bazel or Android/Soong build environments) " +"should probably use Cargo." +msgstr "" + +#: src/chromium/cargo.md +msgid "Examples of Chromium-related projects that are `cargo`\\-based:" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`serde_json_lenient` (experimented with in other parts of Google which " +"resulted in PRs with performance improvements)" +msgstr "" + +#: src/chromium/cargo.md +msgid "Fontations libraries like `font-types`" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`gnrt` tool (we will meet it later in the course) which depends on `clap` " +"for command-line parsing and on `toml` for configuration files." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Disclaimer: a unique reason for using `cargo` was unavailability of `gn` " +"when building and bootstrapping Rust standard library when building Rust " +"toolchain.)" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`run_gnrt.py` uses Chromium's copy of `cargo` and `rustc`. `gnrt` depends on " +"third-party libraries downloaded from the internet, by `run_gnrt.py` asks " +"`cargo` that only `--locked` content is allowed via `Cargo.lock`.)" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Students may identify the following items as being implicitly or explicitly " +"trusted:" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`rustc` (the Rust compiler) which in turn depends on the LLVM libraries, the " +"Clang compiler, the `rustc` sources (fetched from GitHub, reviewed by Rust " +"compiler team), binary Rust compiler downloaded for bootstrapping" +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"`rustup` (it may be worth pointing out that `rustup` is developed under the " +"umbrella of the https://github.com/rust-lang/ organization - same as `rustc`)" +msgstr "" + +#: src/chromium/cargo.md +msgid "`cargo`, `rustfmt`, etc." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Various internal infrastructure (bots that build `rustc`, system for " +"distributing the prebuilt toolchain to Chromium engineers, etc.)" +msgstr "" + +#: src/chromium/cargo.md +msgid "Cargo tools like `cargo audit`, `cargo vet`, etc." +msgstr "" + +#: src/chromium/cargo.md +msgid "" +"Rust libraries vendored into `//third_party/rust` (audited by " +"security@chromium.org)" +msgstr "" + +#: src/chromium/cargo.md +msgid "Other Rust libraries (some niche, some quite popular and commonly used)" +msgstr "" + +#: src/chromium/policy.md +msgid "Chromium Rust policy" +msgstr "" + +#: src/chromium/policy.md +msgid "" +"Chromium does not yet allow first-party Rust except in rare cases as " +"approved by Chromium's [Area Tech Leads](https://source.chromium.org/" +"chromium/chromium/src/+/main:ATL_OWNERS)." +msgstr "" + +#: src/chromium/policy.md +msgid "" +"Chromium's policy on third party libraries is outlined [here](https://" +"chromium.googlesource.com/chromium/src/+/main/docs/adding_to_third_party." +"md#rust) - Rust is allowed for third party libraries under various " +"circumstances, including if they're the best option for performance or for " +"security." +msgstr "" + +#: src/chromium/policy.md +msgid "" +"Very few Rust libraries directly expose a C/C++ API, so that means that " +"nearly all such libraries will require a small amount of first-party glue " +"code." +msgstr "" + +#: src/chromium/policy.md +msgid "" +"```bob\n" +"\"C++\" Rust\n" +".- - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - " +"-.\n" +": : : :\n" +": Existing Chromium : : Chromium Rust Existing " +"Rust :\n" +": \"C++\" : : \"wrapper\" " +"crate :\n" +": +---------------+ : : +----------------+ +-------------" +"+ :\n" +": | | : : | | | " +"| :\n" +": | o-----+-+-----------+-+-> o-+----------+--> " +"| :\n" +": | | : Language : | | Crate | " +"| :\n" +": +---------------+ : boundary : +----------------+ API +-------------" +"+ :\n" +": : : :\n" +"`- - - - - - - - - -' `- - - - - - - - - - - - - - - - - - - - - - " +"-'\n" +"```" +msgstr "" + +#: src/chromium/policy.md +msgid "" +"First-party Rust glue code for a particular third-party crate should " +"normally be kept in `third_party/rust///wrapper`." +msgstr "" + +#: src/chromium/policy.md +msgid "Because of this, today's course will be heavily focused on:" +msgstr "" + +#: src/chromium/policy.md +msgid "Bringing in third-party Rust libraries (\"crates\")" +msgstr "" + +#: src/chromium/policy.md +msgid "Writing glue code to be able to use those crates from Chromium C++." +msgstr "" + +#: src/chromium/policy.md +msgid "If this policy changes over time, the course will evolve to keep up." +msgstr "" + +#: src/chromium/build-rules.md +#, fuzzy +msgid "Build rules" +msgstr "İnşa (Build) Kuralları" + +#: src/chromium/build-rules.md +msgid "" +"Rust code is usually built using `cargo`. Chromium builds with `gn` and " +"`ninja` for efficiency --- its static rules allow maximum parallelism. Rust " +"is no exception." +msgstr "" + +#: src/chromium/build-rules.md +msgid "Adding Rust code to Chromium" +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"In some existing Chromium `BUILD.gn` file, declare a `rust_static_library`:" +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"You can also add `deps` on other Rust targets. Later we'll use this to " +"depend upon third party code." +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"You must specify _both_ the crate root, _and_ a full list of sources. The " +"`crate_root` is the file given to the Rust compiler representing the root " +"file of the compilation unit --- typically `lib.rs`. `sources` is a complete " +"list of all source files which `ninja` needs in order to determine when " +"rebuilds are necessary." +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"(There's no such thing as a Rust `source_set`, because in Rust, an entire " +"crate is a compilation unit. A `static_library` is the smallest unit.)" +msgstr "" + +#: src/chromium/build-rules.md +msgid "" +"Students might be wondering why we need a gn template, rather than using " +"[gn's built-in support for Rust static libraries](https://gn.googlesource." +"com/gn/+/main/docs/reference.md#func_static_library). The answer is that " +"this template provides support for CXX interop, Rust features, and unit " +"tests, some of which we'll use later." +msgstr "" + +#: src/chromium/build-rules/unsafe.md +msgid "Including `unsafe` Rust Code" +msgstr "" + +#: src/chromium/build-rules/unsafe.md +msgid "" +"Unsafe Rust code is forbidden in `rust_static_library` by default --- it " +"won't compile. If you need unsafe Rust code, add `allow_unsafe = true` to " +"the gn target. (Later in the course we'll see circumstances where this is " +"necessary.)" +msgstr "" + +#: src/chromium/build-rules/unsafe.md +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [\n" +" \"lib.rs\",\n" +" \"hippopotamus.rs\"\n" +" ]\n" +" allow_unsafe = true\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules/depending.md +msgid "Simply add the above target to the `deps` of some Chromium C++ target." +msgstr "" + +#: src/chromium/build-rules/depending.md +msgid "" +"```gn\n" +"import(\"//build/rust/rust_static_library.gni\")\n" +"\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +"}\n" +"\n" +"# or source_set, static_library etc.\n" +"component(\"preexisting_cpp\") {\n" +" deps = [ \":my_rust_lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Types are elided in Rust code, which makes a good IDE even more useful than " +"for C++. Visual Studio code works well for Rust in Chromium. To use it," +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Ensure your VSCode has the `rust-analyzer` extension, not earlier forms of " +"Rust support" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"`gn gen out/Debug --export-rust-project` (or equivalent for your output " +"directory)" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "`ln -s out/Debug/rust-project.json rust-project.json`" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"A demo of some of the code annotation and exploration features of rust-" +"analyzer might be beneficial if the audience are naturally skeptical of IDEs." +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"The following steps may help with the demo (but feel free to instead use a " +"piece of Chromium-related Rust that you are most familiar with):" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "Open `components/qr_code_generator/qr_code_generator_ffi_glue.rs`" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Place the cursor over the `QrCode::new` call (around line 26) in " +"\\`qr_code_generator_ffi_glue.rs" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Demo **show documentation** (typical bindings: vscode = ctrl k i; vim/CoC = " +"K)." +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Demo **go to definition** (typical bindings: vscode = F12; vim/CoC = g d). " +"(This will take you to `//third_party/rust/.../qr_code-.../src/lib.rs`.)" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Demo **outline** and navigate to the `QrCode::with_bits` method (around line " +"164; the outline is in the file explorer pane in vscode; typical vim/CoC " +"bindings = space o)" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"Demo **type annotations** (there are quote a few nice examples in the " +"`QrCode::with_bits` method)" +msgstr "" + +#: src/chromium/build-rules/vscode.md +msgid "" +"It may be worth pointing out that `gn gen ... --export-rust-project` will " +"need to be rerun after editing `BUILD.gn` files (which we will do a few " +"times throughout the exercises in this session)." +msgstr "" + +#: src/exercises/chromium/build-rules.md +#, fuzzy +msgid "Build rules exercise" +msgstr "İnşa (Build) Kuralları" + +#: src/exercises/chromium/build-rules.md +msgid "" +"In your Chromium build, add a new Rust target to `//ui/base/BUILD.gn` " +"containing:" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"**Important**: note that `no_mangle` here is considered a type of unsafety " +"by the Rust compiler, so you'll need to to allow unsafe code in your `gn` " +"target." +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"Add this new Rust target as a dependency of `//ui/base:base`. Declare this " +"function at the top of `ui/base/resource/resource_bundle.cc` (later, we'll " +"see how this can be automated by bindings generation tools):" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"Call this function from somewhere in `ui/base/resource/resource_bundle.cc` - " +"we suggest the top of `ResourceBundle::MaybeMangleLocalizedString`. Build " +"and run Chromium, and ensure that \"Hello from Rust!\" is printed lots of " +"times." +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"If you use VSCode, now set up Rust to work well in VSCode. It will be useful " +"in subsequent exercises. If you've succeeded, you will be able to use right-" +"click \"Go to definition\" on `println!`." +msgstr "" + +#: src/exercises/chromium/build-rules.md +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Where to find help" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"The options available to the [`rust_static_library` gn template](https://" +"source.chromium.org/chromium/chromium/src/+/main:build/rust/" +"rust_static_library.gni;l=16)" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"Information about [`#[no_mangle]`](https://doc.rust-lang.org/beta/reference/" +"abi.html#the-no_mangle-attribute)" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"Information about [`extern \"C\"`](https://doc.rust-lang.org/std/keyword." +"extern.html)" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"Information about gn's [`--export-rust-project`](https://gn.googlesource.com/" +"gn/+/main/docs/reference.md#compilation-database) switch" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"[How to install rust-analyzer in VSCode](https://code.visualstudio.com/docs/" +"languages/rust)" +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"This example is unusual because it boils down to the lowest-common-" +"denominator interop language, C. Both C++ and Rust can natively declare and " +"call C ABI functions. Later in the course, we'll connect C++ directly to " +"Rust." +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"`allow_unsafe = true` is required here because `#[no_mangle]` might allow " +"Rust to generate two functions with the same name, and Rust can no longer " +"guarantee that the right one is called." +msgstr "" + +#: src/exercises/chromium/build-rules.md +msgid "" +"If you need a pure Rust executable, you can also do that using the " +"`rust_executable` gn template." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"Rust community typically authors unit tests in a module placed in the same " +"source file as the code being tested. This was covered [earlier](../testing." +"md) in the course and looks like this:" +msgstr "" + +#: src/chromium/testing.md +msgid "" +"In Chromium we place unit tests in a separate source file and we continue to " +"follow this practice for Rust --- this makes tests consistently discoverable " +"and helps to avoid rebuilding `.rs` files a second time (in the `test` " +"configuration)." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"This results in the following options for testing Rust code in Chromium:" +msgstr "" + +#: src/chromium/testing.md +msgid "" +"Native Rust tests (i.e. `#[test]`). Discouraged outside of `//third_party/" +"rust`." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"`gtest` tests authored in C++ and exercising Rust via FFI calls. Sufficient " +"when Rust code is just a thin FFI layer and the existing unit tests provide " +"sufficient coverage for the feature." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"`gtest` tests authored in Rust and using the crate under test through its " +"public API (using `pub mod for_testing { ... }` if needed). This is the " +"subject of the next few slides." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"Mention that native Rust tests of third-party crates should eventually be " +"exercised by Chromium bots. (Such testing is needed rarely --- only after " +"adding or updating third-party crates.)" +msgstr "" + +#: src/chromium/testing.md +msgid "" +"Some examples may help illustrate when C++ `gtest` vs Rust `gtest` should be " +"used:" +msgstr "" + +#: src/chromium/testing.md +msgid "" +"QR has very little functionality in the first-party Rust layer (it's just a " +"thin FFI glue) and therefore uses the existing C++ unit tests for testing " +"both the C++ and the Rust implementation (parameterizing the tests so they " +"enable or disable Rust using a `ScopedFeatureList`)." +msgstr "" + +#: src/chromium/testing.md +msgid "" +"Hypothetical/WIP PNG integration may need to implement memory-safe " +"implementation of pixel transformations that are provided by `libpng` but " +"missing in the `png` crate - e.g. RGBA => BGRA, or gamma correction. Such " +"functionality may benefit from separate tests authored in Rust." +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md +msgid "" +"The [`rust_gtest_interop`](https://chromium.googlesource.com/chromium/src/+/" +"main/testing/rust_gtest_interop/README.md) library provides a way to:" +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md +msgid "" +"Use a Rust function as a `gtest` testcase (using the `#[gtest(...)]` " +"attribute)" +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md +msgid "" +"Use `expect_eq!` and similar macros (similar to `assert_eq!` but not " +"panicking and not terminating the test when the assertion fails)." +msgstr "" + +#: src/chromium/testing/rust-gtest-interop.md +#, fuzzy +msgid "Example:" +msgstr "Örnek" + +#: src/chromium/testing/build-gn.md +msgid "" +"The simplest way to build Rust `gtest` tests is to add them to an existing " +"test binary that already contains tests authored in C++. For example:" +msgstr "" + +#: src/chromium/testing/build-gn.md +msgid "" +"```gn\n" +"test(\"ui_base_unittests\") {\n" +" ...\n" +" sources += [ \"my_rust_lib_unittest.rs\" ]\n" +" deps += [ \":my_rust_lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/testing/build-gn.md +msgid "" +"Authoring Rust tests in a separate `static_library` also works, but requires " +"manually declaring the dependency on the support libraries:" +msgstr "" + +#: src/chromium/testing/build-gn.md +msgid "" +"```gn\n" +"rust_static_library(\"my_rust_lib_unittests\") {\n" +" testonly = true\n" +" is_gtest_unittests = true\n" +" crate_root = \"my_rust_lib_unittest.rs\"\n" +" sources = [ \"my_rust_lib_unittest.rs\" ]\n" +" deps = [\n" +" \":my_rust_lib\",\n" +" \"//testing/rust_gtest_interop\",\n" +" ]\n" +"}\n" +"\n" +"test(\"ui_base_unittests\") {\n" +" ...\n" +" deps += [ \":my_rust_lib_unittests\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md +msgid "" +"After adding `:my_rust_lib` to GN `deps`, we still need to learn how to " +"import and use `my_rust_lib` from `my_rust_lib_unittest.rs`. We haven't " +"provided an explicit `crate_name` for `my_rust_lib` so its crate name is " +"computed based on the full target path and name. Fortunately we can avoid " +"working with such an unwieldy name by using the `chromium::import!` macro " +"from the automatically-imported `chromium` crate:" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md +msgid "\"//ui/base:my_rust_lib\"" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md +msgid "Under the covers the macro expands to something similar to:" +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md +msgid "" +"More information can be found in [the doc comment](https://source.chromium." +"org/chromium/chromium/src/+/main:build/rust/chromium_prelude/" +"chromium_prelude.rs?q=f:chromium_prelude.rs%20pub.use.*%5Cbimport%5Cb;%20-f:" +"third_party&ss=chromium%2Fchromium%2Fsrc) of the `chromium::import` macro." +msgstr "" + +#: src/chromium/testing/chromium-import-macro.md +msgid "" +"`rust_static_library` supports specifying an explicit name via `crate_name` " +"property, but doing this is discouraged. And it is discouraged because the " +"crate name has to be globally unique. crates.io guarantees uniqueness of its " +"crate names so `cargo_crate` GN targets (generated by the `gnrt` tool " +"covered in a later section) use short crate names." +msgstr "" + +#: src/exercises/chromium/testing.md +#, fuzzy +msgid "Testing exercise" +msgstr "egzersiz:" + +#: src/exercises/chromium/testing.md +msgid "Time for another exercise!" +msgstr "" + +#: src/exercises/chromium/testing.md +msgid "In your Chromium build:" +msgstr "" + +#: src/exercises/chromium/testing.md +msgid "" +"Add a testable function next to `hello_from_rust`. Some suggestions: adding " +"two integers received as arguments, computing the nth Fibonacci number, " +"summing integers in a slice, etc." +msgstr "" + +#: src/exercises/chromium/testing.md +msgid "Add a separate `..._unittest.rs` file with a test for the new function." +msgstr "" + +#: src/exercises/chromium/testing.md +msgid "Add the new tests to `BUILD.gn`." +msgstr "" + +#: src/exercises/chromium/testing.md +msgid "Build the tests, run them, and verify that the new test works." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"The Rust community offers multiple options for C++/Rust interop, with new " +"tools being developed all the time. At the moment, Chromium uses a tool " +"called CXX." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"You describe your whole language boundary in an interface definition " +"language (which looks a lot like Rust) and then CXX tools generate " +"declarations for functions and types in both Rust and C++." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"See the [CXX tutorial](https://cxx.rs/tutorial.html) for a full example of " +"using this." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"Talk through the diagram. Explain that behind the scenes, this is doing just " +"the same as you previously did. Point out that automating the process has " +"the following benefits:" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"The tool guarantees that the C++ and Rust sides match (e.g. you get compile " +"errors if the `#[cxx::bridge]` doesn't match the actual C++ or Rust " +"definitions, but with out-of-sync manual bindings you'd get Undefined " +"Behavior)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"The tool automates generation of FFI thunks (small, C-ABI-compatible, free " +"functions) for non-C features (e.g. enabling FFI calls into Rust or C++ " +"methods; manual bindings would require authoring such top-level, free " +"functions manually)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "The tool and the library can handle a set of core types - for example:" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"`&[T]` can be passed across the FFI boundary, even though it doesn't " +"guarantee any particular ABI or memory layout. With manual bindings `std::" +"span` / `&[T]` have to be manually destructured and rebuilt out of a " +"pointer and length - this is error-prone given that each language represents " +"empty slices slightly differently)" +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"Smart pointers like `std::unique_ptr`, `std::shared_ptr`, and/or `Box` " +"are natively supported. With manual bindings, one would have to pass C-ABI-" +"compatible raw pointers, which would increase lifetime and memory-safety " +"risks." +msgstr "" + +#: src/chromium/interoperability-with-cpp.md +msgid "" +"`rust::String` and `CxxString` types understand and maintain differences in " +"string representation across the languages (e.g. `rust::String::lossy` can " +"build a Rust string from non-UTF8 input and `rust::String::c_str` can NUL-" +"terminate a string)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "" +"CXX requires that the whole C++/Rust boundary is declared in `cxx::bridge` " +"modules inside `.rs` source code." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "\"example/include/blobstore.h\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "// Definitions of Rust types and functions go here\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "Point out:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "" +"Although this looks like a regular Rust `mod`, the `#[cxx::bridge]` " +"procedural macro does complex things to it. The generated code is quite a " +"bit more sophisticated - though this does still result in a `mod` called " +"`ffi` in your code." +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "Native support for C++'s `std::unique_ptr` in Rust" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "Native support for Rust slices in C++" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "Calls from C++ to Rust, and Rust types (in the top part)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "Calls from Rust to C++, and C++ types (in the bottom part)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/example-bindings.md +msgid "" +"**Common misconception**: It _looks_ like a C++ header is being parsed by " +"Rust, but this is misleading. This header is never interpreted by Rust, but " +"simply `#include`d in the generated C++ code for the benefit of C++ " +"compilers." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"By far the most useful page when using CXX is the [type reference](https://" +"cxx.rs/bindings.html)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "CXX fundamentally suits cases where:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"Your Rust-C++ interface is sufficiently simple that you can declare all of " +"it." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"You're using only the types natively supported by CXX already, for example " +"`std::unique_ptr`, `std::string`, `&[u8]` etc." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"It has many limitations --- for example lack of support for Rust's `Option` " +"type." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"These limitations constrain us to using Rust in Chromium only for well " +"isolated \"leaf nodes\" rather than for arbitrary Rust-C++ interop. When " +"considering a use-case for Rust in Chromium, a good starting point is to " +"draft the CXX bindings for the language boundary to see if it appears simple " +"enough." +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"You should also discuss some of the other sticky points with CXX, for " +"example:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "" +"Its error handling is based around C++ exceptions (given on the next slide)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/limitations-of-cxx.md +msgid "Function pointers are awkward to use." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"CXX's [support for `Result`](https://cxx.rs/binding/result.html) relies " +"on C++ exceptions, so we can't use that in Chromium. Alternatives:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "The `T` part of `Result` can be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"Returned via out parameters (e.g. via `&mut T`). This requires that `T` can " +"be passed across the FFI boundary - for example `T` has to be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "A primitive type (like `u32` or `usize`)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"A type natively supported by `cxx` (like `UniquePtr`) that has a suitable " +"default value to use in a failure case (_unlike_ `Box`)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"Retained on the Rust side, and exposed via reference. This may be needed " +"when `T` is a Rust type, which cannot be passed across the FFI boundary, and " +"cannot be stored in `UniquePtr`." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "The `E` part of `Result` can be:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"Returned as a boolean (e.g. `true` representing success, and `false` " +"representing failure)" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling.md +msgid "" +"Preserving error details is in theory possible, but so far hasn't been " +"needed in practice." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +#, fuzzy +msgid "CXX Error Handling: QR Example" +msgstr "Hata İşleme" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +msgid "" +"The QR code generator is [an example](https://source.chromium.org/chromium/" +"chromium/src/+/main:components/qr_code_generator/qr_code_generator_ffi_glue." +"rs;l=13-18;drc=7bf1b75b910ca430501b9c6a74c1d18a0223ecca) where a boolean is " +"used to communicate success vs failure, and where the successful result can " +"be passed across the FFI boundary:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +msgid "\"qr_code_generator\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +msgid "" +"Students may be curious about the semantics of the `out_qr_size` output. " +"This is not the size of the vector, but the size of the QR code (and " +"admittedly it is a bit redundant - this is the square root of the size of " +"the vector)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +msgid "" +"It may be worth pointing out the importance of initializing `out_qr_size` " +"before calling into the Rust function. Creation of a Rust reference that " +"points to uninitialized memory results in Undefined Behavior (unlike in C++, " +"when only the act of dereferencing such memory results in UB)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-qr.md +msgid "" +"If students ask about `Pin`, then explain why CXX needs it for mutable " +"references to C++ data: the answer is that C++ data can’t be moved around " +"like Rust data, because it may contain self-referential pointers." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +#, fuzzy +msgid "CXX Error Handling: PNG Example" +msgstr "Hata İşleme" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "" +"A prototype of a PNG decoder illustrates what can be done when the " +"successful result cannot be passed across the FFI boundary:" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "\"gfx::rust_bindings\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "" +"/// This returns an FFI-friendly equivalent of `Result,\n" +" /// ()>`.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "/// C++ bindings for the `crate::png::ResultOfPngReader` type.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "/// C++ bindings for the `crate::png::PngReader` type.\n" +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "" +"`PngReader` and `ResultOfPngReader` are Rust types --- objects of these " +"types cannot cross the FFI boundary without indirection of a `Box`. We " +"can't have an `out_parameter: &mut PngReader`, because CXX doesn't allow C++ " +"to store Rust objects by value." +msgstr "" + +#: src/chromium/interoperability-with-cpp/error-handling-png.md +msgid "" +"This example illustrates that even though CXX doesn't support arbitrary " +"generics nor templates, we can still pass them across the FFI boundary by " +"manually specializing / monomorphizing them into a non-generic type. In the " +"example `ResultOfPngReader` is a non-generic type that forwards into " +"appropriate methods of `Result` (e.g. into `is_err`, `unwrap`, and/or " +"`as_mut`)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "Using cxx in Chromium" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"In Chromium, we define an independent `#[cxx::bridge] mod` for each leaf-" +"node where we want to use Rust. You'd typically have one for each " +"`rust_static_library`. Just add" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"```gn\n" +"cxx_bindings = [ \"my_rust_file.rs\" ]\n" +" # list of files containing #[cxx::bridge], not all source files\n" +"allow_unsafe = true\n" +"```" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"to your existing `rust_static_library` target alongside `crate_root` and " +"`sources`." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "C++ headers will be generated at a sensible location, so you can just" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "\"ui/base/my_rust_file.rs.h\"" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"You will find some utility functions in `//base` to convert to/from Chromium " +"C++ types to CXX Rust types --- for example [`SpanToRustSlice`](https://" +"source.chromium.org/chromium/chromium/src/+/main:base/containers/span_rust.h;" +"l=21)." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "Students may ask --- why do we still need `allow_unsafe = true`?" +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"The broad answer is that no C/C++ code is \"safe\" by the normal Rust " +"standards. Calling back and forth to C/C++ from Rust may do arbitrary things " +"to memory, and compromise the safety of Rust's own data layouts. Presence of " +"_too many_ `unsafe` keywords in C/C++ interop can harm the signal-to-noise " +"ratio of such a keyword, and is [controversial](https://steveklabnik.com/" +"writing/the-cxx-debate), but strictly, bringing any foreign code into a Rust " +"binary can cause unexpected behavior from Rust's perspective." +msgstr "" + +#: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md +msgid "" +"The narrow answer lies in the diagram at the top of [this page](../" +"interoperability-with-cpp.md) --- behind the scenes, CXX generates Rust " +"`unsafe` and `extern \"C\"` functions just like we did manually in the " +"previous section." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +#, fuzzy +msgid "Exercise: Interoperability with C++" +msgstr "Birlikte Çalışabilirlik" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Part one" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"In the Rust file you previously created, add a `#[cxx::bridge]` which " +"specifies a single function, to be called from C++, called " +"`hello_from_rust`, taking no parameters and returning no value." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Modify your previous `hello_from_rust` function to remove `extern \"C\"` and " +"`#[no_mangle]`. This is now just a standard Rust function." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Modify your `gn` target to build these bindings." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"In your C++ code, remove the forward-declaration of `hello_from_rust`. " +"Instead, include the generated header file." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Build and run!" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Part two" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"It's a good idea to play with CXX a little. It helps you think about how " +"flexible Rust in Chromium actually is." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Some things to try:" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Call back into C++ from Rust. You will need:" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"An additional header file which you can `include!` from your `cxx::bridge`. " +"You'll need to declare your C++ function in that new header file." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"An `unsafe` block to call such a function, or alternatively specify the " +"`unsafe` keyword in your `#[cxx::bridge]` [as described here](https://cxx.rs/" +"extern-c++.html#functions-and-member-functions)." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"You may also need to `#include \"third_party/rust/cxx/v1/crate/include/cxx." +"h\"`" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Pass a C++ string from C++ into Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Pass a reference to a C++ object into Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Intentionally get the Rust function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Intentionally get the C++ function signatures mismatched from the `#[cxx::" +"bridge]`, and get used to the errors you see." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Pass a `std::unique_ptr` of some type from C++ into Rust, so that Rust can " +"own some C++ object." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Create a Rust object and pass it into C++, so that C++ owns it. (Hint: you " +"need a `Box`)." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Declare some methods on a C++ type. Call them from Rust." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Declare some methods on a Rust type. Call them from C++." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Part three" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"Now you understand the strengths and limitations of CXX interop, think of a " +"couple of use-cases for Rust in Chromium where the interface would be " +"sufficiently simple. Sketch how you might define that interface." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "The [`cxx` binding reference](https://cxx.rs/bindings.html)" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"The [`rust_static_library` gn template](https://source.chromium.org/chromium/" +"chromium/src/+/main:build/rust/rust_static_library.gni;l=16)" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "Some of the questions you may encounter:" +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"I'm seeing a problem initializing a variable of type X with type Y, where X " +"and Y are both function types. This is because your C++ function doesn't " +"quite match the declaration in your `cxx::bridge`." +msgstr "" + +#: src/exercises/chromium/interoperability-with-cpp.md +msgid "" +"I seem to be able to freely convert C++ references into Rust references. " +"Doesn't that risk UB? For CXX's _opaque_ types, no, because they are zero-" +"sized. For CXX trivial types yes, it's _possible_ to cause UB, although " +"CXX's design makes it quite difficult to craft such an example." +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "" +"Rust libraries are called \"crates\" and are found at [crates.io](https://" +"crates.io). It's _very easy_ for Rust crates to depend upon one another. So " +"they do!" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +#, fuzzy +msgid "C++ library" +msgstr "kütüphane:" + +#: src/chromium/adding-third-party-crates.md +#, fuzzy +msgid "Rust crate" +msgstr "Rust Ekosistemi" + +#: src/chromium/adding-third-party-crates.md +#, fuzzy +msgid "Build system" +msgstr "Rust Ekosistemi" + +#: src/chromium/adding-third-party-crates.md +msgid "Lots" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Consistent: `Cargo.toml`" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Typical library size" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Large-ish" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Small" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Transitive dependencies" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "Few" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "For a Chromium engineer, this has pros and cons:" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "" +"All crates use a common build system so we can automate their inclusion into " +"Chromium..." +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "" +"... but, crates typically have transitive dependencies, so you will likely " +"have to bring in multiple libraries." +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "We'll discuss:" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "How to put a crate in the Chromium source code tree" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "How to make `gn` build rules for it" +msgstr "" + +#: src/chromium/adding-third-party-crates.md +msgid "How to audit its source code for sufficient safety." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md +msgid "Configuring the `Cargo.toml` file to add crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md +msgid "" +"Chromium has a single set of centrally-managed direct crate dependencies. " +"These are managed through a single [`Cargo.toml`](https://source.chromium." +"org/chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/Cargo." +"toml):" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md +msgid "" +"```toml\n" +"[dependencies]\n" +"bitflags = \"1\"\n" +"cfg-if = \"1\"\n" +"cxx = \"1\"\n" +"# lots more...\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md +msgid "" +"As with any other `Cargo.toml`, you can specify [more details about the " +"dependencies](https://doc.rust-lang.org/cargo/reference/specifying-" +"dependencies.html) --- most commonly, you'll want to specify the `features` " +"that you wish to enable in the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-cargo-toml.md +msgid "" +"When adding a crate to Chromium, you'll often need to provide some extra " +"information in an additional file, `gnrt_config.toml`, which we'll meet next." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +msgid "" +"Alongside `Cargo.toml` is [`gnrt_config.toml`](https://source.chromium.org/" +"chromium/chromium/src/+/main:third_party/rust/chromium_crates_io/gnrt_config." +"toml). This contains Chromium-specific extensions to crate handling." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +msgid "" +"If you add a new crate, you should specify at least the `group`. This is one " +"of:" +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "For instance," +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +msgid "" +"Depending on the crate source code layout, you may also need to use this " +"file to specify where its `LICENSE` file(s) can be found." +msgstr "" + +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +msgid "" +"Later, we'll see some other things you will need to configure in this file " +"to resolve problems." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "" +"A tool called `gnrt` knows how to download crates and how to generate `BUILD." +"gn` rules." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "To start, download the crate you want like this:" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "" +"Although the `gnrt` tool is part of the Chromium source code, by running " +"this command you will be downloading and running its dependencies from " +"`crates.io`. See [the earlier section](../cargo.md) discussing this security " +"decision." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "This `vendor` command may download:" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +#, fuzzy +msgid "Your crate" +msgstr "Kullanışlı sandıklar (crates)" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "Direct and transitive dependencies" +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "" +"New versions of other crates, as required by `cargo` to resolve the complete " +"set of crates required by Chromium." +msgstr "" + +#: src/chromium/adding-third-party-crates/downloading-crates.md +msgid "" +"Chromium maintains patches for some crates, kept in `//third_party/rust/" +"chromium_crates_io/patches`. These will be reapplied automatically, but if " +"patching fails you may need to take manual action." +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "" +"Once you've downloaded the crate, generate the `BUILD.gn` files like this:" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "Now run `git status`. You should find:" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "" +"At least one new crate source code in `third_party/rust/chromium_crates_io/" +"vendor`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "" +"At least one new `BUILD.gn` in `third_party/rust//v`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "An appropriate `README.chromium`" +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +#, fuzzy +msgid "" +"The \"major semver version\" is a [Rust \"semver\" version number](https://" +"doc.rust-lang.org/cargo/reference/semver.html)." +msgstr "" +"[çalışma alanları](https://doc.rust-lang.org/cargo/reference/workspaces.html)" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "" +"Take a close look, especially at the things generated in `third_party/rust`." +msgstr "" + +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md +msgid "" +"Talk a little about semver --- and specifically the way that in Chromium " +"it's to allow multiple incompatible versions of a crate, which is " +"discouraged but sometimes necessary in the Cargo ecosystem." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "" +"If your build fails, it may be because of a `build.rs`: programs which do " +"arbitrary things at build time. This is fundamentally at odds with the " +"design of `gn` and `ninja` which aim for static, deterministic, build rules " +"to maximize parallelism and repeatability of builds." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "" +"Some `build.rs` actions are automatically supported; others require action:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "build script effect" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Supported by our gn templates" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Work required by you" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Checking rustc version to configure features on and off" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "None" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Checking platform or CPU to configure features on and off" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +#, fuzzy +msgid "Generating code" +msgstr "Jenerikler" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Yes - specify in `gnrt_config.toml`" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Building C/C++" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Patch around it" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "Arbitrary other actions" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems.md +msgid "" +"Fortunately, most crates don't contain a build script, and fortunately, most " +"build scripts only do the top two actions." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +msgid "" +"If `ninja` complains about missing files, check the `build.rs` to see if it " +"writes source code files." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +msgid "" +"If so, modify [`gnrt_config.toml`](../configuring-gnrt-config-toml.md) to " +"add `build-script-outputs` to the crate. If this is a transitive dependency, " +"that is, one on which Chromium code should not directly depend, also add " +"`allow-first-party-usage=false`. There are several examples already in that " +"file:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +msgid "" +"```toml\n" +"[crate.unicode-linebreak]\n" +"allow-first-party-usage = false\n" +"build-script-outputs = [\"tables.rs\"]\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +msgid "" +"Now rerun [`gnrt.py -- gen`](../generating-gn-build-rules.md) to regenerate " +"`BUILD.gn` files to inform ninja that this particular output file is input " +"to subsequent build steps." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "" +"Some crates use the [`cc`](https://crates.io/crates/cc) crate to build and " +"link C/C++ libraries. Other crates parse C/C++ using [`bindgen`](https://" +"crates.io/crates/bindgen) within their build scripts. These actions can't be " +"supported in a Chromium context --- our gn, ninja and LLVM build system is " +"very specific in expressing relationships between build actions." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "So, your options are:" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "Avoid these crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "Apply a patch to the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +msgid "" +"Patches should be kept in `third_party/rust/chromium_crates_io/patches/" +"` - see for example the [patches against the `cxx` crate](https://" +"source.chromium.org/chromium/chromium/src/+/main:third_party/rust/" +"chromium_crates_io/patches/cxx/) - and will be applied automatically by " +"`gnrt` each time it upgrades the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "" +"Once you've added a third-party crate and generated build rules, depending " +"on a crate is simple. Find your `rust_static_library` target, and add a " +"`dep` on the `:lib` target within your crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "Specifically," +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "" +"```bob\n" +" +------------+ +----------------------+\n" +"\"//third_party/rust\" | crate name | \"/v\" | major semver version | \":" +"lib\"\n" +" +------------+ +----------------------+\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md +msgid "" +"```gn\n" +"rust_static_library(\"my_rust_lib\") {\n" +" crate_root = \"lib.rs\"\n" +" sources = [ \"lib.rs\" ]\n" +" deps = [ \"//third_party/rust/example_rust_crate/v1:lib\" ]\n" +"}\n" +"```" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "Auditing Third Party Crates" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Adding new libraries is subject to Chromium's standard [policies](https://" +"chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/rust." +"md#Third_party-review), but of course also subject to security review. As " +"you may be bringing in not just a single crate but also transitive " +"dependencies, there may be a lot of code to review. On the other hand, safe " +"Rust code can have limited negative side effects. How should you review it?" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Over time Chromium aims to move to a process based around [cargo vet]" +"(https://mozilla.github.io/cargo-vet/)." +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Meanwhile, for each new crate addition, we are checking for the following:" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Understand why each crate is used. What's the relationship between crates? " +"If the build system for each crate contains a `build.rs` or procedural " +"macros, work out what they're for. Are they compatible with the way Chromium " +"is normally built?" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "Check each crate seems to be reasonably well maintained" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Use `cd third-party/rust/chromium_crates_io; cargo audit` to check for known " +"vulnerabilities (first you'll need to `cargo install cargo-audit`, which " +"ironically involves downloading lots of dependencies from the internet[2](../" +"cargo.md))" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Ensure any `unsafe` code is good enough for the [Rule of Two](https://" +"chromium.googlesource.com/chromium/src/+/main/docs/security/rule-of-2." +"md#unsafe-code-in-safe-languages)" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "Check for any use of `fs` or `net` APIs" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"Read all the code at a sufficient level to look for anything out of place " +"that might have been maliciously inserted. (You can't realistically aim for " +"100% perfection here: there's often just too much code.)" +msgstr "" + +#: src/chromium/adding-third-party-crates/reviews-and-audits.md +msgid "" +"These are just guidelines --- work with reviewers from `security@chromium." +"org` to work out the right way to become confident of the crate." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "Checking Crates into Chromium Source Code" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "`git status` should reveal:" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "Crate code in `//third_party/rust/chromium_crates_io`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "" +"Metadata (`BUILD.gn` and `README.chromium`) in `//third_party/rust//" +"`" +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "Please also add an `OWNERS` file in the latter location." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "" +"You should land all this, along with your `Cargo.toml` and `gnrt_config." +"toml` changes, into the Chromium repo." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "" +"**Important**: you need to use `git add -f` because otherwise `.gitignore` " +"files may result in some files being skipped." +msgstr "" + +#: src/chromium/adding-third-party-crates/checking-in.md +msgid "" +"As you do so, you might find presubmit checks fail because of non-inclusive " +"language. This is because Rust crate data tends to include names of git " +"branches, and many projects still use non-inclusive terminology there. So " +"you may need to run:" +msgstr "" + +#: src/chromium/adding-third-party-crates/keeping-up-to-date.md +msgid "" +"As the OWNER of any third party Chromium dependency, you are [expected to " +"keep it up to date with any security fixes](https://chromium.googlesource." +"com/chromium/src/+/main/docs/adding_to_third_party.md#add-owners). It is " +"hoped that we will soon automate this for Rust crates, but for now, it's " +"still your responsibility just as it is for any other third party dependency." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "" +"Add [uwuify](https://crates.io/crates/uwuify) to Chromium, turning off the " +"crate's [default features](https://doc.rust-lang.org/cargo/reference/" +"features.html#the-default-feature). Assume that the crate will be used in " +"shipping Chromium, but won't be used to handle untrustworthy input." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "" +"(In the next exercise we'll use uwuify from Chromium, but feel free to skip " +"ahead and do that now if you like. Or, you could create a new " +"[`rust_executable` target](https://source.chromium.org/chromium/chromium/src/" +"+/main:build/rust/rust_executable.gni) which uses `uwuify`)." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "Students will need to download lots of transitive dependencies." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "The total crates needed are:" +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`instant`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`lock_api`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`parking_lot`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`parking_lot_core`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`redox_syscall`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`scopeguard`," +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`smallvec`, and" +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "`uwuify`." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "" +"If students are downloading even more than that, they probably forgot to " +"turn off the default features." +msgstr "" + +#: src/exercises/chromium/third-party.md +msgid "" +"Thanks to [Daniel Liu](https://github.com/Daniel-Liu-c0deb0t) for this crate!" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "Bringing It Together --- Exercise" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"In this exercise, you're going to add a whole new Chromium feature, bringing " +"together everything you already learned." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "The Brief from Product Management" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"A community of pixies has been discovered living in a remote rainforest. " +"It's important that we get Chromium for Pixies delivered to them as soon as " +"possible." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"The requirement is to translate all Chromium's UI strings into Pixie " +"language." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"There's not time to wait for proper translations, but fortunately pixie " +"language is very close to English, and it turns out there's a Rust crate " +"which does the translation." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"In fact, you already [imported that crate in the previous exercise](https://" +"crates.io/crates/uwuify)." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"(Obviously, real translations of Chrome require incredible care and " +"diligence. Don't ship this!)" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "Steps" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"Modify `ResourceBundle::MaybeMangleLocalizedString` so that it uwuifies all " +"strings before display. In this special build of Chromium, it should always " +"do this irrespective of the setting of `mangle_localized_strings_`." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"If you've done everything right across all these exercises, congratulations, " +"you should have created Chrome for pixies!" +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"UTF16 vs UTF8. Students should be aware that Rust strings are always UTF8, " +"and will probably decide that it's better to do the conversion on the C++ " +"side using `base::UTF16ToUTF8` and back again." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"If students decide to do the conversion on the Rust side, they'll need to " +"consider [`String::from_utf16`](https://doc.rust-lang.org/std/string/struct." +"String.html#method.from_utf16), consider error handling, and consider which " +"[CXX supported types can transfer a lot of u16s](https://cxx.rs/binding/" +"slice.html)." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"Students may design the C++/Rust boundary in several different ways, e.g. " +"taking and returning strings by value, or taking a mutable reference to a " +"string. If a mutable reference is used, CXX will likely tell the student " +"that they need to use [`Pin`](https://doc.rust-lang.org/std/pin/). You may " +"need to explain what `Pin` does, and then explain why CXX needs it for " +"mutable references to C++ data: the answer is that C++ data can't be moved " +"around like Rust data, because it may contain self-referential pointers." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"The C++ target containing `ResourceBundle::MaybeMangleLocalizedString` will " +"need to depend on a `rust_static_library` target. The student probably " +"already did this." +msgstr "" + +#: src/exercises/chromium/bringing-it-together.md +msgid "" +"The `rust_static_library` target will need to depend on `//third_party/rust/" +"uwuify/v0_2:lib`." +msgstr "" + +#: src/exercises/chromium/solutions.md +msgid "" +"Solutions to the Chromium exercises can be found in [this series of CLs]" +"(https://chromium-review.googlesource.com/c/chromium/src/+/5096560)." +msgstr "" + +#: src/bare-metal.md +msgid "Welcome to Bare Metal Rust" +msgstr "" + +#: src/bare-metal.md +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 +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 +msgid "What is `no_std` Rust?" +msgstr "" + +#: src/bare-metal.md +msgid "Writing firmware for microcontrollers." +msgstr "" + +#: src/bare-metal.md +msgid "Writing bootloader / kernel code for application processors." +msgstr "" + +#: src/bare-metal.md +msgid "Some useful crates for bare-metal Rust development." +msgstr "" + +#: src/bare-metal.md +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 +msgid "" +"To get started, install some tools we'll need later. On gLinux or Debian:" +msgstr "" + +#: src/bare-metal.md +msgid "" +"And give users in the `plugdev` group access to the micro:bit programmer:" +msgstr "" + +#: src/bare-metal.md src/bare-metal/microcontrollers/debugging.md +msgid "On MacOS:" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`core`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`std`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "Slices, `&str`, `CStr`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`NonZeroU8`..." +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Option`, `Result`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Display`, `Debug`, `write!`..." +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`panic!`, `assert_eq!`..." +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`NonNull` and all the usual pointer-related functions" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Future` and `async`/`await`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`fence`, `AtomicBool`, `AtomicPtr`, `AtomicU32`..." +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Duration`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Box`, `Cow`, `Arc`, `Rc`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Vec`, `BinaryHeap`, `BtreeMap`, `LinkedList`, `VecDeque`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`String`, `CString`, `format!`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Error`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Mutex`, `Condvar`, `Barrier`, `Once`, `RwLock`, `mpsc`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`File` and the rest of `fs`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`println!`, `Read`, `Write`, `Stdin`, `Stdout` and the rest of `io`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Path`, `OsString`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`net`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`Command`, `Child`, `ExitCode`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`spawn`, `sleep` and the rest of `thread`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`SystemTime`, `Instant`" +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`HashMap` depends on RNG." +msgstr "" + +#: src/bare-metal/no_std.md +msgid "`std` re-exports the contents of both `core` and `alloc`." +msgstr "" + +#: src/bare-metal/minimal.md +msgid "A minimal `no_std` program" +msgstr "" + +#: src/bare-metal/minimal.md +msgid "This will compile to an empty binary." +msgstr "" + +#: src/bare-metal/minimal.md +msgid "`std` provides a panic handler; without it we must provide our own." +msgstr "" + +#: src/bare-metal/minimal.md +msgid "It can also be provided by another crate, such as `panic-halt`." +msgstr "" + +#: src/bare-metal/minimal.md +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 +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 +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 +msgid "" +"// Safe because `HEAP` is only used here and `entry` is only called once.\n" +msgstr "" + +#: src/bare-metal/alloc.md +msgid "// Give the allocator some memory to allocate.\n" +msgstr "" + +#: src/bare-metal/alloc.md +msgid "// Now we can do things that require heap allocation.\n" +msgstr "" + +#: src/bare-metal/alloc.md +#, fuzzy +msgid "\"A string\"" +msgstr "string:" + +#: src/bare-metal/alloc.md +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 +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 +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 +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 +msgid "This example will build but not run, as it doesn't have an entry point." +msgstr "" + +#: src/bare-metal/microcontrollers.md +msgid "" +"The `cortex_m_rt` crate provides (among other things) a reset handler for " +"Cortex M microcontrollers." +msgstr "" + +#: src/bare-metal/microcontrollers.md +msgid "" +"Next we'll look at how to access peripherals, with increasing levels of " +"abstraction." +msgstr "" + +#: src/bare-metal/microcontrollers.md +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 +msgid "Run the example with `cargo embed --bin minimal`" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +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 +msgid "/// GPIO port 0 peripheral address\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +msgid "// GPIO peripheral offsets\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +msgid "// PIN_CNF fields\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +#: src/bare-metal/microcontrollers/pacs.md +#: src/bare-metal/microcontrollers/hals.md +msgid "// Configure GPIO 0 pins 21 and 28 as push-pull outputs.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +msgid "" +"// Safe because the pointers are to valid peripheral control registers, and\n" +" // no aliases exist.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +#: src/bare-metal/microcontrollers/pacs.md +#: src/bare-metal/microcontrollers/hals.md +msgid "// Set pin 28 low and pin 21 high to turn the LED on.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/mmio.md +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 +#: src/bare-metal/microcontrollers/pacs.md +#: src/bare-metal/microcontrollers/hals.md +#: src/bare-metal/microcontrollers/board-support.md +msgid "Run the example with:" +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md +msgid "Peripheral Access Crates" +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md +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 +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 +msgid "" +"They are organised by peripheral, register, field and value, with names, " +"descriptions, addresses and so on." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md +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 +msgid "`cortex-m-rt` provides the vector table, among other things." +msgstr "" + +#: src/bare-metal/microcontrollers/pacs.md +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 +msgid "HAL crates" +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md +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 +msgid "// Create HAL wrapper for GPIO port 0.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md +msgid "" +"`set_low` and `set_high` are methods on the `embedded_hal` `OutputPin` trait." +msgstr "" + +#: src/bare-metal/microcontrollers/hals.md +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 +msgid "Board support crates" +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md +msgid "" +"Board support crates provide a further level of wrapping for a specific " +"board for convenience." +msgstr "" + +#: src/bare-metal/microcontrollers/board-support.md +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 +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 +msgid "`microbit-v2` includes a simple driver for the LED matrix." +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md +msgid "The type state pattern" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md +msgid "// let gpio0_01_again = gpio0.p0_01; // Error, moved.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md +msgid "// pin_input.is_high(); // Error, moved.\n" +msgstr "" + +#: src/bare-metal/microcontrollers/type-state.md +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 +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 +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 +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 +msgid "Many HAL crates follow this pattern." +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +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 +msgid "GPIO" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +msgid "ADC" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +msgid "I2C, SPI, UART, CAN" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +msgid "RNG" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +msgid "Timers" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +msgid "Watchdogs" +msgstr "" + +#: src/bare-metal/microcontrollers/embedded-hal.md +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 +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 +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 +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 +msgid "" +"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md +msgid "GDB stub and Microsoft DAP (Debug Adapter Protocol) server" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md +msgid "Cargo integration" +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md +msgid "" +"`cargo-embed` is a cargo subcommand to build and flash binaries, log RTT " +"(Real Time Transfers) output and connect GDB. It's configured by an `Embed." +"toml` file in your project directory." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md +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 +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 +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 +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 +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 +msgid "cargo-embed is a binary built using the probe-rs library." +msgstr "" + +#: src/bare-metal/microcontrollers/probe-rs.md +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 +msgid "_Embed.toml_:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md +msgid "In one terminal under `src/bare-metal/microcontrollers/examples/`:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md +msgid "In another terminal in the same directory:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md +msgid "On gLinux or Debian:" +msgstr "" + +#: src/bare-metal/microcontrollers/debugging.md +msgid "In GDB, try running:" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +#: src/bare-metal/aps/other-projects.md +msgid "Other projects" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "[RTIC](https://rtic.rs/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "\"Real-Time Interrupt-driven Concurrency\"" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "" +"Shared resource management, message passing, task scheduling, timer queue" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "[Embassy](https://embassy.dev/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "`async` executors with priorities, timers, networking, USB" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "[TockOS](https://www.tockos.org/documentation/getting-started)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "" +"Security-focused RTOS with preemptive scheduling and Memory Protection Unit " +"support" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "[Hubris](https://hubris.oxide.computer/)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "" +"Microkernel RTOS from Oxide Computer Company with memory protection, " +"unprivileged drivers, IPC" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "[Bindings for FreeRTOS](https://github.com/lobaro/FreeRTOS-rust)" +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +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 +msgid "RTIC can be considered either an RTOS or a concurrency framework." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "It doesn't include any HALs." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +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 +msgid "Cortex-M only." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "" +"Google uses TockOS on the Haven microcontroller for Titan security keys." +msgstr "" + +#: src/bare-metal/microcontrollers/other-projects.md +msgid "" +"FreeRTOS is mostly written in C, but there are Rust bindings for writing " +"applications." +msgstr "" + +#: src/exercises/bare-metal/morning.md +msgid "" +"We will read the direction from an I2C compass, and log the readings to a " +"serial port." +msgstr "" + +#: src/exercises/bare-metal/morning.md src/exercises/concurrency/morning.md +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"morning.md) provided." +msgstr "" + +#: src/exercises/bare-metal/compass.md +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 +msgid "Hints:" +msgstr "" + +#: src/exercises/bare-metal/compass.md +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 +msgid "" +"The LSM303AGR Inertial Measurement Unit is connected to the internal I2C bus." +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "" +"TWI is another name for I2C, so the I2C master peripheral is called TWIM." +msgstr "" + +#: src/exercises/bare-metal/compass.md +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 +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 +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 +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 src/exercises/bare-metal/rtc.md +msgid "_src/main.rs_:" +msgstr "" + +#: src/exercises/bare-metal/compass.md +#: src/exercises/bare-metal/solutions-morning.md +msgid "// Configure serial port.\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md +#: src/exercises/bare-metal/solutions-morning.md +msgid "// Use the system timer as a delay provider.\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "" +"// Set up the I2C controller and Inertial Measurement Unit.\n" +" // TODO\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md +#: src/exercises/bare-metal/solutions-morning.md +msgid "\"Ready.\"" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "" +"// Read compass data and log it to the serial port.\n" +" // TODO\n" +msgstr "" + +#: src/exercises/bare-metal/compass.md src/exercises/bare-metal/rtc.md +msgid "_Cargo.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "_Embed.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md src/exercises/bare-metal/rtc.md +msgid "_.cargo/config.toml_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "See the serial output on Linux with:" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "" +"Or on Mac OS something like (the device name may be slightly different):" +msgstr "" + +#: src/exercises/bare-metal/compass.md +msgid "Use Ctrl+A Ctrl+Q to quit picocom." +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "Bare Metal Rust Morning Exercise" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "([back to exercise](compass.md))" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "// Set up the I2C controller and Inertial Measurement Unit.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "\"Setting up IMU...\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "// Set up display and timer.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "// Read compass data and log it to the serial port.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "\"{},{},{}\\t{},{},{}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-morning.md +msgid "" +"// If button A is pressed, switch to the next mode and briefly blink all " +"LEDs\n" +" // on.\n" +msgstr "" + +#: src/bare-metal/aps.md +msgid "Application processors" +msgstr "" + +#: src/bare-metal/aps.md +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 +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 +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 +msgid "" +"Before we can start running Rust code, we need to do some initialisation." +msgstr "" + +#: src/bare-metal/aps/entry-point.md +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 +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 +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 +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 +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 +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 +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 +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 +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 +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 +msgid "Inline assembly" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "" +"Sometimes we need to use assembly to do things that aren't possible with " +"Rust code. For example, to make an HVC (hypervisor call) to tell the " +"firmware to power off the system:" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +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 +msgid "\"hvc #0\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w0\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w1\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w2\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w3\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w4\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w5\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w6\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +msgid "\"w7\"" +msgstr "" + +#: src/bare-metal/aps/inline-assembly.md +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 +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 +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 +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 +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 +msgid "" +"Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/mmio.md +msgid "Volatile memory access for MMIO" +msgstr "" + +#: src/bare-metal/aps/mmio.md +msgid "Use `pointer::read_volatile` and `pointer::write_volatile`." +msgstr "" + +#: src/bare-metal/aps/mmio.md +msgid "Never hold a reference." +msgstr "" + +#: src/bare-metal/aps/mmio.md +msgid "" +"`addr_of!` lets you get fields of structs without creating an intermediate " +"reference." +msgstr "" + +#: src/bare-metal/aps/mmio.md +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 +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 +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 +msgid "" +"Use the `addr_of!` macro to get struct field pointers from a pointer to the " +"struct." +msgstr "" + +#: src/bare-metal/aps/uart.md +msgid "Let's write a UART driver" +msgstr "" + +#: src/bare-metal/aps/uart.md +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 +msgid "/// Minimal driver for a PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md src/bare-metal/aps/better-uart/driver.md +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 src/bare-metal/aps/better-uart/driver.md +#: src/exercises/bare-metal/rtc.md +msgid "/// Writes a single byte to the UART.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md src/bare-metal/aps/better-uart/driver.md +#: src/exercises/bare-metal/rtc.md +msgid "// Wait until there is room in the TX buffer.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md +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 src/bare-metal/aps/better-uart/driver.md +#: src/exercises/bare-metal/rtc.md +msgid "// Write to the TX buffer.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md src/bare-metal/aps/better-uart/driver.md +#: src/exercises/bare-metal/rtc.md +msgid "// Wait until the UART is no longer busy.\n" +msgstr "" + +#: src/bare-metal/aps/uart.md +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 +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 +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 +msgid "More traits" +msgstr "" + +#: src/bare-metal/aps/uart/traits.md +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 src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "" +"// Safe because it just contains a pointer to device memory, which can be\n" +"// accessed from any context.\n" +msgstr "" + +#: src/bare-metal/aps/uart/traits.md +msgid "" +"Implementing `Write` lets us use the `write!` and `writeln!` macros with our " +"`Uart` type." +msgstr "" + +#: src/bare-metal/aps/uart/traits.md +msgid "" +"Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "A better UART driver" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +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 +msgid "Offset" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "Register name" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "Width" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x00" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "DR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "12" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x04" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "RSR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x18" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "FR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "9" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x20" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "ILPR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x24" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "IBRD" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "16" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x28" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "FBRD" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x2c" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "LCR_H" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x30" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "CR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x34" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "IFLS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x38" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "IMSC" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "11" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x3c" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "RIS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x40" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "MIS" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x44" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "ICR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "0x48" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "DMACR" +msgstr "" + +#: src/bare-metal/aps/better-uart.md +msgid "There are also some ID registers which have been omitted for brevity." +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md +msgid "" +"The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " +"working with bitflags." +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Flags from the UART flag register.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Clear to send.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Data set ready.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Data carrier detect.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// UART busy transmitting data.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Receive FIFO is empty.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Transmit FIFO is full.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Receive FIFO is full.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Transmit FIFO is empty.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md src/exercises/bare-metal/rtc.md +msgid "/// Ring indicator.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/bitflags.md +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 +msgid "Multiple registers" +msgstr "" + +#: src/bare-metal/aps/better-uart/registers.md +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 +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 +msgid "Now let's use the new `Registers` struct in our driver." +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md +msgid "/// Driver for a PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md src/exercises/bare-metal/rtc.md +msgid "" +"// Safe because we know that self.registers points to the control\n" +" // registers of a PL011 device which is appropriately mapped.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md src/exercises/bare-metal/rtc.md +msgid "" +"/// Reads and returns a pending byte, or `None` if nothing has been\n" +" /// received.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md src/exercises/bare-metal/rtc.md +msgid "// TODO: Check for error conditions in bits 8-11.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/driver.md +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 src/bare-metal/aps/logging/using.md +msgid "Using it" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md +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 src/bare-metal/aps/logging/using.md +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Base address of the primary PL011 UART.\n" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md src/bare-metal/aps/logging/using.md +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +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 src/bare-metal/aps/logging/using.md +msgid "\"main({x0:#x}, {x1:#x}, {x2:#x}, {x3:#x})\"" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md +msgid "b'\\r'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md src/async/pitfalls/cancellation.md +msgid "b'\\n'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md +msgid "b'q'" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md +msgid "\"Bye!\"" +msgstr "" + +#: src/bare-metal/aps/better-uart/using.md +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 +msgid "" +"Run the example in QEMU with `make qemu` under `src/bare-metal/aps/examples`." +msgstr "" + +#: src/bare-metal/aps/logging.md +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 src/exercises/bare-metal/rtc.md +msgid "\"[{}] {}\"" +msgstr "" + +#: src/bare-metal/aps/logging.md src/exercises/bare-metal/rtc.md +msgid "/// Initialises UART logger.\n" +msgstr "" + +#: src/bare-metal/aps/logging.md +msgid "" +"The unwrap in `log` is safe because we initialise `LOGGER` before calling " +"`set_logger`." +msgstr "" + +#: src/bare-metal/aps/logging/using.md +msgid "We need to initialise the logger before we use it." +msgstr "" + +#: src/bare-metal/aps/logging/using.md src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"{info}\"" +msgstr "" + +#: src/bare-metal/aps/logging/using.md +msgid "Note that our panic handler can now log details of panics." +msgstr "" + +#: src/bare-metal/aps/logging/using.md +msgid "" +"Run the example in QEMU with `make qemu_logger` under `src/bare-metal/aps/" +"examples`." +msgstr "" + +#: src/bare-metal/aps/exceptions.md +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 +msgid "EL is exception level; all our examples this afternoon run in EL1." +msgstr "" + +#: src/bare-metal/aps/exceptions.md +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 +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 +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 +msgid "[oreboot](https://github.com/oreboot/oreboot)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "\"coreboot without the C\"" +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "Supports x86, aarch64 and RISC-V." +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "Relies on LinuxBoot rather than having many drivers itself." +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "" +"[Rust RaspberryPi OS tutorial](https://github.com/rust-embedded/rust-" +"raspberrypi-OS-tutorials)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "" +"Initialisation, UART driver, simple bootloader, JTAG, exception levels, " +"exception handling, page tables" +msgstr "" + +#: src/bare-metal/aps/other-projects.md +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 +msgid "[`cargo-call-stack`](https://crates.io/crates/cargo-call-stack)" +msgstr "" + +#: src/bare-metal/aps/other-projects.md +msgid "Static analysis to determine maximum stack usage." +msgstr "" + +#: src/bare-metal/aps/other-projects.md +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 +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 +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 +msgid "Useful crates" +msgstr "Kullanışlı sandıklar (crates)" + +#: src/bare-metal/useful-crates.md +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 +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 +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 +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 +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 +msgid "" +"`zerocopy::byteorder` has types for byte-order aware numeric primitives." +msgstr "" + +#: src/bare-metal/useful-crates/zerocopy.md +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 +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 +msgid "// Create a new page table with identity mapping.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md +msgid "// Map a 2 MiB region of memory as read-only.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md +msgid "// Set `TTBR0_EL1` to activate the page table.\n" +msgstr "" + +#: src/bare-metal/useful-crates/aarch64-paging.md +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 +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 +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 +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 +msgid "PCI BARs always have alignment equal to their size." +msgstr "" + +#: src/bare-metal/useful-crates/buddy_system_allocator.md +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 +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 +msgid "" +"`tinyvec` requires that the element type implement `Default` for " +"initialisation." +msgstr "" + +#: src/bare-metal/useful-crates/tinyvec.md +msgid "" +"The Rust Playground includes `tinyvec`, so this example will run fine inline." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md +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 +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 +msgid "Be careful to avoid deadlock if you take locks in interrupt handlers." +msgstr "" + +#: src/bare-metal/useful-crates/spin.md +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 +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 +msgid "" +"The Rust Playground includes `spin`, so this example will run fine inline." +msgstr "" + +#: src/bare-metal/android.md +msgid "" +"To build a bare-metal Rust binary in AOSP, you need to use a " +"`rust_ffi_static` Soong rule to build your Rust code, then a `cc_binary` " +"with a linker script to produce the binary itself, and then a `raw_binary` " +"to convert the ELF to a raw binary ready to be run." +msgstr "" + +#: src/bare-metal/android/vmbase.md +msgid "vmbase" +msgstr "vmbase" + +#: src/bare-metal/android/vmbase.md +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 +msgid "" +"The `main!` macro marks your main function, to be called from the `vmbase` " +"entry point." +msgstr "" + +#: src/bare-metal/android/vmbase.md +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 +msgid "We will write a driver for the PL031 real-time clock device." +msgstr "" + +#: src/exercises/bare-metal/afternoon.md src/exercises/concurrency/afternoon.md +msgid "" +"After looking at the exercises, you can look at the [solutions](solutions-" +"afternoon.md) provided." +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "RTC driver" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +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 +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 +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 +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 +msgid "Use the RTC interrupt, which is wired to the GIC as `IntId::spi(2)`." +msgstr "" + +#: src/exercises/bare-metal/rtc.md +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 +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 +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Base addresses of the GICv3.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"main({:#x}, {:#x}, {:#x}, {:#x})\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#: src/exercises/bare-metal/solutions-afternoon.md +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 +msgid "// TODO: Create instance of RTC driver and print current time.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// TODO: Wait for 3 seconds.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +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:214 +#: src/exercises/bare-metal/rtc.md msgid "" -"```rust,compile_fail\n" "// Copyright 2023 Google LLC\n" "//\n" "// Licensed under the Apache License, Version 2.0 (the \"License\");\n" @@ -14143,102 +16391,106 @@ msgid "" "// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" "// See the License for the specific language governing permissions and\n" "// limitations under the License.\n" -"\n" -"#![allow(unused)]\n" -"\n" -"use core::fmt::{self, Write};\n" -"use core::ptr::{addr_of, addr_of_mut};\n" -"\n" -"// ANCHOR: Flags\n" -"use bitflags::bitflags;\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART flag register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct Flags: u16 {\n" -" /// Clear to send.\n" -" const CTS = 1 << 0;\n" -" /// Data set ready.\n" -" const DSR = 1 << 1;\n" -" /// Data carrier detect.\n" -" const DCD = 1 << 2;\n" -" /// UART busy transmitting data.\n" -" const BUSY = 1 << 3;\n" -" /// Receive FIFO is empty.\n" -" const RXFE = 1 << 4;\n" -" /// Transmit FIFO is full.\n" -" const TXFF = 1 << 5;\n" -" /// Receive FIFO is full.\n" -" const RXFF = 1 << 6;\n" -" /// Transmit FIFO is empty.\n" -" const TXFE = 1 << 7;\n" -" /// Ring indicator.\n" -" const RI = 1 << 8;\n" -" }\n" -"}\n" -"// ANCHOR_END: Flags\n" -"\n" -"bitflags! {\n" -" /// Flags from the UART Receive Status Register / Error Clear Register.\n" -" #[repr(transparent)]\n" -" #[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -" struct ReceiveStatus: u16 {\n" -" /// Framing error.\n" -" const FE = 1 << 0;\n" -" /// Parity error.\n" -" const PE = 1 << 1;\n" -" /// Break error.\n" -" const BE = 1 << 2;\n" -" /// Overrun error.\n" -" const OE = 1 << 3;\n" -" }\n" -"}\n" -"\n" -"// ANCHOR: Registers\n" -"#[repr(C, align(4))]\n" -"struct Registers {\n" -" dr: u16,\n" -" _reserved0: [u8; 2],\n" -" rsr: ReceiveStatus,\n" -" _reserved1: [u8; 19],\n" -" fr: Flags,\n" -" _reserved2: [u8; 6],\n" -" ilpr: u8,\n" -" _reserved3: [u8; 3],\n" -" ibrd: u16,\n" -" _reserved4: [u8; 2],\n" -" fbrd: u8,\n" -" _reserved5: [u8; 3],\n" -" lcr_h: u8,\n" -" _reserved6: [u8; 3],\n" -" cr: u16,\n" -" _reserved7: [u8; 3],\n" -" ifls: u8,\n" -" _reserved8: [u8; 3],\n" -" imsc: u16,\n" -" _reserved9: [u8; 2],\n" -" ris: u16,\n" -" _reserved10: [u8; 2],\n" -" mis: u16,\n" -" _reserved11: [u8; 2],\n" -" icr: u16,\n" -" _reserved12: [u8; 2],\n" -" dmacr: u8,\n" -" _reserved13: [u8; 3],\n" -"}\n" -"// ANCHOR_END: Registers\n" -"\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"sync_exception_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"irq_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"No pending interrupt\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"IRQ {intid:?}\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"fiq_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"serr_current\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"sync_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"irq_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"fiq_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"serr_lower\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "_src/logger.rs_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR: main\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "_src/pl011.rs_ (you shouldn't need to change this):" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR: Flags\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR_END: Flags\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "" +"/// Flags from the UART Receive Status Register / Error Clear Register.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "/// Framing error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "/// Parity error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "/// Break error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "/// Overrun error.\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR: Registers\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR_END: Registers\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "" "// ANCHOR: Uart\n" "/// Driver for a PL011 UART.\n" -"#[derive(Debug)]\n" -"pub struct Uart {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Uart {\n" -" /// Constructs a new instance of the UART driver for a PL011 device at " -"the\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "" +"/// Constructs a new instance of the UART driver for a PL011 device at the\n" " /// given base address.\n" " ///\n" " /// # Safety\n" @@ -14248,108 +16500,55 @@ msgid "" " /// PL011 device, which must be mapped into the address space of the " "process\n" " /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Writes a single byte to the UART.\n" -" pub fn write_byte(&self, byte: u8) {\n" -" // Wait until there is room in the TX buffer.\n" -" while self.read_flag_register().contains(Flags::TXFF) {}\n" -"\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe {\n" -" // Write to the TX buffer.\n" -" addr_of_mut!((*self.registers).dr).write_volatile(byte.into());\n" -" }\n" -"\n" -" // Wait until the UART is no longer busy.\n" -" while self.read_flag_register().contains(Flags::BUSY) {}\n" -" }\n" -"\n" -" /// Reads and returns a pending byte, or `None` if nothing has been " -"received.\n" -" pub fn read_byte(&self) -> Option {\n" -" if self.read_flag_register().contains(Flags::RXFE) {\n" -" None\n" -" } else {\n" -" let data = unsafe { addr_of!((*self.registers).dr)." -"read_volatile() };\n" -" // TODO: Check for error conditions in bits 8-11.\n" -" Some(data as u8)\n" -" }\n" -" }\n" -"\n" -" fn read_flag_register(&self) -> Flags {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL011 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).fr).read_volatile() }\n" -" }\n" -"}\n" -"// ANCHOR_END: Uart\n" -"\n" -"impl Write for Uart {\n" -" fn write_str(&mut self, s: &str) -> fmt::Result {\n" -" for c in s.as_bytes() {\n" -" self.write_byte(*c);\n" -" }\n" -" Ok(())\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Uart {}\n" -"```" msgstr "" -#: src/exercises/bare-metal/rtc.md:410 +#: src/exercises/bare-metal/rtc.md +msgid "// ANCHOR_END: Uart\n" +msgstr "" + +#: src/exercises/bare-metal/rtc.md msgid "_build.rs_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:414 -msgid "" -"```rust,compile_fail\n" -"// Copyright 2023 Google LLC\n" -"//\n" -"// Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"// you may not use this file except in compliance with the License.\n" -"// You may obtain a copy of the License at\n" -"//\n" -"// http://www.apache.org/licenses/LICENSE-2.0\n" -"//\n" -"// Unless required by applicable law or agreed to in writing, software\n" -"// distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"// See the License for the specific language governing permissions and\n" -"// limitations under the License.\n" -"\n" -"use cc::Build;\n" -"use std::env;\n" -"\n" -"fn main() {\n" -" #[cfg(target_os = \"linux\")]\n" -" env::set_var(\"CROSS_COMPILE\", \"aarch64-linux-gnu\");\n" -" #[cfg(not(target_os = \"linux\"))]\n" -" env::set_var(\"CROSS_COMPILE\", \"aarch64-none-elf\");\n" -"\n" -" Build::new()\n" -" .file(\"entry.S\")\n" -" .file(\"exceptions.S\")\n" -" .file(\"idmap.S\")\n" -" .compile(\"empty\")\n" -"}\n" -"```" +#: src/exercises/bare-metal/rtc.md +msgid "\"linux\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"CROSS_COMPILE\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#, fuzzy +msgid "\"aarch64-linux-gnu\"" +msgstr "aarch64-paging" + +#: src/exercises/bare-metal/rtc.md +msgid "\"aarch64-none-elf\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"entry.S\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#, fuzzy +msgid "\"exceptions.S\"" +msgstr "İstisnalar" + +#: src/exercises/bare-metal/rtc.md +msgid "\"idmap.S\"" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "\"empty\"" msgstr "" -#: src/exercises/bare-metal/rtc.md:446 +#: src/exercises/bare-metal/rtc.md msgid "_entry.S_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:450 +#: src/exercises/bare-metal/rtc.md msgid "" "```armasm\n" "/*\n" @@ -14511,11 +16710,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:595 +#: src/exercises/bare-metal/rtc.md msgid "_exceptions.S_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:599 +#: src/exercises/bare-metal/rtc.md msgid "" "```armasm\n" "/*\n" @@ -14709,11 +16908,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:780 +#: src/exercises/bare-metal/rtc.md msgid "_idmap.S_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:784 +#: src/exercises/bare-metal/rtc.md msgid "" "```armasm\n" "/*\n" @@ -14762,11 +16961,11 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:829 +#: src/exercises/bare-metal/rtc.md msgid "_image.ld_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:833 +#: src/exercises/bare-metal/rtc.md msgid "" "```ld\n" "/*\n" @@ -14877,339 +17076,355 @@ msgid "" "```" msgstr "" -#: src/exercises/bare-metal/rtc.md:940 +#: src/exercises/bare-metal/rtc.md msgid "_Makefile_ (you shouldn't need to change this):" msgstr "" -#: src/exercises/bare-metal/rtc.md:944 -msgid "" -"```makefile\n" -"# Copyright 2023 Google LLC\n" -"#\n" -"# Licensed under the Apache License, Version 2.0 (the \"License\");\n" -"# you may not use this file except in compliance with the License.\n" -"# You may obtain a copy of the License at\n" -"#\n" -"# http://www.apache.org/licenses/LICENSE-2.0\n" -"#\n" -"# Unless required by applicable law or agreed to in writing, software\n" -"# distributed under the License is distributed on an \"AS IS\" BASIS,\n" -"# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n" -"# See the License for the specific language governing permissions and\n" -"# limitations under the License.\n" -"\n" -"UNAME := $(shell uname -s)\n" -"ifeq ($(UNAME),Linux)\n" -"\tTARGET = aarch64-linux-gnu\n" -"else\n" -"\tTARGET = aarch64-none-elf\n" -"endif\n" -"OBJCOPY = $(TARGET)-objcopy\n" -"\n" -".PHONY: build qemu_minimal qemu qemu_logger\n" -"\n" -"all: rtc.bin\n" -"\n" -"build:\n" -"\tcargo build\n" -"\n" -"rtc.bin: build\n" -"\t$(OBJCOPY) -O binary target/aarch64-unknown-none/debug/rtc $@\n" -"\n" -"qemu: rtc.bin\n" -"\tqemu-system-aarch64 -machine virt,gic-version=3 -cpu max -serial mon:stdio " -"-display none -kernel $< -s\n" -"\n" -"clean:\n" -"\tcargo clean\n" -"\trm -f *.bin\n" -"```" +#: src/exercises/bare-metal/rtc.md +msgid "# Copyright 2023 Google LLC" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "$(shell uname -s)" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +#, fuzzy +msgid "aarch64-linux-gnu" +msgstr "aarch64-paging" + +#: src/exercises/bare-metal/rtc.md +msgid "stdio -display none -kernel $< -s" +msgstr "" + +#: src/exercises/bare-metal/rtc.md +msgid "cargo clean" msgstr "" -#: src/exercises/bare-metal/rtc.md:995 +#: src/exercises/bare-metal/rtc.md msgid "Run the code in QEMU with `make qemu`." msgstr "" -#: src/concurrency.md:1 +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "Bare Metal Rust Afternoon" +msgstr "Yalın (Bare) Metal Rust Öğleden Sonra" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "([back to exercise](rtc.md))" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "_main.rs_:" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Base address of the PL031 RTC.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// The IRQ used by the PL031 RTC.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +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 +msgid "\"RTC: {time}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "// Wait for 3 seconds, without interrupts.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"Waiting for {}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"matched={}, interrupt_pending={}\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "\"Finished waiting\"" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "// Wait another 3 seconds for an interrupt.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "_pl031.rs_:" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Data register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Match register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Load register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Control register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Interrupt Mask Set or Clear register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Raw Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Masked Interrupt Status\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Interrupt Clear Register\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +msgid "/// Driver for a PL031 real-time clock.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +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 +msgid "/// Reads the current RTC value.\n" +msgstr "" + +#: src/exercises/bare-metal/solutions-afternoon.md +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 +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 +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 +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 +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 +msgid "/// Clears a pending interrupt, if any.\n" +msgstr "" + +#: src/concurrency.md msgid "Welcome to Concurrency in Rust" msgstr "" -#: src/concurrency.md:3 +#: src/concurrency.md msgid "" "Rust has full support for concurrency using OS threads with mutexes and " "channels." msgstr "" -#: src/concurrency.md:6 +#: src/concurrency.md 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 +#: src/concurrency/threads.md msgid "Rust threads work similarly to threads in other languages:" msgstr "" -#: src/concurrency/threads.md:5 -msgid "" -"```rust,editable\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" thread::spawn(|| {\n" -" for i in 1..10 {\n" -" println!(\"Count in thread: {i}!\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -" });\n" -"\n" -" for i in 1..5 {\n" -" println!(\"Main thread: {i}\");\n" -" thread::sleep(Duration::from_millis(5));\n" -" }\n" -"}\n" -"```" +#: src/concurrency/threads.md +msgid "\"Count in thread: {i}!\"" +msgstr "" + +#: src/concurrency/threads.md +msgid "\"Main thread: {i}\"" msgstr "" -#: src/concurrency/threads.md:24 +#: src/concurrency/threads.md msgid "Threads are all daemon threads, the main thread does not wait for them." msgstr "" -#: src/concurrency/threads.md:25 +#: src/concurrency/threads.md msgid "Thread panics are independent of each other." msgstr "" -#: src/concurrency/threads.md:26 +#: src/concurrency/threads.md msgid "Panics can carry a payload, which can be unpacked with `downcast_ref`." msgstr "" -#: src/concurrency/threads.md:32 +#: src/concurrency/threads.md msgid "" -"Notice that the thread is stopped before it reaches 10 — the main thread is " -"not waiting." +"Notice that the thread is stopped before it reaches 10 --- the main thread " +"is not waiting." msgstr "" -#: src/concurrency/threads.md:35 +#: src/concurrency/threads.md msgid "" "Use `let handle = thread::spawn(...)` and later `handle.join()` to wait for " "the thread to finish." msgstr "" -#: src/concurrency/threads.md:38 +#: src/concurrency/threads.md msgid "Trigger a panic in the thread, notice how this doesn't affect `main`." msgstr "" -#: src/concurrency/threads.md:40 +#: src/concurrency/threads.md 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 "" - -#: src/concurrency/scoped-threads.md:3 -msgid "Normal threads cannot borrow from their environment:" -msgstr "" - -#: src/concurrency/scoped-threads.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"\n" -"fn foo() {\n" -" let s = String::from(\"Hello\");\n" -" thread::spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -"}\n" -"\n" -"fn main() {\n" -" foo();\n" -"}\n" -"```" +"lang.org/std/any/index.html)." msgstr "" -#: 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:" +#: src/concurrency/scoped-threads.md +msgid "Normal threads cannot borrow from their environment:" msgstr "" -#: src/concurrency/scoped-threads.md:22 +#: src/concurrency/scoped-threads.md msgid "" -"```rust,editable\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let s = String::from(\"Hello\");\n" -"\n" -" thread::scope(|scope| {\n" -" scope.spawn(|| {\n" -" println!(\"Length: {}\", s.len());\n" -" });\n" -" });\n" -"}\n" -"```" +"However, you can use a [scoped thread](https://doc.rust-lang.org/std/thread/" +"fn.scope.html) for this:" msgstr "" -#: src/concurrency/scoped-threads.md:40 +#: src/concurrency/scoped-threads.md 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 "" -#: src/concurrency/scoped-threads.md:41 +#: src/concurrency/scoped-threads.md msgid "" "Normal Rust borrowing rules apply: you can either borrow mutably by one " "thread, or immutably by any number of threads." msgstr "" -#: src/concurrency/channels.md:3 +#: src/concurrency/channels.md 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:6 -msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" tx.send(10).unwrap();\n" -" tx.send(20).unwrap();\n" -"\n" -" println!(\"Received: {:?}\", rx.recv());\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"\n" -" let tx2 = tx.clone();\n" -" tx2.send(30).unwrap();\n" -" println!(\"Received: {:?}\", rx.recv());\n" -"}\n" -"```" +#: src/concurrency/channels.md +msgid "\"Received: {:?}\"" msgstr "" -#: src/concurrency/channels.md:26 +#: src/concurrency/channels.md 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:28 +#: src/concurrency/channels.md 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 +#: src/concurrency/channels/unbounded.md msgid "You get an unbounded and asynchronous channel with `mpsc::channel()`:" msgstr "" -#: src/concurrency/channels/unbounded.md:5 -msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::channel();\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" +#: src/concurrency/channels/unbounded.md src/concurrency/channels/bounded.md +msgid "\"Message {i}\"" msgstr "" -#: src/concurrency/channels/bounded.md:3 -msgid "" -"With bounded (synchronous) channels, `send` can block the current thread:" +#: src/concurrency/channels/unbounded.md src/concurrency/channels/bounded.md +msgid "\"{thread_id:?}: sent Message {i}\"" +msgstr "" + +#: src/concurrency/channels/unbounded.md src/concurrency/channels/bounded.md +msgid "\"{thread_id:?}: done\"" msgstr "" -#: src/concurrency/channels/bounded.md:5 +#: src/concurrency/channels/unbounded.md src/concurrency/channels/bounded.md +msgid "\"Main: got {msg}\"" +msgstr "" + +#: src/concurrency/channels/bounded.md msgid "" -"```rust,editable\n" -"use std::sync::mpsc;\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::sync_channel(3);\n" -"\n" -" thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" for i in 1..10 {\n" -" tx.send(format!(\"Message {i}\")).unwrap();\n" -" println!(\"{thread_id:?}: sent Message {i}\");\n" -" }\n" -" println!(\"{thread_id:?}: done\");\n" -" });\n" -" thread::sleep(Duration::from_millis(100));\n" -"\n" -" for msg in rx.iter() {\n" -" println!(\"Main: got {msg}\");\n" -" }\n" -"}\n" -"```" +"With bounded (synchronous) channels, `send` can block the current thread:" msgstr "" -#: src/concurrency/channels/bounded.md:31 +#: src/concurrency/channels/bounded.md 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 +#: src/concurrency/channels/bounded.md msgid "" "A call to `send` will abort with an error (that is why it returns `Result`) " "if the channel is closed. A channel is closed when the receiver is dropped." msgstr "" -#: src/concurrency/channels/bounded.md:33 +#: src/concurrency/channels/bounded.md 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 "" - -#: src/concurrency/send-sync.md:3 +#: src/concurrency/send-sync.md msgid "" "How does Rust know to forbid shared access across threads? The answer is in " "two traits:" msgstr "" -#: src/concurrency/send-sync.md:5 +#: src/concurrency/send-sync.md 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 +#: src/concurrency/send-sync.md 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 +#: src/concurrency/send-sync.md 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 " @@ -15217,65 +17432,57 @@ msgid "" "you know it is valid." msgstr "" -#: src/concurrency/send-sync.md:20 +#: src/concurrency/send-sync.md msgid "" "One can think of these traits as markers that the type has certain thread-" "safety properties." msgstr "" -#: src/concurrency/send-sync.md:21 +#: src/concurrency/send-sync.md msgid "They can be used in the generic constraints as normal traits." msgstr "" -#: src/concurrency/send-sync/send.md:1 -msgid "`Send`" -msgstr "" - -#: src/concurrency/send-sync/send.md:3 +#: src/concurrency/send-sync/send.md 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 +#: src/concurrency/send-sync/send.md 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 +#: src/concurrency/send-sync/send.md 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 "" - -#: src/concurrency/send-sync/sync.md:3 +#: src/concurrency/send-sync/sync.md 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 +#: src/concurrency/send-sync/sync.md msgid "More precisely, the definition is:" msgstr "" -#: src/concurrency/send-sync/sync.md:8 +#: src/concurrency/send-sync/sync.md msgid "`T` is `Sync` if and only if `&T` is `Send`" msgstr "" -#: src/concurrency/send-sync/sync.md:14 +#: src/concurrency/send-sync/sync.md 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 +#: src/concurrency/send-sync/sync.md 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 " @@ -15284,255 +17491,218 @@ msgid "" "be accessed from any thread safely." msgstr "" -#: src/concurrency/send-sync/examples.md:3 +#: src/concurrency/send-sync/examples.md msgid "`Send + Sync`" msgstr "" -#: src/concurrency/send-sync/examples.md:5 +#: src/concurrency/send-sync/examples.md msgid "Most types you come across are `Send + Sync`:" msgstr "" -#: src/concurrency/send-sync/examples.md:7 +#: src/concurrency/send-sync/examples.md msgid "`i8`, `f32`, `bool`, `char`, `&str`, ..." msgstr "" -#: src/concurrency/send-sync/examples.md:8 +#: src/concurrency/send-sync/examples.md msgid "`(T1, T2)`, `[T; N]`, `&[T]`, `struct { x: T }`, ..." msgstr "" -#: src/concurrency/send-sync/examples.md:9 +#: src/concurrency/send-sync/examples.md msgid "`String`, `Option`, `Vec`, `Box`, ..." msgstr "" -#: src/concurrency/send-sync/examples.md:10 +#: src/concurrency/send-sync/examples.md msgid "`Arc`: Explicitly thread-safe via atomic reference count." msgstr "" -#: src/concurrency/send-sync/examples.md:11 +#: src/concurrency/send-sync/examples.md msgid "`Mutex`: Explicitly thread-safe via internal locking." msgstr "" -#: src/concurrency/send-sync/examples.md:12 +#: src/concurrency/send-sync/examples.md msgid "`AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions." msgstr "" -#: src/concurrency/send-sync/examples.md:14 +#: src/concurrency/send-sync/examples.md msgid "" "The generic types are typically `Send + Sync` when the type parameters are " "`Send + Sync`." msgstr "" -#: src/concurrency/send-sync/examples.md:17 +#: src/concurrency/send-sync/examples.md msgid "`Send + !Sync`" msgstr "" -#: src/concurrency/send-sync/examples.md:19 +#: src/concurrency/send-sync/examples.md 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 +#: src/concurrency/send-sync/examples.md msgid "`mpsc::Sender`" msgstr "" -#: src/concurrency/send-sync/examples.md:23 +#: src/concurrency/send-sync/examples.md msgid "`mpsc::Receiver`" msgstr "" -#: src/concurrency/send-sync/examples.md:24 +#: src/concurrency/send-sync/examples.md msgid "`Cell`" msgstr "" -#: src/concurrency/send-sync/examples.md:25 +#: src/concurrency/send-sync/examples.md msgid "`RefCell`" msgstr "" -#: src/concurrency/send-sync/examples.md:27 +#: src/concurrency/send-sync/examples.md msgid "`!Send + Sync`" msgstr "" -#: src/concurrency/send-sync/examples.md:29 +#: src/concurrency/send-sync/examples.md msgid "" "These types are thread-safe, but they cannot be moved to another thread:" msgstr "" -#: src/concurrency/send-sync/examples.md:31 +#: src/concurrency/send-sync/examples.md msgid "" "`MutexGuard`: Uses OS level primitives which must be deallocated on " "the thread which created them." msgstr "" -#: src/concurrency/send-sync/examples.md:34 +#: src/concurrency/send-sync/examples.md msgid "`!Send + !Sync`" msgstr "" -#: src/concurrency/send-sync/examples.md:36 +#: src/concurrency/send-sync/examples.md msgid "These types are not thread-safe and cannot be moved to other threads:" msgstr "" -#: src/concurrency/send-sync/examples.md:38 +#: src/concurrency/send-sync/examples.md 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 +#: src/concurrency/send-sync/examples.md msgid "" "`*const T`, `*mut T`: Rust assumes raw pointers may have special concurrency " "considerations." msgstr "" -#: src/concurrency/shared_state.md:3 +#: src/concurrency/shared_state.md 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 +#: src/concurrency/shared_state.md 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 +#: src/concurrency/shared_state.md 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 "" - -#: src/concurrency/shared_state/arc.md:3 +#: src/concurrency/shared_state/arc.md 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:5 -msgid "" -"```rust,editable\n" -"use std::thread;\n" -"use std::sync::Arc;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(vec![10, 20, 30]);\n" -" let mut handles = Vec::new();\n" -" for _ in 1..5 {\n" -" let v = Arc::clone(&v);\n" -" handles.push(thread::spawn(move || {\n" -" let thread_id = thread::current().id();\n" -" println!(\"{thread_id:?}: {v:?}\");\n" -" }));\n" -" }\n" -"\n" -" handles.into_iter().for_each(|h| h.join().unwrap());\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" +#: src/concurrency/shared_state/arc.md +msgid "\"{thread_id:?}: {v:?}\"" +msgstr "" + +#: src/concurrency/shared_state/arc.md src/concurrency/shared_state/example.md +msgid "\"v: {v:?}\"" msgstr "" -#: src/concurrency/shared_state/arc.md:29 +#: src/concurrency/shared_state/arc.md 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 +#: src/concurrency/shared_state/arc.md 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 +#: src/concurrency/shared_state/arc.md 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 +#: src/concurrency/shared_state/arc.md msgid "" "Beware of reference cycles, `Arc` does not use a garbage collector to detect " "them." msgstr "" -#: src/concurrency/shared_state/arc.md:36 +#: src/concurrency/shared_state/arc.md msgid "`std::sync::Weak` can help." msgstr "" -#: src/concurrency/shared_state/mutex.md:1 -msgid "`Mutex`" -msgstr "" - -#: src/concurrency/shared_state/mutex.md:3 +#: src/concurrency/shared_state/mutex.md 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:" +"interface (another form of [interior mutability](../../borrowing/interior-" +"mutability)):" msgstr "" -#: src/concurrency/shared_state/mutex.md:6 -msgid "" -"```rust,editable\n" -"use std::sync::Mutex;\n" -"\n" -"fn main() {\n" -" let v = Mutex::new(vec![10, 20, 30]);\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"\n" -" {\n" -" let mut guard = v.lock().unwrap();\n" -" guard.push(40);\n" -" }\n" -"\n" -" println!(\"v: {:?}\", v.lock().unwrap());\n" -"}\n" -"```" +#: src/concurrency/shared_state/mutex.md +msgid "\"v: {:?}\"" msgstr "" -#: src/concurrency/shared_state/mutex.md:22 +#: src/concurrency/shared_state/mutex.md 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 +#: src/concurrency/shared_state/mutex.md msgid "" -"`Mutex` in Rust looks like a collection with just one element - the " +"`Mutex` in Rust looks like a collection with just one element --- the " "protected data." msgstr "" -#: src/concurrency/shared_state/mutex.md:32 +#: src/concurrency/shared_state/mutex.md msgid "" "It is not possible to forget to acquire the mutex before accessing the " "protected data." msgstr "" -#: src/concurrency/shared_state/mutex.md:33 +#: src/concurrency/shared_state/mutex.md 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 +#: src/concurrency/shared_state/mutex.md 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`." +#: src/concurrency/shared_state/mutex.md +msgid "A read-write lock counterpart: `RwLock`." msgstr "" -#: src/concurrency/shared_state/mutex.md:37 -msgid "Why does `lock()` return a `Result`? " +#: src/concurrency/shared_state/mutex.md +msgid "Why does `lock()` return a `Result`?" msgstr "" -#: src/concurrency/shared_state/mutex.md:38 +#: src/concurrency/shared_state/mutex.md msgid "" "If the thread that held the `Mutex` panicked, the `Mutex` becomes " "\"poisoned\" to signal that the data it protected might be in an " @@ -15541,107 +17711,65 @@ msgid "" "You can call `into_inner()` on the error to recover the data regardless." msgstr "" -#: src/concurrency/shared_state/example.md:3 +#: src/concurrency/shared_state/example.md msgid "Let us see `Arc` and `Mutex` in action:" msgstr "" -#: src/concurrency/shared_state/example.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use std::thread;\n" -"// use std::sync::{Arc, Mutex};\n" -"\n" -"fn main() {\n" -" let v = vec![10, 20, 30];\n" -" let handle = thread::spawn(|| {\n" -" v.push(10);\n" -" });\n" -" v.push(1000);\n" -"\n" -" handle.join().unwrap();\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" +#: src/concurrency/shared_state/example.md +msgid "// use std::sync::{Arc, Mutex};\n" msgstr "" -#: src/concurrency/shared_state/example.md:23 +#: src/concurrency/shared_state/example.md msgid "Possible solution:" msgstr "" -#: src/concurrency/shared_state/example.md:25 -msgid "" -"```rust,editable\n" -"use std::sync::{Arc, Mutex};\n" -"use std::thread;\n" -"\n" -"fn main() {\n" -" let v = Arc::new(Mutex::new(vec![10, 20, 30]));\n" -"\n" -" let v2 = Arc::clone(&v);\n" -" let handle = thread::spawn(move || {\n" -" let mut v2 = v2.lock().unwrap();\n" -" v2.push(10);\n" -" });\n" -"\n" -" {\n" -" let mut v = v.lock().unwrap();\n" -" v.push(1000);\n" -" }\n" -"\n" -" handle.join().unwrap();\n" -"\n" -" println!(\"v: {v:?}\");\n" -"}\n" -"```" -msgstr "" - -#: src/concurrency/shared_state/example.md:49 +#: src/concurrency/shared_state/example.md msgid "Notable parts:" msgstr "" -#: src/concurrency/shared_state/example.md:51 +#: src/concurrency/shared_state/example.md msgid "" "`v` is wrapped in both `Arc` and `Mutex`, because their concerns are " "orthogonal." msgstr "" -#: src/concurrency/shared_state/example.md:52 +#: src/concurrency/shared_state/example.md 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 +#: src/concurrency/shared_state/example.md 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 +#: src/concurrency/shared_state/example.md msgid "" "Blocks are introduced to narrow the scope of the `LockGuard` as much as " "possible." msgstr "" -#: src/exercises/concurrency/morning.md:3 +#: src/exercises/concurrency/morning.md msgid "Let us practice our new concurrency skills with" msgstr "" -#: src/exercises/concurrency/morning.md:5 +#: src/exercises/concurrency/morning.md msgid "Dining philosophers: a classic problem in concurrency." msgstr "" -#: src/exercises/concurrency/morning.md:7 +#: src/exercises/concurrency/morning.md 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 +#: src/exercises/concurrency/dining-philosophers.md msgid "The dining philosophers problem is a classic problem in concurrency:" msgstr "" -#: src/exercises/concurrency/dining-philosophers.md:5 +#: src/exercises/concurrency/dining-philosophers.md 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 " @@ -15653,63 +17781,103 @@ msgid "" "down both forks." msgstr "" -#: src/exercises/concurrency/dining-philosophers.md:13 +#: src/exercises/concurrency/dining-philosophers.md 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:19 +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md msgid "" -"```rust,compile_fail\n" -"use std::sync::{mpsc, Arc, Mutex};\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" // left_fork: ...\n" +"// left_fork: ...\n" " // right_fork: ...\n" " // thoughts: ...\n" -"}\n" -"\n" -"impl Philosopher {\n" -" fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))\n" -" .unwrap();\n" -" }\n" -"\n" -" fn eat(&self) {\n" -" // Pick up forks...\n" -" println!(\"{} is eating...\", &self.name);\n" -" thread::sleep(Duration::from_millis(10));\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Hypatia\", \"Plato\", \"Aristotle\", \"Pythagoras\"];\n" -"\n" -"fn main() {\n" -" // Create forks\n" -"\n" -" // Create philosophers\n" -"\n" -" // Make each of them think and eat 100 times\n" -"\n" -" // Output their thoughts\n" -"}\n" -"```" msgstr "" -#: src/exercises/concurrency/dining-philosophers.md:61 +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Eureka! {} has a new idea!\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Pick up forks...\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"{} is eating...\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Socrates\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Hypatia\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Plato\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Aristotle\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Pythagoras\"" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Create forks\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Create philosophers\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +msgid "// Make each of them think and eat 100 times\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Output their thoughts\n" +msgstr "" + +#: src/exercises/concurrency/dining-philosophers.md msgid "You can use the following `Cargo.toml`:" msgstr "" -#: src/exercises/concurrency/dining-philosophers.md:65 +#: src/exercises/concurrency/dining-philosophers.md msgid "" "```toml\n" "[package]\n" @@ -15719,7 +17887,7 @@ msgid "" "```" msgstr "" -#: src/exercises/concurrency/link-checker.md:3 +#: src/exercises/concurrency/link-checker.md 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 " @@ -15727,36 +17895,36 @@ msgid "" "until all pages have been validated." msgstr "" -#: src/exercises/concurrency/link-checker.md:8 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/link-checker.md msgid "" "The `cargo add` calls will update the `Cargo.toml` file to look like this:" msgstr "" -#: src/exercises/concurrency/link-checker.md:37 +#: src/exercises/concurrency/link-checker.md msgid "" "```toml\n" "[package]\n" @@ -15773,107 +17941,130 @@ msgid "" "```" msgstr "" -#: src/exercises/concurrency/link-checker.md:50 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/link-checker.md msgid "Your `src/main.rs` file should look something like this:" msgstr "" -#: src/exercises/concurrency/link-checker.md:57 -msgid "" -"```rust,compile_fail\n" -"use reqwest::{blocking::Client, Url};\n" -"use scraper::{Html, Selector};\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Error, Debug)]\n" -"enum Error {\n" -" #[error(\"request error: {0}\")]\n" -" ReqwestError(#[from] reqwest::Error),\n" -" #[error(\"bad http response: {0}\")]\n" -" BadResponse(String),\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct CrawlCommand {\n" -" url: Url,\n" -" extract_links: bool,\n" -"}\n" -"\n" -"fn visit_page(client: &Client, command: &CrawlCommand) -> Result, " -"Error> {\n" -" println!(\"Checking {:#}\", command.url);\n" -" let response = client.get(command.url.clone()).send()?;\n" -" if !response.status().is_success() {\n" -" return Err(Error::BadResponse(response.status().to_string()));\n" -" }\n" -"\n" -" let mut link_urls = Vec::new();\n" -" if !command.extract_links {\n" -" return Ok(link_urls);\n" -" }\n" -"\n" -" let base_url = response.url().to_owned();\n" -" let body_text = response.text()?;\n" -" let document = Html::parse_document(&body_text);\n" -"\n" -" let selector = Selector::parse(\"a\").unwrap();\n" -" let href_values = document\n" -" .select(&selector)\n" -" .filter_map(|element| element.value().attr(\"href\"));\n" -" for href in href_values {\n" -" match base_url.join(href) {\n" -" Ok(link_url) => {\n" -" link_urls.push(link_url);\n" -" }\n" -" Err(err) => {\n" -" println!(\"On {base_url:#}: ignored unparsable {href:?}: " -"{err}\");\n" -" }\n" -" }\n" -" }\n" -" Ok(link_urls)\n" -"}\n" -"\n" -"fn main() {\n" -" let client = Client::new();\n" -" let start_url = Url::parse(\"https://www.google.org\").unwrap();\n" -" let crawl_command = CrawlCommand{ url: start_url, extract_links: " -"true };\n" -" match visit_page(&client, &crawl_command) {\n" -" Ok(links) => println!(\"Links: {links:#?}\"),\n" -" Err(err) => println!(\"Could not extract links: {err:#}\"),\n" -" }\n" -"}\n" -"```" +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"request error: {0}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"bad http response: {0}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"Checking {:#}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"href\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"On {base_url:#}: ignored unparsable {href:?}: {err}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md +msgid "\"https://www.google.org\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +msgid "\"Links: {links:#?}\"" +msgstr "" + +#: src/exercises/concurrency/link-checker.md +msgid "\"Could not extract links: {err:#}\"" msgstr "" -#: src/exercises/concurrency/link-checker.md:120 +#: src/exercises/concurrency/link-checker.md msgid "Run the code in `src/main.rs` with" msgstr "" -#: src/exercises/concurrency/link-checker.md:128 +#: src/exercises/concurrency/link-checker.md msgid "" "Use threads to check the links in parallel: send the URLs to be checked to a " "channel and let a few threads check the URLs in parallel." msgstr "" -#: src/exercises/concurrency/link-checker.md:130 +#: src/exercises/concurrency/link-checker.md 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 +#: src/exercises/concurrency/solutions-morning.md +msgid "Concurrency Morning Exercise" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "([back to exercise](dining-philosophers.md))" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "\"{} is trying to eat\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +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 +msgid "\"{thought}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "Link Checker" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "([back to exercise](link-checker.md))" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "" +"/// Determine whether links within the given page should be extracted.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "" +"/// Mark the given page as visited, returning false if it had already\n" +" /// been visited.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "// The sender got dropped. No more commands coming in.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "\"Got crawling error: {:#}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-morning.md +msgid "\"Bad URLs: {:#?}\"" +msgstr "" + +#: src/async.md msgid "Async Rust" msgstr "" -#: src/async.md:3 +#: src/async.md msgid "" "\"Async\" is a concurrency model where multiple tasks are executed " "concurrently by executing each task until it would block, then switching to " @@ -15883,113 +18074,88 @@ msgid "" "primitives for efficiently identifying I/O that is able to proceed." msgstr "" -#: src/async.md:10 +#: src/async.md 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 +#: src/async.md msgid "" "Futures are polled by an async runtime, and several different runtimes are " "available." msgstr "" -#: src/async.md:17 -msgid "Comparisons" -msgstr "" - -#: src/async.md:19 +#: src/async.md 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 +#: src/async.md 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 "" - -#: src/async/async-await.md:3 +#: src/async/async-await.md msgid "" "At a high level, async Rust code looks very much like \"normal\" sequential " "code:" msgstr "" -#: src/async/async-await.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use futures::executor::block_on;\n" -"\n" -"async fn count_to(count: i32) {\n" -" for i in 1..=count {\n" -" println!(\"Count is: {i}!\");\n" -" }\n" -"}\n" -"\n" -"async fn async_main(count: i32) {\n" -" count_to(count).await;\n" -"}\n" -"\n" -"fn main() {\n" -" block_on(async_main(10));\n" -"}\n" -"```" +#: src/async/async-await.md +msgid "\"Count is: {i}!\"" msgstr "" -#: src/async/async-await.md:27 +#: src/async/async-await.md 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 +#: src/async/async-await.md msgid "What is the return type of an async call?" msgstr "" -#: src/async/async-await.md:31 +#: src/async/async-await.md msgid "Use `let future: () = async_main(10);` in `main` to see the type." msgstr "" -#: src/async/async-await.md:33 +#: src/async/async-await.md msgid "" "The \"async\" keyword is syntactic sugar. The compiler replaces the return " -"type with a future. " +"type with a future." msgstr "" -#: src/async/async-await.md:36 +#: src/async/async-await.md 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 +#: src/async/async-await.md msgid "" "You need an executor to run async code. `block_on` blocks the current thread " -"until the provided future has run to completion. " +"until the provided future has run to completion." msgstr "" -#: src/async/async-await.md:42 +#: src/async/async-await.md 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 +#: src/async/async-await.md msgid "" "`.await` can only be used inside an `async` function (or block; these are " -"introduced later). " +"introduced later)." msgstr "" -#: src/async/futures.md:3 +#: src/async/futures.md 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 " @@ -15997,7 +18163,7 @@ msgid "" "doc.rust-lang.org/std/task/enum.Poll.html)." msgstr "" -#: src/async/futures.md:23 +#: src/async/futures.md msgid "" "An async function returns an `impl Future`. It's also possible (but " "uncommon) to implement `Future` for your own types. For example, the " @@ -16005,76 +18171,76 @@ msgid "" "joining to it." msgstr "" -#: src/async/futures.md:27 +#: src/async/futures.md 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 +#: src/async/futures.md 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 +#: src/async/futures.md 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 +#: src/async/futures.md msgid "" "`Context` allows a Future to schedule itself to be polled again when an " "event occurs." msgstr "" -#: src/async/futures.md:41 +#: src/async/futures.md 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 +#: src/async/runtimes.md 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 +#: src/async/runtimes.md 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 +#: src/async/runtimes.md 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 +#: src/async/runtimes.md msgid "[smol](https://docs.rs/smol/latest/smol/): simple and lightweight" msgstr "" -#: src/async/runtimes.md:14 +#: src/async/runtimes.md 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 +#: src/async/runtimes.md 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 +#: src/async/runtimes.md 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 " @@ -16082,82 +18248,66 @@ msgid "" "used." msgstr "" -#: src/async/runtimes/tokio.md:4 -msgid "Tokio provides: " +#: src/async/runtimes/tokio.md +msgid "Tokio provides:" msgstr "" -#: src/async/runtimes/tokio.md:6 +#: src/async/runtimes/tokio.md msgid "A multi-threaded runtime for executing asynchronous code." msgstr "" -#: src/async/runtimes/tokio.md:7 +#: src/async/runtimes/tokio.md msgid "An asynchronous version of the standard library." msgstr "" -#: src/async/runtimes/tokio.md:8 +#: src/async/runtimes/tokio.md msgid "A large ecosystem of libraries." msgstr "" -#: src/async/runtimes/tokio.md:10 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::time;\n" -"\n" -"async fn count_to(count: i32) {\n" -" for i in 1..=count {\n" -" println!(\"Count in task: {i}!\");\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" tokio::spawn(count_to(10));\n" -"\n" -" for i in 1..5 {\n" -" println!(\"Main task: {i}\");\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"```" +#: src/async/runtimes/tokio.md +msgid "\"Count in task: {i}!\"" +msgstr "" + +#: src/async/runtimes/tokio.md +msgid "\"Main task: {i}\"" msgstr "" -#: src/async/runtimes/tokio.md:33 +#: src/async/runtimes/tokio.md msgid "With the `tokio::main` macro we can now make `main` async." msgstr "" -#: src/async/runtimes/tokio.md:35 +#: src/async/runtimes/tokio.md msgid "The `spawn` function creates a new, concurrent \"task\"." msgstr "" -#: src/async/runtimes/tokio.md:37 +#: src/async/runtimes/tokio.md msgid "Note: `spawn` takes a `Future`, you don't call `.await` on `count_to`." msgstr "" -#: src/async/runtimes/tokio.md:39 +#: src/async/runtimes/tokio.md msgid "**Further exploration:**" msgstr "" -#: src/async/runtimes/tokio.md:41 +#: src/async/runtimes/tokio.md msgid "" "Why does `count_to` not (usually) get to 10? This is an example of async " "cancellation. `tokio::spawn` returns a handle which can be awaited to wait " "until it finishes." msgstr "" -#: src/async/runtimes/tokio.md:45 +#: src/async/runtimes/tokio.md msgid "Try `count_to(10).await` instead of spawning." msgstr "" -#: src/async/runtimes/tokio.md:47 +#: src/async/runtimes/tokio.md msgid "Try awaiting the task returned from `tokio::spawn`." msgstr "" -#: src/async/tasks.md:3 +#: src/async/tasks.md msgid "Rust has a task system, which is a form of lightweight threading." msgstr "" -#: src/async/tasks.md:5 +#: src/async/tasks.md 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` " @@ -16166,216 +18316,170 @@ msgid "" "and an I/O operation." msgstr "" -#: src/async/tasks.md:10 -msgid "" -"```rust,compile_fail\n" -"use tokio::io::{self, AsyncReadExt, AsyncWriteExt};\n" -"use tokio::net::TcpListener;\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> io::Result<()> {\n" -" let listener = TcpListener::bind(\"127.0.0.1:6142\").await?;\n" -"\tprintln!(\"listening on port 6142\");\n" -"\n" -" loop {\n" -" let (mut socket, addr) = listener.accept().await?;\n" -"\n" -" println!(\"connection from {addr:?}\");\n" -"\n" -" tokio::spawn(async move {\n" -" if let Err(e) = socket.write_all(b\"Who are you?\\n\").await {\n" -" println!(\"socket error: {e:?}\");\n" -" return;\n" -" }\n" -"\n" -" let mut buf = vec![0; 1024];\n" -" let reply = match socket.read(&mut buf).await {\n" -" Ok(n) => {\n" -" let name = std::str::from_utf8(&buf[..n]).unwrap()." -"trim();\n" -" format!(\"Thanks for dialing in, {name}!\\n\")\n" -" }\n" -" Err(e) => {\n" -" println!(\"socket error: {e:?}\");\n" -" return;\n" -" }\n" -" };\n" -"\n" -" if let Err(e) = socket.write_all(reply.as_bytes()).await {\n" -" println!(\"socket error: {e:?}\");\n" -" }\n" -" });\n" -" }\n" -"}\n" -"```" +#: src/async/tasks.md +msgid "\"127.0.0.1:0\"" +msgstr "" + +#: src/async/tasks.md +msgid "\"listening on port {}\"" +msgstr "" + +#: src/async/tasks.md +msgid "\"connection from {addr:?}\"" +msgstr "" + +#: src/async/tasks.md +msgid "b\"Who are you?\\n\"" +msgstr "" + +#: src/async/tasks.md +msgid "\"socket error\"" +msgstr "" + +#: src/async/tasks.md +msgid "\"Thanks for dialing in, {name}!\\n\"" msgstr "" -#: src/async/tasks.md:52 src/async/control-flow/join.md:36 +#: src/async/tasks.md src/async/control-flow/join.md msgid "" "Copy this example into your prepared `src/main.rs` and run it from there." msgstr "" -#: src/async/tasks.md:54 +#: src/async/tasks.md msgid "" "Try connecting to it with a TCP connection tool like [nc](https://www.unix." "com/man-page/linux/1/nc/) or [telnet](https://www.unix.com/man-page/linux/1/" "telnet/)." msgstr "" -#: src/async/tasks.md:56 +#: src/async/tasks.md 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:59 +#: src/async/tasks.md msgid "" "This is the first time we've seen an `async` block. This is similar to a " "closure, but does not take any arguments. Its return value is a Future, " -"similar to an `async fn`. " +"similar to an `async fn`." msgstr "" -#: src/async/tasks.md:63 +#: src/async/tasks.md msgid "" "Refactor the async block into a function, and improve the error handling " -"using `?`. " +"using `?`." msgstr "" -#: src/async/channels.md:3 +#: src/async/channels.md msgid "" "Several crates have support for asynchronous channels. For instance `tokio`:" msgstr "" -#: src/async/channels.md:5 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::mpsc::{self, Receiver};\n" -"\n" -"async fn ping_handler(mut input: Receiver<()>) {\n" -" let mut count: usize = 0;\n" -"\n" -" while let Some(_) = input.recv().await {\n" -" count += 1;\n" -" println!(\"Received {count} pings so far.\");\n" -" }\n" -"\n" -" println!(\"ping_handler complete\");\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (sender, receiver) = mpsc::channel(32);\n" -" let ping_handler_task = tokio::spawn(ping_handler(receiver));\n" -" for i in 0..10 {\n" -" sender.send(()).await.expect(\"Failed to send ping.\");\n" -" println!(\"Sent {} pings so far.\", i + 1);\n" -" }\n" -"\n" -" drop(sender);\n" -" ping_handler_task.await.expect(\"Something went wrong in ping handler " -"task.\");\n" -"}\n" -"```" +#: src/async/channels.md +msgid "\"Received {count} pings so far.\"" +msgstr "" + +#: src/async/channels.md +msgid "\"ping_handler complete\"" +msgstr "" + +#: src/async/channels.md +msgid "\"Failed to send ping.\"" msgstr "" -#: src/async/channels.md:35 +#: src/async/channels.md +msgid "\"Sent {} pings so far.\"" +msgstr "" + +#: src/async/channels.md +msgid "\"Something went wrong in ping handler task.\"" +msgstr "" + +#: src/async/channels.md msgid "Change the channel size to `3` and see how it affects the execution." msgstr "" -#: src/async/channels.md:37 +#: src/async/channels.md 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 +#: src/async/channels.md msgid "Try removing the `std::mem::drop` call. What happens? Why?" msgstr "" -#: src/async/channels.md:42 +#: src/async/channels.md 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 +#: src/async/channels.md 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 +#: src/async/control-flow.md msgid "Futures Control Flow" msgstr "" -#: src/async/control-flow.md:3 +#: src/async/control-flow.md 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 +#: src/async/control-flow.md msgid "[Join](control-flow/join.md)" msgstr "" -#: src/async/control-flow.md:7 +#: src/async/control-flow.md msgid "[Select](control-flow/select.md)" msgstr "" -#: src/async/control-flow/join.md:3 +#: src/async/control-flow/join.md 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:7 -msgid "" -"```rust,editable,compile_fail\n" -"use anyhow::Result;\n" -"use futures::future;\n" -"use reqwest;\n" -"use std::collections::HashMap;\n" -"\n" -"async fn size_of_page(url: &str) -> Result {\n" -" let resp = reqwest::get(url).await?;\n" -" Ok(resp.text().await?.len())\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let urls: [&str; 4] = [\n" -" \"https://google.com\",\n" -" \"https://httpbin.org/ip\",\n" -" \"https://play.rust-lang.org/\",\n" -" \"BAD_URL\",\n" -" ];\n" -" let futures_iter = urls.into_iter().map(size_of_page);\n" -" let results = future::join_all(futures_iter).await;\n" -" let page_sizes_dict: HashMap<&str, Result> =\n" -" urls.into_iter().zip(results.into_iter()).collect();\n" -" println!(\"{:?}\", page_sizes_dict);\n" -"}\n" -"```" +#: src/async/control-flow/join.md +msgid "\"https://google.com\"" +msgstr "" + +#: src/async/control-flow/join.md +msgid "\"https://httpbin.org/ip\"" +msgstr "" + +#: src/async/control-flow/join.md +msgid "\"https://play.rust-lang.org/\"" +msgstr "" + +#: src/async/control-flow/join.md +msgid "\"BAD_URL\"" msgstr "" -#: src/async/control-flow/join.md:38 +#: src/async/control-flow/join.md 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 +#: src/async/control-flow/join.md msgid "" "The risk of `join` is that one of the futures may never resolve, this would " -"cause your program to stall. " +"cause your program to stall." msgstr "" -#: src/async/control-flow/join.md:45 +#: src/async/control-flow/join.md 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 " @@ -16384,7 +18488,7 @@ msgid "" "demonstrates `join!`." msgstr "" -#: src/async/control-flow/select.md:3 +#: src/async/control-flow/select.md 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." @@ -16392,65 +18496,40 @@ msgid "" "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." +#: src/async/control-flow/select.md +msgid "" +"Similar to a match statement, the body of `select!` has a number of arms, " +"each of the form `pattern = future => statement`. When a `future` is ready, " +"its return value is destructured by the `pattern`. The `statement` is then " +"run with the resulting variables. The `statement` result becomes the result " +"of the `select!` macro." +msgstr "" + +#: src/async/control-flow/select.md +msgid "\"Felix\"" +msgstr "" + +#: src/async/control-flow/select.md +msgid "\"Failed to send cat.\"" +msgstr "" + +#: src/async/control-flow/select.md +msgid "\"Rex\"" msgstr "" -#: src/async/control-flow/select.md:13 -msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::mpsc::{self, Receiver};\n" -"use tokio::time::{sleep, Duration};\n" -"\n" -"#[derive(Debug, PartialEq)]\n" -"enum Animal {\n" -" Cat { name: String },\n" -" Dog { name: String },\n" -"}\n" -"\n" -"async fn first_animal_to_finish_race(\n" -" mut cat_rcv: Receiver,\n" -" mut dog_rcv: Receiver,\n" -") -> Option {\n" -" tokio::select! {\n" -" cat_name = cat_rcv.recv() => Some(Animal::Cat { name: cat_name? }),\n" -" dog_name = dog_rcv.recv() => Some(Animal::Dog { name: dog_name? })\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (cat_sender, cat_receiver) = mpsc::channel(32);\n" -" let (dog_sender, dog_receiver) = mpsc::channel(32);\n" -" tokio::spawn(async move {\n" -" sleep(Duration::from_millis(500)).await;\n" -" cat_sender\n" -" .send(String::from(\"Felix\"))\n" -" .await\n" -" .expect(\"Failed to send cat.\");\n" -" });\n" -" tokio::spawn(async move {\n" -" sleep(Duration::from_millis(50)).await;\n" -" dog_sender\n" -" .send(String::from(\"Rex\"))\n" -" .await\n" -" .expect(\"Failed to send dog.\");\n" -" });\n" -"\n" -" let winner = first_animal_to_finish_race(cat_receiver, dog_receiver)\n" -" .await\n" -" .expect(\"Failed to receive winner\");\n" -"\n" -" println!(\"Winner is {winner:?}\");\n" -"}\n" -"```" +#: src/async/control-flow/select.md +msgid "\"Failed to send dog.\"" +msgstr "" + +#: src/async/control-flow/select.md +msgid "\"Failed to receive winner\"" +msgstr "" + +#: src/async/control-flow/select.md +msgid "\"Winner is {winner:?}\"" msgstr "" -#: src/async/control-flow/select.md:62 +#: src/async/control-flow/select.md 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 " @@ -16458,35 +18537,35 @@ msgid "" "that take 500ms." msgstr "" -#: src/async/control-flow/select.md:67 +#: src/async/control-flow/select.md msgid "" "You can use `oneshot` channels in this example as the channels are supposed " "to receive only one `send`." msgstr "" -#: src/async/control-flow/select.md:70 +#: src/async/control-flow/select.md msgid "" "Try adding a deadline to the race, demonstrating selecting different sorts " "of futures." msgstr "" -#: src/async/control-flow/select.md:73 +#: src/async/control-flow/select.md msgid "" "Note that `select!` drops unmatched branches, which cancels their futures. " "It is easiest to use when every execution of `select!` creates new futures." msgstr "" -#: src/async/control-flow/select.md:76 +#: src/async/control-flow/select.md 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 +#: src/async/pitfalls.md msgid "Pitfalls of async/await" msgstr "" -#: src/async/pitfalls.md:3 +#: src/async/pitfalls.md msgid "" "Async / await provides convenient and efficient abstraction for concurrent " "asynchronous programming. However, the async/await model in Rust also comes " @@ -16494,27 +18573,27 @@ msgid "" "chapter:" msgstr "" -#: src/async/pitfalls.md:5 +#: src/async/pitfalls.md msgid "[Blocking the Executor](pitfalls/blocking-executor.md)" msgstr "" -#: src/async/pitfalls.md:6 +#: src/async/pitfalls.md msgid "[Pin](pitfalls/pin.md)" msgstr "" -#: src/async/pitfalls.md:7 +#: src/async/pitfalls.md msgid "[Async Traits](pitfalls/async-traits.md)" msgstr "" -#: src/async/pitfalls.md:8 +#: src/async/pitfalls.md msgid "[Cancellation](pitfalls/cancellation.md)" msgstr "" -#: src/async/pitfalls/blocking-executor.md:1 +#: src/async/pitfalls/blocking-executor.md msgid "Blocking the executor" msgstr "" -#: src/async/pitfalls/blocking-executor.md:3 +#: src/async/pitfalls/blocking-executor.md 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 " @@ -16522,54 +18601,39 @@ msgid "" "possible." msgstr "" -#: src/async/pitfalls/blocking-executor.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"use futures::future::join_all;\n" -"use std::time::Instant;\n" -"\n" -"async fn sleep_ms(start: &Instant, id: u64, duration_ms: u64) {\n" -" std::thread::sleep(std::time::Duration::from_millis(duration_ms));\n" -" println!(\n" -" \"future {id} slept for {duration_ms}ms, finished after {}ms\",\n" -" start.elapsed().as_millis()\n" -" );\n" -"}\n" -"\n" -"#[tokio::main(flavor = \"current_thread\")]\n" -"async fn main() {\n" -" let start = Instant::now();\n" -" let sleep_futures = (1..=10).map(|t| sleep_ms(&start, t, t * 10));\n" -" join_all(sleep_futures).await;\n" -"}\n" -"```" +#: src/async/pitfalls/blocking-executor.md +msgid "\"future {id} slept for {duration_ms}ms, finished after {}ms\"" +msgstr "" + +#: src/async/pitfalls/blocking-executor.md +msgid "\"current_thread\"" msgstr "" -#: src/async/pitfalls/blocking-executor.md:29 +#: src/async/pitfalls/blocking-executor.md msgid "" "Run the code and see that the sleeps happen consecutively rather than " "concurrently." msgstr "" -#: src/async/pitfalls/blocking-executor.md:32 +#: src/async/pitfalls/blocking-executor.md 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 +#: src/async/pitfalls/blocking-executor.md msgid "" "Switch the `std::thread::sleep` to `tokio::time::sleep` and await its result." msgstr "" -#: src/async/pitfalls/blocking-executor.md:38 +#: src/async/pitfalls/blocking-executor.md 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 +#: src/async/pitfalls/blocking-executor.md 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 " @@ -16579,135 +18643,146 @@ msgid "" "situations." msgstr "" -#: src/async/pitfalls/blocking-executor.md:47 +#: src/async/pitfalls/blocking-executor.md 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 +#: src/async/pitfalls/pin.md 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." +"Async blocks and functions return types implementing the `Future` trait. The " +"type returned is the result of a compiler transformation which turns local " +"variables into data stored inside the future." msgstr "" -#: src/async/pitfalls/pin.md:8 +#: src/async/pitfalls/pin.md 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." +"Some of those variables can hold pointers to other local variables. Because " +"of that, the future should never be moved to a different memory location, as " +"it would invalidate those pointers." msgstr "" -#: src/async/pitfalls/pin.md:12 +#: src/async/pitfalls/pin.md +msgid "" +"To prevent moving the future type in memory, it can only be polled through a " +"pinned pointer. `Pin` is a wrapper around a reference that disallows all " +"operations that would move the instance it points to into a different memory " +"location." +msgstr "" + +#: src/async/pitfalls/pin.md msgid "" -"```rust,editable,compile_fail\n" -"use tokio::sync::{mpsc, oneshot};\n" -"use tokio::task::spawn;\n" -"use tokio::time::{sleep, Duration};\n" -"\n" "// A work item. In this case, just sleep for the given time and respond\n" "// with a message on the `respond_on` channel.\n" -"#[derive(Debug)]\n" -"struct Work {\n" -" input: u32,\n" -" respond_on: oneshot::Sender,\n" -"}\n" -"\n" -"// A worker which listens for work on a queue and performs it.\n" -"async fn worker(mut work_queue: mpsc::Receiver) {\n" -" let mut iterations = 0;\n" -" loop {\n" -" tokio::select! {\n" -" Some(work) = work_queue.recv() => {\n" -" sleep(Duration::from_millis(10)).await; // Pretend to work.\n" -" work.respond_on\n" -" .send(work.input * 1000)\n" -" .expect(\"failed to send response\");\n" -" iterations += 1;\n" -" }\n" -" // TODO: report number of iterations every 100ms\n" -" }\n" -" }\n" -"}\n" -"\n" -"// A requester which requests work and waits for it to complete.\n" -"async fn do_work(work_queue: &mpsc::Sender, input: u32) -> u32 {\n" -" let (tx, rx) = oneshot::channel();\n" -" work_queue\n" -" .send(Work {\n" -" input,\n" -" respond_on: tx,\n" -" })\n" -" .await\n" -" .expect(\"failed to send on work queue\");\n" -" rx.await.expect(\"failed waiting for response\")\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let (tx, rx) = mpsc::channel(10);\n" -" spawn(worker(rx));\n" -" for i in 0..100 {\n" -" let resp = do_work(&tx, i).await;\n" -" println!(\"work result for iteration {i}: {resp}\");\n" -" }\n" -"}\n" -"```" msgstr "" -#: src/async/pitfalls/pin.md:68 +#: src/async/pitfalls/pin.md +msgid "// A worker which listens for work on a queue and performs it.\n" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "// Pretend to work.\n" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "\"failed to send response\"" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "// TODO: report number of iterations every 100ms\n" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "// A requester which requests work and waits for it to complete.\n" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "\"failed to send on work queue\"" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "\"failed waiting for response\"" +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "\"work result for iteration {i}: {resp}\"" +msgstr "" + +#: src/async/pitfalls/pin.md msgid "" "You may recognize this as an example of the actor pattern. Actors typically " "call `select!` in a loop." msgstr "" -#: src/async/pitfalls/pin.md:71 +#: src/async/pitfalls/pin.md msgid "" "This serves as a summation of a few of the previous lessons, so take your " "time with it." msgstr "" -#: src/async/pitfalls/pin.md:74 +#: src/async/pitfalls/pin.md msgid "" "Naively add a `_ = sleep(Duration::from_millis(100)) => { println!(..) }` to " "the `select!`. This will never execute. Why?" msgstr "" -#: src/async/pitfalls/pin.md:77 +#: src/async/pitfalls/pin.md msgid "" "Instead, add a `timeout_fut` containing that future outside of the `loop`:" msgstr "" -#: src/async/pitfalls/pin.md:88 +#: src/async/pitfalls/pin.md msgid "" "This still doesn't work. Follow the compiler errors, adding `&mut` to the " "`timeout_fut` in the `select!` to work around the move, then using `Box::" "pin`:" msgstr "" -#: src/async/pitfalls/pin.md:102 +#: src/async/pitfalls/pin.md msgid "" "This compiles, but once the timeout expires it is `Poll::Ready` on every " "iteration (a fused future would help with this). Update to reset " "`timeout_fut` every time it expires." msgstr "" -#: src/async/pitfalls/pin.md:106 +#: src/async/pitfalls/pin.md msgid "" "Box allocates on the heap. In some cases, `std::pin::pin!` (only recently " "stabilized, with older code often using `tokio::pin!`) is also an option, " "but that is difficult to use for a future that is reassigned." msgstr "" -#: src/async/pitfalls/pin.md:110 +#: src/async/pitfalls/pin.md 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 +#: src/async/pitfalls/pin.md +msgid "" +"Data that contains pointers to itself is called self-referential. Normally, " +"the Rust borrow checker would prevent self-referential data from being " +"moved, as the references cannot outlive the data they point to. However, the " +"code transformation for async blocks and functions is not verified by the " +"borrow checker." +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "" +"`Pin` is a wrapper around a reference. An object cannot be moved from its " +"place using a pinned pointer. However, it can still be moved through an " +"unpinned pointer." +msgstr "" + +#: src/async/pitfalls/pin.md +msgid "" +"The `poll` method of the `Future` trait uses `Pin<&mut Self>` instead of " +"`&mut Self` to refer to the instance. That's why it can only be called on a " +"pinned pointer." +msgstr "" + +#: src/async/pitfalls/async-traits.md 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 " @@ -16715,65 +18790,27 @@ msgid "" "nightly.html))" msgstr "" -#: src/async/pitfalls/async-traits.md:5 +#: src/async/pitfalls/async-traits.md msgid "" "The crate [async_trait](https://docs.rs/async-trait/latest/async_trait/) " "provides a workaround through a macro:" msgstr "" -#: src/async/pitfalls/async-traits.md:7 -msgid "" -"```rust,editable,compile_fail\n" -"use async_trait::async_trait;\n" -"use std::time::Instant;\n" -"use tokio::time::{sleep, Duration};\n" -"\n" -"#[async_trait]\n" -"trait Sleeper {\n" -" async fn sleep(&self);\n" -"}\n" -"\n" -"struct FixedSleeper {\n" -" sleep_ms: u64,\n" -"}\n" -"\n" -"#[async_trait]\n" -"impl Sleeper for FixedSleeper {\n" -" async fn sleep(&self) {\n" -" sleep(Duration::from_millis(self.sleep_ms)).await;\n" -" }\n" -"}\n" -"\n" -"async fn run_all_sleepers_multiple_times(sleepers: Vec>, " -"n_times: usize) {\n" -" for _ in 0..n_times {\n" -" println!(\"running all sleepers..\");\n" -" for sleeper in &sleepers {\n" -" let start = Instant::now();\n" -" sleeper.sleep().await;\n" -" println!(\"slept for {}ms\", start.elapsed().as_millis());\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" let sleepers: Vec> = vec![\n" -" Box::new(FixedSleeper { sleep_ms: 50 }),\n" -" Box::new(FixedSleeper { sleep_ms: 100 }),\n" -" ];\n" -" run_all_sleepers_multiple_times(sleepers, 5).await;\n" -"}\n" -"```" +#: src/async/pitfalls/async-traits.md +msgid "\"running all sleepers..\"" +msgstr "" + +#: src/async/pitfalls/async-traits.md +msgid "\"slept for {}ms\"" msgstr "" -#: src/async/pitfalls/async-traits.md:51 +#: src/async/pitfalls/async-traits.md msgid "" "`async_trait` is easy to use, but note that it's using heap allocations to " "achieve this. This heap allocation has performance overhead." msgstr "" -#: src/async/pitfalls/async-traits.md:54 +#: src/async/pitfalls/async-traits.md 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 " @@ -16782,13 +18819,13 @@ msgid "" "digging deeper." msgstr "" -#: src/async/pitfalls/async-traits.md:60 +#: src/async/pitfalls/async-traits.md 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 +#: src/async/pitfalls/cancellation.md 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 " @@ -16796,237 +18833,119 @@ msgid "" "example, it shouldn't deadlock or lose data." msgstr "" -#: src/async/pitfalls/cancellation.md:8 -msgid "" -"```rust,editable,compile_fail\n" -"use std::io::{self, ErrorKind};\n" -"use std::time::Duration;\n" -"use tokio::io::{AsyncReadExt, AsyncWriteExt, DuplexStream};\n" -"\n" -"struct LinesReader {\n" -" stream: DuplexStream,\n" -"}\n" -"\n" -"impl LinesReader {\n" -" fn new(stream: DuplexStream) -> Self {\n" -" Self { stream }\n" -" }\n" -"\n" -" async fn next(&mut self) -> io::Result> {\n" -" let mut bytes = Vec::new();\n" -" let mut buf = [0];\n" -" while self.stream.read(&mut buf[..]).await? != 0 {\n" -" bytes.push(buf[0]);\n" -" if buf[0] == b'\\n' {\n" -" break;\n" -" }\n" -" }\n" -" if bytes.is_empty() {\n" -" return Ok(None)\n" -" }\n" -" let s = String::from_utf8(bytes)\n" -" .map_err(|_| io::Error::new(ErrorKind::InvalidData, \"not " -"UTF-8\"))?;\n" -" Ok(Some(s))\n" -" }\n" -"}\n" -"\n" -"async fn slow_copy(source: String, mut dest: DuplexStream) -> std::io::" -"Result<()> {\n" -" for b in source.bytes() {\n" -" dest.write_u8(b).await?;\n" -" tokio::time::sleep(Duration::from_millis(10)).await\n" -" }\n" -" Ok(())\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> std::io::Result<()> {\n" -" let (client, server) = tokio::io::duplex(5);\n" -" let handle = tokio::spawn(slow_copy(\"hi\\nthere\\n\".to_owned(), " -"client));\n" -"\n" -" let mut lines = LinesReader::new(server);\n" -" let mut interval = tokio::time::interval(Duration::from_millis(60));\n" -" loop {\n" -" tokio::select! {\n" -" _ = interval.tick() => println!(\"tick!\"),\n" -" line = lines.next() => if let Some(l) = line? {\n" -" print!(\"{}\", l)\n" -" } else {\n" -" break\n" -" },\n" -" }\n" -" }\n" -" handle.await.unwrap()?;\n" -" Ok(())\n" -"}\n" -"```" +#: src/async/pitfalls/cancellation.md +msgid "\"not UTF-8\"" +msgstr "" + +#: src/async/pitfalls/cancellation.md +msgid "\"hi\\nthere\\n\"" +msgstr "" + +#: src/async/pitfalls/cancellation.md +msgid "\"tick!\"" msgstr "" -#: src/async/pitfalls/cancellation.md:72 +#: src/async/pitfalls/cancellation.md 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 +#: src/async/pitfalls/cancellation.md msgid "" "Unlike `panic` and `?`, cancellation is part of normal control flow (vs " "error-handling)." msgstr "" -#: src/async/pitfalls/cancellation.md:78 +#: src/async/pitfalls/cancellation.md msgid "The example loses parts of the string." msgstr "" -#: src/async/pitfalls/cancellation.md:80 +#: src/async/pitfalls/cancellation.md msgid "" "Whenever the `tick()` branch finishes first, `next()` and its `buf` are " "dropped." msgstr "" -#: src/async/pitfalls/cancellation.md:82 +#: src/async/pitfalls/cancellation.md msgid "" "`LinesReader` can be made cancellation-safe by making `buf` part of the " "struct:" msgstr "" -#: src/async/pitfalls/cancellation.md:83 -msgid "" -"```rust,compile_fail\n" -"struct LinesReader {\n" -" stream: DuplexStream,\n" -" bytes: Vec,\n" -" buf: [u8; 1],\n" -"}\n" -"\n" -"impl LinesReader {\n" -" fn new(stream: DuplexStream) -> Self {\n" -" Self { stream, bytes: Vec::new(), buf: [0] }\n" -" }\n" -" async fn next(&mut self) -> io::Result> {\n" -" // prefix buf and bytes with self.\n" -" // ...\n" -" let raw = std::mem::take(&mut self.bytes);\n" -" let s = String::from_utf8(raw)\n" -" // ...\n" -" }\n" -"}\n" -"```" +#: src/async/pitfalls/cancellation.md +msgid "// prefix buf and bytes with self.\n" msgstr "" -#: src/async/pitfalls/cancellation.md:104 +#: src/async/pitfalls/cancellation.md 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 +#: src/async/pitfalls/cancellation.md 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 +#: src/async/pitfalls/cancellation.md 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 +#: src/exercises/concurrency/afternoon.md msgid "" "To practice your Async Rust skills, we have again two exercises for you:" msgstr "" -#: src/exercises/concurrency/afternoon.md:5 +#: src/exercises/concurrency/afternoon.md 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 +#: src/exercises/concurrency/afternoon.md 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 +#: src/exercises/concurrency/solutions-afternoon.md +#, fuzzy +msgid "Dining Philosophers --- Async" +msgstr "Filozofların Akşam Yemeği" -#: src/exercises/concurrency/dining-philosophers-async.md:3 +#: src/exercises/concurrency/dining-philosophers-async.md msgid "" "See [dining philosophers](dining-philosophers.md) for a description of the " "problem." msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md:6 +#: src/exercises/concurrency/dining-philosophers-async.md 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:13 -msgid "" -"```rust,compile_fail\n" -"use std::sync::Arc;\n" -"use tokio::time;\n" -"use tokio::sync::mpsc::{self, Sender};\n" -"use tokio::sync::Mutex;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" // left_fork: ...\n" -" // right_fork: ...\n" -" // thoughts: ...\n" -"}\n" -"\n" -"impl Philosopher {\n" -" async fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))." -"await\n" -" .unwrap();\n" -" }\n" -"\n" -" async fn eat(&self) {\n" -" // Pick up forks...\n" -" println!(\"{} is eating...\", &self.name);\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Hypatia\", \"Plato\", \"Aristotle\", \"Pythagoras\"];\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" // Create forks\n" -"\n" -" // Create philosophers\n" -"\n" -" // Make them think and eat\n" -"\n" -" // Output their thoughts\n" -"}\n" -"```" +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Make them think and eat\n" msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md:57 +#: src/exercises/concurrency/dining-philosophers-async.md 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 +#: src/exercises/concurrency/dining-philosophers-async.md msgid "" "```toml\n" "[package]\n" @@ -17035,22 +18954,22 @@ msgid "" "edition = \"2021\"\n" "\n" "[dependencies]\n" -"tokio = {version = \"1.26.0\", features = [\"sync\", \"time\", \"macros\", " -"\"rt-multi-thread\"]}\n" +"tokio = { version = \"1.26.0\", features = [\"sync\", \"time\", \"macros\", " +"\"rt-multi-thread\"] }\n" "```" msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md:72 +#: src/exercises/concurrency/dining-philosophers-async.md 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? " +#: src/exercises/concurrency/dining-philosophers-async.md +msgid "Can you make your implementation single-threaded?" msgstr "" -#: src/exercises/concurrency/chat-app.md:3 +#: src/exercises/concurrency/chat-app.md 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 " @@ -17059,23 +18978,23 @@ msgid "" "that it receives to all the clients." msgstr "" -#: src/exercises/concurrency/chat-app.md:9 +#: src/exercises/concurrency/chat-app.md msgid "" "For this, we use [a broadcast channel](https://docs.rs/tokio/latest/tokio/" "sync/broadcast/fn.channel.html) on the server, and [`tokio_websockets`]" -"(https://docs.rs/tokio-websockets/0.4.0/tokio_websockets/) for the " -"communication between the client and the server." +"(https://docs.rs/tokio-websockets/) for the communication between the client " +"and the server." msgstr "" -#: src/exercises/concurrency/chat-app.md:13 +#: src/exercises/concurrency/chat-app.md msgid "Create a new Cargo project and add the following dependencies:" msgstr "" -#: src/exercises/concurrency/chat-app.md:15 +#: src/exercises/concurrency/chat-app.md msgid "_Cargo.toml_:" msgstr "" -#: src/exercises/concurrency/chat-app.md:19 +#: src/exercises/concurrency/chat-app.md msgid "" "```toml\n" "[package]\n" @@ -17084,58 +19003,57 @@ msgid "" "edition = \"2021\"\n" "\n" "[dependencies]\n" -"futures-util = { version = \"0.3.28\", features = [\"sink\"] }\n" -"http = \"0.2.9\"\n" +"futures-util = { version = \"0.3.30\", features = [\"sink\"] }\n" +"http = \"1.0.0\"\n" "tokio = { version = \"1.28.1\", features = [\"full\"] }\n" -"tokio-websockets = { version = \"0.4.0\", features = [\"client\", " +"tokio-websockets = { version = \"0.5.1\", features = [\"client\", " "\"fastrand\", \"server\", \"sha1_smol\"] }\n" "```" msgstr "" -#: src/exercises/concurrency/chat-app.md:32 +#: src/exercises/concurrency/chat-app.md msgid "The required APIs" msgstr "" -#: src/exercises/concurrency/chat-app.md:33 +#: src/exercises/concurrency/chat-app.md msgid "" "You are going to need the following functions from `tokio` and " -"[`tokio_websockets`](https://docs.rs/tokio-websockets/0.4.0/" -"tokio_websockets/). Spend a few minutes to familiarize yourself with the " -"API. " +"[`tokio_websockets`](https://docs.rs/tokio-websockets/). Spend a few minutes " +"to familiarize yourself with the API." msgstr "" -#: src/exercises/concurrency/chat-app.md:37 +#: src/exercises/concurrency/chat-app.md msgid "" "[StreamExt::next()](https://docs.rs/futures-util/0.3.28/futures_util/stream/" -"trait.StreamExt.html#method.next) implemented by `WebsocketStream`: for " +"trait.StreamExt.html#method.next) implemented by `WebSocketStream`: for " "asynchronously reading messages from a Websocket Stream." msgstr "" -#: src/exercises/concurrency/chat-app.md:39 +#: src/exercises/concurrency/chat-app.md msgid "" "[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" -"trait.SinkExt.html#method.send) implemented by `WebsocketStream`: for " +"trait.SinkExt.html#method.send) implemented by `WebSocketStream`: for " "asynchronously sending messages on a Websocket Stream." msgstr "" -#: src/exercises/concurrency/chat-app.md:41 +#: src/exercises/concurrency/chat-app.md 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 +#: src/exercises/concurrency/chat-app.md 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 +#: src/exercises/concurrency/chat-app.md msgid "Two binaries" msgstr "" -#: src/exercises/concurrency/chat-app.md:48 +#: src/exercises/concurrency/chat-app.md 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 " @@ -17143,123 +19061,83 @@ msgid "" "but we are going to put them in a single Cargo project with two binaries. " "For this to work, the client and the server code should go under `src/bin` " "(see the [documentation](https://doc.rust-lang.org/cargo/reference/cargo-" -"targets.html#binaries)). " +"targets.html#binaries))." msgstr "" -#: src/exercises/concurrency/chat-app.md:55 +#: src/exercises/concurrency/chat-app.md msgid "" "Copy the following server and client code into `src/bin/server.rs` and `src/" "bin/client.rs`, respectively. Your task is to complete these files as " -"described below. " +"described below." msgstr "" -#: src/exercises/concurrency/chat-app.md:59 -#: src/exercises/concurrency/solutions-afternoon.md:99 +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "_src/bin/server.rs_:" msgstr "" -#: src/exercises/concurrency/chat-app.md:63 -msgid "" -"```rust,compile_fail\n" -"use futures_util::sink::SinkExt;\n" -"use futures_util::stream::StreamExt;\n" -"use std::error::Error;\n" -"use std::net::SocketAddr;\n" -"use tokio::net::{TcpListener, TcpStream};\n" -"use tokio::sync::broadcast::{channel, Sender};\n" -"use tokio_websockets::{Message, ServerBuilder, WebsocketStream};\n" -"\n" -"async fn handle_connection(\n" -" addr: SocketAddr,\n" -" mut ws_stream: WebsocketStream,\n" -" bcast_tx: Sender,\n" -") -> Result<(), Box> {\n" -"\n" -" // TODO: For a hint, see the description of the task below.\n" -"\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), Box> {\n" -" let (bcast_tx, _) = channel(16);\n" -"\n" -" let listener = TcpListener::bind(\"127.0.0.1:2000\").await?;\n" -" println!(\"listening on port 2000\");\n" -"\n" -" loop {\n" -" let (socket, addr) = listener.accept().await?;\n" -" println!(\"New connection from {addr:?}\");\n" -" let bcast_tx = bcast_tx.clone();\n" -" tokio::spawn(async move {\n" -" // Wrap the raw TCP stream into a websocket.\n" -" let ws_stream = ServerBuilder::new().accept(socket).await?;\n" -"\n" -" handle_connection(addr, ws_stream, bcast_tx).await\n" -" });\n" -" }\n" -"}\n" -"```" +#: src/exercises/concurrency/chat-app.md +msgid "// TODO: For a hint, see the description of the task below.\n" +msgstr "" + +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"127.0.0.1:2000\"" msgstr "" -#: src/exercises/concurrency/chat-app.md:103 -#: src/exercises/concurrency/solutions-afternoon.md:166 +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"listening on port 2000\"" +msgstr "" + +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"New connection from {addr:?}\"" +msgstr "" + +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Wrap the raw TCP stream into a websocket.\n" +msgstr "" + +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "_src/bin/client.rs_:" msgstr "" -#: src/exercises/concurrency/chat-app.md:107 -msgid "" -"```rust,compile_fail\n" -"use futures_util::stream::StreamExt;\n" -"use futures_util::SinkExt;\n" -"use http::Uri;\n" -"use tokio::io::{AsyncBufReadExt, BufReader};\n" -"use tokio_websockets::{ClientBuilder, Message};\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), tokio_websockets::Error> {\n" -" let (mut ws_stream, _) =\n" -" ClientBuilder::from_uri(Uri::from_static(\"ws://127.0.0.1:2000\"))\n" -" .connect()\n" -" .await?;\n" -"\n" -" let stdin = tokio::io::stdin();\n" -" let mut stdin = BufReader::new(stdin).lines();\n" -"\n" -"\n" -" // TODO: For a hint, see the description of the task below.\n" -"\n" -"}\n" -"```" +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"ws://127.0.0.1:2000\"" msgstr "" -#: src/exercises/concurrency/chat-app.md:130 +#: src/exercises/concurrency/chat-app.md msgid "Running the binaries" msgstr "" -#: src/exercises/concurrency/chat-app.md:131 +#: src/exercises/concurrency/chat-app.md msgid "Run the server with:" msgstr "" -#: src/exercises/concurrency/chat-app.md:137 +#: src/exercises/concurrency/chat-app.md msgid "and the client with:" msgstr "" -#: src/exercises/concurrency/chat-app.md:145 +#: src/exercises/concurrency/chat-app.md msgid "Implement the `handle_connection` function in `src/bin/server.rs`." msgstr "" -#: src/exercises/concurrency/chat-app.md:146 +#: src/exercises/concurrency/chat-app.md 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 +#: src/exercises/concurrency/chat-app.md msgid "Complete the main function in `src/bin/client.rs`." msgstr "" -#: src/exercises/concurrency/chat-app.md:150 +#: src/exercises/concurrency/chat-app.md msgid "" "Hint: As before, use `tokio::select!` in a continuous loop for concurrently " "performing two tasks: (1) reading user messages from standard input and " @@ -17267,19 +19145,79 @@ msgid "" "displaying them for the user." msgstr "" -#: src/exercises/concurrency/chat-app.md:154 +#: src/exercises/concurrency/chat-app.md 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 +#: src/exercises/concurrency/solutions-afternoon.md +msgid "Concurrency Afternoon Exercise" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "([back to exercise](dining-philosophers-async.md))" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +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 +msgid "// The locks are dropped here\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +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 +msgid "// tx is dropped here, so we don't need to explicitly drop it later\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Here is a thought: {thought}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "([back to exercise](chat-app.md))" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"Welcome to chat! Type a message\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +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 +msgid "\"From client {addr:?} {text:?}\"" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "// Continuous loop for concurrently sending and receiving messages.\n" +msgstr "" + +#: src/exercises/concurrency/solutions-afternoon.md +msgid "\"From server: {}\"" +msgstr "" + +#: src/thanks.md msgid "" "_Thank you for taking Comprehensive Rust 🦀!_ We hope you enjoyed it and " "that it was useful." msgstr "" -#: src/thanks.md:6 +#: src/thanks.md 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, " @@ -17287,2662 +19225,1021 @@ msgid "" "comprehensive-rust/discussions). We would love to hear from you." msgstr "" -#: src/glossary.md:3 +#: src/glossary.md msgid "" "The following is a glossary which aims to give a short definition of many " "Rust terms. For translations, this also serves to connect the term back to " "the English original." msgstr "" -#: src/glossary.md:30 +#: src/glossary.md msgid "" "allocate: \n" "Dynamic memory allocation on [the heap](memory-management/stack-vs-heap.md)." msgstr "" -#: src/glossary.md:32 -msgid "argument:" +#: src/glossary.md +msgid "" +"argument: \n" +"Information that is passed into a function or method." msgstr "" -#: src/glossary.md:33 +#: src/glossary.md msgid "" "Bare-metal Rust: \n" "Low-level Rust development, often deployed to a system without an operating " "system. See [Bare-metal Rust](bare-metal.md)." msgstr "" -#: src/glossary.md:36 +#: src/glossary.md msgid "" "block: \n" "See [Blocks](control-flow/blocks.md) and _scope_." msgstr "" -#: src/glossary.md:38 +#: src/glossary.md msgid "" "borrow: \n" "See [Borrowing](ownership/borrowing.md)." msgstr "" -#: src/glossary.md:40 +#: src/glossary.md msgid "" "borrow checker: \n" "The part of the Rust compiler which checks that all borrows are valid." msgstr "" -#: src/glossary.md:42 +#: src/glossary.md msgid "" "brace: \n" "`{` and `}`. Also called _curly brace_, they delimit _blocks_." msgstr "" -#: src/glossary.md:44 -msgid "build:" -msgstr "" - -#: src/glossary.md:45 -msgid "call:" -msgstr "" - -#: src/glossary.md:46 -msgid "" -"channel: \n" -"Used to safely pass messages [between threads](concurrency/channels.md)." -msgstr "" - -#: src/glossary.md:48 -msgid "" -"Comprehensive Rust 🦀: \n" -"The courses here are jointly called Comprehensive Rust 🦀." -msgstr "" - -#: src/glossary.md:50 -msgid "concurrency:" -msgstr "eşzamanlılık:" - -#: src/glossary.md:51 -msgid "" -"Concurrency in Rust: \n" -"See [Concurrency in Rust](concurrency.md)." -msgstr "" - -#: src/glossary.md:53 -msgid "constant:" -msgstr "" - -#: src/glossary.md:54 -msgid "control flow:" -msgstr "kontrol akışı:" - -#: src/glossary.md:55 -msgid "crash:" -msgstr "" - -#: src/glossary.md:56 -msgid "enumeration:" -msgstr "numaralandırma:" - -#: src/glossary.md:57 -msgid "error:" -msgstr "" - -#: src/glossary.md:58 -msgid "error handling:" -msgstr "hata işleme:" - -#: src/glossary.md:59 -msgid "exercise:" -msgstr "egzersiz:" - -#: src/glossary.md:60 -msgid "function:" -msgstr "fonksiyon:" - -#: src/glossary.md:61 -msgid "garbage collector:" -msgstr "çöp toplama:" - -#: src/glossary.md:62 -msgid "generics:" -msgstr "jenerikler:" - -#: src/glossary.md:63 -msgid "immutable:" -msgstr "" - -#: src/glossary.md:64 -msgid "integration test:" -msgstr "entegrasyon testi:" - -#: src/glossary.md:65 -msgid "keyword:" -msgstr "" - -#: src/glossary.md:66 -msgid "library:" -msgstr "kütüphane:" - -#: src/glossary.md:67 -msgid "macro:" -msgstr "" - -#: src/glossary.md:68 -msgid "main function:" -msgstr "main fonksiyonu:" - -#: src/glossary.md:69 -msgid "match:" -msgstr "" - -#: src/glossary.md:70 -msgid "memory leak:" -msgstr "" - -#: src/glossary.md:71 -msgid "method:" -msgstr "metot:" - -#: src/glossary.md:72 -msgid "module:" -msgstr "modül:" - -#: src/glossary.md:73 -msgid "move:" -msgstr "" - -#: src/glossary.md:74 -msgid "mutable:" -msgstr "" - -#: src/glossary.md:75 -msgid "ownership:" -msgstr "sahiplik:" - -#: src/glossary.md:76 -msgid "panic:" -msgstr "panik:" - -#: src/glossary.md:77 -msgid "parameter:" -msgstr "" - -#: src/glossary.md:78 -msgid "pattern:" -msgstr "" - -#: src/glossary.md:79 -msgid "payload:" -msgstr "" - -#: src/glossary.md:80 -msgid "program:" -msgstr "" - -#: src/glossary.md:81 -msgid "programming language:" -msgstr "" - -#: src/glossary.md:82 -msgid "receiver:" -msgstr "alıcı:" - -#: src/glossary.md:83 -msgid "reference counting:" -msgstr "" - -#: src/glossary.md:84 -msgid "return:" -msgstr "" - -#: src/glossary.md:85 -msgid "Rust:" -msgstr "Rust:" - -#: src/glossary.md:86 +#: src/glossary.md msgid "" -"Rust Fundamentals: \n" -"Days 1 to 3 of this course." +"build: \n" +"The process of converting source code into executable code or a usable " +"program." msgstr "" -#: src/glossary.md:88 +#: src/glossary.md msgid "" -"Rust in Android: \n" -"See [Rust in Android](android.md)." +"call: \n" +"To invoke or execute a function or method." msgstr "" -#: src/glossary.md:90 -msgid "safe:" +#: src/glossary.md +msgid "" +"channel: \n" +"Used to safely pass messages [between threads](concurrency/channels.md)." msgstr "" -#: src/glossary.md:91 -msgid "scope:" +#: src/glossary.md +msgid "" +"Comprehensive Rust 🦀: \n" +"The courses here are jointly called Comprehensive Rust 🦀." msgstr "" -#: src/glossary.md:92 -msgid "standard library:" -msgstr "standart kütüphane:" - -#: src/glossary.md:93 -msgid "static:" +#: src/glossary.md +msgid "" +"concurrency: \n" +"The execution of multiple tasks or processes at the same time." msgstr "" -#: src/glossary.md:94 -msgid "string:" -msgstr "string:" - -#: src/glossary.md:95 -msgid "struct:" -msgstr "yapı:" - -#: src/glossary.md:96 -msgid "test:" +#: src/glossary.md +msgid "" +"Concurrency in Rust: \n" +"See [Concurrency in Rust](concurrency.md)." msgstr "" -#: src/glossary.md:97 -msgid "thread:" -msgstr "iş parçacığı:" - -#: src/glossary.md:98 -msgid "thread safety:" +#: src/glossary.md +msgid "" +"constant: \n" +"A value that does not change during the execution of a program." msgstr "" -#: src/glossary.md:99 -msgid "trait:" -msgstr "özellik (trait):" - -#: src/glossary.md:100 -msgid "type:" +#: src/glossary.md +msgid "" +"control flow: \n" +"The order in which the individual statements or instructions are executed in " +"a program." msgstr "" -#: src/glossary.md:101 -msgid "type inference:" -msgstr "tür çıkarımı:" - -#: src/glossary.md:102 -msgid "undefined behavior:" +#: src/glossary.md +msgid "" +"crash: \n" +"An unexpected and unhandled failure or termination of a program." msgstr "" -#: src/glossary.md:103 -msgid "union:" -msgstr "birlik (union):" - -#: src/glossary.md:104 -msgid "unit test:" -msgstr "birim testi:" - -#: src/glossary.md:105 -msgid "unsafe:" +#: src/glossary.md +msgid "" +"enumeration: \n" +"A data type that holds one of several named constants, possibly with an " +"associated tuple or struct." msgstr "" -#: src/glossary.md:106 -msgid "variable:\\" -msgstr "değişken:\\" - -#: src/other-resources.md:1 -msgid "Other Rust Resources" +#: src/glossary.md +msgid "" +"error: \n" +"An unexpected condition or result that deviates from the expected behavior." msgstr "" -#: src/other-resources.md:3 +#: src/glossary.md msgid "" -"The Rust community has created a wealth of high-quality and free resources " -"online." +"error handling: \n" +"The process of managing and responding to errors that occur during program " +"execution." msgstr "" -#: src/other-resources.md:6 -msgid "Official Documentation" +#: src/glossary.md +msgid "" +"exercise: \n" +"A task or problem designed to practice and test programming skills." msgstr "" -#: src/other-resources.md:8 -msgid "The Rust project hosts many resources. These cover Rust in general:" +#: src/glossary.md +msgid "" +"function: \n" +"A reusable block of code that performs a specific task." msgstr "" -#: src/other-resources.md:10 +#: src/glossary.md 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." +"garbage collector: \n" +"A mechanism that automatically frees up memory occupied by objects that are " +"no longer in use." msgstr "" -#: src/other-resources.md:13 +#: src/glossary.md 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." +"generics: \n" +"A feature that allows writing code with placeholders for types, enabling " +"code reuse with different data types." msgstr "" -#: src/other-resources.md:17 +#: src/glossary.md msgid "" -"[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation " -"of the standard library for Rust." +"immutable: \n" +"Unable to be changed after creation." msgstr "" -#: src/other-resources.md:19 +#: src/glossary.md msgid "" -"[The Rust Reference](https://doc.rust-lang.org/reference/): an incomplete " -"book which describes the Rust grammar and memory model." +"integration test: \n" +"A type of test that verifies the interactions between different parts or " +"components of a system." msgstr "" -#: src/other-resources.md:22 -msgid "More specialized guides hosted on the official Rust site:" +#: src/glossary.md +msgid "" +"keyword: \n" +"A reserved word in a programming language that has a specific meaning and " +"cannot be used as an identifier." msgstr "" -#: src/other-resources.md:24 +#: src/glossary.md msgid "" -"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " -"including working with raw pointers and interfacing with other languages " -"(FFI)." +"library: \n" +"A collection of precompiled routines or code that can be used by programs." msgstr "" -#: src/other-resources.md:27 +#: src/glossary.md 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." +"macro: \n" +"Rust macros can be recognized by a `!` in the name. Macros are used when " +"normal functions are not enough. A typical example is `format!`, which takes " +"a variable number of arguments, which isn't supported by Rust functions." msgstr "" -#: src/other-resources.md:30 +#: src/glossary.md 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." +"`main` function: \n" +"Rust programs start executing with the `main` function." msgstr "" -#: src/other-resources.md:33 -msgid "Unofficial Learning Material" +#: src/glossary.md +msgid "" +"match: \n" +"A control flow construct in Rust that allows for pattern matching on the " +"value of an expression." msgstr "" -#: src/other-resources.md:35 -msgid "A small selection of other guides and tutorial for Rust:" +#: src/glossary.md +msgid "" +"memory leak: \n" +"A situation where a program fails to release memory that is no longer " +"needed, leading to a gradual increase in memory usage." msgstr "" -#: src/other-resources.md:37 +#: src/glossary.md msgid "" -"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust " -"from the perspective of low-level C programmers." +"method: \n" +"A function associated with an object or a type in Rust." msgstr "" -#: src/other-resources.md:39 +#: src/glossary.md 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." +"module: \n" +"A namespace that contains definitions, such as functions, types, or traits, " +"to organize code in Rust." msgstr "" -#: src/other-resources.md:42 +#: src/glossary.md 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." +"move: \n" +"The transfer of ownership of a value from one variable to another in Rust." msgstr "" -#: src/other-resources.md:45 +#: src/glossary.md msgid "" -"[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " -"you learn Rust." +"mutable: \n" +"A property in Rust that allows variables to be modified after they have been " +"declared." msgstr "" -#: src/other-resources.md:47 +#: src/glossary.md 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." +"ownership: \n" +"The concept in Rust that defines which part of the code is responsible for " +"managing the memory associated with a value." msgstr "" -#: src/other-resources.md:52 +#: src/glossary.md 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." +"panic: \n" +"An unrecoverable error condition in Rust that results in the termination of " +"the program." msgstr "" -#: src/other-resources.md:58 +#: src/glossary.md 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." +"parameter: \n" +"A value that is passed into a function or method when it is called." msgstr "" -#: src/other-resources.md:63 +#: src/glossary.md msgid "" -"Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " -"for even more Rust books." +"pattern: \n" +"A combination of values, literals, or structures that can be matched against " +"an expression in Rust." msgstr "" -#: src/credits.md:3 +#: src/glossary.md 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." +"payload: \n" +"The data or information carried by a message, event, or data structure." msgstr "" -#: src/credits.md:7 +#: src/glossary.md 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." +"program: \n" +"A set of instructions that a computer can execute to perform a specific task " +"or solve a particular problem." msgstr "" -#: src/credits.md:12 -msgid "Rust by Example" +#: src/glossary.md +msgid "" +"programming language: \n" +"A formal system used to communicate instructions to a computer, such as Rust." msgstr "" -#: src/credits.md:14 +#: src/glossary.md 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." +"receiver: \n" +"The first parameter in a Rust method that represents the instance on which " +"the method is called." msgstr "" -#: src/credits.md:19 -msgid "Rust on Exercism" +#: src/glossary.md +msgid "" +"reference counting: \n" +"A memory management technique in which the number of references to an object " +"is tracked, and the object is deallocated when the count reaches zero." msgstr "" -#: src/credits.md:21 +#: src/glossary.md 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." +"return: \n" +"A keyword in Rust used to indicate the value to be returned from a function." msgstr "" -#: src/credits.md:26 -msgid "CXX" +#: src/glossary.md +msgid "" +"Rust: \n" +"A systems programming language that focuses on safety, performance, and " +"concurrency." msgstr "" -#: src/credits.md:28 +#: src/glossary.md 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." +"Rust Fundamentals: \n" +"Days 1 to 3 of this course." msgstr "" -#: src/credits.md:34 +#: src/glossary.md msgid "" -"The [Why Rust? - An Example in C](why-rust/an-example-in-c.md) section has " -"been taken from the presentation slides of [Colin Finck's Master Thesis]" -"(https://colinfinck.de/Master_Thesis_Colin_Finck.pdf). It has been " -"relicensed under the terms of the Apache 2.0 license for this course by the " -"author." +"Rust in Android: \n" +"See [Rust in Android](android.md)." msgstr "" -#: src/exercises/solutions.md:3 -msgid "You will find solutions to the exercises on the following pages." +#: src/glossary.md +msgid "" +"Rust in Chromium: \n" +"See [Rust in Chromium](chromium.md)." msgstr "" -#: src/exercises/solutions.md:5 +#: src/glossary.md 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." +"safe: \n" +"Refers to code that adheres to Rust's ownership and borrowing rules, " +"preventing memory-related errors." msgstr "" -#: src/exercises/day-1/solutions-morning.md:1 -msgid "Day 1 Morning Exercises" +#: src/glossary.md +msgid "" +"scope: \n" +"The region of a program where a variable is valid and can be used." msgstr "" -#: src/exercises/day-1/solutions-morning.md:5 -msgid "([back to exercise](for-loops.md))" +#: src/glossary.md +msgid "" +"standard library: \n" +"A collection of modules providing essential functionality in Rust." msgstr "" -#: src/exercises/day-1/solutions-morning.md:7 +#: src/glossary.md msgid "" -"```rust\n" -"fn transpose(matrix: [[i32; 3]; 3]) -> [[i32; 3]; 3] {\n" -" let mut result = [[0; 3]; 3];\n" -" for i in 0..3 {\n" -" for j in 0..3 {\n" -" result[j][i] = matrix[i][j];\n" -" }\n" -" }\n" -" return result;\n" -"}\n" -"\n" -"fn pretty_print(matrix: &[[i32; 3]; 3]) {\n" -" for row in matrix {\n" -" println!(\"{row:?}\");\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_transpose() {\n" -" let matrix = [\n" -" [101, 102, 103], //\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -" let transposed = transpose(matrix);\n" -" assert_eq!(\n" -" transposed,\n" -" [\n" -" [101, 201, 301], //\n" -" [102, 202, 302],\n" -" [103, 203, 303],\n" -" ]\n" -" );\n" -"}\n" -"\n" -"fn main() {\n" -" let matrix = [\n" -" [101, 102, 103], // <-- the comment makes rustfmt add a newline\n" -" [201, 202, 203],\n" -" [301, 302, 303],\n" -" ];\n" -"\n" -" println!(\"matrix:\");\n" -" pretty_print(&matrix);\n" -"\n" -" let transposed = transpose(matrix);\n" -" println!(\"transposed:\");\n" -" pretty_print(&transposed);\n" -"}\n" -"```" +"static: \n" +"A keyword in Rust used to define static variables or items with a `'static` " +"lifetime." msgstr "" -#: src/exercises/day-1/solutions-morning.md:57 -msgid "Bonus question" +#: src/glossary.md +msgid "" +"string: \n" +"A data type storing textual data. See [`String` vs `str`](basic-syntax/" +"string-slices.html) for more." msgstr "" -#: src/exercises/day-1/solutions-morning.md:59 +#: src/glossary.md 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." +"struct: \n" +"A composite data type in Rust that groups together variables of different " +"types under a single name." msgstr "" -#: src/exercises/day-1/solutions-morning.md:61 +#: src/glossary.md 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." +"test: \n" +"A Rust module containing functions that test the correctness of other " +"functions." msgstr "" -#: src/exercises/day-1/solutions-morning.md:63 +#: src/glossary.md 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." +"thread: \n" +"A separate sequence of execution in a program, allowing concurrent execution." msgstr "" -#: src/exercises/day-1/solutions-morning.md:65 +#: src/glossary.md msgid "" -"```rust\n" -"use std::convert::AsRef;\n" -"use std::fmt::Debug;\n" -"\n" -"fn pretty_print(matrix: Matrix)\n" -"where\n" -" T: Debug,\n" -" // A line references a slice of items\n" -" Line: AsRef<[T]>,\n" -" // A matrix references a slice of lines\n" -" Matrix: AsRef<[Line]>\n" -"{\n" -" for row in matrix.as_ref() {\n" -" println!(\"{:?}\", row.as_ref());\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" // &[&[i32]]\n" -" pretty_print(&[&[1, 2, 3], &[4, 5, 6], &[7, 8, 9]]);\n" -" // [[&str; 2]; 2]\n" -" pretty_print([[\"a\", \"b\"], [\"c\", \"d\"]]);\n" -" // Vec>\n" -" pretty_print(vec![vec![1, 2], vec![3, 4]]);\n" -"}\n" -"```" +"thread safety: \n" +"The property of a program that ensures correct behavior in a multithreaded " +"environment." msgstr "" -#: src/exercises/day-1/solutions-morning.md:92 +#: src/glossary.md 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." +"trait: \n" +"A collection of methods defined for an unknown type, providing a way to " +"achieve polymorphism in Rust." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:1 -msgid "Day 1 Afternoon Exercises" +#: src/glossary.md +msgid "" +"trait bound: \n" +"An abstraction where you can require types to implement some traits of your " +"interest." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:5 -msgid "([back to exercise](luhn.md))" +#: src/glossary.md +msgid "" +"tuple: \n" +"A composite data type that contains variables of different types. Tuple " +"fields have no names, and are accessed by their ordinal numbers." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:7 +#: src/glossary.md msgid "" -"```rust\n" -"pub fn luhn(cc_number: &str) -> bool {\n" -" let mut sum = 0;\n" -" let mut double = false;\n" -" let mut digit_seen = 0;\n" -"\n" -" for c in cc_number.chars().filter(|&f| f != ' ').rev() {\n" -" if let Some(digit) = c.to_digit(10) {\n" -" if double {\n" -" let double_digit = digit * 2;\n" -" sum += if double_digit > 9 {\n" -" double_digit - 9\n" -" } else {\n" -" double_digit\n" -" };\n" -" } else {\n" -" sum += digit;\n" -" }\n" -" double = !double;\n" -" digit_seen += 1;\n" -" } else {\n" -" return false;\n" -" }\n" -" }\n" -"\n" -" if digit_seen < 2 {\n" -" return false;\n" -" }\n" -"\n" -" sum % 10 == 0\n" -"}\n" -"\n" -"fn main() {\n" -" let cc_number = \"1234 5678 1234 5670\";\n" -" println!(\n" -" \"Is {cc_number} a valid credit card number? {}\",\n" -" if luhn(cc_number) { \"yes\" } else { \"no\" }\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_non_digit_cc_number() {\n" -" assert!(!luhn(\"foo\"));\n" -" assert!(!luhn(\"foo 0 0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_empty_cc_number() {\n" -" assert!(!luhn(\"\"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -" assert!(!luhn(\" \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_single_digit_cc_number() {\n" -" assert!(!luhn(\"0\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_two_digit_cc_number() {\n" -" assert!(luhn(\" 0 0 \"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_valid_cc_number() {\n" -" assert!(luhn(\"4263 9826 4026 9299\"));\n" -" assert!(luhn(\"4539 3195 0343 6467\"));\n" -" assert!(luhn(\"7992 7398 713\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_invalid_cc_number() {\n" -" assert!(!luhn(\"4223 9826 4026 9299\"));\n" -" assert!(!luhn(\"4539 3195 0343 6476\"));\n" -" assert!(!luhn(\"8273 1232 7352 0569\"));\n" -"}\n" -"```" +"type: \n" +"A classification that specifies which operations can be performed on values " +"of a particular kind in Rust." msgstr "" -#: src/exercises/day-1/solutions-afternoon.md:86 -msgid "Pattern matching" -msgstr "Desen eşleştirme" - -#: src/exercises/day-1/solutions-afternoon.md:88 +#: src/glossary.md msgid "" -"```rust\n" -"/// An operation to perform on two subexpressions.\n" -"#[derive(Debug)]\n" -"enum Operation {\n" -" Add,\n" -" Sub,\n" -" Mul,\n" -" Div,\n" -"}\n" -"\n" -"/// An expression, in tree form.\n" -"#[derive(Debug)]\n" -"enum Expression {\n" -" /// An operation on two subexpressions.\n" -" Op {\n" -" op: Operation,\n" -" left: Box,\n" -" right: Box,\n" -" },\n" -"\n" -" /// A literal value\n" -" Value(i64),\n" -"}\n" -"\n" -"/// The result of evaluating an expression.\n" -"#[derive(Debug, PartialEq, Eq)]\n" -"enum Res {\n" -" /// Evaluation was successful, with the given result.\n" -" Ok(i64),\n" -" /// Evaluation failed, with the given error message.\n" -" Err(String),\n" -"}\n" -"// Allow `Ok` and `Err` as shorthands for `Res::Ok` and `Res::Err`.\n" -"use Res::{Err, Ok};\n" -"\n" -"fn eval(e: Expression) -> Res {\n" -" match e {\n" -" Expression::Op { op, left, right } => {\n" -" let left = match eval(*left) {\n" -" Ok(v) => v,\n" -" Err(msg) => return Err(msg),\n" -" };\n" -" let right = match eval(*right) {\n" -" Ok(v) => v,\n" -" Err(msg) => return Err(msg),\n" -" };\n" -" Ok(match op {\n" -" Operation::Add => left + right,\n" -" Operation::Sub => left - right,\n" -" Operation::Mul => left * right,\n" -" Operation::Div => {\n" -" if right == 0 {\n" -" return Err(String::from(\"division by zero\"));\n" -" } else {\n" -" left / right\n" -" }\n" -" }\n" -" })\n" -" }\n" -" Expression::Value(v) => Ok(v),\n" -" }\n" -"}\n" -"\n" -"#[test]\n" -"fn test_value() {\n" -" assert_eq!(eval(Expression::Value(19)), Ok(19));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_sum() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(20)),\n" -" }),\n" -" Ok(30)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_recursion() {\n" -" let term1 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Value(10)),\n" -" right: Box::new(Expression::Value(9)),\n" -" };\n" -" let term2 = Expression::Op {\n" -" op: Operation::Mul,\n" -" left: Box::new(Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(3)),\n" -" right: Box::new(Expression::Value(4)),\n" -" }),\n" -" right: Box::new(Expression::Value(5)),\n" -" };\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Add,\n" -" left: Box::new(term1),\n" -" right: Box::new(term2),\n" -" }),\n" -" Ok(85)\n" -" );\n" -"}\n" -"\n" -"#[test]\n" -"fn test_error() {\n" -" assert_eq!(\n" -" eval(Expression::Op {\n" -" op: Operation::Div,\n" -" left: Box::new(Expression::Value(99)),\n" -" right: Box::new(Expression::Value(0)),\n" -" }),\n" -" Err(String::from(\"division by zero\"))\n" -" );\n" -"}\n" -"fn main() {\n" -" let expr = Expression::Op {\n" -" op: Operation::Sub,\n" -" left: Box::new(Expression::Value(20)),\n" -" right: Box::new(Expression::Value(10)),\n" -" };\n" -" println!(\"expr: {:?}\", expr);\n" -" println!(\"result: {:?}\", eval(expr));\n" -"}\n" -"```" +"type inference: \n" +"The ability of the Rust compiler to deduce the type of a variable or " +"expression." msgstr "" -#: src/exercises/day-2/solutions-morning.md:1 -msgid "Day 2 Morning Exercises" +#: src/glossary.md +msgid "" +"undefined behavior: \n" +"Actions or conditions in Rust that have no specified result, often leading " +"to unpredictable program behavior." msgstr "" -#: src/exercises/day-2/solutions-morning.md:3 -msgid "Designing a Library" -msgstr "Kütüphane Tasarlama" - -#: src/exercises/day-2/solutions-morning.md:5 -msgid "([back to exercise](book-library.md))" +#: src/glossary.md +msgid "" +"union: \n" +"A data type that can hold values of different types but only one at a time." msgstr "" -#: src/exercises/day-2/solutions-morning.md:7 +#: src/glossary.md msgid "" -"```rust\n" -"struct Library {\n" -" books: Vec,\n" -"}\n" -"\n" -"struct Book {\n" -" title: String,\n" -" year: u16,\n" -"}\n" -"\n" -"impl Book {\n" -" // This is a constructor, used below.\n" -" fn new(title: &str, year: u16) -> Book {\n" -" Book {\n" -" title: String::from(title),\n" -" year,\n" -" }\n" -" }\n" -"}\n" -"\n" -"// Implement the methods below. Notice how the `self` parameter\n" -"// changes type to indicate the method's required level of ownership\n" -"// over the object:\n" -"//\n" -"// - `&self` for shared read-only access,\n" -"// - `&mut self` for unique and mutable access,\n" -"// - `self` for unique access by value.\n" -"impl Library {\n" -"\n" -" fn new() -> Library {\n" -" Library { books: Vec::new() }\n" -" }\n" -"\n" -" fn len(&self) -> usize {\n" -" self.books.len()\n" -" }\n" -"\n" -" fn is_empty(&self) -> bool {\n" -" self.books.is_empty()\n" -" }\n" -"\n" -" fn add_book(&mut self, book: Book) {\n" -" self.books.push(book)\n" -" }\n" -"\n" -" fn print_books(&self) {\n" -" for book in &self.books {\n" -" println!(\"{}, published in {}\", book.title, book.year);\n" -" }\n" -" }\n" -"\n" -" fn oldest_book(&self) -> Option<&Book> {\n" -" // Using a closure and a built-in method:\n" -" // self.books.iter().min_by_key(|book| book.year)\n" -"\n" -" // Longer hand-written solution:\n" -" let mut oldest: Option<&Book> = None;\n" -" for book in self.books.iter() {\n" -" if oldest.is_none() || book.year < oldest.unwrap().year {\n" -" oldest = Some(book);\n" -" }\n" -" }\n" -"\n" -" oldest\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut library = Library::new();\n" -"\n" -" println!(\n" -" \"The library is empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -"\n" -" println!(\n" -" \"The library is no longer empty: library.is_empty() -> {}\",\n" -" library.is_empty()\n" -" );\n" -"\n" -" library.print_books();\n" -"\n" -" match library.oldest_book() {\n" -" Some(book) => println!(\"The oldest book is {}\", book.title),\n" -" None => println!(\"The library is empty!\"),\n" -" }\n" -"\n" -" println!(\"The library has {} books\", library.len());\n" -" library.print_books();\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_len() {\n" -" let mut library = Library::new();\n" -" assert_eq!(library.len(), 0);\n" -" assert!(library.is_empty());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" assert_eq!(library.len(), 2);\n" -" assert!(!library.is_empty());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_is_empty() {\n" -" let mut library = Library::new();\n" -" assert!(library.is_empty());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" assert!(!library.is_empty());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_print_books() {\n" -" let mut library = Library::new();\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" // We could try and capture stdout, but let us just call the\n" -" // method to start with.\n" -" library.print_books();\n" -"}\n" -"\n" -"#[test]\n" -"fn test_library_oldest_book() {\n" -" let mut library = Library::new();\n" -" assert!(library.oldest_book().is_none());\n" -"\n" -" library.add_book(Book::new(\"Lord of the Rings\", 1954));\n" -" assert_eq!(\n" -" library.oldest_book().map(|b| b.title.as_str()),\n" -" Some(\"Lord of the Rings\")\n" -" );\n" -"\n" -" library.add_book(Book::new(\"Alice's Adventures in Wonderland\", " -"1865));\n" -" assert_eq!(\n" -" library.oldest_book().map(|b| b.title.as_str()),\n" -" Some(\"Alice's Adventures in Wonderland\")\n" -" );\n" -"}\n" -"```" +"unit test: \n" +"Rust comes with built-in support for running small unit tests and larger " +"integration tests. See [Unit Tests](testing/unit-tests.html)." msgstr "" -#: src/exercises/day-2/solutions-morning.md:153 -msgid "([back to exercise](health-statistics.md))" +#: src/glossary.md +msgid "" +"unit type: \n" +"Type that holds no data, written as a tuple with no members." msgstr "" -#: src/exercises/day-2/solutions-morning.md:155 +#: src/glossary.md msgid "" -"```rust\n" -"pub struct User {\n" -" name: String,\n" -" age: u32,\n" -" height: f32,\n" -" visit_count: usize,\n" -" last_blood_pressure: Option<(u32, u32)>,\n" -"}\n" -"\n" -"pub struct Measurements {\n" -" height: f32,\n" -" blood_pressure: (u32, u32),\n" -"}\n" -"\n" -"pub struct HealthReport<'a> {\n" -" patient_name: &'a str,\n" -" visit_count: u32,\n" -" height_change: f32,\n" -" blood_pressure_change: Option<(i32, i32)>,\n" -"}\n" -"\n" -"impl User {\n" -" pub fn new(name: String, age: u32, height: f32) -> Self {\n" -" Self {\n" -" name,\n" -" age,\n" -" height,\n" -" visit_count: 0,\n" -" last_blood_pressure: None,\n" -" }\n" -" }\n" -"\n" -" pub fn name(&self) -> &str {\n" -" &self.name\n" -" }\n" -"\n" -" pub fn age(&self) -> u32 {\n" -" self.age\n" -" }\n" -"\n" -" pub fn height(&self) -> f32 {\n" -" self.height\n" -" }\n" -"\n" -" pub fn doctor_visits(&self) -> u32 {\n" -" self.visit_count as u32\n" -" }\n" -"\n" -" pub fn set_age(&mut self, new_age: u32) {\n" -" self.age = new_age\n" -" }\n" -"\n" -" pub fn set_height(&mut self, new_height: f32) {\n" -" self.height = new_height\n" -" }\n" -"\n" -" pub fn visit_doctor(&mut self, measurements: Measurements) -> " -"HealthReport {\n" -" self.visit_count += 1;\n" -" let bp = measurements.blood_pressure;\n" -" let report = HealthReport {\n" -" patient_name: &self.name,\n" -" visit_count: self.visit_count as u32,\n" -" height_change: measurements.height - self.height,\n" -" blood_pressure_change: match self.last_blood_pressure {\n" -" Some(lbp) => Some((\n" -" bp.0 as i32 - lbp.0 as i32,\n" -" bp.1 as i32 - lbp.1 as i32\n" -" )),\n" -" None => None,\n" -" }\n" -" };\n" -" self.height = measurements.height;\n" -" self.last_blood_pressure = Some(bp);\n" -" report\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" println!(\"I'm {} and my age is {}\", bob.name(), bob.age());\n" -"}\n" -"\n" -"#[test]\n" -"fn test_height() {\n" -" let bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.height(), 155.2);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_set_age() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.age(), 32);\n" -" bob.set_age(33);\n" -" assert_eq!(bob.age(), 33);\n" -"}\n" -"\n" -"#[test]\n" -"fn test_visit() {\n" -" let mut bob = User::new(String::from(\"Bob\"), 32, 155.2);\n" -" assert_eq!(bob.doctor_visits(), 0);\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (120, 80),\n" -" });\n" -" assert_eq!(report.patient_name, \"Bob\");\n" -" assert_eq!(report.visit_count, 1);\n" -" assert_eq!(report.blood_pressure_change, None);\n" -"\n" -" let report = bob.visit_doctor(Measurements {\n" -" height: 156.1,\n" -" blood_pressure: (115, 76),\n" -" });\n" -"\n" -" assert_eq!(report.visit_count, 2);\n" -" assert_eq!(report.blood_pressure_change, Some((-5, -4)));\n" -"}\n" -"```" +"unsafe: \n" +"The subset of Rust which allows you to trigger _undefined behavior_. See " +"[Unsafe Rust](unsafe.html)." msgstr "" -#: src/exercises/day-2/solutions-afternoon.md:1 -msgid "Day 2 Afternoon Exercises" +#: src/glossary.md +msgid "" +"variable: \n" +"A memory location storing data. Variables are valid in a _scope_." msgstr "" -#: src/exercises/day-2/solutions-afternoon.md:5 -msgid "([back to exercise](strings-iterators.md))" +#: src/other-resources.md +msgid "Other Rust Resources" msgstr "" -#: src/exercises/day-2/solutions-afternoon.md:7 +#: src/other-resources.md msgid "" -"```rust\n" -"pub fn prefix_matches(prefix: &str, request_path: &str) -> bool {\n" -"\n" -" let mut request_segments = request_path.split('/');\n" -"\n" -" for prefix_segment in prefix.split('/') {\n" -" let Some(request_segment) = request_segments.next() else {\n" -" return false;\n" -" };\n" -" if request_segment != prefix_segment && prefix_segment != \"*\" {\n" -" return false;\n" -" }\n" -" }\n" -" true\n" -"\n" -" // Alternatively, Iterator::zip() lets us iterate simultaneously over " -"prefix\n" -" // and request segments. The zip() iterator is finished as soon as one " -"of\n" -" // the source iterators is finished, but we need to iterate over all " -"request\n" -" // segments. A neat trick that makes zip() work is to use map() and " -"chain()\n" -" // to produce an iterator that returns Some(str) for each pattern " -"segments,\n" -" // and then returns None indefinitely.\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_without_wildcard() {\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/" -"abc-123\"));\n" -" assert!(prefix_matches(\"/v1/publishers\", \"/v1/publishers/abc/" -"books\"));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/publishersBooks\"));\n" -" assert!(!prefix_matches(\"/v1/publishers\", \"/v1/parent/" -"publishers\"));\n" -"}\n" -"\n" -"#[test]\n" -"fn test_matches_with_wildcard() {\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/bar/books\"\n" -" ));\n" -" assert!(prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/books/book1\"\n" -" ));\n" -"\n" -" assert!(!prefix_matches(\"/v1/publishers/*/books\", \"/v1/" -"publishers\"));\n" -" assert!(!prefix_matches(\n" -" \"/v1/publishers/*/books\",\n" -" \"/v1/publishers/foo/booksByAuthor\"\n" -" ));\n" -"}\n" -"\n" -"fn main() {}\n" -"```" +"The Rust community has created a wealth of high-quality and free resources " +"online." msgstr "" -#: src/exercises/day-3/solutions-morning.md:1 -msgid "Day 3 Morning Exercise" +#: src/other-resources.md +msgid "Official Documentation" msgstr "" -#: src/exercises/day-3/solutions-morning.md:5 -msgid "([back to exercise](simple-gui.md))" +#: src/other-resources.md +msgid "The Rust project hosts many resources. These cover Rust in general:" msgstr "" -#: src/exercises/day-3/solutions-morning.md:7 +#: src/other-resources.md msgid "" -"```rust\n" -"pub trait Widget {\n" -" /// Natural width of `self`.\n" -" fn width(&self) -> usize;\n" -"\n" -" /// Draw the widget into a buffer.\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write);\n" -"\n" -" /// Draw the widget on standard output.\n" -" fn draw(&self) {\n" -" let mut buffer = String::new();\n" -" self.draw_into(&mut buffer);\n" -" println!(\"{buffer}\");\n" -" }\n" -"}\n" -"\n" -"pub struct Label {\n" -" label: String,\n" -"}\n" -"\n" -"impl Label {\n" -" fn new(label: &str) -> Label {\n" -" Label {\n" -" label: label.to_owned(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Button {\n" -" label: Label,\n" -"}\n" -"\n" -"impl Button {\n" -" fn new(label: &str) -> Button {\n" -" Button {\n" -" label: Label::new(label),\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Window {\n" -" title: String,\n" -" widgets: Vec>,\n" -"}\n" -"\n" -"impl Window {\n" -" fn new(title: &str) -> Window {\n" -" Window {\n" -" title: title.to_owned(),\n" -" widgets: Vec::new(),\n" -" }\n" -" }\n" -"\n" -" fn add_widget(&mut self, widget: Box) {\n" -" self.widgets.push(widget);\n" -" }\n" -"\n" -" fn inner_width(&self) -> usize {\n" -" std::cmp::max(\n" -" self.title.chars().count(),\n" -" self.widgets.iter().map(|w| w.width()).max().unwrap_or(0),\n" -" )\n" -" }\n" -"}\n" -"\n" -"\n" -"impl Widget for Window {\n" -" fn width(&self) -> usize {\n" -" // Add 4 paddings for borders\n" -" self.inner_width() + 4\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" let mut inner = String::new();\n" -" for widget in &self.widgets {\n" -" widget.draw_into(&mut inner);\n" -" }\n" -"\n" -" let inner_width = self.inner_width();\n" -"\n" -" // TODO: after learning about error handling, you can change\n" -" // draw_into to return Result<(), std::fmt::Error>. Then use\n" -" // the ?-operator here instead of .unwrap().\n" -" writeln!(buffer, \"+-{:- usize {\n" -" self.label.width() + 8 // add a bit of padding\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" let width = self.width();\n" -" let mut label = String::new();\n" -" self.label.draw_into(&mut label);\n" -"\n" -" writeln!(buffer, \"+{:- usize {\n" -" self.label\n" -" .lines()\n" -" .map(|line| line.chars().count())\n" -" .max()\n" -" .unwrap_or(0)\n" -" }\n" -"\n" -" fn draw_into(&self, buffer: &mut dyn std::fmt::Write) {\n" -" writeln!(buffer, \"{}\", &self.label).unwrap();\n" -" }\n" -"}\n" -"\n" -"fn main() {\n" -" let mut window = Window::new(\"Rust GUI Demo 1.23\");\n" -" window.add_widget(Box::new(Label::new(\"This is a small text GUI demo." -"\")));\n" -" window.add_widget(Box::new(Button::new(\n" -" \"Click me!\"\n" -" )));\n" -" window.draw();\n" -"}\n" -"```" +"[The Rust Programming Language](https://doc.rust-lang.org/book/): the " +"canonical free book about Rust. Covers the language in detail and includes a " +"few projects for people to build." msgstr "" -#: src/exercises/day-3/solutions-morning.md:144 -msgid "([back to exercise](points-polygons.md))" +#: src/other-resources.md +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/exercises/day-3/solutions-morning.md:146 +#: src/other-resources.md msgid "" -"```rust\n" -"#[derive(Debug, Copy, Clone, PartialEq, Eq)]\n" -"pub struct Point {\n" -" x: i32,\n" -" y: i32,\n" -"}\n" -"\n" -"impl Point {\n" -" pub fn new(x: i32, y: i32) -> Point {\n" -" Point { x, y }\n" -" }\n" -"\n" -" pub fn magnitude(self) -> f64 {\n" -" f64::from(self.x.pow(2) + self.y.pow(2)).sqrt()\n" -" }\n" -"\n" -" pub fn dist(self, other: Point) -> f64 {\n" -" (self - other).magnitude()\n" -" }\n" -"}\n" -"\n" -"impl std::ops::Add for Point {\n" -" type Output = Self;\n" -"\n" -" fn add(self, other: Self) -> Self::Output {\n" -" Self {\n" -" x: self.x + other.x,\n" -" y: self.y + other.y,\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl std::ops::Sub for Point {\n" -" type Output = Self;\n" -"\n" -" fn sub(self, other: Self) -> Self::Output {\n" -" Self {\n" -" x: self.x - other.x,\n" -" y: self.y - other.y,\n" -" }\n" -" }\n" -"}\n" -"\n" -"pub struct Polygon {\n" -" points: Vec,\n" -"}\n" -"\n" -"impl Polygon {\n" -" pub fn new() -> Polygon {\n" -" Polygon { points: Vec::new() }\n" -" }\n" -"\n" -" pub fn add_point(&mut self, point: Point) {\n" -" self.points.push(point);\n" -" }\n" -"\n" -" pub fn left_most_point(&self) -> Option {\n" -" self.points.iter().min_by_key(|p| p.x).copied()\n" -" }\n" -"\n" -" pub fn iter(&self) -> impl Iterator {\n" -" self.points.iter()\n" -" }\n" -"\n" -" pub fn length(&self) -> f64 {\n" -" if self.points.is_empty() {\n" -" return 0.0;\n" -" }\n" -"\n" -" let mut result = 0.0;\n" -" let mut last_point = self.points[0];\n" -" for point in &self.points[1..] {\n" -" result += last_point.dist(*point);\n" -" last_point = *point;\n" -" }\n" -" result += last_point.dist(self.points[0]);\n" -" result\n" -" // Alternatively, Iterator::zip() lets us iterate over the points as " -"pairs\n" -" // but we need to pair each point with the next one, and the last " -"point\n" -" // with the first point. The zip() iterator is finished as soon as " -"one of \n" -" // the source iterators is finished, a neat trick is to combine " -"Iterator::cycle\n" -" // with Iterator::skip to create the second iterator for the zip and " -"using map \n" -" // and sum to calculate the total length.\n" -" }\n" -"}\n" -"\n" -"pub struct Circle {\n" -" center: Point,\n" -" radius: i32,\n" -"}\n" -"\n" -"impl Circle {\n" -" pub fn new(center: Point, radius: i32) -> Circle {\n" -" Circle { center, radius }\n" -" }\n" -"\n" -" pub fn circumference(&self) -> f64 {\n" -" 2.0 * std::f64::consts::PI * f64::from(self.radius)\n" -" }\n" -"\n" -" pub fn dist(&self, other: &Self) -> f64 {\n" -" self.center.dist(other.center)\n" -" }\n" -"}\n" -"\n" -"pub enum Shape {\n" -" Polygon(Polygon),\n" -" Circle(Circle),\n" -"}\n" -"\n" -"impl From for Shape {\n" -" fn from(poly: Polygon) -> Self {\n" -" Shape::Polygon(poly)\n" -" }\n" -"}\n" -"\n" -"impl From for Shape {\n" -" fn from(circle: Circle) -> Self {\n" -" Shape::Circle(circle)\n" -" }\n" -"}\n" -"\n" -"impl Shape {\n" -" pub fn perimeter(&self) -> f64 {\n" -" match self {\n" -" Shape::Polygon(poly) => poly.length(),\n" -" Shape::Circle(circle) => circle.circumference(),\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -"\n" -" fn round_two_digits(x: f64) -> f64 {\n" -" (x * 100.0).round() / 100.0\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_magnitude() {\n" -" let p1 = Point::new(12, 13);\n" -" assert_eq!(round_two_digits(p1.magnitude()), 17.69);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_dist() {\n" -" let p1 = Point::new(10, 10);\n" -" let p2 = Point::new(14, 13);\n" -" assert_eq!(round_two_digits(p1.dist(p2)), 5.00);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_point_add() {\n" -" let p1 = Point::new(16, 16);\n" -" let p2 = p1 + Point::new(-4, 3);\n" -" assert_eq!(p2, Point::new(12, 19));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_left_most_point() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -" assert_eq!(poly.left_most_point(), Some(p1));\n" -" }\n" -"\n" -" #[test]\n" -" fn test_polygon_iter() {\n" -" let p1 = Point::new(12, 13);\n" -" let p2 = Point::new(16, 16);\n" -"\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(p1);\n" -" poly.add_point(p2);\n" -"\n" -" let points = poly.iter().cloned().collect::>();\n" -" assert_eq!(points, vec![Point::new(12, 13), Point::new(16, 16)]);\n" -" }\n" -"\n" -" #[test]\n" -" fn test_shape_perimeters() {\n" -" let mut poly = Polygon::new();\n" -" poly.add_point(Point::new(12, 13));\n" -" poly.add_point(Point::new(17, 11));\n" -" poly.add_point(Point::new(16, 16));\n" -" let shapes = vec![\n" -" Shape::from(poly),\n" -" Shape::from(Circle::new(Point::new(10, 20), 5)),\n" -" ];\n" -" let perimeters = shapes\n" -" .iter()\n" -" .map(Shape::perimeter)\n" -" .map(round_two_digits)\n" -" .collect::>();\n" -" assert_eq!(perimeters, vec![15.48, 31.42]);\n" -" }\n" -"}\n" -"\n" -"fn main() {}\n" -"```" +"[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation " +"of the standard library for Rust." msgstr "" -#: src/exercises/day-3/solutions-afternoon.md:1 -msgid "Day 3 Afternoon Exercises" +#: src/other-resources.md +msgid "" +"[The Rust Reference](https://doc.rust-lang.org/reference/): an incomplete " +"book which describes the Rust grammar and memory model." msgstr "" -#: src/exercises/day-3/solutions-afternoon.md:5 -msgid "([back to exercise](safe-ffi-wrapper.md))" +#: src/other-resources.md +msgid "More specialized guides hosted on the official Rust site:" msgstr "" -#: src/exercises/day-3/solutions-afternoon.md:7 +#: src/other-resources.md msgid "" -"```rust\n" -"mod ffi {\n" -" use std::os::raw::{c_char, c_int};\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" use std::os::raw::{c_long, c_ulong, c_ushort, c_uchar};\n" -"\n" -" // Opaque type. See https://doc.rust-lang.org/nomicon/ffi.html.\n" -" #[repr(C)]\n" -" pub struct DIR {\n" -" _data: [u8; 0],\n" -" _marker: core::marker::PhantomData<(*mut u8, core::marker::" -"PhantomPinned)>,\n" -" }\n" -"\n" -" // Layout according to the Linux man page for readdir(3), where ino_t " -"and\n" -" // off_t are resolved according to the definitions in\n" -" // /usr/include/x86_64-linux-gnu/{sys/types.h, bits/typesizes.h}.\n" -" #[cfg(not(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_ino: c_ulong,\n" -" pub d_off: c_long,\n" -" pub d_reclen: c_ushort,\n" -" pub d_type: c_uchar,\n" -" pub d_name: [c_char; 256],\n" -" }\n" -"\n" -" // Layout according to the macOS man page for dir(5).\n" -" #[cfg(all(target_os = \"macos\"))]\n" -" #[repr(C)]\n" -" pub struct dirent {\n" -" pub d_fileno: u64,\n" -" pub d_seekoff: u64,\n" -" pub d_reclen: u16,\n" -" pub d_namlen: u16,\n" -" pub d_type: u8,\n" -" pub d_name: [c_char; 1024],\n" -" }\n" -"\n" -" extern \"C\" {\n" -" pub fn opendir(s: *const c_char) -> *mut DIR;\n" -"\n" -" #[cfg(not(all(target_os = \"macos\", target_arch = \"x86_64\")))]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" // See https://github.com/rust-lang/libc/issues/414 and the section " -"on\n" -" // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" -" //\n" -" // \"Platforms that existed before these updates were available\" " -"refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " -"PowerPC.\n" -" #[cfg(all(target_os = \"macos\", target_arch = \"x86_64\"))]\n" -" #[link_name = \"readdir$INODE64\"]\n" -" pub fn readdir(s: *mut DIR) -> *const dirent;\n" -"\n" -" pub fn closedir(s: *mut DIR) -> c_int;\n" -" }\n" -"}\n" -"\n" -"use std::ffi::{CStr, CString, OsStr, OsString};\n" -"use std::os::unix::ffi::OsStrExt;\n" -"\n" -"#[derive(Debug)]\n" -"struct DirectoryIterator {\n" -" path: CString,\n" -" dir: *mut ffi::DIR,\n" -"}\n" -"\n" -"impl DirectoryIterator {\n" -" fn new(path: &str) -> Result {\n" -" // Call opendir and return a Ok value if that worked,\n" -" // otherwise return Err with a message.\n" -" let path = CString::new(path).map_err(|err| format!(\"Invalid path: " -"{err}\"))?;\n" -" // SAFETY: path.as_ptr() cannot be NULL.\n" -" let dir = unsafe { ffi::opendir(path.as_ptr()) };\n" -" if dir.is_null() {\n" -" Err(format!(\"Could not open {:?}\", path))\n" -" } else {\n" -" Ok(DirectoryIterator { path, dir })\n" -" }\n" -" }\n" -"}\n" -"\n" -"impl Iterator for DirectoryIterator {\n" -" type Item = OsString;\n" -" fn next(&mut self) -> Option {\n" -" // Keep calling readdir until we get a NULL pointer back.\n" -" // SAFETY: self.dir is never NULL.\n" -" let dirent = unsafe { ffi::readdir(self.dir) };\n" -" if dirent.is_null() {\n" -" // We have reached the end of the directory.\n" -" return None;\n" -" }\n" -" // SAFETY: dirent is not NULL and dirent.d_name is NUL\n" -" // terminated.\n" -" let d_name = unsafe { CStr::from_ptr((*dirent).d_name.as_ptr()) };\n" -" let os_str = OsStr::from_bytes(d_name.to_bytes());\n" -" Some(os_str.to_owned())\n" -" }\n" -"}\n" -"\n" -"impl Drop for DirectoryIterator {\n" -" fn drop(&mut self) {\n" -" // Call closedir as needed.\n" -" if !self.dir.is_null() {\n" -" // SAFETY: self.dir is not NULL.\n" -" if unsafe { ffi::closedir(self.dir) } != 0 {\n" -" panic!(\"Could not close {:?}\", self.path);\n" -" }\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn main() -> Result<(), String> {\n" -" let iter = DirectoryIterator::new(\".\")?;\n" -" println!(\"files: {:#?}\", iter.collect::>());\n" -" Ok(())\n" -"}\n" -"\n" -"#[cfg(test)]\n" -"mod tests {\n" -" use super::*;\n" -" use std::error::Error;\n" -"\n" -" #[test]\n" -" fn test_nonexisting_directory() {\n" -" let iter = DirectoryIterator::new(\"no-such-directory\");\n" -" assert!(iter.is_err());\n" -" }\n" -"\n" -" #[test]\n" -" fn test_empty_directory() -> Result<(), Box> {\n" -" let tmp = tempfile::TempDir::new()?;\n" -" let iter = DirectoryIterator::new(\n" -" tmp.path().to_str().ok_or(\"Non UTF-8 character in path\")?,\n" -" )?;\n" -" let mut entries = iter.collect::>();\n" -" entries.sort();\n" -" assert_eq!(entries, &[\".\", \"..\"]);\n" -" Ok(())\n" -" }\n" -"\n" -" #[test]\n" -" fn test_nonempty_directory() -> Result<(), Box> {\n" -" let tmp = tempfile::TempDir::new()?;\n" -" std::fs::write(tmp.path().join(\"foo.txt\"), \"The Foo " -"Diaries\\n\")?;\n" -" std::fs::write(tmp.path().join(\"bar.png\"), \"\\n\")?;\n" -" std::fs::write(tmp.path().join(\"crab.rs\"), \"//! Crab\\n\")?;\n" -" let iter = DirectoryIterator::new(\n" -" tmp.path().to_str().ok_or(\"Non UTF-8 character in path\")?,\n" -" )?;\n" -" let mut entries = iter.collect::>();\n" -" entries.sort();\n" -" assert_eq!(entries, &[\".\", \"..\", \"bar.png\", \"crab.rs\", \"foo." -"txt\"]);\n" -" Ok(())\n" -" }\n" -"}\n" -"```" -msgstr "" - -#: src/exercises/bare-metal/solutions-morning.md:1 -msgid "Bare Metal Rust Morning Exercise" +"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " +"including working with raw pointers and interfacing with other languages " +"(FFI)." msgstr "" -#: src/exercises/bare-metal/solutions-morning.md:5 -msgid "([back to exercise](compass.md))" +#: src/other-resources.md +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/exercises/bare-metal/solutions-morning.md:7 +#: src/other-resources.md msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"extern crate panic_halt as _;\n" -"\n" -"use core::fmt::Write;\n" -"use cortex_m_rt::entry;\n" -"use core::cmp::{max, min};\n" -"use lsm303agr::{AccelOutputDataRate, Lsm303agr, MagOutputDataRate};\n" -"use microbit::display::blocking::Display;\n" -"use microbit::hal::prelude::*;\n" -"use microbit::hal::twim::Twim;\n" -"use microbit::hal::uarte::{Baudrate, Parity, Uarte};\n" -"use microbit::hal::Timer;\n" -"use microbit::pac::twim0::frequency::FREQUENCY_A;\n" -"use microbit::Board;\n" -"\n" -"const COMPASS_SCALE: i32 = 30000;\n" -"const ACCELEROMETER_SCALE: i32 = 700;\n" -"\n" -"#[entry]\n" -"fn main() -> ! {\n" -" let board = Board::take().unwrap();\n" -"\n" -" // Configure serial port.\n" -" let mut serial = Uarte::new(\n" -" board.UARTE0,\n" -" board.uart.into(),\n" -" Parity::EXCLUDED,\n" -" Baudrate::BAUD115200,\n" -" );\n" -"\n" -" // Set up the I2C controller and Inertial Measurement Unit.\n" -" writeln!(serial, \"Setting up IMU...\").unwrap();\n" -" let i2c = Twim::new(board.TWIM0, board.i2c_internal.into(), FREQUENCY_A::" -"K100);\n" -" let mut imu = Lsm303agr::new_with_i2c(i2c);\n" -" imu.init().unwrap();\n" -" imu.set_mag_odr(MagOutputDataRate::Hz50).unwrap();\n" -" imu.set_accel_odr(AccelOutputDataRate::Hz50).unwrap();\n" -" let mut imu = imu.into_mag_continuous().ok().unwrap();\n" -"\n" -" // Set up display and timer.\n" -" let mut timer = Timer::new(board.TIMER0);\n" -" let mut display = Display::new(board.display_pins);\n" -"\n" -" let mut mode = Mode::Compass;\n" -" let mut button_pressed = false;\n" -"\n" -" writeln!(serial, \"Ready.\").unwrap();\n" -"\n" -" loop {\n" -" // Read compass data and log it to the serial port.\n" -" while !(imu.mag_status().unwrap().xyz_new_data\n" -" && imu.accel_status().unwrap().xyz_new_data)\n" -" {}\n" -" let compass_reading = imu.mag_data().unwrap();\n" -" let accelerometer_reading = imu.accel_data().unwrap();\n" -" writeln!(\n" -" serial,\n" -" \"{},{},{}\\t{},{},{}\",\n" -" compass_reading.x,\n" -" compass_reading.y,\n" -" compass_reading.z,\n" -" accelerometer_reading.x,\n" -" accelerometer_reading.y,\n" -" accelerometer_reading.z,\n" -" )\n" -" .unwrap();\n" -"\n" -" let mut image = [[0; 5]; 5];\n" -" let (x, y) = match mode {\n" -" Mode::Compass => (\n" -" scale(-compass_reading.x, -COMPASS_SCALE, COMPASS_SCALE, 0, " -"4) as usize,\n" -" scale(compass_reading.y, -COMPASS_SCALE, COMPASS_SCALE, 0, " -"4) as usize,\n" -" ),\n" -" Mode::Accelerometer => (\n" -" scale(\n" -" accelerometer_reading.x,\n" -" -ACCELEROMETER_SCALE,\n" -" ACCELEROMETER_SCALE,\n" -" 0,\n" -" 4,\n" -" ) as usize,\n" -" scale(\n" -" -accelerometer_reading.y,\n" -" -ACCELEROMETER_SCALE,\n" -" ACCELEROMETER_SCALE,\n" -" 0,\n" -" 4,\n" -" ) as usize,\n" -" ),\n" -" };\n" -" image[y][x] = 255;\n" -" display.show(&mut timer, image, 100);\n" -"\n" -" // If button A is pressed, switch to the next mode and briefly blink " -"all LEDs on.\n" -" if board.buttons.button_a.is_low().unwrap() {\n" -" if !button_pressed {\n" -" mode = mode.next();\n" -" display.show(&mut timer, [[255; 5]; 5], 200);\n" -" }\n" -" button_pressed = true;\n" -" } else {\n" -" button_pressed = false;\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[derive(Copy, Clone, Debug, Eq, PartialEq)]\n" -"enum Mode {\n" -" Compass,\n" -" Accelerometer,\n" -"}\n" -"\n" -"impl Mode {\n" -" fn next(self) -> Self {\n" -" match self {\n" -" Self::Compass => Self::Accelerometer,\n" -" Self::Accelerometer => Self::Compass,\n" -" }\n" -" }\n" -"}\n" -"\n" -"fn scale(value: i32, min_in: i32, max_in: i32, min_out: i32, max_out: i32) -" -"> i32 {\n" -" let range_in = max_in - min_in;\n" -" let range_out = max_out - min_out;\n" -" cap(\n" -" min_out + range_out * (value - min_in) / range_in,\n" -" min_out,\n" -" max_out,\n" -" )\n" -"}\n" -"\n" -"fn cap(value: i32, min_value: i32, max_value: i32) -> i32 {\n" -" max(min_value, min(value, max_value))\n" -"}\n" -"```" +"[The Embedded Rust Book](https://doc.rust-lang.org/stable/embedded-book/): " +"an introduction to using Rust on embedded devices without an operating " +"system." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:5 -msgid "([back to exercise](rtc.md))" +#: src/other-resources.md +msgid "Unofficial Learning Material" msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:7 -msgid "_main.rs_:" +#: src/other-resources.md +msgid "A small selection of other guides and tutorial for Rust:" msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:9 +#: src/other-resources.md msgid "" -"```rust,compile_fail\n" -"#![no_main]\n" -"#![no_std]\n" -"\n" -"mod exceptions;\n" -"mod logger;\n" -"mod pl011;\n" -"mod pl031;\n" -"\n" -"use crate::pl031::Rtc;\n" -"use arm_gic::gicv3::{IntId, Trigger};\n" -"use arm_gic::{irq_enable, wfi};\n" -"use chrono::{TimeZone, Utc};\n" -"use core::hint::spin_loop;\n" -"use crate::pl011::Uart;\n" -"use arm_gic::gicv3::GicV3;\n" -"use core::panic::PanicInfo;\n" -"use log::{error, info, trace, LevelFilter};\n" -"use smccc::psci::system_off;\n" -"use smccc::Hvc;\n" -"\n" -"/// Base addresses of the GICv3.\n" -"const GICD_BASE_ADDRESS: *mut u64 = 0x800_0000 as _;\n" -"const GICR_BASE_ADDRESS: *mut u64 = 0x80A_0000 as _;\n" -"\n" -"/// Base address of the primary PL011 UART.\n" -"const PL011_BASE_ADDRESS: *mut u32 = 0x900_0000 as _;\n" -"\n" -"/// Base address of the PL031 RTC.\n" -"const PL031_BASE_ADDRESS: *mut u32 = 0x901_0000 as _;\n" -"/// The IRQ used by the PL031 RTC.\n" -"const PL031_IRQ: IntId = IntId::spi(2);\n" -"\n" -"#[no_mangle]\n" -"extern \"C\" fn main(x0: u64, x1: u64, x2: u64, x3: u64) {\n" -" // Safe because `PL011_BASE_ADDRESS` is the base address of a PL011 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let uart = unsafe { Uart::new(PL011_BASE_ADDRESS) };\n" -" logger::init(uart, LevelFilter::Trace).unwrap();\n" -"\n" -" info!(\"main({:#x}, {:#x}, {:#x}, {:#x})\", x0, x1, x2, x3);\n" -"\n" -" // Safe because `GICD_BASE_ADDRESS` and `GICR_BASE_ADDRESS` are the " -"base\n" -" // addresses of a GICv3 distributor and redistributor respectively, and\n" -" // nothing else accesses those address ranges.\n" -" let mut gic = unsafe { GicV3::new(GICD_BASE_ADDRESS, " -"GICR_BASE_ADDRESS) };\n" -" gic.setup();\n" -"\n" -" // Safe because `PL031_BASE_ADDRESS` is the base address of a PL031 " -"device,\n" -" // and nothing else accesses that address range.\n" -" let mut rtc = unsafe { Rtc::new(PL031_BASE_ADDRESS) };\n" -" let timestamp = rtc.read();\n" -" let time = Utc.timestamp_opt(timestamp.into(), 0).unwrap();\n" -" info!(\"RTC: {time}\");\n" -"\n" -" GicV3::set_priority_mask(0xff);\n" -" gic.set_interrupt_priority(PL031_IRQ, 0x80);\n" -" gic.set_trigger(PL031_IRQ, Trigger::Level);\n" -" irq_enable();\n" -" gic.enable_interrupt(PL031_IRQ, true);\n" -"\n" -" // Wait for 3 seconds, without interrupts.\n" -" let target = timestamp + 3;\n" -" rtc.set_match(target);\n" -" info!(\n" -" \"Waiting for {}\",\n" -" Utc.timestamp_opt(target.into(), 0).unwrap()\n" -" );\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" while !rtc.matched() {\n" -" spin_loop();\n" -" }\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" info!(\"Finished waiting\");\n" -"\n" -" // Wait another 3 seconds for an interrupt.\n" -" let target = timestamp + 6;\n" -" info!(\n" -" \"Waiting for {}\",\n" -" Utc.timestamp_opt(target.into(), 0).unwrap()\n" -" );\n" -" rtc.set_match(target);\n" -" rtc.clear_interrupt();\n" -" rtc.enable_interrupt(true);\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" while !rtc.interrupt_pending() {\n" -" wfi();\n" -" }\n" -" trace!(\n" -" \"matched={}, interrupt_pending={}\",\n" -" rtc.matched(),\n" -" rtc.interrupt_pending()\n" -" );\n" -" info!(\"Finished waiting\");\n" -"\n" -" system_off::().unwrap();\n" -"}\n" -"\n" -"#[panic_handler]\n" -"fn panic(info: &PanicInfo) -> ! {\n" -" error!(\"{info}\");\n" -" system_off::().unwrap();\n" -" loop {}\n" -"}\n" -"```" +"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust " +"from the perspective of low-level C programmers." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:127 -msgid "_pl031.rs_:" +#: src/other-resources.md +msgid "" +"[Rust for Embedded C Programmers](https://docs.opentitan.org/doc/ug/" +"rust_for_c/): covers Rust from the perspective of developers who write " +"firmware in C." msgstr "" -#: src/exercises/bare-metal/solutions-afternoon.md:129 +#: src/other-resources.md msgid "" -"```rust\n" -"use core::ptr::{addr_of, addr_of_mut};\n" -"\n" -"#[repr(C, align(4))]\n" -"struct Registers {\n" -" /// Data register\n" -" dr: u32,\n" -" /// Match register\n" -" mr: u32,\n" -" /// Load register\n" -" lr: u32,\n" -" /// Control register\n" -" cr: u8,\n" -" _reserved0: [u8; 3],\n" -" /// Interrupt Mask Set or Clear register\n" -" imsc: u8,\n" -" _reserved1: [u8; 3],\n" -" /// Raw Interrupt Status\n" -" ris: u8,\n" -" _reserved2: [u8; 3],\n" -" /// Masked Interrupt Status\n" -" mis: u8,\n" -" _reserved3: [u8; 3],\n" -" /// Interrupt Clear Register\n" -" icr: u8,\n" -" _reserved4: [u8; 3],\n" -"}\n" -"\n" -"/// Driver for a PL031 real-time clock.\n" -"#[derive(Debug)]\n" -"pub struct Rtc {\n" -" registers: *mut Registers,\n" -"}\n" -"\n" -"impl Rtc {\n" -" /// Constructs a new instance of the RTC driver for a PL031 device at " -"the\n" -" /// given base address.\n" -" ///\n" -" /// # Safety\n" -" ///\n" -" /// The given base address must point to the MMIO control registers of " -"a\n" -" /// PL031 device, which must be mapped into the address space of the " -"process\n" -" /// as device memory and not have any other aliases.\n" -" pub unsafe fn new(base_address: *mut u32) -> Self {\n" -" Self {\n" -" registers: base_address as *mut Registers,\n" -" }\n" -" }\n" -"\n" -" /// Reads the current RTC value.\n" -" pub fn read(&self) -> u32 {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of!((*self.registers).dr).read_volatile() }\n" -" }\n" -"\n" -" /// Writes a match value. When the RTC value matches this then an " -"interrupt\n" -" /// will be generated (if it is enabled).\n" -" pub fn set_match(&mut self, value: u32) {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).mr).write_volatile(value) }\n" -" }\n" -"\n" -" /// Returns whether the match register matches the RTC value, whether or " -"not\n" -" /// the interrupt is enabled.\n" -" pub fn matched(&self) -> bool {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" let ris = unsafe { addr_of!((*self.registers).ris)." -"read_volatile() };\n" -" (ris & 0x01) != 0\n" -" }\n" -"\n" -" /// Returns whether there is currently an interrupt pending.\n" -" ///\n" -" /// This should be true if and only if `matched` returns true and the\n" -" /// interrupt is masked.\n" -" pub fn interrupt_pending(&self) -> bool {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" let ris = unsafe { addr_of!((*self.registers).mis)." -"read_volatile() };\n" -" (ris & 0x01) != 0\n" -" }\n" -"\n" -" /// Sets or clears the interrupt mask.\n" -" ///\n" -" /// When the mask is true the interrupt is enabled; when it is false " -"the\n" -" /// interrupt is disabled.\n" -" pub fn enable_interrupt(&mut self, mask: bool) {\n" -" let imsc = if mask { 0x01 } else { 0x00 };\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).imsc)." -"write_volatile(imsc) }\n" -" }\n" -"\n" -" /// Clears a pending interrupt, if any.\n" -" pub fn clear_interrupt(&mut self) {\n" -" // Safe because we know that self.registers points to the control\n" -" // registers of a PL031 device which is appropriately mapped.\n" -" unsafe { addr_of_mut!((*self.registers).icr).write_volatile(0x01) }\n" -" }\n" -"}\n" -"\n" -"// Safe because it just contains a pointer to device memory, which can be\n" -"// accessed from any context.\n" -"unsafe impl Send for Rtc {}\n" -"```" +"[Rust for professionals](https://overexact.com/rust-for-professionals/): " +"covers the syntax of Rust using side-by-side comparisons with other " +"languages such as C, C++, Java, JavaScript, and Python." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:1 -msgid "Concurrency Morning Exercise" +#: src/other-resources.md +msgid "" +"[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " +"you learn Rust." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:5 -msgid "([back to exercise](dining-philosophers.md))" +#: src/other-resources.md +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/exercises/concurrency/solutions-morning.md:7 +#: src/other-resources.md msgid "" -"```rust\n" -"use std::sync::{mpsc, Arc, Mutex};\n" -"use std::thread;\n" -"use std::time::Duration;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" left_fork: Arc>,\n" -" right_fork: Arc>,\n" -" thoughts: mpsc::SyncSender,\n" -"}\n" -"\n" -"impl Philosopher {\n" -" fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))\n" -" .unwrap();\n" -" }\n" -"\n" -" fn eat(&self) {\n" -" println!(\"{} is trying to eat\", &self.name);\n" -" let left = self.left_fork.lock().unwrap();\n" -" let right = self.right_fork.lock().unwrap();\n" -"\n" -" println!(\"{} is eating...\", &self.name);\n" -" thread::sleep(Duration::from_millis(10));\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Hypatia\", \"Plato\", \"Aristotle\", \"Pythagoras\"];\n" -"\n" -"fn main() {\n" -" let (tx, rx) = mpsc::sync_channel(10);\n" -"\n" -" let forks = (0..PHILOSOPHERS.len())\n" -" .map(|_| Arc::new(Mutex::new(Fork)))\n" -" .collect::>();\n" -"\n" -" for i in 0..forks.len() {\n" -" let tx = tx.clone();\n" -" let mut left_fork = Arc::clone(&forks[i]);\n" -" let mut right_fork = Arc::clone(&forks[(i + 1) % forks.len()]);\n" -"\n" -" // To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" -" if i == forks.len() - 1 {\n" -" std::mem::swap(&mut left_fork, &mut right_fork);\n" -" }\n" -"\n" -" let philosopher = Philosopher {\n" -" name: PHILOSOPHERS[i].to_string(),\n" -" thoughts: tx,\n" -" left_fork,\n" -" right_fork,\n" -" };\n" -"\n" -" thread::spawn(move || {\n" -" for _ in 0..100 {\n" -" philosopher.eat();\n" -" philosopher.think();\n" -" }\n" -" });\n" -" }\n" -"\n" -" drop(tx);\n" -" for thought in rx {\n" -" println!(\"{thought}\");\n" -" }\n" -"}\n" -"```" +"[Beginner's Series to Rust](https://docs.microsoft.com/en-us/shows/beginners-" +"series-to-rust/) and [Take your first steps with Rust](https://docs." +"microsoft.com/en-us/learn/paths/rust-first-steps/): two Rust guides aimed at " +"new developers. The first is a set of 35 videos and the second is a set of " +"11 modules which covers Rust syntax and basic constructs." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:82 -msgid "Link Checker" +#: src/other-resources.md +msgid "" +"[Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial." +"github.io/too-many-lists/): in-depth exploration of Rust's memory management " +"rules, through implementing a few different types of list structures." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:84 -msgid "([back to exercise](link-checker.md))" +#: src/other-resources.md +msgid "" +"Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " +"for even more Rust books." msgstr "" -#: src/exercises/concurrency/solutions-morning.md:86 +#: src/credits.md msgid "" -"```rust,compile_fail\n" -"use std::{sync::Arc, sync::Mutex, sync::mpsc, thread};\n" -"\n" -"use reqwest::{blocking::Client, Url};\n" -"use scraper::{Html, Selector};\n" -"use thiserror::Error;\n" -"\n" -"#[derive(Error, Debug)]\n" -"enum Error {\n" -" #[error(\"request error: {0}\")]\n" -" ReqwestError(#[from] reqwest::Error),\n" -" #[error(\"bad http response: {0}\")]\n" -" BadResponse(String),\n" -"}\n" -"\n" -"#[derive(Debug)]\n" -"struct CrawlCommand {\n" -" url: Url,\n" -" extract_links: bool,\n" -"}\n" -"\n" -"fn visit_page(client: &Client, command: &CrawlCommand) -> Result, " -"Error> {\n" -" println!(\"Checking {:#}\", command.url);\n" -" let response = client.get(command.url.clone()).send()?;\n" -" if !response.status().is_success() {\n" -" return Err(Error::BadResponse(response.status().to_string()));\n" -" }\n" -"\n" -" let mut link_urls = Vec::new();\n" -" if !command.extract_links {\n" -" return Ok(link_urls);\n" -" }\n" -"\n" -" let base_url = response.url().to_owned();\n" -" let body_text = response.text()?;\n" -" let document = Html::parse_document(&body_text);\n" -"\n" -" let selector = Selector::parse(\"a\").unwrap();\n" -" let href_values = document\n" -" .select(&selector)\n" -" .filter_map(|element| element.value().attr(\"href\"));\n" -" for href in href_values {\n" -" match base_url.join(href) {\n" -" Ok(link_url) => {\n" -" link_urls.push(link_url);\n" -" }\n" -" Err(err) => {\n" -" println!(\"On {base_url:#}: ignored unparsable {href:?}: " -"{err}\");\n" -" }\n" -" }\n" -" }\n" -" Ok(link_urls)\n" -"}\n" -"\n" -"struct CrawlState {\n" -" domain: String,\n" -" visited_pages: std::collections::HashSet,\n" -"}\n" -"\n" -"impl CrawlState {\n" -" fn new(start_url: &Url) -> CrawlState {\n" -" let mut visited_pages = std::collections::HashSet::new();\n" -" visited_pages.insert(start_url.as_str().to_string());\n" -" CrawlState {\n" -" domain: start_url.domain().unwrap().to_string(),\n" -" visited_pages,\n" -" }\n" -" }\n" -"\n" -" /// Determine whether links within the given page should be extracted.\n" -" fn should_extract_links(&self, url: &Url) -> bool {\n" -" let Some(url_domain) = url.domain() else {\n" -" return false;\n" -" };\n" -" url_domain == self.domain\n" -" }\n" -"\n" -" /// Mark the given page as visited, returning false if it had already\n" -" /// been visited.\n" -" fn mark_visited(&mut self, url: &Url) -> bool {\n" -" self.visited_pages.insert(url.as_str().to_string())\n" -" }\n" -"}\n" -"\n" -"type CrawlResult = Result, (Url, Error)>;\n" -"fn spawn_crawler_threads(\n" -" command_receiver: mpsc::Receiver,\n" -" result_sender: mpsc::Sender,\n" -" thread_count: u32,\n" -") {\n" -" let command_receiver = Arc::new(Mutex::new(command_receiver));\n" -"\n" -" for _ in 0..thread_count {\n" -" let result_sender = result_sender.clone();\n" -" let command_receiver = command_receiver.clone();\n" -" thread::spawn(move || {\n" -" let client = Client::new();\n" -" loop {\n" -" let command_result = {\n" -" let receiver_guard = command_receiver.lock().unwrap();\n" -" receiver_guard.recv()\n" -" };\n" -" let Ok(crawl_command) = command_result else {\n" -" // The sender got dropped. No more commands coming in.\n" -" break;\n" -" };\n" -" let crawl_result = match visit_page(&client, &crawl_command) " -"{\n" -" Ok(link_urls) => Ok(link_urls),\n" -" Err(error) => Err((crawl_command.url, error)),\n" -" };\n" -" result_sender.send(crawl_result).unwrap();\n" -" }\n" -" });\n" -" }\n" -"}\n" -"\n" -"fn control_crawl(\n" -" start_url: Url,\n" -" command_sender: mpsc::Sender,\n" -" result_receiver: mpsc::Receiver,\n" -") -> Vec {\n" -" let mut crawl_state = CrawlState::new(&start_url);\n" -" let start_command = CrawlCommand { url: start_url, extract_links: " -"true };\n" -" command_sender.send(start_command).unwrap();\n" -" let mut pending_urls = 1;\n" -"\n" -" let mut bad_urls = Vec::new();\n" -" while pending_urls > 0 {\n" -" let crawl_result = result_receiver.recv().unwrap();\n" -" pending_urls -= 1;\n" -"\n" -" match crawl_result {\n" -" Ok(link_urls) => {\n" -" for url in link_urls {\n" -" if crawl_state.mark_visited(&url) {\n" -" let extract_links = crawl_state." -"should_extract_links(&url);\n" -" let crawl_command = CrawlCommand { url, " -"extract_links };\n" -" command_sender.send(crawl_command).unwrap();\n" -" pending_urls += 1;\n" -" }\n" -" }\n" -" }\n" -" Err((url, error)) => {\n" -" bad_urls.push(url);\n" -" println!(\"Got crawling error: {:#}\", error);\n" -" continue;\n" -" }\n" -" }\n" -" }\n" -" bad_urls\n" -"}\n" -"\n" -"fn check_links(start_url: Url) -> Vec {\n" -" let (result_sender, result_receiver) = mpsc::channel::();\n" -" let (command_sender, command_receiver) = mpsc::channel::" -"();\n" -" spawn_crawler_threads(command_receiver, result_sender, 16);\n" -" control_crawl(start_url, command_sender, result_receiver)\n" -"}\n" -"\n" -"fn main() {\n" -" let start_url = reqwest::Url::parse(\"https://www.google.org\")." -"unwrap();\n" -" let bad_urls = check_links(start_url);\n" -" println!(\"Bad URLs: {:#?}\", bad_urls);\n" -"}\n" -"```" +"The material here builds on top of the many great sources of Rust " +"documentation. See the page on [other resources](other-resources.md) for a " +"full list of useful resources." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:1 -msgid "Concurrency Afternoon Exercise" +#: src/credits.md +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/exercises/concurrency/solutions-afternoon.md:5 -msgid "([back to exercise](dining-philosophers-async.md))" +#: src/credits.md +msgid "Rust by Example" msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:7 +#: src/credits.md msgid "" -"```rust,compile_fail\n" -"use std::sync::Arc;\n" -"use tokio::time;\n" -"use tokio::sync::mpsc::{self, Sender};\n" -"use tokio::sync::Mutex;\n" -"\n" -"struct Fork;\n" -"\n" -"struct Philosopher {\n" -" name: String,\n" -" left_fork: Arc>,\n" -" right_fork: Arc>,\n" -" thoughts: Sender,\n" -"}\n" -"\n" -"impl Philosopher {\n" -" async fn think(&self) {\n" -" self.thoughts\n" -" .send(format!(\"Eureka! {} has a new idea!\", &self.name))." -"await\n" -" .unwrap();\n" -" }\n" -"\n" -" async fn eat(&self) {\n" -" // Pick up forks...\n" -" let _first_lock = self.left_fork.lock().await;\n" -" // Add a delay before picking the second fork to allow the " -"execution\n" -" // to transfer to another task\n" -" time::sleep(time::Duration::from_millis(1)).await;\n" -" let _second_lock = self.right_fork.lock().await;\n" -"\n" -" println!(\"{} is eating...\", &self.name);\n" -" time::sleep(time::Duration::from_millis(5)).await;\n" -"\n" -" // The locks are dropped here\n" -" }\n" -"}\n" -"\n" -"static PHILOSOPHERS: &[&str] =\n" -" &[\"Socrates\", \"Hypatia\", \"Plato\", \"Aristotle\", \"Pythagoras\"];\n" -"\n" -"#[tokio::main]\n" -"async fn main() {\n" -" // Create forks\n" -" let mut forks = vec![];\n" -" (0..PHILOSOPHERS.len()).for_each(|_| forks.push(Arc::new(Mutex::" -"new(Fork))));\n" -"\n" -" // Create philosophers\n" -" let (philosophers, mut rx) = {\n" -" let mut philosophers = vec![];\n" -" let (tx, rx) = mpsc::channel(10);\n" -" for (i, name) in PHILOSOPHERS.iter().enumerate() {\n" -" let left_fork = Arc::clone(&forks[i]);\n" -" let right_fork = Arc::clone(&forks[(i + 1) % PHILOSOPHERS." -"len()]);\n" -" // To avoid a deadlock, we have to break the symmetry\n" -" // somewhere. This will swap the forks without deinitializing\n" -" // either of them.\n" -" if i == 0 {\n" -" std::mem::swap(&mut left_fork, &mut right_fork);\n" -" }\n" -" philosophers.push(Philosopher {\n" -" name: name.to_string(),\n" -" left_fork,\n" -" right_fork,\n" -" thoughts: tx.clone(),\n" -" });\n" -" }\n" -" (philosophers, rx)\n" -" // tx is dropped here, so we don't need to explicitly drop it later\n" -" };\n" -"\n" -" // Make them think and eat\n" -" for phil in philosophers {\n" -" tokio::spawn(async move {\n" -" for _ in 0..100 {\n" -" phil.think().await;\n" -" phil.eat().await;\n" -" }\n" -" });\n" -"\n" -" }\n" -"\n" -" // Output their thoughts\n" -" while let Some(thought) = rx.recv().await {\n" -" println!(\"Here is a thought: {thought}\");\n" -" }\n" -"}\n" -"```" +"Some examples and exercises have been copied and adapted from [Rust by " +"Example](https://doc.rust-lang.org/rust-by-example/). Please see the " +"`third_party/rust-by-example/` directory for details, including the license " +"terms." msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:97 -msgid "([back to exercise](chat-app.md))" +#: src/credits.md +msgid "Rust on Exercism" msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:101 +#: src/credits.md msgid "" -"```rust,compile_fail\n" -"use futures_util::sink::SinkExt;\n" -"use futures_util::stream::StreamExt;\n" -"use std::error::Error;\n" -"use std::net::SocketAddr;\n" -"use tokio::net::{TcpListener, TcpStream};\n" -"use tokio::sync::broadcast::{channel, Sender};\n" -"use tokio_websockets::{Message, ServerBuilder, WebsocketStream};\n" -"\n" -"async fn handle_connection(\n" -" addr: SocketAddr,\n" -" mut ws_stream: WebsocketStream,\n" -" bcast_tx: Sender,\n" -") -> Result<(), Box> {\n" -"\n" -" ws_stream\n" -" .send(Message::text(\"Welcome to chat! Type a message\".into()))\n" -" .await?;\n" -" let mut bcast_rx = bcast_tx.subscribe();\n" -"\n" -" // A continuous loop for concurrently performing two tasks: (1) " -"receiving\n" -" // messages from `ws_stream` and broadcasting them, and (2) receiving\n" -" // messages on `bcast_rx` and sending them to the client.\n" -" loop {\n" -" tokio::select! {\n" -" incoming = ws_stream.next() => {\n" -" match incoming {\n" -" Some(Ok(msg)) => {\n" -" if let Some(text) = msg.as_text() {\n" -" println!(\"From client {addr:?} {text:?}\");\n" -" bcast_tx.send(text.into())?;\n" -" }\n" -" }\n" -" Some(Err(err)) => return Err(err.into()),\n" -" None => return Ok(()),\n" -" }\n" -" }\n" -" msg = bcast_rx.recv() => {\n" -" ws_stream.send(Message::text(msg?)).await?;\n" -" }\n" -" }\n" -" }\n" -"}\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), Box> {\n" -" let (bcast_tx, _) = channel(16);\n" -"\n" -" let listener = TcpListener::bind(\"127.0.0.1:2000\").await?;\n" -" println!(\"listening on port 2000\");\n" -"\n" -" loop {\n" -" let (socket, addr) = listener.accept().await?;\n" -" println!(\"New connection from {addr:?}\");\n" -" let bcast_tx = bcast_tx.clone();\n" -" tokio::spawn(async move {\n" -" // Wrap the raw TCP stream into a websocket.\n" -" let ws_stream = ServerBuilder::new().accept(socket).await?;\n" -"\n" -" handle_connection(addr, ws_stream, bcast_tx).await\n" -" });\n" -" }\n" -"}\n" -"```" +"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 +msgid "CXX" msgstr "" -#: src/exercises/concurrency/solutions-afternoon.md:168 +#: src/credits.md msgid "" -"```rust,compile_fail\n" -"use futures_util::stream::StreamExt;\n" -"use futures_util::SinkExt;\n" -"use http::Uri;\n" -"use tokio::io::{AsyncBufReadExt, BufReader};\n" -"use tokio_websockets::{ClientBuilder, Message};\n" -"\n" -"#[tokio::main]\n" -"async fn main() -> Result<(), tokio_websockets::Error> {\n" -" let (mut ws_stream, _) =\n" -" ClientBuilder::from_uri(Uri::from_static(\"ws://127.0.0.1:2000\"))\n" -" .connect()\n" -" .await?;\n" -"\n" -" let stdin = tokio::io::stdin();\n" -" let mut stdin = BufReader::new(stdin).lines();\n" -"\n" -" // Continuous loop for concurrently sending and receiving messages.\n" -" loop {\n" -" tokio::select! {\n" -" incoming = ws_stream.next() => {\n" -" match incoming {\n" -" Some(Ok(msg)) => {\n" -" if let Some(text) = msg.as_text() {\n" -" println!(\"From server: {}\", text);\n" -" }\n" -" },\n" -" Some(Err(err)) => return Err(err.into()),\n" -" None => return Ok(()),\n" -" }\n" -" }\n" -" res = stdin.next_line() => {\n" -" match res {\n" -" Ok(None) => return Ok(()),\n" -" Ok(Some(line)) => ws_stream.send(Message::text(line." -"to_string())).await?,\n" -" Err(err) => return Err(err.into()),\n" -" }\n" -" }\n" -"\n" -" }\n" -" }\n" -"}\n" -"```" +"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 "" +#~ msgid "Small Example" +#~ msgstr "Küçük Örnek" + +#~ msgid "Why Rust?" +#~ msgstr "Neden Rust?" + +#~ msgid "An Example in C" +#~ msgstr "C Dilinde Bir Örnek" + +#~ msgid "Compile Time Guarantees" +#~ msgstr "Derleme Zamanı Garantileri" + +#~ msgid "Runtime Guarantees" +#~ msgstr "Çalışma Zamanı Garantileri" + +#~ msgid "Modern Features" +#~ msgstr "Modern Özellikler" + +#~ msgid "Basic Syntax" +#~ msgstr "Temel Sözdizimi" + +#~ msgid "String vs str" +#~ msgstr "String vs str" + +#~ msgid "Rustdoc" +#~ msgstr "Rustdoc" + +#~ msgid "Overloading" +#~ msgstr "Yükleme (Overloading)" + +#~ msgid "Arrays and for Loops" +#~ msgstr "Diziler ve for Döngüleri" + +#~ msgid "if expressions" +#~ msgstr "if İfadeleri" + +#~ msgid "for expressions" +#~ msgstr "for İfadeleri" + +#~ msgid "while expressions" +#~ msgstr "while İfadeleri" + +#~ msgid "break & continue" +#~ msgstr "break & continue" + +#~ msgid "loop expressions" +#~ msgstr "loop İfadeleri" + +#~ msgid "Variant Payloads" +#~ msgstr "Varyant Yükler" + +#~ msgid "Enum Sizes" +#~ msgstr "Enum Boyutları" + +#~ msgid "Novel Control Flow" +#~ msgstr "Yeni Kontrol Akışları" + +#~ msgid "if let expressions" +#~ msgstr "if let İfadeleri" + +#~ msgid "while let expressions" +#~ msgstr "while let İfadeleri" + +#~ msgid "match expressions" +#~ msgstr "match ifadeleri" + +#~ msgid "Destructuring Structs" +#~ msgstr "Yapıların (Struct) Çözümlenmesi" + +#~ msgid "Destructuring Arrays" +#~ msgstr "Dizilerin Çözümlenmesi" + +#~ msgid "Match Guards" +#~ msgstr "Eşleşme Koşulları/Filtreleri" + +#~ msgid "Stack vs Heap" +#~ msgstr "Stack vs Heap" + +#~ msgid "Stack Memory" +#~ msgstr "Stack Belleği" + +#~ msgid "Manual Memory Management" +#~ msgstr "Manuel Bellek Yönetimi" + +#~ msgid "Scope-Based Memory Management" +#~ msgstr "Kapsam Tabanlı Bellek Yönetimi" + +#~ msgid "Garbage Collection" +#~ msgstr "Çöp Toplama" + +#~ msgid "Moved Strings in Rust" +#~ msgstr "Rust'da Taşınmış Stringler" + +#~ msgid "Double Frees in Modern C++" +#~ msgstr "Modern C++'da Double Free'ler (Adresi iki kez serbest bırakma)" + +#~ msgid "Moves in Function Calls" +#~ msgstr "Fonksiyon Çağrılarında Taşımalar" + +#~ msgid "Copying and Cloning" +#~ msgstr "Kopyalama ve Klonlama" + +#~ msgid "Shared and Unique Borrows" +#~ msgstr "Paylaşımlı (Shared) ve Eşsiz (Unique) Ödünç Almalar" + +#~ msgid "Field Shorthand Syntax" +#~ msgstr "Alanlara İlk Değer Verme Kısaltması'nın Sözdizimi (Syntax)" + +#~ msgid "Method Receiver" +#~ msgstr "Metot Alıcısı" + +#~ msgid "Storing Books" +#~ msgstr "Kitapların Saklanması" + +#~ msgid "Option and Result" +#~ msgstr "Option ve Result" + +#~ msgid "Vec" +#~ msgstr "Vec" + +#~ msgid "HashMap" +#~ msgstr "HashMap" + +#~ msgid "Box" +#~ msgstr "Box" + +#~ msgid "Rc" +#~ msgstr "Rc" + +#~ msgid "Iterators and Ownership" +#~ msgstr "Adımlayıcılar (Iterators) ve Sahiplik" + +#~ msgid "Strings and Iterators" +#~ msgstr "Dizeler (Stringler) ve Adımlayıcılar (Iterators)" + +#~ msgid "Generic Methods" +#~ msgstr "Jenerik Metotlar" + +#~ msgid "Monomorphization" +#~ msgstr "Monomorfizasyon" + +#~ msgid "Default Methods" +#~ msgstr "Varsayılan Metotlar" + +#~ msgid "impl Trait" +#~ msgstr "impl Trait" + +#~ msgid "Important Traits" +#~ msgstr "Önemli Özellikler (Traits)" + +#~ msgid "From and Into" +#~ msgstr "From ve Into" + +#~ msgid "Default" +#~ msgstr "Default" + +#~ msgid "Operators: Add, Mul, ..." +#~ msgstr "Operatörler: Add, Mul, ..." + +#~ msgid "Closures: Fn, FnMut, FnOnce" +#~ msgstr "Kapanışlar (Closures): Fn, FnMut, FnOnce" + +#~ msgid "A Simple GUI Library" +#~ msgstr "Basit bir GUI Kütüphanesi" + +#~ msgid "Points and Polygons" +#~ msgstr "Noktalar ve Çokgenler" + +#~ msgid "Catching Stack Unwinding" +#~ msgstr "Yığın Geri Sarımınının Yakalanması" + +#~ msgid "Structured Error Handling" +#~ msgstr "Yapılandırılmış Hata İşlemesi" + +#~ msgid "Propagating Errors with ?" +#~ msgstr "? ile Hataların Yayılması" + +#~ msgid "Converting Error Types" +#~ msgstr "Hata Türlerinin Dönüştürülmesi" + +#~ msgid "Deriving Error Enums" +#~ msgstr "Hata Enumlarının Türetilmesi" + +#~ msgid "Adding Context to Errors" +#~ msgstr "Hatalara Bağlam (Context) Ekleme" + +#~ msgid "no_std" +#~ msgstr "no_std" + +#~ msgid "alloc" +#~ msgstr "alloc" + +#~ msgid "embedded-hal" +#~ msgstr "embedded-hal" + +#~ msgid "zerocopy" +#~ msgstr "zerocopy" + +#~ msgid "buddy_system_allocator" +#~ msgstr "buddy_system_allocator" + +#~ msgid "tinyvec" +#~ msgstr "tinyvec" + +#~ msgid "spin" +#~ msgstr "spin" + +#~ msgid "Send and Sync" +#~ msgstr "Send ve Sync" + +#~ msgid "Send" +#~ msgstr "Send" + +#~ msgid "Sync" +#~ msgstr "Sync" + +#~ msgid "Arc" +#~ msgstr "Arc" + +#~ msgid "Mutex" +#~ msgstr "Mutex" + +#~ msgid "async/await" +#~ msgstr "async/await" + +#~ msgid "Pin" +#~ msgstr "Pin" + +#~ msgid "Day 1 Morning" +#~ msgstr "1. Gün Sabah" + +#~ msgid "Day 1 Afternoon" +#~ msgstr "1. Gün Öğleden Sonra" + +#~ msgid "Day 2 Morning" +#~ msgstr "2. Gün Sabah" + +#~ msgid "Day 2 Afternoon" +#~ msgstr "2. Gün Öüleden Sonra" + +#~ msgid "Day 3 Morning" +#~ msgstr "3. Gün Sabah" + +#~ msgid "Day 3 Afternoon" +#~ msgstr "3. Gün Öğleden Sonra" + +#~ msgid "Bare Metal Rust Morning" +#~ msgstr "Yalın (Bare) Metal Rust Sabah" + +#~ msgid "Concurrency Morning" +#~ msgstr "Eşzamanlılık Sabah" + +#~ msgid "Concurrency Afternoon" +#~ msgstr "Eşzamanlılık Öğleden Sonra" + +#~ msgid "" +#~ "Day 1: Basic Rust, syntax, control flow, creating and consuming values." +#~ msgstr "" +#~ "1. Gün: Temel Rust, sözdizimi, kontrol akışı, değer oluşturma ve tüketme." + +#~ msgid "" +#~ "Day 2: Memory management, ownership, compound data types, and the " +#~ "standard library." +#~ msgstr "" +#~ "2. Gün: Bellek yönetimi, sahiplik, bileşik veri türleri ve standart " +#~ "kitaplık." + +#~ msgid "Day 3: Generics, traits, error handling, testing, and unsafe Rust." +#~ msgstr "" +#~ "3. Gün: Jenerikler, özellikler (traits), hata işleme, testler ve güvenli " +#~ "olmayan (unsafe) Rust." + +#~ msgid "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust,editable\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "" +#~ "```rust\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" +#~ msgstr "" +#~ "```rust\n" +#~ "fn main() {\n" +#~ " println!(\"Edit me!\");\n" +#~ "}\n" +#~ "```" + +#~ msgid "The Luhn algorithm," +#~ msgstr "Luhn Algortiması," + +#~ msgid "Structs and methods." +#~ msgstr "Yapılar ve metotlar." + +#~ msgid "Stack and Heap Example" +#~ msgstr "Stack vs Heap Örneği" + +#~ msgid "Drawing A Simple GUI" +#~ msgstr "Basit Bir GUI Çizimi" + +#~ msgid "concurrency:" +#~ msgstr "eşzamanlılık:" + +#~ msgid "control flow:" +#~ msgstr "kontrol akışı:" + +#~ msgid "enumeration:" +#~ msgstr "numaralandırma:" + +#~ msgid "error handling:" +#~ msgstr "hata işleme:" + +#~ msgid "garbage collector:" +#~ msgstr "çöp toplama:" + +#~ msgid "generics:" +#~ msgstr "jenerikler:" + +#~ msgid "integration test:" +#~ msgstr "entegrasyon testi:" + +#~ msgid "main function:" +#~ msgstr "main fonksiyonu:" + +#~ msgid "method:" +#~ msgstr "metot:" + +#~ msgid "module:" +#~ msgstr "modül:" + +#~ msgid "ownership:" +#~ msgstr "sahiplik:" + +#~ msgid "panic:" +#~ msgstr "panik:" + +#~ msgid "receiver:" +#~ msgstr "alıcı:" + +#~ msgid "standard library:" +#~ msgstr "standart kütüphane:" + +#~ msgid "struct:" +#~ msgstr "yapı:" + +#~ msgid "thread:" +#~ msgstr "iş parçacığı:" + +#~ msgid "trait:" +#~ msgstr "özellik (trait):" + +#~ msgid "union:" +#~ msgstr "birlik (union):" + +#~ msgid "unit test:" +#~ msgstr "birim testi:" + +#~ msgid "variable:\\" +#~ msgstr "değişken:\\" + +#~ msgid "Pattern matching" +#~ msgstr "Desen eşleştirme" + +#~ msgid "Designing a Library" +#~ msgstr "Kütüphane Tasarlama" + #~ msgid "Pattern Matching (TBD)" #~ msgstr "Desen Eşleştirme"