37 Replies to “The Rust Programming Language

  1. Thanks very much for the great and neat presentation followed Alex Crichton.Your presentation is much appreciated.

  2. Rust is a very, very promising language, and, after some reading, it seems to me that it lacks any glaring deficiencies – unlike let's say Golang (with its horrible type system and non-extensible nature).

    There's certainly space for sane C++ replacements.

    Great presentation of Rust's distinguishing characteristic (ownership/borrowing), although I'd also love an overview of the object system and the very interesting functional features of the language.

  3. I will give it a try in a new project. I will rewrite Lucene (the java, then c++ full text search engine) and add it to a special database for a new AI enabled webscrapper. I think this is a good project that can need lots of multithreading help and thats where i expect the most help from the code. Most important is that i can integrate it with C easily.

  4. I have had an interest in programming for a while and I really like what I'm seeing here in terms of control and structure. My question is if RUST is a good first programing language for a beginner like myself to learn.

  5. Rust is load of crap. It doesn't solve anything. We will still be writing everything in C 50 years from now.

  6. Thank you for the video, which I probably watched in 4 minutes by pressing the right key every second. That's about the time I have.

  7. I have never listened to a great tutorial, precise, simple, articulate, summarized and fully descriptive as well as comprehensively detailed like this one. I have loved the programming language since then. Thanks for the awesome video.

  8. Summing up this lesson:

    The problem in memory management is
    aliasing (2 references to the same variable), and
    mutation
    …happening at the same time.

    To solve that, in Rust a variable can be passed in 3 ways:

    1. "var": *Ownership*. Ownership of var is immediately passed to the called function, and the caller cannot use var anymore, it is completely forgotten. Trying to use var in the caller results in "var has been moved" compiler error.
    2. "&var": *Shared borrow*. The caller can send the variable to multiple consumers, but mutation is forbidden, the callee can only read var but not mutate it. (But mutation is allowed in certain controlled circumstances.)
    3. "&mut var": *Mutable borrow*. The callee, alone, can mutate the variable. The variable is returned through the stack and the caller gets control over the variable again.

Leave a Reply

Your email address will not be published. Required fields are marked *