Understanding Ownership in Rust

What is this b here ----- > if item == b' ' {
return i;
}

well, this one is not easy to understand. 😭

I am going to watch this every day until I understand it in my bones

daning kruger the video

I read the book and i was overwhelmed of new terms and information. this video helped me to visualize it live. yes rust book visualizations were great but for me i find this more helpful. i think after watching this, i will understand the book better. thank you.
there are too little learning resources for rust :)

Can you help the beginner? Is there a possibility for borrow-checker to help to control partial structure updates? I mean can I pass the whole structure to the functions and in&out but borrow checker could help/nag in case called function changed a field value but the rest of the caller function code assumes the value has not been changed/updated? Can you show an example for the structure with the basic u32/int fields?

"Get them tattooed, whatever it takes."

Don't threaten me with a good time buddy.

Thanks for the great website hosting info! Ive examined DreamHost and A2 Web Hosting, but Cloudways with TST20 coupon is the real gem.

I dunno, this seems like a pile of malarkey when proper message passing mechanism could be created in any language.

In C++ you use std::unique_ptr and it auto-deletes when out of scope. Use of `new` is practically deprecated at this point.

This is BY FAR the hardest part to learn Rust. It's frustrating to learn without any C background tbh.

How/where are u executing a()?

This is so confusing. I will have to get back to this later.

Coming from c++ this is intuitive. Unique pointers and move semantics give this type of behavior as options in modern c++ so having them as the default makes sense. Also having the const as default on refs is another good safety measure. I do think a basic understanding of pointers in c and references and smart pointers in c++ will help people understandownership and the ideas it's built upon.

These are great. But some language seems to be used inconsistently in this series and it’s quite frustrating.

It seems copy == clone
And reference == pointer

But if these are different or the same it wasn’t clarified. That’s the frustrating thing.

I tried reading the book but it made no sense. After watching this video I finally understand the ownership and borrowing model.

I work with node and go for my serious business projects but I did get a offer from a firm that uses rust and pretty flexible timeline if I ever wanted to onboard. This got me into going through the rust book and learning the language… I really like it! I also liked go a lot too.. probably because I started in insane crazy js land now these relatively new languages seem to nice

Rather than plagiarize the book, maybe you could demonstrate your understanding by coming up with your own examples and explanations.

i love you bro

Bro you are going to the solutions very quickly without letting us understand the problem. You are not a robot, you can go slow and not act like you're reciting an entire book at 2x speed. No offense

I wish I found this language sooner 😫. The control and defined, predictable behavior is so appealing.

the reference and borrow is definingly the best part of this tutorial

and yet C++ is faster than Rust even with manual memory management.

Regarding the dangling reference, how is '&s' a dangling reference when it is in the same scope as the value it is pointing to? It seems valid to me because the value doesn't get dropped until after the '}' which comes after '&s'

Blaaazinglyyy fast

Best explanation about ownership and borrowing, it helped me a lot.

&str = "hello world" is stored in binary, it's that means "hello world" is directly store in exe file?

You don't need bugs in a garbage collector to create memory leaks. You can easily create a retain cycle with a circular reference.

字符串（String）和字符串切片（&str）这块是最容易懵逼的。

great video bro

Who 0.5x speed？

You could have added: automatic managment in cpp, which has built in types like std::unique_ptr which does the managment for you. You can get by without using pointers in 99.9% of the code.

Honestly man, your videos have really helped me whilst I go through the book. Theres a lot of information to consume so appreciate you taking the time to make these accompanying videos (y), some things are easier to see than to read and vice versa :)

You taking ownership is tedious but why?

Nah... You don't really understand this stuff. Most of what you said is pretty close, but kinda shows you paraphrased a bunch of information you never really engaged with. Your description of stack frames was about a C-/D+ . Functions don't go on the stack, it's the variable data like function arguments and return values. It's possible to put a function pointer on the stack... It largely depends on the ABI and calling conventions related to your architecture. An entire stack frame, however is usually used to save the processor core state when switching contexts.
Also, if you use the heap correctly you usually don't hit any performance hit unless you malloced an ass ton of data that's much larger than your L1 cache.
Someone needs to do more homework.

Best video on rust ownership

I love u, thanks for the clear explanation

I appreciate them trying to make cool stuff and all, but seriously the range syntax could just have been a function and slices could just have been a method
It's not something that deserved its own syntax

S is string literal. If we want dynamic string need to use string type. Ack! Can you see how that might be confusing without clarifying "str" primative type vs. "String" complex object type. I know Rust doesn't have objects, or maybe calls them something else, but objects are a concept I can understand and are prevalent in one or two other programming languages.

great video!

I have found my Cherno for Rust

cut the crap out