Andrew Kaster

fwiw the job rename will break and @CanadaHonk's fork of it used by test262.fyi,

or actually, will it? maybe not, seems those go off the "job name", which is funnily enough something i'd consider *less* stable than filenames

@NotAShelf two things - please observe the contribution guidelines on commit hygiene. We cherry-pick commits directly from the PR branch onto master, without squashing. And we don't use conventional commits...

> I could squash them into a singular commit and describe the changes in the description if that makes more sense to you? Whatever makes the most sense as far...

Sure, these changes look good to me! Thanks for squashing it up. Looks like the linter is upset with your line-wrapping, but I can clean that up and merge this...

This is a missing feature in our SubtleCrypto implementation.

Oo interesting, a javascript crash. Looks like we got a keydown, which the page had hooked, and then messed something up when executing the bytecode that invalidated the declarative environment...

The same type of crash, but without a debug build and real symbols for Interpreter::run_bytecode, and JS::DeclarativeEnvironment we can't possibly know for sure. Everyone uses AK::Vector everywhere, and its member...

If a BUILD_SHARED_LIBS=ON config on linux is not supported, then this can be worked around by explicitly setting it to off for SwiftCollections like so: ``` set(BUILD_SHARED_LIBS_SAVE ${BUILD_SHARED_LIBS}) set(BUILD_SHARED_LIBS OFF)...

Does that mean that swift-collections will be available as a dependency shipped with the toolchain for "external" consumers to use in the future? Similar to how swift-testing is handled? Or...