Working with ES6 Sets in Typescript

[robianmcd]

The constructor for an ES6 Set takes an optional iterable parameter (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) but the declaration in lib.d.ts doesn't include it

declare var Set: {
    new <T>(): Set<T>;
}

So I'm getting a Typescript error if I try to do something like new Set([1,2,3]).

On a somewhat related note I'm using the 1.5 Beta version of typescript which supports a lot of ES6 features but it still relies on the browser to support Sets. Are there plans polyfill Sets in Typescript?

[mhegazy]

TypeScript does not come with built in pollyfills. it is up to you to decide which pollyfill to use, if any. you can use something like es6Collection, es6-shims, corejs..etc.
All the Typescript compiler needs is a declaration for the ES6 constructs you want to use. you can find them all in this lib file.

here is the relevant portion:

interface Set<T> {
    add(value: T): Set<T>;
    clear(): void;
    delete(value: T): boolean;
    entries(): IterableIterator<[T, T]>;
    forEach(callbackfn: (value: T, index: T, set: Set<T>) => void, thisArg?: any): void;
    has(value: T): boolean;
    keys(): IterableIterator<T>;
    size: number;
    values(): IterableIterator<T>;
    [Symbol.iterator]():IterableIterator<T>;
    [Symbol.toStringTag]: string;
}

interface SetConstructor {
    new <T>(): Set<T>;
    new <T>(iterable: Iterable<T>): Set<T>;
    prototype: Set<any>;
}
declare var Set: SetConstructor;

[robianmcd]

How do I tell the TypeScript compiler to use lib.es6.d.ts instead of lib.d.ts? I can't just redeclare Set or I will get a Subsequent variable declarations must have the same type. error. I'm using gulp Traceur and I'm not explicitly including lib.d.ts anywhere so I'm not sure how to replace it.

[mhegazy]

You can declare it in one of your source files and you should not get the duplicate definition errors.

You can also include this file in your project and explicitly reference it..

[robianmcd]

If I add something like

interface SetConstructor {
    new <T>(): Set<T>;
    new <T>(iterable: any): Set<T>;
    prototype: Set<any>;
}
declare var Set: SetConstructor;

to one of my .d.ts or .ts files I get a Subsequent variable declarations... error.

If I include a reference to lib.es6.d.ts I get a bunch of errors like this:

.../typings/lib.es6.d.ts(1196,2): 1169 Computed property names are not allowed in interfaces.

[mhegazy]

Which version of typescript are you using?

I gave you the wrong diffinition sorry about that. So some corrections:

• you need to be using 1.5-beta

And add the typings:

interface Set<T> {
    add(value: T): Set<T>;
    clear(): void;
    delete(value: T): boolean;
    entries(): Array<[T, T]>;
    forEach(callbackfn: (value: T, index: T, set: Set<T>) => void, thisArg?: any): void;
    has(value: T): boolean;
    keys(): Array<T>;
    size: number;
}

interface SetConstructor {
    new <T>(): Set<T>;
    new <T>(iterable: Array<T>): Set<T>;
    prototype: Set<any>;
}
declare var Set: SetConstructor;

@JsonFreeman we should remove the restriction on computer properties in interfaces..right?

@rbuckton is getting a correct es6 typing file ready; @rbuckton please share it with @robianmcd

[JsonFreeman]

@mhegazy Why do you want to remove the restriction on computed properties in interfaces?

[mhegazy]

currently you can not write a declaration file that uses symbols and get it to work in ES5 and ES6, you have to write two. i think this is artificial. we need to allow the use of Symbols and the use of computed properties in both. this way if you are using lib.d.ts you are not getting ES6 types, but if you deliberately use lib.es6.d.ts you can still use that with target ES5.

[mhegazy]

@JsonFreeman let's chat about what and when we need to do this

[DanielRosenwasser]

we need to allow the use of Symbols and the use of computed properties in both

I think this fits well for people who are using a polyfill anyway.

[JsonFreeman]

We do allow computed properties downlevel. So there is nothing to do for that. In terms of Symbols, we do support polyfilling symbols in ES5. You just have to provide the typings yourself. Are you suggesting just to move the Symbols into the main lib.d.ts, where ES5 can see them as well?