Bug 194098
| Summary: | [JSC] Property 'name' should be available in ClassDefinitionEvaluation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Xan Lopez <xan.lopez> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | caitp, chi187, littledan, xan.lopez |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 194095 | ||
Xan Lopez
This got consensus recently in TC39 (https://github.com/tc39/ecma262/pull/1372), and some tests for static fields (see bug #194095) depend on it (see https://github.com/tc39/test262/pull/2057).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Xan Lopez
Turns out JSC was already having 'name' available early enough, so no real changes were needed in the end compared to other engines (see bug #194095, where an implementation for static fields is already available). Closing for now.