4 ms·
Wow. The fact that you care about this being stable implies that you plan to use this "for real"; the fact that you actually implemented this implies you care
by marvy 6y ago
Wow. The fact that you care about this being stable implies that you plan to use this "for real"; the fact that you actually implemented this implies you care enough to put in some real work. So you must have a use case in mind, and I am not imaginative enough to guess what it might be. Is it just about convenience so you don't need to bother with putting your C++ code in a different file? Or is there more to it?
- ogoffart 6y agoI'm using this to write Qt bindings: https://github.com/woboq/qmetaobject-rs/ https://github.com/woboq/qmetaobject-rs/ > Is it just about convenience so you don't need to bother with putting your C++ code in a different file? Yes, mostly. I find that having the code in place makes a big difference. I do not like useless levels of indirection and context switches while coding. This way is much better then having to edit three files (the .cpp, the ffi module, and the caller) each time I want to do a call into C++ while making sure they are in sync.
- marvy 6y agoThat actually makes sense! Cool!