Guy Bedford

@elliottt brought up if we might consider using this rule for clang format. https://clang.llvm.org/docs/ClangFormatStyleOptions.html#insertbraces Thoughts?

gc: add finalization for URL

2

This is a first attempt to fix https://github.com/bytecodealliance/StarlingMonkey/issues/101 for further feedback. In testing, I'm still not able to get the finalizer to run, as I believe we disable the GC...

Per https://github.com/bytecodealliance/StarlingMonkey/pull/108.

As we turn our focus more and more towards performance, it would be good to think about getting some benchmarks together for StarlingMonkey, specifically around testing the performance of builtins...

In the `URL` builtin, we associate all URLs with a Rust URL implementation in https://github.com/bytecodealliance/StarlingMonkey/blob/main/builtins/web/url.cpp#L617, stored in a private slot. This pointer is stored as a private value, which according...

Implement "immutable" headers guard

2

Fetch requests should return a response with headers marked with an `"immutable"` guard, where `check_guard` should always fail. In the Fetch spec it appears this is only ever done for...

Camel casing versus snake casing

1

Do we have a clear convention in the codebase we use for camel casing versus snake casing?

For the test "writer.abort() inside size() should work" In tests/wpt-harness/expectations/streams/transform-streams/reentrant-strategies.any.js.json.

WPT cases regressing in tests/wpt-harness/expectations/compression/decompression-corrupt-input.tentative.any.js.json: * format 'deflate' field ADLER should be error for 255 * format 'gzip' field ISIZE should be error for 1

WPT test regression from tests/wpt-harness/expectations/fetch/api/basic/request-headers-nonascii.any.js.json.