Structs in Rust
HTML-код
- Опубликовано: 7 июн 2024
- The ultimate Rust lang tutorial. Follow along as we go through the Rust lang book chapter by chapter.
📝 Get notified when the Rust Cheatsheet comes out: letsgetrusty.com/cheatsheet
The Rust book: doc.rust-lang.org/stable/book/
0:00 Intro
0:36 Defining/Using Structs
3:39 Function Constructors
5:13 Reusing Instance Data
6:00 Tuple Structs
7:10 Example Use Case
11:43 Method Syntax
15:11 Associated Functions
16:47 Outro
#letsgetrusty #rustlang #tutorial - Наука
📝 Get your *FREE Rust cheat sheet* : www.letsgetrusty.com/cheatsheet
It is kinda helpful that rust tels you what's wrong and you don't have to search the error on stackoverflow
It's EXTREMELY helpful and I absolutely love that in Rust
thank you you saved me from rage quitting.
I just read the structs chapter from the book. You are giving a fantastic walkthrough of the topic. Much easier to follow.
Man, VS Code is freaking awesome for Rust.
say thank you to rust-analyzer developers!
no
nvim with rust-analyzer :)
@@NexushasTaken No.
@@NexushasTaken No.
Thanks for these tutorial.
I was very dubious by the lack of OOP in Rust but implementations in structs has definitely converted me.
Let's get Rusty :D
It's more enums that do that
Such a wonderful course, congrats and thank you for the effort you put into this.
Thanks for your great content!
Your background music is a bit noisy, if you can disable it while recording videos, that helps alot for focusing on learning!
Following the course - it's getting powerful already, and we're not very far in. Nice!
These tutorials are amazing I never realized how good tuples were until now
This is fantastic, THANK YOU! I was looking for videos on Rust to get a feeling of it (learning casually whenever I have some minutes to spare, no coding yet) and the ones I found before yours were either too slow, too advanced or too light on code. But the way you do it is perfect for me. Explain, show example, repeat. Really awesome, thank you!
he's following the book which is very good , sometimes my jelly brain is too bored to read
Weirdly reminded me of TheNewBoston's C++ videos. Nostalgic. Great Tutorial
You are just an awesome man. Thanks for this great content!
love these, thanks so much for making them
Awesome, I hope there is goodness coming in future videos as well. Keep up the good work.
Great course, practical and useful
Very good and complete, thank you.
Thank you so much for your work.
Awesome course ! Thanks
amazing tutorials. awesome and fantastic. subscribed. thank you
Thanks, really helpful!
Love your tutorials. One "why can't" question.
Why can't String types accept String literals? It seems like the compiler could easily determine if a String type was needed, and cut down on some boilerplate
I think it's because String literals have type String slice. And saying "it seems the compiler could easily..." is very easy to say in toy examples, but can you make a set of rules that are guaranteed to do the right thing in ALL cases no matter how complex the code is?
You might ask, why are string literals slices rather than strings. Probably for better performance.
Very helpful :) i find these videos much easier to understand then the books
thank you for great videos
this was very good, thank you :)
very nice; super useful supplement to The Book
its' just really awesome!!
Great one!
Thanks a lot ^_^ it's very helpful ^_^
Hey! Thanks for the lessons, searched a great playlist and I finally found it :)
One question: Whats the point of using String, String::from(), when there is just a &str?)
Thanks for the video. Can you make a video on PhantomData?
cool.. see u in next vid
Definitely, thank you for your excellent podcasts.
Is there a typedef type of definition for a struct? I come from the hostile C environment where I make use of typedefs for structs and fields within structs.
Just learning and wanting to transition to Rust, and port my code over as a learning exercise.
Yes.
type NewTypeName = OldTypeName;
Hi Bogdan. Can you share which VSCode extension you use?
Do you have the repository about this examples? thank you, great tutorials!
uppercase `Self` keyword would've been a nice addition too
Please explain where instances of structs are created? On stack or on heap?
Great video! I'm curious what is happening at 2:50. Is the new "name" variable taking ownership of the username string, is it a reference or does it implicitly clone it?
Excellent question! In this case ownership is being moved. If you try to create another variable and assign username to it, you'll get an error.
@Erfa90 I had the same question. Turns out you get "partially moved value" if you are trying to use `user1.name`. Try `rustc --explain E0382` to learn more about it.
@@markusbergkvist4882 @Let's Get Rusty
This man deserves a hearted comment 💯
In this case immutable reference is the solution.
let name = &user1.username;
@@letsgetrusty 5:52 - What happens to the ownership of the attributes of user2 if we create user3 just without defining email and username?
i mean like:
```
let user3 = User {
..user2
};
```
Could you please point me in the right direction for this "fn initialize(ctx: Context) -> ProgramResult {...}" ... Initialize is a struct, does that mean ctx is a variable of type Context struct with Initialize struct inside?
So if I input &self, its like non-static method and if its empty, its static?
老师讲的非常好,感谢!美中不足是我的英语不太好,翻译的字幕看起来吃力。The teacher spoke very well, thank you! The only drawback is that my English is not very good and the translated subtitles look difficult.
Seem like a bug in rust analyser to annotate the arugments to functions with the parameter names. If I type this out explicitly, I get a compiler error since rust doesn't allow naming arguments to functions (just parameters at definition).
I'll look at opening an issue toward the extension but thought I'd point it out here too.
it would have been good to cover the storage of other structs in a struct, since this is where it gets pretty complex compared to other languages. once it's not one of the primary types
Do structs also follow the snake_case naming convention?
Do they have to start with upper case?
they should be in camel case. if you try otherwise, the compile/rust analyser gives you this warning:
Structure `Rectangle_Struct` should have CamelCase name, e.g. `RectangleStruct`
type `Rectangle_Struct` should have an upper camel case name
convert the identifier to upper camel case: `RectangleStruct`
perfect
Do I need to use all the attributes that we create in the structs ?
Is there a specific reason we used tuples for Struct fields at 6:20 or else could we also use arrays wouldn't which be a better fit for the job of storing same data types and also easy on memory as it would be stored in stack?
They should perform exactly the same, it's just a syntactic difference.
Good tutorials, i'm waiting videos about macro in rust 😃
Coming soon!
I'm a little thrown off coming from C++ and Swift that String and &str (literals/references to literals) cannot be implicitly interchanged, and thus requires an explicit conversion from the literal to a String with ::from("") which is ALL OVER programs.
Isn't there constructors that we can define for our struct
like the way we define constructors in c++?
Great tutorial, thank you.
Just add fn new(..args..) -> Self { ..code.. }
Is there a git repo for this ?
I rarely see people use tuples like class instances, is that how they are supposed to be used?
So Rust doesn't have something like a class where you'd put the functionality inside the struct itself and remove some clutter in the file?
How are "is a" relationships modelled? Say I want square. A square is also a rectangle and computes the area basically in the same way. In c++ i could use inheritance for that but how do you express that in rust?
And is there access control, something like "private", for structs in rust?
A square is not a rectangle in OOP:
A function that uses a rectangle can change its width and be guaranteed that the height doesn't change, but a square breaks that, violating the Liskov substitution principle.
@@AssemblyWizard An immutable square is absolutely a(n immutable) rectangle. If you allow mutation, and have Square inherit from Rectangle, your model is wrong.
You can express using composition, no?
1:26 almost a very unfortunate typo!
Is this in 24 fps?
30 fps actually
Hi!
I know this video was made in 2021, but what about this solution with the can_hold function?
fn can_hold(&self, other: &Rectangle) -> bool {
self.area() > other.area()
}
All the functions in the impl are associated functions irrespective if they carry an instance as a parameter or not. They are not methods if they dont have self as the first parameter.
Why do you sometimes use :: and sometimes . ?
Awesome as usual. Just wishing it didn't have the crappy background music.
why does the sign change colors on every camera cut
You make amazing content but just pointing out an error that is you can't do something that you did at 3:20 instead can use mem::replace
Let's Get Structy
So basically, associative methods are static functions?
I think i died in this episode
You are not alone!
Bro I'm loving rust right now but input gathering is killling me XD
I guess some people are getting confused by the errors showing up around 9:42, it can be solved by adding the return keyword in front of the expression. And a semicolon at the end, ofcourse.
what do you think why rust doesn't have classes?
Rust has other tools such as structs and traits which allow you to accomplish similar goals while favoring composition over inheritance.
OOP requires polymorphism, which is not zero cost. It requires RTTI and every virtual call requires a lookup. It becomes quite costly over time.
@@Christobanistan yea that can be a valid reason, after reading more on structures in c I feel like the way they implemented it is really awesome, all I need is to bind data and the capability to call methods on it and there are access specifiers too
@@Christobanistan I hate Borrow checker though
@@sahilverma4077 then learn c++, very similar but without safe memory management, which is what the borrow checker accomplishes
Good course. But the background music is distracting to the point of maddening.
Great tutorial but the background music is very distracting.
As someone who is learning rust I kinda hate this vscode module. When assigning user2 it is not obvious to people learning rust that email and username should not be typed out, if you do type it out as shown and test or build you will get an error because rust functions do not support named parameters, they are positional only.
is it possible to remove the background soundtrack? it gets annoying after sometime
This one hurts my head.
"chapter 10"
Love your videos, but the background music on this one makes it impossible to concentrate.
It's so distracting seeing the flag on the wall facing the wrong way.