quickjs (normal) support

[cheesycod]

As quickjs (the normal version) has its own optimizations that quickjs-ng doesnt have like con/rope strings, it'd be nice for quickjs-rusty to have optional support for quickjs (the original one, not ng) as a feature flag

[Icemic]

Hi, I had considered this, but it's actually quite challenging to implement, especially given the many existing differences between quickjs and quickjs-ng (MSVC support, BigNumber, some exported functions, etc.).

If your focus is solely on rope strings, you might want to join the discussion quickjs-ng/quickjs#1002 and quickjs-ng/quickjs#1144 . What I mean is, this seems more like an issue that needs to be addressed in the upstream project.

However I'll keep this issue open for further discussion.

[cheesycod]

Ah alright

Also, this is completely unrelated to this issue right now, but could quickjs-rusty support JSClassDef for creating 'exotic' classes with arbitrary properties.

[Icemic]

Ah alright

Also, this is completely unrelated to this issue right now, but could quickjs-rusty support JSClassDef for creating 'exotic' classes with arbitrary properties.

Sorry but no, it is out of goals of quickjs-rusty, which aim to provide simple, easy-to-embed QuickJS bindings rather than tightly coupled rust-quickjs interoperability.

You may prefer to rquickjs for those features.