-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 8u40
-
Component/s: core-libs
-
None
-
b17
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8066117 | 9 | Hannes Wallnoefer | P3 | Resolved | Fixed | b42 |
| JDK-8085547 | emb-9 | Hannes Wallnoefer | P3 | Resolved | Fixed | team |
| JDK-8067624 | 8u45 | Hannes Wallnoefer | P3 | Resolved | Fixed | b01 |
| JDK-8070530 | emb-8u47 | Hannes Wallnoefer | P3 | Resolved | Fixed | team |
There are a few remaining issues with let/const after JDK-8051889:
- let/const declarations should not be allowed in raw switch statements where the case clause does not have a block with explicit curly braces.
- let/const should not be allowed in other unprotected statements such as if or while statements without explicit curly braces for the body of the statement.
- for statement with let/const initializer should copy defined symbols from the outer to the inner block on each iteration (see http://esdiscuss.org/topic/in-es6-do-for-loops-with-a-let-const-initializer-create-a-separate-scope)
- let/const declarations should not be allowed in raw switch statements where the case clause does not have a block with explicit curly braces.
- let/const should not be allowed in other unprotected statements such as if or while statements without explicit curly braces for the body of the statement.
- for statement with let/const initializer should copy defined symbols from the outer to the inner block on each iteration (see http://esdiscuss.org/topic/in-es6-do-for-loops-with-a-let-const-initializer-create-a-separate-scope)
- backported by
-
JDK-8066117 let & const: remaining issues with lexical scoping
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-