Version: 6.5.107
OS: linux
Architecture: x86-64

What steps will reproduce the problem?

Object.getOwnPropertyDescriptor(Proxy.revocable({}, {}).revoke, 'name');

What is the expected output?

undefined

What do you see instead?

{value: "revoke", writable: false, enumerable: false, configurable: true}

Please use labels and text to provide additional information.

Per [1], Proxy revocation functions are anonymous functions, which should not have a "name" property in accordance with [2]. Other anonymous functions in V8 all do not have "name" properties:

- Promise resolve/reject functions
  new Promise((resolve, reject) => { print(resolve.name); print(reject.name); });

- GetCapabilitiesExecutor functions
  class PromiseSub extends Promise { constructor(executor) { print(executor.name); super(executor); } } PromiseSub.resolve();

- Promise.all resolve element functions
  class PromiseSub extends Promise { then(onResolve, onReject) { print(onResolve.name); super.then(onResolve, onReject); } } PromiseSu
b.all([PromiseSub.resolve()]);

- AsyncFunction awaited fulfilled/rejected functions
  (async () => { await { then(onFulfilled, onRejected) { print(onFulfilled.name); print(onRejected.name); } } })()

The cause for this bug seems to be https://cs.chromium.org/chromium/src/v8/src/js/proxy.js?l=23&rcl=f5b1d1d4f29b238ca2f0a13bf3a7b7067854592d, where the "name" property is unfortunately automatically added to the function by virtue of it being in an object literal. An indirect expression like "revoke: (0, () => %JSProxyRevoke(p))" would mitigate this behavior.

SpiderMonkey has the same bug as V8 (bug will be filed soon), but ChakraCore does not.

[1]: https://tc39.github.io/ecma262/#sec-proxy-revocation-functions
[2]: https://tc39.github.io/ecma262/#sec-ecmascript-standard-built-in-objects