1b3984df20
After #1528 and #1532, we now have actual slides which showcase the crates in action. So we can reclaim a few minutes by removing the slide which mentions Mockall and GoogleTest slide. The slide mentioned [proptest](https://docs.rs/proptest) and [rstest](https://docs.rs/rstest) as well. While I'm sure the libraries are useful, we don't have them imported into AOSP and I've never personally used them. We should therefore not advertise them yet at this point since they won't be useful to Android engineers. Of course we can mention things that are not in AOSP (or in Chromium), but I think we should do it in the speaker notes at most. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
mdbook-course
This is an mdBook preprocessor to handle some specific details of Comprehensive Rust.
It provides three binaries:
mdbook-course-- the actual preprocessorcourse-schedule-- prints the course schedule with timingscourse-content-- dumps all course content to stdout, in order
Frontmatter
The preprocessor parses "frontmatter" -- YAML between --- at the beginning of
a Markdown file -- and removes it from the rendered result.
Frontmatter is optional, and can contain any of the following fields, defined below:
minutes: NNN
target_minutes: NNN
course: COURSE NAME
session: SESSION NAME
Course Structure
A book can contain multiple courses. Each course is made up of sessions, which are blocks of instructional time (and include breaks). Typically two sessions are taught per day, morning and afternoon.
Each session is comprised of segments, which are slides on a related theme. Breaks are scheduled between segments.
Each segment is comprised of slides. A slide can be made up of one or more mdBook chapters.
The course structure is derived from the mdBook structure. Each top-level mdBook "section" is treated as a segment, and may optionally begin a new session or course. Within each section, the first chapter and subsequent second-level chapters are each treated as a slide. Any further-nested chapters are treated as parts of the parent slide. For example:
- [Frobnication](frobnication.md)
- [Integer Frobnication](frobnication/integers.md)
- [Frob Expansion](frobnication/expansion.md)
- [Structs](frobnication/expansion-structs.md)
- [Enums](frobnication/expansion-structs.md)
- [Exercise](frobnication/exercise.md)
- [Solution](frobnication/Solution.md)
In this segment, there are four slides: "Frobnication", "Integer Frobnication", "Frob Expansion", and "Exercise". The last two slides are made up of multiple chapters.
The first chapter of a segment can use the course and session fields in its
frontmatter to indicate that it is the first segment in a session or course.
Timing
Each chapter should specify an estimate of the instructional time it will
require in the minutes field. This information is summed, with breaks
automatically added between segments, to give time estimates for segments,
sessions, and courses.
Each session should list a target_minutes that is the target duration of the
session.
Directives
Within the course material, the following directives can be used:
{{%segment outline}}
{{%session outline}}
{{%course outline}}
{{%course outline COURSENAME}}
These will be replaced with a markdown outline of the current segment, session, or course. The last directive can refer to another course by name and is used in the "Running the Course" section.
Course-Schedule Comments
The course-schedule binary generates Markdown output that is included in a
GitHub pull request comment, based on the information provided in the above
format.