Updates

Author: Brian Obot

14e_use_library

@@ -44,8 +44,10 @@ fn main() {
     println!("Person last name: {}", person.last_name);
 
     // self can be used to refer to the current module
-    // super can be used to refer to the parent module
+    // super can be used to refer to the parent scope
     let greeting  = person.greet();
     println!("Greeting: {}", greeting);
 
+    println!("Current Module: {:?}", module_path!());
+
 }

lib14b_modules_extended.rlib

@@ -0,0 +1,19 @@
+// crate is a compilation unit in Rust Programming Language
+// modules do not get compiled individually, only crates do
+
+// a crate can be compiled into a binary or a library
+// by default crate are compiled into binary 
+
+// a crate can be compiled as library with
+// rustc --crate-type=lib <file_name>.rs
+
+// the name of the compiled library is derived from adding lib infront of the filename
+// but this can customized with the --crate-name flag
+
+pub fn public_function() -> u8 {
+    12
+}
+
+fn _private_function() -> u8 {
+    13
+}

lib14d_crate_in_rust.rlib

@@ -0,0 +1,4 @@
+fn main() {
+    let result: u8 = rary::public_function();
+    println!("Result = {}", result);
+}

lib14e_use_library.rlib

@@ -0,0 +1,14 @@
+// this is rust official package management tool
+// it can integrate with crate.io (official rust registry for public crates)
+// awareness of unittests
+// awareness of benchmarks
+
+// when using Cargo, cargo build can be used from any part of the project, including subdirectories
+
+// NOTE: when using cargo to run test, it may run some test concurrently, so ensure the test do not race
+// in cases where a simple compilation bu cargo is not enough to build a project,
+// the steps needed to build the projec can be specified in a build attribute of the package section
+// of the cargo.Toml file, or it can be specified in a file called build.rs.
+
+// the build script is a rust file that would be compiled invoked prior to the compilation of anything else in the package
+