Linus Groh
Linus Groh
See https://github.com/test262-fyi/eshost/pull/17 for a full example of adding a new engine to eshost.
Of course I have, that's why I already migrated away from vue cli to vite recently :) There are several dependencies incompatible with Vue 3 that need to to be...
I would go with option 1 too, for a few reasons: - It is presented as an example in the Zig 0.14 release notes: https://ziglang.org/download/0.14.0/release-notes.html#addLibrary-Function ```zig const linkage = b.option(std.builtin.LinkMode,...
I think this can be closed now that #761 is merged :)
Possibly related: #20468
Upstream eshost and test262-harness are effectively unmaintained, so test262.fyi uses these two forks: - https://github.com/CanadaHonk/eshost - https://github.com/CanadaHonk/test262-harness @CanadaHonk [added boa support](https://github.com/CanadaHonk/eshost/blob/master/runtimes/boa.js) to the eshost fork, test262-harness doesn't need any additional...
Might be related to #48
Yes, I don't mean to block this PR - IMO these changes are good as is while preserving the status quo of how the global object customizations are spec'd.
> Checking the downstream specs, nobody references `SetRealmGlobalObject`, `CreateRealm`, or `SetDefaultGlobalBindings`. It's worth noting that https://tc39.es/proposal-shadowrealm/#sec-shadowrealm will need an update.
> we found some weirdness introduced by these changes, specifically, the fact that calling `InitializeHostDefinedRealm()` changes the execution context to the newly created realm. That was already the case before....