• Omer Katz's avatar
    cppgc: Eliminate marking boilerplate · 18ff5660
    Omer Katz authored
    Starting marking required Creating a Marker and calling StartMarking.
    StartMarking should always have been called immediately after creating
    the marker.
    Since markers are not persisted between GC (a marker exists only while
    marking is in progress), it makes sense to start marking implicitly when
    a marker is created.
    
    Calling StartMarking in MarkerBase ctor is inadvisable since subclasses
    might still to initialize fields.
    Using MarkerFactory instead guarantees that StartMarking is always
    called immediately after creating a Marker.
    
    Bug: chromium:1056170
    Change-Id: Icbf11afd848e1618c204ca6bf951600b3ae9fef2
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2375199
    Commit-Queue: Omer Katz <omerkatz@chromium.org>
    Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
    Reviewed-by: 's avatarAnton Bikineev <bikineev@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#69601}
    18ff5660
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
fuzzilli Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...