Changes between Version 2 and Version 3 of Ticket #3873


Ignore:
Timestamp:
03/24/2016 05:28:59 PM (4 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3873 – Description

    v2 v3  
    22The special property `__proto__` has only recently been added to the ES standard as a legacy feature. Moreover, object literals using `__proto__` causes the whole function to be deoptimized on V8. 
    33 
    4 Anyway, for a while we avoid using `__proto__` now where easily possible, in particular for objects used as a hash-table. With #656, we even migrated most of the code to use `Object.create(null)` where possible. But it seems some bits have been overlooked or got reintroduced later. 
     4Anyway, for a while we avoid using `__proto__` now where easily possible, in particular for objects used as a hash-table. With #656, we even migrated most existing code where possible to use `Object.create(null)` instead. But it seems some bits have been overlooked or got reintroduced later. 
    55 
    6 Most notably, `ActiveFilter.domains` is currently using `__proto__` in an object literal, triggering a deoptimization on V8, that effects filter matching performance. 
     6Most notably, `ActiveFilter.domains` is currently using `__proto__` in an object literal, triggering a deoptimization on V8, that effects filter matching performance on Chrome. 
    77 
    88=== What to change ===