Olivier Goffart

Thanks for the bug report. Pinning the struct would not really help as it removes the benefit of using cpp_class at all, that is, generating the impl for Clone, Default,...

> the idea of cpp_class! appeals to me precisely because of its direct style of integration: the resultant struct is the C++ object. Yes, that's right. maybe we could have...

@guruz The migration strategy is that first, the client understand new algorithm, and then later the server would use them. (Although the server can use serveral at the same time,...

I'd like to add a comment here relative to my experiments relative to the efficiency of niches. It all started because I wanted to implement the use of niche for...

From what I understand, this is the difference in philosophy between the two project. `qmetaobject` aim at just providing a idiomatic Rust API to use QML without having to care...

> While I appreciate qmetaobject and qttypes, I personally think using cxx is a better way forward in the long term than the unsafe cpp approach of embedding arbitrary C++...

Any update? I was trying to do some type safe unit handling, and this would be quite welcome. Edit: but actually it would also be nice to have it in...

PR 6915 adds Open in browser, other actions can be performed from there, i think this is enough.

It appears that the problem is that the destination of the move is not marked as a faillure as far as the socketapi is concerned. That should be easy to...

I suspect the problem is that clang crashes while parsing the compilation database. Can you try running valgrind, this will probably show some more details about what pointer was invalid....