Jerome Gravel-Niquet

Unhandled promise rejections can happen at random moments, I don't think assuming they might only happen when calling C from go is right. I bet it'll often happen right after...

> We can't pass go pointers to C because of the cgo rules. See the comments in v8.go about callbacks. Ah, good to know! > I think the RunMicroTasks is...

I think you can get most of that information from C++ without doing much in go. ```cpp static void OnPromiseReject(PromiseRejectMessage message) { Local promise = message.GetPromise(); // Get the isolate...

For some reason, this doesn't work with all kinds of values... or something. I'm trying to make the whole ctx.Create use one handle scope, but started getting fun errors: ```...

I was wrong, apparently that doesn't keep the locker or any other scope alive. It appears you don't need the locker or anything of the sort to create all kinds...

Update time: I was getting the scope errors because of switching threads. I made a `handleScope` which essentially queues functions to run in scope. The go ctx scope callback locks...

Ok, I woke up realizing that benchmark was unfair. I was not getting and putting the scope back during the benchmark, which the other one does. With that in place,...

This is "best effort" according to the v8 docs, but we could maybe use `SetWeak` on the persistent value: https://v8.paulfryzel.com/docs/master/classv8_1_1_persistent_base.html#aebb8a2c97e219102f613ff3749c956f6 I'm not entirely sure how we'd be able to determine...

I've been playing with `LowMemoryNotification` when the heap gets too high. It mostly works, but then will segfault if there's too much concurrency. For example: ``` context(9423,0x70000539f000) malloc: *** error...

Ok, I fixed my segfaults by using the `ISOLATE_SCOPE` macro, my bad for not using it before 🤦‍♂️ I also tried setting the `Value`'s `release` method as `Release` and am...