« Bugzilla Issues Index
#1406 — 15.14.1.1, 15.15.1.1, 15.16.1.1: Collection objects require "new"
- bug_id:
1406
- creation_ts:
2013-04-10 08:19:00 -0700
- short_desc:
15.14.1.1, 15.15.1.1, 15.16.1.1: Collection objects require "new"
- delta_ts:
2013-08-07 13:56:20 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 14: March 8, 2013 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
WONTFIX
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- flag:
{"_attributes"=>{"name"=>"TC39Review", "id"=>"10", "type_id"=>"1", "status"=>"?", "setter"=>"allen"}}
- commentid:
3587
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-04-10 08:19:09 -0700
See step 1-2 of 15.14.1.1:
> 1. Let map be the this value.
> 2. If Type(map) is not Object then, throw a TypeError exception.
That means `var map = Map()` throws a TypeError instead of creating a new Map object.
- commentid:
3845
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-05-14 08:42:02 -0700
needs TC39 resolution. Do we want Map/Set/Weakmap to act as factory functions?
As a general policy do we want to encourage that usage?
- commentid:
4794
- comment_count:
2
- who:
André Bargull
- bug_when:
2013-08-07 12:08:03 -0700
Resolve as INVALID or WONTFIX based on bug 1732?
- commentid:
4802
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-07 13:56:20 -0700
see comment 2