Paul Wais

Thinking on this point a bit more, there are a handful of tricky issues here: - Java -> C++: `GetPrimitiveArrayCritical()` requires no JNI calls until a `ReleasePrimitiveArrayCritical()`, so the user...

> What I envision (for starters) is a way to exchange a persistent area of memory to which both sides have read/write access. For Java C++, one would need to...

Now that https://github.com/dropbox/djinni/pull/95 hit master, is this issue closed? Thanks @mknejp !!!

My vote would be to have #95 fulfill the ByteBuffer issue; at least my intention is to use that mechanism. `java.nio.ByteBuffer` isn't necessarily the best solution-- `ByteBuffer`s still have a...

@mknejp did you ever poke much farther on this? I'm curious if you ended up implementing anything for Java C++. I dug into this a bit further with the presumption...

FWIW, am hacking on the C++ Java part of this in https://github.com/pwais/djinni/tree/pwais_perf2 (NOT in preview state yet) with the goal of supporting at least {byte[], (direct) ByteBuffer, Unsafe} C++ using...

Really want to finish the C++ Java work I had started earlier (linked above), but have been inundated with other things. In that change, `JHeapArrayHandle-inl.hpp` has all the bits for...

Yea, the generated ctors (and lack of a default) can definitely get annoying quickly. @artwyman what about including this option so that it's not breaking, either in the record def...

I think the expected behavior of default ctor is a function of what language shapes your perspective. C++ and Obj-C expect allocation without initialization; Java does not. Could we add...

My use case is performance-sensitive, and the maintainers of my code will have an understanding of multi-language initialization behavior. (And oblivious users will be isolated from the issue through an...