snek
snek
@dSalieri you can think of it as the source location, here's an example: https://engine262.js.org/#gist=74ea9624bb9f61a9b1c42f7c26ce9417
it hits a spec assertion... we generally consider that type of bugfix to be editorial right?
is this still a thing?
@essen so should i clone cowboy and update the makefile to point to my branch? i've never really worked with erlang directly before 😅
I would guess it is because createAbortSignal+makeTransferable does a lot of prototype mutation stuff and a call into c++ which is basically the bane of js engine performance. i think...
Looking at this more, it seems like we just need to teach v8 how to recognize non-c++-backed "host" objects, and then we wouldn't need to add the JSTransferable superclass. oop...
I don't think we need to do anything at the standards level, if v8 just had an api to tag constructors with a private symbol or similar, it could forward...
My understanding is that they compiled the core nodejs logic to wasm and stubbed out other stuff (like V8) with fake functions that use browser apis. You'd have to ask...
`console.log` is not calling your function, so it would be incorrect for it to be there. at the top level, the script itself is the caller and it is not...