Differences in Storing Data: Rust vs JavaScript

11min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The chapter explores the disparities between Rust and JavaScript when it comes to storing data. It discusses the need for additional tables and relationships in Rust to store arrays of strings, while JavaScript allows direct storage. The importance of specifying data types in Rust for performance benefits is also highlighted, along with an introduction to various data types like U8, floating point numbers, and dynamically sized strings.

In this episode of Syntax, Wes and Scott jump into part 2 of their look at Rust for JavaScript developers, including variables in Rust, type systems in Rust, signed and unsigned integers, and more.

Show Notes

00:10 Welcome
00:43 Audio issue bugs
03:17 Building decks
06:06 Variables in Rust
Syntax 647: Rust for JavaScript Developers - Node vs Rust Concepts

let x = 5; // x is immutable let mut x = 5; // x is mutable const MAX_POINTS: u32 = 100_000; // must be defined at compile time

10:42 Type System in Rust
15:52 Types in Rust
19:06 Why does Rust have signed and unsigned integers?
23:35 Slicing strings with &str
27:35 enum
27:55 struct
28:19 Vec
29:33 HashMap and HashSet
33:00 Converting Signed to Unsigned Numbers

let unsigned_value: u8 = 200; let signed_value: i8 = unsigned_value as i8;

36:12 What’s up with &str?
43:31 Rust error messages
45:28 What is a Struct?

struct User { username: String, email: String, sign_in_count: u64, active: bool, } // You can create an instance of a struct like this: let user1 = User { email: String::from("someone@example.com"), username: String::from("someusername123"), active: true, sign_in_count: 1, }; impl User { fn login(&mut self) { self.login_count += 1; } }