Dylan Thacker-Smith

@etiennemartin Modules are not just a backwards compatible extensions to scripts, so it isn't just going to change using the current APIs. Support needs to be added for the separate...

I think that is expected. Although, the documentation could be updated to make this clearer.

It seems like the documentation has already answered your question, so your example isn't supported. Instead of resolving the promise from another goroutine, send the result over a channel to...

Good point. For context, v8go does internally use v8::Locker on the isolate, which provides some type safety. However, the primary reason for its use is to handle the fact that...

I don't think it makes sense to hide the v8 context, since it has a broader purpose than context.Context. Also, I think supporting the full context capabilities internally to v8go...

[Variable-length arrays](https://en.wikipedia.org/wiki/Variable-length_array) are a part of the C99 standard, although then became an optional feature in C11. It looks like this might be because they got considered a bad practice,...

Do you mean Alpine Linux? There is already a linux build of v8go. Are you having any issues with using the pre-built v8 library for linux that is bundled with...

I see, it isn't actually creating a fully static executable because of dependencies on the system's libc. If v8 were statically compiled against musl, then perhaps we could completely get...

Note that the Go build constraints don't have builtin [build constraint](https://pkg.go.dev/cmd/go#hdr-Build_constraints) support for distinguishing between linux distributions or libc implementations. So even if we wanted a separate pre-compiled v8 build...

> Isolates and Context are NOT thread safe Does this mean we can get rid of the use of v8::Locker in v8go.cc? Since this would just add unnecessary overhead if...