snek

Not sure whether to call this a bug or a feature request, but it should definitely be fixed.

in V8 at least (relevent for node), using the same intrinsics will provide negligible cpu/memory benefits because it already uses the same ones internally: https://v8.dev/blog/embedded-builtins

@bmeck in the section you link they mention reworking most of the indirect calls into single lookups relative to the root I'm sure this still has good security reasons to...

The esm cache is not exposed, and even if it were, it is not mutable. What you want is hot-reload functionality, which has been mentioned in [v8:10476](https://bugs.chromium.org/p/v8/issues/detail?id=10476).

i think package exports can disallow importing your cli entrypoint. I also believe that "you've imported the wrong file" isn't specific to cli entrypoints, there are lots of files that...

@guybedford i'm still fundamentally opposed to this feature. even among people who want it, there is disagreement about what qualifies as "main". With TLA you could do `if (await import.meta.resolve(process.argv[1])...

This backtrace doesn't make much sense to me, CodeRange allocation is not part of setting up the stack. Maybe try a debug build to get a better backtrace?

I don't know much about macOS code signing and I don't have a mac, so I can't really advise you further here.

wow this looks identical to my local changes to this lol. could you update the module_snapshot test to use a new group? that will prevent it from being flakey when...

maybe a hot take, but i think anything involving external async runtimes should be left out, since there isn't actually any integration with e.g. tokio being provided (most notably with...