Understand 'int', 'integer', 'float', 'double', etc. as 'number' in JSDoc

All numeric-sounding names should probably resolve to number (maybe only if no other type is defined with such a given name).

Ideas:

• [u]int[8|16|32|64]
• integer
• float
• double

[andy-ms]

This might require a breaking change later if actual ints are added.

[pilatte]

Arrays in JS are objects so when you access keys with x[<key>], <key> can be anything.

> x = ['foo']
[ 'foo' ]
> x[1.5] = 'bar'
'bar'
> x
[ 'foo', '1.5': 'bar' ]
> x['test']= 15
15
> x
[ 'foo', '1.5': 'bar', test: 15 ]
> x.length
1
> x = new Int8Array(10)
Int8Array(10) [
  0, 0, 0, 0, 0,
  0, 0, 0, 0, 0
]
> x['hello'] = 15
15
> x[1.5] = "foo"
'foo'

In TS, it only checks if the key is a number so a string key will fail but 1.5 is a valid key.

Maybe int could be implemented somehow like literals. But it’s not feasible to guess if a number is an integer or not on computed variables. Typescript does not know the difference between 3/2 and 4/2. One would be a float and the other an int but it is difficult to infer this statically.

Being able to set float keys on an array and not get an error at compile time and neither at runtime is really bad but I guess that’s how it is for now.