API support for dealing with interned strings directly

When C code operates on object properties a C string is passed in (usually a literal but can also be a dynamic input). All such operations will be slowed down by the need to intern the string.

Internally property operations are ultimately always performed using interned strings (duk_hstring *) and since it’s already possible to get a borrowed reference to a heap object, interned strings can already be used for property accesses e.g. as:

duk_push_heapptr(ctx, my_string_ref);
duk_get_prop(ctx, obj_idx);

It would be nice to improve that to e.g.:

duk_get_prop_heapptr(ctx, my_string_ref);

This could be implemented a bit faster internally because the unnecessary value stack push can be avoided.

Naturally there are many API variations, like:

• Instead of using the generic duk_get_heapptr() provide a dedicated API call to intern a string.
• For long lived strings it might be useful to be able to void *mystr = duk_something(ctx, "my_key"); which would store a stash (or other persistent) reference so that you wouldn’t need to worry about string reachability.

But as an initial step, being able to use a borrowed key reference more directly would be easiest.

[svaarala]

Yes, there’s no difference from the internals point of view.

[fatcerberus]

I thought it more important to achieve a functional 1.0.0 rather than keep on rewriting the building blocks over and over for performance (which is also important, but having a baseline release is maybe more important).

Oh, I agree 100%. If it weren’t for Duktape, Spherical still wouldn’t have a modern engine, so I’m glad you released it 😃