rusty_v8 issues

Add support for Fast calls with Uint8Array

Similar to #1039 but this one uses v8 `10.5` branch

Rolling to V8 10.5.218.2

Add x86_64-unknown-linux-musl library release

5

This adds x86_64-unknown-linux-musl as a new supported target for the pre-built rusty_v8 library releases, which should avoid multiple downstream consumers having to build this themselves. This target is useful when...

cd-work

Get link errors when upgrading rusty_v8

2

When I use rusty_v8 as a dependency and it gets upgrade, it doesn't seem to use the new `librusty_v8.a` because I get link errors if the ABI has changed. For...

ry

Mismatched behavior for json stringnify

1

# Summary I don't know if it is **by design**. While testing the performance of JSON stringnify, I found there's a mismatched behavior between using `v8::json::stringnify` and direct evaluation. The...

h-a-n-a

Function pointer types are invalid

5

Recent addition of Fast API calls (at least) use the types `*const c_void` in Rust and `void*` in C++. This is not strictly correct on all platforms, see f.ex. https://rust-lang.github.io/unsafe-code-guidelines/layout/function-pointers.html#representation...

aapoalas

`impl_try_from!` for `Integer` is misleading / too strict

The `TryFrom` macros for the `Integer` class are defined with a conditional on `Value::IsUint32() || Value::IsInt32()`. This is correct in the strictest sense that `Uint32` and `Int32` are the only...

aapoalas

Unreachable code reached in `ScopeData::get_current_mut(isolate)` called from external interrupt handler

2

If an external interrupt handler is used to call back into `rusty_v8` using `CallbackScope` to initialise a call stack, there is a chance that the creation of the `CallbackScope` will...

aapoalas