« Bugzilla Issues Index
#3210 — 14.5.1 note banning "let" as class name is unnecessary
- bug_id:
3210
- creation_ts:
2014-09-04 12:29:00 -0700
- short_desc:
14.5.1 note banning "let" as class name is unnecessary
- delta_ts:
2014-10-14 15:17:44 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 27: August 24, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
trivial
- everconfirmed:
true
- reporter:
Gabe Levi
- assigned_to:
Allen Wirfs-Brock
- commentid:
10152
- comment_count:
0
- who:
Gabe Levi
- bug_when:
2014-09-04 12:29:04 -0700
10.2.1 says "All parts of a ClassDeclaration or a ClassExpression are strict code."
12.1.1 says that if an identifier is "let" in strict mode then it is a syntax error
By themselves, these two lines ban "class let {}"
However, 14.5.1 goes on to explicitly ban using "let" as the identifier in a class declaration or expression.
We can remove the "let" restriction from 14.5.1, right, since "let" is already forbidden by the implicit strict mode as specified by 10.2.1 and 12.1.1. I would argue that this helps simplify the rules around where and when the pseudo-keyword "let" is allowed, which are somewhat complicated.
- commentid:
10159
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-09-05 16:14:17 -0700
fixed in rev28 editor's draft
- commentid:
10385
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-10-14 15:17:44 -0700
fixed in rev28