should allow type predicates when `isType(badInput as any)`

Bug Report

🔎 Search Terms

🕗 Version & Regression Information

• This is a crash
• This changed between versions ______ and _______
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
• I was unable to test this on prior versions because _______

⏯ Playground Link

https://www.typescriptlang.org/play?#code/LAKAZgrgdgxgLgSwPZQAQIM4EEBOOCGAngBQJQAOEcAXKvlIQNoC6qAPqlBALYBGApjgCUtMpTjoMdBi1ABvUAEgc-OBBxo4OCP1ABfUKAA2q1L3wATAJIUqtDFrIBzANyGQCMKlLY8RYubWthL4UvSEQkLySoE24gB0AFZIZMQA5GlRIAYgoAD0eagAAnAYALQITlBIKqCe3pi4BCSxwZHRIIqtCcmpGVk5QA

💻 Code

function isArray(input: any[] | number): input is any[]
{
	return true
}

let badInput: string;

if (isArray(badInput as any))
{
	badInput.join('')
}

// @ts-ignore
if (isArray(badInput))
{
	badInput.join('')
}

🙁 Actual behavior

🙂 Expected behavior

badInput should know as array when use as any

if (isArray(badInput as any))
{
	badInput.join('')
}

Comienza con el TypeScript Playground enlazado y reproduce la diferencia entre isArray(badInput as any) y el caso con @ts-ignore. Lee el comportamiento de comprobación de tipos en torno a los predicados de tipo definidos por el usuario y compara el tipo inferido dentro de cada rama. Se considera terminado cuando la llamada con cast estrecha badInput a un array sin suprimir el diagnóstico.