Love you Mike . You're so awesome! I love your channel and super helpful and informative to me while doing coding challenges to prepare for interview questions. ❤
I followed the custom class example, somehow my compiler asked me to add #include for use `std::for_each` but seems it's not the case of Mike's example. Not knowing what's the difference. Thanks for the great content!
#include is the right thing to do, some compilers may add some standard libraries in implicitly, but always better in my opinion to be explicit and put in the #include 🙂
Mike... when we have a comparator in the form of a functor ( struct compare in the video), shouldn't we pass instance of the struct compare, rather than compare itself? for ex: std::multi_set or std::multi_set etc where comp1 is the instance of struct compare.
Love you Mike . You're so awesome! I love your channel and super helpful and informative to me while doing coding challenges to prepare for interview questions. ❤
Cheers, thank you for the kind words! Good luck on your interview
All the best bro
Cheers!
Wow! Awesome Content!
Cheers!
I followed the custom class example, somehow my compiler asked me to add #include for use `std::for_each` but seems it's not the case of Mike's example. Not knowing what's the difference. Thanks for the great content!
#include is the right thing to do, some compilers may add some standard libraries in implicitly, but always better in my opinion to be explicit and put in the #include 🙂
Hi mike,
Mike... when we have a comparator in the form of a functor ( struct compare in the video), shouldn't we pass instance of the struct compare, rather than compare itself? for ex: std::multi_set or std::multi_set etc where comp1 is the instance of struct compare.
Can you provide a timestamp? I suppose the concern is we want to use the instance in the case of polymorphism?
@@MikeShah it's at timestamp 12.10 min, where you mention std::multiset multi. Shouldn't it be declared as std::multiset multi?
Please can you do more videos on wxWidgets, specifically using the WXAUI