Going from TypeScript to Rust can be very difficult. I sure hope you appreciate this video! I was thinking about making more Rust vs Typescript videos. What do you all think? This one is very educational, but i was also going to just do more comparison (not perf wise, but blazingly ergonomic wise). thoughts? Also, if you like this, SEND THE ALGORITHMIC SIGNALS
Honestly, I was expecting for potential solutions for the second example. I know there are multiple ways to achieve it, but even after months of trying to learn rust, even these simple interactions can become confusing really fast.
Love the Rust vs Typescript video ideas. It makes Rust easier to understand when you compare it with Typescript and how things are working behind the curtain, your explanation is top notch, keep being great Prime Nice AD too
I would LOVE more “Rust for Typescript developers” styled videos. I just started learning Rust with advent of code as well, and have found a lot of things in Rust to be less scary because I know Typescript, while also finding plenty of things that *are* confusing 😂. This video was SERIOUSLY helpful, you have a fantastic ability to teach concepts like these. Thank you prime and happy holidays!
As many before has said, this comparison format (DX I guess) is super nice! For me, someone who hasn't had time to dive in yet but is wondering how the water feels it really hit a spot. More of this stuff please!
I've been struggling in Advent of Code in Rust and the bit at 06:04 sums up perfectly why - Not knowing if a std function, usually an iterator method, mutates in-place or returns a copy. It leads you to a thorn bush of compiler errors. I guess this is just something you learn over time doing Rust? New merch idea - make a cheatsheet for this, and print it upside down on a T-shirt!
so for the most part its pretty simple to know about iterators. &object_that_can_iterate = .iter() = immutable references to items within object_that_can_iterate = .into_iter() = converts object into an iterator (consumes) .iter_mut() = mutable references
I learnt rust during first lockdown for around a month, and almost never touched after that. It was sort of like revision. You did fantastic job explaining important yet confusing concept in simplest way possible.
These three types of values in rust (owned, reference, mutable reference) reoccur everywhere in the language. For iterators, we have .into_iter(), .iter() and iter_mut() for the same three types. For functions we have FnOnce (consumes the value, can therefore only be called once), Fn (takes a reference: can therefore be called multiple times), FnMut (takes mutable reference). It's a very nice language design.
I recently came across a blog suggesting to always make your arrays read-only in typescript. This has really helped med to avoid all the inplace array functions screwing up my data when it's not intentional. It also behaves more like rust immutable arrays. Great video. Keep it up 🤙
Thank you @ThePrimeagen, a year after you made the video. I've been going through Advent of Code 2023 (I know, I'm slow) to try to learn Rust and foolishly only did a couple chapters of The Rust Book before switching just to solving problems. Especially with Copilot's assistance, I've been able to work out how to add `&` and `mut` to make my code compile, but I didn't understand _why_ until this video. I had to rewatch every lesson of this video 2-3 times, but now I feel I finally understand this concept that was repeatedly tripping me up.
I cannot understand why people say that the borrow checker is complex, it does what a C/C++ programmer should be doing when using pointers. Rust people found a brilliant way to automate that reasoning inside tools.
Wow, the borrow checker blew my mind time after time after time. I felt like I was really stuck in a rut and unable to move forward. That is, until I clicked the subscribe button. Suddenly, everything just clicked. Really revolutionary
So effectively Rust moves ownership of a value by default (likely to optimize end-recursive functions in a similar way as Haskell) and it makes all variables immutable by default. In comparison C/C++ copies a value by default and makes all variables mutable by default. So that explains why going from it to Rust creates such a headache until you get through this. Anyway good video to understand the concept.
First explanation of the borrow checker that actually makes sense, tried a couple of days ago asking chatGPT to rephrase it multiple times with no success, probably not enough blazing speed and momentum
Just came here to say, I got inspired to learn rust because of you and NoBoilerPlate; I invested a month in reading the book and now I am learning actix and building a production ready backend in rust. I came so far from javscript to rust because of you, I appreciate you!
Prime has covered it quite well, a few days ago I was thinking I should try rust and I did and I love it. I am following their docs religiously, those who haven't checked out their official docs, these topics are covered there in detail as well. But always thankful to Prime to share this with everyone.
Having written quite a bit of C++ code, it is extremely freeing to have the compiler check things like ownership. Not only does it make code the more safe, it also becomes more difficult to make dumb architecture decisions.
started learning rust due to some thick js fatigue and have to say when I code in rust I finally feel like I can write code with at least some certainty that it'll do what I want it to do
I started the first few advent of code problems using typescript, I was just starting to try out using rust for the rest of the advent, so this video came just in time. Thank you!
The easiest way to beat the borrow checker is to write immutible code and pass by reference. Your debugging team (typically consisting completely of future you) will thank you.
I did some leetcode today and was doing some Rust and C, and I thought about why I like to use rust, C often goes faster to get something to work. And it's because when you write rust code, it takes a while to compile and work, but that's because the compiler more or less forces you to understand what is going on behind the scenes, Like in your last example with the reverse and map. To implement that type of logic, you pretty much NEED to understand what to code does to get it working. Whiles in many other languages you can often get away with code that's: " I don't really know how it works, but it works so I'm happy".
This is amazing and succinct. I literally gave a presentation on this to my company last week (we're primarily Java/JavaScript developers) and it was pretty much beat for beat. Granted I took 30mins instead of 8, but there were a lot of questions 😁
1:55 - it just clicked in my mind (after 2 years of casually coding in rust): the "use of moved value" can roughly translate to "use after free" error in c / c++, because you're passing ownership of `item` to `print_out_item`, as that function consumes it and rust frees the memory for `item`; therefore, you're trying to use a variable after it's freed from memory. and that's a safety rule that rust enforces you to take into account. and that's why i mostly pass variables by reference and prefer to use `.clone()` as a last resort.
I can confirm that the borrow checker was a mystery to me until I subscribed. Once I did, it was as if the crab god directly uploaded the knowledge to my brain. 10/10 would do again.
Yep, this is indeed amazing. I am a developer in multiple languages, with a main focus on C-family languages (especially C#, but also C/C++, JavaScript and Java). So I have seen a lot of things, but what Rust does is certainly special. Everything Immutable by default in combination with memory ownership by default. While still doing many things by-reference a lot like what people do in C++. Such that performance is maintained. Amazing. I have very recently started to experiment with Rust and I am planning to do a lot more with it. Also taking into account some other thoughs and considerations. This language has absolute potential, even though it's also still missing some features, like varargs.
This is the first ThePrimeagen video UA-cam has ever recommended me. I have been binging ThePrimeTime videos for MONTHS and THIS is the FIRST video UA-cam shows me of ThePrimeagen!? But in all seriousness, I guess I need to just learn rust now.
Always a good day when I find a new UA-cam channel this great. I'm usually a documentation > video tutorials kind of guy, but it's hard to beat content this good.
I litterally asked GPT-Chat, like 14 hours ago, to show me, a TypeScript dev, a program in both Rust and TypeScript to help me understand this. And this comes out, Thank you!
This is a great talk. I made a small similar post about this for my company, about how Rust checks these things and how coding like this helps us think about how to program better in other languages. Incoming thought dump: We've been having issues in Grails with an exception called Stale Object. Essentially a reference to a database Domain is getting passed to a service function, mutated with a save(), then outside and after the function that same object is getting mutated with a save(). Groovy lets us compile this code and normally this actually works most of the time. This is a data race. Because it's working with the Database this is an asynchronous process that gets obfuscated and we dont see it. We get this error when things don't catch up in time and the outside object gets updated first followed by the inner reference being updated. Incomes Rust, if you tried to write the code the same way you'd get borrow checker issues because we tried to hold onto two mutable references at the same time. Showed this to my coworkers and they were kinda blown away that a language and compiler can tell when a data race happens. Imagine, no more data races. No more unknown BS in your code base. Rust is hard, but most of the time it is correct! And I can use libraries written by Rust authors knowing it is going to work and not worry about some weird bullshit breaking prod code. Long live crab
Understanding Borrow Checker with Primeagen is so easy I now borrow without checking. Or something. Learning Rust when you are a Prime subscriber gets so trivial that the only thing that is Rusty nowadays is my JavaScript, which is what the language is by default, rusty. You get the point, just subscribe to the guy. We need to subscribe until we find out why Maria did what she did. PorqUÊ.
God yes, the number of times in languages where I'm like, "hang on, am I passing a reference or the value here? Welp, just gotta find out!" is silly. I love that rust not only makes it clear, it gives you the choice!
Very good video, I never quite understood what the borrow checker was doing until now. The one thing that confuses me, however, as predominant C++ user, is that I am used to "pass by value" meaning that you pass the value into a function and any changes made in the function won't be applied to the overarching object/variable, and pass by reference allows you to directly access the object and change it. Interesting!
This is the first time I actually understood what is the Rust borrow checker. My intuition is that its a mechanism that forces you to write safe code but at a much lower level. Kind of similar to how TypeScript forces you to write type safe code. Now I just need an excuse to learn it further. But being in web land I doubt I'll have it soon.
6:32 I Extremely agree!! Oh, heavens!. When I was first starting to learna language (scripting language) of AHK, I was traumatized by the odd behaviours I had to find through trial and error while working with objects like arrays. The second language I had turned into learning better than just basics was actually rust, and even though it was an about 3-4 months struggles (about 1-4 hours daily on average), It was really pleasant to learn because It was clearer to know what I actually was doing. Now my next pain I'm feeling in rust are web servers (Still reading chap 20), Macros and Iterators
idk why i'm watching this video. I've been coding in rust for 3 years and know all this stuff. i guess ThePrimeagen is just too good of a teacher I want to re-learn what i already know
Basically variables passed to functions are c++ const by default and can be passed to a function only once unless passed using a reference, else the variable is owned by the function once it's passed. And to pass a variable several times to different functions and modify it (which is not functional programming but can be useful to avoid copies when needed) the variable needs to be passed as &mut.
the problem about c++ is pass by value this catches many people off guard. even worse is this auto a = std::vector() auto b = a; BOOM copy. WHA???? c++ always has the worst defaults. Rust solves this very well.
can confirm, I only fully understood borrow checking after subscribing, it was like a door was unlocked and I walked through into a beautiful landscape of full understanding
Smashed that subscribe button and suddenly I'm seeing in 4K, understanding quantum physics, and speaking fluent Mandarin... I guess this is how Bradley Cooper felt in Limitless!
Clear like water, awesome Prime!!!!! I think a good topic is async in Rust vs Typescript, without TOKIIIOOOOOOOOOOOOOOOOO of course and the more simple way!!!! Thank UUUUU
Ironically, working through "the rust book" and interacting with the borrow checker helped me understand how to use TypeScript as opposed to the other way around.
As someone who writes code in TS for a living and is now trying to dabble with Rust, this couldn't have come at a better time. I'm trying to write all of this year's advent of codes in Rust and yeah, the beggining may have been a little rusty (sry) but I feel like I'm getting the hang of it.
I have never written a line of rust, barely touched typescript. However, this makes a ridiculous amount of sense if you've completed all the side quests using pointers in C. Maybe I'll actually write some rust code one day. If I do it will be because of stuff like this. Very cool.
I liked the video but I noticed that the main concepts demonstrated here are already very well explained in Chapter 4 of the Rust book. Not only do you get an explanation of the borrow checker's rules e.g. immutable and mutable reference can't co-exist in the same scope. But you also get an explanation of why it is the way it is intuitively i.e. a user of an immutable reference is still reading from that value, so we don't want it be snatched from under their feet by allowing someone else to write (race condition case). They also mention that the overarching reason the BC is the way it is to manage heap data.
That was amazing. At the end, this borrow checker thing is not that hard to grasp at all (once you have some experience with programming in other languages, of course). I also like the idea of explicitly say in the code what is mutable and what is not. That is a plus for Rust indeed. That makes code much clearer and predictable, I believe. Good job, Prime!
Loving the content, but how are you getting the inlay information from compiler diagnostics in rust? I can't get it working in Nvim and I'm sure it's something simple and stupid I'm missing. I have the syntax stuff from lsp, but not the warnings about borrow order.
@@double0028 I did, mostly. It has to do with diagnostic and virtual text, but rust_tools also wants those virtual_text lines. So you need to make s decision on what to use.
Cool think about knowing C++ is that any questions any new languages are answering - it was asked by C++ (most of them) so C++ developers almost always know why any language feature was introduced (Java, Rust, C#)
Rust also does not need a garbage collector -- precisely because of the borrow checker. Which is also only compile time, so no runtime overhead because of GC or borrow checking. Thus the reason it is fast. I learned that a few days ago only. Though I prefer nim or go instead, but I admit rust is cool and helps preventing a f.ton of coding errors.
Your point that you stated that there is good to know if your passed parameter is going to be mutated or not, is valid, however in your comparison where you use typescript (and not pure javascript) you should mention, that in typescript types system you can also specify that idea of mutability.
I like that, it seems like a compiler-level CommandQuerySeparation pattern. I force that pattern in our team's coding guidelines as - like you say - it's pretty terrible when you don't know whether a function will mutate the args or not Ta
Going from TypeScript to Rust can be very difficult. I sure hope you appreciate this video! I was thinking about making more Rust vs Typescript videos. What do you all think? This one is very educational, but i was also going to just do more comparison (not perf wise, but blazingly ergonomic wise).
thoughts? Also, if you like this, SEND THE ALGORITHMIC SIGNALS
please do.
+1 :) great video!
LOVE IT
Honestly, I was expecting for potential solutions for the second example.
I know there are multiple ways to achieve it, but even after months of trying to learn rust, even these simple interactions can become confusing really fast.
TS to RS playlist would be awesome!
Love the Rust vs Typescript video ideas. It makes Rust easier to understand when you compare it with Typescript and how things are working behind the curtain, your explanation is top notch, keep being great Prime
Nice AD too
ty ty ty :)
@@ThePrimeagen yes, pls, more of this.
@@ThePrimeagen would love to see more comparisons videos
you've made a difficult subject simple. Well done.
ty ty :)
I would LOVE more “Rust for Typescript developers” styled videos. I just started learning Rust with advent of code as well, and have found a lot of things in Rust to be less scary because I know Typescript, while also finding plenty of things that *are* confusing 😂. This video was SERIOUSLY helpful, you have a fantastic ability to teach concepts like these. Thank you prime and happy holidays!
As many before has said, this comparison format (DX I guess) is super nice!
For me, someone who hasn't had time to dive in yet but is wondering how the water feels it really hit a spot. More of this stuff please!
yayaya
Doing AoC with Rust really has been the best way to practically learn these things. Loving learning this awesome language!
agreed
I've been struggling in Advent of Code in Rust and the bit at 06:04 sums up perfectly why - Not knowing if a std function, usually an iterator method, mutates in-place or returns a copy. It leads you to a thorn bush of compiler errors. I guess this is just something you learn over time doing Rust?
New merch idea - make a cheatsheet for this, and print it upside down on a T-shirt!
so for the most part its pretty simple to know about iterators.
&object_that_can_iterate = .iter() = immutable references to items within
object_that_can_iterate = .into_iter() = converts object into an iterator (consumes)
.iter_mut() = mutable references
@@ThePrimeagen Oh lord I've just been using the first one, this makes all the difference! Thank you Mr Prime.
I learnt rust during first lockdown for around a month, and almost never touched after that. It was sort of like revision. You did fantastic job explaining important yet confusing concept in simplest way possible.
Me (JS/TS dev): start learning Rust.
Primeagen: makes video "Rust for JS devs".
Love it :)
you are welcome
I subscribed, and it's so much easier to understand the borrow checker!
of course
These three types of values in rust (owned, reference, mutable reference) reoccur everywhere in the language. For iterators, we have .into_iter(), .iter() and iter_mut() for the same three types. For functions we have FnOnce (consumes the value, can therefore only be called once), Fn (takes a reference: can therefore be called multiple times), FnMut (takes mutable reference). It's a very nice language design.
I recently came across a blog suggesting to always make your arrays read-only in typescript. This has really helped med to avoid all the inplace array functions screwing up my data when it's not intentional. It also behaves more like rust immutable arrays. Great video. Keep it up 🤙
Thank you @ThePrimeagen, a year after you made the video. I've been going through Advent of Code 2023 (I know, I'm slow) to try to learn Rust and foolishly only did a couple chapters of The Rust Book before switching just to solving problems. Especially with Copilot's assistance, I've been able to work out how to add `&` and `mut` to make my code compile, but I didn't understand _why_ until this video. I had to rewatch every lesson of this video 2-3 times, but now I feel I finally understand this concept that was repeatedly tripping me up.
Wow that last example was perfect. Thanks for doing this prime! It makes it so much clearer!
yayayayaya!
@@ThePrimeagen yayayayaya
@@ThePrimeagen yayayayaya
I cannot understand why people say that the borrow checker is complex, it does what a C/C++ programmer should be doing when using pointers. Rust people found a brilliant way to automate that reasoning inside tools.
correct
@@ThePrimeagen 0:49 it all makes sense! I could understand the borrow checker because I am subscribed!
Wow, the borrow checker blew my mind time after time after time. I felt like I was really stuck in a rut and unable to move forward. That is, until I clicked the subscribe button. Suddenly, everything just clicked. Really revolutionary
So effectively Rust moves ownership of a value by default (likely to optimize end-recursive functions in a similar way as Haskell) and it makes all variables immutable by default. In comparison C/C++ copies a value by default and makes all variables mutable by default. So that explains why going from it to Rust creates such a headache until you get through this. Anyway good video to understand the concept.
First explanation of the borrow checker that actually makes sense, tried a couple of days ago asking chatGPT to rephrase it multiple times with no success, probably not enough blazing speed and momentum
Just came here to say, I got inspired to learn rust because of you and NoBoilerPlate; I invested a month in reading the book and now I am learning actix and building a production ready backend in rust. I came so far from javscript to rust because of you, I appreciate you!
Languages like javascript, where everything could happen and you need to know it, give me anxiety.
Prime has covered it quite well, a few days ago I was thinking I should try rust and I did and I love it. I am following their docs religiously, those who haven't checked out their official docs, these topics are covered there in detail as well. But always thankful to Prime to share this with everyone.
You made me start to learn Rust and I'm loving it. Currently finishing chapter 10 of the book woohoo
nice
Hi, could you give me the name of book you're reading?
@@boyonline1994 the rust programming language
@@boyonline1994 it's a website
Finished the book yesterday, it is really good! Now, let's go to The Cargo Book :D
Having written quite a bit of C++ code, it is extremely freeing to have the compiler check things like ownership. Not only does it make code the more safe, it also becomes more difficult to make dumb architecture decisions.
The Rust Book actually explains this pretty well when I read it.
started learning rust due to some thick js fatigue and have to say when I code in rust I finally feel like I can write code with at least some certainty that it'll do what I want it to do
Yes. The same when I switched to Go. I stoped playing the game “so what shit will break today?”
Started learning rust and this is one of those things that were somewhat hard to understand having a background mostly with Go. Loved the video
yayaya
@@ThePrimeagen yayayayaya
I started the first few advent of code problems using typescript, I was just starting to try out using rust for the rest of the advent, so this video came just in time. Thank you!
Just wrote my first Rust thing and it is a native app using Tauri and Yew. This video and many more you have about Rust helped me a lot. Thanks men
ThePrimeagen is the best teacher .. i swear to god!.
ty ty
I didn't understood the borrow checker until I subscribed.
Thank you Primeagen, you saved my life
you are welcome
The easiest way to beat the borrow checker is to write immutible code and pass by reference. Your debugging team (typically consisting completely of future you) will thank you.
Had multiple “aha!” moments during the span of this short video. Very concise and to the point. Thank you lots for this, it’s very helpful!
I did some leetcode today and was doing some Rust and C, and I thought about why I like to use rust, C often goes faster to get something to work.
And it's because when you write rust code, it takes a while to compile and work, but that's because the compiler more or less forces you to understand what is going on behind the scenes, Like in your last example with the reverse and map. To implement that type of logic, you pretty much NEED to understand what to code does to get it working. Whiles in many other languages you can often get away with code that's: " I don't really know how it works, but it works so I'm happy".
This is amazing and succinct. I literally gave a presentation on this to my company last week (we're primarily Java/JavaScript developers) and it was pretty much beat for beat. Granted I took 30mins instead of 8, but there were a lot of questions 😁
1:55 - it just clicked in my mind (after 2 years of casually coding in rust): the "use of moved value" can roughly translate to "use after free" error in c / c++, because you're passing ownership of `item` to `print_out_item`, as that function consumes it and rust frees the memory for `item`; therefore, you're trying to use a variable after it's freed from memory.
and that's a safety rule that rust enforces you to take into account. and that's why i mostly pass variables by reference and prefer to use `.clone()` as a last resort.
Great video as always. Would love one about lifetimes. They are the one concepts that I struggle the most in Rust
Learning c and c++ and it sounds like how shared pointers and unique pointers planned to work but no one thought them through
I can confirm that the borrow checker was a mystery to me until I subscribed. Once I did, it was as if the crab god directly uploaded the knowledge to my brain. 10/10 would do again.
The moment I subscribed on this channel I got all knowledge of Prime and an immediate offer from Netflix. Thank you so much Prime!
Yep, this is indeed amazing. I am a developer in multiple languages, with a main focus on C-family languages (especially C#, but also C/C++, JavaScript and Java). So I have seen a lot of things, but what Rust does is certainly special. Everything Immutable by default in combination with memory ownership by default. While still doing many things by-reference a lot like what people do in C++. Such that performance is maintained. Amazing.
I have very recently started to experiment with Rust and I am planning to do a lot more with it. Also taking into account some other thoughs and considerations. This language has absolute potential, even though it's also still missing some features, like varargs.
This is the first ThePrimeagen video UA-cam has ever recommended me. I have been binging ThePrimeTime videos for MONTHS and THIS is the FIRST video UA-cam shows me of ThePrimeagen!? But in all seriousness, I guess I need to just learn rust now.
Always a good day when I find a new UA-cam channel this great. I'm usually a documentation > video tutorials kind of guy, but it's hard to beat content this good.
People complain about side effects and then proceed to complain about a language that throws in your face when you're about to create a side effect
Papi Prime getting a sponsor 😱 good for you!
This video taught me what borrow checker is BLAZINGLY FAST
Absolutely right
I litterally asked GPT-Chat, like 14 hours ago, to show me, a TypeScript dev, a program in both Rust and TypeScript to help me understand this. And this comes out, Thank you!
so GPT-Chat told Primeagen to make this video
@@willi1978 That's the only logical conclusion.
I just started learning Rust, I'm having a hard time understanding some concepts but I'm loving it. Make more videos like this one plsss :)
This is a great talk. I made a small similar post about this for my company, about how Rust checks these things and how coding like this helps us think about how to program better in other languages. Incoming thought dump:
We've been having issues in Grails with an exception called Stale Object. Essentially a reference to a database Domain is getting passed to a service function, mutated with a save(), then outside and after the function that same object is getting mutated with a save(). Groovy lets us compile this code and normally this actually works most of the time. This is a data race. Because it's working with the Database this is an asynchronous process that gets obfuscated and we dont see it. We get this error when things don't catch up in time and the outside object gets updated first followed by the inner reference being updated.
Incomes Rust, if you tried to write the code the same way you'd get borrow checker issues because we tried to hold onto two mutable references at the same time. Showed this to my coworkers and they were kinda blown away that a language and compiler can tell when a data race happens. Imagine, no more data races. No more unknown BS in your code base.
Rust is hard, but most of the time it is correct! And I can use libraries written by Rust authors knowing it is going to work and not worry about some weird bullshit breaking prod code. Long live crab
Understanding Borrow Checker with Primeagen is so easy I now borrow without checking. Or something. Learning Rust when you are a Prime subscriber gets so trivial that the only thing that is Rusty nowadays is my JavaScript, which is what the language is by default, rusty.
You get the point, just subscribe to the guy. We need to subscribe until we find out why Maria did what she did. PorqUÊ.
MARIA%V???
God yes, the number of times in languages where I'm like, "hang on, am I passing a reference or the value here? Welp, just gotta find out!" is silly. I love that rust not only makes it clear, it gives you the choice!
Very good video, I never quite understood what the borrow checker was doing until now. The one thing that confuses me, however, as predominant C++ user, is that I am used to "pass by value" meaning that you pass the value into a function and any changes made in the function won't be applied to the overarching object/variable, and pass by reference allows you to directly access the object and change it. Interesting!
This is the first time I actually understood what is the Rust borrow checker.
My intuition is that its a mechanism that forces you to write safe code but at a much lower level. Kind of similar to how TypeScript forces you to write type safe code.
Now I just need an excuse to learn it further. But being in web land I doubt I'll have it soon.
You can totally do backend web dev with rust - check out the Axum framework.
The king of dev content nowadays. Appreciate all the education and entertainment!
I'm down for the borrow checker. Doesn't bother me at all. Great video. maybe I subscribe as Rust is new into my toolset. Complete beginner on Rust
Short. Compact. Informative. Three pages of the Book in 9 minutes.
6:32 I Extremely agree!! Oh, heavens!.
When I was first starting to learna language (scripting language) of AHK, I was traumatized by the odd behaviours I had to find through trial and error while working with objects like arrays. The second language I had turned into learning better than just basics was actually rust, and even though it was an about 3-4 months struggles (about 1-4 hours daily on average), It was really pleasant to learn because It was clearer to know what I actually was doing. Now my next pain I'm feeling in rust are web servers (Still reading chap 20), Macros and Iterators
Best tutorial ever on borrow checker.. Finally gained some confidence on the same. Thank you so much Primeee...
yayaya
@@ThePrimeagen yayayayaya
idk why i'm watching this video. I've been coding in rust for 3 years and know all this stuff. i guess ThePrimeagen is just too good of a teacher I want to re-learn what i already know
Basically variables passed to functions are c++ const by default and can be passed to a function only once unless passed using a reference, else the variable is owned by the function once it's passed. And to pass a variable several times to different functions and modify it (which is not functional programming but can be useful to avoid copies when needed) the variable needs to be passed as &mut.
the problem about c++ is pass by value
this catches many people off guard.
even worse is this
auto a = std::vector()
auto b = a;
BOOM copy. WHA????
c++ always has the worst defaults. Rust solves this very well.
7:55 in many languages we have const, in rust we have mut. rust is just const by default
I was struggling with learning Rust, particularly the borrow checker. But then I subscribed and it all clicked
can confirm, I only fully understood borrow checking after subscribing, it was like a door was unlocked and I walked through into a beautiful landscape of full understanding
Wow, subscribing actually helped with understanding of Borrow Checker...even if I don't know any rust yet...
its a big improvement, its wild huh?
Smashed that subscribe button and suddenly I'm seeing in 4K, understanding quantum physics, and speaking fluent Mandarin... I guess this is how Bradley Cooper felt in Limitless!
Clear like water, awesome Prime!!!!! I think a good topic is async in Rust vs Typescript, without TOKIIIOOOOOOOOOOOOOOOOO of course and the more simple way!!!!
Thank UUUUU
yeah. tokio is shockingly simple once you get the paradigm :)
not bad for first ad, though i can see more dramatic versions in future like ltt
agreed
You do a great job of being fun and entertaining while also being extremely informative and educational. Great stuff!
This is genius, actually. The best way to spread love for the language is to teach it
I really love the rust book. Concepts like these are explained quite well.
Ironically, working through "the rust book" and interacting with the borrow checker helped me understand how to use TypeScript as opposed to the other way around.
yeah, most people just simple don't know what is happening.
As someone who writes code in TS for a living and is now trying to dabble with Rust, this couldn't have come at a better time. I'm trying to write all of this year's advent of codes in Rust and yeah, the beggining may have been a little rusty (sry) but I feel like I'm getting the hang of it.
This video convinced me to try Rust! Great work ❤
Thank you for this great intro to the borrow checker! 👏👏👏
The reason of the less rust developers, we don’t have content like this, I hope it will increase rust community some day
I have never written a line of rust, barely touched typescript.
However, this makes a ridiculous amount of sense if you've completed all the side quests using pointers in C.
Maybe I'll actually write some rust code one day. If I do it will be because of stuff like this.
Very cool.
awesome!
I was having trouble understanding this video. Thankfully, I subscribed, and now everything is clear!
I liked the video but I noticed that the main concepts demonstrated here are already very well explained in Chapter 4 of the Rust book. Not only do you get an explanation of the borrow checker's rules e.g. immutable and mutable reference can't co-exist in the same scope. But you also get an explanation of why it is the way it is intuitively i.e. a user of an immutable reference is still reading from that value, so we don't want it be snatched from under their feet by allowing someone else to write (race condition case). They also mention that the overarching reason the BC is the way it is to manage heap data.
Oh wow, I didn't understand the Borrow Checker, but then I clicked Subscribe and now it all makes sense!
i knew it!
Wow, I subscribed and now I totally understand Rust! It’s that easy!
I was so confused then I subscribe, now I’ll writing a multi-threaded wait-free red-black tree algorithm in Rust. Thanks @ThePrimeagen.
So true, I didn’t understand the borrowchecker, subscribed to your twitch and then got it, first time
whoa, subscribing like opened up my brain to understanding primeagen concepts, thanks dawg. 👍
That was amazing. At the end, this borrow checker thing is not that hard to grasp at all (once you have some experience with programming in other languages, of course).
I also like the idea of explicitly say in the code what is mutable and what is not. That is a plus for Rust indeed. That makes code much clearer and predictable, I believe.
Good job, Prime!
Can confirm. Subscribing did in fact help me understand the borrow checker.
@ThePrimeagen wants to "reverse()" all the javascript developers into rust :)). Love your videos and your passion :D it's contagious
tytytyt!
Loving the content, but how are you getting the inlay information from compiler diagnostics in rust? I can't get it working in Nvim and I'm sure it's something simple and stupid I'm missing. I have the syntax stuff from lsp, but not the warnings about borrow order.
i am having the same problem. Have you found a solution?
@@double0028 I did, mostly. It has to do with diagnostic and virtual text, but rust_tools also wants those virtual_text lines. So you need to make s decision on what to use.
Cool think about knowing C++ is that any questions any new languages are answering - it was asked by C++ (most of them) so C++ developers almost always know why any language feature was introduced (Java, Rust, C#)
Love this, you explain this concepts super well
Man, great video! You explain things very well; clear and concise. Would love to see more of these.
@ThePrimeagen Rust now is heavily used in Blockchain development: nodes, smart contacts - and it will become #1 language for Blockchain
SUPER nice explanation (didn't expect anything else when I started watching)
Didn’t know mutating by reference was called borrowing, that’s when it clicked for me.
Thanks Primeagen :)
since I was subscribed already, it's so much easier to know the borrow checker completely
Rust also does not need a garbage collector -- precisely because of the borrow checker. Which is also only compile time, so no runtime overhead because of GC or borrow checking. Thus the reason it is fast. I learned that a few days ago only. Though I prefer nim or go instead, but I admit rust is cool and helps preventing a f.ton of coding errors.
I liked the last example. Very nice.
Your point that you stated that there is good to know if your passed parameter is going to be mutated or not, is valid, however in your comparison where you use typescript (and not pure javascript) you should mention, that in typescript types system you can also specify that idea of mutability.
For someone who doesn't really do tutorials, you make a good tutorial :)
I like that, it seems like a compiler-level CommandQuerySeparation pattern. I force that pattern in our team's coding guidelines as - like you say - it's pretty terrible when you don't know whether a function will mutate the args or not
Ta
Wow, fantastic video!!! Great explanation!
brilliant, thanks a lot. Comparing to typescript makes it so much easier! thnaks a lot