I'm a bit confused by the fact that the array starts out typed as `any[]` (e.g. if you hover over the declaration) but then, later on, the type gets refined to `(string | number)[]`. IMO it would be nicer if the declaration already showed the inferred type on hover.

▲ sheept 2 hours ago | parent | next [-]

I agree, it's always been unsettling to see any[] on hover, even though it gets typed in the end.

I think one reason might be to allow the type to be refined differently in different code paths. For example:

    function x () {
        let arr = []
        if (Math.random() < 0.5) {
            arr.push(0)
            return arr
        } else {
            arr.push('0')
            return arr
        }
    }

In each branch, arr is typed as number[] and string[], respectively, and x's return type is number[] | string[]. If it decided to retroactively infer the type of arr at declaration, then I'd imagine x's return type would be the less specific (number | string)[].

▲ bastawhiz 3 hours ago | parent | prev [-]

It depends on your tsconfig. An empty array could be typed as never[], forcing you to annotate it.

	▲	wk_end 3 hours ago \| parent \| next [-]
		I don't believe this is correct. There's no settings that correspond to that AFAIK, and it'd actually be quite bad, because you could access the empty array and then get a `never` object, which you're not supposed to be able to do. https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABM... `unknown[]` might be more appropriate as a default, but TypeScript does you one better: with OP's settings, although it's typed as `any[]`, it'll error out if you don't do anything to give it more information because of `noImplicitAny`.
	▲	loevborg 3 hours ago \| parent \| prev [-]
		Which setting specifically? Can you repro in the typescript playground?