remove workspace from the repository, instead generate a zipfile to upload

[rust-101.git] / workspace / src / part04.rs

diff --git a/workspace/src/part04.rs b/workspace/src/part04.rs
deleted file mode 100644 (file)
index e0d522e..0000000
--- a/workspace/src/part04.rs
+++ /dev/null
@@ -1,72 +0,0 @@
-// Rust-101, Part 04: Ownership, Borrowing, References
-// ===================================================
-
-/*
-  void foo(std::vector<int> v) {
-      int *first = &v[0];
-      v.push_back(42);
-      *first = 1337; // This is bad!
-  }
-*/
-
-// ## Ownership
-fn work_on_vector(v: Vec<i32>) { /* do something */ }
-fn ownership_demo() {
-    let v = vec![1,2,3,4];
-    work_on_vector(v);
-    /* println!("The first element is: {}", v[0]); */               /* BAD! */
-}
-
-// ## Borrowing a shared reference
-
-fn vec_min(v: &Vec<i32>) -> Option<i32> {
-    use std::cmp;
-
-    let mut min = None;
-    // This time, we explicitly request an iterator for the vector `v`. The method `iter` just borrows the vector
-    // it works on, and provides shared references to the elements.
-    for e in v.iter() {
-        // In the loop, `e` now has type `&i32`, so we have to dereference it to obtain an `i32`.
-        min = Some(match min {
-            None => *e,
-            Some(n) => cmp::min(n, *e)
-        });
-    }
-    min
-}
-
-// Now that `vec_min` does not acquire ownership of the vector anymore, we can call it multiple times on the same vector and also do things like
-fn shared_ref_demo() {
-    let v = vec![5,4,3,2,1];
-    let first = &v[0];
-    vec_min(&v);
-    vec_min(&v);
-    println!("The first element is: {}", *first);
-}
-
-// ## Unique, mutable references
-
-fn vec_inc(v: &mut Vec<i32>) {
-    for e in v.iter_mut() {
-        *e += 1;
-    }
-}
-// Here's an example of calling `vec_inc`.
-fn mutable_ref_demo() {
-    let mut v = vec![5,4,3,2,1];
-    /* let first = &v[0]; */
-    vec_inc(&mut v);
-    vec_inc(&mut v);
-    /* println!("The first element is: {}", *first); */             /* BAD! */
-}
-
-// ## Summary
-// The ownership and borrowing system of Rust enforces the following three rules:
-// 
-// * There is always exactly one owner of a piece of data
-// * If there is an active mutable reference, then nobody else can have active access to the data
-// * If there is an active shared reference, then every other active access to the data is also a shared reference
-// 
-// As it turns out, combined with the abstraction facilities of Rust, this is a very powerful mechanism
-// to tackle many problems beyond basic memory safety. You will see some examples for this soon.
-