Allow using normal quickjs as a feature

[cheesycod]

Normal quickjs, to my understanding, does have its own special optimizations like rope/cons strings etc. As such, it would be nice if rquickjs could support normal quickjs (not quickjs-ng) as a feature flag?

[nabetti1720]

The bindings generated may be different because the functions exposed are different (e.g., ng recently added support for PromiseHook). So it may not be easy to control with feature flags.

Although it may divide the community, one idea is to fork the current implementation, prepare a rust binding called rquickjs-ng, and revert the current rquickjs to the rust binding of bellard/quickjs.

Of course, it goes without saying that it would be best if the two quickjs were integrated. :)

[Sytten]

At this point the two projects have diverge and they are not going to integrate. It will be hard to have a unified interface.

We could potentially create a unified core with two crates on two for each implementation.

[richarddd]

Possibly yes. We likely have to feature gate the bindings and have two submodules for sys.

[MulverineX]

Looks like rope strings are on the way for quickjs-ng quickjs-ng/quickjs#1324

[Sytten]

Honestly I prefer working with the ng maintainers, bellard as brilliant as he is doesn't seem interested to work with others. Glad to see this port.