1 // This file was procedurally generated from the following sources:
2 // - src/annex-b-fns/eval-func-no-skip-param.case
3 // - src/annex-b-fns/eval-func/direct-if-decl-else-decl-b.template
5 description: Extension observed when there is a formal parameter with the same name (IfStatement with a declaration in both statement positions in eval code)
6 esid: sec-functiondeclarations-in-ifstatement-statement-clauses
7 flags: [generated, noStrict]
9 The following rules for IfStatement augment those in 13.6:
11 IfStatement[Yield, Return]:
12 if ( Expression[In, ?Yield] ) FunctionDeclaration[?Yield] else Statement[?Yield, ?Return]
13 if ( Expression[In, ?Yield] ) Statement[?Yield, ?Return] else FunctionDeclaration[?Yield]
14 if ( Expression[In, ?Yield] ) FunctionDeclaration[?Yield] else FunctionDeclaration[?Yield]
15 if ( Expression[In, ?Yield] ) FunctionDeclaration[?Yield]
18 B.3.3.3 Changes to EvalDeclarationInstantiation
21 ii. If replacing the FunctionDeclaration f with a VariableStatement that
22 has F as a BindingIdentifier would not produce any Early Errors for
30 'init = f;if (false) function _f() {} else function f() { }after = f;'
34 assert.sameValue(init, 123, 'binding is not initialized to `undefined`');
36 typeof after, 'function', 'value is updated following evaluation'