TypeScript Temporal Uncertainty (that weird error you get sometimes)

preview_player
Показать описание
Sometimes you do a type check on a value but when you try to use it, its suddenly as if you never did the type check. This lesson explains the most common reason why. Its go to do with time ⏱

🚥 Professional Courses

#basarat #TypeScript #JavaScript #tutorial

👇 ❤️ Subscribe for MOORE ❤️ 👇

**Feel Free To Read This Lot**

I'm Basarat, and I love helping developers. More about me:

Microsoft MVP for TypeScript
200K contributions on Stackoverflow. Top Contributor for TypeScript.
Book Author : Beginning NodeJS
Book Author : TypeScript Deep Dive
Creator of multiple hot ✨ed Github Open Source projects

Рекомендации по теме
Комментарии
Автор

Awesome short video format, love it that I can just jump from one thing to the other

ukaszwosek
Автор

Very good video, explained well, nice audio visuals. Way to go, keep it up :)

FrugoDrinkers
Автор

This is great explanation. Thanks! 👍
Also cool hair style 😀

vcfvct
Автор

Familiar with this behavior, but didn't realize it had a name!

bryanhaney
Автор

I don't see why the fact that setTimeout() calls its callback asynchronously has any relevance to an array method that does not call its callback asynchronously. Both behaviours are defined by standards to be how they are and TS should know.

davidmaxwaterman
Автор

Even though the function for forEach is a callback wouldn’t it be synchronous?

nxte
Автор

great tip, just a comment, this tip is not present in your Udemy course. not sure if that's intentional or not. you can decide.

marslogics
Автор

or just use const to begin with? no need for a new variable right?

jazcash