« Bugzilla Issues Index
#4152 — ArrowParameters not strict
- bug_id:
4152
- creation_ts:
2015-03-10 06:29:00 -0700
- short_desc:
ArrowParameters not strict
- delta_ts:
2015-07-10 08:34:17 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 35: March 4, 2015 Release Candidate 2
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
INVALID
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Erik Arvidsson
- assigned_to:
Allen Wirfs-Brock
- cc:
["erik.arvidsson", "jmdyck"]
- commentid:
13676
- comment_count:
0
- who:
Erik Arvidsson
- bug_when:
2015-03-10 06:29:24 -0700
The ArrowFormalParameters are strict but the single binding identifier is not. This means that:
static => 1;
is valid but:
(static) => 1;
is not.
That is kind of weird.
- commentid:
13682
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-10 13:23:16 -0700
How do you figure?
The only static semantic rule for StrictFormalParameters is in 14.1.2 and says that there can't be any duplicate parameter names.
I suppose StrictFormalParameters is a misleading name as it really has nothing to do with strict mode. The strict mode of an arrow function is determined in the usual way (either contained in strict code or its body has a "use strict" directive.
- commentid:
13683
- comment_count:
2
- who:
Erik Arvidsson
- bug_when:
2015-03-10 13:28:38 -0700
This always gets me.
The name always gets me thinking that the strict mode rules for FormalParameters should be applied.
A different name might help but I can't think of anything... Maybe NoDuplicatesFormalParameters to be explicit?
- commentid:
13687
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-10 13:50:39 -0700
SlightlyStrictFormalParameters ??
- commentid:
13689
- comment_count:
4
- who:
Michael Dyck
- bug_when:
2015-03-10 15:30:30 -0700
DistinctFormalParameters ?