Codedamn Pro Sale is now live (limited time)! Codedamn Pro includes coding labs, challenges, courses, learning paths, AI access, projects, interview kits, and so much more! Get 80% discount (limited time): codedamn.com/codeday ---- Some helpful links on Codedamn: Pick a 30-day challenge: codedamn.com/challenges Start practicing with a coding lab: codedamn.com/problems Build a project: codedamn.com/projects New full-stack learning path: codedamn.com/learning-path/shubham-fullstack All courses and content: codedamn.com/explore Once again, if you're learning to code, try Codedamn! Start here: codedamn.com/codeday
I hate stupid interview questions like this because they always depend on context. Where is this code being executed? What runtime? What system? What other code has executed before this code? And 100 other whats before you can conclusively give an answer.
I was not sure how to achieve this, but I was sure it might be overriding a callback invocation after value is returned. One another way around than toString is valueOf
Codedamn Pro Sale is now live (limited time)!
Codedamn Pro includes coding labs, challenges, courses, learning paths, AI access, projects, interview kits, and so much more!
Get 80% discount (limited time): codedamn.com/codeday
----
Some helpful links on Codedamn:
Pick a 30-day challenge: codedamn.com/challenges
Start practicing with a coding lab: codedamn.com/problems
Build a project: codedamn.com/projects
New full-stack learning path: codedamn.com/learning-path/shubham-fullstack
All courses and content: codedamn.com/explore
Once again, if you're learning to code, try Codedamn! Start here: codedamn.com/codeday
Will recommend for sure.... 👌
Bro creating more content in one week than me changing my clothes. Damn. Keep the industry insights going!
Here, I don't even remember when I last took bath.
This is a lot easier :
let a = {
value: 1,
toString: function() {
return this.value++;
}
};
console.log(a == 1 && a == 2 && a == 3); // true
:D Moral of the story: Using == in JS should be illegal.
It can work with === as well, if you use Object.defineProperty with a get() that returns incremented value of a global variable.
This algorithm is also known as it_will_work_in_somtime.
This is your best video ever.
always fun to see multiprocessing magic
Is this make any vulnerability in a website, like buffer overflow
Sir plz upload a new 2024 full stack web development course in one shot like you uploaded it before
I guess that is the reason we have atomics ?
I hate stupid interview questions like this because they always depend on context. Where is this code being executed? What runtime? What system? What other code has executed before this code? And 100 other whats before you can conclusively give an answer.
I was not sure how to achieve this, but I was sure it might be overriding a callback invocation after value is returned.
One another way around than toString is valueOf
Classic JS chaos
Crazy
Wow