Fix setTimeout/setInterval/setImmediate functions

[falsandtru]

Fix too lax typings.

TypeScript Version: master

Expected behavior:

declare function setTimeout(handler: (...args: any[]) => void, timeout?: number, ...args: any[]): number;

Actual behavior:

declare function setTimeout(handler: (...args: any[]) => void, timeout: number): number;
declare function setTimeout(handler: any, timeout?: any, ...args: any[]): number;

[mhegazy]

I think it allows string too. see https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout

[falsandtru]

Then this is valid, right?

declare function setTimeout(handler: ((...args: any[]) => void) | string, timeout?: number, ...args: any[]): number;

[aluanhaddad]

Be aware, that if you pass a string it is equivalent to eval.

Douglas Crockford warned of this.

Perhaps this second declaration could go into @RyanCavanaugh's proposed Annex B 😉

[berickson1]

Looking at some of the new features that Typescript provides, I'd expect the following to be a better more specific definition

declare function setTimeout<T>(handler: string | ((...args: T[]) => void), timeout?: number , ...params: T[]) => number;

[xaviergxf]

Hi, no news about this?

[Jack-Works]

We hit this problem. TypeScript does not check this code:

function f(x: number) {
  x.toExponential()
}

setTimeout(f, 100)
//         ~ should be an error!