Thanks a ton Keerti! Such an awesome video including the multithreading handling part which was unexpected, and while learning I enjoyed it throughly. Paused the video in between to like it because this video and this design pattern series deserves it. Looking forward for next videos in the series :D
Thanks a lot, Keerti. I am fresher and was super scared when I first check what it is online, but you made it super simple that even a fresher who barely knows these concepts in detail can understand it. Super happy learning this in such a simple way.
Hey Keerti, This was really great explanation. Most videos would stop showing the implementation about singleton design pattern. But the fact that you showed how to make them thread safe was a cherry on top. One request though, could you increase the font size or zoom in into your code editor in upcoming videos as it becomes difficult when viewing on phone.
To restrict access to the operator=, you can declare it as private in the class definition, as you've already done. However, you should also provide an empty definition for it to make it inaccessible and avoid compilation errors. Here's how you can do it: cpp code private: Logger& operator=(const Logger&) = delete; Adding = delete explicitly specifies that the copy assignment operator is deleted and cannot be used. This way, any attempt to use the copy assignment operator will result in a compilation error
I use to always skip the design pattern concepts..but with your videos...its so easy to understand...i look forward to other videos... great work thanks for sharing the knowledge wirh us...😍
Thanks a lot Keerti. This is the most complete video I have seen so far. I like the way you explain "WHY" we need to do it. Really appreciate your work.
Once we have checked that loggerInstance==nullptr, why is there a need to check it again, can't we just apply the lock and create a new loggerInstance as we know that it is null?
No, that would miss the case when both the threads have gone passed by the first if-condition, they both will eventually access the constructor, though one after the other. That's why the second if-condition is a must too
Keerti awesome work on the video. I do have a suggestion though. It would be great to if you have have those multiple files in the split window so that it is easily to reference and connect while watching the video itself. This is one way to do it, but the idea is to have visibility or maybe use lesser files. I totally understand that this way it is much more modular but I think for watching everything on a single screen helps better.
Thanks Keerti, Such a great video including each smaller things in it. One request if you can give one session on only mutex and semaphore will help us a lot. Thank you so much again for this wonderful session.
Thanks Keerti for such crisp & nice video capturing all the necessary points related to singleton design pattern. Really appreciate for posting such videos which helps the entire developer community.
Thanks for such a simple explanation!! I have one Q. Should I also delete "move constructor" & "move assignment operator" in singleton class? If YES or No, explanation would be very helpful.
Thank you ma'am. I have a question. If you null pointer check for loggerInstance on Ln. 21 then do you really think null check required on Ln.24 as well
Awesome explanation! but I think you missed to explain why we should go for singleton pattern? I think you mentioned in order to avoid multiple logs in different places? I didn't get that?
Thank you very much Di, got this from end to end like thread safe and all.... One doubt why we use .hpp and .cpp files both..... we can't do in .cpp file only, its little bit confusing to me, i haven't code like this in cpp And please add more videos.... this Playlist is going to be best on RUclips for LLD and system design 💯💯
Thanks Keerthi! Your explanation was very excellent.But I had a doubt.Instead of using header files can't we write all the code in a single file?.Will there be any issues in doing so? Because not everyone can create those header files that easily.I am a fresher basically So I wanted to know if this is the actual convention to be followed or if it is also fine to code everything in a single file.
wonderfull explantion keerti, one doubt -> as explained to use mutex, can we follow this approach -> run 1st thread and after that remaining threads -> anyways we are just blocking 2 threads to make instances for the first time and after the instance is created it would not matter how many threads access it
Yar jo wo problem tha like k if Multithreading is in picture then singleton fails or tabhi muje realise hua uska bhi jugad hota hai par ye interview me pucha tha or sch me tabhi realise hua k hmm such a diff pov
Hi Keerthi, thanks a million for the wonderful videos. I have one question in implementation of singleton design pattern. "Why do we need to make assignment operator in private. Assignment operator gets called when we try to assign existing object to another already existing object. In other words this gets called only when we have two instances already created which we already prevented from happening by making default and copy constructors private.
Hello Keerti, Thanks for the video, but this is still not complete. Particularly the ownership of the instance, how the instance will be released/destroyed. You can use smart pointer (since C++11) But the best would be using Meyer's Singleton that works with C++98 and C++O3 as well
Why have you made 3 files ? logger.hpp , logger.cpp and user.cpp . why cant we directly used logger.hpp in user.cpp ? is there some pattern , folder structuring you have followed ?
What if exception is thrown Inside a mutex lock ? It will never ever unlock the mutex and no other thread will be able to enter the critical section or they will keep waiting to mutex to get unlocked that will never happened. So we should use unique_lock or lock_guard i guess 😒😒
Hey Keerti, I tried this on gcc linux terminal. without mutex also it gave single instance all the time. spent 15 minutes to figure out what wrong I wrote. but then tried it on online gdb compiler; there it varied then.
If you are writing singleton in C++... Meyers singleton is the standard way of doing this. I guess covering meyers singleton was super important not done.... BTW singletons are anti pattern avoid it
When we delete the instance and created new instance 2nd time in main we are unable to delete the instance which we created 2nd time getting double free error
Can we delete the second time nullptr checking as we are already checking it for mtx locking, or that can also cause some problem? just curious, please do reply..
I have 3 things to say.... 1. How is your armpit...seems like due to pole dance you had some issue. 2. Nice explaination 3. How is work at intuit one of my friend joined there and tell me he work day and night and even weekends too.
Dsa is useful for sure (language doesn’t matter that much - as long as you can solve questions) But I do know some front end developers who are doing really well and don’t know dsa much.
![Tee Grizzley - Robbery 8 [Official Video]](http://i.ytimg.com/vi/34_vkNV6wrU/mqdefault.jpg)
Thanks a ton Keerti! Such an awesome video including the multithreading handling part which was unexpected, and while learning I enjoyed it throughly. Paused the video in between to like it because this video and this design pattern series deserves it. Looking forward for next videos in the series :D
Thank you so much. Sorry for releasing the rest of the series late but finishing it soon ❤️😇
Thanks a lot, Keerti. I am fresher and was super scared when I first check what it is online, but you made it super simple that even a fresher who barely knows these concepts in detail can understand it. Super happy learning this in such a simple way.
Hey Keerti, This was really great explanation. Most videos would stop showing the implementation about singleton design pattern. But the fact that you showed how to make them thread safe was a cherry on top. One request though, could you increase the font size or zoom in into your code editor in upcoming videos as it becomes difficult when viewing on phone.
Thanks Pratik. Will definitely increase more from next time😇
Feedback like yours helps me improve in every video❤️😇
To restrict access to the operator=, you can declare it as private in the class definition, as you've already done. However, you should also provide an empty definition for it to make it inaccessible and avoid compilation errors. Here's how you can do it:
cpp code
private:
Logger& operator=(const Logger&) = delete;
Adding = delete explicitly specifies that the copy assignment operator is deleted and cannot be used. This way, any attempt to use the copy assignment operator will result in a compilation error
Thanks for the video Keerti. Simple and detailed. Good work!!
I use to always skip the design pattern concepts..but with your videos...its so easy to understand...i look forward to other videos... great work thanks for sharing the knowledge wirh us...😍
Wonderful explanation Keerti, It is hard to find Oops tutorial in C++ and you have handled it easily. Thanks a lot again.
Thank you so much! Means a lot! Please do share with your friends! ❤️
Lovely explanation of double checking before locking for thread-safe single ton logging🔥
Thanks a lot Keerti. This is the most complete video I have seen so far. I like the way you explain "WHY" we need to do it. Really appreciate your work.
Thank you so much! Means a lot! Hoping you like rest of the videos as well! ❤️😇
Once we have checked that loggerInstance==nullptr, why is there a need to check it again, can't we just apply the lock and create a new loggerInstance as we know that it is null?
Baat me dum hai
No, that would miss the case when both the threads have gone passed by the first if-condition, they both will eventually access the constructor, though one after the other. That's why the second if-condition is a must too
Keerti awesome work on the video. I do have a suggestion though. It would be great to if you have have those multiple files in the split window so that it is easily to reference and connect while watching the video itself. This is one way to do it, but the idea is to have visibility or maybe use lesser files. I totally understand that this way it is much more modular but I think for watching everything on a single screen helps better.
बहोत अच्छेसे और गहराईसे समझाया.
फाॅंट का आकार बडा होता पढने मे आसानी होती.
नलपीटिआर् दो बार चेक हो गया है. जगह और वेग के संबंध मे.
Its best explanation about singleton.Thank You.
Thanks Keerti, Such a great video including each smaller things in it. One request if you can give one session on only mutex and semaphore will help us a lot. Thank you so much again for this wonderful session.
Will do for sure!
Thanks Keerti for such crisp & nice video capturing all the necessary points related to singleton design pattern.
Really appreciate for posting such videos which helps the entire developer community.
Thank you so much, means a lot! Hoping you will like the new videos as well! 😇
Fantastic video. I came here after hearing your interview experience. I learned MULTITHREADING just to understand this video.
Woah! How awesome is that! ❤️😇
@@KeertiPurswani Thank you Di
Clearly Visible, Thank You :)
It complied on first time, on staging code - Truly magical!
Thank you! A lot of effort goes behind every single video! ❤️
Thanks for such a simple explanation!!
I have one Q. Should I also delete "move constructor" & "move assignment operator" in singleton class?
If YES or No, explanation would be very helpful.
Thank you Keerti. Appreciate implementing in c++
Thank you! Please do subscribe and share the video with your friends❤️😇
Very clear explanation with examples. Thanks Kreeti
Mam, please complete the design pattern playlist as fast as possible.
Great video. Thanks for this. :D
One doubt: Isn't the inner if condition redundant as the lock is already captured?
Thanks Suraj. For explaining so well! ❤️😇
And "upper if" to just stop "locking" once you have created the instance.
In a main method, you can create a singleton class instance before creating a thread. There won't be any contention issue, locking is also not needed.
Hey, thanks for the awesome explanation. Why we need the 2 if check, cant we remove the inner if check?
Have the same question...
keerti please do a parallel code for java as well.
Thanks Keerti! Very good way of explanation. God bless you.
Thank you ma'am. I have a question. If you null pointer check for loggerInstance on Ln. 21 then do you really think null check required on Ln.24 as well
Thanks Keerthi, this was a very good explanation about singleton
Thanks for these videos. One thing which would help with visibility is if you can show all open code files side by side
But you won’t be able to see the code clearly on screen. I am going to upload all to github pretty soon!
Awesome explanation! but I think you missed to explain why we should go for singleton pattern? I think you mentioned in order to avoid multiple logs in different places? I didn't get that?
goldmine of a video
Please increase the font size when you write code or zoom in a bit. Difficult to read from distance. Thanks
Thank you very much Di, got this from end to end like thread safe and all....
One doubt why we use .hpp and .cpp files both..... we can't do in .cpp file only, its little bit confusing to me, i haven't code like this in cpp
And please add more videos.... this Playlist is going to be best on RUclips for LLD and system design 💯💯
Nicely explained. Understood it completely
Are freshers (university grads ) expected to face these questions ?
Great video btw !!!
Thanks a lot Kreerti! for the wonderful explantion of singleton design pattern.
Thank you! Hope you like other videos on the channel as well! 😇
Thank you Keerti! Really appreciate your work.
Hi sis, your explanation is very clean & good, if u can add more design patterns .It'll be a great help. Thanks.
Thanks Keerti. Very useful.
Thanks Keerthi! Your explanation was very excellent.But I had a doubt.Instead of using header files can't we write all the code in a single file?.Will there be any issues in doing so? Because not everyone can create those header files that easily.I am a fresher basically So I wanted to know if this is the actual convention to be followed or if it is also fine to code everything in a single file.
For Java People, to handle multithreading do below changes in Logger class -
public static Logger getLogger() {
if(logger == null) {
logger = getInstance();
}
return logger;
}
synchronized public static Logger getInstance(){
if(logger == null)
return new Logger();
else
return logger;
}
Thankyou so much, Keerti Mam
Finally back ☺️
With many many videos this time❤️😇
You made my day
wonderfull explantion keerti, one doubt -> as explained to use mutex, can we follow this approach
-> run 1st thread and after that remaining threads -> anyways we are just blocking 2 threads to make instances for the first time and after the instance is created it would not matter how many threads access it
Assuming if we write the code in java ..Can we create object during initialization like below
public class Singleton {
private static Singleton singleton=new Singleton();;
private Singleton()
{
super();
}
public static Singleton getSingleton()
{
return singleton;
}
}
You are a great teacher !! Thank You !!
Yar jo wo problem tha like k if Multithreading is in picture then singleton fails or tabhi muje realise hua uska bhi jugad hota hai par ye interview me pucha tha or sch me tabhi realise hua k hmm such a diff pov
Hey Keerti, Really a good video and detailed explanation. Hats off and please continue to contribute.
Thank you so much Ritika, means a lot! More videos coming up soon ❤️😇
Very good clear explanation. Expecting more videos on other design patterns.
AWESOME, Great work!
Thanks Keerthi.. Really great explanation 👏.
Hi Keerthi, thanks a million for the wonderful videos. I have one question in implementation of singleton design pattern.
"Why do we need to make assignment operator in private. Assignment operator gets called when we try to assign existing object to another already existing object. In other words this gets called only when we have two instances already created which we already prevented from happening by making default and copy constructors private.
Could you please let us know what is the IDE you are using for practice?
Isn't it better to use static class for logger rather than singleton pattern. Some of the useful example can be parking lot
Thanks Keerti for this video..learn singlton design pattern in detailed . can I get your codes on any website ??
Your effort to keep things simple is amazing...Also don't worry no one will steal your logger constructor.😂
Hehe thank you so much! ❤️❤️
wait wait what was that at the last? making constructor private and operator overloading private... as a non C++ coder that hit me like a train
One Request: Please give the direct link to the playlist of design patterns you are covering to check other patterns easily.
There’s a playlist on the channel - Design Patterns
ruclips.net/p/PLliXPok7ZonlZJuAN0hvUnf5ovFepjxU0
😇😇
Excellent explaination Keerti!
Thanks Keerti, can you please record the session on "Smart Pointer"
Hello Keerti,
Thanks for the video, but this is still not complete. Particularly the ownership of the instance, how the instance will be released/destroyed.
You can use smart pointer (since C++11)
But the best would be using Meyer's Singleton that works with C++98 and C++O3 as well
great stuff as always, waiting for next video on design pattern
You forgot to return as reference when you overloaded the assignment operator.
Hi Guys.. awesome videos
Superb explanation. ❤
Thank you! Hope you like other videos as well! 😇
nice video but could you make videos using java?
It is really a great session and helpful. Thanks for this. If possible pls increase the font size while explaining codes.
Thanks for the feedback! Hoping it’s better in the present videos! ❤️😇
nice explanation
Thank you for explaining in detail.can you please create GitHub links for the codes specially the design pattern ones
Nice explanation :)
One doubt: when are we going to delete the resource(loggerInstance) which we have created dynamically using new keyword.
wonderful explanation thank you so much for teaching us
Thank you! Please do share the video with your friends!
@@KeertiPurswani ofcourse I will this is great stuffs and people need to know about your amazing videos
Why have you made 3 files ? logger.hpp , logger.cpp and user.cpp . why cant we directly used logger.hpp in user.cpp ? is there some pattern , folder structuring you have followed ?
after you implement the double checked lock is the inner if condition needed any more? isnt it bound to be TRUE?
How about RUclips adding search option in comments section.
Thank you so much for this series :)
What if exception is thrown Inside a mutex lock ? It will never ever unlock the mutex and no other thread will be able to enter the critical section or they will keep waiting to mutex to get unlocked that will never happened. So we should use unique_lock or lock_guard i guess 😒😒
Hey Keerti, I tried this on gcc linux terminal. without mutex also it gave single instance all the time.
spent 15 minutes to figure out what wrong I wrote. but then tried it on online gdb compiler; there it varied then.
You can use semaphore ? Why mutex
Please make the code view bigger. It becomes difficult to read while watching on a phone
Excellent video ...simple explaination 👍
Thank you so much! Please do share with your friends?
Really great explanation!!!
Hi didi ,your videos are just awesome keep making videos like this and motivating us
Thank you! Please keep sharing videos and motivating me! ❤️
If you are writing singleton in C++... Meyers singleton is the standard way of doing this. I guess covering meyers singleton was super important not done.... BTW singletons are anti pattern avoid it
Great Teacher YOU are
Thank you! Means a lot❤️😇
When we delete the instance and created new instance 2nd time in main we are unable to delete the instance which we created 2nd time getting double free error
Can we delete the second time nullptr checking as we are already checking it for mtx locking, or that can also cause some problem? just curious, please do reply..
excellent!!, can someone please tell me if this playlist is enough for sde1 interviews?
20:05 can you give me the code for that?
Will it be something like
delete Logger operator=(const Logger &)?
Correct me if I am wrong
awsome explaination
Perfect work
I have 3 things to say....
1. How is your armpit...seems like due to pole dance you had some issue.
2. Nice explaination
3. How is work at intuit one of my friend joined there and tell me he work day and night and even weekends too.
Great complete Video :)
Why are locks expensive
Can someone explain why we need to have objects of the class at all? why can't getLogger function be static also?
Thanks mam
Can someone help me with VS Code as the thread is not supporting !! Any idea how to resolve that ?
Please provide best resume templates for freshers to apply for tech giant's. It's need of many students
Will do!
It was really helpful.
Normally front end developer uses js, learning dsa using js is it useful or not ?
Dsa is useful for sure (language doesn’t matter that much - as long as you can solve questions)
But I do know some front end developers who are doing really well and don’t know dsa much.