Bug 227187
| Summary: | Nonsensical error message when using a variable named eval in the same scope as a usage of eval | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Oliver Hunt <oliver> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | saam, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
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.