NEW 202007
When reifying a custom accessor, we should consider using CustomGetterSetter instead of GetterSetter 
https://bugs.webkit.org/show_bug.cgi?id=202007
Summary When reifying a custom accessor, we should consider using CustomGetterSetter ...
Saam Barati
Reported 2019-09-19 14:57:23 PDT
I'm not sure why we do it the way we currently do, but it seems bad for perf. Since our ICs already know how to call into custom accessors directly, by caching it as a JS getter/setter with a JSFunction which wraps native code, we're just being circuitous. There's probably a reason why it's currently done this way, perhaps to answer getOwnPropertyDescriptor queries, but we could do better.
Attachments
Add attachment proposed patch, testcase, etc.
Note You need to log in before you can comment on or make changes to this bug.