![[The AI Show Episode 148]: Microsoft’s Quiet AI Layoffs, US Copyright Office’s Bombshell AI Guidance, 2025 State of Marketing AI Report, and OpenAI Codex](https://www.marketingaiinstitute.com/hubfs/ep%20148%20cover%20%281%29.png)
![[The AI Show Episode 146]: Rise of “AI-First” Companies, AI Job Disruption, GPT-4o Update Gets Rolled Back, How Big Consulting Firms Use AI, and Meta AI App](https://www.marketingaiinstitute.com/hubfs/ep%20146%20cover.png)
![[FREE EBOOKS] The Embedded Linux Security Handbook, Modern Generative AI with ChatGPT and OpenAI Models & Four More Best Selling Titles](https://www.javacodegeeks.com/wp-content/uploads/2012/12/jcg-logo.jpg){kind=logo}
![Laid off but not afraid with X-senior Microsoft Dev MacKevin Fey [Podcast #173]](https://cdn.hashnode.com/res/hashnode/image/upload/v1747965474270/ae29dc33-4231-47b2-afd1-689b3785fb79.png?#)
.png?width=1920&height=1920&fit=bounds&quality=70&format=jpg&auto=webp#)
_David_Hall_-Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
_Andriy_Popov_Alamy_Stock_Photo.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
![Apple 15-inch M4 MacBook Air On Sale for $1049.99 [Deal]](https://www.iclarified.com/images/news/97419/97419/97419-640.jpg)
![Xiaomi Tops Wearables Market as Apple Slips to Second in Q1 2025 [Chart]](https://www.iclarified.com/images/news/97417/97417/97417-640.jpg)
T vs any in TypeScript
Article originally published here : https://alsohelp.com/blog/t-vs-any-in-typescript Something you probably already heard about, but this is my way of seeing it. Article below This is something that went in my head while learning TypeScript. Both means "could be any kind of type", but there is one huge difference. Similarities of "any" and generic "T" any is never constrained generic is always under constraint somewhere Example with generic T Let's say we want a method that returns an array with only one element : function oneElementArrayOf(stuff: T): [T] { return [stuff]; } T is under constraint : "stuff" can only be of T type, and the return type can only be an array of T In other word, if you see the somewhere, there is another place where it will be used, in the args or the returned type. Same example with any The same code with any function oneElementArrayOf(stuff: any): [any] { return [43]; // valid!! } "any" is not constrained by anything. The code is valid (TS valid I mean), despite not achieving the initial goal. Summary That was quick, but I hope it helped. To sum up, "any" means "zero constraint". "T" means "has at least one constraint". Hope it helped! David.
Article originally published here : https://alsohelp.com/blog/t-vs-any-in-typescript
Something you probably already heard about, but this is my way of seeing it.
Article below
This is something that went in my head while learning TypeScript.
Both means "could be any kind of type", but there is one huge difference.
Similarities of "any" and generic "T"
- any is never constrained
- generic is always under constraint somewhere
Example with generic T
Let's say we want a method that returns an array with only one element :
function oneElementArrayOf<T>(stuff: T): [T] {
return [stuff];
}
T is under constraint : "stuff" can only be of T type, and the return type can only be an array of T
In other word, if you see the somewhere, there is another place where it will be used, in the args or the returned type.
Same example with any
The same code with any
function oneElementArrayOf(stuff: any): [any] {
return [43]; // valid!!
}
"any" is not constrained by anything. The code is valid (TS valid I mean), despite not achieving the initial goal.
Summary
That was quick, but I hope it helped.
To sum up,
- "any" means "zero constraint".
- "T" means "has at least one constraint".
Hope it helped!
David.
