Rust - Lightning Talk

Rust, and why it does what it does

Transcript

1. Rust Lito Nicolai
2. Why is it called Rust?
3. Why is it called Rust? It is named after a family of fungus
4. Why is it called Rust? They are NEAT
5. Why is it called Rust? They have *five* stages of life (humans only have two) that they can move back and forth between
6. Why is it called Rust? Concurrent, distributed organism
7. Why is it called Rust? Nearly unkillable (just ask my favorite camellia trees)
8. Goals of Rust: • Concurrent • Unkillable
9. Goals of Rust: Can we do that while managing the computer’s memory directly?
10. Goals of Rust: Can we do that while managing the computer’s memory directly?
 
 YES!
11. Goals of Rust: Can we do that while managing the computer’s memory directly?
 
 YES! (yay language research!)
12. Ideology How does Rust think people should program?
13. Ideology Pay the frustration costs up front!
14. Frustration Very strict compiler errors – even confusing ones – are betting than debugging
15. Frustration (I like that this mirrors the philosophy of TDD)
16. Frustration Rejecting possibly correct code is better than allowing incorrect code
17. Safety vs Inconvenience A spectrum! (extra programmer time, learning) Proven correct before run Only runtime errors (all errors are logic errors)
18. Ok, it’s not that simple at all. Shhhhhh There are many kinds of correctness, and many different costs of correctness. but stick with me
19. Safety vs Inconvenience Where does Rust live? (extra programmer time, learning)
20. Safety vs Inconvenience (extra programmer time, learning) Machine code
21. Safety vs Inconvenience (extra programmer time, learning) Machine code LISP (1958 version)
22. Safety vs Inconvenience (extra programmer time, learning) Machine code C LISP
23. Safety vs Inconvenience (extra programmer time, learning) Machine code C LISP Ruby
24. Safety vs Inconvenience (extra programmer time, learning) Machine code C Rust LISP Ruby
25. Safety vs Inconvenience • More annoying than Ruby (extra programmer time, learning) Machine code C Rust LISP Ruby
26. Safety vs Inconvenience • More annoying than Ruby • Fewer errors allowed (extra programmer time, learning) Machine code C Rust LISP Ruby
27. Safety vs Inconvenience Rust has a range of correctness! (extra programmer time, learning)
28. Rust and Correctness Address Machine Word Byte
29. Rust and Correctness None of these are checked!
30. Rust and Correctness “Urgh”, I thought
31. Rust and Correctness On the other hand, that’s how you crash your Mars Climate Orbiter.
32. Degrees of Correctness • Immutable reference to immutable data Default: Compiler-enforced!
33. • Immutable reference to immutable data • Immutable ref. to mutable data Degrees of Correctness
34. • Immutable reference to immutable data • Immutable ref. to mutable data • Mutable references to… Degrees of Correctness
35. • Immutable reference to immutable data • Immutable ref. to mutable data • Mutable references to… • Raw pointers to… Degrees of Correctness
36. • Immutable reference to immutable data • Immutable ref. to mutable data • Mutable references to… • Raw pointers to… • Reference-counted pointers to… Degrees of Correctness
37. • Immutable reference to immutable data • Immutable ref. to mutable data • Mutable references to… • Raw pointers to… • Reference-counted pointers to… Degrees of Correctness
38. • Compiler-enforced immutability Kinds of Correctness
39. • Compiler-enforced immutability • Compiler-enforced memory management Kinds of Correctness
40. • Compiler-enforced immutability • Compiler-enforced memory management • Compiler-enforced thread safety Kinds of Correctness
41. • Compiler-enforced immutability • Compiler-enforced memory management • Compiler-enforced thread safety • unsafe, aka “I just want to write C and Assembly” Kinds of Correctness
42. Memory safety!
43. AMAZING error messages How… did you know?
44. Helpful Community • There is NO “You should know this” or “RTFM” • Everyone understands that learning Rust can be tough • Formal structures in place (CoC, etc)
45. Disadvantages That all sounds pretty great. What are the trade-offs?
46. Disadvantages • It is frustrating!! When the compiler rejects code, it’s not always obvious why there’s a problem.
47. Disadvantages • Choose between ALL of the metaprogramming (write your own AST), or only a tiny bit (restricted macros)
48. Disadvantages
49. Disadvantages • Emphasis on compile-time correctness – test support is pretty minimal
50. Why do I think you should use Rust? • Learning about how computers work underneath
51. Why do I think you should use Rust? • Learning about how computers work underneath • Want to write fast code – approaching hardware limits – and don’t want to write C
52. Why do I think you should use Rust? • Learning about how computers work underneath • Want to write fast code – approaching hardware limits – and don’t want to write C • Hate pthreads
53. Why do I think you should use Rust? • Learning about how computers work underneath • Want to write fast code – approaching hardware limits – and don’t want to write C • Hate pthreads • Don’t like race conditions in your concurrent code
54. Why do I think you should use Rust? • Learning about how computers work underneath • Want to write fast code – approaching hardware limits – and don’t want to write C • Hate pthreads • Don’t like race conditions in your concurrent code • Don’t want segfaults and buffer overflows
55. Why do I think you should use Rust? “A language that doesn’t affect the way you think about programming is not worth knowing” I think Rust will change how you think about correctness.
56. Thanks~ @lito_nico
57. Stages of Life • Pycniospores - Haploid (half-chromosome) gametes • Aeciospores - non-repeating (can’t force a host to reinfect itself) dikaryotic (two different nuclei in a cell) vegetative spores • Urediniospores - repeating dikaryotic vegetative spores. • Teliospores - Diploid spores that produce basidia (fruiting bodies) • Basidiospores - Haploid spores which infect an alternate host.