Serialized function name descriptors must take engine support into account

Question

Serialized function name descriptors must take engine support into account

novemberborn opened this issue 7 years ago · comments

Older V8 versions don't generate a function name in all circumstances, see https://kangax.github.io/compat-table/es6/#function_name_property.

Determine which scenarios are supported and store this in the serialization. Then, when comparing a deserialized function descriptor assess the current engine support to decide whether a name mismatch is an error or can be ignored.

Sindre Sorhus · Answer 1 · Thu May 18 2017 23:24:51 GMT+0800 (China Standard Time)

More focused: http://node.green/#ES2015-built-in-extensions-function--name--property

Mark Wubben · Answer 2 · Fri May 19 2017 01:19:45 GMT+0800 (China Standard Time)

Determine which scenarios are supported and store this in the serialization.

See https://github.com/novemberborn/function-name-support.

There is one failure case when Istanbul is used: istanbuljs/istanbuljs#59. If we can fix this then we'll be able to include function names in serializations and correctly asses whether a mismatch is an error.