From a8f9b5e00e874da259a6fd11a55e0d3db87b3154 Mon Sep 17 00:00:00 2001 From: ichxorya Date: Sat, 30 Mar 2024 07:57:28 +0700 Subject: [PATCH] dprint fmt --- po/vi.po | 7163 ++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 4557 insertions(+), 2606 deletions(-) diff --git a/po/vi.po b/po/vi.po index fcc978baf452..6fac9db95c25 100644 --- a/po/vi.po +++ b/po/vi.po @@ -96,11 +96,15 @@ msgstr "Suy diễn kiểu (Type Inference)" msgid "Exercise: Fibonacci" msgstr "Bài tập: Số Fibonacci" -#: 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/lifetimes/solution.md -#: src/iterators/solution.md src/modules/solution.md src/testing/solution.md src/error-handling/solution.md +#: 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/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 msgid "Solution" msgstr "Lời giải" @@ -217,7 +221,8 @@ msgstr "Kiểu cấu trúc có tên (Named Structs)" msgid "Tuple Structs" msgstr "Kiểu cấu trúc bộ (Tuple Structs)" -#: src/SUMMARY.md src/user-defined-types/enums.md src/pattern-matching/destructuring.md +#: src/SUMMARY.md src/user-defined-types/enums.md +#: src/pattern-matching/destructuring.md msgid "Enums" msgstr "Kiểu liệt kê (Enums)" @@ -345,7 +350,8 @@ msgstr "`Option`" msgid "`Result`" msgstr "`Result`" -#: src/SUMMARY.md src/android/aidl/types/primitives.md src/android/interoperability/cpp/type-mapping.md +#: src/SUMMARY.md src/android/aidl/types/primitives.md +#: src/android/interoperability/cpp/type-mapping.md msgid "`String`" msgstr "`String`" @@ -441,7 +447,8 @@ msgstr "Bài tập: Kiểu Builder" msgid "Smart Pointers" msgstr "Con trỏ thông minh (Smart Pointers)" -#: src/SUMMARY.md src/smart-pointers/box.md src/android/interoperability/cpp/type-mapping.md +#: src/SUMMARY.md src/smart-pointers/box.md +#: src/android/interoperability/cpp/type-mapping.md msgid "`Box`" msgstr "`Box`" @@ -797,7 +804,8 @@ msgstr "Xây dựng cho Android: Rust" msgid "With Java" msgstr "Với ngôn ngữ Java" -#: src/SUMMARY.md src/exercises/android/morning.md src/exercises/bare-metal/morning.md src/exercises/bare-metal/afternoon.md +#: 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 "Bài tập" @@ -878,7 +886,8 @@ msgstr "Thêm các bộ thư viện của bên thứ ba (Adding Third Party Crat msgid "Configuring Cargo.toml" msgstr "Tùy chỉnh Cargo.toml" -#: src/SUMMARY.md src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/configuring-gnrt-config-toml.md msgid "Configuring `gnrt_config.toml`" msgstr "Tùy chỉnh `gnrt_config.toml`" @@ -886,7 +895,8 @@ msgstr "Tùy chỉnh `gnrt_config.toml`" msgid "Downloading Crates" msgstr "Tải về các bộ thư viện (Downloading Crates)" -#: src/SUMMARY.md src/chromium/adding-third-party-crates/generating-gn-build-rules.md +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/generating-gn-build-rules.md msgid "Generating `gn` Build Rules" msgstr "Tạo ra luật xây dựng `gn` (Generating `gn` Build Rules)" @@ -894,15 +904,20 @@ msgstr "Tạo ra luật xây dựng `gn` (Generating `gn` Build Rules)" msgid "Resolving Problems" msgstr "Xử lý vấn đề" -#: src/SUMMARY.md src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-generate-code.md msgid "Build Scripts Which Generate Code" msgstr "Scripts xây dựng tạo ra code (Build Scripts Which Generate Code)" -#: src/SUMMARY.md src/chromium/adding-third-party-crates/resolving-problems/build-scripts-which-take-arbitrary-actions.md +#: 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 "Scripts xây dựng ra C++ hoặc thực hiện các hành động tùy ý (Build Scripts Which Build C++ or Take Arbitrary Actions)" +msgstr "" +"Scripts xây dựng ra C++ hoặc thực hiện các hành động tùy ý (Build Scripts " +"Which Build C++ or Take Arbitrary Actions)" -#: src/SUMMARY.md src/chromium/adding-third-party-crates/depending-on-a-crate.md +#: src/SUMMARY.md +#: src/chromium/adding-third-party-crates/depending-on-a-crate.md msgid "Depending on a Crate" msgstr "Phụ thuộc vào một bộ thư viện (Depending on a Crate)" @@ -982,7 +997,8 @@ msgstr "" msgid "Other Projects" msgstr "" -#: src/SUMMARY.md src/exercises/bare-metal/compass.md src/exercises/bare-metal/solutions-morning.md +#: src/SUMMARY.md src/exercises/bare-metal/compass.md +#: src/exercises/bare-metal/solutions-morning.md msgid "Compass" msgstr "" @@ -1126,12 +1142,14 @@ msgstr "" msgid "`Mutex`" msgstr "" -#: src/SUMMARY.md src/memory-management/review.md src/error-handling/try-conversions.md +#: src/SUMMARY.md src/memory-management/review.md +#: src/error-handling/try-conversions.md #: src/concurrency/shared_state/example.md msgid "Example" msgstr "" -#: src/SUMMARY.md src/exercises/concurrency/dining-philosophers.md src/exercises/concurrency/solutions-morning.md +#: src/SUMMARY.md src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/solutions-morning.md msgid "Dining Philosophers" msgstr "" @@ -1163,7 +1181,8 @@ msgstr "" msgid "Tokio" msgstr "" -#: src/SUMMARY.md src/exercises/concurrency/link-checker.md src/async/tasks.md src/exercises/concurrency/chat-app.md +#: src/SUMMARY.md src/exercises/concurrency/link-checker.md src/async/tasks.md +#: src/exercises/concurrency/chat-app.md msgid "Tasks" msgstr "" @@ -1203,7 +1222,8 @@ msgstr "" msgid "Cancellation" msgstr "" -#: src/SUMMARY.md src/exercises/concurrency/chat-app.md src/exercises/concurrency/solutions-afternoon.md +#: src/SUMMARY.md src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "Broadcast Chat Application" msgstr "" @@ -1229,23 +1249,28 @@ msgstr "" #: 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/google/comprehensive-rust/actions/workflows/build.yml?query=branch%3Amain) [![GitHub " -"contributors](https://img.shields.io/github/contributors/google/comprehensive-rust?style=flat-square)](https://github.com/" -"google/comprehensive-rust/graphs/contributors) [![GitHub stars](https://img.shields.io/github/stars/google/comprehensive-" -"rust?style=flat-square)](https://github.com/google/comprehensive-rust/stargazers)" +"[![Build workflow](https://img.shields.io/github/actions/workflow/status/" +"google/comprehensive-rust/build.yml?style=flat-square)](https://github.com/" +"google/comprehensive-rust/actions/workflows/build.yml?query=branch%3Amain) [!" +"[GitHub contributors](https://img.shields.io/github/contributors/google/" +"comprehensive-rust?style=flat-square)](https://github.com/google/" +"comprehensive-rust/graphs/contributors) [![GitHub stars](https://img.shields." +"io/github/stars/google/comprehensive-rust?style=flat-square)](https://github." +"com/google/comprehensive-rust/stargazers)" msgstr "" #: 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 topics like generics and error handling." +"This is a free Rust course developed by the Android team at Google. The " +"course covers the full spectrum of Rust, from basic syntax to advanced " +"topics like generics and error handling." msgstr "" #: src/index.md msgid "" -"The latest version of the course can be found at . If you are reading " -"somewhere else, please check there for updates." +"The latest version of the course can be found at . If you are reading somewhere else, please check there " +"for updates." msgstr "" #: src/index.md @@ -1253,7 +1278,9 @@ msgid "The course is also available [as a PDF](comprehensive-rust.pdf)." msgstr "" #: 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:" +msgid "" +"The goal of the course is to teach you Rust. We assume you don't know " +"anything about Rust and hope to:" msgstr "" #: src/index.md @@ -1273,31 +1300,36 @@ msgid "We call the first four course days Rust Fundamentals." msgstr "" #: src/index.md -msgid "Building on this, you're invited to dive into one or more specialized topics:" +msgid "" +"Building on this, you're invited to dive into one or more specialized topics:" msgstr "" #: 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." +"[Android](android.md): a half-day course on using Rust for Android platform " +"development (AOSP). This includes interoperability with C, C++, and Java." msgstr "" #: src/index.md 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." +"[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 "" #: 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 covered." +"[Bare-metal](bare-metal.md): a whole-day class on using Rust for bare-metal " +"(embedded) development. Both microcontrollers and application processors are " +"covered." msgstr "" #: 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 mutexes) and async/await concurrency (cooperative multitasking using futures)." +"[Concurrency](concurrency.md): a whole-day class on concurrency in Rust. We " +"cover both classical concurrency (preemptively scheduling using threads and " +"mutexes) and async/await concurrency (cooperative multitasking using " +"futures)." msgstr "" #: src/index.md @@ -1305,13 +1337,16 @@ msgid "Non-Goals" msgstr "" #: 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:" +msgid "" +"Rust is a large language and we won't be able to cover all of it in a few " +"days. Some non-goals of this course are:" msgstr "" #: 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](https://doc.rust-lang.org/rust-by-example/macros.html) instead." +"Learning how to develop macros: please see [Chapter 19.5 in the Rust Book]" +"(https://doc.rust-lang.org/book/ch19-06-macros.html) and [Rust by Example]" +"(https://doc.rust-lang.org/rust-by-example/macros.html) instead." msgstr "" #: src/index.md @@ -1320,20 +1355,22 @@ msgstr "" #: 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 C++ to better explain or contrast the Rust approach." +"The course assumes that you already know how to program. Rust is a " +"statically-typed language and we will sometimes make comparisons with C and C" +"++ to better explain or contrast the Rust approach." msgstr "" #: 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." +"If you know how to program in a dynamically-typed language such as Python or " +"JavaScript, then you will be able to follow along just fine too." msgstr "" #: 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 should cover as well as answers to typical questions which come up in class." +"This is an example of a _speaker note_. We will use these to add additional " +"information to the slides. This could be key points which the instructor " +"should cover as well as answers to typical questions which come up in class." msgstr "" #: src/running-the-course.md src/running-the-course/course-structure.md @@ -1341,14 +1378,17 @@ msgid "This page is for the course instructor." msgstr "" #: src/running-the-course.md -msgid "Here is a bit of background information about how we've been running the course internally at Google." +msgid "" +"Here is a bit of background information about how we've been running the " +"course internally at Google." msgstr "" #: src/running-the-course.md msgid "" -"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." +"We typically run classes from 9:00 am to 4:00 pm, with a 1 hour lunch break " +"in the middle. This leaves 3 hours for the morning class and 3 hours for the " +"afternoon class. Both sessions contain multiple breaks and time for students " +"to work on exercises." msgstr "" #: src/running-the-course.md @@ -1357,52 +1397,66 @@ msgstr "" #: 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 speaker notes!). When presenting, you should make sure to open the speaker notes in a popup " -"(click the link with a little arrow next to \"Speaker Notes\"). This way you have a clean screen to present to the class." +"Make yourself familiar with the course material. We've included speaker " +"notes to help highlight the key points (please help us by contributing more " +"speaker notes!). When presenting, you should make sure to open the speaker " +"notes in a popup (click the link with a little arrow next to \"Speaker Notes" +"\"). This way you have a clean screen to present to the class." msgstr "" #: src/running-the-course.md msgid "" -"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." +"Decide on the dates. Since the course takes four days, we recommend that you " +"schedule the days over two weeks. Course participants have said that they " +"find it helpful to have a gap in the course since it helps them process all " +"the information we give them." msgstr "" #: src/running-the-course.md msgid "" -"Find a room large enough for your in-person participants. We recommend a class size of 15-25 people. That's small enough " -"that people are comfortable asking questions --- it's also small enough that one instructor will have time to answer the " -"questions. Make sure the room has _desks_ for yourself and for the students: you will all need to be able to sit and work " -"with your laptops. In particular, you will be doing a lot of live-coding as an instructor, so a lectern won't be very " -"helpful for you." +"Find a room large enough for your in-person participants. We recommend a " +"class size of 15-25 people. That's small enough that people are comfortable " +"asking questions --- it's also small enough that one instructor will have " +"time to answer the questions. Make sure the room has _desks_ for yourself " +"and for the students: you will all need to be able to sit and work with your " +"laptops. In particular, you will be doing a lot of live-coding as an " +"instructor, so a lectern won't be very helpful for you." msgstr "" #: src/running-the-course.md msgid "" -"On the day of your course, show up to the room a little early to set things up. We recommend presenting directly using " -"`mdbook serve` running on your laptop (see the [installation instructions](https://github.com/google/comprehensive-" -"rust#building)). This ensures optimal performance with no lag as you change pages. Using your laptop will also allow you " -"to fix typos as you or the course participants spot them." +"On the day of your course, show up to the room a little early to set things " +"up. We recommend presenting directly using `mdbook serve` running on your " +"laptop (see the [installation instructions](https://github.com/google/" +"comprehensive-rust#building)). This ensures optimal performance with no lag " +"as you change pages. Using your laptop will also allow you to fix typos as " +"you or the course participants spot them." msgstr "" #: src/running-the-course.md msgid "" -"Let people solve the exercises by themselves or in small groups. We typically spend 30-45 minutes on exercises in the " -"morning and in the afternoon (including time to review the solutions). Make sure to ask people if they're stuck or if " -"there is anything you can help with. When you see that several people have the same problem, call it out to the class and " -"offer a solution, e.g., by showing people where to find the relevant information in the standard library." +"Let people solve the exercises by themselves or in small groups. We " +"typically spend 30-45 minutes on exercises in the morning and in the " +"afternoon (including time to review the solutions). Make sure to ask people " +"if they're stuck or if there is anything you can help with. When you see " +"that several people have the same problem, call it out to the class and " +"offer a solution, e.g., by showing people where to find the relevant " +"information in the standard library." msgstr "" #: src/running-the-course.md -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!" +msgid "" +"That is all, good luck running the course! We hope it will be as much fun " +"for you as it has been for us!" msgstr "" #: src/running-the-course.md msgid "" -"Please [provide feedback](https://github.com/google/comprehensive-rust/discussions/86) afterwards so that we can keep " -"improving the course. We would love to hear what worked well for you and what can be made better. Your students are also " -"very welcome to [send us feedback](https://github.com/google/comprehensive-rust/discussions/100)!" +"Please [provide feedback](https://github.com/google/comprehensive-rust/" +"discussions/86) afterwards so that we can keep improving the course. We " +"would love to hear what worked well for you and what can be made better. " +"Your students are also very welcome to [send us feedback](https://github.com/" +"google/comprehensive-rust/discussions/100)!" msgstr "" #: src/running-the-course/course-structure.md @@ -1411,7 +1465,8 @@ msgstr "" #: src/running-the-course/course-structure.md msgid "" -"The first four days make up [Rust Fundamentals](../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 "" #: src/running-the-course/course-structure.md @@ -1551,7 +1606,9 @@ msgid "Deep Dives" msgstr "" #: src/running-the-course/course-structure.md -msgid "In addition to the 4-day class on Rust Fundamentals, we cover some more specialized topics:" +msgid "" +"In addition to the 4-day class on Rust Fundamentals, we cover some more " +"specialized topics:" msgstr "" #: src/running-the-course/course-structure.md @@ -1560,22 +1617,25 @@ msgstr "" #: 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 C, C++, and Java." +"The [Rust in Android](../android.md) deep dive is a half-day course on using " +"Rust for Android platform development. This includes interoperability with " +"C, C++, and Java." msgstr "" #: src/running-the-course/course-structure.md msgid "" -"You will need an [AOSP checkout](https://source.android.com/docs/setup/download/downloading). Make a checkout of the " -"[course repository](https://github.com/google/comprehensive-rust) on the same machine and move the `src/android/` " -"directory into the root of your AOSP checkout. This will ensure that the Android build system sees the `Android.bp` files " -"in `src/android/`." +"You will need an [AOSP checkout](https://source.android.com/docs/setup/" +"download/downloading). Make a checkout of the [course repository](https://" +"github.com/google/comprehensive-rust) on the same machine and move the `src/" +"android/` directory into the root of your AOSP checkout. This will ensure " +"that the Android build system sees the `Android.bp` files in `src/android/`." msgstr "" #: src/running-the-course/course-structure.md msgid "" -"Ensure that `adb sync` works with your emulator or real device and pre-build all Android examples using `src/android/" -"build_all.sh`. Read the script to see the commands it runs and make sure they work when you run them by hand." +"Ensure that `adb sync` works with your emulator or real device and pre-build " +"all Android examples using `src/android/build_all.sh`. Read the script to " +"see the commands it runs and make sure they work when you run them by hand." msgstr "" #: src/running-the-course/course-structure.md @@ -1584,15 +1644,17 @@ msgstr "" #: 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." +"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." +"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 @@ -1601,14 +1663,17 @@ msgstr "" #: 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 application processors are covered." +"The [Bare-Metal Rust](../bare-metal.md) deep dive is a full day class on " +"using Rust for bare-metal (embedded) development. Both microcontrollers and " +"application processors are covered." msgstr "" #: src/running-the-course/course-structure.md msgid "" -"For the microcontroller part, you will need to buy the [BBC micro:bit](https://microbit.org/) v2 development board ahead " -"of time. Everybody will need to install a number of packages as described on the [welcome page](../bare-metal.md)." +"For the microcontroller part, you will need to buy the [BBC micro:bit]" +"(https://microbit.org/) v2 development board ahead of time. Everybody will " +"need to install a number of packages as described on the [welcome page](../" +"bare-metal.md)." msgstr "" #: src/running-the-course/course-structure.md @@ -1617,14 +1682,15 @@ msgstr "" #: 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." +"The [Concurrency in Rust](../concurrency.md) deep dive is a full day class " +"on classical as well as `async`/`await` concurrency." msgstr "" #: src/running-the-course/course-structure.md msgid "" -"You will need a fresh crate set up and the dependencies downloaded and ready to go. You can then copy/paste the examples " -"into `src/main.rs` to experiment with them:" +"You will need a fresh crate set up and the dependencies downloaded and ready " +"to go. You can then copy/paste the examples into `src/main.rs` to experiment " +"with them:" msgstr "" #: src/running-the-course/course-structure.md @@ -1632,7 +1698,9 @@ msgid "Format" msgstr "" #: 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!" +msgid "" +"The course is meant to be very interactive and we recommend letting the " +"questions drive the exploration of Rust!" msgstr "" #: src/running-the-course/keyboard-shortcuts.md @@ -1672,43 +1740,55 @@ msgid ": Activate the search bar." msgstr "" #: src/running-the-course/translations.md -msgid "The course has been translated into other languages by a set of wonderful volunteers:" +msgid "" +"The course has been translated into other languages by a set of wonderful " +"volunteers:" msgstr "" #: 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.com/hugojacob), [@joaovicmendes](https://github.com/joaovicmendes), and " +"[Brazilian Portuguese](https://google.github.io/comprehensive-rust/pt-BR/) " +"by [@rastringer](https://github.com/rastringer), [@hugojacob](https://github." +"com/hugojacob), [@joaovicmendes](https://github.com/joaovicmendes), and " "[@henrif75](https://github.com/henrif75)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) by [@suetfei](https://github.com/suetfei), " -"[@wnghl](https://github.com/wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/kongy), [@noahdragon]" -"(https://github.com/noahdragon), [@superwhd](https://github.com/superwhd), [@SketchK](https://github.com/SketchK), and " -"[@nodmp](https://github.com/nodmp)." +"[Chinese (Simplified)](https://google.github.io/comprehensive-rust/zh-CN/) " +"by [@suetfei](https://github.com/suetfei), [@wnghl](https://github.com/" +"wnghl), [@anlunx](https://github.com/anlunx), [@kongy](https://github.com/" +"kongy), [@noahdragon](https://github.com/noahdragon), [@superwhd](https://" +"github.com/superwhd), [@SketchK](https://github.com/SketchK), and [@nodmp]" +"(https://github.com/nodmp)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) by [@hueich](https://github.com/hueich), " -"[@victorhsieh](https://github.com/victorhsieh), [@mingyc](https://github.com/mingyc), [@kuanhungchen](https://github.com/" -"kuanhungchen), and [@johnathan79717](https://github.com/johnathan79717)." +"[Chinese (Traditional)](https://google.github.io/comprehensive-rust/zh-TW/) " +"by [@hueich](https://github.com/hueich), [@victorhsieh](https://github.com/" +"victorhsieh), [@mingyc](https://github.com/mingyc), [@kuanhungchen](https://" +"github.com/kuanhungchen), and [@johnathan79717](https://github.com/" +"johnathan79717)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[Korean](https://google.github.io/comprehensive-rust/ko/) by [@keispace](https://github.com/keispace), [@jiyongp](https://" -"github.com/jiyongp), [@jooyunghan](https://github.com/jooyunghan), and [@namhyung](https://github.com/namhyung)." +"[Korean](https://google.github.io/comprehensive-rust/ko/) by [@keispace]" +"(https://github.com/keispace), [@jiyongp](https://github.com/jiyongp), " +"[@jooyunghan](https://github.com/jooyunghan), and [@namhyung](https://github." +"com/namhyung)." msgstr "" #: src/running-the-course/translations.md -msgid "[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid](https://github.com/deavid)." +msgid "" +"[Spanish](https://google.github.io/comprehensive-rust/es/) by [@deavid]" +"(https://github.com/deavid)." msgstr "" #: src/running-the-course/translations.md -msgid "Use the language picker in the top-right corner to switch between languages." +msgid "" +"Use the language picker in the top-right corner to switch between languages." msgstr "" #: src/running-the-course/translations.md @@ -1716,49 +1796,58 @@ msgid "Incomplete Translations" msgstr "" #: src/running-the-course/translations.md -msgid "There is a large number of in-progress translations. We link to the most recently updated translations:" +msgid "" +"There is a large number of in-progress translations. We link to the most " +"recently updated translations:" msgstr "" #: src/running-the-course/translations.md -msgid "[Bengali](https://google.github.io/comprehensive-rust/bn/) by [@raselmandol](https://github.com/raselmandol)." +msgid "" +"[Bengali](https://google.github.io/comprehensive-rust/bn/) by [@raselmandol]" +"(https://github.com/raselmandol)." msgstr "" #: 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)." +"[French](https://google.github.io/comprehensive-rust/fr/) by [@KookaS]" +"(https://github.com/KookaS) and [@vcaen](https://github.com/vcaen)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[German](https://google.github.io/comprehensive-rust/de/) by [@Throvn](https://github.com/Throvn) and [@ronaldfw](https://" -"github.com/ronaldfw)." +"[German](https://google.github.io/comprehensive-rust/de/) by [@Throvn]" +"(https://github.com/Throvn) and [@ronaldfw](https://github.com/ronaldfw)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[Japanese](https://google.github.io/comprehensive-rust/ja/) by [@CoinEZ-JPN](https://github.com/CoinEZ) and [@momotaro1105]" -"(https://github.com/momotaro1105)." +"[Japanese](https://google.github.io/comprehensive-rust/ja/) by [@CoinEZ-JPN]" +"(https://github.com/CoinEZ) and [@momotaro1105](https://github.com/" +"momotaro1105)." msgstr "" #: src/running-the-course/translations.md msgid "" -"[Italian](https://google.github.io/comprehensive-rust/it/) by [@henrythebuilder](https://github.com/henrythebuilder) and " -"[@detro](https://github.com/detro)." +"[Italian](https://google.github.io/comprehensive-rust/it/) by " +"[@henrythebuilder](https://github.com/henrythebuilder) and [@detro](https://" +"github.com/detro)." msgstr "" #: 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 get going. Translations are coordinated on the [issue tracker](https://github.com/google/" -"comprehensive-rust/issues/282)." +"If you want to help with this effort, please see [our instructions](https://" +"github.com/google/comprehensive-rust/blob/main/TRANSLATIONS.md) for how to " +"get going. Translations are coordinated on the [issue tracker](https://" +"github.com/google/comprehensive-rust/issues/282)." msgstr "" #: src/cargo.md msgid "" -"When you start reading about Rust, you will soon meet [Cargo](https://doc.rust-lang.org/cargo/), the standard tool used in " -"the Rust ecosystem to build and run Rust applications. Here we want to give a brief overview of what Cargo is and how it " -"fits into the wider ecosystem and how it fits into this training." +"When you start reading about Rust, you will soon meet [Cargo](https://doc." +"rust-lang.org/cargo/), the standard tool used in the Rust ecosystem to build " +"and run Rust applications. Here we want to give a brief overview of what " +"Cargo is and how it fits into the wider ecosystem and how it fits into this " +"training." msgstr "" #: src/cargo.md @@ -1771,24 +1860,28 @@ msgstr "" #: 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 use to install to different compiler versions." +"This will give you the Cargo build tool (`cargo`) and the Rust compiler " +"(`rustc`). You will also get `rustup`, a command line utility that you can " +"use to install to different compiler versions." msgstr "" #: src/cargo.md msgid "" -"After installing Rust, you should configure your editor or IDE to work with Rust. Most editors do this by talking to [rust-" -"analyzer](https://rust-analyzer.github.io/), which provides auto-completion and jump-to-definition functionality for [VS " -"Code](https://code.visualstudio.com/), [Emacs](https://rust-analyzer.github.io/manual.html#emacs), [Vim/Neovim](https://" -"rust-analyzer.github.io/manual.html#vimneovim), and many others. There is also a different IDE available called [RustRover]" -"(https://www.jetbrains.com/rust/)." +"After installing Rust, you should configure your editor or IDE to work with " +"Rust. Most editors do this by talking to [rust-analyzer](https://rust-" +"analyzer.github.io/), which provides auto-completion and jump-to-definition " +"functionality for [VS Code](https://code.visualstudio.com/), [Emacs](https://" +"rust-analyzer.github.io/manual.html#emacs), [Vim/Neovim](https://rust-" +"analyzer.github.io/manual.html#vimneovim), and many others. There is also a " +"different IDE available called [RustRover](https://www.jetbrains.com/rust/)." msgstr "" #: src/cargo.md msgid "" -"On Debian/Ubuntu, you can also install Cargo, the Rust source and the [Rust formatter](https://github.com/rust-lang/" -"rustfmt) via `apt`. However, this gets you an outdated rust version and may lead to unexpected behavior. The command would " -"be:" +"On Debian/Ubuntu, you can also install Cargo, the Rust source and the [Rust " +"formatter](https://github.com/rust-lang/rustfmt) via `apt`. However, this " +"gets you an outdated rust version and may lead to unexpected behavior. The " +"command would be:" msgstr "" #: src/cargo/rust-ecosystem.md @@ -1796,79 +1889,99 @@ msgid "The Rust Ecosystem" msgstr "" #: src/cargo/rust-ecosystem.md -msgid "The Rust ecosystem consists of a number of tools, of which the main ones are:" +msgid "" +"The Rust ecosystem consists of a number of tools, of which the main ones are:" msgstr "" #: src/cargo/rust-ecosystem.md -msgid "`rustc`: the Rust compiler which turns `.rs` files into binaries and other intermediate formats." +msgid "" +"`rustc`: the Rust compiler which turns `.rs` files into binaries and other " +"intermediate formats." msgstr "" #: 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 pass them to `rustc` when building your project. Cargo also comes with a built-in test runner " -"which is used to execute unit tests." +"`cargo`: the Rust dependency manager and build tool. Cargo knows how to " +"download dependencies, usually hosted on , and it will " +"pass them to `rustc` when building your project. Cargo also comes with a " +"built-in test runner which is used to execute unit tests." msgstr "" #: src/cargo/rust-ecosystem.md msgid "" -"`rustup`: the Rust toolchain installer and updater. This tool is used to 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." +"`rustup`: the Rust toolchain installer and updater. This tool is used to " +"install and update `rustc` and `cargo` when new versions of Rust are " +"released. In addition, `rustup` can also download documentation for the " +"standard library. You can have multiple versions of Rust installed at once " +"and `rustup` will let you switch between them as needed." msgstr "" -#: src/cargo/rust-ecosystem.md src/types-and-values/hello-world.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/cargo/rust-ecosystem.md src/types-and-values/hello-world.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/async/async-await.md msgid "Key points:" msgstr "" #: 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 --- plus they enable new functionality." +"Rust has a rapid release schedule with a new release coming out every six " +"weeks. New releases maintain backwards compatibility with old releases --- " +"plus they enable new functionality." msgstr "" #: src/cargo/rust-ecosystem.md -msgid "There are three release channels: \"stable\", \"beta\", and \"nightly\"." +msgid "" +"There are three release channels: \"stable\", \"beta\", and \"nightly\"." msgstr "" #: src/cargo/rust-ecosystem.md -msgid "New features are being tested on \"nightly\", \"beta\" is what becomes \"stable\" every six weeks." +msgid "" +"New features are being tested on \"nightly\", \"beta\" is what becomes " +"\"stable\" every six weeks." msgstr "" #: 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." +"Dependencies can also be resolved from alternative [registries](https://doc." +"rust-lang.org/cargo/reference/registries.html), git, folders, and more." msgstr "" #: src/cargo/rust-ecosystem.md 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." +"Rust also has [editions](https://doc.rust-lang.org/edition-guide/): the " +"current edition is Rust 2021. Previous editions were Rust 2015 and Rust 2018." msgstr "" #: src/cargo/rust-ecosystem.md -msgid "The editions are allowed to make backwards incompatible changes to the language." +msgid "" +"The editions are allowed to make backwards incompatible changes to the " +"language." msgstr "" #: 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." +msgid "" +"To prevent breaking code, editions are opt-in: you select the edition for " +"your crate via the `Cargo.toml` file." msgstr "" #: src/cargo/rust-ecosystem.md -msgid "To avoid splitting the ecosystem, Rust compilers can mix code written for different editions." +msgid "" +"To avoid splitting the ecosystem, Rust compilers can mix code written for " +"different editions." msgstr "" #: 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)." +msgid "" +"Mention that it is quite rare to ever use the compiler directly not through " +"`cargo` (most users never do)." msgstr "" #: src/cargo/rust-ecosystem.md 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:" +"It might be worth alluding that Cargo itself is an extremely powerful and " +"comprehensive tool. It is capable of many advanced features including but " +"not limited to:" msgstr "" #: src/cargo/rust-ecosystem.md @@ -1884,20 +1997,26 @@ msgid "Dev Dependencies and Runtime Dependency management/caching" msgstr "" #: src/cargo/rust-ecosystem.md -msgid "[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts.html)" +msgid "" +"[build scripting](https://doc.rust-lang.org/cargo/reference/build-scripts." +"html)" msgstr "" #: src/cargo/rust-ecosystem.md -msgid "[global installation](https://doc.rust-lang.org/cargo/commands/cargo-install.html)" +msgid "" +"[global installation](https://doc.rust-lang.org/cargo/commands/cargo-install." +"html)" msgstr "" #: 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))." +"It is also extensible with sub command plugins as well (such as [cargo " +"clippy](https://github.com/rust-lang/rust-clippy))." msgstr "" #: src/cargo/rust-ecosystem.md -msgid "Read more from the [official Cargo Book](https://doc.rust-lang.org/cargo/)" +msgid "" +"Read more from the [official Cargo Book](https://doc.rust-lang.org/cargo/)" msgstr "" #: src/cargo/code-samples.md @@ -1906,14 +2025,16 @@ msgstr "" #: 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 and ensures a consistent experience for everyone." +"For this training, we will mostly explore the Rust language through examples " +"which can be executed through your browser. This makes the setup much easier " +"and ensures a consistent experience for everyone." msgstr "" #: src/cargo/code-samples.md msgid "" -"Installing Cargo is still encouraged: it will make it easier for you to do the exercises. On the last day, we will do a " -"larger exercise which shows you how to work with dependencies and for that you need Cargo." +"Installing Cargo is still encouraged: it will make it easier for you to do " +"the exercises. On the last day, we will do a larger exercise which shows you " +"how to work with dependencies and for that you need Cargo." msgstr "" #: src/cargo/code-samples.md @@ -1933,19 +2054,22 @@ msgid " to execute the code when focus is in the text box." msgstr "" #: src/cargo/code-samples.md -msgid "Most code samples are editable like shown above. A few code samples are not editable for various reasons:" +msgid "" +"Most code samples are editable like shown above. A few code samples are not " +"editable for various reasons:" msgstr "" #: src/cargo/code-samples.md msgid "" -"The embedded playgrounds cannot execute unit tests. Copy-paste the code and open it in the real Playground to demonstrate " -"unit tests." +"The embedded playgrounds cannot execute unit tests. Copy-paste the code and " +"open it in the real Playground to demonstrate unit tests." msgstr "" #: src/cargo/code-samples.md msgid "" -"The embedded playgrounds lose their state the moment you navigate away from the page! This is the reason that the students " -"should solve the exercises using a local Rust installation or via the Playground." +"The embedded playgrounds lose their state the moment you navigate away from " +"the page! This is the reason that the students should solve the exercises " +"using a local Rust installation or via the Playground." msgstr "" #: src/cargo/running-locally.md @@ -1954,17 +2078,23 @@ msgstr "" #: 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 Rust Book](https://doc.rust-lang.org/book/ch01-01-installation.html). This should give you a " -"working `rustc` and `cargo`. At the time of writing, the latest stable Rust release has these version numbers:" +"If you want to experiment with the code on your own system, then you will " +"need to first install Rust. Do this by following the [instructions in the " +"Rust Book](https://doc.rust-lang.org/book/ch01-01-installation.html). This " +"should give you a working `rustc` and `cargo`. At the time of writing, the " +"latest stable Rust release has these version numbers:" msgstr "" #: src/cargo/running-locally.md -msgid "You can use any later version too since Rust maintains backwards compatibility." +msgid "" +"You can use any later version too since Rust maintains backwards " +"compatibility." msgstr "" #: 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:" +msgid "" +"With this in place, follow these steps to build a Rust binary from one of " +"the examples in this training:" msgstr "" #: src/cargo/running-locally.md @@ -1972,17 +2102,19 @@ msgid "Click the \"Copy to clipboard\" button on the example you want to copy." msgstr "" #: src/cargo/running-locally.md -msgid "Use `cargo new exercise` to create a new `exercise/` directory for your code:" +msgid "" +"Use `cargo new exercise` to create a new `exercise/` directory for your code:" msgstr "" #: src/cargo/running-locally.md -msgid "Navigate into `exercise/` and use `cargo run` to build and run your binary:" +msgid "" +"Navigate into `exercise/` and use `cargo run` to build and run your binary:" msgstr "" #: 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" +"Replace the boiler-plate code in `src/main.rs` with your own code. For " +"example, using the example on the previous page, make `src/main.rs` look like" msgstr "" #: src/cargo/running-locally.md @@ -1991,21 +2123,24 @@ msgstr "" #: 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/debug/` for a normal debug build. Use `cargo build --release` to produce an optimized release " -"build in `target/release/`." +"Use `cargo check` to quickly check your project for errors, use `cargo " +"build` to compile it without running it. You will find the output in `target/" +"debug/` for a normal debug build. Use `cargo build --release` to produce an " +"optimized release build in `target/release/`." msgstr "" #: src/cargo/running-locally.md msgid "" -"You can add dependencies for your project by editing `Cargo.toml`. When you run `cargo` commands, it will automatically " -"download and compile missing dependencies for you." +"You can add dependencies for your project by editing `Cargo.toml`. When you " +"run `cargo` commands, it will automatically download and compile missing " +"dependencies for you." msgstr "" #: src/cargo/running-locally.md msgid "" -"Try to encourage the class participants to install Cargo and use a local editor. It will make their life easier since they " -"will have a normal development environment." +"Try to encourage the class participants to install Cargo and use a local " +"editor. It will make their life easier since they will have a normal " +"development environment." msgstr "" #: src/welcome-day-1.md @@ -2013,11 +2148,15 @@ msgid "Welcome to Day 1" msgstr "" #: src/welcome-day-1.md -msgid "This is the first day of Rust Fundamentals. We will cover a lot of ground today:" +msgid "" +"This is the first day of Rust Fundamentals. We will cover a lot of ground " +"today:" msgstr "" #: src/welcome-day-1.md -msgid "Basic Rust syntax: variables, scalar and compound types, enums, structs, references, functions, and methods." +msgid "" +"Basic Rust syntax: variables, scalar and compound types, enums, structs, " +"references, functions, and methods." msgstr "" #: src/welcome-day-1.md @@ -2036,12 +2175,15 @@ msgstr "" msgid "Pattern matching: destructuring enums, structs, and arrays." msgstr "" -#: src/welcome-day-1.md src/welcome-day-2.md src/welcome-day-3.md src/welcome-day-4.md +#: 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 +#: 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 "" @@ -2062,7 +2204,9 @@ msgid "[Control Flow Basics](./control-flow-basics.md) (40 minutes)" msgstr "" #: src/welcome-day-1.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 5 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 5 " +"minutes" msgstr "" #: src/welcome-day-1.md @@ -2070,46 +2214,57 @@ msgid "Please remind the students that:" msgstr "" #: src/welcome-day-1.md -msgid "They should ask questions when they get them, don't save them to the end." +msgid "" +"They should ask questions when they get them, don't save them to the end." msgstr "" #: src/welcome-day-1.md -msgid "The class is meant to be interactive and discussions are very much encouraged!" +msgid "" +"The class is meant to be interactive and discussions are very much " +"encouraged!" msgstr "" #: 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." +"As an instructor, you should try to keep the discussions relevant, i.e., " +"keep the discussions related to how Rust does things vs some other language. " +"It can be hard to find the right balance, but err on the side of allowing " +"discussions since they engage people much more than one-way communication." msgstr "" #: src/welcome-day-1.md -msgid "The questions will likely mean that we talk about things ahead of the slides." +msgid "" +"The questions will likely mean that we talk about things ahead of the slides." msgstr "" #: 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." +"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 msgid "" -"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." +"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 msgid "" -"If you're teaching this in a classroom, this is a good place to go over the 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!" +"If you're teaching this in a classroom, this is a good place to go over the " +"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/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/lifetimes.md src/iterators.md +#: 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/lifetimes.md src/iterators.md #: src/modules.md src/testing.md src/error-handling.md src/unsafe-rust.md msgid "In this segment:" msgstr "" @@ -2132,8 +2287,8 @@ 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):" +"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/hello-world/what-is-rust.md @@ -2145,7 +2300,9 @@ msgid "`rustc` uses LLVM as its backend." msgstr "" #: src/hello-world/what-is-rust.md -msgid "Rust supports many [platforms and architectures](https://doc.rust-lang.org/nightly/rustc/platform-support.html):" +msgid "" +"Rust supports many [platforms and architectures](https://doc.rust-lang.org/" +"nightly/rustc/platform-support.html):" msgstr "" #: src/hello-world/what-is-rust.md @@ -2193,7 +2350,8 @@ msgid "High level of control." msgstr "" #: src/hello-world/what-is-rust.md -msgid "Can be scaled down to very constrained devices such as microcontrollers." +msgid "" +"Can be scaled down to very constrained devices such as microcontrollers." msgstr "" #: src/hello-world/what-is-rust.md @@ -2209,7 +2367,9 @@ msgid "Some unique selling points of Rust:" msgstr "" #: src/hello-world/benefits.md -msgid "_Compile time memory safety_ - whole classes of memory bugs are prevented at compile time" +msgid "" +"_Compile time memory safety_ - whole classes of memory bugs are prevented at " +"compile time" msgstr "" #: src/hello-world/benefits.md @@ -2241,7 +2401,9 @@ msgid "No iterator invalidation." msgstr "" #: src/hello-world/benefits.md -msgid "_No undefined runtime behavior_ - what a Rust statement does is never left unspecified" +msgid "" +"_No undefined runtime behavior_ - what a Rust statement does is never left " +"unspecified" msgstr "" #: src/hello-world/benefits.md @@ -2253,7 +2415,9 @@ msgid "Integer overflow is defined (panic or wrap-around)." msgstr "" #: src/hello-world/benefits.md -msgid "_Modern language features_ - as expressive and ergonomic as higher-level languages" +msgid "" +"_Modern language features_ - as expressive and ergonomic as higher-level " +"languages" msgstr "" #: src/hello-world/benefits.md @@ -2289,55 +2453,67 @@ msgid "Excellent Language Server Protocol support." msgstr "" #: src/hello-world/benefits.md -msgid "Do not spend much time here. All of these points will be covered in more depth later." +msgid "" +"Do not spend much time here. All of these points will be covered in more " +"depth later." msgstr "" #: 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:" +"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/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 have the memory unsafety issues. In addition, you get a modern language with constructs " -"like pattern matching and built-in dependency management." +"Experience with C or C++: Rust eliminates a whole class of _runtime errors_ " +"via the borrow checker. You get performance like in C and C++, but you don't " +"have the memory unsafety issues. In addition, you get a modern language with " +"constructs like pattern matching and built-in dependency management." msgstr "" #: src/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 addition you get fast and predictable performance like C and C++ (no garbage collector) as well " -"as access to low-level hardware (should you need it)" +"Experience with Java, Go, Python, JavaScript...: You get the same memory " +"safety as in those languages, plus a similar high-level language feeling. In " +"addition you get fast and predictable performance like C and C++ (no garbage " +"collector) as well as access to low-level hardware (should you need it)" msgstr "" #: src/hello-world/playground.md msgid "" -"The [Rust Playground](https://play.rust-lang.org/) provides an easy way to run short Rust programs, and is the basis for " -"the examples and exercises in this course. Try running the \"hello-world\" program it starts with. It comes with a few " -"handy features:" +"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/hello-world/playground.md -msgid "Under \"Tools\", use the `rustfmt` option to format your code in the \"standard\" way." +msgid "" +"Under \"Tools\", use the `rustfmt` option to format your code in the " +"\"standard\" way." msgstr "" #: 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." +"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/hello-world/playground.md -msgid "If you're interested, use \"ASM\" under \"...\" to see the generated assembly code." +msgid "" +"If you're interested, use \"ASM\" under \"...\" to see the generated " +"assembly code." msgstr "" #: 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." +"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/types-and-values.md @@ -2364,12 +2540,15 @@ msgstr "" msgid "[Exercise: Fibonacci](./types-and-values/exercise.md) (15 minutes)" msgstr "" -#: src/types-and-values.md src/control-flow-basics.md src/generics.md src/modules.md +#: src/types-and-values.md src/control-flow-basics.md src/generics.md +#: src/modules.md msgid "This segment should take about 40 minutes" msgstr "" #: src/types-and-values/hello-world.md -msgid "Let us jump into the simplest possible Rust program, a classic Hello World program:" +msgid "" +"Let us jump into the simplest possible Rust program, a classic Hello World " +"program:" msgstr "" #: src/types-and-values/hello-world.md @@ -2402,14 +2581,15 @@ msgstr "" #: src/types-and-values/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 four days so we " -"start small with something familiar." +"This slide tries to make the students comfortable with Rust code. They will " +"see a ton of it over the next four days so we start small with something " +"familiar." msgstr "" #: src/types-and-values/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." +"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/types-and-values/hello-world.md @@ -2418,28 +2598,34 @@ msgstr "" #: src/types-and-values/hello-world.md msgid "" -"Rust uses macros for situations where you want to have a variable number of arguments (no function [overloading](../" -"control-flow-basics/functions.md))." +"Rust uses macros for situations where you want to have a variable number of " +"arguments (no function [overloading](../control-flow-basics/functions.md))." msgstr "" #: src/types-and-values/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 hygienic](https://veykril.github.io/tlborm/decl-macros/minutiae/hygiene.html)." +"Macros being 'hygienic' means they don't accidentally capture identifiers " +"from the scope they are used in. Rust macros are actually only [partially " +"hygienic](https://veykril.github.io/tlborm/decl-macros/minutiae/hygiene." +"html)." msgstr "" #: src/types-and-values/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, while it is not a functional language, it includes a range of [functional concepts](https://doc." -"rust-lang.org/book/ch13-00-functional-features.html)." +"Rust is multi-paradigm. For example, it has powerful [object-oriented " +"programming features](https://doc.rust-lang.org/book/ch17-00-oop.html), and, " +"while it is not a functional language, it includes a range of [functional " +"concepts](https://doc.rust-lang.org/book/ch13-00-functional-features.html)." msgstr "" #: src/types-and-values/variables.md -msgid "Rust provides type safety via static typing. Variable bindings are made with `let`:" +msgid "" +"Rust provides type safety via static typing. Variable bindings are made with " +"`let`:" msgstr "" -#: src/types-and-values/variables.md src/control-flow-basics/loops/for.md src/control-flow-basics/blocks-and-scopes.md +#: src/types-and-values/variables.md src/control-flow-basics/loops/for.md +#: src/control-flow-basics/blocks-and-scopes.md msgid "\"x: {x}\"" msgstr "" @@ -2451,17 +2637,21 @@ msgstr "" #: src/types-and-values/variables.md msgid "" -"Uncomment the `x = 20` to demonstrate that variables are immutable by default. Add the `mut` keyword to allow changes." +"Uncomment the `x = 20` to demonstrate that variables are immutable by " +"default. Add the `mut` keyword to allow changes." msgstr "" #: src/types-and-values/variables.md msgid "" -"The `i32` here is the type of the variable. This must be known at compile time, but type inference (covered later) allows " -"the programmer to omit it in many cases." +"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/types-and-values/values.md -msgid "Here are some basic built-in types, and the syntax for literal values of each type." +msgid "" +"Here are some basic built-in types, and the syntax for literal values of " +"each type." msgstr "" #: src/types-and-values/values.md src/unsafe-rust/exercise.md @@ -2558,8 +2748,9 @@ msgstr "" #: src/types-and-values/values.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`." +"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/types-and-values/arithmetic.md @@ -2568,8 +2759,9 @@ msgstr "" #: 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." +"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/types-and-values/arithmetic.md @@ -2578,20 +2770,24 @@ msgstr "" #: 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." +"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/types-and-values/arithmetic.md msgid "" -"Change the `i32`'s to `i16` to see an integer overflow, which panics (checked) in a debug build and wraps in a release " -"build. There are other options, such as overflowing, saturating, and carrying. These are accessed with method syntax, e." -"g., `(a * b).saturating_add(b * c).saturating_add(c * a)`." +"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/types-and-values/arithmetic.md msgid "" -"In fact, the compiler will detect overflow of constant expressions, which is why the example requires a separate function." +"In fact, the compiler will detect overflow of constant expressions, which is " +"why the example requires a separate function." msgstr "" #: src/types-and-values/inference.md @@ -2600,20 +2796,24 @@ msgstr "" #: 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." +"This slide demonstrates how the Rust compiler infers types based on " +"constraints given by variable declarations and usages." msgstr "" #: 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." +"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/types-and-values/inference.md msgid "" -"When nothing constrains the type of an integer literal, Rust defaults to `i32`. This sometimes appears as `{integer}` in " -"error messages. Similarly, floating-point literals default to `f64`." +"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/types-and-values/inference.md @@ -2622,12 +2822,15 @@ msgstr "" #: src/types-and-values/exercise.md msgid "" -"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." +"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/types-and-values/exercise.md -msgid "Write a function `fib(n)` that calculates the n'th Fibonacci number. When will this function panic?" +msgid "" +"Write a function `fib(n)` that calculates the n'th Fibonacci number. When " +"will this function panic?" msgstr "" #: src/types-and-values/exercise.md @@ -2655,11 +2858,13 @@ msgid "[Loops](./control-flow-basics/loops.md) (5 minutes)" msgstr "" #: src/control-flow-basics.md -msgid "[break and continue](./control-flow-basics/break-continue.md) (4 minutes)" +msgid "" +"[break and continue](./control-flow-basics/break-continue.md) (4 minutes)" msgstr "" #: src/control-flow-basics.md -msgid "[Blocks and Scopes](./control-flow-basics/blocks-and-scopes.md) (5 minutes)" +msgid "" +"[Blocks and Scopes](./control-flow-basics/blocks-and-scopes.md) (5 minutes)" msgstr "" #: src/control-flow-basics.md @@ -2671,7 +2876,8 @@ msgid "[Macros](./control-flow-basics/macros.md) (2 minutes)" msgstr "" #: src/control-flow-basics.md -msgid "[Exercise: Collatz Sequence](./control-flow-basics/exercise.md) (15 minutes)" +msgid "" +"[Exercise: Collatz Sequence](./control-flow-basics/exercise.md) (15 minutes)" msgstr "" #: src/control-flow-basics/if.md @@ -2680,8 +2886,8 @@ msgstr "" #: src/control-flow-basics/if.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:" +"You use [`if` expressions](https://doc.rust-lang.org/reference/expressions/" +"if-expr.html#if-expressions) exactly like `if` statements in other languages:" msgstr "" #: src/control-flow-basics/if.md @@ -2698,7 +2904,8 @@ msgstr "" #: src/control-flow-basics/if.md msgid "" -"In addition, you can use `if` as an expression. The last expression of each block becomes the value of the `if` expression:" +"In addition, you can use `if` as an expression. The last expression of each " +"block becomes the value of the `if` expression:" msgstr "" #: src/control-flow-basics/if.md @@ -2715,14 +2922,16 @@ msgstr "" #: src/control-flow-basics/if.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." +"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/control-flow-basics/if.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." +"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/control-flow-basics/loops.md @@ -2735,8 +2944,9 @@ msgstr "" #: 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." +"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/control-flow-basics/loops.md @@ -2745,8 +2955,8 @@ msgstr "" #: src/control-flow-basics/loops/for.md msgid "" -"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) iterates over ranges of values or the items in a " -"collection:" +"The [`for` loop](https://doc.rust-lang.org/std/keyword.for.html) iterates " +"over ranges of values or the items in a collection:" msgstr "" #: src/control-flow-basics/loops/for.md @@ -2755,16 +2965,21 @@ msgstr "" #: src/control-flow-basics/loops/for.md msgid "" -"Under the hood `for` loops use a concept called \"iterators\" to handle iterating over different kinds of ranges/" -"collections. Iterators will be discussed in more detail later." +"Under the hood `for` loops use a concept called \"iterators\" to handle " +"iterating over different kinds of ranges/collections. Iterators will be " +"discussed in more detail later." msgstr "" #: src/control-flow-basics/loops/for.md -msgid "Note that the `for` loop only iterates to `4`. Show the `1..=5` syntax for an inclusive range." +msgid "" +"Note that the `for` loop only iterates to `4`. Show the `1..=5` syntax for " +"an inclusive range." msgstr "" #: src/control-flow-basics/loops/loop.md -msgid "The [`loop` statement](https://doc.rust-lang.org/std/keyword.loop.html) just loops forever, until a `break`." +msgid "" +"The [`loop` statement](https://doc.rust-lang.org/std/keyword.loop.html) just " +"loops forever, until a `break`." msgstr "" #: src/control-flow-basics/loops/loop.md @@ -2773,24 +2988,31 @@ msgstr "" #: 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)." +"If you want to immediately start the next iteration use [`continue`](https://" +"doc.rust-lang.org/reference/expressions/loop-expr.html#continue-expressions)." msgstr "" #: src/control-flow-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." +"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/control-flow-basics/break-continue.md src/std-traits/exercise.md src/std-traits/solution.md -#: src/smart-pointers/trait-objects.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 +#: src/control-flow-basics/break-continue.md src/std-traits/exercise.md +#: src/std-traits/solution.md src/smart-pointers/trait-objects.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/control-flow-basics/break-continue/labels.md -msgid "Both `continue` and `break` can optionally take a label argument which is used to break out of nested loops:" +msgid "" +"Both `continue` and `break` can optionally take a label argument which is " +"used to break out of nested loops:" msgstr "" #: src/control-flow-basics/break-continue/labels.md @@ -2799,8 +3021,9 @@ msgstr "" #: src/control-flow-basics/break-continue/labels.md 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)." +"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/control-flow-basics/blocks-and-scopes.md @@ -2809,8 +3032,9 @@ msgstr "" #: src/control-flow-basics/blocks-and-scopes.md msgid "" -"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:" +"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/control-flow-basics/blocks-and-scopes.md @@ -2818,13 +3042,15 @@ msgid "\"y: {y}\"" msgstr "" #: src/control-flow-basics/blocks-and-scopes.md -msgid "If the last expression ends with `;`, then the resulting value and type is `()`." +msgid "" +"If the last expression ends with `;`, then the resulting value and type is " +"`()`." msgstr "" #: src/control-flow-basics/blocks-and-scopes.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`." +"You can show how the value of the block changes by changing the last line in " +"the block. For instance, adding/removing a semicolon or using a `return`." msgstr "" #: src/control-flow-basics/blocks-and-scopes/scopes.md @@ -2832,15 +3058,18 @@ msgid "A variable's scope is limited to the enclosing block." msgstr "" #: src/control-flow-basics/blocks-and-scopes/scopes.md -msgid "You can shadow variables, both those from outer scopes and variables from the same scope:" +msgid "" +"You can shadow variables, both those from outer scopes and variables from " +"the same scope:" msgstr "" #: src/control-flow-basics/blocks-and-scopes/scopes.md msgid "\"before: {a}\"" msgstr "" -#: src/control-flow-basics/blocks-and-scopes/scopes.md src/generics/exercise.md src/generics/solution.md -#: src/std-traits/from-and-into.md src/lifetimes/solution.md +#: src/control-flow-basics/blocks-and-scopes/scopes.md src/generics/exercise.md +#: src/generics/solution.md src/std-traits/from-and-into.md +#: src/lifetimes/solution.md msgid "\"hello\"" msgstr "" @@ -2858,14 +3087,15 @@ msgstr "" #: src/control-flow-basics/blocks-and-scopes/scopes.md msgid "" -"Show that a variable's scope is limited by adding a `b` in the inner block in the last example, and then trying to access " -"it outside that block." +"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/control-flow-basics/blocks-and-scopes/scopes.md msgid "" -"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." +"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/control-flow-basics/blocks-and-scopes/scopes.md @@ -2873,54 +3103,65 @@ msgid "A shadowing variable can have a different type." msgstr "" #: src/control-flow-basics/blocks-and-scopes/scopes.md -msgid "Shadowing looks obscure at first, but is convenient for holding on to values after `.unwrap()`." +msgid "" +"Shadowing looks obscure at first, but is convenient for holding on to values " +"after `.unwrap()`." msgstr "" #: src/control-flow-basics/functions.md -msgid "Declaration parameters are followed by a type (the reverse of some programming languages), then a return type." +msgid "" +"Declaration parameters are followed by a type (the reverse of some " +"programming languages), then a return type." msgstr "" #: 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`)." +"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/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." +"Some functions have no return value, and return the 'unit type', `()`. The " +"compiler will infer this if the `-> ()` return type is omitted." msgstr "" #: src/control-flow-basics/functions.md -msgid "Overloading is not supported -- each function has a single implementation." +msgid "" +"Overloading is not supported -- each function has a single implementation." msgstr "" #: 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." +"Always takes a fixed number of parameters. Default arguments are not " +"supported. Macros can be used to support variadic functions." msgstr "" #: src/control-flow-basics/functions.md -msgid "Always takes a single set of parameter types. These types can be generic, which will be covered later." +msgid "" +"Always takes a single set of parameter types. These types can be generic, " +"which will be covered later." msgstr "" #: src/control-flow-basics/macros.md msgid "" -"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." +"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/control-flow-basics/macros.md msgid "" -"`println!(format, ..)` prints a line to standard output, applying formatting described in [`std::fmt`](https://doc.rust-" -"lang.org/std/fmt/index.html)." +"`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/control-flow-basics/macros.md -msgid "`format!(format, ..)` works just like `println!` but returns the result as a string." +msgid "" +"`format!(format, ..)` works just like `println!` but returns the result as a " +"string." msgstr "" #: src/control-flow-basics/macros.md @@ -2928,11 +3169,15 @@ msgid "`dbg!(expression)` logs the value of the expression and returns it." msgstr "" #: src/control-flow-basics/macros.md -msgid "`todo!()` marks a bit of code as not-yet-implemented. If executed, it will panic." +msgid "" +"`todo!()` marks a bit of code as not-yet-implemented. If executed, it will " +"panic." msgstr "" #: src/control-flow-basics/macros.md -msgid "`unreachable!()` marks a bit of code as unreachable. If executed, it will panic." +msgid "" +"`unreachable!()` marks a bit of code as unreachable. If executed, it will " +"panic." msgstr "" #: src/control-flow-basics/macros.md @@ -2941,16 +3186,21 @@ msgstr "" #: 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." +"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/control-flow-basics/macros.md -msgid "The course does not cover defining macros, but a later section will describe use of derive macros." +msgid "" +"The course does not cover defining macros, but a later section will describe " +"use of derive macros." msgstr "" #: 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" +msgid "" +"The [Collatz Sequence](https://en.wikipedia.org/wiki/Collatz_conjecture) is " +"defined as follows, for an arbitrary n" msgstr "" #: src/control-flow-basics/exercise.md @@ -3102,7 +3352,9 @@ msgid "the sequence terminates." msgstr "" #: src/control-flow-basics/exercise.md -msgid "Write a function to calculate the length of the collatz sequence for a given initial `n`." +msgid "" +"Write a function to calculate the length of the collatz sequence for a given " +"initial `n`." msgstr "" #: src/control-flow-basics/exercise.md src/control-flow-basics/solution.md @@ -3113,8 +3365,8 @@ msgstr "" msgid "\"Length: {}\"" 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 +#: src/welcome-day-1-afternoon.md src/welcome-day-2-afternoon.md +#: src/welcome-day-3-afternoon.md src/welcome-day-4-afternoon.md msgid "Welcome Back" msgstr "" @@ -3131,7 +3383,9 @@ msgid "[User-Defined Types](./user-defined-types.md) (50 minutes)" msgstr "" #: src/welcome-day-1-afternoon.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 35 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 35 " +"minutes" msgstr "" #: src/tuples-and-arrays.md @@ -3147,7 +3401,9 @@ msgid "[Array Iteration](./tuples-and-arrays/iteration.md) (3 minutes)" msgstr "" #: src/tuples-and-arrays.md -msgid "[Patterns and Destructuring](./tuples-and-arrays/destructuring.md) (5 minutes)" +msgid "" +"[Patterns and Destructuring](./tuples-and-arrays/destructuring.md) (5 " +"minutes)" msgstr "" #: src/tuples-and-arrays.md @@ -3160,15 +3416,18 @@ msgstr "" #: src/tuples-and-arrays/arrays.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. Slices, " -"which have a size determined at runtime, are covered later." +"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/tuples-and-arrays/arrays.md msgid "" -"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." +"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/tuples-and-arrays/arrays.md @@ -3177,13 +3436,17 @@ msgstr "" #: src/tuples-and-arrays/arrays.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." +"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/tuples-and-arrays/arrays.md -msgid "Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be easier to read." +msgid "" +"Adding `#`, eg `{a:#?}`, invokes a \"pretty printing\" format, which can be " +"easier to read." msgstr "" #: src/tuples-and-arrays/tuples.md @@ -3195,13 +3458,15 @@ msgid "Tuples group together values of different types into a compound type." msgstr "" #: src/tuples-and-arrays/tuples.md -msgid "Fields of a tuple can be accessed by the period and the index of the value, e.g. `t.0`, `t.1`." +msgid "" +"Fields of a tuple can be accessed by the period and the index of the value, " +"e.g. `t.0`, `t.1`." msgstr "" #: src/tuples-and-arrays/tuples.md msgid "" -"The empty tuple `()` is referred to as the \"unit type\" and signifies absence of a return value, akin to `void` in other " -"languages." +"The empty tuple `()` is referred to as the \"unit type\" and signifies " +"absence of a return value, akin to `void` in other languages." msgstr "" #: src/tuples-and-arrays/iteration.md @@ -3209,19 +3474,23 @@ msgid "The `for` statement supports iterating over arrays (but not tuples)." msgstr "" #: src/tuples-and-arrays/iteration.md -msgid "This functionality uses the `IntoIterator` trait, but we haven't covered that yet." +msgid "" +"This functionality uses the `IntoIterator` trait, but we haven't covered " +"that yet." msgstr "" #: src/tuples-and-arrays/iteration.md msgid "" -"The `assert_ne!` macro is new here. There are also `assert_eq!` and `assert!` macros. These are always checked while, " -"debug-only variants like `debug_assert!` compile to nothing in release builds." +"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/tuples-and-arrays/destructuring.md msgid "" -"When working with tuples and other structured values it's common to want to extract the inner values into local variables. " -"This can be done manually by directly accessing the inner values:" +"When working with tuples and other structured values it's common to want to " +"extract the inner values into local variables. This can be done manually by " +"directly accessing the inner values:" msgstr "" #: src/tuples-and-arrays/destructuring.md @@ -3229,29 +3498,35 @@ msgid "\"left: {left}, right: {right}\"" msgstr "" #: src/tuples-and-arrays/destructuring.md -msgid "However, Rust also supports using pattern matching to destructure a larger value into its constituent parts:" +msgid "" +"However, Rust also supports using pattern matching to destructure a larger " +"value into its constituent parts:" msgstr "" #: src/tuples-and-arrays/destructuring.md msgid "" -"The patterns used here are \"irrefutable\", meaning that the compiler can statically verify that the value on the right of " -"`=` has the same structure as the pattern." +"The patterns used here are \"irrefutable\", meaning that the compiler can " +"statically verify that the value on the right of `=` has the same structure " +"as the pattern." msgstr "" #: src/tuples-and-arrays/destructuring.md msgid "" -"A variable name is an irrefutable pattern that always matches any value, hence why we can also use `let` to declare a " -"single variable." +"A variable name is an irrefutable pattern that always matches any value, " +"hence why we can also use `let` to declare a single variable." msgstr "" #: src/tuples-and-arrays/destructuring.md msgid "" -"Rust also supports using patterns in conditionals, allowing for equality comparison and destructuring to happen at the " -"same time. This form of pattern matching will be discussed in more detail later." +"Rust also supports using patterns in conditionals, allowing for equality " +"comparison and destructuring to happen at the same time. This form of " +"pattern matching will be discussed in more detail later." msgstr "" #: src/tuples-and-arrays/destructuring.md -msgid "Edit the examples above to show the compiler error when the pattern doesn't match the value being matched on." +msgid "" +"Edit the examples above to show the compiler error when the pattern doesn't " +"match the value being matched on." msgstr "" #: src/tuples-and-arrays/exercise.md @@ -3264,7 +3539,8 @@ msgstr "" #: src/tuples-and-arrays/exercise.md msgid "" -"Use an array such as the above to write a function `transpose` which will transpose a matrix (turn rows into columns):" +"Use an array such as the above to write a function `transpose` which will " +"transpose a matrix (turn rows into columns):" msgstr "" #: src/tuples-and-arrays/exercise.md @@ -3272,10 +3548,13 @@ msgid "Hard-code both functions to operate on 3 × 3 matrices." msgstr "" #: src/tuples-and-arrays/exercise.md -msgid "Copy the code below to and implement the functions:" +msgid "" +"Copy the code below to and implement the " +"functions:" msgstr "" -#: src/tuples-and-arrays/exercise.md src/borrowing/exercise.md src/unsafe-rust/exercise.md +#: 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 "" @@ -3321,14 +3600,16 @@ msgstr "" #: 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." +"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/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." +"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/references/shared.md @@ -3337,43 +3618,54 @@ msgstr "" #: src/references/shared.md msgid "" -"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." +"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/references/shared.md msgid "" -"References are implemented as pointers, and a key advantage is that they can be much smaller than the thing they point to. " -"Students familiar with C or C++ will recognize references as pointers. Later parts of the course will cover how Rust " -"prevents the memory-safety bugs that come from using raw pointers." +"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/references/shared.md -msgid "Rust does not automatically create references for you - the `&` is always required." +msgid "" +"Rust does not automatically create references for you - the `&` is always " +"required." msgstr "" #: src/references/shared.md msgid "" -"Rust will auto-dereference in some cases, in particular when invoking methods (try `r.is_ascii()`). There is no need for " -"an `->` operator like in C++." +"Rust will auto-dereference in some cases, in particular when invoking " +"methods (try `r.is_ascii()`). There is no need for an `->` operator like in C" +"++." msgstr "" #: src/references/shared.md msgid "" -"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." +"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/references/shared.md -msgid "A shared reference does not allow modifying the value it refers to, even if that value was mutable. Try `*r = 'X'`." +msgid "" +"A shared reference does not allow modifying the value it refers to, even if " +"that value was mutable. Try `*r = 'X'`." msgstr "" #: src/references/shared.md msgid "" -"Rust is tracking the lifetimes of all references to ensure they live long enough. Dangling references cannot occur in safe " -"Rust. `x_axis` would return a reference to `point`, but `point` will be deallocated when the function returns, so this " -"will not compile." +"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/references/shared.md @@ -3382,21 +3674,25 @@ msgstr "" #: src/references/exclusive.md msgid "" -"Exclusive references, also known as mutable references, allow changing the value they refer to. They have type `&mut T`." +"Exclusive references, also known as mutable references, allow changing the " +"value they refer to. They have type `&mut T`." msgstr "" #: src/references/exclusive.md msgid "" -"\"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." +"\"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/references/exclusive.md msgid "" -"Be sure to note the difference between `let mut x_coord: &i32` and `let x_coord: &mut i32`. The first one represents a " -"shared reference which can be bound to different values, while the second represents an exclusive reference to a mutable " -"value." +"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/references/slices.md @@ -3416,40 +3712,49 @@ msgid "Question: What happens if you modify `a[3]` right before printing `s`?" msgstr "" #: src/references/slices.md -msgid "We create a slice by borrowing `a` and specifying the starting and ending indexes in brackets." +msgid "" +"We create a slice by borrowing `a` and specifying the starting and ending " +"indexes in brackets." msgstr "" #: src/references/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." +"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/references/slices.md -msgid "The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are identical." +msgid "" +"The same is true for the last index, so `&a[2..a.len()]` and `&a[2..]` are " +"identical." msgstr "" #: src/references/slices.md -msgid "To easily create a slice of the full array, we can therefore use `&a[..]`." +msgid "" +"To easily create a slice of the full array, we can therefore use `&a[..]`." msgstr "" #: src/references/slices.md 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." +"`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/references/slices.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." +"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/references/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." +"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/references/strings.md @@ -3486,38 +3791,44 @@ msgstr "" #: src/references/strings.md 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." +"`&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/references/strings.md -msgid "Rust's `String` type is a wrapper around a vector of bytes. As with a `Vec`, it is owned." +msgid "" +"Rust's `String` type is a wrapper around a vector of bytes. As with a " +"`Vec`, it is owned." msgstr "" #: src/references/strings.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." +"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/references/strings.md msgid "" -"The `format!()` macro is a convenient way to generate an owned string from dynamic values. It accepts the same format " -"specification as `println!()`." +"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/references/strings.md msgid "" -"You can borrow `&str` slices from `String` via `&` and optionally range selection. If you select a byte range that is not " -"aligned to character boundaries, the expression will panic. The `chars` iterator iterates over characters and is preferred " -"over trying to get character boundaries right." +"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/references/strings.md msgid "" -"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)." +"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/references/strings.md @@ -3526,20 +3837,24 @@ msgstr "" #: src/references/strings.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:" +"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/references/exercise.md msgid "" -"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." +"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/references/exercise.md msgid "" -"// Calculate the magnitude of a vector by summing the squares of its coordinates\n" -"// and taking the square root. Use the `sqrt()` method to calculate the square\n" +"// 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 "" @@ -3570,7 +3885,9 @@ msgid "/// Calculate the magnitude of the given vector.\n" msgstr "" #: src/references/solution.md -msgid "/// Change the magnitude of the vector to 1.0 without changing its direction.\n" +msgid "" +"/// Change the magnitude of the vector to 1.0 without changing its " +"direction.\n" msgstr "" #: src/user-defined-types.md @@ -3594,10 +3911,12 @@ msgid "[Type Aliases](./user-defined-types/aliases.md) (2 minutes)" msgstr "" #: src/user-defined-types.md -msgid "[Exercise: Elevator Events](./user-defined-types/exercise.md) (15 minutes)" +msgid "" +"[Exercise: Elevator Events](./user-defined-types/exercise.md) (15 minutes)" msgstr "" -#: src/user-defined-types.md src/methods-and-traits.md src/borrowing.md src/lifetimes.md +#: src/user-defined-types.md src/methods-and-traits.md src/borrowing.md +#: src/lifetimes.md msgid "This segment should take about 50 minutes" msgstr "" @@ -3609,7 +3928,8 @@ msgstr "" msgid "\"{} is {} years old\"" msgstr "" -#: src/user-defined-types/named-structs.md src/android/interoperability/with-c/bindgen.md +#: src/user-defined-types/named-structs.md +#: src/android/interoperability/with-c/bindgen.md msgid "\"Peter\"" msgstr "" @@ -3621,8 +3941,8 @@ msgstr "" msgid "\"Jackie\"" msgstr "" -#: src/user-defined-types/named-structs.md src/user-defined-types/enums.md src/pattern-matching/match.md -#: src/methods-and-traits/methods.md +#: src/user-defined-types/named-structs.md src/user-defined-types/enums.md +#: src/pattern-matching/match.md src/methods-and-traits/methods.md msgid "Key Points:" msgstr "" @@ -3639,27 +3959,35 @@ msgid "Unlike in C++, there is no inheritance between structs." msgstr "" #: src/user-defined-types/named-structs.md -msgid "This may be a good time to let people know there are different types of structs." +msgid "" +"This may be a good time to let people know there are different types of " +"structs." msgstr "" #: src/user-defined-types/named-structs.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." +"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/user-defined-types/named-structs.md -msgid "The next slide will introduce Tuple structs, used when the field names are not important." +msgid "" +"The next slide will introduce Tuple structs, used when the field names are " +"not important." msgstr "" #: src/user-defined-types/named-structs.md -msgid "If you already have variables with the right names, then you can create the struct using a shorthand." +msgid "" +"If you already have variables with the right names, then you can create the " +"struct using a shorthand." msgstr "" #: src/user-defined-types/named-structs.md msgid "" -"The syntax `..avery` allows us to copy the majority of the fields from the old struct without having to explicitly type it " -"all out. It must always be the last element." +"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/user-defined-types/tuple-structs.md @@ -3678,13 +4006,17 @@ msgstr "" msgid "\"Ask a rocket scientist at NASA\"" msgstr "" -#: 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 +#: 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/user-defined-types/tuple-structs.md -msgid "Newtypes are a great way to encode additional information about the value in a primitive type, for example:" +msgid "" +"Newtypes are a great way to encode additional information about the value in " +"a primitive type, for example:" msgstr "" #: src/user-defined-types/tuple-structs.md @@ -3693,16 +4025,20 @@ msgstr "" #: src/user-defined-types/tuple-structs.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)`." +"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/user-defined-types/tuple-structs.md -msgid "Demonstrate how to add a `f64` value to a `Newtons` type by accessing the single field in the newtype." +msgid "" +"Demonstrate how to add a `f64` value to a `Newtons` type by accessing the " +"single field in the newtype." msgstr "" #: src/user-defined-types/tuple-structs.md -msgid "Rust generally doesn’t like inexplicit things, like automatic unwrapping or for instance using booleans as integers." +msgid "" +"Rust generally doesn’t like inexplicit things, like automatic unwrapping or " +"for instance using booleans as integers." msgstr "" #: src/user-defined-types/tuple-structs.md @@ -3711,12 +4047,14 @@ msgstr "" #: src/user-defined-types/tuple-structs.md msgid "" -"The example is a subtle reference to the [Mars Climate Orbiter](https://en.wikipedia.org/wiki/Mars_Climate_Orbiter) " -"failure." +"The example is a subtle reference to the [Mars Climate Orbiter](https://en." +"wikipedia.org/wiki/Mars_Climate_Orbiter) failure." msgstr "" #: src/user-defined-types/enums.md -msgid "The `enum` keyword allows the creation of a type which has a few different variants:" +msgid "" +"The `enum` keyword allows the creation of a type which has a few different " +"variants:" msgstr "" #: src/user-defined-types/enums.md @@ -3740,13 +4078,16 @@ msgid "Enumerations allow you to collect a set of values under one type." msgstr "" #: src/user-defined-types/enums.md -msgid "`Direction` is a type with variants. There are two values of `Direction`: `Direction::Left` and `Direction::Right`." +msgid "" +"`Direction` is a type with variants. There are two values of `Direction`: " +"`Direction::Left` and `Direction::Right`." msgstr "" #: src/user-defined-types/enums.md msgid "" -"`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." +"`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/user-defined-types/enums.md @@ -3755,14 +4096,15 @@ msgstr "" #: src/user-defined-types/enums.md msgid "" -"In both, you can have a simple version without fields (unit struct) or one with different types of fields (variant " -"payloads)." +"In both, you can have a simple version without fields (unit struct) or one " +"with different types of fields (variant payloads)." msgstr "" #: src/user-defined-types/enums.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." +"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/user-defined-types/enums.md @@ -3775,38 +4117,47 @@ msgstr "" #: 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." +"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/user-defined-types/enums.md -msgid "You can control the discriminant if needed (e.g., for compatibility with C):" +msgid "" +"You can control the discriminant if needed (e.g., for compatibility with C):" msgstr "" #: src/user-defined-types/enums.md -msgid "Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 bytes." +msgid "" +"Without `repr`, the discriminant type takes 2 bytes, because 10001 fits 2 " +"bytes." msgstr "" -#: src/user-defined-types/enums.md src/user-defined-types/static.md src/memory-management/review.md -#: src/memory-management/move.md src/smart-pointers/box.md src/borrowing/shared.md +#: src/user-defined-types/enums.md src/user-defined-types/static.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/user-defined-types/enums.md -msgid "Rust has several optimizations it can employ to make enums take up less space." +msgid "" +"Rust has several optimizations it can employ to make enums take up less " +"space." msgstr "" #: 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::>()`." +"Null pointer optimization: For [some types](https://doc.rust-lang.org/std/" +"option/#representation), Rust guarantees that `size_of::()` equals " +"`size_of::>()`." msgstr "" #: src/user-defined-types/enums.md 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." +"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/user-defined-types/static.md @@ -3814,7 +4165,9 @@ msgid "`static`" msgstr "" #: src/user-defined-types/static.md -msgid "Static variables will live during the whole execution of the program, and therefore will not move:" +msgid "" +"Static variables will live during the whole execution of the program, and " +"therefore will not move:" msgstr "" #: src/user-defined-types/static.md @@ -3827,10 +4180,12 @@ msgstr "" #: src/user-defined-types/static.md 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." +"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/user-defined-types/static.md @@ -3839,14 +4194,15 @@ msgstr "" #: src/user-defined-types/static.md msgid "" -"`static` provides object identity: an address in memory and state as required by types with interior mutability such as " -"`Mutex`." +"`static` provides object identity: an address in memory and state as " +"required by types with interior mutability such as `Mutex`." msgstr "" #: src/user-defined-types/static.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." +"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/user-defined-types/static.md @@ -3858,18 +4214,21 @@ msgid "`const`" msgstr "" #: src/user-defined-types/const.md -msgid "Constants are evaluated at compile time and their values are inlined wherever they are used:" +msgid "" +"Constants are evaluated at compile time and their values are inlined " +"wherever they are used:" msgstr "" #: src/user-defined-types/const.md msgid "" -"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-vs-static.html) these are inlined upon use." +"According to the [Rust RFC Book](https://rust-lang.github.io/rfcs/0246-const-" +"vs-static.html) these are inlined upon use." msgstr "" #: src/user-defined-types/const.md msgid "" -"Only functions marked `const` can be called at compile time to generate `const` values. `const` functions can however be " -"called at runtime." +"Only functions marked `const` can be called at compile time to generate " +"`const` values. `const` functions can however be called at runtime." msgstr "" #: src/user-defined-types/const.md @@ -3878,11 +4237,14 @@ msgstr "" #: src/user-defined-types/const.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." +"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/user-defined-types/aliases.md -msgid "A type alias creates a name for another type. The two types can be used interchangeably." +msgid "" +"A type alias creates a name for another type. The two types can be used " +"interchangeably." msgstr "" #: src/user-defined-types/aliases.md @@ -3895,18 +4257,22 @@ msgstr "" #: 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 `{:?}`." +"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/user-defined-types/exercise.md msgid "" -"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." +"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/user-defined-types/exercise.md src/user-defined-types/solution.md -msgid "/// An event in the elevator system that the controller must react to.\n" +msgid "" +"/// An event in the elevator system that the controller must react to.\n" msgstr "" #: src/user-defined-types/exercise.md @@ -3930,7 +4296,9 @@ msgid "/// The car doors have closed.\n" msgstr "" #: src/user-defined-types/exercise.md src/user-defined-types/solution.md -msgid "/// A directional button was pressed in an elevator lobby on the given floor.\n" +msgid "" +"/// A directional button was pressed in an elevator lobby on the given " +"floor.\n" msgstr "" #: src/user-defined-types/exercise.md src/user-defined-types/solution.md @@ -3998,7 +4366,9 @@ msgid "Welcome to Day 2" msgstr "" #: src/welcome-day-2.md -msgid "Now that we have seen a fair amount of Rust, today will focus on Rust's type system:" +msgid "" +"Now that we have seen a fair amount of Rust, today will focus on Rust's type " +"system:" msgstr "" #: src/welcome-day-2.md @@ -4018,7 +4388,8 @@ msgid "Generics: parameterizing types on other types." msgstr "" #: src/welcome-day-2.md -msgid "Standard library types and traits: a tour of Rust's rich standard library." +msgid "" +"Standard library types and traits: a tour of Rust's rich standard library." msgstr "" #: src/welcome-day-2.md @@ -4038,7 +4409,9 @@ msgid "[Generics](./generics.md) (40 minutes)" msgstr "" #: src/welcome-day-2.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 55 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 55 " +"minutes" msgstr "" #: src/pattern-matching.md @@ -4054,7 +4427,9 @@ msgid "[Let Control Flow](./pattern-matching/let-control-flow.md) (10 minutes)" msgstr "" #: src/pattern-matching.md -msgid "[Exercise: Expression Evaluation](./pattern-matching/exercise.md) (30 minutes)" +msgid "" +"[Exercise: Expression Evaluation](./pattern-matching/exercise.md) (30 " +"minutes)" msgstr "" #: src/pattern-matching.md src/memory-management.md @@ -4063,8 +4438,8 @@ msgstr "" #: src/pattern-matching/match.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." +"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/match.md @@ -4083,7 +4458,8 @@ msgstr "" msgid "\"Quitting\"" msgstr "" -#: src/pattern-matching/match.md src/generics/exercise.md src/generics/solution.md src/std-traits/solution.md +#: src/pattern-matching/match.md src/generics/exercise.md +#: src/generics/solution.md src/std-traits/solution.md #: src/error-handling/exercise.md src/error-handling/solution.md msgid "'a'" msgstr "" @@ -4104,11 +4480,13 @@ msgstr "" msgid "\"Moving around\"" msgstr "" -#: src/pattern-matching/match.md src/error-handling/exercise.md src/error-handling/solution.md +#: src/pattern-matching/match.md src/error-handling/exercise.md +#: src/error-handling/solution.md msgid "'0'" msgstr "" -#: src/pattern-matching/match.md src/error-handling/exercise.md src/error-handling/solution.md +#: src/pattern-matching/match.md src/error-handling/exercise.md +#: src/error-handling/solution.md msgid "'9'" msgstr "" @@ -4126,18 +4504,22 @@ msgstr "" #: src/pattern-matching/match.md msgid "" -"The `_` pattern is a wildcard pattern which matches any value. The expressions _must_ be exhaustive, meaning that it " -"covers every possibility, so `_` is often used as the final catch-all case." +"The `_` pattern is a wildcard pattern which matches any value. The " +"expressions _must_ be exhaustive, meaning that it covers every possibility, " +"so `_` is often used as the final catch-all case." msgstr "" #: src/pattern-matching/match.md msgid "" -"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 `()`." +"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/pattern-matching/match.md -msgid "A variable in the pattern (`key` in this example) will create a binding that can be used within the match arm." +msgid "" +"A variable in the pattern (`key` in this example) will create a binding that " +"can be used within the match arm." msgstr "" #: src/pattern-matching/match.md @@ -4145,7 +4527,9 @@ msgid "A match guard causes the arm to match only if the condition is true." msgstr "" #: src/pattern-matching/match.md -msgid "You might point out how some specific characters are being used when in a pattern" +msgid "" +"You might point out how some specific characters are being used when in a " +"pattern" msgstr "" #: src/pattern-matching/match.md @@ -4166,19 +4550,23 @@ msgstr "" #: src/pattern-matching/match.md 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." +"Match guards as a separate syntax feature are important and necessary when " +"we wish to concisely express more complex ideas than patterns alone would " +"allow." msgstr "" #: src/pattern-matching/match.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." +"They are not the same as separate `if` expression inside of the match arm. " +"An `if` expression inside of the branch block (after `=>`) happens after the " +"match arm is selected. Failing the `if` condition inside of that block won't " +"result in other arms of the original `match` expression being considered." msgstr "" #: src/pattern-matching/match.md -msgid "The condition defined in the guard applies to every expression in a pattern with an `|`." +msgid "" +"The condition defined in the guard applies to every expression in a pattern " +"with an `|`." msgstr "" #: src/pattern-matching/destructuring.md @@ -4203,8 +4591,9 @@ msgstr "" #: src/pattern-matching/destructuring.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:" +"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 @@ -4221,8 +4610,9 @@ msgstr "" #: src/pattern-matching/destructuring.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." +"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 @@ -4235,40 +4625,50 @@ msgstr "" #: src/pattern-matching/destructuring.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." +"The distinction between a capture and a constant expression can be hard to " +"spot. Try changing the `2` in the second arm to a variable, and see that it " +"subtly doesn't work. Change it to a `const` and see it working again." msgstr "" #: src/pattern-matching/destructuring.md -msgid "The `if`/`else` expression is returning an enum that is later unpacked with a `match`." +msgid "" +"The `if`/`else` expression is returning an enum that is later unpacked with " +"a `match`." msgstr "" #: src/pattern-matching/destructuring.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." +"You can try adding a third variant to the enum definition and displaying the " +"errors when running the code. Point out the places where your code is now " +"inexhaustive and how the compiler tries to give you hints." msgstr "" #: src/pattern-matching/destructuring.md -msgid "The values in the enum variants can only be accessed after being pattern matched." +msgid "" +"The values in the enum variants can only be accessed after being pattern " +"matched." msgstr "" #: 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." +"Demonstrate what happens when the search is inexhaustive. Note the advantage " +"the Rust compiler provides by confirming when all cases are handled." msgstr "" #: src/pattern-matching/destructuring.md msgid "" -"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." +"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/pattern-matching/let-control-flow.md -msgid "Rust has a few control flow constructs which differ from other languages. They are used for pattern matching:" +msgid "" +"Rust has a few control flow constructs which differ from other languages. " +"They are used for pattern matching:" msgstr "" #: src/pattern-matching/let-control-flow.md @@ -4285,8 +4685,9 @@ msgstr "" #: src/pattern-matching/let-control-flow.md 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:" +"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/pattern-matching/let-control-flow.md @@ -4299,9 +4700,10 @@ msgstr "" #: src/pattern-matching/let-control-flow.md msgid "" -"For the common case of matching a pattern and returning from the function, use [`let else`](https://doc.rust-lang.org/rust-" -"by-example/flow_control/let_else.html). The \"else\" case must diverge (`return`, `break`, or panic - anything but falling " -"off the end of the block)." +"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/pattern-matching/let-control-flow.md @@ -4320,21 +4722,25 @@ msgstr "" msgid "\"result: {:?}\"" msgstr "" -#: src/pattern-matching/let-control-flow.md src/generics/trait-bounds.md src/smart-pointers/solution.md -#: src/testing/solution.md src/android/testing.md src/android/testing/googletest.md +#: src/pattern-matching/let-control-flow.md src/generics/trait-bounds.md +#: src/smart-pointers/solution.md src/testing/solution.md +#: src/android/testing.md src/android/testing/googletest.md msgid "\"foo\"" msgstr "" #: src/pattern-matching/let-control-flow.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:" +"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/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." +"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/pattern-matching/let-control-flow.md @@ -4342,7 +4748,9 @@ msgid "if-let" msgstr "" #: 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`." +msgid "" +"Unlike `match`, `if let` does not have to cover all branches. This can make " +"it more concise than `match`." msgstr "" #: src/pattern-matching/let-control-flow.md @@ -4350,7 +4758,8 @@ msgid "A common usage is handling `Some` values when working with `Option`." msgstr "" #: src/pattern-matching/let-control-flow.md -msgid "Unlike `match`, `if let` does not support guard clauses for pattern matching." +msgid "" +"Unlike `match`, `if let` does not support guard clauses for pattern matching." msgstr "" #: src/pattern-matching/let-control-flow.md @@ -4359,8 +4768,9 @@ msgstr "" #: src/pattern-matching/let-control-flow.md msgid "" -"`if-let`s can pile up, as shown. The `let-else` construct supports flattening this nested code. Rewrite the awkward " -"version for students, so they can see the transformation." +"`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/pattern-matching/let-control-flow.md @@ -4372,13 +4782,16 @@ msgid "while-let" msgstr "" #: src/pattern-matching/let-control-flow.md -msgid "Point out that the `while let` loop will keep going as long as the value matches the pattern." +msgid "" +"Point out that the `while let` loop will keep going as long as the value " +"matches the pattern." msgstr "" #: src/pattern-matching/let-control-flow.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 `name.pop()`. The `while let` provides syntactic sugar for the above scenario." +"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/pattern-matching/exercise.md @@ -4387,29 +4800,33 @@ msgstr "" #: 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)`." +"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/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." +"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/pattern-matching/exercise.md 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. You can also skip a test temporarily with " -"`#[ignore]`:" +"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/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?" +"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/pattern-matching/exercise.md src/pattern-matching/solution.md @@ -4449,11 +4866,14 @@ msgid "[Deriving](./methods-and-traits/deriving.md) (3 minutes)" msgstr "" #: src/methods-and-traits.md -msgid "[Exercise: Generic Logger](./methods-and-traits/exercise.md) (20 minutes)" +msgid "" +"[Exercise: Generic Logger](./methods-and-traits/exercise.md) (20 minutes)" msgstr "" #: src/methods-and-traits/methods.md -msgid "Rust allows you to associate functions with your new types. You do this with an `impl` block:" +msgid "" +"Rust allows you to associate functions with your new types. You do this with " +"an `impl` block:" msgstr "" #: src/methods-and-traits/methods.md @@ -4494,27 +4914,28 @@ msgstr "" #: src/methods-and-traits/methods.md msgid "" -"The `self` arguments specify the \"receiver\" - the object the method acts on. There are several common receivers for a " -"method:" +"The `self` arguments specify the \"receiver\" - the object the method acts " +"on. There are several common receivers for a method:" msgstr "" #: src/methods-and-traits/methods.md msgid "" -"`&self`: borrows the object from the caller using a shared and immutable reference. The object can be used again " -"afterwards." +"`&self`: borrows the object from the caller using a shared and immutable " +"reference. The object can be used again afterwards." msgstr "" #: src/methods-and-traits/methods.md msgid "" -"`&mut self`: borrows the object from the caller using a unique and mutable reference. The object can be used again " -"afterwards." +"`&mut self`: borrows the object from the caller using a unique and mutable " +"reference. The object can be used again afterwards." msgstr "" #: src/methods-and-traits/methods.md 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." +"`self`: takes ownership of the object and moves it away from the caller. The " +"method becomes the owner of the object. The object will be dropped " +"(deallocated) when the method returns, unless its ownership is explicitly " +"transmitted. Complete ownership does not automatically mean mutability." msgstr "" #: src/methods-and-traits/methods.md @@ -4523,8 +4944,8 @@ msgstr "" #: src/methods-and-traits/methods.md msgid "" -"No receiver: this becomes a static method on the struct. Typically used to create constructors which are called `new` by " -"convention." +"No receiver: this becomes a static method on the struct. Typically used to " +"create constructors which are called `new` by convention." msgstr "" #: src/methods-and-traits/methods.md @@ -4533,14 +4954,15 @@ msgstr "" #: src/methods-and-traits/methods.md msgid "" -"Methods are called on an instance of a type (such as a struct or enum), the first parameter represents the instance as " -"`self`." +"Methods are called on an instance of a type (such as a struct or enum), the " +"first parameter represents the instance as `self`." msgstr "" #: src/methods-and-traits/methods.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." +"Developers may choose to use methods to take advantage of method receiver " +"syntax and to help keep them more organized. By using methods we can keep " +"all the implementation code in one predictable place." msgstr "" #: src/methods-and-traits/methods.md @@ -4548,29 +4970,39 @@ msgid "Point out the use of the keyword `self`, a method receiver." msgstr "" #: 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." +msgid "" +"Show that it is an abbreviated term for `self: Self` and perhaps show how " +"the struct name could also be used." msgstr "" #: src/methods-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." +msgid "" +"Explain that `Self` is a type alias for the type the `impl` block is in and " +"can be used elsewhere in the block." msgstr "" #: src/methods-and-traits/methods.md -msgid "Note how `self` is used like other structs and dot notation can be used to refer to individual fields." +msgid "" +"Note how `self` is used like other structs and dot notation can be used to " +"refer to individual fields." msgstr "" #: 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." +msgid "" +"This might be a good time to demonstrate how the `&self` differs from `self` " +"by trying to run `finish` twice." msgstr "" #: src/methods-and-traits/methods.md 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`." +"Beyond variants on `self`, there are also [special wrapper types](https://" +"doc.rust-lang.org/reference/special-types-and-traits.html) allowed to be " +"receiver types, such as `Box`." msgstr "" #: src/methods-and-traits/traits.md -msgid "Rust lets you abstract over types with traits. They're similar to interfaces:" +msgid "" +"Rust lets you abstract over types with traits. They're similar to interfaces:" msgstr "" #: src/methods-and-traits/traits.md @@ -4582,13 +5014,15 @@ msgid "/// Print a string to the terminal greeting this pet.\n" msgstr "" #: src/methods-and-traits/traits.md -msgid "A trait defines a number of methods that types must have in order to implement the trait." +msgid "" +"A trait defines a number of methods that types must have in order to " +"implement the trait." msgstr "" #: src/methods-and-traits/traits.md msgid "" -"In the \"Generics\" segment, next, we will see how to build functionality that is generic over all types implementing a " -"trait." +"In the \"Generics\" segment, next, we will see how to build functionality " +"that is generic over all types implementing a trait." msgstr "" #: src/methods-and-traits/traits/implementing.md @@ -4599,37 +5033,45 @@ msgstr "" msgid "\"Oh you're a cutie! What's your name? {}\"" msgstr "" -#: src/methods-and-traits/traits/implementing.md src/smart-pointers/trait-objects.md +#: src/methods-and-traits/traits/implementing.md +#: src/smart-pointers/trait-objects.md msgid "\"Woof, my name is {}!\"" msgstr "" -#: src/methods-and-traits/traits/implementing.md src/smart-pointers/trait-objects.md +#: src/methods-and-traits/traits/implementing.md +#: src/smart-pointers/trait-objects.md msgid "\"Fido\"" msgstr "" #: src/methods-and-traits/traits/implementing.md -msgid "To implement `Trait` for `Type`, you use an `impl Trait for Type { .. }` block." +msgid "" +"To implement `Trait` for `Type`, you use an `impl Trait for Type { .. }` " +"block." msgstr "" #: src/methods-and-traits/traits/implementing.md msgid "" -"Unlike Go interfaces, just having matching methods is not enough: a `Cat` type with a `talk()` method would not " -"automatically satisfy `Pet` unless it is in an `impl Pet` block." +"Unlike Go interfaces, just having matching methods is not enough: a `Cat` " +"type with a `talk()` method would not automatically satisfy `Pet` unless it " +"is in an `impl Pet` block." msgstr "" #: src/methods-and-traits/traits/implementing.md msgid "" -"Traits may provide default implementations of some methods. Default implementations can rely on all the methods of the " -"trait. In this case, `greet` is provided, and relies on `talk`." +"Traits may provide default implementations of some methods. Default " +"implementations can rely on all the methods of the trait. In this case, " +"`greet` is provided, and relies on `talk`." msgstr "" #: src/methods-and-traits/traits/supertraits.md msgid "" -"A trait can require that types implementing it also implement other traits, called _supertraits_. Here, any type " -"implementing `Pet` must implement `Animal`." +"A trait can require that types implementing it also implement other traits, " +"called _supertraits_. Here, any type implementing `Pet` must implement " +"`Animal`." msgstr "" -#: src/methods-and-traits/traits/supertraits.md src/async/control-flow/select.md +#: src/methods-and-traits/traits/supertraits.md +#: src/async/control-flow/select.md msgid "\"Rex\"" msgstr "" @@ -4639,30 +5081,38 @@ msgstr "" #: src/methods-and-traits/traits/supertraits.md msgid "" -"This is sometimes called \"trait inheritance\" but students should not expect this to behave like OO inheritance. It just " -"specifies an additional requirement on implementations of a trait." +"This is sometimes called \"trait inheritance\" but students should not " +"expect this to behave like OO inheritance. It just specifies an additional " +"requirement on implementations of a trait." msgstr "" #: src/methods-and-traits/traits/associated-types.md -msgid "Associated types are placeholder types which are supplied by the trait implementation." +msgid "" +"Associated types are placeholder types which are supplied by the trait " +"implementation." msgstr "" -#: src/methods-and-traits/traits/associated-types.md src/async/control-flow/join.md +#: src/methods-and-traits/traits/associated-types.md +#: src/async/control-flow/join.md msgid "\"{:?}\"" msgstr "" #: src/methods-and-traits/traits/associated-types.md msgid "" -"Associated types are sometimes also called \"output types\". The key observation is that the implementer, not the caller, " -"chooses this type." +"Associated types are sometimes also called \"output types\". The key " +"observation is that the implementer, not the caller, chooses this type." msgstr "" #: src/methods-and-traits/traits/associated-types.md -msgid "Many standard library traits have associated types, including arithmetic operators and `Iterator`." +msgid "" +"Many standard library traits have associated types, including arithmetic " +"operators and `Iterator`." msgstr "" #: src/methods-and-traits/deriving.md -msgid "Supported traits can be automatically implemented for your custom types, as follows:" +msgid "" +"Supported traits can be automatically implemented for your custom types, as " +"follows:" msgstr "" #: src/methods-and-traits/deriving.md @@ -4687,8 +5137,9 @@ msgstr "" #: src/methods-and-traits/deriving.md msgid "" -"Derivation is implemented with macros, and many crates provide useful derive macros to add useful functionality. For " -"example, `serde` can derive serialization support for a struct using `#[derive(Serialize)]`." +"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/methods-and-traits/exercise.md @@ -4697,21 +5148,24 @@ msgstr "" #: 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." +"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/methods-and-traits/exercise.md msgid "" -"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." +"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/methods-and-traits/exercise.md msgid "" -"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?" +"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/methods-and-traits/exercise.md src/methods-and-traits/solution.md @@ -4760,8 +5214,8 @@ msgstr "" #: src/generics/generic-functions.md msgid "" -"Rust supports generics, which lets you abstract algorithms or data structures (such as sorting or a binary tree) over the " -"types used or stored." +"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/generics/generic-functions.md @@ -4785,20 +5239,25 @@ msgid "\"cat\"" msgstr "" #: src/generics/generic-functions.md -msgid "Rust infers a type for T based on the types of the arguments and return value." +msgid "" +"Rust infers a type for T based on the types of the arguments and return " +"value." msgstr "" #: src/generics/generic-functions.md msgid "" -"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." +"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/generics/generic-functions.md msgid "" -"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." +"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/generics/generic-data.md @@ -4818,11 +5277,15 @@ msgid "\"coords: {:?}\"" msgstr "" #: src/generics/generic-data.md -msgid "_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that redundant?" +msgid "" +"_Q:_ Why `T` is specified twice in `impl Point {}`? Isn't that " +"redundant?" msgstr "" #: src/generics/generic-data.md -msgid "This is because it is a generic implementation section for generic type. They are independently generic." +msgid "" +"This is because it is a generic implementation section for generic type. " +"They are independently generic." msgstr "" #: src/generics/generic-data.md @@ -4835,17 +5298,21 @@ msgstr "" #: src/generics/generic-data.md msgid "" -"`Point` is still generic and you can use `Point`, but methods in this block will only be available for `Point`." +"`Point` is still generic and you can use `Point`, but methods in this " +"block will only be available for `Point`." msgstr "" #: src/generics/generic-data.md msgid "" -"Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`. Update the code to allow points that have elements of " -"different types, by using two type variables, e.g., `T` and `U`." +"Try declaring a new variable `let p = Point { x: 5, y: 10.0 };`. Update the " +"code to allow points that have elements of different types, by using two " +"type variables, e.g., `T` and `U`." msgstr "" #: src/generics/generic-traits.md -msgid "Traits can also be generic, just like types and functions. A trait's parameters get concrete types when it is used." +msgid "" +"Traits can also be generic, just like types and functions. A trait's " +"parameters get concrete types when it is used." msgstr "" #: src/generics/generic-traits.md @@ -4862,33 +5329,38 @@ msgstr "" #: src/generics/generic-traits.md msgid "" -"The `From` trait will be covered later in the course, but its [definition in the `std` docs](https://doc.rust-lang.org/std/" -"convert/trait.From.html) is simple." +"The `From` trait will be covered later in the course, but its [definition in " +"the `std` docs](https://doc.rust-lang.org/std/convert/trait.From.html) is " +"simple." msgstr "" #: src/generics/generic-traits.md msgid "" -"Implementations of the trait do not need to cover all possible type parameters. Here, `Foo::From(\"hello\")` would not " -"compile because there is no `From<&str>` implementation for `Foo`." +"Implementations of the trait do not need to cover all possible type " +"parameters. Here, `Foo::From(\"hello\")` would not compile because there is " +"no `From<&str>` implementation for `Foo`." msgstr "" #: src/generics/generic-traits.md msgid "" -"Generic traits take types as \"input\", while associated types are a kind of \"output type. A trait can have multiple " -"implementations for different input types." +"Generic traits take types as \"input\", while associated types are a kind of " +"\"output type. A trait can have multiple implementations for different input " +"types." msgstr "" #: src/generics/generic-traits.md msgid "" -"In fact, Rust requires that at most one implementation of a trait match for any type T. Unlike some other languages, Rust " -"has no heuristic for choosing the \"most specific\" match. There is work on adding this support, called [specialization]" -"(https://rust-lang.github.io/rfcs/1210-impl-specialization.html)." +"In fact, Rust requires that at most one implementation of a trait match for " +"any type T. Unlike some other languages, Rust has no heuristic for choosing " +"the \"most specific\" match. There is work on adding this support, called " +"[specialization](https://rust-lang.github.io/rfcs/1210-impl-specialization." +"html)." msgstr "" #: src/generics/trait-bounds.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." +"When working with generics, you often want to require the types to implement " +"some trait, so that you can call this trait's methods." msgstr "" #: src/generics/trait-bounds.md @@ -4924,17 +5396,21 @@ msgid "It has additional features making it more powerful." msgstr "" #: src/generics/trait-bounds.md -msgid "If someone asks, the extra feature is that the type on the left of \":\" can be arbitrary, like `Option`." +msgid "" +"If someone asks, the extra feature is that the type on the left of \":\" can " +"be arbitrary, like `Option`." msgstr "" #: src/generics/trait-bounds.md msgid "" -"Note that Rust does not (yet) support specialization. For example, given the original `duplicate`, it is invalid to add a " -"specialized `duplicate(a: u32)`." +"Note that Rust does not (yet) support specialization. For example, given the " +"original `duplicate`, it is invalid to add a specialized `duplicate(a: u32)`." msgstr "" #: src/generics/impl-trait.md -msgid "Similar to trait bounds, an `impl Trait` syntax can be used in function arguments and return values:" +msgid "" +"Similar to trait bounds, an `impl Trait` syntax can be used in function " +"arguments and return values:" msgstr "" #: src/generics/impl-trait.md @@ -4957,43 +5433,52 @@ msgstr "" #: src/generics/impl-trait.md msgid "" -"`impl Trait` allows you to work with types which you cannot name. The meaning of `impl Trait` is a bit different in the " -"different positions." +"`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/generics/impl-trait.md -msgid "For a parameter, `impl Trait` is like an anonymous generic parameter with a trait bound." +msgid "" +"For a parameter, `impl Trait` is like an anonymous generic parameter with a " +"trait bound." msgstr "" #: src/generics/impl-trait.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." +"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/generics/impl-trait.md 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::" +"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/generics/impl-trait.md -msgid "What is the type of `debuggable`? Try `let debuggable: () = ..` to see what the error message shows." +msgid "" +"What is the type of `debuggable`? Try `let debuggable: () = ..` to see what " +"the error message shows." msgstr "" #: src/generics/exercise.md msgid "" -"In this short exercise, you will implement a generic `min` function that determines the minimum of two values, using the " -"[`Ord`](https://doc.rust-lang.org/stable/std/cmp/trait.Ord.html) trait." +"In this short exercise, you will implement a generic `min` function that " +"determines the minimum of two values, using the [`Ord`](https://doc.rust-" +"lang.org/stable/std/cmp/trait.Ord.html) trait." msgstr "" #: src/generics/exercise.md msgid "// TODO: implement the `min` function used in `main`.\n" msgstr "" -#: src/generics/exercise.md src/generics/solution.md src/error-handling/exercise.md src/error-handling/solution.md +#: src/generics/exercise.md src/generics/solution.md +#: src/error-handling/exercise.md src/error-handling/solution.md msgid "'z'" msgstr "" @@ -5019,8 +5504,9 @@ msgstr "" #: src/generics/exercise.md msgid "" -"Show students the [`Ord`](https://doc.rust-lang.org/stable/std/cmp/trait.Ord.html) trait and [`Ordering`](https://doc.rust-" -"lang.org/stable/std/cmp/enum.Ordering.html) enum." +"Show students the [`Ord`](https://doc.rust-lang.org/stable/std/cmp/trait.Ord." +"html) trait and [`Ordering`](https://doc.rust-lang.org/stable/std/cmp/enum." +"Ordering.html) enum." msgstr "" #: src/welcome-day-2-afternoon.md @@ -5032,7 +5518,9 @@ msgid "[Standard Library Traits](./std-traits.md) (1 hour and 40 minutes)" msgstr "" #: src/welcome-day-2-afternoon.md -msgid "Including 10 minute breaks, this session should take about 3 hours and 10 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 3 hours and 10 " +"minutes" msgstr "" #: src/std-types.md @@ -5073,32 +5561,38 @@ msgstr "" #: src/std-types.md msgid "" -"For each of the slides in this section, spend some time reviewing the documentation pages, highlighting some of the more " -"common methods." +"For each of the slides in this section, spend some time reviewing the " +"documentation pages, highlighting some of the more common methods." msgstr "" #: src/std-types/std.md 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." +"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/std-types/std.md -msgid "In fact, Rust contains several layers of the Standard Library: `core`, `alloc` and `std`." +msgid "" +"In fact, Rust contains several layers of the Standard Library: `core`, " +"`alloc` and `std`." msgstr "" #: 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." +"`core` includes the most basic types and functions that don't depend on " +"`libc`, allocator or even the presence of an operating system." msgstr "" #: src/std-types/std.md -msgid "`alloc` includes types which require a global heap allocator, such as `Vec`, `Box` and `Arc`." +msgid "" +"`alloc` includes types which require a global heap allocator, such as `Vec`, " +"`Box` and `Arc`." msgstr "" #: src/std-types/std.md -msgid "Embedded Rust applications often only use `core`, and sometimes `alloc`." +msgid "" +"Embedded Rust applications often only use `core`, and sometimes `alloc`." msgstr "" #: src/std-types/docs.md @@ -5106,17 +5600,22 @@ msgid "Rust comes with extensive documentation. For example:" msgstr "" #: src/std-types/docs.md -msgid "All of the details about [loops](https://doc.rust-lang.org/stable/reference/expressions/loop-expr.html)." +msgid "" +"All of the details about [loops](https://doc.rust-lang.org/stable/reference/" +"expressions/loop-expr.html)." msgstr "" #: src/std-types/docs.md -msgid "Primitive types like [`u8`](https://doc.rust-lang.org/stable/std/primitive.u8.html)." +msgid "" +"Primitive types like [`u8`](https://doc.rust-lang.org/stable/std/primitive." +"u8.html)." msgstr "" #: src/std-types/docs.md msgid "" -"Standard library types like [`Option`](https://doc.rust-lang.org/stable/std/option/enum.Option.html) or [`BinaryHeap`]" -"(https://doc.rust-lang.org/stable/std/collections/struct.BinaryHeap.html)." +"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 @@ -5125,30 +5624,36 @@ msgstr "" #: src/std-types/docs.md msgid "" -"/// Determine whether the first argument is divisible by the second argument.\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/std-types/docs.md msgid "" -"The contents are treated as Markdown. All published Rust library crates are automatically documented at [`docs.rs`]" -"(https://docs.rs) using the [rustdoc](https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html) tool. It is idiomatic to " -"document all public items in an API using this pattern." +"The 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/std-types/docs.md msgid "" -"To document an item from inside the item (such as inside a module), use `//!` or `/*! .. */`, called \"inner doc " -"comments\":" +"To document an item from inside the item (such as inside a module), use `//!" +"` or `/*! .. */`, called \"inner doc comments\":" msgstr "" #: src/std-types/docs.md -msgid "//! This module contains functionality relating to divisibility of integers.\n" +msgid "" +"//! This module contains functionality relating to divisibility of " +"integers.\n" msgstr "" #: src/std-types/docs.md -msgid "Show students the generated docs for the `rand` crate at ." +msgid "" +"Show students the generated docs for the `rand` crate at ." msgstr "" #: src/std-types/option.md @@ -5157,8 +5662,9 @@ msgstr "" #: src/std-types/option.md msgid "" -"We have already seen some use of `Option`. It stores either a value of type `T` or nothing. For example, [`String::" -"find`](https://doc.rust-lang.org/stable/std/string/struct.String.html#method.find) returns an `Option`." +"We have already seen some use of `Option`. It stores either a value of " +"type `T` or nothing. For example, [`String::find`](https://doc.rust-lang.org/" +"stable/std/string/struct.String.html#method.find) returns an `Option`." msgstr "" #: src/std-types/option.md @@ -5186,21 +5692,27 @@ msgid "`Option` is widely used, not just in the standard library." msgstr "" #: src/std-types/option.md -msgid "`unwrap` will return the value in an `Option`, or panic. `expect` is similar but takes an error message." +msgid "" +"`unwrap` will return the value in an `Option`, or panic. `expect` is similar " +"but takes an error message." msgstr "" #: src/std-types/option.md -msgid "You can panic on None, but you can't \"accidentally\" forget to check for None." +msgid "" +"You can panic on None, but you can't \"accidentally\" forget to check for " +"None." msgstr "" #: src/std-types/option.md msgid "" -"It's common to `unwrap`/`expect` all over the place when hacking something together, but production code typically handles " -"`None` in a nicer fashion." +"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-types/option.md -msgid "The niche optimization means that `Option` often has the same size in memory as `T`." +msgid "" +"The niche optimization means that `Option` often has the same size in " +"memory as `T`." msgstr "" #: src/std-types/result.md @@ -5209,9 +5721,10 @@ msgstr "" #: 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." +"`Result` is similar to `Option`, but indicates the success or failure of an " +"operation, each with a different type. This is similar to the `Res` defined " +"in the expression exercise, but generic: `Result` where `T` is used in " +"the `Ok` variant and `E` appears in the `Err` variant." msgstr "" #: src/std-types/result.md @@ -5232,19 +5745,23 @@ msgstr "" #: src/std-types/result.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." +"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-types/result.md 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." +"`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-types/result.md -msgid "`Result` is the standard type to implement error handling as we will see on Day 4." +msgid "" +"`Result` is the standard type to implement error handling as we will see on " +"Day 4." msgstr "" #: src/std-types/string.md @@ -5253,11 +5770,12 @@ msgstr "" #: 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:" +"[`String`](https://doc.rust-lang.org/std/string/struct.String.html) is the " +"standard heap-allocated growable UTF-8 string buffer:" msgstr "" -#: src/std-types/string.md src/std-traits/read-and-write.md src/memory-management/review.md src/testing/unit-tests.md +#: 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 "" @@ -5284,43 +5802,53 @@ 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`." +"`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-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." +"`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-types/string.md -msgid "`String::len` returns the size of the `String` in bytes (which can be different from its length in characters)." +msgid "" +"`String::len` returns the size of the `String` in bytes (which can be " +"different from its length in characters)." msgstr "" #: 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 to [grapheme clusters](https://docs.rs/unicode-segmentation/latest/unicode_segmentation/" -"struct.Graphemes.html)." +"`String::chars` returns an iterator over the actual characters. Note that a " +"`char` can be different from what a human will consider a \"character\" due " +"to [grapheme clusters](https://docs.rs/unicode-segmentation/latest/" +"unicode_segmentation/struct.Graphemes.html)." msgstr "" #: src/std-types/string.md -msgid "When people refer to strings they could either be talking about `&str` or `String`." +msgid "" +"When people refer to strings they could either be talking about `&str` or " +"`String`." msgstr "" #: src/std-types/string.md -msgid "When a type implements `Deref`, the compiler will let you transparently call methods from `T`." +msgid "" +"When a type implements `Deref`, the compiler will let you " +"transparently call methods from `T`." msgstr "" #: 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." +"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." +msgid "" +"`String` implements `Deref` which transparently gives it " +"access to `str`'s methods." msgstr "" #: src/std-types/string.md @@ -5329,8 +5857,9 @@ msgstr "" #: 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." +"`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-types/string.md @@ -5338,22 +5867,30 @@ msgid "Compare the different ways to index a `String`:" msgstr "" #: src/std-types/string.md -msgid "To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, out-of-bounds." +msgid "" +"To a character by using `s3.chars().nth(i).unwrap()` where `i` is in-bound, " +"out-of-bounds." msgstr "" #: src/std-types/string.md -msgid "To a substring by using `s3[0..4]`, where that slice is on character boundaries or not." +msgid "" +"To a substring by using `s3[0..4]`, where that slice is on character " +"boundaries or not." msgstr "" #: src/std-types/string.md msgid "" -"Many types can be converted to a string with the [`to_string`](https://doc.rust-lang.org/std/string/trait.ToString." -"html#tymethod.to_string) method. This trait is automatically implemented for all types that implement `Display`, so " -"anything that can be formatted can also be converted to a string." +"Many types can be converted to a string with the [`to_string`](https://doc." +"rust-lang.org/std/string/trait.ToString.html#tymethod.to_string) method. " +"This trait is automatically implemented for all types that implement " +"`Display`, so anything that can be formatted can also be converted to a " +"string." msgstr "" #: src/std-types/vec.md -msgid "[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard resizable heap-allocated buffer:" +msgid "" +"[`Vec`](https://doc.rust-lang.org/std/vec/struct.Vec.html) is the standard " +"resizable heap-allocated buffer:" msgstr "" #: src/std-types/vec.md @@ -5382,37 +5919,42 @@ msgstr "" #: 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`." +"`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-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." +"`Vec` is a type of collection, along with `String` and `HashMap`. The data " +"it contains is stored on the heap. This means the amount of data doesn't " +"need to be known at compile time. It can grow or shrink at runtime." msgstr "" #: src/std-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." +"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-types/vec.md msgid "" -"`vec![...]` is a canonical macro to use instead of `Vec::new()` and it supports adding initial elements to the vector." +"`vec![...]` is a canonical macro to use instead of `Vec::new()` and it " +"supports adding initial elements to the vector." msgstr "" #: 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." +"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-types/vec.md msgid "" -"Slices are covered on day 3. For now, students only need to know that a value of type `Vec` gives access to all of the " -"documented slice methods, too." +"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-types/hashmap.md @@ -5460,13 +6002,15 @@ msgid "\"{page_counts:#?}\"" msgstr "" #: src/std-types/hashmap.md -msgid "`HashMap` is not defined in the prelude and needs to be brought into scope." +msgid "" +"`HashMap` is not defined in the prelude and needs to be brought into scope." msgstr "" #: 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." +"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-types/hashmap.md @@ -5483,54 +6027,64 @@ msgstr "" #: 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-From%3C%5B(K,+V);+N%5D%3E-for-HashMap%3CK,+V,+RandomState%3E), which allows us to easily " -"initialize a hash map from a literal array:" +"Although, since Rust 1.56, HashMap implements [`From<[(K, V); N]>`](https://" +"doc.rust-lang.org/std/collections/hash_map/struct.HashMap.html#impl-From%3C" +"%5B(K,+V);+N%5D%3E-for-HashMap%3CK,+V,+RandomState%3E), which allows us to " +"easily initialize a hash map from a literal array:" msgstr "" #: src/std-types/hashmap.md -msgid "Alternatively HashMap can be built from any `Iterator` which yields key-value tuples." +msgid "" +"Alternatively HashMap can be built from any `Iterator` which yields key-" +"value tuples." msgstr "" #: 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." +"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-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?" +"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-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 Rust docs. Show students the docs for this type, and the helpful link back to the `keys` method." +"This type has several \"method-specific\" return types, such as `std::" +"collections::hash_map::Keys`. These types often appear in searches of the " +"Rust docs. Show students the docs for this type, and the helpful link back " +"to the `keys` method." msgstr "" #: src/std-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." +"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-types/exercise.md msgid "" -"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." +"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-types/exercise.md msgid "" -"If you finish early, try using the [`entry`](https://doc.rust-lang.org/stable/std/collections/struct.HashMap.html#method." -"entry) method to halve the number of hash lookups required to implement the `count` method." +"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-types/exercise.md src/std-types/solution.md -msgid "/// Counter counts the number of times each value of type T has been seen.\n" +msgid "" +"/// Counter counts the number of times each value of type T has been seen.\n" msgstr "" #: src/std-types/exercise.md src/std-types/solution.md @@ -5598,7 +6152,9 @@ msgid "This segment should take about 1 hour and 40 minutes" msgstr "" #: src/std-traits.md -msgid "As with the standard-library types, spend time reviewing the documentation for each trait." +msgid "" +"As with the standard-library types, spend time reviewing the documentation " +"for each trait." msgstr "" #: src/std-traits.md @@ -5607,8 +6163,8 @@ msgstr "" #: src/std-traits/comparisons.md msgid "" -"These traits support comparisons between values. All traits can be derived for types containing fields that implement " -"these traits." +"These traits support comparisons between values. All traits can be derived " +"for types containing fields that implement these traits." msgstr "" #: src/std-traits/comparisons.md @@ -5617,14 +6173,15 @@ msgstr "" #: 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." +"`PartialEq` is a partial equivalence relation, with required method `eq` and " +"provided method `ne`. The `==` and `!=` operators will call these methods." msgstr "" #: src/std-traits/comparisons.md msgid "" -"`Eq` is a full equivalence relation (reflexive, symmetric, and transitive) and implies `PartialEq`. Functions that require " -"full equivalence will use `Eq` as a trait bound." +"`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 @@ -5633,8 +6190,8 @@ msgstr "" #: src/std-traits/comparisons.md msgid "" -"`PartialOrd` defines a partial ordering, with a `partial_cmp` method. It is used to implement the `<`, `<=`, `>=`, and `>` " -"operators." +"`PartialOrd` defines a partial ordering, with a `partial_cmp` method. It is " +"used to implement the `<`, `<=`, `>=`, and `>` operators." msgstr "" #: src/std-traits/comparisons.md @@ -5642,15 +6199,21 @@ msgid "`Ord` is a total ordering, with `cmp` returning `Ordering`." msgstr "" #: src/std-traits/comparisons.md -msgid "`PartialEq` can be implemented between different types, but `Eq` cannot, because it is reflexive:" +msgid "" +"`PartialEq` can be implemented between different types, but `Eq` cannot, " +"because it is reflexive:" msgstr "" #: src/std-traits/comparisons.md -msgid "In practice, it's common to derive these traits, but uncommon to implement them." +msgid "" +"In practice, it's common to derive these traits, but uncommon to implement " +"them." msgstr "" #: src/std-traits/operators.md -msgid "Operator overloading is implemented via traits in [`std::ops`](https://doc.rust-lang.org/std/ops/index.html):" +msgid "" +"Operator overloading is implemented via traits in [`std::ops`](https://doc." +"rust-lang.org/std/ops/index.html):" msgstr "" #: src/std-traits/operators.md @@ -5662,34 +6225,41 @@ msgid "Discussion points:" msgstr "" #: src/std-traits/operators.md -msgid "You could implement `Add` for `&Point`. In which situations is that useful?" +msgid "" +"You could implement `Add` for `&Point`. In which situations is that useful?" msgstr "" #: src/std-traits/operators.md 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." +"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-traits/operators.md -msgid "Why is `Output` an associated type? Could it be made a type parameter of the method?" +msgid "" +"Why is `Output` an associated type? Could it be made a type parameter of the " +"method?" msgstr "" #: src/std-traits/operators.md msgid "" -"Short answer: Function type parameters are controlled by the caller, but associated types (like `Output`) are controlled " -"by the implementer of a trait." +"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-traits/operators.md msgid "" -"You could implement `Add` for two different types, e.g. `impl Add<(i32, i32)> for Point` would add a tuple to a `Point`." +"You could implement `Add` for two different types, e.g. `impl Add<(i32, " +"i32)> for Point` would add a tuple to a `Point`." msgstr "" #: src/std-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:" +"Types implement [`From`](https://doc.rust-lang.org/std/convert/trait.From." +"html) and [`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) to " +"facilitate type conversions:" msgstr "" #: src/std-traits/from-and-into.md @@ -5698,25 +6268,29 @@ msgstr "" #: src/std-traits/from-and-into.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:" +"[`Into`](https://doc.rust-lang.org/std/convert/trait.Into.html) is " +"automatically implemented when [`From`](https://doc.rust-lang.org/std/" +"convert/trait.From.html) is implemented:" msgstr "" #: src/std-traits/from-and-into.md -msgid "That's why it is common to only implement `From`, as your type will get `Into` implementation too." +msgid "" +"That's why it is common to only implement `From`, as your type will get " +"`Into` implementation too." msgstr "" #: src/std-traits/from-and-into.md 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`." +"When declaring a function argument input type like \"anything that can be " +"converted into a `String`\", the rule is opposite, you should use `Into`. " +"Your function will accept types that implement `From` and those that _only_ " +"implement `Into`." msgstr "" #: src/std-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." +"Rust has no _implicit_ type conversions, but does support explicit casts " +"with `as`. These generally follow C semantics where those are defined." msgstr "" #: src/std-traits/casting.md @@ -5733,23 +6307,27 @@ msgstr "" #: src/std-traits/casting.md msgid "" -"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." +"The results of `as` are _always_ defined in Rust and consistent across " +"platforms. This might not match your intuition for changing sign or casting " +"to a smaller type -- check the docs, and comment for clarity." msgstr "" #: src/std-traits/casting.md msgid "" -"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)." +"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/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." +"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/std-traits/casting.md @@ -5758,8 +6336,9 @@ msgstr "" #: src/std-traits/casting.md msgid "" -"`as` is similar to a C++ static cast. Use of `as` in cases where data might be lost is generally discouraged, or at least " -"deserves an explanatory comment." +"`as` is similar to a C++ static cast. Use of `as` in cases where data might " +"be lost is generally discouraged, or at least deserves an explanatory " +"comment." msgstr "" #: src/std-traits/casting.md @@ -5768,8 +6347,9 @@ msgstr "" #: 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:" +"Using [`Read`](https://doc.rust-lang.org/std/io/trait.Read.html) and " +"[`BufRead`](https://doc.rust-lang.org/std/io/trait.BufRead.html), you can " +"abstract over `u8` sources:" msgstr "" #: src/std-traits/read-and-write.md @@ -5785,7 +6365,9 @@ msgid "\"lines in file: {}\"" msgstr "" #: 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:" +msgid "" +"Similarly, [`Write`](https://doc.rust-lang.org/std/io/trait.Write.html) lets " +"you abstract over `u8` sinks:" msgstr "" #: src/std-traits/read-and-write.md @@ -5801,7 +6383,9 @@ msgid "The `Default` Trait" msgstr "" #: src/std-traits/default.md -msgid "[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait produces a default value for a type." +msgid "" +"[`Default`](https://doc.rust-lang.org/std/default/trait.Default.html) trait " +"produces a default value for a type." msgstr "" #: src/std-traits/default.md @@ -5820,16 +6404,20 @@ msgstr "" msgid "\"{almost_default_struct:#?}\"" msgstr "" -#: src/std-traits/default.md src/lifetimes/exercise.md src/lifetimes/solution.md +#: src/std-traits/default.md src/lifetimes/exercise.md +#: src/lifetimes/solution.md msgid "\"{:#?}\"" msgstr "" #: src/std-traits/default.md -msgid "It can be implemented directly or it can be derived via `#[derive(Default)]`." +msgid "" +"It can be implemented directly or it can be derived via `#[derive(Default)]`." msgstr "" #: src/std-traits/default.md -msgid "A derived implementation will produce a value where all fields are set to their default values." +msgid "" +"A derived implementation will produce a value where all fields are set to " +"their default values." msgstr "" #: src/std-traits/default.md @@ -5837,7 +6425,9 @@ msgid "This means all types in the struct must implement `Default` too." msgstr "" #: src/std-traits/default.md -msgid "Standard Rust types often implement `Default` with reasonable values (e.g. `0`, `\"\"`, etc)." +msgid "" +"Standard Rust types often implement `Default` with reasonable values (e.g. " +"`0`, `\"\"`, etc)." msgstr "" #: src/std-traits/default.md @@ -5845,20 +6435,24 @@ msgid "The partial struct initialization works nicely with default." msgstr "" #: src/std-traits/default.md -msgid "The Rust standard library is aware that types can implement `Default` and provides convenience methods that use it." +msgid "" +"The Rust standard library is aware that types can implement `Default` and " +"provides convenience methods that use it." msgstr "" #: src/std-traits/default.md 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)." +"The `..` syntax is called [struct update syntax](https://doc.rust-lang.org/" +"book/ch05-01-defining-structs.html#creating-instances-from-other-instances-" +"with-struct-update-syntax)." msgstr "" #: src/std-traits/closures.md 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:" +"Closures or lambda expressions have types which cannot be named. However, " +"they implement special [`Fn`](https://doc.rust-lang.org/std/ops/trait.Fn." +"html), [`FnMut`](https://doc.rust-lang.org/std/ops/trait.FnMut.html), and " +"[`FnOnce`](https://doc.rust-lang.org/std/ops/trait.FnOnce.html) traits:" msgstr "" #: src/std-traits/closures.md @@ -5879,44 +6473,53 @@ msgstr "" #: src/std-traits/closures.md 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." +"An `Fn` (e.g. `add_3`) neither consumes nor mutates captured values, or " +"perhaps captures nothing at all. It can be called multiple times " +"concurrently." msgstr "" #: src/std-traits/closures.md -msgid "An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it multiple times, but not concurrently." +msgid "" +"An `FnMut` (e.g. `accumulate`) might mutate captured values. You can call it " +"multiple times, but not concurrently." msgstr "" #: 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." +msgid "" +"If you have an `FnOnce` (e.g. `multiply_sum`), you may only call it once. It " +"might consume captured values." msgstr "" #: src/std-traits/closures.md 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." +"`FnMut` is a subtype of `FnOnce`. `Fn` is a subtype of `FnMut` and `FnOnce`. " +"I.e. you can use an `FnMut` wherever an `FnOnce` is called for, and you can " +"use an `Fn` wherever an `FnMut` or `FnOnce` is called for." msgstr "" #: src/std-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." +"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/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`." +"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/std-traits/closures.md msgid "" -"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. `multiply_sum`), depending on what the closure " -"captures." +"The compiler also infers `Copy` (e.g. for `add_3`) and `Clone` (e.g. " +"`multiply_sum`), depending on what the closure captures." msgstr "" #: src/std-traits/closures.md -msgid "By default, closures will capture by reference if they can. The `move` keyword makes them capture by value." +msgid "" +"By default, closures will capture by reference if they can. The `move` " +"keyword makes them capture by value." msgstr "" #: src/std-traits/closures.md src/smart-pointers/trait-objects.md @@ -5933,9 +6536,10 @@ msgstr "" #: src/std-traits/exercise.md msgid "" -"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." +"In this example, you will implement the classic [\"ROT13\" cipher](https://" +"en.wikipedia.org/wiki/ROT13). Copy this code to the playground, and " +"implement the missing bits. Only rotate ASCII alphabetic characters, to " +"ensure the result is still valid UTF-8." msgstr "" #: src/std-traits/exercise.md @@ -5951,7 +6555,9 @@ msgid "\"To get to the other side!\"" msgstr "" #: src/std-traits/exercise.md -msgid "What happens if you chain two `RotDecoder` instances together, each rotating by 13 characters?" +msgid "" +"What happens if you chain two `RotDecoder` instances together, each rotating " +"by 13 characters?" msgstr "" #: src/std-traits/solution.md @@ -5967,7 +6573,9 @@ msgid "Today, we will cover:" msgstr "" #: src/welcome-day-3.md -msgid "Memory management, lifetimes, and the borrow checker: how Rust ensures memory safety." +msgid "" +"Memory management, lifetimes, and the borrow checker: how Rust ensures " +"memory safety." msgstr "" #: src/welcome-day-3.md @@ -5987,7 +6595,9 @@ msgid "[Smart Pointers](./smart-pointers.md) (55 minutes)" msgstr "" #: src/welcome-day-3.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 20 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 20 " +"minutes" msgstr "" #: src/memory-management.md @@ -5995,7 +6605,9 @@ msgid "[Review of Program Memory](./memory-management/review.md) (5 minutes)" msgstr "" #: src/memory-management.md -msgid "[Approaches to Memory Management](./memory-management/approaches.md) (10 minutes)" +msgid "" +"[Approaches to Memory Management](./memory-management/approaches.md) (10 " +"minutes)" msgstr "" #: src/memory-management.md @@ -6064,24 +6676,28 @@ msgstr "" #: src/memory-management/review.md msgid "" -"Creating a `String` puts fixed-sized metadata on the stack and dynamically sized data, the actual string, on the heap:" +"Creating a `String` puts fixed-sized metadata on the stack and dynamically " +"sized data, the actual string, on the heap:" msgstr "" #: src/memory-management/review.md 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." +"Mention that a `String` is backed by a `Vec`, so it has a capacity and " +"length and can grow if mutable via reallocation on the heap." msgstr "" #: src/memory-management/review.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)" +"If students ask about it, you can mention that the underlying memory is heap " +"allocated using the [System Allocator](https://doc.rust-lang.org/std/alloc/" +"struct.System.html) and custom allocators can be implemented using the " +"[Allocator API](https://doc.rust-lang.org/std/alloc/index.html)" msgstr "" #: src/memory-management/review.md -msgid "We can inspect the memory layout with `unsafe` Rust. However, you should point out that this is rightfully unsafe!" +msgid "" +"We can inspect the memory layout with `unsafe` Rust. However, you should " +"point out that this is rightfully unsafe!" msgstr "" #: src/memory-management/review.md src/testing/unit-tests.md @@ -6095,7 +6711,8 @@ msgstr "" #: src/memory-management/review.md msgid "" "// DON'T DO THIS AT HOME! For educational purposes only.\n" -" // String provides no guarantees about its layout, so this could lead to\n" +" // String provides no guarantees about its layout, so this could lead " +"to\n" " // undefined behavior.\n" msgstr "" @@ -6116,7 +6733,8 @@ msgid "Programmer decides when to allocate or free heap memory." msgstr "" #: src/memory-management/approaches.md -msgid "Programmer must determine whether a pointer still points to valid memory." +msgid "" +"Programmer must determine whether a pointer still points to valid memory." msgstr "" #: src/memory-management/approaches.md @@ -6124,15 +6742,20 @@ msgid "Studies show, programmers make mistakes." msgstr "" #: src/memory-management/approaches.md -msgid "Full safety via automatic memory management at runtime: Java, Python, Go, Haskell, ..." +msgid "" +"Full safety via automatic memory management at runtime: Java, Python, Go, " +"Haskell, ..." msgstr "" #: src/memory-management/approaches.md -msgid "A runtime system ensures that memory is not freed until it can no longer be referenced." +msgid "" +"A runtime system ensures that memory is not freed until it can no longer be " +"referenced." msgstr "" #: src/memory-management/approaches.md -msgid "Typically implemented with reference counting, garbage collection, or RAII." +msgid "" +"Typically implemented with reference counting, garbage collection, or RAII." msgstr "" #: src/memory-management/approaches.md @@ -6140,7 +6763,9 @@ msgid "Rust offers a new mix:" msgstr "" #: src/memory-management/approaches.md -msgid "Full control _and_ safety via compile time enforcement of correct memory management." +msgid "" +"Full control _and_ safety via compile time enforcement of correct memory " +"management." msgstr "" #: src/memory-management/approaches.md @@ -6148,54 +6773,67 @@ msgid "It does this with an explicit ownership concept." msgstr "" #: src/memory-management/approaches.md -msgid "This slide is intended to help students coming from other languages to put Rust in context." +msgid "" +"This slide is intended to help students coming from other languages to put " +"Rust in context." msgstr "" #: src/memory-management/approaches.md msgid "" -"C must manage heap manually with `malloc` and `free`. Common errors include forgetting to call `free`, calling it multiple " -"times for the same pointer, or dereferencing a pointer after the memory it points to has been freed." +"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/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." +"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/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." +"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/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)." +"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/memory-management/ownership.md -msgid "All variable bindings have a _scope_ where they are valid and it is an error to use a variable outside its scope:" +msgid "" +"All variable bindings have a _scope_ where they are valid and it is an error " +"to use a variable outside its scope:" msgstr "" #: src/memory-management/ownership.md -msgid "We say that the variable _owns_ the value. Every Rust value has precisely one owner at all times." +msgid "" +"We say that the variable _owns_ the value. Every Rust value has precisely " +"one owner at all times." msgstr "" #: 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." +"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/memory-management/ownership.md msgid "" -"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." +"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/memory-management/move.md @@ -6255,7 +6893,9 @@ msgid "" msgstr "" #: src/memory-management/move.md -msgid "When you pass a value to a function, the value is assigned to the function parameter. This transfers ownership:" +msgid "" +"When you pass a value to a function, the value is assigned to the function " +"parameter. This transfers ownership:" msgstr "" #: src/memory-management/move.md @@ -6272,18 +6912,20 @@ msgstr "" #: src/memory-management/move.md 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!)." +"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/memory-management/move.md 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." +"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/memory-management/move.md -msgid "Simple values (such as integers) can be marked `Copy` (see later slides)." +msgid "" +"Simple values (such as integers) can be marked `Copy` (see later slides)." msgstr "" #: src/memory-management/move.md @@ -6296,28 +6938,32 @@ msgstr "" #: src/memory-management/move.md msgid "" -"With the first call to `say_hello`, `main` gives up ownership of `name`. Afterwards, `name` cannot be used anymore within " -"`main`." +"With the first call to `say_hello`, `main` gives up ownership of `name`. " +"Afterwards, `name` cannot be used anymore within `main`." msgstr "" #: src/memory-management/move.md -msgid "The heap memory allocated for `name` will be freed at the end of the `say_hello` function." +msgid "" +"The heap memory allocated for `name` will be freed at the end of the " +"`say_hello` function." msgstr "" #: src/memory-management/move.md msgid "" -"`main` can retain ownership if it passes `name` as a reference (`&name`) and if `say_hello` accepts a reference as a " -"parameter." +"`main` can retain ownership if it passes `name` as a reference (`&name`) and " +"if `say_hello` accepts a reference as a parameter." msgstr "" #: src/memory-management/move.md -msgid "Alternatively, `main` can pass a clone of `name` in the first call (`name.clone()`)." +msgid "" +"Alternatively, `main` can pass a clone of `name` in the first call (`name." +"clone()`)." msgstr "" #: src/memory-management/move.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." +"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/memory-management/move.md @@ -6337,7 +6983,8 @@ msgid "// Duplicate the data in s1.\n" msgstr "" #: src/memory-management/move.md -msgid "The heap data from `s1` is duplicated and `s2` gets its own independent copy." +msgid "" +"The heap data from `s1` is duplicated and `s2` gets its own independent copy." msgstr "" #: src/memory-management/move.md @@ -6354,19 +7001,24 @@ msgstr "" #: src/memory-management/move.md 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." +"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/memory-management/move.md 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`." +"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/memory-management/move.md -msgid "Unlike Rust, `=` in C++ can run arbitrary code as determined by the type which is being copied or moved." +msgid "" +"Unlike Rust, `=` in C++ can run arbitrary code as determined by the type " +"which is being copied or moved." msgstr "" #: src/memory-management/clone.md @@ -6374,23 +7026,27 @@ msgid "Clone" msgstr "" #: src/memory-management/clone.md -msgid "Sometimes you _want_ to make a copy of a value. The `Clone` trait accomplishes this." +msgid "" +"Sometimes you _want_ to make a copy of a value. The `Clone` trait " +"accomplishes this." msgstr "" #: src/memory-management/clone.md msgid "" -"The idea of `Clone` is to make it easy to spot where heap allocations are occurring. Look for `.clone()` and a few others " -"like `Vec::new` or `Box::new`." +"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/memory-management/clone.md msgid "" -"It's common to \"clone your way out\" of problems with the borrow checker, and return later to try to optimize those " -"clones away." +"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/memory-management/copy-types.md -msgid "While move semantics are the default, certain types are copied by default:" +msgid "" +"While move semantics are the default, certain types are copied by default:" msgstr "" #: src/memory-management/copy-types.md @@ -6414,15 +7070,20 @@ msgid "Copying and cloning are not the same thing:" msgstr "" #: src/memory-management/copy-types.md -msgid "Copying refers to bitwise copies of memory regions and does not work on arbitrary objects." +msgid "" +"Copying refers to bitwise copies of memory regions and does not work on " +"arbitrary objects." msgstr "" #: src/memory-management/copy-types.md -msgid "Copying does not allow for custom logic (unlike copy constructors in C++)." +msgid "" +"Copying does not allow for custom logic (unlike copy constructors in C++)." msgstr "" #: src/memory-management/copy-types.md -msgid "Cloning is a more general operation and also allows for custom behavior by implementing the `Clone` trait." +msgid "" +"Cloning is a more general operation and also allows for custom behavior by " +"implementing the `Clone` trait." msgstr "" #: src/memory-management/copy-types.md @@ -6434,11 +7095,15 @@ msgid "In the above example, try the following:" msgstr "" #: src/memory-management/copy-types.md -msgid "Add a `String` field to `struct Point`. It will not compile because `String` is not a `Copy` type." +msgid "" +"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`." +msgid "" +"Remove `Copy` from the `derive` attribute. The compiler error is now in the " +"`println!` for `p1`." msgstr "" #: src/memory-management/copy-types.md @@ -6451,15 +7116,16 @@ msgstr "" #: 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:" +"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/memory-management/drop.md msgid "\"Dropping {}\"" msgstr "" -#: src/memory-management/drop.md src/exercises/concurrency/link-checker.md src/exercises/concurrency/solutions-morning.md +#: src/memory-management/drop.md src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md msgid "\"a\"" msgstr "" @@ -6496,22 +7162,28 @@ msgid "Values are automatically dropped when they go out of scope." msgstr "" #: 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." +msgid "" +"When a value is dropped, if it implements `std::ops::Drop` then its `Drop::" +"drop` implementation will be called." msgstr "" #: src/memory-management/drop.md -msgid "All its fields will then be dropped too, whether or not it implements `Drop`." +msgid "" +"All its fields will then be dropped too, whether or not it implements `Drop`." msgstr "" #: 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 scope it gets dropped. This makes it a convenient way to explicitly drop values earlier than they " -"would otherwise go out of scope." +"`std::mem::drop` is just an empty function that takes any value. The " +"significance is that it takes ownership of the value, so at the end of its " +"scope it gets dropped. This makes it a convenient way to explicitly drop " +"values earlier than they would otherwise go out of scope." msgstr "" #: src/memory-management/drop.md -msgid "This can be useful for objects that do some work on `drop`: releasing locks, closing files, etc." +msgid "" +"This can be useful for objects that do some work on `drop`: releasing locks, " +"closing files, etc." msgstr "" #: src/memory-management/drop.md @@ -6520,8 +7192,8 @@ msgstr "" #: 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!" +"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/memory-management/drop.md @@ -6530,8 +7202,9 @@ msgstr "" #: src/memory-management/exercise.md msgid "" -"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." +"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/memory-management/exercise.md @@ -6553,7 +7226,8 @@ msgid "\"1\"" msgstr "" #: src/memory-management/exercise.md src/memory-management/solution.md -msgid "/// A builder for a Package. Use `build()` to create the `Package` itself.\n" +msgid "" +"/// A builder for a Package. Use `build()` to create the `Package` itself.\n" msgstr "" #: src/memory-management/exercise.md @@ -6653,7 +7327,9 @@ msgid "[Exercise: Binary Tree](./smart-pointers/exercise.md) (30 minutes)" msgstr "" #: src/smart-pointers/box.md -msgid "[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned pointer to data on the heap:" +msgid "" +"[`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) is an owned " +"pointer to data on the heap:" msgstr "" #: src/smart-pointers/box.md @@ -6662,12 +7338,14 @@ msgstr "" #: 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)." +"`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/smart-pointers/box.md -msgid "Recursive data types or data types with dynamic sizes need to use a `Box`:" +msgid "" +"Recursive data types or data types with dynamic sizes need to use a `Box`:" msgstr "" #: src/smart-pointers/box.md @@ -6686,20 +7364,28 @@ msgstr "" msgid "" "```bob\n" " Stack Heap\n" -".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - - - - - - - - - - - - -.\n" +".- - - - - - - - - - - - - - . .- - - - - - - - - - - - - - - - - - - - " +"- - - - -.\n" ": : : :\n" -": list : : :\n" -": +---------+----+----+ : : +---------+----+----+ +------+----+----+ :\n" -": | Element | 1 | o--+----+-----+--->| Element | 2 | o--+--->| Nil | // | // | :\n" -": +---------+----+----+ : : +---------+----+----+ +------+----+----+ :\n" +": " +"list : : :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" +": | Element | 1 | o--+----+-----+--->| Element | 2 | o--+--->| Nil | // " +"| // | :\n" +": +---------+----+----+ : : +---------+----+----+ +------+----" +"+----+ :\n" ": : : :\n" ": : : :\n" -"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - - - - - - - - - - - - -'\n" +"'- - - - - - - - - - - - - - ' '- - - - - - - - - - - - - - - - - - - - " +"- - - - -'\n" "```" msgstr "" #: src/smart-pointers/box.md -msgid "`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be not null." +msgid "" +"`Box` is like `std::unique_ptr` in C++, except that it's guaranteed to be " +"not null." msgstr "" #: src/smart-pointers/box.md @@ -6707,32 +7393,37 @@ msgid "A `Box` can be useful when you:" msgstr "" #: src/smart-pointers/box.md -msgid "have a type whose size that can't be known at compile time, but the Rust compiler wants to know an exact size." +msgid "" +"have a type whose size that can't be known at compile time, but the Rust " +"compiler wants to know an exact size." msgstr "" #: src/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." +"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/smart-pointers/box.md msgid "" -"If `Box` was not used and we attempted to embed a `List` directly into the `List`, the compiler would not be able to " -"compute a fixed size for the struct in memory (the `List` would be of infinite size)." +"If `Box` was not used and we attempted to embed a `List` directly into the " +"`List`, the compiler would not be able to compute a fixed size for the " +"struct in memory (the `List` would be of infinite size)." msgstr "" #: src/smart-pointers/box.md 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." +"`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/smart-pointers/box.md msgid "" -"Remove the `Box` in the List definition and show the compiler error. We get the message \"recursive without indirection\", " -"because for data recursion, we have to use indirection, a `Box` or reference of some kind, instead of storing the value " -"directly." +"Remove the `Box` in the List definition and show the compiler error. We get " +"the message \"recursive without indirection\", because for data recursion, " +"we have to use indirection, a `Box` or reference of some kind, instead of " +"storing the value directly." msgstr "" #: src/smart-pointers/box.md @@ -6741,8 +7432,8 @@ msgstr "" #: src/smart-pointers/box.md msgid "" -"A `Box` cannot be empty, so the pointer is always valid and non-`null`. This allows the compiler to optimize the memory " -"layout:" +"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/smart-pointers/box.md @@ -6763,8 +7454,9 @@ msgstr "" #: 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:" +"[`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/smart-pointers/rc.md @@ -6777,18 +7469,21 @@ msgstr "" #: 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." +"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/smart-pointers/rc.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." +"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/smart-pointers/rc.md -msgid "`Rc`'s count ensures that its contained value is valid for as long as there are references." +msgid "" +"`Rc`'s count ensures that its contained value is valid for as long as there " +"are references." msgstr "" #: src/smart-pointers/rc.md @@ -6797,12 +7492,15 @@ msgstr "" #: src/smart-pointers/rc.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." +"`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/smart-pointers/rc.md -msgid "`make_mut` actually clones the inner value if necessary (\"clone-on-write\") and returns a mutable reference." +msgid "" +"`make_mut` actually clones the inner value if necessary (\"clone-on-write\") " +"and returns a mutable reference." msgstr "" #: src/smart-pointers/rc.md @@ -6811,12 +7509,14 @@ msgstr "" #: src/smart-pointers/rc.md msgid "" -"`Rc::downgrade` gives you a _weakly reference-counted_ object to create cycles that will be dropped properly (likely in " -"combination with `RefCell`)." +"`Rc::downgrade` gives you a _weakly reference-counted_ object to create " +"cycles that will be dropped properly (likely in combination with `RefCell`)." msgstr "" #: src/smart-pointers/trait-objects.md -msgid "Trait objects allow for values of different types, for instance in a collection:" +msgid "" +"Trait objects allow for values of different types, for instance in a " +"collection:" msgstr "" #: src/smart-pointers/trait-objects.md @@ -6835,62 +7535,92 @@ msgstr "" msgid "" "```bob\n" " Stack Heap\n" -".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - - -.\n" +".- - - - - - - - - - - - - -. .- - - - - - - - - - - - - - - - - - - - - " +"- -.\n" ": : : :\n" -": \"pets: Vec\" : : \"data: Cat\" +----+----+----+----+ :\n" -": +-----------+-------+ : : +-------+-------+ | F | i | d | o | :\n" -": | ptr | o---+---+--. : | lives | 9 | +----+----+----+----+ :\n" -": | len | 2 | : | : +-------+-------+ ^ :\n" -": | capacity | 2 | : | : ^ | :\n" -": +-----------+-------+ : | : | '-------. :\n" -": : | : | data:\"Dog\"| :\n" -": : | : | +-------+--|-------+ :\n" -"`- - - - - - - - - - - - - -' | : +---|-+-----+ | name | o, 4, 4 | :\n" -" `--+-->| o o | o o-|----->| age | 5 | :\n" -" : +-|---+-|---+ +-------+----------+ :\n" -" : | | :\n" -" `- - -| - - |- - - - - - - - - - - - - - - - -'\n" +": \"pets: Vec\" : : \"data: Cat\" +----+----+----" +"+----+ :\n" +": +-----------+-------+ : : +-------+-------+ | F | i | d | " +"o | :\n" +": | ptr | o---+---+--. : | lives | 9 | +----+----+----" +"+----+ :\n" +": | len | 2 | : | : +-------+-------+ " +"^ :\n" +": | capacity | 2 | : | : ^ " +"| :\n" +": +-----------+-------+ : | : | " +"'-------. :\n" +": : | : | data:\"Dog" +"\"| :\n" +": : | : | +-------+--|-------" +"+ :\n" +"`- - - - - - - - - - - - - -' | : +---|-+-----+ | name | o, 4, 4 " +"| :\n" +" `--+-->| o o | o o-|----->| age | 5 " +"| :\n" +" : +-|---+-|---+ +-------+----------" +"+ :\n" +" : | " +"| :\n" +" `- - -| - - |- - - - - - - - - - - - - - - " +"- -'\n" " | |\n" -" | | \"Program text\"\n" -" .- - -| - - |- - - - - - - - - - - - - - - - -.\n" -" : | | vtable :\n" -" : | | +----------------------+ :\n" -" : | `----->| \"::talk\" | :\n" -" : | +----------------------+ :\n" -" : | vtable :\n" -" : | +----------------------+ :\n" -" : '----------->| \"::talk\" | :\n" -" : +----------------------+ :\n" +" | | " +"\"Program text\"\n" +" .- - -| - - |- - - - - - - - - - - - - - - " +"- -.\n" +" : | | " +"vtable :\n" +" : | | +----------------------" +"+ :\n" +" : | `----->| \"::talk" +"\" | :\n" +" : | +----------------------" +"+ :\n" +" : | " +"vtable :\n" +" : | +----------------------" +"+ :\n" +" : '----------->| \"::talk" +"\" | :\n" +" : +----------------------" +"+ :\n" " : :\n" -" '- - - - - - - - - - - - - - - - - - - - - - -'\n" +" '- - - - - - - - - - - - - - - - - - - - - " +"- -'\n" "```" msgstr "" #: src/smart-pointers/trait-objects.md 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." +"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/smart-pointers/trait-objects.md -msgid "`dyn Pet` is a way to tell the compiler about a dynamically sized type that implements `Pet`." +msgid "" +"`dyn Pet` is a way to tell the compiler about a dynamically sized type that " +"implements `Pet`." msgstr "" #: src/smart-pointers/trait-objects.md 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_:" +"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/smart-pointers/trait-objects.md 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." +"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/smart-pointers/trait-objects.md -msgid "The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` has a `lives` field." +msgid "" +"The data for the `Dog` named Fido is the `name` and `age` fields. The `Cat` " +"has a `lives` field." msgstr "" #: src/smart-pointers/trait-objects.md @@ -6899,9 +7629,10 @@ msgstr "" #: src/smart-pointers/exercise.md msgid "" -"A binary tree is a tree-type data structure where every node has two children (left and right). We will create a tree " -"where each node stores a value. For a given node N, all nodes in a N's left subtree contain smaller values, and all nodes " -"in N's right subtree will contain larger values." +"A binary tree is a tree-type data structure where every node has two " +"children (left and right). We will create a tree where each node stores a " +"value. For a given node N, all nodes in a N's left subtree contain smaller " +"values, and all nodes in N's right subtree will contain larger values." msgstr "" #: src/smart-pointers/exercise.md @@ -6909,7 +7640,9 @@ msgid "Implement the following types, so that the given tests pass." msgstr "" #: src/smart-pointers/exercise.md -msgid "Extra Credit: implement an iterator over a binary tree that returns the values in order." +msgid "" +"Extra Credit: implement an iterator over a binary tree that returns the " +"values in order." msgstr "" #: src/smart-pointers/exercise.md src/smart-pointers/solution.md @@ -6948,7 +7681,9 @@ msgid "[Lifetimes](./lifetimes.md) (50 minutes)" msgstr "" #: src/welcome-day-3-afternoon.md -msgid "Including 10 minute breaks, this session should take about 1 hour and 50 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 1 hour and 50 " +"minutes" msgstr "" #: src/borrowing.md @@ -6969,7 +7704,8 @@ msgstr "" #: src/borrowing/shared.md msgid "" -"As we saw before, instead of transferring ownership when calling a function, you can let a function _borrow_ the value:" +"As we saw before, instead of transferring ownership when calling a function, " +"you can let a function _borrow_ the value:" msgstr "" #: src/borrowing/shared.md @@ -6982,8 +7718,8 @@ msgstr "" #: src/borrowing/shared.md msgid "" -"This slide is a review of the material on references from day 1, expanding slightly to include function arguments and " -"return values." +"This slide is a review of the material on references from day 1, expanding " +"slightly to include function arguments and return values." msgstr "" #: src/borrowing/shared.md @@ -6992,11 +7728,13 @@ msgstr "" #: src/borrowing/shared.md 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/?" -"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:" +"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/borrowing/shared.md @@ -7005,12 +7743,16 @@ msgstr "" #: src/borrowing/shared.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." +"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/borrowing/borrowck.md -msgid "Rust's _borrow checker_ puts constraints on the ways you can borrow values. For a given value, at any time:" +msgid "" +"Rust's _borrow checker_ puts constraints on the ways you can borrow values. " +"For a given value, at any time:" msgstr "" #: src/borrowing/borrowck.md @@ -7023,50 +7765,57 @@ msgstr "" #: src/borrowing/borrowck.md msgid "" -"Note that the requirement is that conflicting references not _exist_ at the same point. It does not matter where the " -"reference is dereferenced." +"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/borrowing/borrowck.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." +"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/borrowing/borrowck.md -msgid "Move the `println!` statement for `b` before the scope that introduces `c` to make the code compile." +msgid "" +"Move the `println!` statement for `b` before the scope that introduces `c` " +"to make the code compile." msgstr "" #: src/borrowing/borrowck.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\"." +"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/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." +"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/borrowing/borrowck.md msgid "" -"The borrow checker is designed to accommodate many common patterns, such as taking exclusive references to different " -"fields in a struct at the same time. But, there are some situations where it doesn't quite \"get it\" and this often " -"results in \"fighting with the borrow checker.\"" +"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/borrowing/interior-mutability.md msgid "" -"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." +"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/borrowing/interior-mutability.md msgid "" -"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." +"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/borrowing/interior-mutability.md @@ -7087,66 +7836,81 @@ msgstr "" #: src/borrowing/interior-mutability.md msgid "" -"`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." +"`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/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." +"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/borrowing/interior-mutability.md msgid "" -"`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." +"`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/borrowing/interior-mutability.md msgid "" -"`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." +"`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/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." +"`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/borrowing/interior-mutability.md -msgid "Demonstrate that reference loops can be created by adding `root` to `subtree.children`." +msgid "" +"Demonstrate that reference loops can be created by adding `root` to `subtree." +"children`." msgstr "" #: 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'`." +"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/borrowing/exercise.md msgid "" -"You're working on implementing a health-monitoring system. As part of that, you need to keep track of users' health " -"statistics." +"You're working on implementing a health-monitoring system. As part of that, " +"you need to keep track of users' health statistics." msgstr "" #: 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." +"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/borrowing/exercise.md -msgid "Copy the code below to and fill in the missing method:" +msgid "" +"Copy the code below to and fill in the missing " +"method:" msgstr "" #: src/borrowing/exercise.md -msgid "\"Update a user's statistics based on measurements from a visit to the doctor\"" +msgid "" +"\"Update a user's statistics based on measurements from a visit to the doctor" +"\"" msgstr "" -#: src/borrowing/exercise.md src/borrowing/solution.md src/android/build-rules/library.md +#: src/borrowing/exercise.md src/borrowing/solution.md +#: src/android/build-rules/library.md #: src/android/aidl/example-service/client.md msgid "\"Bob\"" msgstr "" @@ -7156,7 +7920,8 @@ msgid "\"I'm {} and my age is {}\"" msgstr "" #: src/lifetimes.md -msgid "[Lifetime Annotations](./lifetimes/lifetime-annotations.md) (10 minutes)" +msgid "" +"[Lifetime Annotations](./lifetimes/lifetime-annotations.md) (10 minutes)" msgstr "" #: src/lifetimes.md @@ -7173,24 +7938,29 @@ msgstr "" #: src/lifetimes/lifetime-annotations.md msgid "" -"A reference has a _lifetime_, which must not \"outlive\" the value it refers to. This is verified by the borrow checker." +"A reference has a _lifetime_, which must not \"outlive\" the value it refers " +"to. This is verified by the borrow checker." msgstr "" #: src/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`\"." +"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/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." +"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/lifetimes/lifetime-annotations.md -msgid "Lifetimes become more complicated when considering passing values to and returning values from functions." +msgid "" +"Lifetimes become more complicated when considering passing values to and " +"returning values from functions." msgstr "" #: src/lifetimes/lifetime-annotations.md @@ -7203,9 +7973,11 @@ msgstr "" #: src/lifetimes/lifetime-annotations.md msgid "" -"In this example, 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." +"In this example, 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/lifetimes/lifetime-annotations.md @@ -7213,11 +7985,14 @@ msgid "Add `'a` appropriately to `left_most`:" msgstr "" #: src/lifetimes/lifetime-annotations.md -msgid "This says, \"given p1 and p2 which both outlive `'a`, the return value lives for at least `'a`." +msgid "" +"This says, \"given p1 and p2 which both outlive `'a`, the return value lives " +"for at least `'a`." msgstr "" #: src/lifetimes/lifetime-annotations.md -msgid "In common cases, lifetimes can be elided, as described on the next slide." +msgid "" +"In common cases, lifetimes can be elided, as described on the next slide." msgstr "" #: src/lifetimes/lifetime-elision.md @@ -7226,9 +8001,10 @@ msgstr "" #: src/lifetimes/lifetime-elision.md 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). This is not inference -- it is " -"just a syntactic shorthand." +"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/lifetimes/lifetime-elision.md @@ -7236,13 +8012,15 @@ msgid "Each argument which does not have a lifetime annotation is given one." msgstr "" #: src/lifetimes/lifetime-elision.md -msgid "If there is only one argument lifetime, it is given to all un-annotated return values." +msgid "" +"If there is only one argument lifetime, it is given to all un-annotated " +"return values." msgstr "" #: src/lifetimes/lifetime-elision.md msgid "" -"If there are multiple argument lifetimes, but the first one is for `self`, that lifetime is given to all un-annotated " -"return values." +"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/lifetimes/lifetime-elision.md @@ -7251,8 +8029,8 @@ msgstr "" #: src/lifetimes/lifetime-elision.md msgid "" -"The `nearest` function provides another example of a function with multiple references in its arguments that requires " -"explicit annotation." +"The `nearest` function provides another example of a function with multiple " +"references in its arguments that requires explicit annotation." msgstr "" #: src/lifetimes/lifetime-elision.md @@ -7261,15 +8039,18 @@ msgstr "" #: src/lifetimes/lifetime-elision.md msgid "" -"This won't compile, demonstrating that the annotations are checked for validity by the compiler. Note that this is not the " -"case for raw pointers (unsafe), and this is a common source of errors with unsafe Rust." +"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/lifetimes/lifetime-elision.md msgid "" -"Students may ask when to use lifetimes. Rust borrows _always_ have lifetimes. Most of the time, elision and type inference " -"mean these don't need to be written out. In more complicated cases, lifetime annotations can help resolve ambiguity. " -"Often, especially when prototyping, it's easier to just work with owned data by cloning values where necessary." +"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/lifetimes/struct-lifetimes.md @@ -7277,7 +8058,8 @@ msgid "Lifetimes in Data Structures" msgstr "" #: src/lifetimes/struct-lifetimes.md -msgid "If a data type stores borrowed data, it must be annotated with a lifetime:" +msgid "" +"If a data type stores borrowed data, it must be annotated with a lifetime:" msgstr "" #: src/lifetimes/struct-lifetimes.md @@ -7302,18 +8084,22 @@ msgstr "" #: src/lifetimes/struct-lifetimes.md 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." +"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/lifetimes/struct-lifetimes.md -msgid "If `text` is consumed before the end of the lifetime of `fox` (or `dog`), the borrow checker throws an error." +msgid "" +"If `text` is consumed before the end of the lifetime of `fox` (or `dog`), " +"the borrow checker throws an error." msgstr "" #: src/lifetimes/struct-lifetimes.md 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." +"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/lifetimes/struct-lifetimes.md @@ -7322,23 +8108,26 @@ msgstr "" #: src/lifetimes/struct-lifetimes.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." +"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/lifetimes/exercise.md msgid "" -"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." +"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/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." +"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/lifetimes/exercise.md @@ -7347,22 +8136,24 @@ msgstr "" #: src/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." +"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/lifetimes/exercise.md msgid "" -"Integers, including the tag, are represented with a variable-length encoding called VARINT. Luckily, `parse_varint` is " -"defined for you below. The given code also defines callbacks to handle `Person` and `PhoneNumber` fields, and to parse a " -"message into a series of calls to those callbacks." +"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/lifetimes/exercise.md msgid "" -"What remains for you is to implement the `parse_field` function and the `ProtoMessage` trait for `Person` and " -"`PhoneNumber`." +"What remains for you is to implement the `parse_field` function and the " +"`ProtoMessage` trait for `Person` and `PhoneNumber`." msgstr "" #: src/lifetimes/exercise.md src/lifetimes/solution.md @@ -7400,7 +8191,8 @@ msgstr "" #: src/lifetimes/exercise.md src/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" +" /// The Len WireType indicates that the value is a length represented as " +"a\n" " /// VARINT followed by exactly that number of bytes.\n" msgstr "" @@ -7427,7 +8219,8 @@ msgid "//1 => WireType::I64, -- not needed for this exercise\n" msgstr "" #: src/lifetimes/exercise.md src/lifetimes/solution.md -msgid "/// Parse a VARINT, returning the parsed value and the remaining bytes.\n" +msgid "" +"/// Parse a VARINT, returning the parsed value and the remaining bytes.\n" msgstr "" #: src/lifetimes/exercise.md src/lifetimes/solution.md @@ -7449,7 +8242,9 @@ msgid "/// Parse a field, returning the remaining bytes\n" msgstr "" #: src/lifetimes/exercise.md -msgid "\"Based on the wire type, build a Field, consuming as many bytes as necessary.\"" +msgid "" +"\"Based on the wire type, build a Field, consuming as many bytes as " +"necessary.\"" msgstr "" #: src/lifetimes/exercise.md @@ -7458,7 +8253,8 @@ msgstr "" #: src/lifetimes/exercise.md src/lifetimes/solution.md msgid "" -"/// Parse a message in the given data, calling `T::add_field` for each field in\n" +"/// 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" @@ -7485,7 +8281,8 @@ msgid "Welcome to Day 4" msgstr "" #: src/welcome-day-4.md -msgid "Today we will cover topics relating to building large-scale software in Rust:" +msgid "" +"Today we will cover topics relating to building large-scale software in Rust:" msgstr "" #: src/welcome-day-4.md @@ -7505,7 +8302,8 @@ msgid "Error handling: panics, `Result`, and the try operator `?`." msgstr "" #: src/welcome-day-4.md -msgid "Unsafe Rust: the escape hatch when you can't express yourself in safe Rust." +msgid "" +"Unsafe Rust: the escape hatch when you can't express yourself in safe Rust." msgstr "" #: src/welcome-day-4.md @@ -7525,7 +8323,9 @@ msgid "[Testing](./testing.md) (45 minutes)" msgstr "" #: src/welcome-day-4.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 40 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 40 " +"minutes" msgstr "" #: src/iterators.md @@ -7541,7 +8341,8 @@ msgid "[FromIterator](./iterators/fromiterator.md) (5 minutes)" msgstr "" #: src/iterators.md -msgid "[Exercise: Iterator Method Chaining](./iterators/exercise.md) (30 minutes)" +msgid "" +"[Exercise: Iterator Method Chaining](./iterators/exercise.md) (30 minutes)" msgstr "" #: src/iterators.md src/testing.md @@ -7550,9 +8351,10 @@ msgstr "" #: src/iterators/iterator.md msgid "" -"The [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html) trait supports iterating over values in a " -"collection. It requires a `next` method and provides lots of methods. Many standard library types implement `Iterator`, " -"and you can implement it yourself, too:" +"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/iterators/iterator.md @@ -7561,23 +8363,27 @@ msgstr "" #: 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." +"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/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." +"`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/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." +"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/iterators/intoiterator.md @@ -7585,7 +8391,9 @@ msgid "\"point = {x}, {y}\"" msgstr "" #: src/iterators/intoiterator.md -msgid "Click through to the docs for `IntoIterator`. Every implementation of `IntoIterator` must declare two types:" +msgid "" +"Click through to the docs for `IntoIterator`. Every implementation of " +"`IntoIterator` must declare two types:" msgstr "" #: src/iterators/intoiterator.md @@ -7598,8 +8406,8 @@ msgstr "" #: 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`" +"Note that `IntoIter` and `Item` are linked: the iterator must have the same " +"`Item` type, which means that it returns `Option`" msgstr "" #: src/iterators/intoiterator.md @@ -7608,19 +8416,22 @@ msgstr "" #: src/iterators/intoiterator.md msgid "" -"Try iterating over the grid twice in `main`. Why does this fail? Note that `IntoIterator::into_iter` takes ownership of " -"`self`." +"Try iterating over the grid twice in `main`. Why does this fail? Note that " +"`IntoIterator::into_iter` takes ownership of `self`." msgstr "" #: src/iterators/intoiterator.md -msgid "Fix this issue by implementing `IntoIterator` for `&Grid` and storing a reference to the `Grid` in `GridIter`." +msgid "" +"Fix this issue by implementing `IntoIterator` for `&Grid` and storing a " +"reference to the `Grid` in `GridIter`." msgstr "" #: src/iterators/intoiterator.md msgid "" -"The same problem can occur for standard library types: `for e in some_vector` will take ownership of `some_vector` and " -"iterate over owned elements from that vector. Use `for e in &some_vector` instead, to iterate over references to elements " -"of `some_vector`." +"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/iterators/fromiterator.md @@ -7629,8 +8440,9 @@ msgstr "" #: src/iterators/fromiterator.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)." +"[`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/iterators/fromiterator.md @@ -7647,35 +8459,42 @@ msgstr "" #: 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." +"With the \"turbofish\": `some_iterator.collect::()`, as " +"shown. The `_` shorthand used here lets Rust infer the type of the `Vec` " +"elements." msgstr "" #: src/iterators/fromiterator.md -msgid "With type inference: `let prime_squares: Vec<_> = some_iterator.collect()`. Rewrite the example to use this form." +msgid "" +"With type inference: `let prime_squares: Vec<_> = some_iterator.collect()`. " +"Rewrite the example to use this form." msgstr "" #: 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>`." +"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/iterators/exercise.md msgid "" -"In this exercise, you will need to find and use some of the provided methods in the [`Iterator`](https://doc.rust-lang.org/" -"std/iter/trait.Iterator.html) trait to implement a complex calculation." +"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/iterators/exercise.md msgid "" -"Copy the following code to and make the tests pass. Use an iterator expression and `collect` " -"the result to construct the return value." +"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/iterators/exercise.md src/iterators/solution.md msgid "" -"/// Calculate the differences between elements of `values` offset by `offset`,\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" @@ -7698,7 +8517,8 @@ msgid "[use, super, self](./modules/paths.md) (10 minutes)" msgstr "" #: src/modules.md -msgid "[Exercise: Modules for a GUI Library](./modules/exercise.md) (15 minutes)" +msgid "" +"[Exercise: Modules for a GUI Library](./modules/exercise.md) (15 minutes)" msgstr "" #: src/modules/modules.md @@ -7718,11 +8538,15 @@ msgid "\"In the bar module\"" msgstr "" #: src/modules/modules.md -msgid "Packages provide functionality and include a `Cargo.toml` file that describes how to build a bundle of 1+ crates." +msgid "" +"Packages provide functionality and include a `Cargo.toml` file that " +"describes how to build a bundle of 1+ crates." msgstr "" #: src/modules/modules.md -msgid "Crates are a tree of modules, where a binary crate creates an executable and a library crate compiles to a library." +msgid "" +"Crates are a tree of modules, where a binary crate creates an executable and " +"a library crate compiles to a library." msgstr "" #: src/modules/modules.md @@ -7730,13 +8554,15 @@ msgid "Modules define organization, scope, and are the focus of this section." msgstr "" #: src/modules/filesystem.md -msgid "Omitting the module content will tell Rust to look for it in another file:" +msgid "" +"Omitting the module content will tell Rust to look for it in another file:" msgstr "" #: 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`." +"This tells rust that the `garden` module content is found at `src/garden." +"rs`. Similarly, a `garden::vegetables` module can be found at `src/garden/" +"vegetables.rs`." msgstr "" #: src/modules/filesystem.md @@ -7753,13 +8579,14 @@ msgstr "" #: 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." +"Modules defined in files can be documented, too, using \"inner doc comments" +"\". These document the item that contains them -- in this case, a module." msgstr "" #: src/modules/filesystem.md msgid "" -"//! This module implements the garden, including a highly performant germination\n" +"//! This module implements the garden, including a highly performant " +"germination\n" "//! implementation.\n" msgstr "" @@ -7777,14 +8604,14 @@ msgstr "" #: src/modules/filesystem.md 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." +"Before Rust 2018, modules needed to be located at `module/mod.rs` instead of " +"`module.rs`, and this is still a working alternative for editions after 2018." msgstr "" #: src/modules/filesystem.md 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." +"The main reason to introduce `filename.rs` as alternative to `filename/mod." +"rs` was because many files named `mod.rs` can be hard to distinguish in IDEs." msgstr "" #: src/modules/filesystem.md @@ -7792,7 +8619,9 @@ msgid "Deeper nesting can use folders, even if the main module is a file:" msgstr "" #: src/modules/filesystem.md -msgid "The place rust will look for modules can be changed with a compiler directive:" +msgid "" +"The place rust will look for modules can be changed with a compiler " +"directive:" msgstr "" #: src/modules/filesystem.md @@ -7801,8 +8630,8 @@ msgstr "" #: 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." +"This is useful, for example, if you would like to place tests for a module " +"in a file named `some_module_test.rs`, similar to the convention in Go." msgstr "" #: src/modules/visibility.md @@ -7818,7 +8647,9 @@ msgid "Parent and sibling items are always visible." msgstr "" #: src/modules/visibility.md -msgid "In other words, if an item is visible in module `foo`, it's visible in all the descendants of `foo`." +msgid "" +"In other words, if an item is visible in module `foo`, it's visible in all " +"the descendants of `foo`." msgstr "" #: src/modules/visibility.md @@ -7842,13 +8673,15 @@ msgid "Use the `pub` keyword to make modules public." msgstr "" #: src/modules/visibility.md -msgid "Additionally, there are advanced `pub(...)` specifiers to restrict the scope of public visibility." +msgid "" +"Additionally, there are advanced `pub(...)` specifiers to restrict the scope " +"of public visibility." msgstr "" #: 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)." +"See the [Rust Reference](https://doc.rust-lang.org/reference/visibility-and-" +"privacy.html#pubin-path-pubcrate-pubsuper-and-pubself)." msgstr "" #: src/modules/visibility.md @@ -7860,7 +8693,9 @@ msgid "Less commonly, you can give visibility to a specific path." msgstr "" #: src/modules/visibility.md -msgid "In any case, visibility must be granted to an ancestor module (and all of its descendants)." +msgid "" +"In any case, visibility must be granted to an ancestor module (and all of " +"its descendants)." msgstr "" #: src/modules/paths.md @@ -7869,8 +8704,8 @@ msgstr "" #: src/modules/paths.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:" +"A module can bring symbols from another module into scope with `use`. You " +"will typically see something like this at the top of each module:" msgstr "" #: src/modules/paths.md @@ -7906,36 +8741,44 @@ msgid "`bar::foo` refers to `foo` in the `bar` crate." msgstr "" #: src/modules/paths.md -msgid "It is common to \"re-export\" symbols at a shorter path. For example, the top-level `lib.rs` in a crate might have" +msgid "" +"It is common to \"re-export\" symbols at a shorter path. For example, the " +"top-level `lib.rs` in a crate might have" msgstr "" #: src/modules/paths.md -msgid "making `DiskStorage` and `NetworkStorage` available to other crates with a convenient, short path." +msgid "" +"making `DiskStorage` and `NetworkStorage` available to other crates with a " +"convenient, short path." msgstr "" #: src/modules/paths.md msgid "" -"For the most part, only items that appear in a module need to be `use`'d. However, a trait must be in scope to call any " -"methods on that trait, even if a type implementing that trait is already in scope. For example, to use the " -"`read_to_string` method on a type implementing the `Read` trait, you need to `use std::io::Read`." +"For the most part, only items that appear in a module need to be `use`'d. " +"However, a trait must be in scope to call any methods on that trait, even if " +"a type implementing that trait is already in scope. For example, to use the " +"`read_to_string` method on a type implementing the `Read` trait, you need to " +"`use std::io::Read`." msgstr "" #: src/modules/paths.md msgid "" -"The `use` statement can have a wildcard: `use std::io::*`. This is discouraged because it is not clear which items are " -"imported, and those might change over time." +"The `use` statement can have a wildcard: `use std::io::*`. This is " +"discouraged because it is not clear which items are imported, and those " +"might change over time." msgstr "" #: src/modules/exercise.md msgid "" -"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." +"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/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." +"It is typical to put each type or set of closely-related types into its own " +"module, so each widget type should get its own module." msgstr "" #: src/modules/exercise.md @@ -7943,11 +8786,15 @@ msgid "Cargo Setup" msgstr "" #: 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:" +msgid "" +"The Rust playground only supports one file, so you will need to make a Cargo " +"project on your local filesystem:" msgstr "" #: src/modules/exercise.md -msgid "Edit the resulting `src/main.rs` to add `mod` statements, and add additional files in the `src` directory." +msgid "" +"Edit the resulting `src/main.rs` to add `mod` statements, and add additional " +"files in the `src` directory." msgstr "" #: src/modules/exercise.md @@ -7980,7 +8827,8 @@ msgstr "" #: src/modules/exercise.md msgid "" -"// TODO: Change draw_into to return Result<(), std::fmt::Error>. Then use the\n" +"// TODO: Change draw_into to return Result<(), std::fmt::Error>. Then use " +"the\n" " // ?-operator here instead of .unwrap().\n" msgstr "" @@ -7988,7 +8836,8 @@ msgstr "" msgid "\"+-{:- and write additional tests to uncover bugs in the provided " -"implementation, fixing any bugs you find." +"Copy the code below to and write additional " +"tests to uncover bugs in the provided implementation, fixing any bugs you " +"find." msgstr "" #: src/testing/exercise.md src/testing/solution.md @@ -8363,7 +9224,9 @@ msgid "[Unsafe Rust](./unsafe-rust.md) (1 hour and 5 minutes)" msgstr "" #: src/welcome-day-4-afternoon.md -msgid "Including 10 minute breaks, this session should take about 2 hours and 10 minutes" +msgid "" +"Including 10 minute breaks, this session should take about 2 hours and 10 " +"minutes" msgstr "" #: src/error-handling.md @@ -8383,11 +9246,13 @@ msgid "[Error Trait](./error-handling/error.md) (5 minutes)" msgstr "" #: src/error-handling.md -msgid "[thiserror and anyhow](./error-handling/thiserror-and-anyhow.md) (5 minutes)" +msgid "" +"[thiserror and anyhow](./error-handling/thiserror-and-anyhow.md) (5 minutes)" msgstr "" #: src/error-handling.md -msgid "[Exercise: Rewriting with Result](./error-handling/exercise.md) (30 minutes)" +msgid "" +"[Exercise: Rewriting with Result](./error-handling/exercise.md) (30 minutes)" msgstr "" #: src/error-handling/panics.md @@ -8423,15 +9288,20 @@ msgid "Purpose-specific panics can use the `panic!` macro." msgstr "" #: src/error-handling/panics.md -msgid "A panic will \"unwind\" the stack, dropping values just as if the functions had returned." +msgid "" +"A panic will \"unwind\" the stack, dropping values just as if the functions " +"had returned." msgstr "" #: src/error-handling/panics.md -msgid "Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." +msgid "" +"Use non-panicking APIs (such as `Vec::get`) if crashing is not acceptable." msgstr "" #: src/error-handling/panics.md -msgid "By default, a panic will cause the stack to unwind. The unwinding can be caught:" +msgid "" +"By default, a panic will cause the stack to unwind. The unwinding can be " +"caught:" msgstr "" #: src/error-handling/panics.md @@ -8447,11 +9317,15 @@ msgid "\"oh no!\"" msgstr "" #: src/error-handling/panics.md -msgid "Catching is unusual; do not attempt to implement exceptions with `catch_unwind`!" +msgid "" +"Catching is unusual; do not attempt to implement exceptions with " +"`catch_unwind`!" msgstr "" #: src/error-handling/panics.md -msgid "This can be useful in servers which should keep running even if a single request crashes." +msgid "" +"This can be useful in servers which should keep running even if a single " +"request crashes." msgstr "" #: src/error-handling/panics.md @@ -8460,8 +9334,10 @@ msgstr "" #: src/error-handling/try.md msgid "" -"Runtime errors like connection-refused or file-not-found are handled with the `Result` type, but matching this type on " -"every call can be cumbersome. The try-operator `?` is used to return errors to the caller. It lets you turn the common" +"Runtime errors like connection-refused or file-not-found are handled with " +"the `Result` type, but matching this type on every call can be cumbersome. " +"The try-operator `?` is used to return errors to the caller. It lets you " +"turn the common" msgstr "" #: src/error-handling/try.md @@ -8476,7 +9352,8 @@ msgstr "" msgid "//fs::write(\"config.dat\", \"alice\").unwrap();\n" msgstr "" -#: src/error-handling/try.md src/error-handling/try-conversions.md src/error-handling/thiserror-and-anyhow.md +#: src/error-handling/try.md src/error-handling/try-conversions.md +#: src/error-handling/thiserror-and-anyhow.md msgid "\"config.dat\"" msgstr "" @@ -8493,17 +9370,23 @@ msgid "The `username` variable can be either `Ok(string)` or `Err(error)`." msgstr "" #: src/error-handling/try.md -msgid "Use the `fs::write` call to test out the different scenarios: no file, empty file, file with username." +msgid "" +"Use the `fs::write` call to test out the different scenarios: no file, empty " +"file, file with username." msgstr "" #: src/error-handling/try.md 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." +"Note that `main` can return a `Result<(), E>` as long as it implements `std::" +"process::Termination`. In practice, this means that `E` implements `Debug`. " +"The executable will print the `Err` variant and return a nonzero exit status " +"on error." msgstr "" #: src/error-handling/try-conversions.md -msgid "The effective expansion of `?` is a little more complicated than previously indicated:" +msgid "" +"The effective expansion of `?` is a little more complicated than previously " +"indicated:" msgstr "" #: src/error-handling/try-conversions.md @@ -8512,8 +9395,9 @@ msgstr "" #: src/error-handling/try-conversions.md msgid "" -"The `From::from` call here means we attempt to convert the error type to the type returned by the function. This makes it " -"easy to encapsulate errors into higher-level errors." +"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 @@ -8524,34 +9408,38 @@ msgstr "" msgid "\"Found no username in {path}\"" msgstr "" -#: src/error-handling/try-conversions.md src/error-handling/thiserror-and-anyhow.md +#: 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 "" -"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`." +"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/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." +"A common alternative to a `From` implementation is `Result::map_err`, " +"especially when the conversion only happens in one place." msgstr "" #: src/error-handling/try-conversions.md msgid "" -"There is no compatibility requirement for `Option`. A function returning `Option` can use the `?` operator on " -"`Option` for arbitrary `T` and `U` types." +"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/error-handling/try-conversions.md msgid "" -"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`." +"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/error-handling/error.md @@ -8560,8 +9448,10 @@ msgstr "" #: 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." +"Sometimes we want to allow any type of error to be returned without writing " +"our own enum covering all the different possibilities. The `std::error::" +"Error` trait makes it easy to create a trait object that can contain any " +"error." msgstr "" #: src/error-handling/error.md @@ -8582,38 +9472,44 @@ msgstr "" #: src/error-handling/error.md msgid "" -"The `read_count` function can return `std::io::Error` (from file operations) or `std::num::ParseIntError` (from `String::" -"parse`)." +"The `read_count` function can return `std::io::Error` (from file operations) " +"or `std::num::ParseIntError` (from `String::parse`)." msgstr "" #: src/error-handling/error.md msgid "" -"Boxing errors saves on code, but gives up the ability to cleanly handle different error cases differently in the program. " -"As such it's generally not a good idea to use `Box` in the public API of a library, but it can be a good option " -"in a program where you just want to display the error message somewhere." +"Boxing errors saves on code, but gives up the ability to cleanly handle " +"different error cases differently in the program. As such it's generally not " +"a good idea to use `Box` in the public API of a library, but it " +"can be a good option in a program where you just want to display the error " +"message somewhere." msgstr "" #: src/error-handling/error.md msgid "" -"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." +"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/error-handling/thiserror-and-anyhow.md msgid "" -"The [`thiserror`](https://docs.rs/thiserror/) and [`anyhow`](https://docs.rs/anyhow/) crates are widely used to simplify " -"error handling." +"The [`thiserror`](https://docs.rs/thiserror/) and [`anyhow`](https://docs.rs/" +"anyhow/) crates are widely used to simplify error handling." msgstr "" #: src/error-handling/thiserror-and-anyhow.md -msgid "`thiserror` is often used in libraries to create custom error types that implement `From`." +msgid "" +"`thiserror` is often used in libraries to create custom error types that " +"implement `From`." msgstr "" #: src/error-handling/thiserror-and-anyhow.md msgid "" -"`anyhow` is often used by applications to help with error handling in functions, including adding contextual information " -"to your errors." +"`anyhow` is often used by applications to help with error handling in " +"functions, including adding contextual information to your errors." msgstr "" #: src/error-handling/thiserror-and-anyhow.md @@ -8642,8 +9538,8 @@ msgstr "" #: 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." +"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/error-handling/thiserror-and-anyhow.md @@ -8660,8 +9556,9 @@ msgstr "" #: src/error-handling/thiserror-and-anyhow.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." +"`anyhow::Error` is essentially a wrapper around `Box`. As such " +"it's again generally not a good choice for the public API of a library, but " +"is widely used in applications." msgstr "" #: src/error-handling/thiserror-and-anyhow.md @@ -8669,19 +9566,22 @@ msgid "`anyhow::Result` is a type alias for `Result`." msgstr "" #: src/error-handling/thiserror-and-anyhow.md -msgid "Actual error type inside of it can be extracted for examination if necessary." +msgid "" +"Actual error type inside of it can be extracted for examination if necessary." msgstr "" #: 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." +"Functionality provided by `anyhow::Result` may be familiar to Go " +"developers, as it provides similar usage patterns and ergonomics to `(T, " +"error)` from Go." msgstr "" #: src/error-handling/thiserror-and-anyhow.md msgid "" -"`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." +"`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/error-handling/exercise.md @@ -8690,15 +9590,17 @@ msgstr "" #: src/error-handling/exercise.md msgid "" -"The following implements a very simple parser for an expression language. However, it handles errors by panicking. Rewrite " -"it to instead use idiomatic error handling and propagate errors to a return from `main`. Feel free to use `thiserror` and " -"`anyhow`." +"The following implements a very simple parser for an expression language. " +"However, it handles errors by panicking. Rewrite it to instead use idiomatic " +"error handling and propagate errors to a return from `main`. Feel free to " +"use `thiserror` and `anyhow`." msgstr "" #: src/error-handling/exercise.md 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." +"HINT: start by fixing error handling in the `parse` function. Once that is " +"working correctly, update `Tokenizer` to implement " +"`Iterator>` and handle that in the parser." msgstr "" #: src/error-handling/exercise.md src/error-handling/solution.md @@ -8786,7 +9688,8 @@ msgid "[Unsafe](./unsafe-rust/unsafe.md) (5 minutes)" msgstr "" #: src/unsafe-rust.md -msgid "[Dereferencing Raw Pointers](./unsafe-rust/dereferencing.md) (10 minutes)" +msgid "" +"[Dereferencing Raw Pointers](./unsafe-rust/dereferencing.md) (10 minutes)" msgstr "" #: src/unsafe-rust.md @@ -8822,17 +9725,21 @@ msgid "**Safe Rust:** memory safe, no undefined behavior possible." msgstr "" #: src/unsafe-rust/unsafe.md -msgid "**Unsafe Rust:** can trigger undefined behavior if preconditions are violated." +msgid "" +"**Unsafe Rust:** can trigger undefined behavior if preconditions are " +"violated." msgstr "" #: src/unsafe-rust/unsafe.md -msgid "We saw mostly safe Rust in this course, but it's important to know what Unsafe Rust is." +msgid "" +"We saw mostly safe Rust in this course, but it's important to know what " +"Unsafe Rust is." msgstr "" #: src/unsafe-rust/unsafe.md msgid "" -"Unsafe code is usually small and isolated, and its correctness should be carefully documented. It is usually wrapped in a " -"safe abstraction layer." +"Unsafe code is usually small and isolated, and its correctness should be " +"carefully documented. It is usually wrapped in a safe abstraction layer." msgstr "" #: src/unsafe-rust/unsafe.md @@ -8861,14 +9768,17 @@ msgstr "" #: src/unsafe-rust/unsafe.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/)." +"We will briefly cover unsafe capabilities next. For full details, please see " +"[Chapter 19.1 in the Rust Book](https://doc.rust-lang.org/book/ch19-01-" +"unsafe-rust.html) and the [Rustonomicon](https://doc.rust-lang.org/nomicon/)." msgstr "" #: src/unsafe-rust/unsafe.md 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." +"Unsafe Rust does not mean the code is incorrect. It means that developers " +"have turned off some compiler safety features and have to write correct code " +"by themselves. It means the compiler no longer enforces Rust's memory-safety " +"rules." msgstr "" #: src/unsafe-rust/dereferencing.md @@ -8882,7 +9792,8 @@ msgstr "" #: src/unsafe-rust/dereferencing.md msgid "" "// Safe because r1 and r2 were obtained from references and so are\n" -" // guaranteed to be non-null and properly aligned, the objects underlying\n" +" // 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" @@ -8912,14 +9823,15 @@ msgstr "" #: src/unsafe-rust/dereferencing.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." +"It is good practice (and required by the Android Rust style guide) to write " +"a comment for each `unsafe` block explaining how the code inside it " +"satisfies the safety requirements of the unsafe operations it is doing." msgstr "" #: src/unsafe-rust/dereferencing.md 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.:" +"In the case of pointer dereferences, this means that the pointers must be " +"[_valid_](https://doc.rust-lang.org/std/ptr/index.html#safety), i.e.:" msgstr "" #: src/unsafe-rust/dereferencing.md @@ -8927,7 +9839,9 @@ msgid "The pointer must be non-null." msgstr "" #: src/unsafe-rust/dereferencing.md -msgid "The pointer must be _dereferenceable_ (within the bounds of a single allocated object)." +msgid "" +"The pointer must be _dereferenceable_ (within the bounds of a single " +"allocated object)." msgstr "" #: src/unsafe-rust/dereferencing.md @@ -8940,8 +9854,8 @@ msgstr "" #: src/unsafe-rust/dereferencing.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." +"If the pointer was obtained by casting a reference, the underlying object " +"must be live and no reference may be used to access the memory." msgstr "" #: src/unsafe-rust/dereferencing.md @@ -8950,8 +9864,9 @@ msgstr "" #: src/unsafe-rust/dereferencing.md msgid "" -"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_." +"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/unsafe-rust/mutable-static.md @@ -8967,7 +9882,9 @@ msgid "\"HELLO_WORLD: {HELLO_WORLD}\"" msgstr "" #: src/unsafe-rust/mutable-static.md -msgid "However, since data races can occur, it is unsafe to read and write mutable static variables:" +msgid "" +"However, since data races can occur, it is unsafe to read and write mutable " +"static variables:" msgstr "" #: src/unsafe-rust/mutable-static.md @@ -8976,15 +9893,17 @@ msgstr "" #: src/unsafe-rust/mutable-static.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." +"The program here is safe because it is single-threaded. However, the Rust " +"compiler is conservative and will assume the worst. Try removing the " +"`unsafe` and see how the compiler explains that it is undefined behavior to " +"mutate a static from multiple threads." msgstr "" #: src/unsafe-rust/mutable-static.md 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." +"Using a mutable static is generally a bad idea, but there are some cases " +"where it might make sense in low-level `no_std` code, such as implementing a " +"heap allocator or working with some C APIs." msgstr "" #: src/unsafe-rust/unions.md @@ -9005,14 +9924,16 @@ msgstr "" #: src/unsafe-rust/unions.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." +"Unions are very rarely needed in Rust as you can usually use an enum. They " +"are occasionally needed for interacting with C library APIs." msgstr "" #: src/unsafe-rust/unions.md 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." +"If you just want to reinterpret bytes as a different type, you probably want " +"[`std::mem::transmute`](https://doc.rust-lang.org/stable/std/mem/fn." +"transmute.html) or a safe wrapper such as the [`zerocopy`](https://crates.io/" +"crates/zerocopy) crate." msgstr "" #: src/unsafe-rust/unsafe-functions.md @@ -9021,12 +9942,15 @@ msgstr "" #: 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:" +"A function or method can be marked `unsafe` if it has extra preconditions " +"you must uphold to avoid undefined behaviour:" msgstr "" -#: src/unsafe-rust/unsafe-functions.md 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/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/solutions-afternoon.md msgid "\"C\"" @@ -9071,7 +9995,9 @@ msgid "Writing Unsafe Functions" msgstr "" #: src/unsafe-rust/unsafe-functions.md -msgid "You can mark your own functions as `unsafe` if they require particular conditions to avoid undefined behaviour." +msgid "" +"You can mark your own functions as `unsafe` if they require particular " +"conditions to avoid undefined behaviour." msgstr "" #: src/unsafe-rust/unsafe-functions.md @@ -9093,26 +10019,32 @@ msgstr "" #: src/unsafe-rust/unsafe-functions.md msgid "" -"`get_unchecked`, like most `_unchecked` functions, is unsafe, because it can create UB if the range is incorrect. `abs` is " -"incorrect for a different reason: it is an external function (FFI). Calling external functions is usually only a problem " -"when those functions do things with pointers which might violate Rust's memory model, but in general any C function might " -"have undefined behaviour under any arbitrary circumstances." +"`get_unchecked`, like most `_unchecked` functions, is unsafe, because it can " +"create UB if the range is incorrect. `abs` is incorrect for a different " +"reason: it is an external function (FFI). Calling external functions is " +"usually only a problem when those functions do things with pointers which " +"might violate Rust's memory model, but in general any C function might have " +"undefined behaviour under any arbitrary circumstances." msgstr "" #: src/unsafe-rust/unsafe-functions.md msgid "" -"The `\"C\"` in this example is the ABI; [other ABIs are available too](https://doc.rust-lang.org/reference/items/external-" -"blocks.html)." +"The `\"C\"` in this example is the ABI; [other ABIs are available too]" +"(https://doc.rust-lang.org/reference/items/external-blocks.html)." msgstr "" #: src/unsafe-rust/unsafe-functions.md -msgid "We wouldn't actually use pointers for a `swap` function - it can be done safely with references." +msgid "" +"We wouldn't actually use pointers for a `swap` function - it can be done " +"safely with references." msgstr "" #: src/unsafe-rust/unsafe-functions.md msgid "" -"Note that unsafe code is allowed within an unsafe function without an `unsafe` block. We can prohibit this with " -"`#[deny(unsafe_op_in_unsafe_fn)]`. Try adding it and see what happens. This will likely change in a future Rust edition." +"Note that unsafe code is allowed within an unsafe function without an " +"`unsafe` block. We can prohibit this with `#[deny(unsafe_op_in_unsafe_fn)]`. " +"Try adding it and see what happens. This will likely change in a future Rust " +"edition." msgstr "" #: src/unsafe-rust/unsafe-traits.md @@ -9121,14 +10053,14 @@ msgstr "" #: src/unsafe-rust/unsafe-traits.md msgid "" -"Like with functions, you can mark a trait as `unsafe` if the implementation must guarantee particular conditions to avoid " -"undefined behaviour." +"Like with functions, you can mark a trait as `unsafe` if the implementation " +"must guarantee particular conditions to avoid undefined behaviour." msgstr "" #: src/unsafe-rust/unsafe-traits.md msgid "" -"For example, the `zerocopy` crate has an unsafe trait that looks [something like this](https://docs.rs/zerocopy/latest/" -"zerocopy/trait.AsBytes.html):" +"For example, the `zerocopy` crate has an unsafe trait that looks [something " +"like this](https://docs.rs/zerocopy/latest/zerocopy/trait.AsBytes.html):" msgstr "" #: src/unsafe-rust/unsafe-traits.md @@ -9144,12 +10076,14 @@ msgstr "" #: 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." +"There should be a `# Safety` section on the Rustdoc for the trait explaining " +"the requirements for the trait to be safely implemented." msgstr "" #: src/unsafe-rust/unsafe-traits.md -msgid "The actual safety section for `AsBytes` is rather longer and more complicated." +msgid "" +"The actual safety section for `AsBytes` is rather longer and more " +"complicated." msgstr "" #: src/unsafe-rust/unsafe-traits.md @@ -9162,8 +10096,9 @@ msgstr "" #: 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." +"Rust has great support for calling functions through a _foreign function " +"interface_ (FFI). We will use this to build a safe wrapper for the `libc` " +"functions you would use from C to read the names of files in a directory." msgstr "" #: src/unsafe-rust/exercise.md @@ -9184,8 +10119,9 @@ msgstr "" #: 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:" +"You will also want to browse the [`std::ffi`](https://doc.rust-lang.org/std/" +"ffi/) module. There you find a number of string types which you need for the " +"exercise:" msgstr "" #: src/unsafe-rust/exercise.md @@ -9198,8 +10134,8 @@ msgstr "" #: 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)" +"[`str`](https://doc.rust-lang.org/std/primitive.str.html) and [`String`]" +"(https://doc.rust-lang.org/std/string/struct.String.html)" msgstr "" #: src/unsafe-rust/exercise.md @@ -9212,8 +10148,8 @@ msgstr "" #: 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)" +"[`CStr`](https://doc.rust-lang.org/std/ffi/struct.CStr.html) and [`CString`]" +"(https://doc.rust-lang.org/std/ffi/struct.CString.html)" msgstr "" #: src/unsafe-rust/exercise.md @@ -9226,8 +10162,8 @@ msgstr "" #: 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)" +"[`OsStr`](https://doc.rust-lang.org/std/ffi/struct.OsStr.html) and " +"[`OsString`](https://doc.rust-lang.org/std/ffi/struct.OsString.html)" msgstr "" #: src/unsafe-rust/exercise.md @@ -9243,7 +10179,9 @@ msgid "You will convert between all these types:" msgstr "" #: src/unsafe-rust/exercise.md -msgid "`&str` to `CString`: you need to allocate space for a trailing `\\0` character," +msgid "" +"`&str` to `CString`: you need to allocate space for a trailing `\\0` " +"character," msgstr "" #: src/unsafe-rust/exercise.md @@ -9251,29 +10189,39 @@ msgid "`CString` to `*const i8`: you need a pointer to call C functions," msgstr "" #: src/unsafe-rust/exercise.md -msgid "`*const i8` to `&CStr`: you need something which can find the trailing `\\0` character," +msgid "" +"`*const i8` to `&CStr`: you need something which can find the trailing `\\0` " +"character," msgstr "" #: src/unsafe-rust/exercise.md -msgid "`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some unknown data\"," +msgid "" +"`&CStr` to `&[u8]`: a slice of bytes is the universal interface for \"some " +"unknown data\"," msgstr "" #: 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," +"`&[u8]` to `&OsStr`: `&OsStr` is a step towards `OsString`, use [`OsStrExt`]" +"(https://doc.rust-lang.org/std/os/unix/ffi/trait.OsStrExt.html) to create it," msgstr "" #: src/unsafe-rust/exercise.md -msgid "`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to return it and call `readdir` again." +msgid "" +"`&OsStr` to `OsString`: you need to clone the data in `&OsStr` to be able to " +"return it and call `readdir` again." msgstr "" #: src/unsafe-rust/exercise.md -msgid "The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very useful chapter about FFI." +msgid "" +"The [Nomicon](https://doc.rust-lang.org/nomicon/ffi.html) also has a very " +"useful chapter about FFI." msgstr "" #: src/unsafe-rust/exercise.md -msgid "Copy the code below to and fill in the missing functions and methods:" +msgid "" +"Copy the code below to and fill in the missing " +"functions and methods:" msgstr "" #: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md @@ -9304,8 +10252,10 @@ msgid "" "// See https://github.com/rust-lang/libc/issues/414 and the section on\n" " // _DARWIN_FEATURE_64_BIT_INODE in the macOS man page for stat(2).\n" " //\n" -" // \"Platforms that existed before these updates were available\" refers\n" -" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and PowerPC.\n" +" // \"Platforms that existed before these updates were available\" " +"refers\n" +" // to macOS (as opposed to iOS / wearOS / etc.) on Intel and " +"PowerPC.\n" msgstr "" #: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md @@ -9326,7 +10276,8 @@ msgstr "" msgid "// Call closedir as needed.\n" msgstr "" -#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md src/android/interoperability/with-c/rust.md +#: src/unsafe-rust/exercise.md src/unsafe-rust/solution.md +#: src/android/interoperability/with-c/rust.md msgid "\".\"" msgstr "" @@ -9412,54 +10363,71 @@ msgstr "" #: src/android.md msgid "" -"Rust is supported for system software on Android. This means that you can write new services, libraries, drivers or even " -"firmware in Rust (or improve existing code as needed)." +"Rust is supported for system software on Android. This means that you can " +"write new services, libraries, drivers or even firmware in Rust (or improve " +"existing code as needed)." msgstr "" #: src/android.md 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." +"We will attempt to call Rust from one of your own projects today. So try to " +"find a little corner of your code base where we can move some lines of code " +"to Rust. The fewer dependencies and \"exotic\" types the better. Something " +"that parses some raw bytes would be ideal." msgstr "" #: src/android.md -msgid "The speaker may mention any of the following given the increased use of Rust in Android:" +msgid "" +"The speaker may mention any of the following given the increased use of Rust " +"in Android:" msgstr "" #: src/android.md -msgid "Service example: [DNS over HTTP](https://security.googleblog.com/2022/07/dns-over-http3-in-android.html)" +msgid "" +"Service example: [DNS over HTTP](https://security.googleblog.com/2022/07/dns-" +"over-http3-in-android.html)" msgstr "" #: src/android.md -msgid "Libraries: [Rutabaga Virtual Graphics Interface](https://crosvm.dev/book/appendix/rutabaga_gfx.html)" +msgid "" +"Libraries: [Rutabaga Virtual Graphics Interface](https://crosvm.dev/book/" +"appendix/rutabaga_gfx.html)" msgstr "" #: src/android.md -msgid "Kernel Drivers: [Binder](https://lore.kernel.org/rust-for-linux/20231101-rust-binder-v1-0-08ba9197f637@google.com/)" +msgid "" +"Kernel Drivers: [Binder](https://lore.kernel.org/rust-for-linux/20231101-" +"rust-binder-v1-0-08ba9197f637@google.com/)" msgstr "" #: src/android.md -msgid "Firmware: [pKVM firmware](https://security.googleblog.com/2023/10/bare-metal-rust-in-android.html)" +msgid "" +"Firmware: [pKVM firmware](https://security.googleblog.com/2023/10/bare-metal-" +"rust-in-android.html)" msgstr "" #: src/android/setup.md msgid "" -"We will be using a Cuttlefish Android Virtual Device to test our code. Make sure you have access to one or create a new " -"one with:" +"We will be using a Cuttlefish Android Virtual Device to test our code. Make " +"sure you have access to one or create a new one with:" msgstr "" #: src/android/setup.md -msgid "Please see the [Android Developer Codelab](https://source.android.com/docs/setup/start) for details." +msgid "" +"Please see the [Android Developer Codelab](https://source.android.com/docs/" +"setup/start) for details." msgstr "" #: src/android/setup.md -msgid "Cuttlefish is a reference Android device designed to work on generic Linux desktops. MacOS support is also planned." +msgid "" +"Cuttlefish is a reference Android device designed to work on generic Linux " +"desktops. MacOS support is also planned." msgstr "" #: 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." +"The Cuttlefish system image maintains high fidelity to real devices, and is " +"the ideal emulator to run many Rust use cases." msgstr "" #: src/android/build-rules.md @@ -9495,7 +10463,9 @@ msgid "`rust_ffi`" msgstr "" #: src/android/build-rules.md -msgid "Produces a Rust C library usable by `cc` modules, and provides both static and shared variants." +msgid "" +"Produces a Rust C library usable by `cc` modules, and provides both static " +"and shared variants." msgstr "" #: src/android/build-rules.md @@ -9503,7 +10473,9 @@ msgid "`rust_proc_macro`" msgstr "" #: src/android/build-rules.md -msgid "Produces a `proc-macro` Rust library. These are analogous to compiler plugins." +msgid "" +"Produces a `proc-macro` Rust library. These are analogous to compiler " +"plugins." msgstr "" #: src/android/build-rules.md @@ -9527,7 +10499,9 @@ msgid "`rust_protobuf`" msgstr "" #: src/android/build-rules.md -msgid "Generates source and produces a Rust library that provides an interface for a particular protobuf." +msgid "" +"Generates source and produces a Rust library that provides an interface for " +"a particular protobuf." msgstr "" #: src/android/build-rules.md @@ -9535,7 +10509,9 @@ msgid "`rust_bindgen`" msgstr "" #: src/android/build-rules.md -msgid "Generates source and produces a Rust library containing Rust bindings to C libraries." +msgid "" +"Generates source and produces a Rust library containing Rust bindings to C " +"libraries." msgstr "" #: src/android/build-rules.md @@ -9547,24 +10523,29 @@ msgid "Additional items speaker may mention:" msgstr "" #: src/android/build-rules.md -msgid "Cargo is not optimized for multi-language repos, and also downloads packages from the internet." +msgid "" +"Cargo is not optimized for multi-language repos, and also downloads packages " +"from the internet." msgstr "" #: src/android/build-rules.md msgid "" -"For compliance and performance, Android must have crates in-tree. It must also interop with C/C++/Java code. Soong fills " -"that gap." +"For compliance and performance, Android must have crates in-tree. It must " +"also interop with C/C++/Java code. Soong fills that gap." msgstr "" #: src/android/build-rules.md -msgid "Soong has many similarities to Bazel, which is the open-source variant of Blaze (used in google3)." +msgid "" +"Soong has many similarities to Bazel, which is the open-source variant of " +"Blaze (used in google3)." msgstr "" #: src/android/build-rules.md msgid "" -"There is a plan to transition [Android](https://source.android.com/docs/setup/build/bazel/introduction), [ChromeOS]" -"(https://chromium.googlesource.com/chromiumos/bazel/), and [Fuchsia](https://source.android.com/docs/setup/build/bazel/" -"introduction) to Bazel." +"There is a plan to transition [Android](https://source.android.com/docs/" +"setup/build/bazel/introduction), [ChromeOS](https://chromium.googlesource." +"com/chromiumos/bazel/), and [Fuchsia](https://source.android.com/docs/setup/" +"build/bazel/introduction) to Bazel." msgstr "" #: src/android/build-rules.md @@ -9580,7 +10561,9 @@ msgid "Rust Binaries" msgstr "" #: src/android/build-rules/binary.md -msgid "Let us start with a simple application. At the root of an AOSP checkout, create the following files:" +msgid "" +"Let us start with a simple application. At the root of an AOSP checkout, " +"create the following files:" msgstr "" #: src/android/build-rules/binary.md src/android/build-rules/library.md @@ -9591,7 +10574,8 @@ msgstr "" msgid "\"hello_rust\"" msgstr "" -#: src/android/build-rules/binary.md src/android/build-rules/library.md src/android/logging.md +#: src/android/build-rules/binary.md src/android/build-rules/library.md +#: src/android/logging.md msgid "\"src/main.rs\"" msgstr "" @@ -9642,8 +10626,9 @@ msgstr "" #: src/android/build-rules/library.md msgid "" -"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`](https://cs.android.com/android/platform/" -"superproject/+/master:external/rust/crates/)." +"`libtextwrap`, which is a crate already vendored in [`external/rust/crates/`]" +"(https://cs.android.com/android/platform/superproject/+/master:external/rust/" +"crates/)." msgstr "" #: src/android/build-rules/library.md @@ -9666,7 +10651,8 @@ msgstr "" msgid "\"greetings\"" msgstr "" -#: src/android/build-rules/library.md src/android/aidl/example-service/service.md src/android/testing.md +#: src/android/build-rules/library.md +#: src/android/aidl/example-service/service.md src/android/testing.md #: src/android/interoperability/java.md msgid "\"src/lib.rs\"" msgstr "" @@ -9695,15 +10681,16 @@ msgstr "" 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 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/android/aidl.md msgid "" -"The [Android Interface Definition Language (AIDL)](https://developer.android.com/guide/components/aidl) is supported in " -"Rust:" +"The [Android Interface Definition Language (AIDL)](https://developer.android." +"com/guide/components/aidl) is supported in Rust:" msgstr "" #: src/android/aidl.md @@ -9716,8 +10703,9 @@ msgstr "" #: src/android/aidl/birthday-service.md msgid "" -"To illustrate how to use Rust with Binder, we're going to walk through the process of creating a Binder interface. We're " -"then going to both implement the described service and write client code that talks to that service." +"To illustrate how to use Rust with Binder, we're going to walk through the " +"process of creating a Binder interface. We're then going to both implement " +"the described service and write client code that talks to that service." msgstr "" #: src/android/aidl/example-service/interface.md @@ -9728,16 +10716,20 @@ msgstr "" msgid "You declare the API of your service using an AIDL interface:" msgstr "" -#: src/android/aidl/example-service/interface.md src/android/aidl/example-service/service-bindings.md -msgid "_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" +#: src/android/aidl/example-service/interface.md +#: src/android/aidl/example-service/service-bindings.md +msgid "" +"_birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl_:" msgstr "" -#: src/android/aidl/example-service/interface.md src/android/aidl/example-service/service-bindings.md +#: src/android/aidl/example-service/interface.md +#: src/android/aidl/example-service/service-bindings.md #: src/android/aidl/example-service/changing-definition.md msgid "/** Birthday service interface. */" msgstr "" -#: src/android/aidl/example-service/interface.md src/android/aidl/example-service/service-bindings.md +#: src/android/aidl/example-service/interface.md +#: src/android/aidl/example-service/service-bindings.md #: src/android/aidl/example-service/changing-definition.md msgid "/** Generate a Happy Birthday message. */" msgstr "" @@ -9760,8 +10752,9 @@ msgstr "" #: src/android/aidl/example-service/interface.md msgid "" -"Note that the directory structure under the `aidl/` directory needs to match the package name used in the AIDL file, i.e. " -"the package is `com.example.birthdayservice` and the file is at `aidl/com/example/IBirthdayService.aidl`." +"Note that the directory structure under the `aidl/` directory needs to match " +"the package name used in the AIDL file, i.e. the package is `com.example." +"birthdayservice` and the file is at `aidl/com/example/IBirthdayService.aidl`." msgstr "" #: src/android/aidl/example-service/service-bindings.md @@ -9769,7 +10762,9 @@ msgid "Generated Service API" msgstr "" #: src/android/aidl/example-service/service-bindings.md -msgid "Binder generates a trait corresponding to the interface definition. trait to talk to the service." +msgid "" +"Binder generates a trait corresponding to the interface definition. trait to " +"talk to the service." msgstr "" #: src/android/aidl/example-service/service-bindings.md @@ -9777,21 +10772,27 @@ msgid "_Generated trait_:" msgstr "" #: src/android/aidl/example-service/service-bindings.md -msgid "Your service will need to implement this trait, and your client will use this trait to talk to the service." +msgid "" +"Your service will need to implement this trait, and your client will use " +"this trait to talk to the service." msgstr "" #: src/android/aidl/example-service/service-bindings.md -msgid "The generated bindings can be found at `out/soong/.intermediates//`." +msgid "" +"The generated bindings can be found at `out/soong/.intermediates//`." msgstr "" #: src/android/aidl/example-service/service-bindings.md msgid "" -"Point out how the generated function signature, specifically the argument and return types, correspond the interface " -"definition." +"Point out how the generated function signature, specifically the argument " +"and return types, correspond the interface definition." msgstr "" #: src/android/aidl/example-service/service-bindings.md -msgid "`String` for an argument results in a different Rust type than `String` as a return type." +msgid "" +"`String` for an argument results in a different Rust type than `String` as a " +"return type." msgstr "" #: src/android/aidl/example-service/service.md @@ -9802,7 +10803,8 @@ msgstr "" msgid "We can now implement the AIDL service:" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/changing-implementation.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/changing-implementation.md msgid "_birthday_service/src/lib.rs_:" msgstr "" @@ -9810,41 +10812,51 @@ msgstr "" msgid "/// The `IBirthdayService` implementation.\n" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/changing-implementation.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/changing-implementation.md #: src/android/aidl/types/file-descriptor.md msgid "\"Happy Birthday {name}, congratulations with the {years} years!\"" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/server.md #: src/android/aidl/example-service/client.md msgid "_birthday_service/Android.bp_:" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/server.md msgid "\"libbirthdayservice\"" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/server.md #: src/android/aidl/example-service/client.md msgid "\"birthdayservice\"" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/server.md #: src/android/aidl/example-service/client.md msgid "\"com.example.birthdayservice-rust\"" msgstr "" -#: src/android/aidl/example-service/service.md src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/service.md +#: src/android/aidl/example-service/server.md #: src/android/aidl/example-service/client.md msgid "\"libbinder_rs\"" msgstr "" #: src/android/aidl/example-service/service.md -msgid "Point out the path to the generated `IBirthdayService` trait, and explain why each of the segments is necessary." +msgid "" +"Point out the path to the generated `IBirthdayService` trait, and explain " +"why each of the segments is necessary." msgstr "" #: src/android/aidl/example-service/service.md -msgid "TODO: What does the `binder::Interface` trait do? Are there methods to override? Where source?" +msgid "" +"TODO: What does the `binder::Interface` trait do? Are there methods to " +"override? Where source?" msgstr "" #: src/android/aidl/example-service/server.md @@ -9879,15 +10891,18 @@ msgstr "" msgid "\"src/server.rs\"" msgstr "" -#: src/android/aidl/example-service/server.md src/android/aidl/example-service/client.md +#: src/android/aidl/example-service/server.md +#: src/android/aidl/example-service/client.md msgid "// To avoid dynamic link error.\n" msgstr "" #: src/android/aidl/example-service/server.md msgid "" -"The process for taking a user-defined service implementation (in this case the `BirthdayService` type, which implements " -"the `IBirthdayService`) and starting it as a Binder service has multiple steps, and may appear more complicated than " -"students are used to if they've used Binder from C++ or another language. Explain to students why each step is necessary." +"The process for taking a user-defined service implementation (in this case " +"the `BirthdayService` type, which implements the `IBirthdayService`) and " +"starting it as a Binder service has multiple steps, and may appear more " +"complicated than students are used to if they've used Binder from C++ or " +"another language. Explain to students why each step is necessary." msgstr "" #: src/android/aidl/example-service/server.md @@ -9896,18 +10911,23 @@ msgstr "" #: src/android/aidl/example-service/server.md msgid "" -"Wrap the service object in corresponding `Bn*` type (`BnBirthdayService` in this case). This type is generated by Binder " -"and provides the common Binder functionality that would be provided by the `BnBinder` base class in C++. We don't have " -"inheritance in Rust, so instead we use composition, putting our `BirthdayService` within the generated `BnBinderService`." +"Wrap the service object in corresponding `Bn*` type (`BnBirthdayService` in " +"this case). This type is generated by Binder and provides the common Binder " +"functionality that would be provided by the `BnBinder` base class in C++. We " +"don't have inheritance in Rust, so instead we use composition, putting our " +"`BirthdayService` within the generated `BnBinderService`." msgstr "" #: src/android/aidl/example-service/server.md msgid "" -"Call `add_service`, giving it a service identifier and your service object (the `BnBirthdayService` object in the example)." +"Call `add_service`, giving it a service identifier and your service object " +"(the `BnBirthdayService` object in the example)." msgstr "" #: src/android/aidl/example-service/server.md -msgid "Call `join_thread_pool` to add the current thread to Binder's thread pool and start listening for connections." +msgid "" +"Call `join_thread_pool` to add the current thread to Binder's thread pool " +"and start listening for connections." msgstr "" #: src/android/aidl/example-service/deploy.md @@ -9918,7 +10938,8 @@ msgstr "" msgid "" "```shell\n" "m birthday_server\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_server\" /data/local/tmp\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" "```" @@ -9940,7 +10961,8 @@ msgstr "" msgid "Finally, we can create a Rust client for our new service." msgstr "" -#: src/android/aidl/example-service/client.md src/android/aidl/example-service/changing-implementation.md +#: src/android/aidl/example-service/client.md +#: src/android/aidl/example-service/changing-implementation.md msgid "_birthday_service/src/client.rs_:" msgstr "" @@ -9948,7 +10970,8 @@ msgstr "" msgid "/// Call the birthday service.\n" msgstr "" -#: src/android/aidl/example-service/client.md src/android/aidl/types/objects.md src/android/aidl/types/parcelables.md +#: src/android/aidl/example-service/client.md src/android/aidl/types/objects.md +#: src/android/aidl/types/parcelables.md #: src/android/aidl/types/file-descriptor.md msgid "\"Failed to connect to BirthdayService\"" msgstr "" @@ -9981,35 +11004,44 @@ msgstr "" msgid "" "```shell\n" "m birthday_client\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/birthday_client\" /data/local/tmp\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/example-service/client.md -msgid "`Strong` is the trait object representing the service that the client has connected to." +msgid "" +"`Strong` is the trait object representing the service " +"that the client has connected to." msgstr "" #: src/android/aidl/example-service/client.md msgid "" -"`Strong` is a custom smart pointer type for Binder. It handles both an in-process ref count for the service trait object, " -"and the global Binder ref count that tracks how many processes have a reference to the object." +"`Strong` is a custom smart pointer type for Binder. It handles both an in-" +"process ref count for the service trait object, and the global Binder ref " +"count that tracks how many processes have a reference to the object." msgstr "" #: src/android/aidl/example-service/client.md msgid "" -"Note that the trait object that the client uses to talk to the service uses the exact same trait that the server " -"implements. For a given Binder interface, there is a single Rust trait generated that both client and server use." +"Note that the trait object that the client uses to talk to the service uses " +"the exact same trait that the server implements. For a given Binder " +"interface, there is a single Rust trait generated that both client and " +"server use." msgstr "" #: src/android/aidl/example-service/client.md msgid "" -"Use the same service identifier used when registering the service. This should ideally be defined in a common crate that " -"both the client and server can depend on." +"Use the same service identifier used when registering the service. This " +"should ideally be defined in a common crate that both the client and server " +"can depend on." msgstr "" #: src/android/aidl/example-service/changing-definition.md -msgid "Let us extend the API with more functionality: we want to let clients specify a list of lines for the birthday card:" +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/aidl/example-service/changing-definition.md @@ -10018,8 +11050,9 @@ msgstr "" #: src/android/aidl/example-service/changing-definition.md msgid "" -"Note how the `String[]` in the AIDL definition is translated as a `&[String]` in Rust, i.e. that idiomatic Rust types are " -"used in the generated bindings wherever possible:" +"Note how the `String[]` in the AIDL definition is translated as a " +"`&[String]` in Rust, i.e. that idiomatic Rust types are used in the " +"generated bindings wherever possible:" msgstr "" #: src/android/aidl/example-service/changing-definition.md @@ -10055,7 +11088,8 @@ msgid "\"And also: many more\"" msgstr "" #: src/android/aidl/example-service/changing-implementation.md -msgid "TODO: Move code snippets into project files where they'll actually be built?" +msgid "" +"TODO: Move code snippets into project files where they'll actually be built?" msgstr "" #: src/android/aidl/types.md @@ -10075,7 +11109,9 @@ msgid "Collection types like slices, `Vec`s and string types are supported." msgstr "" #: src/android/aidl/types.md -msgid "References to AIDL objects and file handles can be sent between clients and services." +msgid "" +"References to AIDL objects and file handles can be sent between clients and " +"services." msgstr "" #: src/android/aidl/types.md @@ -10090,7 +11126,8 @@ msgstr "" msgid "AIDL Type" msgstr "" -#: src/android/aidl/types/primitives.md src/android/aidl/types/arrays.md src/android/interoperability/cpp/type-mapping.md +#: src/android/aidl/types/primitives.md src/android/aidl/types/arrays.md +#: src/android/interoperability/cpp/type-mapping.md msgid "Rust Type" msgstr "" @@ -10156,8 +11193,9 @@ msgstr "" #: src/android/aidl/types/arrays.md msgid "" -"The array types (`T[]`, `byte[]`, and `List`) get translated to the appropriate Rust array type depending on how they " -"are used in the function signature:" +"The array types (`T[]`, `byte[]`, and `List`) get translated to the " +"appropriate Rust array type depending on how they are used in the function " +"signature:" msgstr "" #: src/android/aidl/types/arrays.md @@ -10184,14 +11222,17 @@ msgstr "" msgid "Return" msgstr "" -#: src/android/aidl/types/arrays.md src/android/interoperability/cpp/type-mapping.md +#: src/android/aidl/types/arrays.md +#: src/android/interoperability/cpp/type-mapping.md msgid "`Vec`" msgstr "" #: src/android/aidl/types/arrays.md msgid "" -"In Android 13 or higher, fixed-size arrays are supported, i.e. `T[N]` becomes `[T; N]`. Fixed-size arrays can have " -"multiple dimensions (e.g. int\\[3\\]\\[4\\]). In the Java backend, fixed-size arrays are represented as array types." +"In Android 13 or higher, fixed-size arrays are supported, i.e. `T[N]` " +"becomes `[T; N]`. Fixed-size arrays can have multiple dimensions (e.g. int" +"\\[3\\]\\[4\\]). In the Java backend, fixed-size arrays are represented as " +"array types." msgstr "" #: src/android/aidl/types/arrays.md @@ -10199,15 +11240,21 @@ msgid "Arrays in parcelable fields always get translated to `Vec`." msgstr "" #: src/android/aidl/types/objects.md -msgid "AIDL objects can be sent either as a concrete AIDL type or as the type-erased `IBinder` interface:" +msgid "" +"AIDL objects can be sent either as a concrete AIDL type or as the type-" +"erased `IBinder` interface:" msgstr "" #: src/android/aidl/types/objects.md -msgid "**birthday_service/aidl/com/example/birthdayservice/IBirthdayInfoProvider.aidl**:" +msgid "" +"**birthday_service/aidl/com/example/birthdayservice/IBirthdayInfoProvider." +"aidl**:" msgstr "" -#: src/android/aidl/types/objects.md src/android/aidl/types/parcelables.md src/android/aidl/types/file-descriptor.md -msgid "**birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl**:" +#: src/android/aidl/types/objects.md src/android/aidl/types/parcelables.md +#: src/android/aidl/types/file-descriptor.md +msgid "" +"**birthday_service/aidl/com/example/birthdayservice/IBirthdayService.aidl**:" msgstr "" #: src/android/aidl/types/objects.md @@ -10218,7 +11265,8 @@ msgstr "" msgid "/** The same thing, but using `IBinder`. */" msgstr "" -#: src/android/aidl/types/objects.md src/android/aidl/types/parcelables.md src/android/aidl/types/file-descriptor.md +#: src/android/aidl/types/objects.md src/android/aidl/types/parcelables.md +#: src/android/aidl/types/file-descriptor.md msgid "**birthday_service/src/client.rs**:" msgstr "" @@ -10235,12 +11283,14 @@ msgid "// Send the binder object to the service.\n" msgstr "" #: src/android/aidl/types/objects.md -msgid "// Perform the same operation but passing the provider as an `SpIBinder`.\n" +msgid "" +"// Perform the same operation but passing the provider as an `SpIBinder`.\n" msgstr "" #: src/android/aidl/types/objects.md msgid "" -"Note the usage of `BnBirthdayInfoProvider`. This serves the same purpose as `BnBirthdayService` that we saw previously." +"Note the usage of `BnBirthdayInfoProvider`. This serves the same purpose as " +"`BnBirthdayService` that we saw previously." msgstr "" #: src/android/aidl/types/parcelables.md @@ -10248,7 +11298,8 @@ msgid "Binder for Rust supports sending parcelables directly:" msgstr "" #: src/android/aidl/types/parcelables.md -msgid "**birthday_service/aidl/com/example/birthdayservice/BirthdayInfo.aidl**:" +msgid "" +"**birthday_service/aidl/com/example/birthdayservice/BirthdayInfo.aidl**:" msgstr "" #: src/android/aidl/types/parcelables.md @@ -10256,7 +11307,9 @@ msgid "/** The same thing, but with a parcelable. */" msgstr "" #: src/android/aidl/types/file-descriptor.md -msgid "Files can be sent between Binder clients/servers using the `ParcelFileDescriptor` type:" +msgid "" +"Files can be sent between Binder clients/servers using the " +"`ParcelFileDescriptor` type:" msgstr "" #: src/android/aidl/types/file-descriptor.md @@ -10290,7 +11343,8 @@ msgstr "" #: src/android/aidl/types/file-descriptor.md msgid "" "// Convert the file descriptor to a `File`. `ParcelFileDescriptor` wraps\n" -" // an `OwnedFd`, which can be cloned and then used to create a `File`\n" +" // an `OwnedFd`, which can be cloned and then used to create a " +"`File`\n" " // object.\n" msgstr "" @@ -10300,12 +11354,15 @@ msgstr "" #: src/android/aidl/types/file-descriptor.md msgid "" -"`ParcelFileDescriptor` wraps an `OwnedFd`, and so can be created from a `File` (or any other type that wraps an " -"`OwnedFd`), and can be used to create a new `File` handle on the other side." +"`ParcelFileDescriptor` wraps an `OwnedFd`, and so can be created from a " +"`File` (or any other type that wraps an `OwnedFd`), and can be used to " +"create a new `File` handle on the other side." msgstr "" #: src/android/aidl/types/file-descriptor.md -msgid "Other types of file descriptors can be wrapped and sent, e.g. TCP, UDP, and UNIX sockets." +msgid "" +"Other types of file descriptors can be wrapped and sent, e.g. TCP, UDP, and " +"UNIX sockets." msgstr "" #: src/android/testing.md @@ -10314,8 +11371,8 @@ msgstr "" #: src/android/testing.md msgid "" -"Building on [Testing](../testing.md), we will now look at how unit tests work in AOSP. Use the `rust_test` module for your " -"unit tests:" +"Building on [Testing](../testing.md), we will now look at how unit tests " +"work in AOSP. Use the `rust_test` module for your unit tests:" msgstr "" #: src/android/testing.md @@ -10380,7 +11437,8 @@ msgid "" "INFO: Elapsed time: 2.666s, Critical Path: 2.40s\n" "INFO: 3 processes: 2 internal, 1 linux-sandbox.\n" "INFO: Build completed successfully, 3 total actions\n" -"//comprehensive-rust-android/testing:libleftpad_test_host PASSED in 2.3s\n" +"//comprehensive-rust-android/testing:libleftpad_test_host PASSED " +"in 2.3s\n" " PASSED libleftpad_test.tests::long_string (0.0s)\n" " PASSED libleftpad_test.tests::short_string (0.0s)\n" "Test cases: finished with 2 passing and 0 failing out of 2 test cases\n" @@ -10388,11 +11446,15 @@ msgid "" msgstr "" #: src/android/testing.md -msgid "Notice how you only mention the root of the library crate. Tests are found recursively in nested modules." +msgid "" +"Notice how you only mention the root of the library crate. Tests are found " +"recursively in nested modules." msgstr "" #: src/android/testing/googletest.md -msgid "The [GoogleTest](https://docs.rs/googletest/) crate allows for flexible test assertions using _matchers_:" +msgid "" +"The [GoogleTest](https://docs.rs/googletest/) crate allows for flexible test " +"assertions using _matchers_:" msgstr "" #: src/android/testing/googletest.md @@ -10404,19 +11466,23 @@ msgid "\"xyz\"" msgstr "" #: src/android/testing/googletest.md -msgid "If we change the last element to `\"!\"`, the test fails with a structured error message pin-pointing the error:" +msgid "" +"If we change the last element to `\"!\"`, the test fails with a structured " +"error message pin-pointing the error:" msgstr "" #: src/android/testing/googletest.md msgid "" -"GoogleTest is not part of the Rust Playground, so you need to run this example in a local environment. Use `cargo add " -"googletest` to quickly add it to an existing Cargo project." +"GoogleTest is not part of the Rust Playground, so you need to run this " +"example in a local environment. Use `cargo add googletest` to quickly add it " +"to an existing Cargo project." msgstr "" #: src/android/testing/googletest.md msgid "" -"The `use googletest::prelude::*;` line imports a number of [commonly used macros and types](https://docs.rs/googletest/" -"latest/googletest/prelude/index.html)." +"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/android/testing/googletest.md @@ -10424,7 +11490,9 @@ msgid "This just scratches the surface, there are many builtin matchers." msgstr "" #: src/android/testing/googletest.md -msgid "A particularly nice feature is that mismatches in multi-line strings are shown as a diff:" +msgid "" +"A particularly nice feature is that mismatches in multi-line strings are " +"shown as a diff:" msgstr "" #: src/android/testing/googletest.md @@ -10446,62 +11514,75 @@ msgid "shows a color-coded diff (colors not shown here):" msgstr "" #: src/android/testing/googletest.md -msgid "The crate is a Rust port of [GoogleTest for C++](https://google.github.io/googletest/)." +msgid "" +"The crate is a Rust port of [GoogleTest for C++](https://google.github.io/" +"googletest/)." msgstr "" #: src/android/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:" +"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/android/testing/mocking.md msgid "" -"Mockall is the recommended mocking library in Android (AOSP). 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." +"Mockall is the recommended mocking library in Android (AOSP). There are " +"other [mocking libraries available on crates.io](https://crates.io/keywords/" +"mock), in particular in the area of mocking HTTP services. The other mocking " +"libraries work in a similar fashion as Mockall, meaning that they make it " +"easy to get a mock implementation of a given trait." msgstr "" #: src/android/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." +"Note that mocking is somewhat _controversial_: mocks allow you to completely " +"isolate a test from its dependencies. The immediate result is faster and " +"more stable test execution. On the other hand, the mocks can be configured " +"wrongly and return output different from what the real dependencies would do." msgstr "" #: src/android/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." +"If at all possible, it is recommended that you use the real dependencies. As " +"an example, many databases allow you to configure an in-memory backend. This " +"means that you get the correct behavior in your tests, plus they are fast " +"and will automatically clean up after themselves." msgstr "" #: src/android/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." +"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/android/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." +"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/android/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:" +"Mockall has a lot more functionality. In particular, you can set up " +"expectations which depend on the arguments passed. Here we use this to mock " +"a cat which becomes hungry 3 hours after the last time it was fed:" msgstr "" #: src/android/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." +"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/android/logging.md -msgid "You should use the `log` crate to automatically log to `logcat` (on-device) or `stdout` (on-host):" +msgid "" +"You should use the `log` crate to automatically log to `logcat` (on-device) " +"or `stdout` (on-host):" msgstr "" #: src/android/logging.md @@ -10548,7 +11629,8 @@ msgstr "" msgid "\"Something went wrong!\"" msgstr "" -#: src/android/logging.md src/android/interoperability/with-c/bindgen.md src/android/interoperability/with-c/rust.md +#: 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 "" @@ -10556,7 +11638,8 @@ msgstr "" msgid "" "```shell\n" "m hello_rust_logs\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/hello_rust_logs\" /data/local/tmp\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 "" @@ -10566,7 +11649,9 @@ 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:" +msgid "" +"Rust has excellent support for interoperability with other languages. This " +"means that you can:" msgstr "" #: src/android/interoperability.md @@ -10579,7 +11664,8 @@ 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." +"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 @@ -10588,8 +11674,8 @@ 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." +"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 @@ -10601,11 +11687,15 @@ 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)." +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." +msgid "" +"This assumes full knowledge of the target platform. Not recommended for " +"production." msgstr "" #: src/android/interoperability/with-c.md @@ -10618,8 +11708,8 @@ 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." +"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 @@ -10671,7 +11761,9 @@ 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):" +msgid "" +"Create a wrapper header file for the library (not strictly needed in this " +"example):" msgstr "" #: src/android/interoperability/with-c/bindgen.md @@ -10726,7 +11818,8 @@ msgstr "" msgid "" "```shell\n" "m print_birthday_card\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/print_birthday_card\" /data/local/tmp\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 "" @@ -10827,19 +11920,23 @@ msgstr "" msgid "" "```shell\n" "m analyze_numbers\n" -"adb push \"$ANDROID_PRODUCT_OUT/system/bin/analyze_numbers\" /data/local/tmp\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." +"`#[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++." +msgid "" +"The [CXX crate](https://cxx.rs/) makes it possible to do safe " +"interoperability between Rust and C++." msgstr "" #: src/android/interoperability/cpp.md @@ -10848,8 +11945,9 @@ 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." +"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 @@ -10860,27 +11958,35 @@ msgstr "" msgid "// Shared structs with fields visible to both languages.\n" msgstr "" -#: src/android/interoperability/cpp/bridge.md src/android/interoperability/cpp/generated-cpp.md +#: 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/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 msgid "\"Rust\"" msgstr "" -#: src/android/interoperability/cpp/bridge.md src/android/interoperability/cpp/cpp-bridge.md +#: 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 +#: 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 +#: src/android/interoperability/cpp/bridge.md +#: src/android/interoperability/cpp/cpp-bridge.md msgid "\"include/blobstore.h\"" msgstr "" @@ -10890,15 +11996,17 @@ 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." +"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)." +"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 @@ -10922,14 +12030,17 @@ msgid "// Free function\n" msgstr "" #: src/android/interoperability/cpp/rust-bridge.md -msgid "Items declared in the `extern \"Rust\"` reference items that are in scope in the parent module." +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." +"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 @@ -10954,12 +12065,15 @@ 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++." +"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." +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 @@ -10972,8 +12086,10 @@ 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." +"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 @@ -10986,9 +12102,10 @@ 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." +"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 @@ -11000,17 +12117,22 @@ msgid "\"Success!\"" msgstr "" #: src/android/interoperability/cpp/rust-result.md -msgid "Rust functions that return `Result` are translated to exceptions on the C++ side." +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." +"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." +msgid "" +"A panic unwinding from Rust to C++ will always cause the process to " +"immediately terminate." msgstr "" #: src/android/interoperability/cpp/cpp-exception.md @@ -11023,15 +12145,16 @@ 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." +"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." +"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 @@ -11091,37 +12214,48 @@ 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." +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:" +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." +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." +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." +"`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-cpp.md +#: src/android/interoperability/cpp/android-cpp-genrules.md #: src/android/interoperability/cpp/android-build-rust.md msgid "Building in Android" msgstr "" #: 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." +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 +#: src/android/interoperability/cpp/android-build-cpp.md +#: src/android/interoperability/cpp/android-build-rust.md msgid "\"libcxx_test_cpp\"" msgstr "" @@ -11133,35 +12267,42 @@ msgstr "" msgid "\"cxx-bridge-header\"" msgstr "" -#: src/android/interoperability/cpp/android-build-cpp.md src/android/interoperability/cpp/android-cpp-genrules.md +#: 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 +#: 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." +"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." +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." +"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`." +"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 @@ -11178,7 +12319,8 @@ msgstr "" msgid "\"$(location cxxbridge) $(in) --header > $(out)\"" msgstr "" -#: src/android/interoperability/cpp/android-cpp-genrules.md src/android/interoperability/cpp/android-build-rust.md +#: src/android/interoperability/cpp/android-cpp-genrules.md +#: src/android/interoperability/cpp/android-build-rust.md msgid "\"lib.rs\"" msgstr "" @@ -11200,18 +12342,20 @@ 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." +"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." +"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`." +msgid "" +"Create a `rust_binary` that depends on `libcxx` and your `cc_library_static`." msgstr "" #: src/android/interoperability/cpp/android-build-rust.md @@ -11228,8 +12372,9 @@ 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." +"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 @@ -11298,8 +12443,8 @@ 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:" +"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 @@ -11312,8 +12457,8 @@ 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." +"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 @@ -11322,31 +12467,36 @@ 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." +"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." +"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):" +"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!)" +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." +"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 @@ -11359,15 +12509,17 @@ 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." +"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 "" -"The 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." +"The 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 @@ -11376,25 +12528,29 @@ 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." +"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)" +"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/)" +"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." +"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 @@ -11406,49 +12562,64 @@ 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." +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." +"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." +"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\"):" +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.)." +"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)" +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`." +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)." +"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`." +msgid "" +"`cargo` makes it easy to add a tool via `cargo install --locked cargo-vet`." msgstr "" #: src/chromium/cargo.md @@ -11456,21 +12627,25 @@ 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:" +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)." +"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." +"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 @@ -11478,7 +12653,9 @@ 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)" +msgid "" +"`serde_json_lenient` (experimented with in other parts of Google which " +"resulted in PRs with performance improvements)" msgstr "" #: src/chromium/cargo.md @@ -11487,36 +12664,41 @@ 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." +"`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." +"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, but `run_gnrt.py` asks `cargo` that only `--locked` content is allowed via `Cargo.lock`.)" +"`run_gnrt.py` uses Chromium's copy of `cargo` and `rustc`. `gnrt` depends on " +"third-party libraries downloaded from the internet, but `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:" +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" +"`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`)" +"`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 @@ -11525,8 +12707,8 @@ msgstr "" #: src/chromium/cargo.md msgid "" -"Various internal infrastructure (bots that build `rustc`, system for distributing the prebuilt toolchain to Chromium " -"engineers, etc.)" +"Various internal infrastructure (bots that build `rustc`, system for " +"distributing the prebuilt toolchain to Chromium engineers, etc.)" msgstr "" #: src/chromium/cargo.md @@ -11534,7 +12716,9 @@ 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)" +msgid "" +"Rust libraries vendored into `//third_party/rust` (audited by " +"security@chromium.org)" msgstr "" #: src/chromium/cargo.md @@ -11547,45 +12731,58 @@ 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)." +"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." +"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." +"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" ": : : :\n" -": Existing Chromium : : Chromium Rust Existing Rust :\n" -": \"C++\" : : \"wrapper\" crate :\n" -": +---------------+ : : +----------------+ +-------------+ :\n" -": | | : : | | | | :\n" -": | o-----+-+-----------+-+-> o-+----------+--> | :\n" -": | | : Language : | | Crate | | :\n" -": +---------------+ : boundary : +----------------+ API +-------------+ :\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" +"`- - - - - - - - - -' `- - - - - - - - - - - - - - - - - - - - - - " +"-'\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`." +"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 @@ -11610,8 +12807,9 @@ msgstr "" #: 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." +"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 @@ -11619,7 +12817,8 @@ 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`:" +msgid "" +"In some existing Chromium `BUILD.gn` file, declare a `rust_static_library`:" msgstr "" #: src/chromium/build-rules.md @@ -11635,27 +12834,33 @@ msgid "" 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." +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." +"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.)" +"(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." +"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 @@ -11664,8 +12869,10 @@ 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.)" +"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 @@ -11707,16 +12914,20 @@ 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," +"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" +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)" +msgid "" +"`gn gen out/Debug --export-rust-project` (or equivalent for your output " +"directory)" msgstr "" #: src/chromium/build-rules/vscode.md @@ -11725,14 +12936,14 @@ 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." +"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):" +"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 @@ -11740,33 +12951,41 @@ 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" +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)." +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`.)" +"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)" +"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)" +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)." +"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 @@ -11774,147 +12993,182 @@ msgid "Build rules exercise" msgstr "" #: src/exercises/chromium/build-rules.md -msgid "In your Chromium build, add a new Rust target to `//ui/base/BUILD.gn` containing:" +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 allow " -"unsafe code in your `gn` target." +"**Important**: note that `no_mangle` here is considered a type of unsafety " +"by the Rust compiler, so you'll need 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):" +"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." +"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!`." +"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 +#: 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)" +"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)" +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)" +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" +"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)" +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." +"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." +"`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." +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:" +"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)." +"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:" +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`." +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." +"`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." +"`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.)" +"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:" +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`)." +"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." +"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:" +"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)" +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)." +"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 @@ -11923,8 +13177,8 @@ msgstr "" #: 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:" +"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 @@ -11940,8 +13194,8 @@ 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:" +"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 @@ -11967,10 +13221,12 @@ 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:" +"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 @@ -11983,16 +13239,19 @@ 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:" +"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." +"`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 @@ -12009,8 +13268,9 @@ 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." +"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 @@ -12027,36 +13287,45 @@ 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." +"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++." +"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." +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:" +"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)" +"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)" +"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 @@ -12065,25 +13334,33 @@ 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)" +"`&[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." +"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)." +"`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." +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 @@ -12100,8 +13377,10 @@ 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." +"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 @@ -12122,12 +13401,16 @@ 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." +"**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)." +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 @@ -12135,31 +13418,41 @@ 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." +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." +"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." +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." +"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:" +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)" +msgid "" +"Its error handling is based around C++ exceptions (given on the next slide)" msgstr "" #: src/chromium/interoperability-with-cpp/limitations-of-cxx.md @@ -12168,8 +13461,8 @@ 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:" +"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 @@ -12178,8 +13471,8 @@ 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:" +"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 @@ -12188,14 +13481,15 @@ 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`)." +"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`." +"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 @@ -12203,11 +13497,15 @@ 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)" +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." +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 @@ -12216,9 +13514,11 @@ msgstr "" #: 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:" +"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 @@ -12227,21 +13527,25 @@ 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)." +"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)." +"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." +"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 @@ -12250,8 +13554,8 @@ msgstr "" #: 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:" +"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 @@ -12274,17 +13578,20 @@ 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." +"`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`)." +"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 @@ -12293,8 +13600,9 @@ 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" +"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 @@ -12307,7 +13615,9 @@ msgid "" msgstr "" #: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md -msgid "to your existing `rust_static_library` target alongside `crate_root` and `sources`." +msgid "" +"to your existing `rust_static_library` target alongside `crate_root` and " +"`sources`." msgstr "" #: src/chromium/interoperability-with-cpp/using-cxx-in-chromium.md @@ -12320,8 +13630,10 @@ 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)." +"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 @@ -12330,17 +13642,21 @@ 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." +"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." +"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 @@ -12353,14 +13669,15 @@ 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." +"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." +"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 @@ -12368,7 +13685,9 @@ 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." +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 @@ -12380,7 +13699,9 @@ 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." +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 @@ -12393,18 +13714,21 @@ 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." +"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)." +"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\"`" +msgid "" +"You may also need to `#include \"third_party/rust/cxx/v1/crate/include/cxx.h" +"\"`" msgstr "" #: src/exercises/chromium/interoperability-with-cpp.md @@ -12417,20 +13741,26 @@ 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." +"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." +"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." +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`)." +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 @@ -12447,8 +13777,9 @@ 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." +"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 @@ -12457,8 +13788,8 @@ 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)" +"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 @@ -12467,21 +13798,24 @@ 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`." +"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." +"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!" +"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 @@ -12533,11 +13867,15 @@ 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..." +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." +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 @@ -12562,8 +13900,10 @@ 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):" +"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 @@ -12579,25 +13919,29 @@ 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." +"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." +"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." +"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:" +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 @@ -12607,16 +13951,20 @@ 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." +"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." +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." +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 @@ -12625,8 +13973,10 @@ 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." +"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 @@ -12642,17 +13992,21 @@ 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." +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." +"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:" +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 @@ -12660,11 +14014,15 @@ 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`" +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`" +msgid "" +"At least one new `BUILD.gn` in `third_party/rust//v`" msgstr "" #: src/chromium/adding-third-party-crates/generating-gn-build-rules.md @@ -12673,28 +14031,33 @@ msgstr "" #: src/chromium/adding-third-party-crates/generating-gn-build-rules.md msgid "" -"The \"major semver version\" is a [Rust \"semver\" version number](https://doc.rust-lang.org/cargo/reference/semver.html)." +"The \"major semver version\" is a [Rust \"semver\" version number](https://" +"doc.rust-lang.org/cargo/reference/semver.html)." msgstr "" #: 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`." +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." +"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." +"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:" +msgid "" +"Some `build.rs` actions are automatically supported; others require action:" msgstr "" #: src/chromium/adding-third-party-crates/resolving-problems.md @@ -12751,18 +14114,23 @@ 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." +"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." +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:" +"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 @@ -12776,16 +14144,18 @@ 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." +"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." +"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 @@ -12802,15 +14172,18 @@ 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." +"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." +"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 @@ -12821,7 +14194,8 @@ msgstr "" msgid "" "```bob\n" " +------------+ +----------------------+\n" -"\"//third_party/rust\" | crate name | \"/v\" | major semver version | \":lib\"\n" +"\"//third_party/rust\" | crate name | \"/v\" | major semver version | \":lib" +"\"\n" " +------------+ +----------------------+\n" "```" msgstr "" @@ -12843,24 +14217,31 @@ 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?" +"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/)." +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:" +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?" +"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 @@ -12869,14 +14250,17 @@ 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))" +"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)" +"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 @@ -12885,14 +14269,15 @@ 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.)" +"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." +"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 @@ -12908,7 +14293,9 @@ 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//`" +msgid "" +"Metadata (`BUILD.gn` and `README.chromium`) in `//third_party/rust//" +"`" msgstr "" #: src/chromium/adding-third-party-crates/checking-in.md @@ -12916,41 +14303,48 @@ 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." +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." +"**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:" +"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." +"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." +"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`)." +"(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 @@ -12994,11 +14388,14 @@ 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." +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!" +msgid "" +"Thanks to [Daniel Liu](https://github.com/Daniel-Liu-c0deb0t) for this crate!" msgstr "" #: src/exercises/chromium/bringing-it-together.md @@ -13006,7 +14403,9 @@ 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." +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 @@ -13015,26 +14414,34 @@ 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." +"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." +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." +"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)." +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!)" +msgid "" +"(Obviously, real translations of Chrome require incredible care and " +"diligence. Don't ship this!)" msgstr "" #: src/exercises/chromium/bringing-it-together.md @@ -13043,51 +14450,61 @@ 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_`." +"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!" +"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." +"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)." +"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." +"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." +"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`." +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)." +"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 @@ -13096,15 +14513,16 @@ 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." +"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:" +"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 @@ -13125,17 +14543,21 @@ 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." +"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:" +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:" +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 @@ -13259,23 +14681,27 @@ 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`." +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." +"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)." +"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" +msgid "" +"// Safe because `HEAP` is only used here and `entry` is only called once.\n" msgstr "" #: src/bare-metal/alloc.md @@ -13292,25 +14718,28 @@ msgstr "" #: 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." +"`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." +"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." +"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." +"`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 @@ -13318,17 +14747,21 @@ 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." +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." +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." +"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 @@ -13336,7 +14769,9 @@ 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:" +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 @@ -13351,7 +14786,9 @@ msgstr "" msgid "// PIN_CNF fields\n" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md src/bare-metal/microcontrollers/pacs.md src/bare-metal/microcontrollers/hals.md +#: 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 "" @@ -13361,15 +14798,21 @@ msgid "" " // no aliases exist.\n" msgstr "" -#: src/bare-metal/microcontrollers/mmio.md src/bare-metal/microcontrollers/pacs.md src/bare-metal/microcontrollers/hals.md +#: 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." +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/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 "" @@ -13380,24 +14823,28 @@ 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." +"[`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." +"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." +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." +"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 @@ -13406,8 +14853,8 @@ 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." +"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 @@ -13416,9 +14863,10 @@ 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)." +"[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 @@ -13426,13 +14874,14 @@ 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." +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." +"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 @@ -13440,15 +14889,21 @@ 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." +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." +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." +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 @@ -13469,23 +14924,29 @@ 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." +"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." +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." +"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." +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 @@ -13494,8 +14955,8 @@ 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." +"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 @@ -13524,24 +14985,32 @@ 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." +"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." +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." +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." +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" +msgid "" +"SWD (Serial Wire Debug) and JTAG via CMSIS-DAP, ST-Link and J-Link probes" msgstr "" #: src/bare-metal/microcontrollers/probe-rs.md @@ -13554,33 +15023,42 @@ 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." +"`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." +"[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." +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." +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." +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." +"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 @@ -13589,8 +15067,8 @@ 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." +"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 @@ -13613,7 +15091,8 @@ msgstr "" msgid "In GDB, try running:" msgstr "" -#: src/bare-metal/microcontrollers/other-projects.md src/bare-metal/aps/other-projects.md +#: src/bare-metal/microcontrollers/other-projects.md +#: src/bare-metal/aps/other-projects.md msgid "Other projects" msgstr "" @@ -13626,7 +15105,8 @@ msgid "\"Real-Time Interrupt-driven Concurrency\"" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md -msgid "Shared resource management, message passing, task scheduling, timer queue" +msgid "" +"Shared resource management, message passing, task scheduling, timer queue" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md @@ -13642,7 +15122,9 @@ 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" +msgid "" +"Security-focused RTOS with preemptive scheduling and Memory Protection Unit " +"support" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md @@ -13650,7 +15132,9 @@ 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" +msgid "" +"Microkernel RTOS from Oxide Computer Company with memory protection, " +"unprivileged drivers, IPC" msgstr "" #: src/bare-metal/microcontrollers/other-projects.md @@ -13659,8 +15143,8 @@ 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)." +"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 @@ -13672,7 +15156,9 @@ 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." +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 @@ -13680,25 +15166,33 @@ msgid "Cortex-M only." msgstr "" #: src/bare-metal/microcontrollers/other-projects.md -msgid "Google uses TockOS on the Haven microcontroller for Titan security keys." +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." +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." +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." +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." +"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 @@ -13707,40 +15201,46 @@ 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/)." +"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." +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." +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." +"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." +"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." +"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." +"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 @@ -13764,7 +15264,8 @@ 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):" +msgid "" +"Or on Mac OS something like (the device name may be slightly different):" msgstr "" #: src/exercises/bare-metal/compass.md @@ -13813,7 +15314,8 @@ 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" +"// If button A is pressed, switch to the next mode and briefly blink all " +"LEDs\n" " // on.\n" msgstr "" @@ -13823,25 +15325,29 @@ 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." +"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." +"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." +"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." +msgid "" +"Before we can start running Rust code, we need to do some initialisation." msgstr "" #: src/bare-metal/aps/entry-point.md @@ -13851,7 +15357,8 @@ msgid "" ".global entry\n" "entry:\n" " /*\n" -" * Load and apply the memory management configuration, ready to enable MMU and\n" +" * Load and apply the memory management configuration, ready to enable " +"MMU and\n" " * caches.\n" " */\n" " adrp x30, idmap\n" @@ -13870,7 +15377,8 @@ msgid "" " mov_i x30, .Lsctlrval\n" "\n" " /*\n" -" * Ensure everything before this point has completed, then invalidate any\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" @@ -13880,7 +15388,8 @@ msgid "" " isb\n" "\n" " /*\n" -" * Configure sctlr_el1 to enable MMU and cache and don't proceed until this\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" @@ -13919,55 +15428,69 @@ 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." +"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." +"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." +"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:" +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." +"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.)" +"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." +"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." +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." +"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 @@ -13976,8 +15499,9 @@ 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:" +"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 @@ -14024,38 +15548,45 @@ 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.)" +"(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." +"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." +"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`." +"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." +"`_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`." +msgid "" +"Run the example in QEMU with `make qemu_psci` under `src/bare-metal/aps/" +"examples`." msgstr "" #: src/bare-metal/aps/mmio.md @@ -14071,29 +15602,35 @@ 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." +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." +"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." +"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." +"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." +msgid "" +"Use the `addr_of!` macro to get struct field pointers from a pointer to the " +"struct." msgstr "" #: src/bare-metal/aps/uart.md @@ -14102,8 +15639,8 @@ 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." +"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 @@ -14117,8 +15654,10 @@ msgid "" " ///\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" +" /// 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 "" @@ -14146,22 +15685,26 @@ 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 " +"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" +"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." +"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 @@ -14169,21 +15712,28 @@ 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." +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/solutions-afternoon.md +#: src/bare-metal/aps/uart/traits.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." +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`." +msgid "" +"Run the example in QEMU with `make qemu_minimal` under `src/bare-metal/aps/" +"examples`." msgstr "" #: src/bare-metal/aps/better-uart.md @@ -14192,9 +15742,11 @@ 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." +"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 @@ -14342,7 +15894,9 @@ 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." +msgid "" +"The [`bitflags`](https://crates.io/crates/bitflags) crate is useful for " +"working with bitflags." msgstr "" #: src/bare-metal/aps/better-uart/bitflags.md @@ -14387,8 +15941,8 @@ 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." +"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 @@ -14396,14 +15950,17 @@ 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." +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." +"[`#[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 @@ -14432,8 +15989,8 @@ 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." +"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 @@ -14441,7 +15998,9 @@ 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." +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 @@ -14478,18 +16037,21 @@ 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." +"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`." +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." +"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 @@ -14501,14 +16063,17 @@ 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`." +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/solutions-afternoon.md +#: src/bare-metal/aps/logging/using.md +#: src/exercises/bare-metal/solutions-afternoon.md msgid "\"{info}\"" msgstr "" @@ -14517,14 +16082,18 @@ 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`." +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:" +"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 @@ -14533,20 +16102,24 @@ 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." +"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." +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." +"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 @@ -14566,17 +16139,21 @@ 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)" +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" +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." +"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 @@ -14589,24 +16166,27 @@ 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:" +"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." +"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." +"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 @@ -14614,47 +16194,55 @@ msgid "Useful crates" msgstr "" #: src/bare-metal/useful-crates.md -msgid "We'll go over a few crates which solve some common problems in bare-metal programming." +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." +"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." +"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." +"`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." +"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." +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.)" +"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." +"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 @@ -14670,26 +16258,34 @@ 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." +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/)." +"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." +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:" +"[`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 @@ -14698,33 +16294,42 @@ 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.)" +"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." +"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." +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." +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?" +"`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." +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 @@ -14733,25 +16338,28 @@ 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." +"`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`." +"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." +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." +"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 @@ -14760,19 +16368,22 @@ msgstr "" #: 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." +"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." +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." +"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 @@ -14780,35 +16391,41 @@ 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." +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 +#: 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." +"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." +"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.)" +"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." +"_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 @@ -14817,18 +16434,20 @@ 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." +"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." +"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 -msgid "_src/exceptions.rs_ (you should only need to change this for the 3rd part of the exercise):" +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 @@ -14979,8 +16598,10 @@ msgid "" " ///\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" +" /// 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 "" @@ -15002,7 +16623,8 @@ msgstr "" #: src/exercises/bare-metal/solutions-afternoon.md msgid "" -"/// Returns whether the match register matches the RTC value, whether or not\n" +"/// Returns whether the match register matches the RTC value, whether or " +"not\n" " /// the interrupt is enabled.\n" msgstr "" @@ -15018,7 +16640,8 @@ msgstr "" msgid "" "/// Sets or clears the interrupt mask.\n" " ///\n" -" /// When the mask is true the interrupt is enabled; when it is false the\n" +" /// When the mask is true the interrupt is enabled; when it is false " +"the\n" " /// interrupt is disabled.\n" msgstr "" @@ -15031,27 +16654,33 @@ msgid "Welcome to Concurrency in Rust" msgstr "" #: src/concurrency.md -msgid "Rust has full support for concurrency using OS threads with mutexes and channels." +msgid "" +"Rust has full support for concurrency using OS threads with mutexes and " +"channels." msgstr "" #: 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." +"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.md -msgid "Rust lets us access OS concurrency toolkit: threads, sync. primitives, etc." +msgid "" +"Rust lets us access OS concurrency toolkit: threads, sync. primitives, etc." msgstr "" #: src/concurrency.md -msgid "The type system gives us safety for concurrency without any special features." +msgid "" +"The type system gives us safety for concurrency without any special features." msgstr "" #: src/concurrency.md msgid "" -"The same tools that help with \"concurrent\" access in a single thread (e.g., a called function that might mutate an " -"argument or save references to it to read later) save us from multi-threading issues." +"The same tools that help with \"concurrent\" access in a single thread (e." +"g., a called function that might mutate an argument or save references to it " +"to read later) save us from multi-threading issues." msgstr "" #: src/concurrency/threads.md @@ -15087,7 +16716,9 @@ msgid "Run the example." msgstr "" #: src/concurrency/threads.md -msgid "5ms timing is loose enough that main and spawned threads stay mostly in lockstep." +msgid "" +"5ms timing is loose enough that main and spawned threads stay mostly in " +"lockstep." msgstr "" #: src/concurrency/threads.md @@ -15095,7 +16726,9 @@ msgid "Notice that the program ends before the spawned thread reaches 10!" msgstr "" #: src/concurrency/threads.md -msgid "This is because main ends the program and spawned threads do not make it persist." +msgid "" +"This is because main ends the program and spawned threads do not make it " +"persist." msgstr "" #: src/concurrency/threads.md @@ -15107,18 +16740,21 @@ msgid "How do we wait around for the spawned thread to complete?" msgstr "" #: src/concurrency/threads.md -msgid "[`thread::spawn`](https://doc.rust-lang.org/std/thread/fn.spawn.html) returns a `JoinHandle`. Look at the docs." +msgid "" +"[`thread::spawn`](https://doc.rust-lang.org/std/thread/fn.spawn.html) " +"returns a `JoinHandle`. Look at the docs." msgstr "" #: src/concurrency/threads.md msgid "" -"`JoinHandle` has a [`.join()`](https://doc.rust-lang.org/std/thread/struct.JoinHandle.html#method.join) method that blocks." +"`JoinHandle` has a [`.join()`](https://doc.rust-lang.org/std/thread/struct." +"JoinHandle.html#method.join) method that blocks." msgstr "" #: src/concurrency/threads.md msgid "" -"Use `let handle = thread::spawn(...)` and later `handle.join()` to wait for the thread to finish and have the program " -"count all the way to 10." +"Use `let handle = thread::spawn(...)` and later `handle.join()` to wait for " +"the thread to finish and have the program count all the way to 10." msgstr "" #: src/concurrency/threads.md @@ -15130,17 +16766,21 @@ msgid "Look at docs again:" msgstr "" #: src/concurrency/threads.md -msgid "[`thread::spawn`](https://doc.rust-lang.org/std/thread/fn.spawn.html)'s closure returns `T`" +msgid "" +"[`thread::spawn`](https://doc.rust-lang.org/std/thread/fn.spawn.html)'s " +"closure returns `T`" msgstr "" #: src/concurrency/threads.md msgid "" -"`JoinHandle` [`.join()`](https://doc.rust-lang.org/std/thread/struct.JoinHandle.html#method.join) returns `thread::" -"Result`" +"`JoinHandle` [`.join()`](https://doc.rust-lang.org/std/thread/struct." +"JoinHandle.html#method.join) returns `thread::Result`" msgstr "" #: src/concurrency/threads.md -msgid "Use the `Result` return value from `handle.join()` to get access to the returned value." +msgid "" +"Use the `Result` return value from `handle.join()` to get access to the " +"returned value." msgstr "" #: src/concurrency/threads.md @@ -15152,7 +16792,9 @@ msgid "Trigger a panic in the thread. Note that this doesn't panic `main`." msgstr "" #: src/concurrency/threads.md -msgid "Access the panic payload. This is a good time to talk about [`Any`](https://doc.rust-lang.org/std/any/index.html)." +msgid "" +"Access the panic payload. This is a good time to talk about [`Any`](https://" +"doc.rust-lang.org/std/any/index.html)." msgstr "" #: src/concurrency/threads.md @@ -15176,7 +16818,9 @@ msgid "If we want to borrow?" msgstr "" #: src/concurrency/threads.md -msgid "Main kills child threads when it returns, but another function would just return and leave them running." +msgid "" +"Main kills child threads when it returns, but another function would just " +"return and leave them running." msgstr "" #: src/concurrency/threads.md @@ -15192,24 +16836,27 @@ msgid "Normal threads cannot borrow from their environment:" msgstr "" #: src/concurrency/scoped-threads.md -msgid "However, you can use a [scoped thread](https://doc.rust-lang.org/std/thread/fn.scope.html) for this:" +msgid "" +"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 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." +"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 msgid "" -"Normal Rust borrowing rules apply: you can either borrow mutably by one thread, or immutably by any number of threads." +"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 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." +"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 @@ -15218,14 +16865,15 @@ msgstr "" #: 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." +"`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 msgid "" -"`send()` and `recv()` return `Result`. If they return `Err`, it means the counterpart `Sender` or `Receiver` is dropped " -"and the channel is closed." +"`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 @@ -15249,51 +16897,59 @@ msgid "\"Main: got {msg}\"" msgstr "" #: src/concurrency/channels/bounded.md -msgid "With bounded (synchronous) channels, `send` can block the current thread:" +msgid "" +"With bounded (synchronous) channels, `send` can block the current thread:" msgstr "" #: 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." +"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 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." +"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 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 `recv`." +"A bounded channel with a size of zero is called a \"rendezvous channel\". " +"Every send will block the current thread until another thread calls `recv`." msgstr "" #: src/concurrency/send-sync.md -msgid "How does Rust know to forbid shared access across threads? The answer is in two traits:" +msgid "" +"How does Rust know to forbid shared access across threads? The answer is in " +"two traits:" msgstr "" #: 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." +"[`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 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." +"[`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 msgid "" -"`Send` and `Sync` are [unsafe traits](../unsafe/unsafe-traits.md). The compiler will automatically derive them for your " -"types as long as they only contain `Send` and `Sync` types. You can also implement them manually when you know it is valid." +"`Send` and `Sync` are [unsafe traits](../unsafe/unsafe-traits.md). The " +"compiler will automatically derive them for your types as long as they only " +"contain `Send` and `Sync` types. You can also implement them manually when " +"you know it is valid." msgstr "" #: src/concurrency/send-sync.md -msgid "One can think of these traits as markers that the type has certain thread-safety properties." +msgid "" +"One can think of these traits as markers that the type has certain thread-" +"safety properties." msgstr "" #: src/concurrency/send-sync.md @@ -15302,24 +16958,27 @@ msgstr "" #: 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." +"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 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." +"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 -msgid "As an example, a connection to the SQLite library must only be accessed from a single thread." +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 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." +"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 @@ -15332,15 +16991,18 @@ msgstr "" #: 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." +"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 msgid "" -"This is because if a type is Sync it means that it can be shared across multiple threads without the risk of data races or " -"other synchronization issues, so it is safe to move it to another thread. A reference to the type is also safe to move to " -"another thread, because the data it references can be accessed from any thread safely." +"This is because if a type is Sync it means that it can be shared across " +"multiple threads without the risk of data races or other synchronization " +"issues, so it is safe to move it to another thread. A reference to the type " +"is also safe to move to another thread, because the data it references can " +"be accessed from any thread safely." msgstr "" #: src/concurrency/send-sync/examples.md @@ -15376,7 +17038,9 @@ msgid "`AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions." msgstr "" #: src/concurrency/send-sync/examples.md -msgid "The generic types are typically `Send + Sync` when the type parameters are `Send + Sync`." +msgid "" +"The generic types are typically `Send + Sync` when the type parameters are " +"`Send + Sync`." msgstr "" #: src/concurrency/send-sync/examples.md @@ -15384,7 +17048,9 @@ msgid "`Send + !Sync`" msgstr "" #: 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:" +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 @@ -15408,11 +17074,14 @@ msgid "`!Send + Sync`" msgstr "" #: src/concurrency/send-sync/examples.md -msgid "These types are thread-safe, but they cannot be moved to another thread:" +msgid "" +"These types are thread-safe, but they cannot be moved to another thread:" msgstr "" #: src/concurrency/send-sync/examples.md -msgid "`MutexGuard`: Uses OS level primitives which must be deallocated on the thread which created them." +msgid "" +"`MutexGuard`: Uses OS level primitives which must be deallocated on " +"the thread which created them." msgstr "" #: src/concurrency/send-sync/examples.md @@ -15424,30 +17093,40 @@ msgid "These types are not thread-safe and cannot be moved to other threads:" msgstr "" #: src/concurrency/send-sync/examples.md -msgid "`Rc`: each `Rc` has a reference to an `RcBox`, which contains a non-atomic reference count." +msgid "" +"`Rc`: each `Rc` has a reference to an `RcBox`, which contains a non-" +"atomic reference count." msgstr "" #: src/concurrency/send-sync/examples.md -msgid "`*const T`, `*mut T`: Rust assumes raw pointers may have special concurrency considerations." +msgid "" +"`*const T`, `*mut T`: Rust assumes raw pointers may have special concurrency " +"considerations." msgstr "" #: src/concurrency/shared_state.md -msgid "Rust uses the type system to enforce synchronization of shared data. This is primarily done via two types:" +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 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," +"[`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 msgid "" -"[`Mutex`](https://doc.rust-lang.org/std/sync/struct.Mutex.html): ensures mutually exclusive access to the `T` value." +"[`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 -msgid "[`Arc`](https://doc.rust-lang.org/std/sync/struct.Arc.html) allows shared read-only access via `Arc::clone`:" +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 @@ -15459,21 +17138,27 @@ msgid "\"v: {v:?}\"" msgstr "" #: src/concurrency/shared_state/arc.md -msgid "`Arc` stands for \"Atomic Reference Counted\", a thread safe version of `Rc` that uses atomic operations." +msgid "" +"`Arc` stands for \"Atomic Reference Counted\", a thread safe version of `Rc` " +"that uses atomic operations." msgstr "" #: 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." +"`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 -msgid "`Arc::clone()` has the cost of atomic operations that get executed, but after that the use of the `T` is free." +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 -msgid "Beware of reference cycles, `Arc` does not use a garbage collector to detect them." +msgid "" +"Beware of reference cycles, `Arc` does not use a garbage collector to detect " +"them." msgstr "" #: src/concurrency/shared_state/arc.md @@ -15482,8 +17167,10 @@ msgstr "" #: 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 (another form of [interior mutability](../../borrowing/interior-mutability)):" +"[`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 (another form of [interior mutability](../../borrowing/interior-" +"mutability)):" msgstr "" #: src/concurrency/shared_state/mutex.md @@ -15492,26 +17179,33 @@ msgstr "" #: 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." +"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 -msgid "`Mutex` in Rust looks like a collection with just one element --- the protected data." +msgid "" +"`Mutex` in Rust looks like a collection with just one element --- the " +"protected data." msgstr "" #: src/concurrency/shared_state/mutex.md -msgid "It is not possible to forget to acquire the mutex before accessing the protected data." +msgid "" +"It is not possible to forget to acquire the mutex before accessing the " +"protected data." msgstr "" #: 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." +"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 -msgid "`Mutex` implements both `Send` and `Sync` iff (if and only if) `T` implements `Send`." +msgid "" +"`Mutex` implements both `Send` and `Sync` iff (if and only if) `T` " +"implements `Send`." msgstr "" #: src/concurrency/shared_state/mutex.md @@ -15524,9 +17218,11 @@ msgstr "" #: 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 inconsistent state. Calling `lock()` on a poisoned mutex fails with a [`PoisonError`](https://doc.rust-lang.org/" -"std/sync/struct.PoisonError.html). You can call `into_inner()` on the error to recover the data regardless." +"If the thread that held the `Mutex` panicked, the `Mutex` becomes \"poisoned" +"\" to signal that the data it protected might be in an inconsistent state. " +"Calling `lock()` on a poisoned mutex fails with a [`PoisonError`](https://" +"doc.rust-lang.org/std/sync/struct.PoisonError.html). You can call " +"`into_inner()` on the error to recover the data regardless." msgstr "" #: src/concurrency/shared_state/example.md @@ -15546,21 +17242,27 @@ msgid "Notable parts:" msgstr "" #: src/concurrency/shared_state/example.md -msgid "`v` is wrapped in both `Arc` and `Mutex`, because their concerns are orthogonal." +msgid "" +"`v` is wrapped in both `Arc` and `Mutex`, because their concerns are " +"orthogonal." msgstr "" #: src/concurrency/shared_state/example.md -msgid "Wrapping a `Mutex` in an `Arc` is a common pattern to share mutable state between threads." +msgid "" +"Wrapping a `Mutex` in an `Arc` is a common pattern to share mutable state " +"between threads." msgstr "" #: 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." +"`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 -msgid "Blocks are introduced to narrow the scope of the `LockGuard` as much as possible." +msgid "" +"Blocks are introduced to narrow the scope of the `LockGuard` as much as " +"possible." msgstr "" #: src/exercises/concurrency/morning.md @@ -15573,8 +17275,8 @@ msgstr "" #: 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." +"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 @@ -15583,71 +17285,93 @@ msgstr "" #: 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 served is a kind of spaghetti which has to be eaten with two forks. Each philosopher can only " -"alternately think and eat. Moreover, a philosopher can only eat their spaghetti when they have both a left and right fork. " -"Thus two forks will only be available when their two nearest neighbors are thinking, not eating. After an individual " -"philosopher finishes eating, they will put down both forks." +"Five philosophers dine together at the same table. Each philosopher has " +"their own place at the table. There is a fork between each plate. The dish " +"served is a kind of spaghetti which has to be eaten with two forks. Each " +"philosopher can only alternately think and eat. Moreover, a philosopher can " +"only eat their spaghetti when they have both a left and right fork. Thus two " +"forks will only be available when their two nearest neighbors are thinking, " +"not eating. After an individual philosopher finishes eating, they will put " +"down both forks." msgstr "" #: src/exercises/concurrency/dining-philosophers.md 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:" +"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 src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md msgid "" "// left_fork: ...\n" " // right_fork: ...\n" " // thoughts: ...\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 +#: 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/solutions-afternoon.md +#: src/exercises/concurrency/dining-philosophers.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 +#: 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 +#: 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 +#: 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 +#: 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 +#: 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 +#: 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/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/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md #: src/exercises/concurrency/solutions-afternoon.md msgid "// Create philosophers\n" msgstr "" @@ -15656,7 +17380,8 @@ msgstr "" 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/dining-philosophers.md +#: src/exercises/concurrency/dining-philosophers-async.md #: src/exercises/concurrency/solutions-afternoon.md msgid "// Output their thoughts\n" msgstr "" @@ -15677,33 +17402,39 @@ msgstr "" #: 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 should recursively check other pages on the same domain and keep doing this until all pages have " -"been validated." +"Let us use our new knowledge to create a multi-threaded link checker. It " +"should start at a webpage and check that links on the page are valid. It " +"should recursively check other pages on the same domain and keep doing this " +"until all pages have been validated." msgstr "" #: src/exercises/concurrency/link-checker.md 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:" +"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 msgid "" -"If `cargo add` fails with `error: no such subcommand`, then please edit the `Cargo.toml` file by hand. Add the " -"dependencies listed below." +"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 -msgid "You will also need a way to find links. We can use [`scraper`](https://docs.rs/scraper/) for that:" +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 -msgid "Finally, we'll need some way of handling errors. We use [`thiserror`](https://docs.rs/thiserror/) for that:" +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 -msgid "The `cargo add` calls will update the `Cargo.toml` file to look like this:" +msgid "" +"The `cargo add` calls will update the `Cargo.toml` file to look like this:" msgstr "" #: src/exercises/concurrency/link-checker.md @@ -15716,41 +17447,50 @@ msgid "" "publish = false\n" "\n" "[dependencies]\n" -"reqwest = { version = \"0.11.12\", features = [\"blocking\", \"rustls-tls\"] }\n" +"reqwest = { version = \"0.11.12\", features = [\"blocking\", \"rustls-tls" +"\"] }\n" "scraper = \"0.13.0\"\n" "thiserror = \"1.0.37\"\n" "```" msgstr "" #: 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/`." +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 msgid "Your `src/main.rs` file should look something like this:" msgstr "" -#: src/exercises/concurrency/link-checker.md src/exercises/concurrency/solutions-morning.md +#: 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 +#: 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 +#: 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 +#: 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 +#: 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 +#: src/exercises/concurrency/link-checker.md +#: src/exercises/concurrency/solutions-morning.md msgid "\"https://www.google.org\"" msgstr "" @@ -15768,14 +17508,15 @@ msgstr "" #: 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." +"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 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." +"Extend this to recursively extract links from all pages on the `www.google." +"org` domain. Put an upper limit of 100 pages or so so that you don't end up " +"being blocked by the site." msgstr "" #: src/exercises/concurrency/solutions-morning.md @@ -15810,7 +17551,8 @@ 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" +msgid "" +"/// Determine whether links within the given page should be extracted.\n" msgstr "" #: src/exercises/concurrency/solutions-morning.md @@ -15837,36 +17579,45 @@ msgstr "" #: 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 another task that is ready to make progress. The model allows running a larger number of tasks on " -"a limited number of threads. This is because the per-task overhead is typically very low and operating systems provide " +"\"Async\" is a concurrency model where multiple tasks are executed " +"concurrently by executing each task until it would block, then switching to " +"another task that is ready to make progress. The model allows running a " +"larger number of tasks on a limited number of threads. This is because the " +"per-task overhead is typically very low and operating systems provide " "primitives for efficiently identifying I/O that is able to proceed." msgstr "" #: src/async.md 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." +"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 -msgid "Futures are polled by an async runtime, and several different runtimes are available." +msgid "" +"Futures are polled by an async runtime, and several different runtimes are " +"available." msgstr "" #: 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." +"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 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." +"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 -msgid "At a high level, async Rust code looks very much like \"normal\" sequential code:" +msgid "" +"At a high level, async Rust code looks very much like \"normal\" sequential " +"code:" msgstr "" #: src/async/async-await.md @@ -15875,8 +17626,8 @@ msgstr "" #: 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!" +"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 @@ -15888,83 +17639,100 @@ msgid "Use `let future: () = async_main(10);` in `main` to see the type." msgstr "" #: src/async/async-await.md -msgid "The \"async\" keyword is syntactic sugar. The compiler replaces the return type with a future." +msgid "" +"The \"async\" keyword is syntactic sugar. The compiler replaces the return " +"type with a future." msgstr "" #: src/async/async-await.md -msgid "You cannot make `main` async, without additional instructions to the compiler on how to use the returned future." +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 msgid "" -"You need an executor to run async code. `block_on` blocks the current thread until the provided future has run to " -"completion." +"You need an executor to run async code. `block_on` blocks the current thread " +"until the provided future has run to completion." msgstr "" #: src/async/async-await.md msgid "" -"`.await` asynchronously waits for the completion of another operation. Unlike `block_on`, `.await` doesn't block the " -"current thread." +"`.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 -msgid "`.await` can only be used inside an `async` function (or block; these are introduced later)." +msgid "" +"`.await` can only be used inside an `async` function (or block; these are " +"introduced later)." msgstr "" #: 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 complete yet. A future can be polled, and `poll` returns a [`Poll`](https://doc.rust-lang.org/" -"std/task/enum.Poll.html)." +"[`Future`](https://doc.rust-lang.org/std/future/trait.Future.html) is a " +"trait, implemented by objects that represent an operation that may not be " +"complete yet. A future can be polled, and `poll` returns a [`Poll`](https://" +"doc.rust-lang.org/std/task/enum.Poll.html)." msgstr "" #: src/async/futures.md msgid "" -"An async function returns an `impl Future`. It's also possible (but uncommon) to implement `Future` for your own types. " -"For example, the `JoinHandle` returned from `tokio::spawn` implements `Future` to allow joining to it." +"An async function returns an `impl Future`. It's also possible (but " +"uncommon) to implement `Future` for your own types. For example, the " +"`JoinHandle` returned from `tokio::spawn` implements `Future` to allow " +"joining to it." msgstr "" #: src/async/futures.md 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." +"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 msgid "" -"The `Future` and `Poll` types are implemented exactly as shown; click the links to show the implementations in the docs." +"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 msgid "" -"We will not get to `Pin` and `Context`, as we will focus on writing async code, rather than building new async primitives. " -"Briefly:" +"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 -msgid "`Context` allows a Future to schedule itself to be polled again when an event occurs." +msgid "" +"`Context` allows a Future to schedule itself to be polled again when an " +"event occurs." msgstr "" #: 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`." +"`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 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:" +"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 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." +"[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 -msgid "[async-std](https://async.rs/): aims to be a \"std for async\", and includes a basic runtime in `async::task`." +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 @@ -15973,20 +17741,24 @@ msgstr "" #: 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." +"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 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." +"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 msgid "" -"Futures are \"inert\" in that they do not do anything (not even start an I/O operation) unless there is an executor " -"polling them. This differs from JS Promises, for example, which will run to completion even if they are never used." +"Futures are \"inert\" in that they do not do anything (not even start an I/O " +"operation) unless there is an executor polling them. This differs from JS " +"Promises, for example, which will run to completion even if they are never " +"used." msgstr "" #: src/async/runtimes/tokio.md @@ -16031,8 +17803,9 @@ msgstr "" #: 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." +"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 @@ -16049,9 +17822,11 @@ msgstr "" #: 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` method polls, corresponding loosely to a call stack. Concurrency within a task is possible by " -"polling multiple child futures, such as racing a timer and an I/O operation." +"A task has a single top-level future which the executor polls to make " +"progress. That future may have one or more nested futures that its `poll` " +"method polls, corresponding loosely to a call stack. Concurrency within a " +"task is possible by polling multiple child futures, such as racing a timer " +"and an I/O operation." msgstr "" #: src/async/tasks.md @@ -16079,33 +17854,39 @@ msgid "\"Thanks for dialing in, {name}!\\n\"" msgstr "" #: 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." +msgid "" +"Copy this example into your prepared `src/main.rs` and run it from there." msgstr "" #: 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/)." +"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 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?" +"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 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`." +"This is the first time we've seen an `async` block. This is similar to a " +"closure, but does not take any arguments. Its return value is a Future, " +"similar to an `async fn`." msgstr "" #: src/async/tasks.md -msgid "Refactor the async block into a function, and improve the error handling using `?`." +msgid "" +"Refactor the async block into a function, and improve the error handling " +"using `?`." msgstr "" #: src/async/channels.md -msgid "Several crates have support for asynchronous channels. For instance `tokio`:" +msgid "" +"Several crates have support for asynchronous channels. For instance `tokio`:" msgstr "" #: src/async/channels.md @@ -16133,7 +17914,9 @@ msgid "Change the channel size to `3` and see how it affects the execution." msgstr "" #: src/async/channels.md -msgid "Overall, the interface is similar to the `sync` channels as seen in the [morning class](concurrency/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 @@ -16142,14 +17925,16 @@ msgstr "" #: 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." +"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 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." +"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 @@ -16158,8 +17943,9 @@ msgstr "" #: 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." +"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 @@ -16172,8 +17958,9 @@ msgstr "" #: 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." +"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 @@ -16194,32 +17981,41 @@ msgstr "" #: 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`." +"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 -msgid "The risk of `join` is that one of the futures may never resolve, this would cause your program to stall." +msgid "" +"The risk of `join` is that one of the futures may never resolve, this would " +"cause your program to stall." msgstr "" #: src/async/control-flow/join.md msgid "" -"You can also combine `join_all` with `join!` for instance to join all requests to an http service as well as a database " -"query. Try adding a `tokio::time::sleep` to the future, using `futures::join!`. This is not a timeout (that requires " -"`select!`, explained in the next chapter), but demonstrates `join!`." +"You can also combine `join_all` with `join!` for instance to join all " +"requests to an http service as well as a database query. Try adding a " +"`tokio::time::sleep` to the future, using `futures::join!`. This is not a " +"timeout (that requires `select!`, explained in the next chapter), but " +"demonstrates `join!`." msgstr "" #: src/async/control-flow/select.md msgid "" -"A select operation waits until any of a set of futures is ready, and responds to that future's result. In JavaScript, this " -"is similar to `Promise.race`. In Python, it compares to `asyncio.wait(task_set, return_when=asyncio.FIRST_COMPLETED)`." +"A select operation waits until any of a set of futures is ready, and " +"responds to that future's result. In JavaScript, this is similar to `Promise." +"race`. In Python, it compares to `asyncio.wait(task_set, return_when=asyncio." +"FIRST_COMPLETED)`." msgstr "" #: src/async/control-flow/select.md 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." +"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 @@ -16244,28 +18040,34 @@ msgstr "" #: 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 whichever arrives first. Since the dog takes 50ms, it wins against the cat that take 500ms." +"In this example, we have a race between a cat and a dog. " +"`first_animal_to_finish_race` listens to both channels and will pick " +"whichever arrives first. Since the dog takes 50ms, it wins against the cat " +"that take 500ms." msgstr "" #: src/async/control-flow/select.md -msgid "You can use `oneshot` channels in this example as the channels are supposed to receive only one `send`." +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 -msgid "Try adding a deadline to the race, demonstrating selecting different sorts of futures." +msgid "" +"Try adding a deadline to the race, demonstrating selecting different sorts " +"of futures." msgstr "" #: 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." +"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 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." +"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 @@ -16274,8 +18076,10 @@ msgstr "" #: 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 with its share of pitfalls and footguns. We illustrate some of them in this chapter:" +"Async / await provides convenient and efficient abstraction for concurrent " +"asynchronous programming. However, the async/await model in Rust also comes " +"with its share of pitfalls and footguns. We illustrate some of them in this " +"chapter:" msgstr "" #: src/async/pitfalls.md @@ -16300,8 +18104,10 @@ msgstr "" #: 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 being executed. An easy workaround is to use async equivalent methods where possible." +"Most async runtimes only allow IO tasks to run concurrently. This means that " +"CPU blocking tasks will block the executor and prevent other tasks from " +"being executed. An easy workaround is to use async equivalent methods where " +"possible." msgstr "" #: src/async/pitfalls/blocking-executor.md @@ -16313,55 +18119,65 @@ msgid "\"current_thread\"" msgstr "" #: src/async/pitfalls/blocking-executor.md -msgid "Run the code and see that the sleeps happen consecutively rather than concurrently." +msgid "" +"Run the code and see that the sleeps happen consecutively rather than " +"concurrently." msgstr "" #: 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." +"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 -msgid "Switch the `std::thread::sleep` to `tokio::time::sleep` and await its result." +msgid "" +"Switch the `std::thread::sleep` to `tokio::time::sleep` and await its result." msgstr "" #: 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." +"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 msgid "" -"You should not think of tasks as OS threads. They do not map 1 to 1 and most executors will allow many tasks to run on a " -"single OS thread. This is particularly problematic when interacting with other libraries via FFI, where that library might " -"depend on thread-local storage or map to specific OS threads (e.g., CUDA). Prefer `tokio::task::spawn_blocking` in such " +"You should not think of tasks as OS threads. They do not map 1 to 1 and most " +"executors will allow many tasks to run on a single OS thread. This is " +"particularly problematic when interacting with other libraries via FFI, " +"where that library might depend on thread-local storage or map to specific " +"OS threads (e.g., CUDA). Prefer `tokio::task::spawn_blocking` in such " "situations." msgstr "" #: src/async/pitfalls/blocking-executor.md 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." +"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 msgid "" -"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." +"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 msgid "" -"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." +"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 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." +"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 @@ -16403,86 +18219,109 @@ 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." +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 -msgid "This serves as a summation of a few of the previous lessons, so take your time with it." +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 msgid "" -"Naively add a `_ = sleep(Duration::from_millis(100)) => { println!(..) }` to the `select!`. This will never execute. Why?" +"Naively add a `_ = sleep(Duration::from_millis(100)) => { println!(..) }` to " +"the `select!`. This will never execute. Why?" msgstr "" #: src/async/pitfalls/pin.md -msgid "Instead, add a `timeout_fut` containing that future outside of the `loop`:" +msgid "" +"Instead, add a `timeout_fut` containing that future outside of the `loop`:" msgstr "" #: 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`:" +"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 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." +"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 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." +"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 msgid "" -"Another alternative is to not use `pin` at all but spawn another task that will send to a `oneshot` channel every 100ms." +"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/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." +"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." +"`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." +"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 were stabilized only recently, in the 1.75 release. This required support for using return-" -"position `impl Trait` (RPIT) in traits, as the desugaring for `async fn` includes `-> impl Future`." +"Async methods in traits are were stabilized only recently, in the 1.75 " +"release. This required support for using return-position `impl Trait` (RPIT) " +"in traits, as the desugaring for `async fn` includes `-> impl Future`." msgstr "" #: src/async/pitfalls/async-traits.md -msgid "However, even with the native support today there are some pitfalls around `async fn` and RPIT in traits:" +msgid "" +"However, even with the native support today there are some pitfalls around " +"`async fn` and RPIT in traits:" msgstr "" #: src/async/pitfalls/async-traits.md -msgid "Return-position impl Trait captures all in-scope lifetimes (so some patterns of borrowing cannot be expressed)" +msgid "" +"Return-position impl Trait captures all in-scope lifetimes (so some patterns " +"of borrowing cannot be expressed)" msgstr "" #: src/async/pitfalls/async-traits.md -msgid "Traits whose methods use return-position `impl trait` or `async` are not `dyn` compatible." +msgid "" +"Traits whose methods use return-position `impl trait` or `async` are not " +"`dyn` compatible." msgstr "" #: src/async/pitfalls/async-traits.md msgid "" -"If we do need `dyn` support, the crate [async_trait](https://docs.rs/async-trait/latest/async_trait/) provides a " -"workaround through a macro, with some caveats:" +"If we do need `dyn` support, the crate [async_trait](https://docs.rs/async-" +"trait/latest/async_trait/) provides a workaround through a macro, with some " +"caveats:" msgstr "" #: src/async/pitfalls/async-traits.md @@ -16495,26 +18334,31 @@ msgstr "" #: 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." +"`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 msgid "" -"The challenges in language support for `async trait` are deep Rust and probably not worth describing in-depth. Niko " -"Matsakis did a good job of explaining them in [this post](https://smallcultfollowing.com/babysteps/blog/2019/10/26/async-" -"fn-in-traits-are-hard/) if you are interested in digging deeper." +"The challenges in language support for `async trait` are deep Rust and " +"probably not worth describing in-depth. Niko Matsakis did a good job of " +"explaining them in [this post](https://smallcultfollowing.com/babysteps/" +"blog/2019/10/26/async-fn-in-traits-are-hard/) if you are interested in " +"digging deeper." msgstr "" #: src/async/pitfalls/async-traits.md -msgid "Try creating a new sleeper struct that will sleep for a random amount of time and adding it to the Vec." +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 msgid "" -"Dropping a future implies it can never be polled again. This is called _cancellation_ and it can occur at any `await` " -"point. Care is needed to ensure the system works correctly even when futures are cancelled. For example, it shouldn't " -"deadlock or lose data." +"Dropping a future implies it can never be polled again. This is called " +"_cancellation_ and it can occur at any `await` point. Care is needed to " +"ensure the system works correctly even when futures are cancelled. For " +"example, it shouldn't deadlock or lose data." msgstr "" #: src/async/pitfalls/cancellation.md @@ -16531,12 +18375,14 @@ msgstr "" #: 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." +"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 -msgid "Unlike `panic` and `?`, cancellation is part of normal control flow (vs error-handling)." +msgid "" +"Unlike `panic` and `?`, cancellation is part of normal control flow (vs " +"error-handling)." msgstr "" #: src/async/pitfalls/cancellation.md @@ -16544,11 +18390,15 @@ msgid "The example loses parts of the string." msgstr "" #: src/async/pitfalls/cancellation.md -msgid "Whenever the `tick()` branch finishes first, `next()` and its `buf` are dropped." +msgid "" +"Whenever the `tick()` branch finishes first, `next()` and its `buf` are " +"dropped." msgstr "" #: src/async/pitfalls/cancellation.md -msgid "`LinesReader` can be made cancellation-safe by making `buf` part of the struct:" +msgid "" +"`LinesReader` can be made cancellation-safe by making `buf` part of the " +"struct:" msgstr "" #: src/async/pitfalls/cancellation.md @@ -16557,60 +18407,74 @@ msgstr "" #: 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'." +"[`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 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." +"[`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 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." +"[`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 -msgid "To practice your Async Rust skills, we have again two exercises for you:" +msgid "" +"To practice your Async Rust skills, we have again two exercises for you:" msgstr "" #: 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." +"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 msgid "" -"A Broadcast Chat Application: this is a larger project that allows you experiment with more advanced Async Rust features." +"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 src/exercises/concurrency/solutions-afternoon.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "Dining Philosophers --- Async" msgstr "" #: src/exercises/concurrency/dining-philosophers-async.md -msgid "See [dining philosophers](dining-philosophers.md) for a description of the problem." +msgid "" +"See [dining philosophers](dining-philosophers.md) for a description of the " +"problem." msgstr "" #: 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:" +"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 src/exercises/concurrency/solutions-afternoon.md +#: src/exercises/concurrency/dining-philosophers-async.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "// Keep trying until we have both forks\n" msgstr "" -#: src/exercises/concurrency/dining-philosophers-async.md src/exercises/concurrency/solutions-afternoon.md +#: 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 -msgid "Since this time you are using Async Rust, you'll need a `tokio` dependency. You can use the following `Cargo.toml`:" +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 @@ -16622,12 +18486,15 @@ 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 -msgid "Also note that this time you have to use the `Mutex` and the `mpsc` module from the `tokio` crate." +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 @@ -16636,15 +18503,19 @@ msgstr "" #: 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 publish their messages. The client reads user messages from the standard input, and sends them " -"to the server. The chat server broadcasts each message that it receives to all the clients." +"In this exercise, we want to use our new knowledge to implement a broadcast " +"chat application. We have a chat server that the clients connect to and " +"publish their messages. The client reads user messages from the standard " +"input, and sends them to the server. The chat server broadcasts each message " +"that it receives to all the clients." msgstr "" #: src/exercises/concurrency/chat-app.md 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/) for the communication between the client and the server." +"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/) for the communication between the client " +"and the server." msgstr "" #: src/exercises/concurrency/chat-app.md @@ -16667,7 +18538,8 @@ msgid "" "futures-util = { version = \"0.3.30\", features = [\"sink\"] }\n" "http = \"1.1.0\"\n" "tokio = { version = \"1.36.0\", features = [\"full\"] }\n" -"tokio-websockets = { version = \"0.7.0\", features = [\"client\", \"fastrand\", \"server\", \"sha1_smol\"] }\n" +"tokio-websockets = { version = \"0.7.0\", features = [\"client\", \"fastrand" +"\", \"server\", \"sha1_smol\"] }\n" "```" msgstr "" @@ -16677,32 +18549,36 @@ msgstr "" #: 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/). " -"Spend a few minutes to familiarize yourself with the API." +"You are going to need the following functions from `tokio` and " +"[`tokio_websockets`](https://docs.rs/tokio-websockets/). Spend a few minutes " +"to familiarize yourself with the API." msgstr "" #: 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 asynchronously reading messages from a Websocket Stream." +"[StreamExt::next()](https://docs.rs/futures-util/0.3.28/futures_util/stream/" +"trait.StreamExt.html#method.next) implemented by `WebSocketStream`: for " +"asynchronously reading messages from a Websocket Stream." msgstr "" #: src/exercises/concurrency/chat-app.md msgid "" -"[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/trait.SinkExt.html#method.send) implemented by " -"`WebSocketStream`: for asynchronously sending messages on a Websocket Stream." +"[SinkExt::send()](https://docs.rs/futures-util/0.3.28/futures_util/sink/" +"trait.SinkExt.html#method.send) implemented by `WebSocketStream`: for " +"asynchronously sending messages on a Websocket Stream." msgstr "" #: src/exercises/concurrency/chat-app.md 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." +"[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 msgid "" -"[Sender::subscribe()](https://docs.rs/tokio/latest/tokio/sync/broadcast/struct.Sender.html#method.subscribe): for " -"subscribing to a broadcast channel." +"[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 @@ -16711,19 +18587,24 @@ msgstr "" #: 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 for the server. You could potentially make them two separate Cargo projects, but we " -"are going to put them in a single Cargo project with two binaries. For this to work, the client and the server code should " -"go under `src/bin` (see the [documentation](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#binaries))." +"Normally in a Cargo project, you can have only one binary, and one `src/main." +"rs` file. In this project, we need two binaries. One for the client, and one " +"for the server. You could potentially make them two separate Cargo projects, " +"but we are going to put them in a single Cargo project with two binaries. " +"For this to work, the client and the server code should go under `src/bin` " +"(see the [documentation](https://doc.rust-lang.org/cargo/reference/cargo-" +"targets.html#binaries))." msgstr "" #: src/exercises/concurrency/chat-app.md 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." +"Copy the following server and client code into `src/bin/server.rs` and `src/" +"bin/client.rs`, respectively. Your task is to complete these files as " +"described below." msgstr "" -#: src/exercises/concurrency/chat-app.md src/exercises/concurrency/solutions-afternoon.md +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "_src/bin/server.rs_:" msgstr "" @@ -16731,27 +18612,33 @@ msgstr "" 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 +#: 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 src/exercises/concurrency/solutions-afternoon.md +#: 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 +#: 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 +#: 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 +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "_src/bin/client.rs_:" msgstr "" -#: src/exercises/concurrency/chat-app.md src/exercises/concurrency/solutions-afternoon.md +#: src/exercises/concurrency/chat-app.md +#: src/exercises/concurrency/solutions-afternoon.md msgid "\"ws://127.0.0.1:2000\"" msgstr "" @@ -16773,8 +18660,9 @@ msgstr "" #: 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." +"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 @@ -16783,13 +18671,16 @@ msgstr "" #: 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 sending them to the server, and (2) receiving messages from the server, and displaying " -"them for the user." +"Hint: As before, use `tokio::select!` in a continuous loop for concurrently " +"performing two tasks: (1) reading user messages from standard input and " +"sending them to the server, and (2) receiving messages from the server, and " +"displaying them for the user." msgstr "" #: src/exercises/concurrency/chat-app.md -msgid "Optional: Once you are done, change the code to broadcast messages to all clients, but the sender of the message." +msgid "" +"Optional: Once you are done, change the code to broadcast messages to all " +"clients, but the sender of the message." msgstr "" #: src/exercises/concurrency/solutions-afternoon.md @@ -16852,20 +18743,24 @@ msgid "\"From server: {}\"" msgstr "" #: src/thanks.md -msgid "_Thank you for taking Comprehensive Rust 🦀!_ We hope you enjoyed it and that it was useful." +msgid "" +"_Thank you for taking Comprehensive Rust 🦀!_ We hope you enjoyed it and that " +"it was useful." msgstr "" #: 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, please get in [contact with us on GitHub](https://github.com/google/comprehensive-rust/" -"discussions). We would love to hear from you." +"We've had a lot of fun putting the course together. The course is not " +"perfect, so if you spotted any mistakes or have ideas for improvements, " +"please get in [contact with us on GitHub](https://github.com/google/" +"comprehensive-rust/discussions). We would love to hear from you." msgstr "" #: src/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." +"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 @@ -16883,7 +18778,8 @@ msgstr "" #: 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)." +"Low-level Rust development, often deployed to a system without an operating " +"system. See [Bare-metal Rust](bare-metal.md)." msgstr "" #: src/glossary.md @@ -16913,7 +18809,8 @@ msgstr "" #: src/glossary.md msgid "" "build: \n" -"The process of converting source code into executable code or a usable program." +"The process of converting source code into executable code or a usable " +"program." msgstr "" #: src/glossary.md @@ -16955,7 +18852,8 @@ msgstr "" #: src/glossary.md msgid "" "control flow: \n" -"The order in which the individual statements or instructions are executed in a program." +"The order in which the individual statements or instructions are executed in " +"a program." msgstr "" #: src/glossary.md @@ -16967,7 +18865,8 @@ msgstr "" #: src/glossary.md msgid "" "enumeration: \n" -"A data type that holds one of several named constants, possibly with an associated tuple or struct." +"A data type that holds one of several named constants, possibly with an " +"associated tuple or struct." msgstr "" #: src/glossary.md @@ -16979,7 +18878,8 @@ msgstr "" #: src/glossary.md msgid "" "error handling: \n" -"The process of managing and responding to errors that occur during program execution." +"The process of managing and responding to errors that occur during program " +"execution." msgstr "" #: src/glossary.md @@ -16997,13 +18897,15 @@ msgstr "" #: src/glossary.md msgid "" "garbage collector: \n" -"A mechanism that automatically frees up memory occupied by objects that are no longer in use." +"A mechanism that automatically frees up memory occupied by objects that are " +"no longer in use." msgstr "" #: src/glossary.md msgid "" "generics: \n" -"A feature that allows writing code with placeholders for types, enabling code reuse with different data types." +"A feature that allows writing code with placeholders for types, enabling " +"code reuse with different data types." msgstr "" #: src/glossary.md @@ -17015,13 +18917,15 @@ msgstr "" #: src/glossary.md msgid "" "integration test: \n" -"A type of test that verifies the interactions between different parts or components of a system." +"A type of test that verifies the interactions between different parts or " +"components of a system." msgstr "" #: 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." +"A reserved word in a programming language that has a specific meaning and " +"cannot be used as an identifier." msgstr "" #: src/glossary.md @@ -17033,8 +18937,9 @@ msgstr "" #: src/glossary.md msgid "" "macro: \n" -"Rust macros can be recognized by a `!` in the name. Macros are used when normal functions are not enough. A typical " -"example is `format!`, which takes a variable number of arguments, which isn't supported by Rust functions." +"Rust macros can be recognized by a `!` in the name. Macros are used when " +"normal functions are not enough. A typical example is `format!`, which takes " +"a variable number of arguments, which isn't supported by Rust functions." msgstr "" #: src/glossary.md @@ -17046,14 +18951,15 @@ msgstr "" #: src/glossary.md msgid "" "match: \n" -"A control flow construct in Rust that allows for pattern matching on the value of an expression." +"A control flow construct in Rust that allows for pattern matching on the " +"value of an expression." msgstr "" #: 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." +"A situation where a program fails to release memory that is no longer " +"needed, leading to a gradual increase in memory usage." msgstr "" #: src/glossary.md @@ -17065,7 +18971,8 @@ msgstr "" #: src/glossary.md msgid "" "module: \n" -"A namespace that contains definitions, such as functions, types, or traits, to organize code in Rust." +"A namespace that contains definitions, such as functions, types, or traits, " +"to organize code in Rust." msgstr "" #: src/glossary.md @@ -17077,19 +18984,22 @@ msgstr "" #: src/glossary.md msgid "" "mutable: \n" -"A property in Rust that allows variables to be modified after they have been declared." +"A property in Rust that allows variables to be modified after they have been " +"declared." msgstr "" #: src/glossary.md msgid "" "ownership: \n" -"The concept in Rust that defines which part of the code is responsible for managing the memory associated with a value." +"The concept in Rust that defines which part of the code is responsible for " +"managing the memory associated with a value." msgstr "" #: src/glossary.md msgid "" "panic: \n" -"An unrecoverable error condition in Rust that results in the termination of the program." +"An unrecoverable error condition in Rust that results in the termination of " +"the program." msgstr "" #: src/glossary.md @@ -17101,7 +19011,8 @@ msgstr "" #: src/glossary.md msgid "" "pattern: \n" -"A combination of values, literals, or structures that can be matched against an expression in Rust." +"A combination of values, literals, or structures that can be matched against " +"an expression in Rust." msgstr "" #: src/glossary.md @@ -17113,7 +19024,8 @@ msgstr "" #: src/glossary.md msgid "" "program: \n" -"A set of instructions that a computer can execute to perform a specific task or solve a particular problem." +"A set of instructions that a computer can execute to perform a specific task " +"or solve a particular problem." msgstr "" #: src/glossary.md @@ -17125,14 +19037,15 @@ msgstr "" #: src/glossary.md msgid "" "receiver: \n" -"The first parameter in a Rust method that represents the instance on which the method is called." +"The first parameter in a Rust method that represents the instance on which " +"the method is called." msgstr "" #: 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." +"A memory management technique in which the number of references to an object " +"is tracked, and the object is deallocated when the count reaches zero." msgstr "" #: src/glossary.md @@ -17144,7 +19057,8 @@ msgstr "" #: src/glossary.md msgid "" "Rust: \n" -"A systems programming language that focuses on safety, performance, and concurrency." +"A systems programming language that focuses on safety, performance, and " +"concurrency." msgstr "" #: src/glossary.md @@ -17168,7 +19082,8 @@ msgstr "" #: src/glossary.md msgid "" "safe: \n" -"Refers to code that adheres to Rust's ownership and borrowing rules, preventing memory-related errors." +"Refers to code that adheres to Rust's ownership and borrowing rules, " +"preventing memory-related errors." msgstr "" #: src/glossary.md @@ -17186,25 +19101,29 @@ msgstr "" #: src/glossary.md msgid "" "static: \n" -"A keyword in Rust used to define static variables or items with a `'static` lifetime." +"A keyword in Rust used to define static variables or items with a `'static` " +"lifetime." msgstr "" #: src/glossary.md msgid "" "string: \n" -"A data type storing textual data. See [`String` vs `str`](basic-syntax/string-slices.html) for more." +"A data type storing textual data. See [`String` vs `str`](basic-syntax/" +"string-slices.html) for more." msgstr "" #: src/glossary.md msgid "" "struct: \n" -"A composite data type in Rust that groups together variables of different types under a single name." +"A composite data type in Rust that groups together variables of different " +"types under a single name." msgstr "" #: src/glossary.md msgid "" "test: \n" -"A Rust module containing functions that test the correctness of other functions." +"A Rust module containing functions that test the correctness of other " +"functions." msgstr "" #: src/glossary.md @@ -17216,44 +19135,50 @@ msgstr "" #: src/glossary.md msgid "" "thread safety: \n" -"The property of a program that ensures correct behavior in a multithreaded environment." +"The property of a program that ensures correct behavior in a multithreaded " +"environment." msgstr "" #: src/glossary.md msgid "" "trait: \n" -"A collection of methods defined for an unknown type, providing a way to achieve polymorphism in Rust." +"A collection of methods defined for an unknown type, providing a way to " +"achieve polymorphism in Rust." msgstr "" #: src/glossary.md msgid "" "trait bound: \n" -"An abstraction where you can require types to implement some traits of your interest." +"An abstraction where you can require types to implement some traits of your " +"interest." msgstr "" #: 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." +"A composite data type that contains variables of different types. Tuple " +"fields have no names, and are accessed by their ordinal numbers." msgstr "" #: src/glossary.md msgid "" "type: \n" -"A classification that specifies which operations can be performed on values of a particular kind in Rust." +"A classification that specifies which operations can be performed on values " +"of a particular kind in Rust." msgstr "" #: src/glossary.md msgid "" "type inference: \n" -"The ability of the Rust compiler to deduce the type of a variable or expression." +"The ability of the Rust compiler to deduce the type of a variable or " +"expression." msgstr "" #: src/glossary.md msgid "" "undefined behavior: \n" -"Actions or conditions in Rust that have no specified result, often leading to unpredictable program behavior." +"Actions or conditions in Rust that have no specified result, often leading " +"to unpredictable program behavior." msgstr "" #: src/glossary.md @@ -17265,8 +19190,8 @@ msgstr "" #: src/glossary.md msgid "" "unit test: \n" -"Rust comes with built-in support for running small unit tests and larger integration tests. See [Unit Tests](testing/unit-" -"tests.html)." +"Rust comes with built-in support for running small unit tests and larger " +"integration tests. See [Unit Tests](testing/unit-tests.html)." msgstr "" #: src/glossary.md @@ -17278,7 +19203,8 @@ msgstr "" #: src/glossary.md msgid "" "unsafe: \n" -"The subset of Rust which allows you to trigger _undefined behavior_. See [Unsafe Rust](unsafe.html)." +"The subset of Rust which allows you to trigger _undefined behavior_. See " +"[Unsafe Rust](unsafe.html)." msgstr "" #: src/glossary.md @@ -17292,7 +19218,9 @@ msgid "Other Rust Resources" msgstr "" #: src/other-resources.md -msgid "The Rust community has created a wealth of high-quality and free resources online." +msgid "" +"The Rust community has created a wealth of high-quality and free resources " +"online." msgstr "" #: src/other-resources.md @@ -17305,25 +19233,29 @@ msgstr "" #: src/other-resources.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." +"[The Rust Programming Language](https://doc.rust-lang.org/book/): the " +"canonical free book about Rust. Covers the language in detail and includes a " +"few projects for people to build." msgstr "" #: src/other-resources.md 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." +"[Rust By Example](https://doc.rust-lang.org/rust-by-example/): covers the " +"Rust syntax via a series of examples which showcase different constructs. " +"Sometimes includes small exercises where you are asked to expand on the code " +"in the examples." msgstr "" #: src/other-resources.md -msgid "[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation of the standard library for Rust." +msgid "" +"[Rust Standard Library](https://doc.rust-lang.org/std/): full documentation " +"of the standard library for Rust." msgstr "" #: 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." +"[The Rust Reference](https://doc.rust-lang.org/reference/): an incomplete " +"book which describes the Rust grammar and memory model." msgstr "" #: src/other-resources.md @@ -17332,20 +19264,23 @@ msgstr "" #: src/other-resources.md msgid "" -"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, including working with raw pointers and " -"interfacing with other languages (FFI)." +"[The Rustonomicon](https://doc.rust-lang.org/nomicon/): covers unsafe Rust, " +"including working with raw pointers and interfacing with other languages " +"(FFI)." msgstr "" #: src/other-resources.md 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." +"[Asynchronous Programming in Rust](https://rust-lang.github.io/async-book/): " +"covers the new asynchronous programming model which was introduced after the " +"Rust Book was written." msgstr "" #: src/other-resources.md 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." +"[The Embedded Rust Book](https://doc.rust-lang.org/stable/embedded-book/): " +"an introduction to using Rust on embedded devices without an operating " +"system." msgstr "" #: src/other-resources.md @@ -17358,60 +19293,72 @@ msgstr "" #: src/other-resources.md msgid "" -"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust from the perspective of low-level C " -"programmers." +"[Learn Rust the Dangerous Way](http://cliffle.com/p/dangerust/): covers Rust " +"from the perspective of low-level C programmers." msgstr "" #: src/other-resources.md 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." +"[Rust for Embedded C Programmers](https://docs.opentitan.org/doc/ug/" +"rust_for_c/): covers Rust from the perspective of developers who write " +"firmware in C." msgstr "" #: src/other-resources.md 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." +"[Rust for professionals](https://overexact.com/rust-for-professionals/): " +"covers the syntax of Rust using side-by-side comparisons with other " +"languages such as C, C++, Java, JavaScript, and Python." msgstr "" #: src/other-resources.md -msgid "[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help you learn Rust." +msgid "" +"[Rust on Exercism](https://exercism.org/tracks/rust): 100+ exercises to help " +"you learn Rust." msgstr "" #: 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." +"[Ferrous Teaching Material](https://ferrous-systems.github.io/teaching-" +"material/index.html): a series of small presentations covering both basic " +"and advanced part of the Rust language. Other topics such as WebAssembly, " +"and async/await are also covered." msgstr "" #: src/other-resources.md 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." +"[Beginner's Series to Rust](https://docs.microsoft.com/en-us/shows/beginners-" +"series-to-rust/) and [Take your first steps with Rust](https://docs." +"microsoft.com/en-us/learn/paths/rust-first-steps/): two Rust guides aimed at " +"new developers. The first is a set of 35 videos and the second is a set of " +"11 modules which covers Rust syntax and basic constructs." msgstr "" #: src/other-resources.md 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." +"[Learn Rust With Entirely Too Many Linked Lists](https://rust-unofficial." +"github.io/too-many-lists/): in-depth exploration of Rust's memory management " +"rules, through implementing a few different types of list structures." msgstr "" #: src/other-resources.md -msgid "Please see the [Little Book of Rust Books](https://lborb.github.io/book/) for even more Rust books." +msgid "" +"Please see the [Little Book of Rust Books](https://lborb.github.io/book/) " +"for even more Rust books." msgstr "" #: src/credits.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." +"The material here builds on top of the many great sources of Rust " +"documentation. See the page on [other resources](other-resources.md) for a " +"full list of useful resources." msgstr "" #: src/credits.md 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." +"The material of Comprehensive Rust is licensed under the terms of the Apache " +"2.0 license, please see [`LICENSE`](https://github.com/google/comprehensive-" +"rust/blob/main/LICENSE) for details." msgstr "" #: src/credits.md @@ -17420,8 +19367,10 @@ msgstr "" #: src/credits.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." +"Some examples and exercises have been copied and adapted from [Rust by " +"Example](https://doc.rust-lang.org/rust-by-example/). Please see the " +"`third_party/rust-by-example/` directory for details, including the license " +"terms." msgstr "" #: src/credits.md @@ -17430,8 +19379,9 @@ msgstr "" #: src/credits.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." +"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 @@ -17440,6 +19390,7 @@ msgstr "" #: src/credits.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." +"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 ""