Function instances all have own 'name' property, contra ES2015 |
|||||||||
Issue descriptionThis is a sub-part of ES2015 function name reform. I'm splitting it off because it may not be web-compatible (several browsers ship 'name' properties on all functions). We will likely want to ship the new function name logic without having to remove 'name' properties on all instances at the same time.
,
Mar 11 2016
,
May 23 2016
State of the world: SpiderMonkey and JSC agree with V8 (all functions have a 'name' instance property). Edge omits it on anonymous functions.
,
Jun 22 2016
,
Jun 22 2016
,
Jun 29 2016
Any thoughts on how to resolve this open question? Since Function.prototype.name is the empty string, this should only be noticeable for cases that depend on an own property. I'm inclined to think the only way to know if this breaks things is to try shipping it, but I'm open to any ideas about usecounting _something_ here.
,
Jul 1 2016
,
Oct 10 2016
,
Mar 23 2017
,
Apr 14 2017
State of the world still the same as in #c3
,
Dec 19 2017
Filed a spec issue: https://github.com/tc39/ecma262/issues/1049
,
Aug 16
Issue 7245 has been merged into this issue.
,
Aug 17
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by littledan@chromium.org
, Mar 10 2016