The Rust Survival Guide
Вставка
- Опубліковано 23 чер 2024
- Think Rust is hard? In this video, I'll guide you through the essential aspects of Rust programming. These topics often pose challenges, leading developers to the brink of frustration. By the end of this tutorial, you'll be armed with the knowledge to write Rust code confidently.
FREE Rust cheat sheet: letsgetrusty.com/cheatsheet
Rust strings explained: • Strings in Rust FINALL...
Rust strings explained 2: • All Rust string types ...
Chapters:
0:00 Intro
0:45 Memory Management
2:18 Ownership
5:19 Borrowing
10:02 Lifetimes
11:53 Conclusion - Наука та технологія
📝Get your *FREE Rust cheat sheet* :
letsgetrusty.com/cheatsheet
I know it took effort to create and all that stuff but come on, remove the registration bs and just make it free to download or just don’t at all.
@@essentialGI support It doesn't look like it's free if you have to sign up.
In the example with pushing an element to the vector you introduced a bug, when you put last element in the variable there was the last element of the vector before it was modified (not 4), but after you swap lines in the last there will be always 4. That's why when you fight with borrow checker you might introduce bugs in business logic. But in this case I believe unit tests are good option to fix that.
Any one figured how to handle this case ?
@@coding8730 hello! I tested a little and the workaround I found is dereferencing with * symbol.
like this
let mut b = vec![0, 1, 3];
let n1 = *b.last().unwrap();
b.push(5); // Compiler doesn't throw error
println!("{}", n1);
The code works OK.
Finally a brief/quick explanation/example for lifetimes!
Apparently, I've missed the part about the generic collapsing to the shortest duration among matching arguments each time I've tried to learn.
That part of the vid could be its own clip/short.
Using the colored vertical lines is a great way to visualize the lifetimes. You could also add inline color to the matching variable references.
The "longest of two strings" is the example from The Book, and everyone uses it, but very few explain what's actually going on. This video is no better in that regard. One video that does explain what's going on (or at least is honest about the fact that there is more going on, and tries to begin pulling on that string, because it's way too much to cover in 10 minutes), see "but what is lifetimes" by leddoo. For a more thorough introduction, Jon Gjengset has an hour and a half of "Crust of Rust: Lifetime Annotations".
@@MasterHigure
Thanks for the pointers to some deeper dives. But yeah, what I appreciate about this video, is that it gets the gist across very concisely/quickly by leveraging animation/visualization.
So how to solve it?
Ive never watched anything about rust or memory stuff in general but still understood most of the things you explained. I would say you did an amazing job at explaining it
I have just wrote down these rules into anki cards after watching video from your rust playbook's course yesterday. I have repeated these cards already for like 3 times and i can say that starting learning rust through spaced repetition is greatest decision i made and i recommend this way for everybody
You explain stuff really well bro, thank you!!
Explained both simply and with details. Really good work!
Really good teaching by example here. I feel like a lot of the time words themselves fail to illustrate concepts like this. Seeing how it works with actual code really cements it. Please keep making videos like this where you can demonstrate such concepts, thanks!
I find with a lot of tech, I need to learn from a combination of reading, listening, watching and practicing. I pick up different things from each medium.
@@kevinmcfarlane2752Totally agree, some things are easier to learn from theory than practice and vice versa.
Wow I can really tell the quality of your content has gone up. Bravo! Good job
Wow.... incredible concise and informative. The line illustrations really helped. I feel like cracking back into rust for some longer running data processing I have to do. Thank you again, looking forward to smart pointers video!
Really clear and concise! Nice work.
Thank you for highlighting these Rust essentials in memory management as well as your clear explanation.
you are an amazing educator! i look forward to your Rust bootcamp 🦀
Wow this was really well explained video of one of the central concepts of Rust!
great job! please continue this series.
I tried it the last couple days and I practically fell in love with the language. rustc and rust-analyzer are incredible! And the language itself is amazing once the light bulb switches on in the back of your brain. I'm pumped :D
Your channel is a gem by the way! Thanks!!
a small rusty island of understanding in this youtube, thank yu, keep going!
This video is insightful. Thank you
You need to make a course, well explained🙌🏽.
You have earned my subscription, Sir. Great video; very well presented! ❤
Clean explaination. Thx!
Your channel is a gem bro thank you so much
Linda explicação!! Parabéns pela didática!!
Especially the lifetimes section was bery helful, thank you!
Excellent explanation!
I’d like to see more content like this. Big thumbs up 👍
My dude this was super helpful thanks
Great explanation dude
Excellent explanations
Thanks. That was easy to understand 😊
Well explained!!! ❤🎉
Excellent video! Thanks
Thanks, waiting for part2
Tbh I got like 50% of it as I've never coded in rust. I hope this would be of great value when we start rust in our project next month
Great video! We want more!
Thanks!
Thank you, this video is very useful!
While it might not have been intentional this video does a great job convincing and explaining why Rust is so fast and memory efficient.
also when I started learning programming Lifetimes is how I imagined a garbage collector worked but was shocked to learn most garbage collector eat up runtime to cleanup your memory. Rust seems like a fun language to learn.
Great video! Thanks for making it!
I was following everything perfectly until we got to the section on lifetimes. I felt like that was a bit rushed and included a bunch of information that wasn’t explained.
that aside this is one of the best simplest explanations of ownership and borrowing in rust I’ve seen. Thank you!
Rust's borrow checker checks lifetimes one function at a time. The function signature contains everything necessary to know if there are borrowing mistakes in it. Without this understanding, borrow checker might seem as this complex system that traces lifetimes across modules. Nope. One function at a time. The function signature is the key to understanding lifetimes.
Great explanation, thank you
The problem with Garbage Collector is not always the runtime overhead, but inconsistent freezes up to a few milliseconds when it's doing the garbage collection. A program in Go will have spikes of cpu load whereas the same program in Rust will have slightly higher median load but more spread out and predictable.
I think Java's Generational ZGC is interesting, it has sub-ms pauses
Great video, thanks for making it :)
Thanks for the clear explanation. Will be pointing ppl here if they struggle.
Feel like I gotta watch this so many times. Rust is my first programming language I’m learning. I’m stubborn so I feel like I can do this!
Great stuff Bogdan 👏
Great content.
best explanation thank you so much!
Thanks. Doing Gods work❤
6:20 Moving `x.push(4);` up a line changes the behavior. Can we instead move it below the print statement? Maybe wrap the let and println statements into their own scope?
...or clone/dereference the value of `last()` so that the value that we add to the local stack (variable reference) *is* the integer rather than a pointer into the heap.
7:15 yeah i was thinking same. thanks for mentioning it.
this particular example shown in video is not practical, but i reckon that he was just focussing on the borrow validation.
@@yash1152 it is pretty practical actually. It actually proves the rule is incorrect as stated. The actual compile error speaks in terms of time / location of usage.
This. Fixing a problem by writing the wrong business logic is not a good advice.
hello for anyone wandering! I tested a little and the workaround I found is dereferencing with * symbol.
like this
let mut b = vec![0, 1, 3];
let n1 = *b.last().unwrap();
b.push(5); // Compiler doesn't throw error
println!("{}", n1);
But I'm a newbie, so idk is this good or bad. It just works :D
Awesome video. :)
Awesome video
My problem with rust evangelist is when people say is not easy, and they inmeditialy start showing the incredible way rust is super optimal, wich is true but that doesn't alievate the learning curve.
I love your survival guide because you really show us how is it done
The reason why Haskell failed compared to Rust is that the Haskell community's attitude towards people who complained about the complexity of the language was along the lines of "Maybe you are not smart enough for the language like we are? Too bad, because this language is superior to every other language once you understand it.". Rust took different approach and invested heavily in material that focused on making the language as easy to learn as possible through official language book / tutorial, in-code documentation code examples (for every standard library function you have instant access to not only the documentation of what the function does but how it is used with runnable code examples) and community efforts.
@@meanmole3212Yes, imagine if Rust didn’t have that stuff. Many would just have moved on after the first hour.
@@meanmole3212 The century is still young -- Haskell still might catch on, but I'm hoping that something Lisp-y will get there first.
Evangelists have already climbed the learning curve (or at least I hope so, though I know some who evangelize even when they barely know stuff themselves).
this was amazing
i studied rust for like 3 months, but now in the uni working on a c++ project i am unintentionaly doing everything rust style. Enums, optionals, etc
This is a good reference vid.
I'm already well into Go as a self taught programmer, likely even employable at this point. My only concern with Rust is the job market, are their even jobs for it? Everything else about it is great, even the way it manages memory is pretty straight forward.
11:04 another way to phrase this is that the lifetime annotations here tell the borrow checker that a and b must live at least as long as the returned value needs to live.
Tbh I think ownership, borrowing, and lifetimes are the easiest topics to learn in rust just because there is SO MUCH content on these topics. If you were doing a memory management video I wish you would've gone into things like Box, Ref, ARef. There isn't a ton of content already out there
Keep it up, more please :)
more video of lifetimes please, especially its annotation in struct
Thanks i have better understanding of lifetime now
Great Video
Never used rust, but it seems super interesting
hey im curious, what video editor did you use? and how did you color the (code) text ?
"The Karen of all compilers". Priceless! You have a hot channel. Keep up the great work.
Beautiful video
new to rust, finally here I know what is
It's pretty typical to use 'a as a "throwaway" lifetime when you don't think it's important to give it a better name. Just habit in this case.
Waouh, Rust is so different from everything i've seen until now.
This video should be included in the official documentation
Could you make a video about most common pitfalls that newcomers fall into? I made same script on NodeJS, Bun and Rust and for some reason the one on Rust has the worst performance. Mostly I used: strings and &str, async functions, reading / writing files and actix-web framework. I understand what you described in this video, but still failed to get good performance
need a follow-up video!!
The fact this video never mentioned reference counting drops its significance by a lot.
"If you
have objects that are used in multiple places and passed around, and
you don't have refcounts, your code is almost certainly broken." (c) Linux documentation for krefs
This is definitely a video about Rust. Yes indeed.
I guess this is kind of nitpicky, but in the first example for explaining the borrow checker (7:10 ish) the code you change it to doesn't do the same thing as it did before you moved the push. Before resolving the borrow checker, it would print 3, but after you "fixed" it, it would print 4. I feel like it wrongly gives the impression that some things aren't "possible" in Rust when there is a way to do it, you just have to be explicit about how the memory is managed (e.g. use a box or something). But I get not wanting to over-complicate it; it probably would have been more accurate/good enough to just move the push after the print, which would maintain the same behavior. Great video nonetheless!
Actually, you just need to move the push down, making it after the print statement. He stated the rule incorrectly. An immutable reference can exist here, but no mutations should happen before the use of the immutable reference.
This is fine:
fn main() {
let mut x = vec![1, 2, 3];
let last = x.last().unwrap();
println!("{:?}", last);
x.push(4);
println!("{:?}", x);
}
In fact, the error speaks in terms of time / location of usage. It does not say "cannot make an immutable borrow".
Ref: rustc --explain E0502
Great explanation. As newbie, 10:42 when defining lifetimes, did you choose to name it by character "a", is it rust convention, or is it related to the function parameter a ?
General convention I've seen is to try to pick a name that makes sense for what the lifetime represents (ie if you have a "DbManager" struct that holds some objects and you take a reference to that object, it'd be wise to use 'db or 'mgr as the lifetime name so that you can more easily tell what the lifetime represents), and if there isn't a good name, just go through the alphabet.
Please create a Rust bootcamp.
Please..... @letsgetrusty
Read rustbook
He already did lmao
I second this, from South Africa 🌍
He did, 2 years ago
The borrow checker is a really smart solution or in general escape analysis. I think the next step would be to do something that Nim and perhaps Swift does. It moves values by default like in Swift but when it notices a shared value it reverts back to reference counting. This way you should get very good performance perhaps even optimal performance when they perfect this formula. In other words zero-overhead memory management. IMHO manual memory management is on life-support and will not be done in the future, how soon it will be a thing of the future I cannot predict. It might be 5 years, 10 years or even 15+ years.
Rust tries to avoid doing things "by default" and instead relies on the programmer to tell it how to handle a situation. Explicit ".clone()"s, borrows and moves make it very easy to avoid memory bugs and work alongside other programmers who's brains you do not have access to.
@@theninjascientist689 That is true. But the point I was trying to make was that the "relies on the programmer to tell it how to handle a situation" will eventually be a thing of the past. There was a time when handwriting assembly was the best solution because compilers were not yet good enough for optimal code. In the meantime, until automatic memory management becomes the norm, the borrow checker will be a vital tool in most system languages.
I was looking at gdscript vs C# and one comment said reference counting is garbage collection, just another form of it, I wonder what could be argued against that.
@@xdanic3 Yeah, garbage collectors AFAIK uses reference counting to track lifetimes. However, Swift uses something they call "automatic reference counting" ARC. I'm not sure exactly how it works, though, but they claim it's not a garbage collector.
the next one that need to be discussed that not being mentioned => closure behavior over function, trait satisfying with derive.
At 7:13, doesn't moving the call to last() after push() change the value of the `last` variable to 4 instead of 3?
Yup, it does change the behavior. If you want to add 4 to the list while still having `last` to evaluate to 3, move `x.push(4)` below the println. He gets the main point delivered, but code examples could be better.
Amazing Video. Wow ===>> Very good Job well done!!!!! Big hug!
Rust players when they stumble upon this video...
Rule one of borrowing is wrong as the intended result of the not compiling version is not the same as the proposed solution. You introduce a bug in the code to satisfy the borroww checker.
Which softwares do you use for creating videos?
6:33 just to clarify: the immutable borrow here is the last *element* of x eg. the &i32 which is returned by last - not x itself and then below that, the mutable borrow is &self which is x itself? Man I'm so confused...halp meeeeeee
Is it good to be interested in Zig also and should one learn it
Lifetimes made my head explode 🤯
Anyone noticed how the compiler will give a lifetime annotation error even when there's not inner scope? Also the compiler didn't see s1 is always returned. There was no need to even annotate the lifetimes, but the compiler still made you do it
An inner scope is only one way that this can happen -- any transfer of ownership will cause this to happen.
It IS the case that the compiler could figure out some of these lifetime contentions, but not all of us have that much time.
Pretty f-ing good!
Zig is a strong contender, newer so not quite on par with Rust yet but it's getting there.
Honestly it sounds rather intuitive, simple even, when youre learning about it.
then you try to actually do anything
Yep. Exactly what I just said a couple of minutes ago! 😊 But you just have to keep plugging away. It’s satisfying when you get there.
@kevinmcfarlane2752 is it really worth it tho? some of the most elegant, concise and clean code I've seen was written in rust. but the opposite is also true. if there's not an idiomatic way to do something, the code ends up looking really ugly and unsatisfying
Karen rust compiler vs Chad cpp compiler:
-Compile this bro.
-Yes master.
-> Segfault
My main issue is I can't figure a side project to hone in all the fundamental stuff that isn't too complex
How do I use wasm-bindgen to use yew and nodejs in vitejs?
I can say that ownership concept is kind of easy to understand. The most difficult for me in rust are macros. Looks like something weird that shouldn't be in this language.
Macros are indeed weird, but they're kind of already not in the language. Rust macros are code that writes Rust code. Most beginners shouldn't be reaching for macros as a tool to solve their problems.
Procedural Macros are one of the things that attracted me to Rust.
Macros is unfortunately needed in order to simplify a lot of stuff that is incredibly tedious to write in pure rust. It is used extensively in language bindings. There is a reason people complain so much about boiler plate in C and or make ad-hoc code generators on a project by project basis. But it seems that Zig's comptime is a better way to do it.
@@NicolaiSyvertsen Can you give me some examples of what you've had to write macros for? I'm curious
0:13 Zig also fits that criteria, not a rust hater, just saying
Zig doesn't guarantee memory safety
@@megagurka Well, going by Rust's definition of memory safety, a memory leak is safe... so...
@@professornumbskull5555It is not "Rust's" definition. It is the definition in CS.
@@dmitriidemenev5258 You're missing the point.
@@professornumbskull5555 Memory leaks in Rust are possible but are generally related to the improper use of Rc, Arc, unsafe. The logic of these memory management primitives doesn't allow for avoiding memory leaks.
Proper solution of this problem requires garbage collection, which has a non-trivial runtime cost and implications. Or maybe another language mechanism that is yet to be devised.
The guarantees that Rust provides are still greater than those of Zig.
Don't get me wrong, Zig is awesome. It's comptime capabilities are great but it's easier to improve compile time capabilities of Rust than to fix safety in Zig.
OCaml set a precedent of achieving even more complex feat by adding resemblance of ownership/borrowing in a language with GC but it introduced a lot of complexity.
Without a complete overhaul, safety in Zig might be fixed only in the form of additions similar to type hints in Python.
11:55 “you’re well set-up for the rust of your rust learning journey”
Heh
Is it not possible to lie to the compiler and cause memory errors with the generic lifetimes bit? Feels like it could be possible....
Lifetimes are annotated with single quotes, not ticks.
> Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not
title should be "The First of Many Rust Survival Guides"
I wouldn't use Rust for everything, but it is complementary to my other languages (I mainly use Python since I am a Django web developer).
However, I find that Rust is the least frustrating language to use (I don't trust google that much to use Go) for low level programming, and I really don't think it's hard, I has a different perspective, It's "Different" not hard, tho the syntax sucks (IMO).
Struct lifetimes please!