News for hackers. Stuff that matters.
Re:Interesting Bugs Caught by ESLint's no-constant-binary-ex... by d3w4s9 on Thursday November 09, 2023 @06:26AM (#38203672)
TypeScript seems to often make arbitrary decisions what they consider a type error and what is not. The argument is often "TypeScript supports everything in JavaScript" but that is done inconsistently.

A typical example is string + number results in no warning. I understand that some people actually want to do it for "convenience", but often this turns out to be a mistake (e.g. passing the wrong variable). However, if you have a Map<string, number> and tries to do map.get( 3 ), that's an error even though you can absolutely do that in JavaScript -- it just always returns undefined, no error thrown.

You can find a stackoverflow thread about this. To me the current behavior does not make any sense -- I use TypeScript for static typing and avoid any implicit type conversion, and I want that to be consistently applied without exception, that's why I am using TypeScript. I am a bit disappointed that there are a number of such holes in TypeScript.

Other times

Re:Interesting Bugs Caught by ESLint's no-constant-binary-ex... by maxloh on Thursday November 09, 2023 @11:23AM (#38207070)
Do you have an url of the Stack overflow article?
Re:Interesting Bugs Caught by ESLint's no-constant-binary-ex... by d3w4s9 on Thursday November 09, 2023 @12:19PM (#38207873)