mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-10-27 10:29:23 +00:00
27d139e817
Some checks are pending
CI / macOS, arm64, Sanitizer, Clang (push) Waiting to run
CI / Linux, x86_64, Fuzzers, Clang (push) Waiting to run
CI / Linux, x86_64, Sanitizer, GNU (push) Waiting to run
CI / Linux, x86_64, Sanitizer, Clang (push) Waiting to run
Package the js repl as a binary artifact / Linux, arm64 (push) Waiting to run
Package the js repl as a binary artifact / macOS, arm64 (push) Waiting to run
Package the js repl as a binary artifact / Linux, x86_64 (push) Waiting to run
Run test262 and test-wasm / run_and_update_results (push) Waiting to run
Lint Code / lint (push) Waiting to run
Label PRs with merge conflicts / auto-labeler (push) Waiting to run
Push notes / build (push) Waiting to run
1. Fix typos in some macro invocations of these error types. We now use a single xmacro to instantiate error definitions to prevent such errors in the future. 2. Use the "WebAssembly." prefix as needed. 3. Allocate the error constructors and prototypes with `realm.create` rather than `heap.allocate`. The latter does not invoke `initialize` methods. This exposed the next issue: 4. Use the correct intrinsic prototype in the error constructor. We were using the base native error prototype. We unfortunately cannot invoke OrdinaryCreateFromConstructor from LibJS directly with the correct prototype, so an implementation was added here. 5. Use intrinsic accessors to create the constructors. I don't think this one was actually a fix, but it makes the setup look more like other built-ins. |
||
|---|---|---|
| .. | ||
| core | ||
| jsapi | ||