ladybird/Libraries/LibJS/Runtime/BooleanObject.cpp

/*
 * Copyright (c) 2020, Jack Karamanian <karamanian.jack@gmail.com>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibJS/Runtime/BooleanObject.h>
#include <LibJS/Runtime/GlobalObject.h>

namespace JS {

GC_DEFINE_ALLOCATOR(BooleanObject);

GC::Ref<BooleanObject> BooleanObject::create(Realm& realm, bool value)
{
    return realm.create<BooleanObject>(value, realm.intrinsics().boolean_prototype());
}

BooleanObject::BooleanObject(bool value, Object& prototype)
    : Object(ConstructWithPrototypeTag::Tag, prototype)
    , m_value(value)
{
}

}
LibJS: Add Boolean constructor object 2020-04-07 00:51:16 -03:00			`/*`
			`* Copyright (c) 2020, Jack Karamanian <karamanian.jack@gmail.com>`
			`*`
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt * 2021-04-22 05:24:48 -03:00			`* SPDX-License-Identifier: BSD-2-Clause`
LibJS: Add Boolean constructor object 2020-04-07 00:51:16 -03:00			`*/`

			`#include <LibJS/Runtime/BooleanObject.h>`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 14:03:52 -03:00			`#include <LibJS/Runtime/GlobalObject.h>`
LibJS: Add Boolean constructor object 2020-04-07 00:51:16 -03:00
			`namespace JS {`
LibJS: Boolean, Number and String prototypes should have values too It appears that calling .valueOf() on an objectified primitive's prototype should return a value after all. This matches what other engines are doing. 2020-04-10 08:04:12 -03:00
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root 2024-11-14 12:01:23 -03:00			`GC_DEFINE_ALLOCATOR(BooleanObject);`
LibJS: Segregate GC-allocated objects by type This patch adds two macros to declare per-type allocators: - JS_DECLARE_ALLOCATOR(TypeName) - JS_DEFINE_ALLOCATOR(TypeName) When used, they add a type-specific CellAllocator that the Heap will delegate allocation requests to. The result of this is that GC objects of the same type always end up within the same HeapBlock, drastically reducing the ability to perform type confusion attacks. It also improves HeapBlock utilization, since each block now has cells sized exactly to the type used within that block. (Previously we only had a handful of block sizes available, and most GC allocations ended up with a large amount of slack in their tails.) There is a small performance hit from this, but I'm sure we can make up for it elsewhere. Note that the old size-based allocators still exist, and we fall back to them for any type that doesn't have its own CellAllocator. 2023-11-19 05:45:05 -03:00
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root 2024-11-14 12:01:23 -03:00			`GC::Ref<BooleanObject> BooleanObject::create(Realm& realm, bool value)`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 14:03:52 -03:00			`{`
LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T> The main motivation behind this is to remove JS specifics of the Realm from the implementation of the Heap. As a side effect of this change, this is a bit nicer to read than the previous approach, and in my opinion, also makes it a little more clear that this method is specific to a JavaScript Realm. 2024-11-13 13:50:17 -03:00			`return realm.create<BooleanObject>(value, realm.intrinsics().boolean_prototype());`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 14:03:52 -03:00			`}`

			`BooleanObject::BooleanObject(bool value, Object& prototype)`
LibJS: Remove Object(Object& prototype) footgun This constructor was easily confused with a copy constructor, and it was possible to accidentally copy-construct Objects in at least one way that we dicovered (via generic ThrowCompletionOr construction). This patch adds a mandatory ConstructWithPrototypeTag parameter to the constructor to disambiguate it. 2022-12-14 08:17:58 -03:00			`: Object(ConstructWithPrototypeTag::Tag, prototype)`
LibJS+LibWeb: Pass prototype to Object constructor Everyone who constructs an Object must now pass a prototype object when applicable. There's still a fair amount of code that passes something fetched from the Interpreter, but this brings us closer to being able to detach prototypes from Interpreter eventually. 2020-04-18 05:27:57 -03:00			`, m_value(value)`
LibJS: Add Boolean constructor object 2020-04-07 00:51:16 -03:00			`{`
			`}`
LibJS: Add missing whitespace around namespace curly braces 2022-04-17 17:59:52 -03:00
LibJS: Add Boolean constructor object 2020-04-07 00:51:16 -03:00			`}`