nikomatsakis / rust-tutorials-keynote Goto Github PK

Thanks for doing this.

It would be awesome to be able to get the decks in PDF though.

Regards,

No typos during my review, but here are some notes I gathered while reviewing them:

• Slide 14: for the "No need for runtime", "Memory safety", you and I noted in the past that there wasn't a clear contender for a language (or language feature) to put below "Data-race freedom." During my most recent presentation, someone in the audience suggested putting "Erlang" below this; I replied "well Erlang's approach isn't like Rust's", but then I immediately noted "then again, a GC approach isn't like Rust's either." So just a thought, if you want to make the arrows all have analogues.

• Slide 26: I've often wondered what to say during this picture. I happened to just notice that the tether in the hand of one of the children could well be considered a refererence! :)

• Slide 33: the fact that the arrow starts from the & in &name is super important. (I have sometimes made the mistake of talking about the lifetime as being something that comes from, or is at least "associated with" r, but that viewpoint is misleading.) You might consider putting & in parentheses after the word "reference" in this slide, to further stress that.

• Slide 34: you might consider comparing the provided non-compiling code with something like:

  fn helper(name: &String) {
      let name_val = name.clone();
      thread::spawn(move || {
          use(name_val);
      });
  }

  (just to make it clear that it is the reference that is not transferable, versus an owned instance of String itself...)