C# LAMBDA Expressions and ANONYMOUS Functions Tutorial | 2021

แชร์
ฝัง
  • เผยแพร่เมื่อ 5 ก.ย. 2024

ความคิดเห็น • 16

  • @tutorialsEU
    @tutorialsEU  3 ปีที่แล้ว +1

    🚀Master C# and .NET programming EASILY with our best-selling C# Masterclass: bit.ly/47Hk3u7

  • @colins2
    @colins2 3 ปีที่แล้ว +7

    Probably the clearest explanation of Lamdas that I have seen.

  • @justynak.6686
    @justynak.6686 2 ปีที่แล้ว +5

    I don't know if it's because it's directed for beginners, you're probably already aware that
    at 12:07 you don't need to write the if else statement at all, just put return keyword before the condition written in the if. Less typing :)

  • @psychoclips6817
    @psychoclips6817 ปีที่แล้ว

    This was an awesome explanation. You kept it clear and simple. Plus you showed exactly how the functions were being used so nothing was left to be guessed.

  • @Syed.KhubaibAli
    @Syed.KhubaibAli 5 หลายเดือนก่อน

    Thankyou for such a nice explanation

  • @TheManChise
    @TheManChise ปีที่แล้ว

    Very nice explanation of lambdas..

  • @leluconygmemuakan1437
    @leluconygmemuakan1437 ปีที่แล้ว

    Thank very much buddy

  • @shaurya007
    @shaurya007 3 ปีที่แล้ว +2

    Could you please do some more tutorials on basics of Kotlin in Android Studio

    • @tutorialsEU
      @tutorialsEU  3 ปีที่แล้ว +1

      I will update the android 10 course to android 12 and there will be a bunch of kotlin basics coming

    • @shaurya007
      @shaurya007 3 ปีที่แล้ว

      @@tutorialsEU Thank You very much 🥰🥰

  • @ronen124
    @ronen124 3 ปีที่แล้ว +1

    good
    (anonymous)

  • @ghosthunter9897
    @ghosthunter9897 ปีที่แล้ว

    Hey man how can I call function inside lamda expression?

  • @Jel.Awesh.M
    @Jel.Awesh.M 2 ปีที่แล้ว

    In other words, a delegate is contract for methods as an interface is a classes, isn't it?

    • @user-pf9jv1fl2n
      @user-pf9jv1fl2n 2 ปีที่แล้ว +2

      A delegate points to a particular method signatures. And can point to multiple method signatures. A interface is a essentially like a contract that you are essentially agreeing to. For example. A classic example would be Innumerable it's a interface and anything that inherits from it will be forced to also include whatever properties the interface has. Since when you inherit from a interface you are agreeing that you will provide every property method etc from the interface. That being said. You're probably wondering why is this even useful. Imagine you want to loop through a bunch of different objects that are somewhat similar. How can you gurantee to the that function that these similar classes will even have the same property. You would do that with a interface because any class thay inherits from a interface will by contract be forced to implement everything that the interface has or more. And since you know now all the inherited objects that inherit from the particular interface have implemented the fields. You can do something like this void loop(Innumerable en)
      And anything that inherits Innumerable you can access similar information since they would have implemented similar data. This is the case for collections so lists arrays etc. This is why we are able to use foreach loop on collections because all the collections inherit the interface Innumerable which one of its properties is the getenumberator method. Hope this helped.

    • @ArnasBies
      @ArnasBies 2 ปีที่แล้ว

      @@user-pf9jv1fl2n Thanks it helped a lot
      (btw your probably meant IEnumerable not Innumerable)