Skip to content
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
This repository was archived by the owner on Apr 22, 2023. It is now read-only.

The Set problem with 0.11.14 [v8 upgrade] #8449

Description

@iliakan

Installed node 0.11.14 on MacOs.

Now consider this one-liner (run with node --harmony):

new Set([1,2]).forEach(function(item) {  console.log(item); });

It outputs nothing. That's a bug in V8, because according to ES6 draft it should list the items.

This breaks both projects which rely on the correct behavior OR which rely on the absence of Set.prototype.forEach (till recent times in V8).

For me, it triggered a failure within a module array-uniq using new Set, and this module was used by array-union, then multimatch, then gulp-load-plugins then my build system.

I believe it can cause other problems as well for other people.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions