I've also learned that you can put the name of the variable inside of the curly braces if you like, instead of outside of the double quotes. eg: let x = 10; println!("x is equal to {x}"); Figured I'd share since I personally prefer the readability of my code when I do it this way :)
you need to have a rather new version of rust to do it however. it might seem like a no issue, but at work it is not uncommon to find yourself using something older, because its tested and porting is dangerous. like java 8 or even java 7. rust is probably no different.
@June@97 Imagine having {}{},{}!!{}--{}++{}bla bla{}{}, apple, pear, grapes, bananas, etc and now you have to delete one specific in the middle of this mess, {apple}{pear}{grapes}{bananas} seems better
I don't think it'll be one of those massive programming languages like Python or JavaScript. I think it will fall more in the range of c and c++ as a low level language. This is because it is a very low level language and more difficult to learn than most other languages pushing most beginners away from it.
@@thehollowknerd3858that's like saying "meat will never be useful in a candy store", of course it won't because it's the wrong use case, you can't compare rust to Javascript, nor python.
4:32 wasnt sure if i would actually use this but right as i saw it tell you exactly what to do i changed my mind completely, im switching from c++ to rust
That's not name shadowing, that's static scoping. To elaborate, static scoping is what you described: you cannot use a variable outside of the lexical scoping. You can use the variable name as many times as you want as long as you are not inside the same static scope. Name shadowing is specifically where you are able to reuse the same variable name in the *same* static scope.
I am programming in Java since a lot of years now and the series was a nice intro to rust.. i started watching because i was bored and i actually think i'll take a deeper look into rust now.
As a seasoned C/C++ programmer who wants to take the first careful steps into Rust, I really appreciate your tutorial. In these two languages, I would call myself quite seasoned (after all, this is what has been paying my bills for the last 18 years), so a tutorial that doesn't introduce basic programming concepts but focuses on how things are done in a certain language is exactly what I am looking for. Therefore, big thanks! There's just one thing that I'd like to politely ask for - and maybe you are already doing it in more recent videos, I just stumbled across your channel, searching for a Rust tutorial. Please don't include background music while you are talking. While it is certainly something for intro and outro, when there is something going on "behind" your explanation, my ears always try to focus on that instead of what you are explaining. While I do lime cinematic videos having cool soundtracks, it doesn't add anything to a video of this type. Of course I don't expect you to upload the videos again without the music, it's just something you could possibly consider for the future if you haven't already.And I am sure I am not the only one who feels like this...
I'm new to Rust but was going through their free book and you can also cancantonate string values to include the variable as in example println!("X is: {x}"); rather than comma notate it
Just subscribed, fancied learning Rust (as a beginner) and your first 2 episodes were very well explained and I really appreciate how well you worded everything. Thanks for making these tutorials.
this programming tutorial is great im a new programmer that started in c++ this was really understandable and really helpful and i understanded everything thank you for making this tutorial
Moving from python to Rust, and being an anarchist that I am. I experiment. Easier string formatting; instead of "println!("x is: { }", x)" you can just do "println!("x is: {x}")" For me personally, I always find this to look more readable, but I also have a deep hatred for commas. This is really just gonna depend on how you learned, I learned this way, and it feels nice that I can apply this in Rust, AND!! I don't even have to put an "f" at the beginning of the string, it just knows to format it. (python = print(f"x is: {x}" for context.)
It would be really awesome if you could, at some point, make an "_alternatives_" video between Rust & for example Python's most used libraries: e.g. "The equivalent of python's requests lib is and it's used like this you can use it like this". Otherwise, great content. Keep it up :)
I do like that Rust is immutable by default. However, coming from a language like Swift or Kotlin, I do find the distinction between const and let quite strange. In Swift and Kotlin you declare a variable with the var keyword, but the convention is to use constants by default, let in Swift and val in Kotlin, which both have type inference.
The difference is that a "const" is a compile time expression while let defines a variable. An immutable variable can only be set once but it can be set to any run time expression, which may depend on other variables or an return values of a function call.
regarding the variable re-declaration changing data types; would it be accurate to think of it like using &variable in c++? where instead of changing the datatype we're changing whats in that memory location? and the rust variable being more like a pointer than an actual variable?
10:06 I guess a better way to show what is actually happening would be to make the first x mutable and not recreate it before the last print, just adding 1 and print the references of x on both scopes every time succeeding the print of x's value. You would then be left with Identical refs for the first and last prints.
It seems counterproductive to me to only enforce types on mutable variables. You're either going to encourage people to define everything as mutable, or you're going to allow people to undermine the static typing of the language by redefining variables. Either option seems bad to me.
It sure seems that it be a helluva lot easier to work with if variables were mutable by default. Any practically logical reason why they are immutable by default besides scoping?
Rust is interesting to me as a embedded developer. It would be cool to use it for embedded in my work but c and c++ are so engrained into the industry that I don’t they they will leave any time soon
Tim, thanks But also your closing cmd is irriating me. alt+tab back, up on keyboard to get the cargo command back, then execute. Thanks for the series though!
constant is not changeable in the entire scope - not entire program. It's allowed to redefine it in another scope. And you cannot use upper constant to calculate new constant in the lower scope. Allowed is: const VALUE_CONST: u32 = 20; println!("The VALUE_CONST is {}", VALUE_CONST); { const VALUE_CONST: u32 = 10; println!("The VALUE_CONST is {}", VALUE_CONST); } println!("The VALUE_CONST is {}", VALUE_CONST); Not allowed is const VALUE_CONST: u32 = 20; println!("The VALUE_CONST is {}", VALUE_CONST); { const VALUE_CONST: u32 = VALUE_CONST + 10; println!("The VALUE_CONST is {}", VALUE_CONST); }
apparently the mutable variables have been changed (either that or my install of rust is different for some weird reason) and rust prompted me to remove the mut so yeah... edit: its because I had used let both times hah
I think that the thing is called "macros", basically it's like a function, but it has a few differences. He probably will talk about them in the future. If don't want to wait, I highly recommend you to check out "The Rust Programming Language" book, there is a section about this topic.
Why does rust create new problems from scratch as language features? Why can't we have nice programming languages? Why they all do try very hard to be quirky?
As someone that started with C many many years ago, all these new languages and styles and whatever, feels more as a hindrance than an actual tool to write better software. A Variable, by name, is variable. A compiler needs to compile the code, not telling me if I read or not a variable, especially if I am designing my algorithm.
It is just a declaration of int 32, we also have int 64 which is called u64 in rust but both basically are the same, but they differ in compiling speed and precission u64 is much more precise but is a lil bit slow I would say (not really sure check it out), whereas u32 is much more faster to process for cpu's, due to which it is commonly used in rust while declaring integer types. Hope this helps!
I've also learned that you can put the name of the variable inside of the curly braces if you like, instead of outside of the double quotes. eg:
let x = 10;
println!("x is equal to {x}");
Figured I'd share since I personally prefer the readability of my code when I do it this way :)
yeah! I was about to write that, string literal is called, awfully similar to JS lol
you need to have a rather new version of rust to do it however.
it might seem like a no issue, but at work it is not uncommon to find yourself using something older, because its tested and porting is dangerous. like java 8 or even java 7.
rust is probably no different.
@June@97 readability for the devs
yes it is more readable and understandable compared to the tutorial.
@June@97 Imagine having {}{},{}!!{}--{}++{}bla bla{}{}, apple, pear, grapes, bananas, etc and now you have to delete one specific in the middle of this mess,
{apple}{pear}{grapes}{bananas} seems better
I think rust will be the next big language
ye hopefully our effort pays off later
I don't think it'll be one of those massive programming languages like Python or JavaScript. I think it will fall more in the range of c and c++ as a low level language. This is because it is a very low level language and more difficult to learn than most other languages pushing most beginners away from it.
It’s only big when you build with it and what you build with it also matters
@@thehollowknerd3858that's like saying "meat will never be useful in a candy store", of course it won't because it's the wrong use case, you can't compare rust to Javascript, nor python.
Dang. You were right!
4:32 wasnt sure if i would actually use this but right as i saw it tell you exactly what to do i changed my mind completely, im switching from c++ to rust
Name shadowing is common in statically typed languages like C++. e.g. if you do
for(int i = 0; i
The fact that this is not the case in e.g. Python really caught me off guard. The C++ way makes way more sense in my opinion.
That's not name shadowing, that's static scoping. To elaborate, static scoping is what you described: you cannot use a variable outside of the lexical scoping. You can use the variable name as many times as you want as long as you are not inside the same static scope. Name shadowing is specifically where you are able to reuse the same variable name in the *same* static scope.
I am programming in Java since a lot of years now and the series was a nice intro to rust.. i started watching because i was bored and i actually think i'll take a deeper look into rust now.
I am using this playlist to start learning Rust once for all, everything goes great so far!
It's bloody awesome you still using Sublime Text in 2023, it's a great IDE and fast as Sonic.
As a seasoned C/C++ programmer who wants to take the first careful steps into Rust, I really appreciate your tutorial. In these two languages, I would call myself quite seasoned (after all, this is what has been paying my bills for the last 18 years), so a tutorial that doesn't introduce basic programming concepts but focuses on how things are done in a certain language is exactly what I am looking for. Therefore, big thanks!
There's just one thing that I'd like to politely ask for - and maybe you are already doing it in more recent videos, I just stumbled across your channel, searching for a Rust tutorial. Please don't include background music while you are talking. While it is certainly something for intro and outro, when there is something going on "behind" your explanation, my ears always try to focus on that instead of what you are explaining. While I do lime cinematic videos having cool soundtracks, it doesn't add anything to a video of this type. Of course I don't expect you to upload the videos again without the music, it's just something you could possibly consider for the future if you haven't already.And I am sure I am not the only one who feels like this...
Tim, I can’t express enough how much I enjoy your tutorials.
I've had so much trouble learning rust but you make it easy
Been waiting for this for 3 days!!!!
same
5:00 Every day I'm reminded what a blessing python's f-strings are: print(f"x is: {x}")
you can do that in rust without the f beforehand
@@ltdbtc2944 why didn’t he do that then?
@@JakeFace0 cause in this video or last he said he was only learning Rust for a few days
I'm new to Rust but was going through their free book and you can also cancantonate string values to include the variable as in example println!("X is: {x}"); rather than comma notate it
this is such a great help. thanks a bunch
Thanks for this. Makes the code easier to read. Similar to f-string in python 😅
@@ifeanyinneji7704 yea I was pleased by it too for the same reason 😂
thanks for posting the whole series at once!
Just subscribed, fancied learning Rust (as a beginner) and your first 2 episodes were very well explained and I really appreciate how well you worded everything.
Thanks for making these tutorials.
Is it overriding or storing in different RAM area as new ref?
this programming tutorial is great im a new programmer that started in c++ this was really understandable and really helpful and i understanded everything thank you for making this tutorial
Awesome when I was starting Python, years back, your series helped a lot for fundamentals I know this will increase my understanding in Rust :)
Moving from python to Rust, and being an anarchist that I am. I experiment.
Easier string formatting; instead of "println!("x is: { }", x)" you can just do "println!("x is: {x}")"
For me personally, I always find this to look more readable, but I also have a deep hatred for commas.
This is really just gonna depend on how you learned, I learned this way, and it feels nice that I can apply this in Rust, AND!! I don't even have to put an "f" at the beginning of the string, it just knows to format it. (python = print(f"x is: {x}" for context.)
11:30 was a bit of weird to me to do something like this, but it definitely proofs the point of redefining something
It would be really awesome if you could, at some point, make an "_alternatives_" video between Rust & for example Python's most used libraries: e.g. "The equivalent of python's requests lib is and it's used like this you can use it like this". Otherwise, great content. Keep it up :)
Tim, you make this super simple to understand even for a semi-noob like me... Thanx!!!
Yes we definitely want this course 🤧
Don't stop this series ,and add project pls
Hey you can use rust analyzer and code runner plugin for better productivity and intellisense for rust.
When I first learned Fortran many years ago, you could say "5=123" and afterwards whenever you used the literal 5, its value would be 123.
Great videos brother. Thanks for your content king!
Dart's compiler messages are even more helpful and amazing.
The best Rust tutorial by far.
I am in the third lesson and I LOVE IT🔥🔥🔥🔥....Thanks Tim
This is amazingly well explained. Thank you.
I do like that Rust is immutable by default. However, coming from a language like Swift or Kotlin, I do find the distinction between const and let quite strange. In Swift and Kotlin you declare a variable with the var keyword, but the convention is to use constants by default, let in Swift and val in Kotlin, which both have type inference.
The difference is that a "const" is a compile time expression while let defines a variable. An immutable variable can only be set once but it can be set to any run time expression, which may depend on other variables or an return values of a function call.
Feeling that Rust is the future and considering that C++ is my weak point, I believe Rust could be a solution to improve my skills.
loved the cat at end of tutorial 2🤣🤣
the scope system is a lot like python, so I quickly understood it's workings
And in C/C++ where it's referred to as a "compound" or "compound statement".
Name shadowing seem like a really useful thing thankyou sensie
tq soooo much tim, was waiting for this from 3 days.
Nice and clear explanations - easy to follow
regarding the variable re-declaration changing data types; would it be accurate to think of it like using &variable in c++? where instead of changing the datatype we're changing whats in that memory location? and the rust variable being more like a pointer than an actual variable?
10:06 I guess a better way to show what is actually happening would be to make the first x mutable and not recreate it before the last print, just adding 1 and print the references of x on both scopes every time succeeding the print of x's value. You would then be left with Identical refs for the first and last prints.
Thanks for your tutorials. This is really cool.
I highly recommend Windows Terminal (and Powershell :) )
Thanks, it's an excellent tutorial
It seems counterproductive to me to only enforce types on mutable variables. You're either going to encourage people to define everything as mutable, or you're going to allow people to undermine the static typing of the language by redefining variables. Either option seems bad to me.
Nope. It's fine
@@chaqua1559 Would you care to elaborate? I'm here to learn.
Remember guys if you do got to edit the data then clone is your best friend.
It sure seems that it be a helluva lot easier to work with if variables were mutable by default. Any practically logical reason why they are immutable by default besides scoping?
My thought too.
Why not just make them all mutable by default unless you declare them as a const?
Rust is interesting to me as a embedded developer. It would be cool to use it for embedded in my work but c and c++ are so engrained into the industry that I don’t they they will leave any time soon
You defined x to be an integer and printed it. Then a string and printed it. What would happen if you tried to reassign x on a 3rd attempt?
A variables reference types (pointers) and constants data types? Basically; variables stored in the heap and constants on the stack?
damn... warnings are cool
7:55 no way rust is this way much flexible
Thank you for sharing such useful knowledge.
Finally wait is over...🎉
I was so excited to see this video!
Cool !!
Tim, thanks
But also your closing cmd is irriating me. alt+tab back, up on keyboard to get the cargo command back, then execute.
Thanks for the series though!
That is a good tutorial
thank you
Are there global variables? If so are they global only to their file? Same questions of constants.
you are a blessing ❤
constant is not changeable in the entire scope - not entire program. It's allowed to redefine it in another scope. And you cannot use upper constant to calculate new constant in the lower scope.
Allowed is:
const VALUE_CONST: u32 = 20;
println!("The VALUE_CONST is {}", VALUE_CONST);
{
const VALUE_CONST: u32 = 10;
println!("The VALUE_CONST is {}", VALUE_CONST);
}
println!("The VALUE_CONST is {}", VALUE_CONST);
Not allowed is
const VALUE_CONST: u32 = 20;
println!("The VALUE_CONST is {}", VALUE_CONST);
{
const VALUE_CONST: u32 = VALUE_CONST + 10;
println!("The VALUE_CONST is {}", VALUE_CONST);
}
Thanks
What would be Rust used for by a beginner?
you're the man
@4:32 - 😎👍
apparently the mutable variables have been changed (either that or my install of rust is different for some weird reason) and rust prompted me to remove the mut so yeah...
edit: its because I had used let both times hah
So let in rust us the equivalent to the auto type in c++
Awesome!
dude so Rust is C but with compiler that babysit you ,?
Rust: the language where all variables all constants by default and redeclaration is allowed.
everytime i run cargo run it just makes a exe saying hello world instead of my actual code in src
very cool serie🤙
in println! what is the exclamation mark for?
I think that the thing is called "macros", basically it's like a function, but it has a few differences. He probably will talk about them in the future. If don't want to wait, I highly recommend you to check out "The Rust Programming Language" book, there is a section about this topic.
@@downfall6223 thank you
any suggested secondary language with Rust?
2:05 euh nope : it gonna EXplicitly assign a type to it, because u IMplicitly revealed it was an int by assigning the value 4 to it ;)
Coming from C++, it feels so wrong to "redeclare" a variable like that.
redeclaration with the same name being a pattern is the most evil thing ive ever seen
why += not working bruh
Why does rust create new problems from scratch as language features? Why can't we have nice programming languages? Why they all do try very hard to be quirky?
As someone that started with C many many years ago, all these new languages and styles and whatever, feels more as a hindrance than an actual tool to write better software.
A Variable, by name, is variable.
A compiler needs to compile the code, not telling me if I read or not a variable, especially if I am designing my algorithm.
Are const arrays frozen?
can anyone please explain what is u32?
It is just a declaration of int 32, we also have int 64 which is called u64 in rust but both basically are the same, but they differ in compiling speed and precission u64 is much more precise but is a lil bit slow I would say (not really sure check it out), whereas u32 is much more faster to process for cpu's, due to which it is commonly used in rust while declaring integer types.
Hope this helps!
You'll like rust analyser
Shadowing. Pretty much closure. This is borrowing from JS so much. Not a bad thing BTW.
so far, not really a fan of rust syntax of declaring variables
double declaration sounds like a bad design the intent would be more clear if you just can't declare again its not like you can declare x2 x3 x4
Cmon, be real. Every time you say 'If you are coming from another language', you are talking about JavaScript.
Hi Tim, I wanna be a data freelancer as soon as possible. So please make a vid about it.
Lmao. Go and research on your own. You're not serious enough
First
i dont think you need a :
My eyes hurt
Weird...my comment keeps getting deleted. Welp, cool vid anyway.
The background music is bad 😖, mute please 🤗.
Dude I just discovered that we have 'constant variables' in many programming languages... That doesn't make any sense. Or you may call it an oxymoron😎
This guy goes too fast
fn, Let, println!
: {}
Rust is all over the place, this is so bad
what's the differents between a unmutable variable and a const variable ?
wait is it just me or any1 else is also facing this issue ? rustfmt isn't formatting the code on sublime/ vscode (tried on both)