As a fellow game developer, I humbly suggest your tutorials to my team, especially the simplicity and real world samples are just on point. Keep up the good work and thank you for sharing👍
Except, this is really the exact opposite of what you were intended to get from the video. The lambda is not the loop. LINQ is running the loop based off of the condition from the lambda expression, to my understanding. Although, I'm nowhere near tarodevs level of knowledge, and I could just straight up be wrong lol.
There's also the thing about performance. Althought in many case LINQ is fasterish and less bug prone than manual foreach ( things like .Except() and especially parallel aggregation), most of the time LINQ will be slower, because of the overhead of delegate invocation. And not even speaking about for loop which is way faster then foreach. So if you actually need to care about performance for example rendering, real time data analysis, etc. it's good to be aware and benchamarking of test subset won't ever harm you.
And as an Olde Timey Programmer (kids... I did key-to-tape! I read EBCDIC, UNICODE, and ASCII! Y'all don't know the pain of dropping yer deck and doing a floor sort! Git off my iLawn before I sic my eDog on ya!): Always design and code for performance from day one if you ever expect to have high performing code. That being said, this is cool, and better yet, useful.
@@LuukDomhof In any case my previous comment was specifically targeting LINQ. Either way... I agree there are cases (even tho highly specific) where foreach is slightly more efficient than for loop. And even with Ben Watson's great article back in 2014 (.NET loop performance) there is no general rule. That's why I suggested that people should make their own tests and know what their code is doing.
While i agree that lambda's are awesome, what you're mostly focusing on here is LINQ, and NOT LAMBDA's (though you are using lambda's with linq, which isnt not really required). The select/where/orderby/etc are all LINQ functions. The "n => n>5" is the lambda part. Everything else is LINQ. Lambda's have FAAAAR more uses than just LINQ. And LINQ can be used without lambda's.
To be fair, I call the arrow function a lambda operator and make sure there's lambda in every example. I debated including the distinction between the two and decided against it. It's an inner battle deciding what to include and cull from each tutorial and there's usually more thought that goes into it than what most people think. For example, would it confuse people unnecessarily while they're trying to process a concept? Re-read your comment and tell me (although written well) it wouldn't be confusing for a brand new dev.
@@Tarodev As a fairly new dev, watching your video, I understood the lambda to be the method chaining, and the lambda expression within the parenthesis was also called lambda. This led to alot of confusion when I found out that wasn't the case. IE "why does his lambda look nothing like mine?" in reference to the LINQ aspect. Rather than "Lambda (+LINQ)" it really just feels like "LINQ (+Lambda)" That being said, this video was very helpful, and did lead me into a grasp on Lambda expressions and statements, so the video itself wasn't bad at all, I would just say to re write the title, so it isn't as misleading.
THANK YOU SO MUCH. I've been looking everywhere for a tutorial which really deconstructed lambda expressions, but couldn't find one anywhere. You are a lifesaver.
You break things down and explain it really well. Also your voice is clear, calm and not rushed. And no stupid drawn-out intros. Thanks for posting - will watch more of your tutorials.
I was intimidated by LINQ this whole time, but you demystified it for me. Thanks. You're my favorite Unity C# channel. I'm following along in LINQpad so I can tinker with no Unity overhead.
there is a downside to using LINQ lambdas instead of for each and that is you can't step through the code that is being iterated upon, so while it may be simpler to write, you are actually making the code much harder to debug. This is fine if the code is simple and will not throw any exceptions but as soon as the code becomes complex and is likely to throw exceptions while iterating through the list then you'll have a really hard time debugging it.. An example of this is using LINQ to initialize a list of objects from a set of records that come from a database. Lets say there is a conversion error when attempting to convert one of the values from the DB into the datatype of the object property you are trying to set. Using LINQ you have no easy way of knowing which item in the list failed. So yeah lambas are great until there is a problem that can only be debugged by stepping through code.
You're right. Writing actual loops also gives you more granular control, thus if done right, better performance. This is negligible for 99% of cases, but it should be known. Regarding your point, it helps having tooling which can convert lambdas into loops and back, such as the power hungry resharper. Side note: Sometimes I convert some nested loops into lambda using resharper and the resulting lambda gives me a brain haemorrhage.
Which editor are you using? With full Visual Studio (not sure about VS Code) you can debug lambdas and place breakpoint inside lambdas (important, the cursor must be inside the lambda before you add the breakpoint, otherwise it will be added at the wrong position) then you step through the code and debug it like a normal loop iteration, where you would place the breakpoint inside the loop code.
This stuff was so much fun to play with. Proceeded to write the dumbest code to make a string basically nonsensical and I couldn't be more proud of my work.
I have struggled with lambdas A LOT (I think mainly because most examples of it that I had seen were so abstract and high level), but this has been probably the best explanation of them yet. Thanks!
I have never understood lambda functions before and you just made it so easy. Thank you so much for this video, even if I do feel a bit sick at all the time I wasted writing loops that I didn't have to write.
Great video! Really glad to see tutorials that cover more advanced topics for beginners. I do find this tutorial covers a lot of System.Linq, which might cause beginners to mix that up with lambda expressions. Lambda expressions is simply a short hand to create an anonymous function. I think it might be beneficial to cover the following: - Differences between anonymous functions and Linq/Extension methods. - Other usage of anonymous functions (i.e. assigning a function to a variable/parameters, callback using System.Action)
Your videos are AWESOME! You are very didactic, patient and interesting, thank you so much! I've been trying to learn pure C# but whenever I ask questions to a "friend" of mine, he mocks me, says I should have known that already, that my code looks like shit.... You, on the other side, make the learning process productive and healthy. Thank you so much!
Those have a C# background before moving to Unity like me are already using it extensively. During the course I have read on some blogs and Q&A forums that Unity might have performance difficulty while processing these expression. Some even said Foreach loops are bad. But so far I haven't observed any issues. Go for it, you can reduce your code by 30% and less time on maintenance.
That burn on cyber punk though. God damn! Very informative. I know how to use lamda but not really why it worked that way. Even picked up some new uses. Thank you for a great video!
Linq makes code clear and concise, but can sometimes be less performant than a standard for loop. But understand this can be the difference between it running 100,000 times a second instead of 105,000 times... so don't worry about performance until you have to because 99% of the time it will be fine.
@@ewwitsantonio As a general rule, don't run LINQ in the game loop (Update method) for big collections/complex queries. But for initialization code (Start, Awake...) or code that does not run each frame, it's totally fine.
Been using linq for a while now. Love the lazy processing and REAL composition, not just employing a tool for composition, which is what the ':' really is for c#. there are more rules you have to follow for real composition, but it gives you so much. Which is one of the fundamental reasons why linq is AMAZEBALLZ. I would not be surprised in the least if the first intelligent aliens we meet have something startlingly like linq on the IL level. It is kind of close to a pure logical expression of the act of parsing related data. Maybe we should be pumping low level linq code into space, prove that there's at least some intelligent life stuck to this rock.
Awesome! Thanks for your content! Not sure if someone already mentioned this before, but as soon as you use foreach in a lazy IEnumerable it will force the query execution. Not sure if that was the intention in your AddRatingToNames method. If you want to stay lazy you could do this instead of using the foreach: return games.Select(g => { g.Name = ...; return g; });
Really nice tutorial. The only thing I disliked is that you used var so often. To understand the connections a little better the specific datatypes would have been better for me.
Dude you really have a special gift in teaching complicated topics... There's really no better way of breaking down this topic... Thanks for your good work!
Hey, what if I wanted it to be based on luckPercentage? I have a dictionary of items, each item has a float luckPercentage Item 1 = 10.0 Item 2 = 40.0 Item 3 = 50.0 So if I would want to take 1 item, item 2 and 3 would be the most often picked, and item 1 would be very rare. How can I achieve something like this?
What am I missing??? When I do the same code you do I get an error. CS0246 C# The type or namespace name 'Game' could not be found (are you missing a using directive or an assembly reference?)
can i change the value of the list using lambda ? like find the game named factorio, set its steam score to 9, using lambda, without creating a new list.
Question: If there is a list of items separated by two categories (owned and not owned by the player), should I use forloop or lambda? My thought is, if I use lambda, I'll have to do it t twice, thus I presume it loops through the collection twice, whereas running the loop just goes through once to separate the list. Your thoughts?
I'm curious what is the lambda I know it's I Greek letter λ but what is the lambda you talking on the video ? So basically lambda is the (>=) faction? If that the lambda faction it's something I use all the time with out even knowing the name of it
As a unity game dev, I almost never use linq for my mobile games, it too expensive for low setting devices. I think you should choose a few more examples for using lambda without linq.
My only wish is that this video was 35 minutes long with 20+ examples instead. So great!!
Thanks a ton!!
Yeah he and I have talked about the speed of the videos too. I'm not a beginner to C#, but I'm not a pro yet either.
search "101 linq examples" in google
That Cyberpunk joke cracked me xD
This is extremly helpful. I've known a bit about lambda functions before but making one actually blew my head off.
They truly are amazing. I rarely find myself writing loops nowadays... In both game dev and my professional day job.
As a fellow game developer, I humbly suggest your tutorials to my team, especially the simplicity and real world samples are just on point. Keep up the good work and thank you for sharing👍
That comment made my night mate. Thank you!
They'll sit down to the intro of the video and think what the hell is this
This tutorial was perfect, I really like how you compared lambdas to a more simplistic loop. It helped it click in my head
I was hoping it would serve that purpose! 😊
i agree
Except, this is really the exact opposite of what you were intended to get from the video. The lambda is not the loop. LINQ is running the loop based off of the condition from the lambda expression, to my understanding. Although, I'm nowhere near tarodevs level of knowledge, and I could just straight up be wrong lol.
@@CyCloNeReactorCore You're right mate
There's also the thing about performance. Althought in many case LINQ is fasterish and less bug prone than manual foreach ( things like .Except() and especially parallel aggregation), most of the time LINQ will be slower, because of the overhead of delegate invocation. And not even speaking about for loop which is way faster then foreach.
So if you actually need to care about performance for example rendering, real time data analysis, etc. it's good to be aware and benchamarking of test subset won't ever harm you.
And as an Olde Timey Programmer (kids... I did key-to-tape! I read EBCDIC, UNICODE, and ASCII! Y'all don't know the pain of dropping yer deck and doing a floor sort! Git off my iLawn before I sic my eDog on ya!):
Always design and code for performance from day one if you ever expect to have high performing code.
That being said, this is cool, and better yet, useful.
There are MANY cases where a foreach loop is faster than a for loop. Check some benchmarks ;)
@@LuukDomhof In any case my previous comment was specifically targeting LINQ.
Either way... I agree there are cases (even tho highly specific) where foreach is slightly more efficient than for loop. And even with Ben Watson's great article back in 2014 (.NET loop performance) there is no general rule. That's why I suggested that people should make their own tests and know what their code is doing.
While i agree that lambda's are awesome, what you're mostly focusing on here is LINQ, and NOT LAMBDA's (though you are using lambda's with linq, which isnt not really required). The select/where/orderby/etc are all LINQ functions. The "n => n>5" is the lambda part. Everything else is LINQ. Lambda's have FAAAAR more uses than just LINQ. And LINQ can be used without lambda's.
To be fair, I call the arrow function a lambda operator and make sure there's lambda in every example. I debated including the distinction between the two and decided against it. It's an inner battle deciding what to include and cull from each tutorial and there's usually more thought that goes into it than what most people think.
For example, would it confuse people unnecessarily while they're trying to process a concept? Re-read your comment and tell me (although written well) it wouldn't be confusing for a brand new dev.
@@Tarodev As a fairly new dev, watching your video, I understood the lambda to be the method chaining, and the lambda expression within the parenthesis was also called lambda. This led to alot of confusion when I found out that wasn't the case. IE "why does his lambda look nothing like mine?" in reference to the LINQ aspect. Rather than "Lambda (+LINQ)" it really just feels like "LINQ (+Lambda)"
That being said, this video was very helpful, and did lead me into a grasp on Lambda expressions and statements, so the video itself wasn't bad at all, I would just say to re write the title, so it isn't as misleading.
@@CyCloNeReactorCore Yup, rewatching it I did a poor job of distinguishing them (or even mentioning it >
@@Tarodev It's okay!! Not every video can address every single facet of the subject. You helped me understand lambdas more so thank you.
@@Tarodev "If I Had More Time, I Would Have Written a Shorter Letter" - Blaise Pascal
You could honestly teach teachers how to teach. You're that good.
THANK YOU SO MUCH. I've been looking everywhere for a tutorial which really deconstructed lambda expressions, but couldn't find one anywhere. You are a lifesaver.
You break things down and explain it really well. Also your voice is clear, calm and not rushed. And no stupid drawn-out intros. Thanks for posting - will watch more of your tutorials.
Hey man, i have to say it, your explanation was crystal clear. It was as relaxing (no noisy music and what's up boyz) as it was helpful. Thank you.
This was the first thing I read after waking up. Thanks mate, glad you enjoyed it.
Although it still has a pretty stupid intro 😜
I was intimidated by LINQ this whole time, but you demystified it for me. Thanks. You're my favorite Unity C# channel. I'm following along in LINQpad so I can tinker with no Unity overhead.
LINQpad is such an excellent way to learn. You're on a great track!
the best tutorial i've ever seen
God damn, this man just straight up explained the shit I've been wanting to understand for months so clearly and effortlessly.
@@PapaBigDoinks now use this knowledge and create!
there is a downside to using LINQ lambdas instead of for each and that is you can't step through the code that is being iterated upon, so while it may be simpler to write, you are actually making the code much harder to debug.
This is fine if the code is simple and will not throw any exceptions but as soon as the code becomes complex and is likely to throw exceptions while iterating through the list then you'll have a really hard time debugging it..
An example of this is using LINQ to initialize a list of objects from a set of records that come from a database.
Lets say there is a conversion error when attempting to convert one of the values from the DB into the datatype of the object property you are trying to set. Using LINQ you have no easy way of knowing which item in the list failed.
So yeah lambas are great until there is a problem that can only be debugged by stepping through code.
You're right. Writing actual loops also gives you more granular control, thus if done right, better performance. This is negligible for 99% of cases, but it should be known.
Regarding your point, it helps having tooling which can convert lambdas into loops and back, such as the power hungry resharper. Side note: Sometimes I convert some nested loops into lambda using resharper and the resulting lambda gives me a brain haemorrhage.
Which editor are you using? With full Visual Studio (not sure about VS Code) you can debug lambdas and place breakpoint inside lambdas (important, the cursor must be inside the lambda before you add the breakpoint, otherwise it will be added at the wrong position) then you step through the code and debug it like a normal loop iteration, where you would place the breakpoint inside the loop code.
@@r1pfake521 I actually did not know this. Thanks for the tip!
Love the threatening aura intro then complete coddling immediately after 🤣 needs to be in more vids
K & d in the wild
K & d in the wild
This stuff was so much fun to play with. Proceeded to write the dumbest code to make a string basically nonsensical and I couldn't be more proud of my work.
I'm also proud of you
@@Tarodev Thanks, papa!
I have struggled with lambdas A LOT (I think mainly because most examples of it that I had seen were so abstract and high level), but this has been probably the best explanation of them yet.
Thanks!
The world of lambda expressions seemed so harsh and difficult, until I saw your video. Thanks for the simplicity 🙏
This actually was so simple but helped so much, I hope you can do a “C# tutorial series” or something along that line! Keep up the good work man
I have never understood lambda functions before and you just made it so easy. Thank you so much for this video, even if I do feel a bit sick at all the time I wasted writing loops that I didn't have to write.
Just don't use them in update 😊
TH-cam has been recommending this video for literally half a week. I should have watched this sooner lol. Great video!
Sometimes they know, lol
Man this was great just explained two advanced topics in 6 mins
"Cyberpunk destroyed our condition, just like it destroyed our dreams" - Tarodev
Great video! Really glad to see tutorials that cover more advanced topics for beginners.
I do find this tutorial covers a lot of System.Linq, which might cause beginners to mix that up with lambda expressions. Lambda expressions is simply a short hand to create an anonymous function. I think it might be beneficial to cover the following:
- Differences between anonymous functions and Linq/Extension methods.
- Other usage of anonymous functions (i.e. assigning a function to a variable/parameters, callback using System.Action)
Exactly! This is what happened to me for a brief while when i first watched this video.. Great video though!
Just to add to all comments above, your typing speed is outstanding😳
love your sense of humor
I love you
😳
I don't think that Cyberpunk reference will ever get old, even if Unity updates their code 10 years from now :D
the intro has this vibe i cannot explain....
I like this video because you encourage people to look into other options. :) Keep up the good work!
I'm in love with c# wow
Wow, C# is really great, thanks for these infos
Jacked and C# instructor? I am among my peeps!
Thank you for your precious help!!
Your videos are AWESOME! You are very didactic, patient and interesting, thank you so much!
I've been trying to learn pure C# but whenever I ask questions to a "friend" of mine, he mocks me, says I should have known that already, that my code looks like shit.... You, on the other side, make the learning process productive and healthy. Thank you so much!
You should probably get a new friend
He is abuser. You should define your borders in your relationship and tell him what you like and what not. Just talk with him about your feelings.
@@torrvic1156 actually, I don't speak with him anymore. I blocked him and don't answer him, I don't even have contact. Never been happier!
I enjoy your videos. Though I've been using and making lambda functions for some time, seeing them this way taught me something new.
Those have a C# background before moving to Unity like me are already using it extensively. During the course I have read on some blogs and Q&A forums that Unity might have performance difficulty while processing these expression. Some even said Foreach loops are bad. But so far I haven't observed any issues. Go for it, you can reduce your code by 30% and less time on maintenance.
The cyberpunk joke won me over. Good job.
You sir, are a legend. Thank you for this.
Unexpected bonus for Extension methods at 05:39 !
Use it wisely :)
You are a great Teacher. Thank you
Love the golden ratio used in the list example
That burn on cyber punk though. God damn!
Very informative. I know how to use lamda but not really why it worked that way. Even picked up some new uses. Thank you for a great video!
I just feel calm looking at these tutorials and even on the way I'm getting smarter and developing my code knowledge
oh boy 2:40 hit way to hard. great vid
God damn that was clear and succinct, just how we like it in attention deficit 2024
heh :D
This is more like a System.Linq tutorial than general lambda expressions. But anyways this is still good content.
Man, you never disappoint, thanks!
very clear and easy to understand!!
Wonderful! So easy to understand!
make more of these you're an exam saviour....
Nice video! Can you share your thoughts on using LINQ in Unity? Anything we should keep in mind?
Linq makes code clear and concise, but can sometimes be less performant than a standard for loop. But understand this can be the difference between it running 100,000 times a second instead of 105,000 times... so don't worry about performance until you have to because 99% of the time it will be fine.
@@Tarodev Thanks for the thoughts! Appreciate it
@@ewwitsantonio As a general rule, don't run LINQ in the game loop (Update method) for big collections/complex queries. But for initialization code (Start, Awake...) or code that does not run each frame, it's totally fine.
Been using linq for a while now. Love the lazy processing and REAL composition, not just employing a tool for composition, which is what the ':' really is for c#. there are more rules you have to follow for real composition, but it gives you so much. Which is one of the fundamental reasons why linq is AMAZEBALLZ.
I would not be surprised in the least if the first intelligent aliens we meet have something startlingly like linq on the IL level. It is kind of close to a pure logical expression of the act of parsing related data. Maybe we should be pumping low level linq code into space, prove that there's at least some intelligent life stuck to this rock.
Thank you very much. It's really helped me!!
That was rad dude!
Awesome! Thanks for your content!
Not sure if someone already mentioned this before, but as soon as you use foreach in a lazy IEnumerable it will force the query execution. Not sure if that was the intention in your AddRatingToNames method.
If you want to stay lazy you could do this instead of using the foreach:
return games.Select(g =>
{
g.Name = ...;
return g;
});
More examples, nothing else!
👏👏👏Excellent explanation. Clear and to the point.
Great Tutorial Thanks m8
underrated!
Great video. Always good to refresh your knowledge or learn new stuff
Great explanation
best unity tutorial!
Gracias Mister Tarodev que poder de las expresiones Lambda.....saludos de los andes peruanos
Thank you very much ! Very useful video !
OMG I FINALLY GET IT. THANK YOU. lol
This was really helpful, great tutorial!
Thanks mate 🙏
Just purely amazing!!
It's all fine and dandy, but hard to debug, which is why we don't use these as often. But maybe you have some debug tips?
thanks fam! great video!
2:40 yup, that's a like and sub right there
This is amazing, thank you so much!!
If only this video would last for an hour showing examples. Amazing stuff
Whoa. Solid video
Thing I didn't know I needed to know
Really nice tutorial. The only thing I disliked is that you used var so often. To understand the connections a little better the specific datatypes would have been better for me.
Nice tutorial, and bonus points for including Valheim in the list of Steam games (one of my all time favorites). 😀
Big Like ( within start of a min ) watching this video
bro is teaching and doing asmr at the same time
😉
Dude you really have a special gift in teaching complicated topics... There's really no better way of breaking down this topic... Thanks for your good work!
Thanks very much for this, subscribed long ago 🎉
I feel for you bro. I know that mood.
Hey, what if I wanted it to be based on luckPercentage? I have a dictionary of items, each item has a float luckPercentage
Item 1 = 10.0
Item 2 = 40.0
Item 3 = 50.0
So if I would want to take 1 item, item 2 and 3 would be the most often picked, and item 1 would be very rare. How can I achieve something like this?
I don't get
.OrderBy(g=>_random.Next())
_random.Next() will return a random int value. How does that shuffle the elements?
How does it work?
We are looping the list, assigning a transient random value to each element and then ordering them by that random.
damn, this is called lamda? so I did it on accident every time. Learned this on tutorials and didn't knew the other way thx for this :D
how should i do for running system.linq.dynamic.core properly in Unity. It gives an error
very good thank you my friend
What am I missing??? When I do the same code you do I get an error. CS0246 C# The type or namespace name 'Game' could not be found (are you missing a using directive or an assembly reference?)
that was a great intro
can i change the value of the list using lambda ? like find the game named factorio, set its steam score to 9, using lambda, without creating a new list.
Good video
"just like it destroyed our hopes and dreams..." - genius.
Awesome!
They look nice, but are they faster than for loop?
99% of the time, no. But until you see a performance problem, use the cleanest solution.
Yea definitly prematue optimization is the root to the all evil. xD
Question: If there is a list of items separated by two categories (owned and not owned by the player), should I use forloop or lambda?
My thought is, if I use lambda, I'll have to do it t twice, thus I presume it loops through the collection twice, whereas running the loop just goes through once to separate the list.
Your thoughts?
Damn good bro
you can use predicates lamda? right.
I'm curious what is the lambda I know it's I Greek letter λ but what is the lambda you talking on the video ?
So basically lambda is the (>=) faction?
If that the lambda faction it's something I use all the time with out even knowing the name of it
Subbed.. lovely
As a unity game dev, I almost never use linq for my mobile games, it too expensive for low setting devices. I think you should choose a few more examples for using lambda without linq.
I not only use lambda's I use them all of the time with Joins and GroupJoins good times
Should have included a inner join and outer join IMO but venn diagrams in code might break your audience.