Odd behavior with --noImplicitAny false --strictNullChecks true

[ghost]

Given this code:

const x = [];
x.push(1);
const y: string = x[0];

With various settings of --noImplicitAny and strictNullChecks, we get the following types for x on line 3:

	--noImplicitAny false	--noImplicitAny true
--strictNullChecks false	any[]	number[]
--strictNullChecks true	never[]	number[]

I would expect the lower-left corner to also be any[], not never[].
(Ref: #16218 (comment))

[ghost]

With --noImplicitAny true --strictNullChecks false, I would expect an un-annotated [] to fail -- and it does, but only inside another array, as in [[]].

const a = []; // OK?
const b = [[]]; // Error
const c = [].map(() => []); // OK?

[paleo]

I would expect the lower-left corner to also be any[], not never[].

Thank you.

With the --strict true and --noImplicitAny false compiler options, the compiler forces us to sprinkle the code with unpleasant statements:

const arr: any[] = []