Bug 227187 – Nonsensical error message when using a variable named eval in the same scope as a usage of eval

• Status: RESOLVED
• Resolution: INVALID
• Component: JavaScriptCore

[Oliver Hunt]

Given this exciting function:
function f() { let eval=eval; print(a)}

We get the error

Cannot access uninitialized variable

It appears that triggering this requires using a variable named eval, and also accessing eval in the same scope.

This is very clearly a P0 :D

[Radar WebKit Bug Importer]

<rdar://problem/79822761>

[Oliver Hunt]

I wish I recalled the context for this, but afaict given current semantics this is correct behavior.