New issue
Advanced search Search tips

Issue 716715 link

Starred by 1 user
Status: Duplicate
Merged: issue v8:6022
Owner:
neis@chromium.org
Closed: May 2017
Cc:
gsat...@chromium.org
adamk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect Completion Value for ClassDeclaration statement

Reported by joepec...@gmail.com, Apr 29 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
eval(`1; class C {}`)

What is the expected behavior?
1

What went wrong?
C

Did this work before? N/A 

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

https://tc39.github.io/ecma262/#sec-class-definitions-runtime-semantics-evaluation

Comment 1 Deleted

Comment 2 by littledan@chromium.org, Apr 29 2017

Status: Available (was: WontFix)

Comment 3 by gsat...@chromium.org, Apr 29 2017

Cc: gsat...@chromium.org
Components: -Blink Blink>JavaScript>Language

Comment 4 Deleted

Comment 5 by adamk@chromium.org, May 1 2017

Owner: adamk@chromium.org
Status: WontFix (was: Available)
This is working as intended, as step 2 of Evaluation for ClassDefinition (from the link above) is "Return NormalCompletion(empty)". It appears Chakra and JSC get this wrong, but V8 agrees with SpiderMonkey.

Comment 6 by joepec...@gmail.com, May 1 2017 

In Chrome: Version 58.0.3029.81 (64-bit)

  > eval(`1; class C {}`)
  class C {}

How is that working as intended? Am I using an outdated version of Chrome?

Comment 7 by adamk@chromium.org, May 1 2017

Cc: adamk@chromium.org
Mergedinto: v8:6022
Owner: neis@chromium.org
Status: Duplicate (was: WontFix)
Ah, yes, this is actually "Fixed", not "WontFix". neis@ fixed this in https://chromium-review.googlesource.com/446349
►

Sign in to add a comment