ladybird/Userland/Libraries/LibJS/Runtime/WeakSet.cpp

/*
 * Copyright (c) 2021, Idan Horowitz <idan.horowitz@serenityos.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibJS/Runtime/WeakSet.h>

namespace JS {

WeakSet* WeakSet::create(Realm& realm)
{
    return realm.heap().allocate<WeakSet>(realm, *realm.intrinsics().weak_set_prototype());
}

WeakSet::WeakSet(Object& prototype)
    : Object(prototype)
    , WeakContainer(heap())
{
}

void WeakSet::remove_dead_cells(Badge<Heap>)
{
    m_values.remove_all_matching([](Cell* cell) {
        return cell->state() != Cell::State::Live;
    });
}

}
LibJS: Add the WeakSet built-in object 2021-06-09 19:23:04 +03:00			`/*`
			`* Copyright (c) 2021, Idan Horowitz <idan.horowitz@serenityos.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#include <LibJS/Runtime/WeakSet.h>`

			`namespace JS {`

LibJS+LibWeb: Replace GlobalObject with Realm in create() functions This is a continuation of the previous two commits. As allocating a JS cell already primarily involves a realm instead of a global object, and we'll need to pass one to the allocate() function itself eventually (it's bridged via the global object right now), the create() functions need to receive a realm as well. The plan is for this to be the highest-level function that actually receives a realm and passes it around, AOs on an even higher level will use the "current realm" concept via VM::current_realm() as that's what the spec assumes; passing around realms (or global objects, for that matter) on higher AO levels is pointless and unlike for allocating individual objects, which may happen outside of regular JS execution, we don't need control over the specific realm that is being used there. 2022-08-16 00:20:49 +01:00			`WeakSet* WeakSet::create(Realm& realm)`
LibJS: Add the WeakSet built-in object 2021-06-09 19:23:04 +03:00			`{`
LibJS: Move intrinsics to the realm Intrinsics, i.e. mostly constructor and prototype objects, but also things like empty and new object shape now live on a new heap-allocated JS::Intrinsics object, thus completing the long journey of taking all the magic away from the global object. This represents the Realm's [[Intrinsics]] slot in the spec and matches its existing [[GlobalObject]] / [[GlobalEnv]] slots in terms of architecture. In the majority of cases it should now be possibly to fully allocate a regular object without the global object existing, and in fact that's what we do now - the realm is allocated before the global object, and the intrinsics between both :^) 2022-08-27 00:54:55 +01:00			`return realm.heap().allocate<WeakSet>(realm, *realm.intrinsics().weak_set_prototype());`
LibJS: Add the WeakSet built-in object 2021-06-09 19:23:04 +03:00			`}`

			`WeakSet::WeakSet(Object& prototype)`
			`: Object(prototype)`
LibJS: Generify the garbage collector's weak container notifications This will allow us to use the same interface for other JS weak containers like the WeakMap & WeakRef. 2021-06-12 05:23:33 +03:00			`, WeakContainer(heap())`
LibJS: Add the WeakSet built-in object 2021-06-09 19:23:04 +03:00			`{`
			`}`

LibJS: Make WeakContainer pruning do less work Instead of iterating all swept cells when pruning weak containers, only iterate the cells actually in the container. Also, instead of compiling a list of all swept cells, we can simply check the Cell::state() flag to know if something should be pruned. 2021-10-05 18:44:31 +02:00			`void WeakSet::remove_dead_cells(Badge<Heap>)`
LibJS: Notify WeakSets when heap cells are sweeped This is an implementation of the following optional optimization: https://tc39.es/ecma262/#sec-weakref-execution 2021-06-09 20:10:47 +03:00			`{`
LibJS: Use HashTable::remove_all_matching() in WeakSet :^) 2022-01-05 16:48:05 +01:00			`m_values.remove_all_matching([](Cell* cell) {`
			`return cell->state() != Cell::State::Live;`
			`});`
LibJS: Add the WeakSet built-in object 2021-06-09 19:23:04 +03:00			`}`

			`}`