Dylan Thacker-Smith
Dylan Thacker-Smith
> Actually, now that I think about it, we need to fall back to KEYS if the SCAN yields a Redis::CommandError Having it be possible for KEYS to be send...
> I don't think it's in a state to be published though. You can open it as a draft PR to indicate that it isn't quite ready as well as...
Fundamentally, the GC can't be designed to manage memory growth for a heap that it doesn't know about. Otherwise, it won't know that when that memory it doesn't manage is...
> Go would then know about the allocations but Go's GC still wouldn't be able to make any use of it because it ignores cgo heap. So if all one...
> What I am doing instead though is I've added a pre-GC hook in V8 which calls into Go to run there runtime.GC(). The idea being that the V8 GC...
> What I thought might be good would be a `iso.Prune()` that would free all the values that are being tracked against that isolate. Doesn't that prevent the ability to...
The approach I'm looking into is to more closely match c++ API by: * turning `Value` into an alias to `LocalValue` * using a `Isolate.HandleScope(func())` to explicitly enter a top-level...
V8 is written in C++, so cgo is needed to use it. Your issue looks like https://github.com/rogchap/v8go/issues/83, but it looked like that might have been for an old version of...
> TQMH Your abbreviation is too obscure for me and for https://www.abbreviations.com/TQMH > **project path exec go test -c** As is `project path exec`, although I'm guessing it sets up...
Oh, you are trying to run the v8go tests on windows with the latest commit. So as I already mentioned > Note that this project is actually in need of...