Why does the argument for Array.prototype.includes(searchElement) need the same type as array elements?

See microsoft/TypeScript#26255 for a full discussion on Array.prototype.includes() and supertypes.


Yes, technically it should be safe to allow the searchElement parameter in Array<T>.includes() to be a supertype of T, but the standard TypeScript library declaration assumes that it is just T. For most purposes, this is a good assumption, since you don’t usually want to compare completely unrelated types as @GustavoLopes mentions. But your type isn’t completely unrelated, is it?

There are different ways to deal with this. The assertion you’ve made is probably the least correct one because you are asserting that a string is an AllowedChars even though it might not be. It “gets the job done” but you’re right to feel uneasy about it.


Another way is to locally override the standard library via declaration merging to accept supertypes, which is a bit complicated because TypeScript doesn’t support supertype constraints (see ms/TS#14520 for the feature request). Instead, the declaration uses conditional types to emulate a supertype constraint:

// remove "declare global" if you are writing your code in global scope to begin with
declare global {
  interface Array<T> {
    includes<U extends (T extends U ? unknown : never)>(
      searchElement: U, fromIndex?: number): boolean;
  }
}

Then your original code will just work:

if (exampleArr.includes(e.key)) {} // okay
// call to includes inspects as
// (method) Array<AllowedChars>.includes<string>(
//    searchElement: string, fromIndex?: number | undefined): boolean (+1 overload)

while still preventing the comparison of completely unrelated types:

if (exampleArr.includes(123)) {} // error
// Argument of type '123' is not assignable to parameter of type 'AllowedChars'.

But the easiest and still correct way to deal with this is to widen the type of exampleArr to readonly string[]:

const stringArr: readonly string[] = exampleArr; // no assertion
if (stringArr.includes(e.key)) {}  // okay

Or more succinctly like:

if ((exampleArr as readonly string[]).includes(e.key)) {} // okay

Widening to readonly string[] is fine, but be careful widening to string[], which is a little more dangerous because TypeScript unsafely treats Array<T> as covariant in T for convenience. This is fine for reading, but when you write properties you run into problems:

(exampleArr as string[]).push("whoopsie"); // uh oh, don't do this

But since you’re just reading from the array it’s perfectly safe, and why readonly is recommended.


Playground link to code

Leave a Comment