But the CPU would be thoroughly confused in many cases. Like if you added a number with a string. This means low level tools have too and therefore people who do low level programming are confused and the generally carefree has rules can make it difficult to debug js.
Also I think rust making you write “safe” code unless you explicitly tell it otherwise is a great thing.
So I think that tools telling the user that they’re doing something wrong is great, tools telling the user to stick with physical limitations for better performance are completely valid but what js does seem really weird with having constants be reassignable, making them nothing but labels combined with HTML I find it even more annoying.
I’m always more confused by adding integers to strings or something being an empty object because something else was undefined and the console didn’t bother to tell me.
Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.
If you actually meant type qualifier, then no. That was never required.
Missing type or identifier.
A const what?
Its javascript, itll just let you do that
Pretty much sums up JavaScript’s entire philosophy.
Imo, its better for it. A tool shouldnt tell the user what to do
But the CPU would be thoroughly confused in many cases. Like if you added a number with a string. This means low level tools have too and therefore people who do low level programming are confused and the generally carefree has rules can make it difficult to debug js.
Also I think rust making you write “safe” code unless you explicitly tell it otherwise is a great thing.
So I think that tools telling the user that they’re doing something wrong is great, tools telling the user to stick with physical limitations for better performance are completely valid but what js does seem really weird with having constants be reassignable, making them nothing but labels combined with HTML I find it even more annoying.
Gets me every time.
I’m always more confused by adding integers to strings or something being an empty object because something else was undefined and the console didn’t bother to tell me.
You’re downvoted, but you’re 100% right. The web is designed to not break. Engineers who can’t accept that don’t get to complain
I think, most of us consider it part of the job of a good tool, that it prevents us from using it wrongly. Allows us to use it much more recklessly.
Let me just coalesce these types for you.
:any
const long pain = 1;
1L
void
Maybe…
const pain = InfinityAckshually you don’t need a type qualifier in C
Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.
If you actually meant type qualifier, then no. That was never required.
Really? TIL.
Defaults to int if I’m not mistaken.