Bug 194098 - [JSC] Property 'name' should be available in ClassDefinitionEvaluation
Summary: [JSC] Property 'name' should be available in ClassDefinitionEvaluation
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 194095
  Show dependency tree / graph
 
Reported: 2019-01-31 10:35 PST by Xan Lopez
Modified: 2019-06-28 06:49 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Xan Lopez 2019-01-31 10:35:07 PST 
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).
Comment 1 Xan Lopez 2019-06-28 06:49:36 PDT 
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.