Sami Vaarala
Sami Vaarala
Ok, I'll do that. The only non-trivial thing is to figure out where that array should go :)
It seems `uv` has a bunch of misc bindings as well, so maybe `uv.argv` or `uv.get_argv()`?
To mimic Node.js it could be`process.argv` but since DukLuv is not trying to emulate Node.js that's not really a big point. Placing it in `uv` would at least have the...
I thought of `misc.c` as the place to implement because of this: https://github.com/creationix/dukluv/blob/master/src/duv.c#L104-L123; it already contains things like `cpu_info()` and other odds and ends.
Yeah, one simple approach would be to construct the argv array in `main()` and just stick it in the global stash and let `uv.argv()` then read it from there. Or...
It'd be nice to read it back from libuv but that doesn't seem possible. I'll open a pull with a proposal, thanks!
With the JSON fast path enabled the JSON encoding is relatively well optimized, CBOR is not refined to such an extent which explains some of the difference. In principle it...
If you happen to test CBOR performance with DUK_CBOR_{TEXT,BYTE}_STRINGS enabled, it'd be nice to know how much impact that has. The same level of overhead would be eliminated after the...
Thanks for the measurements :+1: > Fastest encode was with DUK_CBOR_BYTE_STRINGS but then decode becomes very slow for some reason. This is probably because when decoding back, CBOR byte strings...
duk_create_heap_default() is not an exposed function, it's a macro in duktape.h.