A FunctionExpression/Method/Getter/Setter may capture its own name about proposal-binary-ast

[syg]

I think this is only a bug for named FunctionExpressions. FunctionDeclarations' names are treated as bindings in the enclosing scope. Method, Getter, and Setter can't be recursively called like that, since they don't make a binding.

[Yoric]

So, if I read this correctly, we store the information in the parameterScope, right? This would probably deserve a comment in the webidl section.

[syg]

So, if I read this correctly, we store the information in the parameterScope, right? This would probably deserve a comment in the webidl section.

That's right, and it's mainly because of how the declared names are checked. AssertedParameterScopes' declared names are checked with the BoundNames static semantics in ecma262, instead of VarDeclaredNames or LexicallyDeclaredNames. That happens to match what the Catch production's runtime semantics already does.