To type or not to type ?
![](https://kbin.cafe/media/cache/resolve/entry_thumb/56/74/567431c2c53dc5b9ab8ca25e453518a4020ab4747de2954ca183c7d5fffb1adb.webp)
darcy, ![]()
typescript is still weakly typed.
it is just a hacky static analysis that compiles to weakly typed js
vox, ![]()
tbh c/c++ type system is super fucked up
What the fuck isunsigned long long int
just call itu64
Johanno, Well it isn’t always 64 bytes. Some architectures differ.
darcy, ![]()
usize
then
akariii, you can just use
unsigned long long
(drop the int) or, if it bothers you that much,uint64t
but keep in mind that yhe size ofunsigned long long
may vary depending on the architecture
fiah, ![]()
const a: any = “You have no power here!”
socsa, laughs in reinterpret_cast
Is it even a programming language if you can’t casually introduce type overflows?
lowleveldata, tbh unsigned int scares me too. I just use int anyway to avoid strange things happening.
zeropublix, The use of it quite limited in the every-day coders life. People acting like they be using 500TB databases these days.
rikudou, ![]()
Solution:
export type unsigned_int = number
shootwhatsmyname, ![]()
export type App = unknown
Add comment