Array‘s includes and indexOf parameters whether is any more suitable

[1587315093]

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

Playground link with relevant code

💻 Code

const test1 = [123].includes("456")
const test2 = [true].includes(123)

🙁 Actual behavior

Argument of type 'string' is not assignable to parameter of type 'number'.

🙂 Expected behavior

I think includes should accept any type, after all it is a judgment function

[MartinJohns]

Duplicate of #14520.

[fatcerberus]

For the record: proposals to re-type the parameter to any (in lieu of #14520) have been outright rejected in the past on the grounds that it should be an error if, e.g., you check whether string[] contains a number.

[1587315093]

For the record: proposals to re-type the parameter to any (in lieu of #14520) have been outright rejected in the past on the grounds that it should be an error if, e.g., you check whether string[] contains a number.

But it feels a bit inflexible. When I use [null, undefined]. includes (value) to detect whether an external source's value is null and undefined, a prompt will appear. shouldn't the judgment of includes be more flexible

[RyanCavanaugh]

You're totally free to add the any overload to your project if that's the behavior you'd prefer.