summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Silverstone <dsilvers@digital-scurf.org>2019-01-23 17:10:00 +0000
committerDaniel Silverstone <dsilvers@digital-scurf.org>2019-01-23 17:10:00 +0000
commitc6d29a2a124ea277319bc8cf82c2e14e42d70c62 (patch)
treec1045aad3fc51236b45006cc0b589ef186d6b784
parent38029764bb5ff97df1fac69026c52fef239fca90 (diff)
downloadrust-talk-c6d29a2a124ea277319bc8cf82c2e14e42d70c62.tar.bz2
Mention cargo fixHEADmaster
-rw-r--r--presentation.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/presentation.md b/presentation.md
index 5cdea83..f1881ea 100644
--- a/presentation.md
+++ b/presentation.md
@@ -1643,6 +1643,30 @@ count: false
---
+count: false
+
+## The Rust software ecosystem
+
+- `rustc` and `cargo`
+- `crates.io`
+- `clippy`
+- `rustfmt` (and `cargo fmt`)
+- `rustdoc` (and `cargo doc`)
+- ... culminating in `https://docs.rs/`
+- `#[cfg(test)]`, `#[test]`, `tests/*.rs`, and `cargo test`
+- `cargo fix`
+
+???
+
+- Rust compiler errors, warnings, lints, etc often come with recommendation on
+ on how to fix them. For example adding or removing references.
+- Where those are mechanically applicable, the information is provided to the
+ tooling, and `cargo fix` can apply these updates
+- This reduces the cognitive load of resolving warnings and lints and therefore
+ result in more consistent quality of code across crates.
+
+---
+
## Installing Rust
???