1
0
mirror of https://github.com/google/comprehensive-rust.git synced 2024-11-24 17:06:37 +02:00
This is the Rust course used by the Android team at Google. It provides you the material to quickly teach Rust.
Go to file
2024-07-19 18:23:43 +02:00
.github Fix direction of translation diff. (#2235) 2024-07-19 15:28:34 +00:00
mdbook-course cargo: bump the patch group with 2 updates (#2229) 2024-07-15 10:32:46 +01:00
mdbook-exerciser cargo: bump the patch group with 3 updates (#2179) 2024-07-01 11:54:41 +01:00
po ar: Second patch of Arabic translation (#2231) 2024-07-19 18:23:43 +02:00
src cargo: bump the patch group with 2 updates (#2229) 2024-07-15 10:32:46 +01:00
theme Publish Ukrainian translation to language selector (#2183) 2024-07-03 14:04:54 -07:00
third_party cargo: bump the minor group with 2 updates (#1783) 2024-02-05 11:25:39 +00:00
.gitignore Add VSCode config directory to .gitignore (#2147) 2024-06-16 21:04:06 +01:00
book.toml Upgrade mdbook-pandoc and disable it except during CI workflows (#2212) 2024-07-18 13:01:25 +02:00
Cargo.lock cargo: bump the patch group with 2 updates (#2229) 2024-07-15 10:32:46 +01:00
Cargo.toml Update Concurrency course with times (#2007) 2024-04-23 13:26:41 +00:00
CONTRIBUTING.md Update Windows Gettext installation instructions (#1447) 2023-11-06 13:05:13 -08:00
dprint.json Use stable rustfmt (#2168) 2024-06-25 09:07:15 +01:00
LICENSE Rename LICENSE.txt to LICENSE (#293) 2023-01-29 14:20:55 +01:00
README.md Publish report of translation status. (#2190) 2024-07-08 10:51:14 -04:00
rustfmt.toml Format all Markdown files with dprint (#1157) 2023-12-31 00:15:07 +01:00
STYLE.md Add a dev theme to help with slide aspect ratio (#1842) 2024-03-05 10:33:42 +00:00
TRANSLATIONS.md Link to translation reports. (#2213) 2024-07-12 10:11:31 -04:00

Comprehensive Rust 🦀

Build workflow GitHub contributors GitHub stars

This repository has the source code for Comprehensive Rust 🦀, a multi-day Rust course developed by the Android team. The course covers all aspects of Rust, from basic syntax to generics and error handling. It also includes deep dives on Android, Chromium, bare-metal, and concurrency.

Read the course at https://google.github.io/comprehensive-rust/.

Course Format and Target Audience

The course is used internally at Google when teaching Rust to experienced software engineers. They typically have a background in C++ or Java.

The course is taught in a classroom setting and we hope it will be useful for others who want to teach Rust to their team. The course will be less useful for self-study since you miss out on the discussions happening in the classroom. You don't see the questions and answers and you don't see the compiler errors we trigger when going through the code samples. We hope to improve on this via speaker notes and by publishing videos.

Press

Articles and blog posts from around the web which cover Comprehensive Rust:

Building

The course is built using a few tools:

First install Rust by following the instructions on https://rustup.rs/. Then clone this repository:

git clone https://github.com/google/comprehensive-rust/
cd comprehensive-rust

Then install these tools with:

cargo install mdbook
cargo install --locked mdbook-svgbob
cargo install --locked mdbook-i18n-helpers
cargo install --locked i18n-report
cargo install --locked --path mdbook-exerciser
cargo install --locked --path mdbook-course

Run

mdbook test

to test all included Rust snippets. Run

mdbook serve

to start a web server with the course. You'll find the content on http://localhost:3000. You can use mdbook build to create a static version of the course in the book/ directory. Note that you have to separately build and zip exercises and add them to book/html. To build any of the translated versions of the course, run MDBOOK_BOOK__LANGUAGE=xx mdbook build -d book/xx where xx is the ISO 639 language code (e.g. da for the Danish translation). TRANSLATIONS.md contains further instructions.

Note

On Windows, you need to enable symlinks (git config --global core.symlinks true) and Developer Mode.

Contact

For questions or comments, please contact Martin Geisler or start a discussion on GitHub. We would love to hear from you.