c5863f6642
* Add methods to mask and clear interrupts. * Start on GICv3 driver. * Enable and use RTC interrupt. * WFI * Add newtype for interrupt ID. * Add extension to use interrupt. * Add method to send an SGI. * Silence warnings about unused methods in provided drivers. * Implement Debug manually for IntId. It's useful to say what kind of interrupt it is. * Acknowledge and log interrupt. We should end it as well, but doing so results in a loop unless we first clear the match. * cargo fmt with imports_granularity = "module" * Use arm-gic crate rather than including driver in the example.
Comprehensive Rust 🦀
This repository has the source code for Comprehensive Rust 🦀, a four 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 Android-specific content on the last day.
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.
Building
The course is built using a few tools:
Install these tools with:
$ cargo install mdbook
$ cargo install mdbook-svgbob
$ cargo install mdbook-i18n-helpers
$ cargo install --path mdbook-exerciser
Then 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.
Contact
For questions or comments, please contact Martin Geisler or start a discussion on GitHub. We would love to hear from you.