I have been programming for some time now and have been fortunate enough to have worked on a bunch of different languages like Java, C#, Python, JavaScript (TypeScript).
\nI have been thinking of picking up a new language for sometime now and the choice came down to Go & Rust. As the title indicates, I went with Rust.
\nThis post is supposed to be just a journal of things that I might like, dislike or find interesting enough to document as I learn Rust enough to build a simple CLI app. I am following the Rust Programming Language Book and many snippets here are picked from there.
\nrust-analyzer$PATHchmod +x rust-analyzerLSP: Enable Language Server Globallyrust-analyzerRust has an expressive match syntax that can be used to compare values. A match expression is written like -
use std::cmp::Ordering;\n\nfn main(){\n let guess = 4; // some sample value, can be input\n let secret = 5; // another value to compare against.\n\n match guess.cmp(&secret) {\n Ordering::Less => println!(\"Under\"),\n Ordering::Equal => println!(\"Match!!\"),\n Ordering::Greater => println!(\"Over\")\n }\n}Each line in the match block is called an arm. In my opinion this makes the code very easy to read and understand at a glance.
Some operations, like I/O always require error handling. Rust’s Result type represents either a success (OK) or an error (Err).
The great thing here is that if a function returns a Result, then the caller must handle both success and failure cases.
Consider this code that converts a string to an int -
\nlet guess: u32 = match guess.trim().parse() {\n Ok(num) => num,\n Err(_) => {\n eprintln!(\"{} is not a legit number, try again;\", guess.trim());\n return ()\n },\n };One major difference in Rust vs the other langugages I mentioned above is that variables in Rust are immutable by default.
\nIn cases where we need to re-assign a value to a variable, we need to explicitly mark that variable as mutable by using the mut keyword.
let a = 5; //This is immutable, `a` cannot be re-assigned.\nlet mut b = 10; // `b` can be reassigned.Rust allows developers to re-declare a variable with the same name in a scope. This is called Shadowing.
\nConsider the following snippet -
\nfn main() {\n let x = 5;\n\n let x = x + 1;\n\n {\n let x = x * 2;\n println!(\"The value of x in the inner scope is: {}\", x); // This will print 12\n }\n\n println!(\"The value of x is: {}\", x); // This is still 6.\n}Honestly, the first time I saw this, I was pretty confused. Alot of other languages just refuse this kind of re-declaring of variables in scope.
\nTechnically, this variable is still immutable, i.e. this snippet would fail -
\nfn main() {\n let x = 5;\n\n x = x + 1; // will fail\n}The usecase for shadowing defined in the Rust Book is for running multiple transforms on the same variable without having to declare a bunch of variables names that we don’t care about.
\nIt will interesting to see if this causes any issues on larger Rust codebases.
\nlet x:[char, 5] = ['a','b','c','d','e']let x = [3;'a']. This creates an array like ['a','a','a']Statements do not return a value. An assignemnt is a statement. Consider the following JavaScript snippet;
\nconst a = (b = 12)\nconsole.log(a) // prints 12\nconsole.log(b) // prints 12Here the variable a gets a value 12, because b=12 returns 12. However, assignments in Rust don’t return a value.
Expressions return a value, Rust is an Expression oriented language.
\nThe block {} created for new scopes is an expression and thus can be assigned to variable like -
let y = {\n let x = 3;\n x + 1\n };Here the last line in the block does not end with a semi-colon (;), thats because expressions do not include ending semicolons, if we add a semicolon, then it becomes a statement and hence it does not return a value.
\nIn Rust, the by default, the return value of the function is the value returned by the last expression in the function. Using return can be used to exit early, but otherwise its optional.
Since if is an expression, conditional assignemnts don’t require additional syntax.
let condition = true;\nlet number = if condition { 5 } else { 6 };Rust has built-in support for infinite loops using the loop keyword. This is the first language where I am seeing this.
Another first for me, was the ability to return values with the break keyword.
let mut counter = 0;\n\n let result = loop {\n counter += 1;\n\n if counter == 10 {\n break counter * 2;\n }\n };\n\n println!(\"The result is {}\", result);loop is treated as an expression that yields a value, we can put it on the right side of assignment.break counter * 2 statement not only stops the loop, but assigns the value to the variable resultSource https://doc.rust-lang.org/book/ch03-05-control-flow.html#returning-values-from-loops
\nJust refer - https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html
\nConsider the following JS Code:
\nconst x = { foo: 1 }\nconst y = x\ny.foo = 2 // this works and sets x.foo = 2Here JavaScript assigns the reference to the variable x to y. So when some code alters y.foo, it’s actually changing x.foo.
Consider the following rust snippet
\n let s1 = String::from(\"hello\");\n let s2 = s1;\n println!(s1); // this errors.In this case, Rust too copies the pointer to where “Hello” is stored, but does not copy the data itself. However, due to how ownership works, and to keep things simple, let s2=s1 actually invalidates s1 and transfers the ownership of Hello to s2. After the re-assignment s1 can no longer be used. This is called move.
As explained here, this is done so that hello only has one owner (s2) and when s2 goes out of scope, Rust can easily free up the memory.
Note: Fixed length data like integers and floats, that is stored on the stack can be re-assiged without invalidating the old variable. Read More Here
\nPassing data to functions as arguments also transfers the ownership of that data. Assume a regular say_hello function like -
fn say_hello(name: String)->String {\n String::from(\"Hello!, \") + &name\n}\n\nfn main() {\n let s1 = String::from(\"foo\");\n println!(\"{}\", say_hello(s1));\n println!(\"{}\". s1); // This would complain about `s1` having moved\n}Passing variables to a function and then storing its return value back in a different variable will obviously be tedios and not always desirable. To get around this Rust has the concept of References
\nfn say_hello(name: &String)->String {\n String::from(\"Hello!, \") + &name\n}\n\nfn main() {\n let s1 = String::from(\"foo\");\n println!(\"{}\", say_hello(&s1));\n println!(\"{}\". s1);\n}The & syntax creates a reference to the value of s1, but it does not own it. Creating references is called borrowing.
Notes
\n&mut.Refer: https://doc.rust-lang.org/book/ch04-03-slices.html
\nLast Updated: 15 December 2021.
","frontmatter":{"title":"Learning Rust - The Interesting Parts","date":"December 10, 2021","ogimage":null}}},"pageContext":{"slug":"/learning-rust/","previous":{"fields":{"slug":"/gitlab-todos-hammerspoon/"},"frontmatter":{"title":"Tracking GitLab Todos with Hammerspoon"}},"next":{"fields":{"slug":"/book-notes-psychology-of-money/"},"frontmatter":{"title":"Book Notes: Psychology of Money"}}}},"staticQueryHashes":["426816048","983108779"]}