Bug 241639
| Summary: | [WebIDL] Optimize / rework maplike<> and setlike<> declarations | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Shvayka <ashvayka> |
| Component: | Bindings | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Enhancement | CC: | cdumez, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Alexey Shvayka
As Yusuke suggested in https://github.com/WebKit/WebKit/pull/1523#pullrequestreview-1006702442, Map / Set methods can be moved to JSGlobalObject's fields.
Also, we can go further and drop JSC::call and invoke C++ functions like mapProtoFuncValues directly, or even manipulate JSMap directly.
Sam suggested in https://github.com/WebKit/WebKit/pull/1523#issuecomment-1156653410 that we might not need backing Map / Set at all, as it merely duplicates data in most cases given DOM C++ code usually already had a HashMap or HashSet backing things.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/95709260>