Simon Ask Ulsnes

Also keep in mind that we need to match column names in cross-binding usage scenarios (such as sync). :-) This also means that things like the _table name_ must be...

Perhaps an approach like what V8 does can be employed, where adding a new property causes a new "type" to be generated, and each type contains a map of which...

I wrote up a small ~100 line proof-of-concept in C++14. Could you read through it and let me know if it more or less matches what you had in mind?...

Coming up on the 2-year anniversary for this issue, are there any current plans to support this? If nothing else, it would probably be good to catch any use of...

If this is still relevant, please do submit a PR, I would be happy to look at it. :-)

It would be helpful to know if the behavior is different here from `unsafe-libyaml`. This library is intended to be "bug-for-bug" compatible, so that's important (but that doesn't mean we...

> I think interior mutable access is still unsound without a runtime check due to reenetrancy/aliasing through JS. Can you elaborate? I believe you need a `&mut Isolate` (such as...

I should perhaps have explained more clearly - apologies. This technique is inspired by [qcell](https://docs.rs/qcell/latest/qcell/), where interior mutability is achieved by "outsourcing" it to something other than the physical memory...

However, I should point out: As is, this API is not safe in the presence of multiple Isolates. If you can produce two overlapping `&mut v8::Isolate` (e.g. by creating two...

> thanks for clarifying, i should've read the patch before commenting :) No worries :) > v8 doesn't generally prevent you from doing this, it will happily corrupt itself. though...