[Webkit-unassigned] [Bug 256026] New: Investigate fast path for Object.assign({}, nonEmptyObject)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=256026

            Bug ID: 256026
           Summary: Investigate fast path for Object.assign({},
                    nonEmptyObject)
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jarred at jarredsumner.com

The following common pattern could possibly be optimized further:

```
Object.assign({}, nonEmptyObject);
```

If we know that {} is an empty final object, could we reuse nonEmptyObject's JSC::Structure?


> https://github.com/WebKit/WebKit/pull/13220#issuecomment-1524421218
> I think probably opposite case is getting many benefit from the past optimizations already, but we could get better by detecting empty object of the target in DFG / FTL and change it to object-cloning fast path. Can you file a bugzilla to track this kind of possibility?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230427/3f45b5d6/attachment-0001.htm>